Veritas NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Adding NetBackup credentials for VMware
- Validating VMware virtualization server certificates in NetBackup
- Configure NetBackup policies for VMware
- VMware backup options
- Exclude Disks tab
- Configure a VMware Intelligent Policy
- Reduce the size of backups
- Back up virtual machines
- Use Accelerator to back up virtual machines
- Restore virtual machines
- Restoring the full VMware virtual machine
- Virtual Machine Recovery dialog boxes (restore to original location)
- Virtual Machine Recovery dialogs boxes (restore to alternate location)
- Restoring VMware virtual machine disks by using Backup, Archive, and Restore
- Restoring VMware virtual machine disks by using NetBackup commands
- Restoring individual VMware virtual machine files
- Browse and search virtual machines for restore
- Restore virtual machines with Instant Recovery
- Use NetBackup for vCloud Director
- Virtual machine recovery dialog boxes for vCloud Director
- Best practices and more information
- Troubleshooting
- Appendix A. NetBackup commands to back up and restore virtual machines
- Using NetBackup commands to create a VMware policy
- Appendix B. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- About configuring services for NFS on Windows 2008 and 2008 R2 (NetBackup for VMware)
- Appendix C. The Reuse VM selection query results option
- Appendix D. Backup of VMware raw devices (RDM)
Troubleshooting vmdk restore to existing VM
For virtual disk restores to an existing VM, be aware of the following:
If the VMDKs cannot be attached to the target VM, the restored VMDKs are retained on the temporary VM. The name of the temporary VM is available in the job details in NetBackup. In the following job details example, the temporary VM name is vCenter60vm1_rhel6.4_1465584674:
06/10/2016 13:51:17 - Info bpVMutil (pid=3400) Restoring [datastore1] vCenter60vm1_rhel6.4/vCenter60vm1_rhel6.4_4.vmdk to [datastore1] vCenter60vm1_rhel6.4/vCenter60vm1_rhel6.4_4-1465584677.vmdk 06/10/2016 13:51:38 - Info bpVMutil (pid=3400) Successfully created virtual machine vCenter60vm1_rhel6.4_1465584674 with specified disks. 06/10/2016 13:51:41 - requesting resource @aaaab
You can access the data on the temporary VM.
If the temporary VM is retained after a restore failure, the restore job contains a message similar to the following:
06/14/2016 15:29:06 - Info bpVMutil (pid=5225) attachDisksToExistingVM: Unable to attach restored disks to target VM vCenter60vm2_rhel6.4 06/14/2016 15:29:06 - Info bpVMutil (pid=5225) attachDisksToExistingVM: Temporary VM with restored virtual disks was left in place, it can be used to access restored data
By default, NetBackup retains the temporary VM if the disks are not attached. To change that behavior, set the DeleteRestoredVMOnError field to Yes in the restore parameters file.
After a restore to an existing VM, the next backup of the VM backs up the restored virtual disks. This backup may show a warning during collection of the Changed Block Tracking (CBT) information.