Notes and limitations for tag usage in VMware Intelligent Policy queries
NetBackup does not support the selection of virtual machines based on the category.
NetBackup uses tags for virtual machine selection independent of the tag's category. The VMware vSphere Web Client can create tags in two different categories with the same tag name. In the example, both virtual machines are selected if the policy is configured to include virtual machines with the "HR" tag.
Example:
Virtual_Machine_1 has a user-specified tag HR in the category Production
Virtual_Machine_2 has a user-specified tag HR in the category Test
NetBackup only recognizes the tags that are associated with virtual machines, not other vCenter objects such as Datastores.
vCenter Server 6.0 or later is required.
The NetBackup master server and all discovery hosts must be at NetBackup 7.7.1 or later.
When you use media server load balancing, all media servers that are associated with the storage unit group must be at 7.7.1 or later.
Any Windows host with only the NetBackup Client Software installed that is also defined in the VMware policy's Client tab as the NetBackup host to perform automatic virtual machine selection must have NetBackup Java installed. Install the NetBackup Remote Administration Console to install NetBackup Java.
Be aware of a known bug in vSphere 6.0 when either the tag description or category description shown in the VMware vSphere web client is blank. If either field is blank, all tag queries fail with a NetBackup Status Code 4261.
VMware knowledge base article: http://kb.vmware.com/kb/2124204
Veritas has confirmed that this issue is resolved in vCenter Server 6.0 Update 1.
Be aware of a known bug in vSphere 6.0 when the system time of the discovery host and the vCenter Server are not synchronized. This issue is known to cause backups to fail with a NetBackup Status Code 4263.
VMware knowledge base article: http://kb.vmware.com/kb/2125193
In large VMware environments, consider increasing the Maximum bearer token lifetime from the default value. Veritas has observed issues with discovery jobs timing out because the default value is too small. The Maximum bearer token lifetime is a vCenter Server setting. More information on this issue is available.