User`s guide

156 Copyright © Acronis, Inc., 2000-2010
You will be taken to the Backup plans and tasks view where you can examine the state and progress
of the recovery task.
Post-conversion operations
The resulting machine always has SCSI disk interface and basic MBR volumes. If the machine uses a
custom boot loader, you might need to configure the loader to point to the new devices and
reactivate it. Configuring GRUB is described in "How to reactivate GRUB and change its configuration
(p. 157)".
Tip. If you want to preserve logical (LVM) volumes on a Linux machine, consider the alternative method of
conversion. Create a new virtual machine, boot it using bootable media and perform recovery just like you do on
a physical machine. The LVM structure can be automatically recreated (p.
190) during recovery if it has been
saved in the backup.
6.3.11 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.
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
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.
 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.
 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.
Solution: Boot the machine from the Acronis Disk Director's bootable media and select in the
menu Tools -> Activate OS Selector.
 The system uses GRand Unified Bootloader (GRUB) and was recovered from a normal (not
from a raw, that is, sector-by-sector) backup