Correct way to move from 2.0.x to 2.2.7 on new hardware/server?
Dear collegues, we are running OTRS 2.0.x in production on FreeBSD 6.x + apache 1.x. Now we need to secure some minimal (in order of minutes) interruption of service while moving to 2.2.7. Here below is my step-by-step plan to achieve this; what I'd like to ask you is your comments, additions and suggestions - is the plan correct? what are my mistakes? is it suboptimal, maybe? Thanks in advanse. 1. Install new hardware server, install and configure FreeBSD 7-STABLE (as of today) on it. Install up to date ports and packages. (this has been DONE). 2. Install up to date Perl, Apache 2.x and MySQL 5.x on a new system (this is in progress now). Install OTRS 2.2.7 but skip initalization of the database (is it correct?) 3. Run ~otrs/scripts/backup.pl -d /var/tmp -c bzip2 -t fullbackup on an old 2.0.x system. This should give a complete packed copy of an old installation. Problem #1. bash-2.05b# time ./backup.pl -d /var/tmp -c bzip2 -t fullbackup Backup /var/tmp/2008-07-04_11-58/Config.tar.gz ... tar: Kernel/Config/GenericAgen*.pm: Cannot stat: No such file or directory ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ????? tar: Error exit delayed from previous errors. failed Backup /var/tmp/2008-07-04_11-58/Application.tar.gz ... ^Cfailed ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ went asleep, probably forever Dump MySQL rdbms ... done Compress SQL-file... done real 25m30.840s user 15m11.339s sys 0m32.480s bash-2.05b# What I'm doing wrong? Or do I need to stop apache before running ./backup.pl ? 4. Suppose I got a correct nice backup of the 2.0.x install. Ok now I copy the backup to a new system and run restore but database only (BTW how do I do this, namely - restore database without overwriting everything else? Or maybe it's better to restore full backup first, and install 2.2.7 over it then? 5. Ok this way or that, but I have a copy of old DB and config on a new system, but with 2.2.7 code. Now I run conversion scripts 2.0-to-2.1, 2.1-to-2.2. Voila? Will I have a ready new OTRS 2.2.7 system with all my data preserved at this moment? Thank you for your time and help! WBR, Andrew
Den 04/07/2008 kl. 12.35 skrev Andrew Stesin:
2. Install up to date Perl, Apache 2.x and MySQL 5.x on a new system (this is in progress now). Install OTRS 2.2.7 but skip initalization of the database (is it correct?)
That seems okay. You can even initialize the database to set it up correctly.
3. Run ~otrs/scripts/backup.pl -d /var/tmp -c bzip2 -t fullbackup on an old 2.0.x system. This should give a complete packed copy of an old installation.
Yes, but are you sure you need that? The complete backup includes the 2.0.x application. If you have not changed anything in the Kernel/Output/HTML folder (i.e. created a new theme or hacked about an existing one), you only need your database, configuration and any attachmenths the tickets may have. You can create a backup of the database manually: mysqldump -u otrs -p otrs > otrs-database.sql It'll prompt you for the otrs password to the database. scripts/backup.pl also creates a dump of the database. Maybe that part is done before your backup crashes, look in /var/tmp (your specified output directory). The configuration of OTRS is simply extracted via SysConf in the Admin menu. There's a download-button.
4. Suppose I got a correct nice backup of the 2.0.x install. Ok now I copy the backup to a new system and run restore but database only (BTW how do I do this, namely - restore database without overwriting everything else?
Copy your database backup to the new system, then: mysql -u root -p otrs < otrs-database.sql It'll prompt you for the otrs password to the new database. I don't know if you have this yet since you haven't installed the database on the new system. You can set it up manually, though: mysql -u root -p mysql grant all on otrs.* to 'otrs'@'localhost' identified by 'your otrs password goes here'; This is assuming your database is called 'otrs'.
5. Ok this way or that, but I have a copy of old DB and config on a new system, but with 2.2.7 code. Now I run conversion scripts 2.0-to-2.1, 2.1-to-2.2.
Yes.
Voila? Will I have a ready new OTRS 2.2.7 system with all my data preserved at this moment?
Probably. As long as you haven't switched DNS or IP with the original server, you're able to log in to your new system and check it out before going live. -- Lars
participants (2)
-
Andrew Stesin -
Lars Jørgensen