To recover a VM to an alternate location

1. On the left, click VMware.
2. Locate and click on the VM.
3. Click the Recovery points tab. In the calendar view on the left, click the date on which the backup occurred.

   The available images are listed in rows with the backup timestamp for each image.

4. On the image you want to recover, click Recover > To alternate location.
5. Review or change the following options:

   Restore to:

   • Lists the new VM display name appended with _copy.

   • Lists the ESXi server or cluster and other destination details. The defaults are from the original VM image. Click Change to make different selections.

   Recovery options:

   Allow overwrite of existing virtual machine	If a VM with the same display name exists at the destination, that VM must be deleted before the recovery begins. Otherwise, the recovery fails.
   Power on after recovery	Automatically powers on the VM when the recovery is complete.

   Advanced settings:

   Create a new BIOS UUID	Restores the VM with a new BIOS UUID instead of the original BIOS UUID.
   Create a new instance UUID	Restores the VM with a new instance UUID instead of the original instance UUID.
   Remove backing information for devices	For example, this option restores the VM without restoring any ISO file that was mounted when the VM was backed up.
   Remove original network configuration	Removes the NIC cards from the VM. Note that for network access, the restored VM requires network configuration. Enable this option if: The network connections on the destination virtual machine have changed since the backup was made. The original virtual machine still exists and a duplicate VM may cause conflicts.
   Retain original hardware version	Enable this option to restore the VM with its original hardware version (such as 4). It retains the original version even if the target ESXi server by default uses a different hardware version (such as 7 or 8). If the target ESXi server does not support the virtual machine's hardware version, the restore may fail. If this option is disabled, the restored virtual machine is converted to the default hardware version that the ESXi server uses.

   Format of restored virtual disks:

   Original provisioning	Restores the VM's virtual disks with their original provisioning.
   Thick provisioning lazy zeroed	Configures the restored virtual disks in the thick format. The virtual disk space is allocated when the disk is created. This option restores the populated blocks, but initializes vacant blocks with zeros later, on demand. Note: If the vmdk is completely written, VMware automatically converts a lazy-zeroed disk to Thick provisioning eager zeroed.
   Thick provisioning eager zeroed	Configures the restored virtual disks in the thick format. Restores the populated blocks and immediately initializes vacant blocks with zeros (eager zeroed). Creation of the virtual disks may take more time with this option. However, if the restore occurs over a SAN, the eager zeroed feature may speed up the restore by reducing network communication with the vCenter server.
   Thin provisioning	Configures the restored virtual disks in the thin format. Restores the populated blocks but does not initialize vacant blocks or commit them. Thin provisioning saves disk space through dynamic growth of the vmdk file. The vmdk files are no larger than the space that the data on the virtual machine requires. The virtual disks automatically increase in size as needed. Note: If the vmdk is completely written, VMware automatically converts a thin disk to Thick provisioning eager zeroed.

6. Click Start recovery.

   If you refresh the display, the Restore activity tab shows the job progress.

   For information on the recovery status codes, see the NetBackup administrator or the NetBackup Status Codes Reference Guide, available here:

   http://www.veritas.com/docs/000003214