45856: Acronis Backup: Recovery/Conversion to Virtual Machine Troubleshooting Guide

Also read in:

Translate to:

Operating Systems:

    This article provides instruction for troubleshooting recovery and conversion to virtual machine failures in Acronis Backup (Acronis Backup & Recovery).

    Follow these steps to troubleshoot the recovery and conversion to virtual machine:

    1. Get familiar with technology of restore and conversion to virtual machine in the About part.
    2. Check for known issues in the Known issues part.
    3. Follow to Troubleshooting part to troubleshoot and resolve the issue.

    About

    Acronis Backup (Acronis Backup & Recovery) offers a number of ways of conversion into a virtual machine:

    • Regular conversion to virtual machine as a part of backup plan
    • Recovery of the backed-up disks or volumes to the "New virtual machine" destination
    • Recovery of the backed-up disks or volumes to a manually created virtual machine by using bootable media

    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 ESX(i):

    • VMware ESX(i)

    Agent for Hyper-V:

    • Microsoft Hyper-V

    Steps of the conversion operation

    Regular conversion to a virtual machine:

    Set up the backup plan

    When creating a backup plan, you can set up regular conversion of a disk or volume backup to a virtual machine. By setting up regular conversion, you obtain a copy of your server or workstation on a virtual machine which can be readily powered on in case the original machine fails.

    VM backup is created

    Before the regular conversion starts, a backup of the virtual machine is created including the settings of the virtual machine.

    Backup is converted to a virtual machine

    The way the repeated conversions work depends on where you choose to create the virtual machine.

    • If you choose to save the virtual machine as a set of files: each conversion re-creates the virtual machine from scratch.
    • If you choose to create the virtual machine on a virtualization server: when converting an incremental or differential backup, the software updates the existing virtual machine instead of re-creating it. Such conversion is normally faster. It saves network traffic and CPU resource of the host that performs the conversion. If updating the virtual machine is not possible, the software re-creates it from scratch.

    Virtual machine is created in the folder/on the datastore of the virtualization server

    Virtual disks and virtual machine configuration files are placed/updated in the specified destination.

    Recovery to the "New virtual machine":

    Set up the recovery task

    Data to recover, virtual machine/virtualization sesion and virtual machine settings should be specified.

    Backup is converted to a virtual machine

    Rather than converting a TIB file to a virtual disk file, which requires additional operations to bring the virtual disk into use, Acronis Backup performs the conversion by recovery of a disk backup to a fully configured and operational new virtual machine.

    Virtual machine is created in the folder/on the datastore of the virtualization server

    Virtual disks and virtual machine configuration files are placed/updated in the specified destination.

    Recovery to a manually created virtual machine by using bootable media:

    Preparation of a bootable media with Acronis Universal Restore functionality

    A bootable media with Universal Restore as well as the virtualization platform drivers for Windows guest OS in the backup should be prepared.

    Configuration of the volume and recovery task

    Dynamic volumes for Windows are created prior to recovery task. Software RAID/LVM structure should be applied within the recovery task.

    Recovery of data to the virtual disks

    Data is recovered from backup to the disks.

    Acronis Universal Restore is applied

    Universal Restore replaces HAL on Windows OS or initial RAM disk on Linux OS.

    Best practices:

    • Use recovery to a manually created virtual machine by using bootable media if the source OS contains dynamical volumes (Windows) or software RAID/LVM (Linux).
    • For better performance of conversion directly to a an ESX(i) host, choose an Agent for ESX(i) (Virtual Appliance) located on that ESX(i).
    • If the original machine uses Unified Extensible Firmware Interface (UEFI) for booting, consider creating a virtual machine that is also UEFI-based. 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 & Recovery creates a UEFI-based machine. Otherwise, the resulting machine will use the BIOS boot firmware.

    See more about conversion to virtual machine in following articles:

    Title

    Related to

    Acronis Backup 11.7/11.5: Importing Converted Virtual Machine to Red Hat Enterprise Virtualization Platform Importing VM to RHEV
    Acronis Backup & Recovery 11 Virtual Edition: Incremental Conversion to Virtual Machine Incremental conversion
    Acronis Backup 11.7/11.5: Importing the Converted Virtual Machine Files to VMware ESX Server Importing VM to ESX(i)
    Importing Converted Virtual Machine to Citrix XenServer Importing VM to Xen
    Acronis Backup & Recovery 10: Converting Backup Archive of a Windows System to a Virtual Machine Converting backup to VM
    Converting Backup Archive of a Linux System to a Virtual Machine Converting Linux to VM
    Importing Converted VHD Virtual Disk to Citrix XenServer Importing VHD to Xen
    Adding Converted VMDK Virtual Disk to VMware Virtual Machine Importing VMDK to ESX(i)
    Acronis Backup & Recovery 10: Scheduled Backup Conversion to VM Scheduled conversion
    Acronis Backup & Recovery 10: Converting Backup Archive to a KVM/RHEV Virtual Machine Conversion to KVM/RHEV
    Acronis Backup & Recovery 10: Creating OVF Template to Import VMware Workstation Virtual Machine to ESX/ESXi Server Converting to OVF

    Known Issues

    Title Error Message/Code Related to
    Acronis Backup 11.7/11.5: Powering on an Imported Virtual Machine Fails with the Error “Unsupported and/or Invalid Disk Type” Unsupported and/or Invalid Disk Type Importing VM to ESX(i)
    Acronis Backup & Recovery 10 Advanced Server Virtual Edition Agent for ESX/ESXi: Restore of Windows Server 2008 via Virtual Appliance Makes the System Unbootable

    Status: 0xc0000225

    Info: The boot selection failed because a required device is inaccessible.

    VM settings
    Acronis Backup & Recovery 10 Advanced Server Virtual Edition: Windows Server 2008 R2 Virtual Machine Recovered from a Backup BSODs

    0x0000007B

    File system corruption
    Acronis Backup & Recovery: After Restoring Red Hat Enterprise Linux 4.6 x64 into an Red Hat Enterprise Virtualization Virtual Machine Booting Fails with Kernel Panic

    Kernel Panic

    Kernel compatibility
    Title Related to
    Acronis Backup & Recovery 10 Advanced Server Virtual Edition: Windows Server 2008 R2 Restored as a Virtual Machine Is Detected as Windows 7 VM settings
    Acronis Backup & Recovery 10: Virtual Machine Conversion Does Not Support Citrix XenServer 5.6 Importing VM to Xen
    Windows Activation Required after Restore Using Acronis Universal Restore, Cloning or Converting of Windows Based Partition Backup to Different Hardware or Virtual Environment Windows activation
    MS Virtual PC Does Not Boot from Converted VHD Disk MS Virtual PC limitations
    Acronis Backup 11.7/11.5: Automatic Conversion from Linux System Does Not Recreate LVM/RAID on a Virtual Machine Linux LVM/RAID conversion

    Troubleshooting

    Follow step-by-step instructions below to troubleshoot the issue. Complete prerequisites step before proceeding to error troubleshooting step.

    1. Prerequisites

    Following conditions should be met for the correct functioning of the backup conversion or recovery to a virtual machine. Complete all steps before proceeding to error troubleshooting step.

    1.1 Correct agent and license should be used

    Depending on the conversion way, make sure that the correct agent has been installed and appropriate license is used.

    Save a new virtual machine as a set of files

    • Acronis Agent for Windows
    • Acronis Agent for Linux

    Create a new virtual machine on the virtualization server

    • Acronis Agent for Hyper-V
    • Acronis Agent for ESX(i)

    Recovery to a manually created virtual machine

    • Acronis Bootable Media with Acronis Universal Restore

    1.2 Regular conversion to a virtual machine restrictions

    Consider following restriction on regular conversion from the backup plan:

    • Conversion of a backup from the following locations is not available: CD, DVD, Blu-Ray Discs, tape devices and Acronis Online Backup Storage.
    • Conversion to a Citrix XenServer virtual machine is not available as a part of the backup plan. As an alternative, use recovery to a new or manually created virtual machine.
    • Microsoft Virtual PC does not support virtual disks larger than 127 GB. During a conversion to a Virtual PC machine, the size of every disk that exceeds 127 GB will be reduced to this value. If the disk resize is not possible, the conversion will fail. If you need larger virtual disks in order to connect them to a Hyper-V machine, use recovery to a new or manually created virtual machine.

    1.3 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 to a manually created virtual machine.

    1.4 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 & Recovery 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".

    1.5 Disk interface and custom loader reactivation

    When converting to a new virtual machine:

    • 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.
    • Conversion of logical volumes to basic ones may also prevent the system from booting up.

    When recovering to a manually created virtual machine, you may want its disks to have a different interface than those of the original machine.

    • You may want to change all disk interfaces from IDE to SCSI when migrating a machine to ESX(i), because SCSI is a default disk interface for ESX(i) and it provides better performance.
    • You need to change the system disk interface from SCSI to IDE when migrating a machine to Hyper-V, because Hyper-V does not support booting from SCSI disks.

    For these reasons, 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 normally not needed because Acronis Backup does this automatically. Should the need arise, use the procedure described in "How to reactivate GRUB and change its configuration".

    If all steps above have been executed and issue still persists, go to error troubleshooting step.

    2. Error troubleshooting

    Troubleshoot the conversion to virtual machine errors. Complete all steps before proceeding to collect information step.

    2.1 Validate pre-conversion operations

    Error during conversion may point to the issue in the source data, e.g. in the backup file that is used for conversion.

    Make sure that:

    • The backup is available from the agent in the vault.
    • The backup is valid. If the backup corruption is suspected, validated it. See "Validating archives and backups". To troubleshoot issues with corrupt backups refer to Troubleshooting Issues with Corrupt Backups.
    • The backup is compatible with the version of the agent that is used for conversion. Remember that forward compatibility is not supported for any Acronis backup archives even withing the same product, e.g. a backup created with the build version 37975 may not be compatible for recovery/conversion by the build version 32308. Only backward compatibility is supported, e.g. every newer version can restore backups created with earlier version. Also see Backup archive compatibility across different product versions.

    If regular conversion fails, confirm that the backup file is created correctly prior to start the conversion. Check the recovery to "New virtual machine" with the same destination to allocate the issue.

    If you suspect source data corruption but the archive validation is successful, perform recovery to other type of virtual machine or to other destination or recover a part of the data to allocate the issue.

    Proceed to the next step if issue persists.

    2.2 Troubleshoot conversion process

    Depending on the conversion process check for possible issues:

    2.2.1 Saving a virtual machine as a set of files

    Make sure that the destination folder for the virtual machine files is available:

    • Necessary user rights should be provided in order to create files. Check that the specified agent service user can create files in that folder.
    • File system of the destination folder should have no errors.
    • There should be sufficient free space for the virtual disk files and the configuration files.

    2.2.2 Creating a virtual machine on a virtualization server

    The agent should be able to create or modify virtual machines on the specified virtualization server:

    2.2.3 Recovering from bootable media

    Make sure that the bootable media detects the virtual ware correctly.

    • If the bootable media crashes on any stage of the recovery process, try recreating the media with the latest avaialble build. To download the latest media see Downloading Acronis Bootable Media.
    • The Acronis bootable media should already have all necessary drivers for the supported virtualization platforms. Proceed as described in the articled, if Acronis Bootable Media Does Not Detect HDD, RAID or NIC.
    • Try using a WinPE media if you suspect issues with the Acronis Linux environment.

    See also:

    If the issue persists, proceed to the next step.

    2.3 Troubleshoot post-conversion issues

    If the conversion to the virtual machine has completed successfully, but the operating system is not booting or post-boot problems appear:

    • Make sure that the prerequisites are fulfilled and when required, boot loader is reactivated.
    • Operating system of the virtual machine should be supported.
    • Make sure that correct drivers have been specified for the Universal Restore. Proceed to Troubleshooting Acronis Universal Restore.

    Proceed to next step if issue persists.

    2.4 Check for known issues

    Go to known issues part and check for known solutions

    If a known solution has been applied, but the issue still persists, go to prerequisites step to troubleshoot the new issue.

    If all steps above have been executed and issue still persists, go to collect information step.

    3. Collect information

    Collect following information and contact Acronis Customer Central.

    3.1 AcronisInfo

    Collect System Report from the Agent or media that performed the conversion.

    If recovery is performed via the bootable media, collect the system report right after the recovery process.

    If the virtual machine can boot to OS but there is an issue with the functionality of the OS, collect AcronisInfo from within it:

    3.2 Information about environment

    Provide the conversion environment details:

    • The virtual machine OS.
    • Where the source machine resided initially (hypervisor version and configuration, hardware details for physical machine).
    • What the destination for the new virtual machine is (hypervisor version and configuration).

    Tags: 

    You are reporting a typo in the following text:
    Simply click the "Send typo report" button to complete the report. You can also include a comment.
    CAPTCHA
    This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
    9 + 8 =
    Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.