Hi,
using a fresh ESX 3.5 setup I have a problem using VCB. I started vcbmounter manually and got the following log file:
Current working directory: C:\Program Files\VMware\VMware Consolidated Backup Framework
HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1.
HOSTINFO: This machine has 1 physical CPUS, 4 total cores, and 4 logical CPUs.
Connecting to host chi-nt-vc1.ads-storck.com on port 443 using protocol https
Using system libcrypto, version 90709F
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
Sending soap request to : retrieveContent
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs chi-nt-vc1.ads-storck.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Received soap response from : retrieveContent
Connected using API Namespace vim25.
Authenticating user rudolf-adm
Sending soap request to : login
Received soap response from : login
Sending soap request to : retrieveContent
Received soap response from : retrieveContent
Sending soap request to : findByIp
Received soap response from : findByIp
Sending soap request to : GetSummary
Received soap response from : GetSummary
Sending soap request to : GetSnapshot
No snapshot info for this VM, nothing to do.
Sending soap request to : createSnapshot
Received soap response from : createSnapshot
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Snapshot created, ID: snapshot-138
Mount operation created snapshot.
Sending soap request to : GetConfig
Received soap response from : GetConfig
Sending soap request to : GetLayout
Received soap response from : GetLayout
Found a device: vim.vm.device.VirtualDisk
Found a device: vim.vm.device.VirtualBusLogicController
Sending soap request to : GetConfig
Received soap response from : GetConfig
Mount operation obtained backup info.
Sending soap request to : GetConfig
Received soap response from : GetConfig
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetResourcePool
Received soap response from : GetResourcePool
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Received soap response from : GetParent
Sending soap request to : GetParent
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : GetRuntime
Received soap response from : GetRuntime
Sending soap request to : GetName
Received soap response from : GetName
Sending soap request to : retrieveInternalContent
Received soap response from : retrieveInternalContent
Sending soap request to : getVmFiles
Received soap response from : getVmFiles
Establishing NFC connection to host chi-lx-esx2.ads-storck.com on port 902, service vpxa-nfc
Copying "[LUN0] chi-nt-ws1/chi-nt-ws1.vmx":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1/chi-nt-ws1.nvram":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1//vmware-1.log":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1//vmware-2.log":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1//vmware-3.log":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1//vmware-4.log":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1//vmware-5.log":
0%=====================50%=====================100%
**************************************************
Copying "[LUN0] chi-nt-ws1//vmware.log":
0%=====================50%=====================100%
*************************************************
Filenames: blklst://snapshot-138[LUN0] chi-nt-ws1/chi-nt-ws1.vmdk@chi-nt-vc1.ads-storck.com?rudolf-adm/xxxx --> e:\mnt\test\scsi0-0-0-chi-nt-ws1.vmdk
Trying to open path
?\scsi#disk&ven_dell&prod_perc_6#i&rev_1.11#5&1270f7a2&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
Now using Path
?\scsi#disk&ven_dell&prod_perc_6#i&rev_1.11#5&1270f7a2&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
Reading 32256 bytes from offset 0.
Found 1 partition(s) on this device.
Trying to open path
?\scsi#disk&ven_dgc&prod_raid_5&rev_0220#5&e729187&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
Path
?\scsi#disk&ven_dgc&prod_raid_5&rev_0220#5&e729187&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} seems to be inactive, ignoring.
Could not scan for partitions on device. No VMFS names will be associated with this device.
Trying to open path
?\scsi#disk&ven_dgc&prod_raid_5&rev_0220#5&e729187&0&000001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
Now using Path
?\scsi#disk&ven_dgc&prod_raid_5&rev_0220#5&e729187&0&000001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
Reading 32256 bytes from offset 0.
Found 1 partition(s) on this device.
Obtained list of SCSI disk devices.
Establishing new connection for chi-nt-vc1.ads-storck.com:rudolf-adm
Connecting to host chi-nt-vc1.ads-storck.com on port 443 using protocol https
Sending soap request to : retrieveContent
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs chi-nt-vc1.ads-storck.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Received soap response from : retrieveContent
Connected using API Namespace vim25.
Authenticating user rudolf-adm
Sending soap request to : login
Received soap response from : login
Sending soap request to : retrieveInternalContent
Received soap response from : retrieveInternalContent
Sending soap request to : retrieveInternalContent
Received soap response from : retrieveInternalContent
Sending soap request to : GetConfig
Received soap response from : GetConfig
Sending soap request to : retrieveContent
Received soap response from : retrieveContent
Sending soap request to : findByUuid
Received soap response from : findByUuid
Sending soap request to : GetRuntime
Received soap response from : GetRuntime
Sending soap request to : GetSummary
Received soap response from : GetSummary
VM Hosted by VMware ESX Server, version 3.5.0
Sending soap request to : acquireLeaseExt
Received soap response from : acquireLeaseExt
Sending soap request to : renewAllLeases
SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs chi-nt-vc1.ads-storck.com
SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
The host name used for the connection does not match the subject name on the host certificate
A certificate in the host's chain is based on an untrusted root.
SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0
SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
Attempting to open LVID:491af706-543eb900-60dd-00221911de59/491af706-2588f691-2f96-00221911de59/1.
No path to device LVID:491af706-543eb900-60dd-00221911de59/491af706-2588f691-2f96-00221911de59/1 found.
Sending soap request to : release
Closing connection chi-nt-vc1.ads-storck.com:rudolf-adm
Sending soap request to : logout
Error: Failed to open the disk: 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.
An error occurred, cleaning up...
Sending soap request to : GetSummary
Received soap response from : GetSummary
Sending soap request to : remove
Received soap response from : remove
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Sending soap request to : GetInfo
Received soap response from : GetInfo
Deleted directory e:\mnt\test
Sending soap request to : logout
There seems to be some problem accessing the VMDK file, although the log files, VMX file etc is copied successfully. Could this be a problem with the VCB server and the ESX servers seeing the LUNs in a different way although the other files have been backed up ok?
Thanks in advance.
Regards,
Malte
It looks to me by looking at the log that you are using a Clariion. Try uninstalling powerpath. There are some issues with current versions. Also, run a vcbSanDbg and direct it to a text file. Make sure it can "see" all connections to the VMFS LUNs.
When you installed VCB, did it ask you to install the virtual disk driver? You may have a security policy set to ingnore unsigned drivers, this will cause an issue too.
Also, in the future, please attache the entire log file as an attachment, don't paste it into the thread, makes for messy reading after a while.
Dave
************************
The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents.
Nathaniel Borenstein
I have been told by our Dell suppliers that VCB does not support multipath software on the EMC san. Here is what he said
"VCB does not support multipaths or multipathing software, hence a single HBA dedicated to the LUNs visible on each of the CX3's SPs"
Maltic -
As long as you have enable read-write access to the disk and this is what you are seeing with vcbSanDbg, then try uninstalling the powerpath.
Paulplatypus -
Not 100% true ... Some versions of powerpath ARE supported and it seems that the HP and Microsoft versions of the MPIO drivers work as well.Check out this KB -> http://kb.vmware.com/kb/1007479 it tells you the supported versions.
Dave
************************
The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents.
Nathaniel Borenstein