We have had VCB working for well over a year. I was working fine with NetBackup 5.1 and Virtual Center 2.5 and ESX version 3.5 when we upgraded to NetBackup 6.5.1 last week. Now VCB does not work. We are getting a (74) bpstart_notify timeout. Has anyone gotten this to work with 6.5.1?
You have to remove the VMware Intergration Module if you're using 6.5 or above....
/Rubeck
You have to remove the VMware Intergration Module if you're using 6.5 or above....
/Rubeck
Hasn't 6.5.2 been released? Check out chapter two of this doc for 652 -> http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/302438.pdf
Dave
sharvey2 -
Actually, you can keep the integration kit, you just need to delete the bpstart_notify and bpend_notify scripts. Uninstalling the integration kit SHOULD remove these, unless you used custom scripts...
Dave
We're up and running. Symantec support for VCB is a lot tighter now. We had to completely rip out the VCB framework from the windows proxy and re-install, and we had to install a Snapshot Client License on the master backup server. We also had to upgrade the NetBackup client on the proxy to 6.5.1. It's working, now we have to see how much $$$ Symantec is going to demand. We think we only have the one client, as before (since VCB and Virtual Center are doing most of the work). Their sales guy is talking about multi-tiered licensing for all our ESX servers.
He will try to sell you clients for all the VMs too. You should look into 6.5.2 there are a pile of fixes. I had problems with 6.5.1 on my last engagement.
As dconvery says... Go with 6.5.2. It also includes the -nbd option with VCB ![]()
/Rubeck
