This is an archive version of the document. To get the most up-to-date information, see the current version.

Before You Begin

Before you perform Instant Recovery, do the following:

  • Power off the original machine if it is still present in the target location.
  • Deploy a dedicated server to mount workload images directly from backups stored in backup repositories and allocate minimum 512 MB of additional RAM for each VM disk that you want to recover. Make sure that the Server for NFS role and the Client for NFS component are not installed on the server, and that the Veeam vPower NFS Service is running.
  • [Applies only to VMs being restored from backups stored in the archive tier of scale-out backup repositories] Retrieve backup data as described in the Veeam Backup & Replication User Guide, section Retrieving Backup Files. However, this requirement is not applicable to backups stored in the archive tier that consists of the Amazon S3 Glacier Instant Retrieval extent.
  • [Applies only to Linux VMs] Make sure that the file systems (also referred to as devices or partitions) listed in the the /etc/fstab file are mounted using UUIDs. Instant Recovery of file systems mounted using device names is not supported as the restored VMs may fail to boot.
  • [Applies only to Windows VMs being restored from backups created by solutions other than Veeam Backup for Nutanix AHV] Make sure to install SCSI drivers and Nutanix Guest Tools on the VMs — before the backups are created. You will not be able to add or modify the VM drivers during the recovery operation.