Tivoli Storage Manager Sample Architecture - IBM

Tivoli Storage Manager Deduplication Sample Architecture
1. Overview of the architecture
This document provides a sample architecture for data protection using Tivoli Storage Manager (TSM) with a
deduplicated disk-based storage pool on IBM Power hardware running AIX. The architecture also provides a
second storage pool hierarchy for a subset of clients with a traditional backup ingestion to a random-disk
staging pool with daily migration to a tape storage pool.
The system is implemented with two different storage pool technologies (deduplicated disk versus traditional
disk to tape) for the purpose of breadth of test coverage, but also demonstrates the flexibility of TSM in terms
of establishing different storage policies for clients with different business requirements. A new
implementation of TSM can use either one of the storage pool hierarchies individually.
1.1 Deduplication technology
Deduplication technology provides an effective method of reducing the amount of data which TSM needs to
store in storage pools. Detailed information describing the deduplication technology in TSM is available in
the paper Effective Planning and Use of Tivoli Storage manager V6 Deduplication.
1.2 Executive summary
The sample TSM architecture provides a disk-based backup solution that retains data in a deduplicated
storage pool for its entire retention. Data protection is provided for hundreds of clients in the deduplicated
storage pool. The following table summarizes some key points which are detailed in the remainder of the
document:
Key point Summary
• 500 clients are protected with a daily scheduled backup.
Protected clients
• 300 of these clients use a mix of server-side and client-side
deduplication with up to 100 clients using client-side
deduplication.
• 4 TB of storage allocated for the database with 3 TB
TSM database size •
currently used by the database.
2.8 billion objects are being protected (primary copy).
• A secondary copy of every object is being protected in a
copy storage pool.
TSM log sizes • 130 GB for the active log (120 GB assigned).
• 428 GB for the archive log.
• Up to 2TB of new data is ingested into the server each
day (size before deduplication)
Deduplicated storage pool • 83 TB of disk storage is allocated for the deduplicated
storage pool. Of this storage:
o 74TB of data is protected (size before
deduplication) using only 21TB of storage
Networks • 1Gb LAN for client backup ingestion.
• 4Gb SAN for storage.
Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012
Version: 1.0
Page 5 of 21