Archive:Disaster Recovery for Linux 2.0 en
|THE CONTENT OF THIS PAGE IS OUTDATED|
|SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.|
Copyright © SEP AG 1999-2022. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.
- 1 SEP sesam Linux BSR Restore
- 1.1 Introduction
- 1.2 Supported Distributions and File systems
- 1.3 Supported operating systems
- 1.4 System requirements
- 1.5 SAN Devices
- 1.6 Setup of the Linux BSR Backup
- 1.7 How to do a restore of a Linux client system
- 1.8 Adding the client system to the SEP sesam Server
- 1.9 Performing the restore through SEP sesam
- 1.10 Troubleshooting
SEP sesam Linux BSR Restore
This documentation explains the procedure for a Client Disaster Recovery with SEP sesam Linux BSR.
This manual shows the restore of a SUSE Linux Enterprise System (32 bit).
The restore of a Linux client-system is done with the SEP sesam Linux BSR Live-CD, which includes a sesam Client. After booting the Live-CD, the client must be added to the SEP sesam Server and the restore of a lost system is done through a regular restore on the SEP sesam Server.
Supported Distributions and File systems
Supported operating systems
- SEP sesam Server Version ≥ 126.96.36.199
- SEP sesam Client Version ≥ 188.8.131.52
- SEP sesam BSR CD Image for the used architecture, based on SLES 11. (SLES 11, Download)
- Identical System for the Restore.
|Ubuntu 08/04||i386, x86-64|
|Debian Etch||i386, x86-64|
The hard disk of the target system must have equal or greater size than the original systems hard disk.
The Systems fstab and grub/menu.lst should not refer to the unique disk identifier (/dev/disk/by-id/) but to real device names (/dev/sdaX)
This restore procedure is supported on identical hardware only!
If the backed up system was attached to a SAN infrastructure, the layout of the san devices is also saved during the backup. This means, during restore the SEP sesam Client may also repartition and reformat SAN devices which are visible from the booted live system.
Setup of the Linux BSR Backup
After the setup of the SEP sesam Client on a system which should be backed up using BSR the following steps have to be performed:
- Create a "disk_info" Backup-Source.
This backup source saves the system partition layout and existing file systems (will also include LVM and SoftRaid information):
- Create a backup task which has an "all" backup source in order to backup the real
data from the system:
How to do a restore of a Linux client system
Boot from SEP sesam BSR Live CD
After booting from the Live-CDROM a boot menu will be shown. Choose SEP sesam Live client nox in order to boot the SLES11 Live System:
During booting the SLES11 YAST Menu will pop up. There the detected network devices can be configured on the new system. After the network configuration the SEP sesam client will be installed automatically into the Live-CD's Ramdisk.
This may take some time!
In this example, the Live-CD Client will be configured as "recover.sep.de", using DHCP:
It is also possible to use a static IP-address instead of DHCP.
End of live-cd boot
After successful configuration and boot a regular Linux shell appears:
During this step it is also possible to do further configurations on the Live-CD system and also do some diagnosis in order to ensure the system is set up properly. Tools like "ping" and "nslookup" or "host" are available on this live-CD image.
In order to start a root shell use "su" to switch to the root user:
Root PW: recover
Check if the SEP sesam client is running correctly:
Access live-cd by ssh
It is also possible to access the booted Live-CD image remote by using SSH. The password for the root user is "recover".
Adding the client system to the SEP sesam Server
In order to perform a restore onto the system which has been booted from the Live-CD, you have to add the system to the SEP sesam Server.
The connection between SEP sesam Client and Server has to be successful. If there are errors while adding the client please make sure to check the regular configuration parameters (network, dns, ping, reverse dns lookup etc).
Performing the restore through SEP sesam
The restore is split into the following parts:
- Restore of "disk_info" save-set which partitions the hard-disk.
- Restore of the "all" save-set and installation of the bootloader.
Restore of disk_info partition layout
In this example the restore always goes to the system "recover" (the Live CD-system) not the original one.
Check if the restore of disk_info was successful
After a successful restore you may want to check if the restore was successful. The restore will create the partition layout of the original system and format its partitions.
After formatting the partitions it continues to mount them to /mnt/disk/ on the Live-CD image.
You can check if this procedure was successful by looking at the restore protocol. Search for the following part:
In this example our original system had one partition using an ext3 file system which was created, formatted and mounted to /mnt/disk:
Current mount status: ============================================================ /dev/sda2 on /mnt/disk type ext3 (rw) ============================================================
Restore of the "all" save-set
If the repartitioning of the disk_info restore was successful, the real data of the system (from the configured "all" Backup Task") has to be restored. It is essential that the restore target is set to "/mnt/disk/" otherwise the restore will write all data to the Ramdisk of the Live-CD:
Reboot of the system
After a successful restore of the "all" saveset, the system can be restarted with the recovered client.
If the restore of a system runs into a virtual machine, the network interface has to be reconfigured, because the MAC address will be different.
The following RAID Controller is currently not supported by the SEP Appliance based on SLES 11:
SmartArray B110i in HP Proliant DL320G6 Server