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:

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.

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 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

If you use block-level incremental backups (BLIBs) with a VMware VIP policy, understand the effect of changing the VMware discovery host setting. After this policy change, subsequent incremental backups will back up the full data, not only the changed data, because the policy manager loses the backup references. If the discovery host must be changed, a full schedule backup is needed after the policy change to allow subsequent incremental backups to back up the changed data.

In large VMware environments, consider increasing the Maximum bearer token lifetime from the default value. Cohesity 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.

See Troubleshooting VMware tag usage.