Veritas NetBackup™ for VMware Administrator's Guide
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Adding NetBackup credentials for VMware
- 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
- 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)
How to determine the ESX network that NetBackup used for the backup or restore
If a virtual machine's disks are accessible to multiple ESX hosts, the disks can be accessed through any of the ESX hosts. The ESX host that is used for the access may or may not be the ESX host where the virtual machine is running or registered. All of the following must be accessible to each other and should have DNS configured:
The vCenter server.
All ESX hosts under the vCenter that have access to the virtual machine's vmdk files.
The backup host.
If all hosts are not accessible to each other, the backup or restore may not succeed. In that case, you must determine which network NetBackup used for the backup or restore.
Note: For an NBD transport mode backup through vCenter, NetBackup uses the ESX network over which the ESX host was added or registered to the vCenter. For an NBD transport mode backup directly from the ESX host, NetBackup uses the ESX host's DNS/IP network.
The VxMS provider logs contain information on the network that NetBackup used.
Check the VxMS provider logs for messages similar to those in this example:
10:49:21.0926 : g_vixInterfaceLogger:libvix.cpp:1811 <INFO> : Opening file [MYDATASTORE] TestVM/TestVM-000001.vmdk (vpxa-nfc://[MYDATASTORE] TestVM/TestVM-000001.vmdk@MyESX.xxx.xxx.com:902) 10:49:22.0301 : g_vixInterfaceLogger:libvix.cpp:1811 <INFO> : DISKLIB-LINK : Opened 'vpxa-nfc://[MYDATASTORE] TestVM/TestVM-000001.vmdk@MyESX.xxx.xxx.com:902' (0x1e): custom, 41943040 sectors / 20 GB. 10:49:22.0301 : g_vixInterfaceLogger:libvix.cpp:1811 <INFO> : DISKLIB-LIB : Opened "vpxa-nfc://[MYDATASTORE] TestVM/TestVM-000001.vmdk@MyESX.xxx.xxx.com:902" (flags 0x1e, type custom). 10:49:22.0301 : vdOpen:VixInterface.cpp:480 <DEBUG> : Done with VixDiskLib_Open(): 200346144 10:49:22.0301 : openLeafSnapshotDisks:VixGuest.cpp:475 <DEBUG> : vdOpen() succeess 10:49:22.0301 : openLeafSnapshotDisks:VixGuest.cpp:476 <INFO> : Transport mode in effect = nbd
VMware logs the messages starting with
g_vixInterfaceLogger. Such messages in the example indicate that TestVM-000001.vmdk is opened over the ESX host network
The following article contains related information:
Best practices when using advanced transport for backup and restore