--------------------------------------------------------------------- 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
If I understand correctly and you are taking a backup of your 3.1 database and restoring it to a different server on 3.3, you still need to run the SQL extents scripts in the installers to do the database modifications. You would do best to install the 3.1 version on the new system, then upgrade to the 3.2.x path, then to 3.3. This way you can be sure you did not miss any steps.
Good morning,
In my case I did the following, which worked perfectly fine:
a. Update all installed AddOns to the latest possible version for OTRS 3.1
b. 3.1.x->3.2.12 (follow the upgrade document found here: http://doc.otrs.org/3.2/en/html/upgrading.html
c. Update all installed AddOns to the latest possible version for OTRS 3.2
d. 3.2.12->3.3.3 (follow the upgrade document found here: http://doc.otrs.org/3.3/en/html/upgrading.html
e. Update all installed AddOns to the latest possible version for OTRS 3.3
I practically did the same thing as you did. Moved to a new server and update to the latest OTRS version, at that time 3.3.3. Worst part was, moving from a Windows server to a CentOS server (the bad part was getting rid of all Windows specific stuff in the config files).
If you move to a CentOS (6.5) server, I can give you a small part of my own upgrade documentation, with which you can easily install/update the AddOns on the server directly using the “otrs.PackageManager.pl”, kind of a checklist thing. (would also work with RHEL 6.5)
Just let me know.
Cheers,
Fabian
I practically did the same thing as you did. Moved to a new server and update to the latest OTRS version, at that time 3.3.3. Worst part was, moving from a Windows server to a CentOS server (the bad part was getting rid of all Windows specific stuff in the config files).
If you move to a CentOS (6.5) server, I can give you a small part of my own upgrade documentation, with which you can easily install/update the AddOns on the server directly using the “otrs.PackageManager.pl”, kind of a checklist thing. (would also work with RHEL 6.5)
Consider donating the whole document to the project. Enough people do this that it’d be a valuable addition to the project documentation
Hello All,
sure thing, will do! Just have to cleanup the documentation a little bit. Will provide it by the end of tomorrow :)
Cheers,
Fabian
Von: otrs-b...@otrs.org [mailto:otrs-b...@otrs.org]
Im Auftrag von David Boyes
Gesendet: Mittwoch, 19. Februar 2014 15:58
An: User questions and discussions about OTRS.
Betreff: Re: [otrs] How to migrate from 3.1.10 to 3.3.4
I practically did the same thing as you did. Moved to a new server and update to the latest OTRS version, at that time 3.3.3. Worst part was, moving from a Windows server to a CentOS server (the bad part was getting rid of all Windows specific stuff in the config files).
As my original message is still sitting in the approval queue, here without attachments.
Regards,
Fabian
Von: Fabian Reichardt
Gesendet: Donnerstag, 20. Februar 2014 13:26
An: User questions and discussions about OTRS.
Betreff: AW: [otrs] How to migrate from 3.1.10 to 3.3.4
Hello All,
as promised, please find attached the documentation I created for our OTRS upgrade 2.4.5 -> 3.3.3. As this was a German documentation, please bare with me if there are any German screenshots or words in it.
It should be now issue to replace the 3.3.3 files with the 3.3.4 files and then follow the steps shown in the documentation. Unfortunately I do not use KIX4OTRS, as there was now version available for 3.3.3 at that time.
If you have any questions about it, please feel free to ask ;)
If there is an issue with the attachments, I’ve uploaded them as a zip file here: https://app.box.com/s/c3xbr03tgfrmg6t2jcp1
Regards,
Fabian
Fabian Reichardt
Consultant
cbs Corporate Business Solutions Unternehmensberatung GmbH
Im Breitspiel 19 | 69126 Heidelberg
T +49 6221 3304-0 | F +49 6221 3304-200
fabian.r...@cbs-consulting.de |
www.cbs-consulting.com
/opt/otrs/var/tmpUsually User and Group is "www-data" which differs from system to system. (wwwrun, www, nogroup, apache, ...)
chown -R otrs:www-data /opt/otrs/var/tmpUsually "/opt/otrs/bin/otrs.SetPermissions.pl" should also do the trick, but in some cases, it does not.
/opt/otrs/bin/otrs.UnlockTickets.pl --timeout >> /dev/null(If you don´t do this, it would be done by cron every hour...)
-- ------------------------------------- Friedrich Koelbel http://www.graz4u.at -------------------------------------