Tivoli Storage Manager Sample Architecture - IBM

Tivoli Storage Manager Deduplication Sample Architecture
1.3 Architecture details
The diagram above illustrates the architecture that includes two primary storage pool hierarchies. The first is
a deduplicated sequential-file storage pool. Data remains in this pool for its entire retention and is never
allowed to migrate to another storage pool. There second storage pool hierarchy using a random disk
storage pool with a tape storage pool as the next pool. This represents the traditional TSM model of
ingesting backups to disk and migrating to tapes. The second hierarchy is used for a subset of clients for
which the use of deduplication is not appropriate. Tape storage is also used to provide a copy storage pool
for creating storage pool backup copies of all of the data in both primary storage pools.
The following summarizes key aspects of the architecture:
• Client backups are ingested over the LAN to one of two primary storage pool destinations.
1. A deduplicated primary file-based disk storage pool is used for a majority of clients with a mix
of both client-side and server-side deduplication. Objects are stored in this pool for their
entire retention.
2. A random disk-based primary storage pool is used as temporary storage during backup
ingestion for a subset of clients. The data is migrated each day to a primary tape storage
pool for the remainder of its retention.
• A tape copy storage pool is used for a storage pool backup copy of all data in the primary storage
pools.
Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012
Version: 1.0
Page 6 of 21