Tivoli Storage Manager Sample Architecture - IBM

2.2 Protected data
Tivoli Storage Manager Deduplication Sample Architecture
Item/metric Variations Limit/Range Notes
TSM database (used) 3 TB
Number of stored objects (primary copy) 2.8 billion There is also a storage pool backup copy of
every object.
Total protected data (size
before deduplication
including all versions)
2.3 Data movement
In non-deduplicated
storage pools
In deduplicated storage
pools
41 TB
Total 115 TB
74 TB Stored: 21 TB
Item/metric Variations Limit/Range Notes
Eliminated by deduplication: 53 TB
Objects deleted by expire inventory (daily) 1 - 6 million Typical duration is 350-450 minutes with
resource=8.
Throughput of database backup 240 MB/sec Full backup to LTO5 tapes using three
streams. Typical completion time is 3.5
hours.
Throughput of storage pool
backup
Random disk 108 MB/sec 6 processes.
With deduplication 55 MB/sec 6 processes. Actual rate may be higher. 2
Throughput of reclamation Tape 70 MB/sec 3 processes.
Throughput of duplicate
identification
Throughput of migration,
random disk to tape
File with deduplication 29 MB/sec 6 processes. Actual rate may be higher. 3
46 MB/sec 4 processes.
29 MB/sec 5 processes.
2 Query process output which is used to calculate this rate is based on the reduced size of objects after
deduplication. The actual amount of data copied is higher than what is reported by query process due to
rehydrating data. The actual copy rate is estimated to be 64 MB/sec.
3 Query process output for reclamation of deduplicated data is also based on the reduced object size. The
actual amount of data moved is more than reported which we can estimate to be an overall movement rate of
47 MB/sec.
Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012
Version: 1.0
Page 9 of 21