VCB Backup

[ofladung]

Hi All,

we use VCB without any problems, but a restore of a virtual machine creates many 2GB VMDK files instead of one (+ config files). We use the vmware converter to put the files together. Unfortunately the converter crashes if there are too many 2 GB files (300 GB virtual machine = 150 x 2 GB files). Because of that we're unable to restore big virtual machines. Would it be possible to change that? I know that the default for vcbmounter is -M 0, but I dont know how (and where) to change that.

Thanks!
Oliver

 

[a060463xyz]

I have a workarround for you :

Install the free "Unix Services foe Windows 3.5" (sfu3.5) on your vcb Backup-Proxy.
Share your export Directory e.g. F;\vcbmnt as a NFS-Share.
Mount the NFS-Share to the kernel of your esx server (you need a VMkernel Network to do so).
now you can use the vmaware command vcbRestore

I have a script template for this :

#The name of the VMs exportdirectory as a command line #parameter

VMname="$1"
cmd=/usr/sbin/vcbRestore
#vcenter=name of my VirtualCenterServer or esx Server
url=vcenter:443
user=administrator
pass=password
#the number in the last part of the path is the "guid" of the mounted nfs share and has to be changed for every installtion

base=/vmfs/volumes/7c8d13a1-3d955b3/

$cmd -h $url -u $user -p $pass -s "$base""$VMname

 

[ofladung]

Hi All,

our VMware Consultant found a solution which works very well. In the file "glue.js" on the backup server (it's a part of the vcb framework package) you will find the paragraph:

function AttachVMData(VMinfo, vmMoRef, createSnapshot, deleteSnapshot)

He changed the following part below the paragraph:

// set the transport mode (san/nbd)
cmd += "-M1 -m " + TRANSPORT_MODE + " ";

Now the vcbmounter creates a single file for every virtual hard drive.

Regards,
Oliver