TSM Sizing Concepts

Advanced Technical Skills (ATS) North America
TSM & TSMVE Sizing Concepts with the TSM Sizer

Tom Hepner Dan Wolfe Advanced Technical Skills November 3, 2011
2011 IBM Corporation
Agenda
Backup-Type Basics
Backup Sizing Basics
TSM Storage Pools

TSM & TSMVE Sizing Factors
Using the TSM Sizer

Sizing vStorage Backup Servers
IBM
2
Basic TSM Sizing Factors

What is the data retention business requirement?
Sizing any TSM environment involves disk, tape
and network. You cannot ignore any of these
Gathering accurate data that details all aspects of

the TSM environment is crucial
Dont confuse sizing with data availability TSM data is retained based on two criteria
IBM
3
Volume of Data Factors

Daily incrementals backup changed & new data Database (DB2, Oracle, etc.) backups are usually
full backups
Daily backup will determine diskpool size
Daily backup, retention period and version settings

determine tapepool & library size
IBM
4
Sizing the Network

Understand the bandwidth limitations for all
network paths (LAN, WAN, SAN)
Bandwidth requirements for all client &

server data movement must be considered All backup/restore events (TSM) All other applications
IBM
5
Sizing TSM Disk Pools

Determine which data will backup to disk and
which data will backup directly to tape Incremental backup of file system data is good
candidate for backup to disk Large files, database backups (DB2, Oracle, etc.) are best for backup to tape
Configure enough disk to handle one day's

backups plus some cushion (10-20%) Avoid Migration during backup.
(Have enough disk.) Factor in compression and deduplication
IBM
6
Sizing the TSM Tape Pools
Tape activities that influence sizing

Daily backups Direct backup to tape Migration from disk Stgpool backup Activedata pool on tape TSM DB backup Reclamation threshold Backupsets & Export/Import Node Replication
IBM
7
Sizing the TSM Tape Pools
Tape components to size

Number of Tape Cartridges Number of Library Slots Number of Tape Drives
IBM
8
Tape Device Best Practices

Always configure at least 2 tape drives
Be sure you configure enough adapters based

on drive and adapter throughput values
Consider parallelism -- more parallelism

usually gives higher throughput -- configure enough drives to support all backup, restore, stgpool backup and DB backup requirements
IBM
9
TSM DB Disk (approximations)

V5: TSM DB will be 5% of the total data
backed up (including versions) V6: 1.5-2 times larger than TSM V5 Specific factors: 1000 bytes for each Backup/Archive file 200 bytes for each Copy,ADP object Add space for projected growth % Add 50% for headroom Factor in mirroring (RAID)
IBM
10
Sizing the TSM RL Disk

Active log contains in-flight transactions Archive log and Failover Archive log consist of
active log data that has not been backed up (Backup DB)
Starting point: Active log space

(see system requirements)
Add space for Deduplication Add space for Reorganization

11
Backup-Type Basics
Full: All data Differential: Only data changed since last full
Incremental: Only changed data since the last full

or incremental
Incremental Forever: Only changed data. Sent to a

backup server (application). (Keeps track of all the backups and can restore all or part of the backup to the needed target.)
12
Backup Sizing Basics

Full Backups can be sized based on a backup
rotation scheme
FIFO - First In First Out GFS - Grandfather Father Son
TOH - Towers of Hanoi
13
TSM Incremental Forever

Copygroup Parameters FREQuency VERExists VERDeleted RETExtra RETOnly MODE SERialization
14

Example:
If you wish to retain all backups for 30 days, set VEREXISTS and VERDELETED to NOLIMIT and RETONLY and RETEXTRA to 30
The actual storage requirement is dependent on

how much data changes daily. Since this is unpredictable, there is no way to predict the exact amount of storage needed
15

However, over several years we have come up with storage prediction strategies. One of these strategies is based on the following: A mature TSM server will eventually reach a state of equilibrium where the amount of daily backups will equal the amount of data expired daily That will be influenced by the daily change rate and data growth rate
16
TSM VE Incremental
DP for VMware uses vStorages incremental
backup. (Fulls and successive incrementals)
Two factors to consider Number of full backups to keep Number of incremental backups between fulls
17
TSM VE Incremental
Example:
If you do 1 full backup each week and 1 incremental backup each day. Each final (monthly) full kept until year end and last monthly full kept for the required number of years. Yearly storage requirements would be 6 incremental and 12 full backups
18
Questions?
19
Using the TSM Sizer
20
TSM Sizer - MS Excel Worksheet Pros Many defaults to speed data entry Quickly calculates disk & tape stgpools,
DB/RL, tape cartridges and more Includes IBM Tape device metrics Provides ballpark values for needed throughput of disk, tape & network Quickly calculates primary stgpool TBs
21
Worksheet Gotchas Copy and Paste Will copy all characteristics of a cell Values Formulas Formats Comments Etc. Will create a link between the source and
target worksheets when copying from another worksheet
IBM
22
Worksheet Gotchas While rows and cells can easily be deleted,

moved, or added; VB macros are not aware of these changes
Use a fresh copy if you see these errors:

#NULL! #DIV/0 (exception) #VALUE! #REF! #NAME? #NUM!
IBM
23
Using the TSM Sizer Storage Data Entry
Note multiple tabs
24
Using the TSM Sizer System Entries
Row #3 is for basic TSM server information
25
Using the TSM Sizer Client Entries
Rows 6 thru 1009 holds client information
26
Using the TSM Sizer Client Entries
Special formatting gives extra info and indicates problems
27
Using the TSM Sizer Storage Totals
Output for new TSM pricing model Primary TBs
28
Using the TSM Sizer Storage Data Totals
29
TSM Sizer DB/RL Estimates
30
TSM Sizer Throughput Estimates
31
Using the TSM Sizer Custom Settings
32
Using the TSM Sizer Advanced Settings
Caution: Only make changes if you are confident!
33
Using the TSM Sizer Converter
Scratch pad for throughput calculations
34
Using the TSM Sizer Starting a new worksheet
35
Use drop-down to choose tape device
36
Select a row where you want to start deleting
37
Using the TSM Sizer TSMVE Features
38
Using the TSM Sizer TSMVE Features
39
Sizing vStorage Backup Servers
40
Scope and Assumptions

Scope: VBS hosts: quantity and configuration Assumptions: Each environment considered is heterogeneous: Average amount of data per VM is consistent Average number of VMs per ESX is consistent TSM server(s) is capable of load from proxies Including backend storage pool devices ESX/I datastore devices/network are capable of load Virtual Machines are at Hardware Level 7 TSM-VE Feature Changed Block Tracking is used
IBM
41
Overview of Sizing Process

Choose a backup plan. Calculate required aggregate throughput (GB/hour). Calculate required number of concurrent backup
processes. Calculate the number of VBS hosts. Check for constraints. Optional: Calculate VBS->TSM Server Write Throughput
IBM
42
Backup Plan
Plan Name Scheduling Complexity Workload Distribution
Batched Fulls
Low
None
Rotating Fulls by ESX Host Rotating Fulls by VM
Meduim
Good
High
Best
43
Batched Fulls (during extended backup window)

All VMs full backup during extended time
E.g., weekend (2 day window) All VMs incremental during week (daily incremental for 5 days)
Advantages:
This is the easiest approach to configure/schedule Least number of TSM schedule definitions required Refer to TSM4VE Schedule Recommendations whitepaper https://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Rec ommendations+for+Scheduling+with+TSM+for+Virtual+Environments
Disadvantages:
Requires dedicated window for full backups of all VMs VBS hosts are sized to accommodate tightest window
44
Batched Fulls Weekend Schedule
45
Batched Fulls Weekday Schedule
46
Rotating Fulls by ESX Host

Full backups are interleaved within incrementals
Scheduled on per ESX host basis:
all VMs in ESX host are either full or incremental depending upon the day
For n day backup cycle:

Full backups for 1/n VMs Incremental backups for (n-1)/n VMs
Advantage:
Distributes backup workload/window throughout the week
Disadvantage:
More complex configuration: Requires more schedule definitions
47
Rotating Fulls by ESX Host
48
Rotating Fulls by Backup Plan

Requires external scheduling tool
E.g., workload scheduler or scripting
Advantage:
Best distribution of workload/backup window throughout week
Disadvantage:
Requires additional tool/scripting
49
Rotating Fulls by Daily Schedule
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
Conclusion:
7 14 days between fulls is a good recommendation
Will always depend upon customers specific requirements
74
Summary
Get good information about the clients you

will backup
Be sure the assumptions you make are valid

and agreed to
Be sure that all the solution components are

properly sized
IBM
75
Questions?
76

TSM Sizing Concepts

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

TSM Sizing Concepts

Enviado por

Direitos autorais:

Formatos disponíveis

Advanced Technical Skills (ATS) North America

TSM & TSMVE Sizing Concepts with the TSM Sizer

2011 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM Storage Pools

Using the TSM Sizer

Advanced Technical Skills (ATS) North America

Basic TSM Sizing Factors

Gathering accurate data that details all aspects of

Advanced Technical Skills (ATS) North America

Volume of Data Factors

Daily backup will determine diskpool size

Daily backup, retention period and version settings

Advanced Technical Skills (ATS) North America

Sizing the Network

Bandwidth requirements for all client &

Advanced Technical Skills (ATS) North America

Sizing TSM Disk Pools

Configure enough disk to handle one day's

Advanced Technical Skills (ATS) North America

Sizing the TSM Tape Pools

Tape activities that influence sizing

Advanced Technical Skills (ATS) North America

Sizing the TSM Tape Pools

Tape components to size

Advanced Technical Skills (ATS) North America

Tape Device Best Practices

Be sure you configure enough adapters based

Consider parallelism -- more parallelism

Advanced Technical Skills (ATS) North America

TSM DB Disk (approximations)

Advanced Technical Skills (ATS) North America

Sizing the TSM RL Disk

Starting point: Active log space

Add space for Deduplication Add space for Reorganization

Advanced Technical Skills (ATS) North America

Incremental: Only changed data since the last full

Incremental Forever: Only changed data. Sent to a

Advanced Technical Skills (ATS) North America

Backup Sizing Basics

FIFO - First In First Out GFS - Grandfather Father Son

TOH - Towers of Hanoi

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM Incremental Forever

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM Incremental Forever

The actual storage requirement is dependent on

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM Incremental Forever

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

2010 IBM Corporation

Advanced Technical Skills (ATS) North America

Using the TSM Sizer

2010 IBM Corporation

Advanced Technical Skills (ATS) North America