VMware Cloud Community
jpjeffery
Contributor
Contributor

VCBMounter errors

We have a batch file which runs every night to backup some virtual machines.

Here's an example of one of the lines:

vcbmounter -h vcs01 -u administrator -p password -a ipaddr:server01 -r e:\VCBBackups\server01 -t fullvm -m san -M 1

The errors/warnings from the log file are:

SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vcs01

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 not time valid*

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

The command then copies the files:

Copying "[TestLun1] server01/server01.vmx":

  • 0%=====================50%=====================100%*

  • ***************************************************

Copying "[TestLun1] server01/server01.nvram":

  • 0%=====================50%=====================100%*

  • ***************************************************

Copying "[TestLun1] server01//vmware-31.log":

  • 0%=====================50%=====================100%*

  • ***************************************************

Further errors/warnings occur and the job rolls back:

SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vcs01

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 not time valid*

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

SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vcs01

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 not time valid*

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

No path to device LVID:48108681-93ac1e7b-a944-001e0b7170ba/48108681-597158d9-d5f8-001e0b7170ba/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:\VCBBackups\server01

I've had no luck finding out anything about those errors in the Knowledge Base (I find it bizarre when vendors don't freely document their own error codes!) so I'm turning to the community for help. I see the suggestion from the errors of running "net stop vmount2" but found that this service is already stopped. I'll be rebooting the server after applying Windows Updates (as the server has been up and running continuously for 193 days) which just might make this question redundant..but I've typed it now!

Jeff

London

Tags (1)
0 Kudos
12 Replies
AndreTheGiant
Immortal
Immortal

If you use net mode (-m ndb) instead of san mode, does it works?

If yes, it's a problem with your SAN configuration, and you must check that the VCB server can "see" the same VMFS LUN of the ESXs.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
jpjeffery
Contributor
Contributor

Anybody - Well, the reboot of the server has restored the functionality of the stopped service but the script still failed (same errors).

Andre - What's the difference between net mode and san mode? are there any implications to making such a change? Also, how would I check that the VCB server can see the same VMFS LUN of the ESXs?

0 Kudos
AndreTheGiant
Immortal
Immortal

What's the difference between net mode and san mode?

In SAN mode the VCB proxy must see (under disk management) the ESX LUNs.

With NET mode you work though the normal network.

See also:

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
jpjeffery
Contributor
Contributor

In SAN mode the VCB proxy must see (under disk management) the ESX LUNs.

</div>

Interesting. Under Windows Disk Management? Well, they're not there, all I can see is the local C: and E: drives (and the 😧 CD-ROM drive).

0 Kudos
jpjeffery
Contributor
Contributor

OK, well nbd has worked. Looking at the back of the VCB server there are no fibre cables attached which I'm assuming are what would provide the ability for Disk Management to see the LUNs. In the absence of that I guess we're going to have to go with the network based connectivity in the meantime.

Please confirm if I'm right or wrong about the fibre cables! :smileyblush:

0 Kudos
AndreTheGiant
Immortal
Immortal

If your storage is FC you need at least one fibre pain, the correct switch zoning and the correct storage masking.

Same for a new ESX node in your cluster.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
vDeepak
Enthusiast
Enthusiast

AM too facing the same issue and same error.

In my case i am getting error "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."

i can confirm that i can see the LUN from computer management from VCB server.

Plese suggest what could be the problem here?

0 Kudos
AndreTheGiant
Immortal
Immortal

If in net mode VCB works, than is still a problem on SAN configuration.

So first test in net mode.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
vDeepak
Enthusiast
Enthusiast

just checked and found that if i use -nmd and running the backup , then backup gets successfull.

here i have two questions:

1. while using switch -nbd i checked and found that all files are get backed up , only vmdk , -flat.vmdk , nvram , vmx and .log file sgets backes up. : please confirm is it in general thats supposed to be or there is something wrong.

2, as my backup is running fine with -nbd command and getting failed if i am using -san , and also i am able to look over LUN from by VCB server from computer management , so do you think so that still there is some issue with LUN availability?

0 Kudos
AndreTheGiant
Immortal
Immortal

1. All files are fine.

Note that you got multiple file for each vmdk, but this is VCB behavior

2. Yes.

If in net mode VCB works and in san mode no, than is still a SAN issues (in your case seems that zoning and masking are fine).

But there can be also other problem, like multipath, HBA drivers, and so on...

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
vDeepak
Enthusiast
Enthusiast

1. fine

2. ok, please let me know , step by step what needs to be checked to fix the issue if its storage issue.

please elaborate the process.

0 Kudos
AndreTheGiant
Immortal
Immortal

The second point it not so simple Smiley Happy

Ask your storage vendor or consultant.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos