
-----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