Metadata
Title | Proven Practice: Integrating Tivoli Storage Manager 5.5 with VCB 1.1 | |
Version | VMware 07/AUG/2008 1.0 | |
Author |
| servlet/JiveServlet/downloadImage/102-1075-2-1067/vmware.gif] 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 TSM_5.5 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 TSM 5.5 | |
Actors | VMware Certified Professionals, Storage Management / Sysadmin / Operations / Backup experts | |
References | TBD | |
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 IBM’s Tivoli Storage Manager (TSM) with VMware’s Consolidated Backup Framework. 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. Trial versions can be obtained from IBM’s web site. Some of the text was extracted from the integration module help files.
This document assumes the following configuration:
VirtualCenter 2.5
ESX 3.5
VCB 1.1 proxy server
IBM Tivoli Storage Manager 5.5
Windows Services for Unix 3.5.
See the attached PDF for the detailed steps.
Steve Chambers says:
@mcfm, that is a great comment - do you think you might be able to write your practice up? Just a series of steps... you don't have to include screenshots, but it helps... perhaps you have this in a word doc or something, which you could attach to a new viops doc?
Miguel Miranda says:
in response to: Steve Chambers
Steve I don't have that documented, but I will manage that.
Pitt says:
in response to: Miguel Miranda
Well boy's what fantastic timing, as a company managing multiple VMware installations that are currently backed up with CA ARCServe, which is causing us problems and we are looking at making use of Tivoli.
I have a lot of experience with backup platforms as would be REALLY keen to keep track of this and make use of the excellent document you have posted here.
I am just waiting for our IBM man to get in touch about some eval software, and so am just gathering information for my trial install.
Please keen me up-to-date with any ideas and I’d love any tips etc.
Thanks
Again
Steve
barvos says:
in response to: Miguel Miranda
Thanks Miguel for the great explanation.
I am preparing to my first installaton. Besides your explanation, there are very few comments on the topic in the web. I've found only:
1. a notice that options that you mentioned (VMCHost, VM.. ) are used by the TSM to automatically pass virtualfsname, virtualhostname etc so that the backup/restore is more seamless. Backup vm also runs transparently for us all pre and post schedules related to snapshots . Correct?
2. a notice that the c:\mnt is hardcoded regardless of any integration stuff like config.js etc.
I am especially curious what scripts are called by 'dsmc backup vm' command, and how to pass parameters to vcbmounter, what are all config files in the end to end process, how to call also VM tools for applications quiescing etc.
Another question would be how to dynamically call a group VMs (group could be defined by IP alias? or could be 'all' VMs?)
Looking forward to any posts..
Hi Chris,
If you are doing file-level backups, you also can, with TSM 5.5, integrate it with VCB without TSM VCB Integration Modules.
You have 4 new parameters in TSM BAClient dsm.opt which are VMCHOST, VMCUSER, VMCPWD, VMLIST, and a new dsmc command option, "backup vm".
One advantage to me is, you create a tsm node for each virtual machine you want to backup, like in a physical environment, then you grant authority to the proxy node (VCB/TSM). When you backup, the tsm client parses a command that invokes VCB, all mount points to the VM are mounted in C:/mnt and the backup is done. Now the advantage, each filespace, you have backed up, belonging to each VM are under is tsm node and not in the VCB tsm node. If you want to restore just a single file, and if you have installed and only configured dsm.opt, you have the possibility to restore directly in the VM. One other thing is, if you decommission a VM and want to delete all its backups, you just have to delete its own filespaces.