I'm currently testing VCB backups (with HP Data Protector 6.0) and, after being hit with the "disks on multiple stores snapshot problem", I did some basic testing yesterday which allowed me to sucessfully & cleanly back up 3 single-disk VMs (in FILE mode).
Looking through the forums today I thought I found a way to get around the disks-on-multiple-stores issue (using the KB article to rename the disks on the second storage so that the .vmdk filenames aren't the same).
So, I've just removed, renamed & re-added the .vmdks to three guests and tried to run the preexec command I sucessfully used yesterday, but it's now failing to snapshot on \*all* guests!
I reduced the command down to one known-good vm (backed up yesterday) but it still fails.
Below is the (reduced) command I'm using - do the errors ring any bells with anyone? I searched the forums for the "988" error but didn't come up with anything:
(apologies for the poor wrapping, it's copied & pasted straight from a command prompt).
===================================================
C:\Program Files\OmniBack\bin>vmwarepreexec.cmd -a PLANNING01 -r c:\mnt -h esx2.
hbbc.loc -t file -m san
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Selected VM: PLANNING01
Starting: "C:\Program Files\VMware\VMware Consolidated Backup Framework
vcbvmna
me.exe" -h esx2.hbbc.loc -u root -p ******** -s any
Discovered VM: 'CIVICATEST' on server esx2.hbbc.loc
Discovered VM: 'DEV-VM1' on server esx2.hbbc.loc
Discovered VM: 'CIVICA01' on server esx2.hbbc.loc
Discovered VM: 'CIVICADB' on server esx2.hbbc.loc
Discovered VM: 'SAG01' on server esx2.hbbc.loc
Discovered VM: 'PLANNING01' on server esx2.hbbc.loc
Starting: "C:\Program Files\VMware\VMware Consolidated Backup Framework
vcbmoun
ter.exe" -h esx2.hbbc.loc -u root -p ******** -m san
\[2007-08-27 06:09:52.546 'App' 988 info] Current working directory: C:\P
rogram Files\OmniBack\bin
\[2007-08-27 06:09:53.000 'BaseLibs' 4044 warning] \[Vmdb_Unset] Unsetting
unknown path: /vmomi/
\[2007-08-27 06:09:56.750 'vcbMounter' 988 error] Error: Error while open
ing disk blklst:///vmfs/volumes/4672b0e9-37b3ee10-852a-0017a4770018/PLANNING01/P
LANNING01.vmx-snapshot-21\[VMFS_OS_01] PLANNING01/PLANNING01.vmdk@esx2.hbbc.loc?x
xxx/xxxx: A virtual disk could not be opened. -- Cannot open disk file: Error :
Unable to open 'blklst:///vmfs/volumes/4672b0e9-37b3ee10-852a-0017a4770018/PLANN
ING01/PLANNING01.vmx-snapshot-21\[VMFS_OS_01] PLANNING01/PLANNING01.vmdk@esx2.hbb
c.loc'. Failed to configure disk scsi0:0.
\[2007-08-27 06:09:56.750 'vcbMounter' 988 error] An error occured, clean
ing up...
Error VM :'PLANNING01' snapshot failed
C:\Program Files\OmniBack\bin>
Not a solution, but one of the most frustrating things surrounding VCB has always been why it suddenly breaks and for some reason why at times it suddenly starts to work..
Its mostly for this reason we use esxRanger to drive VCB..