Step 6. Select Destination for Virtual Disk Updates
The Datastore step of the wizard is available if you have chosen to change the location and settings of the restored VM.
At the Datastore step of the wizard, you can select where redo logs must be written when the VM is running from the backup. By default, redo logs are stored directly on the backup server. However, you can store redo logs on any datastore in the virtual environment. Redirecting redo logs improves recovery performance but makes Storage vMotion not possible for ESX(i) 5.x and earlier.
To redirect redo logs:
- Select the Redirect virtual disk updates check box.
- Choose the datastore.
Mind the following:
- If you plan to migrate the recovered VM to the same datastore which is used as the destination for redirecting virtual disk updates, Veeam Backup & Replication will automatically switch to Veeam Quick Migration instead of using Storage vMotion. The described behavior is implemented to prevent data loss due to a bug in VMware Storage vMotion. Note that using Veeam Quick Migration will cause minimal VM downtime.
- If disks of a restored VM are located on VSAN and their size is greater than 2 TB, you must place redo logs on a VMFS datastore. For virtual disks greater than 2 TB, VMware vSphere creates snapshots in the SEsparse format. If you place redo logs on a VSAN datastore, Veeam Backup & Replication will fail to create a snapshot for the restored VM since SEsparse snapshots are not supported on VSAN. For more information about snapshot formats, see https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-88E5A594-DEBC-4662-812F-EA421591C70F.html.