VMware Cloud Community
fritz101
Contributor
Contributor

vcb cannot find lun

I'm trying to get VCB working and running into a problem where it can't find the SAN sotrage to mount the vm. Not sure if it has anything to do with the architecture, but all the ESX hosts are using Fiber Channel, whereas my VCB server is using iSCSI. I've verified that all the LUN's are visible in Windows Disk Manager (they show up as Online, Healthy (Unknown Partition))

Here is the command and output I'm trying to test with (minus all the SSL errors):

vcbmounter -h VC-SERVER -u VC-USER -t fullvm -r e:\mnt\VM-NAME -a uuid:5008414e-52f7-88e2-eaec-4707774fc3f5

Current working directory: C:\Program Files\VMware\VMware Consolidated Backup Framework

HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2.

HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 2 logical CPUs.

Using system libcrypto, version 90709F

Copying "[EMC-Vol5] VMNAME/VMNAME.vmx":

0%=====================50%=====================100%

**************************************************

Copying "[EMC-Vol5] VMNAME/VMNAME.nvram":

0%=====================50%=====================100%

**************************************************

Copying "[EMC-Vol5] VMNAME//vmware-1.log":

0%=====================50%=====================100%

**************************************************

Copying "[EMC-Vol5] VMNAME//vmware-2.log":

0%=====================50%=====================100%

**************************************************

Copying "[EMC-Vol5] VMNAME//vmware.log":

0%=====================50%=====================100%

**************************************************

Could not scan for partitions on device. No VMFS names will be associated with this device.

No path to device LVID:4982d274-f79431d1-d6bc-00170851e05a/4982d274-d93a5941-b904-00170851e05a/1 found.

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...

Deleted directory e:\mnt\VMNAME

So I ran a vcbSanDbg.exe to see what names the VCB machine sees. Although there are 5 SAN LUNs, it only gets names for these and throws a "No active paths found" for one of them

4624f801-60dce898-bb30-00170851

4624f813-5b550af6-a345-00170851

4624f821-c6f5d8c0-f3f1-00170851

497161aa-d8097510-0b94-00170851

Whats odd is that from the ESX server, the vmfs volume ID's are listed as:

4624f804-b050f8ba-2d66-00170851e05a

497161ca-6e4c5844-aef6-00170851e05a

4624f815-79269c27-ab43-00170851e05a

4982d279-6c99748b-e3f3-00170851e05a

4624f824-eab945a6-05b9-00170851e05a

49c1123f-c5345fb4-b4f2-00237d21ad02

Curious that they are simliar, some very close to what VCB sees, but different in length and not identical.

Any ideas?

Thanks!

frustrated & confused

Reply
0 Kudos
0 Replies