238 Copyright © Acronis, Inc., 2000-20108. [Optionally] Review the Virtual machine settings (p. 232) and make changes if necessary. Hereyou can change the path to the new virtual machine.The same type of machines with the same name cannot be created in the same folder. Change either theVM name, or the path if you get an error message caused by identical names.9. Select the destination disk for each of the source disks or source volumes and MBRs.On a Microsoft Virtual PC, be sure to recover the disk or volume where the operating system's loaderresides to the Hard disk 1. Otherwise the operating system will not boot. This cannot be fixed by changingthe 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 virtualmachine automatically, after the recovery is completed. This option is available only when thenew machine is created on a virtualization server.12. Click OK. If the recovery task is scheduled for the future, specify the credentials under which thetask will run.You will be taken to the Backup plans and tasks view where you can examine the state and progressof the recovery task.Post-conversion operationsThe resulting machine always has SCSI disk interface and basic MBR volumes. If the machine uses acustom boot loader, you might need to configure the loader to point to the new devices andreactivate it. Configuring GRUB is described in "How to reactivate GRUB and change its configuration(p. 240)".Tip. If you want to preserve logical (LVM) volumes on a Linux machine, consider the alternative method ofconversion. Create a new virtual machine, boot it using bootable media and perform recovery just like you do ona physical machine. The LVM structure can be automatically recreated (p. 273) during recovery if it has beensaved (p. 47) in the backup.6.3.11 Bootability troubleshootingIf 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 duringrecovery, especially if you change volume sizes, locations or destination drives. Acronis Backup &Recovery 10 automatically updates Windows loaders after recovery. Other loaders might also befixed, but there are cases when you have to re-activate the loaders. Specifically when you recoverLinux volumes, it is sometimes necessary to apply fixes or make booting changes so that Linux canboot 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 withthe most critical drivers included in the backupSolution for Windows: Recover the volume once again. When configuring recovery, opt forusing Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.
