VCB error

[GreenIT]

Hi,

I have set up a new proxy server for VCB backups. vcbMounter runs fine for "Ndb". Presented SAN luns to the proxy server but when I run the "SAN" backpus it fails.

Copying "[OS LUN] VDC-BlackBerry-x131/VDC-BlackBerry-x131.vmx":

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

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

Copying "[OS LUN] VDC-BlackBerry-x131/VDC-BlackBerry-x131.nvram":

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

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

Copying "[OS LUN] VDC-BlackBerry-x131//vmware-1.log":

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

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

Copying "[OS LUN] VDC-BlackBerry-x131//vmware-2.log":

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

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

Copying "[OS LUN] VDC-BlackBerry-x131//vmware.log":

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

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

Could not scan for partitions on de

vice. No VMFS names will be associated with this device.

Could not scan for partitions on de

vice. No VMFS names will be associated with this device.

Could not scan for partitions on de

vice. No VMFS names will be associated with this device.

SSLVerifyCertAgainstSystemStor

e: Subject mismatch: VMware vs virtualcenter.reisys.com

SSLVerifyCertAgainstSystemStor

e: The remote host certificate has these problems:

• The host name used for the connection does not match the subject name on the h

ost 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

SSLVerifyCertAgainstSystemStor

e: Certificate verification is disabled, so connection will proceed despite the

error

SSLVerifyCertAgainstSystemStor

e: Subject mismatch: VMware vs virtualcenter.reisys.com

SSLVerifyCertAgainstSystemStor

e: The remote host certificate has these problems:

• The host name used for the connection does not match the subject name on the h

ost 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

SSLVerifyCertAgainstSystemStor

e: Certificate verification is disabled, so connection will proceed despite the

error

No path to device LVID:49353a02-128a2

f80-0e94-001d097331da/49353a02-ded26c62-83c9-001d097331da/1 found.

Error: Failed to open the disk

: Cannot access a SAN/iSCSI LUN backing this virtual disk. (Hint: If you are usi

ng vcbMounter you can use the option "-m ndb" to switch to network based disk ac

cess if this is what you want.) If you were attempting file-level access, stop t

he vmount Service by typing "net stop vmount2" on a command prompt to force vmou

nt to re-scan for SAN LUNs and re-try the command.

An error occurred, cleaning up

...

Deleted directory d:\test1

Help is appreciated.

[AntonVZhbankov]

Does VCB proxy see presented LUN as disk?
---

VMware vExpert '2009

http://blog.vadmin.ru

[GreenIT]

Yes, screeshot attached.

[AntonVZhbankov]

As I see, VMFS partitions are unreadable.

---

VMware vExpert '2009

http://blog.vadmin.ru

[GreenIT]

So what could be the issue and how can I troubleshoot this?

[AntonVZhbankov]

Check drivers on VCB, mutipathing, array settings. That's an issue between Windows and SAN, completely unrelated to VCB.

---

VMware vExpert '2009

http://blog.vadmin.ru

[dconvery]

You may not have the Virtual Disk driver installed. Some GPO's prevent unsigned drivers from being installed. Also, you may be using an unsupported version of MPIO software only powerpath 5.0, 5.1 and 5.2 are supported. Try running the vcbSanDbg utility and piping it to a text file. Attach the file here if you need help.

Check out my post on VI:OPS for a better guide for installing VCB ->http://viops.vmware.com/home/docs/DOC-1392

Dave Convery

VMware vExpert 2009

http://www.dailyhypervisor.com

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

[GreenIT]

Thanks for your reply. The drivers installation seem to be fine. Also I am not running any multi pathing software. vcsSanDbg.txt is attached.

[dconvery]

Sorry for the delay...

The key error message is "No path to device LVID:49353a02-128a2f80-0e94-001d097331da/49353a02-ded26c62-83c9-001d097331da/1 found."

When you look at disk management, the VMFS LUNs should show up as "Unknown" and "Healthy". For some reason, yours are not. Sometimes just stopping the vmount2 service or rebooting the VCB proxy helps. If you believe that you are really running Powerpath 5.0, 5.1 or 5.2 then try uninstalling it to see if that corrects the issue.

Dave Convery

VMware vExpert 2009

http://www.dailyhypervisor.com

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

[dconvery]

I need to pay attention....

You said you do NOT have powerpath installed. If that is the case, then you do not have all paths present to the Clariion. You cannot single path an A?P array. Make sure you see four paths between the Clariion and the VCB server. It is also fine to install the supported versions of Powerpath.

Dave Convery

VMware vExpert 2009

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

[GreenIT]

Thanks a lot! Currently four paths are not set between the Clariion and the VCB server. Once I do it, the VCB should work . I would post the result soon.

Thanks again for your valuable input.

[dconvery]

Any Time

Dave Convery

VMware vExpert 2009

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"