Pulse2011 Customer Case Chesapeake Energy Corporation
TSM backups of total 1.4PB from 1560 Servers
5 TSM servers
- 3 Oklahoma City
- 2 Fort Worth
4 Tabe libraries total 34 LTO drives
- 2 Oklahoma City
- 2 Fort Worth
1 80TB XIV in OKC
Quote “XIV is great for TSM”
How TSM reduces managed data in Chesapeake environment
- Incremental Forever
- Compression
- Deduplication at server or client
Other ways to reduce
- Keep fewer backups
- Dont backup
Dedupe what makes sence
Full backups
- DB
- Exchange
- VMware
Incremental Forevers backups
- OS and system state
Other considerations
- Data change rate
- Retention
- Restore reqirements
Selected Oracle backups to dedupe
- Backups are kept fo 2 weeks
- Dedupe at TSM server side
Selected Oracle DB’s about 1TB per day
- RMAN and TDP with compression
- 75% dedupe
350 Windows servers with TSM 6.2 client with client compression
- C-drive and system state
- 5.4TB compresed incremental forever data managed
- After client dedupe -> 2.1TB -> 62% reduction
Cost when not deduping
- Disk space
- Tapes -> onsite and offsite
- Lbrary ceels and tape drives needed
Costs when deduping
- Additional disk space
- Savings -> Less tape -> offsite
- Savings -> Fewer library cells, tape drives
- Savings -> Dedupe is included with TSM (every edition)
AIX used in TSM servers no performance issues with TSM Server side deduplication
Dedupe data that helps meet our Goal. It should:
- Reduce managed space
- Ectend the use of existing HW resources
- Meet and improve restore requirements
- Simpify
- Dedupe is “free”, no additional cost. Comes with TSM
Chesepeake uses capacity based pricing model with TSM. Savings in not needing to count PVUs and took back control of backup costs. Online data grows lke crazy but backup costs are under control and growth is under control by utilizing TSM capabilities.

#ibmpulse