ESx is pretty new at the office here and I'm just starting to look at VCB.
I setup a new server and installed VCB. I'm trying to backup a vm and copy the files locally and it's not working.. (see error below) The server running VCB is basically just a network connected server without any HBA's installed. I thought I could pull VM's across ethernet without having direct lun access. Can I not? The error I'm getting seems to tell me otherwise.. Any tips or tricks would be extremely helpful..
vcbMounter -h swvc01.swmed.org -u vcenter -p ******* -a uuid:503ea8ae-ec68-73c3-95b7-376de53e7abe -r D:\mnt\sw2kstat1 -t fullvm -m san
\[2007-03-07 11:29:54.371 'App' 3264 info] Current working directory: D:\Program Files\VMware\VMware
Consolidated Backup Framework
\[2007-03-07 11:29:54.871 'BaseLibs' 3700 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm/sw2kstat1 StatComm.vmx":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm/sw2kstat1 StatComm.nvram":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm//vmware-1.log":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm//vmware-2.log":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm//vmware-4.log":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm//vmware-3.log":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm//vmware-5.log":
0%=====================50%=====================100%
**************************************************
Copying "\[SWES30_SAN_LUN_0] sw2kstat1 StatComm//vmware.log":
0%=====================50%=====================100%
**************************************************
\[2007-03-07 11:30:07.714 'BaseLibs' 2244 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/
\[2007-03-07 11:30:08.589 'BlockList' 3264 warning] Could not log out (swvc01.swmed.org:vcenter)
\[2007-03-07 11:30:08.589 'vcbMounter' 3264 error] Error: Failed to open the disk: One LUN could not
be opened
\[2007-03-07 11:30:08.589 'vcbMounter' 3264 error] An error occured, cleaning up...
You have to have direct connection, aka an HBA, to your SAN for VCB to work.
Thats what I was thinking.
If I put hba's in this Windows Server how do I keep Windows from tagging each disk on the san and borking up my vm's?
VMware has some steps as part of the configuration to ensure that Windows does not write a disk signature to the disks. As long as you tell people NOT do to it after that you are fine. I have had VCB running since pre-beta and it's never harmed my LUNS.