500 likes | 736 Views
Protecting VMware Virtual Machines with Tivoli Storage Manager. Randy Larson larsonr@us.ibm.com. TSM ATS Team. Dave Canan ddcanan@us.ibm.com Dave Daun djdaun@us.ibm.com Tom Hepner hep@us.ibm.com Randy Larson larsonr@us.ibm.com. Agenda. VMware Consolidated Backup (VCB) Introduction
E N D
Protecting VMware Virtual Machines withTivoli Storage Manager Randy Larson larsonr@us.ibm.com
TSM ATS Team • Dave Canan • ddcanan@us.ibm.com • Dave Daun • djdaun@us.ibm.com • Tom Hepner • hep@us.ibm.com • Randy Larson • larsonr@us.ibm.com
Agenda • VMware Consolidated Backup (VCB) Introduction • IBM and TSM Support • What is VCB? • TSM exploitation of VCB • Sample Configuration • Hardware Components • SAN configuration, zoning, and LUN Masking • ESX and Guests Setup • TSM configuration • Making it Happen • VCB file level backup and restore • Full VM Backup and Restore • Backup using TSM Linux Client
IBM Software Support for Virtualized Environments • IBM software products leverage binary compatibility provided by the virtualization technologies because the Virtual Environment products themselves provide transparency to the operating systems, applications, and middleware that operate above it. • If you submit a standard usage or defect-related service request, and your software is running on a virtual environment, IBM Support will assume that the problem is common to both native and virtual operating environments, and we may require that you recreate the problem in a native environment only if there is reason to believe that the problem may be unique to the Virtual Environment.
TSM Support and Restrictions for Virtualized Environments • The support position and restrictions for Tivoli Storage Manager products and components running as guests on Virtual Machines and through virtualization is further clarified in technotes below • For example: • The guest must be running an operating system supported by the TSM product. • For the Data Protection products, the application being protected must also support running on that operating system as a guest • See: • http://www-01.ibm.com/support/docview.wss?uid=swg21394300 • http://www-01.ibm.com/support/docview.wss?uid=swg21239546
VIO support • Historically VIO has not been supported • RESERVE/RELEASE IOCTLs sent to parent FC adapter, not the drive • Now supported by TSM/AIX when used with NPIV • NPIV (N-Port ID Virtualization) requires • p6 System p • 5735 PCIe 8Gb Fibre Channel Adapter • NPIV capable SAN switch • HBA presents multiple unique WWNs to the OS • TSM requirements • Virtual I/O Server 2.1.0 with fix pack V2.1 applied • AIX 6.1 TL 3 SP 1 • See TSM supported platforms webpage for AIX
Tivoli Storage Manager and VMware History • TSM 5.3 and up (Traditional VMware backups without VCB) • Run a TSM B/A Client from within the individual machines itself • Run TSM B/A Client on Linux on the ESX Server and backup flat VMware files • TSM 5.4 • Basic integration using the VCB integration module (TSMIM) • Recovery view of the data is centered around the VCB host • Manual Scripting involved • TSM 5.5 • Integrated VCB product-based solution requiring no manual scripting for file-level backup • Does not require integration module from VMware • Better recovery and transparent management of the data on the TSM Server • User is removed from the fact that the backup was performed from a VCB backup host • Manage a virtual machine's backup data as if it had been backed-up by a TSM client running inside the virtual machine • TSM 6.1 • Integrated Full VM backup • Works with VMWare converter for FULLVM restore
Roadmap: VMware enhancements TSM 6.x 1H10 • Auto Discovery - Allows TSM VCB backup functions (full VM and file-level) to automatically discover when new guests are brought on-line. • Leverage vStorage API for Data Protection for file-level backup and recovery • LAN-free backup of virtual machines from a centralized proxy server • VMware released v1.5 of Consolidated Backup Framework which supports legacy VCB operations with ESX/ESXi 4.0 Benefits: • Auto discover new guests, • No more manual process to track guests • File-Level backup and recovery using vStorage API for Data Protection APIs for low impact backup and recovery. * TSM Roadmap Statements of IBM future plans and directions are provided for information purposes only. Plans and direction are subject to change without notice.
Roadmap: Microsoft Hyper V guest backup using Volume Shadow Copy Services (VSS) TSM 6.x 1H10 Win2008 guest Benefits: • Full snapshot backup of guest machine • Snapshots synchronized with applications and file systems inside guests with VSS TSM BA client installed on Hyper-V host Win2003 guest Win2000 guest * TSM Roadmap Statements of IBM future plans and directions are provided for information purposes only. Plans and direction are subject to change without notice.
VMware Consolidated Backup (VCB)Introduction IBM and TSM virtualization support What is VCB? TSM exploitation of VCB
vCenter Structure { Folder DataCenter Guest Host
VMware Data Protection Without VCB • Cumulative backup loads are very difficult to quantify in a virtualized environment • Disk I/O • Network I/O • CPU load • Backing up via the Service Console may overburden ESX machine and slow production applications • Use of ESX console for backup will not be supported in future ESX levels
VMware Consolidated Backup (VCB) • VCB, introduced in VMware Virtual Infrastructure 3, allows the backup of multiple virtual machines to be off-loaded to a dedicated physical host (Backup Proxy). • Off-loading the backup from virtual machines and the ESX service console, allows backups to be completed LAN-free. • VCB significantly reduces the load on ESX Servers which allow it to run more virtual machines
VCB – TSM File Level Backup • VCB invokes a snapshot of the guest to be done by ESX • Vmtools flushes filesystem buffers prior to snapshot • Optional script can be invoked to work with applications • VCB connects to snapshot (on shared LUNs) • Uses Windows Mountpoint capabilities • Mountpoint exposed as a directory tree to Windows applications • Tivoli Storage Manager client uses traditional incremental backup • Proxy support employed • Data treated as if backed up by guest • VCB deletes mountpoint and ESX snapshot
VCB – TSM Full VM Backup • Full VM for Disaster Recovery provides support to move entire VMDK files (disk to disk across a SAN) via a backup proxy, to TSM storage • Provides a backup method similar to a TSM Linux x86 client backing up entire virtual machines directly from the ESX server service console • Similar to a TSM image backup but comprises the entire virtual machine in a set of files that represent the physical disks of the virtual machine and other control information. • Guest image owned by proxy node, not by guest VM
Sample Configuration Hardware Components SAN configuration and Zoning ESX and Guests Setup TSM configuration
VCB Environment Requirements • ESX server with SAN attached storage • Dedicated Windows 2003 server • Recommended to be dedicated, not required • Zone and configure SAN so that all ESX servers, VMs and the Proxy have same access • Install Components: • VMware Infrastructure 3 • VMware Consolidated Backup framework • VMware Converter tool
Service Console Configuration SAN365-1 (ESX 3.5.0) SAN360-2 (Win 2003) VM4 C D Backup Proxy C Other Guests VCB Framework TSM Client SAN Storage Subsystem (ESS800) TSM STA VMFS TSM Server LPAR P570 Tape Library vmdk vmdk vmdk
Service Console File level Backup SAN365-1 (ESX 3.5.0) SAN360-2 (Win 2003) VM4 C D 2nd Choice is LAN Backup Proxy C Other Guests VCB Framework H:\mnt\vm4\letters\c H:\mnt\vm4\letters\d TSM Client 1st Choice is SAN SAN Storage Subsystem (ESS800) TSM STA VMFS TSM Server LPAR P570 Tape Library vmdk vmdk vmdk C:\... D:\...
Service Console Full VM Backup SAN365-1 (ESX 3.5.0) SAN360-2 (Win 2003) VM4 C D 2nd Choice is LAN Backup Proxy C Other Guests VCB Framework H:\mnt\vm4\ TSM Client 1st Choice is SAN SAN Storage Subsystem (ESS800) TSM STA VMFS TSM Server LPAR P570 Tape Library vmdk vmdk vmdk
TSM / VCB Environment Requirements • Ensure that the VMware tools are installed on each guest • Optionally configure the VMware pre-freeze and post-thaw scripts on guests • Configure the required TSM options in dsm.opt for VCB for proxy node • Configure TSM on guest (for file restore) • Register nodes and grant authorization • REGister NOde VMGUEST1 password • REGister Node PROXYNODE password • GRant PROXynode TArget=VMGUEST1 AGent=PROXYNODE
Configure User ID on ESX • In VirtualCenter 2.5, use a predefined role called VMware Consolidated Backup User • Otherwise create new role and select the following privileges: • VirtualMachine > Configuration > Disk Lease • VirtualMachine > State > Create Snapshot • VirtualMachine > State > Remove Snapshot • VirtualMachine > Provisioning > Allow Virtual Machine Download • Virtual Machine > Provisioning > Allow Read‐only Disk Access • Assign User to this role
Proxy Client options file options • Vmchost Address of ESX / vCenter • Vmcuser VCB ID on ESX • Vmcpw Password for ESX VCB ID • Vmlist List of VM guests to backup • Vmbackuptype Type of backup to perform file or fullvm • Vmbackdir Destination on proxy for mountpoint or copy • Vmbacknodelete Optionally save FULLVM image on proxy disk
Set password –type=vcb myesxhost.whatever.ibm.com vcbmgr vcbpassword Backup vm –vmbackuptype=file Backup vm –vmbackuptype=fullvm Query vm –vmbackuptype=file Query vm –vmbackuptype=fullvm Restore vm [vmguest] [destination] Proxy Client commands and over-rides • Command line options override options file defaults
ESX TSM Options (using Linux client on ESX) • dsm.opt SErvername atsr4p22 • followsymbolic yes • dsm.sys SErvername atsr4p22 nodename san365-1 COMMMethod TCPip TCPPort 1500 TCPServeraddress atsr4p22.wsclab.washington.ibm.com passwordaccess generate • virtualmountpoint /vmfs * Exclude options exclude /vmfs/.../*.vswp exclude /vmfs/.../*.REDO • Going away in future levels of ESX
Making it Happen VCB File level Backup and Restore VCB Full VM Backup and Restore Backup using TSM Linux Client
VCB File level backup command Command: dsmc backup vm [–vmbackuptype=file] Performs all the functions as if: "C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbmounter" -h san365-1.wsclab.washington.ibm.com -u vcbmgr -p vcbpasswd -a ipaddr:san365-1-vm4.wsclab.washington.ibm.com -t file -m san -r C:\mnt\tsmvmbackup\filelevel\san365-1-vm4 dsmc –asnode=san365-1-vm4 incr c: –snapshotroot=C:\mnt\tsmvmbackup\filelevel\san365-1-vm4\letters\c incr d: –snapshotroot=C:\mnt\tsmvmbackup\filelevel\san365-1-vm4\letters\d "C:\Program Files\VMWare\VMware Consolidated Backup Framework\vcbMounter" -h san365-1.wsclab.washington.ibm.com -u vcbmgr -p vcbpasswd -U C:\mnt\tsmvmbackup\filelevel\san365-1-vm4
“dsmc backup vm” - VCB setup C:\Program Files\Tivoli\TSM\baclient>dsmc backup vm IBM Tivoli Storage Manager Command Line Backup-Archive Client Interface Client Version 6, Release 1, Level 0.0 . . . Backup VM command started. Total number of virtual machines to process: 1 Backup of Virtual Machine 'san365-1-vm4' Mount virtual machine disk on backup proxy for VM 'san365-1-vm4' . . . Done mounting Volume 1 mounted at h:\mnt\filelevel\san365-1-vm4\digits\1 (mbSize=13311 fsType=NTFS ) Volume 2 mounted at h:\mnt\filelevel\san365-1-vm4\digits\2 (mbSize=4094 fsType=NTFS ) Volume 1 also mounted on h:\mnt\filelevel\san365-1-vm4\letters\C Volume 2 also mounted on h:\mnt\filelevel\san365-1-vm4\letters\D Finished command. Return code is: 0
“dsmc backup vm” – TSM incremental backup Incremental backup of Virtual Machine 'san365-1-vm4' Querying all_local drives for VM 'san365-1-vm4' Searching for VM 'san365-1-vm4' volumes for backup at location: h:\mnt\filelevel\san365-1-vm4\letters Accessing as node: san365-1-vm4 Incremental backup of volume '\\san365-1-vm4\c$' Incremental backup of volume '\\san365-1-vm4\d$' Successful incremental backup of '\\san365-1-vm4\d$' Successful incremental backup of '\\san365-1-vm4\c$' Total number of objects inspected: 34,022 Total number of objects backed up: 35 . . .
“dsmc backup vm” – VCB cleanup processing Successful incremental backup of Virtual Machine 'san365-1-vm4' Unmount virtual machine disk on backup proxy for VM 'san365-1-vm4' Unmounted h:\mnt\filelevel\san365-1-vm4\digits\1\ (formatted) Unmounted h:\mnt\filelevel\san365-1-vm4\digits\2\ (formatted) Deleted directory h:\mnt\filelevel\san365-1-vm4\digits\1\ Deleted directory h:\mnt\filelevel\san365-1-vm4\digits\2\ Deleted directory h:\mnt\filelevel\san365-1-vm4\digits Deleted directory h:\mnt\filelevel\san365-1-vm4\letters\C\ Deleted directory h:\mnt\filelevel\san365-1-vm4\letters\D\ Deleted directory h:\mnt\filelevel\san365-1-vm4\letters Deleted directory h:\mnt\filelevel\san365-1-vm4 Finished command. Return code is: 0 Accessing as node: VCBPROXY Backup VM command complete Total number of virtual machines backed up successfully: 1 virtual machine san365-1-vm4 backed up to nodename san365-1-vm4 Total number of virtual machines failed: 0 Total number of virtual machines processed: 1
VCB FullVM Backup Script (pre V6) "C:\Program Files\VMWare\VMware Consolidated Backup Framework\vcbmounter“ -h san365-1.wsclab.washington.ibm.com -u vcbmgr -p vcbpasswd -a ipaddr:san365-1-vm4.wsclab.washington.ibm.com -t fullvm -m san -r h:\mnt\san365-1-vm4 dsmc sel "h:\mnt\san365-1-vm4\*“ –su=on "C:\Program Files\VMWare\VMware Consolidated Backup Framework\vcbmounter“ -h san365-1.wsclab.washington.ibm.com -u vcbmgr -p vcbpasswd -U h:\mnt\san365-1-vm4
VCB FullVM Backup (with V6) Backup command: dsmc backup vm [–vmbackuptype=full] Restore command: dsmc restore vm [vmguest] [destination]
Restoring a guest machine example • dsmc restore vm san365-1-vm2 • Use VMware converter to rebuild guest
ESX Console FullVM Backup Script vcbMounter -h san365-1.wsclab.washington.ibm.com -u vcbmgr -p vcbpasswd -a ipaddr:san365-1-vm4.wsclab.washington.ibm.com -t fullvm -r /vmfs/volumes/VCBDISKS/vcb/san365vm4 dsmc sel "/vmfs/volumes/VCBDISKS/vcb/san365vm4/*" vcbMounter -h san365-1.wsclab.washington.ibm.com -u vcbmgr -p vcbpasswd -U /vmfs/volumes/VCBDISKS/vcb/san365vm4 • Going away in future levels of ESX
TSM Client on each VM TSM Client on ESX server(Support going away) TSM Client on Backup Proxy + File-level backup & restore - No central backup | restore - Additional ESX resource load + Central BM VM backup & restore - Additional ESX resource load - Needs client on VM for restore - Additional downtime on VM + Central Bare VM backup and restore + File-level backup + Full-volume backup + Reduced network/cpu load - Needs TSM client on VM for file restores VMWare & TSM Configurations – Pros / Cons
Summary • Tivoli Storage Manager provides flexible data protection options for VMware guest systems • Integrated with VMware Consolidated Backup with file-level and full VM backup and restore options • Backup and restore support on VMware guest machine • More in the future
Reference Information • TSM V6 Information Center http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp • VMware Virtual Machine Backup Guide http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_vm_backup.pdf • VMware Consolidated Backup framework http://www.vmware.com/download/vi • VMware Converter toolhttp://www.vmware.com/download/converter/ • VMware ESX Server Documentation http://www.vmware.com/support/pubs/esx_pubs.html • VMware Perl API documentation:http://www.vmware.com/pdf/Scripting_API_21.pdf • VMware Professional Services: http://www.vmware.com/services/