Last week we started having problems with our working VCB server. The server is a Windows 2003 physical server with the LUNs mapped to our ESX clusters. We are using VCB 1.1, VC 2.5 Update 1 and ESX 3.5 (no update 1 yet).
Last Thursday 2 minutes before some errors appeared the Windows VCB proxy had the following in the Application log
"Successful auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt>"
2 minutes later there were 4 errors for the VMware Virtual Mount Service Extended, Event ID: 3, Error:2. Then our VCB backups started failing.
I uninstalled VCB and our Integration Module (TSM 5.4). I reinstalled everything. The edited the config.js file so everything was the same then compared it to the VCB server that was working. But still no backups.
I manually enter "pre-command <jobname> FQDN.server. The snapshot is created for the VM but is immediately removed. The vmware-vmount.log file has this in it:
"Error: (vmountDriverSupport:473) Last Error: 0x103
"Error: vmountDevice:1481)Cannot open virtual storage driver. Make sure it is running"
I'm stumped.
Any ideas? I've checked the LUNs and they appear OK on the Windows server. The SAN is an IBM DS4000 with some FC datastores and SATA datastores.
