VMware Cloud Community
sfhsfredj
Contributor
Contributor

vcb 1.5 / ESX 3.5 U2

My apologies if this is not the right forum...I saw some questions regarding VCB here, please move to appropriate forum if incorrect. :smileyshocked:

========================================================================================================

I am testing vcb 1.5 to backup my test box for one our core apps. I am running ESX 3.5 U2. The test vm box is running

Windows 2003 R2 with two virual drives ( 25GB and 50GB / Independent drive mode is unchecked). MY VCB proxy box

is also running windows 2003 R2.

Here is the syntax of my backup:

vcbMounter -h sfhsesx1.mydomain.net -u root -p ******** -m nbd -a name:MISYSTST1 -r d:\VMbackup\MISYSTST1 -t fullvm

Here's portion of the output from the backup command executed above.

C:\PROGRA1\VMware\VMWARE1>echo on

C:\PROGRA1\VMware\VMWARE1>vcbMounter -h sfhsesx1.mydomain.net -u root -p ********

x -m nbd -a name:MISYSTST1 -r d:\VMbackup\MISYSTST1 -t fullvm

Current working directory: C:\PROGRA~1

\VMware\VMWARE~1

HOSTINFO: Seeing Intel CPU, numCo

resPerCPU 1 numThreadsPerCore 2.

HOSTINFO: This machine has 2 phys

ical CPUS, 2 total cores, and 4 logical CPUs.

Using system libcrypto, version 9

0709F

SSLVerifyCertAgainstSystemStor

e: Subject mismatch: esx1.local.com vs sfhsesx1.sfhshi.net

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

Copying "[esx1:storage1] MISYSLAB1/MISYSLAB1.vmx":

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

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

Copying "[esx1:storage1] MISYSLAB1/MISYSLAB1.nvram":

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

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

Copying "[esx1:storage1] MISYSLAB1/vmware-7.log":

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

My question is since I have only two virtual drives why are there so many vmdk files?

This is only a portion of the list, backup is still running?

Directory of D:\VMbackup\MISYSTST1

02/10/2009 10:30 AM <DIR> .

02/10/2009 10:30 AM <DIR> ..

02/10/2009 09:41 AM 1,039 catalog

02/10/2009 09:41 AM 8,684 MISYSLAB1.nvram

02/10/2009 09:41 AM 2,450 MISYSLAB1.vmx

02/10/2009 10:30 AM 2,142,568,448 scsi0-0-0-MISYSLAB1-s001.vmdk

02/10/2009 10:30 AM 1,092,419,584 scsi0-0-0-MISYSLAB1-s002.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s003.vmdk

02/10/2009 10:30 AM 1,812,267,008 scsi0-0-0-MISYSLAB1-s004.vmdk

02/10/2009 10:30 AM 1,267,793,920 scsi0-0-0-MISYSLAB1-s005.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s006.vmdk

02/10/2009 10:30 AM 1,376,256 scsi0-0-0-MISYSLAB1-s007.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s008.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s009.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s010.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s011.vmdk

02/10/2009 10:30 AM 327,680 scsi0-0-0-MISYSLAB1-s012.vmdk

02/10/2009 10:30 AM 458,752 scsi0-0-0-MISYSLAB1-s013.vmdk

02/10/2009 10:30 AM 1,029 scsi0-0-0-MISYSLAB1.vmdk

02/10/2009 10:30 AM 2,140,733,440 scsi0-1-0-MISYSLAB1_1-s001.vmdk

02/10/2009 10:30 AM 707,330,048 scsi0-1-0-MISYSLAB1_1-s002.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s003.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s004.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s005.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s006.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s007.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s008.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s009.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s010.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s011.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s012.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s013.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s014.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s015.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s016.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s017.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s018.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s019.vmdk

02/10/2009 10:30 AM 327,680 scsi0-1-0-MISYSLAB1_1-s020.vmdk

Tags (3)
Reply
0 Kudos
3 Replies
kjb007
Immortal
Immortal

The original vmdk file is being split into chunks, so as not to create one huge file which your filesystem may not support. This will typically be in 2 GB chunks, and will fill those slices up to how much disk is actually in use.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
sfhsfredj
Contributor
Contributor

Thanks KJB, just needed confirmation from folks how have actually done this. I tested a simple VM of XP workstation and use Converter 3.03 to restore and it worked. Is that common practice rather than using vcb backup restore CLI options?

Reply
0 Kudos
kjb007
Immortal
Immortal

Yes, converter is the easiest option. Using the CLI based tools requires additional work, which the converter will do for you automatically.

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos