Tivoli Storage Manager Sample Architecture - IBM

Tivoli Storage Manager Deduplication Sample Architecture
2. Observed performance
Observed performance results are presented in this section based on measurements taken on the sample
architecture in the test lab. This information is provided to serve as a reference during planning a TSM
implementation, and is not intended to be a guarantee of the performance to be expected in a different
environment.
2.1 Data ingestion
Data ingestion is performed over a seven hour backup window.
Item/metric Variations Limit/Range Notes
Protected clients Number of active clients 400-500 There is a variety of client types. 1
Typical session peak 300-500 Clients are divided into groups
with start times staggered at
00:00, 02:00, and 03:00.
New data ingested Number of objects 2-3 million new
objects per day
Break down of daily
ingestion
Object sizes vary, but on average
fall into the small - medium
workload in the range of 1KB -
10MB.
Volume of data 500GB - 2TB Data size represents the size
before deduplication and/or
compression reductions.
Without deduplication
(random disk)
With deduplication
(server)
With deduplication
(client)
Objects inspected with incremental backup
(active set of files queried during incremental)
100-500GB
250GB - 1TB
250GB - 1TB Data size represents the size
before deduplication and/or
compression reductions.
600 million
1 Client workloads primarily include backup-archive clients performing incremental backups. One hundred of
the clients perform client-side deduplication, 200 are processed using server-side deduplication, and the
remaining clients are stored in the random disk to tape hierarchy. The clients also include select TDP clients,
TSM for Virtual Environments, and client image backups.
Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012
Version: 1.0
Page 8 of 21