VMware Cloud Community
copperjohan
Contributor
Contributor

Problems with VCBMounter

Hi Admins!!

I have a strange problem......

I cant backup some of my VMs vith VCB....

VCBmounter just hangs for 20 min or so....

C:\Program Files\VMware\VMware Consolidated Backup Framework>vcbMounter.exe -h 192.168.247.69 -u johan.ham -p password -a ipaddr:10.126.139.41 -r Z:\vs\VMNAME -t fullvm -m san -L 6

\[2007-04-19 14:08:04.828 'App' 4388 info] Current working directory: C:\Program Files\VMware\VMware Consolidated Backup Framework

\[2007-04-19 14:08:04.828 'vcbMounter' 4388 trivia] Initializing SSL context

\[2007-04-19 14:08:04.828 'BaseLibs' 4388 info] Using system libcrypto, version 90703F

\[2007-04-19 14:08:05.609 'App' 4388 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

\[2007-04-19 14:08:05.609 'vcbMounter' 4388 info] Connecting to host 192.168.247.69 on port 902

\[2007-04-19 14:08:05.843 'vcbMounter' 4388 verbose] Connected to stream: \[class Vmacore::Ssl::SSLStreamImpl:016E3970]

\[2007-04-19 14:08:05.843 'BaseLibs' 5100 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2007-04-19 14:08:05.890 'vcbMounter' 4388 info] Authenticating user johan.ham

\[2007-04-19 14:08:06.046 'vcbMounter' 4388 info] Logged in!

\[2007-04-19 14:08:06.046 'vcbMounter' 4388 info] Performing SearchIndex find.

\[2007-04-19 14:08:06.265 'vcbMounter' 4388 info] Attempting index search.

\[2007-04-19 14:08:06.265 'vcbMounter' 4388 info] Found VM using index search.

\[2007-04-19 14:08:06.265 'vcbMounter' 4388 info] Got VM MoRef

\[2007-04-19 14:08:06.953 'vcbMounter' 4388 info] Got access method

\[2007-04-19 14:08:06.953 'vcbMounter' 4388 info] Got coordinator object

\[2007-04-19 14:08:06.953 'vcbMounter' 4388 info] Attempting data access.

\[2007-04-19 14:08:07.140 'vcbMounter' 4388 info] Scanning snapshot Before SP2

\[2007-04-19 14:08:07.140 'vcbMounter' 4388 info] Creating snapshot

\[2007-04-19 14:08:11.734 'vcbMounter' 4388 info] Snapshot created, ID: snapshot-6251

\[2007-04-19 14:08:11.734 'vcbMounter' 4388 info] Mount operation created snapshot.

\[2007-04-19 14:08:11.781 'vcbMounter' 4388 verbose] Found a device: vim.vm.device.VirtualLsiLogicController

\[2007-04-19 14:08:11.781 'vcbMounter' 4388 verbose] Found a device: vim.vm.device.VirtualDisk

\[2007-04-19 14:08:11.781 'vcbMounter' 4388 verbose] Found a device: vim.vm.device.VirtualLsiLogicController

\[2007-04-19 14:08:11.781 'vcbMounter' 4388 verbose] Found a device: vim.vm.device.VirtualDisk

\[2007-04-19 14:08:11.812 'vcbMounter' 4388 info] Mount operation obtained backup info.

\[2007-04-19 14:08:11.812 'vcbMounter' 4388 info] Creating export directory

\[2007-04-19 14:08:11.828 'vcbMounter' 4388 info] Writing restore config file

\[2007-04-19 14:08:17.859 'vcbMounter' 4388 info] Exporting VM config files

Copying "\[SAN2-LUN4] VMNAME/VMNAME.vmx":

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

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

Copying "\[SAN2-LUN4] VMNAME/VMNAME.nvram":

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

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

Copying "\[SAN2-LUN4] VMNAME//vmware.log":

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

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

\[2007-04-19 14:08:18.171 'vcbMounter' 4388 info] Exporting disks

\[2007-04-19 14:08:18.171 'vcbMounter' 4388 info] Filenames: blklst://snapshot-6251\[SAN2-LUN4] VMNAME/VMNAME-000001.vmdk@192.168.247.69?johan.ham/password --> Z:\vs\VMNAME\scsi0-0-0-VMNAME.vmdk

\[2007-04-19 14:08:18.265 'BlockList' 4388 info] Establishing new connection for 192.168.247.69:johan.ham

\[2007-04-19 14:08:18.265 'blocklist' 4388 trivia] Initializing SSL context

\[2007-04-19 14:08:18.265 'blocklist' 4388 info] Connecting to host 192.168.247.69 on port 902

\[2007-04-19 14:08:18.484 'blocklist' 4388 verbose] Connected to stream: \[class Vmacore::Ssl::SSLStreamImpl:016F1830]

\[2007-04-19 14:08:18.484 'BaseLibs' 5488 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2007-04-19 14:08:18.531 'blocklist' 4388 info] Authenticating user johan.ham

\[2007-04-19 14:08:18.734 'blocklist' 4388 info] Logged in!

\[2007-04-19 14:34:21.796 'App' 4388 verbose] ============BEGIN FAILED METHOD CALL DUMP============

\[2007-04-19 14:34:21.796 'App' 4388 verbose] Invoking \[acquireLease] on \[vim.host.DiskManager:DiskManager]

\[2007-04-19 14:34:21.796 'App' 4388 verbose] Arg snapshot:

'vim.vm.Snapshot:snapshot-6251'

\[2007-04-19 14:34:21.796 'App' 4388 verbose] Arg diskPath:

"\[SAN2-LUN4] VMNAME/VMNAME-000001.vmdk"

\[2007-04-19 14:34:21.796 'App' 4388 verbose] Fault Msg: "Failed to communicate with the remote host, either due to network errors or because the host is not responding."

\[2007-04-19 14:34:21.796 'App' 4388 verbose] =============END FAILED METHOD CALL DUMP=============

\[2007-04-19 14:34:21.796 'BlockList' 4388 error] Host is unreachable.

\[2007-04-19 14:34:21.796 'BlockList' 4388 info] Closing connection 192.168.247.69:johan.ham

\[2007-04-19 14:34:21.812 'App' 4388 verbose] Got vmdb error -14 (Pipe connection has been broken) when invoking \[logout] on \[vim.SessionManager:SessionManager]

\[2007-04-19 14:34:21.812 'BlockList' 4388 warning] Could not log out (192.168.247.69:johan.ham)

\[2007-04-19 14:34:21.812 'App' 4388 verbose] Got vmdb error -14 (Pipe connection has been broken) when invoking \[logout] on \[vim.SessionManager:SessionManager]

\[2007-04-19 14:34:21.812 'blocklist' 4388 info] Error on logout (ignored): vmodl.fault.HostNotReachable

\[2007-04-19 14:34:21.812 'blocklist' 4388 verbose] Shutting down VMDB service...

\[2007-04-19 14:34:21.812 'blocklist' 4388 verbose] Unregistering callback...

\[2007-04-19 14:34:21.812 'blocklist' 4388 verbose] ...done

\[2007-04-19 14:34:21.812 'vcbMounter' 4388 error] Error: Failed to open the disk: Unspecified error

\[2007-04-19 14:34:21.812 'vcbMounter' 4388 error] An error occured, cleaning up...

\[2007-04-19 14:34:22.250 'vcbMounter' 4388 warning] Snapshot deletion failed. Attempting to clean up snapshot database...

\[2007-04-19 14:34:22.265 'vcbMounter' 4388 info] Scanning snapshot Before SP2

\[2007-04-19 14:34:22.265 'vcbMounter' 4388 info] Scanning snapshot \_VCB-BACKUP_

\[2007-04-19 14:34:22.265 'vcbMounter' 4388 info] Creating snapshot

\[2007-04-19 14:34:22.593 'App' 4388 verbose] Got vmdb error -14 (Pipe connection has been broken) when invoking \[logout] on \[vim.SessionManager:SessionManager]

\[2007-04-19 14:34:22.593 'vcbMounter' 4388 info] Error on logout (ignored): vmodl.fault.HostNotReachable

\[2007-04-19 14:34:22.593 'vcbMounter' 4388 verbose] Shutting down VMDB service...

\[2007-04-19 14:34:22.593 'vcbMounter' 4388 verbose] Unregistering callback...

\[2007-04-19 14:34:22.593 'vcbMounter' 4388 verbose] ...done

C:\Program Files\VMware\VMware Consolidated Backup Framework>

C:\Program Files\VMware\VMware Consolidated Backup Framework>

C:\Program Files\VMware\VMware Consolidated Backup Framework>

Any ideas?

Regards

Johan

0 Kudos
11 Replies
copperjohan
Contributor
Contributor

Arrrgggg Come on u Admins!!

Plz help a newbie!!!!

0 Kudos
beckmana
Enthusiast
Enthusiast

Hi,

is the VM ip address 10.126.139.41 reachable from the backup proxy server ? if not, the try uuid instead ipaddr.

Regards,

Andreas

0 Kudos
copperjohan
Contributor
Contributor

Hi,

The IP is reachable.

Copying "\[SAN2-LUN4] VMNAME/VMNAME.vmx":

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

\**************************************************

Copying "\[SAN2-LUN4] VMNAME/VMNAME.nvram":

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

\**************************************************

Copying "\[SAN2-LUN4] VMNAME//vmware.log":

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

\**************************************************

But the mounting of the vmdk files wont start!??

0 Kudos
admin
Immortal
Immortal

How many paths from your VCB server to your SAN volumes? VCB only supports a single path, if you have more than one you'll get errors.

0 Kudos
beckmana
Enthusiast
Enthusiast

With VMware Consolidated Backup 1.0.2

there is no need to disable path

VCB can now ignore any inactive paths to a SAN LUN. Previous releases of VCB required you to deactivate all inactive paths showing up on the VCB proxy or the backup process could fail. With VCB version 1.0.2, this step is no longer required. Please see http://kb.vmware.com/kb/2195414 for more information.

0 Kudos
admin
Immortal
Immortal

Didn't know that about VCB1.0.2, every day's a school day eh. Thanks for the info. Smiley Happy

0 Kudos
beckmana
Enthusiast
Enthusiast

Hi,

look for old snapshots

Regards,

Andreas

0 Kudos
copperjohan
Contributor
Contributor

Hi,

There is another snap-shot.

2007-04-19 14:08:07.140 'vcbMounter' 4388 info] Scanning snapshot Before SP2

\[2007-04-19 14:08:07.140 'vcbMounter' 4388 info] Creating snapshot

\[2007-04-19 14:08:11.734 'vcbMounter' 4388 info] Snapshot created, ID: snapshot-6251

\[2007-04-19 14:08:11.734 'vcbMounter' 4388 info] Mount operation created snapshot.

But could that be a problem??

regards

Johan

0 Kudos
beckmana
Enthusiast
Enthusiast

Hi,

only old VCB snapshots could be a problem.

are the vmware-tools of the VM up to date an running ?

Regards,

Andreas

0 Kudos
copperjohan
Contributor
Contributor

I dont like silence Smiley Sad

0 Kudos
copperjohan
Contributor
Contributor

Installed the latest VCB...Now it seems to work Smiley Happy

0 Kudos