Restore issue

[vmotrs]

Hello Guys,

I have some issues to restore my OTRS environnement from my production environment to my backup machine, and after checking the forums, I still can't find the reason why.
Maybe someone can help me or give me some tips...
My production machine is the following
Ubuntu 11.10 (GNU/Linux 3.0.0-22-server x86_64) / OTRS 3.0.10 /Packages : FAQ - MasterSlave - Support - SystemMonitoring
My backup machine is the following (virtual machine - VBox)
Ubuntu 11.10 (GNU/Linux 3.0.0-22-server x86_64) / OTRS 3.0.10 /Packages : FAQ - MasterSlave - Support - SystemMonitoring

I'm doing my weekly backup with the following script, launched by cron:
/usr/share/otrs/scripts/backup.pl -d /home/commun/NetDisk/09-BckupOTRS/

On My BackUp Machine, I have installed OTRS from scratch (same release as the production : 3.0.10), then I have copied the backup data from production machine, then I ran the restore.pl script.
First, I got an error message because the RELEASE file was missing from my backup machine... After checking, I have noticed that otrs is installed under /usr/share/otrs on my production machine and under /opt/otrs on my backup machine !! So, I've add a symlink named otrs under /usr/share/ pointing to /opt/otrs/ and I have launched the restore.pl script again. I don't have the error about RELEASE file anymore, but this time, I got an error saying that the DB is not configured in my envronment..and I should define which DB engine I want to use (mysql , pgsql or other). [sorry, I don't have the error message here... I'll copy it here later]

I'm wondering what I'm doing wrong... any tips are welcome.
OTRS on my both environments are using MySQL engine and both environments are working fine... but I need to have the possibility to migrate my data from 1 machine to another machine.

Thanks in advance
Best Regards
Vincent

[crythias]

While the restore script may be useful in some circumstances, it may not in others, especially if you've tar'd in one folder and expect it to untar in another.

So ... untar the backups in a temp folder and copy/paste to the new location
Know that Config.pm in the different folder may need to be adjusted to reflect the new path.

as for MySQL, that should likewise be a standard mysql read from .sql file. Note that your mysql backup may be compressed, so uncompress it before restore.

[vmotrs]

Hi Crythias,

Thanks for your reply. I have found the reason of my issue.
On my production machine otrs was installed using the 'apt-get install otrs2' command (long time ago) and on my new backup machine I have installed otrs using a procedure I have found here: (http://wiki.otterhub.org/index.php?titl ... %2810.4%29).
Both installation processes are working but they are slightly different... that's why the restore process is not working !

To fix my issue, I have installed otrs2 using apt-get install otrs2 on my backup machine and this time the restore process is working fine.

A little comment : before launching the restore process, I have to manually drop and recreate the otrs2 DB in mysql (the restore process doesn't accept to restore if tables are present in the database). It seems to be a little bit weird for me ? Am I doing something wrong ?

Thanks for your precious help anyway
Regds
Vincent

[crythias]

I have installed otrs2 using apt-get install otrs2 on my backup machine and this time the restore process is working fine.

ok. but for some reason that would tell me otrs2 not otrs3. but if it works for you...

A little comment : before launching the restore process, I have to manually drop and recreate the otrs2 DB in mysql (the restore process doesn't accept to restore if tables are present in the database). It seems to be a little bit weird for me ? Am I doing something wrong ?

Whether it seems to be a little bit weird or not, consider that a restore is a destructive process and relies on the schema stored with the backup, which may be different from the schema of the destination of the same name.