Metadata
Title | Proven Practice: Integrating CommVault Galaxy 6.1 SP4 with VCB 1.1 Proxy Server |
Version | VMware 07/AUG/2008 1.0 Rodney Haywood (Rodos) 18/02/2009 1.1 - Updated outline to match document, fix broken VMware image. Remove reference to vcbRestore which is not covered in the actual document. |
Author |
VMware (NYSE: VMW) is the global leader in virtualization solutions from the desktop to the data center. Customers of all sizes rely on VMware to reduce capital and operating expenses, ensure business continuity, strengthen security and go green. With 2007 revenues of $1.33 billion, more than 120,000 customers and nearly 18,000 partners, VMware is one of the fastest-growing public software companies. VMware is headquartered in Palo Alto, California, and on the Web at www.vmware.com.
Chris Skinner |
Tags | availability backup CommVault Galaxy_6.1_SP4 VCB vmware_consolidated_backup |
Location | The specified document was not found. |
Context | Instead of installing backup agents in all of our guests and backing up over the LAN, we prefer to use VCB with our chosen backup provider in LAN-free mode.
VMware Consolidated Backup enables the LAN-free operation by providing access to the VMDKs and quiescing guest disk operations to provide a clean backup, but you still need backup software to read the mounted disk and back it up.
In our case we use Legator Networker 7.4. |
Actors | VMware Certified Professionals, Storage Management / Sysadmin / Operations / Backup experts |
References | See attached PDF |
Outline |
|
Disclaimer | You use this proven practice at your discretion. VMware and the author do not guarantee any results from the use of this proven practice. This proven practice is provided on an as-is basis and is for demonstration purposes only. |
How to use this proven practice
This paper documents the steps to successfully integrate CommVault’s Galaxy 6.1 SP4 with VMware’s Consolidated Backup Framework. CommVault provides three ways to integrate with VCB. Two of the solutions involve the installation of the iDataAgent backup agents into the virtual machine’s operating system. The third option is to not install the backup agent into the guest operating system, but instead use VCB for all backup operations. Although all three options are variants of each other, this paper focuses on the “agent-less” method since that is the premise of VCB in the first place.
This document assumes the following configuration:
VirtualCenter 2.5
ESX 3.5
VCB 1.1 proxy server
CommVault Galaxy 6.1 SP4
See the attached PDF for the detailed steps.
Rodos says:
The metadata did not match the attached document, fixed this up.
However the attached document does not even match itself. The introduction in the document states "Additionally, instructions on how to use Microsoft’s Services for Unix to run vcbRestore from the Service Console without first having to copy the backup files to the Service Console by creating an NFS share on the Windows machine. " but there is not a single reference to it in the document.
This is why I don't like the practices being based on attached files, they should be in the wiki format so that people can come and maintain, edit, improve them.
Still early days. Lets see if my updates are approved.
Over on VMTN there was a link to http://www.yellow-bricks.com/2008/01/30/vcb-backup-all-running-vms/ which had this great script snippet from depping...
Today I was busy trying to find out a way to schedule VCB backups with Commvault with just 1 schedule without having to rewrite your script every time someone creates a VM. The standard procedure is to create a subclient for every VM which is very human error prone. I stumbled upon a blog on RTFM about backing up all running VM’s, the actual script was done by Andrew Neilson, thanks! Of which the following was the most important part:
for /f “tokens=2 delims=:” %%i in (’vcbvmname -h virtualcenter.rtfm-ed.co.uk -u administrator -p password -s Powerstate:on ^| find “name:”‘) do @rd /s /q “D:\Backups\All\%%i” &vcbmounter -h virtualcenter.rtfm-ed.co.uk -u administrator -p password -a name:”%%i” -r “D:\Backups\All\%%i” -t fullvm > “D:\Backups\All\%%i.log
In other words: the second word of the outcome of the vcbvmname command will be parsed into the vcbmounter command. You could use this line and mix it with the standard script that Commvault uses:
for /f “tokens=2 delims=:” %%i in (’vcbvmname -h
-s Powerstate:on ^| find “name:”‘) do cscript pre-command.wsf “c:\program files\vmware\vmware consolidated backup framework\” %%i fullvm