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

Before You Begin

In this article

    Before you perform Instant VM Recovery, check the following prerequisites:

    • You can restore a VM from a backup that has at least one successfully created restore point.
    • If you are recovering a VM to the production network, make sure that the original VM is powered off to avoid conflicts.
    • On non-Microsoft Windows SMB3 storages, 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 storages.
    • You must have at least 10 GB of free disk space on the vPower NFS datastore to store virtual disk updates for the restored VM. By default, virtual disk updates are written to the C:\ProgramData\Veeam\Backup\NfsDatastore folder on the vPower NFS server. Veeam vPower NFS cache is not used when you choose to redirect virtual disk updates to a VMware vSphere datastore in the Instant VM Recovery wizard.
    • Finalizing Instant VM Recovery using Veeam Quick Migration with Smart Switch requires at least the amount of instantly recovered VM RAM settings plus 200 MB of free disk space in vPower NFS cache location to suspend the VM state to disk. For example, if the restored VM has 32 GB of virtual RAM, 32.2 GB of free space is required. This is not a requirement when you are using vSphere Storage vMotion instead.