virtualvizion

Welcome to virtualvizion Sign in | Join | Help
in Search

Large VM's fail with VCB

Last post 09-23-2008, 7:34 AM by kellino. 3 replies.
Sort Posts: Previous Next
  •  09-18-2008, 5:37 AM 10505

    Large VM's fail with VCB

    ...and the error is not clear to me at all. so I'm not sure where to begin.

    Here are the logs for 2 different VM's.  I removed all SSL/Certificate errors from the logs for easier reading:

    VM #1

    Backup Result: Error

    VM Name: xxxxxxxxx

    VM Current Host: xxxxxxxx

    Log: Preparing Disk Mode of Skipped Disks.

    Executing vRanger(VCB) Process.

    Status: Preparing to Launch VCB.

    Status: Vizioncore VCB Plug-in Version: 2.0.3.1

    Status: Vizioncore VCB Backup Started.

    Status: [2008-09-17 17:02:04.054 'App' 2228 info] Current working directory: C:\Program Files\vizioncore\esxRanger Professional\Plugins\Vcb

    Status: [2008-09-17 17:02:04.054 'BaseLibs' 2228 info] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

    Status: [2008-09-17 17:02:04.054 'BaseLibs' 2228 info] HOSTINFO: This machine has 2 physical CPUS, 4 total cores, and 4 logical CPUs.

    Status: [2008-09-17 17:02:04.522 'BaseLibs' 2228 info] Using system libcrypto, version 90709F

    Status: Deleted directory R:\vRanger\xxxxxxxx_20080917170145

    Status:

    Error: VCB Exit Code: 1

    Restoring Pre-Backup Disk Mode of Skipped Disks.

    Cleaning Up After Backup.

    Determining Backup Statistics.

    Writing Backup Information.

    Writing Backup Information to the Database.

    VM # 2

    Backup Result: Error

    VM Name: xxxxxxxx

    VM Current Host: xxxxxxxxxx

    Log: Preparing Disk Mode of Skipped Disks.

    Executing vRanger(VCB) Process.

    Status: Preparing to Launch VCB.

    Status: Vizioncore VCB Plug-in Version: 2.0.3.1

    Status: Vizioncore VCB Backup Started.

    Status: [2008-09-17 19:10:21.072 'App' 5624 info] Current working directory: C:\Program Files\vizioncore\esxRanger Professional\Plugins\Vcb

    Status: [2008-09-17 19:10:21.072 'BaseLibs' 5624 info] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

    Status: [2008-09-17 19:10:21.072 'BaseLibs' 5624 info] HOSTINFO: This machine has 2 physical CPUS, 4 total cores, and 4 logical CPUs.

    Status: [2008-09-17 19:10:21.588 'BaseLibs' 5624 info] Using system libcrypto, version 90709F

    Status: Deleted directory R:\vRanger\xxxxxxx_20080917191000

    Status:

    Error: VCB Exit Code: 1

    Restoring Pre-Backup Disk Mode of Skipped Disks.

    Cleaning Up After Backup.

    Determining Backup Statistics.

    Writing Backup Information.

    Writing Backup Information to the Database.

    We are NOT skipping any disks.  The vRanger command is configured to back up the entire Virtual Center environment except for a few servers which are skipped entirely.

    I also have another larger VM that failed with a blank log:

    Backup Result: Error

    VM Name: xxxxxxxxxxxxxxx

    VM Current Host: xxxxxxxxxxxx

    Log:

    That's all we got....a blank log.

    Where do we have to look to get more detail on why these jobs are failing?

    Thanks!

  •  09-19-2008, 9:41 AM 10516 in reply to 10505

    Re: Large VM's fail with VCB

    Open a cmd prompt and navigate to the VMware Consolidated Backup Framework directory.

    Are you able to run the following without any problems?

    vcbMounter -h <vchost> -u <user> -p <pw> -m san -a name<guest name> -r <windows path> -M 1 -F 1


    SK | Vizioncore Inc.
    975 Weiland Rd., Buffalo Grove, IL 60089 USA | www.vizioncore.com
    Phone (847) 589-2222 | Fax (847) 279-1868 |
  •  09-23-2008, 7:22 AM 10542 in reply to 10516

    Re: Large VM's fail with VCB

    I looked at the backups for the past 4 days.  Over 4 days, 7 different VM's failed, but only 2 of these failed on EACH attempt.

    I'm concerned about the "occasional failures" but for now I want to focus on those which fail consistently.

    I tried the command you gave on one of these VM's.  It hung for 5 minutes and gave no indication of progress.  I did a CTRL-C and it says "operation can not be cancelled".

    * A certificate in the host's chain is based on an untrusted root.
    [2008-09-23 13:23:41.961 'BaseLibs' 5588 warning] SSLVerifyIsEnabled: failed to
    read registry value. Assuming verification is disabled. LastError = 0
    [2008-09-23 13:23:41.961 'BaseLibs' 5588 warning] SSLVerifyCertAgainstSystemStor
    e: Certificate verification is disabled, so connection will proceed despite the
    error
    [2008-09-23 13:27:49.274 'App' 5340 error] Canceling, please wait...
    [2008-09-23 13:27:49.602 'vcbMounter' 5588 warning] Please wait. (The current op
    eration cannot be cancelled.)

  •  09-23-2008, 7:34 AM 10543 in reply to 10542

    Re: Large VM's fail with VCB

    UPDATE:

    I see a task to create a snapshot that is timing out in virtual center.  The inability to create a snapshot for these 2 VM's appears to be the issue.  I'll address myself and with VMWAre if necessary.  Thanks for the help.

View as RSS news feed in XML