Acronis Backup for Windows Server - User Guide - Manual (Page 132)

132 Copyright © Acronis International GmbH, 2002-2014

During conversion which is part of a backup plan (p. 133), the software creates the virtual
machine in addition to creating the backup. The virtual machine has the same configuration as
the original machine.

During recovery to the "New virtual machine" destination (p. 136), the software creates the
virtual machine from a backup you already have. You can change the configuration of the virtual
machine.
Depending on the agent that performs the conversion, Acronis Backup can create a virtual machine
of any of these formats:
Agent for Windows, Agent for Linux

VMware Workstation

Microsoft Virtual PC (includes Windows Virtual PC)

Citrix XenServer OVA (only during recovery to the "New virtual machine" destination)

Kernel-based Virtual Machine

Red Hat Enterprise Virtualization (RAW format)
Agent for VMware

VMware ESX(i)
Agent for Hyper-V

Microsoft Hyper-V
6.2.1 Considerations before conversion
Converting a UEFI-based machine
Virtual machines that use Unified Extensible Hardware Interface (UEFI) are currently supported in
VMware ESXi 5 only. If the target virtualization platform is ESXi 5, Acronis Backup creates a
UEFI-based machine. Otherwise, the resulting machine will use the BIOS boot firmware.
Acronis Backup adjusts the Windows boot mode to the BIOS boot firmware and ensures that
Windows remains bootable.
For Linux operating systems, changing the boot mode from UEFI to BIOS is not supported. When
converting a UEFI-based machine running Linux, make sure that it uses GRUB version 1 and that the
target virtualization platform is ESXi 5. For more details, see "Support for UEFI-based machines" (p.
34).
Logical and dynamic volumes
The resulting machine will have basic volumes, even if Linux logical volume structure is present in the
backup. The same applies to dynamic volumes used in Windows systems. If you want to recreate
logical or dynamic volumes on the machine, perform the conversion as described in “Recovery to a
manually created virtual machine” (p. 139).
Custom loader reactivation

During conversion, the disk interfaces may be changed as a result of migration to a different
platform or just manually. The software sets the system-disk interface to be the same as the
default interface for the new platform. The default interface is SCSI for VMware and IDE for other
supported platforms. If the system disk interface changes, the name of the boot device also
changes, while the boot loader still uses the old name.