Before You Begin

Before you perform Instant Recovery to Microsoft Hyper-V, consider the following:

  • You must add the Hyper-V target host to which you want to recover machines to your backup infrastructure.
  • The following configuration is not supported:
  • The storage I/O balancing is enabled on a Hyper-V host. Starting from Microsoft Windows Server 2012, I/O balancing is enabled by default.
  • The backup repository role is assigned to a VM on this Hyper-V host. The backup from which you recover is stored on this repository.
  • You plan to recover a VM to this Hyper-V host or SureBackup is targeted to this host.

For information on how to recover with such configuration, see this Veeam KB article.

  • Make sure that the Disable changed block tracking for this host option is not selected for a host to which you plan to recover a workload. If this option is selected for the host, the driver required for work of Instant Recovery will be disabled. For more information, see Configuring Connected Volumes.
  • You can recover a workload from a backup that has at least one successfully created restore point.
  • If you recover a workload to the production network, make sure that the original workload is powered off to avoid conflicts.
  • Consider the following for Linux workloads:
  • We strongly recommend having dracut and mkinitrd installed on workloads that will be restored. Otherwise, they may not boot after restore.
  • Open the /etc/fstab/ file and check that all file systems are mounted using UUID. If any filesystems are mounted using block device name, the restored VM may not boot.
  • [If you recover Hyper-V VMs] The version of the target host on which a VM is recovered must be the same or later than the version of the source host where the original VM was registered.

For example, you can restore a VM from the host that runs Microsoft Windows Server 2016 to the target host that runs Microsoft Windows Server 2016 (including version 1809), Microsoft Windows Server 2019 or later.

The Hyper-V role must be enabled on both source and target hosts.

  • If you want to scan recovered VM data for viruses, check the secure restore requirements and limitations.
  • On non-Microsoft Windows SMB3 storage, for example, Tintri, Veeam Backup & Replication may display the "Failed to disable integrity bit on disk N" warning during the restore process. You can ignore this warning for non-Microsoft Windows SMB3 storage.
  • The recovered VM will have the same MAC address as the original workload. Therefore, if you recover the workload to the same Hyper-V host where the original workload is running, a MAC address conflict may occur. To overcome this situation, power off the original workload before you start the recovery process.
  • [For Nutanix AHV VMs] The recovered VM will not be connected to a network. You must connect to the network manually.
  • [For Nutanix AHV VMs, Amazon EC2 instances and Microsoft Azure virtual machines] Instantly recovered VM will have default virtual hardware settings: 2 CPU cores, 4GB RAM and one network adapter. If you want to change the default settings, turn off the VM and set the required virtual resources. Note that you must not switch off the instant recovery session before turning off the VM.