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)
Virtual machine host names and display names should be unique if VMs are selected manually in the policy
This topic applies to NetBackup for VMware.
Certain VMware environments do not require unique names for virtual machines. For instance, virtual machines within a vCenter server can have the same host or display names as virtual machines in another vCenter server. The same is true of datacenters, which are logical groupings of virtual resources within a vCenter server. Virtual machine host names or display names must be unique within a datacenter. They do not need to be unique between two datacenters on the same vCenter. A virtual machine named VM1 can exist in datacenter A. Another virtual machine (also named VM1) can exist in datacenter B, on the same vCenter server.
Identically named virtual machines can present a problem for any policies that are configured as follows:
The master server's policies use the Clients tab to select the VMs for backup.option on the
The VMware tab identifies VMs by their host names or display names.option on the
These policies may back up a different but identically named VM, instead of the VM that you selected. In that case, the VM that you selected is not backed up. For these policies to work, the virtual machines' display names or host names must be unique.
Consider the following options:
For manual policies that identify VMs by display name or host name, change the VM names so that each VM has a unique host name or display name.
As an alternative, configure the policies'option to identify the VMs by their UUIDs instead of by host name or display name. Use the type of UUID that is appropriate for your virtual machine environment.
Instead of policies with manual-selection, use VMware Intelligent policies to select the VMs through a query. Even if theoption is set to host name or display name, NetBackup identifies each VM by its UUID.