1 / 47

Tivoli Storage Manager: VMware Backup and Recovery with TSM 6.1

Tivoli Storage Manager: VMware Backup and Recovery with TSM 6.1. Jim Smith May 14, 2009. Introduction.

bernard-oneill
Download Presentation

Tivoli Storage Manager: VMware Backup and Recovery with TSM 6.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tivoli Storage Manager:VMware Backup and Recovery with TSM 6.1 Jim Smith May 14, 2009

  2. Introduction • Tivoli Storage Manager provides data backup and recovery protection for VMware virtual machines. This session will include a discussion of the challenges of data backup and recovery in the VMware virtual environment, and of how the challenges are addressed with TSM's integration with VMware Consolidated Backup (VCB). In particular, the topics of how to use a dedicated backup proxy server to offload the virtual machine backup workload and the associated recovery options are addressed TSM 6.1 Backup and Recovery for VMware

  3. Agenda • VMware backup and recovery options • Backups from within the guest machines • Backups from the ESX Console OS • VMware Consolidated Backup (VCB) • VCB in depth • How it works • History of TSM changes for VCB support • VMware snapshots and Microsoft VSS TSM 6.1 Backup and Recovery for VMware

  4. Virtual Machine Backup/Recovery Within Guest TSM Server = TSM Agent VM1 C: D: • Backup-Archive or Data Protection clients installed on guests as if they were physical machines Service Console /a /b VM2 ESX Server SAN File-level backup VMFS vmdk vmdk vmdk SAN Storage Subsystem 4 TSM 6.1 Backup and Recovery for VMware

  5. VM Guest Backups – A Quick Look • Advantages • File level incremental backup • Backup of individual virtual machine file systems (c, d, e, etc.) • Virtual machine user file level restore to file system • Agents work with no modification and requires no re-training • Considerations • Unpredictable resource degradation with multiple concurrent backups • Requires a Backup-Archive client on each VM guest • Not integrated with backup and restore from ESX console OS backups • Decentralized control of backups TSM 6.1 Backup and Recovery for VMware

  6. IBM Software 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. • More information about this internet search: ibm tsm support guest virtual environments TSM 6.1 Backup and Recovery for VMware

  7. TSM Support for VMware Guest Environments • Current statement for VMware guest support TSM 6.1 Backup and Recovery for VMware

  8. Virtual Machine Backup/Recovery On ESX Console OS TSM Server = TSM Agent VM1 • TSM Linux x86 client installed on the ESX service console OS (COS) • Guest backup done at full VM level • Backups independent of guest OS • dsmc selective backup of guest vmdk directory strucutre C: D: Service Console /a /b VM2 ESX Server SAN Full VM-level backup VMFS vmdk vmdk vmdk SAN Storage Subsystem 8 TSM 6.1 Backup and Recovery for VMware

  9. Console OS Backup - A Quick Look • Advantages • Fast, east bare machine backup and recovery\ • Backup is OS agnostic • Considerations • Only supported on ESX; ESXi does not have a console OS • Console OS built on Linux 2.4 kernel and not supported with TSM 6.1 (must continue to use TSM 5.5 Backup-Archive client) • Not integrated with backup and restore from agents living inside the guests • Backing up via the Service Console may overburden ESX machine and slow production applications TSM 6.1 Backup and Recovery for VMware

  10. Console OS Backup – How Backup Works • Configure and use vcbMounter command to create snapshot of vmdk and related files:vcbMounter -a ipaddr:vmwinxp.storage.sanjose.ibm.com -r /vmfs/volumes/tsmdisk2/vcb/vmwinxp • Use Linux x86 Backup-Archive client to backup snapshot copy of files:dsmc sel /vmfs/volumes/tsmdisk2/vcb/vmwinxp/"*" TSM 6.1 Backup and Recovery for VMware

  11. Console OS Backup – What is Exported? root@odin vmware]# ls -l /vmfs/volumes/tsmdisk2/vcb/vmwinxp total 4594432 -rw-r--r-- 1 root root 997 Mar 9 15:37 catalog -rw------- 1 root root 856752128 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s001.vmdk -rw------- 1 root root 848887808 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s002.vmdk -rw------- 1 root root 1774518272 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s003.vmdk -rw------- 1 root root 1130430464 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s004.vmdk -rw------- 1 root root 327680 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s005.vmdk -rw------- 1 root root 87883776 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s006.vmdk -rw------- 1 root root 65536 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp-s007.vmdk -rw------- 1 root root 708 Mar 9 15:47 scsi0-0-0-winXP - vmwinxp.vmdk -rw-r--r-- 1 root root 54 Mar 9 15:47 unmount.dat -rw------- 1 root root 34536 Mar 9 15:37 vmware-4.log -rw------- 1 root root 35939 Mar 9 15:37 vmware-5.log -rw------- 1 root root 35838 Mar 9 15:37 vmware-6.log -rw------- 1 root root 29253 Mar 9 15:37 vmware-7.log -rw------- 1 root root 22304 Mar 9 15:37 vmware-8.log -rw------- 1 root root 48133 Mar 9 15:37 vmware-9.log -rw------- 1 root root 42534 Mar 9 15:37 vmware.log -rw------- 1 root root 8664 Mar 9 15:37 winXP - vmwinxp.nvram -rw------- 1 root root 1758 Mar 9 15:37 winXP - vmwinxp.vmx TSM 6.1 Backup and Recovery for VMware

  12. Console OS Backup – How Restore Works • Use Linux x86 Backup-Archive client to restore files to temporary location:dsmc rest /vmfs/volumes/vcb/vm1/"*" /vmfs/volumes/vcb/vcbrest/ • Shut down guest machine • Use the VCB restore utility to recover the virtual machine from these temporary files:vcbRestore -s /vmfs/volumes/vcb/vcbrest TSM 6.1 Backup and Recovery for VMware

  13. Console OS Backup – For More Information • Tivoli Field Guide – Using Tivoli Storage Manager for Backup and Restore Operations on the VMware Service Console • Internet search: tivoli field guide vmware esx • Topics • Differences in storage layout between ESX 2 and ESX 3 • TSM configuration • Backup methods including schedules • Restore procedures • Example of backup operation with VCB utilities TSM 6.1 Backup and Recovery for VMware

  14. Is There a Better Solution? • Cumulative backup loads are very difficult to quantify in a virtualized environment • Disk I/O • Network I/O • CPU load • No easy story for SAN data movement • VMware introduces VMware Consolidated Backup (VCB) to initially solve these basic problems TSM 6.1 Backup and Recovery for VMware

  15. VCB Goals • Leverage VMware’s unique technology to improve file system backup • Offload backup cycles from ESX Server • Work without SAN-specific software • Easy implementation for end users • Begin reducing the overall complexity of backup infrastructure TSM 6.1 Backup and Recovery for VMware

  16. What is VMware Consolidated Backup (VCB) • API and utility that enables mounting .vmdk files or VMFS on a Windows machine enabling off-loaded LAN-free backup of virtual machine guests • Includes (included) integration modules (pre & post processing scripts) to integrate with some backup products including TSM • Centrally managed proxy server that runs on Windows 2003+ server; removes load from ESX Server hosts and virtual machines TSM 6.1 Backup and Recovery for VMware

  17. What is VMware Consolidated Backup … Not! • A backup engine or data mover • An enterprise backup solution • A standalone product • The silver bullet to all backup issues in a virtual environment TSM 6.1 Backup and Recovery for VMware

  18. Types of VCB Backups • File-level • Backup and recovery of individual files • Exploit TSM progressive incremental technology • Geared for unstructured Windows file data (e.g., file servers) • Full-VM • Similar to image backup; backup of a blob which is comprised of the virtual disk files (.vmdk), and other control information • Geared for disaster recovery of any type of guest • Non-Windows guests • Windows guests running Exchange, SQL, SharePoint, etc. TSM 6.1 Backup and Recovery for VMware

  19. VMware Consolidated Backup: File-Level Backup TSM Server = TSM Agent 2. VCB connects to snapshot and exposes it as a network share VM1 C: D: Backup Proxy Service Console X:\mnt\vm1\letters\d VCB Framework /a /b VM2 X:\mnt\vm1\letters\c ESX Server SAN 1. TSM client initiates snapshot of virtual guest (vcbMounter) and VCB invokes snapshot SAN VMFS 3. TSM performs federated, progressive incremental backup vmdk vmdk vmdk SnapsVM1 4. VCB deletes mount point and snapshot SAN Storage Subsystem 19 TSM 6.1 Backup and Recovery for VMware

  20. VMware Consolidated Backup: File-Level Restore TSM Server = TSM Agent 1. Restore directly to B-A client within guest OS VM1 C: D: Backup Proxy Service Console X:\tmp VCB Framework /a /b VM2 ESX Server SAN VMFS 2. or restore from proxy to shared storage (using TSM asnode option) vmdk vmdk vmdk SAN Storage Subsystem 20 TSM 6.1 Backup and Recovery for VMware

  21. Backup Without Namespace Management tsm: NAXOS_5500>q files Node Name Filespace FSID Platform Filespace Is Files- Capacity Pct Name Type pace (MB) Util Unicode? --------------- ----------- ---- -------- --------- --------- ----------- ----- BACKUPPROXY \\backuppr- 15 WinNT NTFS Yes 280,000.1 31.9 oxy\mnt\- vm1\lett- ers\c BACKUPPROXY \\backuppr- 16 WinNT NTFS Yes 280,000.1 31.9 oxy\mnt\- vm1\lett- ers\d BACKUPPROXY \\backuppr- 17 WinNT NTFS Yes 280,000.1 31.9 oxy\mnt\- vm2\lett- ers\c TSM 6.1 Backup and Recovery for VMware

  22. Backup With Namespace Management tsm: NAXOS_5500>q files Node Name Filespace FSID Platform Filespace Is Files- Capacity Pct Name Type pace (MB) Util Unicode? --------------- ----------- ---- -------- --------- --------- ----------- ----- VM1 \\vm1\c$ 18 WinNT NTFS Yes 280,000.1 31.9 VM1 \\vm1\c$ 19 WinNT NTFS Yes 280,000.1 31.9 VM2 \\vm2\c$ 20 WinNT NTFS Yes 280,000.1 31.9 TSM 6.1 Backup and Recovery for VMware

  23. Namespace Management Explained TSM Server = TSM Agent 3. Client backups data from mountpoints into file space for original drive name, e.g., \\vm1\c$ (~snapshotroot) VM1 C: D: Backup Proxy Service Console X:\mnt\vm1\letters\d VCB Framework /a /b VM2 X:\mnt\vm1\letters\c ESX Server SAN 1. TSM client authenticates as nodename BACKUPPROXY SAN VMFS 2. Client switches identity to nodename VM1 (~ asnode) vmdk vmdk vmdk SnapsVM1 4. Client switches identity to nodename VM2 (if part of backup) and repeats SAN Storage Subsystem 23 TSM 6.1 Backup and Recovery for VMware

  24. VMware Consolidated Backup: Full-VM Backup TSM Server = TSM Agent 2. VCB exports .vmdk files and control files to a pre-defined staging area VM1 C: D: Backup Proxy Service Console /a VM2 VCB Framework C: D: config ESX Server SAN 1. TSM client initiates snapshot of virtual guest (vcbMounter) and VCB invokes snapshot SAN VMFS 3. Client performs selective backup of staging directory vmdk vmdk vmdk SnapsVM1 4. Client deletes files from staging directory (optional) and VCB removes snapshot SAN Storage Subsystem 24 TSM 6.1 Backup and Recovery for VMware

  25. VMware Consolidated Backup: Full-VM Recovery TSM Server = TSM Agent 2. VMware Converter used to recover machine from restored files VM1 C: D: Backup Proxy Service Console /a VM2 VCB Framework C: D: config ESX Server SAN 1. TSM client performs restore to staging area SAN VMFS vmdk vmdk vmdk SAN Storage Subsystem 25 TSM 6.1 Backup and Recovery for VMware

  26. What is a VCB Snapshot • Software snapshot (no hardware snapshot exploitation) • List of pointers to blocks of data on virtual machine’s drives, VMware configuration, BIOS configuration. • During snapshot operation, changes are saved to a REDO log inside a VMFS volume. • When the snapshot is released, the REDO log data is written back into the virtual machine VMDK files and then deleted. TSM 6.1 Backup and Recovery for VMware

  27. Sample VSS Writer Interaction TSM 6.1 Backup and Recovery for VMware

  28. Microsoft Volume Shadow Copy Services (VSS) • ESX 3.5 update 2 provides snapshot integration with VSS • All VSS writers (e.g., Exchange, SQL) within the guest notified of backup operating and allowed to quiesce to put their data stores in a consistent state • VSS uses a COPY backup (VSS_BT_COPY) • Files on disk will be copied to a backup medium regardless of the state of each file's backup history, and the backup history will not be updated. • Guest machine needs to upgrade VMware tools in order to exploit TSM 6.1 Backup and Recovery for VMware

  29. VMware Tools Update to Enable VSS Support TSM 6.1 Backup and Recovery for VMware

  30. TSM Changes for VCB • TSM 5.4 • Basic integration using the VCB integration module • Recover view of the data is centered around the VCB proxy • TSM 5.5 • Does not require integration module from VMware for file-level backups • Better recovery and 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 on the virtual machine TSM 6.1 Backup and Recovery for VMware

  31. TSM Changes for VCB • TSM 6.1 • Integrated Full-VM backups • Does not require integration module from VMware for either file-level or Full-VM backups • Linux client does not support ESX backups (no file-level support for Linux guest OS) • VCB passwords are stored encrypted • All changes independent of TSM server • In order to exploit Windows adaptive subfile backup processing you will need a TSM 6.1 server or TSM 5.5 server with proper patch TSM 6.1 Backup and Recovery for VMware

  32. VCB Environment Requirements • ESX server with SAN attached storage • Dedicated Windows 2003 server • Recommended to be dedicated, not required • Disable Automatic Drive-Letter Assignment • 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 TSM 6.1 Backup and Recovery for VMware

  33. TSM + VCB Configuration • Create and register TSM nodes and grant authorization • Authorize node on VCB proxy to backup into filespaces for guest machines • Provide authentication with ESX or VirtualCenter • Configure the required TSM options in dsm.opt for VCB • Configure TSM options on guest VM (for file-level restore) • Ensure that the VMware tools are installed on each guest • Optionally configure the VMware pre-freeze and post-thaw scripts on guests TSM 6.1 Backup and Recovery for VMware

  34. Creating Node Definitions in TSM • Grant authority to TSM node backupproxy to backup and restore data on behalf of nodes vm1 and vm2dsmadmc register node backupproxy secretpw backdel=yesdsmadmc register node vm1 secretpwdsmadmc register node vm2 secretpwdsmadmc grant proxynode target=vm1 agent=backupproxydsmadmc grant proxynode target=vm2 agent=backupproxy TSM 6.1 Backup and Recovery for VMware

  35. Authenticating With VirtualCenter or ESX • Use client options to specify host, user id and password • Vmchost, Vmcuser, Vmcpw • or use TSM 6.1 preference editor to specify these options (will get written to the options file) • or TSM 6.1 use the DSMC SET PASSWORD command to store the password securely in the Windows Registrydsmc set password –type=vcb myesxhost.ibm.com vcbmgr secretpw • Still need to specify Vmchost in options file TSM 6.1 Backup and Recovery for VMware

  36. Specifying Which VM Guests to Backup • Vmlist command used to optionally specify a list of virtual machines • Available in 6.1 preference editor, options file or on dsmc backup vm command • Use this option to map virtual machine host names to TSM nodenames if they are not the same:vmlist vm3[tsmnodeX] • Use this option if there is no DNS resolution availablevmlist 9.22.100.85[vm4],9.22.100.90[vm5] TSM 6.1 Backup and Recovery for VMware

  37. Specifying VM Backup Commands • Vmbackuptype to specify file-level or full-VM:dsmc backup vm –vmbackuptype=filedsmc backup vm –vmbackuptype=fullvm • Vmbackdir specifies the location of the exported files to be processed for full-vm backups • Vmbacknodelete specifies not to delete the exported files processed for full-vm backups • Each export for backup will be time-stamped for identifcation TSM 6.1 Backup and Recovery for VMware

  38. Backup VM – Set-up Phase C:\Program Files\Tivoli\TSM\baclient>dsmc backup vm –vmbackuptype=file 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 TSM 6.1 Backup and Recovery for VMware

  39. Backup VM – File-Level Incremental Phase 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 … TSM 6.1 Backup and Recovery for VMware

  40. Backup VM – Clean-Up Phase 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 TSM 6.1 Backup and Recovery for VMware

  41. Querying Full-VM Backups tsm> QUERY VM * -vmbackuptype=FILEFilespace Query for Virtual Machine 'vm1' Accessing as node: vm1 # Last Incr Date Type File Space Name __ _____________________ ____ _______________ 1 09/25/2008 12:19:23 NTFS \\vm1\c$ fsID: 2 2 09/25/2008 12:19:25 NTFS \\vm1\e$ fsID: 3 3 09/25/2008 12:19:22 NTFS \\vm1\z$ fsID: 1 Filespace Query for Virtual Machine 'vm2' Accessing as node: vm2 # Last Incr Date Type File Space Name __ _____________________ ____ _______________ 1 09/25/2008 10:49:10 NTFS \\vm2\c$ fsID: 2 2 09/25/2008 10:49:09 NTFS \\vm2\h$ fsID: 1 TSM 6.1 Backup and Recovery for VMware

  42. Restoring Full-VM Backups • dsmc restore vm command:dsmc RESTORE VM vm2 G:\restdir • Restores files to:G:\restdir\fullvm\vm2\RESTORE_DATE_2009_06_30[11-22-11]\ • Need to run VMware Converter to recovery virtual machine TSM 6.1 Backup and Recovery for VMware

  43. TSM 6.1 Preference Editor TSM 6.1 Backup and Recovery for VMware

  44. TSM 6.1 Restore VM Selection TSM 6.1 Backup and Recovery for VMware

  45. TSM 6.1 Restore VM Panel TSM 6.1 Backup and Recovery for VMware

  46. TSM 6.1 Search and Filter VMs TSM 6.1 Backup and Recovery for VMware

  47. Summary Comparison of Backup Methods TSM 6.1 Backup and Recovery for VMware

More Related