TSM Sizing Concepts

Advanced Technical Skills (ATS) North America

© 2011 IBM Corporation

TSM & TSMVE Sizing Concepts with the TSM Sizer

Tom Hepner Dan Wolfe Advanced Technical Skills November 3, 2011



Backup-Type Basics

Backup Sizing Basics

TSM Storage Pools

TSM & TSMVE Sizing Factors

Using the TSM Sizer

Sizing vStorage Backup Servers

IBM

Agenda

2



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

Don’t confuse sizing with data availability

TSM data is retained based on two criteria

IBM

Basic TSM Sizing Factors

3



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

Volume of Data Factors

4



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

Sizing the Network

5



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

Sizing TSM Disk Pools

6



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

Sizing the TSM Tape Pools

7



Tape components to size

Number of Tape Cartridges

Number of Library Slots

Number of Tape Drives

IBM

Sizing the TSM Tape Pools…

8



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

Tape Device Best Practices

9



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

TSM DB Disk (approximations)

10



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

Sizing the TSM RL Disk

11



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.)

Backup-Type Basics

12



Full Backups can be sized based on a backup

rotation scheme

FIFO - First In First Out

GFS - Grandfather Father Son

TOH - Towers of Hanoi

Backup Sizing Basics

13



Copygroup Parameters

FREQuency

VERExists

VERDeleted

RETExtra

RETOnly

MODE

SERialization

TSM Incremental Forever

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



DP for VMware uses vStorage’s incremental

backup. (Fulls and successive incrementals)

Two factors to consider

Number of full backups to keep

Number of incremental backups between fulls

TSM VE Incremental

17



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

TSM VE Incremental

18



Questions?

19



Using the TSM Sizer

20



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

TSM Sizer - MS Excel Worksheet

21



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

Worksheet Gotchas

22



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

Worksheet Gotchas…

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

Primary TBs

Output for new TSM pricing model

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



Using the TSM Sizer – Starting a new worksheet…

Use drop-down to choose tape device

36



Using the TSM Sizer – Starting a new worksheet…

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:

VBS hosts: quantity and configuration

Assumptions:

Each environment considered is heterogeneous:

Average amount of data per VM is consistent

Average number of VM’s 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

Scope and Assumptions

41



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

Overview of Sizing Process

42



Backup Plan

Plan Name Scheduling Complexity Workload Distribution

Batched Fulls

Low None

Rotating Fulls by ESX

Host

Meduim Good

Rotating Fulls by VM High Best

43



Batched Fulls (during extended backup window)

All VM’s full backup during extended time

– E.g., weekend (2 day window)

– All VM’s 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 VM’s

– 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 VM’s in ESX host are either full or incremental depending upon the

day

For ‘n’ day backup cycle:

– Full backups for 1/n VM’s

– Incremental backups for (n-1)/n VM’s

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


© 2010 IBM Corporation 51















































Conclusion:

7 – 14 days between fulls is a good

recommendation

– Will always depend upon customer’s

specific requirements

74



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

Summary

75



Questions?

76

Date post:	04-Oct-2014
Category:	Documents
Upload:	craig-lorenz
View:	468 times
Download:	3 times

TSM Sizing Concepts

Documents