1 / 72

Agenda

Tivoli Storage Manager Version 6 Technical Overview IBM Advanced Technical Support Dave Daun djdaun@us.ibm.com. Agenda. New Install Process New TSM Database – Port to DB2 Data Deduplication Real-Time Monitoring and Reporting Individual Mailbox Restore for Microsoft Exchange

missy
Download Presentation

Agenda

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 Version 6Technical OverviewIBM Advanced Technical SupportDave Daun djdaun@us.ibm.com

  2. Agenda • New Install Process • New TSM Database – Port to DB2 • Data Deduplication • Real-Time Monitoring and Reporting • Individual Mailbox Restore for Microsoft Exchange • N-Series SnapDiff Integration and Snap Mirror to Tape Integration • VMware Consolidated Backup Improvements • Microsoft Windows Active Directory Individual Object Restore • AdminCenter Improvements

  3. Agenda • Disaster Recovery Manager for Active Data Pool Objects • GPFS for LANfree • Improved Restore Performance • Improvements to EXPIRE INVENTORY • Other New Features

  4. Overview • Some perspective on the TSM V6 announcement • Announced on February 10, 2009 • Electronic download available on March 27, 2009, Media on April 24, 2009 • Significant in terms of scope and function • Beta program started in April 2008 and has included over 200 participants • What’s coming in in the Lunch & Learn Series • Preparing for the Next Release of TSM (January 22) • TSM V6 Performance Assessment • TSM V6 Database Upgrade Process • TSM V6 Integrated Reporting Feature • TSM V6 Data Deduplication Feature • TSM V6 Administration Center Update

  5. TSM Installation Tivoli Storage Manager V6

  6. TSM V6 Installation • New installation tool – Deployment Engine • No longer use the native install tools (smit, Windows Installer, etc.) • Installs all components easily • Used by the TSM server, client and reporting tool

  7. TSM V6 Installation

  8. TSM V6 Installation

  9. TSM V6 Installation

  10. TSM Database Tivoli Storage Manager V6

  11. TSM V6 Database – Port to DB2 • Major restructuring of the TSM database – complete port to IBM DB2 • Why do this ?? • Current DB is reaching its limits in terms of size, performance, and function • Position for long term growth • Position for future additional function (online audit and reorg) • Free up development resources • Performance goal is to provide “equivalent performance” • Compared to Version 5.5 • “Port” to a new database has some side effects • !! Not the solution to every problem !!

  12. TSM V6 Database – Port to DB2 • Completely New TSM Database • External to TSM – you can see it there and you can interact directly with the DB2 database manager – DON’T ALTER ANYTHING • Design goal is make DB2 as transparent as possible – there is no expectation that TSM administrations will need to be DB2 administrators • One-to-One relationship between TSM and database • Must use the DB2 that is installed with TSM – cannot use an existing DB2 instance • No merge of multiple TSM instances into one database • Can run multiple TSM / database instances on same OS image

  13. TSM V6 Database – Port to DB2 • Upgrade utility is provided as a separate install package • Use the utility to upgrade a V5.4 or V5.5 server to TSM V6 • Upgrade can run in-place or to a separate install of TSM V6 • Upgrade can run using an intermediate media (sequential) or direct network connection • Utility can coexist with TSM V5 • Upgrade process: • Upgrade existing TSM database to V5.5.2 level • Extract from existing V5 database • Insert into new TSM V6 database • Source server is down during extract process • If TSM V5.5.2, existing TSM server can restart • If prior to V5.5.2, the TSM database needs to be restored

  14. TSM V6 Database – Port to DB2 Upgrade with Media Process Source TSM V5 Server Target TSM V6 Server DB2 Sequential Media 2. dsmserv loadformat 3. dsmserv insertdb 1. dsmupgrd extractdb Extractdb/dsmserv insertdb done in separate steps.

  15. TSM V6 Database – Port to DB2 Upgrade with Network Process Source TSM V5 Server Target TSM V6 Server DB2 Network Connection dsmserv loadformat 2a. dsmserv insertdb 2b. dsmupgrd extractdb Extractdb/dsmserv and insertdb done at same time.

  16. Data Deduplication Tivoli Storage Manager V6

  17. TSM Data Deduplication • Only supported with stgpools using devclass=file • Including ADPs • Server-side • No required change to clients or legacy data in storage pools • Duplicates across clients can be identified • V6.1 client will change to identify meta data vs content • Not required, but this will improve the de-dup process on the server • Out-of-band process • Background process • No impact on backup window

  18. TSM Data De-DuplicationConcept 1. Chunk the object • Divide object into logical segments called chunks 2. Identify duplicate chunks • Hash each chunk to produce unique identifier • Compare each chunk identifier with index to determine whether chunk is already stored 3. Eliminate redundant chunks • Update index to reference matching chunks • Deallocate space for redundant chunks 5 5 91 91 17 17 25 25 Chunk identifiers Chunk identifiers Object Chunks Index Index

  19. A A B B A C B C C TSM Data Deduplication Overview Deduplicated disk storage pool stores unique chunks to reduce disk utilization Client 1 Deduplication Server Client 2 Tape copy pool stores A, B, and C individually to avoid performance degradation during restore TSM Database Client 3 Files A, B and C have common data Allows more objects to be stored on disk for fast access

  20. TSM DeduplicationNew Externals • DEFINE / UPDATE STGPOOL stgpoolname DEDUPlicate=No | Yes IDENTIFYPRocess=nn (default number of background processes) • IDentify DUPlicates stgpoolname DUration=mm (minutes to run process) NUMPRocess=nn (override stgpool setting)

  21. TSM Deduplication Considerations • Consider deduplication if • Data recovery would improve by storing more data objects on limited amount of disk • Data will remain on disk for extended period of time • Much redundancy in data stored by TSM (e.g., for common operating-system or project files) • TSM server CPU and disk I/O resources are available for intensive processing to identify duplicate chunks • Deduplication might not be indicated for • Mission-critical data, whose recovery could be delayed by accessing chunks that are not stored contiguously • TSM servers that do not have sufficient resources • Data that will soon be migrated to tape

  22. Real-Time Monitoring and Reporting Tivoli Storage Manager V6

  23. TSM Real-Time Monitoring and Reporting • A new stand-alone monitoring and reporting server based on IBM/Tivoli Monitoring (ITM) and Tivoli Common Reporting (TCR) • Monitoring/Reporting server installs on Windows, AIX, and Linux86 • Monitoring agent installs directly on some server platforms or runs on the monitoring server • Uses Deployment Engine to install all components easily • DB2 • IBM/Tivoli Monitoring/Tivoli Enterprise Portal/Tivoli Data Warehouse • Tivoli Common Reporting and TSM ISC/Admin Center • TSM/TEP Workspaces and TSM/TCR report definitions • During installation, the administrator will select userid's and passwords for each of the ITM/TEP/TDW/TCR components. • No need to license DB2, ITM or TCR separately

  24. TSM Real-Time Monitoring and Reporting TSM Tivoli Common Reporting • Integrated, common-reporting engine that integrates to IBM Tivoli Monitoring (ITM) and Tivoli Data Warehouse (TDW) • Uses an agent to communicate with the TSM server and extract data from the TSM database and return this data to the ITM server to be stored in the TDW database • ITM will act as a monitoring application while the Tivoli Common Reporting (TCR) portion of ITM will report on the retrieved data • TCR uses the Eclipse/BIRT (open-source) engine to report on the data using customized and standardized reporting templates provided by TCR and customized by TSM developers.

  25. TSM Real-Time Monitoring and Reporting Platform Support

  26. TSM Real-Time Monitoring and Reporting

  27. TSM Real-Time Monitoring and Reporting

  28. TSM Real-Time Monitoring and Reporting Using the Event Monitor • ITM workspaces are presented on the Tivoli Enterprise Portal foundation. A number of workspaces will be delivered with the TSM reporting solution. These workspaces will be easily selected from a list of workspaces in the TEP console. Once selected, each workspace will communicate with the TSM agent to retrieve and present data to the user from the selected TSM server. • The user opens the TEP console on their computer desktop • A userid and password will be entered into the TEP console for access to the predefined workspaces • The main TEP screen displayed will present the user with a set of attribute groups and workspaces that they can select to display the appropriate information

  29. TSM Real-Time Monitoring and Reporting Using the Event Monitor

  30. TSM Real-Time Monitoring and Reporting Using the Event Monitor

  31. TSM Real-Time Monitoring and Reporting Using the Reporting Feature • To start TCR, the user will point their browser to a URL in the same as the user points to the Admin Center URL. ISC will request a userid and password to access the TCR product. • The user will be presented, after login, a list of reports available to them in the ISC navigation tree. They will select each report which will then be displayed to them in the ISC console at which time they may choose to save the report in a number of different formats or print the report.

  32. TSM Real-Time Monitoring and Reporting Using the Reporting Feature

  33. TSM Real-Time Monitoring and Reporting Using the Reporting Feature

  34. Individual Mailbox Restore for MS Exchange Tivoli Storage Manager V6

  35. Individual Mailbox Restore for MS Exchange • Perform individual mailbox and item-level recovery operations in Microsoft Exchange Server 2003 or Microsoft Exchange Server 2007 environments using Data Protection for Exchange backups • GUI or Command-line interface • TDP EXCC RESTOREMailbox mailbox_name(s)

  36. Individual Mailbox Restore for MS Exchange • Supports mainstream platforms • Exchange Server 2003 and Exchange Server 2007 • Windows Server 2003, Windows Server 2008 • 32-bit x86 and 64-bit x64 • Uses strictly Microsoft recommended techniques and interfaces • Recovery Storage Groups • Messaging API (MAPI) • Single user interface for: • Storage group, database, mailbox or message restore • Legacy or VSS restores • Full, differential, incremental, and copy restores • Supports existing backup procedures – no changes required • Does not require separate, costly “brick” backups • Mailboxes can be restored from backups made with previous versions of TSM for Mail

  37. Individual Mailbox Restore for MS Exchange

  38. Individual Mailbox Restore for MS Exchange

  39. N-Series and NetApp SnapDiff and SM2T Tivoli Storage Manager V6

  40. N-Series and NetApp SnapDiff • As NAS filers get bigger and bigger, there is a requirement to perform incremental backups of the NAS filesystems • NetApp uses a closed operating system so a TSM client cannot be created or installed • This feature takes advantage of NetApp’s Snapshot Difference API to enumerate the differences between two snapshots • TSM then performs a backup of only the changed files • Not a replacement for a normal incremental backup – some circumstances can result in missed files • Only available with AIX (nfs mount) and Windows (CIFS mount) TSM clients

  41. Get files dsmc incremental –snapdiff H: 5 1 Create snapshot Get changes 2 3 Backup to TSM 6 Populate database 4 N-Series and NetApp SnapDiff TSM Windows or AIX Client N-Series or NetApp TSM Server

  42. N-Series and NetApp SnapDiff New Client Option |--DIFFSNAPSHOT = | CREATE --| >>-------------------------------------------->< |--DIFFSNAPSHOT = | CREATE --| | LATEST --|

  43. N-Series and NetApp Snap Mirror to Tape (SM2T) • NDMP backups of very large NAS devices can be slow • SM2T is a block level movement of a filesystem • Similar to BA Client BACKUP IMAGE command • Data written to tape is a block by block copy of the file system • Disk geometry taken into account • Restoration of traditional volume to unlike geometry can be very slow • SM2T operations are only supported for Netapp and IBM nSeries file servers • Implementation provided by extending NDMP functions

  44. N-Series and NetApp Snap Mirror to Tape (SM2T) The following specific functions will be provided: • Backup a Netapp file system to media using the Netapp NDMP SnapMirror to Tape function. • TSM admin command: BACKUP NODE • Both Direct to tape and TSM Native stgpool using filer-to-server • Retrieve a SnapMirror copy of a Netapp file system • TSM admin command: RESTORE NODE • Display information about SnapMirror copies. • TSM admin command: QUERY NASBACKUP • TSM back-end data movement for SnapMirror copies • Same support as currently provided for NDMP backup images. • BACKUP STGPOOL, MOVE DATA

  45. N-Series and NetApp Snap Mirror to Tape (SM2T) • Admin Command Line only • No BA Client interface, neither Web GUI nor command line • No support through Admin Center • No NDMP differential backup of SnapMirror images • No NDMP Directory level backup using SnapMirror to tape • TSM will not permit an SM2T backup operation on a server virtual filespace mapping • No Generation of a Table of Contents for SM2T images • No NDMP file level restore from SM2T images

  46. N-Series and NetApp Snap Mirror to Tape (SM2T) • Command • BACKUP NODE nodename fsname type=snapmirror • Must be MODE=FULL • Must be TOC=NO • RESTORE NODE nodename fsname [destination_fsname] type=snapmirror • QUERY NASBACKUP nodename fsname

  47. VMware Consolidated Backup Tivoli Storage Manager V6

  48. Primary TSM/VCB Backup VMware Consolidated Backup • 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

  49. VMware Consolidated 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 comprise the entire virtual machine in a set of files that represent the physical disks of the virtual machine and other control information.

  50. VMware Consolidated Backup

More Related