Before You Begin

Before you perform Instant Recovery, consider the following:

• Prerequisites for Instant Recovery from storage snapshots are listed in the Data Recovery from Storage Snapshots section in the Storage System Snapshot Integration Guide.

• You can recover a workload from a backup that has at least one successfully created restore point.
• [For VMware vSphere version 8.0 and later] You cannot perform Instant Recovery for a VM that has disks on a vVol datastore and that is located on an ESXi host version 8.0 or later.
• If you recover a workload to the production network, make sure that the original workload is powered off.

• Restore of CSV (Cluster Shared Volumes) is not supported. Cluster disks used as CSV are automatically excluded from restore.
• When you restore workloads other than VMware vSphere VMs, Veeam Backup & Replication assigns to the restored VMs the highest VM hardware version supported by the ESXi host to which you restore the workloads. For more information on ESXi hosts and compatible virtual machine hardware versions, see this VMware KB article.

• Consider the following for Linux workloads:

• We strongly recommend having dracut, mkinitrd or initramfs installed on workloads that will be restored. Otherwise, they may not boot after restore.
• Open the /etc/fstab/ file and check that all filesystems are mounted using UUID. If any filesystems are mounted using block device name, the restored VM may not boot.

• If you want to scan recovered VM data for viruses, check the secure restore requirements and limitations.

• You must provide enough free disk space in vPower NFS datastore. The minimum amount of free space must equal the RAM capacity of the recovered VM plus 200MB. For example, if the recovered VM has 32 GB of virtual RAM, 32.2 GB of free space is required.

By default, vPower NFS datastore is located in the IRCache folder on a volume with the maximum amount of free space, for example, C:\ProgramData\Veeam\Backup\IRCache. The vPower NFS datastore is not used when you select to redirect virtual disk updates to a VMware vSphere datastore when configuring the job.

• You cannot use a vVol datastore as a destination for virtual disk updates.
• [For Veeam Agents] Restore of 4K native drives is not supported. For more information on VMware vSphere limitations, see this VMware KB article.
• [For Veeam Quick Migration with Smart Switch] In addition to the disk space mentioned above, you need to provide more disk space in vPower NFS datastore. The minimum amount of free space must equal the RAM capacity of the recovered VM.
• [For Nutanix AHV VMs] Instantly recoverd 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.