Instant Infrastructure
URGENT: Backups and Upgrading to a new JumpBox from an old oneSubmitted by blang on Thu, 07/03/2008 - 8:17am.I'm in the process of upgrading from otrs 1.0 to otrs 1.1.0. Unfortunately when I go to restore the backup from the old JumpBox on the new one, I get errors. The most common error is: Error: couldn't run tar When I attempt to unzip the archive I get this error from WinRAR: ! \\srv-bkup\OTRSBackup\jb-otrs-1.0-20080703013002\bu.tar: The archive is corrupt So my backups for the last several months all look to be corrupt, and I am unable to get the new JumpBox up and running. This is an Urgent item as we are running this system in production and have no reliable backup in place. |
Search |
Thank you
I would like to publicly thank Austin for the time he spent with me troubleshooting my backup/restore problem. AT no point during the last seven weeks did I feel that my data was in danger. I was uncomfortable with the fact that I couldn't do an automatic backup and restore, but I was able to successfully dump the database manually at any time (and did so, many times). I knew that I could fall back on this dump at any time. We also maintain a separate email archive of all incoming messages, so those could be redirected back into OTRS if necessary.
Ultimately, the solution to this problem was to do a full manual backup.
I ended up doing a manual dump of the database from the original 1.0 JumpBox. On the new 1.1.2 JumpBox, a number of steps were required:
* drop the predefined database
* create the database
* insert the data from my manual dump
* run the OTRS MySQL upgrade script
* run the OTRS upgrade script in perl
* run the post-perl OTRS MySQL upgrade script
I'm not going to post the technical details as I've given them all to Austin so they can be implemented in the 1.1.3 JumpBox. :)
Finally, to cover all the bases, I was able to run a backup on the 1.1.2 JumpBox and restore it to a fresh copy of the 1.1.2 JumpBox. Everything worked as expected.
Thank you again Austin.
Brian.
Also, have you manually ran
Oh, one more thing with trying restores. You should not try to reuse one after a failed restore. So what I suggest is that you get your 1.1.0 jumpbox setup take a snapshot that you can revert to until we figure out what the problem is. After a failed restore, you can revert and try again.
Austin
Also, have you manually ran
Also, have you manually ran a backup? And if so does it show an error of some sort when you run it?
Which restore method are you trying?
Austin
could you email me the
could you email me the output of 'tar -tzf' on the file to me at godber at jumpbox dot com?
Austin
OK, I did a tar -xf on
OK, I did a tar -xf on archive I listed above. It generated no errors.
However, I am unable to restore from this archive into my 1.1.0 jumpbox.
Most recent backup filename
Most recent backup filename (from 1:37 this morning): jb-otrs-1.0-20080703013002.tgz
Most recent backup filename
Hmmm,
Can you SSH into the JumpBox and run 'df -h' and paste the output here.
Austin
Most recent backup filename
Also, I am not familiar with WinRAR and during our backup process we do something slightly strange that could make it unhappy. So I wouldn't jump to the conclusion that the backups are bad. What we need to do is use linux tar to see if the archive is OK.
Austin
Output from "df
Output from "df -h":
Filesystem Size Used Avail Use% Mounted on /dev/sda1 965M 536M 381M 59% / varrun 126M 80K 126M 1% /var/run varlock 126M 0 126M 0% /var/lock udev 126M 60K 126M 1% /dev devshm 126M 0 126M 0% /dev/shm /dev/sdb1 9.9G 552M 8.9G 6% /storage /storage/tmp 9.9G 552M 8.9G 6% /tmp /storage/mysql 9.9G 552M 8.9G 6% /var/lib/mysql /storage/otrs 9.9G 552M 8.9G 6% /var/data/otrs /storage/otrs-webroot 9.9G 552M 8.9G 6% /var/data/otrs-webrootHow do I run tar?
URGENT: Backups and Upgrading to a new JumpBox from an old one
This DF was on your old 1.0 OTRS JumpBox right?
Austin
URGENT: Backups and Upgrading to a new JumpBox from an old one
Can you show us the complete filename of one of your backups. I suspect you are encountering an out of memory condition during your backup which is leaving temporary files on your backup share.
We have a simple fix for this and can get you moved forward. If the files in your backup share end with '.tar' they are bad, if they end with '.tgz' they are good.
Let us pull together the fix for you and get back to you.
Austin
otrs backup 1.0 > 1.1.0
Is your data confidential or can you send us the most recent backup? info@jumpbox.com
I've restored from 1.0 to 1.1.0 successfully before but will look into it some more.
David
It's a 182 MB file...
It's a 182 MB file...