Your database needs to migrate through the 3.x releases, so consider that
you can't just skip the intermediate steps once you get it working on
staging.
As for the first step, you can very well start with 3.1.latest on the
staging server, restore your 3.0 database to it, then run the migration
steps in the UPGRAADING documentation.
For what you're attempting, you don't *have* to build 3.0.11 first on
staging, then blow away the files to upgrade to 3.1.latest ... with the
same database anyway.
Note that you will have to be cognizant of the 3.1->3.2 change from MyISAM
to InnoDB, but there's a utility to assist with that:
https://github.com/OTRS/otrs/blob/rel-3_2_18/bin/otrs.MySQLInnoDBSwitch.pl
There's more to it, of course, The docs are pretty good, but you should
note that much of your filesystem customization will need to adjust greatly
for the differing APIs.
Also, don't forget to include your Config.pm and Config Files that the
documentation asks for. They're important to make sure the configuration
changes process properly.
Please don't consider this as a substitute for the documentation. It
certainly doesn't contain all the instructions or caveats you'll encounter,
but you have not just a few steps to complete the upgrade.
On Mon, Nov 2, 2015 at 6:35 PM, Rob Mitchell
Greetings: We have been using OTRS 3.0.11 ITSM with very good stability and success, but now we'd like to upgrade to the latest version. The documentation states:
"If you are running a lower version of OTRS you have to follow the upgrade path to 4 first (...3.0->3.1->3.2->3.3->4)!"
I don't have any problem with doing the upgrades in sequence as directed, but I would prefer not to do so on the production server (an Amazon EC2 EBS instance running Ubuntu). I'd rather build a test server on a current clean build of the Ubuntu LTS version, upgrade that all the way up to the current version on the test box, then ultimately I would like to install a clean 5.0.x OTRS instance on a new EC2 VM and copy over the database and our config and support files. After testing we can simply edit the A Record to point to the new EC2 VM and press on. Does this sound like an appropriate upgrade path?
In order to build a test environment to do this should I start off by installing 3.0.11 on a test box, then restoring our OTRS directory and restore a copy of the database, then upgrade to 3.1, or is it possible to install a 3.1 instance and upgrade the database on it? Thanks in advance for your advice.
Kind regards, Rob in Memphis
--------------------------------------------------------------------- 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