Professional Documents
Culture Documents
Speaker: Chris Dedham, Business Continuity Specialist, Mainline Information Systems Chris Dedham: Hello my name is Chris Dedham and I am a Business Continuity Specialist at Mainline as well as a TSM-certified professional. Today I am going to bring you up to date with TSMs latest release version 6.2.2. The agenda is as follows.
Tivoli Storage, IBM Software Group
Agenda
TSM 6 Benefits (Review from v6.1) TSM 6.2 Updates TSM 6.2.2 Updates TSM 6.3 TSM for Virtual Environments
1993 1994
1995 1996
1997 1998
2003 2004
ADSM V3.1: enhanced UI, improved performance and integration w/ systems management applications
Tivoli Storage Manager (TSM) V3.7, succeeds ADSM ; added enterprise management
TSM 5.5: enhancements to data security, Deeper Windows application coverage, protection of VMware environments and scalability
Since its inception in 1993, TSM has been a leader in disk-to-disk backup and you will see that disk-to-disk backup has been taken to a new level is version 6 of TSM.
Data Center
FastBack
Clients TSM for VE + TSM B/A Virtual Machines
D/R Site
FlashCopy
Manager
IBM System Storage
TSM B/A
Clients
FastBack
Server Tiers of Storage
TSM Server
Explosive data growth along with shrinking backup windows and reduced recovery times has precipitated the deployment of different technologies like block-level backup, snapshots and continuous data protection. The emergence of these new data protection technologies has prompted manufacturers to develop unified recovery management platforms.
* Results will vary depending on users environment, systems/processors, type of data, 2009 IBM Corporation expiration policies, data change rates, etc.
TSM version 6.1 was a significant change to the underlying architecture of TSM version 5 because it replaced the catalog of the TSM server with IBMs enterprise class DB2 relational database system. The introduction of DB2 has brought many improvements to TSM, for example the TSM DB2 database can manage the four times the number of objects that version 5 could allowing the database to scale to 2 terabytes in size versus a practical limit of about 150 gig with version 5. These result in fewer TSM servers to manage the same amount of data, also the recovery log is now 9 times larger.
* Results obtained in lab conditions for multiple clients backing up small files. Customer results will vary 2009 IBMrates, Corporation depending on environment, systems/processors, type of data, expiration policies, data change etc.
Meaning that significantly more jobs can run concurrently allowing more work to be completed in a shorter period of time and the performance of backing up small files and database expiration processes has also improved dramatically.
Tivoli Storage Manager 6 Extended Edition includes data deduplication for sequential-access disk pools, at no extra charge Improves recovery times relative to recovery from tape as many more recovery points can be stored on disk; or reduces the amount of capacity needed Operates as a post-process / no impact on backup performance / automatic space reclamation Complementary with the IBM TS7650G ProtecTIER Gateway
TSM 6 built-in data deduplication and the TS7650G ProtecTIER Gateway can coexist to meet different customer needs
Tivoli Storage Manager 6, combining progressive incremental data capture with data deduplication, does a better job of reducing storage capacity requirements than pure data deduplication solutions
Finally, in an effort to deal with explosive data growth, TSM 6.1 took disk-to-disk backup to a new level by introducing server side data deduplication.
Now let us discuss TSM version 6.2. TSM version 6.2 has delivered on a number of new features and for the sake of time, I will only address a few of these in detail but I will run down the list first. Windows VA client 4 for GPFS 3.3. In the past there was support for only AIX and Linux. Higher limits for transaction byte limit and move size threshold parameters which helped take advantage of high-speed tape drives and the limit has been increased to 32 gig. Windows pass through drivers allow you to install the native Microsoft driver since TSM device drivers are not supported drivers. There are considerations for both approaches, which should be researched before implementing one or the other. Automatic deployment of windows clients, TSM for ERP, which has improved the handling of very large objects, which can reduce the possibility of the TSM recovery log being corrupt, full backup support for Microsoft Hyper V, VSS and simultaneous rights during storage pool migrations and concurrent access to Sentara volumes, which works the same as the concurrent access TSM gate to the file device path in version 5.5, auto discovery of new VMware guests, VCB generation 2 support, which is now called the V storage API for data protection, SSL support and in addition to server side data deduplication, TSM version 6.2 now can do client side deduplication to further reduce the amount of data that must be processed, incremental backups of the systems state can be conducted with can reduce a lot of backup activity especially with Windows 2008.
Incremental forever
Client only sends changed files
Subfile backup
Client only sends changed subfiles
Server-side deduplication
Server eliminates redundant data chunks
Client-side deduplication
Client and server eliminate redundant data chunks Yes Backup, archive, API Redundant data from any files in storage pool Yes
Yes Backup, archive, HSM, API Redundant data within same file on client node No
Yes
Yes Backup (Windows only) Subfiles that do not change between backups No
No Backup, archive, HSM, API Redundant data from any files in storage pool Yes
Scope of data reduction Avoids storing identical files renamed, copied, or relocated on client node? Removes redundant data for files from different client nodes?
No
No
No
Yes
Yes
Available prior to V5
Available 6.1
Available 6.2
The name of the game today when protecting data is data reduction, the less data you have to store, the better your data protection coverage is. TSM has a history of reducing storage requirements with a progressive backup methodology also known as the incremental forever for backup. Now TSM can further reduce storage requirements with its client side and server side data reduplication capabilities.
Benefits:
Deduplication for file and application data Reduce network traffic by deduplicating data before transfer Reduced storage pool space requirements Faster backups Optimized to reduce network chattiness when identifying duplicate data New Backup-Archive Client statistics report on deduplication and data reduction savings
LAN / WAN
Storage Manager 6
Conserves Bandwidth
Saves Storage
Duplicate files or portions of a file are not moved over the network Conserves bandwidth used during backup operations
Only unique files or portions of a file are stored on disk Indexes are used to act as pointers to the original file
TSM client side deduplication uses a file device flat storage pool on the TSM server with de-dupe turned on so redundant data is filtered off before it is sent to the server and there can be many benefits to the setup such as reduced network traffic, faster backups, and reduced storage pool consumption.
1. Client creates chunks 2. Client and server identify which chunks need to be sent
C D
4. Entire file is reconstructed during Backup Stgpool operation to nondeduplicated stg. pool
TSM Client
3. Client sends chunks and hashes to server so that it can represent object in database
File 4
File 2
File 3
File 4
hash Index
One of the benefits of client side deduplication is to provide global de-dupe and so if client B has the same files as client A TSM wont backup the redundant files from client B. Data that is copied from a TSM storage pool to a physical tape is rehydrated.
Storage Manager 6
TSM administrator obtains Windows BA client maintenance release from the FTP site From Admin Center, TSM admin selects a maint. level to be distributed to a list of existing clients
Now existing TSM clients have version 5.4 or higher can be upgraded by the TSM server to version 6.2 in an automated scheduled manner. Distribution of the updated TSM client is managed from the admin. center.
Data flow
Combines windows for migration, storage pool backup, and copy active data
Reduces total time for these operations Frees server resources for other operations
Part of the challenge today is making a DR copy in a timely manner before they pickup. Simultaneous rights will allow you to make the DR copy at the same time you are migrating your data or writing data to the active data pool.
Benefits: Eliminate manual processes for tracking VM guests Low impact backup and recovery
2009 IBM Corporation
Auto discovery of the new VMware guests allow TSM to be aware of new guests that have been added to the ESX server for backup purposes, thereby minimizing the risk of VMs and not being backed up or by reducing the possibility of overloading the system by having to catch up from VMs that have not been backed up at all.
Client1
Extended platform support Linux Solaris HP-UX Available in TSM 5.5: Windows, AIX
SSL
Storage Manager 6
Server
Benefits: Secure data transmission between client and server 256-bit AES encryption for in-flight data Compatible with TSM server- or client-side deduplication Simplified deployment and validation of TSM server certificates
2009 IBM Corporation
There can be a secure transfer of data using SSL, which works well for both server side and client side data deduplication. The TSM database manages their certificates.
Now let us talk about what is new in version 6.2.2 of TSM, the most current release. There is new platform support for automated system recovery which includes Vista, 2008 and Windows 7. There is a VSS writer for ASR and it now relies on the Windows preinstallation environment. Also there are enhancements to the snap-tif function for Netapp, which came out in version 6,2 and there is also a VMware proxy backup for the V Storage API that will allow you to do full VM backups.
Subsequent incrementals
Name of the previous Snapshot retrieved from TSM server TSM client creates a new Snapshot version* Snapshot differencing API compares previous and new Snapshot versions and reports file and directory differences to TSM client, UnicodeNew names are supported (Data ONTAP 7.3.3) TSM client backs up files identified in the report New Snapshot name is stored in the TSM server for use in the next incremental TSM client deletes the previous Snapshot version*
* Initial snapshot is always a full snapshot, use diffsnapshot option on subsequent snapshots
N series
New
Win/Linux Files
Win/Linux Files
19
Snap-tif allows TSM to rapidly backup large quantities of files from Netapp or N series by quickly reading the differences between 2 snapshots. There is support for the non-7 bit ASCII files using TSM client 6.2.2. with data on cap, 7.3.3 or 8.1 with the file access protocol. You can backup files that change, or are new or are deleted without issues. There is expanding support to Linux, Redhat 5.0 and Slice Pen.
Site B
Database
Copy Storage Pool
Database
No special hardware/software required Deduplication gives storage/bandwidth savings All data in primary hierarchy could be replicated, after initially being stored in deduplicated primary pool 1:1 replication only TSM Server in Site B spins up only in a DR scenario
Since TSM uses DB2, DB2 has the ability to conduct log shipping between two databases. This allows the TSM server to replicate its database to another TSM server, which can greatly speed up the ark since the TSM server does not have to have its database resorted.
New TDP
Full VM recovery will be handled in a similar way to what currently exists, other, more granular recovery options will be handled differently, here is an outline of the recovery methodologies.
User access the data on TSM disk storage pool and mounts it locally.
23
Released on March 13 of this year is the new TSM for virtual environments. TSM for VE uses the V storage API to make a single pass of the VMBK while delivering volume image of file level recovery and additionally change block tracking is supported so backups are faster since less data is backed up. The data that is backed up can be deduped by TSMs client side dedupe technology.
New TDP
Full VM recovery will be handled in a similar way to what currently exists, other, more granular recovery options will be handled differently, here is an outline of the recovery methodologies.
Administrator launches the restore UI on the proxy server (or any other windows machine)
User/Administrator maps the mounted volume back to the guest (or any other machine) and performs the restore
24
With TSM for VE it is possible to do an instant restore by immediately accessing the VMVK on the TSM server storage pool.
TSM version 6.3, typically will release TSM version 6.3 in the third quarter of 2011.
Site B
TSM Server B Database
DB2
Storage Hierarchy
Storage Hierarchy
TSM server would replicate all data and metadata for specified nodes to another server, ensuring node completeness and consistency of data/metadata Incremental client data transfer with deduplication to minimize bandwidth consumption Remote TSM server could be hot standby for primary server, for improved RTO Native TSM solution with no dependency on specific storage device Many-to-1 transfer to target server (recovery manageability) Supports dissimilar hardware and configuration at primary and remote sites
Remote vaulting without manual tape transfer Efficient use of bandwidth through deduplicated replication Allows hot standby at remote site
2009 IBM Corporation
It will have several new interesting features and an exciting feature for those who are trying to improve the DR recovery objectives and to get away from handling physical tape will be the TSM server replication at the node level with deduplication and today the TSM server can copy its storage pool to another TSM server or variety but must rehydrate the data first. Now bandwidth can be saved with deduplication and replication can be done at the node level and not at the storage pool level and more importantly DRTSM servers are active for the replicated data at the DR site is readily available.
Before
After
28
Since there is more data in storage pools, TSM databases are getting larger which is therefore taking more time to back them up and today only backup stream can be initiated and so if there are multiple tape drives available they cannot be used to increase the backup throughput of the TSM database.
TSM Reporting
Easier
Installation install, configure and use reporting and monitoring within 2 hours
Automated post-installation configuration Additional out of the box' reports Integrated Cognos reporting engine providing better creation of 'custom reports' capabilities Create a custom report in 30 mins or less
An aggregated view of reporting and monitoring for the entire TSM environment
Ability to build 'custom data collection agents' with the newest IBM Tivoli Monitoring end-user license More TSM data-collection agent performance features
TSM activity log custom-data collection in the TSM data-collection agent
29
Storage Manager 6
Storage Manager 6
Storage Manager 6
Storage Manager 6
In version 6.3 the TSM DB can have parallel streams during the backup process and Tivoli continues to enhance reporting but more of the out of the box reports in the integration of Cognos into Tivoli Common Reporting. TCR can use both BRT and Cognos to create reports from the data warehouse.
Client Updates
Deploy maintenance updates to non-Windows platforms
AIX, Solaris, HP-UX, Linux, Macintosh
AIX
new
Solaris HP Linux
Client updates
Storage Manager 6
Mac
30 2009 IBM Corporation
The popular Windows client deployment from the TSM server has been enhanced to include other operating systems for upgrade and maintenance purposes.
TSM clients will scan system and send processor data to TSM Server TSM server will store processor data and calculate PVU value
Virtualization Capacity (Sub-Capacity) customers are still required to use the IBM License Metric Tool (ILMT) to create, verify, adjust, sign and save reports
2009 IBM Corporation
31
Since TSM licensing is based on the number and type of processors and cores of the servers as protected, customers have had struggles keeping track of the processor counts for TSM licensing purposes. There will be now be a processor value in a report which will help with license compliance. Thank you for attending todays recording on TSM version 6.2.2. Another way of experiencing version 6.2 is in a virtual lab environment that mainline can provide you. You can take TSM for test drives or simply sharpen your skills with the new features TSM 6.2 has offered and if you would like to learn more, dont hesitate to contact us.