VCB error during pre-command

[MarkOne]

Hi to all,

I'm having a problem on Backup of one Virtual Machine using VCB and TSM.

During pre-command I have this messages:

\[2007-09-04 01:54:51.085 'App' 4612 info] Current working directory: C:\Program Files\tivoli\tsm\baclient

\[2007-09-04 01:54:51.819 'BaseLibs' 5148 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB/VIRTUAL_WINDOWS_DB.vmx":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB/VIRTUAL_WINDOWS_DB.nvram":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware-7.log":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware-8.log":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware-9.log":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware-4.log":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware-6.log":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware-5.log":

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

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

Copying "\[SANvolume0] VIRTUAL_WINDOWS_DB//vmware.log":

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

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

\[2007-09-04 01:55:04.726 'BaseLibs' 6632 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2007-09-04 01:58:25.728 'BlockList' 4612 error] Host is unreachable.

\[2007-09-04 01:58:25.744 'BlockList' 4612 warning] Could not log out (VIRTUAL_CENTER1:902:fsvcbuser)

\[2007-09-04 01:58:25.759 'vcbMounter' 4612 error] Error: Failed to open the disk: Unspecified error

\[2007-09-04 01:58:25.759 'vcbMounter' 4612 error] An error occured, cleaning up...

\[2007-09-04 01:58:26.181 'vcbMounter' 4612 warning] Snapshot deletion failed. Attempting to clean up snapshot database...

failed to prepare Virtual_Windows_DB for backup, PrepareForBackup() returned error 1

External command failed. See error above.

Exit Code: 1

Can you help me on understanding why I have this message only on this Virtual machine?

Many Thanks

[Mayur_Patel]

Turn up logging (use -L 6) and see which host it is trying to reach. I have a situation where VCB is trying to contact the wrong host for the VM that is being VCB'd.

[MarkOne]

I'm sorry but where and how can I turn up logging?

[MarkOne]

I'm giving this command:

C:\Program Files\VMware\VMware Consolidated Backup Framework>vcbMounter.exe -h

Why??

[Mayur_Patel]

in the -a option, you have to enter "ipaddr", on the actual IP address. Your command should be:

vcbMounter.exe -h c:\FNT_mount.log

[MarkOne]

With your indication, Today I've mounted manually VM on my Proxy Backup Server.

Now I have another problem: after mounting was finished files disappeared immediately and i can't make full backup of the VM.

Errors are below reported:

\[2007-09-05 13:12:55.369 'vcbMounter' 5532 info] Disk export complete

\[2007-09-05 13:12:57.041 'vcbMounter' 5532 warning] Snapshot deletion failed. Attempting to clean up snapshot database...

\[2007-09-05 13:12:57.275 'vcbMounter' 5532 info] Scanning snapshot Consolidate Helper

\[2007-09-05 13:12:57.275 'vcbMounter' 5532 info] Found match: /vmfs/volumes/451d4b7b-d0845410-4ae8-00145e1b58fa/VIRTUALMACHINE/VIRTUALMACHINE.vmx-snapshot-42

\[2007-09-05 13:13:08.807 'vcbMounter' 5532 error] Error: Snapshot remove failed: Unable to access a file since it is locked.

\[2007-09-05 13:13:08.807 'vcbMounter' 5532 error] An error occured, cleaning up...

\[2007-09-05 13:13:09.682 'App' 5532 verbose] ============BEGIN FAILED METHOD CALL DUMP============

\[2007-09-05 13:13:09.682 'App' 5532 verbose] Invoking \[remove] on \[vim.vm.Snapshot:/vmfs/volumes/451d4b7b-d0845410-4ae8-00145e1b58fa/VIRTUALMACHINE/VIRTUALMACHINE.vmx-snapshot-43]

\[2007-09-05 13:13:09.682 'App' 5532 verbose] Arg removeChildren:

false

\[2007-09-05 13:13:09.682 'App' 5532 verbose] Fault Msg: "The request refers to an object that no longer exists or has never existed."

\[2007-09-05 13:13:09.682 'App' 5532 verbose] =============END FAILED METHOD CALL DUMP=============

\[2007-09-05 13:13:09.697 'vcbMounter' 5532 warning] Snapshot deletion failed. Attempting to clean up snapshot database...

\[2007-09-05 13:13:09.713 'vcbMounter' 5532 info] Scanning snapshot Consolidate Helper

\[2007-09-05 13:13:09.713 'vcbMounter' 5532 info] Found match: /vmfs/volumes/451d4b7b-d0845410-4ae8-00145e1b58fa/VIRTUALMACHINE/VIRTUALMACHINE.vmx-snapshot-44

\[2007-09-05 13:13:11.401 'App' 5532 verbose] Got vmdb error -14 (Pipe connection has been broken) when invoking \[logout] on \[vim.SessionManager:ha-sessionmgr]

\[2007-09-05 13:13:11.401 'vcbMounter' 5532 info] Error on logout (ignored): vmodl.fault.HostNotReachable

\[2007-09-05 13:13:11.401 'vcbMounter' 5532 verbose] Shutting down VMDB service...

\[2007-09-05 13:13:11.401 'vcbMounter' 5532 verbose] Unregistering callback...

\[2007-09-05 13:13:11.401 'vcbMounter' 5532 verbose] ...done

But I look that there are not problem on VM configuration.

It has 2 disks on the same LUN.

Can you halp ME?

[kix1979 · Accepted solution]

Do the VMDKs have the same name or are there snapshots open on the VM? If so you need to fix those issues first.

[MarkOne]

So.

I see an error on configuration of my VM.

On Settings (by Virtual Center and Web Access) I see that all disks (2) are in the same LUN (SANvolume0).

When I browse with putty I see that 1 disk is located on SANvolume0 and 1 disk on SANvolume1.

Is for this problem that i can't remove snapshot?

Why visualization is wrong?

[kix1979]

If they are named the same thing and the snapshot is open, you will need to power off the VM to commit the snapshot. After that you need to rename one to something like VMDK_1.vmdk or such. That should fix the issue. As for the GUI, who knows... it has issues at times like this.

[Mayur_Patel]

I may be wrong, but VCB might have a problem if a VM has virtual disks on 2 different LUNs.

Can any one verify that? If that is the case, can you move all of the virtual disks to one directory (also rename them inthe process)

[MarkOne]

Thanks to all of you.