Tivoli Storage Manager Sample Architecture - IBM

Tivoli Storage Manager Deduplication Sample Architecture
• The best practices implementation of separating the activities of data ingestion and server data
maintenance tasks into two distinct windows each day is used. This includes ordering the data
maintenance tasks optimally to avoid resource contention.
• Different disk storage is used for holding the TSM database and TSM storage pools. Faster disk is
used for the database, and less-expensive and slower disk is used for the storage pools.
1.3.1 Deduplicated primary pool
The deduplicated primary storage pool retains backup objects for their entire retention. A majority of clients
ingest backups directly into this storage pool. Of these clients, one-third use client-side deduplication during
backup ingestion. The remaining clients backup without deduplication, allowing the data to be later
deduplicated using server-side deduplication.
The following considerations are used to determine which clients use this storage pool:
• Fast restore times are desired without the delay associated with tape mounts, and data spread
across multiple tapes.
• The data responds well to deduplication in terms of the amount of reduction.
• Objects backed up do not exceed 500GB in size.
• Data is not encrypted on the client.
1.3.2 Random disk storage pool
The remaining clients ingest into a random disk storage pool which cannot use deduplication. This pool is a
temporary staging pool from which data is moved to tape each day using storage pool migration. The staging
pool provides an efficient mechanism for ingesting from a large number of clients without contention for tape
mounts. The following factors determine which clients ingest into this storage pool:
• Clients with large objects (greater than 500GB) which are not suitable for deduplication.
• Lower-priority clients that do not require faster restore times making the lower-cost tape storage more
desirable, or require using encryption.
1.3.3 Tape copy storage pool
The tape copy storage pool is used to support taking storage pool backups of all primary storage pools. The
copies are created using the BACKUP STGPOOL command that incrementally keeps a secondary copy of
every backup object. The tape device is also used for storing backup copies of the TSM database using the
BACKUP DATABASE command. The tapes from the copy storage pool and database backups can be taken
to an off-site location to provide for disaster recovery.
Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012
Version: 1.0
Page 7 of 21