Recover a VM
You can recover a VM to its original location where it existed when it was backed up or to different location. You can choose to recover from the default copy of the backup image or from an alternate copy, if one exists. The default copy is also known as the primary copy.
To recover a VM
- On the left, click VMware.
- Locate and click on the VM.
- Click the Recovery points tab. In the calendar view on the left, select the date on which the backup occurred.
The available images are listed in rows with the backup timestamp for each image.
On the image that you want to recover, select one of the following image recovery options:
Recover
Recover from the default copy of the backup image. This option is displayed if only one copy exists.
Recover from default copy
Recover from the default copy of the backup image. This option is displayed if more than one copy exists.
nn copies
Recover from the default copy or a different copy of the backup image. NetBackup allows up to ten copies of the same backup image. All available copies are displayed when you select this option. For each copy, the Storage name, Storage Server, and the Storage server type are displayed. Click Recover for the copy that you want to recover.
Choose the location to which you want to recover the backup image:
Original location: Recovers the backup image to the original location.
Alternate location: Recovers the backup image to an alternate location.
Create instant access virtual machine: Recovers the backup image to a new instant access virtual machine. This option is available only if the backup image has instant access capability. See Create an instant access VM.
Download files and folders: Downloads the files and folders from a VM backup image. This option is available only if the backup image has instant access capability. See Download files and folders from a VM backup image.
Restore files and folders: Restores the files and folders from a VM backup image. This option is available only if the backup image has instant access capability. See See Restore files and folders from a VM backup image.
- Review the Restore to values.
The default values come from the backup image of the VM. New display name is appended with
_copyif you restore to an alternate location.If you recover the backup image to the original location, you cannot change the default values.
To recover to an alternate location, change the restore values, if necessary. Then click Next. More information is available if you cannot change the ESXi server or cluster:
- Review or change the Recover option values.
For more information about the recovery options, refer to the 90 for VMware Administrator's Guide.
Allow overwrite of existing virtual machine
Deletes any VM with the same display name that exists at the destination. That VM must be deleted before the recovery begins. Otherwise, the recovery fails.
Note:
You must have the Overwrite Asset permission to use this option. See your security administrator if you need this permission.
Power on after recovery
Automatically powers on the VM when the recovery is complete.
Recovery host
Indicate the host that you want to use to perform the recovery. By default, the recovery host is the one that performed the backup.
- Review or change the Advanced Settings values.
For more information about the advanced settings, refer to the NetBackup for VMware Administrator's Guide.
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.
If this option is disabled, the recovery might fail if the backing information is not longer available for devices, such as DVD/CD-ROM drives, or serial or parallel ports.
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
Restores 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.
Transport mode:
Use transport mode used for backup
Uses the same transport mode that was used when the backup was performed.
Try the selected transport modes in the following order
SAN
For unencrypted transfer over Fibre Channel (SAN) or iSCSI.
Note:
This mode is not supported for the virtual machines that use VMware Virtual Volumes (VVols).
HotADD
Lets you run the VMware backup host in a virtual machine. For more information about the HotAdd transport mode, see NetBackup for VMware Administrator's Guide.
Note:
For the virtual machines that use VVols, the virtual machine and the backup host (hotadd) virtual machine must reside on same VVol datastore.
For instructions on this transport mode and on installing the backup host in a VMware virtual machine, refer to your VMware documentation.
LAN
Transfer the virtual disk data over the network.
NBD
For unencrypted transfer over a local network that uses the Network Block Device (NBD) driver protocol. This mode of transfer is usually slower than Fibre Channel.
NBDSSL
For encrypted transfer (SSL) over a local network that uses the Network Block Device (NBD) driver protocol. This mode of transfer is usually slower than Fibre Channel.
- Click Pre-recovery check.
NetBackup verifies the credentials and appropriate paths and connectivity, determines whether the datastore or datastore cluster has available space, and reviews other requirements. For more information about the pre-recovery check, refer to the NetBackup for VMware Administrator's Guide.
- Resolve any errors.
You can choose to ignore the errors. However, the recovery may fail.
- Click Start recovery.
Click the Restore Activity tab to monitor a job's progress. Select a specific job to view its details.
For information on the recovery status codes, see the NetBackup administrator or the 90 Status Codes Reference Guide.