Your SlideShare is downloading. ×

Ibm tivoli storage manager v6.1 technical guide sg247718

7,768

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
7,768
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
75
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Front coverTivoli Storage ManagerV6.1 Technical GuideLearn the new features and function inTivoli Storage Manager V6.1Detailed installation, upgrade, andcustomization providedMonitoring and reportingenhancement examples Mary Lovelace Gerd Becker Dan Edwards Shayne Gardener Mikael Lindstrom Craig McAllister Norbert Pottibm.com/redbooks
  • 2. International Technical Support OrganizationTivoli Storage Manager V6.1 Technical GuideDecember 2009 SG24-7718-00
  • 3. Note: Before using this information and the product it supports, read the information in “Notices” on page xiii.First Edition (December 2009)This edition applies to Version 6, Release 1, of IBM Tivoli STorage Manager (product number 5698-B22).© Copyright International Business Machines Corporation 2009. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.
  • 4. Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii The team who wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxPart 1. IBM Tivoli Storage Manager introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. IBM Tivoli Storage Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Product positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3 Overview of the development timeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3.1 Upgrade path for clients and servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3.2 Migration guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.4 Overview of new features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.1 Server enhancements, additions, and changes from Version 6.1. . . . . . . . . . . . . . 7 1.4.2 Client enhancements, additions, and changes from Version 6.1 . . . . . . . . . . . . . . 8 1.5 Additional functionality overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.5.1 Tivoli Storage Manager for SAN, additions, and changes . . . . . . . . . . . . . . . . . . 10 1.5.2 Tivoli Storage Manager HSM for Windows Version 6.1, additions, and changes . 11 1.5.3 Tivoli Storage Manager for Space Management, additions and changes. . . . . . . 11 1.6 Additional information about Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . . . . . . 12 Chapter 2. IBM Tivoli Storage Manager for products. . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 IBM Tivoli Storage Manager for Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2 Data Protection for Microsoft Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3 IBM Tivoli Storage Manager for Microsoft SharePoint V6.1 . . . . . . . . . . . . . . . . . . . . . 15 2.4 IBM Tivoli Storage Manager for ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.5 IBM Tivoli Storage Manager for Advanced Copy Services V6.1 and IBM Tivoli Storage Manager for Copy Services V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Part 2. Tivoli Storage Manager enhancements since V5.4 and V5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Chapter 3. Tivoli Storage Manager enhancements provided since V5.5 availability . 21 3.1 SAN Device Mapping for Virtual Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.2 RELABELSCRATCH parameter for Virtual Tape Libraries . . . . . . . . . . . . . . . . . . . . . . 24 3.3 RECLAIMDELAY and RECLAIMPERIOD server options . . . . . . . . . . . . . . . . . . . . . . . 26 3.4 Tivoli Storage Manager HP-UX passthru driver support . . . . . . . . . . . . . . . . . . . . . . . . 27Part 3. Tivoli Storage Manager V6.1 Server enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Chapter 4. Commands, utilities, and option changes . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.1 New server commands, utilities, and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.2 Updated server commands, utilities, and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.3 Deleted server commands, utilities, and options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Chapter 5. IBM Tivoli Storage Manager database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 5.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42© Copyright IBM Corp. 2009. All rights reserved. iii
  • 5. 5.2 Transition to DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5.2.1 Database transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5.2.2 General DB2 configuration items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 5.2.3 Database and log configuration items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.3 Database administration tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.3.1 DB2 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.3.2 DB2 Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.4 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.4.1 Backing up your database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.4.2 Restoring the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.4.3 Increase database space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.4.4 Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Chapter 6. IBM Tivoli Storage Manager Disaster Recovery Manager . . . . . . . . . . . . 121 6.1 Introduction to disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 6.2 Disaster Recovery Manager changes in V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 6.2.1 New system requirements for V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 6.2.2 Recovery plan limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 6.2.3 DRM enhancements for V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 6.2.4 Disaster Recovery Manager exclusions in V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.3 Recovery of a V6.1 Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.3.1 Local disaster recovery of the Tivoli Storage Manager database . . . . . . . . . . . . 128 6.3.2 DR site recovery of the Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . 129 6.3.3 DR site recovery scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 6.4 Data deduplication considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 6.4.1 Data life cycle for a Tivoli Storage Manager server and DRM . . . . . . . . . . . . . . 137 6.4.2 Data life cycle for a Tivoli Storage Manager server and DRM including deduplicated storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 6.5 Seven tiers of disaster recovery solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 6.5.1 A breakdown of the seven tiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 6.5.2 Selecting the optimum Disaster Recovery solution. . . . . . . . . . . . . . . . . . . . . . . 142 6.6 Best practices for offsite data vaulting and security . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Chapter 7. Data deduplication in Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . 145 7.1 Introduction to deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 7.1.1 Deduplication approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 7.1.2 Deduplication ratios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 7.1.3 Tivoli Storage Manager V6.1 deduplication overview . . . . . . . . . . . . . . . . . . . . . 148 7.1.4 Should we use Tivoli Storage Manager, or VTL/Filer deduplication? . . . . . . . . . 150 7.2 Implementing deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Chapter 8. No-query restore changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 8.1.1 Proprietary NQR algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 8.1.2 Objectives of the new NQR process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 8.1.3 New NQR process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 8.2 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Chapter 9. Expiration enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 9.1.1 Proprietary expiration algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 9.1.2 Objectives of the new expiration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 9.1.3 Enhanced Tivoli Storage Manager V6.1 expiration algorithm . . . . . . . . . . . . . . . 164 9.2 Externals of the enhanced expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164iv Tivoli Storage Manager V6.1 Technical Guide
  • 6. 9.2.1 Command line changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 9.2.2 Administration Center integration: Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 9.2.3 Administration Center integration: maintenance script . . . . . . . . . . . . . . . . . . . . 168 9.2.4 New server messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 9.2.5 Expiration restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 9.2.6 Expiration retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 9.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Chapter 10. Changes to the TXNGROUPMAX default . . . . . . . . . . . . . . . . . . . . . . . . . 177 10.1 Transaction handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 10.1.1 TXNGROUPMAX option examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 10.1.2 Server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 10.2 Implementation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 10.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Part 4. Tivoli Storage Manager V6.1 Client enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Chapter 11. HSM for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 11.2 Automatic threshold migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 11.2.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 11.2.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 11.2.3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 11.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Chapter 12. Active Directory Object Item Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 12.1 Active Directory overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 12.2 Version 6.1 Client Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 12.2.1 Design limitations for restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 12.2.2 New client commands and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 12.2.3 New client options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Chapter 13. Client restore statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 13.1 QUERYSUMMARY option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 13.2 QUERYSUMMARY output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Part 5. Complimentary products and NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Chapter 14. N Series support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 14.1.1 Large file system backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 14.1.2 IP address of server interface to receive NDMP backup data . . . . . . . . . . . . . 213 14.2 SnapMirror to Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 14.2.1 How to set up, use, and control SnapMirror to Tape for backup. . . . . . . . . . . . 217 14.2.2 How to restore a NAS Volume from SnapMirror to Tape backup . . . . . . . . . . . 219 14.3 The snapdiff option for NFS data stored on NetApp filers. . . . . . . . . . . . . . . . . . . . . 220 14.3.1 Overview of SnapDiff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 14.3.2 How the Backup Archive Client interacts with the SnapDiff-API . . . . . . . . . . . . 222 14.3.3 Preparation for using SnapDiff API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 14.3.4 Using snapdiff option to do Incremental Backup for NAS file systems . . . . . . . 225 14.3.5 Hints and tips for troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 14.3.6 Performance issues and test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Chapter 15. IBM Tivoli Storage Manager Data Protection for Mail: Exchange 6.1 . . 235 15.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Contents v
  • 7. 15.1.1 Data Protection for Microsoft Exchange V6.1 on Windows for x86. . . . . . . . . . 236 15.1.2 Microsoft Exchange Server 2003 SP2 or later . . . . . . . . . . . . . . . . . . . . . . . . . 236 15.1.3 Data Protection for Microsoft Exchange V6.1 on Windows for x64. . . . . . . . . . 236 15.1.4 Compatibility issues with earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 15.1.5 Backup methods supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 15.2 Individual Mailbox Restore feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 15.2.1 Individual Mailbox Restore limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 15.2.2 Tivoli Storage Manager 6.1 Mailbox Restore features . . . . . . . . . . . . . . . . . . . 239 15.2.3 Exchange Server: Mailbox Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 15.2.4 Tivoli Storage Manager Mailbox Restore limitations . . . . . . . . . . . . . . . . . . . . . 242 15.2.5 The restoremailbox command line parameter. . . . . . . . . . . . . . . . . . . . . . . . . . 242Part 6. Tivoli Storage Manager V6.1 planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Chapter 16. Installation and upgrade planning for Tivoli Storage Manager V6.1 . . . 245 16.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 16.2 Upgrade strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 16.2.1 What you can and cannot do with Tivoli Storage Manager V6.1 . . . . . . . . . . . 246 16.2.2 Upgrade considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 16.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 16.3.1 System requirements for the V6.1 server system . . . . . . . . . . . . . . . . . . . . . . . 248 16.3.2 System requirements for the V6.1 reporting and monitoring. . . . . . . . . . . . . . . 250 16.3.3 Client environment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 16.3.4 Tivoli Storage Manager Client compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 16.4 Database capacity planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 16.4.1 Overview of the four different log types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 16.4.2 Recovery logs summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 16.5 Planning an upgrade from V5 to V6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 16.5.1 Database restructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 16.5.2 Estimating the upgrade time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 16.5.3 Space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 16.5.4 Work sheet for planning space for the V6.1 server . . . . . . . . . . . . . . . . . . . . . . 263 16.5.5 High level process for upgrading the server to V6.1 . . . . . . . . . . . . . . . . . . . . . 263 16.6 Naming best practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 16.7 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 16.8 Upgrading an existing system versus a new system. . . . . . . . . . . . . . . . . . . . . . . . . 266 16.8.1 Comparison of methods for moving data to the V6.1 database . . . . . . . . . . . . 267 16.8.2 Details of the database upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 16.8.3 Tivoli Storage Manager V6.1 upgrade utilities . . . . . . . . . . . . . . . . . . . . . . . . . 274 16.9 Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 16.9.1 Scenario 1: New system, media method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 16.9.2 Upgrading the server using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 16.9.3 Scenario 2: New system, network method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 16.9.4 Upgrading using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 16.9.5 Scenario 3: Same system, media method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 16.9.6 Summary of the wizard method scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 16.9.7 Scenario 4: Same system, network method . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 16.9.8 Upgrading the server using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 16.9.9 Hybrid upgrade migration method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 16.10 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 16.10.1 Testing the upgrade process for a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 16.10.2 Test by extracting data from a separate copy of the server . . . . . . . . . . . . . . 289 16.10.3 Test by extracting data from the production server. . . . . . . . . . . . . . . . . . . . . 290vi Tivoli Storage Manager V6.1 Technical Guide
  • 8. 16.11 Planning for operational changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 16.12 Why use the database upgrade wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 16.13 An upgrade test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 16.13.1 Upgrading from V5.5 to V6.1, step by step . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 16.13.2 Additional preparation activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 16.14 Modifying the server before the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 16.14.1 Performance tips for the V5 database extraction process . . . . . . . . . . . . . . . 299 16.14.2 Performance tips for inserting data into the V6.1 database . . . . . . . . . . . . . . 300 16.15 Tivoli Storage Manager documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Part 7. Installation, customization, and upgrade of Tivoli Storage Manager V6.1 Server and Client 301 Chapter 17. Installation of Tivoli Storage Manager V6.1 on AIX . . . . . . . . . . . . . . . . . 303 17.1 System requirements for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 17.1.1 Planning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 17.1.2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 17.2 Installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 17.2.1 Prepare the installation source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 17.2.2 Choosing the installation method for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 17.3 Installing Tivoli Storage Manager for AIX software . . . . . . . . . . . . . . . . . . . . . . . . . . 307 17.4 Installation using the console installation wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 17.4.1 Setup of X11 environment for non-graphical environments . . . . . . . . . . . . . . . 311 17.4.2 Installation wizard using X11 redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 17.5 Post-installation steps for Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 316 17.5.1 Preparing the AIX server for Tivoli Storage Manager instances . . . . . . . . . . . . 316 17.5.2 Post-completion tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 17.5.3 Configuring using the dsmicfgx and X11 redirection. . . . . . . . . . . . . . . . . . . . . 333 17.6 Upgrading from Tivoli Storage Manager V6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 17.7 Problem determination and recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 17.7.1 Database queries and validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 17.7.2 Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 17.7.3 Completely removing the Deployment Engine if required . . . . . . . . . . . . . . . . . 347 17.8 Backup considerations for production on V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Chapter 18. Installation of Tivoli Storage Manager V6.1 on Windows . . . . . . . . . . . . 353 18.1 IBM Tivoli Storage Manager planning for installation . . . . . . . . . . . . . . . . . . . . . . . . 354 18.2 System requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 18.2.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 18.2.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 18.3 Planning for space for the V6.1 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 18.4 Tivoli Storage Manager V6.1 components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 18.4.1 Package names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 18.4.2 Package extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 18.4.3 Installing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 18.5 Installing the Tivoli Storage Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . 358 18.6 Installation wizard installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 18.7 Command-line console wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 18.8 Silent mode installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 18.8.1 Silent mode without saving responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 18.8.2 Silent mode saving responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 18.9 Creating directories and user ID for the server instance . . . . . . . . . . . . . . . . . . . . . . 376 18.9.1 Creating the directories for the server instance . . . . . . . . . . . . . . . . . . . . . . . . 376 18.9.2 Creating the user ID for the server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 18.10 Configuring a new Tivoli Storage Manager Server instance . . . . . . . . . . . . . . . . . . 377 Contents vii
  • 9. 18.11 Using the Tivoli Storage Manager configuration wizard . . . . . . . . . . . . . . . . . . . . . 378 18.12 Creating the server instance manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 18.12.1 Manually creating a Tivoli Storage Manager instance . . . . . . . . . . . . . . . . . . 393 18.12.2 Running multiple server instances on a single system . . . . . . . . . . . . . . . . . . 398 18.12.3 Configuring server and client communications . . . . . . . . . . . . . . . . . . . . . . . . 399 18.12.4 TCP/IP options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 18.12.5 Named Pipes options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 18.12.6 Shared memory options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 18.12.7 SNMP DPI subagent options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 18.12.8 Monitoring the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 18.12.9 Network connection types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 18.13 Debugging techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 18.13.1 Investigating log messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 18.13.2 How to completely remove Deployment Engine . . . . . . . . . . . . . . . . . . . . . . . 403 18.14 Gathering logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Chapter 19. Tivoli Storage Manager V6.1 Backup-Archive Client update and installation changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 19.1 Backup-Archive Client updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 19.1.1 New function in Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 408 19.1.2 Related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 19.2 Installation of the Tivoli Storage Manager V6.1 client . . . . . . . . . . . . . . . . . . . . . . . . 411 19.2.1 Migrating from earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 19.2.2 Considerations for migrating between processor architectures . . . . . . . . . . . . 412 19.2.3 Unicode considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 19.2.4 Additional migration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 19.2.5 Upgrading Open File Support or online image . . . . . . . . . . . . . . . . . . . . . . . . . 414 19.2.6 NDMP support requirements (Extended Edition only) . . . . . . . . . . . . . . . . . . . 414 19.2.7 Installing from the Tivoli Storage Manager DVD . . . . . . . . . . . . . . . . . . . . . . . . 415 19.2.8 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 19.2.9 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416Part 8. Tivoli Storage Manager V6.1 monitoring, reporting, ISC, and Administration Center . . . . . . 429 Chapter 20. Monitoring and reporting in Tivoli Storage Manager V6.1 . . . . . . . . . . . 431 20.1 Monitoring and reporting overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 20.1.1 Administration Center: Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 20.1.2 Administration Center: Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 20.1.3 Tivoli Storage Manager Monitoring and Reporting . . . . . . . . . . . . . . . . . . . . . . 434 20.2 Monitoring and reporting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 20.3 Installing the Monitoring and Reporting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 20.4 Business Intelligence and Reporting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Chapter 21. Integrated Solutions Console and Administration Center . . . . . . . . . . . 449 21.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 21.1.1 New installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 21.1.2 Upgrade and co-existence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 21.1.3 Upgrade considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 21.2 Administration Center updates and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 452 21.2.1 Policy Domain configuration panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 21.2.2 Updated Integrated Solutions Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 21.2.3 WebSphere Windows service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 21.3 Administration Center features in V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 21.3.1 Identify managing servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452viii Tivoli Storage Manager V6.1 Technical Guide
  • 10. 21.3.2 Hover help for table links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 21.3.3 Information links for server and Administration Center messages . . . . . . . . . . 453 21.3.4 Maintenance script enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 21.3.5 Client nodes and backup sets enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 453 21.3.6 Centralized server-connection management . . . . . . . . . . . . . . . . . . . . . . . . . . 453 21.3.7 Changes to management-class activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 21.3.8 DRM support for Active Data Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 21.3.9 Health Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 21.3.10 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 21.3.11 Creating a new server instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 21.3.12 Client nodes and backup set enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 467 21.3.13 Maintenance plan enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 21.4 Integrated Solutions Console changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 21.4.1 Tivoli Common Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 21.4.2 Single user ID signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 21.4.3 Credential Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 21.4.4 Manage Global Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 21.4.5 Quick references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 21.5 Additional notes of interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492Part 9. Tivoli Storage Manager V6.1 upgrade consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Chapter 22. Upgrading to Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . . . . . . . 497 22.1 Upgrade strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 22.1.1 The process for upgrading the server to V6.1. . . . . . . . . . . . . . . . . . . . . . . . . . 498 22.1.2 The DSMUPGRD upgrade utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 22.2 Hardware and software server requirements for upgrade. . . . . . . . . . . . . . . . . . . . . 499 22.2.1 Hardware and software requirements for V5 server upgrade . . . . . . . . . . . . . . 500 22.2.2 Upgrade utility additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 22.2.3 Hardware and software requirements for the upgraded server. . . . . . . . . . . . . 502 22.2.4 Server requirements on AIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 22.2.5 Server requirements on HP-UX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 22.2.6 Server requirements on Linux systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 22.2.7 Server requirements for Linux on x86_64 systems. . . . . . . . . . . . . . . . . . . . . . 506 22.2.8 Server requirements for Linux on System z systems . . . . . . . . . . . . . . . . . . . . 508 22.2.9 Server requirements on Sun Solaris systems . . . . . . . . . . . . . . . . . . . . . . . . . . 509 22.2.10 Server requirements on Microsoft Windows systems . . . . . . . . . . . . . . . . . . . 510 22.3 Planning space for the upgrade process and server. . . . . . . . . . . . . . . . . . . . . . . . . 511 22.3.1 Space requirements for the V5 server system . . . . . . . . . . . . . . . . . . . . . . . . . 512 22.3.2 Space requirements for the Tivoli Storage Manager V6 server system . . . . . . 512 22.3.3 Estimating total space requirements for upgrade process and server . . . . . . . 514 22.4 Estimating the upgrade time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 22.4.1 Performance tips for the extraction process . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 22.4.2 Performance tips for inserting data into the V6.1 database . . . . . . . . . . . . . . . 516 22.5 Planning for upgrading multiple servers and components . . . . . . . . . . . . . . . . . . . . 517 22.5.1 Compatibility with servers and components running at earlier versions . . . . . . 517 22.5.2 Planning for upgrading multiple servers on a single system . . . . . . . . . . . . . . . 517 22.5.3 Planning for upgrading library managers and library clients . . . . . . . . . . . . . . . 517 22.5.4 Planning for upgrading clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 22.5.5 Planning for upgrading storage agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 22.6 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 22.7 Preparing for operational changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Chapter 23. Tivoli Storage Manager V6.1 Upgrade Scenarios . . . . . . . . . . . . . . . . . . 521 Contents ix
  • 11. 23.1 The basics of planning the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 23.2 Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 23.3 Upgrading from V5.5 to V6.1 step by step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 23.3.1 Modifying the server before the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 23.3.2 Upgrade steps: V5.5 server to V6.1 on Windows platform . . . . . . . . . . . . . . . . 528 23.3.3 Summary of the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 23.4 Steps after V6.1 server is started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 23.4.1 Initial verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 23.4.2 Database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 23.5 Sample commands to run for database upgrade validation . . . . . . . . . . . . . . . . . . . 557 23.6 Common database maintenance tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 23.7 Scripting and reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 23.7.1 SQL function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 23.7.2 SQL syntax enforcement examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 23.8 How to rollback to V5 if needed or restart the process . . . . . . . . . . . . . . . . . . . . . . . 560 23.9 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 23.10 Gathering logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 23.11 Upgrade for NAS TOC data on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 23.11.1 Steps for the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 23.11.2 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570Part 10. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Appendix A. Configuring ODBC connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 DB2 configuration for ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 ODBC target machine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 ODBC client machine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 ODBC connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Appendix B. DB2 and SQL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 Commands to manage the database environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 Diagnosing and troubleshooting the database environment . . . . . . . . . . . . . . . . . . . . . . . 604 Monitoring the status and health of the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610 Changes to the SELECT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612 LIKE predicate for a nested SELECT statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613 SELECT statements for time calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613 The index_keyseq and index_order columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 Access to database objects using the SELECT command . . . . . . . . . . . . . . . . . . . . . . 614 Table joins and column labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615 Results of the SELECT command for the DISK device class . . . . . . . . . . . . . . . . . . . . 615 Extra spaces appearing in output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616 Appendix C. Recovering from log exhausted conditions . . . . . . . . . . . . . . . . . . . . . . 617 Preparing for the out of log space condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 The server crash scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 Recovering the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 Complete the recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627 IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629x Tivoli Storage Manager V6.1 Technical Guide
  • 12. Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631 Contents xi
  • 13. xii Tivoli Storage Manager V6.1 Technical Guide
  • 14. NoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area.Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service that doesnot infringe any IBM intellectual property right may be used instead. However, it is the users responsibility toevaluate and verify the operation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matter described in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, inwriting, to:IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of those products.This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,cannot guarantee or imply reliability, serviceability, or function of these programs.© Copyright IBM Corp. 2009. All rights reserved. xiii
  • 15. TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both. These and other IBM trademarked terms aremarked on their first occurrence in this information with the appropriate symbol (® or ™), indicating USregistered or common law trademarks owned by IBM at the time this information was published. Suchtrademarks may also be registered or common law trademarks in other countries. A current list of IBMtrademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtmlThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: AIX 5L™ IBM® System i® AIX® MQSeries® System p® DB2® NetView® System Storage™ DPI® OS/390® System z® DS6000™ Passport Advantage® Tivoli® DS8000® POWER5™ TotalStorage® FlashCopy® POWER® WebSphere® GDPS® ProtecTIER® XIV® GPFS™ Redbooks® z/OS® HACMP™ Redbooks (logo) ® zSeries® HyperSwap® SANergy®The following terms are trademarks of other companies:ITIL is a registered trademark, and a registered community trademark of the Office of GovernmentCommerce, and is registered in the U.S. Patent and Trademark Office.Snapshot, Network Appliance, SnapMirror, SnapLock, FlexVol, FilerView, Data ONTAP, NetApp, and theNetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and other countries.Data ONTAP, FilerView, FlexVol, NetApp, Network Appliance, SnapMirror, Snapshot, and the NetworkAppliance logo are trademarks or registered trademarks of Network Appliance, Inc. in the U.S. and othercountries.AMD, AMD Opteron, the AMD Arrow logo, and combinations thereof, are trademarks of Advanced MicroDevices, Inc.SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and othercountries.Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/orits affiliates.ACS, Red Hat, and the Shadowman logo are trademarks or registered trademarks of Red Hat, Inc. in the U.S.and other countries.mySAP, SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in severalother countries.VMware, the VMware "boxes" logo and design are registered trademarks or trademarks of VMware, Inc. in theUnited States and/or other jurisdictions.Java, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, othercountries, or both.Microsoft, Windows NT, Windows, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.Intel, Itanium, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registeredtrademarks of Intel Corporation or its subsidiaries in the United States and other countries.UNIX is a registered trademark of The Open Group in the United States and other countries.xiv Tivoli Storage Manager V6.1 Technical Guide
  • 16. Linux is a trademark of Linus Torvalds in the United States, other countries, or both.Other company, product, or service names may be trademarks or service marks of others. Notices xv
  • 17. xvi Tivoli Storage Manager V6.1 Technical Guide
  • 18. Preface This IBM® Redbooks® publication provides details of changes, updates, and new functions in IBM Tivoli® Storage Manager Version 6.1. We also cover all the new functions of Tivoli Storage Manager that have become available since the publication of IBM Tivoli Storage Manager Version 5.4 and Version 5.5 Technical Guide, SG24-7447. This book is for customers, consultants, IBM Business Partners, and IBM and Tivoli staff who are familiar with earlier releases of Tivoli Storage Manager and who want to understand what is new in Version 6.1. Because we target an experienced audience, we use certain shortcuts to commands and concepts of Tivoli Storage Manager. If you want to learn more about Tivoli Storage Manager functionality, see IBM Tivoli Storage Management Concepts, SG24-7447, and IBM Tivoli Storage Manager Implementation Guide, SG24-5416. This publication should be used in conjunction with the manuals and readme files provided with the products and is not intended to replace any information contained in them.The team who wrote this book This book was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center shown in Figure 1. Figure 1 The team: Dan, Craig, Mary, Mikael, Gerd, Shayne, Norbert Mary Lovelace is a Consulting IT specialist at the International Technical Support Organization. She has more than 20 years of experience with IBM in large systems, storage, and Storage Networking product education, system engineering and consultancy, and systems support. She has written many Redbooks publications about Tivoli lStorage Productivity Center and z/OS® storage products. Gerd Becker is a Project Manager for EMPALIS GmbH, a Premium IBM Business Partner in Germany. He has more than 25 years of IT experience, including over 13 years experience with storage management products such as DFSMS and Tivoli Storage Manager. His areas of expertise include IBM Tivoli Storage Manager implementation projects and education at customer sites, including mainframe environments (OS/390®, VSE, VM, and Linux® for zSeries®). He holds several certifications, including technical and sales, and is an IBM Tivoli Certified Instructor. He has developed and taught several storage classes for IBM Education Services in Germany, Switzerland, and Austria. He has been Chairman of the Guide Share Europe (GSE) user group for more than six years. He is author of the Redbooks publication, IBM Tivoli Storage Manager Technical Guide 5.3, participated in the beta test for Tivoli Storage Manager Version 5.5 and 6.1, and is a member of the Tivoli Storage Manager Advisory Council.© Copyright IBM Corp. 2009. All rights reserved. xvii
  • 19. Dan Edwards is a Consulting I/T Specialist with IBM Global Services, Global Technology Services, based in Ottawa, Canada. Dan has over 31 years experience in the computing industry, including 19 years spent working on UNIX®, High Availability, Tivoli Storage Manager (ADSM), and other storage solutions. He holds multiple product certifications, including MCSE, Tivoli Storage Manager, AIX®, HACMP™, and Oracle. He is also an IBM Certified Professional and a member of the I/T Specialist Certification Board. Dan contracts with IBM clients globally, and over the past seven years, has primarily consulted on Tivoli Storage Manager, High Availability, and Disaster Recovery engagements. Dan has co-authored several books, including IBM Tivoli Storage Manager in a Clustered Environment, SG24-6679, and IBM Tivoli Storage Manager: Building a Secure Environment, SG24-7505. Shayne Gardener is a Tivoli Storage Consultant based in the United Kingdom as a member of the EMEA Global Response Team. He has nearly 20 years of customer facing experience in Computer Support. He has an HND in Computing from Gloucestershire University in Cheltenham, United Kingdom. He has nearly 10 years of service with IBM. His skill areas include IBM Tivoli Storage Manager and its complementary products along with Professional and Technical Certification. He is certified as an IBM Certified Deployment Professional - Tivoli Storage Manager V6.1, an IBM Certified Specialist - Tivoli Storage Manager FastBack V5.5, an IBM Certified Solution Advisor - Tivoli Storage Solutions 2009 and is also certified for the ITIL® V3 Foundation Certificate in IT Service Management. Mikael Lindstrom is a IT Specialist for IBM ITD Sweden working as a team leader for Storage and as a Technology lead for Tivoli Storage Manager. He has nine years of IT experience and has been working for IBM since 2006. Mikael has Tivoli Storage Manager server and client experience on Windows® and AIX platforms since 2002 including three years experience in designing and implementing Tivoli Storage Manager Solutions on Windows and AIX platforms. He has participated in the Tivoli Storage Manager V6.1 Beta program. He is a certified Tivoli Storage Manager Storage Administrator and certified Tivoli Storage Manager Deployment Professional in V5 and V6 and is the Tivoli Storage Manager officer of the Tivoli User Group in Sweden. Craig McAllister is a Tivoli Consultant who has specialized in storage management and closely related topics since 1998. He has worked for IBM United Kingdom since the year 2000 and he supports clients all over the region for presales and services engagements with Tivoli Storage Manager and TotalStorage® Productivity Center. Craig has authored several Redbooks publications, including IBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide, SG24-7447. Norbert Pott is an IBM Tivoli Storage Manager Support Specialist in Germany. He works for the Tivoli Storage Manager back-end support team and provides support to customers worldwide. He has 27 years of experience with IBM, over 18 years of experience in IT, and more than 11 years of experience with the Tivoli Storage Manager product, starting with ADSM Version 2.1.5. His areas of expertise include Tivoli Storage Manager client development skill and in-depth knowledge when it comes to problem determination. He is an author of the Redbooks publications, IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide, SG24-6774, IBM Tivoli Storage Manager Implementation Guide, SG24-5416, IBM Tivoli Storage Management Concepts, SG24-4877, and IBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide, SG24-7447.xviii Tivoli Storage Manager V6.1 Technical Guide
  • 20. Thanks to the following people for their contributions to this project:Barry FruchtmanColin DawsonDonald MoxleyJo LayKen HanniganMatthew AnglinMichael G. SiscoTivoli Storage Manager Server developmentAlexei KojenovStefan BenderTivoli Storage Manager Client DevelopmentAndy RuhlBenjamin SchockertJohn WangTodd OwczarzakWolfgang BeuttlerTivoli Storage Manager Software SupportClare M ByrneGary SpizizenHolly KingLiudyte BakerTivoli Storage Manager Information DevelopmentRoger StakkestadIBM SWG NorwayCyrus NiltchianTricia JiangTechnology Sales EnablementCharles NicholsDave CananRandy LarsonRobert ElderTomas HepnerZong LingPerformance and ATSUrs MoserIntegrated Technology Delivery, Server Systems OperationsAusten M CookTashfique HossainStorage System TestJoerg PohlmannIBM Global Services, CanadaRoger StakkestadIBM SWG Norway Preface xix
  • 21. Peter Kask IBM Innovation Center - Stockholm, Sweden Konstantin Arnold Biozentrum Pharmazentrum Information Technology / Div. of Bioinformatics Swiss Institute of Bioinformatics (SIB) Dieter Unterseher NetApp®Become a published author Join us for a two- to six-week residency program! Help write a book dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will have the opportunity to team with IBM technical professionals, Business Partners, and Clients. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.htmlComments welcome Your comments are important to us! We want our books to be as helpful as possible. Send us your comments about this book or other IBM Redbooks publications in one of the following ways: Use the online Contact us review Redbooks form found at: ibm.com/redbooks Send your comments in an e-mail to: redbooks@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400xx Tivoli Storage Manager V6.1 Technical Guide
  • 22. Part 1Part 1 IBM Tivoli Storage Manager introduction This part of the book provides an overview of the IBM Tivoli Storage Manager and Tivoli Storage Manager for Products.© Copyright IBM Corp. 2009. All rights reserved. 1
  • 23. 2 Tivoli Storage Manager V6.1 Technical Guide
  • 24. 1 Chapter 1. IBM Tivoli Storage Manager overview In this chapter we present an overview of the new functionality and changes that come with the IBM Tivoli Storage Manager Version 6.1. In a separate chapter we detail the cumulative changes in the releases since Version 5.5.0, when the previous Technical Guide was published. We discuss the following major areas of change: Server enhancements, additions, and changes Client enhancements, additions, and changes Additional Tivoli Storage Manager features© Copyright IBM Corp. 2009. All rights reserved. 3
  • 25. 1.1 Overview IBM Tivoli Storage Manager protects data from hardware failures, errors, and unforeseen disasters by storing backup and archive copies on offline and off-site storage. Scaling to protect hundreds to thousands of computers running more than a dozen operating systems, ranging from mobile computers to mainframes and connected together by the Internet, WANs, LANs, or SANs, Storage Manager Extended Editions centralized Web-based management, intelligent data move and store techniques, and comprehensive policy-based automation all work together to minimize administration costs and the impact to both computers and networks. Optional software modules allow business-critical applications that must run 24x365 to utilize Storage Managers centralized data protection with no interruption to their service. Optional software extensions also allow SAN-connected computers to use the SAN for data protection data movements, and provide Hierarchical Storage Management to automatically move unused data files from online disk storage to offline tape storage. Storage Manager Extended Edition expands on the data backup and restore and managed data archive and retrieve capabilities of the base Storage Manager by adding disaster planning capability, NDMP control for NAS filers, and support for large tape libraries. Figure 1-1shows the interrelation of the components in IBM Tivoli Storage Manager. A separate server is optional for the ISC but mandatory for the monitoring and reporting server Integrated Solution IP Network TSM Monitoring and Console with TSM Admin Reporting Center Log Database Storage Servers, Clients, Repository Application systems Storage Area Network ISC Server can be run on the same server as the TSM server TSM Clients TSM ServerTSM Stgpools TSM Monitoring & Reporting Figure 1-1 How the product components interrelate Note: We recommend installing the standard Tivoli Storage Manager Administration Center and Tivoli Storage Manager Monitoring and Reporting on the same server to manage multiple mixed Tivoli Storage Manager Servers.4 Tivoli Storage Manager V6.1 Technical Guide
  • 26. With the initial shipment of the Tivoli Storage Manager V6.1, it was not supported to install additional products that deploy and use DB2® on the same system as the server was running. This restriction has now been partially lifted; check the following Technote for the current status: http://www-01.ibm.com/support/docview.wss?uid=swg21386858 Disaster preparation and recovery Local copies of data do not protect against a local disaster. IBM Tivoli Storage Manager Extended Edition facilitates the tracking of the additional copies of your active data that IBM Tivoli Storage Manager creates for safekeeping at an off-site location. This is known as the Disaster Recovery Manager. IBM Tivoli Storage Manager Extended Edition prepares and keeps up to date a text file, the recovery plan, which contains detailed recovery steps and automated scripts to recover your server. Should a disaster strike and destroy your storage and computers, this plan and the off-site data copies will get your business back up and running quickly.1.2 Product positioning IBM Tivoli Storage Manager and its complementary products provide a comprehensive solution focused on the key data protection activities of backup, archive, recovery, space management, and disaster recovery planning. IBM Tivoli Storage Manager helps ensure recoverability through the automated creation, tracking, and vaulting of reliable recovery points. IBM Tivoli Storage Manager Extended Edition provides the following support: Base IBM Tivoli Storage Manager (for basic backup-archive using a tape library with up to four drives and 48 slots) Disaster Recovery Manager NDMP (for selected network-attached storage devices) Large tape libraries (more than four drives or 48 slots) IBM Tivoli Storage Manager for Storage Area Networks and IBM Tivoli Storage Manager for Space Management can be used with either IBM Tivoli Storage Manager or IBM Tivoli Storage Manager Extended Edition. Additional Tivoli products working in conjunction with Tivoli Storage Manager are described in “IBM Tivoli Storage Manager for products” on page 13. Chapter 1. IBM Tivoli Storage Manager overview 5
  • 27. 1.3 Overview of the development timeline IBM Tivoli Storage Manager started life as ADSTAR Distributed Storage Manager (ADSM). Figure 1-2 shows the release time line for the various versions of ADSM, and its subsequent and present name, IBM Tivoli Storage Manager, up to the current version. TSM V6.1 TSM V5.5 TSM V5.4 TSM V5.3 TSM V5.2.2 er ADSM Marketing/ TSM V5.2 Sales moved from g na IBM Storage TSM V5.1.5 Ma Systems to 03/2009 IBM Tivoli Software TSM V5.1 11/2007 e ag 12/200401/2007 TSM V4.2 r Sto 12/2003 TSM V4.1 li Tivoli Storage o 06/2003 Tiv 10/2002 Manager V3.7 ADSM V3.1 ADSM V2.1 IB M 04/2002 06/2001 ADSM V1.1 07/2000 M ADSM V1.2 DS 09/1999 A 01/1999 1997 1995 1993 Figure 1-2 IBM Tivoli Storage Manager overall product progression1.3.1 Upgrade path for clients and servers Generally, the migration plan for a Tivoli Storage Manager update allows clients and servers to be upgraded at different times. This configuration is supported as long as the older version is supported. Although Tivoli Storage Manager is very flexible as to the versions of client code used, and also functions with most of the old and unsupported client code versions according to their functionality, it is best to follow these rules for updating to Version 6.n. See the announcement letters for more specific examples related to particular versions.1.3.2 Migration guidelines To help prevent disruption to your backup and archive activities during the migration, follow these guidelines: NAS backups performed on a Tivoli Storage Manager Version 6.1 server using the servers BACKUP NODE command can only be restored using the servers RESTORE NODE command or a Tivoli Storage Manager Version 6.1 client. A Tivoli Storage Manager Version 5.5 client can perform backup, restore, archive, and retrieve functions to a Tivoli Storage Manager Version 6.1 server. A Tivoli Storage Manager Version 6.1 client can perform backup, restore, archive, retrieve, and query functions to a Tivoli Storage Manager Version 5.5 server.6 Tivoli Storage Manager V6.1 Technical Guide
  • 28. A Tivoli Storage Manager Version 5.5 Space Management client can perform migrate and recall functions to a Tivoli Storage Manager Version 6.1 server. A Tivoli Storage Manager Version 6.1 Space Management client can perform migrate and recall functions to a Tivoli Storage Manager Version 5.5 server. If you back up or archive data from a Tivoli Storage Manager Version 5.4 or Version 5.5 client to any Tivoli Storage Manager server, you can restore or retrieve that data using a Tivoli Storage Manager Version 6.1 client. This is also true when recalling data that was migrated with the Version 5.4 or Version 5.5 Space Management client. If you back up or archive data from a Tivoli Storage Manager Version 6.1 client, you cannot restore or retrieve that data using a Tivoli Storage Manager Version 5.5 or earlier client. All administrative clients can administer Tivoli Storage Manager Version 5.5 and Version 6.1 servers. The format of the Tivoli Storage Manager passwords stored in the Windows Registry has changed. If you install the Version 5.4.0 or later IBM Tivoli Storage Manager API client or Tivoli Data Protection, which is using the Tivoli Storage Manager API, and you attempt to use the Version 5.3 or earlier IBM Tivoli Storage Manager Backup-Archive client, you will be unable to start the Tivoli Storage Manager Backup-Archive Client Scheduler service or client acceptor daemon service. The method for processing system state data changed in Tivoli Storage Manager Version 5.5, such that system state (and system service) backup from prior clients is supported but is no longer recommended. When you use the Tivoli Storage Manager Version 5.5 client, you will generate new system state backups using the new methods. For operations that you cannot perform, check the following Web site. http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.it sm.client.doc/c_inst_mig_upg.html You can find information about upgrading to and from various versions of Tivoli Storage Manager server and client in the appropriate installation guides. Also, you can check the Tivoli Storage Manager Version 6.1 information center for new installation instructions: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm. nav.doc/t_installing.html Upgrade instructions can be found at the following Web site: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm. nav.doc/t_upgrading.html1.4 Overview of new features This section summarizes the various new features and changes to different Tivoli Storage Manager components. Many of these are covered in greater detail in subsequent chapters of this book. We start with highlights for the most recent version, Version 6.1, then present more specific details for both server and client.1.4.1 Server enhancements, additions, and changes from Version 6.1 This section lists the functional enhancements, additions, and changes for the IBM Tivoli Storage Manager Server introduced in Version 6.1.0. Chapter 1. IBM Tivoli Storage Manager overview 7
  • 29. IBM Tivoli Storage Manager Servers Version 6.1 New features and enhancements are available in the Tivoli Storage Manager Version 6.1 server and related products. Here we summarize these features and enhancements in short, high-level descriptions, so that you can start thinking about the potential benefits to your storage-management operations. The changes introduced in Version 6.1.0 onwards are: Changes to the Version 6.1 Administration Center: Many features in the Tivoli Storage Manager Administration Center Version 6.1 are new for previous users. Data deduplication: Data deduplication is a method of eliminating redundant data in sequential-access disk (FILE) primary, copy, and active-data storage pools. One unique instance of the data is retained on storage media, and redundant data is replaced with a pointer to the unique data copy. The goal of deduplication is to reduce the overall amount of time that is required to retrieve data by letting you store more data on disk, rather than on tape. Storage devices: New device support and other changes to storage devices are available in Tivoli Storage Manager Version 6.1. Disaster recovery manager support for active-data pools: To restore your client systems more quickly and efficiently, you can now use active-data pools in your recovery plans and procedures. EXPIRE INVENTORY command enhancements: The EXPIRE INVENTORY command is now enhanced with new functionality. No-query restore changes: The no-query restore (NQR) function and the internal algorithms responsible for NQR were changed to take advantage of DB2 capabilities and to improve performance. Server database: Tivoli Storage Manager version 6.1 provides a new server database. Advantages include automatic statistics collection and database reorganization, full-function SQL queries, and elimination of the need for offline audits of the database. Support for NetApp SnapMirror® to Tape feature: With Tivoli Storage Manager you can create SnapMirror to Tape images of file systems on NetApp file servers. ODBC driver support: Tivoli Storage Manager Version 6.1 uses the DB2 open database connectivity (ODBC) driver to query the database and display the results. Reporting and monitoring feature: The reporting and monitoring feature uses a combination of the Tivoli Common Reporting tool, IBM Tivoli Monitoring, and the IBM Tivoli Data Warehouse to offer you reports and real time monitoring information about Tivoli Storage Manager servers and client activity.1.4.2 Client enhancements, additions, and changes from Version 6.1 This chapter lists all the functional enhancements, additions, and changes for the IBM Tivoli Storage Manager Backup Archive Client introduced as of Version 6.1.8 Tivoli Storage Manager V6.1 Technical Guide
  • 30. IBM Tivoli Storage Manager Clients Version 6.1Here we list changes introduced with Version 6.1. IBM Tivoli Storage Manager AdministrationCenter. Mac OS X-specific information now included in the UNIX and Linux publication: The Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation and Users Guide includes the Mac OS X-specific information. Mac OS X NLS support: The Tivoli Storage Manager for Mac OS X Backup-Archive Client now supports the NLS languages supported by the Tivoli Storage Manager. Mac OS X API support: The Tivoli Storage Manager API is now supported on Mac OS X. Improved memory usage for backup of Hierarchical Storage Management (HSM) managed file systems: The Tivoli Storage Manager Backup-Archive client can do a full incremental backup of very large HSM managed file systems containing 100,000,000 files or more. UTF-8 encoding support is added for Tivoli Storage Manager UNIX and Linux clients: UTF-8 is added for the language locales that are already supported by the Tivoli Storage Manager Backup-Archive Client. The Tivoli Storage Manager Version 6.1 client message catalogs and help files are encoded in UTF-8. If you are installing Tivoli Storage Manager client message catalogs for languages other than English, you must also have the appropriate iconv UTF-8 converters installed on your system. If the appropriate iconv UTF-8 converters are not installed, all Tivoli Storage Manager client messages will be displayed in English. Availability of 64–bit binaries: The client packages for Linux on POWER®, Linux zSeries, and one of the AIX clients contain 64-bit binaries. NetApp Snapshot™ Difference API (SnapDiff API) support: When used with the incremental command, the snapdiff option streamlines the incremental process by performing an incremental backup of the files reported as changed by the NetApp Snapshot Difference API, instead of scanning the volume looking for files that have changed. Full VM backup and restore support: The Tivoli Storage Manager backup vm command has been enhanced to provide full VM backup capabilities in addition to the file-level backup capabilities previously provided. You can copy full VM virtual disk exports to the backup proxy from snapshots. The entire virtual machine is backed up as a single item, similar to a Tivoli Storage Manager image backup. The exports are broken into 2 GB file chunks that the Tivoli Storage Manager backup-archive client backs up at a file level. Support for restoring Active Directory individual objects: You can use Active Directory individual object recovery and item-level restore during normal day-to-day operations to recover from accidental corruption or deletion of Active Directory objects by restoring one or more individual Active Directory objects. This feature does not require you to shut down or restart the Active Directory server. Chapter 1. IBM Tivoli Storage Manager overview 9
  • 31. The Windows Native GUI has been replaced with the Java™ GUI: The Windows GUI is a Java application. The non-Java Windows Native GUI is installed as dsmmfc.exe in the installation directory. However, it has not been updated with the new Tivoli Storage Manager Version 6.1 features. The querysummary option support: You can use the querysummary processing option to extend the query archive and query backup commands. This support provides a restore preview so that you can determine whether to use the classic or no-query restore method. The srvoptsetencryptiondisabled option support: You can use the srvoptsetencryptiondisabled processing option to ignore encryption options in a client options set from a Tivoli Storage Manager server. Enhanced help facilities: The command-line client help command is enhanced so that you can specify the command, option, or message on which you want help information. In the graphical user interface, message boxes are enhanced with a button that you can click to see detailed message information. New API function dsmUpdateObjEx The dsmUpdateObjEx function call updates the meta information that is associated with backup or archive objects on the server. This provides the ability to select from several archive objects with the same name.1.5 Additional functionality overview This section summarizes the status and new features and changes for different Tivoli Storage Manager components. Tivoli Storage Manager for SAN, additions, and changes Tivoli Storage Manager HSM for Windows Version 6.1, additions, and changes Tivoli Storage Manager Space Management, additions, and changes1.5.1 Tivoli Storage Manager for SAN, additions, and changes IBM Tivoli Storage Manager for Storage Area Networks is a feature of Tivoli Storage Manager that enables LAN-free client data movement. This feature allows the client system to directly write data to, or read data from, storage devices attached to a storage area network (SAN), instead of passing or receiving the information over the network. Data movement is thereby off-loaded from the LAN and from the Tivoli Storage Manager server, making network bandwidth available for other uses. For instance, using the SAN for client data movement decreases the load on the Tivoli Storage Manager server and allows it to support a greater number of concurrent client connections. The storage agent, a component of the feature, makes LAN-free data movement possible. See also the relevant user guide for your system. For AIX it is IBM Tivoli Storage Manager for SAN for AIX Storage Agent Users Guide, Version 6.1, SC23-9797.10 Tivoli Storage Manager V6.1 Technical Guide
  • 32. Enhancements in Version 6.1.0 Enhancements in Version 6.1.0 are as follows: GPFS™ file system support for file device class: With Tivoli Storage Manager for Storage Area Networks Version 6.1, you can use the file-device-sharing software IBM General Parallel File System. Tivoli SANergy® or IBM TotalStorage SAN File System: You can also continue to use either Tivoli SANergy® or IBM TotalStorage SAN File System. IBM General Parallel File System is the preferred option for the operating systems on which it is supported.1.5.2 Tivoli Storage Manager HSM for Windows Version 6.1, additions, and changes IBM Tivoli Storage Manager HSM for Windows provides space management for Microsoft® Windows NTFS file systems. File migration policies can be defined by an administrator using the HSM for Windows GUI. File migration eligibility is determined by include and exclude policy criteria such as file type (extension) and various criteria related to the age of a file (creation, modification, last access). HSM for Windows helps free administrators and users from file system pruning tasks. HSM for Windows is designed to assist administrators to more effectively manage Windows NTFS disk storage by automatically migrating files selected based on administrator established policy to less expensive storage devices, while preserving Windows NTFS file accessibility. See also IBM Tivoli Storage Manager HSM for Windows Administration Guide, Version 6.1, SC23-9795, and Using the Tivoli Storage Manager HSM Client for Windows, REDP-4126. Enhancements in Version 6.1 Enhancements in Version 6.1 are: Automatic threshold migration: Automatic threshold migration helps automatically maintain a certain amount of free space on protected file systems. Support for Microsoft Windows Server 2008 (64 bit) Support for Internet Protocol V6 (IPv6)1.5.3 Tivoli Storage Manager for Space Management, additions and changes The IBM Tivoli Storage Manager for Space Management client for UNIX and Linux (the HSM client) migrates files from your local file system to distributed storage and can then recall the files either automatically or selectively. Migrating files to storage frees space for new data on your local file system and takes advantage of lower-cost storage resources that are available in your network environment. Tivoli Storage Manager for Space Management is available for AIX JFS2 and GPFS, Linux GPFS, Solaris VxFS, and HP-UX JFS file systems. Also refer to the IBM Tivoli Storage Manager for Space Management for UNIX and Linux Users Guide, Version 6.1, SC23-9794-00. Chapter 1. IBM Tivoli Storage Manager overview 11
  • 33. Enhancements in Version 6.1 Enhancements in Version 6.1 are: GPFS 3.2 storage pool support: – Tivoli Storage Manager 6.1 allows multiple General Parallel File System (GPFS) storage pools in one file system. Monitoring a file system includes monitoring each storage pool in the file system. – The automigration command, dmsautomig, permits automatic migration of storage pools and file systems. Hierarchical Storage Management (HSM) for AIX and Linux for GPFS does not require RSCT fileset for cluster support. A new responsiveness service function is being added. It provides: – Node response monitoring – Node failure detection and initiate failover actions – Event notification processing This function replaces the requirement of installing the RSCT Group Services. Do not use RSCT fileset for cluster support. Partial file recall enhancements for optimal tape access: The dsmrecall command will recall partial files with the -OFFset and -SIZE options. With this command, you can specify the portion of a file that is to be recalled.1.6 Additional information about Tivoli Storage Manager V6.1 For full details, always refer to the announcement letter, and to the installation and user guides for the relevant server. Announcement letters include the following information: Detailed product description, including description of new function Product-positioning statement Packaging and ordering details International compatibility information Announcement letters can be found using keyword Tivoli Storage Manager at: http://www-01.ibm.com/common/ssi/index.wss You can see the original Tivoli Storage Manager V6.1 announcement letter at: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=i Source&supplier=897&letternum=ENUS209-004 Information about additional Tivoli Storage Manager V6.1 products can be found at: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=i Source&supplier=897&letternum=ENUS209-088 The Tivoli Storage Manager V6.1 documentation is available at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp12 Tivoli Storage Manager V6.1 Technical Guide
  • 34. 2 Chapter 2. IBM Tivoli Storage Manager for products In this chapter we give you a brief description of the recent changes in the additional IBM Tivoli Storage Manager products: Tivoli Storage Manager for Mail (Microsoft Exchange) Tivoli Storage Manager for Microsoft SharePoint Tivoli Storage Manager for Enterprise Resource Planning (ERP) Tivoli Storage Manager for Advanced Copy Services and Tivoli Storage Manager for Copy Services For further details about the separate products, see the relevant parts of the Tivoli Storage Manager announcement letters as found using the product keywords, for example, Tivoli Storage Manager for Mail, at: http://www-01.ibm.com/common/ssi/index.wss You can also consult the installation and users guides for the different products and platforms at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp Note: Be aware that these products have separate license features. Be sure to register these licences to ensure the desired function.© Copyright IBM Corp. 2009. All rights reserved. 13
  • 35. 2.1 IBM Tivoli Storage Manager for Mail IBM Tivoli Storage Manager for Mail V6.1 consists of the following component: Data Protection for Microsoft Exchange V6.12.2 Data Protection for Microsoft Exchange Server Data Protection for Exchange helps protect and manage Exchange Server data by making it easy to perform the following actions: Back up Exchange Server storage groups and transaction logs. Maintain multiple versions of Exchange Server storage group and transaction log backups. Restore storage group and transaction log backups and replay the transaction log files. Automatically inactivate previous backups when performing a full backup. Data Protection for Exchange performs online backups and restores of Microsoft Exchange Server storage groups. New features Data Protection for Exchange 6.1 provides the new mailbox restore feature. With the Data Protection for Exchange 6.1 mailbox restore feature, you can perform individual mailbox recovery and item-level recovery operations in Microsoft Exchange Server 2003 or Microsoft Exchange Server 2007 environments using Data Protection for Exchange backups. Note: Mailbox restore tracks and stores mailbox location history, which is used to automate mailbox restore operations. This causes a slight delay before each backup. Mailbox restore applies to backups that are taken with Data Protection for Exchange: For Exchange Server 2003 environments, mailbox restore applies to Data Protection for Exchange proprietary backups only. For Exchange Server 2003, mailbox restore operations cannot be performed using VSS backups. For Exchange Server 2007 environments, mailbox restore applies to any Data Protection for Exchange proprietary backups or VSS backups. Data Protection for Exchange 6.1 (and later) maintains mailbox location history. No mailbox location history is available for backups taken with prior versions. When restoring from these prior version backups, if the mailbox to be restored from has been moved or deleted since the time of the backup, the /mailboxoriglocation parameter is necessary. Supported environments The hardware and software requirements for IBM Tivoli Storage Manager for Mail Version 6.1 are documented at: http://www-01.ibm.com/support/docview.wss?&uid=swg2131843414 Tivoli Storage Manager V6.1 Technical Guide
  • 36. 2.3 IBM Tivoli Storage Manager for Microsoft SharePoint V6.1 Customers are increasingly depending on Microsoft SharePoint Portal and Windows SharePoint Services to store, manage and access documents across their enterprise. With this growth of business critical data and content within the SharePoint environment, customers want to manage and protect this data. IBM Tivoli Storage Manager for Microsoft SharePoint allows you to quickly and confidently restore your Microsoft SharePoint business data and content due to a business interruption of almost any kind. New features The following new features are provided: Automatic classification of Microsoft SharePoint content is based on business importance and modification frequency, which allows creation of custom backup plans to help optimize storage space and system resources. A new enhanced graphical user interface (GUI) can streamline user interaction for typical tasks and can improve the end-user experience. Added support is provided for reusable backup templates to assist in the standardization of common backup settings. Item level backup data can be indexed for easier retrieval of data on restore. A new fast backup method is available to help leverage SharePoints change logs. Supported environments The Tivoli Storage Manager for Microsoft SharePoint supported operating systems and system requirements: http://www-01.ibm.com/support/docview.wss?rs=667&uid=swg213782272.4 IBM Tivoli Storage Manager for ERP Tivoli Storage Manager for Enterprise Resource Planning V6.1 provides automated data protection, helps reduce the impact of data backups and restores on the SAP database server, and helps reduce the administrator workload necessary to meet data protection and storage management requirements. It seamlessly integrates with the database-specific utilities of IBM DB2 UDB (db2 admin) and Oracle (RMAN), and with the SAP BR*Tools. Tivoli Storage Manager for Enterprise Resource Planning is specifically optimized to help protect your vital SAP data. An administration assistant helps maximize administrator productivity by helping to simplify administration, configuration, and monitoring of Tivoli Storage Manager for Enterprise Resource Planning in production environments. This powerful solution helps enable administrators to effectively, consistently, and reliably manage backup and recovery of multiple SAP systems with large volumes of data. The Tivoli Storage Manager for Enterprise Resource Planning software module allows multiple SAP database servers to share a single Tivoli Storage Manager server to automatically manage the backup data. As the intelligent interface to SAP databases, Tivoli Storage Manager for Enterprise Resource Planning V6.1 supports heterogeneous environments with large volume data backups, data recovery, data cloning, and disaster recovery of multiple SAP database servers. Tivoli Storage Manager for Enterprise Resource Planning V6.1 has enhancements to take advantage of enhancements in Tivoli Storage Manager for Advanced Copy Services V6.1. Chapter 2. IBM Tivoli Storage Manager for products 15
  • 37. The supported versions of Oracle or DB2 are as supported by SAP, with some restrictions depending on operating system and version. Always consult the announcement letter or the actual installation and user guide for each product for additional details. New features Here we describe the new functions and improvements in IBM Tivoli Storage Manager for ERP V6.1. Note that SAP AG has discontinued the use of the term mySAP in favor of SAP. The following new functionality has been added to Version 6.1 of Data Protection for SAPOracle or DB2: Executable files on Windows platforms (except Java applets) now bear a digital signature. Install Anywhere has replaced Install Shield as the installation vehicle. As of version 7.1, the SAP BR*Tools components have a facility for invoking snapshot (in SAP terminology, volume) backups and restores. Such requests received by Tivoli Storage Manager for ERP are redirected to the Tivoli Storage Manager for Advanced Copy Services (ACS) product (if it is installed). To facilitate the interaction of Tivoli Storage Manager for ACS with Tivoli Storage Manager for ERP when the user wants to perform a Tivoli Storage Manager backup of the snapshots produced, certain parameters have been added to the Tivoli Storage Manager for ERP profile for use by Tivoli Storage Manager for ACS. For more information, refer to the Tivoli Storage Manager for ACS documentation. AIX 6.1 is now supported. Other changes are that: Support for 32–bit platforms has been discontinued. Supported environments The list of IBM Tivoli Storage Manager for Enterprise Resource Planning V6.1.0 requirements is documented at: http://www-01.ibm.com/support/docview.wss?rs=667&uid=swg213218262.5 IBM Tivoli Storage Manager for Advanced Copy ServicesV6.1 and IBM Tivoli Storage Manager for Copy Services V6.1 Tivoli Storage Manager for Copy Services and Tivoli Storage Manager for Advanced Copy Services can help protect your mission-critical data that requires 24 x 7 availability. They offer ready-to-use, application consistent, product-based solutions designed to implement high-efficiency backup and restore processes for business-critical applications, and help to eliminate backup-related performance impact on the production host. By integrating hardware and software-based snapshot capabilities with IBM Tivoli Storage Manager and its data protection components for Microsoft Exchange, Microsoft SQL, IBM DB2 UDB, Oracle, and SAP, you can help manage your snapshot backup operations and leverage the performance, scheduling, and media management functions of Tivoli Storage Manager to help ensure that your application servers are operational 24 hours a day. Tivoli Storage Manager for Copy Services provides the integration with Microsoft Volume Shadow Copy Service (VSS) and VSS providers for snapshots. Tivoli Storage Manager for Advanced Copy Services provides the integration with IBM FlashCopy® as supported by IBM System Storage™ SAN Volume Controller (SVC), IBM System Storage DS6000™, IBM System Storage DS8000®, and other snapshot mechanisms.16 Tivoli Storage Manager V6.1 Technical Guide
  • 38. In todays business world, application servers often are operational 24 hours a day. The dataon the application servers should be well protected. With the rapid increase in the amount ofdata on these servers, their critical business needs, and the shrinking backup windows,traditional backup and restore methods might be reaching their limits in meeting yourchallenging requirements. Snapshot operations can help minimize the impact caused bybackups. Because a snapshot operation typically takes much less time than the time for atape backup, the window during which the application must be aware of a backup can bereduced. The snapshots can be retained as backups on local disk, sent to Tivoli StorageManager server storage pools, or both.New features in Tivoli Storage Manager Advanced Copy ServicesThe following new features are provided: Enhanced Oracle application snapshot support when used in conjunction with the IBM System Storage SAN Volume Controller (SVC), IBM System Storage DS6000, IBM System Storage DS8000, IBM XIV® Storage System, IBM N series NAS, and NetApp NAS. Enhancements include: – Support for multiple snapshot versions – Support for FlashCopy of a single mirror set in LVM mirrored environments – Support for IBM XIV Storage System snapshots Support for FlashCopy restore onto a Peer-to-Peer Remote Copy (PPRC) source volume. PPRC is a continuous disk-based mirroring function typically used for environments requiring high availability disaster recovery. Enhanced snapshot support for SAP environments. Through integration with the Backint interface, integration of Tivoli Storage Manager Advanced Copy Services snapshot functionality into conventional backup procedures in SAP is simplified. Enhanced backup performance by incremental FlashCopy support for the IBM SAN Volume Controller. Tivoli Storage Manager for Advanced Copy Services now exploits incremental FlashCopy. This can eliminate the need to perform a full background copy of the source data for each FlashCopy image that is created. After the initial FlashCopy image is created, only the changed blocks will be copied to the same set of target volumes, improving backup performance.New features in Tivoli Storage Manager for Copy ServicesThe following new features are provided: Updates to take advantage of the enhancements in Tivoli Storage Manager for Mail V6.1. The hardware integration module, previously shipped with Tivoli Storage Manager, has been removed. It is now included with the Tivoli Storage Manager Backup-Archive client.Supported environmentsThe IBM Tivoli Storage Manager for Advanced Copy Services V6.1 requirements aredocumented at:http://www-01.ibm.com/support/docview.wss?rs=3043&uid=swg21321830The hardware and software requirements for IBM Tivoli Storage Manager for Copy ServicesV6.1 are documented at:http://www-01.ibm.com/support/docview.wss?rs=3042&uid=swg21321332 Chapter 2. IBM Tivoli Storage Manager for products 17
  • 39. 18 Tivoli Storage Manager V6.1 Technical Guide
  • 40. Part 2Part 2 Tivoli Storage Manager enhancements since V5.4 and V5.5 This part of the book covers the enhancements and integrated fixes since the previous version of this book was published.© Copyright IBM Corp. 2009. All rights reserved. 19
  • 41. 20 Tivoli Storage Manager V6.1 Technical Guide
  • 42. 3 Chapter 3. Tivoli Storage Manager enhancements provided since V5.5 availability In this chapter we discuss the enhancements in Tivoli Storage Manager since the previous version of this book was published. While the enhancements are included in V6.1, they are described here for completeness and include the following features: SAN Device Mapping for Virtual Tape Libraries RELABELSCRATCH parameter for Virtual Tape Libraries SnapLock® volume reclaim HP-UX Passthru driver support© Copyright IBM Corp. 2009. All rights reserved. 21
  • 43. 3.1 SAN Device Mapping for Virtual Tape Library In a SAN environment, device IDs can change dynamically (for example, device or cabling changes). Tivoli Storage Manager uses a method that dynamically discovers and maps devices in the environment, even when the paths change. Tivoli Storage Manager V5.5 is enhanced to allow for the mapping and discovery of Virtual Tape Library (VTL) devices in the SAN: SAN Device Mapping is done by checking the Serial Number, not by WWN. Some VTLs present the same WWN for all virtual drives. In prior versions, if VTL presented the same WWN for all drives: – When a change was detected in the Serial Number,Tivoli Storage Manager first checked for persistent WWN support in the library. – It assumed that this was a drive swap with persistent WWNs, and thus changed the drive Serial Number and not the device address. In Version 5.5, if VTL presents same WWN for all drives – When a change is detected in Serial Number, Tivoli Storage Manager will first continue to search for the matching S/N before checking for persistent WWNs. – If a match is found, it will update the device address for the drive with that Serial Number. In Example 3-1, you can see the relationship between the WWN and the Serial Number of the VTL to the SAN discovery on the Tivoli Storage Manager Server. Example 3-1 WWN and Serial Number of the SAN Adapters and virtual drives on a VTL 1. Port:- Name: 0a Role: Frontend Port WWNN: 500a09800000de30 Port WWPN: 510a09820000de30 Topology: Link Down Port ID: 0x0 Loop ID: 0x0 2. Port:- Name: 0b Role: Backend Port WWNN: 500a09800000de30 Port WWPN: 510a09830000de30 Topology: Private Loop Port ID: 0xef Loop ID: 0x0 .. lines deleted .. 21. Virtual Drive:- Virtual Library: testpc_vtl Virtual Drive: Drive0 Serial Number: 77e846640f01a098045df0 Vendor ID: IBM Product ID: ULTRIUM-TD4 Barcode: 22. Virtual Drive:-22 Tivoli Storage Manager V6.1 Technical Guide
  • 44. Virtual Library: testpc_vtl Virtual Drive: Drive1 Serial Number: 77e85f960f01a098045df0 Vendor ID: IBM Product ID: ULTRIUM-TD4 Barcode:..lines deleted..Example 3-2 shows how the SAN devices are mapped in Tivoli Storage Manager, which wecan query with the query san f=d command.Example 3-2 Tivoli Storage Manager-command query san f=dq san f=d Device Type: LIBRARY Vendor: NETAPP Product: VTLSerial Number: 77e696d40f01a098045df0 Device: lb0.0.0.3 Data Mover: No Node WWN: 500A09800000DE30 Port WWN: 510A09820000DE30 LUN: 0 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 0 Device Type: DRIVE Vendor: IBM Product: ULTRIUM-TD4Serial Number: 77e846640f01a098045df0Device: Tape0 Data Mover: No Node WWN: 500A09800000DE30 Port WWN: 510A09820000DE30 LUN: 1 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 0 Device Type: DRIVE Vendor: IBM Product: ULTRIUM-TD4Serial Number: 77e85f960f01a098045df0 Device: Tape1 Data Mover: No Node WWN: 500A09800000DE30 Port WWN: 510A09820000DE30 LUN: 2 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 0 Device Type: DRIVE Vendor: IBM Product: ULTRIUM-TD4Serial Number: 77e86ec80f01a098045df0 Chapter 3. Tivoli Storage Manager enhancements provided since V5.5 availability 23
  • 45. Device: Tape2 Data Mover: No Node WWN: 500A09800000DE30 Port WWN: 510A09820000DE30 LUN: 3 SCSI Port: 3 SCSI Bus: 0 SCSI Target: 0 .. lines deleted .. Use this information to check the SAN devices and map them to the corresponding element address. With this new functionality, it is also possible for virtual tape libraries to discover automatically the correct device address and update the path definitions.3.2 RELABELSCRATCH parameter for Virtual Tape Libraries The RELABELSCRATCH parameter allows you to automatically relabel volumes when they are returned to scratch. Support for this parameter is available in Fix Pack 5.5.1 and later levels. Virtual Tape Libraries (VTLs) maintain volume space allocation after Tivoli Storage Manager has deleted a volume and returned it to a scratch state. The VTL has no knowledge that the volume was deleted and it keeps the full size of the volume allocate. This can be extremely large depending on the devices being emulated. As a result of multiple volumes that return to scratch, the VTL can maintain their allocation size and run out of storage space. The only way for the VTL to realize that a volume has been deleted and its space can be reallocated is to write to the beginning of the newly returned scratch volume. The VTL will then see the volume as available. Tivoli Storage Manager can relabel volumes that have just been returned to scratch if the RELABELSCRATCH parameter is specified. This optional parameter has been added to the DEFINE and UPDATE LIBRARY commands and is intended for use with VTLs. It specifies whether the server relabels volumes that have been deleted and returned to scratch. The syntax is: RELABELSCRatch Yes I No When this parameter is set to Yes, a LABEL LIBVOLUME operation is started and the existing volume label is overwritten. Note: If you have both virtual and real volumes in your VTL, both types will be relabeled when this parameter is enabled. If the VTL includes real volumes, specifying this option could impact performance. This function is only available for SCSI Libraries.24 Tivoli Storage Manager V6.1 Technical Guide
  • 46. Example 3-3 shows how virtual tapes will be relabeled when their status is changed toSCRATCH.Example 3-3 RELABEL scratch exampleANR8468I LTO volume TSM0006 dismounted from drive TAPE_DEVICE_2 (mt0.3.0.3) inlibrary TESTPC_VTL.ANR1141I Move data process ended for volume TSM0006.ANR0515I Process 4 closed volume TSM0008.ANR0515I Process 4 closed volume TSM0079.ANR0986I Process 4 for MOVE DATA running in the BACKGROUND processed 155287 itemsfor a total of 50,948,409,476 bytes with a completion state of SUCCESS at05:18:12.ANR0984I Process 5 for RELABEL started in the BACKGROUND at 05:18:17.ANR8799I RELABEL: Operation for library TESTPC_VTL started as process 5.ANR1341I Scratch volume TSM0006 has been deleted from storage pool BACKUP_VTL.ANR8810I Volume TSM0006 has been labeled in library TESTPC_VTL.ANR8801I LABEL LIBVOLUME process 5 for library TESTPC_VTL completed; 1 volume(s)labeled, 1 volume(s) checked-in.ANR0985I Process 5 for RELABEL running in the BACKGROUND completed with completionstate SUCCESS at 05:18:19.To determine if the RELABELSCRATCH parameter is set to Yes, you can issue the QUERYLIBRARY command, as shown in Example 3-4.Example 3-4 QUERY LIBRARY command exampleq libr f=d Library Name: TESTPC_VTL Library Type: SCSI ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: RSM Media Type: Shared: Yes LanFree: ObeyMountRetention: Primary Library Manager: WWN: Serial Number: 77e696d40f01a098045df0 AutoLabel: Yes Reset Drives: Yes Relabel Scratch: YesLast Update by (administrator): ADMIN Last Update Date/Time: 06/17/2009 07:45:36 Chapter 3. Tivoli Storage Manager enhancements provided since V5.5 availability 25
  • 47. 3.3 RECLAIMDELAY and RECLAIMPERIOD server options Two server options, which allow you to set the reclaim delay time and reclaim period time for SnapLock volumes are available. RECLAIMDELAY This option delays the reclamation of a SnapLock volume, allowing remaining data to expire, so that there is no need to reclaim the volume. Specifies the number of days to delay the reclamation of a SnapLock volume. Before reclamation of a SnapLock volume begins, the Tivoli Storage Manager server allows the specified number of days to pass, so that any files remaining on the volume have a chance to expire. The default reclaim delay period is four days and can be set anywhere from 1 to 120 days. In Example 3-5 we specify that the number of days to delay reclamation is 30 days. Example 3-5 SETOPT RECLAIMDELAY option setopt reclaimdelay 30 ANR2119I The RECLAIMDELAY option has been changed in the options file. dsmserv.opt: NDMPPREFDATAINTERFACE 192.168.111.81 SANDISCOVERY ON RECLAIMDELAY 30 RECLAIMPERIOD This option allows you to set the number of days for the reclamation period of a SnapLock volume. It specifies the number of days allowed for the reclamation period of a SnapLock volume. After the retention of a SnapLock volume has expired, the Tivoli Storage Manager server will reclaim the volume within the specified number of days if there is still data remaining on the volume. The default reclaim period is 30 days and can be set anywhere from 7 to 365 days. In Example 3-6 we specify 30 days as the reclamation period for our SnapLock volume: Example 3-6 setopt reclaimperiod 30 ANR2119I The RECLAIMPERIOD option has been changed in the options file. dsmserv.opt: NDMPPREFDATAINTERFACE 192.168.111.81 SANDISCOVERY ON RECLAIMDELAY 30 RECLAIMPERIOD 30 Note: The reclamation period does not begin until the RECLAIMDELAY period has expired.26 Tivoli Storage Manager V6.1 Technical Guide
  • 48. 3.4 Tivoli Storage Manager HP-UX passthru driver support The Tivoli Storage Manager passthru device driver is supported on 64 bit HP-UX 11i v1, v2, and v3. This passthru driver replaces Tivoli Storage Managers kernel device drivers (tsmscsi) and is packaged as part of Tivoli Storage Manager server Version 5.4.3.0, Version 5.5.1.0 and later. The following changes have been implemented to the Tivoli Storage Manager server for HP-UX passthru device driver support: The Tivoli Storage Manager device driver package no longer includes the ddtrace utility, Tivoli Storage Manager kernel modules mod.o for HP 11i v1 or tsmtape, tsmchgr, tsmoptc for HP 11i v2. Two new device configuration tools, autoconf and tsmdlst, are included in the device driver package and are installed to the /opt/tivoli/tsm/devices/bin directory unless you specify another location. The Tivoli Storage Manager passthru device driver is packaged with the Tivoli Storage Manager server and storage agent packages. The sctl driver must be loaded into the kernel before devices are configured for the Tivoli Storage Manager passthru device driver. Issue the following command to verify that the sctl driver is installed. >lsdev | grep sctl If the driver has been loaded, you will see output similar to this: lsdev | grep sctl 203 -1 sctl ctl The HP-UX stape, sdisk, and schgr native drivers are required for device configuration for the Tivoli Storage Manager passthru device driver. To verify that these drivers are loaded in the kernel, issue the following commands from any directory. You should see output similar to what is listed with each command: – stape: >lsdev | grep stape lsdev | grep stape 205 -1 stape tape – sdisk: >lsdev | grep sdisk lsdev | grep sdisk 188 31 sdisk disk – schgr: >lsdev | grep schgr lsdev | grep schgr 231 29 schgr autoch Configuring devices for the Tivoli Storage Manager passthru device driver Follow these steps to configure the devices: 1. Make sure that the Tivoli Storage Manager server is not running. 2. Delete the Tivoli Storage Manager device names that have previously been created by issuing the following command: >rm /dev/rmt/tsm* Chapter 3. Tivoli Storage Manager enhancements provided since V5.5 availability 27
  • 49. 3. Run the ioscan command to make sure that all attached tape drives, auto-changers and optical disk devices have hardware paths associated with corresponding HBAs on the system. 4. Run the autoconf utility to configure devices for the Tivoli Storage Manager passthru device driver: /opt/tivoli/tsm/devices/bin/autoconf The autoconf utility uses the tsmddcfg script to configure devices and calls the tsmdlst utility to display all devices that have been configured by the passthru device driver. The device information is saved in lbinfo, mtinfo, and optinfo in the devices bin directory. Note: You can also run autoconf with the -f option. Autoconf will issue ioscan to scan the system before configuring devices. This might take several minutes. To prevent potential data integrity problems, verify that Tivoli Storage Manager devices can only be accessed through Tivoli Storage Manager passthru special files. If a device is controlled by the passthru driver and also one of the stape, schger, or sdisk drivers, you need to delete the corresponding device special files that are created by those drivers. If there are no changes to the device hardware path on the system during the migration from the Tivoli Storage Manager kernel device driver to the passthru device driver, Tivoli Storage Manager device names should remain the same.28 Tivoli Storage Manager V6.1 Technical Guide
  • 50. Part 3Part 3 Tivoli Storage Manager V6.1 Server enhancements This part of the book covers the server enhancements provided in Tivoli Storage Manager V6.1.© Copyright IBM Corp. 2009. All rights reserved. 29
  • 51. 30 Tivoli Storage Manager V6.1 Technical Guide
  • 52. 4 Chapter 4. Commands, utilities, and option changes With the transition to DB2, new commands, utilities, and server options were introduced. Others either were updated or became obsolete and have been deleted. In this chapter we list new, changed, and deleted commands, utilities, and options. If they are discussed in the book, you will find references to the related section. New commands, utilities, and options are available for the V6.1 server because of changes in database operations and new functions.© Copyright IBM Corp. 2009. All rights reserved. 31
  • 53. 4.1 New server commands, utilities, and options Table 4-1 describes the new server commands in Tivoli Storage Manager V6.1. Table 4-1 New server commands Command Function Comparable commands in previous versions EXTEND DBSPACE Makes additional storage space DEFINE DBVOLUME see Chapter 5.4.3, “Increase available for the server to use followed by EXTEND DB database space” on page 111. for its database. You can have multiple locations for the database storage space. After installation and initial use of DSMSERV FORMAT or DSMSERV LOADFORMAT, you can add more locations for the storage space for the database. IDENTIFY DUPLICATES Starts or stops processes that None identify duplicate data in a storage pool. QUERY DBSPACE Displays the current locations QUERY DBVOLUME see “Monitoring the database for the database storage, along space” on page 54. with total space, and used space. SET DBRECOVERY Sets the device class to use for DEFINE see “Configuring for manual backup of the servers DBBACKUPTRIGGER database backups” on page 87. database. See Example 5-18 on page 87. SET DBREPORTMODE Sets the amount of diagnostic None see “DBREPORTMODE information that is reported for option” on page 114 the database. SET Sets the active-data pools that None DRMACTIVEDATASTGPOOL are included in your recovery plans and procedures. Table 4-2 lists the new server utilities in Tivoli Storage Manager V6.1. Table 4-2 New server utilities Utility Function Comparable commands in previous versions DSMSERV DISPLAY Offline utility to view the current DSMSERV DISPLAY DBSPACE locations for database storage. DBVOLUMES see Example 5-38 on page 105 DSMSERV DISPLAY LOG Offline utility to view information DSMSERV DISPLAY see Example 5-40 on page 107 about the recovery logs (active LOGVOLUMES log and archive logs).32 Tivoli Storage Manager V6.1 Technical Guide
  • 54. Utility Function Comparable commands in previous versionsDSMSERV INSERTDB Offline utility used only for None inserting data that has been extracted from a V5 server database into an empty V6.1 database.DSMSERV REMOVEDB Use this command to remove aFor an example see 6.3.3, “DR Tivoli Storage Manager serversite recovery scenario” on database. This commandpage 129. deletes all user data and log files, as well as any backup and restore history for the database. If the log files are needed for a roll-forward recovery after a restore operation, these files should be saved before you issue this command.DSMUPGRD PREPAREDB Offline utility used only on a V5 server to prepare the database for extraction. After this utility is run, the data can be extracted from the database using the DSMUPGRD EXTRACTDB utility. This is one of the upgrade utilities.DSMUPGRD EXTRACTDB Offline utility used only on a V5 server to extract the data from the database. The extracted data is inserted into a V6.1 database using the DSMSERV INSERTDB utility. This is one of the upgrade utilities.DSMUPGRD EXTEND DB Offline utility used only on a V5 server to extend the database when database space is insufficient to successfully complete the upgrade process. This is one of the upgrade utilities.DSMUPGRD EXTEND LOG Offline utility used only on a V5 server to extend the recovery log when recovery log space is insufficient to successfully complete the upgrade process. This is one of the upgrade utilities.DSMUPGRD QUERYDB Offline utility used only on a V5 server to display information about the database and recovery log. This is one of the upgrade utilities. Chapter 4. Commands, utilities, and option changes 33
  • 55. Figure 4-3 shows the new server options in Tivoli Storage Manager V6.1. Table 4-3 New server options Option Function Comparable commands or options in previous versions ACTIVELOGDIR The new directory for the DEFINE LOGVOLUME For an example see 6.3.3, “DR location where the active log is site recovery scenario” on stored. Use this option to page 129. change the location of the active log. The location is originally specified during installation. There is only one location for the active log. ACTIVELOGSIZE The maximum size of the active EXTEND LOG see “LOG configuration” on log. REDUCE LOG page 55. ARCHFAILOVERLOGDIR The directory in which the None For an example, see 6.3.3, “DR server stores archive log files if site recovery scenario” on they cannot be stored in the page 129. archive log location. ARCHLOGDIR The directory in which the For an example, see 6.3.3, “DR server stores the archive log. site recovery scenario” on page 129. DBMEMPERCENT Sets a limit on the percentage see “Memory management” on of the system memory that is page 46. used for the database. DEDUPREQUIRESBACKUP Control for backup operations for primary sequential-access storage pools that are set up for deduplication. DISKSTGPOOLMEMSIZE The size of the cache that the server can use to manage operations for storage pools with the device type of DISK. MIRRORLOGDIR The directory where the log DEFINE LOGCOPY For an example, see “DR site mirror for the active log is recovery scenario” on stored. page 129.34 Tivoli Storage Manager V6.1 Technical Guide
  • 56. 4.2 Updated server commands, utilities, and options Commands, utilities, and options are updated for Tivoli Storage Manager V6.1 because of changes in database operations and other new functions. Table 4-4 shows updated server commands. Table 4-4 Updated server commands Command Changes BACKUP DB The SET DBRECOVERY command must be run first to set a device For an example, see 6.3.3, “DR class for database backups. site recovery scenario” on page 129. An incremental database backup is now a backup of all changes since the last full backup. In earlier versions of the server, an incremental backup was a backup of all changes since either the last full backup or the last incremental backup. BACKUP/RESTORE NODE The commands support creating SnapMirror to Tape images of file QUERY NASBACKUP systems on NetApp file servers. BACKUP/DELETE/QUERY/ Database dump operations are no longer available, therefore UPDATE VOLHISTORY database dump volumes do not appear in the volume history. see Chapter , “Restore Query output is changed. prerequisites” on page 103. DEFINE/UPDATE DEVCLASS Device formats have been added for some operating systems. DEFINE/DELETE/QUERY/UP The space trigger commands now support space triggers only for DATE SPACETRIGGER storage pools. The database and log space triggers are no longer available. See “Triggered automatic backups” on page 98. DEFINE/QUERY/UPDATE The storage pool commands support the data deduplication STGPOOL functions. DEFINE VOLUME The maximum capacity of a volume in a DISK storage pool is 8 TB. EXPIRE INVENTORY Expiration can be run for specific nodes and node groups, or for all see Chapter 9, “Expiration nodes in a policy domain. The types of data to be examined for enhancements” on page 161. expiration can also be specified. GRANT/REVOKE ANALYST privilege class is removed. AUTHORITY HALT The QUIESCE parameter is no longer needed. MOVE/QUERY DRMEDIA Changes to disaster recovery manager commands allow you to include active-data pools in your recovery plans and procedures. PREPARE For an example, see 6.3.3, “DR site recovery scenario” on page 129. QUERY DRMSTATUS QUERY DB Output is changed. See “Configuring for manual database backups” on page 87. QUERY LOG See Example 5-33 on page 99. QUERY OPTION Obsolete options are removed from the output. Chapter 4. Commands, utilities, and option changes 35
  • 57. Command Changes QUERY PROCESS Information about duplicate identification processes is available through this command. QUERY SESSION A new field in the output indicates the actions that occurred during the session. QUERY STATUS Output is changed. Obsolete options are removed, and the database backup trigger is removed. SELECT Some parameters that were previously allowed might cause see “Changes to the SELECT errors. SQL parameter usage must now conform to usage that is command” on page 612. acceptable to the database manager. SETOPT Obsolete options are removed. UPDATE ADMIN ANALYST privilege class is removed. Table 4-5 shows the updated server utilities. Table 4-5 Updated server utilities Utility Changes DSMSERV (starting the server) New options are available for specifying the owning user ID for the server instance on startup. The new options are also available for other DSMSERV utilities. DSMSERV FORMAT Obsolete parameters are removed. New parameters are added to see “Database configuration” specify the directories for database space, and the maximum size on page 53 and “LOG and locations of the recovery log. configuration” on page 55. This utility is used to format a database for installation of a new server. DSMSERV LOADFORMAT This utility is used only for formatting a new, completely empty see “Database configuration” database. An empty database is used only as part of the process on page 53 and Chapter , “LOG of upgrading an earlier version of the server to V6.1. After you configuration” on page 55 format an empty database, you use the DSMSERV INSERTDB utility to insert data that was extracted from the database of an earlier version of the server. DSMSERV RESTORE DB Volume history is now required for restoring the database. Restore a database to its most current state All restore operations use roll-forward recovery. see Example 5-45 on page 109. The function for restoring individual database volumes was Restore a database to a removed. The server no longer manages database volumes. point in time36 Tivoli Storage Manager V6.1 Technical Guide
  • 58. Table 4-6 shows the updated server options in Tivoli Storage Manager V6.1. Table 4-6 Updated server options Option Changes TXNGROUPMAX The default value is increased from 256 to 4096. Check whether the server options file has this option: If the server options file does not include this option, the server automatically uses the new default value. If the server options file includes a value for the option, the server uses that specified value. If the specified value is less than 4096, consider increasing this value, or removing the option so that the server uses the new default value. Increasing the value or using the new default value can improve the performance for data movement operations such as storage pool migration and storage pool backup. Increasing the value for the TXNGROUPMAX option has no effect on data-movement performance for files that were stored on the server using a lower value for the option. For a detailed discussion of the new TXNGROUPMAX default, refer to Chapter 10, “Changes to the TXNGROUPMAX default” on page 177.4.3 Deleted server commands, utilities, and options Some commands, utilities, and options are deleted because their function is no longer needed. In some cases, new commands replace deleted commands. Table 4-7 shows deleted server commands in Tivoli Storage Manager V6.1. Table 4-7 Deleted server commands Command Changes CONVERT ARCHIVE The operation that this command performed is no longer needed. DEFINE/DELETE/QUERY/UP Ensure that you schedule backups of the database to occur at DATE DBBACKUPTRIGGER least once per day. DEFINE DBCOPY Database volumes are no longer used. DEFINE/DELETE/QUERY Space allocation is done automatically in the directory locations DBVOLUME specified for the database. DEFINE LOGCOPY Instead of log volume copies, you can specify a log mirror to have the active log protected by a mirror copy. DEFINE/DELETE/QUERY The database manager automatically manages space in the LOGVOLUME recovery log directories. For information about the directories that are used for the logs, use the QUERY LOG command. ESTIMATE DBREORGSTATS Collecting and resetting database statistics occurs automatically. Database-reorganization operations are done automatically by the database manager as needed. Chapter 4. Commands, utilities, and option changes 37
  • 59. Command Changes EXTEND DB Space allocation is done automatically in the directory locations specified for the database. If the server needs additional space, you can add directory locations by using the EXTEND DBSPACE command. EXTEND LOG Server options are available for increasing the size of recovery see “LOG configuration” on logs. page 55 QUERY SQLSESSION The information that this command supplied is no longer in the server database. SQL SELECT settings are replaced by syntax options that are available in a DB2 SELECT command. REDUCE DB Space allocation is done automatically in the directory locations specified for the database. You cannot adjust the assigned capacity of the database. REDUCE LOG The database manager automatically manages space in the recovery log directories. RESET BUFPOOL The BUFPOOLSIZE option has been eliminated, therefore this command is not needed. RESET DBMAXUTILIZATION Collecting and resetting database statistics occurs automatically. RESET LOGCONSUMPTION RESET LOGMAXUTILIZATION SET LOGMODE Logging mode for the database is now always roll-forward mode. SET SQLDATETIMEFORMAT The commands are replaced by options in the DB2 SELECT command syntax. SET SQLDISPLAYMODE SET SQLMATHMODE UNDO ARCHCONVERSION The operation that this commands performed are no longer needed. UPDATE ARCHIVE Table 4-8 shows deleted server utilities in Tivoli Storage Manager V6.1. Table 4-8 Deleted server utilities Command Changes DSMFMT Space allocation is done automatically in the directory locations specified for the database. DSMSERV AUDITDB Offline database audits are no longer required. As data is added to the server database, the database manager automatically checks data constraints and data types. The online integrity checks prevent problems for which offline audits had been needed in earlier releases. DSMSERV DISPLAY Information about volumes used for database backup is available DBBACKUPVOLUME from the volume history file. The volume history file is now required to restore the database.38 Tivoli Storage Manager V6.1 Technical Guide
  • 60. Command Changes DSMSERV DISPLAY Use DSMSERV DISPLAY DBSPACE to view information about DBVOLUMES database space when the server is not running. DSMSERV DISPLAY Use DSMSERV DISPLAY LOG to display information about LOGVOLUMES recovery logs including the active log, the mirror for the active log, the failover directory for the archive log, and the overflow location for logs. DSMSERV DUMPDB The operation that this utility performed is no longer needed. DSMSERV EXTEND LOG This utility is replaced by the following server options: ACTIVELOGSIZE ACTIVELOGDIR MIRRORLOGDIR With these options, you can add recovery log space if the log is full when the server is down. DSMSERV LOADDB The operation that this utility performed is no longer needed. DSMSERV RESTORE DB The server does not track individual database volumes in V6.1. Restore a single database volume to its most current The volume history file is required to perform database restore state operations. Restore a database to a point in time when a volume history file is unavailable DSMSERV UNLOADDB The operation that this utility performed is no longer needed.Table 4-9 shows deleted server options in Tivoli Storage Manager V6.1.Table 4-9 Deleted server options Command Changes BUFPOOLSIZE The server adjusts the value of buffer pool size dynamically. DBPAGESHADOW The options are no longer needed. DBPAGESHADOWFILE LOGPOOLSIZE The server uses its own fixed-size recovery log buffer pool. LOGWARNFULLPERCENT The option is no longer needed. MIRRORREAD Mirroring of the active log is supported, but not of the database. Provide availability protection for the database by locating the MIRRORWRITE database on devices that have high availability characteristics. SELFTUNEBUFPOOLSIZE The server adjusts the buffer pool size dynamically.New and changed server messagesIf you have scripts or other automation that use server messages, check the lists of new,changed, and deleted messages for items that you might need to change.The list is available in the Information Center located at the following Web site:http://publib.boulder.ibm.com/infocenter/tsminfo/v6The list is also available in the Tivoli Storage Manager Messages publication for V6.1. Chapter 4. Commands, utilities, and option changes 39
  • 61. 40 Tivoli Storage Manager V6.1 Technical Guide
  • 62. 5 Chapter 5. IBM Tivoli Storage Manager database Functionality and scalability are the key themes of the new Tivoli Storage Manager V6.1 announcement. For additional scalability, Tivoli Storage Managers internal, proprietary database has been ported to IBM DB2. In this chapter we provide a brief history of the proprietary database that comes with previous versions of IBM Tivoli Storage Manager server and introduces the new DB2 database used with Tivoli Storage Manager V6.1. We explain how to estimate the space requirements for the database and log, and we guide you through a complete backup and restore cycle for your database. We give you a list of helpful DB2 commands and system utilities, and you learn how to configure the DB2 and the DB2 Control Center, a graphical administration tool, to connect to a Tivoli Storage Manager database. At the end of the chapter, we introduce some tips to collect diagnostic information, in case this is required.© Copyright IBM Corp. 2009. All rights reserved. 41
  • 63. 5.1 Background This section describes the Tivoli Storage Manager proprietary database, the limitations of that database, and the expectations of the advantages coming with the port to a DB2 database. Tivoli Storage Manager proprietary database The Tivoli Storage Manager database that comes with pre-6.1 servers uses a proprietary B+ Tree database that originated from IBM Almaden Research. This database utilizes state of the art ARIES/NT1 technology for the recovery log. This proprietary database was chosen for two primary reasons at the time: The Tivoli Storage Manager proprietary database was portable across platforms. The V1R1 of ADSM shipped for the MVS and VM platforms. In subsequent releases, this platform coverage expanded to OS/2, AIX, HP, SUN, Windows, and so on. This expanded platform coverage was possible because the proprietary DB package was imbedded in the product and the architecture was to be platform independent. At the time Tivoli Storage Manager was first being delivered, DB2 was not available on all of the platforms where Tivoli Storage Manager was expected to run, or on platforms that Tivoli Storage Manager was expected to be ported. The Tivoli Storage Manager proprietary database was chosen for performance. The Tivoli Storage Manager proprietary database does not have locking or other common database serialization constructs built into it. It was optimized more for performance than what typical database products provided at the time. The database has surpassed every expectation in terms of scalability and performance, supporting up to 530 GB databases. Over time, however, Tivoli Storage Manager development had to develop and maintain code that essentially keeps alternative indices for every table and can audit and correct referential integrity problems between tables. The database does not support secondary indexes, and a lot of code had to be written to implement and maintain alternate index information to speed searches. In addition, Tivoli Storage Manager development has written and maintained its own SQL engine for query processing and to load the data warehouse from the server database. Here are some significant characteristics of the Tivoli Storage Manager proprietary database: Locking is done at an "advisory" level within the application itself. The database does not implement locking at a record level and such, there are latch semantics at a page level that latch a page in “exclusive” mode when a given record on the page is being inserted, updated, or deleted. The database package does not provide or maintain indexes for tables. The Tivoli Storage Manager application maintains the tables and any apparent index or alternate table view that is currently needed or supported by implementing these as separate tables. For example, if a given object on the server is represented by a record entry in tables A, B, and C, it is the application’s responsibility to insert all three of these records when the object is created, the application must make any necessary updates across these records if an object is updated, and it must delete all three of these records if a given object is deleted. 1 ARIES/NT: A Recovery Method Based on Write-Ahead Logging for Nested Transactions was described by IBM fellow C. Mohan and K. Rothermel. You can find the original paper at http://www.vldb.org/conf/1989/P337.PDF42 Tivoli Storage Manager V6.1 Technical Guide
  • 64. Referential integrity checking is done by the application. For Tivoli Storage Manager, this means that the application code has to manage and enforce any referential dependencies between rows in tables and such. Along these lines, the AUDITDB facility within Tivoli Storage Manager was implemented to evaluate and enforce many of the referential constraints that exist with Tivoli Storage Manager. Because referential integrity checking is done at the application levels, it allows for inconsistencies in how the checking is done. It also provides the opportunity to introduce errors in the database because of misunderstanding the relationships that exist. The upper limit of the database size is at 530 GB. The database uses internal control structures to manage the available size of the database. Today customers are reaching the upper bound limit with their production databases. Similarly, the disaster recovery products (DR450) and other content manager type offerings have brought forward concerns over the maximum number of objects that could be stored in the server database.As Tivoli Storage Manager has evolved over the years, enhancements to the database havegenerally been small. There has been investment in the database such as the followingenhancements: DUMP/LOAD/AUDITDB, BACKUP/RESTORE, and SQL. However, theinvestment in the database has been primarily on an as-needed basis.DB2 and other database productsWhen reviewing DB2 or other database products, note that they usually provide the followingfunctions currently not available with the proprietary database: Constraints: Constraints are used to validate attributes/values of a column for a row. Constraints are typically easy to represent and can be defined when a table is created. Constraints can easily check and enforce specific values in a column, in a row, or ranges of values for a column, and so on. Triggers: Triggers cause other checks to be run, such as a fetch against another table to validate that some condition or relationship exists. Typically triggers are used to exercise more complex SQL statements then can be readily implemented or enforced by a constraint. Referential integrity (R/I): These are relationships defined between tables using “foreign keys” in one table to relate a given row to a row in another table. Similarly, it is also possible to implement referential integrity checking by stored procedures or even triggers. The main questions at this point are the complexity of the R/I check to be implemented, and what is the runtime (performance) impact to the check. Expanded database size: DB2 has much greater flexibility and potential capacity depending upon how it is configured. The limitations being dictated are based on the way DB2 is configured to manage its space (DMS verses SMS) and the page size to use. Where limitations do arise, they tend to be on a “per tablespace” basis, so there is at least still flexibility to evolve the tablespace scheme used by Tivoli Storage Manager to provide for further growth and expansion of the database.Do not take this list for a complete reference or explanation of the actual capabilities, it isshown here only to illustrate advanced capabilities compared to the proprietary Tivoli StorageManager database. These and additional functions are provided directly within DB2 or otherdatabase products. Compared to Tivoli Storage Manager Version 6, in older versions of theproduct, equivalents had to be implemented and maintained in the application code itself asopposed to the database. Chapter 5. IBM Tivoli Storage Manager database 43
  • 65. As with Tivoli Storage Manager, DB2 has evolved and has continued to be enhanced to remain competitive with other database products in the market. Today DB2 has platform coverage across all platforms that Tivoli Storage Manager supports and brings all the functions and features of a production enterprise-class database to an application using it. Goals of the transition to DB2 Through the years, while discussing with customers the transition to DB2 for the Tivoli Storage Manager database, the following major expectations or objectives were chosen: Tivoli Storage Manager administration should not become more complex than it is with the current database. You do not want additional DBA skills to be required for administration of Tivoli Storage Manager and to complete the tasks you do already today. Conversion from the proprietary database to the new database should be automated and should not require an unreasonable amount of time. Performance should be comparable to or better than that with the proprietary database. Existing and supported pre-6.1 storage agents must still be able to perform remote database operations. Summarizing all the foregoing considerations, we identified these value propositions: Scalability: DB2 scales to much larger sizes and continues to be enhanced in this regard. Performance: There are many more tuning capabilities within DB2 than with the proprietary database. Recoverability: Many more tools and techniques are available for repairing or recovering DB2 databases than those that exist for the proprietary database. Monitoring and automation: A complete and robust implementation of SQL will now be available for customers to monitor and solicit information from Tivoli Storage Manager. Database license: There is no additional expense for a database license. Repair and recovery tools: Having a complete SQL implementation as well as the other features offered by DB2 eliminates the current techniques used to diagnose and repair the database, making the offline audit of the database obsolete.5.2 Transition to DB2 While one of the target goals of the transition to the DB2 database was not to require any DB2 skills by a Tivoli Storage Manager administrator there are some aspects we want to discuss and explain to give you a better understanding on what happens under the cover. Over the years, Tivoli Storage Manager administrators developed a good sense of how to use existing commands and utilities to configure for best performance. Most of these did become obsolete as the database itself now takes care of them5.2.1 Database transition The Tivoli Storage Manager server had to make a number of changes in order to utilize and exploit DB2 in place of the existing proprietary B+ tree database package that has been used since Tivoli Storage Manager was first released.44 Tivoli Storage Manager V6.1 Technical Guide
  • 66. Here it is important to distinguish that Tivoli Storage Manager has code that is dedicated tomanaging the server database. Similarly, Tivoli Storage Manager has a large amount of codethat provides the end-user (administrative and backup/archive/hsm client) capabilities. Theseend-user capabilities are the “application” code for purposes of this discussion. The existingTivoli Storage Manager database management code is done using the database (DB) andrecovery log (LOG) components. These components work in tandem doing transactionalmaintenance of the database for various database activities such as insert, update, delete,and fetch.Figure 5-1 illustrates the various components involved when an operation is made to theintegrated proprietary database. Recovery Application Code Log DB Operation (Admin & B/A/HSM & Server Mgmt Processes) Database (DB) Log Logical Volume Management (LVM) + Pseudo -Kernel/Device Interface DatabaseFigure 5-1 Tivoli Storage Manager proprietary database and log componentsThe changes that were necessary to utilize and exploit DB2 as the Tivoli Storage Managerdatabase were as follows: In order to use DB2 as the database, the existing DB component was eliminated. It was replaced with a component known as a remote data base (RDB). In this context, “remote” implies a database remote or separate from the Tivoli Storage Manager server itself. The RDB component is responsible for managing the Tivoli Storage Manager interaction with the available DB2 call level interface (CLI) APIs. This interface also provides the management of the available DB2 administrative APIs. The existing recovery log processing and component is superseded by DB2. The component is removed from the server initialization processing. DB2 owns and manages the recovery log functionality using its own recovery log capabilities and management. Transaction management now considers DB2 as a participant on a transaction. The Tivoli Storage Manager DB component has always been a participant in a transaction and now the RDB component will also be a participant in any database related transaction. The RDB component is integrated in Tivoli Storage Manager so that it allows for the existing two-phase commit processing. Historically Tivoli Storage Manager has provided its own transaction manager and the DB2 semantics fit well in the existing model. The pre-Tivoli Storage Manager V6.1 locking scheme was implemented to “protect” sections of the database based on decisions being done by the application code. However, DB2 has its own locking and access control strategies. The Tivoli Storage Manager server code was updated to continue to provide the appropriate access control Chapter 5. IBM Tivoli Storage Manager database 45
  • 67. and serialization to data in the database while utilizing capabilities that DB2 provides in this area. Primarily, Tivoli Storage Manager implemented its DB2 calls specifying “WITH UR,” which indicates “with uncommitted read.” The rational for this rule is that locking semantics and deadlock detection are already in place. Uncommitted Read (UR) allows an application to access uncommitted changes of other transactions. The application also does not lock other applications out of the row that it is reading, unless the other application attempts to drop or alter the table. The pre-Tivoli Storage Manager V6.1 table schema is predicated upon the application level code owning and maintaining the relationships between rows in various tables as shown in Figure 5-2 on page 49. The new server exploits various capabilities that DB2 offers for the following purposes: – Eliminating duplication across tables: There were many cases where data was replicated across many tables. This was done because the proprietary database did not provide for multiple indices on the same table, thus allowing for search optimizations. – Changing the key specifications for some tables: Tivoli Storage Manager’s key and primary key selections historically have been limited by the fact that the only index/key available had to be unique and was governed by the B+ tree structure of the underlying tables. The new server takes advantage of various unique keys and primary keys to better suit optimization for DB2 and also to best meet performance objectives. There are additional capabilities within DB2 that are now used to validate or ensure integrity of the fields in the database and the tables themselves. A few of the DB2 capabilities used for this are views, triggers, stored procedures, and constraints. This explanation is drastically simplified and does not even try to explain these capabilities. For a complete understanding of these DB2 features, refer to the DB2 Information Center at: http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp5.2.2 General DB2 configuration items In this section we provide information about general DB2 configuration features. Memory management The primary memory usage item for the server has historically been the server buffer pool specified by the BUFPOOLSIZE option. The buffer pool is the in-memory cache for the database pages used for pre-Tivoli Storage Manager V6.1 database management operations. With the transition to DB2, the buffer pool space shifts to the DB2 buffer pool where it is used for DB2s own database management operations on the Tivoli Storage Manager server’s behalf. There is also additional memory that DB2 will utilize for its own operating and management. You can consider the DBMEMPERCENT option being the replacement for the BUFPOOLSIZE option. However, it represents much more than the historic buffer pool because it represents the amount of RAM that DB2 can use for everything, such as the buffer pools (plural now) and the sort heap. On UNIX systems, when you start the Tivoli Storage Manager server, the server attempts to change the ulimit values to unlimited. In general, this helps to ensure optimal performance and to assist in debugging. If you are a non-root user, when you start the server, attempts to change the ulimits might fail. To ensure proper server operation if you are running as a non-root user, make sure that you set the ulimits as high as possible, preferably to unlimited, before starting the server.46 Tivoli Storage Manager V6.1 Technical Guide
  • 68. This includes setting DB2 user limits as high as possible. DB2 relies on private data memoryfor sort memory allocations during SQL processing. Insufficient shared heap memory canlead to Tivoli Storage Manager server failures when interacting with DB2. For moreinformation about setting the appropriate platform values, see the following Technote:http://www.ibm.com/support/docview.wss?uid=swg21212174DB and log security in UNIXThe Tivoli Storage Manager server must be run by a member of the DB2 SYSADM_GROUPof the instance. This can be the instance user ID itself, or any member of that group. If youintend to run the server as the root user, you must add root to this group.Even if you are running the server as root, all DB and log directories and files must bewritable by the database instance user ID. The server no longer writes the DB and log files;DB2 does.Required kernel parameter tuningHP-UX, Sun Solaris, and Linux systems require some kernel parameter tuning before youinstall. If you do not update these parameters, the installation of DB2 and Tivoli StorageManager might fail. If these values are not set and the installation is successful, operationalissues might still be encountered when using the server.HP-UX and Sun Solaris systems recommendationsFor HP-UX and Sun Solaris systems, you can run the db2osconf utility to get recommendedchanges based on the size of your system. The db2osconf utility checks the current kernelconfiguration parameter settings, and suggests any updates that should be made. Thedb2osconf utility does not change the settings in the /etc/system file, but only suggestsupdates to help improve performance.The suggested updates provided by the db2osconf utility are the minimum settings required torun DB2 on your system. To run both Tivoli Storage Manager and DB2, additional changesare required in addition to the suggestions made by the db2osconf utility (see Table 5-1 andTable 5-2).Table 5-1 HP-UX recommended kernel parameter values Parameter name Description Recommended value semume The process-wide maximum number of undo 8589934592 structures per process maxdsiz_64bit The maximum data segment size, in bytes for 8589934592 an executing process msgmnb The maximum number of bytes on a message 2097152 queue msgmni The maximum number of message queues 32767 msgtgl The maximum number of messages on all 262144 message queues Chapter 5. IBM Tivoli Storage Manager database 47
  • 69. Table 5-2 Sun Solaris recommended kernel parameter values Parameter name Description Recommended value set semsys:seminfo_semume The process-wide maximum number of undo 5120 structures per process set semsys:seminfo_semmni The number of semaphore identifiers 6144 set shmsys:shminfo_shmmax The maximum shared-memory segment size 46369367654 set shmsys:shminfo_shmmni The minimum shared-memory segment size 6144 set rlim_fd_max The process open-file descriptors limit 65536 set rlim_fd_cur The file descriptor limit 4096 Details about the db2osconf utility are available at the IBM DB2 Database for Linux, UNIX, and Windows Information Center: http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?tab=search&searchWo rd=db2osconf&maxHits=500 Linux system recommendations To update the kernel parameters on Red Hat and SUSE Linux, you can run the ipcs - l command to list the parameter values and then analyze the output to determine whether any changes are required for your system. Additional details on changing kernel parameters are available at the IBM DB2 Database for Linux, UNIX, and Windows Information Center: http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?tab=search&searchWo rd=kernel&parameters&maxHits=500 You can use the information in Table 5-3 to determine the minimum values that you should set to run Tivoli Storage Manager and DB2 together on your target operating system. Table 5-3 Linux recommended kernel parameter values Parameter Description Recommended value name SHMMNI The maximum number of segments 32768 SHMMAX The maximum size of a shared memory x86 systems - 268435456 segment (kbytes) 64-bit systems - 1073741824 SHMALL The maximum allocation of shared memory 8388608 pages (kbytes) SEMMNI The maximum number of arrays 1024 SEMMSL The maximum semaphores per array 250 SEMMNS The maximum semaphores per system 256000 SEMOPM The maximum operations per semaphore call 35 MSGMNI The maximum number of system-wide 1024 message queues MSGMAX The maximum size of messages (bytes) 65536 MSGMNB The default maximum size of queue (bytes) 6553648 Tivoli Storage Manager V6.1 Technical Guide
  • 70. 5.2.3 Database and log configuration items Here we discuss the items to consider when configuring the DB2 database and log directories. Figure 5-2 shows the Tivoli Storage Manager V6.1 components involved: database, active log directory, mirror log directory, archive log directory, and the archive failover directory. TSM V6 Components Active Log TSM Server ActiveLogDir Log Mirror (optional) TSM DB MirrorLogDir Archive Log ArchiveLogDir TSM STGPools (disk, tape) Failover Archive Log (optional) ArchFailoverLogDir Figure 5-2 v V6.1 components Estimating database space requirements The process to estimate how much space to configure differs between installing a new server or upgrading an existing server. Here we discuss both processes. If you plan to take advantage of the integrated deduplication function, you need to consider additional database and log space requirements. For additional information about deduplication, refer to Chapter 7, “Data deduplication in Tivoli Storage Manager V6.1” on page 145. Estimate database space requirements for a new server The size of the database depends on the number of client files to be stored and the method by which the server manages them. If you can estimate the maximum number of files that might be in server storage at any time, you can estimate the database size from the following information: Each stored version of a file requires about 600 to 1000 bytes of database space. Each cached file, copy storage pool file, and active-data pool file requires about 100 to 200 bytes of database space. Overhead can require up to 25% in additional space. In the following examples, the computations are probable maximums. In addition, the numbers are not based on using file aggregation. In general, aggregation of small files reduces the required database space. Assume the following numbers for a Tivoli Storage Manager system: The size of the database depends on the number of client files to be stored and the method by which the server manages them. Chapter 5. IBM Tivoli Storage Manager database 49
  • 71. If you can estimate the maximum number of files that might be in server storage at any time, you can estimate the database size from the following information: Each stored version of a file requires about 600 to 1000 bytes of database space. Each cached file, copy storage pool file, and active-data pool file requires about 100 to 200 bytes of database space. Overhead can require up to 50% in additional space. Versions of files The following considerations apply: Backed up files: Up to 500,000 client files might be backed up. Storage policies call for keeping up to three copies of backed up files: 500.000 files x 3 copies = 1.500.000 files Archived files: Up to 100,000 files might be archived copies of client files. Space-managed files: Up to 200,000 files migrated from client workstations might be in server storage. File aggregation does not affect space-managed files. At 600 bytes per file, the space required for these files is: (1.500.000 + 100.000 + 200.000) x 600 = 1.0GB Cached, copy storage pool, and active-data pool files The following considerations apply: Cached copies: Caching is enabled in a 5 GB disk storage pool. The pools high and low migration thresholds are 90% and 70% respectively. Thus, 20% of the disk pool, or 1 GB, is occupied by cached files. If the average file size is about 10 KB, about 100,000 files are in cache at any one time. 100.000 files x 200 bytes = 19 MB Copy storage pool files: All primary storage pools are backed up to the copy storage pool: (1.500.000 + 100.000 + 200.000) x 200 bytes = 343 MB Active-data pool files: All the active client-backup data in primary storage pools is copied to the active-data pool. Assume that 500,000 versions of the 1,500,000 backup files in the primary storage pool are active. 500.000 x 200 bytes = 95 MB Therefore, cached files, copy storage pool files, and active-data pool files require about 0.5 GB of database space. Overhead About 1.5 GB is required for file versions, cached copies, copy storage pool files, and active-data pool files. Allow up to 50% additional space (or 0.7 GB) for overhead. The database should then be approximately 2.2 GB at a minimum.50 Tivoli Storage Manager V6.1 Technical Guide
  • 72. If you cannot estimate the numbers of files, you can roughly estimate the database size asfrom 1% to 5% of the required server storage space. For example, if you need 100 GB ofserver storage, your database should be between 1 GB and 5 GB.During SQL queries of the server, intermediate results are stored in temporary tables thatrequire space in the free portion of the database. Therefore, using SQL queries requiresadditional database space. The more complicated the queries, the greater the space that isrequired. Note: In the preceding examples, the results are estimates. The actual size of the database might differ from the estimate because of factors such as the number of directories and the length of the path and file names. As a best practice, periodically monitor your database and adjust its size as necessary. Adding a new database directory after initial load will cause a REORG of the database. Because this is expensive and disruptive, it should be avoided.For example, if you need 100 GB of server storage, your database should be between 1 GBand 5 GB. During SQL queries of the server, intermediate results are stored in temporarytables that require space in the free portion of the database. Therefore, using SQL queriesrequires additional database space. The more complicated the queries, the greater the spacethat is required. Notice: In the preceding examples, the results are estimates. The actual sizeof the database might differ from the estimate because of factors such as the number ofdirectories and the length of the path and file names. As a best practice, periodically monitoryour database and adjust its size as necessary.You can use the worksheet in Table 5-4 to help you plan the amount and location of storageneeded for the V6.1 server.Table 5-4 Worksheet for planning space Item Space required Location The instance directory for the server, which is a directory that contains files specifically for this server instance (the server options file and other server-specific files) The database Active log Archive log Optional: Log mirror for the active log Optional: Secondary archive log (failover location for archive log)Estimate database space requirements for a server upgradeThe amount of database space that is required depends on the size of the original V5database, and on how much data the server will be managing.The amount of storage space for the database is managed automatically. The databasespace can be spread across multiple directories. After you specify the directories for thedatabase, the server uses the disk space available to those directories as required. Chapter 5. IBM Tivoli Storage Manager database 51
  • 73. Locate the database and recovery log directories on separate physical volumes or file systems. Ideally, use multiple directories for database space and locate them across as many physical devices or logical unit numbers (LUNs) as there are directories. Plan for 33 - 50% more than the space that is used by the V5 database. (Do not include allocated but unused space for the V5 database in the estimate.) Some databases can grow temporarily during the upgrade process; consider providing up to 80% more than the space that is used by the V5 database. Estimation steps You can estimate the amount of space that the database will require by completing the following steps: 1. Use the QUERY DB FORMAT=DETAILED command to determine the number of used database pages in your V5 database. 2. Multiply the number of used database pages by 4096 to get the number of used bytes. 3. Add 33 - 50% to the used bytes to estimate the database space requirements. Consider testing the upgrade of the database to get a more accurate estimate. Not all databases will grow as much as the suggested 33 - 50% increase in space. When the server is operating normally, after the upgrade process, some operations might cause occasional large, temporary increases in the amount of space used by the database. Continue to monitor the usage of database space to determine whether the server needs more database space. For the best efficiency in database operations, anticipate future growth when you set up space for the database. If you underestimate the amount of space that is needed for the database and then must add directories later, the database manager might need to perform more database reorganization, which can consume resources on the system. Estimate requirements for additional database space based on 600 - 1000 bytes per additional object stored in the server. Note: You cannot use raw logical volumes for the database. If you want to reuse space on the disk where raw logical volumes were located for an earlier version of the server, you must create file systems on the disk first. Estimating log space requirements In this section we show how to estimate log space requirements. Active log space Ensure that the recovery log has enough space. The minimum size of the active log is 2048 MB (2 GB); the maximum is 131.072 MB (128 GB). The default is 2048 MB. You might want to begin with an active log size of 4 GB to 8 GB. Monitor the space usage and adjust the size of the active log as needed. Active log mirror space The active log mirror is a duplicate copy of the active log and should be the same size as the active log. Creating a log mirror is optional. The additional space that the log mirror requires is another factor to consider when deciding whether to create a log mirror.52 Tivoli Storage Manager V6.1 Technical Guide
  • 74. Archive log spaceThe size of the archive log depends on the number of objects stored by client nodes over theperiod of time between full backups of the database.A full backup of the database causes obsolete archive log files to be pruned, to recoverspace. The archive log files that are included in a backup are automatically pruned after twomore full database backups have been completed. Therefore, the archive log should be largeenough to contain the logs generated since the previous two full backups.If you perform a full backup of the database every day, the archive log must be large enoughto hold the log files for client activity that occurs over two days. Typically 600 - 4000 bytes oflog space are used when an object is stored in the server. Therefore you can estimate astarting size for the archive log using the following calculation:objects stored per day x 3000 bytes per object x 2 daysFor example:5.000.000 objects/day x 3000