The vCenter VM is on local storage for one of the servers. The vcb proxy and target VM (I'm trying to do a snapshot) are on the same (DeployVMs) iSCSI LUN (my iSCSI is the software target available with Fedora). Here is the command I am using:

vcbMounter -h 192.168.1.3 -u Administrator -p secret -a name:P1TAVM3.Web -r e:\Backups\P1TAVM3.Web -t file -L 6

The VM exists and is running. I can see from the internal log messages that it is able to log into the machine and actually does some things before it throws the following error:

2009-10-03 13:12:41.612 'vcbMounter' 1952 error] Error: Cannot open disk blklst://snapshot-69DeployVMs P1TAVM3.Web/P1TAVM3.Web.vmdk@192.168.1.3?xxxx/xxxx. Cannot open disk file: Error : Disk library failed (Cannot access a SAN/iSCSI LUN backing this virtual disk. (Hint: If you are using vcbMounter you can use the option "-m ndb" to switch to network based disk access if this is what you want.) If you were attempting file-level access, stop the vmount Service by typing "net stop vmount2" on a command prompt to force vmount to re-scan for SAN LUNs and re-try the command.). Unable to open 'blklst://snapshot-69DeployVMs P1TAVM3.Web/P1TAVM3.Web.vmdk@192.168.1.3'. Failed to configure disk scsi0:0.

After the error, vcbmounter cleans up the work it's already done.

I can take a snapshot without a problem using vCenter's graphic interface. It's the command line from the vcb proxy that's giving me fits.

I am not using DNS so you can see the internal LAN address for my virtualized vCenter machine.

I could not match the LVID with any of the LVIDs on either ESX server so I can't figure out what path it's looking for. I went into the ESX servers and did an "ll" in the /vmfs/volumes directories to get the LVIDs know to the servers.

I do not have multipath. The vcb and VM in question are on the same iSCSI target. I tried the 'net stop vmount2' trick suggested in several postings and the error msg. That had no effect. "-m ndb", with my other operands, throws a syntax error on the command. I walked through one site which was said to be some sort of debugging information but in general it gave you no clue about what was happening if any of the steps failed!

Up until now I've not had any particular problems getting labs to run in either the install or the deploy classes but this one stumps me and I don't see any VMware documentation that shows the error messages and either breaks them down so I can figure out what it's looking for, or gives any guidance on how to resolve the issue.