Source:Troubleshooting Disaster Recovery: Difference between revisions
(Minor update.) |
m (link to new faq) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<noinclude><languages /><br /></noinclude> | |||
<noinclude><translate><!--T:1--> | |||
{{Copyright SEP AG en}} | |||
< | <!--T:2--> | ||
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo''/5.0.0 ''Jaglion'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|documentation archive]]}}<br /></translate></noinclude> | |||
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/ | ==<translate><!--T:3--> Disaster recovery on Linux</translate>== | ||
==Disaster recovery on Linux== | |||
<noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b> | <noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b> | ||
Additional resources</b></center> | <translate><!--T:4--> Additional resources</translate></b></center> | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | | | rowspan="2" style="padding:0px 10px 0px;" | | ||
[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_sesam_Disaster_Recovery]] | [[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_sesam_Disaster_Recovery]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
See also: [[Special:MyLanguage/SEP_sesam_Disaster_Recovery|SEP sesam Disaster Recovery]] | <translate><!--T:5--> See also: [[Special:MyLanguage/SEP_sesam_Disaster_Recovery|SEP sesam Disaster Recovery]]</translate> | ||
|} | |} | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | | | rowspan="2" style="padding:0px 10px 0px;" | | ||
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]] | [[File:SEP Tip.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:FAQ|FAQ]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions. | <translate><!--T:6--> Check [[Special:MyLanguage/4_4_3_Beefalo:FAQ|FAQ]] to find the answers to most common questions.</translate> | ||
|} | |} | ||
Line 25: | Line 26: | ||
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]] | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. | <translate><!--T:7--> Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]</translate>. | ||
|} | |} | ||
</div></noinclude> | </div></noinclude> | ||
=== Problem with a ReaR backup execution === | <translate>=== Problem with a ReaR backup execution === <!--T:8--> | ||
'''Problem''' | <!--T:9--> | ||
'''Problem'''</translate> | |||
<ul><li>SEP sesam Client package was successfully installed and path backups are working. If you have problems executing a ''ReaR backup'' check the backup log if there are some missing dependencies.</li> | <ul><li><translate><!--T:10--> SEP sesam Client package was successfully installed and path backups are working. If you have problems executing a ''ReaR backup'' check the backup log if there are some missing dependencies.</translate></li> | ||
Example: | <translate><!--T:11--> Example</translate>: | ||
<pre> | <pre> | ||
<translate><!--T:12--> | |||
There are binaries or libraries in the ReaR recovery system that need additional libraries | There are binaries or libraries in the ReaR recovery system that need additional libraries | ||
/opt/sesam/bin/sesam/libvirtmod.so requires additional libraries (fatal error) | /opt/sesam/bin/sesam/libvirtmod.so requires additional libraries (fatal error) | ||
libvirt.so.0 => not found | libvirt.so.0 => not found</translate> | ||
</pre> | </pre> | ||
</ul> | </ul> | ||
<translate><!--T:13--> | |||
'''Cause''' | '''Cause''' | ||
⇒ '''Solution''' | <!--T:14--> | ||
*In this case the package ''libvirt-client'' is missing.</translate> | |||
⇒ <translate><!--T:15--> | |||
'''Solution''' | |||
<!--T:16--> | |||
*Depending on your distribution, install ''libvirt-client'' as follows: | *Depending on your distribution, install ''libvirt-client'' as follows: | ||
**On ''RHEL/CentOS 7'' use the command: <tt>yum install libvirt-client</tt> | **On ''RHEL/CentOS 7'' use the command:</translate> <tt>yum install libvirt-client</tt> | ||
**On SLES ''12/15'' use: <tt>zypper install libvirt-client</tt> | **<translate><!--T:17--> On SLES ''12/15'' use:</translate> <tt>zypper install libvirt-client</tt> | ||
===The workflow ''mkrescue'' is not supported in the ReaR system=== | <translate>===The workflow ''mkrescue'' is not supported in the ReaR system=== <!--T:18--> | ||
<!--T:19--> | |||
'''Problem''' | '''Problem''' | ||
*The workflow ''mkrescue'' is not supported in the ReaR rescue/recovery system. | <!--T:20--> | ||
*The workflow ''mkrescue'' is not supported in the ReaR rescue/recovery system.</translate> | |||
⇒ <translate><!--T:21--> | |||
'''Solution''' | |||
<!--T:22--> | |||
*Delete the file <tt>/etc/rear-release</tt>. | *Delete the file <tt>/etc/rear-release</tt>. | ||
=== ReaR image hangs during bootup === | === ReaR image hangs during bootup === <!--T:23--> | ||
'''Problem''' | <!--T:24--> | ||
<ul><li>The system hangs during bootup like shown in the following image:</li> | '''Problem'''</translate> | ||
<ul><li><translate><!--T:25--> The system hangs during bootup like shown in the following image:</translate></li> | |||
[[File: rear-hang.jpg|link=]] | [[File: rear-hang.jpg|link=]] | ||
</ul> | </ul> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:26--> | ||
'''Solution''' | |||
<!--T:27--> | |||
*Boot the system with the ''ACPI=OFF'' option (this option can be specified on the command line in the boot menu prompt, after the options ''BACKUP=SESAM OUTPUT=ISO''). | *Boot the system with the ''ACPI=OFF'' option (this option can be specified on the command line in the boot menu prompt, after the options ''BACKUP=SESAM OUTPUT=ISO''). | ||
=== The recovered system does not boot === | === The recovered system does not boot === <!--T:28--> | ||
<!--T:29--> | |||
'''Problem 1''' | '''Problem 1''' | ||
*The system does not boot because <tt>/root/dev/console</tt> cannot be found. | *The system does not boot because <tt>/root/dev/console</tt> cannot be found. | ||
<!--T:30--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*Certain distributions rely on the existence of the directory <tt>/dev/</tt> while booting | *Certain distributions rely on the existence of the directory <tt>/dev/</tt> while booting | ||
* Certain static devices must exist before the <tt>udev</tt> daemon creates them. | * Certain static devices must exist before the <tt>udev</tt> daemon creates them.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:31--> | ||
'''Solution''' | |||
<!--T:32--> | |||
*Include the <tt>/dev/</tt> file system in your backup. | *Include the <tt>/dev/</tt> file system in your backup. | ||
* If the restore cannot restore <tt>/dev/</tt>: | * If the restore cannot restore <tt>/dev/</tt>:</translate> | ||
#Boot from the SEP sesam LIVE CD | #<translate><!--T:33--> | ||
#Mount the ROOT partition of the restored system | Boot from the SEP sesam LIVE CD. | ||
#Manually create the <tt>/dev/</tt> directory | #Mount the ROOT partition of the restored system. | ||
#Manually create the <tt>/dev/console</tt> entry with: | #Manually create the <tt>/dev/</tt> directory. | ||
#Manually create the <tt>/dev/console</tt> entry with:</translate> | |||
mknod /path/to/target/mount//dev/console c 0 0 | mknod /path/to/target/mount//dev/console c 0 0 | ||
<translate><!--T:34--> | |||
'''Problem 2''' | '''Problem 2''' | ||
*The system does not boot because of missing ''libblkid.so.1''. | *The system does not boot because of missing ''libblkid.so.1''. | ||
<!--T:35--> | |||
'''Possible cause''' | '''Possible cause''' | ||
*This is most likely caused by ''SELinux'' which is activated by default. | <!--T:36--> | ||
*This is most likely caused by ''SELinux'' which is activated by default.</translate> | |||
⇒ '''Solution''' | ⇒ <translate><!--T:37--> '''Solution'''</translate> | ||
<ul><li>Especially on RHEL6 or CentOS6 systems, follow these steps after rebooting from the ReaR recovery:</li> | <ul><li><translate><!--T:38--> Especially on RHEL6 or CentOS6 systems, follow these steps after rebooting from the ReaR recovery:</translate></li> | ||
<ol><li>Press a key when prompted by the boot loader (GRUB):</li> | <ol><li><translate><!--T:39--> Press a key when prompted by the boot loader (GRUB):</translate></li> | ||
[[File: rhelcentos_grub1.jpg|link=]] | [[File: rhelcentos_grub1.jpg|link=]] | ||
<li>Select the appropriate boot loader entry:</li> | <li><translate><!--T:40--> Select the appropriate boot loader entry:</translate></li> | ||
[[File: rhelcentos_grub2.jpg|link=]] | [[File: rhelcentos_grub2.jpg|link=]] | ||
<li>Press '''e''' to modify the commands for the selected entry:</li> | <li><translate><!--T:41--> Press '''e''' to modify the commands for the selected entry:</translate></li> | ||
[[File: rhelcentos_grub3.jpg|link=]] | [[File: rhelcentos_grub3.jpg|link=]] | ||
<li>Add '''selinux=0''' to the commands:</li> | <li><translate><!--T:42--> Add '''selinux=0''' to the commands:</translate></li> | ||
[[File: rhelcentos_grub4.jpg|link=]] | [[File: rhelcentos_grub4.jpg|link=]] | ||
<li>Press '''Enter''' to confirm the changes and '''b''' to boot up the machine with ''SELinux'' disabled.</li> | <li><translate><!--T:43--> Press '''Enter''' to confirm the changes and '''b''' to boot up the machine with ''SELinux'' disabled.</translate></li> | ||
<li>When having access to the system, change the option ''SELinux'' of ''/etc/selinux/config'' to the following:</li> | <li><translate><!--T:44--> When having access to the system, change the option ''SELinux'' of ''/etc/selinux/config'' to the following:</translate></li> | ||
SELINUX=permissive | SELINUX=permissive | ||
</ol> | </ol> | ||
Afterwards, reboot the system and feel free to set the ''SELinux'' value back to ''enforcing'' if needed. | <translate><!--T:45--> Afterwards, reboot the system and feel free to set the ''SELinux'' value back to ''enforcing'' if needed.</translate> | ||
</ul> | </ul> | ||
=== No bootable operating system can be found === | <translate>=== No bootable operating system can be found === <!--T:46--> | ||
<!--T:47--> | |||
'''Problem''' | '''Problem''' | ||
*The system is not able to find a bootable OS instance after the restore. | *The system is not able to find a bootable OS instance after the restore. | ||
<!--T:48--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*There may have been problems during the installation of the GRUB boot loader. | *There may have been problems during the installation of the GRUB boot loader.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:49--> | ||
*The restore protocol includes a statement whether or not the installation of the boot loader was successful: | '''Solution''' | ||
*The restore protocol includes a statement whether or not the installation of the boot loader was successful:</translate> | |||
2009-12-14 14:48:27: sbc-3500: Info: Reinstall boot manager | 2009-12-14 14:48:27: sbc-3500: Info: Reinstall boot manager | ||
[/sesam/bin/sesam//sbc_grub_auto /mnt/disk/ AUTO] | [/sesam/bin/sesam//sbc_grub_auto /mnt/disk/ AUTO] | ||
*It is also possible to boot the system again from the live-CD, mount the target partitions and use <tt>grub-install</tt> to install the boot loader correctly. | *<translate><!--T:50--> | ||
It is also possible to boot the system again from the live-CD, mount the target partitions and use <tt>grub-install</tt> to install the boot loader correctly. | |||
=== The device does not have a corresponding BIOS drive === | === The device does not have a corresponding BIOS drive === <!--T:51--> | ||
<!--T:52--> | |||
'''Problem''' | '''Problem''' | ||
*During the restore, the following error occurs: | *During the restore, the following error occurs:</translate> | ||
/dev/sda1 does not have any corresponding BIOS drive | /dev/sda1 does not have any corresponding BIOS drive | ||
<translate><!--T:53--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*Check the file <tt>/boot/grub/device.map</tt> on the target system. If there are entries referring to the disk through <tt>/dev/by-disk/...</tt> as shown in the example below, the entry is most likely the reference to the hard disk partition of the broken system. GRUB will not find the proper device: | *Check the file <tt>/boot/grub/device.map</tt> on the target system. If there are entries referring to the disk through <tt>/dev/by-disk/...</tt> as shown in the example below, the entry is most likely the reference to the hard disk partition of the broken system. GRUB will not find the proper device:</translate> | ||
hd(0) /dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1GLA14263-part1 | hd(0) /dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1GLA14263-part1 | ||
⇒ '''Solution''' | ⇒ <translate><!--T:54--> | ||
'''Solution''' | |||
*Reboot from the live-CD | *Reboot from the live-CD | ||
*Mount the root and boot partitions to <tt>/mnt/disk</tt> (and <tt>/mnt/disk/boot</tt>, if necessary) | *Mount the root and boot partitions to <tt>/mnt/disk</tt> (and <tt>/mnt/disk/boot</tt>, if necessary) | ||
*Restart <tt>grub-install</tt> with the following options: | *Restart <tt>grub-install</tt> with the following options:</translate> | ||
grub-install --root-directory=/mnt/disk --recheck hd0 | grub-install --root-directory=/mnt/disk --recheck hd0 | ||
Output: | <translate><!--T:55--> Output:</translate> | ||
grub-probe: error: Cannot open `/boot/grub/device.map' | grub-probe: error: Cannot open `/boot/grub/device.map' | ||
Line 158: | Line 192: | ||
(hd1) /dev/hdb | (hd1) /dev/hdb | ||
You can ignore the error <tt>line 374: [: =: unary operator expected</tt>. <br>More important is the result <tt>Installation finished. No error reported.</tt> | <translate><!--T:56--> | ||
You can ignore the error <tt>line 374: [: =: unary operator expected</tt>. | |||
<br>More important is the result <tt>Installation finished. No error reported.</tt> | |||
=== No corresponding BIOS drive for /dev/cciss/c0d0p2 === | === No corresponding BIOS drive for /dev/cciss/c0d0p2 === <!--T:57--> | ||
<!--T:58--> | |||
'''Problem''' | '''Problem''' | ||
*You receive the message: ''/dev/cciss/c0d0p2 does not have any corresponding BIOS drive'' in restore log. | *You receive the message: ''/dev/cciss/c0d0p2 does not have any corresponding BIOS drive'' in restore log.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:59--> | ||
'''Solution''' | |||
*Please see: [http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7001376&sliceId=1&docTypeID=DT_TID_1_1&dialogID=70466304&stateId=0%200%20134988932 Novell support] | *Please see: [http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7001376&sliceId=1&docTypeID=DT_TID_1_1&dialogID=70466304&stateId=0%200%20134988932 Novell support] | ||
=== fsck.ext3: File system has unsupported features=== | === fsck.ext3: File system has unsupported features=== <!--T:60--> | ||
<!--T:61--> | |||
'''Problem''' | '''Problem''' | ||
* During a restore of a system with kernel version 2.4 the system may not boot because the Live-CD creates a file system with features which are not supported by kernel 2.4. | * During a restore of a system with kernel version 2.4 the system may not boot because the Live-CD creates a file system with features which are not supported by kernel 2.4. | ||
<!--T:62--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*Most likely the file system options <tt>resize_inode,dir_index,large_file,ext_attr</tt> are causing the problem and making the system unbootable. | *Most likely the file system options <tt>resize_inode,dir_index,large_file,ext_attr</tt> are causing the problem and making the system unbootable.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:63--> | ||
'''Solution''' | |||
*Reboot from the Live-CD image, which includes the tool <tt>debugfs</tt>. | *Reboot from the Live-CD image, which includes the tool <tt>debugfs</tt>. | ||
* Show the file system features with <tt>debugfs</tt>: | *Show the file system features with <tt>debugfs</tt>:</translate> | ||
root@recover#: debugfs -w <b>/dev/sda2</b> | root@recover#: debugfs -w <b>/dev/sda2</b> | ||
Line 186: | Line 227: | ||
quit | quit | ||
<translate><!--T:64--> | |||
Replace <tt>/dev/sda2</tt> with the corresponding partition names on your system. | Replace <tt>/dev/sda2</tt> with the corresponding partition names on your system. | ||
*To remove file system features: | <!--T:65--> | ||
*To remove file system features:</translate> | |||
root@recover#: debugfs -w <b>/dev/sda2</b> | root@recover#: debugfs -w <b>/dev/sda2</b> | ||
Line 195: | Line 238: | ||
quit | quit | ||
<translate><!--T:66--> | |||
After removing the options, the system should boot correctly. | After removing the options, the system should boot correctly. | ||
=== Incorrect inode size (256) === | === Incorrect inode size (256) === <!--T:67--> | ||
<!--T:68--> | |||
'''Problem ''' | '''Problem ''' | ||
*After a successful restore the boot process stops with ''incorrect inode size (256)''. | *After a successful restore the boot process stops with ''incorrect inode size (256)''. | ||
<!--T:69--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*Older kernel versions (2.4) may use a different inode size than the one the file system's created through the Live-CD (which includes kernel 2.6). For example, this happens during the restore of SLES8 based systems which use an inode size of 128k. | *Older kernel versions (2.4) may use a different inode size than the one the file system's created through the Live-CD (which includes kernel 2.6). For example, this happens during the restore of SLES8 based systems which use an inode size of 128k.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:70--> | ||
*This can only be solved by formatting the devices manually from the Live-CD, using the proper <tt>mkfs</tt> options: | '''Solution''' | ||
<!--T:71--> | |||
*This can only be solved by formatting the devices manually from the Live-CD, using the proper <tt>mkfs</tt> options:</translate> | |||
mkfs.ext3 -I 128 /dev/sda1 | mkfs.ext3 -I 128 /dev/sda1 | ||
<translate><!--T:72--> | |||
After this step, remount the partition to <tt>/mnt/disk</tt> and repeat the restore operations. Changing the inode size is only possible by reformatting the devices. | After this step, remount the partition to <tt>/mnt/disk</tt> and repeat the restore operations. Changing the inode size is only possible by reformatting the devices. | ||
=== Missing root file system === | === Missing root file system === <!--T:73--> | ||
<!--T:74--> | |||
'''Problem''' | '''Problem''' | ||
*The restored system can't find a root file system and fails during resume. | *The restored system can't find a root file system and fails during resume. | ||
<!--T:75--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*The <tt>/etc/fstab</tt> file was configured with the root file system as UUID. | *The <tt>/etc/fstab</tt> file was configured with the root file system as UUID.</translate> | ||
⇒ <translate><!--T:76--> | |||
'''Solution''' | |||
<!--T:77--> | |||
* Specify the root file system device name in conventional device names if you are using a different physical disk. After booting, use YAST to reconfigure your boot loader or edit your <tt>/boot/grub/menu.lst</tt> manually: | * Specify the root file system device name in conventional device names if you are using a different physical disk. After booting, use YAST to reconfigure your boot loader or edit your <tt>/boot/grub/menu.lst</tt> manually:</translate> | ||
root=/dev/sda2 | root=/dev/sda2 | ||
=== Missing network cards === | <translate>=== Missing network cards === <!--T:78--> | ||
<!--T:79--> | |||
'''Problem''' | '''Problem''' | ||
*The restored system does not find any network cards. | *The restored system does not find any network cards. | ||
<!--T:80--> | |||
'''Possible causes''' | '''Possible causes''' | ||
*If the restore was done to dissimilar hardware, SLES-based distributions may not configure the network devices correctly. SLES-based systems save their network configuration by using the system's MAC address. Most likely the system will not use <tt>eht0</tt> as a device name, but <tt>eth1</tt>, as it has another MAC address. | *If the restore was done to dissimilar hardware, SLES-based distributions may not configure the network devices correctly. SLES-based systems save their network configuration by using the system's MAC address. Most likely the system will not use <tt>eht0</tt> as a device name, but <tt>eth1</tt>, as it has another MAC address.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:81--> | ||
'''Solution''' | |||
*Use '''YaST''' and reconfigure your network interfaces. | *Use '''YaST''' and reconfigure your network interfaces. | ||
=== Client does not start on the RHEL6/Debian9 recovery image === | === Client does not start on the RHEL6/Debian9 recovery image === <!--T:82--> | ||
<!--T:83--> | |||
'''Problem''' | '''Problem''' | ||
*The SEP sesam Client does not start automatically on RHEL6 and Debian9-based recovery images. | *The SEP sesam Client does not start automatically on RHEL6 and Debian9-based recovery images. | ||
<!--T:84--> | |||
'''Cause''' | '''Cause''' | ||
*The file <tt>/etc/init.d/functions</tt> is missing within the recovery image. | *The file <tt>/etc/init.d/functions</tt> is missing within the recovery image.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:85--> | ||
<ul><li>The client can be started manually via:</li> | '''Solution''' | ||
<ul><li>The client can be started manually via:</li></translate> | |||
/opt/sesam/bin/sesam/sm_main start | /opt/sesam/bin/sesam/sm_main start | ||
</ul> | </ul> | ||
=== RHEL7-related issues === | <translate>=== RHEL7-related issues === <!--T:86--> | ||
==== RHEL7 backup fails with an error ==== | |||
==== RHEL7 backup fails with an error ==== <!--T:87--> | |||
<!--T:88--> | |||
'''Error 1''' | '''Error 1''' | ||
<ul><li>The RHEL backup fails with the following error:</li> | <ul><li>The RHEL backup fails with the following error:</li></translate> | ||
ERROR: The LSB package is not installed. | ERROR: The LSB package is not installed. | ||
</ul> | </ul> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:89--> | ||
'''Solution''' | |||
<ul><li>Install the ''lsb'' package as follows:</li> | <!--T:90--> | ||
<ul><li>Install the ''lsb'' package as follows:</li></translate> | |||
yum install redhat-lsb-core mkisofs syslinux | yum install redhat-lsb-core mkisofs syslinux | ||
</ul> | </ul> | ||
<translate><!--T:91--> | |||
'''Error 2''' | '''Error 2''' | ||
<ul><li>The RHEL backup fails with:</li> | <!--T:92--> | ||
<ul><li>The RHEL backup fails with:</li></translate> | |||
ERROR: Cannot find required programs: mingetty | ERROR: Cannot find required programs: mingetty | ||
For more details, see [https://github.com/rear/rear/issues/348 Rear dependencies on RHEL7]. | <translate><!--T:93--> For more details, see [https://github.com/rear/rear/issues/348 Rear dependencies on RHEL7].</translate> | ||
</ul> | </ul> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:94--> '''Solution'''</translate> | ||
<ul><li>To solve this problem, proceed as follows:</li> | |||
<ol><li>Edit</li> | <ul><li><translate><!--T:95--> To solve this problem, proceed as follows:</translate></li> | ||
<ol><li><translate><!--T:96--> Edit</translate></li> | |||
/var/opt/sesam/var/lib/rear/usr/share/rear/conf/default.conf | /var/opt/sesam/var/lib/rear/usr/share/rear/conf/default.conf | ||
<translate><!--T:97--> | |||
and from the line: | and from the line: | ||
# required programs. Same as above, but if they are missing, we abort. | <!--T:98--> | ||
# required programs. Same as above, but if they are missing, we abort.</translate> | |||
REQUIRED_PROGS=( | REQUIRED_PROGS=( | ||
"$SCRIPT_FILE" | "$SCRIPT_FILE" | ||
remove the line: | <translate><!--T:99--> remove the line:</translate> | ||
mingetty | mingetty | ||
<li>Run the backup again.</li></ol></ul> | <li><translate><!--T:100--> Run the backup again.</translate></li></ol></ul> | ||
==== ReaR error occurred during ''grub2-mkimage'' of ''bootx64.efi'' ==== | <translate>==== ReaR error occurred during ''grub2-mkimage'' of ''bootx64.efi'' ==== <!--T:101--> | ||
<!--T:102--> | |||
{{Note|In order to be able to create an UEFI/EFI bootable ISO image, the additional tool ''ebiso'' has to be installed on the client system as described in the section [[Special:MyLanguage/Disaster_Recovery_Troubleshooting|Installing ''ebiso'' for creating UEFI aware ISO images]].}} | {{Note|In order to be able to create an UEFI/EFI bootable ISO image, the additional tool ''ebiso'' has to be installed on the client system as described in the section [[Special:MyLanguage/Disaster_Recovery_Troubleshooting|Installing ''ebiso'' for creating UEFI aware ISO images]].}} | ||
<!--T:103--> | |||
'''Problem''' | '''Problem''' | ||
*The ReaR error occurrs during ''grub2-mkimage'' of ''bootx64.efi''. | *The ReaR error occurrs during ''grub2-mkimage'' of ''bootx64.efi''.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:104--> | ||
'''Solution''' | |||
*To solve the problem, install the ''grub2-efi-x64-modules'' package. | *To solve the problem, install the ''grub2-efi-x64-modules'' package. | ||
=== SLES-related issues === | === SLES-related issues === <!--T:105--> | ||
==== <tt>SM_SSH</tt> does not work on SLES11 recovery image==== | |||
⇒ '''Solution''' | ==== <tt>SM_SSH</tt> does not work on SLES11 recovery image==== <!--T:106--></translate> | ||
<ul><li>In this case, execute</li> | ⇒ <translate><!--T:107--> '''Solution'''</translate> | ||
<ul><li><translate><!--T:108--> In this case, execute</translate></li> | |||
mount -t tmpfs none /dev/shm/ -o rw,nosuid,nodev,noexec | mount -t tmpfs none /dev/shm/ -o rw,nosuid,nodev,noexec | ||
before starting the recovery process. | <translate><!--T:109--> before starting the recovery process.</translate> | ||
</ul> | </ul> | ||
==== Client is unreachable after booting the rescue image ==== | <translate>==== Client is unreachable after booting the rescue image ==== <!--T:110--> | ||
<!--T:111--> | |||
'''Problem''' | '''Problem''' | ||
*After booting the rescue image the client is not reachable. | *After booting the rescue image the client is not reachable.</translate> | ||
⇒ '''Solution''' | ⇒ <translate><!--T:112--> '''Solution'''</translate> | ||
<ul><lI>Start the client manually using the following command on the rescue command line:</li> | <ul><lI><translate><!--T:113--> Start the client manually using the following command on the rescue command line:</translate></li> | ||
sh /etc/scripts/system-setup.d/59-start-sesam-client.sh | sh /etc/scripts/system-setup.d/59-start-sesam-client.sh | ||
</ul> | </ul> | ||
==== {{anchor|ebiso}}Installing ''ebiso'' for creating UEFI aware ISO images ==== | <translate>==== EFI bootable image cannot be created on SLES11 ==== <!--T:114--> | ||
<!--T:115--> | |||
'''Problem''' | |||
* EFI bootable image of ''GRUB2'' cannot be created on SLES11. | |||
<!--T:116--> | |||
'''Cause''' | |||
*SEP sesam v. [[SEP_sesam_Release_Versions|4.4.3.64 ''Grolar'']] is the last version that supports ''SLES11 with UEFI''.</translate> | |||
⇒ <translate><!--T:117--> | |||
'''Solution''' | |||
*To continue using SLES with UEFI, you ''should not upgrade'' to a later version of SEP sesam. | |||
==== {{anchor|ebiso}}Installing ''ebiso'' for creating UEFI aware ISO images ==== <!--T:118--> | |||
In order to be able to create an UEFI/EFI bootable ISO image the, the additional tool ''ebiso'' has to be installed on the client system. This package is not part of a regular ''SLES12/SLES15'' installation and can be downloaded at the following URL: | <!--T:119--> | ||
In order to be able to create an UEFI/EFI bootable ISO image the, the additional tool ''ebiso'' has to be installed on the client system. This package is not part of a regular ''SLES12/SLES15'' installation and can be downloaded at the following URL:</translate> | |||
http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/SLE_12/x86_64/ | http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/SLE_12/x86_64/ | ||
or | <translate><!--T:120--> or</translate> | ||
http://download.sep.de/utils/bsr-linux/ | http://download.sep.de/utils/bsr-linux/ | ||
<translate><!--T:121--> | |||
For other Linux distributions contact ''SEP support'' at [mailto:support@sep.de support@sep.de] for assistance. | For other Linux distributions contact ''SEP support'' at [mailto:support@sep.de support@sep.de] for assistance. | ||
Install ''ebiso'' as follows: | <!--T:122--> | ||
Install ''ebiso'' as follows:</translate> | |||
rpm -i ebiso-<version>.rpm | rpm -i ebiso-<version>.rpm | ||
<translate><!--T:123--> | |||
Note that in ReaR v. < 1.19, the generated ISO image mount migt be too small for storing all needed information and need to be adjusted. | Note that in ReaR v. < 1.19, the generated ISO image mount migt be too small for storing all needed information and need to be adjusted. | ||
In this case, under | <!--T:124--> | ||
In this case, under</translate> | |||
/var/opt/sesam/var/lib/rear/usr/share/rear/lib/uefi-functions.sh''' (line 64) | /var/opt/sesam/var/lib/rear/usr/share/rear/lib/uefi-functions.sh''' (line 64) | ||
change | <translate><!--T:125--> change</translate> | ||
(shim.efi|elilo.efi) size=128000 ;; | (shim.efi|elilo.efi) size=128000 ;; | ||
to | <translate><!--T:126--> to</translate> | ||
(shim.efi|elilo.efi) size=228000 ;; | (shim.efi|elilo.efi) size=228000 ;; | ||
<noinclude>== See also == | <noinclude><translate>== See also == <!--T:127--> | ||
[[Special:MyLanguage/SEP_sesam_Disaster_Recovery|SEP sesam Disaster Recovery]]</noinclude> | [[Special:MyLanguage/SEP_sesam_Disaster_Recovery|SEP sesam Disaster Recovery]]</translate></noinclude> |
Revision as of 11:59, 22 March 2022
Disaster recovery on Linux
Problem with a ReaR backup execution
Problem
- SEP sesam Client package was successfully installed and path backups are working. If you have problems executing a ReaR backup check the backup log if there are some missing dependencies. Example:
There are binaries or libraries in the ReaR recovery system that need additional libraries /opt/sesam/bin/sesam/libvirtmod.so requires additional libraries (fatal error) libvirt.so.0 => not found
Cause
- In this case the package libvirt-client is missing.
⇒ Solution
- Depending on your distribution, install libvirt-client as follows:
- On RHEL/CentOS 7 use the command: yum install libvirt-client
- On SLES 12/15 use: zypper install libvirt-client
The workflow mkrescue is not supported in the ReaR system
Problem
- The workflow mkrescue is not supported in the ReaR rescue/recovery system.
⇒ Solution
- Delete the file /etc/rear-release.
ReaR image hangs during bootup
Problem
- The system hangs during bootup like shown in the following image:
⇒ Solution
- Boot the system with the ACPI=OFF option (this option can be specified on the command line in the boot menu prompt, after the options BACKUP=SESAM OUTPUT=ISO).
The recovered system does not boot
Problem 1
- The system does not boot because /root/dev/console cannot be found.
Possible causes
- Certain distributions rely on the existence of the directory /dev/ while booting
- Certain static devices must exist before the udev daemon creates them.
⇒ Solution
- Include the /dev/ file system in your backup.
- If the restore cannot restore /dev/:
- Boot from the SEP sesam LIVE CD.
- Mount the ROOT partition of the restored system.
- Manually create the /dev/ directory.
- Manually create the /dev/console entry with:
mknod /path/to/target/mount//dev/console c 0 0
Problem 2
- The system does not boot because of missing libblkid.so.1.
Possible cause
- This is most likely caused by SELinux which is activated by default.
⇒ Solution
- Especially on RHEL6 or CentOS6 systems, follow these steps after rebooting from the ReaR recovery:
- Press a key when prompted by the boot loader (GRUB):
- Select the appropriate boot loader entry:
- Press e to modify the commands for the selected entry:
- Add selinux=0 to the commands:
- Press Enter to confirm the changes and b to boot up the machine with SELinux disabled.
- When having access to the system, change the option SELinux of /etc/selinux/config to the following: SELINUX=permissive
Afterwards, reboot the system and feel free to set the SELinux value back to enforcing if needed.
No bootable operating system can be found
Problem
- The system is not able to find a bootable OS instance after the restore.
Possible causes
- There may have been problems during the installation of the GRUB boot loader.
⇒ Solution
- The restore protocol includes a statement whether or not the installation of the boot loader was successful:
2009-12-14 14:48:27: sbc-3500: Info: Reinstall boot manager [/sesam/bin/sesam//sbc_grub_auto /mnt/disk/ AUTO]
- It is also possible to boot the system again from the live-CD, mount the target partitions and use grub-install to install the boot loader correctly.
The device does not have a corresponding BIOS drive
Problem
- During the restore, the following error occurs:
/dev/sda1 does not have any corresponding BIOS drive
Possible causes
- Check the file /boot/grub/device.map on the target system. If there are entries referring to the disk through /dev/by-disk/... as shown in the example below, the entry is most likely the reference to the hard disk partition of the broken system. GRUB will not find the proper device:
hd(0) /dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1GLA14263-part1
⇒ Solution
- Reboot from the live-CD
- Mount the root and boot partitions to /mnt/disk (and /mnt/disk/boot, if necessary)
- Restart grub-install with the following options:
grub-install --root-directory=/mnt/disk --recheck hd0
Output:
grub-probe: error: Cannot open `/boot/grub/device.map' /usr/sbin/grub-install: line 374: [: =: unary operator expected Installation finished. No error reported. This is the contents of the device map /mnt/disk/boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (hd0) /dev/hda (hd1) /dev/hdb
You can ignore the error line 374: [: =: unary operator expected.
More important is the result Installation finished. No error reported.
No corresponding BIOS drive for /dev/cciss/c0d0p2
Problem
- You receive the message: /dev/cciss/c0d0p2 does not have any corresponding BIOS drive in restore log.
⇒ Solution
- Please see: Novell support
fsck.ext3: File system has unsupported features
Problem
- During a restore of a system with kernel version 2.4 the system may not boot because the Live-CD creates a file system with features which are not supported by kernel 2.4.
Possible causes
- Most likely the file system options resize_inode,dir_index,large_file,ext_attr are causing the problem and making the system unbootable.
⇒ Solution
- Reboot from the Live-CD image, which includes the tool debugfs.
- Show the file system features with debugfs:
root@recover#: debugfs -w /dev/sda2 debugfs 1.41.1 (01-Sep-2008) debugfs: features Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file quit
Replace /dev/sda2 with the corresponding partition names on your system.
- To remove file system features:
root@recover#: debugfs -w /dev/sda2 debugfs: features -resize_inode -ext_attr -dir_index -large_file -needs_recovery -sparse_super Filesystem features: has_journal filetype quit
After removing the options, the system should boot correctly.
Incorrect inode size (256)
Problem
- After a successful restore the boot process stops with incorrect inode size (256).
Possible causes
- Older kernel versions (2.4) may use a different inode size than the one the file system's created through the Live-CD (which includes kernel 2.6). For example, this happens during the restore of SLES8 based systems which use an inode size of 128k.
⇒ Solution
- This can only be solved by formatting the devices manually from the Live-CD, using the proper mkfs options:
mkfs.ext3 -I 128 /dev/sda1
After this step, remount the partition to /mnt/disk and repeat the restore operations. Changing the inode size is only possible by reformatting the devices.
Missing root file system
Problem
- The restored system can't find a root file system and fails during resume.
Possible causes
- The /etc/fstab file was configured with the root file system as UUID.
⇒ Solution
- Specify the root file system device name in conventional device names if you are using a different physical disk. After booting, use YAST to reconfigure your boot loader or edit your /boot/grub/menu.lst manually:
root=/dev/sda2
Missing network cards
Problem
- The restored system does not find any network cards.
Possible causes
- If the restore was done to dissimilar hardware, SLES-based distributions may not configure the network devices correctly. SLES-based systems save their network configuration by using the system's MAC address. Most likely the system will not use eht0 as a device name, but eth1, as it has another MAC address.
⇒ Solution
- Use YaST and reconfigure your network interfaces.
Client does not start on the RHEL6/Debian9 recovery image
Problem
- The SEP sesam Client does not start automatically on RHEL6 and Debian9-based recovery images.
Cause
- The file /etc/init.d/functions is missing within the recovery image.
⇒ Solution
- The client can be started manually via: /opt/sesam/bin/sesam/sm_main start
RHEL7 backup fails with an error
Error 1
- The RHEL backup fails with the following error: ERROR: The LSB package is not installed.
⇒ Solution
- Install the lsb package as follows: yum install redhat-lsb-core mkisofs syslinux
Error 2
- The RHEL backup fails with: ERROR: Cannot find required programs: mingetty For more details, see Rear dependencies on RHEL7.
⇒ Solution
- To solve this problem, proceed as follows:
- Edit /var/opt/sesam/var/lib/rear/usr/share/rear/conf/default.conf and from the line: # required programs. Same as above, but if they are missing, we abort. REQUIRED_PROGS=( "$SCRIPT_FILE" remove the line: mingetty
- Run the backup again.
ReaR error occurred during grub2-mkimage of bootx64.efi
Note | |
In order to be able to create an UEFI/EFI bootable ISO image, the additional tool ebiso has to be installed on the client system as described in the section Installing ebiso for creating UEFI aware ISO images. |
Problem
- The ReaR error occurrs during grub2-mkimage of bootx64.efi.
⇒ Solution
- To solve the problem, install the grub2-efi-x64-modules package.
SM_SSH does not work on SLES11 recovery image
⇒ Solution
- In this case, execute mount -t tmpfs none /dev/shm/ -o rw,nosuid,nodev,noexec before starting the recovery process.
Client is unreachable after booting the rescue image
Problem
- After booting the rescue image the client is not reachable.
⇒ Solution
- Start the client manually using the following command on the rescue command line: sh /etc/scripts/system-setup.d/59-start-sesam-client.sh
EFI bootable image cannot be created on SLES11
Problem
- EFI bootable image of GRUB2 cannot be created on SLES11.
Cause
- SEP sesam v. 4.4.3.64 Grolar is the last version that supports SLES11 with UEFI.
⇒ Solution
- To continue using SLES with UEFI, you should not upgrade to a later version of SEP sesam.
Installing ebiso for creating UEFI aware ISO images
In order to be able to create an UEFI/EFI bootable ISO image the, the additional tool ebiso has to be installed on the client system. This package is not part of a regular SLES12/SLES15 installation and can be downloaded at the following URL:
http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/SLE_12/x86_64/
or
http://download.sep.de/utils/bsr-linux/
For other Linux distributions contact SEP support at support@sep.de for assistance.
Install ebiso as follows:
rpm -i ebiso-<version>.rpm
Note that in ReaR v. < 1.19, the generated ISO image mount migt be too small for storing all needed information and need to be adjusted.
In this case, under
/var/opt/sesam/var/lib/rear/usr/share/rear/lib/uefi-functions.sh (line 64)
change
(shim.efi|elilo.efi) size=128000 ;;
to
(shim.efi|elilo.efi) size=228000 ;;