We have some updated information.  The backup proxy server is a 64bit system.  Apparently when the VMware converter utilities are installed, they are installed as 32 bit binaries but are supposed to be compatible (from VMware’s perspective) with 64 bit systems.  However, NetBackup requires a change to the registry in order to support the converter binaries. After making the changes to the registry recommended by support, our errors have gone away…but the files still never make it from the proxy server to the Virtual Infrastructure server.  More results pending from latest log files sent to support.

 

Thanks George…one of the things we will try is to try running the bpvmutil manually to see if that gives us any more information than what we are currently getting in the log files.

 

Renee

 

 

Hi Renee.

 

There are a couple of reasons why this might happen. 

 

Most common issue is DNS.  For example, the Virtual Center server might not be resolving correctly from the VMware Backup Proxy.  You can easily check this by adding the hostname of Virtual Center Server to the Backup Proxy’s “hosts” file.

 

You might have a permissions issue.  What account are you using when you define the Virtual Center credentials?  If you are not using the Virtual Center server “administrator” account you might not have been granted the appropriate permissions within the Virtual Center server.  Look in documentation that can be found on VMware’s site to find out what permissions are required.

 

Another cause could be that the VCB Framework is not actually installed on the Backup Proxy.  From your description, this does not sound likely but I thought I would mention it.

 

You should also make sure that the Backup Proxy has been defined on the Master Server Hosts Properties.

 

One way you can see what NetBackup is doing when attempting to contact the Virtual Center server is to manually run the “bpvmutil” command (found in netbackup\bin on the Backup Proxy).  This is the syntax for this command:

 

bpvmutil  0  NOCACHE  0

 

NOTE:  Use the number “zero” twice, not the letter O.  Also “NOCACHE” must be all caps.

 

The output of this command points you to a text file that is created.  If nothing (or very little) is written to this file then NetBackup cannot communicate with the Backup Proxy.  Maybe a firewall issue?  You can also create a bpvmutil log directory to obtain more information related to this command.

 

HTH

 

-George Winter

 

 

 

 

When trying to search for Virtual Machines in a VCB policy, the search keeps failing with cannot connect on socket error.  I have double checked credentials, tried both the ESX server and the Virtual infrastructure server, tried both ports 902 and 443 (which should be the correct one for VCB framework 1.5).  Tried to log in to the VI server and the ESX server with the user name and password I am giving the credentials…both are successful.  Tried to telnet to the port from the master server on the ESX server and VI server and that is successful.  Running Solaris 10 with NBU 6.5.1 on the master server.

 

Anyone have any ideas?

 

Renee