Before You Begin

In this article

    Before you perform Instant Recovery, consider the following:

    • 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.
    • Restore of CSV (Cluster Shared Volumes) is not supported. Cluster disks used as CSV are automatically excluded from restore.
    • Mind the following for Linux workloads:
    • We strongly recommend to have 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 filesystems are mounted using UUID. If any filesystems are mounted using block device name, the restored VM may not boot.
    • 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.

    • [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.