Before You Begin
In this article
Before you perform Instant VM Recovery, consider the following:
- You must add the Hyper-V target host to which you want to restore machines to your backup infrastructure.
- Make sure that the Disable changed block tracking for this host option is not selected for a host to which you plan to restore a workload. If this option is selected for the host, the driver required for work of Instant VM Recovery will be disabled.
- You can restore a workload from a backup that has at least one successfully created restore point.
- If you restore a workload to the production network, make sure that the original workload is powered off to avoid conflicts.
- 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 restored VM will have the same MAC address as the original workload. Therefore, if you restore 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 restore process.
- [For Nutanix AHV VMs] The restored 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 restored 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.