Skip to main content

VCB with NTBackup

VCB (VMWare Consolidate Backup) Framework is backup proxy. VCB is NOT Backup software. It acts as a relay agent between the Virtual Machine and backup software. Generally, VCB would be installed as part of vCenter OR it can be installed on any standalone system as well.

VCB comprehensive software of Backup, Snapshot and mounting the virtual disk.



Download the VCB Framework from www.vmware.com download portal. Install it on a Windows XP system.

It install under the following path:

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

Before take backup of the VMs, its virtual disk has to be mounted with our local system.

Enter following command in Command prompt to mount the Virtual Disk:


vcbmounter -h 172.17.42.55 -u -p -a name: -t file -r C:\VCC001 -m nbd

where as

-h can either ESX Host OR vCenter Server

-u Username

-p Password

-a VM parameters (name: enter VM name as per the inventory)

-t Fileflavor

-r Mount point

-m mode

After run this command, you will folder called VCC001 on C Drive of local disk, open the VCC001 folder, you will see “C” drive of the VM as shown in the picture:





To UNMOUNT
It is necessary to unmount the mounted Virtual disk after backup done.
vcbmounter -h virtualcenter.domain.com -u username -p password -U c:\mnt\nameofthevm

Although NTBackup is unsupported for use with VCB, because it has no pre- and post-scripts, you can however use a batch file to mount the VMs, start NTBackup and Unmount those VMs.

@ECHO OFF
SET VCBFW="C:\Program Files\VMware\VMware Consolidated Backup Framework"
%VCBFW%\vcbmounter -h virtualcenter.domain.com -u username -p password -a name:%1 -t file -r c:\mnt\%1 -m nbd
ntbackup backup c:\mnt\%1\letters\c /j "%1 C-disk" /f "c:\ntbackup\%1.bkf" /snap:off /m normal
%VCBFW%\vcbmounter -h virtualcenter.domain.com -u username -p password -U c:\mnt\%1


Use Task Scheduler to schedule the backup using this batch file.

VCB with NTBackup is simple and costless solution for small enterprises and non-mission critical systems.

Some Pros and Cons:

1. NTBackup thru Windows XP NOT allow us to select any specified folder to be backedup

2. NTBackup thru Windows 2003 allows us to take backup of any specified folder

3. The mounted Virtual Disk is READBLE ONLY

4. We need to manually schedule the backup jobs thru “Scheduled Tasks”

5. It can be security breach, if someone knows the username and password, they can easily use the VCB to mount the Virtual Disk and steal the data

6. We can’t do incremental and differential backup as the mounted virtual disk is read-only and NTBackup can’t set the archive bit.

7. VCB using Port 443

8. After unmount the virtual disk thru command, sometimes, its not removing the snapshots and delta disks from the particular Virtual Machine. Therefore, it not allows us to mount the same Virtual Disk again. Therefore, we used the following commands to remove the snapshots:

# vmware-cmd /vmfs// hassnapshot

If it return as 1, snapshot existing

# vmware-cmd /vmfs// removesnapshots

It should return null.

WARNING: Using this method to remove the snapshots may remove the other snapshots which are needed critically.

Comments

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires. We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software. This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment. When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console. Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager Creating DSN Create a System DSN f

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only. Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address) ~ # /ipmitool lan set 1 vlan id 333 ~ # /ipmitool lan print1 Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : 255.255.254.0 MAC

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called " vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format. If you don’t have a VMotion/SVMotion license, use the following command to achieve the same. From Thick to Thin: vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk" It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store. Use the following command to see real-time usage of thin disk: du –h "Thindisk.vmdk" You can notice the big difference of disk usage between of Thin and Thick format disks. From Thin to Thick: vmkfstools –i "Thindisk.vmdk" -d zeroedthick "T