Esg Lab Validation TSM 6.3 Til14047usen

Lab Validation
Report

IBM Tivoli Storage Manager 6.3

Deduplication, Remote Site Recovery, and Scalability
By Tony Palmer, Senior Lab Analyst

November 2012

2012 by The Enterprise Strategy Group, Inc. All Rights Reserved.
Lab Validation: IBM Tivoli Storage Manager 6.3 2
Contents
Introduction .................................................................................................................................................. 3
Background ............................................................................................................................................................... 3
IBM TSM 6.3 ............................................................................................................................................................. 4
ESG Lab Validation ........................................................................................................................................ 7
Boosting Scalability ................................................................................................................................................... 7
Improving Efficiency ............................................................................................................................................... 10
Node Replication and Disaster Recovery ............................................................................................................... 14
Ease of Use and Management ................................................................................................................................ 18
ESG Lab Validation Highlights ..................................................................................................................... 20
Issues to Consider ....................................................................................................................................... 20
The Bigger Truth ......................................................................................................................................... 21
Appendix ..................................................................................................................................................... 22

All trademark names are property of their respective companies. Information contained in this publication has been obtained by sources The Enterprise
Strategy Group (ESG) considers to be reliable but is not warranted by ESG. This publication may contain opinions of ESG, which are subject to change from
time to time. This publication is copyrighted by The Enterprise Strategy Group, Inc. Any reproduction or redistribution of this publication, in whole or in
part, whether in hard-copy format, electronically, or otherwise to persons not authorized to receive it, without the express consent of The Enterprise
Strategy Group, Inc., is in violation of U.S. copyright law and will be subject to an action for civil damages and, if applicable, criminal prosecution. Should
you have any questions, please contact ESG Client Relations at 508.482.0188.
ESG Lab Reports
The goal of ESG Lab reports is to educate IT professionals about data center technology products for
companies of all types and sizes. ESG Lab reports are not meant to replace the evaluation process that should
be conducted before making purchasing decisions, but rather to provide insight into these emerging
technologies. Our objective is to go over some of the more valuable feature/functions of products, show how
they can be used to solve real customer problems and identify any areas needing improvement. ESG Lab's
expert third-party perspective is based on our own hands-on testing as well as on interviews with customers
who use these products in production environments. This ESG Lab report was sponsored by IBM.
Introduction
Data growth continues unabated and at an unprecedented rate. This explosion of data represents a massive
challenge to IT. Data protection has morphed from tactical necessity to strategic imperative. Any impact to business
continuity can threaten an organizations very existence. Tivoli Storage Manager (TSM) from IBM provides a turnkey
solution to a range of data protection issues. IBM TSM software is a client/server software solution providing
backup/recovery, archive, hierarchical storage management (HSM), and disaster recovery (DR). This ESG Lab
Validation focuses on key improvements in the TSM platform that drive greater scalability, efficiency, and
availability: support for up to four billion objects per TSM backup server, embedded client and server side data
deduplication, as well as enhanced disaster recovery with TSM node replication.
Background
The impact of datas unfettered growth on its protection is an issue that has IT managers concerned. The problem
with capacity growth is twofold: can the system accommodate it and can backups be executed in time? The
question with protection is how much is enough? As shown in Figure 1, ESG research shows that the top two data
protection challenges faced by IT organizations are reducing backup times and costs. Nearly half of respondents
cited remote site backup and recovery and keeping pace with data growth as challenges as well.
1

Figure 1. Data Protection Challenges

Source: Enterprise Strategy Group, 2012.
Today, end-users are eyeing new approaches and technologies in hopes of easing the stress on their backup and
recovery environments. Employing disk in the backup process has proven to be a powerful weapon for reducing
pressure on backup windows caused by ever-increasing data growth. While typically used as a temporary cache for
backups on the way to less-costly tape media, the combination of lower disk costs and the desire to comply with
recovery SLAs has prompted many organizations to retain backups longer on diskwith some eliminating tape

1
Source: ESG Research Report, Trends in Data Protection Modernization, August 2012.
36%
36%
37%
38%
42%
42%
42%
47%
49%
50%
56%
0% 10% 20% 30% 40% 50% 60%
Implementing/improving business continuity
Bandwidth availability/cost for transferring
Data protection for virtual environment
Management of data protection environment
Database-/application-specific backup/recovery
Need to improve backup and recovery reliability
Keeping pace with capacity of data to protect
Remote site backup/recovery
Securing confidential data
Need to reduce backup time
Cost(s)
Which of the following would you characterize as challenges with your
organizations current data protection processes and technologies? (Percent of
respondents, N=330)
altogether. The practicality and feasibility of leveraging disk in backup and recovery processes changes dramatically
when capacity optimization technology, such as data deduplication, is applied.
IBM TSM 6.3
IBM Tivoli Storage Manager is a scalable software offering from IBM designed to provide centralized, automated
data protection. TSM software offers not only backup and recovery management, but hierarchical storage
management, and functionality that helps users manage massive amounts of data simply and easily. TSM is
compatible with all modern operating systems, from Windows and Linux, to zOS and offers components tailored for
protection of virtualized environments and business critical applications.
TSM is now available in a capacity-based bundle that includes application agents, VMware backup and advanced
backup technologes. As an example, IBM Tivoli Storage Manager Suite for Unified Recovery includes IBM Tivoli
Storage Manager FastBack, a technology that provides quick point in time recovery for critical Windows and Linux
servers.
IBM TSM has introduced improvements vital to driving down IT costs while improving performance and availability.
Significant enhancements include client-side deduplication introduced in 6.2 in 2010, which can improve overall
deduplication ratios; asynchronous disaster recovery node replication to a warm TSM server at a remote site; and
support for four billion data objects in a single backup server, introduced in TSM 6.3 in November 2011.
Protecting an organizations data from failures is the goal of TSM, which is accomplished by storing backup, archive,
space management, and bare-metal restore data offline. Compliance and disaster recovery data are handled even
more efficiently by TSM 6.3. Protection is provided across a wide range of operating systems running on hardware
as different as notebooks and mainframes.
Progressive incremental backups reduce data redundancy which leads to savings on network bandwidth and
storage pool consumption. TSM uses policy-based automation in tandem with intelligent move-and-store
techniques to ensure data protection while reducing administration effort.
Figure 2 depicts a simplified view of the TSM 6.3 architecture. Each TSM server can now scale to four billion objects
and supports built-in disaster recovery replication. The VMware vStorage API and VSS for Hyper-V are fully
supported for optimized virtual machine protection, and client-side deduplication has been added to further reduce
backup traffic across the wire.
Figure 2. TSM Architecture

Enhancements to TSM since version 6.1 include:
Data Security
Client-side Encryption
1. The TSM Client or API can encrypt data before sending across the wire.
2. Keys can be manually entered each time, stored locally, or created automatically and stored on
the TSM server.
3. Data remains encrypted throughout its entire lifecycle.
SSL Encryption
1. Enables encryption of data in-flight without impact to deduplication
2. Self-generated or externally managed keys are supported.
Native support for encrypted tape systems (application managed encryption)
1. TSM creates a key for each volume the first time it is added to a storage pool. TSM generates a
new key if the volume is emptied or scratched before re-use.
2. Encryption keys are contained in the TSM database.
TSM interoperates with encryption-enabled libraries or external encryption devices.
TSM and Tivoli Key Lifecycle Manager can be utilized together to meet more stringent key management
requirements.
Centralized Monitoring and Management
Centralized Monitoring and Management is included in TSM.
Multiple TSM and TSM FastBack Servers can be managed from a single location.
TSM FastBack for Workstations Central Administration Center for workstation backups can be included on
the management host.
Near real-time monitoring of the TSM Infrastructure
Advanced reporting with Cognos
Numerous pre-defined reports in addition to customized reporting capabilities
Ease of Use
Cognos added to Tivoli Common Reporting to enable enhanced TSM monitoring and reporting.
Client Software Updates simplified
1. Windows base client push introduced in TSM 6.2
2. Unix/Linux base client push introduced in TSM 6.3, including the ability to push lower-level
client packages, enabling automated update of systems running older versions of TSM clients.
Licensing Compliance Enhancements
1. PVU Counter for CPU Core-based licensing
2. Capacity-based licensing model and capacity reporting utility
Virtual Environment Enhancements
TSM uses the vStorage API for Data Protection to interface with VMware hypervisors or vCenter.
Backup and restore of individual virtual machines, including block-level incremental backup.
Virtual Machine, volume, and file-level restore capability from a single backup.
Offload of backups from the hypervisor to a vStorage backup server (physical or virtual).
Movement of Virtual Machines by vMotion will not break or duplicate backups.
New or moved Virtual Machines are automatically discovered.
TSM has made such significant enhancements in the area of virtualization support that ESG Lab will be examining
TSM for Virtualized Environments (TSM VE) exclusively in an upcoming report.
This ESG Lab report takes a detailed look at version 6.3 to gauge TSMs improved capabilities. ESG Lab audited and
tested scalability, efficiency, disaster recovery, and data encryption.

ESG Lab Validation
ESG Lab performed hands-on evaluation and testing of IBM TSM 6.3 at IBMs labs in Tucson, Arizona. Validation was
performed using a combination of hands-on testing, audits of IBM test environments, and detailed discussions with
IBM TSM experts. ESG Lab began with an examination of the improved scalability of TSM 6.3.
Boosting Scalability
Through version 5.5, TSM used a proprietary back-end database developed specifically for TSM. The database had a
hard size limit of 530 GB, but in practice, users kept their databases much smaller than that for performance and
manageability. For TSM version 6.1, IBM integrated the high performance DB2 database, allowing for far greater
capacity and higher data ingestion rates during backup windows, with simultaneous writes which allow data to be
directed to the optimal storage location to keep data flowing without bottlenecks. Data transfers from large
numbers of clients and/or large clients are handled using optimized WAN, LAN, and SAN data pathways enabling
TSM to choose the best pathway for any given client.
TSM has a long history of providing a highly scalable data protection environment and version 6.3 increases the size
of the database supported in a single server, doubling the number of objects managed, as seen in Figure 3, while
improving performance. Four billion objects can be maintained on a single TSM server, leading to a reduced cost of
ownership with fewer servers to manage. As an organization scales, using TSM can delay or preclude the need for
additional media servers for backup. A central interface oversees backup and multiple TSM backup engine instances
can be run from a single host. In effect, there is no practical limit to the amount of storage TSM can handle in a
storage pool hierarchy. Of course, administrators should always consider hardware, workload, and service level
requirements that might influence scalability as well.
Figure 3. Number of Managed Objects per Server

In addition, a larger maximum size for the TSM database recovery log means the server has more capacity for
concurrent operations, which increases performance. Automated reorganization of the database while server
operations continue provides better database integrity and no need for offline audits. Full-function SQL queries
allow deeper analyses of data.
The TSM server keeps the database updated and catalogued throughout the backup/restore process. The attributes
of client datanumber of versions, retention timeframes, and storage destinationare stored in the database. This
0
500,000,000
1,000,000,000
1,500,000,000
2,000,000,000
2,500,000,000
3,000,000,000
3,500,000,000
4,000,000,000
4,500,000,000
TSM 5.5 2008 TSM 6.1 2009 TSM 6.2 2010 TSM 6.3 2011
Number of Managed Objects
enables TSM to define storage management policies for clients, satisfy recovery requests, and provide advanced
data protection functionality, such as progressive incremental backups.
ESG Lab Testing
ESG lab first examined the scalability of TSM 6.3 by performing numerous backups in a controlled environment
which was configured for DR replication to a simulated secondary site, as shown in Figure 4.
2

Figure 4. TSM Scalability Test Bed

A number of large backups were run using generated data sets to store sufficient objects to cross the four billion
object threshold. As shown in Figure 5, when enough backups had run to store 4,200,000,000 objects, the database
had grown to 4.22 TB. IBM best practices dictate that a TSM environment configured for DR should be able to
complete a full TSM database backup (copy) in less than ten hours. ESG Lab confirmed that the backup for this 4 TB
database completed in only five hours.
Figure 5. The TSM Database Scaling to More Than 4TB

Finally, ESG Lab connected to a running TSM 6.3 system in IBMs Client Environment Test (CET) lab. The CET lab is
used to test TSM against large numbers of clients with large, dynamic data sets modeled after real customer
environments. As seen in Table 1, this particular server is running a DB2 instance 3.02 TB in size and was managing
protection of approximately 2.85 billion objects for 289 TSM clients.

2
Configuration details can be found in the Appendix.

Table 1. TSM Scalability in the CET Environment

Measurement Result
Objects Stored 2,856,998,897
TSM Database Size 3.02TB
Total Data in Deduplicated Storage Pools 75TB
Physical Storage Consumed in Deduplicated storage
pool
20TB
Total Data in non-Deduplicated Storage Pools 41TB
Daily Ingest of New Data (Before Deduplication) 300GB - 2TB
Clients Protected 289
This test was designed as a long running test to evaluate how TSM manages the following workloads:
Source-side deduplication of 80 clients
Server-side deduplication of a different set of 159 clients
Ingest to random disk staging with migration to tape of another 50 clients
Secondary DR copy with storage pool backup to tape of all objects

This environment was established by IBM in 2008 just before the release of TSM 6.1. It had one full backup at that
time and has been backed up seven days a week using progressive incremental backups from that time to the
present, approximately four years. Using the assumption that the first full backup was about 1TB, ESG Lab
estimates the total protected data to be approximately 1.4PB. Considering that the physical space consumed is only
61TB, the overall data reduction rate is approximately 95.8%.
A more complete view of data reduction rates users can expect with both progressive incremental and
deduplication enabled is explored in the next chapter and documented in Table 2. It's important to note that
deduplication ratios are highly dependent upon the data type. For example, deduplicating the OS drives of a large
number of similar systems will yield a very high deduplication rate, while backing up a transactional database would
yield a lower deduplication rate.
Why This Matters
ESG asked IT managers to identify major challenges with their data protection technologies and processes.
3
The
top two responses were the need to reduce backup times, and the cost of data protection systems. Keeping pace
with capacity of data to protect was also high on the list, cited by 42% of respondents. For years, backup
administrators have been struggling to complete nightly backups before business resumes in the morning. As
backup windows continue to shrink and data sets grow, IT managers need a solution that can scale to meet the
challenge.
ESG Lab has confirmed that TSM 6.3 leverages the DB2 database to deliver significantly greater backup capacity
than previous versions while offering higher availability and advanced functionality. Administrators can potentially
consolidate their TSM environment onto even fewer serversprotecting greater numbers of clients with larger
data sets.

3
Improving Efficiency
For 18 years, TSM has been providing customers with its progressive incremental backup technology. Traditional
backup methodologies use periodic full backups combined with more frequent incremental or differential backups
to conserve storage capacity. This approach makes restores more complex and time consuming as users must first
restore the most recent full backup, then restore subsequent incremental backups to recover to the current point
in time. TSMs progressive incremental backup technology makes one initial full backup, but all subsequent backups
are incremental. When combined with TSMs advanced data management techniques, this enables fast full restores
without the complexity of managing multiple backup sets. Users get the speed and recoverability benefits of a daily
full backup in addition to the reduced network traffic and data storage requirements of incremental backups.
With version 6.1, server-side data deduplication took this one step further. Figure 6 shows a simplified timeline of
backups using both progressive incremental and deduplication technology. Day 1 represents the first full backup, in
which all files are sent to TSM. TSM then applies deduplication to the data set, marking redundant blocks of data
for removal. A separate process (reclamation) deletes the redundant blocks. Day 2 represents the first incremental
backup, in which one new file was added. Just that one file is sent to TSM, which then compares the blocks in the
file to the pool of already stored blocks and marks redundant blocks for removal. Day n represents a future
incremental after a file has been changed. The changed file is sent to TSM, which again compares the blocks in the
file to already stored data in the deduplicated disk pool. The unique blocks are retained and the redundant blocks
are marked for deletion during the next reclamation process. TSM manages the organization and placement of data
so that the backup administrator can select any day and perform a full restore to that point in time without having
to perform multiple passes of full and incremental or differential backups.
Figure 6. Improving Efficiency with Progressive Incremental Backups and Deduplication

With version 6.2, IBM added client-side data deduplication which executes deduplication on data before it is sent to
the TSM server, reducing backup traffic across the wire. Deduplicated DR replication, introduced in version 6.3,
further optimized data reduction and backup/replication bandwidth across the enterprise. Figure 7 shows the
deduplication options in TSM, and where they operate.

Figure 7. Data Deduplication: Client-side, Server-side, and in Replication

ESG Lab Testing
TSM 6.3 was used to perform a backup with client side deduplication and compression enabled on a windows 2008
client. Client-side deduplication was configured in TSM with a single mouse lick, as shown in Figure 8.
Figure 8. Enabling Client-Side Deduplication

The backup was kicked off and monitored using TSM. The detailed status report, seen in Figure 9, shows the status
of the backup process, the compression and deduplication percentages achieved, as well as the total data reduction
for this individual backup. It's important to note that compression and deduplication are operating on the same
backup and providing a combined benefit.

Figure 9. Client-Side Deduplication and Compression

ESG Lab also audited IBMs in-house testing to validate the benefit of deduplication in combination with progressive
incremental technology.
4
During the ten day period examined, IBM performed nearly 500 backups daily against an
11 TB environment containing a mix of data typically found in an enterprise environment, including user files,
VMware images, databases, and Microsoft Exchange data.
Figure 10 shows the combined benefits of progressive incremental backups combined with data deduplication
technology in TSM 6. The red line at the top represents the total data protected, and the blue line indicates the
data actually stored on disk after nightly deduplication and reclamation.
ESG Lab examined the capacity consumed in the file pool after running each backup, deduplication, and
reclamation session. Immediately after the first backup had completed, the full data set was measured at just over
11 TB. After 11 backup jobs, with an average change rate of 2.1% per day, progressive incremental backups in
combination with deduplication had reduced required capacity to only 7.8 TB. The capacity savings over time are
also shown in Figure 10. In this example, the combination of TSM progressive incremental backups and data
deduplication reduced disk capacity by a factor of 19:1 after just ten backups.

4
Configuration details can be found in the Appendix.
Figure 10. Cumulative Storage Space Reduction Over Time

Table 2. Cumulative Storage Space Reduction-Detail
Day
Cumulative Data
Protected (TB)
New or
Changed Data
(TB)
Data Stored on
Disk (TB)
Data Reduction Factor
1 11.2 0.0 11.2 0.0%
2 24.2 0.24 11.0 54.5%
3 37.2 0.25 10.4 72.0%
4 50.9 0.25 10.3 79.8%
5 64.8 0.26 10.0 84.6%
6 78.8 0.26 9.0 88.5%
7 93.4 0.27 9.2 90.2%
8 107.5 0.27 9.0 91.6%
9 121.5 0.28 8.2 93.2%
10 135.5 0.28 7.8 94.3%
11 149.6 0.29 7.8 94.8%
At the end of the test period, ESG Lab compared these results to the storage space reduction achieved by
progressive incremental backups alone and found that deduplication had shrunk the final data set by nearly 50%.
What the Numbers Mean
IBMs storage space reduction technologies reduce capacity requirements dramatically while providing
fast, single-pass restore capability.
After just six incremental backups, data storage requirements were reduced by 90% as compared to daily
full backups.
Data deduplication enhanced data reduction in TSM by nearly 50% over progressive incremental backups
alone.
Client-side backups were simple to configure and provided immediate data reduction and reduced traffic to
the TSM server.

Why This Matters
ESG research
5
indicates that cost is the leading challenge in data protection processes and technologies reported by
IT administrators. Storage capacity and WAN bandwidth required for replication can both present significant costs
to organizations trying to implement disaster recovery. Data reduction technologies can change the economics of
backup by reducing the cost of storage required to retain backups on disk and reducing the amount of data that
needs to be sent across the wire.
ESG Lab has validated that progressive incremental backups and ubiquitous data deduplication in IBM TSM can be
used to significantly reduce disk capacity while enabling administrators to apply deduplication appropriately to
address data type and retention needs. Using client-side, server-side, and replication deduplication, TSM
administrators can effectively provide high performance backup and recovery with disaster recovery services, using
greatly reduced disk capacity and minimal network bandwidth. This lowers the cost per GB for backup data and
enables companies to retain data exponentially longer for recovery purposes while minimizing the impact of
deduplication on backup windows and recovery SLAs. The inclusion of deduplication in TSM EE at no additional cost
adds to the value delivered to users.

Node Replication and Disaster Recovery
TSM 6.3 has introduced built-in disaster recovery node replication between TSM servers, allowing a hot TSM server
disaster recovery configuration. With enhanced disaster recovery replication, TSM 6.3 extends native deduplication
by replicating deduplicated data when data resides in native deduplication-enabled storage pools on both source
and target sides. When replicating between devices that provide DR services, such as IBM ProtecTIER, a warm TSM
server at a disaster recovery site allows data and metadata replicas to be kept in sync using DB2's high availability
disaster recovery (HADR) capabilities. TSM also integrates to use electronic or physical vaulting with a cold TSM
server, so the system can manage the creation of physical copies of the data. A single TSM server can support any
combination of all three DR server types if different types of data need different types of recovery after a disaster.
TSM keeps track of the physical location or media, and so will know what data is available during a disaster. All of
these technologies are tightly integrated into a comprehensive data protection offering, as illustrated in Figure 11.

5
Figure 11. IBM Data Protection Across the Enterprise

ESG Lab Testing
ESG Lab walked through a configuration of node replication for the primary data center TSM server, named
BACKUPS_HQ in this environment, configured with deduplicated storage pools, to get a feel for what it would take
to set up a hot TSM server DR environment. In the Tivoli Integrated Portal, ESG Lab clicked on the Manage Servers
tab, and then General. As seen in Figure 12, the BACKUPS_EAST server was configured as the target replication
server.
Figure 12. Managing Node Replication

Under Tivoli Storage Manager each source TSM server can replicate to one other TSM server. Many-to-one
replication is supported where multiple TSM source servers all replicate to the same target.
Next, ESG Lab clicked on Client Nodes and was treated to a list of every server under management by TSM, shown
in Figure 13. Replication can be enabled, executed, or configured from this screen with one click. ESG Lab simply
clicked Enable Replication.
Figure 13. Enabling Node Replication

ESG Lab next executed a series of backups. As backups completed, data was automatically replicated to the hot
TSM server. Finally, a disaster was simulated by disabling the source server and promoting the target to read-write
to access the backups. When a client executed a restore on a backup from the previous step, TSM automatically
connected to the hot standby server, as seen in Figure 14.
Figure 14. Client Connection after Failover

Why This Matters
Offsite copies of backup data are needed to ensure that an organization can recover from a disaster.
Organizations with large amounts of backup data protected by legacy backup and recovery solutions havent
been able to afford to make offsite copies of backup data electronically due to the high cost of WAN bandwidth.
ESG research
6
indicates that 76% of organizations cannot tolerate more than four hours of downtime for their
most critical applications without significant adverse business impact; restoring from tapes that have been
moved offsite can take 24 hours or more as tapes must be shipped from the storage center before restores can
even begin.
ESG Lab has verified that TSM enhanced DR replication enables disaster recovery for deduplicated data sets
from a live source server to a hot standby server. In ESG Lab's tests, this represented a significant reduction of
the amount of data that needed to be transmitted across the wire. In this example, a 149.6TB Data set was
replicated to a second TSM server by moving only 7.8TB of data, a 94.8% reduction. TSM also provides seamless
and transparent restores for clients when a disaster is declared.

6
Ease of Use and Management
TSM has introduced numerous ease of use and management enhancements in since TSM 6.1, including automated
client deployment for Windows systems in version 6.2, and in 6.3 that capability was extended to Unix and Linux
systems.
ESG Lab Testing
ESG Lab selected Manage Client Auto Deployments under Manage Servers in the TSM Integrated Portal. As shown
in Figure 15, the import location was defined as a shared folder on a file server in the test bed environment that
contained TSM client software and the CLIENT DEPLOYMENT storage pool was assigned as the repository for the
client software inside TSM.
Figure 15. Client Auto Deployment Configuration

Figure 16 shows the client auto deployment schedule screen. ESG Lab pulled down the select action menu and
clicked View Deployment Results.

Figure 16. The Client Auto Deployment Schedule

As seen in Figure 17, one client had been successfully updated to version 6.3.0.0 to version 6.3.0.16.
Figure 17. The Client Auto Deployment Schedule

Why This Matters
More than 40% of enterprises asked by ESG Lab identified management of their data protection environment as a
significant challenge.
7
Data protection solutions need to provide tight integration and easy management of local
and remote clients to manage a modern distributed enterprise.
ESG Lab has validated through hands on testing that TSM 6.3 provides quick and easy management of any size
environment from a single pane of glass and automates deployment of client software across Windows and
Unix/Linux environments, providing more efficient management and faster time to backup/recovery.

7
ESG Lab Validation Highlights
TSM 6.3 progressive incremental backup, combined with client- and source-side data deduplication
technology provided an impressive 95% data reduction factor (more than 19:1) over just 11 days of
backups.
DB2 continues to provide an enterprise-class, scalable back-end for TSM. ESG Lab confirmed that TSM 6.3
can scale to more than four billion objects under management while providing higher performance and
more functionality.
TSM 6.3 offers hot TSM server disaster recovery, and demonstrated the ability to replicate deduplicated
data sets from a live TSM server to a hot standby server. TSM 6.3 provided seamless and transparent
restores for clients after failover.
TSM 6.3 showed many improvements to ease of use and management. The Tivoli Integrated Portal (TIP)
provided a common repository for all TSM interfaces, with a single pane of glass for management of an
enterprise TSM environment. ESG Lab also tested automated client deployment, with no scripting or
manual commands needed.

Issues to Consider
Under Tivoli Storage Manager each source TSM server can replicate to one other TSM server. While a
replication scenario is supported where multiple TSM source servers all replicate to the same target (many
to one), a one-to-many configuration, with a source server replicating to multiple targets, is not supported
in TSM 6.3.
The Bigger Truth
IBM has continually invested in the TSM platform, recognizing its standing on the cutting edge of data protection.
TSM has been uniquely positioned for open systems data managementprotecting, retaining, and ensuring
accessibility to data. TSMs architecture and design principles were rooted in mainframe storage management
concepts, distinguishing it from comparable solutions with features such as integrated archiving, disk-to-disk
backup, and progressive incremental backup policies. These and other features are proof points of the level of
optimization in the TSM platform. With TSM 6.3, IBM has pushed the envelope again, to meet and exceed the
demands of organizations grappling with relentless growth in digital information.
ESG Lab performed hands-on testing of key TSM 6.3 features to demonstrate and audit its capabilities. ESG Lab
tested client-side data deduplication to understand the value of this capacity optimization technique in
combination with deduplicated storage pools and progressive incremental backups over time. ESG Lab found that
the two technologies (deduplication and progressive incremental backups) working in concert were able to achieve
90% data reduction after just six incremental backups and 95% reduction after ten backups. Replication is also now
fully integrated with deduplication, optimizing bandwidth for disaster recovery.
With the inclusion of DB2 as the underlying TSM relational database in version 6.1 in 2009, ESG Lab verified active
TSM 6.1 installations with databases in excess of 700 GB, managing hundreds of millions of objects, significantly
larger than anything possible with previous versions of TSM. With version 6.3, ESG Lab verified the ability to
support databases in excess of 4 TB in size, managing more than four billion objects. As ESG Lab observed in
previous testing, this does not appear to represent an upper limit, and there is every reason to assume that TSM
will continue to scale.
ESG Lab continues to believe that the TSM platform achieves optimization in data management in multiple,
powerful ways. The solution creates capacity efficiencies through integrated archiving, disk-based data protection,
an incremental forever strategy, and data deduplication everywhere. Similarly, IBM has been and continues to be
focused on backup and recovery performance, ease of management, and availability. Optimizations, including
integration of the DB2 database, help accelerate backup and recovery processes significantly while integrated node
replication simplifies and speeds disaster recovery in distributed enterprise environments. IBM has clearly put a lot
of time and effort into TSM 6.3 and that hard work is paying off for users: IBM has again reinforced TSMs position
as a preeminent enterprise data protection platform with lots of enhancements for its large existing customer
baseand even more to offer potential new users.

Appendix
Table 3. ESG Lab Test Bed

Deduplication
IBM TSM Server
IBM p550, 16x 2.1GHz POWER5+ cores,
32 GB RAM
4x 4Gb/sec FC HBAs -QLA2340
IBM TSM 6.3
AIX 5.3

IBM XIV 40 TB
IBM DS4000 10 TB
IBM TS3500 Tape Library LTO3

Installation and Upgrade
IBM TSM Server
IBM x336, 2x 3.0GHz XEON CPU, 4 GB RAM
IBM TSM 6.3
Windows 2008 R2
Windows NAS and VMware
IBM TSM Server
IBM x3650, 8x 3.0GHz XEON CPU, 24 GB RAM
2x HBA -QLA2340
IBM TSM 6.3
Windows 2008 R2

IBM N3600 NAS Appliance
IBM DS4800, DS6000
IBM TS3584 Tape Library LTO4
IBM TS3592 VTL

20 Asylum Street | Milford, MA 01757 | Tel: 508.482.0188 Fax: 508.482.0218 | www.esg-global.com

Esg Lab Validation TSM 6.3 Til14047usen

Uploaded by

Copyright:

Available Formats

You might also like

Esg Lab Validation TSM 6.3 Til14047usen

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Esg Lab Validation TSM 6.3 Til14047usen

Uploaded by

Copyright:

Available Formats

Lab Validation

You might also like