Can't get VCB backups working on NB 6.5.2!

[tjhebert]

I have tried everything - I think!

We're running virtual center, and using root account and root password with port 443 for credentials.

VCB proxy server is w2k3 x64, VCB 1.1, Converter 3.0.2, ESX 3.02

proxy server has access to datastores

timeouts set: GUI is 500, policies is 600

I can't browse virtual machines when setting up policy.

Can anyone out there help??

[Dion]

Can your NetBackup master and proxy server resolve the names of the clients?  Even thought it does not need to use IP for VCB backup, it still needs to resolve the client names.

There are also quite a lot of comment regarding these types of issue earilier on in this forum - just do a search.

[Peter_Jakobs]

Create the c:\Program Files\Veritas\netbackup\logs\bpvmutil directory, set verbose to 5 and try to browse. Mostly the error is clear there.

Peter

[Anonymous · Accepted solution]

The bpvmutil log file will indicate a lot of debugging. But you mention root account and root password.

You should use the vcadmin account or better still create a account on the virtual center server called vcbuser and give them only restricted permissions/roles for better security and so the 'root'/privileged password is not used outside the Virtual Infrastructure.

This is documented in several best practices documents and details the permissions to give that user in the Virtual Infrastructure. See here:

http://vmetc.com/2008/01/09/create-a-vcbuser-vcb-best-practice/

http://www.vmware.com/files/pdf/vcb_best_practices.pdf

As you dont want to have your virtual center admin or root account anywhere else other than on the virtual center server for security reasons.

(Also will be interesting to know if you get this completely working to the point of testing a restore of a full virtual machine using the converter option.

I have W2K3 STD 64bit Server and the restore of the virtual machine fails to run the supplied scripts to put the virtual machine back into the virtual infrastructure using VMware converter on the proxy server because first lack of the existence of a registry key tree - namely HKLM/Software/VMware, Inc/ however this exist on a 32bit server. Then when you do hack the registry with the key and the path to the converter the debug log files say that it has a permission issue.)

Master: NB 6.5.2

VCB Proxy: Windows 2003 Server R2 Std Edtn 64 bit; VCB 1.1

VI: 3.5; Converter: 3.03; Virtual Center: 2.5