VMware Cloud Community
admin
Immortal
Immortal

VCB Error - File-Level mounting

Hi ,

I am able to perform fullVM backup using -t fullVM, however when using -t file for file-level backup using the below cmd:

vcbMounter -h vc1 -u VCBOprs -p xxxxxx -a ipaddr:155.69.24.244 -r f:\mnt\2k3std32bit -t file

I encountered the below error:

2007-12-27 15:43:35.265 'vcbMounter' 3920 error Error: Error while opening dis

k blklst://snapshot-32911[SAN Storage 3] LEODEV04/LEODEV04.vmdk@vc1?xxxx/xxxx: A

virtual disk could not be opened. -- Cannot open disk file: Error : Unable to o

pen 'blklst://snapshot-32911[SAN Storage 3] LEODEV04/LEODEV04.vmdk@vc1'. Failed

to configure disk scsi0:0.

2007-12-27 15:43:35.265 'vcbMounter' 3920 error An error occurred, cleaning up

...

Any advice. Thanks

Irene

0 Kudos
4 Replies
dconvery
Champion
Champion

Did you unmount the FullVM command first? This will release the disk lease and delete the snapshot. Check to see if a snapshot still exists on the VM. Also, if you are running VCB1.1 and VIM2.5, make sure your VCBOprs user is defined at the datacenter AND at the Hosts&Clusters level. I don't know why, but I saw on a previous thread that this fixed issues.

http://communities.vmware.com/message/827025

Dave

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"
0 Kudos
admin
Immortal
Immortal

Hi,

Yes. The unmount command have been issued and snapshots removed.

Any other suggestions would be appreciated. Thanks!

Regards

0 Kudos
dconvery
Champion
Champion

Check the following:

dispart -> automount disable

dispart -> automount scrub.

LUN IDs match on esx hosts and VCB proxy

LATEST verison of VCB for version of ESX/VC that you are running

VC cannot run on VCB proxy - driver conflicts

finally...it is winders...reboot the proxy

Dave

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"
0 Kudos
admin
Immortal
Immortal

Hi Dave,

The error have been resolved, saw on some of the threads and advice customer to try a few approaches.

Just need to restart the vmount2 service and file level backup is resumed.

Thanks!

0 Kudos