Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: pearless on July 06, 2006, 12:44:58 PM

Title: Upgrading from 6.01 to 7.0rc3 -> restore from tape fails?
Post by: pearless on July 06, 2006, 12:44:58 PM
I have a 6.01 system.

I did a backup to tape.

I shutdown the server and replaced the 2x80GB drives with 2x160GB new drives.

I booted off the 7.0rc3 disk and installed v7 and answered the configuration questions (etc).

I then did a restore from the same tape and I got:

Code: [Select]

Backup or restore server data
Warning: a reboot is required before proceeding! Failure to reboot now may leave your system in an unknown state!

The server provides two ways to back up and restore your server: using your local desktop or a tape drive.

The first method creates a copy of your server configuration and user data files, and downloads it to your local desktop via your web browser. Currently your configuration and data files total approximately 248kb. The backup file will be somewhat less than this, depending on how compressible the data are. The "Verify desktop backup file" option can be used to check the integrity of a desktop backup file.

The tape backup method uses a software package called flexbackup to back up your entire hard disk to tape every night. This requires a supported tape drive and a tape that is not write-protected. The backup is performed automatically at the selected time every night (with a reminder automatically e-mailed to the administrator during the day). Currently your hard disk contains 1Gb of data.

Both restore methods allow you to restore your configuration and user data files. Ideally, the restore should be performed on a freshly installed server.
Backup configuration and status

Tape backups are disabled

A system restore has completed
It began at: Thu Jul 6 22:33:36 2006
and finished at: Thu Jul 6 22:33:57 2006

You must reboot the server to activate any configuration changes that were made as a result of this restore.


Hmm, that only took 21 seconds (the backup to that tape took many minutes), very suspicious.

Rebooted, and I got the
Code: [Select]

Please standby while your changes are activated

(I think I typed that message in OK)

And when it finished rebooting, it still looked like a fresh 7.0rc3 server, no users, i-bays, mail, nothing.

Have I done something wrong here??

I have tried it twice now with no luck, I even tried restoring from the previous days full backup tape.

HELP!!
Title: Upgrading from 6.01 to 7.0rc3 -> restore from tape fails?
Post by: ldkeen on July 06, 2006, 03:15:31 PM
You could connect one of the old 80GB drives and use the built in CopyFromDisk procedure to restore your old data. The basic procedure is as follows:
1. Plug in external USB caddy containing old hard disk. Check dmesg to find the drive config. Should load up as /dev/sda. Being from an old install the drive has an extended partition on it and the data I need is on /dev/sda6.
2. cd /
3. mkdir /mnt/tmp
4. mount /dev/sda6 /mnt/tmp
5. /sbin/e-smith/db configuration setprop backup Program CopyFromDisk status enabled
6. /sbin/e-smith/signal-event pre-restore
7. /sbin/e-smith/signal-event restore-tape /mnt/tmp
8. /sbin/e-smith/signal-event post-upgrade
9. /sbin/e-smith/signal-event reboot
Lloyd
Title: Re: Upgrading from 6.01 to 7.0rc3 -> restore from tape fa
Post by: CharlieBrady on July 06, 2006, 04:19:36 PM
Quote from: "pearless"

Have I done something wrong here??


Yes, someting didn't work properly and you did not report the possible bug via the Bug Tracker. Please do so now.

Thanks.
Title: Re: Upgrading from 6.01 to 7.0rc3 -> restore from tape fa
Post by: pearless on July 06, 2006, 11:30:01 PM
Quote from: "CharlieBrady"
Quote from: "pearless"

Have I done something wrong here??


Yes, someting didn't work properly and you did not report the possible bug via the Bug Tracker. Please do so now.

Thanks.


OK, I just wan't to make sure it was my stuff-up before I logged it as a bug.

I am going to put the new disks back in and extract off the message log in case it is needed for the bug I have just logged.

Now to find that USB drive case I had somewhere...