Read this forum post:
https://www-secure.symantec.com/connect/forums/nbu-65-vmware-intergration-failed-get-vm-server-info-list
Note:
NetBackup uses DNS lookups to populate the browse list. Make sure that the virtual machine’s FQDNs can be resolved or they are listed in the HOSTS file on the VCB proxy server. This populated list is cached in a file on the VCB proxy server in:
C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\vcbnames_vc-FQDN_Any
In a few cases, the directory may not have been created during the install. If this is true, manually create and recreate the policy. This list may be outdated if new virtual machines have been added. Simply click the refresh button to update the list.
- Also check your NetBackup Admin Console > View menu >Options > Policies tab and increase the VMware connect timeout value. I'm sure this fixed that for me in the early days.
Problem reaching the Virtual Machine from
vcb_best_practices.pdf
<snippet from page 16>
When you attempt a snapshot backup, you may receive an error message saying the command cannot reach the virtual machine. There are a number of possible reasons for this error message.
Sometimes, the virtual machine is not properly registered with the VirtualCenter database, or the virtual machine might not receive an IP address before the backup begins.
To test for these problems, run the vcbVmName command from a command prompt on the backup proxy server.
The following examples illustrate how to use vcbVmName:
• vcbVmName -s powerstate:on — Lists all powered on virtual machines.
• vcbVmName -s any: — Lists all known virtual machines.
• vcbVmName -s ipaddr:vm37.company.com — Displays information about the virtual machine with the specified address.
The following example illustrates the output of vcbVmName:
# vcbVmName -s name:vm37.company.com
Found VM:
moref:192
name:Virtual Machine 37
uuid:564d78a1-8c1c-59b4-fa02-be14138797be
ipaddr:10.17.5.31
Compare the IP address reported by vcbVmName with the address shown in the VI Client. The two should be the same. If they are not, it might indicate that your VirtualCenter database is not current and that some of the virtual machine information in the database is inaccurate. If there is a mismatch, it might indicate a VMware Tools failure. Make sure the version of VMware Tools installed in the virtual machine is up-to-date.
</snippet>
- In the VI Client can you see the IP address against the Summary of all your VM's, and that VMware Tools is OK
- VCB 1.5 should be installed and update to at least NetBackup 6.5.3 also.
Also here is a good resource for VMware Backups/VCB docs
http://www.vmware-land.com/Vmware_Links.html#Backups
VMware Proven Practice Doc
Integrating Netbackup 6.5.1 with VCB 1.1