Hello, I'm planning a major upgrade, form 1.3.2 to the current version. And I'm wondering if this is going to work... I don't care about the configuration files, I could easily apply any modification to the config files that come with the new version. But what about the database and the tickets (stored on the filesystems)? Are these going to survive? Is it enough to apply the DB-upgrade scripts, and everyone is happy? Any comments, thoughts or pas experiences would be appreaciated. Best regards, Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gilles Massen schrieb am 07.09.2007 9:11 Uhr:
Hello,
I'm planning a major upgrade, form 1.3.2 to the current version. And I'm wondering if this is going to work... I don't care about the configuration files, I could easily apply any modification to the config files that come with the new version. But what about the database and the tickets (stored on the filesystems)? Are these going to survive? Is it enough to apply the DB-upgrade scripts, and everyone is happy?
Any comments, thoughts or pas experiences would be appreaciated.
Best regards, Gilles
Hello Gilles,
We run OTRS since the 1.3.x Series, upgraded to 2.0.4 and now to 2.2.1
recently. We are running with the same DB holding the Tickets ever
since and are happy with this.
The only thing you have to asure is to execute EVERY DB Upgrade Skript
since your actual Version:
.) backup everything eg.:
cp -r /opt/otrs/Kernel/ <destination>
/usr/bin/mysqldump -A -u otrs -p <destination>/backup.sql
cat crontab -u otrs -e > <destination>
.) make sure you backuped everything
.) update source to 2.2.x (our your desired Version)
.) execute upgrade skript
Hello Franz, Thanks for your reply (and sorry for the late follow-up). [...]
We run OTRS since the 1.3.x Series, upgraded to 2.0.4 and now to 2.2.1 recently. We are running with the same DB holding the Tickets ever since and are happy with this. The only thing you have to asure is to execute EVERY DB Upgrade Skript since your actual Version: [...]
That's good to know, and fairly reassuring. How did you manage the config files? Did you keep them from one version to the other, did you diff them, or drop them alltogether? Best regards, Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473
We basically did the same thing.. We basically just ran database upgrade
scripts and exported the sysconfig then reimported it back once the upgrade
was done.
Of course you want to back up your files before doing this though.
-Andy
On 9/25/07 5:24 AM, "Gilles Massen"
Hello Franz,
Thanks for your reply (and sorry for the late follow-up).
[...]
We run OTRS since the 1.3.x Series, upgraded to 2.0.4 and now to 2.2.1 recently. We are running with the same DB holding the Tickets ever since and are happy with this. The only thing you have to asure is to execute EVERY DB Upgrade Skript since your actual Version: [...]
That's good to know, and fairly reassuring. How did you manage the config files? Did you keep them from one version to the other, did you diff them, or drop them alltogether?
Best regards, Gilles
--
participants (3)
-
Andy Lubel -
Franz Ferdinand Esberger -
Gilles Massen