Perform Recovery dialog box
Review the settings to be applied to the restored virtual machine.
Recovery settings
Lists the settings that are used for the recovery.
Run Pre-Recovery Check
Click this option to verify the following: The credentials, the available space on the datastore, and other important requirements. For a description of the checks, see Table: Pre-recovery checks.
Start Recovery
Starts the recovery of the virtual machine.
Table: Pre-recovery checks
Type of check | Description |
|---|---|
Verify vSphere server credential | Verifies that NetBackup has the correct credentials to access the vSphere server for the restore. |
Verify datacenter path | Verifies that NetBackup can access the datacenter that is designated for the restore. |
Verify folder path | Verifies that NetBackup can access the VM folder that is designated for the restore. |
Unsupported non-ASCII characters | Checks for unsupported characters in the VM display name, datastore name, or network name. |
VM exists overwrite | If the original VM exists at the restore destination, verifies that the option is selected. If the VM exists and the overwrite option is selected, the VM is overwritten with the restored VM. If the original VM does not exist at the restore destination, verifies that the original VM's vmx configuration file directory does not exist. If the original VM does not exist but the vmx directory exists, specify a different display name for the restored the VM. |
Adequate space on datastore (or datastore cluster) for configuration file | Verifies that the datastore (or datastore cluster) for the restore has enough space for the restored VM's vmx configuration file. |
VMware connectivity test | Verifies that the NetBackup restore host can communicate with the vCenter server. |
Datastore/Datastore Cluster space available | Verifies that the datastore (or datastore cluster) for the restore has enough space for the restored VM files. |
SAN datastore compatibility | Verifies that the selected datastore has a compatible block size. For example, this check fails if it detects the following problem: The VM's vmdk files are not a multiple of the VMFS block size. In that case, the last partial-block write may fail during the restore, and the restore job fails with status 2820. The NetBackup job details log contains messages similar to the following: 12/12/2011 3:12:28 AM - Critical bpbrm(pid=3560) from client io.acme.com: FTL - Virtual machine restore: file write failed In this case, use the NBD or the NBDSSL transport mode when you restore the VM. |
Verify unique BIOS UUID | If only the SAN transport mode is selected for the restore, determines if a VM with the same BIOS UUID exists on the specified vCenter. |