246
Copyright © Acronis, Inc., 2000-2010
On a Microsoft Virtual PC, be sure to recover the disk or volume where the operating system's loader
resides to the Hard disk 1. Otherwise the operating system will not boot. This cannot be fixed by changing
the boot device order in BIOS, because a Virtual PC ignores these settings.
10.
In When to recover, specify when to start the recovery task.
11.
[Optionally] Review Recovery options and change the settings from the default ones, if need be.
You can specify in Recovery options > VM power management whether to start the new virtual
machine automatically, after the recovery is completed. This option is available only when the
new machine is created on a virtualization server.
12.
Click OK. If the recovery task is scheduled for the future, specify the credentials under which the
task will run.
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. 247)".
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. 281) during recovery if it has been
saved (p. 48) 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
