Video Screencast Help
Backup and Recovery Community Blog

VCB (VMware Consolidated Backup)

Created: 12 Jun 2009 • 6 comments
GFK's picture
+1 1 Vote
Login to vote

Protecting the VMware environment has its own unique set of data protection challenges. There are basically three ways to protect VMware: the guest OS method, the console backup method and the VMware Consolidated Backup (VCB) method. The guest OS method treats each virtual machine as a standalone server and backups take place as usual as if the virtual is physical server. The second practice is the console backup practice, in which virtualisation administrators back up the VMware ESX Server with no regard of the underlying virtual machines in the ESX environment. (There is a “free” product, ESXi, but it has no console, and requires add-ons to manage.)

VCB Backup requires VMware Infrastructure 3 (VI3) and initially SAN attached disk (iSCSI or Fibre Chanel) but now supports VMFS with local, JBOD, iSCSI and Fibre-Channel-attached disk, network file system (NFS) and virtual compatibility mode raw device mapping (RDM). The only mode not currently supported is physical compatibility mode RDM, together with a dedicated Windows Server 2003 acts as the backup proxy. You then install the VCB software on the Windows Server and provide access to the same SAN Logical Unit Number (LUN) used for the VMware Virtual Disk Files.

The Symantec Backup Exec 12.5 Agent for VMware Virtual Infrastructure (AVVI) is specifically related to the VMware Consolidated Backup framework and is designed and built to communicate directly with VMware ESX and VirtualCenter.VCB was originally introduced in 2006 as nothing more than a collection of interfaces and utilities that backup vendors could exploit. Since then VCB itself and backup vendor support has expanded considerably. The many different code levels for both VCB and backup applications have caused considerable confusion around what environments are supported and what VCB is today.

It is best to think of VCB as a backup framework with a collection of VMware utilities that facilitates backups. Today VCB utilises standard backup products together with snapshot capabilities. It uses command line interface (CLI) capabilities in VMware to take a VM snapshot of Windows-based VMs to offload a copy of the data for the backup product which Backup Exec then mounts and backs up.

Effectively, VCB provides a centralised backup facility that enables you to use Backup Exec to protect system, application, and user data in your virtual machines while reducing the load on virtualised servers. This allows you to backup your virtual machines without disrupting users and applications. So, VCB provides a way to do server-free and LAN-free backup and VM snapshots can be NFS mounted for quicker recovery and GRT as well as centrally manage backups to simplify management of IT resources.

Cool so far?

If you are not using VCB you do not need the BE 12.5 AVVI. Most organisations not using VCB are likely to be using ESXi. Although ESXi is free, there is no service console anymore. So you can’t use local agents on your ESXi host. Everything needs to be able to communicate with the VI API or any other remote connect method to gather information – not so cool.

So, the bottom line is AVVI is only needed when there is a VCB framework around the Virtual infrastructure.

VMware’s Virtual Infrastructure 3 (VI3) family includes: VMware ESX, VirtualCenter, VCB, VMware Converter & VMotion. Backup Exec 12.5’s Agent for VMware Virtual Infrastructure (AVVI) can leverage all of these components of VMware VI3 to automatically discover, protect, and recover virtual machines and their data. All Guest virtual machines (VM’s) hosted by V3I, including Windows and Linux virtual machines, can be protected using Backup Exec’s AVVI integrated support of VCB.

Comments 6 CommentsJump to latest comment

dododo..'s picture

One of attracted reasons of VCB and NBU backup proxy is the backup traffic going through fiber. But I don't know why all my VM backups using LAN instead of FC? (I did specify the terasfer type to 0-san).

Is there any resaon you can think of?

Thank you.

0
Login to vote
Stuart Green's picture

https://www-secure.symantec.com/connect/forums/vmw...

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

0
Login to vote
Symanticus's picture

Hi All,

Does (Storage) VMotion feature uses the same underlying technology as VCB too ?

/* Infrastructure Support Engineer */

+1
Login to vote
Stuart Green's picture

According to the 6 steps of the storage vmotion process it does use snapshots, which is how you are able to get a backup of a VM using VCB also via snapshots.

VMware Storage VMotion consists of six steps outlined below:

Step 1. Copy virtual machine home directory to new location. This step uses NFC copier to copy the files over to the new location

Step 2. Self-VMotion to new virtual machine home. A self-VMotion uses the same process as a normal VMotion operation. This step enables the use of the new swap file and reopen other copied files such as the virtual machine config file and other such files.

Step 3. Take a disk-only snapshot. This creates a child disk which will now be used to maintain ALL changes being made to the Virtual Machine data.

Step 4. Copy virtual machine disk to destination (read-only).

Step 5. Consolidate child disk created in step 4 into copied disk.

Step 6. Delete original virtual machine home and disks and enable read/write on new copied disk

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

+1
Login to vote
Symanticus's picture

Hi All,

Thanks for all of your suggestion, here's what I've done to make the VM backup possible:

1. Uninstalling the existing VMWare tools (previously i performed COMPLETE install)
2. Restart the VM
3. Install VMWare tools without the VSS support.
4. restart the VM
5. make sure the Microsoft VSS manager and VSS writer services both enabled - automatic.

by then i execute the following command line to perform the backup from the backup proxy server cmd prompt and surprisingly it was success !

vcbmounter -h ESXServer01 -u root -p password -a ipaddr:<TargetWindows2003VM> -r \\DLINKDNS323-SAN01\Volume_1\Test -L 6 -m nbd

i also tried to backup through Symantec Backup Exec 12.5 with the same parameter and it was success as well.

but there is still one question remains, that is if i do have SQL Server 2005 or any VSS-aware application, would this VM is still be safe to backup without installing the VSS support ?

I wonder how do people do people do in backing up their VSS-aware application VM on Windows Server 2003 VM.

/* Infrastructure Support Engineer */

+1
Login to vote
Symanticus's picture

Hi All,

I've tried to performs backup of my VM recently and then somehow it failed with the following error:

Completed status: Failed
Final error: 0xe000fe3c - Before you can back up this resource, you must purchase and install a license key for the appropriate Backup Exec agent. See the job log for details.
Final error category: Security Errors

For additional information regarding this error refer to link V-79-57344-65084

i thought only the GRT options with the AVVI that needs a license :-|
I'm ok for my backup to be like the  .BKF file as oppose to use AVVI which can give us the full VMWare directory structure .VMX and .VMDK as long as it is free.

can anyone clarify this matter please ?

/* Infrastructure Support Engineer */

+1
Login to vote