VCBMount cannot access SAN LUN's

[jdoz_bw]

I am starting to use VCB. My Proxy host is a Win2K3 R2 server. This proxy host can see all of the VMFS LUN's in my ESX environment. However, when attempting to do a VCBMount I am getting the following errors:

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

App 4292 Error: No path to device LVID 36474xxxxxx found. Blocklist 4292 Error.

vcbMounter 4292 Error: Failed to open the disk: Cannot access a SAN/iSCSI LUN backing this virtual disk.

How can I ensure everything is visible? The proxy host is setup in the same zone group on the SAN as the ESX hosts. I've rebooted the Proxyhost and re-scanned, etc...

Thanks

John

[dconvery]

John -

In case no one said it - welcome to the forums!

You can run vcbSanDbg. http://www.vmware.com/download/eula/vcbsdt_eula.html

Make sure that all RDMs that are in virtual mode are also presented to the proxy if you are backing up those VMs.

Dave

[kumarkv]

Hey

Check the following:

1. HBA Card of VCB Server is Zoned to the same Storage group as the ESX Server.

2. Disable Remote Storage Service in the Windows Server.

2. Have you disabled automount and automatic drive letter assignment as shown below?

To disable assignment of drive letters

1 Shut down the VCB proxy.

2 Disconnect the VCB proxy from the SAN or mask all the LUNs containing VMFS

volumes or RDMs.

3 Boot the proxy and log in as administrator.

4 Open a command‐line interface.

5 Run the Diskpart utility by typing:

diskpart

The Diskpart utility starts up and prints its own command prompt.

6 Disable automatic drive‐letter assignment to newly seen volumes by typing at the

Diskpart command prompt:

automount disable

7 Clean out entries of previously mounted volumes in the registry by typing at the

Diskpart command prompt:

automount scrub

8 Exit the Diskpart utility by typing:

exit

9 Shut down Windows.

10 Reconnect the VCB proxy to the SAN, or unmask all previously masked LUNs

containing either VMFS volumes or RDMs.

11 Boot the proxy

**********

Check and let me know

Thx

Kumar

[jdoz_bw]

Thanks.. Here is the output of the utility... Also note, I am running VCB version 1.10.64559, which supports Multipathing (EMC PowerPath in this case)

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

HOSTINFO: Seeing AMD CPU, numCoresPerCPU 1 numThreadsPerCore 1.

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

Building SCSI Device List...

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hp&prod_logical_volume&rev_2.76#5&3797ea60&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hp&prod_logical_volume&rev_2.76#5&3797ea60&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Found 1 partition(s) on this device.

Evaluating 4 paths.

Trying to open path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} seems to be inactive, ignoring.

Trying to open path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} seems to be inactive, ignoring.

Trying to open path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} seems to be inactive, ignoring.

Trying to open path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Path
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} seems to be inactive, ignoring.

No active paths found.

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

Dumping SCSI Device/LUN List.

**** Begin SCSI Device LIst ****

Found SCSI Device: NAA:600508b10018443953534a335a4b00054c4f47494341

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hp&prod_logical_volume&rev_2.76#5&3797ea60&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0 Target: 4 Lun: 0

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: NAA:5006016090208e815006016090208e814c554e5a2020

Visible on 4 paths:

Device Name:
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0 Target: 5 Lun: 0

Device Name:
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0 Target: 5 Lun: 0

Device Name:
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0 Target: 4 Lun: 0

Device Name:
?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0 Target: 4 Lun: 0

Lun does not contain any VMFS/LVM signatures.

**** End SCSI Device LIst ****

[dconvery]

It looks like you have the wrong LUN presented. This on does not contain a VMFS signature...

Dave

PS - if you are going to VMWorld, check out my breakout session on VCB - BC2497 VMware Consolidated Backup - Report from the Trenches

[jdoz_bw]

1. HBA card is zoned to the same storage (19 LUN"s)

2. RSM is disabled.

3. This is Win2003Advanced, so automatic drive lettering does not come into play.

[jdoz_bw]

On my EMC Clariion array I have this VCB proxyhost in the same storage group as my ESX hosts. I have confirmed that the Proxy host can see the same LUN set as the ESX hosts.

[dconvery]

Is it marked as write protected? You can't do that either. What type of storage is it and can you show the output of vcbSanDbg?

Dave

[dconvery]

Are there actually VMs on the LUNs presented to the proxy?

[jdoz_bw]

It is not write-protected. output of vcbSanDbg is above.

[jdoz_bw]

Yes, all of my VM's are on these LUN's. The command line vcbMounter that I am running detects the VM. It brings up the list of files to backup, then it fails saying "could not scan for partition or device. No VMFS names will be associated with this device."

[dconvery]

Sorry - our posts are crossing... Heres some things from the output:

2008-07-28 15:38:00.408 'App' 4200 trivia Evaluating 4 paths.

2008-07-28 15:38:00.408 'App' 4200 trivia Trying to

open path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

2008-07-28 15:38:00.408 'App' 4200 info Path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

seems to be inactive, ignoring.

2008-07-28 15:38:01.408 'App' 4200 trivia Trying to

open path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

2008-07-28 15:38:01.408 'App' 4200 info Path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

seems to be inactive, ignoring.

2008-07-28 15:38:02.408 'App' 4200 trivia Trying to

open path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

2008-07-28 15:38:02.408 'App' 4200 info Path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

seems to be inactive, ignoring.

2008-07-28 15:38:03.408 'App' 4200 trivia Trying to

open path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

2008-07-28 15:38:03.408 'App' 4200 info Path

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

seems to be inactive, ignoring.

2008-07-28 15:38:04.408 'App' 4200 info No active paths found.

The "DGC indiacates it is a Clariion (Data General Corp was the original manufacturer) NO ACTIVE PATHS

2008-07-28 15:38:04.408 'App' 4200 warning Could not scan for partitions on device. No VMFS names will be associated with this device.

2008-07-28 15:38:04.408 'App' 4200 error Dumping SCSI Device/LUN List.

2008-07-28 15:38:04.408 'App' 4200 info **** Begin SCSI Device LIst ****

2008-07-28 15:38:04.408 'App' 4200 info Found SCSI Device: NAA:600508b10018443953534a335a4b00054c4f47494341

2008-07-28 15:38:04.408 'App' 4200 info Visible on 1 paths:

2008-07-28 15:38:04.408 'App' 4200 info Device Name:

?\scsi#disk&ven_hp&prod_logical_volume&rev_2.76#5&3797ea60&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b},

Bus: 0 Target: 4 Lun: 0

2008-07-28 15:38:04.408 'App' 4200 info Lun does not contain any VMFS/LVM signatures.

This is an internal HP drive?

2008-07-28 15:38:04.408 'App' 4200 info Found SCSI Device: NAA:5006016090208e815006016090208e814c554e5a2020

2008-07-28 15:38:04.408 'App' 4200 info Visible on 4 paths:

2008-07-28 15:38:04.408 'App' 4200 info Device Name:

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b},

Bus: 0 Target: 5 Lun: 0

2008-07-28 15:38:04.408 'App' 4200 info Device Name:

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f355f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b},

Bus: 0 Target: 5 Lun: 0

2008-07-28 15:38:04.408 'App' 4200 info Device Name:

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f345f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b},

Bus: 0 Target: 4 Lun: 0

2008-07-28 15:38:04.408 'App' 4200 info Device Name:

?\mpio#disk&ven_dgc&prod_lunz&rev_0219#1&7f6ac24&0&305f325f345f30#{53f56307-b6bf-11d0-94f2-00a0c91efb8b},

Bus: 0 Target: 4 Lun: 0

2008-07-28 15:38:04.408 'App' 4200 info Lun does not contain any VMFS/LVM signatures.

Another Clariion LUN - NO VMFS...

[dconvery]

Something is up with the Clariion configuration. Check the LUN masking. Is it set up properly as a host within Navisphere?

[dconvery]

BTW...VCB 1.5 was released on Friday. You may want to use that version...

[dconvery]

I JUST remembered something...do you have driver signing set to "prompt"? You need top say yes to the VMware Mount Driver during VCB install. If you didn't get that prompt, that is your problem...

[dconvery]

Screenshot

[jdoz_bw]

I didn't get such a prompt when installing VCB. I will also check the Clariion configuration, it is entirely possible the LUN 's are not setup right, my SAN guy did those. I can visually see the setup in Navisphere and it appears that both the ESX hosts and the proxy have the same disk's. Stay tuned...

[jdoz_bw]

Attached is a screenshot of the Navisphere config for ESX Group 1. besxapXX are my ESX hosts, and bcvsap08 is my VCB server. If this helps..

Also, I just upgraded VCB to 1.5. Thanks

[jdoz_bw]

I have attached a screenshot of the Navisphere manager "ESX Group 1" storage group. bcvsap08 is the VCB server and besxap** are the ESX hosts.

Also I just installed VCB 1.5.. Thanks for the tip.

[jdoz_bw]

Attached is a screenshot of the Clariion setup. for "ESX GROUP 1" storage group.

Also I have just upgraded VCB to 1.5.