VCBMounter Host Connection Error

[AustinPowers]

Running VCBMounter command from my proxy:

vcbmounter -h xx.x.x.xxx -u uname -p pword -a ipaddr:xxx.x.x.xxx -r f:\backups\test -m san -L 6

returns 692 error:

2009-01-16 08:12:52.728 'vcbMounter' 692 error Error: Could not connect to ESX host xxxx.xxx.xxx: Cannot connect to

host xxxx.xxx.xxx: A connection attempt failed because the connected party did not properly respond after a period of

time, or established connection failed because connected host has failed to respond

Username and password work when connecting VC client to VC database. After that, VC's preexisting authenticated connection to the host is used to access the VM for vcbmounter, right?

And I can ping from the host to VC by name or address on the service console subnet.

So why isn't the host responding to the request to access the VM?

[kjb007]

Are you using a limited access account, or an admin account to connect to the ESX host? If limited, does the account have vmware consolidated backup user role?

-KjB

[AustinPowers]

I'm using an admin acount to connect to VC. My understanding is that VC uses its own authentication to connect to the host.

[kjb007]

That is correct, vc will talk to ESX on its own. Can you see the ESX LUNs on your proxy server?

-KjB

[AustinPowers]

That's a good question. How might I check that?

[kjb007 · Accepted solution]

Go to disk management and see if there are disks visible there. Rescan disks just to be sure. If you don't see disks there, they will not be readable, nor should they have drive letters associated.

-KjB

[AustinPowers]

Took me a few days to get back onsite to continue troubleshooting.

Proxy did not have access to the VMFS datastore on the SAN. Got that resolved, Proxy now sees it as a 1TB unknown partition. Run vcbmounter command, it returns:

Establishing NFC connection to host xxxx.xxx.xxx on port 902, service vxa-nfc, SSL %s

Error: Could not connect to xxxx.xxx.xxx: Cannot connect to host xxxx.xxx.xxx: A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond

Any ideas?

[kjb007]

Here's a quick cheat sheet for vcb. See if you've done everything here. http://communities.vmware.com/docs/DOC-2770

-KjB

[AustinPowers]

I went back and completely reconfigured my Proxy connections to the VMFS & NTFS volumes on the SAN. Viola! Good to go. Thanks for your help.