Acronis Backup Recovery 10 Server for Windows Manuale Utente
Copyright © Acronis, Inc., 2000-2009
135
Example 2. The following command assembles the device /dev/md0 combined of the disks /dev/sdb
and /dev/sdc:
and /dev/sdc:
mdadm --assemble /dev/md0 -ayes /dev/sdb /dev/sdc
If recovering an MD device requires the machine to be rebooted (usually, when the device contains
the boot volume), follow these guidelines:
the boot volume), follow these guidelines:
•
If all parts of the MD device are volumes (a typical case, such as in the first example), make sure
that the type of each volume—called partition type or system ID—is Linux raid automount; the
hexadecimal code of this partition type is 0xFD. This will guarantee that the device will be
automatically assembled following the reboot. To view or change the partition type, use a disk
partitioning utility such as fdisk.
that the type of each volume—called partition type or system ID—is Linux raid automount; the
hexadecimal code of this partition type is 0xFD. This will guarantee that the device will be
automatically assembled following the reboot. To view or change the partition type, use a disk
partitioning utility such as fdisk.
•
Otherwise (such as in the second example), recover the device from bootable media—no reboot
is required in this case. Use the mdadm utility for assembly. In bootable media, you may need to
create the MD device manually, as described in Recovering MD devices and logical volumes (p.
164).
is required in this case. Use the mdadm utility for assembly. In bootable media, you may need to
create the MD device manually, as described in Recovering MD devices and logical volumes (p.
164).
6.3.10. Bootability troubleshooting
If a system was bootable at the time of backup, you expect that it will boot after recovery. However,
the information the operating system stores and uses for booting up may become outdated during
recovery, especially if you change volume sizes, locations or destination drives. Acronis Backup &
Recovery 10 automatically updates Windows loaders after recovery. Other loaders might also be
fixed, but there are cases when you have to re-activate the loaders. Specifically when you recover
Linux volumes, it is sometimes necessary to apply fixes or make booting changes so that Linux can
boot and load correctly.
the information the operating system stores and uses for booting up may become outdated during
recovery, especially if you change volume sizes, locations or destination drives. Acronis Backup &
Recovery 10 automatically updates Windows loaders after recovery. Other loaders might also be
fixed, but there are cases when you have to re-activate the loaders. Specifically when you recover
Linux volumes, it is sometimes necessary to apply fixes or make booting changes so that Linux can
boot and load correctly.
Below is a summary of typical situations that require additional user actions.
Why a recovered operating system may be unbootable
•
The machine BIOS is configured to boot from another HDD.
Solution: Configure the BIOS to boot from the HDD where the operating system resides.
•
The system was recovered on dissimilar hardware and the new hardware is incompatible with
the most critical drivers included in the backup
the most critical drivers included in the backup
Solution for Windows: Recover the volume once again. When configuring recovery, opt for
using Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.
using Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.
•
Windows was recovered to a dynamic volume that cannot be bootable
Solution: Recover Windows to a basic, simple or mirrored volume.
•
A system volume was recovered to a disk that does not have an MBR
When you configure recovery of a system volume to a disk that does not have an MBR, the
program prompts whether you want to recover the MBR along with the system volume. Opt
for not recovering, only if you do not want the system to be bootable.
Solution: Recover the volume once again along with the MBR of the corresponding disk.
program prompts whether you want to recover the MBR along with the system volume. Opt
for not recovering, only if you do not want the system to be bootable.
Solution: Recover the volume once again along with the MBR of the corresponding disk.
•
The system uses Acronis OS Selector
Because the Master Boot Record (MBR) can be changed during the system recovery, Acronis
OS Selector, which uses the MBR, might become inoperable. If this happens, reactivate
Acronis OS Selector as follows.
OS Selector, which uses the MBR, might become inoperable. If this happens, reactivate
Acronis OS Selector as follows.