Upgrade process from OTRS 3.1.3 -> 5
Hello! I just inherited the job of updating our production IT HelpDesk server from a IT tech that is no longer here. Due to the nature of our setup in cannot be down for very long, which is why it was left to get so far behind. The server is currently running on OTRS 3.1.3 on a Ubuntu Linux 12.04 LTS server. I looked at the documentation for the process of upgrading here: https://otrs.github.io/doc/manual/admin/3.2/en/html/upgrading.html It sounds like I have to update from to every subversion e.g. 3.1.3 -> 3.1.4 -> 3.2.1 -> 3.2.2.... etc.. You get the idea. :) Is there a way to fast track theses updates? The idea is that we want to be on OTRS 5 once it is released. Is is possible to just perform fresh install of the latest OTRS and import and upgrade the database? Thanks. :) [image: Everett Community College] http://www.everettcc.edu/ Alex Zimmerman / Information Technology Specialist III Web Data & Development Services / Enterprise Services / Information Security Direct line:(425) 259-8724 / Help Desk:(425)388 9333 email: azimmerman@everettcc.edu [image: Twitter] http://www.twitter.com/liquidspikes [image: Linkedin] http://www.linkedin.com/in/alexzimmerman/ *How did I do? Please take a minute to help us improve our IT service by completing the * *IT Feedback Survey. http://goo.gl/J3nGC (http://goo.gl/J3nGC http://goo.gl/J3nGC)* *Thank you!*
Hi, 13/10/2015 18:00 - Alex Zimmerman wrote:
I just inherited the job of updating our production IT HelpDesk server from a IT tech that is no longer here. Due to the nature of our setup in cannot be down for very long, which is why it was left to get so far behind.
Typical (bad) scenario. Solution? Managed OTRS. Sorry that I am commercial on the mailing list, but actually this is an issue. And can be solved with a managed OTRS.
The server is currently running on OTRS 3.1.3 on a Ubuntu Linux 12.04 LTS server. (...) It sounds like I have to update from to every subversion e.g. 3.1.3 -> 3.1.4 -> 3.2.1 -> 3.2.2.... etc..
Nope. What you describe is "Patch Release" Updates... If you read the documentation carefully you'll find: ,--- | Within a single minor version you can skip patch level releases if | you want to upgrade. For instance you can upgrade directly from | OTRS 4 patchlevel 2 to version 4 patchlevel 6. `--- So you need to go to: 3.2.x -> 3.3.x -> 4.0.x -> 5.0.x (x = latest patch)
Is is possible to just perform fresh install of the latest OTRS and import and upgrade the database?
No. You have to follow the path. Good Luck. :) -- Florian
Thank you Florian!
[image: Everett Community College] http://www.everettcc.edu/
Alex Zimmerman / Information Technology Specialist III
Web Data & Development Services / Enterprise Services / Information
Security
Direct line:(425) 259-8724 / Help Desk:(425)388 9333
email: azimmerman@everettcc.edu [image: Twitter]
http://www.twitter.com/liquidspikes [image: Linkedin]
http://www.linkedin.com/in/alexzimmerman/
*How did I do? Please take a minute to help us improve our IT service by
completing the *
*IT Feedback Survey. http://goo.gl/J3nGC (http://goo.gl/J3nGC
http://goo.gl/J3nGC)*
*Thank you!*
On Tue, Oct 13, 2015 at 9:39 AM, Florian Edlhuber
Hi,
13/10/2015 18:00 - Alex Zimmerman wrote:
I just inherited the job of updating our production IT HelpDesk server from a IT tech that is no longer here. Due to the nature of our setup in cannot be down for very long, which is why it was left to get so far behind.
Typical (bad) scenario. Solution? Managed OTRS. Sorry that I am commercial on the mailing list, but actually this is an issue. And can be solved with a managed OTRS.
The server is currently running on OTRS 3.1.3 on a Ubuntu Linux 12.04 LTS server. (...) It sounds like I have to update from to every subversion e.g. 3.1.3 -> 3.1.4 -> 3.2.1 -> 3.2.2.... etc..
Nope. What you describe is "Patch Release" Updates...
If you read the documentation carefully you'll find: ,--- | Within a single minor version you can skip patch level releases if | you want to upgrade. For instance you can upgrade directly from | OTRS 4 patchlevel 2 to version 4 patchlevel 6. `---
So you need to go to: 3.2.x -> 3.3.x -> 4.0.x -> 5.0.x (x = latest patch)
Is is possible to just perform fresh install of the latest OTRS and import and upgrade the database?
No. You have to follow the path. Good Luck. :)
-- Florian
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Hi, 13/10/2015 18:00 - Alex Zimmerman wrote: Due to the nature of our setup in cannot be down for very long, which is why it was left to get so far behind. can you define what "not down for very long" means? Is there a defined timeframe? The server is currently running on OTRS 3.1.3 on a Ubuntu Linux 12.04 LTS server. You should also check the [1]requirements for OTRS 5. Maybe you need to upgrade/switch the server as well. I looked at the documentation for the process of upgrading here: [2]https://otrs.github.io/doc/manual/admin/3.2/en/html/upgrading.html It sounds like I have to update from to every subversion e.g. 3.1.3 -> 3.1.4 -> 3.2.1 -> 3.2.2.... etc.. Like already explained by Florian, you just need to take into account the major versions (3.2., 3.3 4, 5). --Mathias [1] http://otrs.github.io/doc/manual/admin/5.0/en/html/otrs.html#software-requir... [2] https://otrs.github.io/doc/manual/admin/3.2/en/html/upgrading.html
participants (3)
-
Alex Zimmerman -
Florian Edlhuber -
Mathias Bräunling