Before You Begin

Before you restore a VM from a backup, consider the following:

  • You can restore a VM from a backup that has at least one successfully created restore point.
  • If you back up a VM with vRDM disks, Veeam Backup & Replication converts the disks into VMDK files. Thus, when you restore a VM with a vRDM disk, Veeam Backup & Replication restores this disk as a VMDK file. If you want to preserve the vRDM format for restored disks, use Quick Rollback. For more information, see Quick Rollback.
  • Check requirements and limitations in the VMs section in Platform Support.
  • [For restore to original location] If the original VM is still running, Veeam Backup & Replication powers off the original VM and deletes it before the restore.
  • If you want to scan VM data for viruses, check the secure restore requirements and limitations.
  • If you want to run an executable script for a VM, check the staged 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 VM restore. You can ignore this warning for non-Microsoft Windows SMB3 storage.
  • The restored VM will have the same MAC address as the original VM. Therefore, if you restore the VM to the same Hyper-V host where the original VM is running, a MAC address conflict may occur. To overcome this situation, power off the original VM before you start the restore process.
  • The version of the target host on which the VM is restored 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.

Page updated 2/6/2024

Page content applies to build