Académique Documents
Professionnel Documents
Culture Documents
Mary Lovelace Gerd Becker Dan Edwards Shayne Gardener Mikael Lindstrom Craig McAllister Norbert Pott
ibm.com/redbooks
7718edno.fm
International Technical Support Organization Tivoli Storage Manager V6.1 Technical Guide August 2009
SG24-7718-00
7718edno.fm
Note: Before using this information and the product it supports, read the information in Notices on page xiii.
First Edition (August 2009) This edition applies to Version 6, Release 1, of IBM Tivoli STorage Manager (product number 5698-B22). This document created or updated on November 13, 2009.
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 Schedule Contract with IBM Corp.
7718TOC.fm
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Part 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.4 New features overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . 10 1.5.3 Tivoli Storage Manager for Space Management, additions and changes. . . . . . . 11 1.6 Additional information on Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . . . . . . . . 11 Chapter 2. IBM Tivoli Storage Manager for products. . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 IBM Tivoli Storage Manager for Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.1.1 Data Protection for Microsoft Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2 IBM Tivoli Storage Manager for Microsoft SharePoint V6.1 . . . . . . . . . . . . . . . . . . . . . 14 2.3 IBM Tivoli Storage Manager for ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.4 IBM Tivoli Storage Manager for Advanced Copy Services V6.1 and IBM Tivoli Storage Manager for Copy Services V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Part 2. Tivoli Storage Manager enhancements since V5.4 and V5.5 book . . . . . . . . . . . . . . . . . . . . . . 19 Chapter 3. Tivoli Storage Manager enhancements provided since V5.5 availability . 3.1 SAN Device Mapping for Virtual Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 RELABELSCRATCH parameter for Virtual Tape Libraries . . . . . . . . . . . . . . . . . . . . . . 3.3 RECLAIMDELAY and RECLAIMPERIOD server options . . . . . . . . . . . . . . . . . . . . . . . 3.4 Tivoli Storage Manager HP-UX passthru driver support . . . . . . . . . . . . . . . . . . . . . . . . 21 22 24 25 26
Part 3. Tivoli Storage Manager V6.1 Server enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Chapter 4. Command, utilities and option changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 New server commands, utilities, and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Updated server commands, utilities, and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Deleted server commands, utilities, and options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1 New and changed server messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 32 34 37 39
iii
7718TOC.fm
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 5.3.2 DB2 Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.4 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 5.4.1 Backing up your database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 5.4.2 Restoring the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 5.4.3 Increase database space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.4.4 Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Chapter 6. IBM Tivoli Storage Manager Disaster Recovery Manager . . . . . . . . . . . . 123 6.1 Introduction to disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2 Disaster Recovery Manager changes in V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2.1 New system requirements for V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2.2 Recovery plan limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.2.3 DRM enhancements for V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.2.4 Disaster Recovery Manager exclusions in V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.3 Recovery of a V6.1 Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.3.1 Local disaster recovery of the Tivoli Storage Manager database . . . . . . . . . . . . 130 6.3.2 DR site recovery of the Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . 131 6.3.3 DR site recovery scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 6.4 Data deduplication considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 6.4.1 Data lifecycle for a Tivoli Storage Manager server and DRM . . . . . . . . . . . . . . . 139 6.4.2 Data lifecycle for a Tivoli Storage Manager server and DRM including deduplicated storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 6.5 Seven tiers of disaster recovery solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 6.5.1 A breakdown of the seven tiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 6.5.2 Selecting the optimum Disaster Recovery solution. . . . . . . . . . . . . . . . . . . . . . . 144 6.6 Best practices for offsite data vaulting and security . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Chapter 7. Data deduplication in Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . 7.1 Introduction to deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 Deduplication approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Deduplication ratios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.3 Tivoli Storage Manager V6.1 deduplication overview . . . . . . . . . . . . . . . . . . . . . 7.1.4 Should we use Tivoli Storage Manager, or VTL/Filer deduplication? . . . . . . . . . 7.2 Implementing deduplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 8. No-query restore changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 Legacy NQR algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 Objectives of the new NQR process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.3 New NQR process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 9. Expiration enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1 Legacy expiration algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.2 Objectives of the new expiration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.3 Enhanced Tivoli Storage Manager V6.1 expiration algorithm . . . . . . . . . . . . . . . 9.2 Externals of the enhanced expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Tivoli Storage Manager V6.1 Technical Guide
147 148 148 149 150 152 153 157 158 158 158 159 161 163 164 164 165 165 166
7718TOC.fm
9.2.1 Command line changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.2 Administration Center integration: expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.3 Administration Center integration: maintenance script . . . . . . . . . . . . . . . . . . . . 9.2.4 New server messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.5 Expiration restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.6 Expiration retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 10. Changes to the TXNGROUPMAX default . . . . . . . . . . . . . . . . . . . . . . . . . 10.1 Transaction handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.1 TXNGROUPMAX option examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.2 Server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Implementation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
166 168 170 172 174 178 179 181 182 182 183 183 185
Part 4. Tivoli Storage Manager V6.1 Client enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Chapter 11. HSM for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Automatic threshold migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 12. Active Directory Object Item Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Active Directory overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Version 6.1 Client Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1 Design limitations for restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2 New client commands and parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.3 New client options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 190 191 192 194 197 198 199 200 201 202 202 204
Chapter 13. Client restore statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 13.1 QUERYSUMMARY option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Part 5. Complimentary products and NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Chapter 14. N Series support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1.1 Large filesystem backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1.2 IP address of server interface to receive NDMP backup data . . . . . . . . . . . . . 14.2 Snap Mirror to Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2.1 How to setup, use and control SnapMirror to Tape for bakup. . . . . . . . . . . . . . 14.2.2 How to restore a NAS Volume from SnapMirror to Tape backup . . . . . . . . . . . 14.3 Snapdiff option for NFS data stored on NetApp filers . . . . . . . . . . . . . . . . . . . . . . . . 14.3.1 Overview of SnapDiff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.2 How the Backup Archive Client interacts with the SnapDiff-API . . . . . . . . . . . . 14.3.3 Preparation for using SnapDiff API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.4 Using snapdiff option to do Incremental Backup for NAS filesystems . . . . . . . 14.3.5 Hints and Tips, Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.6 Performance issues and test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 216 216 217 219 221 223 224 224 226 227 229 235 236
Chapter 15. IBM Tivoli Storage Manager Data Protection for Mail - Exchange 6.1 . . 239 15.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 15.1.1 Data Protection for Microsoft Exchange V6.1 on Windows for x86. . . . . . . . . . 240
Contents
7718TOC.fm
15.1.2 Microsoft Exchange Server 2003 SP2 or later . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3 Data Protection for Microsoft Exchange V6.1 on Windows for x64. . . . . . . . . . 15.1.4 Compatibility issues with earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5 Backup methods supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2 Individual Mailbox Restore feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.1 Individual Mailbox Restore limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.2 New command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.3 Tivoli Storage Manager 6.1 Mailbox Restore features . . . . . . . . . . . . . . . . . . . 15.2.4 Exchange Server - Mailbox Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.5 Tivoli Storage Manager Mailbox Restore limitations . . . . . . . . . . . . . . . . . . . . 15.2.6 Restoremailbox command line parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . .
240 240 241 241 242 243 243 243 245 246 246
Part 6. Tivoli Storage Manager V6.1 planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1 . . . . . . . 16.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 Upgrade strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.1 What you can and can not do with Tivoli Storage Manager V6.1 . . . . . . . . . . . 16.2.2 Upgrade considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3.1 System requirements for the V6.1 server system . . . . . . . . . . . . . . . . . . . . . . . 16.3.2 System requirements for the V6.1 reporting and monitoring. . . . . . . . . . . . . . . 16.3.3 Client environment requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3.4 Tivoli Storage Manager Client compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4 Database capacity planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4.1 Overview of the four different log types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5 Planning an upgrade from V5 to V6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5.1 Database restructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5.2 Estimating the upgrade time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5.3 Space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5.4 Work sheet for planning space for the V6.1 server . . . . . . . . . . . . . . . . . . . . . . 16.5.5 High level process for upgrading the server to V6.1 . . . . . . . . . . . . . . . . . . . . . 16.6 Naming best practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.6.1 Directories for database space and recovery log . . . . . . . . . . . . . . . . . . . . . . . 16.7 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.8 Upgrading an existing system verses a new system. . . . . . . . . . . . . . . . . . . . . . . . . 16.8.1 Comparison of methods for moving data to the V6.1 database . . . . . . . . . . . . 16.8.2 Details of the database upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.8.3 Tivoli Storage Manager V6.1 upgrade utilities . . . . . . . . . . . . . . . . . . . . . . . . . 16.9 Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.1 Scenario 1: new system, media method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.2 Upgrading the server using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.3 Scenario 2: new system, network method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.4 Upgrading using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.5 Scenario 3: same system, media method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.6 The following steps are a summary of the wizard method scenario . . . . . . . . . 16.9.7 Scenario 4: same system, network method . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.8 Upgrading the server using the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.9.9 Hybrid upgrade migration method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.10 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.10.1 Testing the upgrade process for a server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.10.2 Test by extracting data from a separate copy of the server . . . . . . . . . . . . . . 16.10.3 Test by extracting data from the production server. . . . . . . . . . . . . . . . . . . . . 251 252 252 252 253 254 254 255 256 256 256 257 260 260 261 262 269 270 270 271 272 272 274 278 280 282 283 283 284 284 285 285 287 287 289 295 295 296 297
vi
7718TOC.fm
16.11 Planning for operational changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.11.1 Adapting existing Operational Reporting for V6.1 . . . . . . . . . . . . . . . . . . . . . . 16.12 Why use the database upgrade wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.13 An upgrade test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.13.1 Upgrade from V5.5 to V6.1 step by step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.14 Modifying the server before the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.14.1 Performance tips for the V5 database extraction process . . . . . . . . . . . . . . . 16.14.2 Performance tips for inserting data into the V6.1 database . . . . . . . . . . . . . . 16.15 Tivoli Storage Manager documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part 7. Installation, customization and upgrade of Tivoli Storage Manager V6.1 Server and Client 309 Chapter 17. Installation of Tivoli Storage Manager V6.1 on AIX . . . . . . . . . . . . . . . . . 17.1 System requirements for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.1 Planning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2 Installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2.1 Prepare the installation source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2.2 Choosing the installation method for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 Install Tivoli Storage Manager for AIX software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3.1 Using the command-line console wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4 Install using the console installation wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4.1 Setup of X11 environment for non-graphical environments . . . . . . . . . . . . . . . 17.4.2 Installation wizard using X11 redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.5 Post installation steps for Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 17.5.1 Prepare the AIX server for Tivoli Storage Manager instances . . . . . . . . . . . . . 17.5.2 Post completion tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.5.3 Configuring using the dsmicfgx and X11 redirection. . . . . . . . . . . . . . . . . . . . . 17.6 Upgrading from Tivoli Storage Manager V6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.1 Installing update software using AIX install process . . . . . . . . . . . . . . . . . . . . . 17.7 Problem determination and recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.7.1 Database queries and validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.7.2 Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.7.3 Completely removing the DE if required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.8 So now you are in production on V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.8.1 Did you remember to setup a database backup methodology? . . . . . . . . . . . . Chapter 18. Installation of Tivoli Storage Manager V6.1 on Windows . . . . . . . . . . . . 18.1 IBM Tivoli Storage Manager planning for installation . . . . . . . . . . . . . . . . . . . . . . . . 18.1.1 What you should know first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 System requirements for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3 Planning for space for the V6.1 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3.1 Estimating database space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4 Tivoli Storage Manager V6.1 components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.1 Package names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.2 Package extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.3 Installing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.5 Installing the Tivoli Storage Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . 18.6 Installation wizard install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.7 Command-line console wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.8 Silent mode installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.8.1 Silent mode without saving responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.8.2 Silent mode saving responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
311 312 312 312 313 313 314 315 315 320 320 321 325 325 337 342 351 351 352 352 355 356 356 357 361 362 362 362 363 364 364 364 365 365 365 367 368 376 381 381 381 vii
7718TOC.fm
18.9 Creating directories and user ID for the server instance . . . . . . . . . . . . . . . . . . . . . . 18.9.1 Creating the directories for the server instance . . . . . . . . . . . . . . . . . . . . . . . . 18.9.2 Creating the user ID for the server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.10 Configure a new Tivoli Storage Manager Server instance . . . . . . . . . . . . . . . . . . . 18.10.1 Prepare the configuration of Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . 18.11 Using the Tivoli Storage Manager configuration wizard. . . . . . . . . . . . . . . . . . . . . . 18.11.1 Configuring the server instance using the wizard . . . . . . . . . . . . . . . . . . . . . . 18.12 Creating the server instance manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12.1 Manually create a Tivoli Storage Manager instance . . . . . . . . . . . . . . . . . . . . 18.12.2 Running multiple server instances on a single system . . . . . . . . . . . . . . . . . . 18.12.3 Configuring server and client communications: . . . . . . . . . . . . . . . . . . . . . . . 18.12.4 TCP/IP options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12.5 Named Pipes options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12.6 Shared memory options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12.7 SNMP DPI subagent options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12.8 Monitoring the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.12.9 Network connection types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.13 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.13.1 Here we present various ways to debug the installation . . . . . . . . . . . . . . . . . 18.13.2 How to completely remove Deployment Engine . . . . . . . . . . . . . . . . . . . . . . . 18.14 Gathering logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.14.1 Code description of various exit error codes in InstallAnywhere. . . . . . . . . . .
383 383 383 384 384 385 385 399 400 406 406 406 407 407 408 408 408 409 409 410 411 411
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation 413 19.1 Backup-archive client updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 19.1.1 New function in Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 414 19.1.2 Related commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 19.2 Installation of the Tivoli Storager Manager V6.1 client . . . . . . . . . . . . . . . . . . . . . . . 417 19.2.1 Migrating from earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 19.2.2 Considerations for migrating between processor architectures . . . . . . . . . . . . 418 19.2.3 Unicode considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 19.2.4 Additional migration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 19.2.5 Upgrading Open File Support or online image . . . . . . . . . . . . . . . . . . . . . . . . . 420 19.2.6 NDMP support requirements (Extended Edition only) . . . . . . . . . . . . . . . . . . . 420 19.2.7 Installing from the Tivoli Storage Manager DVD . . . . . . . . . . . . . . . . . . . . . . . . 421 19.2.8 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 19.2.9 Install steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Part 8. Tivoli Storage Manager V6.1 monitoring, reporting, ISC and administration center . . . . . . . 435 Chapter 20. Monitoring and Reporting in Tivoli Storage Manager V6.1. . . . . . . . . . . 20.1 Monitoring and Reporting overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1.1 Administration Center - Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1.2 Administration Center - Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1.3 Tivoli Storage Manager Monitoring and Reporting . . . . . . . . . . . . . . . . . . . . . . 20.2 Monitoring and reporting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.3 Installing Monitoring and Reporting feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.4 Business Intelligence and Reporting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.4.1 Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 438 438 439 440 442 443 451 451
Chapter 21. Integrated Solutions Console and Administration Center . . . . . . . . . . . 453 21.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 21.1.1 New installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 viii
Tivoli Storage Manager V6.1 Technical Guide
7718TOC.fm
21.1.2 Upgrade and co-existence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.3 Upgrade considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Administration Center updates and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1 Policy Domain configuration panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.2 Updated Integrated Solutions Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.3 WebSphere Windows service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Administration Center features in V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.1 Identify managing servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.2 Hover help for table links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.3 Information links for server and Administration Center messages . . . . . . . . . . 21.3.4 Maintenance script enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.5 Client nodes and backup sets enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.6 Centralized server-connection management . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.7 Changes to management-class activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.8 DRM support for Active Data Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.9 Health Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.10 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.11 Creating a new server instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.12 Client Nodes and backupset enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.13 Maintenance plan enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4 Integrated Solutions Console changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.1 Tivoli Common Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.2 Single user ID signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.3 Credential Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.4 Manage Global Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.5 Quick references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.5 Additional notes of interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
454 455 455 456 456 456 456 456 456 456 457 457 457 457 457 458 462 464 471 478 491 492 492 493 494 496 496
Part 9. Tivoli Storage Manager V6.1 Upgrade consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 Chapter 22. Upgrade to Tivoli Storage Manager V6.1 . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 Upgrade strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1.1 The process for upgrading the server to V6.1. . . . . . . . . . . . . . . . . . . . . . . . . . 22.1.2 The DSMUPGRD upgrade utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 Hardware and software server requirements for upgrade. . . . . . . . . . . . . . . . . . . . . 22.2.1 Hardware and software requirements for V5 server upgrad . . . . . . . . . . . . . . . 22.2.2 Upgrade utility additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.3 Hardware and software requirements for the upgraded server. . . . . . . . . . . . . 22.2.4 Server requirements on AIX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.5 Server requirements on HP-UX systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.6 Server requirements on Linux systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.7 Server requirements for Linux on x86_64 systems. . . . . . . . . . . . . . . . . . . . . . 22.2.8 Server requirements for Linux on System z systems . . . . . . . . . . . . . . . . . . . . 22.2.9 Server requirements on Sun Solaris systems . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.10 Server requirements on Microsoft Windows systems . . . . . . . . . . . . . . . . . . . 22.3 Planning space for the upgrade process and server. . . . . . . . . . . . . . . . . . . . . . . . . 22.3.1 Space requirements for the V5 server system . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.2 Space requirements for the Tivoli Storage Manager V6 server system . . . . . . 22.3.3 Estimating total space requirements for upgrade process and server . . . . . . . 22.4 Estimating the upgrade time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.4.1 Performance tips for inserting data into the V6.1 database . . . . . . . . . . . . . . . 22.5 Planning for upgrading multiple servers and components . . . . . . . . . . . . . . . . . . . . 22.5.1 Compatibility with servers and components running at earlier versions . . . . . . 501 502 502 503 503 504 506 506 507 508 510 512 513 515 516 517 518 518 520 521 522 522 523
Contents
ix
7718TOC.fm
22.5.2 Planning for upgrading multiple servers on a single system . . . . . . . . . . . . . . . 22.5.3 Planning for upgrading library managers and library clients . . . . . . . . . . . . . . . 22.5.4 Planning for upgrading clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5.5 Planning for upgrading storage agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7 Preparing for operational changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 23. Tivoli Storage Manager V6.1 Upgrade Scenarios . . . . . . . . . . . . . . . . . . 23.1 The basics of planning the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2 Upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3 Upgrade from V5.5 to V6.1 step by step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3.1 Modifying the server before the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3.2 Upgrade steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3.3 Summary of the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4 Steps after V6.1 server is started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4.1 Database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.5 Sample commands to run for database upgrade validation . . . . . . . . . . . . . . . . . . . 23.6 Common database maintenance tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.7 Scripting and reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.7.1 SQL function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.8 How to rollback to V5 if needed or restart the process . . . . . . . . . . . . . . . . . . . . . . . 23.8.1 If we need to restart the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.9 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.9.1 Here we present various ways to debug the installation . . . . . . . . . . . . . . . . . . 23.10 Gathering logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.11 Upgrade for NAS TOC data on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.11.1 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
523 523 524 524 524 524 527 528 528 529 530 534 557 561 561 563 564 566 566 567 567 568 568 568 568 576
Part 10. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 Appendix A. Configuring ODBC connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DB2 configuration for ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.11.2 ODBC target machine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.11.3 ODBC client machine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.11.4 ODBC connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix B. DB2 and SQL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Commands to manage the database environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnosis and troubleshoot the database environment . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor the status and health of the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changes to the SELECT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LIKE predicate for a nested SELECT statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SELECT statements for time calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The index_keyseq and index_order columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access to database objects using the SELECT command . . . . . . . . . . . . . . . . . . . . . . Table joins and column labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Results of the SELECT command for the DISK device class . . . . . . . . . . . . . . . . . . . . Extra spaces appearing in output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix C. Recover from log exhausted conditions . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for the out of log space condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The server crash scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recover the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 582 582 584 592 603 604 610 616 619 619 620 620 621 621 621 622 623 624 624 625 629
7718TOC.fm
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 633 633 634 635 635
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Contents
xi
7718TOC.fm
xii
7718spec.fm
Notices
This 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. Consult your 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 IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate 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. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, 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 such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express 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 made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials 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 without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities 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 them as 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 business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs 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.
xiii
7718spec.fm
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
AIX 5L AIX DB2 DPI DS6000 DS8000 FlashCopy GDPS GPFS HACMP HyperSwap IBM MQSeries NetView OS/390 Passport Advantage POWER5 POWER ProtecTIER Redbooks Redbooks (logo) SANergy System i System p System Storage System z Tivoli TotalStorage WebSphere XIV z/OS zSeries
The following terms are trademarks of other companies: ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Data ONTAP, FilerView, FlexVol, NetApp, Network Appliance, SnapMirror, Snapshot, and the Network Appliance logo are trademarks or registered trademarks of Network Appliance, Inc. in the U.S. and other countries. AMD, AMD Opteron, the AMD Arrow logo, and combinations thereof, are trademarks of Advanced Micro Devices, Inc. SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and other countries. Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its 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 several other countries. VMware, the VMware "boxes" logo and design are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Java, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows NT, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Itanium, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks 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. Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
xiv
7718spec.fm
Other company, product, or service names may be trademarks or service marks of others.
Notices
xv
7718spec.fm
xvi
7718pref.fm
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. Since 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.
Figure 1 The team: Dan, Craig, Mary, Mikael, Gerd, Shayne, Norbert
Mary Lovelace is a 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 IBM 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 IBM Redbook 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 member of the Tivoli Storage Manager Advisory Council.
Copyright IBM Corp. 2009. All rights reserved.
xvii
7718pref.fm
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 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 IBM Redbook 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 IBM 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. Thanks to the following people for their contributions to this project: Barry Fruchtman Colin Dawson Donald Moxley Jo Lay
xviii
7718pref.fm
Ken Hannigan Matthew Anglin Michael G. Sisco Tivoli Storage Manager Server development Alexei Kojenov Stefan Bender Tivoli Storage Manager Client Development Andy Ruhl Benjamin Schockert John Wang Todd Owczarzak Wolfgang Beuttler Tivoli Storage Manager Software Support Clare M Byrne Gary Spizizen Holly King Liudyte Baker Tivoli Storage Manager Information Development Roger Stakkestad IBM SWG Norway Cyrus Niltchian Tricia Jiang Technology Sales Enablement Charles Nichols Dave Canan Randy Larson Robert Elder Tomas Hepner Zong Ling Performance and ATS Urs Moser Integrated Technology Delivery, Server Systems Operations Austen M Cook Tashfique Hossain Storage System Test Joerg Pohlmann IBM Global Services, Canada Roger Stakkestad IBM SWG Norway Peter Kask IBM Innovation Center - Stockholm, Sweden Konstantin Arnold Biozentrum Pharmazentrum Information Technology / Div. of Bioinformatics Swiss Institute of Bioinformatics (SIB)
Preface
xix
7718pref.fm
Comments 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-5400
xx
7718p01.fm
Part 1
Part
7718p01.fm
7718TSM6Overview.fm
Chapter 1.
7718TSM6Overview.fm
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 via the Internet, WANs, LANs, or SANs, Storage Manager Extended Edition's 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 Manager's 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
IP Network
Log
Database
Storage
Repository
ISC Server can be run on the same server as the TSM server
TSM Clients
Note: It is recommended to install 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. 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 4
7718TSM6Overview.fm
running. This restriction partially was lifted, you want to check the following technote for the current status: http://www-01.ibm.com/support/docview.wss?uid=swg21386858
7718TSM6Overview.fm
IB M
Ma
g na
er
03/2009 11/2007
06/2001
M DS A
1997
07/2000 09/1999
01/1999
1995 1993
7718TSM6Overview.fm
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 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 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 will 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.html
7718TSM6Overview.fm
7718TSM6Overview.fm
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 64bit 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. 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. 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. 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.
Chapter 1. IBM Tivoli Storage Manager overview
7718TSM6Overview.fm
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.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.
10
7718TSM6Overview.fm
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.
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 User's Guide, Version 6.1, SC23-9794-00.
11
7718TSM6Overview.fm
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&appnam e=iSource&supplier=897&letternum=ENUS209-004 Information about additional Tivoli Storage Manager V6.1 products is found at: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appnam e=iSource&supplier=897&letternum=ENUS209-088 The Tivoli Storage Manager V6.1 documentation is available at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp
12
7718TSMProductsOverview.fm
Chapter 2.
13
7718TSMProductsOverview.fm
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 Legacy 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 Legacy 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=swg21318434.
7718TSMProductsOverview.fm
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
Automatic classification of Microsoft SharePoint content 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) that can streamline user interaction for typical tasks and can improve the end-user experience. Added support 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 SharePoint's 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=swg21378227
15
7718TSMProductsOverview.fm
New features
These are 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 include: Support for 32bit 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=swg21321826
2.4 IBM Tivoli Storage Manager for Advanced Copy Services V6.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. In today's business world, application servers often are operational 24 hours a day. The data on the application servers should be well protected. With the rapid increase in the amount of data on these servers, their critical business needs, and the shrinking backup windows, traditional backup and restore methods may be reaching their limits in meeting your 16
Tivoli Storage Manager V6.1 Technical Guide
7718TSMProductsOverview.fm
challenging requirements. Snapshot operations can help minimize the impact caused by backups. Since a snapshot operation typically takes much less time than the time for a tape backup, the window during which the application must be aware of a backup can be reduced. The snapshots can be retained as backups on local disk, sent to Tivoli Storage Manager server storage pools, or both.
Supported environments
The IBM Tivoli Storage Manager for Advanced Copy Services V6.1 requirements are documented at http://www-01.ibm.com/support/docview.wss?rs=3043&uid=swg21321830. The hardware and software requirements for IBM Tivoli Storage Manager for Copy Services V6.1 are documented at: http://www-01.ibm.com/support/docview.wss?rs=3042&uid=swg21321332
17
7718TSMProductsOverview.fm
18
7718p02.fm
Part 2
Part
19
7718p02.fm
20
7718Enhan55.fm
Chapter 3.
21
7718Enhan55.fm
1. Port:Name: Role: Port WWNN: Port WWPN: Topology: Port ID: Loop ID: 2. Port:Name: Role: Port WWNN: Port WWPN: Topology: Port ID: Loop ID: .. lines deleted .. 21. Virtual Drive:Virtual Library: Virtual Drive: Serial Number: Vendor ID: Product ID: Barcode: 22. Virtual Drive:Virtual Library: testpc_vtl Virtual Drive: Drive1 testpc_vtl Drive0 77e846640f01a098045df0 IBM ULTRIUM-TD4 0b Backend 500a09800000de30 510a09830000de30 Private Loop 0xef 0x0 0a Frontend 500a09800000de30 510a09820000de30 Link Down 0x0 0x0
22
7718Enhan55.fm
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 we can query with the query san f=d command.
Example 3-2 Tivoli Storage Manager-command query san f=d
q san f=d Device Type: Vendor: Product: Serial Number: Device: Data Mover: Node WWN: Port WWN: LUN: SCSI Port: SCSI Bus: SCSI Target: Device Type: Vendor: Product: Serial Number: Device: Tape0 Data Mover: Node WWN: Port WWN: LUN: SCSI Port: SCSI Bus: SCSI Target: Device Type: Vendor: Product: Serial Number: Device: Data Mover: Node WWN: Port WWN: LUN: SCSI Port: SCSI Bus: SCSI Target: Device Type: Vendor: Product: Serial Number: Device:
LIBRARY NETAPP VTL 77e696d40f01a098045df0 lb0.0.0.3 No 500A09800000DE30 510A09820000DE30 0 3 0 0 DRIVE IBM ULTRIUM-TD4 77e846640f01a098045df0 No 500A09800000DE30 510A09820000DE30 1 3 0 0 DRIVE IBM ULTRIUM-TD4 77e85f960f01a098045df0 Tape1 No 500A09800000DE30 510A09820000DE30 2 3 0 0 DRIVE IBM ULTRIUM-TD4 77e86ec80f01a098045df0 Tape2 23
7718Enhan55.fm
Data Mover: Node WWN: Port WWN: LUN: SCSI Port: SCSI Bus: SCSI Target: .. lines deleted ..
No 500A09800000DE30 510A09820000DE30 3 3 0 0
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.
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.
Example 3-3 shows, how virtual tapes will be relabeled when their status is changed to SCRATCH.
Example 3-3 RELABEL scratch example
ANR8468I LTO volume TSM0006 dismounted from drive TAPE_DEVICE_2 (mt0.3.0.3) in library TESTPC_VTL.
24
7718Enhan55.fm
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 items for a total of 50,948,409,476 bytes with a completion state of SUCCESS at 05: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 completion state SUCCESS at 05:18:19.
To determine if the RELABELSCRATCH parameter is set to Yes, you can issue the QUERY LIBRARY command, as shown in Example 3-4 on page 25.
Example 3-4 QUERY LIBRARY command example
q libr f=d Library Name: Library Type: ACS Id: Private Category: Scratch Category: WORM Scratch Category: External Manager: RSM Media Type: Shared: LanFree: ObeyMountRetention: Primary Library Manager: WWN: Serial Number: AutoLabel: Reset Drives: Relabel Scratch: Last Update by (administrator): Last Update Date/Time: TESTPC_VTL SCSI
Yes
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.
25
7718Enhan55.fm
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 seven to 365 days. In Example 3-6 we specify 30 days as 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
7718Enhan55.fm
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 the following: 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
1. Make sure 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* 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
27
7718Enhan55.fm
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 may 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 corresponding device special files which 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
7718p03.fm
Part 3
Part
29
7718p03.fm
30
7718TSMCommandsUtilitiesOptions.fm
Chapter 4.
31
7718TSMCommandsUtilitiesOptions.fm
None
Table 4-2 on page 32 lists the new server utilities in Tivoli Storage Manager V6.1.
Table 4-2 New server utilities Utility DSMSERV DISPLAY DBSPACE see Example 5-38 on page 107 DSMSERV DISPLAY LOG see Example 5-40 on page 108 Function Offline utility to view the current locations for database storage. Offline utility to view information about the recovery logs (active log and archive logs). Comparable commands in previous versions DSMSERV DISPLAY DBVOLUMES DSMSERV DISPLAY LOGVOLUMES
32
7718TSMCommandsUtilitiesOptions.fm
Function Offline utility used only for inserting data that has been extracted from a V5 server database into an empty V6.1 database. Use this command to remove a Tivoli Storage Manager server database. This command 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 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. 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. 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. 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. Offline utility used only on a V5 server to display information about the database and recovery log. This is one of the upgrade utilities.
DSMSERV REMOVEDB For an example see 6.3.3, DR site recovery scenario on page 131.
DSMUPGRD PREPAREDB
DSMUPGRD EXTRACTDB
DSMUPGRD EXTEND DB
DSMUPGRD QUERYDB
Table 4-3 on page 34 shows the new server options in Tivoli Storage Manager V6.1.
Chapter 4. Command, utilities and option changes
33
7718TSMCommandsUtilitiesOptions.fm
Table 4-3 New server options Option ACTIVELOGDIR For an example see 6.3.3, DR site recovery scenario on page 131. Function The new directory for the location where the active log is stored. Use this option to change the location of the active log. The location is originally specified during installation. There is only one location for the active log. ACTIVELOGSIZE see LOG configuration on page 56. ARCHFAILOVERLOGDIR For an example, see 6.3.3, DR site recovery scenario on page 131. ARCHLOGDIR For an example, see 6.3.3, DR site recovery scenario on page 131. DBMEMPERCENT see Memory management on page 46. DEDUPREQUIRESBACKUP The maximum size of the active log. The directory in which the server stores archive log files if they cannot be stored in the archive log location. The directory in which the server stores the archive log. EXTEND LOG REDUCE LOG None Comparable commands or options in previous versions DEFINE LOGVOLUME
Sets a limit on the percentage of the system memory that is used for the database. Control for backup operations for primary sequential-access storage pools that are set up for deduplication. The size of the cache that the server can use to manage operations for storage pools with the device type of DISK. The directory where the log mirror for the active log is stored. DEFINE LOGCOPY
DISKSTGPOOLMEMSIZE
34
7718TSMCommandsUtilitiesOptions.fm
Table 4-4 Updated server commands Command BACKUP DB For an example, see 6.3.3, DR site recovery scenario on page 131. Changes The SET DBRECOVERY command must be run first to set a device class for database backups. 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. The commands support creating SnapMirror to Tape images of file systems on NetApp file servers. Database dump operations are no longer available, therefore database dump volumes do not appear in the volume history. Query output is changed. Device formats have been added for some operating systems. The space trigger commands now support space triggers only for storage pools. The database and log space triggers are no longer available. See Triggered automatic backups on page 99. The storage pool commands support the data deduplication functions. The maximum capacity of a volume in a DISK storage pool is 8 TB. Expiration can be run for specific nodes and node groups, or for all nodes in a policy domain. The types of data to be examined for expiration can also be specified.
BACKUP/RESTORE NODE QUERY NASBACKUP BACKUP/DELETE/QUERY/ UPDATE VOLHISTORY see Chapter , Restore prerequisites on page 104. DEFINE/UPDATE DEVCLASS DEFINE/DELETE/QUERY/UP DATE SPACETRIGGER
DEFINE/QUERY/UPDATE STGPOOL DEFINE VOLUME EXPIRE INVENTORY see Chapter 9, Expiration enhancements on page 163. GRANT/REVOKE AUTHORITY HALT MOVE/QUERY DRMEDIA PREPARE For an example, see 6.3.3, DR site recovery scenario on page 131. QUERY DRMSTATUS QUERY DB see Configuring for manual database backups on page 88. QUERY LOG see Example 5-33 on page 100 QUERY OPTION QUERY PROCESS QUERY SESSION
Output is changed.
Obsolete options are removed from the output. Information about duplicate identification processes is available through this command. A new field in the output indicates the actions that occurred during the session.
35
7718TSMCommandsUtilitiesOptions.fm
Command QUERY STATUS SELECT see Changes to the SELECT command on page 619. SETOPT UPDATE ADMIN
Changes Output is changed. Obsolete options are removed, and the database backup trigger is removed. Some parameters that were previously allowed might cause errors. SQL parameter usage must now conform to usage that is acceptable to the database manager. Obsolete options are removed.
DSMSERV FORMAT see Database configuration on page 53 and LOG configuration on page 56.
DSMSERV RESTORE DB Restore a database to its most current state see Example 5-45 on page 111. Restore a database to a point in time
Table 4-6 on page 37 shows the updated server options in Tivoli Storage Manager V6.1.
36
7718TSMCommandsUtilitiesOptions.fm
Table 4-6 Updated server options Option TXNGROUPMAX Changes 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 181.
37
7718TSMCommandsUtilitiesOptions.fm
Command EXTEND DB
Changes 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. Server options are available for increasing the size of recovery logs. 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. Space allocation is done automatically in the directory locations specified for the database. You cannot adjust the assigned capacity of the database. The database manager automatically manages space in the recovery log directories. The BUFPOOLSIZE option has been eliminated, therefore this command is not needed. Collecting and resetting database statistics occurs automatically.
REDUCE DB
REDUCE LOG RESET BUFPOOL RESET DBMAXUTILIZATION RESET LOGCONSUMPTION RESET LOGMAXUTILIZATION SET LOGMODE SET SQLDATETIMEFORMAT SET SQLDISPLAYMODE SET SQLMATHMODE UNDO ARCHCONVERSION UPDATE ARCHIVE
Logging mode for the database is now always roll-forward mode. The commands are replaced by options in the DB2 SELECT command syntax.
Table 4-8 on page 38 shows deleted server utilities in Tivoli Storage Manager V6.1.
Table 4-8 Deleted server utilities Command DSMFMT DSMSERV AUDITDB Changes Space allocation is done automatically in the directory locations specified for the database. 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 DBBACKUPVOLUME Information about volumes used for database backup is available from the volume history file. The volume history file is now required to restore the database.
38
7718TSMCommandsUtilitiesOptions.fm
Changes Use DSMSERV DISPLAY DBSPACE to view information about database space when the server is not running. Use DSMSERV DISPLAY LOG to display information about 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.. The operation that this utility performed is no longer needed. 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 DSMSERV RESTORE DB Restore a single database volume to its most current state 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. The server does not track individual database volumes in V6.1. The volume history file is required to perform database restore operations.
Table 4-9 on page 39 shows deleted server options in Tivoli Storage Manager V6.1.
Table 4-9 Deleted server options Command BUFPOOLSIZE DBPAGESHADOW DBPAGESHADOWFILE LOGPOOLSIZE LOGWARNFULLPERCENT MIRRORREAD MIRRORWRITE SELFTUNEBUFPOOLSIZE The server uses its own fixed-size recovery log buffer pool. The option is no longer needed. Mirroring of the active log is supported, but not of the database. Provide availability protection for the database by locating the database on devices that have high availability characteristics. The server adjusts the buffer pool size dynamically. Changes The server adjusts the value of buffer pool size dynamically. The options are no longer needed.
39
7718TSMCommandsUtilitiesOptions.fm
The list is also available in the Tivoli Storage Manager Messages publication for V6.1.
40
7718TSMDB2_Database.fm
Chapter 5.
41
7718TSMDB2_Database.fm
5.1 Background
This section describes the Tivoli Storage Manager proprietary database, the limitations of that database and the expectations on the advantages coming with the port to a DB2 database.
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.PDF
42
7718TSMDB2_Database.fm
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 have generally been small. There has been investment in the database such as the following enhancements: DUMP/LOAD/AUDITDB, BACKUP/RESTORE, SQL. However the investment in the database has been primarily on an as needed basis.
43
7718TSMDB2_Database.fm
44
7718TSMDB2_Database.fm
Figure 5-1 illustrates the various components involved when an operation is made to the integrated proprietary database:
Application Code (Admin & B/A/HSM & Server Mgmt Processes) Database (DB) Log
Recovery Log
Figure 5-1 Tivoli Storage Manager proprietary database and log components
The changes necessary to utilize and exploit DB2 as the Tivoli Storage Manager database were the following: In order to use DB2 as the database, the existing DB component was eliminated. It was replaced with a so called remote data base (RDB) component. 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 API's. 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 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 is that locking semantics and deadlock detection is 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 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
Chapter 5. IBM Tivoli Storage Manager database
DB Operation
Database
45
7718TSMDB2_Database.fm
shown in Figure 5-2 on page 49. The new server exploits various capabilities that DB2 offers for the following purpose: eliminate 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. change the key specifications for some tables Tivoli Storage Managers 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 suite 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 is a drastically simplified and does not even try to explain these capabilities, for a complete understanding of these DB2 features, refer to the DB2 infocenter at http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp.
Memory management
The primary memory usage item for the server has historically been the server buffer pool specified via 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 DB2's own database management operations on the Tivoli Storage Manager servers 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 bufferpool as it represents the amount of RAM DB2 can use for everything, like the bufferpools (plural now) and sortheap. 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. This includes setting DB2 user limits as high as possible. DB2 relies on private data memory for sort memory allocations during SQL processing. Insufficient shared heap memory can lead to Tivoli Storage Manager server failures when interacting with DB2. For more information on setting the appropriate platform values, see the following Technote: http://www.ibm.com/support/docview.wss?uid=swg21212174
46
7718TSMDB2_Database.fm
maxdsiz_64bit
8589934592
Table 5-2
set semsys:seminfo_semmni
6144
47
7718TSMDB2_Database.fm
Parameter name set shmsys:shminfo_shmmax set shmsys:shminfo_shmmni set rlim_fd_max set rlim_fd_cur
Description The maximum shared-memory segment size The minimum shared-memory segment size The process open-file descriptors limit The file descriptor limit
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
48
7718TSMDB2_Database.fm
Description The maximum size of messages (bytes) The default maximum size of queue (bytes)
TSM V6 Components
TSM Server
Archive Log
ArchiveLogDir
49
7718TSMDB2_Database.fm
In the following example, 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. 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
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
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. 50
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDB2_Database.fm
The database should then be approximately 2.2 GB at a minimum. If you cannot estimate the numbers of files, you can roughly estimate the database size as from 1% to 5% of the required server storage space. For example, if you need 100 GB of server storage, your database should be between 1 GB and 5 GB. During SQL queries of the server, intermediate results are stored in temporary tables that require space in the free portion of the database. Therefore, using SQL queries requires additional database space. The more complicated the queries, the greater the space that is required. 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. As 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 GB and 5 GB. During SQL queries of the server, intermediate results are stored in temporary tables that require space in the free portion of the database. Therefore, using SQL queries requires additional database space. The more complicated the queries, the greater the space that is required. Notice: 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. You can use the worksheet in Table 5-4 on page 51 to help you plan the amount and location of storage needed 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)
51
7718TSMDB2_Database.fm
Estimation steps
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.
52
7718TSMDB2_Database.fm
Database configuration
With the utilization of Database Managed Space (DMS) table space design, the database manager controls the storage space. Use the DBDIR/DBFILE parameter with the DSMSERV [LOAD]FORMAT command to specify up to 128 directories available to DB2 as so called containers. This is DB2 terminology for what Tivoli Storage Manager calls database directories. The database volumes are managed by DB2, you are no longer asked to format them. DB and log security (UNIX) on page 47 discusses this in more detail. You cannot place the containers on raw logical volumes and you should make sure each container is in a separate filesystem/LUN. Additional considerations when configuring the database are: The database manager uses striping to ensure an even distribution of data across all containers. DB2 striping is recommended when writing data into multiple containers. If you choose to implement disk striping along with DB2 striping, the extent size of the table space and the strip size of the disk should be identical.
53
7718TSMDB2_Database.fm
The containers that make up a DMS table space do not need to be the same size; however, this is not normally recommended, because it results in uneven striping across the containers, and sub-optimal performance. If any container is full, DMS table spaces use available free space from other containers. If the disk subsystem supports it, disable read cache for the DB but enable write cache for it. In addition configure for random IO access. The database is used to contain committed Tivoli Storage Manager transactions. Page sizes used for the database are 8K and 32K depending on the tablespace. The largest tables, such as the big inventory tables, use a 32 KB page size. For any other table that we did not designate as large, we will use a page size of 8 KB. The maximum supported database size is 1TB. No testing was done yet for performance but from current feedback page sizes used work fine with default disk subsystem segment sizes. Use fast disk. Using the slow internal disk included by default in most servers, or using consumer grade PATA/SATA disk will slow everything down. If your disk storage is virtualized (such as when using a SAN Volume Controller), or is controlled by a RAID controller, you may be able to further improve I/O parallelism by setting the DB2 registry variable DB2_PARALLEL_IO. This is set using the DB2SET command, as in db2set DB2_PARALLEL_IO=value The value is a comma separated list of tablespace ids or '*', followed by a colon, followed by a number which indicates the number of physical disks backing your database container (directory). For Tivoli Storage Manager, it is recommended to specify '*' for the table space ids, and then whatever number of disks you have in your raid configuration. Example: For LUNs of 4+1 RAID5, you would use: db2set DB2_PARALLEO_IO=*:4 This requires a restart of DB2. Separate the Tivoli Storage Manager components (DB LUNs, Log LUNs, Storage Pool LUNs). The database defined for Tivoli Storage manager is taking advantage of the AUTOMATIC STORAGE parameter. Automatic storage is a storage management technique where storage for multiple tablespaces is automatically managed at the database level: multiple tablespaces automatically draw increments of storage from a database storage pool on demand removes the need to watch for disk shortages in each individual tablespace removes the need to manually enlarge containers or add stripe sets uses DMS infrastructure internally: combines performance benefits of DMS infrastructure with manageability benefits of System Managed Space (SMS) Automatic storage allows the server to create the database and associate a set of storage paths with it add storage paths to the database after creation create AUTOMATIC STORAGE tablespaces no explicit container definitions are provided containers automatically created across the database storage paths growth of existing containers and addition of new ones managed by DB2 redefine database storage paths during a database restore
7718TSMDB2_Database.fm
backup. Example 5-1 shows that the server aborts the transaction and closes the session with the client.
Example 5-1 ANR0131E, Server database space exhausted
ANR0131E dbieval.c(809): Server DB space exhausted. ANR0162W Supplemental database diagnostic information: -1:57011:-289 ([IBM][CLI Driver][DB2/NT] SQL0289N Unable to allocate new pages in table space "LARGESPACE1". SQLSTATE=57011 ). ANR0532W smnode.c(3361): Transaction 0:7594 was aborted for session 4 for node OLDSKOOL (WinNT). ANR0514I Session 4 closed volume D:\GALLIUM_SERVER1\FILECLASS\0000003F.BFS. ANR0403I Session 4 ended for node OLDSKOOL (WinNT).
You should monitor the filesystem for space being available to the database, use the QUERY DBSPACE command as shown with Example 5-2.
Example 5-2 QUERY DBSPACE: monitoring the database for available space
tsm: TIRAMISU>q dbspace Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): g:\tsm\server1\database 59,388.70 59,387.81 0.00
The QUERY DBSPACE is a new command for the Tivoli Storage Manager V6.1 server, use the DSMSERV DISPLAY DBSPACE utility (see Example 5-38 on page 107) when the server is not running. Table 5-5 explains the fields being returned by the command:
Table 5-5 QUERY DBSPACE command explained Field Location Total Size of File System (MB) Description Directory or path used for storing the database Windows: Total space (in MB) on the drive where the directory is located UNIX and Linux: Total space in the file system where the path is located Space Used on File System (MB) Windows: Total used space (in MB) on the drive where the directory is located UNIX and Linux: Total used space in the file system where the path is located
55
7718TSMDB2_Database.fm
Description Windows: Space remaining on the drive where the directory is located UNIX and Linux: Space remaining in the file system where the path is located If there are more than one directories or paths located on the same drive (Windows) or the same file system then the total free space will be divided to how many directories or paths
LOG configuration
You specify the logs used by the server with the ACTIVELOGDIR and the ARCHLOGDIR parameters to the DSMSERV [LOAD]FORMAT command. Both parameters are required For the active log you can, in addition, specify the optional ACTIVELOGSIZE parameter. If you do not specify the active log size, it defaults to 2GB. The active log directory specifies the directory in which the Tivoli Storage Manager server writes and stores active log files. There is only one active log location. The name must be a fully qualified directory name. The directory must already exist, it must be empty, and it must be accessible by the user ID of the database manager. The maximum number of characters is 175. In this context, active log is a Tivoli Storage Manager term, DB2 uses logs and archive logs. Optionally you can specify the ARCHFAILOVERLOGDIR and MIRRORLOGDIR with either of the format commands. ARCHFAILOVERLOGDIR specifies the directory to be used as an alternate storage location if the ARCHLOGDIR directory is full. MIRRORLOGDIR specifies the directory in which the server mirrors the active log (those files in the ACTIVELOGDIR directory). For both the same restrictions apply as with the ARCHLOGDIR.
7718TSMDB2_Database.fm
I/O characteristic is sequential Usage is required. Have up to three full backups worth of space for archive logs. Required to roll forward transactions after a database restore Log files older than two full backups ago are removed after DB backup. The ARCHIVELOGDIR value can be changed in the dsmserv.opt file (requires server restart), the initial value is taken from the format command.
S0000000.LOG S0000095.LOG
57
7718TSMDB2_Database.fm
The active log is used to store current in-flight transactions for the server. For example, if the server has 10 backup/archive client sessions performing backups, the transactions used by those sessions will be represented in the active log and used to track changes to the server database such as the insert, delete, or update to records for tables within the server database. The active log needs to be sized large enough to hold the largest concurrent workload that the server will encounter. Or put another way, it needs to be able to store the data representing in-flight transactions for the largest concurrent workload that the server will support. The archive log is used as a storage repository for log files that were previously active and no longer contain transaction references for in-flight transactions. So, once a given log file in the active log directory is no longer referenced by an in-flight transaction, that log file is eligible to be copied to the archive log directory where it will then be retained. The copy of log files from the active log directory to the archive log directory is done automatically by the DB2. The active log will then continue at a steady state of the defined active log size. As new transactions are started in response to server activities, this will drive the head of the log forward as these new transaction records are prepended to the head of the active log. The tail of the active log is continually truncated as the oldest in-flight transactions complete which allows active log volumes to become inactive and eligible to be archived (copied) to the archive log directory. The archive log size is not maintained using a steady state or pre-defined size like the active log uses. The archive log will store all inactive log files based on retention policies that the Tivoli Storage Manager server manages. These policies are not configurable by you as an administrator, the archive log files will be pruned by DB2 following the pruning policy set up by Tivoli Storage Manager. This pruning is a function of full database backup cycles. To take a step back, we need to first understand how and why full database backups are considered in this processing. When any database backup is performed, the database backup will contain the actual database pages that are allocated and in use for the database and the active and archive log information necessary to represent transaction consistency for the database data stored within that database backup. The Tivoli Storage Manager V6.1 server only operates in ROLLFORWARD recovery mode. In order to accomodate this, the archive log files are kept in order to represent all the transactional changes to the server database from the time of the last FULL database backup. So, a full database backup cycle in this discussion represents both the time between one full database backup and the next and more importantly it represents all the transactional changes that were recorded from the time the previous full database backup was performed until the time the next full database backup is done. The Tivoli Storage Manager server requires that archive log space is retained representing two full database backup cycles. Since the server requires archive log space representing two full database backup cycles, you must also consider the active or current transaction load which is the files from the active log that become inactive and eligible to be moved to the archive log. his then increases the archive log space requirement from being two times the space needed to store the transactional data for a single database backup cycle to being up to a total of three times this total space requirement. Given the framework of the discussion above, the following then are recommendations on how to size the active and archive log space assigned to a Tivoli Storage Manager V6.1 server.
Active and archive log sizing upgrading to Tivoli Storage Manager V6.1
Here we discuss the active and archive log sizing considerations when upgrading from a Tivoli Storage Manager V5.x server to Tivoli Storage Manager V6. As a starting point, the
58
7718TSMDB2_Database.fm
active log should be two times the size of the existing Tivoli Storage Manager V5.x recovery log. So if the V5.x recovery log was 10 GB, an active log size of 20 GB would be appropriate. To estimate the transaction activity on your V5.x server between full database backups, do the following: 1. Prior to your next regularly scheduled FULL database backup, issue the command "SHOW LOGV". Make note of the log head LSN (HeadLsn) which will be in the form XXXXX.YYY.ZZZZ. Example 5-3 shows the output for one of our test servers, but let us assume for your production server the value is 140312.105.1011.
Example 5-3 SHOW LOGV command
tsm: LEONARD>show logv Log Global Variables: SegTableSize=1000, ResizeLocked=False, EmptySegs=999, PagesReserved=131, MaxPagesUsed=378, PagesInUse=363, LastReportedFull=90 HeadLsn: StableLsn: TruncLsn: ScanLsn: ScanEndLsn: 16354.231.1737 (segment 0, page 231) 16354.231.986 (segment 0, page 231) 16354.223.16 (segment 0, page 223) 16354.223.16 16354.223.16
Log Restart Record: VersId=1, RecLen=88, InstallId=4A3D12ED, FmtCapacity=1000, Capacity=1000, NewCapacity=1000 FmtDate=1245516525, ResizeDate=0, MovePhase=0, SourceSeg=-1, TargetSeg=-1, consumedLsn=1.0.0, consumedReset=1245516525 TruncBaseLsn: 16354.0.0 (segment 0, page 0)
2. Let the full database backup run and then allow the server to operate normally. 3. At the next scheduled FULL database backup, issue the SHOW LOGV command. Again make note of the log head LSN (HeadLsn), this may now be a value like 158600.88.16. 4. To estimate the transaction activity for this server between full database backups, subtract the XXXXX values from the noted log head LSNs that were captured from the SHOW LOGV command. Using our example values, we would use 158600 - 140312. The result in this example is 18288. This value represents megabytes (MB) so the transaction load for a single database backup cycle for this example would be approximately 18 GB. Using the estimated transaction workload for a single full database backup cycle, a conservative estimate of the space needed for the archive log would then be three times this value. Using the example values from the previous step, this would be 18 GB * 3 or approximately 54 GB.
Sizing consideration for active and archive log if deploying a new V6.1 server
When deploying a new Tivoli Storage Manager V6.1 server, an estimate is needed based on the expected load on the server in terms of the number of files to be stored nightly. The number of files stored for a given nightly schedule window is just one way to estimate this. This estimate needs to be done by the administrator or team implementing this server. This
Chapter 5. IBM Tivoli Storage Manager database
59
7718TSMDB2_Database.fm
estimate should consider the total number of files to be backed up, archived, and space managed in a given night. An example of this estimate is: Nightly Client Operations: 300 Clients How many files will be stored in a single transaction: 4096 (this is derived as the total files to be stored nightly per client times the server option setting for TXNGROUPMAX, for purposes of this example the default value of 4096 will be used. ) Total concurrent workload represented by in-flight client transactions: 1,228,800 (this is derived as number of clients times files stored in a single client transaction) Total active log needed to support 1,228,800 files for 300 in-flight client session with TXNGROUPMAX=4096: 3.5 GB Note that for this calculation, log bytes needed per file in a given transaction is 3053. This represents the log bytes needed when backing up files from a Windows server where the file names vary in length from 12 to 120 bytes. This was done as a backup to a DISK storage pool as these pools have increased log overhead and use as compared to sequential media storage pools. A value larger then 3053 may need to be considered if the data being stored has file names that are longer then referenced above. In this example, the recommended active log size would be 3.5 GB. There are a number of variations or other considerations which we will discuss.
Variation 1:
If the 300 clients use the client option RESOURCEUTILIZATION set greater then default such that each client session ran with up to a maximum of 3 sessions in parallel. This would then change the servers inflight concurrent load from 300 sessions to 900 (as a maximum). The calculation then becomes: (((900 * 4096) * 3053) / 1 GB) = 10.5 GB
Variation 2:
If the workload was 1000 clients used with the client option RESOURCEUTILIZATION set greater then default such that each client session ran with up to a maximum of 3 sessions in parallel. This would then result in: (((3000 * 4096) * 3053) / 1GB) = 35 GB
Variation 3:
If the backups were being done using simultaneous write such that the data was being stored to two copy pools in addition to the primary storage pool, the log bytes estimate per file should be increased. If a value of 200 bytes for each copy storage pool is used then this value is 3453. Using the original calculations, the result would be nearly 4 GB. In the examples and discussion above, this assumes that the client store operations are done in isolation. For example, migration, deduplication (identify processing), reclamation, expiration, and even other administrative tasks such as administrative commands or SQL from administrative clients are not being run concurrent with this client workload. Any of these operations included in the processing during time for this client workload would increase the active log space required. This also assumes that the client workloads are somewhat homogeneous. Of particular interest is the duration of transactions. If there are a large number of transactions that complete quickly (complete in a short amount of time), this may cause active log space issues if there are also long running (complete in a long amount of time) transactions in this mix. If the mix of client workloads and the relative amount of time needed for specific 60
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDB2_Database.fm
transactions to complete is somewhat heterogeneous, then increasing the active log size may be needed in order to compensate for these timing differences. In this scenario, migration from the DISK storage pool to a sequential media pool (DEVTYPE=FILE) uses approximately 110 bytes per file migrated which results in 10.5 MB of log space used for each 100,000 files migrated. Using the original example above where the nightly client load in terms of number of files is 1,228,800, if these files then were migrated to NEXT pool, the log space needed for this migration operation (assuming all files were migrated) would be: 129 MB. Continuing then with the log size estimate for a Tivoli Storage Manager V6.1 server, if the active log is estimated to require 3.5 GB, then the archive log would require 10.5 GB.
Does deduplication for storage pools affect the active and archive log sizing?
The affect of deduplication on the active and archive log needed for the server will vary depending upon the deduplication ratio of the data. In a scenario where there is a high percentage of data that can be deduplicated, the active log bytes per extent identified by the IDENTIFY process is approximately 1500 bytes. As an example, if the number of extents that can be identified during the execution of the IDENTIFY process is 250,000, then the active log space needed for this operation is estimated to be 358 MB. Using the information from Variation 2: on page 60 about sizing the active log for a new Tivoli Storage Manager V6.1 server installation, if the nightly backup load is 100,000 files for each of 300 clients. (100,000 files is a change rate of 10% on a total number of files of 1,000,000 for each client) This represents 30,000,000 files for that nightly workload. If those 30,000,000 files represented 60,000,000 deduplicable extents, the total archive log space this would require or represent is estimated to be 84 GB. In this scenario, the active log impact of 60,000,000 extents is based on the TXNGROUPMAX server options setting. The identify process will operate on aggregates (groups) of files based on how many files were stored in a given transaction. If the average number of extents per file is two (60,000,000 / 30,000,000) and the number of files in a transaction is 4096, then the extents per aggregate is 8192 which results in 12 MB of active log space used per 4096 files having 8192 extents. The next consideration relative to the active log size needed for IDENTIFY processing is how many processes are being run. If there are 10 IDENTIFY processes running in parallel, then the concurrent load on the active log is 12 MB * 10 or 120 MB. The final consideration for active log impacts from IDENTIFY processing is what are the impacts of really large files. For example, if a client backs up a single object, perhaps an image backup of a filesystem, that is 800 GB in size. This may represent a very high number of extents because of the nature of this data, for this discussion assume it is 1.2 million extents. This 1.2 million extents would represent a single transaction for an IDENTIFY process that requires an estimated 1.7 GB of active log space. This 1.7 GB of active log space may be easily attainable in isolation. But if lots of other activity is happening in the active log, such as other IDENTIFY processes that are only having to process 8192 extents per transaction, the active log may become constrained for space because the small transactions are intermixing with the large transaction used to identify the extents for the 800 GB single object. The recommendation if the deduplication enabled storage pool will have a mix of data with lots of uniform relatively small files while also having a small number of very large highly deduplicatable objects, then plan to increase the active log size by a factor of two. The issue being that it is not only the raw space that is needed but the timing and duration of the transactions that require that space while other activities are concurrently processing. So, if the estimates above recommend a 25 GB active log size, then with
61
7718TSMDB2_Database.fm
deduplication in the mix the active log size becomes 50 GB and the archive log then is 150 GB. In conclusion, there are a number of factors to consider when planning for the size of the Tivoli Storage Manager V6.1 server active and archive logs. The examples and discussion above present and touch on some basic values that can be used for estimation purposes. Keep in mind that larger values may need to be considered in your actual environment.
62
7718TSMDB2_Database.fm
utility fails to recognize a table space backup image on an old log sequence if a database restore operation is immediately followed by the table space restore operation. Until the database is actually rolled forward, the log sequence that is to be used is unknown. If the table space is on an old log sequence, it must be "caught" by the table space rollforward operation. A restore operation using an invalid backup image might complete successfully, but the table space rollforward operation for that table space will fail, and the table space will be left in restore pending state. For example, suppose that a table space-level backup operation, Backup 3, completes between S0000013.LOG and S0000014.LOG in the top log sequence. If you want to restore and roll forward using the database-level backup image, Backup 2, you will need to roll forward through S0000012.LOG. After this, you could continue to roll forward through either the top log sequence or the (newer) bottom log sequence. If you roll forward through the bottom log sequence, you will not be able to use the table space-level backup image, Backup 3, to perform table space restore and rollforward recovery. To complete a table space rollforward operation to the end of the logs using the table space-level backup image, Backup 3, you will have to restore the database-level backup image, Backup 2, and then roll forward using the top log sequence. Once the table space-level backup image, Backup 3, has been restored, you can initiate a rollforward operation to the end of the logs.
Backup 1
Backup 2
Backup 3
0000010.LOG
0000011.LOG
0000012.LOG
0000013.LOG
0000014.LOG
0000013.LOG
Restore Backup 2 and Roll Forward to end of log 12.
0000014.LOG
63
7718TSMDB2_Database.fm
book. If you are interested and want to have more information review the DB2 information center at http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp.
Note: For the Tivoli Storage Manager server to work correctly and the integrated DB2 database being able to manage itself appropriately, use of the administration tools is not required.
C:\Program Files\Tivoli\TSM\db2\BIN>db2 (c) Copyright IBM Corporation 1993,2007 Command Line Processor for DB2 Client 9.5.2 You can issue database manager commands and SQL statements from the command prompt. For example:
64
7718TSMDB2_Database.fm
db2 => connect to sample db2 => bind sample.bnd For general help, type: ?. For command help, type: ? command, where command can be the first few keywords of a database manager command. For example: ? CATALOG DATABASE for help on the CATALOG DATABASE command ? CATALOG for help on all of the CATALOG commands. To exit db2 interactive mode, type QUIT at the command prompt. Outside interactive mode, all commands must be prefixed with 'db2'. To list the current command option settings, type LIST COMMAND OPTIONS. For more detailed help, refer to the Online Reference Manual. db2 => list active databases Active Databases Database name Applications connected currently Database path = TSMDB1 = 5 = G:\SERVER1\NODE0000\SQL00001\
Before you can submit commands against a Tivoli Storage Manager database, you need to tell the command line processor to establish a connection with the database with the db2 connect command, see Example 5-5. Once completed with your task submit the connect db2 connect reset command to free up resources. Note that for the db2 select command to work the fully qualified name in the form schema.table-name, in this case tsmdb1.nodes, must be used. An alias for the table cannot be used in place of the actual table. The schema is the user name under which the table or view was created.
Example 5-5 DB2: connect to database command
db2 => select nodename, platform from tsmdb1.nodes SQL1024N A database connection does not exist. SQLSTATE=08003 db2 => connect to tsmdb1 Database Connection Information Database server SQL authorization ID Local database alias = DB2/NT 9.5.2 = ADMINIST... = TSMDB1
-------------------------------------------------------------- ----------------OLDSKOOL WinNT db2 => connect reset DB20000I The SQL command completed successfully.
65
7718TSMDB2_Database.fm
You can use the command line processor to get detailed explanations on the reported SQLCODE and/or SQLSTATE. We use the SQL1024N and SQLSTATE=08003 from the previous example with Example 5-6. The user response reported confirms that we had to connect to the database.
Example 5-6 DB2: SQLCODE and SQLSTATE explained
SQL1024N
Explanation: There is no connection to a database. Other SQL statements cannot be processed unless an SQL CONNECT was previously executed. The command cannot be processed. User response: If the error occurred when disconnecting from the database, continue processing. If the error occurred on another SQL statement, issue an SQL CONNECT statement and resubmit the command or statement. sqlcode: -1024 sqlstate: 08003
db2 => ? 08003 SQLSTATE 08003: The connection does not exist. To verify the current database configuration, the db2 get db cfg command becomes helpful. You can familiarize with the result returned by reviewing Example 5-7. We highlighted some of the configurables you should already know about.
Example 5-7 DB2: get db cfg command db2 => get db cfg Database Configuration for Database Database configuration release level Database release level Database territory Database code page Database code set Database country/region code Database collating sequence Alternate collating sequence Number compatibility Varchar2 compatibility Database page size Dynamic SQL Query management = 0x0c00 = 0x0c00 = = = = = (ALT_COLLATE) = = = = C 819 ISO8859-1 1 IDENTITY OFF OFF 16384
(DYN_QUERY_MGMT) = DISABLE
66
7718TSMDB2_Database.fm
Restrict access Default query optimization class (DFT_QUERYOPT) Degree of parallelism (DFT_DEGREE) Continue upon arithmetic exceptions (DFT_SQLMATHWARN) Default refresh age (DFT_REFRESH_AGE) Default maintained table types for opt (DFT_MTTB_TYPES) Number of frequent values retained (NUM_FREQVALUES) Number of quantiles retained (NUM_QUANTILES) Decimal floating point rounding mode Backup pending Database is consistent Rollforward pending Restore pending Multi-page file allocation enabled Log retain for recovery status User exit for logging status Self tuning memory (SELF_TUNING_MEM) Size of database shared memory (4KB) (DATABASE_MEMORY) Database memory threshold (DB_MEM_THRESH) Max storage for lock list (4KB) (LOCKLIST) Percent. of lock lists per application (MAXLOCKS) Package cache size (4KB) (PCKCACHESZ) Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) Sort list heap (4KB) (SORTHEAP) Database heap (4KB) Catalog cache size (4KB) Log buffer size (4KB) Utilities heap size (4KB) Buffer pool size (pages) SQL statement heap (4KB) Default application heap (4KB) Application Memory Size (4KB) Statistics heap size (4KB) Interval for checking deadlock (ms) Lock timeout (sec) Changed pages threshold Number of asynchronous page cleaners Number of I/O servers Index sort flag Sequential detect flag Default prefetch size (pages) Track modified pages Default number of containers Default tablespace extentsize (pages) Max number of active applications (DBHEAP) (CATALOGCACHE_SZ) (LOGBUFSZ) (UTIL_HEAP_SZ) (BUFFPAGE) (STMTHEAP) (APPLHEAPSZ) (APPL_MEMORY) (STAT_HEAP_SZ)
(DECFLT_ROUNDING) = ROUND_HALF_EVEN = NO = NO = NO = NO = YES = NO = YES = = = = = = = = = = = = = = = = = ON AUTOMATIC 10 AUTOMATIC AUTOMATIC AUTOMATIC AUTOMATIC AUTOMATIC AUTOMATIC 260 98 48371 250 AUTOMATIC AUTOMATIC AUTOMATIC AUTOMATIC
(DLCHKTIME) = 10000 (LOCKTIMEOUT) = -1 (CHNGPGS_THRESH) (NUM_IOCLEANERS) (NUM_IOSERVERS) (INDEXSORT) (SEQDETECT) (DFT_PREFETCH_SZ) = = = = = = 80 AUTOMATIC AUTOMATIC YES YES AUTOMATIC
67
7718TSMDB2_Database.fm
Log file size (4KB) (LOGFILSIZ) Number of primary log files (LOGPRIMARY) Number of secondary log files (LOGSECOND) Changed path to log files (NEWLOGPATH) Path to log files log\ Overflow log path (OVERFLOWLOGPATH) elog\RstDbLog\ Mirror log path (MIRRORLOGPATH) First active log file Block log on disk full (BLK_LOG_DSK_FUL) Percent max primary log space by transaction (MAX_LOG) Num. of active log files for 1 active UOW(NUM_LOG_SPAN) Group commit count (MINCOMMIT) Percent log file reclaimed before soft chckpt (SOFTMAX) Log retain for recovery enabled (LOGRETAIN) User exit for logging enabled (USEREXIT) HADR HADR HADR HADR HADR HADR HADR HADR HADR database role local host name local service name remote host name remote service name instance name of remote server timeout value log write synchronization mode peer window duration (seconds)
= s:\tsm\server1\archiv = = = = = = = = = = = = = = = = = =
First log archive method (LOGARCHMETH1) = rchivelog\archmeth1\ Options for logarchmeth1 (LOGARCHOPT1) = Second log archive method (LOGARCHMETH2) = Options for logarchmeth2 (LOGARCHOPT2) = Failover log archive path (FAILARCHPATH) = elog\failarch\ Number of log archive retries on error (NUMARCHRETRY) = Log archive retry Delay (secs) (ARCHRETRYDELAY) = Vendor options (VENDOROPT) = Auto restart enabled (AUTORESTART) Index re-creation time and redo index build (INDEXREC) Log pages during index build (LOGINDEXBUILD) Default number of loadrec sessions (DFT_LOADREC_SES) Number of database backups to retain (NUM_DB_BACKUPS) Recovery history retention (days) (REC_HIS_RETENTN) Auto deletion of recovery objects (AUTO_DEL_REC_OBJ) TSM TSM TSM TSM management class node name owner password (TSM_MGMTCLASS) (TSM_NODENAME) (TSM_OWNER) (TSM_PASSWORD) (AUTO_MAINT) (AUTO_DB_BACKUP) (AUTO_TBL_MAINT) (AUTO_RUNSTATS) = = = = = = = = = = = = = = =
Automatic maintenance Automatic database backup Automatic table maintenance Automatic runstats
ON OFF ON OFF
68
7718TSMDB2_Database.fm
Automatic statement statistics Automatic statistics profiling Automatic profile updates Automatic reorganization Enable XML Character operations WLM Collection Interval (minutes)
= = = =
Use the db2 list db directory command to list the contents of the system database directory. If you specify an optional path, the contents of the local database directory are listed.
Example 5-8 DB2: list db directory command
db2 => list db directory System Database Directory Number of entries in the directory = 1 Database 1 entry: Database alias Database name Local database directory Database release level Comment Directory entry type Catalog database partition number Alternate server hostname Alternate server port number = = = = = = = = = TSMDB1 TSMDB1 G: c.00 Indirect 0
As shown with Example 5-9 you can use the db2 get instance command to verify the current instance, if you need a list of available instances see db2ilist - List instances command on page 610.
Example 5-9 db2: get instance command
db2 => get instance The current database manager instance is: SERVER1
Use the db2 describe table command to list details on a specific table. As shown with Example 5-10, the command lists the following information about each column: Column name Type schema Type name Length ScaleNulls (yes/no)
Example 5-10 DB2: describe table command db2 => describe table tsmdb1.activity_log Data type Column Chapter 5. IBM Tivoli Storage Manager database
69
7718TSMDB2_Database.fm
Column name ------------------------------DATETIME UNIQUE MESSAGENUM MESSAGE ORIGINATOR SESSIONID SEVERITY NODENAME OWNERNAME SCHEDNAME DOMAINNAME SERVERNAME SESSIONTOKEN PROCESSTOKEN 14 record(s) selected.
schema --------SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM SYSIBM
Data type name Length Scale Nulls ------------------- ---------- ----- -----TIMESTAMP 10 0 No INTEGER 4 0 No INTEGER 4 0 No VARCHAR 2001 0 No INTEGER 4 0 No INTEGER 4 0 Yes SMALLINT 2 0 Yes VARCHAR 65 0 Yes VARCHAR 65 0 Yes VARCHAR 31 0 Yes VARCHAR 31 0 Yes VARCHAR 65 0 Yes INTEGER 4 0 Yes INTEGER 4 0 Yes
To query DB2 for the current code release level use the db2level command as shown with Example 5-12.
Example 5-12 DB2: db2level system command C:\Program Files\Tivoli\TSM\db2\BIN>db2level
70
7718TSMDB2_Database.fm
DB21085I Instance "SERVER1" uses "32" bits and DB2 code release "SQL09052"with level identifier "03030107". Informational tokens are "DB2 v9.5.201.3237", "special_21101", "WR21421_21101", and Fix Pack "2a". Product is installed at "C:\PROGRA~1\Tivoli\TSM\db2" with DB2 Copy Name "DB2TSM1".
To query DB2 for the current code release level use the db2level command as shown with Example 5-13.
Example 5-13 DB2: db2level system command
C:\Program Files\Tivoli\TSM\db2\BIN>db2licm -l Product name: "DB2 Enterprise Server Edition" License type: "Restricted" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "9.5"
You can use the db2start and db2stop commands to start and stop the DB2 database manager, however the preferred method to stop is a halt command submitted by either the Tivoli Storage Manager command line or by an administrative user. Use the commands only if directed so by IBM, if you try to stop or start DB2 while the Tivoli Storage Manager server is up and running an error will be reported. Messages SQL1025N and SQL1026N, as shown with Example 5-14, remind you not to submit the commands while the Tivoli Storage Manager server is up.
Example 5-14 DB2: dbstart and dbstop commands
C:\Program Files\Tivoli\TSM\db2\BIN>db2stop SQL1025N The database manager was not stopped because databases are still active. C:\Program Files\Tivoli\TSM\db2\BIN>db2start SQL1026N The database manager is already active. Appendix B, DB2 and SQL commands on page 603 lists additional DB2 and DB2 system commands you will find to be useful. f you are interested in more information on the CLP have a look at DB2 Basics: Getting to know the DB2 UDB command line processor, http://www.ibm.com/developerworks/db2/library/techarticle/dm-0503melnyk/
71
7718TSMDB2_Database.fm
By default the Tivoli Storage Manager instance is not configured for access by the DB2 Control Center. In the following figures we explain how to setup the DB2 Control Center so you can act on the database. Figure 5-5 shows the initialisation screen presented to you with the invocation of the DB2 Control Center.
Next you are asked to specify the DB2 Control Center view type. Select the Advanced view type, an click OK.
The DB2 Control Center opens in the object view. You can use the object tree to display and work with system and database objects. The object tree displays the relation between objects in a hierarchy. You expand the object tree down from a particular object, the objects that reside, or are contained, in that object are displayed underneath.
72
7718TSMDB2_Database.fm
To invoke actions on an object in the object tree, right-click to open a pop-up menu of available actions. Then select a menu choice. A window or notebook opens to guide you through the steps required to complete the action. You will see examples later.
If, from a fresh installation, you try to expand All Databases, as shown with Figure 5-7, the expansion selector (+) disappears. No database is configured to be accessible by the DB2 Control Center so far. Next you press the expansion selector (+) to expand All Systems, see Figure 5-8 on page 74
73
7718TSMDB2_Database.fm
At this point, the local system Idaho is the only system known to the DB2 Control Center. You press the expansion selector (+) to expand the IDAHO system branch.
74
7718TSMDB2_Database.fm
Next you press the expansion selector (+) to expand the IDAHO system Instances branch.
The DB2 Control Center expands the instances branch, the default DB2TSM is shown. The DB2TSM instance is a dummy instance created during the installation of the Tivoli Storage manager product. DB2 makes it the default instance then. If you open a command window, or start up the DB2 Control Center, this is the instance that is going to be acted on. hat makes it the default instance is the fact that the DB2INSTANCE environment variable is set in your user profile, and it points to this the DB2TSM instance. Note: Future versions of the product might no longer create the dummy DB2TSM instance.
75
7718TSMDB2_Database.fm
If you try to expand the DB2TSM databases, as shown with Figure 5-12 and Figure 5-13 on page 77, the expansion selector (+) just disappears. No database is configured for the dummy instance.
76
7718TSMDB2_Database.fm
77
7718TSMDB2_Database.fm
Now you start adding the Tivoli Storage Manager server instance to the DB2 Control Center, select the IDAHO Instances branch as shown with Figure 5-14.
Right-click the Instances branch, then select Add from the action options as shown with Figure 5-15 on page 79.
78
7718TSMDB2_Database.fm
Figure 5-15 DB2 Control Center: IDAHO Instances branch action options
The Add Instance window allows you to make the Tivoli Storage Manager server instance available to the DB2 Control center. As shown with Figure 5-16 just press Discover.
The Discovery Search window allows you to select from detected instances. You select the SERVER1 instance and click OK.
79
7718TSMDB2_Database.fm
Figure 5-18 shows that next you are prompted for an Instance Node Name. A unique nickname is required.
In Figure 5-19 on page 81 we specify IDAHO_S1 as the instance node name, and click Apply to continue.
80
7718TSMDB2_Database.fm
Next click on the new IDAHO_S1 (SERVER1) instance you just created as shown in Figure 5-20 on page 81.
The Databases branch for IDAHO_S1 (SERVER1) is displayed (see Figure 5-21 on page 82). If you try to expand that, again the expansion selector (+) disappears.
81
7718TSMDB2_Database.fm
Right-click the Databases branch for action options, then select Add as shown with Figure 5-22 on page 83.
82
7718TSMDB2_Database.fm
Again you can click Discover, this time to search for available databases as shown in Figure 5-23 on page 83.
From the database discovery search window, select the Tivoli Storage Manager database, TSMDB1, and click OK to continue (see Figure 5-24 on page 84).
83
7718TSMDB2_Database.fm
On the Add Database window you can specify an Alias and an additional Comment. In our example you accept the details and click Apply (see Figure 5-25 on page 84).
By default the DB2 Control Center tries to search additional databases, click Cancel to return the the DB2 Control Center object view (see Figure 5-26 on page 85).
84
7718TSMDB2_Database.fm
Figure 5-26 DB2 Control Center: cancel search for additional databases
At this point you completed the task, instance IDAHO_S1 and the database TSMDB1 are accessible through the DB2 Control Center (see Figure 5-27 on page 85).
Figure 5-27 DB2 Control Center: TSMDB1 configured for instance IDAHO_S1
You can also manually make the database and the instance available to the DB2 ControlCenter. What the DB2 Control Center actually does when you add the server instance as described above, is to define it as a remote node/instance in the local, default instance using a command as sown below. CATALOG LOCAL NODE node-name INSTANCE tsm-instance-name When you go and add the database in DB2 Control Center, it catalogs it as a remote database on that remote node/instance, using a command similar to the following:
85
7718TSMDB2_Database.fm
CATALOG DATABASE TSMDB1 AS alias-name ON node-name The effect of both of these commands is that the new Tivoli Storage Manager instance and the new database are both cataloged in the local, default instance. For an example of this approach being documented see Client ODBC configuration on page 591. Alternatively, you can set the db2instance environment variable and then invoke the DB2 Control Center with the db2cc command as shown in Example 5-15.
Example 5-15 Setting the db2instance environment variable
86
7718TSMDB2_Database.fm
TSM Server
3 1 2 3 4 Initiate database backup Intercept inbound session from DB2 Stream backup to seq. datastream Add volume to volume history 4
Volhist
The first time we get into contact with a server database back up being performed is right after installation. You will see the messages as reported with Example 5-16 on page 87.
Example 5-16 ANR2976I and ANR2974I
The ICC support module has been loaded. Database manager successfully started. Database manager successfully started. The buffer pool monitor switch is enabled. Server formatting complete, database ready for loading. Stopping the database manager because of a server shutdown. Offline DB backup for database TSMDB1 started. Offline DB backup for database TSMDB1 completed successfully.
87
7718TSMDB2_Database.fm
After completing the installation and configuration of the server, it is recommended that a FULL database backup be performed. This database backup and any subsequent database backups will be tracked in the server volume history, as expected, and used as part of the server disaster recovery manager (DRM) processing.
tsm: TIRAMISU>backup db devc=file ANR2590E BACKUP DB failed - SET DBRECOVERY command has not been issued. So we submit the SET DBRECOVERY, see Example 5-18 for the results.
Example 5-18 SET DBRECOVERY command.
tsm: TIRAMISU>set dbrecovery file ANR2782I SET DBRECOVERY completed successfully and device class for automatic DB backup is set to FILE. You use the SET DBRECOVERY command to specify the device class to be used for full automatic backups. You can verify the current setting with the QUERY DB FORMAT=DETAIL command as shown in Example 5-19 on page 88.
Example 5-19 Query the database and verify DBRECOVERY setting
TSM:TIRAMISU>q db f=d ANR2017I Administrator SERVER_CONSOLE issued command: QUERY DB f=d Database Name: Total Size of File System (MB): Space Used by Database(MB): Free Space Available (MB): Page Size(Bytes): Total Pages: Usable Pages: Used Pages: Free Pages: Buffer Pool Hit Ratio: Total Buffer Requests: Sort Overflows: Lock Escalation: Package Cache Hit Ratio: Last Database Reorganization: Full Device Class Name: Incrementals Since Last Full: Last Complete Backup Date/Time: TSMDB1 59,389 448 27,231 32,772 32,636 23,740 8,896 97.4 53,137 0 0 68.5 FILE 1 06/03/2009 09:19:32
As you can see with Example 5-19 on page 88 above, the output returned by the QUERY DATABASE command has changed, Table 5-6 gives you the details:
88
7718TSMDB2_Database.fm
Table 5-6 QUERY DATABASE description Field Database Name Total Size of File System (MB) Description The name of the database Total space in MB in the current storage location Windows: Total space on the drive where the directory is located UNIX and Linux: Total space in the file system where the path is located Space Used by Database(MB) Free Space Available (MB) Space in MB currently allocated and in use in the current storage location Space in MB not in use but available in the database Windows: Space remaining on the drive where the directory is located UNIX and Linux: Space remaining in the file system where the path is located Page Size(Bytes) Total Pages Usable Pages Used Pages Free Pages Buffer Pool Hit Ratio The database page size (in bytes) Total number of pages in table space. The number of usable pages in table space. The number of used pages in table space Number of pages not in use in table space. The total hit ratio percent. The ratio of physical reads to logical reads gives the hit ratio for the bufferpool. The lower the hit ratio, the more the data is being read from disk rather than the cached buffer pool which can be a more costly operation The total number of bufferpool data logical reads and index logical reads since the last time the database was started or since the database monitor was reset. The total number of sorts that ran out of the sort heap and might have required disk space for temporary storage The number of times that locks have been escalated from several row locks to a table lock. A percentage indicating how well the package cache is helping to avoid reloading packages and sections for static SQL from the system catalogs. It also indicates how well the package cache is helping to avoid recompiling dynamic SQL statements. A high ratio indicates it is successful in avoiding these activities The last time that the database manager performed an automatic reorganization activity The name of the device class this is used for full database backups. The number of incremental backups that were performed since the last full backup.
Last Database Reorganization Full Device Class Name Incrementals Since Last Full
89
7718TSMDB2_Database.fm
Completing the SET DBRECOVERY was easy, now we can start the database backup again (see Example 5-20).
Example 5-20 Backup DB still terminates
TSM:TIRAMISU>backup db devc=file ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB devc=file ANR4559I Backup DB is in progress. ANR0984I Process 3 for DATABASE BACKUP started in the BACKGROUND at 12:23:14. ANR2281I Incremental database backup started as process 3. TSM:TIRAMISU> ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc: 406. ANR0985I Process 3 for DATABASE BACKUP running in the BACKGROUND completed with completion state FAILURE at 12:23:15. Example 5-20 documents the backup still fails. When a BACKUP DB or RESTORE DB command fails with a message indicating the DB2 SQLCODE or the SQLERRMC with return codes, you can get a description of the DB2 SQLCODE by completing the following procedures: 1. On a Windows operating sytem, click Start All Programs IBM DB2 <DB2 Instance> Command Line Tools Command Line Processor to open a DB2 command-line interface. For all other supported platforms, log on to the DB2 instance ID and open a shell window, then issue the command DB2. 2. Enter the SQLCODE. For example, if the DB2 SQLCODE is -2033, issue the command as documented with Example 5-21.
Example 5-21 Retrieve DB2 SQLCODE descriptions
SQL2033N An error occurred while accessing TSM during the processing of a database utility. TSM reason code: "<reason-code>". Explanation: Some common TSM reason codes are: 106 The specified file is being used by another process. You tried to read from or write to a file that is currently being used by another process. TSM authentication failure. Password file is needed, but user is not root. This message is often generated when the DSMI_DIR environment variable points to a directory that contains a 32-bit version of the dsmtca program, yet the DB2 instance is 64-bit, or vice-versa. An invalid option was specified on the OPTIONS parameter passed
137 168
400
90
7718TSMDB2_Database.fm
The utility stops processing. User response: Responses for common TSM problems are: 106 Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location. If the TSM parameter PASSWORDACCESS is that the system administrator has used set the password. If PASSWORDACCESS is that the TSM_NODENAME and TSM_PASSWORD parameters have been set correctly. set to GENERATE, ensure the dsmapipw utility to set to PROMPT, ensure database configuration
137
168
Ensure that DSMI_DIR points to a directory containing the correct version of db2tca, restart the instance, and execute the command again. Ensure that the OPTIONS parameter specified on the BACKUP or RESTORE command is correct. Ensure that the DSMI_CONFIG environment variable points to a valid TSM options file. Ensure that the instance owner has read access to the dsm.opt file. Ensure that the DSMI_CONFIG environment variable is set in the db2profile.
400
406
In general, the sqlcode -2033 errors are all set up related errors. As we did not do any configuration for the database backup to work through the API we have to do that now. If you use the Tivoli Storage Manager Server Instance Configuration wizard to create a server instance, configuration is done automatically. If you are configuring an instance manually, for the back up to work, the following requirements must be met: Tivoli Storage Manager API is installed on server machine (done by COI install) Tivoli Storage Manager API has the correct client option settings DSMI_DIR, DSMI_CONFIG, DSMI_LOG environment variables are set in DB2 instance process DSMI_DIR, DSMI_CONFIG, DSMI_LOG point to correct places Api executables Api configuration files Api log file directory The correct password is set Here we guide you through a manual configuration, so first we need to resolve the DB2 SQLCODE -2033 SQLERRMC 406. SQL error message code 406 requires that the following issues are resolved: The DSMI_CONFIG environment variable points to a valid Tivoli Storage Manager options file. The instance owner has read access to the dsm.opt file.
91
7718TSMDB2_Database.fm
The DSMI_CONFIG environment variable is set in the db2profile. The steps required to complete the task are: 1. We create a file we name tsmdbmgr.env in the instance directory with the content documented in Example 5-22.
Example 5-22 Content of tsmdbmgr.env
DSMI_CONFIG=g:\progra~1\tivoli\tsm\server1\tsmdbmgr.opt DSMI_LOG=g:\progra~1\tivoli\tsm\server1 2. We set the DSMI_ api environment-variable configuration for the database instance. Open a DB2 command window, on the Windows operating sytem, click Start All Programs IBM DB2 <DB2 Instance> Command Line Tools Command Window. This will open a window in the DB2 install directory, from here you can submit the db2set ommand,as shown in Example 5-23.
Example 5-23 DB2 CLP: db2set command
C:\Program Files\Tivoli\TSM\db2\BIN>db2set -i server1 DB2_VENDOR_INI=g:\progra~1\tivoli\tsm\server1 To verify the current setting of the DB2_VENDOR_INI variable you can submit the command as shown in Example 5-24.
Example 5-24 Verify DB2_VENDOR_INI setting
3. Now we create the tsmdbmgr.opt file in the \program files\tivoli\tsm\server1 directory with the following contents:
Example 5-25 tsmdbmgr.opt file
nodename $$_TSMDBMGR_$$ commmethod tcpip tcpserveraddr localhost tcpport 1500 passwordaccess generate errorlogname g:\progra~1\tivoli\tsm\server1\tsmdbmgr_server1.log The $$_TSMDBMGR_$$ node is a special hidden nodefor the purpose of the database backup. You cant query the node on the server using the QUERY NODE command. 4. Next we make the changes active to DB2, we use the command window from above and submit the following commands shown in Example 5-26.
Example 5-26 Activating the DB2 changes
C:\Program Files\Tivoli\TSM\db2\BIN>SET DB2INSTANCE=server1 C:\Program Files\Tivoli\TSM\db2\BIN>db2stop SQL1064N DB2STOP processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2start SQL1063N DB2START processing was successful.
92
7718TSMDB2_Database.fm
It is important to stop and restart DB2 to activate the changes. Failing to do so will result in the backup not working later. 5. We set the correct password as shown with Example 5-27. If you are use to the dsmcutil command note the slight difference: this is the dsmsutil command you find in the server installation directory. The password, TSMDBMGR, is preset at the server and cannot be changed as the special node, $$_TSMDBMGR_$$. The password for this node does not expire!
Example 5-27 Update password for $$_TSMDBMGR_$$
C:\Documents and Settings\Administrator>set DSMI_CONFIG=g:\progra~1\tivoli\tsm\server1\tsmdbmgr.opt C:\Documents and Settings\Administrator>"C:\Program Files\Tivoli\TSM\server\dsms util" UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO TSM Windows NT Client Service Configuration Utility Command Line Interface - Version 6, Release 1, Level 0.0 1027FB (C) Copyright IBM Corporation, 1990, 2008, All Rights Reserved. Last Updated Oct 28 2008 TSM Api Version 6.1.0 Command: Update Registry Password Machine: GALLIUM(Local Machine) The Registry password for node $$_TSMDBMGR_$$ has been updated . You can also use the dsmapipw command to propagate the password to the Tivoli Storage Manager Server as shown with Example 5-28. Change the directory to the servers db2\adsm directory, for example to C:\Program Files\tivoli\TSM\db2\adsm and then submit the command.
Example 5-28 Use dsmapipw to propagate the password to the server
C:\Program Files\tivoli\TSM\db2\adsm>set DSMI_CONFIG=g:\progra~1\tivoli\tsm\server1\tsmdbmgr.opt C:\Program Files\tivoli\TSM\db2\adsm>dsmapipw ************************************************************* * Tivoli Storage Manager * * API Version = 6.1.0 * ************************************************************* Enter your current password:TSMDBMGR
93
7718TSMDB2_Database.fm
6. Finally we can submit the database backup, so let us give the backup database command a try. Example 5-29 documents the results and shown we managed to complete the task.
Example 5-29 The first manual backup
TSM:TIRAMISU>backup db devc=file type=full ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB devc=file type=full ANR4559I Backup DB is in progress. ANR0984I Process 10 for DATABASE BACKUP started in the BACKGROUND at 09:29:37. ANR2280I Full database backup started as process 10. TSM:TIRAMISU> ANR0406I Session 17 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(4668)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44132980.DBV mounted. ANR0511I Session 17 opened output volume G:\TSM\SERVER1\FILECLASS\44132980.DBV.A NR1360I Output volume G:\TSM\SERVER1\FILECLASS\44132980.DBV opened (sequence number 1). ANR1361I Output volume G:\TSM\SERVER1\FILECLASS\44132980.DBV closed. ANR0514I Session 17 closed volume G:\TSM\SERVER1\FILECLASS\44132980.DBV. ANR0403I Session 17 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR0406I Session 18 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(4673)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44133021.DBV mounted. ANR0511I Session 18 opened output volume G:\TSM\SERVER1\FILECLASS\44133021.DBV.A NR1360I Output volume G:\TSM\SERVER1\FILECLASS\44133021.DBV opened (sequence number 1). ANR1361I Output volume G:\TSM\SERVER1\FILECLASS\44133021.DBV closed. ANR0514I Session 18 closed volume G:\TSM\SERVER1\FILECLASS\44133021.DBV. ANR0403I Session 18 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR4550I Full database backup (process 10) completed. ANR0985I Process 10 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 09:30:23. Note that the configuration for a UNIX server database backup through the API differs slightly from the example for the Windows platform we went through here. If you want to configure for a different environment, have a look for the Preparing the database manager for backup chapter available from the infocenter at http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm. srv.install.doc/t_srv_prep_dbmgr.html Remember the SET DBRECOVERY command we submitted with Example 5-18 on page 88? If you submit the BACKUP DB command with a different device class a warning message ANR4976W will be reported, reminding you about the DBRECOVERY default device class as shown with Example 5-30 on page 94.
Example 5-30 ANR4976W, database backup to different device class
TSM:TIRAMISU>backup db type=full devc=test ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=full devc=test ANR4976W The device class TEST is not the same as device class FILE defined for the serverbackup node $$_TSMDBMGR_$$. ANR2280I Full database backup started as process 14.ANR4559I Backup DB is in progress. ANR0984I Process 13 for DATABASE BACKUP started in the BACKGROUND at 10:39:47.
94
7718TSMDB2_Database.fm
the serverbackup node $$_TSMDBMGR_$$. ANR2280I Full database backup started as process 13. As we mentioned earlier, if you use the Tivoli Storage Manager Server Instance Configuration wizard to create a server instance, configuration is done automatically. By using the wizard, you can avoid some configuration steps that are complex when done manually. Start the wizard on the system where you installed the Tivoli Storage Manager Version 6.1 server. On a UNIX box you find the dsmifgx program in the Tivoli Storage Manager servers bin directory, on a Windows box you can double-click the dsmicfgx.exe program in the C:\Program Files\Tivoli\TSM\server directory. Note: It is recommended to use the the GUI post-install configuration, dsmicfgx or dsmicfgx.exe, to configure the server for database backup. You avoid some configuration steps that are complex when done manually.
Summary
You do not t need to submit DB2 commands to backup a Tivoli Storage Manager V6.1 database. You can still use the known backup commands for manual database backups, as you did with earlier versions. However, you need to configure the server to be able to backup through the API used by DB2 to complete the task.
Backup methodologies
If the Tivoli Storage Manager server database or the recovery log is unusable, the entire server is unavailable. If a database is lost and cannot be recovered, all of the data managed by that server is lost. If a storage pool volume is lost and cannot be recovered, the data on the volume is also lost. To back up the database and storage pools regularly, define administrative schedules. If you lose your database or storage pool volumes, you can use offline utilities provided by IBM Tivoli Storage Manager to restore your server and data. With the proprietary database it has been widely used practice to configure for regular full backups followed by a sequence of incremental backups. The maximum number of incremental backups you can run between full backups is 32. Assumed you scheduled for weekly full backups the scenario looks like the one shown with Figure 5-29.
95
7718TSMDB2_Database.fm
V5 database backup
Sun Full
Mon Incr
Tue Incr
Wed Incr
Thu Incr
Fri Incr
Sat Incr
Sun Full
With the Tivoli Storage Manager V6.1 backup command, at a first look things might not have changed much as the database backup methodologies supported are: Full Backup Specifies that you want to run a full backup of the Tivoli Storage Manager database. For devclass tape, at least one tape volume used Contains the database backup and also active/archive logs since last full For devclass file, at least two volumes used First contains the database backup, the second contains active/archive logs since last full backup. Clears the archive logs Incremental Backup Specifies that you want to run an incremental backup of the Tivoli Storage Manager database. An incremental (or cumulative) backup image contains a copy of all database data that has changed since the last successful full backup operation was performed. For devclass tape, at least one volume used. Contains changed pages, plus initial database metadata. For devclass file, at least two volumes used. Contains changed pages, plus initial database metadata. Tivoli Storage Manager database snapshot Specifies that you want to run a full snapshot database backup. The entire contents of a database are copied and a new snapshot database backup is created without interrupting the existing full and incremental backup series for the database. Snapshot database backups should be used in addition to full and incremental backups. For devclass tape, at least one tape volume used Contains the DB backup and also active/archive logs since last full backup. At least two volumes used
96
7718TSMDB2_Database.fm
First contains the DB backup, second contains active/archive logs since last full backup. The following file device class volume naming conventions apply: DBV - normal backup file device class volume DSS - snapshot backup file device class volume Now let us compare the V5 style database backup schedule with the same approach adopted to a Tivoli Storage Manager V6.1 server. Figure 5-30 shows how the space requirements rise with each incremental backup. .
V6 database backup
Sun Full
Mon Incr
Tue Incr
Wed Incr
Thu Incr
Fri Incr
Sat Incr
Sun Full
In DB2 terms, the backup methodology introduced for the Tivoli Storage Manager server is an incremental cumulative backup. The incremental database now represents all database data that has changed since the most recent, successful, full backup operation. If you plan to restore to Wednesdays backup, you only need Sundays full backup, plus the last incremental backup for Wednesday. If you want to complete the same task in V5 you need Sundays full backup and the incremental backup volumes from Monday, Tuesday and Wednesday. If you are used to the methodology of weekly full database backups and in between incremental backups you should however notice the difference when staying with this approach: 1. Only full backups allow for the deletion of archive log volumes 2. The incremental backups will not free archive log space, requiring more space in the archive log directories. 3. The incremental database backups result in increased volume utilization to include the additional archive log information.
97
7718TSMDB2_Database.fm
administrator to monitor the activity log and adjust the scheduled backups to best meet your requirements. You define the scheduled database backup as an administrative schedule as you are used to, see Example 5-31 for the exact command.
Example 5-31 Define a schedule for full database backup
TSM:TIRAMISU>define schedule db_daily_backup type=administrative cmd="backup db deviceclass=file type=full" starttime=10:00 ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE SCHEDULE db_daily_backup type=administrative cmd='backup db deviceclass=file type=full' starttime=10:00 ANR2577I Schedule DB_DAILY_BACKUP defined. TSM:TIRAMISU>q sched db_daily_backup type=admin f=d ANR2017I Administrator SERVER_CONSOLE issued command: QUERY SCHEDULE db_daily_backup type=admin f=d Schedule Name: Description: Command: Priority: Start Date/Time: Duration: Schedule Style: Period: Day of Week: Month: Day of Month: Week of Month: Expiration: Active?: Last Update by (administrator): Last Update Date/Time: Managing profile: DB_DAILY_BACKUP backup db deviceclass=file type=full 5 06/12/2009 10:00:00 1 Hour(s) Classic 1 Day(s) Any
With the above setup we protect the server by running database backups at least once per day. Even more frequent backups might be needed if the server handles high numbers of client transactions. You need to monitor the activity log for triggered database backups starting and messages indicating a database backup is required, for this see Table 5-9 on page 102. The observation will allow for proper scheduling. A best practice is to schedule regular backups of the server database, and verify that they occur as scheduled. We do this with Example 5-32.
Example 5-32 Verification that scheduled database backups are working
ANR2750I Starting scheduled command db_daily_backup ( backup db deviceclass=file type=full ). ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=full devc=file ANR0984I Process 2 for DATABASE BACKUP started in the BACKGROUND at 14:51:29. ANR2280I Full database backup started as process 2. TSM:TIRAMISU> ANR0406I Session 1 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(3223)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44843491.DBV mounted. 98
7718TSMDB2_Database.fm
ANR0511I Session 1 opened output volume G:\TSM\SERVER1\FILECLASS\44843491.DBV. ANR1360I Output volume G:\TSM\SERVER1\FILECLASS\44843491.DBV opened (sequence number 1). ANR1361I Output volume G:\TSM\SERVER1\FILECLASS\44843491.DBV closed. ANR0514I Session 1 closed volume G:\TSM\SERVER1\FILECLASS\44843491.DBV. ANR0403I Session 1 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR0406I Session 2 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(3249)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44843516.DBV mounted. ANR0511I Session 2 opened output volume G:\TSM\SERVER1\FILECLASS\44843516.DBV. ANR1360I Output volume G:\TSM\SERVER1\FILECLASS\44843516.DBV opened (sequence number 1). ANR1361I Output volume G:\TSM\SERVER1\FILECLASS\44843516.DBV closed. ANR0514I Session 2 closed volume G:\TSM\SERVER1\FILECLASS\44843516.DBV. ANR0403I Session 2 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR4550I Full database backup (process 2) completed. ANR0985I Process 2 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 14:51:57.
99
7718TSMDB2_Database.fm
ANR4531I: An automatic full database backup will be started. The last log number used is last log used and the first log number used is first log used. The log file size is log file size megabytes. The maximum log file size is maximum log file size megabytes. Log utilization ratio The DB2 API db2GetSnapshot() function is used to get totalActiveLogSpaceUsed and totalActiveLogSpaceAvailable. The log utilization ratio is calculated with the following formula: logUsedRatio = totalActiveLogSpaceUsed / ( totalActiveLogSpaceUsed + totalActiveLogSpaceAvailable ) If the logUsedRatio exceeds the predefined threshold of 80%, an automatic incremental backup will be triggered. ANR4529I: An automatic full or incremental database backup will be started. The active log space used is active log space used megabytes, and the active log space available is active log space available megabytes. The ratio, ratio, exceeds the threshold 0.80. Use the QUERY LOG F=D command to monitor the log usage, the output changed from earlier versions. For details see Example 5-33. If the server is not running, you can use the DSMSERV DISPLAY LOG utility. See Example 5-40 on page 108 for details.
Example 5-33 QUERY LOG command
TSM:TIRAMISU>q log f=d ANR2017I Administrator SERVER_CONSOLE issued command: QUERY LOG f=d Total Used Free Active Log Mirror Log Archive Failover Log Archive Log Space(MB): Space(MB): Space(MB): Directory: Directory: Directory: Directory: 2,048 0.28 2,039.72 d:\tsm\server1\activelog
d:\tsm\server1\archivelog
Note that the above configuration is not recommended, active log and archive log, as well as the database directories, should not be configured to a single disk. Table 5-7 explains the new fields for the QUERY LOG F=D command.
Table 5-7 QUERY LOG command Field Total Space(MB) Used Space(MB) Free Space(MB) Active Log Directory Description Specifies the maximum size in megabytes of the active log. Specifies the total amount of active log space that is used in the database in megabytes Specifies the amount of active log space in the database that is not being used by uncommitted transactions in megabytes Specifies the location where active log files are stored. When you change the active log directory, the server moves all archived logs to the archive log directory and all active logs to a new active log directory
100
7718TSMDB2_Database.fm
Field Mirror Log Directory Archive Failover Log Directory Archive Log Directory
Description Specifies the location where the mirror for the active log is maintained Specifies the location into which the server saves archive logs if the logs cannot be archived to the archive log directory Specifies the location into which the server can archive a log file after all the transactions that are represented in that log file are completed
Coming back to triggered backups, if you are used to the DBBACKUPTRIGGER option, you need to understand that this configurable is no longer available. Table 5-8 compares the Tivoli Storage Manager V5 database backup trigger options with the new database trigger functionality.
Table 5-8 Comparison of trigger attributes
Attribute Description
V6.1 Equivalent
Comments
V6.1 triggered backups use the device class specified with the SET DBRECOVERY command. This is essentially equivalent behavior to what was previously available in V5.x. If the log space used since the last backup exceeds the configured ACTIVELOGSIZE, a full database backup is triggered. An incremental backup is triggered when the log utilization ratio exceeds 80%. See Chapter , Triggered automatic backups on page 99 for details.
LOGFULLPct
When log utilization reaches this percentage, an automatic database backup starts.
None
INCRDEVCLASS
Device class used for triggered incremental backups. The number of incremental backups to perform before the next FULL must be performed. The minimum time to elapse between allowing triggered backups.
None
V6.1 triggered backups use the device class specified with the SET DBRECOVERY command.
NUMINCremental
None
MININTERVAL
None
101
7718TSMDB2_Database.fm
Attribute Description
V6.1 Equivalent
Comments
Minimum percentage of log space that must be freed by the automatic backup before it will be performed.
None
While the database backups with V6.1 do impact log utilization and the DB2 archival log operations, the differences in log management and overall log capacity mitigate this difference.
a. For some configurations, this message can be ignored. See the following technote for details: http://www.ibm.com/support/docview.wss?uid=swg21380107
Online table reorganization consumes log space. As a result of the log use because of database reorganization, a database backup might become necessary to manage the available active log space. Example 5-34 on page 102 shows the messages being issued for the BF.Aggregated.Bitfiles and the Backup.Objects table.
Example 5-34 ANR0293I, ANR0294I:Indicators for database backup requirement
Reorganization for table BF.Aggregated.Bitfiles started. Reorganization for table BF.Aggregated.Bitfiles ended. Reorganization for table Backup.Objects started. Reorganization for table Backup.Objects ended.
102
7718TSMDB2_Database.fm
Store at least one copy of the volume history file offsite or on a disk separate from the database Store a printout of the file offsite Store a copy of the file offsite with your database backups and device configuration file Store a remote copy of the file, for example, on an NFS-mounted file system. DRM: DRM saves a copy of the volume history file in its disaster recovery plan file. For DRM restore scenarios see Chapter 6, IBM Tivoli Storage Manager Disaster Recovery Manager on page 123 The VOLUMEHISTORY server option lets you specify backup volume history files. Then, whenever the server updates volume information in the database, it also updates the same information in the backup files. If you try to back up a database without a valid VOLUMEHISTORY option configured to the dsmserv.opt file, the backup will fail with message ANR2639E as shown with Example 5-35.
Example 5-35 ANR2639E; VOLUMEHISTORY option not configured
TSM:TIRAMISU>backup db type=full devc=file ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=full devc=file ANR2639E BACKUP DB failed - no files have been defined for storing sequential volume history information.
Summary
In Tivoli Storage Manager V5.x, the log was circular and as such the notion of how much log would be freed up by a database backup had significance because it implied that the log was healthy and the tail of the log could be moved up to free some amount of space based on the database backup. With Tivoli Storage Manager V6, the log no longer is circular, so the need to free a specific amount of log space during a database backup is no longer significant. Database backup with Tivoli Storage Manager V6.1 is oriented on protecting the database then was previously the case. While the V5 database backup triggers are no longer supported, Tivoli Storage Manager still triggers automatic backups. Depending on which trigger is met, a full or an incremental backup is executed.
103
7718TSMDB2_Database.fm
TSM Server
Volhist
4
1 2 3 4 Retrieve volume history information Initiate DB2 restore Intercept inbound session from DB2 Initiate database backup
Three types of database restore operations are supported: restoring the database to its most current state restoring the database to a point in time restoring the database from a snapshot This section will provide an example of a restore scenario and which requirements to meet for a successfully restore.
Restore prerequisites
To restore your database, the following information is required: You must have copies of the volume history file and the device configuration file. You must have copies of, or you must be able to create, the server options file and the database and recovery log set up information (the output from detailed queries of your database and recovery log). The server needs information from the volume history file. Volume history information is stored in the database, but during a database restore, it is not available from there. It is critical that you make a copy of your volume history file and save it. The file cannot be recreated. The database volumes we created with the database backup from Example 5-29 on page 94 are listed by the volume history file as shown with Example 5-36 below.
104
7718TSMDB2_Database.fm
********************************************************************************* * * Sequential Volume Usage History * Updated 06/04/2009 09:30:23 * ********************************************************************************* Operation Date/Time: 2009/06/12 14:51:29 Volume Type: BACKUPFULL * Location for volume G:\TSM\SERVER1\FILECLASS\44843491.DBV is: '' Database Backup LLA: FULL_BACKUP.20090612145129.1 Database Backup HLA: \NODE0000\ Volume Name: "G:\TSM\SERVER1\FILECLASS\44843491.DBV" Backup Series: 5 Backup Op: 0 Volume Seq: 1 Device Class Name: FILE Database Backup ID: 0 , 3073 Database Backup Home Position: 0 Database Backup Total Data Bytes : 0 , 381800459 Database Backup Total Log Bytes: 0 , 13656075 Database Backup Log Block Number: -1 , -1 ************************************************** Operation Date/Time: 2009/06/12 14:51:29 Volume Type: BACKUPFULL * Location for volume G:\TSM\SERVER1\FILECLASS\44843516.DBV is: '' Database Backup LLA: FULL_BACKUP.20090612145129.2 Database Backup HLA: \NODE0000\ Volume Name: "G:\TSM\SERVER1\FILECLASS\44843516.DBV" Backup Series: 5 Backup Op: 0 Volume Seq: 2 Device Class Name: FILE Database Backup ID: 0 , 3074 Database Backup Home Position: 0 Database Backup Total Data Bytes : 0 , 381800459 Database Backup Total Log Bytes: 0 , 13656075 Database Backup Log Block Number: -1 , -1 ************************************************** There is new information in the volume history file and the volume history file is now needed for a restore of the database. The new information follows. Database Backup LLA: This is provided by DB2 and used by the restore process to determine the DB2 backup time stamp. Database Backup Home Position: This is the home position for the tape used by the restore processing to know where the database data starts. This is only valid for tape volumes. For file device class, this will be 0. Database Backup Total Data Bytes:
105
7718TSMDB2_Database.fm
This is the total number of DB data bytes in this database backup. Database Backup Total Log Bytes: This is the total number of bytes for recovery log in this database backup. Database Backup Log Block Number: This is the starting block number where the backup recovery log starts. This is only valid for tape volumes. For file device class, this will be -1. Tivoli Storage Manager needs this information since the database backup/restore are done in two sessions. One is for the database data and the other is for the recovery logs. Note: It is essential to save your volume history file. Without it, you cannot restore your database. To ensure the availability of volume history information, it is extremely important to take one of the following steps: Store at least one copy of the volume history file offsite or on a disk separate from the database Store a printout of the file offsite Store a copy of the file offsite with your database backups and device configuration file Store a remote copy of the file, for example, on an NFS-mounted file system. The VOLUMEHISTORY server option lets you specify backup volume history files. Then, whenever the server updates volume information in the database, it also updates the same information in the backup files. You can also back up the volume history information at any time, by entering backup volhistory command. If you do not specify file names, the server backs up the volume history information to all files specified with the VOLUMEHISTORY server option. In order to ensure updates are complete before the server is halted, the following steps are recommended: Do not halt the server for a few minutes after issuing the BACKUP VOLHISTORY command. Specify multiple VOLUMEHISTORY options in the server options file. Examine the volume history file to see if the file is updated.
Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. 106
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDB2_Database.fm
All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR0152I Database manager successfully started. ANR0130E rdbdb.c(1306): Server LOG space exhausted. To increase the amount of log space available to the server, evaluate the directories and filesystem assigned to the ACTIVELOGDIR, ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. An out of log space condition may occur because the ACTIVELOGDIR location is full. Alternatively, an out of log condition may occur if the log files in the ACTIVELOGDIR which are no longer active can not be archived to the ARCHIVELOGDIR and ARCHFAILOVERLOGDIR locations. If necessary, a larger ARCHIVELOGDIR or ARCHFAILOVERLOGDIR can be specified by updating this option in the dsmserv.opt file and then restarting the server. We take the ANR0130E as a hint for a reorganization of our server database and log setup. Our plan is to extend the log space to allow the server to start again. Then we take a database backup, add new filesystems to the box and finally restore the database to the new filesystems. First we free up some space on the G: drive via deleting unused files we were able to identify. Next we create the new archive log directory under the new target, d:\tsm\server1\archivelog. We change the dsmserv.opt file to reflect the new location of the archivelogdir temprarily to the ARCHLOGDirectory located at d:\tsm\server1\archivelog and start the server to activate that change as shown with Example 5-38 below. We use the DSMSERV DISPLAY DBSPACE parameter to the dsmserv command to verify the current database setup.
Example 5-38 Server utility: display dbspace command
G:\Program Files\tivoli\tsm\server1>"c:\Program Files\tivoli\tsm\server\dsmserv. exe" display dbspace ANR0900I Processing options file G:\Program Files\tivoli\tsm\server1\dsmserv.opt. ANR7800I DSMSERV generated at 14:46:49 on May 19 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I ANR0153I ANR1380I ANR0153I The ICC support module has been loaded. Database manager already running. The buffer pool monitor switch is enabled. Database manager already running. d:\gallium_server1\db 102,398.65 35,141.96 67,256.69
Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB):
107
7718TSMDB2_Database.fm
Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB):
This start activated our change to the archive log, and an archivelog structure was created under the new location. Now we copy all the old logfiles to this new location, once completed we delete the old archivelog directory (see Example 5-39).
Example 5-39 Copying archivelog data while the server is down
D:\TSM\server1\archivelog>xcopy /E G:\TSM\server1\archivelog\* . G:\TSM\server1\archivelog\archmeth1\SERVER1\TSMDB1\NODE0000\C0000000\S0000025.LOG .. lines deleted .. G:\TSM\server1\archivelog\archmeth1\SERVER1\TSMDB1\NODE0000\C0000000\S0000047.LOG G:\TSM\server1\archivelog\RstDbLog\SQLLPATH.TAG 23 File(s) copied D:\TSM\server1\archivelog>del /s /q G:\TSM\server1\archivelog\* Deleted file G:\TSM\server1\archivelog\archmeth1\SERVER1\TSMDB1\NODE0000\C0000000\S0000025.LOG .. lines deleted .. Deleted file G:\TSM\server1\archivelog\archmeth1\SERVER1\TSMDB1\NODE0000\C0000000\S0000047.LOG Deleted file - G:\TSM\server1\archivelog\RstDbLog\SQLLPATH.TAG In addition Example 5-40 documents the log layout we collect with the DSMSERV DISPLAY LOG command.
Example 5-40 Server utility: display log
G:\Program Files\tivoli\tsm\server1>"c:\Program Files\tivoli\tsm\server\dsmserv. exe" display log ANR0900I Processing options file G:\Program Files\tivoli\tsm\server1\dsmserv.opt. ANR7800I DSMSERV generated at 14:46:49 on May 19 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR0152I Database manager successfully started. ANR1380I The buffer pool monitor switch is enabled. Total Space(MB): 2,048 108
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDB2_Database.fm
Used Free Active Log Mirror Log Archive Failover Log Archive Log
d:\tsm\server1\archivelog
We will use the d: drive for the archivelog temporarily only, later we separate the log again from the d: drive which we use for file device class volumes. Example 5-41 documents the backup process we initiate next.
Example 5-41 Create a database backup, type backup
TSM:TIRAMISU>backup db type=dbsnapshot devc=file ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=dbsnapshot devc=file ANR4559I Backup DB is in progress. ANR0984I Process 3 for DATABASE BACKUP started in the BACKGROUND at 15:09:40. ANR2287I Snapshot database backup started as process 3. TSM:TIRAMISU> ANR0406I Session 3 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(4331)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44844582.DSS mounted. ANR0511I Session 3 opened output volume G:\TSM\SERVER1\FILECLASS\44844582.DSS. ANR1360I Output volume G:\TSM\SERVER1\FILECLASS\44844582.DSS opened (sequence number 1). ANR1361I Output volume G:\TSM\SERVER1\FILECLASS\44844582.DSS closed. ANR0514I Session 3 closed volume G:\TSM\SERVER1\FILECLASS\44844582.DSS. ANR0403I Session 3 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR0406I Session 4 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(4363)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44844610.DSS mounted. ANR0511I Session 4 opened output volume G:\TSM\SERVER1\FILECLASS\44844610.DSS. ANR1360I Output volume G:\TSM\SERVER1\FILECLASS\44844610.DSS opened (sequence number 1). ANR1361I Output volume G:\TSM\SERVER1\FILECLASS\44844610.DSS closed. ANR0514I Session 4 closed volume G:\TSM\SERVER1\FILECLASS\44844610.DSS. ANR0403I Session 4 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR4558I Snapshot database backup (process 3) completed. ANR0985I Process 3 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 15:10:11. We create the directories for the database, active log and archivelog using the commands documented with Example 5-42.
Example 5-42 Create DBDIR, ACTIVELOGDIR and ARCHIVELOGDIR directories
109
7718TSMDB2_Database.fm
Again we apply a change to the dsmserv.opt file to now reflect the final target directory for the archive logs: ARCHLOGDirectory l:\tsm\archivelog Before we can start the restore, we create a file for the database directory locations to be used with the restore command. We enter each location on a separate line. In our scenario the dbdir.txt file looks as documented with Example 5-43.
Example 5-43 dbdir.txt file
i:\tsm\dbdir1 j:\tsm\dbdir2 The DSMSERV REMOVEDB command we use with Example 5-44 removes the information about table TSMDB1 from the DB2 database. This command deletes all user data and log files, as well as any backup/restore history for the database. If the log files are needed for a roll-forward recovery after a restore operation, or the backup history required to restore the database, these files should be saved prior to issuing this command. The REMOVEDB command uses the DB2 API sqledrpd command, the DB2 equivalent is the command db2 drop db <db_alias> At the time you submit the command the database must not be in use.
Example 5-44 DSMSERV REMOVEDB command
G:\Program Files\tivoli\tsm\server1>"c:\Program Files\tivoli\tsm\server\dsmserv.exe" removedb tsmdb1 ANR0900I Processing options file G:\Program Files\tivoli\tsm\server1\dsmserv.opt. ANR7800I DSMSERV generated at 09:55:28 on Jun 11 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR2638W This command will delete all user data and log files, as well as any backup/restore history for the TSM server database. Are you sure you want your database and all of its references removed (y or n)? y ANR0152I Database manager successfully started. ANR0366I Database TSMDB1 was removed successfully. Example 5-45 below documents the restore process, note that we had to fully qualify the On parameter to the restore command for this to work successful. This parameter specifies a file listing the directories to which the database will be restored, see Example 5-43 on page 110 for our definitions.
110
7718TSMDB2_Database.fm
G:\Program Files\tivoli\tsm\server1>"c:\Program Files\tivoli\tsm\server\dsmserv.exe" restore db todate=today totime=now source=dbsnapshot on=g:\progra~1\tivoli\tsm\server1\dbdir.txt activelogd=k:\tsm\activelog recoveryd=m:\recoveryd ANR0900I Processing options file G:\Program Files\tivoli\tsm\server1\dsmserv.opt. ANR7800I DSMSERV generated at 09:55:28 on Jun 11 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR1636W The server machine GUID changed: old value (), new value (10.81.67.e1.6a.5a.11.dd.aa.6e.00.02.55.c6.b9.40). ANR7808W Sun Microsystems Library Attach module libacs.dll is not available from the system. ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1500. ANR0152I Database manager successfully started. ANR4916I Starting point-in-time database restore snapshot to date 06/12/2009 16:50:55. ANR4620I Database backup series 2 operation 0 device class FILE. ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44844582.DSS mounted. ANR1363I Input volume G:\TSM\SERVER1\FILECLASS\44844582.DSS opened (sequence number 1). ANR1364I Input volume G:\TSM\SERVER1\FILECLASS\44844582.DSS closed. ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44844610.DSS mounted. ANR1363I Input volume G:\TSM\SERVER1\FILECLASS\44844610.DSS opened (sequence number 1). ANR1364I Input volume G:\TSM\SERVER1\FILECLASS\44844610.DSS closed. ANR4638I Restore of backup series 2 operation 0 in progress. ANR0406I Session 1 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(2688)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44844582.DSS mounted. ANR0510I Session 1 opened input volume G:\TSM\SERVER1\FILECLASS\44844582.DSS. ANR1363I Input volume G:\TSM\SERVER1\FILECLASS\44844582.DSS opened (sequence number 1). ANR4912I Database full restore in progress and DB Data bytes transferred 67,371,008. ANR4912I Database full restore in progress and DB Data bytes transferred 134,742,016. ANR4912I Database full restore in progress and DB Data bytes transferred 202,113,024. ANR4912I Database full restore in progress and DB Data bytes transferred 269,484,032. ANR4912I Database full restore in progress and DB Data bytes transferred 336,855,040. ANR1365I Volume G:\TSM\SERVER1\FILECLASS\44844582.DSS closed (end reached).
Chapter 5. IBM Tivoli Storage Manager database
111
7718TSMDB2_Database.fm
ANR4912I Database full restore in progress and DB Data bytes transferred 381,800,459. ANR1364I Input volume G:\TSM\SERVER1\FILECLASS\44844582.DSS closed. ANR0514I Session 1 closed volume G:\TSM\SERVER1\FILECLASS\44844582.DSS. ANR0403I Session 1 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR0406I Session 2 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(2710)). ANR8340I FILE volume G:\TSM\SERVER1\FILECLASS\44844610.DSS mounted. ANR0510I Session 2 opened input volume G:\TSM\SERVER1\FILECLASS\44844610.DSS. ANR1363I Input volume G:\TSM\SERVER1\FILECLASS\44844610.DSS opened (sequence number 1). ANR1365I Volume G:\TSM\SERVER1\FILECLASS\44844610.DSS closed (end reached). ANR4912I Database full restore in progress and DB transaction log bytes transferred 27,291,659. ANR1364I Input volume G:\TSM\SERVER1\FILECLASS\44844610.DSS closed. ANR0514I Session 2 closed volume G:\TSM\SERVER1\FILECLASS\44844610.DSS. ANR0403I Session 2 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR0406I Session 3 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip gallium(2712)). ANR0403I Session 3 ended for node $$_TSMDBMGR_$$ (DB2/NT). ANR0153I Database manager already running. ANR1380I The buffer pool monitor switch is enabled. ANR0153I Database manager already running. ANR4917I Point-in-time database restore with snapshot complete, restore date 06/12/2009 15:09:40. ANR0369I Stopping the database manager because of a server shutdown.
So our restore is complete, but did we reach our goal, the relocation of the database and log volumes? We start the server and use the QUERY DBSPACE and the QUERY LOG command again to verify, the result is documented with Example 5-46. The database is spread over drives J: and K:, the active log is on drive K: and the archive log was relocated to L: drive.
Example 5-46 Relocation verification
TSM:TIRAMISU>q dbspace ANR2017I Administrator SERVER_CONSOLE issued command: QUERY DBSPACE Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): j:\tsm\dbdir2 5,114.41 709.00 4,405.41 i:\tsm\dbdir1 5,114.41 708.98 4,405.43
TSM:TIRAMISU>q log f=d ANR2017I Administrator SERVER_CONSOLE issued command: QUERY LOG f=d Total Space(MB): 2,048 Used Space(MB): 2.80 Free Space(MB): 2,037.20 112
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDB2_Database.fm
Summary
In this chapter we discussed an example of a database restore scenario. You should now know how to prepare and complete a database restore. In addition, you now understand that the V5 approach of adding and deleting databases volumes for Tivoli Storage Manager database relocation no longer works. Relocating server volumes requires a database restore and results in server downtime. This makes planning in the beginning more important. Remaining tasks at this point include the configuration of a mirror for the active log or the definition of an archive log failover directory. However, at this point you should be able to complete those steps with the information from the administrators reference guide and the manual. If you are interested in the review of other restore scenarios, Chapter 6.3, Recovery of a V6.1 Tivoli Storage Manager server on page 130discusses a DRM restore to a new hardware box.
TSM:TIRAMISU>extend dbspace m:\tsmdb\dbdir3 ANR2017I Administrator SERVER_CONSOLE issued command: EXTEND DBSPACE m:\tsmdb\dbdir3 ANR2592I Directory(ies) 'm:\tsmdb\dbdir3' has been defined in the database space. TSM:TIRAMISU>q dbspace ANR2017I Administrator SERVER_CONSOLE issued command: QUERY DBSPACE Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): Location: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): j:\tsm\dbdir2 5,114.41 709.00 4,405.41 i:\tsm\dbdir1 5,114.41 708.98 4,405.43 m:\tsmdb\dbdir3 5,114.41 28.22 5,086.19
113
7718TSMDB2_Database.fm
Database Name: Total Size of File System (MB): Space Used by Database(MB): Free Space Available (MB): Page Size(Bytes): Total Pages: Usable Pages: Used Pages: Free Pages: Buffer Pool Hit Ratio: Total Buffer Requests: Sort Overflows: Lock Escalation: Package Cache Hit Ratio: Last Database Reorganization: Full Device Class Name: Incrementals Since Last Full: Last Complete Backup Date/Time:
TSMDB1 15,343 454 13,897 33,048 32,776 23,744 9,032 97.5 53,178 0 0 66.3 FILE 0 06/12/2009 14:51:29
Example 5-47 on page 113 documents how we submitted the EXTEND DBSPACE command and subsequent QUERY DBSPACE and QUERY DB commands do show the directory assigned to the database. However, if you look at Example 5-48 you see that the directory is just empty.
Example 5-48 Database directory stays empty
G:\Program Files\tivoli\tsm\server1>dir m:\tsmdb\dbdir3 Volume in drive M is tsmdb3 Volume Serial Number is 1C55-D0C5 Directory of m:\tsmdb\dbdir3 06/12/2009 06/12/2009 08:49 PM <DIR> . 08:49 PM <DIR> .. 0 File(s) 0 bytes 2 Dir(s) 5,333,258,240 bytes free
Once we restart the server, the new database directory gets populated by DB2 and is available for the our server. To further explain this scenario, assume DB2 manages your database consisting of four LUNs, 50GB each as shown with Figure 5-32. Each LUN is assigned its own volume group on the host and each volume group has one file system. With this configuration DB2 uses separate I/O threads for each directory/file system.
114
7718TSMDB2_Database.fm
Now if you are running out of database space, you can use the EXTEND DBSPACE command to add space to the database. In this example, you create two new 50GB LUNs, assign them to the volume group and create a separate filesystem for each LUN. Once you add the space to your Tivoli Storage Manager server, with the next restart DB2 runs through a reorganization of the database as shown with Figure 5-33 on page 115.
Note: Adding a new database directory after initial load will cause a REORG of the database. As this is expensive and disruptive it should be avoided. To prevent this from happening it is recommended that you carefully configure your DBSPACE and if possible just extend the filespaces as this is transparent to your Tivoli Storage Manager server and the underlying database. As shown with Figure 5-34 on page 116, you create four new 25GB LUNs and extend each of your database filesystems by those 25GBs. It is not necessary to submit the EXTEND DBSPACE command and a database RORG is not performed.
115
7718TSMDB2_Database.fm
DBREPORTMODE option
You use the SET DBREPORTMODE for the V6.1 Tivoli Storage Manager server to set the database error reporting level. Possible values are: None No database diagnostic reporting is to be done. Purpose: If some pervasive symptom is encountered that is flooding the activity log with messages, disable reporting by setting to NONE can eliminate the noise. Partial (Default) Report exception cases or items that are likely issues that need to be considered. Purpose: Report the exception cases, those cases where something unexpected occurs. Full Report all available information when an exception case is encountered. Purpose: Can be enabled, to pursue additional information if a given exception case does not report enough information initially. Lighter weight then full trace enablement. As an example, a database deadlock might get encountered, with DBREPORTMODE set to FULL, additional server transaction and lock information will be reported. Additional database related information is available via the QUERY STATUS command, you can verify the current DBREPORTMODE setting as shown with Example 5-49.
Example 5-49 QUERY STAUS: additional information
TSM:TIRAMISU>q sta ANR2017I Administrator SERVER_CONSOLE issued command: QUERY STATUS Storage Management Server for Windows - Version 6, Release 1, Level 2.0
Server Name: TIRAMISU Server host name or IP address: Server TCP/IP port number: 1500 Crossdefine: Off 116
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDB2_Database.fm
Server Password Set: Server Installation Date/Time: Server Restart Date/Time: Authentication: Password Expiration Period: Invalid Sign-on Attempt Limit: Minimum Password Length: Registration: Subfile Backup: Availability: Accounting: Activity Log Retention: Activity Log Number of Records: Activity Log Size: Activity Summary Retention Period: License Audit Period: Last License Audit: Server License Compliance: Central Scheduler: Maximum Sessions: Maximum Scheduled Sessions: Event Record Retention Period: Client Action Duration: Schedule Randomization Percentage: Query Schedule Period: Maximum Command Retries: Retry Period: Scheduling Modes: Active Receivers: Configuration manager?: Refresh interval: Last refresh date/time: Context Messaging: Table of Contents (TOC) Load Retention: Machine Globally Unique ID: Archive Retention Protection: Database Reporting Mode: Database Directories: Total Size of File System (MB): Space Used on File System (MB): Free Space Available (MB): Encryption Strength:
No 06/01/2009 21:55:51 06/12/2009 17:29:52 On 90 Day(s) 0 0 Closed No Enabled Off 1 Day(s) 185 <1 M 30 Day(s) 30 Day(s) 06/02/2009 09:43:06 Valid Active 25 12 10 Day(s) 5 Day(s) 25 Client Client Client Any CONSOLE ACTLOG NTEVENTLOG Off 60 Off 120 Minute(s) 10.81.67.e1.6a.5a.11.dd.aa.6e.00.02.55.c6.b9.40 Off Partial j:\tsm\dbdir2,i:\tsm\dbdir1 10,228.82 1,417.98 8,810.84 AES
117
7718TSMDB2_Database.fm
configuration command. Example 5-50 shows some of the output returned. We cut ouf information not required for this discussion.
Example 5-50 DB command: get database manager configuration
C:\Program Files\Tivoli\TSM\db2\BIN>db2 get database manager configuration Database Manager Configuration Node type = Enterprise Server Edition with local and remote clients Database manager configuration release level Maximum total of files open CPU speed (millisec/instruction) Communications bandwidth (MB/sec) = 0x0c00
Max number of concurrently active databases (NUMDB) = 8 Federated Database System Support (FEDERATED) = NO Transaction processor monitor name (TP_MON_NAME) = Default charge-back account Java Development Kit installation path C:\PROGRA~1\Tivoli\TSM\db2\java\jdk Diagnostic error capture level Notify Level Diagnostic data directory path (DFT_ACCOUNT_STR) = (JDK_PATH) =
The level parameters specify the type of errors that will be recorded. Valid values are: 0 - No diagnostic data captured 1 - Severe errors only 2 - All errors 3 - All errors and warnings (Default) 4 - All errors, warnings and informational messages Use the UPDATE DBM CFG command to update either of the values: db2 attach to <instance-name> db2 update dbm cfg using <parameter-name> <value> db2 detach For example: DB2 UPDATE DBM CFG USING DIAGLEVEL X where X is the desired notification level.
118
7718TSMDB2_Database.fm
Note: The administration notification file and the db2diag.log file grow continuously. When either one gets too large, back it up and then erase the file. A new file is generated automatically the next time it is required by the system. On platforms supporting the korn shell, the DB2 team provides a script to archive and maintain DB2 message logs and diagnostic data. For a complete description go to the following url: http://www.ibm.com/developerworks/data/library/techarticle/dm-0904db2messagelogs/i ndex.html?S_TACT=105AGX11
db2diag.log
The db2diag.log file is intended for use by DB2 support for troubleshooting purposes, it is available on all platforms supported by DB2. Per default it is found in the directory identified by the diagpath database manager configuration parameter and is created automatically when the instance is created. The db2diag.log file contains diagnostic information about error and warnings encountered by the instance. This information is used for problem determination and is intended for IBM
119
7718TSMDB2_Database.fm
software support. The type of message recorded in this file is determined by the diaglevel database manager configuration parameter. You can format the db2diag.log using the db2diag utility. When the utility is run without any option, as we do with Example 5-51, it reminds you to submit the command db2diag -h to review available formatting and filter options.
Example 5-51 dbdiag command
C:\Program Files\tivoli\TSM\db2\BIN>db2diag > db2diag.txt db2diag invoked with the default set of filtering/formatting options on file "C:\DOCUME~1\ALLUSE~1\APPLIC~1\IBM\DB2\DB2TSM1\DB2TSM\db2diag.log". Enter "db2diag -h" to get a short description of all available options.
The returned db2diag output always starts with DB2 installation specific information and gives you additional details about the running system, see Example 5-52.
Example 5-52 db2diag header output.
2009-06-11-18.35.02.843000-420 I1H962 LEVEL: Event PID : 1084 TID : 3668 PROC : db2bp.exe INSTANCE: DB2TSM NODE : 000 EDUID : 3668 FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120 START : New Diagnostic Log file DATA #1 : Build Level, 128 bytes Instance "DB2TSM" uses "32" bits and DB2 code release "SQL09052" with level identifier "03030107". Informational tokens are "DB2 v9.5.201.3237", "special_21101", "WR21421_21101", Fix Pack "2a". DATA #2 : System Info, 1564 bytes System: WIN32_NT GALLIUM Service Pack 2 5.2 x86 Family 6, model 11, stepping 1 CPU: total:2 online:2 Cores per socket:1 Threading degree per core:1 Physical Memory(MB): total:3776 free:2577 available:1989 Virtual Memory(MB): total:5669 free:4681 Swap Memory(MB): total:1893 free:2104 Information in this record is only valid at the time when this file was created (see this record's time stamp) Example 5-53 shows an event with message ADM7514W being generated upon a database stop via the db2stop command. For details how to interpret the fields please review the available DB2 documentation and search for db2diag.log.
Example 5-53 DB2 stop event as reported in the db2diag.log
NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911 MESSAGE : ADM7514W 120 Database manager has stopped.
7718TSMDB2_Database.fm
STOP
: DB2 DBM
Summary
With the transition to DB2 additional log files need to be reviewed in case you are investigating an unwanted symptom or have to do some troubleshooting. You now know how to adjust reporting levels and diagnostic file path information for your server.
121
7718TSMDB2_Database.fm
122
7718TSMDRM.fm
Chapter 6.
123
7718TSMDRM.fm
124
7718TSMDRM.fm
125
7718TSMDRM.fm
If you enter a null string (""), all current names are removed, and no active-data pool volumes in MOUNTABLE state are processed if they were not explicitly entered as MOVE DRMEDIA , QUERY DRMEDIA, or PREPARE command parameters. Example 6-1 demonstrates the syntax to add multiple activedata storagepool entries.
MOVE DRMEDIA
This command has been updated so that Active Data Pool (ADP) media can be cycled off site/on site per underlying server policies and processes. The command has been updated with the ACTIVEDATASTGPOOL parameter, which allows for override of the previously enabled SET ACTIVEDATASTGPOOL, or one time movement of volumes from the mountable state. If the ACTIVEDATASTGPOOL parameter not used, only those ADP(s) enabled via SET command are processed. Multiple ADP names can be entered via a comma delimited list, as shown in Example 6-1.
Example 6-1 DRM move data command using the activedatastgpool parameter.
MOVE DRMedia * WHEREstate=Mountable ACTIVEDATAStgpool= fileactivepool ANR0609I MOVE DRMEDIA started as process 13024. ANR6682I MOVE DRMEDIA command ended: 13024 volumes processed. Query DRMedia * WHEREstate=Mountable ACTIVEDATAStgpool= fileactivepool
QUERY DRMEDIA
The SQL Engine and QUERY DRMEDIA have been updated so that ADP media can be tracked and managed appropriately.
PREPARE
The PREPARE command will be updated to provide the ability to include ADP volumes in the scripts, macros and documentation included in the recovery plan file. The existing command has been updated with activedatastgpool parameter. This new parameter allows for the override of previously enabled SET DRM ADP(s) or one-time processing of eligible ADP volumes. If activedatastgpool parameter not used, only those ADPs enabled by the SET command are processed. If no ADPs have been set, only the ADP volumes marked on site at the time the prepare ran will be processed. These volumes are marked unavailable. Multiple ADP names can be entered through a comma delimited list, as shown in Example 6-2.
Example 6-2 Disaster Recovery Manager command to set up activedata storage pools.
After setting the drmactivedatapool values, the run the prepare command, as shown in Example 6-3 to review the differences in the recovery plan.
Example 6-3 DRM prepare command using the activedatastgpool parameter.
PREPare ACTIVEDATAStgpool=activepool24,activepool35
126
7718TSMDRM.fm
Volume Type: DBSNAPSHOT * Location for volume G:\TSM\SERVER1\FILECLASS\44844610.DSS is: '' Database Backup LLA: FULL_BACKUP.20090612150940.2 Database Backup HLA: \NODE0000\ Volume Name: "G:\TSM\SERVER1\FILECLASS\44844610.DSS" Backup Series: 2 Backup Op: 0 Volume Seq: 2 Device Class Name: FILE Database Backup ID: 0 , 3076 Database Backup Home Position: 0 Database Backup Total Data Bytes : 0 , 381800459 Database Backup Total Log Bytes: 0 , 27291659 Database Backup Log Block Number: -1 , -1
127
7718TSMDRM.fm
Note: Unlike previous versions of Tivoli Storage Manager, you must have the volume history and devconfig files to recover a V6.1 DB
SERVER.REQUIREMENTS changes
This stanza now reflects the same information as output of the query db and query log admin commands. The changes hold the appropriate DB2 information instead of V5.5 Tivoli Storage Manager db and log volume information. This is still a useful reference point at the recovery site for determining the amount of disk space required on a replacement machine and db and log directory names for pre-creation.
RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
For this stanza, the LOGANDDB.VOLUMES.INSTALL.CMD invocation was removed, and the invocation of the altered dsmserv restore db command was added, however is remarked out in the script, however demonstrates how to restore db to a new location, not using paths recorded in the DB2 backup image.
RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
The DB.STORAGEPATHS stanza is populated as a result of a DB2 query.
ACTIVEDATASTGPOOL.VOLUMES.AVAILABLE
This stanza has been added to the recovery plan to support active data storage pools, and is implemented to mark active-data storage pool volumes as available for use in recovery, as shown in Example 6-5. 128
Tivoli Storage Manager V6.1 Technical Guide
7718TSMDRM.fm
/* Recovery Administrator: Remove any volumes that have not been obtained /* from the vault or are not available for any reason. /* Note: It is possible to use the mass update capability of the /* UPDATE command instead of issuing an update for each volume. However, /* the 'update by volume' technique used here allows you to select /* a subset of volumes to be processed. upd upd upd upd vol vol vol vol /tsm1/activepool/srv/0000169D.BFS /tsm1/activepool/srv/00001700.BFS /tsm1/activepool/srv/00001701.BFS /tsm1/activepool/srv/00001702.BFS acc=READO acc=READO acc=READO acc=READO wherestg=FILEACTIVEPOOL wherestg= FILEACTIVEPOOL wherestg= FILEACTIVEPOOL wherestg= FILEACTIVEPOOL
*/ */ */ */ */ */
ACTIVEDATASTGPOOL.VOLUMES.DESTROYED
This stanza has been added to the recovery plan to support active data storagepools, and is implemented to mark destroyed active-data storage pool volumes as unavailable, as shown in Example 6-6.
Example 6-6 DRM activedatastgpool.volumes.destroyed stanza
/* Volumes in this macro were not marked as 'off site' at the time the /* PREPARE ran. They were likely destroyed in the disaster. /* Recovery Administrator: Remove any volumes that were not destroyed. */
*/ */
upd vol /tsm1/activepool/srv/00001703.BFS acc=UNAVAIL wherestg=TSMACTIVEDIRS /* del vol /tsm1/activepool/srv/00001703.BFS */ upd vol /tsm1/activepool/srv/00001703.BFS acc=UNAVAIL wherestg=TSMACTIVEDIRS /* del vol /tsm1/activepool/srv/00001703.BFS */
RECOVERY.VOLUMES.REQURED
This stanza has been updated to provide information on activedata storage pool volumes to include the recovery process, and is shown in Example 6-7
Example 6-7 activedata storage pool stanza
Volumes required for client restore(s) using active data Location = Safe Vault Inc. Active Storage Pool = FILEACTIVEPOOL Device Class = FILECLASS Volume Name = /tsm1/activepool/srv/0000169D.BFS
RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
This stanza has been updated to include the ADP stanza for exploding into macros.
129
7718TSMDRM.fm
When running a Tivoli Storage Manager server with multiple instances, it is recommended that each instance be protected with Disaster Recovery Manager. Some basic setup commands as shown in Example 6-8 to establish your plan and instructions for your new server instance.
Example 6-8 An example for naming convention and command syntax for DRM instances
LOGANDDB.VOLUMES.CREATE script LOG.VOLUMES DB.VOLUMES LOGANDDB.VOLUMES.INSTALL script The exclusions for the Windows platform V5.5 recovery plan file is shown in Example 6-10 on page 130.
Example 6-10 Windows DRM stanza exclusions from the V6.1 recovery plan.
LOG.VOLUMES DB.VOLUMES LOGANDDB.VOLUMES.INSTALL script These exclusions are an important phase in the rebuilding of the Tivoli Storage Manager server, which must now be performed manually, prior to invoking the recovery scripts.
130
7718TSMDRM.fm
On UTAH-TSM2
1. def devc dbb_file devt=file maxcap=20G DIR=/tsmstg/dbb 2. set dbrecovery dbb_file 3. backup db type=full devc=dbb_file scratch=yes. 4. prepare 5. Transport the recovery plan, with the copy pools tapes and database backup to Vermont.
131
7718TSMDRM.fm
Filesystem 1024-blocks /dev/dbdir5lv 2097152 /dev/dbdir6lv 2097152 /dev/dbdir7lv 2097152 /dev/dbdir8lv 2097152 /dev/actlog1lv 9371648 /dev/actlog1mlv 9371648 /dev/archlog1lv 18808832
Iused %Iused Mounted on 4 1% /tsm2/dbdir001 4 1% /tsm2/dbdir002 4 1% /tsm2/dbdir003 4 1% /tsm2/dbdir004 4 1% /tsm2/actlog 4 1% /tsm2/activelogm 4 1% /tsm2/archlog
2. For this setup purpose, we are configuring the instance tsm2 as the name of our DR instance (utah-TSM2). The tasks involved the creation of the group, user ID and home directory for our Tivoli Storage Manager instance, as shown in Example 6-12.
Example 6-12 Tivoli Storage Manager instance user ID creation in AIX
# mkuser -a id=1003 pgrp=tsmsrvrs home=/home/tsm2 tsm2 # passwd tsm2 Changing password for "tsm2" tsm1's New password: Enter the new password again:
3. Next, log in using the user ID and password, and you will be prompted to change the password for user ID, as shown in Example 6-13.
Example 6-13 Logging into AIX and changing the password for TSM1 new instance creation.
You must change your password now and login again! Changing password for "tsm2" tsm1's Old password: tsm1's New password: 4. Next, we edit the .profile file as seen in the existing TSM2 instance, or copy the file. This is to maintain environment consistancy with the instances. Performing this step, ensure any specific path details are altered for the new instance. 5. Change the ownership of the newly created filesystem mount points. Changing the ownership of the tsm2 mounts and directories can be accomplished by issuing the commands shown in Example 6-14.
Example 6-14 AIX chown command and review of owner and group setttings
$ su root's Password: # cd /
132
7718TSMDRM.fm
# chown -R tsm2.tsmsrvrs # ls -l /tsm2 total 0 drwxr-xr-x 3 tsm2 drwxr-xr-x 3 tsm2 drwxr-xr-x 3 tsm2 drwxr-xr-x 3 tsm2 drwxr-xr-x 3 tsm2 drwxr-xr-x 3 tsm2 drwxr-xr-x 3 tsm2
/tsm2/*
21 21 21 21 21 21 21
6. Create a new server options file (dsmserv.opt) by either referencing the recovery plan file, or copy the existing instance TSM1 server option file, and edit any detail required. Reference the IBM Tivoli Storage Manager for AIX Installation Guide V6.1, GC23-9781 for more details regarding dsmserv.opt parameters and settings. 7. Increase the size of the instance directory for TSM2, which is in this case the /home filesystem. Each instance requires aproximately 420MB of additional space. 8. The next step is to log out of AIX as the root user, and log in as the instance user ID (tsm2). Upon completing this, you will find an environment for DB2 has been established, as discussed in the previous steps. 9. Next update the default directory for the database to reflect the instance directory, by running the db2 update command as shown in Example 6-15.
Example 6-15 Setting the default directory for the database to be the same as the instance directory
$ pwd /home/tsm2 $ db2 update dbm cfg using dftdbpath /tsm2 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
10.Preparing the DB2 database and recovery logs is our next step. The db2icrt command will update the instance details with in DB2. The command is run as shown in Example 6-16.
Example 6-16 Command to configure a Tivoli Storage Manager V6.1 server instance
11.Following the successful formatting, the next step will be to start the Tivoli Storage Manager V6.1 server in the foreground. To perform this, we will use the new parameters provided in the dsmserv command, as shown in Example 6-17.
Example 6-17 Starting the Tivoli Storage Manager V6.1 server instance in the foreground
133
7718TSMDRM.fm
configuration is done automatically. If you are configuring an instance manually, for the back up to work, the following requirements must be met: Tivoli Storage Manager API is installed on server machine (done by COI install) Tivoli Storage Manager API has the correct client option settings DSMI_DIR, DSMI_CONFIG, DSMI_LOG environment variables are set in DB2 instance process DSMI_DIR, DSMI_CONFIG, DSMI_LOG point to correct places Api executables Api configuration files Api log file directory The correct password is set The steps required to complete this task are: 1. We set the DSMI_ api environment variables in the <instance>/sqllib/db2profile file, as shown in Example 6-18.
Example 6-18 The line items added to the sqllib/db2profile file.
export DSMI_CONFIG=/home/tsm1/tsmdbmgr.opt export DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 export DSMI_LOG=/home/tsm1 2. Then log out, and back into the instance, or issue the command as shown in the ~/.profile to re-read the profile. 3. Next, create a file called tsmdbmgr.opt in the /home/tsm1 directory and add the following line as shown in example Example 6-19.
Example 6-19 Content of the /home/tsm2/tsmdbmgr.opt file
servername tsmdbmgr_tsm2 4. Next, edit the /usr/tivoli/tsm/client/api/bin64/dsm.sys. Avoid placing the server name, TSMDBMGR_TSM2, first in dsm.sys because it should not be the system-wide default. In this example, the added lines are after the stanza for server_a, as shown in Example 6-20 on page 134.
Example 6-20 /usr/tivoli/tsm/client/api/bin64/dsm.sys
Servername server_a COMMMethod TCPip TCPPort 1500 TCPServeraddress node.domain.company.COM servername TSMDBMGR_TSM2 commmethod tcpip tcpserveraddr localhost tcpport 1500 passwordaccess generate passworddir /home/tsm2 errorlogname /home/tsm2/tsmdbmgr.log nodename $$_TSMDBMGR_$$ 5. Next set the API password for the instance TSM1, using the password (current and new) as TSMDBMGR, as root user, as shown in Example 6-21.
134
7718TSMDRM.fm
# cd /home/tsm1/sqllib/adsm # ./dsmapipw ************************************************************* * Tivoli Storage Manager * * API Version = 6.1.0 * ************************************************************* Enter your current password: Enter your new password: Enter your new password again:
This db2 upd command establishes the db2 configuration for the tsmdb1 database, and can be reviewed for TSM2 instance by running an AIX command line db2 get snapshot for database on TSMDB1, as shown in Example 6-22, to query the TSMDB1 database for the TSM2 server instance.
Example 6-22 db2 get snapshot for database on TSMDB1 DB2 command
$ db2 get snapshot for database on TSMDB1 |grep tsm2 Database path = /home/tsm2/tsm2/NODE0000/SQL00001/ Automatic storage path = /tsm2/dbdir001 Automatic storage path = /tsm2/dbdir002 Automatic storage path = /tsm2/dbdir003 Automatic storage path = /tsm2/dbdir004 6. Next, stop the running Tivoli Storage Manager TSM2 instance using the dsmcadmc command or ISC and Administration Center. 7. Drop the DB2 database tsmdb1 created by the configuration process we just followed. Use the command DSMSERV REMOVEDB to drop the TSM1DB database from DB2, as shown in the Example 6-23.
Example 6-23 Dropping the DB2 database created for the DR instance.
$ dsmserv removedb TSMDB1 Tivoli Storage Manager for AIX Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 438424. ANR0900I Processing options file /home/tsm2/dsmserv.opt. ANR7811I Using instance directory /home/tsm2. ANR4726I The ICC support module has been loaded. ANR2638W This command will delete all user data and log files, as well as any backup/restore history for the TSM server database. Are you sure you want your database and all of its references removed (y or n)? y
135
7718TSMDRM.fm
ANR0152I Database manager successfully started. ANR0366I Database TSMDB1 was removed successfully.
8. Next, ensure the active log path and recovery directory are empty prior to the restore, as shown in Example 6-24.
Example 6-24 Ensure the active log path and recovery directory are empty
$ rm -r /tsmstg/recoveryd/* $ rm -r /tsm2/actlog/* $ rm -r /tsm2/dirdb001/* 9. Run the DSMSERV RESTOREDB command, referencing the exploded DB.STORAGEPATHS file, as shown in the Example 6-25
Example 6-25 dsmserv restoredb command
10.Now, reviewing the output of the restore results shown in Example 6-26.
Example 6-26 Output of the dsmserv restore db command on AIX
Tivoli Storage Manager for AIX Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 356514. ANR0900I Processing options file /home/tsm2/dsmserv.opt. ANR0921I Tracing is now active to file trace.txt. ANR7811I Using instance directory /home/tsm2. ANR4726I The ICC support module has been loaded. ANR1636W The server machine GUID changed: old value (), new value (00.00.00.00.4f.96.11.de.82.b2.08.63.09.0c.05.7f). ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1502. ANR0153I Database manager already running. ANR4634I Starting point-in-time database restore to date 06/24/09 23:59:59. ANR4620I Database backup series 4 operation 0 device class DBB_FILE. ANR8340I FILE volume /tsmstg/dbb/45798964.DBV mounted. ANR1363I Input volume /tsmstg/dbb/45798964.DBV opened (sequence number 1). ANR1364I Input volume /tsmstg/dbb/45798964.DBV closed. ANR8340I FILE volume /tsmstg/dbb/45800956.DBV mounted. ANR1363I Input volume /tsmstg/dbb/45800956.DBV opened (sequence number 1). ANR1364I Input volume /tsmstg/dbb/45800956.DBV closed. ANR4638I Restore of backup series 4 operation 0 in progress. ANR0406I Session 1 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32915)).
136
7718TSMDRM.fm
ANR8340I FILE volume /tsmstg/dbb/45798964.DBV mounted. ANR0510I Session 1 opened input volume /tsmstg/dbb/45798964.DBV. ANR1363I Input volume /tsmstg/dbb/45798964.DBV opened (sequence number 1). ANR4912I Database full restore in progress and DB Data bytes transferred 67,371,008. ANR4912I Database full restore in progress and DB Data bytes transferred 134,742,016. ANR4912I Database full restore in progress and DB Data bytes transferred 202,113,024. ANR4912I Database full restore in progress and DB Data bytes transferred 269,484,032. ANR4912I Database full restore in progress and DB Data bytes transferred 336,855,040. ANR4912I Database full restore in progress and DB Data bytes transferred 404,226,048. ANR4912I Database full restore in progress and DB Data bytes transferred 471,597,056. ANR4912I Database full restore in progress and DB Data bytes transferred 538,968,064. ANR4912I Database full restore in progress and DB Data bytes transferred 606,339,072. ANR4912I Database full restore in progress and DB Data bytes transferred 673,710,080. ANR4912I Database full restore in progress and DB Data bytes transferred 741,081,088. ANR1365I Volume /tsmstg/dbb/45798964.DBV closed (end reached). ANR4912I Database full restore in progress and DB Data bytes transferred 807,632,907. ANR1364I Input volume /tsmstg/dbb/45798964.DBV closed. ANR0514I Session 1 closed volume /tsmstg/dbb/45798964.DBV. ANR0403I Session 1 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR0406I Session 2 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32916)). ANR8340I FILE volume /tsmstg/dbb/45800956.DBV mounted. ANR0510I Session 2 opened input volume /tsmstg/dbb/45800956.DBV. ANR1363I Input volume /tsmstg/dbb/45800956.DBV opened (sequence number 1). ANR4912I Database full restore in progress and DB transaction log bytes transferred 67,371,008. ANR1365I Volume /tsmstg/dbb/45800956.DBV closed (end reached). ANR4912I Database full restore in progress and DB transaction log bytes transferred 73,441,291. ANR1364I Input volume /tsmstg/dbb/45800956.DBV closed. ANR0514I Session 2 closed volume /tsmstg/dbb/45800956.DBV. ANR0403I Session 2 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR0406I Session 3 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32917)). ANR0403I Session 3 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR0153I Database manager already running. ANR1380I The buffer pool monitor switch is enabled. ANR4645I The restore date reflects the most recent backup available up to the specified TODATE. ANR4635I Point-in-time database restore complete, restore date 06/23/09 19:16:01. ANR0369I Stopping the database manager because of a server shutdown. $
137
7718TSMDRM.fm
11.Next, and last step prior to restore testing is to start the recovered Tivoli Storage Manager server from Utah-tsm1, and now on Vermont as TSM2, in the foreground, as shown in Example 6-27
Example 6-27 Output of a recovered AIX Tivoli Storage Manager V6.1 server on a DR instance
Tivoli Storage Manager for AIX Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 356514. ANR0900I Processing options file /home/tsm2/dsmserv.opt. ANR0921I Tracing is now active to file trace.txt. ANR7811I Using instance directory /home/tsm2. ANR4726I The ICC support module has been loaded. ANR1636W The server machine GUID changed: old value (), new value (00.00.00.00.4f.96.11.de.82.b2.08.63.09.0c.05.7f). ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1502. ANR0153I Database manager already running.A NR1311E Vary-on failed for disk volume /tsmstg/backuppool02F - unable to access disk device. ANR7807W Unable to get information for file xxxxxx lines removed to save output space...... ANR2103I Activity log pruning completed: 1299 records removed. ANR0984I Process 1 for IDENTIFY PROCESS started in the BACKGROUND at 08:18:12. ANR1018I Volume deduplication process 1 started for storage pool DD, identify processes=3. ANR0984I Process 2 for IDENTIFY PROCESS started in the BACKGROUND at 08:18:12. ANR1018I Volume deduplication process 2 started for storage pool DD, identify processes=3. ANR0984I Process 3 for IDENTIFY PROCESS started in the BACKGROUND at 08:18:12. ANR1018I Volume deduplication process 3 started for storage pool DD, identify processes=3. ANR2803I License manager started. ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1502. ANR2718W Schedule manager disabled. ANR2828I Server is licensed to support Tivoli Storage Manager Basic Edition. ANR2828I Server is licensed to support Tivoli Storage Manager Extended Edition. TSM:UTAH-TSM1> ANR0993I Server initialization complete. ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use. TSM:UTAH-TSM1>
138
7718TSMDRM.fm
As we have highlighted in the output from Example 6-27 on page 138, three processes are started which are for the server dedup function which has been recovered at the DR site. 12.Restore high priority clients 13.Run or perform the steps in recovery.normal.mode.script to restore primary storage pools.
Summary
We have shown in this section a disaster recovery scenaro of a V6.1.2 Tivoli Storage Manager server instance running on Utah as TSM1, which is the deduplication instance in our test lab. The recovery instance was on the DR server Vermont, into a newly created instance called TSM2. An existing TSM1 was already in place, and the intent of this excersize was to demostrate the DR target could be any system, with any path structure.
6.4.1 Data lifecycle for a Tivoli Storage Manager server and DRM
The general view of the data lifecycle within a Tivoli Storage Manager server once it has been stored (either archived or backed up) is typically the following.
139
7718TSMDRM.fm
offset protection by rotating those volumes to an off site location in order to protect from a major disaster that results in the loss of the primary data center or server hardware and devices.
Database backup
Database backup for the server needs to happen as the last step in this sequence because the pointers and other meta-data characteristics that are recorded in the database are influenced or impacted by the migration and storage pool backup steps listed above. Finally, movement of volumes for off site storage may now be performed. If using Tivoli Storage Managers DRM feature, this would be the MOVE DRMEDIA command and related processing. The notion here being to take the current database backup along with matching storage pool backup volumes that and remove them from the primary location for the purpose of transporting them to the off site data protection location. Note that the sequence listed above is not an absolute. For example, if simultaneous write is used when the data is stored, a copy storage pool copy of the data will be created in parallel or concurrent with the store of the data into the primary storage pool. Alternatively, the use of migration may not be used in your configured environment, you may simply be storing to a primary location and then creating copy storage pool copies from that without any actual storage hierarchy in place.
6.4.2 Data lifecycle for a Tivoli Storage Manager server and DRM including deduplicated storage pools
There are a number of operational considerations when using deduplicated primary or copy storage pools. One key consideration though is that deduplication is only allowed for storage pools using a device class of DEVTYPE=FILE. As such, deduplicated copy storage pools do
140
7718TSMDRM.fm
not lend themselves to use by DRM for the off site protection of the Tivoli Storage Manager server. The following scenarios discuss some typical or expected implementations: PRIMARY POOL DEDUPLICATED, SINGLE COPY STORAGE POOL NOT DEDUPLICATED This is probably the typical situation that is expected. In this case, the time to backup the primary storage pool to a non-deduplicated copy storage pool may take longer. The issue being that as data is copied to the copy storage pool, the deduplicated chunks representing a given file need to be read and the file "recomposed" or "undeduplicated" and stored in its entirety in the copy storage pool. However, this allows for the use of the Tivoli Storage Manager DRM feature and the use of off site copy storage pool volumes to recovery data at a disaster recovery site. PRIMARY POOL DEDUPLICATED, MULTIPLE COPY STORAGE POOLS NOT DEDUPLICATED This is also expected to be a typical situation or configuration. In this case, the time to backup the primary storage pool may also take longer because of the reads necessary to get the various chunks representing a given object being written to one of these copy storage pools. This is similar to the case above but also provides an on site copy storage pool copy of the data in addition to the off site support. PRIMARY POOL DEDUPLICATED, SINGLE COPY STORAGE POOL DEDUPLICATED In this case, the primary goal is space savings at the primary server location. However, this does not provide for DRM exploitation and off site rotation of copy storage pool volumes because the deduplicated copy storage pool can only be achieved using DEVTYPE=FILE volumes. This approach may have inherent risk associated with it, that risk being that there is no off site copy of the data that can be used in the event that the primary server location, hardware, or data center is damaged or destroyed. Note: This approach does not provide for an off site copy of the data or the use of Tivoli Storage Manager's DRM feature. If the primary product server or data center were damaged or destroyed this may result in the loss of data or inability to recover that data PRIMARY POOL DEDUPLICATED, SINGLE COPY STORAGE POOL NOT DEDUPLICATED, SINGLE COPY STORAGE POOL DEDUPLICATED In this case, the deduplicated copy storage pool is providing space savings for the primary server location as well as duplication of the data that resides in the primary storage pool. Keep in mind that Tivoli Storage Manager server deduplication is done at the level of a single storage pool so a deduplicated primary pool and a deduplicated copy storage pool will be referencing different chunks and maintaining different database references in order to track and manage the data chunks that represent a given file. On the other hand, the non-deduplicated copy storage pool in this case, is likely real tape (something other then DEVTYPE=FILE) and is being used along with DRM for the purpose of having an off site data protection site. The off site copy storage pool volumes in conjunction with an appropriate database backup can then be used to restore the server and restore/retrieve data from the copy storage pool volumes.
141
7718TSMDRM.fm
Value (Cost)
BC Tier 6 Storage mirroring (with or without automation) BC Tier 5 Software mirroring (transaction integrity) BC Tier 4 Point in Time disk copy, Tivoli Storage Manager BC Tier 3 Electronic Vaulting, Tivoli Storage Mgr BC Tier 2 Hot Site, Restore from Tape BC Tier 1 Restore Days from Tape
15 Min.
1-4 Hr..
4 -8 Hr..
8-12 Hr..
12-16 Hr..
24 Hr..
142
7718TSMDRM.fm
Typical recovery time: The length of recovery time in this instance is unpredictable. In fact, it may not be possible to recover at all. Your business longevity if any disaster where to occur is at risk.
143
7718TSMDRM.fm
7718TSMDRM.fm
Degraded Operations Objective (DOO) What will be the impact on operations with fewer data centers? Network Recovery Objective (NRO) How long to switch over the network? Normally all the components that make up continuous availability are situated in the same computer room. The building, therefore, becomes the single point-of-failure. While you must be prepared to react to a disaster, the solution you select may be more of a recovery solution than a continuous-availability solution. A recovery solution must then be defined by making a trade-off among implementation costs, maintenance costs, and the financial impact of a disaster. These will all be reviewed as a result of performing a business impact analysis of your business as part of a larger Business Continuity Plan. For more information on Business Continuity planning, seeIBM System Storage Business Continuity: Part 1 Planning Guide, SG24-6547 and IBM System Storage Business Continuity: Part 2 Solutions Guide, SG24-6548.
145
7718TSMDRM.fm
7. System Managed Encryption or Library Managed Encyrption (or equivalent functionality provided by other vendors) is used for any Tivoli Storage Manager full (or snapshot) database backup cartridges which are removed from the library a. when there is no SME or LME possible, transport and store the Tivoli Storage Manager database backup separately from the copypool data 8. All electronic vaulting is transferred over; a. an encrypted IP network segment, using VPN, IPSec or SSL based encryption b. OSI layer 1 - Fiber Channel network 9. All copypool data held off site should consist of active, inactive data and possibly deduplicated data.
146
7718DataDedup.fm
Chapter 7.
147
7718DataDedup.fm
7718DataDedup.fm
MD5 listed with the file. Example 7-1 shows a pair of example hashes for a given file: the two hash functions are MD5 and SHA-1 in this case. MD5 produces a 128-bit digest (hash value), where SHA1 produces a 160-bit value. This is shown by the different digest lengths (note the 05e4.. is shorter than the 0d14.. value).
Example 7-1 Hash values of two commonly used functions against the same file
# csum -h MD5 tivoli.tsm.devices.6.1.2.0.bff 05e43d5f73dbb5beb1bf8d370143c2a6 tivoli.tsm.devices.6.1.2.0.bff # csum -h SHA1 tivoli.tsm.devices.6.1.2.0.bff 0d14d884e9bf81dd536a9bea71276f1a9800a90f tivoli.tsm.devices.6.1.2.0.bff A typical method of deduplication is to logically separate the data in a store into manageable chunks then produce a hash value for each chunk, and store those hash values in a table. When new data is taken in (ingested) into the store, the table is then compared with the hash value of each new chunk coming in, and where theres a match, only a small pointer to the first copy of the chunk is truly stored as opposed to the new data itself. Typical chunk sizes could be anywhere in the range of 2KB to 4MB, although theorerically any chunk size could be used. There is a tradeoff to be made with chunk size: a smaller chunk size means a larger hash table, so if we use a chunk which is too small, the size of the table of hash pointers will be large, and could outweigh the space saved by deduplication. A larger chunk size means that in order to gain savings, the data must have larger sections of repeating patterns, so while the hash-pointer table will be small, the deduplication will find fewer matches. The hashes used in deduplication are similar to those used for security products; MD5 and SHA-1 are both commonly used cryptographic hash algorithms, and both are used in deduplication products, along with other more specialist customised algorithms. With any hash, there is a possibility of a collision, which is the situation when two chunks with different data happen to have the same hash value. This possibility is extremely remote: in fact the chance of this happening is less likely than the undetected, unrecovered hardware error rate. Other methods exist in the deduplication technology area which are not hash based, so do not have any logical possibility of collisions. One such method is called hyperfactor; this is implemented in the IBM ProtecTIER storage system.
149
7718DataDedup.fm
deduplication ratio might be as high as 202:1. This ignores a lot of factors but gives an idea of a best-case scenario. Alternatively, a compressed file (such as mpeg video) will not usually further compress or deduplicate at all, but the savings could still be 100:1 in the example above because the same data is repeated 101 times. Similar savings are also quite common on certain types of databases. Taking a very simple, traditional approach to backup (taking full backups daily) results in a high proportion of redundancy in the data stored, which traditionally meant lots of tapes. On tape we might be looking at 20 or more copies of the same files, each containing the same redundancies. In the example above, we could mutliply the 200:1 ratio by nearly 20 in such a case. Deduplicating that sort of system is a very good idea indeed, from a space-savings point of view: the ratios achieved would be high, the space savings large. With Tivoli Storage Manager, IBM has always endeavoured to use storage more intelligently. The progressive incremental backup method reduces the duplication inherent in backups, so when we look at equivalent ratios for Tivoli Storage Manager backup data, they do not flatter the deduplication equipment so much. What we are really seeing here is how much more efficient Tivoli Storage Manager is at avoiding duplicates in the first place, than the traditional approach. We have tried to avoid un-necessary duplication, and in some ways Tivoli Storage Manager is still more efficent: for example, doing full backups every day still requires the processor, disk and network resources to move all the data to the deduplication system. With Tivoli Storage Manager and progressive incremental backups, we avoid reading a lot of that data, so we avoid using the resources. Add subfile backups to the solution, and we only move the parts of the files that have changed, further reducing the redundancy, before the data ever gets to the Tivoli Storage Manager Server.
150
7718DataDedup.fm
individually, so it is possible to deduplicate those types of data which will benefit most as opposed to everything. There is no requirement for it to be enabled for all pools. Data is deduplicated after ingestion, in order to allow the Tivoli Storage Manager server to accept data without the possibility of having to slow down in order to deduplicate inline. When migrating or copying from the FILE devtype pools to tape, Tivoli Storage Manager V6.1 does not store the deduplicated version of the data on tape devclass devices, instead it reconstructs the data so that full copies are stored on tape. This is to aid processing for recoveries, which could otherwise become difficult to manage. If Tivoli Storage Manager V6.1 had implemented deduplication with a fixed chunk size, the statistical probability of a collision would be to the order of 50% at 280 hashes. Since Tivoli Storage Manager varies its chunk size and uses that as part of the comparison, the possibility is made even more remote (something less remote than 50% probability at 2100 hashes) whereas a single Tivoli Storage Manager server is currently architecturally capable of storing 263 bitfile objects, itself impossible because of limitations in other places (for example, storage pool space to store the data from so many objects). The probability of a collision is very remote indeed. The average chunk size is typically about 250KB, although Tivoli Storage Manager V6.1 varies this as needed between 2KB and 4MB. Before Tivoli Storage Manager chunks the data at a bit file object level, it calculates an MD5 of all the objects in question, which are then sliced up into chunks. Each chunk has an SHA1 hash associated with it, which is used for the deduplication. The MD5s are there to verify that objects submitted to the deduplication system are reformed correctly, since the MD5 is recalculated and compared with the saved one to ensure that returned data is correct. Table 7-1 on page 151 shown an overview of data deduplication in Tivoli Storage Manager V6.1.
151
7718DataDedup.fm
Sizing deduplication
Sizing the deduplication in Tivoli Storage Manager versus externally in a VTL or similar is a judgement related to the system performance required. Reasons to consider Tivoli Storage Manager deduplication are: If you have a large preexisting disk storage pool and want to leverage this If you have CPU cycles available that are not already in use With Tivoli Storage Manager s new expiration algorithm - your Tivoli Storage Manager server may now have CPU/bandwidth available over Tivoli Storage Manager V5. If you cannot consider alternatives for cost, support, power or other reasons If your installation is too small to effectively use an alternative deduplication method Reasons to consider ProtecTIER or a similar deduplication device: If your Tivoli Storage Manager server is already CPU, memory or disk IO constrained If deduplication across Tivoli Storage Manager servers is desired If replication between sites of the deduplicated store is required For environments with many Tivoli Storage Manager Servers, or with larger amounts of data, we recommend looking at platforms like IBMs ProtecTIER product as best practice. Apart from scaling to very large sizes (at the time of writing, a single ProtecTIER custer handles 1PB of real (non - deduplicated) storage at access rates over 900MB/sec), it also opens the door to deduplication between separate Tivoli Storage Manager Servers, something Tivoli Storage Managers internal deduplication does not currently allow, as well as other benefits like inline deduplication, IP-based replication of stores and so on.
152
7718DataDedup.fm
An additional recommentation is to use storage media with fast access characteristics for Tivoli Storage Manager deduplication: we recommend SSD or SAS/FC over SATA disks, if deduplication performance is an issue. Random read I/O is the majority of the profile seen during deduplication processing, so concentrating on that has the best effect for deduplication.
Note: In terms of sizing Tivoli Storage Manager V6.1 deduplication, we currently recommend using Tivoli Storage Manager to deduplicate up to 6TB total of storagepool space for the deduplicated pools. This is a rule of thumb only and exists solely to give an indication of where to start investigating VTL or filer deduplication. The reason a particular figure is mentioned is for guidance in typical scenarios on commodity hardware. If more than 6TB of real diskspace is to be duplicated, you can either use Tivoli Storage Manager or a hardware deduplication device. The 6TB is in addition to whatever disk is required by non-deduplicated storagepools. This rule of thumb will change as processor and disk technologies advance, since the recommendation is not an architectural, support or testing limit.
153
7718DataDedup.fm
this is set to yes (which is the default), then data will only be processed for deduplication if it has been safeguarded previously by a storage pool backup. In order to expedite an example of this, the first thing we do here is disable the feature as shown in Example 7-2 on page 154.
Example 7-2 Disabling the default deduprequiresbackup feature tsm: UTAH-TSM1>setopt deduprequiresbackup no Do you wish to proceed? (Yes (Y)/No (N)) y ANR2119I The DEDUPREQUIRESBACKUP option has been changed in the options file. tsm: UTAH-TSM1>
Now we must set up a file-type device class. In the example, this is called dedupe, although we could have named it any way we wanted as with any other device class. We then create a new primary sequential storage pool called dd, on our new device class. Note that during the creation of this, we specify the deduplicate=yes parameter, and the number of identify processes along with the usual storage pool creation parameters (see Example 7-3 on page 154).
Example 7-3 Setting up a declass and deduplicated storage pool tsm: UTAH-TSM1>define devclass dedupe devtype=file mountl=20 maxcap=100m dir=/tsmstg ANR2203I Device class DEDUPE defined. tsm: UTAH-TSM1>define stgpool dd dedupe maxscr=100 deduplicate=yes identifyprocess=3 ANR2200I Storage pool DD defined (device class DEDUPE).
We have set up an example with a regular random disk storage pool with 10GB of space available, under the default backuppool storage pool. We put 3.7GB of backup data into it, as shown in Example 7-4.
Example 7-4 Our random diskpool containing 3.7GB of data
tsm: UTAH-TSM1>q stg Storage Pool Name ----------ARCHIVEPOOL BACKUPPOOL DD SPACEMGPOOL tsm: UTAH-TSM1> Device Class Name ---------DISK DISK DEDUPE DISK Estimated Capacity ---------0.0 M 10 G 10 G 0.0 M Pct Util ----0.0 37.0 0.0 0.0 Pct Migr ----0.0 37.0 0.0 0.0 High Mig Pct ---90 90 90 90 Low Mig Pct --70 70 70 70 Next Storage Pool ----------DD
Now we migrate from backuppool to dd using the nextstg parameter on the backuppool pointing to our new dd pool.
Example 7-5 Migrate STGPOOL tsm: UTAH-TSM1>migrate stg backuppool lo=0 ANR2110I MIGRATE STGPOOL started as process 5. ANR1000I Migration process 5 started for storage pool BACKUPPOOL manually, highMig=90, lowMig=0, duration=No.
154
7718DataDedup.fm
At this point, Tivoli Storage Manager starts processing the data for deduplication. We then run reclamation on the dd storagepool so volumes principally emptied out by the deduplication can be reclaimed. In terms of how deduplication processing works on the Tivoli Storage Manager Server, it looks slightly different if compared with other processes. Running the query process command on a server where a storage pool has deduplication enabled will always return some identify processes. From Tivoli Storage Manager V6.1.2 onward, these are called Identify Duplicates processes. These processes look for chunks of duplicated data, and there can be from one to twenty of them per storage pool. If there is no deduplication backlog, the deduplication processes will show up as idle. The deduplication processes are different because they stay resident - they do not terminate when they finish work, instead, they go to an idle mode until they are needed again, as shown in Example 7-6.
Example 7-6 Deduplication Identify Processes in idle mode, Tivoli Storage Manager V6.1.0 tsm: UTAH-TSM1>q pro Process Number -------2 Process Description -------------------Identify Process Status ------------------------------------------------Storage pool: DD. Volume: NONE. State: idle. State Date/Time: 06/10/09 14:32:14. Current Physical File(bytes): 0. Total Files Processed: 0. Total Duplicate Extents Found: 0. Total Duplicate Bytes Found: 0. Storage pool: DD. Volume: NONE. State: idle. State Date/Time: 06/10/09 14:32:14. Current Physical File(bytes): 0. Total Files Processed: 0. Total Duplicate Extents Found: 0. Total Duplicate Bytes Found: 0. Storage pool: DD. Volume: NONE. State: idle. State Date/Time: 06/10/09 14:32:14. Current Physical File(bytes): 0. Total Files Processed: 0. Total Duplicate Extents Found: 0. Total Duplicate Bytes Found: 0.
Identify Process
Identify Process
tsm: UTAH-TSM1>
In addition to these new processes, deduplication has some effects on already existing processes. When Tivoli Storage Manager deduplication runs, it dereferences objects no longer required by Tivoli Storage Manager in a similar way as expiration does, and in common with expired objects on sequential media, we must run reclamation in order to recover the space on those volumes. As part of an administrative schedule or maintenance plan, we would usually run reclamation after deduplication. Another command affected by deduplication is the query stgpool command, which now shows three extra pieces of information as shown in Example 7-7.
Example 7-7 Query STGPool including new deduplication information
155
7718DataDedup.fm
tsm: UTAH-TSM1>q stg dd f=d Storage Pool Name: Storage Pool Type: Device Class Name: Reclamation Type: Overwrite Data when Deleted: . . . Deduplicate Data?: Yes Processes For Identifying Duplicates: 3 Duplicate Data Not Stored: 1,526 M (38%) DD Primary DEDUPE Threshold
tsm: UTAH-TSM1>
Before enabling Tivoli Storage Manager deduplication on a previously existing server, we must understand the consequences. During initial deduplication processing, the Tivoli Storage Manager log file and database will grow. The log grows because the database will be processing lots of transactions, and the database will grow to accommodate the table for hashes of objects and hashes for the chunks which enables deduplication to function. The size of this table is proportional to the number of chunks and objects Tivoli Storage Manager is processing. If we have a Tivoli Storage Manager server with a 30GB DB, and we deduplicate every object in storage (because all of our objects are on a file-based storage pool), we may end up with a 70GB Tivoli Storage Manager database, so it is important to have available database and log space when turning on deduplication on a live system. Disabling deduplication does not delete the hash information for objects already chunked, so there is no way of simply going back to the 30GB version of our database. In order to do that, we would have to remove the existing backup data either by expiring it, or by backing up the data to new nodes and then deleting the relevant filespaces. Even if we delete filespaces (thus de-referencing the objects in storage), Tivoli Storage Manager will still spend some time resolving the deduplication hashes in the background. This takes time, for example, it may take up to a day for changes to filter through on a very busy system.
156
7718TSMNoQueryRestoreChanges.fm
Chapter 8.
157
7718TSMNoQueryRestoreChanges.fm
8.1 Introduction
Restore (NQR).
Tivoli Storage Manager restore processing is done in one of two models, Classic or No Query
The NQR reduces the memory requirement on Tivoli Storage Manager clients during restore and is optimized for large file systems. In installations with clients backing up very large client file systems or backup data spread over many volumes, performance issues were reported when the NQR technique is used and only very few files qualify as restore candidates. The changes made to the NQR restore process, by exploiting the DB2 database, address this issues.
158
7718TSMNoQueryRestoreChanges.fm
No new messages
Session established with server MERLOT1: Solaris SPARC Server Version 5, Release 5, Level 0.0 Server date/time: 06/24/2009 18:56:00 Last access: 06/24/2009 15:36:15 Total Total Total Total Total Total Total Total number number number number number number number number of of of of of of of of objects objects objects journal objects objects objects objects inspected: restored: updated: objects: rebound: deleted: expired: failed: 178 178 0 0 0 0 0 0
159
7718TSMNoQueryRestoreChanges.fm
Total number of bytes transferred: 204.92 KB LanFree data bytes: 0 B Data transfer time: 8,519.75 sec Network data transfer rate: 0.02 KB/sec Aggregate data transfer rate: 0.02 KB/sec Total number of bytes pre-compress: 0 Total number of bytes post-compress: 0 Objects compressed by: 0% Elapsed processing time: 02:28:12 Average file size: 0 B
Session established with server MERLOT1: Solaris SPARC Server Version 5, Release 5, Level 0.0 Server date/time: 05/24/2009 12:35:45 Last access: 06/24/2009 10:02:38 Total number of objects inspected: 178 Total number of objects restored: 178 Total number of objects updated: 0 Total number of journal objects: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred: 204.92 KB LanFree data bytes: 0 B Data transfer time: 1.02 sec Network data transfer rate: 199.34 KB/sec Aggregate data transfer rate: 49.01 KB/sec Total number of bytes pre-compress: 0 Total number of bytes post-compress: 0 Objects compressed by: 0% Elapsed processing time: 00:00:04 Average file size: 0 B
Session established with server MERLOT1: Solaris SPARC Server Version 6, Release 1, Level 0.0 Server date/time: 06/25/2009 15:14:29 Last access: 06/25/2009 15:13:31
160
7718TSMNoQueryRestoreChanges.fm
Total number of objects inspected: 178 Total number of objects restored: 178 Total number of objects updated: 0 Total number of journal objects: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred: 204.92 KB LanFree data bytes: 0 B Data transfer time: 0.01 sec Network data transfer rate: 13,661.91 KB/sec Aggregate data transfer rate: 33.00 KB/sec Total number of bytes pre-compress: 0 Total number of bytes post-compress: 0 Objects compressed by: 0% Elapsed processing time: 00:00:06 Average file size: 0 B
Again, please note that these numbers were collected for a synthetic test, values for a production environment will vary depending on server load, object distribution, and other affects that might impact performance.
8.2 Summary
With the transition to DB2 and the changes made to the NQR process you get comparable restore performance without having to configure anything.
161
7718TSMNoQueryRestoreChanges.fm
162
7718TSMExpirationEnhancements.fm
Chapter 9.
Expiration enhancements
In this chapter we discuss the enhancements to the Tivoli Storage Manager V6.1 server EXPIRATION process and the externals that are introduced with the changed process.
163
7718TSMExpirationEnhancements.fm
9.1 Introduction
The Tivoli Storage Manager expiration process deletes server objects from the database that no longer conform to the rules in associated management classes.
Algorithm only used two threads. Search algorithm could scan a lot of objects that were not actually eligible for expiration.
Figure 9-1 Legacy expiration algorithm
Flexibility: Many administrators expressed the desire to be able to run expiration on specific node(s). This would allow them to cleanup from some sort of policy error or change or to simply expire out old data for a client node that was consuming a large amount of space in the storage hierarchy.
164
7718TSMExpirationEnhancements.fm
This flexibility is partly available in the legacy expiration processor. For instance, you are allowed to specify a sequential range of node ids via undocumented options (begin node id/end node id). There is no ability to specify multiple nodes that are not sequentially aligned within the expiration table. This also requires that you have knowledge of node ids. As there is no documented procedure how to retrieve the node ids, most of the time a service call was necessary to exploit the function.
preserves Restart ability Command initiated (command or administrative schedule) Server initiated (based on EXPINTERVAL)
165
7718TSMExpirationEnhancements.fm
Not only the dispatch thread logic has changed to take advantage of the new server database schema, you now can also define how many threads you want to allow for expiration via the RESOURCE parameter.
166
7718TSMExpirationEnhancements.fm
'-Wait--=--+-No--+-' '-Yes-'
'-SKipdirs--=--+-No--+-' '-Yes-'
.-Node--=--*------------------. >--+-----------------------------+------------------------------> '-Node--=---node1,node2,...---' >--+-------------------------------------+----------------------> '-DOmain--=----domainName-------------' .-REsource--=--4--------. >--+-----------------------+------------------------------------> '-REsource--=--value--+-' .-Type--=--ALl---------. >--+----------------------+-------------------------------------> '-Type--=--+-ALl-----+-' |-ARchive-| |-Backup--| '-Other---' >--+-----------------------+-----------------------------------? '-DUration--=--minutes-'
Table 9-1 documents different combinations for the new parameters to the expiration command, valid and invalid ones, and the expected results. Use the examples as a starting point to review your current expiration schedules.
Table 9-1 Sample expiration process NODE and DOMAIN parameter combinations Node Value None Domain Value None Result All nodes for all domains will be processed. This is the default behavior. Invalid domain may not be wild carded. All nodes for all domains will be processed. All nodes assigned to the specified domain will be processed. Invalid domain may not be wild carded. All nodes matching the pattern DEPT_A* that are assigned to domain XXX will be processed. Nodes A, B, C and any matching the pattern D* will be processed.
* * None
* None DOMAIN=xxx
None NODE=DEPT_A*
DOMAIN=xxx* DOMAIN=xxx
NODE=A,B,C,D*
None
167
7718TSMExpirationEnhancements.fm
The expiration process TYPE parameter allows to define which specific data types to expire. You can specify one of the four following values, with ALL being the default: ARCHIVE: process only archive data for the candidate nodes. BACKUP: process only backup data for the candidate nodes. OTHER: process remote DRM recovery plan files and database backups from the volume history. ALL: process all eligible data (Archive, Backup, and Other) The expiration process RESOURCE parameter specifies the number of threads that can run in parallel. Specify a number from 1 to 10. The resources represent parallel work by the server within the single expiration process (expiration still runs as a single process). For example, if you specify NODE=X,Y,Z and RESOURCE=3 (or greater), then expiration processing for the three client nodes X, Y, and Z runs in parallel. NODE=X,Y,Z and RESOURCE=5, then expiration processing for the three client nodes runs in parallel, and the extra two resources are ignored.
168
7718TSMExpirationEnhancements.fm
Open the Select Action dropdown list and click Expire Inventory as shown with Figure 9-4 on page 169.
From the Expire Inventory window for server UTAH_TSM1,as shown in Figure 9-5 on page 170, you can specify all the options to fit your needs. See that the window supports all new parameters, the number of threads to be utilized, which data to process, domain and node selection. For the domain parameter, you can select the domain from a list of available domains configured to your system.
169
7718TSMExpirationEnhancements.fm
170
7718TSMExpirationEnhancements.fm
The maintenance script wizard includes the following tasks: Back up primary storage pools Copy active data from a primary pool to an active-data pool Back up the server database Identify the copy storage pool and database backup volumes to be moved Create a disaster recovery plan file Migrate stored data from primary storage pools to secondary storage pools Remove expired data from server storage Reclaim fragmented tapes by consolidating active data
Here we look at the expiration task only, so after the wizards welcome screen you are guided through the definitions for database backup and storage pool migration before you are presented with the Expire Stored Data window (see Figure 9-7 on page 172). In this scenario we specify the expiration process to run for 20 minutes with 8 threads. Once completed click Next to continue.
171
7718TSMExpirationEnhancements.fm
Again, the wizard helps you, now with the definitions for reclamation and maintenance scheduling. Finally, before you click Finish, you are asked to review the settings specified in the Wizard as shown in Figure 9-8. The settings you made in the expiration wizard are listed under the Expire Stored Data section.
ANR2017I Administrator ADMIN issued command: EXPIRE INVENTORY ANR0984I Process 2 for EXPIRE INVENTORY started in the BACKGROUND at 09:24:56. ANR0811I Inventory client file expiration started as process 2.
172
7718TSMExpirationEnhancements.fm
.. lines deleted .. ANR0165I Inventory file expiration started processing for node OLDSKOOL, filespace \\gallium\g$, copygroup BACKUP and object type FILE. ANR2017I Administrator ADMIN issued command: QUERY PROCESS ANR0166I Inventory file expiration finished processing for node OLDSKOOL, filespace \\gallium\g$, copygroup BACKUP and object type FILE with processing statistics: examined 9649, deleted 9649, retrying 0, and failed 0. ANR2369I Database backup volume and recovery plan file expiration starting under process 2. .. lines deleted .. ANR0167I Inventory file expiration process 2 processed for 13 minutes. ANR0812I Inventory file expiration process 2 completed: processed 8 nodes, examined 239685 objects, deleting 239685 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried and 0 errors were encountered. ANR0987I Process 2 for EXPIRE INVENTORY running in the BACKGROUND processed 239685 items with a completion state of SUCCESS at 09:38:23.
Have a look at the statistics here: while the expiration methodology did not change much, the exploitation of DB2 allows the algorithm to be much more efficient, in most cases the expiration process inspects only what is eligible for expiration. However, you might see more objects inspected related to the number of objects expired when processing expiration for example on backupset objects, DRM plan files or a retention enabled server. For each node, filespace, data type, and object type processed, the ANR0165I and ANR0166I messages are reported as with Example 9-3.
Example 9-3 Expiration messages ANR0165I and ANR0166I
ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY node=capitola,monterey,pleasanton reso=3 type=backup ANR0984I Process 1 for EXPIRE INVENTORY started in the BACKGROUND at 10:48:59. (PROCESS: 1) ANR0811I Inventory client file expiration started as process 1. (PROCESS: 1) ANR0165I Inventory file expiration started processing for node PLEASANTON, filespace \1000000KB_of_10KB, copygroup BACKUP and object type FILE. (PROCESS: 1) ANR0166I Inventory file expiration finished processing for node PLEASANTON, filespace \1000000KB_of_10KB, copygroup BACKUP and object type FILE with processing statistics: examined 10004, deleted 10004, retrying 0, and failed 0. (PROCESS: 1) ANR0165I Inventory file expiration started processing for node MONTEREY, filespace \1000000KB_of_10KB, copygroup BACKUP and object type FILE. (PROCESS: 1) ANR0166I Inventory file expiration finished processing for node MONTEREY, filespace \1000000KB_of_10KB, copygroup BACKUP and object type FILE with processing statistics: examined 90006, deleted 90006, retrying 0, and failed 0. (PROCESS: 1) ANR0167I Inventory file expiration process 1 processed for 7 minutes. (PROCESS: 1) ANR0812I Inventory file expiration process 1 completed: processed 3 nodes, examined 100010 objects, deleting 100010 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried and 0
Chapter 9. Expiration enhancements
173
7718TSMExpirationEnhancements.fm
errors were encountered. (PROCESS: 1) ANR0987I Process 1 for EXPIRE INVENTORY running in the BACKGROUND processed 100010 items with a completion state of SUCCESS at 10:56:24. (PROCESS: 1)
When expiration processes backupsets, as with Example 9-4, a different set of messages is reported, ANR0190I and ANR0191I. The summary records are cut each time an ANR0166I is issued.
Example 9-4 Expiration messages ANR0190I and ANR0191I
ANR0190I Inventory file expiration started processing node ALMADEN for backup sets. .. lines deleted .. ANR0191I Inventory file expiration finished processing node ALMADEN for backup sets with processing statistics: examined 2, deleted 0, retrying 0, and failed 0.
The output returned by the QUERY PROCESS command has changed, see Example 9-5 on page 174. You should remember that the number of nodes reported includes in-flight nodes.
Example 9-5 QUERY PROCES command expiration record
Expiration
Processed 8 nodes, examined 134746 objects, deleting 134746 backup objects, 0 archive objects, 0 DB backup volumes, 0 recovery plan files; 0 objects have been retried and 0 errors encountered.
174
7718TSMExpirationEnhancements.fm
If a command is re-issued and there is a matching restart position, expiration finishes processing those in-flight nodes and then any other nodes that had not been processed and that were candidates to be processed for that expiration run. If restart data exists for a given expiration and the command has not been re-executed for two weeks (14 days), the "stale" restart data is deleted such that the next time this expiration command is run it will start from the beginning. The deletion of the stale expiration restart information happens as a part of expiration processing itself - at the end of the process while cleaning up the existing process and information it checks for and deletes any stale restart information. Once all candidate nodes for that expiration have been processed, across however many restarts that may be, the expiration process will complete and the restart tracking will be cleaned up as there is no more restart position to track. Example 9-6 shows the ANR4896I message issued in case of an expiration restart. We use the domain parameter with the expire command to process only nodes for domain OTHERDOMAIN.
Example 9-6 ANR4896I: expiration restart message
ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY reso=2 dom=otherdomain ANR0984I Process 1 for EXPIRE INVENTORY started in the BACKGROUND at 08:57:04. ANR0811I Inventory client file expiration started as process 1. .. lines deleted .. ANR2017I Administrator SERVER_CONSOLE issued command: CANCEL PROCESS 1 ANR0940I Cancel request accepted for process 1. .. lines deleted .. ANR0167I Inventory file expiration process 1 processed for 1 minutes. ANR0813I Inventory file expiration process 1 canceled prior to completion: processed 4 nodes, examined 11 objects, deleting 10 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried and 0 errors were encountered. ANR0987I Process 1 for EXPIRE INVENTORY running in the BACKGROUND processed 11 items with a completion state of SUCCESS at 08:58:05. .. lines deleted .. ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY reso=2 dom=otherdomain ANR0984I Process 2 for EXPIRE INVENTORY started in the BACKGROUND at 08:59:38. ANR0811I Inventory client file expiration started as process 2. ANR4896I Inventory client file expiration is restarting process 1 from 06/19/2009. .. lines deleted .. ANR2017I Administrator SERVER_CONSOLE issued command: CANCEL PROCESS 2 ANR0940I Cancel request accepted for process 2. .. lines deleted ..
Chapter 9. Expiration enhancements
175
7718TSMExpirationEnhancements.fm
ANR0987I Process 2 for EXPIRE INVENTORY running in the BACKGROUND processed 5893 items with a completion state of SUCCESS at 09:00:23. ANR2017I Administrator SERVER_CONSOLE issued command: QUERY PROCESS ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY reso=2 dom=otherdomain ANR0984I Process 3 for EXPIRE INVENTORY started in the BACKGROUND at 09:00:48. ANR0811I Inventory client file expiration started as process 3. ANR4896I Inventory client file expiration is restarting process 2 from 06/19/2009. ANR2369I Database backup volume and recovery plan file expiration starting under process 3. .. lines deleted .. ANR0167I Inventory file expiration process 3 processed for 2 minutes. ANR0812I Inventory file expiration process 3 completed: processed 1 nodes, examined 35003 objects, deleting 35003 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried and 0 errors were encountered. ANR0987I Process 3 for EXPIRE INVENTORY running in the BACKGROUND processed 35003 items with a completion state of SUCCESS at 09:02:57.
Consider the following scenario: Expiration starts and determines that nodes A, B, C, D, E, F, G, H, I and J need to be processed. Expiration completes processing nodes A and B, nodes C and D are in-flight at the time expiration is cancelled. Expiration is invoked again and begins by processing C and D based on the restart information of what was previously done. As C and D complete, expiration progresses to the remaining candidate nodes, which in this case would be E, F, G, H, and I. Expiration would progress in this manner across cancellations and restarts until all nodes from the original candidate list were completed. Once expiration completes processing all nodes from the original candidate list, a new EXPIRATION invocation resolves a new candidate node list and begins processing as just described. Figure 9-9 explains the scenario we just described, for easier understanding it assumes that the expiration payload is the same for all nodes:
176
7718TSMExpirationEnhancements.fm
EXPIRATION RESTART
EXPIRE INVENTORY NODES=A,B,C,D,E,F,GH,I,J RES=4
NODE A NODE B NODE C NODE D NODE E NODE F WAIT WAIT NODE G WAIT NODE H WAIT NODE I WAIT NODE J WAIT
Cancel exp
Cancel exp
Now with all the new expiration parameters, you might wonder what happens if expiration is trying to expire a single node from multiple processes in parallel. We tried to expire the same node with two separate expiration commands and different parameters to make the commands distinct. Example 9-7 shows that the condition is detected and only one process expires the nodes data.
Example 9-7 Parallel expiration attempt for the same node
ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY node=oldskool reso=1 ANR0984I Process 1 for EXPIRE INVENTORY started in the BACKGROUND at 10:26:02. ANR0811I Inventory client file expiration started as process 1. ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY node=oldskool reso=2 ANR4298I Expiration thread already processing - unable to begin another expiration process.
Then we tried the same by defining a nodegroup and we added the same node plan to expire to that group. Example 9-8 shows that the condition is detected again, in addition you see that you can invoke expiration on NODEGROUPS defined to the server.
Example 9-8 Parallel expiration attempt, node and nodegroup
TSM:TIRAMISU>def nodegroup expiregroup ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE NODEGROUP expiregroup ANR4780I Node group EXPIREGROUP defined. TSM:TIRAMISU>define nodegroupmember expiregroup oldskool ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE NODEGROUPMEMBER expiregroup oldskool ANR4789I Node OLDSKOOL associated to node group EXPIREGROUP.
177
7718TSMExpirationEnhancements.fm
ANR4787I DEFINE NODEGROUPMEMBER: 1 members defined in the node group EXPIREGROUP. TSM:TIRAMISU>expire inventory node=oldskool ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY node=oldskool ANR0984I Process 1 for EXPIRE INVENTORY started in the BACKGROUND at 11:32:40. ANR0811I Inventory client file expiration started as process 1. TSM:TIRAMISU> .. lines deleted .. TSM:TIRAMISU>expire inventory node=EXPIREGROUP ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY node=EXPIREGROUP ANR4298I Expiration thread already processing - unable to begin another expiration process. .. lines deleted .. ANR0167I Inventory file expiration process 1 processed for 1 minutes. ANR0812I Inventory file expiration process 1 completed: processed 1 nodes, examined 47 objects, deleting 47 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried and 0 errors were encountered. ANR0985I Process 1 for EXPIRE INVENTORY running in the BACKGROUND completed with completion state SUCCESS at 11:32:55.
If you see the ANR4298I reported in your activity log, this might be caused by the fact that you configured the same node and type to different expiration jobs.
ANR0166I Inventory file expiration finished processing for node NODE1, filespace \\ibm-164391ac47a\c$, copygroup ARCHIVE and object type FILE with processing statistics: examined 400, deleted 400, retrying 400, and failed 0. If the expiration process retries the same batch five times and still cannot acquire the necessary locks, the expiration status message reflects this as shown in Example 9-10. Once this situation is encountered expiration attempts to throttle back the number of files contained within the deletion transaction batch in an attempt to delete as much as possible and minimize risk of lock conflicts.
178
7718TSMExpirationEnhancements.fm
ANR0166I Inventory file expiration finished processing for node NODE1, filespace \\ibm-164391ac47a\c$, copygroup ARCHIVE and object type FILE with processing statistics: examined 400, deleted 0, retrying 0, and failed 400. The expiration process is robust against locking problems it might encounter and will retry the operation if a locking condition is met.
9.3 Summary
The Tivoli Storage Manager V6.1 enhancements to the server expiration process integrate the new database schema and provide: Improved efficiency by abandoning the producer/consumer thread model. Each thread involved examines and deletes its own candidate list independent of the other threads that may be running. The workload is split up across the available number of threads designated by the RESOURCE value on the command. Improved flexibility by giving you the ability to control for whom expiration is done and what is expired.
179
7718TSMExpirationEnhancements.fm
180
7718TSMTxnGroupmaxDefault.fm
10
Chapter 10.
181
7718TSMTxnGroupmaxDefault.fm
7718TSMTxnGroupmaxDefault.fm
transactions end, the recovery log can release the space that is used by the oldest transactions. These transactions complete, and the log space usage increases. Based on the previous two examples, five concurrent transactions with a TXNGROUPMAX setting of 2000 consume significantly more space in the recovery log. This increase in log space usage also increases the risk of running out of recovery log space. Table 10-1 shows a comparison of the examples of the preceding TXNGROUPMAX settings. This example becomes more significant if a given log record takes 100 bytes.
Table 10-1 Example of log bytes that are consumed by five concurrent sessions TXNGROUPMAX Setting TXNGROUPMAX=20 TXNGROUPMAX=2000 Number of Log Bytes Consumed 100.000 10.000.000
183
7718TSMTxnGroupmaxDefault.fm
Have a look at the following numbers collected in our lab. We make sure we back up the data to a clean filesystem, 25000 files of 10kb each. With the new TXNGROUPMAX default of 4096 we see the numbers as reported with Example 10-1.
Example 10-1 Storage pool migration statistics, TXNGROUPMAX 4096
tsm: UTAH-TSM1>show transferstats backuppool Statistics for last migration from pool BACKUPPOOL Start date/time: 06/12/09 01:07:03 Elapsed time: 10 seconds Total wait time: 0 seconds Number of participating processes: 1 Total duration of all processes: 10 seconds Total physical files: 7 Total logical files: 25000 Total bytes: 261603328 Average logical files per physical file: 3571.4 Average physical file size: 36496.0 KB Number of batch/file transactions ended: 1 Number of batch transactions aborted: 0 Number of file transactions started: 0 Number of file transactions aborted: 0 No storage pool backup information available for BACKUPPOOL. Do not expect the average logical files per physical file be exact the number specified with the TXNGROUPMAX option. There are more factors involved, but at least the numbers should be close enough. The 3571 files from the above example are fine. We now delete the clients filesystem on the server an do the exact same backup, followed by a migration. The numbers are reported in Example 10-2.
Example 10-2 Storage pool migration statistics, TXNGROUPMAX 256
tsm: UTAH-TSM1>show transferstats backuppool Statistics for last migration from pool BACKUPPOOL Start date/time: 06/12/09 01:19:12 Elapsed time: 15 seconds Total wait time: 1 seconds Number of participating processes: 1 Total duration of all processes: 15 seconds Total physical files: 98 Total logical files: 25000 Total bytes: 261603328 Average logical files per physical file: 255.1 Average physical file size: 2606.9 KB Number of batch/file transactions ended: 1 Number of batch transactions aborted: 0 Number of file transactions started: 0 Number of file transactions aborted: 0 No storage pool backup information available for BACKUPPOOL.
Even with this simple example the migration already took much longer than with the new default. 184
Tivoli Storage Manager V6.1 Technical Guide
7718TSMTxnGroupmaxDefault.fm
10.3 Summary
The new TXNGROUPMAX default better fits todays environments, especially when it comes to transfer to tape. At this point, you know how to control the settings are honored using the SHOW TRANSFERSTATS command.
185
7718TSMTxnGroupmaxDefault.fm
186
7718p04.fm
Part 4
Part
187
7718p04.fm
188
7718TSMHSMforWindows.fm
11
Chapter 11.
189
7718TSMHSMforWindows.fm
11.1 Introduction
IBM Tivoli Storage Manager for HSM for Windows client provides hierarchical storage management (HSM) for Windows NTFS file systems. HSM is a data storage system that automatically moves data between high-cost and low-cost storage media. HSM exists because high-speed storage devices, such as hard disk drives, are more expensive per byte stored than slower devices, such as optical discs and magnetic tape drives. While it would be ideal to have all data available on high-speed devices all the time, this is prohibitively expensive for many organizations. Instead, you can use HSM to store the bulk of your enterprise's data on slower devices, and then copy data to faster disk drives only when needed. With the previous versions of the code, migration jobs are used to control which data is to be migrated. These jobs contain the information, which files are to be migrated and which file space on the Tivoli Storage Manager server is used. All files that match the criteria of a job are migrated, and it does not matter, whether this job will migrate only few files or nearly all files. One migration job can span over multiple volumes, if nested volumes are present. A migration job can also span multiple volumes, if nested volumes are not present. You can add for example "D:\dir1" and "E:\Dir2" to one single migration job. In that case this single job will migrate files from two different volumes. Migration jobs can be executed manually in the HSM for Windows GUI or on the command line by running the dsmclc tool. It is not possible to schedule two jobs at the same time, as every HSM for Windows executable can be started only once at a time. Alternatively any scheduler can be used to start the dsmclc tool for migration. This provides some kind of "automated" migration for HSM for Windows, but does not guarantee a certain amount of free space in the volume nor does it generally avoid out of space situations, the typical space usage with this implementation is shown with Figure 11-1.
190
7718TSMHSMforWindows.fm
191
7718TSMHSMforWindows.fm
Figure 11-2 Space usage with version 6.1 HSM for Windows threshold migration
The capability to automatically maintain a certain amount of free space in the file system is similar to the Tivoli Storage Manager for Space Management threshold migration available on UNIX platforms. If you are used to the UNIX methodology of threshold migration, the HSM for Windows threshold migration differs from the one on UNIX platforms. Note: The HSM for Windows 6.1 client does not support on demand migration or premigration. Threshold migration monitors space usage, there is not out-of-space event like on UNIX. And, as the monitoring is done in configurable intervals, like every 5 minutes, it might happen, that the file system runs out of space in the meantime and applications get I/O errors.
11.2.1 Installation
Threshold migration is supported on all environments on which HSM for Windows is supported. In general the requirements are: Windows Server 2008 (Standard and Enterprise) Only 64 bit with minimum 1GB memory for HSM and minimum 100MB free disk space Single Node or MSCS Cluster Requires Tivoli Storage Manager Backup Archive client of the same version and PTF (6.1.X) being installed Requires the Tivoli Storage Manager Server to be at least 5.5 For MSCS cluster installations the client must be installed on every node, where files should be migrated or recalled (for example, on any node to which a volume with stubs can failover).
192
7718TSMHSMforWindows.fm
Figure 11-3 on page 193 is the IBM Tivoli Storage Manager HSM Client InstallShield Wizard Custom Setup. Select the IBM Tivoli Storage Manager Monitor Service and click Next to continue.
The installation itself does not require any planning, you just invoke the setup.exe to start installation. In order to configure HSM for Windows you need to contact your Tivoli Storage Manager server administrator to register the HSM client node and, if installed on a cluster, to grant proxy for the individual nodes. This is not part of the setup, but the setup displays the required commands. The IBM Tivoli Storage Manager Monitor Service will be installed by default. Upon a successful installation you can check via the Windows task manager if the monitor service is running. Search for hsmmonitor.exe as shown in Figure 11-4 on page 193.
You can also click Start Administrative Tools Services and search for the IBM Tivoli Storage Manager Monitor Service as shown in Figure 11-5.
193
7718TSMHSMforWindows.fm
You can also use the HSM command line client, dsmhsmclc.exe to verify the service is running, Example 11-1 shows the output of a dsmhsmclc check command.
Example 11-1 dsmhsmclc check output
C:\Program Files\Tivoli\TSM\hsmclient>dsmhsmclc.exe check Command Line HSM Reconcile and Threshold Migration Interface - Version 6, Release 1, Level 0.0 (c) Copyright by IBM Corporation and other(s) 2005, 2009. All Rights Reserved HSM Service is running: YES Monitor Service is running: YES DLL state: N/A (single node) HSMResTypDLL.dll version: N/A (single node) HSMResTypDLLEx.dll version: N/A (single node) Configuration check for volume 'D:\': success Highest return code was 0
11.2.2 Configuration
Example 11-1 on page 194 shows that the configuration check for volume D:\ was successful. We configured the volume for threshold migration using the HSM GUI. Click Tools Threshold Migration as shown in Figure 11-6.
194
7718TSMHSMforWindows.fm
On the Threshold Migration Settings panel, select the drive you want to be monitored for threshold migration and click Configure. In Figure 11-7 on page 195 you can see that that we specified the L:\ path.
You can now enter the Threshold Migration settings. We complete the configuration as shown with Figure 11-8 on page 196.
195
7718TSMHSMforWindows.fm
Table 11-1 explains the configurable options you have to set up threshold migration, the volume mount path and the server filespace definition is required, all other options come with a default.
Table 11-1 Threshold migration options Option volume mount path FILESpace Range Default Explanation name of the volume (like D:) - required target filespace on the Tivoli Storage Manager server - required disk usage that triggers the start of threshold migration disk usage that triggers the stop of threshold migration monitoring frequency interval for scanning for new candidates interval for validation of candidates
196
7718TSMHSMforWindows.fm
Explanation minimal size for a migration candidate minimal age for a migration candidate timestamp to be used to calculate the age of a file importance of file age relative to filesize backup files before migration
AGEWEIGHT BACKUPBEforemigrate
50 no
You can use the command line client to configure the parameters: dsmhsmclc -CONFIGUREThresholdmig D: -FILESPace HSMOldskool
All migration methods can run in parallel: threshold migration, job migration or file list migration can run in parallel. Any combination of the following is possible: job migration HSM GUI or dsmclc migrate <parameters> run migration based on file value (job migration) file list migration dsmclc migratelist <parameters> run migration based on external input (file list migration) Threshold migration hsmmonitor Service run migration based on capacity (threshold migration)
11.2.3 Operation
There are four major tasks to threshold migration, they run in parallel in different threads of the HSM monitor service: 1. Monitoring for file system threshold (MONitorinterval) Check the file system usage for High threshold 2. Scan for new candidates
197
7718TSMHSMforWindows.fm
The scan searches for new candidates in the volume and stores them in the candidates list. This candidates list is a binary file in the volume root and the name is dsmthreshmig.bin. This file is hidden and excluded from the backup with the B/A client. You can query the candidates list with the following command: dsmhsmclc -dumpthreshold -FILESYSTEM d: -CANDidateslist full There are three different types of scans: Regular scan (SCANinterval) regularly searches in the volume for new good candidates and adds them to the candidates list (dsmthreshmig.bin) Demand scan fills up the candidates list, if not enough candidates are available to migrate from HT to LT Emergency scan finds candidates during threshold migration, if no more candidates are available 3. Validation (CHECKCANDidatesinterval) Verifies that the files in the candidate list are still valid candidates and removes invalid candidates 4. Threshold migration The actual migration itself, gets candidates from candidates list and migrates them
11.3 Summary
Threshold migration is easy to understand and to configure and integrates seamless into the existing HSM for Windows client. The threshold migration starts when a high threshold (HT) is reached and continues to run until a low threshold (LT) is reached or until all migratable files are migrated. Once threshold migration is configured for your system, for example your file server will have almost always free space. You can, however, use threshold migration in combination with additional migration jobs, schedules or manual.
198
7718AActive Directory.fm
12
Chapter 12.
199
7718AActive Directory.fm
An active directory is a directory structure used on Microsoft Windows based computers and servers to store information and data about networks and domains (see Figure 12-2). It is primarily used for online information and was originally created in 1996 and first used with Windows 2000. An active directory (sometimes referred to as an AD) does a variety of functions including the ability to provide information on objects, helps organize these objects for easy retrieval and access, allows access by end users and administrators and allows the administrator to set security up for the directory. An active directory can be defined as a hierarchical structure and this structure is usually broken up into three main categories, the resources which might include hardware such as printers, services for end users such as web email servers and objects which are the main functions of the domain and network.
200
7718AActive Directory.fm
201
7718AActive Directory.fm
202
7718AActive Directory.fm
Restore ADOBJects Query SYSTEMSTate NTDS (Q Systemstate not new) Query ADOBJect sourcepathspec [options] Displays local Active Directorys deleted objects and corresponding attributes attributes from a System State backup, located on a Tivoli Storage Manager server (2008 server only) Windows Server 2003 Windows Server 2008
Supported clients
Query ADOBJect Options Table 12-1 on page 203 shows the options and how to use them.
Table 12-1 Active Directory options
Restore ADOBJect Sourcepathspec this specifies the Active Directory object or container to restore When a container is specified, all contents will also be restored See http://msdn2.microsoft.com/en-us/library/aa746384.aspx Full distinguished name of an object or a container Just the name attribute ('cn' or 'ou') wildcards might be used Wildcards are not supported in distinguished name specification Specification
203
7718AActive Directory.fm
Option
dateformat pick pitdate (2008 only) pittime (2008 only) replace timeformat
Where to use
dsm.opt or command line
Query SystemState ntds Specifies that you want to display a list of Active Directory backups This is existing command with new argument. This is only valid for 2008 Windows Server (see Example 12-1).
Example 12-1 Query SystemState ntds command
>>-Query SYSTEMSTate--+-----------------+---------------------->< +- BOOTABLE-------+ +- BITS-----------+ +- EVENTLOG-------+ +- RSM------------+ +- RSS------------+ +- CLUSTERDB------+ +- TLS------------+ +- WMI------------+ +- IIS------------+ +- DHCP-----------+ +- WINSDB---------+ +- component_name-+ +- NTDS-----------+ +- REGISTRY-------+ +- COMPDB---------+ '- SYSFILES-------'
Stagingdir path Defines the location where the client can restore the ntds DB Data is deleted by the client upon exit Used by Active Directory objects restore operation
204
7718AActive Directory.fm
205
7718AActive Directory.fm
Figure 12-5 Tivoli Storage Manager Client V6.1 - system state backup
206
7718AActive Directory.fm
Confirmation of Restore
Once you actually press the Restore button, you will see the information in Figure 12-6 on page 207.
Figure 12-6 ivoli Storage Manager Client V6.1 - Active Directory database directory restore
Figure 12-7 Tivoli Storage Manager Client V6.1 - organizational unit restore
207
7718AActive Directory.fm
208
7718TSMClientRestoreStats.fm
13
Chapter 13.
209
7718TSMClientRestoreStats.fm
TSM:TIRAMISU>q occ oldskool ANR2017I Administrator SERVER_CONSOLE issued command: QUERY OCCUPANCY oldskool Node Name Type Filespace FSID Storage Number of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) ---------- ---- ---------- ----- ---------- --------- --------- --------OLDSKOOL Bkup \\gallium3 FILEPOOL 50,539 816.33 816.33 \g$
Example 13-2 shows the QUERYSUMMARY output for a sample restore from that filesystem.
Example 13-2 QUERYSUMMARY output from sample restore
tsm> query ba \\gallium\g$\*\Eric* -su=yes -querysummary Size Backup Date Mgmt Class A/I File ----------------------0 B 06/25/2009 19:52:58 STANDARD llium\g$\mmw\load\750m\0058\0754\STOPDBG\Erica .. <lines deleted> .. 1,024 B 06/25/2009 20:16:51 DEFAULT A \\ga llium\g$\mmw\load\97656m1k\alt_sources\0272\0285\BDGXCC32\0744\0590\cascade\Eri c
Summary Statistics Total Files Total Dirs ----------- ---------68 2 Avg. File Size Total Data -------------- ---------18.07 KB 1.20 MB Memory Est. ---------26.62 KB
210
7718TSMClientRestoreStats.fm
The QUERYSUMMARY output allows you to better plan your restore and retrieve activities. Before you even start the restore you can verify that the target destination does not run out of storage space, or the client having enough memory available to complete the operation. The estimated number of volumes could indicate to do a server MOVE NODEDATA before starting the restore attempt.
211
7718TSMClientRestoreStats.fm
212
7718pComplimentary_Prods.fm
Part 5
Part
213
7718pComplimentary_Prods.fm
214
7718NSeries.fm
14
Chapter 14.
N Series support
Tivoli Storage Manager uses Network Data Management Protocol (NDMP) to perform high-performance, scalable backups and restores. The backups and restores minimize network traffic and transfer data outboard of the Tivoli Storage Manager client and server.
215
7718NSeries.fm
14.1 Overview
Tivoli Storage Manager V6 provides enhancements to address the really big filer challenge. Customers who are using very large filesystems on there systems often come to the point where it is not possible to do ether the standard incremental backup nor use the NDMP backup implementation with Table of Content created during backup. But there is the need of single file restore for several versions and often many retention days. A solution is needed that can put together several kinds of backup methods, like Snapshot backup, incremental backup, and block based image dump.Tivoli Storage Manager V6 provides enhancements designed to improve performance with IBM System Storage N series and NetApp Network Attached Storage (NAS) devices. Note: It is not necessary to upgrade to IBM Tivoli Storage Manager Version 6.1 Server in order to use this new fuction.
216
7718NSeries.fm
If you get the error message ANR4794E (see Example 14-1) during NAS backup or your NDMP backup seems to be very slow, you can verify it with an NDMP trace on your Filer and a Tivoli Storage Manager trace on your Tivoli Storage Manager-Server.
Example 14-1 Error message ANR4794E
ANR4794E The NAS file server 192.168.111.190 failed to open an NDMP data connection to the TSM tape server. Please verify that the file server is capable of outbound data connections.
Setup the NDMP Trace on the Filer and a Tivoli Storage Manager Trace on your Tivoli Storage Manager Server to find out what is going wrong (see Example 14-2 on page 217).
Example 14-2 setup the NDMP trace on the Filer
NAS1> ndmpd debug 70 ndmpd debug verbose: 70 ndmpd debug stack trace: false 217
7718NSeries.fm
ndmpd debug screen trace: true ndmpd debug file trace: true output after the test in /etc/log/ndmp.nnn looks similar to this: Jun Jun Jun Jun Jun Jun 05 05 05 05 05 05 02:51:33 02:51:33 02:51:33 02:51:33 02:51:33 02:51:34 GMT+02:00 GMT+02:00 GMT+02:00 GMT+02:00 GMT+02:00 GMT+02:00 [ndmpd:32]: [ndmpd:32]: [ndmpd:32]: [ndmpd:32]: [ndmpd:32]: [ndmpd:32]: Data connection type: 1 TCP Addr: 0.0.0.0 TCP Port: 0 Error code: NDMP_CONNECT_ERR IOException: Connection timed out NDMP message type: NDMP_DATA_ABORT
You have discovered that the TCP Address in the trace is 0.0.0.0 and the TCP Port is 0. Setup up the Tivoli Storage Manager trace on the server as shown in Example 14-3.
Example 14-3 Setup the Tivoli Storage Manager trace on the Server
trace disable * trace enable spi spid sessremote addmsg trace begin <pathandfilenamehere>
In this case it is necessary to define the dedicated network address to the server using the NDMPPREFDATAINTERFACE server option. After you have set the NDMPPREFDATAINTERFACE option the backup starts without an error as you can see in the trace (see Example 14-4).
Example 14-4 Results after setting the NDMPPREFDATAINTERFACE option
setopt ndmpprefdatainterface 192.168.111.81 output after the test in /etc/log/ndmp.nnn looks similar to this: Jun Jun Jun Jun Jun 05 05 05 05 05 03:02:34 03:02:34 03:02:34 03:02:34 03:02:34 GMT+02:00 GMT+02:00 GMT+02:00 GMT+02:00 GMT+02:00 [ndmpd:34]: [ndmpd:34]: [ndmpd:34]: [ndmpd:34]: [ndmpd:34]: Data connection type: 1 TCP Addr: 192.168.111.81 TCP Port: 2077 Error code: NDMP_NO_ERR NDMP message type: NDMP_DATA_START_BACKUP_V4
on TSM: trace flush trace end trace disable on the Filer: ndmpd ndmpd ndmpd ndmpd debug debug debug debug 0 verbose: 0 stack trace: false screen trace: true
218
7718NSeries.fm
ndmpd debug file trace: true To check the correct network interface, use the SYSSTAT function on the Filer to verify the Network speed (see Example 14-6).
Example 14-6 Sysstat shows data flow during full and differential backup of the NAS device
NAS1> sysstat -x 1 CPU NFS CIFS 64% 47% 47% 20% 33% 20% 17% 6% 8% 27% 56% 32% 28% 17% 40% 25% 36% 15% 15% 10% 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
HTTP 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Net kB/s in out 47 1658 67 2763 64 2763 50 2202 37 1667 59 2960 42 1939 26 1149 11 553 56 2741 56 2760 32 1928 59 3046 29 1658 61 3315 19 1106 36 2208 0 156 11 393 0 0
Disk kB/s read write 1668 20 2476 8 2656 0 2124 0 1564 0 2785 0 1940 8 807 0 1008 0 2627 0 1982 104 2084 64 2732 4 1900 8 2940 0 1076 0 2046 8 167 0 254 0 207 0
Cache age >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60 >60
219
7718NSeries.fm
Tape
Nseries
TSM Server
Figure 14-1 SnapMirror to tape support with Filer-to-Server and Filer-to-Tape
SnapMirror to Tape provides an alternative method for backing up very large NetApp file systems. Because this backup method has limitations, use this method when copying very large NetApp file systems to secondary storage for disaster recovery purposes. You can back up very large NetAppfile systems using the NetAppSnapMirror to Tape feature. Using a block-level copy of data for backup, the SnapMirror to Tape method is faster than a traditional Network Data Management Protocol (NDMP) full backup and can be used when NDMP full backups are impractical. Use the NDMP SnapMirror to Tape feature as a disaster recovery option for copying very large NetAppfile systems to secondary storage. For most NetApp filesystems, use the standard NDMP full or differential backup method, the new SnapDiff-API incremental backup, the snapshot functions of the filer or a combination of them. Using a parameter option on the BACKUP and RESTORE NODE commands, you can back up and restore file systems using SnapMirror to Tape. There are several limitations and restrictions on how SnapMirror images can be used. Consider the following guidelines before you use it as a backup method: You cannot initiate a SnapMirror to Tape backup or restore operation from the Tivoli Storage Manager Web client, command-line client or the Administration Center. You cannot perform differential backups of SnapMirror images. You cannot perform a directory-level backup using SnapMirror-to-Tape, Tivoli Storage Manager does not permit an SnapMirror to Tape backup operation on a server virtual filespace.
220
7718NSeries.fm
You cannot perform an NDMP file-level restore operation from SnapMirror to Tape images. Therefore, a table of contents is never created during SnapMirror to Tape image backups. At the start of a SnapMirror to Tape copy operation, the file server generates a snapshot of the file system. NetApp provides an NDMP environment variable to control whether this snapshot should be removed at the end of the SnapMirror to Tape operation.Tivoli Storage Manager always sets this variable to remove the snapshot. After a SnapMirror to Tape image is retrieved and copied to a NetAppfile system, the target file system is left configured as a SnapMirror partner. NetApp provides an NDMP environment variable to control whether this SnapMirror relationship should be broken. Tivoli Storage Manager always breaks the SnapMirror relationship during the retrieval. After the restore operation is complete, the target file system is in the same state as that of the original file system at the point-in-time of backup.
14.2.1 How to setup, use and control SnapMirror to Tape for bakup
The only difference between an normal NDMP Backup and a SnapMirror to tape backup is to specify the additional option type=snapm in the backup node and restore node administrative server command. The syntax for this option is described here.
TYPE
Specifies the backup method used to perform the NDMP backup operation. The default value for this parameter is BACKUPIMAGE and it should be used to perform a standard NDMP base or differential backup. Other image types represent backup methods that might be specific to a particular file server.
BACKUPImage
Specifies that the file system should be backed up using an NDMP dump operation. This is the default method for performing an NDMP backup. The BACKUPIMAGE type operation supports full and differential backups, file-level restore processing and directory-level backup.
SNAPMirror
Specifies that the file system should be copied to a Tivoli Storage Manager storage pool using the Network Appliance SnapMirror to Tape function. SnapMirror images are block level full backup images of a file system. Typically, a SnapMirror backup takes significantly less time to perform than a traditional NDMP full file system backup. However there are limitations and restrictions on how SnapMirror images can be used. The SnapMirror to Tape function is intended to be used as a disaster-recovery option for copying very large Network Appliance file systems to secondary storage. For most Network Appliance file systems, use the standard NDMP full or differential backup method. See the IBM Tivoli Storage Manager Administrators Guide for your platform for limitations on using SnapMirror images as a backup method. The Tivloi publications can be found at the Web site: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm. nav.doc/r_pdfs.html
221
7718NSeries.fm
Refer to the documentation that came with your Network Appliance file server for more information. When setting the TYPE parameter to SNAPMirror, note the following restrictions: You cannot specify TOC=YES or TOC=PREFERRED. The file_system_name cannot be a virtual filespace name. The snapshot which is created automatically by the file server during the SnapMirror copy operation will be deleted at end of the operation. This parameter is valid for Network Appliance and IBM N-Series fileservers only. An example of the TYPE option to start the SnapMirror to tape backup is shown in Example 14-7.
Example 14-7 how to start an SnapMirror to tape backup
dsmadmc: backup node SIM1 /vol/mixedvol01 type=snapm ANR2685I SnapMirror backup of NAS node SIM1, file system /vol/mixedvol01, started as process 16 by administrator TSMADMIN ANR0986I Process 16 for NAS SNAPMIRROR BACKUP running in the BACKGROUND processed 1 items for a total of 6,344,704 bytes with a completion state of SUCCESS. You will find the result of this task in several logs, queries and tables. An example of the Tivoli Storage Manager-Server Nas-Backup query is shown in Example 14-8.
Example 14-8 query nasbackup to display the SnapMirror to tape backups
tsm: TESTPC-81>query nasbackup sim1 * type=snapm Node Name Mgmt Class Image Name Storage Pool Name ------------ ----------- ----------- --------- ---------- ---------- ---------SIM1 /vol/vol0 SnapMirror 189.5 06/05/2009 STANDARD NASPOOL 18:45:00 SIM1 /vol/winvo- SnapMirror 5.5 06/03/2009 STANDARD NASPOOL l01 19:04:53 SIM1 /vol/winvo- SnapMirror 5.5 06/03/2009 STANDARD NASPOOL l01 20:21:36 SIM1 /vol/winvo- SnapMirror 5.5 06/03/2009 STANDARD NASPOOL l01 20:28:26 SIM1 /vol/winvo- SnapMirror 5.5 06/03/2009 STANDARD NASPOOL l01 20:45:13 SIM1 /vol/winvo- SnapMirror 5.5 06/03/2009 STANDARD NASPOOL l01 20:59:28 SIM1 /vol/winvo- SnapMirror 5.5 06/03/2009 STANDARD NASPOOL l01 21:06:49 SIM1 /vol/winvo- SnapMirror 6.1 06/04/2009 STANDARD NASPOOL l01 19:59:45 SIM1 /vol/winvo- SnapMirror 6.1 06/04/2009 STANDARD NASPOOL l01 20:02:31 more... (<ENTER> to continue, 'C' to cancel) SIM1 /vol/mixed- SnapMirror 6.1 06/06/2009 STANDARD NASPOOL Filespace Name Object Type Object Size (MB) Creation Date
222
7718NSeries.fm
>select start_time,end_time,activity,number,entity,examined,affected,failed, bytes,idle,mediaw,processes,successful from summary where activity like '%Snap%' START_TIME: END_TIME: ACTIVITY: NUMBER: ENTITY: EXAMINED: AFFECTED: FAILED: BYTES: IDLE: MEDIAW: PROCESSES: SUCCESSFUL: 2009-06-06 00:35:36.000000 2009-06-06 00:36:05.000000 NAS SnapMirror Backup 16 SIM1 1 1 0 6344704 0 1 1 YES
In the Filer logs is the snapmirror log ( see Example 14-10), which is always created during normal NDMP backup and SnapMirror to tape backup.
Example 14-10 Output of the /etc/logs/snapmirror
slk Sat Jun 6 02:00:10 CES state.softlock.mixedvol01.000003da.155.snapmirror_tape_6_6_09_02:00:09 Softlock_add (Transfer) src Sat Jun 6 02:00:11 CES sim1:mixedvol01 sim1:NDMP_REMOTE41 Request (Store) src Sat Jun 6 02:00:11 CES sim1:mixedvol01 sim1:NDMP_REMOTE41 Start src Sat Jun 6 02:00:30 CES sim1:mixedvol01 sim1:NDMP_REMOTE41 End (5160 KB, Compression 0.0 : 1) slk Sat Jun 6 02:00:30 CES state.softlock.mixedvol01.000003da.155.snapmirror_tape_6_6_09_02:00:09 Softlock_delete (Release)
223
7718NSeries.fm
operation. After the restore is complete, the target file system returns to the same state as that of the original file system at the point-in-time of the backup. You cannot specify the FILELIST parameter. Neither the source_file_system_name nor the destination_file_system_name can be a virtual filespace name. Restoration of traditional volume to unlike geometry can be very slow The destination of the retrieval must use the same or later version of Data ONTAP The traditional volume file system format is different from the FlexVol volume file system format FlexVol volume cannot be restored to a traditional volume Traditional volume cannot be restored to a FlexVol volume. This parameter is valid for Network Appliance and IBM N-Series file servers only.
224
7718NSeries.fm
The snapdiff option is for backing up NAS/N-Series file server volumes that are NFS or CIFS attached. When used with the incremental command, snapdiff streamlines the incremental process by performing an incremental backup of the files that were reported as changed by NetApp, instead of scanning the volume looking for files that have changed. Use this option with an incremental backup of a NAS filer volume instead of a simple incremental or incremental with snapshotroot whenever the NAS filer is running ONTAP V7.3 or later, for performance reasons. Do not use the snapdiff and snapshotroot options together. The first time you perform an incremental backup with this option, a snapshot is created (the base snapshot) and a traditional incremental backup is performed using this snapshot as the source. The name of the snapshot that is created is recorded in the Tivoli Storage Manager database. The second time an incremental backup is run with this option, a newer snapshot is either created or an existing one is used to find the differences between these two snapshots. This second snapshot is called the diffsnapshot. Tivoli Storage Manager then incrementally backs up the files reported as changed by snapdiff to the Tivoli Storage Manager server. The file space selected for snapdiff processing must be mapped or mounted to the root of the volume. You cannot use the snapdiff option for any file space that is not mounted or mapped to the root of the volume. After backing up data using the snapdiff option, the snapshot that was used as the base snapshot is deleted from the .snapshot directory. Tivoli Storage Manager does not delete the snapshot if it was not created by Tivoli Storage Manager. You can also perform a snapdiff incremental backup with the -DiffSnapShot=Latest option. For NAS and N-Series filers running ONTAP 7.3 or later, you can use the snapdiff option when performing a full volume incremental backup. Using this option reduces memory usage and speeds up the processing. However, similar to using the incremental-by-date method, the following considerations and situations apply: A file is excluded due to an exclude rule in the include-exclude file. Tivoli Storage Manager performs a backup of the current snapshot with that exclude rule in effect. This happens when you have not made changes to the file, but you have removed the rule that excluded the file. NetApp will not detect this include-exclude change because it only detects file changes between two snapshots. If you have added an include statement to the option file, that include option will not take effect unless NetApp detects that the file has changed. This is because Tivoli Storage Manager does not inspect each file on the volume during backup. You have used the dsmc delete backup command to explicitly delete a file from the Tivoli Storage Manager inventory. The NetApp will not detect that a file has been manually deleted from Tivoli Storage Manager. Therefore, the file remains unprotected in Tivoli
Chapter 14. N Series support
225
7718NSeries.fm
Storage Manager storage until it is changed on the volume and the change is detected by NetApp signalling Tivoli Storage Manager to back it up again. Policy changes such as changing the policy from mode=modified to mode=absolute are not detected. The entire file space is deleted from the Tivoli Storage Manager inventory. This causes the snapdiff option to create a new snapshot to use as the source, and a full incremental backup will be performed. Tivoli Storage Manager will not control what constitutes a changed object, that is controlled by NetApp. For more information see IBM Tivoli Storage Manager for Windows Backup-Archive Clients Version 6.1, SC23-9792 and IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients 6.1, SC23-9791
14.3.2 How the Backup Archive Client interacts with the SnapDiff-API
Here we describe the initial incremental backup with snapdiff option process. 1. Tivoli Storage Manager client creates a Snapshot version. You can use the diffsnapshot option to use the most recent externally creates Snapshot. 2. Tivoli Storage Manager backs up all files from Snapshot 3. The Snapshot name is stored in the Tivoli Storage Manager server Subsequent incrementals with snapdiff option process follow the following steps. 1. The name of the previous Snapshot is retrieved from Tivoli Storage Manager server 2. Tivoli Storage Manager client creates a new Snapshot version. You can use the diffsnapshot option to use the most recent externally creates Snapshot. 3. Snapshot differencing API compares previous and new Snapshot versions and reports file and directory differences to the Tivoli Storage Manager client 4. The Tivoli Storage Manager client backs up files identified in the report. 5. The new Snapshot name is stored in the Tivoli Storage Manager server for use in the next inceremental backup. 6. The Tivoli Storage Manager client deletes the previous Snapshot version, if you have not used the difsnapshot option to use the most recent externally created Snapshot. Figure 14-3 show how the Tivoli Storage Manager Client interacts with Snapshot Differencing API.
Figure 14-3 How Tivoli Storage Manager Client interacts with Snapshot Differencing API
226
7718NSeries.fm
tsm> set password -type=filer sim1 administrator Please enter password for user id "administrator@sim1": ***** Re-enter the password for verification:***** ANS0302I Successfully done. If you have mounted the file server volume with IP address, you should create the password with the appropriate IP address (see Example 14-12 on page 227).
Example 14-12 Specify set password with IP address
tsm> set password -type=filer 192.168.111.190 administrator Please enter password for user id "administrator@192.168.111.190": ***** Re-enter the password for verification:***** ANS0302I Successfully done. The result will be stored in the Windows Registry (see Figure 14-4).
Figure 14-4 Windows Registry with stored passwords
For AIX, you will use the same command, but the name resolution of the IP address should be possible, so you have to check the /etc/hosts. Example 14-13 shows, how to set up the password for the AIX Backup/Archive client.
227
7718NSeries.fm
dsmc set password -type=filer sim1 administrator tsm> set password -type=filer sim1 administrator Please enter password for user id "administrator@sim1": Re-enter the password for verification: ANS0302I Successfully done.
# more TSM.PWD This file contains an encrypted TSM password, do not change or delete. ^C^C^D^D^M^M^ENULLSIM1administratorM-^MM-^Pd^VJ0M-^EM-^QJ
If the password is not created correctly or if the name resolution did not work properly, you will get the error messages shown in Example 14-15.
Example 14-15 Error message when password is set incorrect
Incremental by snapshot difference of volume '/unix01' ANS2837E Failed to perform incremental backup operation using snapshot difference as the user id and password for NAS Filer 'sim1' have not been configured correctly. ANS2832E Incremental by snapshot difference failed for /unix01. Please see error log for details. ANS5283E The operation was unsuccessful.
You can find the reason of the error, using a TSM Client trace. To do this put the trace options in the dsm.opt client option file as shown in Example 14-16.
Example 14-16 AIX BA-Client Option File dsm.opt
Tracefile \tmp\tracefile.out Tracemax 2048 Tracesegsize 256 Traceflags enter exit general snapshot hci hci_detail diskmap diskmap_detail hdw hdw_detail
The output in the trace file as a result of entering the failed incremental command is sshown in Example 14-17.
Example 14-17 Trace-File output
06/04/09 18:53:21.764 : snapcommon.cpp ( 281): Entering nsGetNasVolumeInfo(): with: inputPath: </unix01>. 06/04/09 18:53:21.765 : PsDiskMapper.cpp (3531): dmMapNasVolume: statvfs() for </unix01>. vfs_num <19>. type<nf s3>. fsid<7> 06/04/09 18:53:21.765 : PsDiskMapper.cpp (3312): psCollectMountTableInfo: DevId:<19> NFS Mount point:</unix01>
228
7718NSeries.fm
NFS Volume:</vol/unixvol01> NFS Host Name:<192.168.111.190> NFS Mount Options: <>: 06/04/09 18:53:21.769 : PsDiskMapper.cpp (3795): psGetHostName(): gethostbyaddr() failed. hostname: <192.168.11 1.190>. Error: <1>. 06/04/09 18:53:21.769 : PsDiskMapper.cpp (3626): dmMapNasVolume(): psGetHostName() failed. hostname: <192.168.1 11.190>. Error: <6201>. 06/04/09 18:57:01.139 : PsDiskMapper.cpp (3531): dmMapNasVolume: statvfs() for </unix01>. vfs_num <19>. type<nfs3>. fsid<7> 06/04/09 18:57:01.139 : PsDiskMapper.cpp (3312): psCollectMountTableInfo: DevId:<19> NFS Mount point:</unix01> NFS Volume:</vol/unixvol01> NFS Host Name:<192.168.111.190> NFS Mount Options: <>: 06/04/09 18:57:01.143 : PsDiskMapper.cpp (3795): psGetHostName(): gethostbyaddr() failed. hostname: <192.168.11 1.190>. Error: <1>. 06/04/09 18:57:01.143 : PsDiskMapper.cpp (3626): dmMapNasVolume(): psGetHostName() failed. hostname: <192.168.1 11.190>. Error: <6201>. 06/04/09 18:57:01.144 : snapcommon.cpp ( 347): nsGetNasVolumeInfo(): dmMapNfsVolume() failed to map remote volume for path: </unix01>.
tsm> inc -snapdiff=yes /unix01 Incremental by snapshot difference of volume '/unix01' Performing a full incremental of volume '/unix01' to establish a base snapshot Successful incremental backup of '/unix01'
of of of of of of of
10,111 10,111 0 0 0 0 0
229
7718NSeries.fm
Total number of bytes transferred: 10.46 MB Data transfer time: 0.21 sec Network data transfer rate: 48,860.41 KB/sec Aggregate data transfer rate: 33.87 KB/sec Objects compressed by: 0% Elapsed processing time: 00:05:16 tsm>
The first time, a full incremental backup has to be taken, to establish a base snapshot. To verify the snapshots on your filer, enter the snap list command on your filer interface as shown in Example 14-19.
Example 14-19 Snap list command on Filer
snap list winvol01 Volume winvol01 working... %/used ---------1% ( 1%) 2% ( 1%) 3% ( 1%) 5% ( 1%) 10% ( 6%) 12% ( 2%) 13% ( 2%) 14% ( 1%) %/total ---------0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) date -----------Jun 04 20:00 Jun 04 16:00 Jun 04 12:00 Jun 04 08:00 Jun 04 00:00 Jun 03 20:00 Jun 03 16:00 May 25 00:00 name -------hourly.0 hourly.1 hourly.2 hourly.3 nightly.0 hourly.4 hourly.5 nightly.1
snap list unixvol01 Volume unixvol01 working... %/used ---------0% ( 0%) 0% ( 0%) 0% ( 0%) 1% ( 0%) 1% ( 0%) 1% ( 0%) 1% ( 0%) 1% ( 0%) %/total ---------0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) date -----------Jun 04 20:00 Jun 04 16:00 Jun 04 12:00 Jun 04 08:00 Jun 04 00:00 Jun 03 20:00 Jun 03 16:00 May 25 00:00 name -------hourly.0 hourly.1 hourly.2 hourly.3 nightly.0 hourly.4 hourly.5 nightly.1
snap list mixedvol01 Volume mixedvol01 working... %/used ---------1% ( 1%) 6% ( 5%) 7% ( 1%) 8% ( 1%) 230 %/total ---------0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) date -----------Jun 04 20:00 Jun 04 16:00 Jun 04 12:00 Jun 04 08:00 name -------hourly.0 hourly.1 hourly.2 hourly.3
7718NSeries.fm
( ( ( (
0% 0% 0% 0%
( ( ( (
04 03 03 25
The second time an incremental backup is run with this option, a newer snapshot is either created or an existing one is used to find the differences between these two snapshots. This second snapshot is called the diffsnapshot. Tivoli Storage Manager then incrementally backs up the files reported as changed by NetApp by the Tivoli Storage Manager server. The file space selected for snapdiff processing must be mapped or mounted to the root of the volume. You cannot use the snapdiff option for any file space that is not mounted or mapped to the root of the volume. After backing up data using the snapdiff option, the snapshot that was used as the base snapshot is deleted from the .snapshot directory. Tivoli Storage Manager does not delete the snapshot if it was not created by Tivoli Storage Manager. You can also perform a snapdiff incremental backup with the -DiffSnapShot=Latest option. This will be documented in the statistics at the end of the backup, that no objects were inspected (see Example 14-20 on page 231).
Example 14-20 Second incremental backup with NetApp snapshot difference
tsm> inc -snapdiff=yes /unix01 Incremental by snapshot difference of volume '/unix01' Successful incremental backup of '/unix01'
Total number of objects inspected: 0 Total number of objects backed up: 0 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred: 0 B Data transfer time: 0.00 sec Network data transfer rate: 0.00 KB/sec Aggregate data transfer rate: 0.00 KB/sec Objects compressed by: 0% Elapsed processing time: 00:00:04
If you are monitoring this backup on your filer, you will find that a snapshot will be created and after successful completion, the previous one will be deleted. Now, when we are looking for existing snapshots after we did the backup with NetApp snapshot difference, we will see the snapshot created and referenced by Tivoli Storage Manager as shown in Example 14-21.
Example 14-21 list snapshots after backup with NetApp snapshot difference
sim1*> snap list winvol01 Volume winvol01 working... %/used %/total date name 231
7718NSeries.fm
---------1% ( 1%) 2% ( 1%) 3% ( 1%) 4% ( 1%) 5% ( 1%) 6% ( 1%) 7% ( 1%) 8% ( 1%) 9% ( 1%) 10% ( 1%) 11% ( 1%) 12% ( 1%)
---------0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%) 0% ( 0%)
-----------Jun 09 19:21 Jun 09 19:15 Jun 09 18:55 Jun 06 00:00 Jun 05 20:00 Jun 05 16:00 Jun 05 12:00 Jun 05 08:00 Jun 05 00:00 Jun 04 21:16 Jun 04 20:00 Jun 04 16:00
-------TSM_TEST4A2E9A320_WINVOL01 newsnap02 newsnap01 nightly.0 hourly.0 hourly.1 hourly.2 hourly.3 nightly.1 TSM_RS604A280EA537B71_WINVOL01 hourly.4 hourly.5
The filesystem must be mounted either with IP Address or by network name. The password you have set must be stored with same IP Address or network name. The next step is to select the backup method, use the new function incrementsl (snapshot difference) instead of traditional incremental (see Figure 14-6 on page 233).
232
7718NSeries.fm
When you press the backup button, you will get another window that asks you, if you will create a new snapshot or if you will use an existing one that you have created before manually on the filer. In our case we select Create (see Figure 14-7 on page 234).
233
7718NSeries.fm
After successful backup, you will get the statistics, that shows 11 new files are backed up, but no files were inspected. This is because we are using NetApp (see Figure 14-8 on page 234).
Figure 14-8 Detailed statistics report from backup with NetApp snapshot difference
234
7718NSeries.fm
sim1> qtree qtree: This command is deprecated; using qtree status. Volume Tree Style Oplocks Status -------- -------- ----- -------- --------vol0 unix enabled normal winvol01 ntfs enabled normal unixvol01 unix enabled normal mixedvol01 mixed enabled normal It is highly recommended to avoid mixed style volumes: if mixed is necessary, avoid offering or using write-access from CIFS and NFS-world on volume-level. Backup only from that world, where writes are allowed. if mixed, avoid at least write-access from CIFS and NFS-world on directory-level. Backup only from that world, where writes are allowed on directory level. if you do mixed mode and write from different worlds (for example, NFS and CIFS) to the directory, you will loose some write-attributes over time (at least, when you have to restore from backups). Note: Backup of mixed style volumes is not supported with Tivoli Storage Manager backup archive client, even if it works
235
7718NSeries.fm
In this case, the password was set to the name and we are trying to do the backup against the ip address of the filer. So this is a dependency you must consider. This may not appear on AIX systems, when the IP Address can be resolved. Note: We could not use the Tivoli Storage Manager Web Client GUI, because mapped drives are not visible under the Network node in the Backup Tree Window of the Tivoli Storage Manager Web client GUI when connecting to Tivoli Storage Manager clients on Windows XP and Windows 2003. For more information refer to Technote Unable to view/back up network drives using Tivoli Storage Manager Web client on Windows, http://www-01.ibm.com/support/docview.wss?uid=swg21385371
236
7718NSeries.fm
performs better than classic incremental, but especially so when relatively few files have been changed. Testing was also performed on a small filesystem to ensure there was no performance degradation when using NetApp on such a system.
Test environment
Filer: N5300 with Data ONTAP Release 7.3 Tivoli Storage Manager Server: 5.5.1.0 on a 2-way 3.4 GHz, 4GB Windows Server 2003 Tivoli Storage Manager Client: 6.1.0.0 connected to local Tivoli Storage Manager Server Storage Pool: File pool on fibre-attached DS8K Small Workload: 8 thousand 100KB files Large Workload: 1.2 million 10KB files Huge Workload: 12 million 10KB files
Test conclusion
In the Huge Workload test, when 10% data changed, using NetApp snapshot difference improved throughput from 199 KB/sec to 537 KB/sec (170% improvement). As an example of reduced backup window, NetApp reduced the backup window of this test from almost 17 hours to about 6.25 hours (37% of the time). The improvement is quite significant when only a small percentage of the data changes. Specific results will vary depending on the hardware configuration. If the percentage of changed data is lower than 10%, an even greater improvement will be expected. http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm. nav.doc/r_pdfs.html
237
7718NSeries.fm
238
15
Chapter 15.
IBM Tivoli Storage Manager Data Protection for Mail - Exchange 6.1
The Tivoli Storage Manager for Mail 6.1 product updated the Data Protection for MS Exchange component. This product has been updated to include Individual Mailbox Restore (IMR), using the GUI. With this mailbox restore feature, we can perform individual mailbox and item-level recovery operations in Microsoft Exchange Server 2003 or Microsoft Exchange Server 2007 environments using Data Protection for Exchange backups.
239
15.1.1 Data Protection for Microsoft Exchange V6.1 on Windows for x86
Data Protection for Microsoft Exchange on Windows for x86 requires the following hardware and software. Intel Pentium 166, or later processor (or equivalent) with at least 20 MB of available disk space and 96 MB of RAM. One of the following operating system options is required. Windows Server 2003 with SP2, or later: Standard, Enterprise, or Data Center editions Windows Server 2003 R2 with SP2, or later: Standard, Enterprise, or Data Center editions Windows Server 2008 Standard, Enterprise, or Data Center without Hyper-V editions Note: Microsoft Cluster Server (MSCS) and Veritas Cluster Server (VCS) are supported. Refer to the User's Guide for details on MSCS and VCS configuration. Running in a Microsoft Virtual Server 2005 R2 SP1 or later x86 guest is supported.
15.1.3 Data Protection for Microsoft Exchange V6.1 on Windows for x64
Data Protection for Microsoft Exchange on Windows for x64 requires the following hardware and software. Intel EMT64, or AMD Opteron, or equivalent x64 processor with at least 20 MB of available disk space and 96 MB of RAM. One of the following operating system options:
240
Windows Server 2003 with SP2 or later: Standard x64, Enterprise x64, or Data Center x64 editions. Windows Server 2008 Standard x64, Enterprise x64, or Data Center x64, without Hyper-V editions Microsoft Exchange Server 2007: Standard or Enterprise Editions. Tivoli Storage Manager server Version 5.5.0 or later. Tivoli Storage Manager API Version 5.5.1 or later. Tivoli Storage Manager API Version 5.5.1 is included and automatically installed with Data Protection for Exchange 6.1. An IBM Tivoli Storage Manager backup-archive client V5.5.1, or later, if IBM Tivoli Storage Manager central scheduling is used. An IBM Tivoli Storage Manager backup-archive client V5.5.1, or later, if VSS operations are used. Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 version 6.5.8067.0, or later, if mailbox restore operations are used. Note: Microsoft Cluster Server (MSCS) and Veritas Cluster Server (VCS) are supported. Refer to the User's Guide for details on MSCS and VCS configuration.
241
Database Copy Backup (Legacy only) A database copy backup backs up only the specified database as well as its associated transaction logs.
Can recover deleted or relocated users Can run recovery from original server or alternate server Maintains mailbox history (which backups contain which mailboxes) Active Directory-based security Supports multiple restore destinations Original location Alternate mailbox and folder Outlook data (.PST) file Restores multiple object types Messages Calendar entries Contacts Notes, tasks User folders
242
Multiple mailboxes Single mailbox Multiple messages or contacts Individual message or contact Subject Sender Message date/time Attachments Other text, such as message body or folder name
Chapter 15. IBM Tivoli Storage Manager Data Protection for Mail - Exchange 6.1
243
CDOExm Exchange Management Shell Single user interface for: Storage group, database, mailbox or message restore Legacy or VSS restores Full, differential, incremental, and copy restores Supports existing backup procedures no changes required Does not require separate, costly brick backups Mailboxes can be restored from backups made with previous versions of Tivoli Storage Manager for Mail Full Tivoli Storage Manager integration Full automation and handling of Exchange recovery Simple command-line interface tdpexcc restoremailbox <mailbox> Simple GUI - GUI panel allows for easy user selection Globalization and localization Can recover deleted or relocated users Can run recovery from original server or alternate server Maintains mailbox history (which backups contain which mailboxes) Active Directory-based security Supports multiple restore destinations Original location Alternate mailbox and folder Outlook data (.PST) file Restores multiple object types Messages Calendar entries Contacts Notes, tasks User folders User-selectable restore granularity Multiple mailboxes Single mailbox Multiple messages or contacts Individual message or contact Advanced filtering capability based on: Subject Sender Message date/time Attachments
244
The next window you are presented is the Restore Progress as shown in Figure 15-2 on page 246.
Chapter 15. IBM Tivoli Storage Manager Data Protection for Mail - Exchange 6.1
245
246
Use the command-line interface when you must use the mailboxoriglocation optional parameter to specify the server, the storage group, and the database where the mailbox was located at the time of backup. Additional command line parameters required for this recovery are; server-name The name of the Exchange Server where the mailbox resided at the time of backup sg-name The name of the storage group where the mailbox resided at the time of backup dbname The name of the database where the mailbox resided at the time of backup
Chapter 15. IBM Tivoli Storage Manager Data Protection for Mail - Exchange 6.1
247
248
7718p03n.fm
Part 6
Part
249
7718p03n.fm
250
7718Planning.fm
16
Chapter 16.
251
7718Planning.fm
16.1 Overview
We will discuss what is delivered this release of Tivoli Storage Manager, as well as what is not included. We will further go through the steps in preparation, those things that you need to think about when to do the upgrade. The intent here to give you an understanding of what the requirements are, to put into perspective the resources, time, and effort that are required to install or upgrade to Tivoli Storage Manager V6.1 using the DB2 database. We will begin our discussion about strategy and what the upgrade is, in terms of resources time and effort to get there. The basic things to consider is the upgrade process itself, it is a resource intensive process, and there are a number of considerations in planning for the upgrade. In certain ways this upgrade process is similar to previous upgrades, but because of the time and resources required it can become complicated and planning is really the solution.
16.2.1 What you can and can not do with Tivoli Storage Manager V6.1
The following list are examples of what can and cannot be done in Tivoli Storage Manager V6.1. This list is subject to change and we suggest you go to the Tivoli Storage Manager Wiki for the latest updates: http://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Home
You can
You can run multiple Tivoli Storage Manager database instances on the same operating systems image
252
7718Planning.fm
You can forget about having to do database audits and off-line reorganizations. The reorganizations will happen when DB2 has less activity and when there is a need for it. You will see messages in the activity log when that will happen. The database and log volumes must be on a file system, you cannot use Raw Logical Volumes for the database and Log volumes from a disaster recovery perspective where it takes less time to create Raw Logical Volumes and bring up the system faster. The upgrade utility will read the database or logs if they are on Raw Logical Volumes. You can still use Raw Logical Volumes for storage pool volumes If you have multiple instances on the same operation system, you can run multiple Tivoli Storage Manager database upgrades at the same time, given you have enough resources. When you upgrade one of the instances to V6.1 you need to upgrade all instances before you can start the other instances. We can use Tivoli Storage Manager export/import to go from V5.x to V6 to do the upgrade instead of using Tivoli Storage Manager database upgrade utilities
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
253
7718Planning.fm
If you have a shared library configuration you must upgrade the server that is the library manager first and follow this by upgrading the library clients. Library clients must be at least level 5.4 or higher for compatibility with V6.1 Tivoli Storage Manager Server.
16.3 Preparation
To prepare for the installation or upgrade, you must first review a few sections and consider developing a structured plan for this activity. The sub-sections immediately following provide platform specific links for both installation and upgrade, and a few other useful components you must review prior to starting your tasks.
Installation platforms
AIX
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/r_srv_aix_sysreq_inst.html
HP-UX
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/r_srv_hp_sysreq_inst.html
Linux
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/r_srv_lnx_sysreq_inst.html 254
Tivoli Storage Manager V6.1 Technical Guide
7718Planning.fm
Solaris
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/r_srv_sun_sysreq_inst.html
Windows
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/r_srv_wnt_sysreq_inst.html
Upgrade platforms
Hardware and software requirements for V5 servers
The system requirements for the upgrade utility are the same as the system requirements for a V5.5 server, because the upgrade utility is based on the V5.5 server code. For additional information refer to the following Web sites to compare the system on which your Tivoli Storage Manager V5.3 or V5.4 server is running with the requirements for a V5.5 server. http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/r_srv_upgrd_v5srv_reqmts.html
AIX
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/r_srv_upgrd_aix_sysreq.html
HP-UX
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/r_srv_upgrd_hp_sysreq.html
Linux
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/r_srv_upgrd_lnx_sysreq.html
Solaris
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/r_srv_upgrd_sun_sysreq.html
Windows
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/r_srv_upgrd_win_sysreq.html
255
7718Planning.fm
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/r_rpt_inst_hwswreqs.html
Tivoli Storage Manager Version 6.1 Tivoli Storage Manager Version 5.5 Tivoli Storage Manager Version 5.4
Note: V5.4 clients do not include the special 5.3.6-level clients (Window 2000, Solaris 8, and Linux
x86 RHEL 3.
7718Planning.fm
across as many physical devices or logical unit numbers (LUNs) as there are directories. With Tivoli Storage Manager V6.1, we recommend for a production server to use at least four database directories (disks), where number reflects the database size, however this can grow up to 128 database directories for the DB2 database as required. You can add DB2 directories with the new EXTEND DBSPACE command to an existing installation and this requires a restart of the server for the change to become active. An important item to mention is when we add a new database directory, after the initial load it will cause a REORG, which needs to be avoided if possible. A REORG is expensive and disruptive. One method that will not cause a REORG is to extend the existing filesystems in UNIX or disks in Windows if there is need for database space. Adding the physical disk, then extending the file systems (and subsequently the directories holding the DB2 databases) will not cause the REORG to occur. To review the V6.1 product capacity planning information, and access product planning sheets, go to the following URL; http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.install .doc/t_srv_plan_capacity.html
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
257
7718Planning.fm
once the ACTIVE log is full. If the ARCHIVE log directory is full, ACTIVE log files cannot be copied over to the ARCHIVE log directory. If the ACTIVE log files cannot be copied they cannot be deleted, which leads to an out-of-log space in the ACTIVE log and no new ACTIVE logs can be created. Transactions can still be active when they are archived but the active log file cannot be deleted until ALL transactions within the log file are either committed or aborted. This also applies to transactions which flow through an active log file.
258
7718Planning.fm
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
259
7718Planning.fm
To maintain database integrity, ensure that the storage hardware can withstand failures such as power outages and controller failure. You can improve database performance by using hardware that provides a fast, nonvolatile write cache for both the database and logs. If there is an error writing to either primary or log mirror, the failing path to the log is marked as bad and a message written to log. The writes continue to remaining good log volume until the current log volume is filled. When DB2 needs to open the next log file, then the path is retested and reused if it is ok. If an error occurs in the remaining good path, Tivoli Storage Manager will halt. Ultimately, with the cost of disk storage continuing to drop, do not hesitate to over configure your database and log structure. The investment will pay dividends over an under configured environment. Balancing your IO is a critical area, especially for heavily loaded servers.
260
7718Planning.fm
In Tivoli Storage Manager V6.1 there is a significant increase in real memory utilization. The recommended memory size is approximately four times the current recommended values, for instance, in the past this has been 2 gigabytes per instance on AIX, and now our recommendation is 8 gigabytes per instance. This is not a minimum, nor is it a requirement, it is simply our recommendation for a normal workload, Another change to keep in mind is growth in the database itself. Not only will the overall size of the database increase, but also DB2 may use additional disk space for temporary work based on your workload. There are two places that we have seen significant growth in the database, one is during the insertion of database entries during the upgrade process and the other during the execution of certain queries. The database recovery log space requirement also increases for this upgrade. DB2 is managing this log space and you will need space for both an active log and for archive logs. The DB2 database is in what in V5 we would refer to as roll-forward mode, there is no support for circular logging. We will briefly describe the upgrade process here and we will go into it in more detail later in this material. Simply stated the upgrade process prepares the existing V5 database, extracts its contents, then inserts that extracted data into a newly created DB2 database. Compared to previous release-to-release upgrades, this is a time consuming process. It is the time that this process takes that is one of the major reasons to carefully plan your upgrade strategy. The fall-back plan is basically the same as it has been in the past, but perhaps a little more complex because of the addition of the DB2 installation. You will need to reinstall your previous release of Tivoli Storage Manager and restore its database. There are no changes to your existing storage pools, so the normal precautions for protecting previously backed data are sufficient, such as disabling migration and reclamation
Database creation
Estimate the extract and insert processes between 5GB/hr and 10GB/hr. This rate is currently what has been experienced for the upgrade process, however that assumes a normal Tivoli Storage Manager workload. It also assumes a pristine Tivoli Storage Manager database. The number of objects has an impact on insert, however the extract is purely sequential block reads. This 5GB/hr to 10GB/hr rate is based on the amount of space that is actually used by the V5 database, not the allocated space. Your environment might produce different results. Testing upgrade operations in your environment is especially important for Tivoli Storage Manager servers that support essential systems.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
261
7718Planning.fm
Workload type
The type of workload that the server has handled. A workload that consists of large numbers of small files, or files with very long file names, can cause a relatively longer upgrade time. An example of an abnormal configuration might be a Content Manager or many large file servers, which tend to manage more objects per GB, so they may be considerably slower when using GB/hr estimate. Estimate the upgrade time to help plan for the amount of time that the server will be unavailable. The time that is required to complete the upgrade depends on multiple factors. The Tivoli Storage Manager V5 server is not available for use while data is being extracted from the database. The network method for the data movement overlaps the extraction time with the insertion time. Using the network method might help reduce the total time required for the upgrade because of the overlap. Note: If theTivoli Storage Manager server is V5.5.x or higher, the existing Tivoli Storage Manager server can restart, and if prior to V5.5.x, the DB must be restored if you need to restart the Tivoli Storage Manager server after running the upgrade utility.
262
7718Planning.fm
Media method
You need media to store the data that will be extracted from the Tivoli Storage Manager V5 database. The media can be tape, or disk space that is defined as a sequential-access disk device class. The space required for the extracted data is the same as the used space in your database. If your database is safely backed up, and you are certain that you no longer need to run the Tivoli Storage Manager V5 server, after you extract the data you can optionally release the space used by the Tivoli Storage Manager V5 database and recovery log.
Network method
You must have the working copy of the Tivoli Storage Manager V5 database and recovery log on the Tivoli Storage Manager V5 system. If you are working with a copy of the database that was created for testing the upgrade process, you need enough space to hold the total allocated size of the database; you can use the minimum size for a V5 recovery log.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
263
7718Planning.fm
Future growth
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. For more information about estimating database space requirements, see the Administrators Guide for your specific platform listed in the Other publications on page 633. Restriction: 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. Visit the support site for the latest information and recommendations. http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
7718Planning.fm
After the server is upgraded, monitor the active log and archive log directories to ensure that these directories have enough free space to handle the actual server workload. For more information about estimating recovery log space requirements, see the Administrators Guide for your specific platform listed in the Other publications on page 633.
Active log
The default, minimum size of 2 GB is large enough to complete the upgrade process. The maximum size of the active log is 128 GB. When you begin normal operations with the server after the upgrade, you might need to increase the size of the active log. The required size depends on the amount of concurrent activity that the server handles. A large number of concurrent client sessions might require a larger active log. For simple backup and archive activity with no data deduplication, 26 GB for the active log is more than adequate. If you use data deduplication, and if you de duplicate very large objects (for example, image backups), use an active log size that is 20% of the database size.
Archive log
The size required depends on the number of objects stored by client nodes over the period of time between full backups of the database. Remember that a full backup of the database causes obsolete archive log files to be pruned, to recover space. The archive log files that are included in a backup are automatically pruned after two more full database backups have been completed. If you perform a full backup of the database every day, the archive log must be large enough to hold the log files for client activity that occurs over two days. Typically 600 - 4000 bytes of log space are used when an object is stored in the server. Therefore you can estimate a starting size for the archive log using the following calculation: objects stored per day x 3000 bytes per object x 2 days For example: 5 000 000 objects/day x 3000 bytes/object x 2 days = 30 000 000 000 bytes, or 30 GB
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
265
7718Planning.fm
For the latest information and recommendations, go to the support site: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
Table 16-3 contains tips for estimating space requirements. Select the scenario then read down the column.
266
7718Planning.fm
Table 16-3 Tips for estimating space requirements Items that require space Type of space Scenario 1 Scenario 2 Scenario 3 Scenario 4
Same system as V5 server Network method Space that is allocated for the V5 database
0
Sequential media
Space that is used by the V5 database (based on% utilization) Space that is used by the V5 database (based on% utilization) V5 recovery log Disk The amount of space that is allocated for the V5 recovery log Disk Space that is used by the V5 database plus 33 - 50% more
Same as estimated database size
Space that is used by the V5 database (based on% utilization) Space that is used by the V5 database (based on% utilization)
0
Sequential media
V5 recovery log
Disk
V5 recovery log Disk The amount of space that is allocated for the V5 recovery log Disk Space that is used by the V5 database plus 33 - 50% more
Same as estimated database size
Disk
2 GB during the upgrade process. A higher value might be needed for normal use
If used, same size as active log
2 GB during the upgrade process. A higher value might be needed for normal use
If used, same size as active log
2 GB during the upgrade process. A higher value might be needed for normal use
If used, same size as active log
2 GB during the upgrade process. A higher value might be needed for normal use
If used, same size as active log
Disk
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
267
7718Planning.fm
Type of space
Scenario 1
Scenario 2
Scenario 3
Scenario 4
Same system as V5 server Network method Estimate based on client activity and database backup frequency
Table 16-4 shows a sample filled-in work sheet for a 100 GB, V5 database that has 80% space utilization, with the assumption that the database increases by 33 - 50% when upgraded.
Table 16-4 Sample space estimates for a 100 GB V5.5 database Items that require space Type of space Scenario 1 Scenario 2 Scenario 3 Scenario 4
Sequential media
80 GB
80 GB
80 GB
80 GB
80 GB
80 GB
8 GB (8 GB)
8 GB (8 GB)
8 GB (8 GB)
8 GB (8 GB)
268
7718Planning.fm
Type of space
Scenario 1
Scenario 2
Scenario 3
Scenario 4
V6.1 archive log directory Total disk space required during the upgrade process Total sequential media required during the upgrade process Total disk space for the V6.1 server after upgrade and cleanup
Disk
16.5.4 Work sheet for planning space for the V6.1 server
You can use the work sheet to help you plan the amount and location of storage needed for the V6.1 server.
Table 16-5 Work sheet for space planning 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)
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
269
7718Planning.fm
Instance user ID
The instance user ID is used as the basis for other names related to the server instance. The instance user ID is also called the instance owner.
270
7718Planning.fm
For example: tsminst1 The instance user ID is the user ID that must have ownership or read/write access authority to all directories that you create for the database, the recovery log, and storage pools that are FILE device type.
Database name
The database name is always TSMDB1, for every server instance. This name cannot be changed.
Server name
The server name is an internal name for Tivoli Storage Manager, and is used for operations that involve communication among multiple Tivoli Storage Manager servers. Examples include server-to-server communication and library sharing. The server name is also used when you add the server to the Administration Center so that it can be managed using that interface. Use a unique name for each server. For easy identification in the Administration Center (or from a QUERY SERVER command), use a name that reflects the location or purpose of the server. For example: tsminst1 If you use the instance configuration wizard, the default name that is suggested is the host name of the system that you are using. You can use a different name that is meaningful in your environment. If you have more than one server on the system and you use the instance configuration wizard, you can use the default name for only one of the servers. You must enter a unique name for each server. For example: Liam_SERVER1 Leon_SERVER2
271
7718Planning.fm
j:\tsminst1\actlogm - activelogmirror directories k:\tsminst1\archlog - archivelog directories l:\tsminst1\archlogf - archivefailover log directories
16.7 Performance
For best performance, use multiple LUNs that map to multiple independent disks, or that map to RAID arrays with a large stripe size (for example, 128 KB). Use a different file system on each LUN. Table 16-6 on page 272 shows an example of LUN usage.
Table 16-6 Use of separate disks for database and logs.
# of LUN
4-128 1 1 1 1
Usage
Database
If the disk storage is supplied by a virtualization device (high-end storage controller, or a SAN virtualization device), ensure that none of the virtual LUNs are on the same physical disk drive. Ensure that the directories in use are on different physical disk drives within the virtualization device.
System hardware
Additional resources (disk space, memory, and possibly processor capacity) are required on the existing system.
A new system that meets requirements, in addition to the existing system, is required. You must upgrade to a new system if the existing server is on one of the platforms that are not supported for V6.1.
272
7718Planning.fm
Item
Software
Software on the system must meet requirements for V6.1. The V6.1 server cannot coexist with other versions on the same system.
Software on the new system must meet requirements for V6.1. Software on the original V5 system must meet requirements for the upgrade utilities (upgrade utilities requirements are the same as for a V5.5 server). You can stage the upgrade of multiple servers, because the V5 server program can be left on the original system. A V5.5 server on the original system can be restarted after the database extract completes. A V5.3 or V5.4 server on the original system can be restarted, but its database must be restored first (using the database backup that was made before the upgrade process).
V5 server availability
All V5 server instances on the system are unavailable after the V6.1 server program is installed. Data managed by a server instance cannot be accessed until the upgrade process is complete for that server instance. To revert to using the V5 server, you must reinstall the same level of the V5 server program as before, and restore the V5 database from a backup that was made before the upgrade process.
The database can be moved with a local-host network connection, or can be moved by using disk or external media.
You must have either a network connection between the existing and the new systems, or a device and media available to store the extracted database.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
273
7718Planning.fm
Item
Existing attached devices can be used. You must change ownership or permissions for all disk space that is used for storage pools (device types of FILE or DISK). The user ID that you will create to be the owner of the upgraded server instance must be given ownership or read/write permission to the disk space for storage pools.
The new system must have access to all storage that is used by the original system. Definitions for devices such as FILE device types might need to be changed after the upgrade. You must change ownership or permissions for all disk space that is used for storage pools (device types of FILE or DISK). The user ID that you will create to be the owner of the upgraded server instance must be given ownership or read/write permission to the disk space for storage pools.
The network address on clients and storage agents must be updated after the upgrade, or network changes made so that the new system has the same address as the original system.
Media method
You can extract data from the original database to media, and later load the data into the new database. The new database can be located either on the same system or a different system.
274
7718Planning.fm
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
275
7718Planning.fm
Figure 16-3 Export and import used for a staged Tivoli Storage Manager V5 to V6 node migration.
Network method
The network method reduces the amount of storage that is required because there are no requirements for disk or tapes to hold the data unloaded from the Tivoli Storage Manager V5 database. With either method, the original server cannot be running in production mode while the data is being extracted.
276
7718Planning.fm
277
7718Planning.fm
server using the export/import functionality. This can be accomplished using the network as shown in Figure 16-6 on page 278.
Figure 16-6 Export and importing using server to server communication for a staged migration.
278
7718Planning.fm
utilities are run on the original database, and this utility upgrades a server database version to V5.5, and performs some cleanup to prepare for the extraction process. The DSMUPGRD utility has the same code as the V5.5.2 server. The difference is its function is limited to upgrade related tasks as such, it cannot be used to run normal server. However, it is the same code as the server, and the decision to function as upgrade utility or server is based on the name. DSMUPGRD* will operate as the upgrade. The following major upgrade tasks are discussed in further detai in this chapter. PREPAREDB EXTRACTDB QUERYDB Emergency LOG and DB extension UPDATE (for Windows Registry maintenance) Available on all platforms supported by V5.5 (but not V5.3 or V5.4) It uses different install locations and package names than V5 or V6.1 server
PREPAREDB
The PREPAREDB command prepares a V5.x database for upgrade to V6.1, and is the required second step in upgrade process, (the first step is to back up database in case you need to roll back the database the utility upgrade for example the V5.4 database to V5.5.2 This will upgrade the database version to V5.5 as an dsmserv upgradedb. This checks for some known database problems like moving from asterisk to ASCI - USS filespace conversion status. The tool stops if it detects any USS filespaces that are not converted. Currently it does not run any database repair utilities but that may change. When the database problem check is finished it backs up device configuration information to configured devconfig files and backs up the server instances registry entries on Windows. Note: Tivoli Storage Manager V6.1 does not support presence of NAS Backups with TOCs and presence of Backup Sets. This will be fixed in V6.1.2
EXTRACTDB overview
The EXTRACTDB command extracts data from the V5.5 database, using a sequential block reads, and is the base of V5 piece of the upgrade utility, by extracting out the V5 database objects, for further use by the insertdb tool. You can use the utility to either simultaneously extract and insert the data into a new database over a network, or extract the data to media for later insertion into a new database. The data extraction operation can be run with multiple processes.
EXTRACTDB (media)
The EXTRACTDB command extracts data from the V5.5 database and writes extracted data to sequential media.
Required parms
DEVclass=device class name (must be an already defined deviceclass) MANifest=filename (we record here information needed parameters as deviceclass name and list the volumes we wrote to
Optional parms
VOLumenames=volume list
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
279
7718Planning.fm
SCRatch=Yes|No Saves volume list, devclass name in manifest file, and uses devclass definition from database, not devconfig file
EXTRACTDB (network)
Sends extracted data over network session, which uses server-to-server communications and treats target server as a V6.1 version of itself. This utility is specific to V6.1 upgrade, and skips tables which are not pertinent for V6.1 upgrade due to some redundant tables in the V5 database. This utility also manipulates data to ease inserts into the V6.1 database and thus positioning the data for the insertion process. This command requires minimal authorization with hard coded source and arget server names. $UPGRADESOURCE$, $UPGRADETARGET$ Server name/password is not required to be set
Required parms
HLAddress=ipaddress (may be localhost) LLAddress=portnumber Target must be listening at specified address & port
EXTRACTDB (general)
General parms
EVentbasedused=Yes|Never Was event based archive retention ever used? YES results in extraction of extra expiration info from db Never say NEVER if there is any doubt Has no effect on new V5.3.6, V5.4.2, V5.5.0 servers or if REPAIR EXPIRATION * TYPE=ARCHIVE EVENTBASEUSED=FIX FIX=YES was run Undocumented parms MAXStream=n (currently disabled, default=1) MAXPRocess=n (n from 1 to 20, default=4
EXTEND DB I LOG
Emergency database and log extension, which behaves the same as DSMSERV EXTEND DB/LOG in V5.5 server code. This is used when PREPAREDB database upgrade runs out of database or log and will extend database or log even if database version is lower than V5.5.
UPDATE
Recreates backup copies of registry entries and is required if upgrading to same system and V6 instance directories are different than V5 instance directories, and the V6 LOADFORMAT run before PREPAREDB. This utility is run from the V5.x instance directory.
Syntax
DSMUPGRD [-k key_name] UPDATE
280
7718Planning.fm
LOADFORMAT
Formats a new Tivoli Storage Manager V6.1 database for upgrades use, and uses the identical syntax and usage as DSMSERV FORMAT. This utility creates database and logs, defines tables, and does not insert any default values into the V6.1 database.
INSERTDB
This utility reads data from media or from network session, and inserts this data into a V6.1 database, and has an explicit knowledge of Tivoli Storage Manager V5.5 database schema. The utility maps data from V5.5 schema to V6.1 schema, while validating the data before inserting it into database. In some situations, the insertdb will correct data before inserting it and logs invalid rows that cannot be corrected.
INSERTDB (media)
This utility reads extracted data from sequential media. This utility will read a volume list, devclass name from a manifest, and uses devclass definition from devconfig file. This utility requires a DEVCONFIG option to be specified in dsmserv.opt and requires a copy of devconfig file from source server.
Required parms
MANifest=filename
Optional parms
DEVclass=device class name
INSERTDB (network)
This utility reads extracted data from the network session, which is sequential in nature. This will also initializes the server and then waits for a connection.
Required parms
None
Optional parms
SESSWait=n (#minutes to wait, default=60) ANR1336I INSERTDB: Ready for connections from the source server
INSERTDB (general)
This utility validates database schema before inserting data into db. Performs all INSERTDB actions except insert into DB. This utility runs almost as fast as EXTRACTDB can provide data, and checks data for errors, and will provides insight into amount of data transferred. The new parameter is targeted for V6.1.2.
Other parms
PREVIEW=Yes|No
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
281
7718Planning.fm
Note: DSMSERV INSERTDB repeatedly issues status message ANR1525I with no sign that any progress is being made. For example: ANR1524I INSERTDB: Beginning database update phase. ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 0:23:10. ANR1525I INSERTDB: Updated 0 of 25,185,883 database entries in 0:53:13. In the database update phase, DSMSERV INSERTDB merges information from two source tables into a single target table. The merge is performed as a single, long running DB2 UPDATE operation. The UPDATE operation does not provide status until it completes, which is why the ANR1525I message repeatedly shows 0 entries updated for such an extended period of time. INSERTDB merges multiple sets of tables during the database update phase. After each set of tables is merged, the ANR1525I message will change to reflect the progress up to that point. However, each set of tables can take a considerable amount of time to merge, during which the status will remain the same. This should not be a cause for alarm; rather an indication that INSERTDB is still alive and continuing to function. Once INSERTDB enters the database update phase, most of the remaining work will be done by DB2. Unfortunately, only indirect methods are available to tell if it is making progress. One such method is to use a system monitor such as topas on AIX to confirm that the DB2 db2sysc process is operating. Consuming CPU cycles and performing I/O to the database volumes are both good indications that the update phase is progressing.
Scenario 1 - for upgrading the server: new system, media method Scenario 2 - for upgrading the server: new system, network method Scenario 3 - for upgrading the server: same system, media method Scenario 4 - for upgrading the server: same system, network method
New system
Network method
282
7718Planning.fm
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
283
7718Planning.fm
The following steps are a summary of the procedure for this scenario. 1. Perform all preparation tasks on the original system. Preparation includes performing a database backup. 2. Install the DSMUPGRD utilities package on the original system. The utilities package must be installed whether you are using the upgrade wizard or performing the upgrade manually with utilities. 3. Install the Tivoli Storage Manager V6.1 server code on the new system. 4. Create the directories for the Tivoli Storage Manager V6.1 database and logs, and the user ID that will own the server instance. 5. Start the upgrade wizard to configure the new server and upgrade the Tivoli Storage Manager V5 database. With the wizard, you complete the following tasks: a. On the original system, prepare the V5 database. b. On the original system, extract the V5 database to external media. c. On the new system, create and format an empty database to receive the data. d. On the new system, insert the data from the media to which it was extracted. e. Configure the new system for database backup. 6. Complete the post-installation tasks, including backing up the database and verifying the database contents.
284
7718Planning.fm
Figure 16-8 Upgrade to V6.1 on a new system using the network wizard method
16.9.6 The following steps are a summary of the wizard method scenario
Figure 16-9 shows a high overview on a Tivoli Storage Manager V6.1 upgrade on a same system using the media method wizard.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
285
7718Planning.fm
Figure 16-9 Upgrade to 6.1 on a same system using the media wizard method.
1. Perform all preparation tasks, which includes performing a database backup. 2. Install the upgrade utilities package (DSMUPGRD) on the system. The utilities package must be installed whether you are using the upgrade wizard or performing the upgrade with utilities. 3. Prepare the Tivoli Storage Manager V5 database using the DSMUPGRD PREPAREDB utility.
286
7718Planning.fm
4. Uninstall the Tivoli Storage Manager V5 server code. 5. Install the Tivoli Storage Manager V6.1 server code on the system. 6. Create the directories for the Tivoli Storage Manager V6.1 database and logs, and the user ID that will own the server instance. 7. Start the upgrade wizard to configure the new server and upgrade the Tivoli Storage Manager V5 database. With the wizard, you complete the following tasks: a. Extract the V5 database to external media. b. Create and format an empty database to receive the data. c. Insert the data from the media to which it was extracted. d. Configure the system for database backup. 8. Complete the post-installation tasks, including backing up the database and verifying the database contents.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
287
7718Planning.fm
The following steps are a summary of the procedure for this scenario. 1. Perform all preparation tasks, which includes performing a database backup.
288
7718Planning.fm
2. Install the upgrade utilities package (DSMUPGRD) on the system. The utilities package must be installed whether you are using the upgrade wizard or performing the upgrade with utilities. 3. Prepare the Tivoli Storage Manager V5 database using the DSMUPGRD PREPAREDB utility. 4. Uninstall the Tivoli Storage Manager V5 server code. 5. Install the Tivoli Storage Manager V6.1 server code on the system. 6. Create the directories for the Tivoli Storage Manager V6.1 database and logs, and the user ID that will own the server instance. 7. Start the upgrade wizard to configure the new server and upgrade the Tivoli Storage Manager V5 database. With the wizard, you complete the following tasks: a. Create and format an empty database to receive the data. b. Move the data from the Tivoli Storage Manager V5 database to the Tivoli Storage Manager V6.1 database. c. Configure the system for database backup. 8. Complete the post-installation tasks, including backing up the database and verifying the database contents.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
289
7718Planning.fm
Administrators must also review and be familiar with the upgrade processes and methodologies as documented by the Tivoli Storage Manager V6 publications. Administrators must be knowledgeable of the server EXPORT and IMPORT functions including timing implications, and how EXPORT may be affected by data being backed up or archived while the export operation is being performed.
290
7718Planning.fm
For purposes of this testing, the storage devices (hierarchy) are not needed. However, differences in hardware (processor, I/O performance to disk, and so on) might affect the time measured for the upgrade process in the test environment. Use the same or equivalent hardware to achieve results that most accurately represent what can be achieved for your production Tivoli Storage Manager server upgrade.
Restrictions
To employ the hybrid upgrade-migration method, your operational situation for particular Tivoli Storage Manager server instances must accommodate the following restrictions. If you are unable to accommodate these restrictions, do not use this method because it can cause problems including possible loss of data. This method can only be used with the Upgrade Guide Scenarios 3 and 4, for example, upgrading the V5.x server to V6 on a new system using either the media or the network method.
Operational restrictions
The set of restrictions below are restrictions on, or changes to, the operation of your Tivoli Storage Manager server during the duration of the migration when using this method. Also, this set of restrictions will be referred to in subsequent sections. Disable data migration between storage pools to keep the object pointers in the V6 server database synchronized with the actual location of the objects. You can disable migration for all storage pools by using the undocumented server option NOMIGRRECL. Enable the NOMIGRRECL option by adding it to the server options file. The advantage of using NOMIGRRECL is that it turns off all migration and reclamation all at once as opposed to having to issue commands to disable migration and reclamation for the various storage pools. The disadvantage is that there is no documentation for additional information. If you want to use a documented method instead, disable migration by setting the migration threshold to 100% on all primary storage pools with the following command: update stgpool <stgpools-name> HIGHMIG=100 Disable reclamation for all storage pools using tape device classes and FILE type device class to prevent orphaned objects in the V6 server database. As with migration, you can disable reclamation by using the NOMIGRRECL server option. If you want to use a documented method instead, reclamation can be disabled with the command: update stgpool <stgpools-name> REClaim=100 Disable database expiration processing from the point in time that data is extracted from the V5.x server database until the V6 server is put into production. The reason for this restriction is that the V6 database, built from the insert process, still has references to client objects in storage pools of device class DISK. Expiration processing on the V5.x server after the extraction would allow the V5.x server to reuse the space on DISK storage pools. The V6 server would then have orphan objects in the database. If you use the EXPINTERVAL server option to automatically expire data, set the option to EXPINTERVAL 0. Alternatively, if you use scheduled administrative commands to expire data, disable or delete that schedule. If you use an external automation or scheduling tool to expire data, identify and stop that tool. Tip: Tivoli Storage Manager V6 has a number of changes and enhancements to the expiration process including new command parameters. Evaluate these new capabilities for use in the production V6 server environment after the upgrade is completed.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
291
7718Planning.fm
Do not move data between storage pools with the move data or move nodedata commands, either manually or automatically as part of scripts or administrative schedules. This restriction is necessary to prevent orphaned objects in the V6 server database. Either disable backup storage pool operations, or audit the volumes used for storage pool backups on the V6 server after it goes into production. Be aware that the storage-pool backup volumes created after the extractdb operation will not be usable after the V6 server is put into production. Suspend using active data pools, that were created with the COPY ACTIVEDATA command. Changes to active data pools during the interim period can cause the V6 server database to be out of synchronization with the actual storage pools. Do not make changes to policies or existing administrator ID definitions, or register any new administrator IDs on the V5.x server.
Variation 1
Follow the upgrade steps documented in Tivoli Storage Manager V6 Upgrade Guide, SC23-9554, "Scenario 3: Upgrading the server manually using utilities or Scenario 4 for upgrading the server: New system, network method - up to and including extracting the database, with the extractdb command. However, instead of stopping the Tivoli Storage Manager V5.x server operation after the database data is extracted, that server is put back into operation. Requirement: You must implement all the operational restrictions in Operational restrictions on page 291 before putting the V5.x server back into operation. Migration and reclamation must remain disabled on the V6 server. If you used the NOMIGRRECL option to disable migration and reclamation, set that option in the V6 server options file as well. In parallel with the continued operation of the V5.x server, the remaining steps of upgrading the server manually using utilities are performed. When the database backup is complete, the V6 server is almost ready to be put into operation. However, there may now be client data that was stored into the V5.x server while the insertdb process was completing on the V6 server. This new data must be migrated. This is accomplished by exporting the new client (that is: node) data. The data must be exported to a media that can be used on the V6 server. Example 16-1 is an example expoty node command.
292
7718Planning.fm
Note: If data shredding is in use with storage pools from which node data is to be exported, you will need to use the additional allowshreddable=yes parameter. The data exported from the V5.x server is imported into the V6 server using the import node command in Example 16-2.
Example 16-2 import node command
Variation 2
The basic improvement with Variations 2 and 3 over Variation 1 is to decrease the time for export and import during server cut over. In Variation 1, the production Tivoli Storage Manager server is down during the extractdb process. The server is also down during the server cut over, which occurs after the insertdb is completed. The cut over period includes time to: 1. Export all the new node data from the V5.x server. 2. Switch the attachment of the storage pool devices. 3. Import all the new node data to the V6 server. The length of time to export data from the V5.x server and import the data to the V6 server might be significant and undesirably long. This variation describes ways to decrease downtime resulting from export and import, but the overall downtime might not be better than variation 1. You must determine which variation is best for your environment. In this variation, you perform multiple exports and one import - that is, import of multiple exports in one operation - at time of cut over. These multiple exports are incremental node data exports. This way, during the cut over period, a smaller amount of node data must be exported, which will be the last remaining node data ingested since the last incremental export. 1. Generate the incremental exports at regular intervals, for example, 4 or 8 hours, using the EXPORT command fromdate and fromtime, and todate and totime parameters. The parameters must be carefully specified so that the export increments are contiguous and not overlapping. 2. When you are ready to put the V6 server into production, export the final node data. 3. Shut down the V5.x server. 4. Connect the storage devices (containing all the storage pools) to the V6 server, and start the V6 server. 5. Import all the incremental exports.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
293
7718Planning.fm
Variation 3
This final variation requires an excellent working knowledge of Tivoli Storage Manager and detailed planning. The amount of time to perform the import operation (done at the point of production cut-over to the V6 server) might be decreased further by having to import only the last incremental export. However, this means that the other incremental exports must be imported while the V5.x server is still in operation. Here is an example scenario: You have determined the INSERTDB phase of processing will take 20 hours. During that time, the V5.x server is left in production, and every 4 hours an EXPORT is performed. After the V6 server completes the INSERTDB processing, the V5.x server is still operational. During this time, the incremental exports taken from the V5.x server are imported on the V6 server. During this overlap period, client access to the V6 server must be disabled. Also, client schedules must be disabled on the V6 server when it is running, including when the import operations are performed. The reason is that you do not want the V6 server to start scheduled client operations in parallel with what is being done by the V5.x server, which is still in production. Once all but the most recent EXPORT from the V5.x server have been imported to the V6 server, stop the V5.x server and import the final node data export. In this way, the effective server down-time is the time needed to perform the FINAL incremental import on the V6 server. This approach requires: 1. Making all the original volumes of the destination storage pools unavailable. 2. Defining new volumes to the destination primary-storage pools on the V6 server (which is operational but not in production) on storage devices that must be available to the V6 server before the V5.x server storage devices are re-cabled to the V6 server. The data imported earlier goes to these new volumes. After the V6 server is put into production, the client data on these volumes can be moved to the original storage-pool volumes. When the data move is complete, those volumes can be deleted. If you choose to take this approach, disable normal server operations and availability on the V6 server when it is started. Taking these steps minimizes operational difficulties and error messages when you use the V6 server before it is put into production, when performing the early imports. The disabling of normal server operations can be done immediately after starting the V6 server. However, it is easier and decreases risk of unwanted activities if you disable the server operations before the V6 server is started. This can be accomplished by disabling the functions on the V5.x server before the database extraction is performed. As indicated in Operational restrictions on page 291, some of these operations should remain disabled on the V5.x server even after the extractdb operation is performed. Table 16-9 on page 295 gives a list of the server operations to consider disabling, and the commands or options to accomplish that.
294
7718Planning.fm
Table 16-9 Server operations to consider disabling Server operation Command or option to disable the operation Retain disablement on V5.x server Yes
Database expiration Storage pool reclamation (set for all storage pools)
Server option: expinterval=0 Storage pool parameter: reclaim=100 (Not required if the NOMIGRRECL option is used.) Storage pool parameter: highmig=100 (Not required if the NOMIGRRECL option is used.)
Yes
Yes
Storage pool volume accessibility (make the old volume unavailable on the V6 server) Client access to the V6 server (disable on the V6 server) Client and administrative schedules on the V6 server (disable on the V6 server)
No
No
No
16.10 Testing
Tivoli Storage Manager V6.1 has many new features, which have contributed to the need for additional planning and testing, some of the most significant feature changes include: De-duplication Disk structure for DB2, active logs and archive logs, storage pool volumes Disaster recovery using the Disaster Recovery Manager feature Reporting and monitoring The are many additional changes to Tivoli Storage Manager V6.1, as shown in Chapter 4, Command, utilities and option changes on page 31. In addition, there are many methods of upgrading and moving data during the upgrade, thus understanding all your options and the cost of each is important (monetary and downtime costs may vary based on each scenario).
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
295
7718Planning.fm
such as DRM, reporting and monitoring have been tested and documented prior to the production implementation. The original V5.x server and the new V6.1 server cannot co-exist on a system at the same time. To evaluate and test the V6.1 server, you must install Tivoli Storage Manager V6.1 on a new system. To test with a copy of production data, or to test the upgrade process, you can use the upgrade utilities to create a test server. Follow the normal upgrade procedure, with these additional considerations: To avoid affecting your original production server, you must install the V6.1 server on a different system. Different versions of the server cannot be run on a system at the same time. In addition, you will need to provide a scaled down copy of your V5.x server in the test scenario. Ensure that the storage devices for your production server are not available to the test server. If the test server can detect the devices that your production server uses, it might start operations such as issuing resets on tape drives or unloading tapes. If you prefer not to add the second test server, then you must upgrade your current production server to at least V5.5.2. Then the DSMUPGRD utility can complete the upgrade to your test V6.1 server, and leave your production server untouched. Always backup your Tivoli Storage Manager database prior to any upgrade activity. If you do not want to upgrade your production server, nor add a test V5 server, then consider using extractdb of the production database to the test server using either media or the network. The advantage of extracting the database to media is that you can repeatedly load the test database without stopping your production server each time. For example, if your tape drives are connected in a storage area network (SAN), you might need to change the zones in your SAN to prevent the test server from detecting the devices. For testing, you can use one of the following methods to use a backup copy of the database. The methods are given in outline form. See the detailed procedures for instructions for each step.
296
7718Planning.fm
Refer to the Tivoli Storage Manager Planning Guide, Chapter 4, Scenario 1: Same system, media method, located at the following URL: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/t_srv_upgrd_s1_ssmm.html Tivoli Storage Manager Planning Guide, Chapter 5, Scenario 2: Same system, network method located at the following URL: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.d oc/t_srv_upgrd_s2_ssnm.html
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
297
7718Planning.fm
Understand how database and recovery log space is used, and how monitoring needs to change. Check scripts and administrative schedules. The V6.1 server adds new commands, changes some commands, and deletes some commands that are no longer needed. These changes will affect your automated operations. For more information on the new commands and utilities go to Chapter 4, Command, utilities and option changes on page 31. Check SELECT commands that you use regularly. Some parameters and syntax that were previously allowed are not accepted by the database manager program. If you use products from independent software vendors to interface with the server, ensure that the products are compatible with the V6.1 server.
298
7718Planning.fm
Figure 16-11 Files to alter for in the console folder, for the Operational Reporting tool adjustment
These xml templates will be referenced after you have defined theTivoli Storage Manager V6.1 server computer to the ORF. Then create the Daily Report and Hourly Monitor, click on the properties of the Daily Report and Hourly Monitor and as opposed to the default xml templates, select the ones below (copy them first to the console directory). When attempting to add and configure a new Tivoli Storage Manager V6.1 instance, using operational reporting V5.5.2.1, you may receive some of the errors shown in Figure 16-12 on page 299.
Figure 16-12 Operational Reporting errors when referencing a Tivoli Storage Manager V6.1 instance
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
299
7718Planning.fm
300
7718Planning.fm
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
301
7718Planning.fm
7718Planning.fm
If you typically use a DELETE VOLHISTORY command to delete database backups, ensure that the command does not delete database backups for at least the same number of days that you set for the REUSEDELAY period for sequential-access storage pools. For important clients that use the server, check that the value for the schedlogretention client option is set to retain the client schedule log for a long enough time. Update the option for clients if needed. The entries in the client schedule log might be useful if the server must revert to the original version. If the retention period for the schedule log is too short, the schedule log information might be deleted too soon. In preparation for the upgrade, prevent activity on the server by disabling new sessions. Cancel any existing sessions. The commands in the following procedure are Tivoli Storage Manager administrative commands. To prevent all clients, storage agents, and other servers from starting new sessions with the server use the commands: disable sessions client disable sessions server Prevent administrative activity from any user ID other than the administrator ID that is being used to perform the upgrade preparation. Lock out other administrator IDs if necessary: lock admin administrator_name Check whether any sessions exist, and notify the users that the server is going to be stopped. To check for existing sessions, use the command: query session Cancel sessions that are still running. Use the command: cancel session Back up storage pools and the server database Immediately before upgrading the server, back up primary storage pools to copy storage pools, and perform a full database backup. Back up primary storage pools to copy storage pools using the BACKUP STGPOOL command. If you have been performing regular backups of the storage pools, this step backs up only the data that was added to the primary storage pools since they were last backed up. Back up the database using the following command. Use either a full or snapshot backup type. backup db type=type devclass=device_class_name The device class that you specify must exist and have volumes that are available to it. For example, to perform a snapshot backup of your database to the TAPECLASS device class using scratch volumes, enter: backup db type=dbsnapshot devclass=tapeclass To use specific volumes instead of scratch volumes, specify the volume names in the command. Consider making two copies of the backup to protect the backup from media failures. Back up configuration information Before installing the new version, back up critical files and information for the server. Store the files in a safe place, because they are needed after the installation of the new software
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
303
7718Planning.fm
version is completed. You also need these files if you must revert to the previous version after the upgrade. Back up device configuration information: backup devconfig filenames=file_name Back up volume history information: backup volhistory filenames=file_name Ensure that the volume history includes information about the database backup that you completed in the preceding steps. For example, issue the command: query volhistory type=dbbackup Make copies of these files, which are located in the default directory for the server: server options file, typically named dsmserv.opt dsmserv.dsk Optional make a copy of the accounting log file, dsmaccnt.log Back up any scripts that have been used to perform daily housekeeping for the server. Examine the scripts for changes that are needed after the upgrade. Store the device configuration file, the volume history file, the server options file, and the other files in a safe place. Select a location that is not on the system that is being upgraded. Create a summary of database contents Create a summary of the contents of the original database. After the upgrade, you can use the same commands to compare the results and to confirm that the database contents are intact. Run commands that give a summary of information about your database contents. For example, issue commands that summarize the file spaces being protected, and save the results. See the sample commands for ideas. Stop the server before installing the upgrade Stop all server processes and dismount any tapes that are mounted. Then stop the server. The commands in the following procedure are Tivoli Storage Manager administrative commands. Cancel sessions if any are still running. Use the command: cancel session Allow time for the sessions to be stopped. Some sessions, such as backup by a backup-archive client, might take some time to stop. Determine whether server processes are running. Either cancel processes, or allow them to complete. Use the commands: query process cancel process process_number Allow time for the processes to be stopped. Some processes, such as storage pool migration, might take some time to stop. After all sessions and processes are stopped, determine whether any tapes are mounted. Dismount any tapes that are mounted. Use the commands: query mount dismount volume volume_name Stop the server using the command: halt
304
7718Planning.fm
Installing the upgrade utilities You must install the upgrade utilities on the system where the V5 server is located. The installation package for the utilities must be downloaded from a Web site. You need an upgrade version that is greater than or equal to the level of the Tivoli Storage Manager server you are upgrading. First perform all preparation tasks on the original (source) system. Preparation includes: For the storage pools set reuse delay to the number of days during you want to be able to revert back to the original server if that becomes necessary. For each copy storage pool, set the RECLAIM parameter to 100. Backup and make copies of device configuration, volumehistory and server options files. Backup storage pools and server database, create a summary of the database contents. You can use the DSMUPGRD utility for this. Log on to source server with an administrator ID to install the upgrade utilities on the system where the V5 server is located. and run the executable package. The default location for the installation of the utilities is based on the location where the V5 server was last installed. The package to install is available for download from the FTP downloads site. The upgrade utilities are used to prepare and extract the database from the original server. Note: When we use the upgrade utilities and if we have multiple servers running on the system, we must use the -k option to specify the name of the Windows registry key from which to retrieve information about the server being upgraded.
Do not install the utilities in the same directory as the original server that is to be
upgraded, this is a restriction and is not allowed. The utilities package must be installed whether you are using the upgrade wizard or performing the upgrade manually with utilities. When we use the upgrade utilities and if we have multiple servers running on the system, we must use the -k option to specify the name of the Windows registry key from which to retrieve information about the server being upgraded. For example, if the V5 server was installed using the default path, C:\Program Files\Tivoli\TSM\server, create a upgrade folder and the upgrade utilities should be installed in path C:\Program Files\Tivoli\TSM\upgrade. After the upgrade utilities are installed, continue with installing the V6.1 server on the target server. Log on to the target system as an administrator and change to the directory where you placed the executable file. n the next step, the files are extracted to the current directory. Ensure that the file is in the directory where you want the extracted files to be located. Either double-click the executable file, or enter the following command on the command line to extract the installation files. The files are extracted to the current directory. 6.1.0.0-TIV-TSMALL-platform.exeInstall the V6.1 server code on the new system. After the install is check the installations logs in path C:\Program Files\Tivoli\TSM Create the directories for the V6.1 database and logs, and the user ID that will own the server instance. We choose TSM1 as the DB2 user ID. Start the upgrade wizard by double clicking in it or run the command on following path "c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe" to configure the new server and upgrade the V5 database. With the wizard, you complete the following tasks:
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
305
7718Planning.fm
On the original system, prepare the V5 database. On the new system, create and format an empty database to receive the data. Move the data from the V5 database to the V6.1 database. Configure the new system for database backup.
Complete the post-installation tasks, including backing up the database and verifying the database contents. Note: Need upgrade version that is greater than or equal to the level of the Tivoli Storage Manager server you are upgrading
16.14.2 Performance tips for inserting data into the V6.1 database
The process for inserting the V5 extracted data into the V6.1 database is the longest-running part of an upgrade process, and is the most sensitive to the configuration of the system. On a system that meets the minimum requirements, the insertion process will run, but performance might be slow. For better performance, set up the system as described in the tips. Processors The insertion process is designed to exploit multiple processors or cores.
306
7718Planning.fm
The insertion process will typically perform better on a system with a relatively small number of fast processors than on a system with more but slower processors. Disk storage The insertion process is designed to exploit high-bandwidth disk storage subsystems. The speed of the process is highly dependent on the disk storage that is used. For best performance, use multiple LUNs that map to multiple independent disks, or that map to RAID arrays with a large stripe size (for example, 128 KB). Use a different file system on each LUN. Table 16-10 shows an example of good usage of LUNs.
Table 16-10 Use of separate disks for database and logs.
# of LUN
4-128 1 1 1 1
Usage
Database
Note: If the disk storage is supplied by a virtualization device (high-end storage controller, or a SAN virtualization device), ensure that none of the virtual LUNs are on the same physical disk drive. Ensure that the directories in use are on different physical disk drives within the virtualization device.
Chapter 16. Install and Upgrade Planning for Tivoli Storage Manager V6.1
307
7718Planning.fm
308
7718pInstall.fm
Part 7
Part
Installation, customization and upgrade of Tivoli Storage Manager V6.1 Server and Client
This part of the book contains the Tivoli Storage Manager V6.1 installation and upgrade of the server and clients information.
309
7718pInstall.fm
310
7718Install_AIX.fm
17
Chapter 17.
311
7718Install_AIX.fm
Hardware
Table 17-1 describes the hardware requirements for your AIX system. For further details, reference the Tivoli Storage manager for AIX, Installation Guide, Capacity Planning, GC23-9781 to assist you in understanding greater detail for disk planning.
Table 17-1 Hardware requirements for Tivoli Storage Manager v6.1 for AIX Type of hardware Hardware Disk space Hardware Requirements 64-bit p4, p5 or p6 System p computer The following is minimum disk space 5 MB for the /var directory 2 GB for the /opt directory 160 MB for the /tmp directory 300 MB for the /usr directory At least 2 GB. A minimum of 4 GB for production servers. 8 GB is optimal.
Memory
Table 17-2 describes the minimum software requirements for Tivoli Storage Manager v6.1 running on an AIX system.
312
7718Install_AIX.fm
Table 17-2 Software requirements for Tivoli Storage Manager V6 for AIX Type of Software Operating system Minimum software requirements AIX 5.3 running in a 64-bit kernel environment wit the following additional requirements for DB@:
AIX 5.3 Technology Level (TL) 6 and Service Pack (SP) 2 plus the fix for APAR IZ03063 Minimum C++ runtime level with the xlC.rte 9.0.0.8 and xlC.aix50.rte 9.0.0.8 filesets. These filesets are included in the June 2008 cumulative fix package for IBM C++ Runtime Environment Components for AIX.
AIX 6.1 running in a 64-bit kernel environment requires the following filesets for DB2:
Minimum C++ runtime level with the xlC.rte 9.0.0.8 and xlC.aix61.rte 9.0.0.8 filesets. These filesets are included in the June 2008 cumulative fix package for IBM C++ Runtime Environment Components for AIX.
Communication protocol Drivers A configured communication method. If you have an IBM 3570, IBM 3590, or IBM Ultrium tape library or drive, install the most current device driver before you install Tivoli Storage manager 6.1. You can locate the device drivers at ftp://ftp.software.ibm.com/storage/devdrvr/.
313
7718Install_AIX.fm
Example 17-1 AIX command line example for the chmod command
chmod a+x 6.1.2.0-TIV-TSMALL-AIX.bin Run the following command to extract the installation files: ./6.1.0.0-TIV-TSMALL-platform.bin Following the extraction, we find the following directories and files have been created.
Example 17-2 Contents of the extraction directory
# ls -l total 3530528 -rwxr-x--x 1 root system 1732513010 May drwxr-xr-x 4 root system 256 drwxr-xr-x 3 root system 256 -rwxr-xr-x 1 root system 1128 -rwxr-xr-x 1 root system 75111171 drwxr-xr-x 2 root system 256
21 20:15 6.1.2.0-TIV-TSMALL-AIX.bin May 19 14:46 COI May 19 14:46 DE May 19 14:53 PostFailureTask.xml May 19 14:23 install.bin May 21 11:36 lost+found
Disk consumption at this point for the COI directory is shown in the example below, presented in 1024kb blocks.
Example 17-3 Disk usage of the COI directory, following the extraction of the install package.
# du -ks COI 2050972 COI Disk consumption for the DE directory is shown in the example below, presented in 1024kb blocks.
Example 17-4 Disk consumption of the DE directory, following the extraction of the install package.
# du -ks DE 125324 DE
# ./install.bin Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... 314
Tivoli Storage Manager V6.1 Technical Guide
7718Install_AIX.fm
Configuring the installer for this system's environment... Launching installer... Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX) Stack Trace: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:196) at java.awt.Window.<init>(Window.java:346) at java.awt.Frame.<init>(Frame.java:452) at java.awt.Frame.<init>(Frame.java:417) at javax.swing.JFrame.<init>(JFrame.java:180) at com.zerog.ia.installer.LifeCycleManager.g(DashoA10*..) at com.zerog.ia.installer.LifeCycleManager.h(DashoA10*..) at com.zerog.ia.installer.LifeCycleManager.a(DashoA10*..) at com.zerog.ia.installer.Main.main(DashoA10*..) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 43) at java.lang.reflect.Method.invoke(Method.java:618) at com.zerog.lax.LAX.launch(DashoA10*..) at com.zerog.lax.LAX.main(DashoA10*..) This Application has Unexpectedly Quit: Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX) Note: If you have connected using telnet, and the system you are installing on has a graphics console, you will not see this error, nor the graphical installation screens.
315
7718Install_AIX.fm
Example 17-6 AIX Tivoli Storage Manager command line console for installation
# ./install.bin -i console 2. Next, choose your console local (language), as shown in Example 17-7.
Example 17-7 Select the locale for the install console
Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... Preparing CONSOLE Mode Installation... =============================================================================== Choose Locale... ---------------1->23456Deutsch English Espaol Franais Italiano Portugus
(Brasil)
CHOOSE LOCALE BY NUMBER: 2 3. Following this selection, the next screen which is presented is the installation welcome screen as show in Example 17-8 on page 316.
Example 17-8 Installation Welcome screen
Tivoli Storage Manager (created with InstallAnywhere by Macrovision) ------------------------------------------------------------------------------=============================================================================== Tivoli Storage Manager Install -----------------------------Welcome Tivoli Storage Manager 6.1 Licensed Materials - Property of IBM Corp. (c) IBM Corporation and other(s) 1993, 2008. All rights reserved. US Government Users Restricted Rights -Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. It is strongly recommended that you quit all programs before continuing with this installation. PRESS <ENTER> TO CONTINUE:
316
7718Install_AIX.fm
4. Next, after pressing <enter>, you are presented with the license agreement screen, which also identifies options for traversing the text, as seen in Example 17-9.
Example 17-9 Tivoli Storage Manager V6.1.2 Component Selection panel
International Program License Agreement Part 1 - General Terms BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON, COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS, - DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE PROGRAM; AND - PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM YOU ACQUIRED IT TO OBTAIN A REFUND OF THE AMOUNT YOU PAID. IF YOU DOWNLOADED THE PROGRAM, CONTACT THE PARTY FROM WHOM YOU ACQUIRED IT. "IBM" is International Business Machines Corporation or one of its Press Enter to continue viewing the license agreement, or enter "1" to accept the agreement, "2" to decline it, "3" to print it, "4" to read non-IBM terms, or "99" to go back to the previous screen.: 5. You must eventually select option 1 to accept the licensing terms to continue. After doing this, you must select what software components to install. In this example we are selecting options 1,3 and 6. It is recommended to install the Administration Center feature on another system, possibly sharing this secondary system with the Reporting feature software. 6. After selecting the components to install, the next task is to choose the Administrator Center ID and password as shown in the following Example 17-10.
Example 17-10 Administration Center install
Administration Center --------------------To install the Administration Center enter the following information. ISC user name: (DEFAULT: iscadmin): iscadmin =============================================================================== ISC password::********* ===============================================================================
317
7718Install_AIX.fm
7. Following this selection, a Deployment Engine Initialization occurs. We have removed multiple lines to reduce the amount of line outputs. This is shown in Example 17-11.
Example 17-11 Deployment Engine Initialization screen
Deployment Engine Initialization -------------------------------Please Wait .. completed: 1 ; total: 19 Lines have been removed ... completed: 19 ; total: 19 Completed. Completed.
8. Next, you are presented with a review panel as shown in Figure 17-1. Pre-Installation Summary -----------------------Please Review the Following Before Continuing: Product Name: Tivoli Storage Manager Install Folder: /opt/tivoli/tsm Components: TSM Server,DB2 9.5,TSM Client API,TSM License,eWAS,ISC,TSM Administration Center Disk Space Information (for Installation Target): Required: 2,251,666,227 bytes Available: 2,327,085,056 bytes PRESS <ENTER> TO CONTINUE:
Figure 17-1 Pre-installation Summary panel
9. After the completion of the installation, the summary screen and exit prompt are presented, as shown in Example 17-12.
318
7718Install_AIX.fm
Example 17-12 Tivoli Storage Manager v6.1 successfully installed summary panel
=============================================================================== Installation Complete --------------------See /var/tivoli/tsm/log.txt for details. The following components were successfully installed: TSM Server DB2 9.5 TSM Client API TSM License eWAS ISC TSM Administration Center To continue, either configure a new server instance or upgrade an existing server instance. To configure a new server instance, choose one of the following methods: Log in as root user or administrator and open the local new-instance wizard, dsmicfgx, located in the server installation directory. Log on to a Version 6.1 Tivoli Storage Manager Administration Center and start the Create New Instance wizard. Configure the new instance manually. See the Tivoli Storage Manager Information Center, or the Installation Guide. To upgrade an existing server instance, log in as root user or administrator and start the upgrade wizard, dsmupgdx, located in the server installation directory. You can also upgrade a server manually. See the Tivoli Storage Manager Information Center, or the Server Upgrade Guide. For more information about any of these tasks, see the Tivoli Storage Manager Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6 PRESS <ENTER> TO EXIT THE INSTALLER:
10.After completing the installation process, we will need to complete the configuration, as continued in section 17.5, Post installation steps for Tivoli Storage Manager on page 325.
319
7718Install_AIX.fm
Under the X11 category : X-start-menu-icons X-startup-scripts cygwin-x-doc xorg-x11-base xorg-x11-bin xorg-x11-bin-dlls xorg-x11-f100 xorg-x11-fcyr xorg-x11-fenc xorg-x11-fscl xorg-x11-man-pages xorg-x11-man-pages-html xorg-x11-xwin
320
7718Install_AIX.fm
xorg-Xterm xwinclip Minimum Under the "Net" category (if you use ssh) : openssh openssl ping
2. If "ssh" is running on the remote machine : a. from a cygwin shell, enter the following command startx b. this will start another cygwin shell, from that new shell, enter the following command xhost <remote_machine_ip> c. from that same cygwin shell, start a ssh session with the remote machine : ssh -X -l <user> <remote_machine_ip> d. from the ssh shell, start an X11 remote shell by issuing the xterm & command. Type exit to end the test connection, or continue to the Installation wizard using X11 redirection on page 321 once you have completed this step. 3. if "ssh" is not running on the remote machine : a. from a cygwin shell, enter the following command startx b. this will start another cygwin shell, from that new shell, enter the following command xhost <remote_machine_ip> c. leave these shells running d. from a "normal MSDOS" window shell, use the telnet command to the remote machine, telnet <remote_machine_ip> e. once you are logged in, enter the following command export DISPLAY= <ip_of_windows_machine>:0.0 f. In the telnet shell, start an X11 remote shell by issuing the xterm & command. Type exit to end the test connection, or continue to the Installation wizard using X11 redirection on page 321 once you have completed this step.
# IATEMPDIR=/code # export IATEMPDIR 2. Next, we then create a seperate logical volume for the target directory of /opt/tivoli/tsm, which we create at 2.4 GB in size. This will hold all of the base installation software.
Chapter 17. Installation of Tivoli Storage Manager V6.1 on AIX
321
7718Install_AIX.fm
3. Next, start the installation steps by issuing the command shown in Example 17-15 from the installation source directory.
Example 17-15 AIX Tivoli Storage Manager installation wizard
# ./install.bin This command results in the screen output shown in Example 17-16.
Example 17-16 Result of install.bin command
# ./install.bin Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer.. Now, at this point the X11 graphics redirection begins to the Windows system, as shown in Figure 17-2 on page 322.
4. Select the language for your installation and follow the wizard directions, selecting OK to step through the wizard to choose English. Then, click Next to complete the welcome screen. 5. Following this, you must accept the license agreement to proceed, as shown in Figure 17-3 on page 323.
322
7718Install_AIX.fm
6. Next, we select the components that we want to install (server, licenses, and Administration Center). There is no default so you must make a selection or you will receive an error message and be returned to the components page. Our selections are shown in Figure 17-4 on page 323.
Figure 17-4 Select Components for AIX Tivoli Storage Manager install
323
7718Install_AIX.fm
7. Since we selected the Administration Center component, we are prompted for a user name and password, as seen in Figure 17-5 on page 324. We will use these later to log onto the Integrated Solutions Console and Administration Center.
Note: The Tivoli Storage Manager client application programming interface (API) is automatically installed when you select the server component. 8. After selecting next on the Administration Center panel, the pre-installation summary panel appears, as shown in Figure 17-6.
324
7718Install_AIX.fm
After reviewing, we select the install option to continue. Then, at the end of the installation, a message is displayed on the summary page that Tivoli Storage Manager successfully installed and a summary is provided. If there were any errors during the installation, the summary page lists the errors and directs you to an error log file. Fix the errors before continuing. The installation log is stored in the following location: /var/tivoli/tsm/log.txt
17.5.1 Prepare the AIX server for Tivoli Storage Manager instances
Tivoli Storage Manager will use default locations, however it is recommended to preconfigure your disk structure first, possibly considering a naming convention that facilitates multiple instances. In AIX, this might imply Volume Group, Logical Volume and mount points which reflect an instance naming convention.
Disk Structure
Tivoli Storage Manager will use default locations, however it is recommended to preconfigure your disk structure first, possibly considering a naming convention that facilitates multiple
325
7718Install_AIX.fm
instances. Once you have created your disk structure, then provide these path names during the install process. The following example shows our test configuration.
Table 17-3 Disk paths required and the test environment setup AIX Volume Group AIX Logical Volume Naming Convention Default Size (MB) Test System Sizing (MB) 3072 400 2048 2048 2048 2048 2048 2048 2048 2048 8192 8192 16384 8192 Seperate Disk Volume if Possible yes yes Yes Yes Yes Yes Yes Yes Yes Yes
tsmvg <instance>vg <instance>dbvg <instance>dbvg <instance>dbvg <instance>dbvg <instance>logvg <instance>logvg <instance>logvg <instance>logvg
/dev/tsmbinlv /dev/hd1 (default) /dev/dbdir001lv /dev/dbdir002lv /dev/dbdir003lv /dev/dbdir004lv /dev/actloglv /dev/actlogmlv /dev/archlog /dev/archlogf
/opt/tivoli/tsm /home/<instance> <instance>/dbdir001 <instance>/dbdir002 <instance>/dbdir003 <instance>/dbdir004 <instance>/activelog <instance>/activelogm <instance>/archlog <instance>/archlogf
The filesystems created for this AIX system are shown in Example 17-17. This demonstrates one of many ways to name and mount volumes for use with a tsm1 instance.
Example 17-17 AIX filesystems, including all the custom logical volume and JFS2 created
Filesystem 512-blocks Free %Used /dev/hd4 655360 289784 56% /dev/hd2 4587520 333488 93% /dev/hd9var 262144 103120 61% /dev/hd3 655360 115128 83% /dev/hd1 917504 916456 1% /dev/hd11admin 262144 261416 1% /proc /dev/hd10opt 1703936 1143584 33% /dev/download_lv 5242880 1144808 79% /dev/codelv 52428800 47126688 11% /dev/tsmbinlv 4980736 460856 91% /dev/tsmbinlv 4980736 394256 93% /dev/dbdir001lv 4194304 3963168 6% /dev/dbdir002lv 4194304 3963152 6% /dev/dbdir003lv 4194304 3963144 6% /dev/dbdir004lv 4194304 3963152 6% /dev/actlog 8519680 1168120 87% /dev/actlogm 8519680 8495760 1% /dev/archlog 16777216 9427808 44% /dev/archlogf 8388608 8386600 1%
Iused %Iused Mounted on 11942 25% / 44675 49% /usr 4767 29% /var 4035 23% /tmp 14 1% /home 5 1% /admin - /proc 3153 3% /opt 17 1% /download 2296 1% /code 26700 33% /opt/tivoli/tsm 26714 37% /opt/tivoli/tsm 44 1% /tsm1/dbdir001 44 1% /tsm1/dbdir002 44 1% /tsm1/dbdir003 44 1% /tsm1/dbdir004 14 1% /tsm1/activelog 12 1% /tsm1/activelogm 14 1% /tsm1/archlog 12 1% /tsm1/archlogf
326
7718Install_AIX.fm
# mkgroup id=1001 tsmsrvrs # mkuser -a id=1002 pgrp=tsmsrvrs home=/home/tsm1 tsm1 # passwd tsm2 Changing password for "tsm1" tsm1's New password: Enter the new password again:
Next, log in using the user ID and password, and you will be prompted to change the password as that user ID, as shown in Example 17-19.
Example 17-19 Logging into AIX and changing the password for TSM1 new instance creation.
You must change your password now and login again! Changing password for "tsm2" tsm1's Old password: tsm1's New password:
# cd /tsm1 # pwd /tsm1 # chown -R tsm1.tsmsrvrs * # ls -l total 0 drwxr-xr-x 4 tsm1 tsmsrvrs drwxr-xr-x 4 tsm1 tsmsrvrs drwxr-xr-x 4 tsm1 tsmsrvrs drwxr-xr-x 5 tsm1 tsmsrvrs drwxr-xr-x 4 tsm1 tsmsrvrs drwxr-xr-x 4 tsm1 tsmsrvrs drwxr-xr-x 4 tsm1 tsmsrvrs drwxr-xr-x 4 tsm1 tsmsrvrs
01 01 01 01 01 01 01 01
327
7718Install_AIX.fm
# pwd /home/tsm1 # ls -l total 168 -rwxr----1 -rw------1 -rw------1 -rw-r--r-1 drwxrwsr-t 18 # du -ks sqllib 300588 sqllib
26 26 26 26 26
2. db2incrt also establishes the database instance within DB2, and the directory and file heiarchy to manage this is shown in Example 17-23.
Example 17-23 DB2 files to manage the new Tivoli Storage Manager instance
# ls -Rl tsm1 total 0 drwxrwxr-x 4 tsm1 tsm1/NODE0000: total 8 drwxr-x--4 tsm1 drwxrwxr-x 2 tsm1 tsm1/NODE0000/SQL00001: total 13160 -rw-r----1 tsm1 -rw------1 tsm1 -rw------1 tsm1 -rw------1 tsm1 -rw------1 tsm1 -rw-r----1 tsm1 -rw------1 tsm1 -rw------1 tsm1 328
tsmsrvrs
tsmsrvrs tsmsrvrs
13 11 11 26 13 13 13 13
7718Install_AIX.fm
drwxr-x---rw-------rw-------rw-------rw-------rw-------rw-r----drwxr-x---rw-r-----rw-r-----
2 1 1 1 1 1 1 3 1 1
tsm1 tsm1 tsm1 tsm1 tsm1 tsm1 tsm1 tsm1 tsm1 tsm1
tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs tsmsrvrs
May Jun May May Jun Jun May May Jun Jun
26 13 26 26 13 13 26 26 14 14
20:27 19:04 20:22 20:22 19:05 19:05 20:22 20:22 00:59 00:59
SQLOGDIR SQLOGMIR.LFH SQLSGF.1 SQLSGF.2 SQLSPCS.1 SQLSPCS.2 SQLTMPLK db2event db2rhist.asc db2rhist.bak
tsm1/NODE0000/SQL00001/db2event/db2detaildeadlock: total 4808 -rw-r--r-1 tsm1 tsmsrvrs 2096516 Jun 12 01:42 00000000.evt -rw-r--r-1 tsm1 tsmsrvrs 352369 Jun 13 19:04 00000001.evt -rw-r----1 tsm1 tsmsrvrs 39 Jun 12 01:42 db2event.ctl tsm1/NODE0000/sqldbdir: total 24 -rw-rw-r-1 tsm1 -rw-rw-r-1 tsm1 -rw-rw-r-1 tsm1
1512 May 26 20:30 sqldbbak 1512 May 26 20:30 sqldbdir 540 May 26 20:23 sqldbins
3. The next step is to log out of AIX as the root user, and log in as the instance user ID (tsm1). Upon completing this, you will find an environment for DB2 has been established, as discussed in the previous steps. 4. The next step we update the default directory for the database to reflect the instance directory, by running the db2 update command as shown in Example 17-24.
Example 17-24 Setting the default directory for the database to be the same as the instance directory.
$ pwd /home/tsm1 $ db2 update dbm cfg using dftdbpath /tsm1 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
This db2 upd command establishes the db2 configuration for the tsmdb1 database, and can be reviewed by running a db2 => get snapshot for database on TSMDB1, as shown in Example 17-25.
Example 17-25 Get snapshot for database on TSMDB1 DB2 command
cd /home/tsm1/sqllib/bin db2 => get snapshot for database on TSMDB1 Database Snapshot
Chapter 17. Installation of Tivoli Storage Manager V6.1 on AIX
329
7718Install_AIX.fm
Database name = TSMDB1 Database path = /home/tsm1/tsm1/NODE0000/SQL00001/ Input database alias = TSMDB1 Database status = Active Catalog database partition number = 0 Catalog network node name = Operating system running at database server= AIX 64BIT Location of the database = Local First database connect timestamp = 06/01/2009 12:44:05.254311 Last reset timestamp = Last backup timestamp = 06/01/2009 12:41:33.000000 Snapshot timestamp = 06/01/2009 13:59:45.841818 Number of automatic storage paths Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) = = = = = = = = = = = = = = = = = = = = = = = = = 4 /tsm1/dbdir001 0 9223372238718238723 2029142016 118341632 2147483648 /tsm1/dbdir002 0 9223372238718238724 2029133824 118349824 2147483648 /tsm1/dbdir003 0 9223372238718238725 2029129728 118353920 2147483648 /tsm1/dbdir004 0 9223372238718238726 2029133824 118349824 2147483648
5. Next, format the files for the database and logs, using the Tivoli Storage Manager server command dsmserv format as shown in Example 17-26.
Example 17-26 dsmserv format command syntax for setting up a server instance in V6.1
The successful output of the dsmserv format command is shown in Example 17-27.
Example 17-27 Output of the dsmserv format command in Tivoli Storage Manager V6.1
330
7718Install_AIX.fm
Tivoli Storage Manager for AIX Version 6, Release 1, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2008. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I ANR0900I ANR7811I ANR4726I ANR0152I ANR0152I ANR1380I ANR0992I ANR0369I ANR2976I ANR2974I Subsystem process ID is 323600. Processing options file /home/tsm1/dsmserv.opt. Using instance directory /home/tsm1. The ICC support module has been loaded. Database manager successfully started. Database manager successfully started. The buffer pool monitor switch is enabled. Server's database formatting complete. Stopping the database manager because of a server shutdown. Offline DB backup for database TSMDB1 started. Offline DB backup for database TSMDB1 completed successfully.
6. Following the successful formatting, the next step will be to start the Tivoli Storage Manager V6.1 server in the foreground. To perform this, we will use the new parameters provided in the dsmserv command, as shown in Example 17-28. Refer to Table 4-5 on page 36 for information on the DSMSERV command.
Example 17-28 Starting the Tivoli Storage Manager V6.1 server instance in the foreground
$ /opt/tivoli/tsm/server/bin/dsmserv -u tsm1 -i /home/tsm1 The foreground output of the Tivoli Storage Manager V6.1 startup appears similar to that of previous releases, with the exception of Database Manager startup, as shown in Example 17-29 on page 331.
Example 17-29 Tivoli Storage Manager server instance startup output on AIX
ANR7800I DSMSERV generated at 16:29:44 on Mar 13 2009. Tivoli Storage Manager for AIX Version 6, Release 1, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2008. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 368828. ANR0900I Processing options file /home/tsm1/dsmserv.opt. ANR7811I Using instance directory /home/tsm1. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0152I Database manager successfully started. ANR1380I The buffer pool monitor switch is enabled.
331
7718Install_AIX.fm
ANR1635I The server machine GUID, c8.8d.1e.ec.41.e6.11.de.98.6e.08.63.09.0c.05.0c, has initialized. ANR2100I Activity log process has started. ANR4726I The NAS-NDMP support module has been loaded. ANR1794W TSM SAN discovery is disabled by options. ANR2803I License manager started. ANR0984I Process 1 for EXPIRE INVENTORY (Automatic) started in the BACKGROUND at 13:31:05. ANR8285I Shared Memory driver ready for connection with clients on port 1510 ANR0811I Inventory client file expiration started as process 1. ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1500. ANR2560I Schedule manager started. ANR0167I Inventory file expiration process 1 processed for 0 minutes. ANR0812I Inventory file expiration process 1 completed: processed 0 nodes, examined 0 objects, deleting 0 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried and 0 errors were encountered. ANR0985I Process 1 for EXPIRE INVENTORY (Automatic) running in the BACKGROUND completed with completion state SUCCESS at 13:31:07. ANR2841W Server is NOT IN COMPLIANCE with license terms. ANR0984I Process 2 for AUDIT LICENSE started in the BACKGROUND at 13:31:07. ANR2820I Automatic license audit started as process 2. ANR2825I License audit process 2 completed successfully - 0 nodes audited. ANR0985I Process 2 for AUDIT LICENSE running in the BACKGROUND completed with completion state SUCCESS at 13:31:08. ANR2841W Server is NOT IN COMPLIANCE with license terms. TSM:SERVER1> ANR0993I Server initialization complete. ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use. Storage Management Server for AIX - Version 6, Release 1, Level 0.0 TSM:SERVER1> The startup time for a new server instance is approximately 8 minutes, as shown by using the AIX time command, and allowing for halt time, shown in Example 17-30.
Example 17-30 Output of the AIX time command: V6.1 startup and immediate halt time
332
7718Install_AIX.fm
Api log file directory The correct password is set The steps required to complete this task are: 1. We set the DSMI_ api environment variables in the <instance>/sqllib/db2profile file, as shown in Example 17-31.
Example 17-31 The line items added to the sqllib/db2profile file.
export DSMI_CONFIG=/home/tsm1/tsmdbmgr.opt export DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 export DSMI_LOG=/home/tsm1 2. Then log out, and back into the instance, or issue the command as shown in the Example 17-32 ~/.profile to re-read the profile.
Example 17-32
$ ~/.profile 3. Next, create a file called tsmdbmgr.opt in the /home/tsm1 directory and add the following line as shown in example Example 17-33
Example 17-33 Content of the /ome/tsm1/tsmdbmgr.opt file.
servername tsmdbmgr_tsm1 4. Next, edit the /usr/tivoli/tsm/client/api/bin64/dsm.sys. Avoid placing the server name, TSMDBMGR_TSM1, first in dsm.sys because it should not be the system-wide default. In this example, the added lines are after the stanza for server_a, as shown in Example 17-34 on page 333.
Example 17-34 /usr/tivoli/tsm/client/api/bin64/dsm.sys
Servername server_a COMMMethod TCPip TCPPort 1500 TCPServeraddress node.domain.company.COM servername TSMDBMGR_TSM1 commmethod tcpip tcpserveraddr localhost tcpport 1500 passwordaccess generate passworddir /home/tsm1 errorlogname /home/tsm1/tsmdbmgr.log nodename $$_TSMDBMGR_$$
$ db2stop $ db2start 6. Next set the API password for the instance TSM1, using the password (current and new) as TSMDBMGR, as root user, as shown in Example 17-36.
333
7718Install_AIX.fm
# cd /home/tsm1/sqllib/adsm # ./dsmapipw ************************************************************* * Tivoli Storage Manager * * API Version = 6.1.0 * ************************************************************* Enter your current password: Enter your new password: Enter your new password again:
7. Finally we can submit the database backup,issue the backup database command. Example 17-37 documents the results, and shows we successfully completed the task.
Example 17-37 The first manual backup
To reference the product manual for this process refer to the following site. http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm. srv.install.doc/t_srv_prep_dbmgr.html
Registering an Administrator
During this type of installation, there was no prompt for any Adminstrator ID or password. 8. After starting the server instance in the foreground, we must register an administrative user and password, using reg admin admin admin1 and finally grant authority using the command grant auth admin classes=system as a system user, as shown in Example 17-38.
Example 17-38 Registering an administrator and granting system authority
TSM:SERVER1> reg admin admin admin1 ANR2017I Administrator SERVER_CONSOLE issued command: REGISTER ADMIN admin ?***? ANR2068I Administrator ADMIN registered. TSM:SERVER1> grant auth admin classes=system ANR2017I Administrator SERVER_CONSOLE issued command: GRANT AUTHORITY admin classes=system ANR2076I System privilege granted to administrator ADMIN. 9. Following the administrator registration, we then establish the automatic startup of the ISC/AC by running the script: /opt/tivoli/tsm/AC/products/tsm/bin/setTSMUnixLinks.sh which will update the /etc/inittab with the following details, shown in Example 17-39.
Example 17-39 /etc/inittab entry as a result of running setTSMUnixLinks.sh script
334
7718Install_AIX.fm
10.Then, for the time we will manually start up the ISC/AC server process, as shown in Example 17-40.
Example 17-40 Manual command to start the ISC/AC Server processes
# /opt/tivoli/tsm/AC/products/tsm/bin/rc.IBMTSM start & Following the the startup command, the output of the Integrated Solutions Console is shown in Example 17-41.
Example 17-41 ISC/AC startup command output
ADMU0116I: Tool information is being logged in file /opt/tivoli/tsm/AC/ISCW61/profiles/TsmAC/logs/tsmServer/startServer.log ADMU0128I: Starting tool with the TsmAC profile ADMU3100I: Reading configuration for server: tsmServer ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server tsmServer open for e-business; process id is 319680
11.Then, the following step we will connect remotely to the ISC/AC using HTTPS, using the connection address https://9.12.5.12:9043/ibm/console, as shown in Figure 17-7 on page 335.
335
7718Install_AIX.fm
Following the connection sucess, log into the using the Integrated Solutions Console userid and password which was established during the installation process, as shown in Figure 17-8 on page 336.
12.Once logged in, at this point you can view the Integrated Solutions Console, however at this point, you can log out as this step is verified as working correctly. Logout is shown in Figure 17-9 on page 337.
336
7718Install_AIX.fm
Figure 17-9 Demonstrating the logout of the V6.1 Integrated Solutions Console
337
7718Install_AIX.fm
on page 338. which starts by expanding the Tivoli Storage Manger option in the left side panel.
338
7718Install_AIX.fm
Next, use the Select Action drop down and choose Add Server Connection, as shown in Figure 17-12 on page 339.
Next, type in the connection details for the new TSM1 instance, as shown in Figure 17-13.
Figure 17-13 Adding a server connection for server instance within the Integrated Solutions Console
339
7718Install_AIX.fm
After clicking OK wait for the successful completion panel as shown in Figure 17-14 on page 340. Next click the OK button once again.
Figure 17-14 Summary page after adding a server connection in the Integrated Solutions Console
Finally, for test and review of the server connection, click on the TSM1 server link, as shown in Figure 17-15 on page 340.
Figure 17-15 V6.1 Manage Servers panel in the Integrated Solutions Console interface
On the next panel click on Database and Log option on the left side panel, as shown in Figure 17-16 on page 341.
340
7718Install_AIX.fm
Lastly, you can observe the initial database size, with the preformatted log size, which was input during the dsmformat stage of the installation, as shown in Figure 17-17.
Figure 17-17 Database and recoverylog size shown in Tivoli Storage Manager V6.1
tsm1:2:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsm1 -i /home/tsm1 -q >/dev/console 2>&1 Next, to setup the autostart function for the Administrator Center, you must complete the following tasks. Log in with the root user ID. Change to the /opt/tivoli/tsm/AC/products/tsm/bin directory. Run the following script: setTSMUnixLinks.sh
341
7718Install_AIX.fm
This script inserts a line in the /etc/inittab files as shown in Example 17-43.
Example 17-43 Entry into the /etc/inittab to startup V6.1 Admin Center service on AIX
# cd /opt/tivoli/tsm/server/bin # export DISPLAY=9.12.6.78:0.0 # ./dsmicfgx Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... 3. The Instance Configuration Wizard is launched. First, choose the language, as shown in Figure 17-18.
342
7718Install_AIX.fm
4. After clicking on OK, the introduction screen is displayed as shown in Figure 17-19 on page 343.
5. Click on Next, the instance user ID and password are requested. This panel with our response is shown in Figure 17-20 on page 344.
343
7718Install_AIX.fm
6. Click Next, we will continue by supplying the path of the instance files, as shown in Figure 17-21 on page 344.
344
7718Install_AIX.fm
7. Clicking Next, we progress to the database directories configuration panel, as shown in Figure 17-22.
Note: If you have not updated the permissions for your instance directories ( chown -R tsm1.tsmsrvrs /tms1) you will receive an error, which you then click <ok>, fix the permissions and click Next to retry the operation. 8. Next, we select the recovery log directories, using the Choose button to select the pre-defined directories for these logs, with the completed panel shown in Figure 17-23.
345
7718Install_AIX.fm
Note: You must have your filesystem slightly larger than the 8GB required for the recovery log, or this step may return an error. 9. After clicking Next, the server information screen will appear, and we will verify that all the fields are as we require, as shown in Figure 17-24 on page 347.
346
7718Install_AIX.fm
10.Clicking Next, the following panel is for the administror credentials.This refers to the Tivoli Storage Manager instance administrator, which is reference when configuring the server connection with in the administration center or directly connecting using the dsmadmc command. This panel is shown in Figure 17-25 on page 348. The minimum password criteria of one number included is enforced by this panel.
347
7718Install_AIX.fm
11.After clicking Next the following panel to appear is for server communication. This panel includes IPv6, shared memory and SSL communication options. In this example we are accepting the default, as shown in Figure 17-26 on page 349.
348
7718Install_AIX.fm
12.Clicking Next, you are presented with the configuration summary panel, as shown in Figure 17-27 on page 350.
349
7718Install_AIX.fm
13.After clicking Next, the configuration wizard will begin, and will present any errors if found. An example of an error due to insufficient space for the database, is shown in Figure 17-28 on page 351.
350
7718Install_AIX.fm
# ls .toc tivoli.tsm.devices.6.1.2.0.bff tivoli.tsm.devices.msg.en_US.6.1.2.0.bff tivoli.tsm.server.6.1.2.0.bff tivoli.tsm.server.license.6.1.2.0.bff tivoli.tsm.server.msg.en_US.6.1.2.0.bff Next, issue the AIX update_all command to install the updates, as shown in Example 17-46. 351
7718Install_AIX.fm
# smitty update_all The resulting output of the installation is shown in Example 17-47. Much of the text has been removed to reduced the volume of output captured.
Example 17-47 AIX smitty update_all command example for applying V6.1.2 update
Before command completion, additional instructions may appear below. geninstall -I "a -cgNqwXY -J" Text removed.... +-----------------------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------------------tivoli.tsm.server.msg.en_US 6.1.2.0 USR APPLY SUCCESS tivoli.tsm.server.license.c 6.1.2.0 USR APPLY SUCCESS tivoli.tsm.server 6.1.2.0 USR APPLY SUCCESS tivoli.tsm.server 6.1.2.0 ROOT APPLY SUCCESS tivoli.tsm.server.license.r 6.1.2.0 USR APPLY SUCCESS -Z -d . -f File 2>&1
cd /home/tsm1/sqllib/bin db2 => get snapshot for database on TSMDB1 Database Snapshot Database name Database path Input database alias Database status Catalog database partition number Catalog network node name 352
Tivoli Storage Manager V6.1 Technical Guide
= = = = = =
7718Install_AIX.fm
Operating system running at database server= AIX 64BIT Location of the database = Local First database connect timestamp = 06/01/2009 12:44:05.254311 Last reset timestamp = Last backup timestamp = 06/01/2009 12:41:33.000000 Snapshot timestamp = 06/01/2009 13:59:45.841818 Number of automatic storage paths Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) Automatic storage path Node number File system ID Storage path free space (bytes) File system used space (bytes) File system total space (bytes) = = = = = = = = = = = = = = = = = = = = = = = = = 4 /tsm1/dbdir001 0 9223372238718238723 2029142016 118341632 2147483648 /tsm1/dbdir002 0 9223372238718238724 2029133824 118349824 2147483648 /tsm1/dbdir003 0 9223372238718238725 2029129728 118353920 2147483648 /tsm1/dbdir004 0 9223372238718238726 2029133824 118349824 2147483648
Lock list memory in use (Bytes) Deadlocks detected Lock escalations Exclusive lock escalations Agents currently waiting on locks Lock Timeouts Number of indoubt transactions
= = = = = = =
34816 0 0 0 0 0 0
Buffer pool statistics removed to reduce output ... Direct reads Direct writes Direct read requests Direct write requests Direct reads elapsed time (ms) Direct write elapsed time (ms) Database files closed = = = = = = = 11352 3204 1562 534 4617 5988 0
353
7718Install_AIX.fm
Log space used by the database (Bytes) Maximum secondary log space used (Bytes) Maximum total log space used (Bytes) Secondary logs allocated currently Log pages read Log read time (sec.ns) Log pages written Log write time (sec.ns) Number write log IOs Number read log IOs Number partial page log IOs Number log buffer full Log data found in buffer Appl id holding the oldest transaction Log to be redone for recovery (Bytes) Log accounted for by dirty pages (Bytes) Memory usage for database: Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Secondary ID Current size (bytes) High water mark (bytes) Configured size (bytes)
= = = = = = = = = = = = = = = =
= = = = = = = = = =
0 Backup/Restore/Util Heap 65536 65536 213581824 0 Package Cache Heap 6881280 8454144 7864320
= Other Memory = 196608 = 196608 = 20971520 = = = = = = = = = = = 0 Catalog Cache Heap 1048576 1048576 4294967296 0 Buffer Pool Heap 4 101580800 247398400 4294967296
Removal multiple Buffer Pool Heap stanza entries..... Node number Memory Pool Type Secondary ID Current size (bytes) = = = = 0 Buffer Pool Heap System 4k buffer pool 393216
354
7718Install_AIX.fm
High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Secondary ID Current size (bytes) High water mark (bytes) Configured size (bytes)
= 393216 = 4294967296 = = = = = = = = = = = = = = = = = = = = = 0 Shared Sort Heap 65536 1048576 36831232 0 Lock Manager Heap 11534336 13762560 13828096 0 Database Heap 37093376 37093376 50266112 0 Application Heap 557 65536 65536 1048576
Removal of multiple Application Heap stanza entries ..... Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) = = = = = 0 Applications Shared Heap 1835008 1835008 81920000
17.7.2 Logs
This section lists logs that will be useful in product status and problem determination. Zip file containing all logs is located in; /var/tivoli/tsm/logs.zip Main log file is located in; <install_location>/coi/plan/MachinePlan_localhost/logs/MachinePlan_localhost_[INSTA LL_0414_22.35].log DB2 logs are located in; <install_location>/coi/plan/MachinePlan_localhost/00002_DB2_9.5/DB2_9.5.log <install_location>/coi/plan/tmp Administration Center logs are located in;
Chapter 17. Installation of Tivoli Storage Manager V6.1 on AIX
355
7718Install_AIX.fm
<install_location>/coi/plan/MachinePlan_localhost/00003_TSM_AdminCenter/logs: addJVMPropertyTCR.log addSharedLibTCR.log addUserRole.log deployEarTCR.log deployWarTCR.log deployWarTSM.log install.properties processReq-stderr.log processReq-stdout.xml setupDatasourceTCR.log setupTCR.log startServer.log stopServer.log
Deployment Engine logs are located in; /usr/ibm/common/acsi/logs/root DE_Install.log acu_de.log de_cbe.log de_msg.log de_trace.log
356
7718Install_AIX.fm
$ /opt/tivoli/tsm/server/bin/rc.dsmserv -u tsm1 -i /home/tsm1 ANR7800I DSMSERV generated at 11:52:37 on Jun 4 2009. Tivoli Storage Manager for AIX Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I ANR0900I ANR7811I ANR4726I ANR0990I ANR0152I ANR0130E Subsystem process ID is 458996. Processing options file /home/tsm1/dsmserv.opt. Using instance directory /home/tsm1. The ICC support module has been loaded. Server restart-recovery in progress. Database manager successfully started. rdbdb.c(1315): Server LOG space exhausted.
In Tivoli Storage Manager V5.5 an extend log command would be required, provided you were not already at the 13GB limit. However in V6.1 we have a different recovery log process, which helps to understand in order to correct this current system down condition. There are four log functions with our new Tivoli Storage Manager and DB2 environment, so which one might be the root cause in this situation? The space situation is as shown in Example 17-50.
Example 17-50 Vermont-tsm1 filesystem state after the log exhausted error.
26719 44 44 44 44 14 12 22 24
37% 1% 1% 1% 1% 1% 1% 1% 1%
357
7718Install_AIX.fm
As seen, none of the filesystems which hold logs have 512MB of available space, thus all would be considered full to DB2. As for which one do we need to add filesystem space to in order to sucessfully restart Tivoli Storage Manager, then perform a full database backup? The answer to this question is the archlog (archive log), and this is because the recovery log size was set during the installation process, and is essentially fixed at this point. So if we add space to the archive log, which is the overflow log location, when we start up Tivoli Storage Manager and DB2 will have room to process additional transactions, long enough to complete the full database backup. Next, we increase the JFS2 filesystem for the archive log as demonstrated in Example 17-51.
Example 17-51 AIX command chfs -a which is used to expand the JFS2 filesystem.
Now, we have more than 512MB of space available on the /tsm1/archlog file system, and will restart the Tivoli Storage Manager V6.1 server in the foreground as before, then configure for a database backup to file, which will clear the logs. It will take two full backups to clear out the archive logs. prior to the startup in the foreground, we add three statements into the /home/tsm1/dsmserv.opt file to ensure reclamation, expire inventory and client schedules (see Example 17-52).
Example 17-52 dsmserv.opt additions to ensure no database and recovery log activity will run
Now, we are ready to start the foreground Tivoli Storage Manager server V6.1, as shown in Example 17-53 on page 358.
Example 17-53 Foreground V6.1 startup after correcting the log exhaustion problem
TSM:VERMONT-TSM1> define devc dbb_file devt=file dir=/code/dbb_backups ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE DEVCLASS dbb_file devt=file dir=/code/dbb_backups ANR2203I Device class DBB_FILE defined. TSM:VERMONT-TSM1> set dbrecovery dbb_file ANR2017I Administrator SERVER_CONSOLE issued command: SET DBRECOVERY dbb_file ANR2782I SET DBRECOVERY completed successfully and device class for automatic DB backup is set to DBB_FILE. TSM:VERMONT-TSM1> ba db type=full devc=dbb_file scratch=yes ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=full devc=dbb_file scratch=yes ANR4559I Backup DB is in progress. ANR0984I Process 2 for DATABASE BACKUP started in the BACKGROUND at 11:47:17. ANR2280I Full database backup started as process 2.
358
7718Install_AIX.fm
TSM:VERMONT-TSM1> ANR0406I Session 1 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32834)). ANR8340I FILE volume /code/dbb_backups/45437242.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45437242.DBV. ANR1360I Output volume /code/dbb_backups/45437242.DBV opened (sequence number 1). ANR8341I End-of-volume reached for FILE volume /code/dbb_backups/45437242.DBV. ANR1362I Output volume /code/dbb_backups/45437242.DBV closed (full). ANR0514I Session 1 closed volume /code/dbb_backups/45437242.DBV. ANR8340I FILE volume /code/dbb_backups/45437299.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45437299.DBV. ANR1360I Output volume /code/dbb_backups/45437299.DBV opened (sequence number 2). ANR8341I End-of-volume reached for FILE volume /code/dbb_backups/45437299.DBV. ANR1362I Output volume /code/dbb_backups/45437299.DBV closed (full). ANR0514I Session 1 closed volume /code/dbb_backups/45437299.DBV. ANR8340I FILE volume /code/dbb_backups/45437353.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45437353.DBV. ANR1360I Output volume /code/dbb_backups/45437353.DBV opened (sequence number 3). ANR8341I End-of-volume reached for FILE volume /code/dbb_backups/45437353.DBV. ANR1362I Output volume /code/dbb_backups/45437353.DBV closed (full). ANR0514I Session 1 closed volume /code/dbb_backups/45437353.DBV. ANR8340I FILE volume /code/dbb_backups/45437411.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45437411.DBV. ANR1360I Output volume /code/dbb_backups/45437411.DBV opened (sequence number 4). ANR1361I Output volume /code/dbb_backups/45437411.DBV closed. ANR0514I Session 1 closed volume /code/dbb_backups/45437411.DBV. ANR0403I Session 1 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR0406I Session 2 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32835)). ANR8340I FILE volume /code/dbb_backups/45437452.DBV mounted. ANR0511I Session 2 opened output volume /code/dbb_backups/45437452.DBV. ANR1360I Output volume /code/dbb_backups/45437452.DBV opened (sequence number 1). ANR1361I Output volume /code/dbb_backups/45437452.DBV closed. ANR0514I Session 2 closed volume /code/dbb_backups/45437452.DBV. ANR0403I Session 2 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR4550I Full database backup (process 2) completed. ANR0985I Process 2 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 11:50:54. ba db devc=dbb_file type=full scratch=yes ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB devc=dbb_file type=full scratch=yes ANR4559I Backup DB is in progress. ANR0984I Process 1 for DATABASE BACKUP started in the BACKGROUND at 14:16:48. ANR2280I Full database backup started as process 1. TSM:VERMONT-TSM1> ANR0406I Session 1 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32839)). ANR8340I FILE volume /code/dbb_backups/45446210.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45446210.DBV. ANR1360I Output volume /code/dbb_backups/45446210.DBV opened (sequence number 1). ANR8341I End-of-volume reached for FILE volume /code/dbb_backups/45446210.DBV. ANR1362I Output volume /code/dbb_backups/45446210.DBV closed (full). ANR0514I Session 1 closed volume /code/dbb_backups/45446210.DBV.
359
7718Install_AIX.fm
ANR8340I FILE volume /code/dbb_backups/45446268.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45446268.DBV. ANR1360I Output volume /code/dbb_backups/45446268.DBV opened (sequence number 2). ANR8341I End-of-volume reached for FILE volume /code/dbb_backups/45446268.DBV. ANR1362I Output volume /code/dbb_backups/45446268.DBV closed (full). ANR0514I Session 1 closed volume /code/dbb_backups/45446268.DBV. ANR8340I FILE volume /code/dbb_backups/45446321.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45446321.DBV. ANR1360I Output volume /code/dbb_backups/45446321.DBV opened (sequence number 3). ANR8341I End-of-volume reached for FILE volume /code/dbb_backups/45446321.DBV. ANR1362I Output volume /code/dbb_backups/45446321.DBV closed (full). ANR0514I Session 1 closed volume /code/dbb_backups/45446321.DBV. ANR8340I FILE volume /code/dbb_backups/45446377.DBV mounted. ANR0511I Session 1 opened output volume /code/dbb_backups/45446377.DBV. ANR1360I Output volume /code/dbb_backups/45446377.DBV opened (sequence number 4). ANR1361I Output volume /code/dbb_backups/45446377.DBV closed. ANR0514I Session 1 closed volume /code/dbb_backups/45446377.DBV. ANR0403I Session 1 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR0406I Session 2 started for node $$_TSMDBMGR_$$ (DB2/AIX64) (Tcp/Ip loopback(32840)). ANR8340I FILE volume /code/dbb_backups/45446428.DBV mounted. ANR0511I Session 2 opened output volume /code/dbb_backups/45446428.DBV. ANR1360I Output volume /code/dbb_backups/45446428.DBV opened (sequence number 1). ANR1361I Output volume /code/dbb_backups/45446428.DBV closed. ANR0514I Session 2 closed volume /code/dbb_backups/45446428.DBV. ANR0403I Session 2 ended for node $$_TSMDBMGR_$$ (DB2/AIX64). ANR4550I Full database backup (process 1) completed. ANR0985I Process 1 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 14:20:30. ba volhistory ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP VOLHISTORY ANR2463I BACKUP VOLHISTORY: Server sequential volume history information was written to all configured history files. We have now worked around our exhausted log issue, with a few points to further emphasize; 1. Ensure your backup methodology and frequency aligns with your rate of new and update activity. 2. Ensure you position the database and logging file systems on technology which allows simple expansion. 3. Plan for archive log and archive failover growth space. 4. Beyond these directly related points, always ensure your volume history file is backed up following your database backups.
360
7718Install_Windows_1_October.fm
18
Chapter 18.
361
7718Install_Windows_1_October.fm
7718Install_Windows_1_October.fm
18.2.1 Hardware
Table 18-1 describes the hardware requirements for your Windows system. For further details, reference the Tivoli Storage manager for Windows, Installation Guide, Capacity Planning to assist you in understanding greater detail for disk planning. Check that the system memory meets the server requirements. If you plan to run multiple Tivoli Storage Manager instances of the V6.1 server on the system, each Tivoli Storage Manager Instance requires the memory listed for one server. Multiply the memory for one server by the number of Tivoli Storage Manager Instances planned for the system
Table 18-1 Hardware requirements for Tivoli Storage Manager V6.1 for Windows Type of hardware Hardware Disk space Hardware Requirements Intel Pentium compatible processor or multiprocessor-based computer At least 3 GB of free disk storage (for a default installation) Plan for more space for the databasel logs 200 MB partition size in the C:\ drive 200 MB temporary directory space 300 MB in the Tivoli Storage Manager Instance directory
Additional disk space is required for database and log files. The server is installed in the drive you select, and the database and logs can be installed in another drive
Memory At least 2 GB. A minimum of 4 GB for production servers. We recommend 8 GB.for normaly loaded servers
Software
Table 18-2 on page 363 describes the minimum software requirements for Tivoli Storage Manager V6.1 running on an Windows system. Note: We strongly recommend the Windows 32Bit to migrate into a 64Bit Windows
Table 18-2 Software requirements for Tivoli Storage Manager V6 for Windows Type of Software Operating system Minimum software requirements
363
7718Install_Windows_1_October.fm
At least one of the following communication protocols (installed by default with the current Windows operating systems):
Named Pipes TCP/IP Version 4 or Version 6 Shared Memory
Web browser
A Web browser to log in and use the console. The Web browser can be installed on the same or a separate system. The following browsers are supported: Microsoft Internet Explorer 6.0 SP1 Microsoft Internet Explorer 7.0 FireFox 1.5 FireFox 2.0 FireFox 3.0 Mozilla 1.7.8 Your browser must support the server code page. If your browser does not support the server code page, the windows might be unreadable. If your browser meets these requirements but does not correctly display a Tivoli Storage Manager Web-based interface, consider trying a different browser.
364
7718Install_Windows_1_October.fm
Composite Offering Installer (COI) infrastructure (COI) is a technology that was created by the Autonomic Computing Self-Configuration and Deployment offering team and was designed to assist IBM development teams in coordinating the deployment (installation and configuration) of a suite of products and components in both single-machine and multi-machine environments. The Deployment Engine The Deployment Engine is a collection of common software packaging, deployment, and configuration technologies from IBM Tivoli. The common technologies provide a standard way for application developers to package their software for deployment to a number of popular operating system and application environments. In addition, Deployment Engine can manage subsequent functionality and maintenance updates on the deployed software as performed by the administrator. InstallAnywhere InstallAnywhere is an application that creates wizard installers for multiple platforms where the options are showed in the installer. Payloads Tivoli Storage Manager native packages for server, license, device driver, storage agent, languages, and client application programming interfaces (APIs). DB2, WebSphere Application Server), Integrated Solution Console (ISC), and the Administration Center Web Application Archive (WAR) file.
365
7718Install_Windows_1_October.fm
It is advisble to install Tivoli Storage Manager Administration Center and Tivoli Storage Manager reporting and monitoring on the same server. Note: The current restriction that is documented in the Tivoli Storage Manager publications for the installation of other DB2 versions (or applications that deploy and use DB2) on the same Windows system as a Tivoli Storage Manager V6 server is still in place and not affected by the support discussed here. Similar support for Windows systems is currently being evaluated. Assuming that the testing and evaluation do not uncover any issues to prevent it, the target is to remove this restriction with a follow-on TECHNOTE towards the end of third quarter of 2009 or in fourth quarter of 2009. Table 18-3 describes all of the components.
Table 18-3 Tivoli Storage Manager components
Description
Additional information
This component includes the Tivoli Storage Manager database, management console, client API, and tools to help you configure and manage Tivoli Storage Manager. Each language pack (one for each language) contains language-specific information for the server and the management console. This component includes support for all Tivoli Storage Manager licensed features. After you install this package, you must configure the licenses that you have purchased. (Use complete sentences) This component extends Tivoli Storage Manager media management capability. The Tivoli Storage Manager device driver is generally preferred for use with the Tivoli Storage Manager server. It is required for use with automated library devices and optical disk devices, unless you are using Windows Removable Storage Manager to manage the media.
Refer to the Tivoli Storage Manager server overview in the Administrators Guide. Refer to Other publications on page 633 for the exact book title and order number for your platform.
Licenses (REQUIRED)
Refer to the chapter on managing server operations in the Administrators Guide Refer to Other publications on page 633 for the exact book title and order number for your platform. Refer to the chapter on adding devices in the Administrators Guide. A list of devices supported by this driver is available from the Tivoli Storage Manager Web site at: http://www.ibm.com/software /sysmgmt/products/support/I BMTivoliStorageManager.html
366
7718Install_Windows_1_October.fm
Note: We highly recommend that you read the readme.first file to see the changes in the Tivoli Storage Manager version you are about to install, the hardware and software prerequisites, and any additional installation steps that might be needed. Using the Tivoli Storage Manager installation software, you can install the following components: Tivoli Storage Manager server Tivoli Storage Manager server languages Tivoli Storage Manager license Tivoli Storage Manager device driver Tivoli Storage Manager storage agent Tivoli Storage Manager Administration Center
NoteThe Tivoli Storage Manager client Application Programming Interface (API) is automatically installed when you select the server component
The following steps install Tivoli Storage Manager components. 1. If you are installing the products using the Tivoli Storage Manager DVD, complete the following steps: Log on as an administrator. Insert the Tivoli Storage Manager server DVD. If autorun is on, the DVD browser window opens. If autorun is off, use Windows Explorer to go to the DVD drive, double-click the DVD, and then double-click install.exe. To access Windows Explorer, go to Start Programs Accessories or right-click the Start button. The Tivoli Storage Manager server DVD browser window opens. 2. If you downloaded the executable file from Passport Advantage, complete the following steps: Change to the directory where you placed the executable file. Either double-click the following executable file or enter the following command from the Windowscommand line to extract the installation files. The extracted files will go into your current directory. - 6.1.0.0-TIV-TSMALL-platform.exe where platform denotes the operating system.
367
7718Install_Windows_1_October.fm
There are three basic ways to install Tivoli Storage Manager. We strongly recommend the use of the Wizard that will do all the work for you. Installation wizard Installing Tivoli Storage Manager using the installation wizard (see 18.6, Installation wizard install Command-line console wizard see Command-line console wizard on page 376. Silent mode see Silent mode installation on page 381.
The Welcome screen is shown in Figure 18-2 on page 369. Review the information and click Next to continue.
368
7718Install_Windows_1_October.fm
Next, review the Software License Agreement. You must accept the license agreement to proceed. Select I accept both the IBM and non-IBM terms (see Figure 18-3 on page 370). Click Next to continue.
369
7718Install_Windows_1_October.fm
The next step is to choose the installation folder. The path is by default C:\Program File\Tivoli\TSM Click Next to proceed (see Figure 18-4 on page 371).
370
7718Install_Windows_1_October.fm
Here we select the components to install. There is no default so you must make a selection or you will receive an error message and be returned to the components page. If you select the Administration Center component, you are prompted for a user name and password. You will use these later to log onto the Integrated Solutions Console and Administration Center. Note: If you previously installed a server, ensure that you select the same directory when you install a language pack, license, or device driver. If you previously installed a storage agent, ensure that you select the same directory if you return to install a device driver. A server and a storage agent cannot be installed on the same workstation. We selected the Tivoli Storage Manager Server and License components as shown in Figure 18-5 on page 372. Click Next to proceed.
371
7718Install_Windows_1_October.fm
The DB2 Version 9.5 is installed during the Tivoli Storage Manager server installation. You are prompted to create and confirm a password. Defaults are provided for the DB2 user name and database name. The password must contain an @ or # character if we are installing on Windows Server 2008. An empty database instance called DB2TSM is created during the installation. This DB2TSM database instance is not used by Tivoli Storage Manager (see Figure 18-6 on page 373) click Next to continue.
372
7718Install_Windows_1_October.fm
The install wizard now configures the IBM Autonomic Deployment Engine on the local machine as shown in Figure 18-7 on page 373. Click Next to proceed.
373
7718Install_Windows_1_October.fm
Figure 18-8 on page 374 shows the summary of the Pre-Installation tasks. You can see which components you choose to install, where you have defined the instance server1 folder and also the diskspace information for the installation taget. Click Next to proceed with the Tivoli Storage Manager installation.
Figure 18-9 on page 375 shows the Tivoli Storage Manager installation progress and the V6.1 Server is in the install phase.
374
7718Install_Windows_1_October.fm
Figure 18-10 on page 376 shows the Tivoli Storage Manager installation completed. At the end of the installation, a message is displayed on the summary page that Tivoli Storage Manager successfully installed and a summary is provided. If there were any errors during the installation, another summary page lists the errors and directs you to an error log file. Fix the errors before continuing. The installation log is stored in the following location: The directory that was chosen for installation (look for the files log.txt and logs.zip). See C:\Program Files\Tivoli\TSM\log.txt for details. Click Next to proceed
375
7718Install_Windows_1_October.fm
Here we continue to either configure a new server instance or upgrade an existing server instance. To configure a new server instance, choose one of the following methods: Log in as an administrator and open the local new-instance wizard, dsmicfgx, located in the server installation directory. Log on to a Version 6.1 Tivoli Storage Manager Administration Center and start the Create New Instance wizard. Configure the new instance manually. See the Tivoli Storage Manager Information Center, or the IBM Tivoli Storage Manager for Windows Installation Guide V6.1, GC23-9785. To upgrade an existing server instance, log in as an administrator and start the upgrade wizard, dsmupgdx.exe file, located in the server installation directory. You can also upgrade a server manually. See the Tivoli Storage Manager Information Center, or the IBM Tivoli Storage Manager Server Upgrade Guide, SC23-9554. For more information about any of these tasks, see the Tivoli Storage Manager Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6
376
7718Install_Windows_1_October.fm
To start the wizard without saving your responses, enter the following command: install.exe -i console To start the wizard and save your responses, enter the following command, and specify the -r option: install.exe -i console -r C:\response.rsp Select the language for your installation and follow the prompts. Select the components that you want to install (server, languages, licenses, device driver, storage agent, and Administration Center). There is no default so you must make a selection or you will receive an error message. Here we show you a basic Tivoli Storage Manager default installation and configuration and provide images of the Console Mode wizard interface. From the directory where you have downloaded the install package submit install.exe -i console to start the installation. Example 18-1 shows the starting screen where we have to choose the apropriate Locale for the installation.
Example 18-1 Here we choose the Locale Language
(Brasil)
Example 18-2 on page 377 shows the Welcome Screen,. Press ENTER to move to the next screen.
Example 18-2 Windows Command Line Installation: Welcome Screen
Tivoli Storage Manager (created with InstallAnywhere by Macrovision) ------------------------------------------------------------------------------=============================================================================== Tivoli Storage Manager Install Welcome Tivoli Storage Manager 6.1 Licensed Materials - Property of IBM Corp. (c) IBM Corporation and other(s) 1993, 2008. All rights reserved. US Government Users Restricted Rights -Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. It is strongly recommended that you quit all programs before continuing with this installation. PRESS <ENTER> TO CONTINUE:
377
7718Install_Windows_1_October.fm
Next step will be to review the Software License Agreement, You must accept the license agreement to proceed. Enter 1 as shown in Example 18-3.
Example 18-3 Windows Command Line Installation: Review License Information
International Program License Agreement Part 1 - General Terms BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING THE PROGRAM YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON, COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS, - DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE PROGRAM; AND - PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM YOU ACQUIRED IT TO OBTAIN A REFUND OF THE AMOUNT YOU PAID. IF YOU DOWNLOADED THE PROGRAM, CONTACT THE PARTY FROM WHOM YOU ACQUIRED IT. Press Enter to continue viewing the license agreement, or enter "1" to accept the agreement, "2" to decline it, "3" to print it, "4" to read non-IBM terms, or "99" to go back to the previous screen.: 1 Here we decide to install the Tivoli Storage Manager Server and the License components in the default folder. Example 18-4 shows the related steps.
Example 18-4 Windows Command Line Installation: Install Folder and Component Selection
Choose Install Folder --------------------Where would you like to install? Default Install Folder: C:\Program Files\Tivoli\TSM ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : =============================================================================== Component Selection ------------------Select the components to install. 123456Tivoli Tivoli Tivoli Tivoli Tivoli Tivoli Storage Storage Storage Storage Storage Storage Manager Manager Manager Manager Manager Manager Server Server Languages License Device Driver Storage Agent Administration Center
378
7718Install_Windows_1_October.fm
1,3
Example 18-5 shows the parameters to specify during database server instance creation. We choose to use the default user ID, db2user1, and the default database name of DB2. For the password use either the Tivoli Storage Manager DB2 administrative -user ID and password, or a new user ID and password that you create now.
Example 18-5 Windows Command Line Installation: Create database server instance
DB2 Enterprise Server Edition Enter the following information to create a DB2 database for your server instance. Use either the Tivoli Storage Manager DB2 administrative-user ID and password, or a new user ID and password that you create now. DB2 administrative-user ID: (DEFAULT: db2user1): =============================================================================== DB2 Password::********* =============================================================================== Verify Password::********* Database name: (DEFAULT: DB2): Example 18-6 shows the messages submitted during deployment engine initialization. For easier readability we removed some lines. Once the engine is initialized we press ENTER to move on with the installation.
Example 18-6 Windows Command Line Installation: Deployment Engine Initialization
Deployment Engine Initialization -------------------------------Please Wait .. completed: 1 ; total: 19 .. lines removed .. completed: 19 ; total: 19 Completed. Pre-Installation Summary: Please Review the Following Before Continuing: Product Name: Tivoli Storage Manager Install Folder: C:\Program Files\Tivoli\TSM Components: TSM Server,DB2 9.5,TSM Client API,TSM License Disk Space Information (for Installation Target): Required: 1 363 977 792 bytes
Chapter 18. Installation of Tivoli Storage Manager V6.1 on Windows
379
7718Install_Windows_1_October.fm
Next you will see a message indicating the install is progressing and finally complete (see Example 18-7 on page 380). You are provided a summary of the components that were installed.
Example 18-7 Windows Command Line Installation:
Installing... [==================|==================|==================|==================] [------------------|------------------|------------------|------------------] =============================================================================== Installation Complete --------------------See C:\Program Files\Tivoli\TSM\log.txt for details. The TSM DB2 TSM following components were successfully installed: Server 9.5 License
To continue, either configure a new server instance or upgrade an existing server instance. To configure a new server instance, choose one of the following methods: Log in as root user or administrator and open the local new-instance wizard, dsmicfgx, located in the server installation directory. Log on to a Version 6.1 Tivoli Storage Manager Administration Center and start the Create New Instance wizard. Configure the new instance manually. See the Tivoli Storage Manager Information Center, or the Installation Guide. To upgrade an existing server instance, log in as root user or administrator and start the upgrade wizard, dsmupgdx, located in the server installation directory. You can also upgrade a server manually. See the Tivoli Storage Manager Information Center, or the Server Upgrade Guide. For more information about any of these tasks, see the Tivoli Storage Manager Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6 PRESS <ENTER> TO EXIT THE INSTALLER
You have the choices of continue, either configure a new server instance or upgrade an existing server instance. To configure a new server instance, choose one of the following methods:
380
7718Install_Windows_1_October.fm
Log in as an administrator and open the local new-instance wizard, dsmicfgx.exe, located in the server installation directory. Log on to a Version 6.1 Tivoli Storage Manager Administration Center and start the Create New Instance wizard. Configure the new instance manually. See the Tivoli Storage Manager Information Center, or the Installation Guide. To upgrade an existing server instance, log in as root user or administrator and start the upgrade wizard, dsmupgdx, located in the server installation directory. You can also upgrade a server manually. See the Tivoli Storage Manager Information Center, or the Tivoli Storage Manager Server Upgrade Guide, SC23-9554 For more information about any of these tasks, see the Tivoli Storage Manager Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6
install.exe -i silent -DLICENSE_ACCEPTED=true -DINSTALL_SERVER=1 -DINSTALL_SERVER_LANGUAGES=0 -DINSTALL_LICENSE=1 -DINSTALL_DEVICES=0 -DINSTALL_STAGENT=0 -DINSTALL_ADMINCENTER=0 -DDB2_USER=db2user1 -DDB2_PW=db2user1 -DDB2_NAME=DB2 -DUSER_INSTALL_DIR=i"C:\Program Files\Tivoli\TSM"
Note: It is important to use brackets if you have spaces in the path name.
install.exe -i silent -DLICENSE_ACCEPTED=true -DINSTALL_SERVER=1 -DINSTALL_SERVER_LANGUAGES=0 -DINSTALL_LICENSE=1 -DINSTALL_DEVICES=0 -DINSTALL_STAGENT=0 -DINSTALL_ADMINCENTER=0 -DDB2_USER=db2user1 -DDB2_PW=db2user1 -DDB2_NAME=DB2 -DUSER_INSTALL_DIR=C:\Program Files\Tivoli\TSM" -r C:\response.rsp
381
7718Install_Windows_1_October.fm
install.exe -i silent -DLICENSE_ACCEPTED=true -f response_file where the response_file is the full directory path to a file that you previously created in the Tivoli Storage Manager installation process. The response file contains variables you selected in a prior installation. If you include LICENSE_ACCEPTED=true in the response file manually, then issue this command: install.exe -i silent -f response_file
Batch script
To run the silent installation so that you can see the progress of the installation, create a batch script by completing the following steps: 1. Create a file and name it install.bat. The file name must end with .bat, not bat.txt. 2. Choose an installation option (with or without a response file) and enter the command into the install.bat file and save it.
Example 18-11 Silent install using batch script
For example: install.exe -i silent -DLICENSE_ACCEPTED=true -f response_file 3. Open a command prompt to run the batch file. Issue the command: install.bat 4. 4. After the installation is complete, issue the following command to retrieve the return code: echo %ERRORLEVEL% Example 18-12 shows we have created an install.bat file with the required information for the install.bat file.
Example 18-12 Silent install with batch script using parameters
install.exe -i silent -DLICENSE_ACCEPTED=true -DINSTALL_SERVER=1 -DINSTALL_SERVER_LANGUAGES=0 -DINSTALL_LICENSE=1 -DINSTALL_DEVICES=0 -DINSTALL_STAGENT=0 -DINSTALL_ADMINCENTER=0 -DDB2_USER=db2user1 -DDB2_PW=db2user1 -DDB2_NAME=DB2 -DUSER_INSTALL_DIR="C:\Program Files\Tivoli\TSM" -r C:\response.rsp Here we show you a basic Tivoli Storage Manager default installation and configuration and provide images of Silent Mode interface using the install.bat file. When using the echo %ERRORLEVEL% command you will get an returncode and you are returned to the command prompt as shown in Example 18-13.
Example 18-13 Tivoli Storage Manager Silent Installation
C:\TSM_images\6.1_Server>install.bat C:\TSM_images\6.1_Server>install.exe -i silent -r C:\response.rsp -DLICENSE_ACCE PTED=true -DINSTALL_SERVER=1 -DINSTALL_SERVER_LANGUAGES=0 -DINSTALL_LICENSE=1 -D INSTALL_DEVICES=0 -DINSTALL_STAGENT=0 -DINSTALL_ADMINCENTER=0 -DDB2_USER=db2user 1 -DDB2_PW=db2user1 -DDB2_NAME=DB2 -DUSER_INSTALL_DIR="C:\Program Files\Tivoli\T SM" C:\TSM_images\6.1_Server>echo %ERRORLEVEL% 0
382
7718Install_Windows_1_October.fm
C:\TSM_images\6.1_Server>
Example 18-13 shows we got return code 0 and the silent installation was successfull. For return codes see Debugging on page 409.
383
7718Install_Windows_1_October.fm
You use this user ID when you create the server instance in a later step. Identify the user account that will own the Tivoli Storage Manager server instance. When the server is started as a Windows service, this is the account that the service will log on to. The user account must have administrative authority on the system. One user account can own more than one server instance. If you have multiple servers on one system there is no need to run each server with a different user account. You can have one user ID associated with multiple servers on a Windows system. Check the directories. For all directories that were created for the server instance, ensure that the user ID for the server instance has read/write access. The directories to check include the instance directory and all database and log directories. In the Microsoft Management Console we can see which groups the user ID belong.
384
7718Install_Windows_1_October.fm
Here we see the Instance Configuration Wizard Introduction window. Click Next to continue as shown in Figure 18-12 on page 386.
385
7718Install_Windows_1_October.fm
The instance user ID is the ID that is used by the database manager to read and write the database and log files. This user ID must have write permission to all directories containing database and log files. The instance user ID is not necessarily the same user ID that you will use to run the Tivoli Storage Manager server.The user ID must already exist on the system, and must not be disabled or locked. The primary group of the specified user will become the administrative group of the database. Any other users in this group can manage the database (including starting and stopping the database manager). If you want to restrict this access, you should create a separate group for the instance user ID, so that only the instance user ID can manage this database. To validate the user ID and password, a connection will be made to the local system using either SSH, RSH, or REXEC. You must enable one of these protocols to allow the wizard to proceed. To validate the user ID and password, a connection will be made to the local system using either SSH, RSH, REXEC, or SMB protocols. SMB is the interface used by File and Print Sharing (also known as CIFS). In order to use the SMB protocol, you must make sure File and Print Sharing is enabled, and that port 445 is not blocked by your firewall. Note: netsh firewall set service type = fileandprint mode = enable Additionally, if you are running on Windows Server 2008 or Windows Vista, you may need to disable User Account Control (at least while running this wizard). If you choose not to disable
386
7718Install_Windows_1_October.fm
User Account Conrol, you must make sure one of the other protocols is configured to allow the wizard to proceed. Here we manually specify the Tivoli Storage Manager Instance name of the new Instance and specify the user ID and password under which the database manager for this Instance, Click Next to continue (see Figure 18-13 on page 387).
Figure 18-13 IBM Tivoli Storage Manager Instance Configuration Wizard - Instance User ID
Set the path to the Instance Directory that stores all the server configuration such as the server options file, trace files and other files specific to this instance, Click Choose and browse to the installation folder. Here we manually create the Server1 folder. Click Next to continue (see Figure 18-14 on page 388).
387
7718Install_Windows_1_October.fm
Figure 18-14 IBM Tivoli Storage Manager Instance Configuration Wizard - Instance Directory
There are two ways to specify the database directories: Create a temporary file, and place each database directory on its own line in the file, then specify the location of the file in the top field, or specify each database directory directly in the bottom field, one directory per line. Here we have specified the text file containing a list of database directorories, Click Next to continue.
388
7718Install_Windows_1_October.fm
Figure 18-15 IBM Tivoli Storage Manager Instance Configuration Wizard - Database Directories file
The Tivoli Storage Manager database is stored in a series of directories managed by the database manager. To improve data throughput, specify a large number of directories to allow the database manager to spread the workload over multiple disks. Each database directory must be empty, and, for maximum performance, should reside on its own dedicated disk. Here we have choosed to specify a list of four directories per line to use for the Tivoli Storage Manager database. Note that you can use up to 128 directories for the instance. Click Next to continue (see Figure 18-16 on page 390).
389
7718Install_Windows_1_October.fm
Figure 18-16 IBM Tivoli Storage Manager Instance Configuration Wizard - Database Directory
So we now specify the directories for the database and log volumes. The active log directory contains all transactions currently in progress on the server. If the system crashes or the server stops, the active log is all that is required to restart the server. The active log is broken up into files. After all transactions in a log file are completed, the log file is copied to an archive log directory. If a log file cannot be copied to the primary archive log directory, it is copied to the ArchiveLogFailover log directory, if specified. If a log file cannot be copied to either log directory, it remains in the active directory. If the active log fills up, transactions will fail. Therefore, ensure that the archive log directories are online with sufficient space to hold the log files. Logs in the archive log directories can be copied to another location, but these logs must be returned to the archive directory to perform a database restore operation. The mirror log directory contains the same contents as the active log directory, and is used for redundancy in case of disk failure. If your active log directory resides on a disk that is already mirrored or has other RAID protection, you might not need to specify a mirror log directory. In the Recovery Log Directory window here we have shorten the names for the recoverylogs: ActiveLog as Actlog ArchiveLog as Archlog ActiveLogMirror as Actlogm ArchiveLogFailover as Archlogf. 390
Tivoli Storage Manager V6.1 Technical Guide
7718Install_Windows_1_October.fm
Figure 18-17 IBM Tivoli Storage Manager Instance Configuration Wizard- Recovery Log Directories
We specify the server name and select the language. Click Next to continue (see Figure 18-18 on page 392).
391
7718Install_Windows_1_October.fm
Figure 18-18 IBM Tivoli Storage Manager Instance Configuration Wizard - Server Information
The administrator name must be 1-64 characters and must contain only alphanumeric characters. The adminstrator name is not case sensitive. The administrator password must be 4-64 characters, contain only alphanumeric characters, and must contain at least 1 numeral. Click Next to continue (see Figure 18-19 on page 393).
392
7718Install_Windows_1_October.fm
Figure 18-19 IBM Tivoli Storage Manager Instance Configuration Wizard - Administrator Credentials
Tivoli Storage Manager requires TCP/IP communications for client or administrator access. You must specify a port for each, but both ports may be the same. In addition to TCP/IP, you can also select Shared Memory Communication. This uses a TCP/IP port for initial contact, and the port specified must be different than the client port or the administrator port. Click Next to continue (see Figure 18-20 on page 394).
393
7718Install_Windows_1_October.fm
Figure 18-20 IBM Tivoli Storage Manager Instance Configuration Wizard - Server Communication
Here we have configuration summary where we can see the user ID we have created, where we have the instance directory, the four database containers we have defined, and the log files directories Click Next to continue (see Figure 18-21 on page 395).
394
7718Install_Windows_1_October.fm
Figure 18-21 IBM Tivoli Storage Manager Instance Configuration Wizard - Configuration Summary
The intance is now being configured. Configuration will take several minutes to complete. The progress of the configuration is shown in Figure 18-22 on page 396.
395
7718Install_Windows_1_October.fm
Figure 18-22 IBM Tivoli Storage Manager Instance Configuration Wizard - Configure Instance
During the server installation format processing for the Tivoli Storage Manager V6.1instance you will see that the server performs a backup of the database. This can be seen by the messages shown in Figure 18-23 on page 397. ANR2976I Offline DB backup for database TSMDB1 started. ANR2974I Offline DB backup for database TSMDB1 completed successfully. Note: This initial backup is required by DB2 in order for Tivoli Storage Manager to set the recovery log processing mode to ROLLFORWARD. At this point, this database backup only contains the server schema Data Definition Language (DDL). This database backup is performed to a file in the local filesystem. This database backup is subsequently deleted by Tivoli Storage Manager since it only contains the server schema definitions which can be recreated by Tivoli Storage Manager anyway After completing the installation and configuration of the Tivoli Storage Manager server, it is recommended that a FULL database backup be performed. This database backup and any subsequent database backups will be tracked in the server volume history, as expected, and used as part of the server Disaster Recovery Manager (DRM) processing and such.
396
7718Install_Windows_1_October.fm
Figure 18-23 IBM Tivoli Storage Manager Instance Configuration Wizard - database backup
The Tivoli Storage Manager Server1 instance is now configured. Click Next to continue (see Figure 18-24 on page 398).
397
7718Install_Windows_1_October.fm
Figure 18-24 IBM Tivoli Storage Manager Instance Configuration Wizard - configuration complete
Here we have finished the installation and the server is now up and running. Log in to the admin center or through the admin command line to set up storage pools and policys (see Figure 18-25 on page 399).
398
7718Install_Windows_1_October.fm
Figure 18-25 IBM Tivoli Storage Manager Instance Configuration Wizard- Configuration Successful
Set up your directories and for the Tivoli Storage Manager instance
We use the mkdir command to create the directories using the commands in Example 18-15.
Example 18-15 Manually creating required directories
mkdir e:\tsminst1\dbdir001 mkdir f:\tsminst1\dbdir002 mkdir g:\tsminst1\dbdir003 mkdir h:\tsminst1\dbdir004 mkdir i:\tsminst1\actlog mkdir j:\tsminst1\actlogm
Chapter 18. Installation of Tivoli Storage Manager V6.1 on Windows
399
7718Install_Windows_1_October.fm
mkdir k:\tsminst1\archlog mkdir l:\tsminst1\archlogf In the Microsoft Management Console you can see which groups the user ID tsm1 belongs to as shown in Figure 18-26 on page 400. This is the user ID under which the database manager for the instance runs.
400
7718Install_Windows_1_October.fm
5. Volumes for DEVTYPE=FILE storage pools, if the directory for the device class is not fully specified, or not fully qualified 6. User exits 7. Trace output (if not fully qualified)
401
7718Install_Windows_1_October.fm
Note: The installation program creates a set of registry keys. One of these keys points to the directory where a default server, named SERVER1, is created. To install an additional server, create a new directory and use the DSMSERV FORMAT utility, with the -k parameter, from that directory. That directory becomes the location of the server. The registry tracks the installed servers.
Here is one example to FORMAT a database with the default ActiveLog size 2GB database logs.
Issue the DSMSERV FORMAT command to start the format of the database (see Example 18-16). Example 18-16 Database format
dsmserv -k tsminst1 format dbdir=e:\tsm1\dbdir001,f:\tsm1\dbdir002,g:\tsm1\dbdir003,h:\tsm1\dbdir004 activelogdir=i:\tsm1\actlog archlogdir=k:\tsm1\archlog mirrorlogdir=j:\tsm1\actlogm archfailoverlogdir=l:\tsm1\archlogf The output from the DSMSERV FORMAT command is shown in Example 18-17.
Example 18-17 DSMSERV FORMAT command output
ANR0900I Processing options file C:\Program Files\Tivoli\TSM\tsminst1\dsmserv.opt ANR7800I DSMSERV generated at 16:44:45 on Mar 13 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2008. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I ANR0152I ANR0152I ANR1380I ANR0992I ANR0369I ANR2976I ANR2974I The ICC support module has been loaded. Database manager successfully started. Database manager successfully started. The buffer pool monitor switch is enabled. Server's database formatting complete. Stopping the database manager because of a server shutdown. Offline DB backup for database TSMDB1 started. Offline DB backup for database TSMDB1 completed successfully.
402
7718Install_Windows_1_October.fm
In the following commands, the examples use d:\server1 for the database instance and C:\Program Files\Tivoli\TSM\server1 for the Tivoli Storage Manager instance directory. Here we create the tsmdbmgr.env file in the C:\Program Files\Tivoli\TSM\tsminst1 directory with the contents in Example 18-18.
Example 18-18 Contents of tsmdbmgr.env file
DSMI_CONFIG=C:\PROGRA~1\Tivoli\TSM\tsminst1\tsmdbmgr.opt DSMI_LOG=C:\PROGRA~1\Tivoli\TSM\tsminst1 We then set the DSMI_ api environment-variable configuration for the database instance. Open a DB2 command window. One method of doing this is by going to the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage Manager in a different location, go to the db2\bin subdirectory in your main installation directory. Issue this command: db2cmd A new window opens where you then issue the command: db2set -i tsminst1 DB2_VENDOR_INI=C:\Program Files\Tivoli\TSM\tsminst1\tsmdbmgr.env Create the tsmdbmgr.opt file in the C:\Program Files\Tivoli\TSM\tsminst1 directory with the contents in Example 18-19.
Example 18-19 tsmdbmgr.opt file
nodename $$_TSMDBMGR_$$ commmethod tcpip tcpserveraddr localhost tcpport 1500 passwordaccess generate errorlogname C:\Program Files\Tivoli\TSM\tsminst1\TSMDBMGR_TSMSERVER1.log Then we stop and start the database instance: Open a DB2 command window. One method of doing this is by going to the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage Manager in a different location, go to the db2\bin subdirectory in your main installation directory. Issue the commands in Example 18-20 to set the database instance, stop DB2, and then start DB2.
Example 18-20 Stop and start the database instance
db2cmd SET DB2INSTANCE=tsminst1 db2stop db2start Issue the commands in Example 18-21 to set the API environmental variable.
403
7718Install_Windows_1_October.fm
C:\Program Files\Tivoli\TSM\db2\BIN>set DSMI_CONFIG=C:\Program Files\Tivoli\TSM\tsminst1\tsmdbmgr.opt C:\Program Files\Tivoli\TSM\db2\BIN>"C:\Program Files\Tivoli\TSM\server\dsmsutil UPDATEPW /NODE:$$_TSMDBMGR_$$ /PASSWORD:TSMDBMGR /VALIDATE:NO
Here is the result of the command. Note that we have updated the password in the registry (see Example 18-22).
Example 18-22
TSM Windows NT Client Service Configuration Utility Command Line Interface - Version 6, Release 1, Level 0.0 1027FB (C) Copyright IBM Corporation, 1990, 2008, All Rights Reserved. Last Updated Oct 28 2008 TSM Api Version 6.1.0 Command: Update Registry Password Machine: TSM-1(Local Machine) The Registry password for node $$_TSMDBMGR_$$ has been updated
404
7718Install_Windows_1_October.fm
server, issue the halt command from the Tivoli Storage Manager command prompt. The server console stops. Note: If you start the Tivoli Storage Manager server as a service, after you stop it, the database service continues to run.
Registering licenses
Immediately register any Tivoli Storage Manager licensed functions that you purchase so you do not lose any data after you start server operations, such as backing up your data. Use the REGISTER LICENSE command for this task.
405
7718Install_Windows_1_October.fm
TCPPORT The server TCP/IP port address. The default value is 1500. TCPWINDOWSIZE Specifies the size of the TCP/IP buffer that is used when sending or receiving data. The window size that is used in a session is the smaller of the server and client window sizes. Larger window sizes use additional memory but can improve performance. To use the default window size for the operating system, specify zero. TCPNODELAY 406
Tivoli Storage Manager V6.1 Technical Guide
7718Install_Windows_1_October.fm
Specifies whether or not the server sends small messages or lets TCP/IP buffer the messages. Sending small messages can improve throughput but increases the number of packets sent over the network. Specify YES to send small messages or NO to let TCP/IP buffer them. The default is YES. TCPADMINPORT Specifies the port number on which the server TCP/IP communication driver is to wait for requests other than client sessions. The default value is 1500. SSLTCPPORT (SSL-only) Specifies the Secure Sockets Layer (SSL) port number on which the server TCP/IP communication driver waits for requests for SSL-enabled sessions for the command-line backup-archive client and the command-line administrative client. SSLTCPADMINPORT Specifies the port address on which the server TCP/IP communication driver waits for requests for SSL-enabled sessions for the command-line administrative client. The following is an example of a list of TCP/IP options you can use to set up your system. commmethod tcpip tcpport 1500 tcpwindowsize 63 tcpnodelay yes
407
7718Install_Windows_1_October.fm
408
7718Install_Windows_1_October.fm
Backup operations that occur over relatively slower connections cause transactions that take a longer time to complete. The transactions use space in the active log for a longer period of time. If the server is handling transactions with a wide variety of characteristics, the space that is used for the active log might go up and down by a large amount over time. For such a server, you might need to ensure that the active log typically has a smaller percentage of its space used. The extra space allows the active log to grow for transactions that take a very long time to complete, for example.
18.13 Debugging
In cases where we need to investigate log messages we have several files to find additional information.
409
7718Install_Windows_1_October.fm
MachinePlan_localhost_[INSTALL_0414_22.35].log DB2 step logs coi\plan\install\MachinePlan_localhost\00002_DB2_9.5\DB2_9.5.log coi\plan\tmp: Administration Center step logs coi\plan\install\MachinePlan_localhost\00003_TSM_AdminCenter\logs: Deployment Engine Logs C:\Program Files\IBM\Common\acsi\logs\<system user>
Problem determination
If the Deployment Engine is not working properly and is causing the Tivoli Storage Manager installs to fail, follow these instructions. 1) Check log.txt for the following entry return code SI_UP_TO_DATE Windows: (Install directory)\log.txt Unix: /var/tivoli/tsm/log.txt 2) If there is a problem with the Deployment Engine, ensure the following files do not exist: Windows: (Install directory)\\_uninst\plan\inventory\inventoryCheck.properties Unix: /opt/tivoli/tsm/_uninst/plan/inventory/inventoryCheck.properties
410
7718Install_Windows_1_October.fm
411
7718Install_Windows_1_October.fm
2001 - The installation failed the authorization check, may indicate an expired version. 2002 - The installation failed a rules check. A rule placed on the installer itself failed. 2003 - An unresolved dependency in silent mode caused the installer to exit. 2004 - The installation failed because not enough disk space was detected during the execution of the Install action. 2005 - The installation failed while trying to install on a Windows 64-bit system, but installation did not include support for Windows 64-bit systems. 2006 - The installation failed because it was launched in a UI mode that is not supported by this installer. 3000 - Unhandled error specific to a launcher. 3001 - The installation failed due to an error specific to the lax.main.class property. 3002 - The installation failed due to an error specific to the lax.main.method property. 3003 - The installation was unable to access the method specified in the lax.main.method property. 3004 - The installation failed due to an exception error caused by the lax.main.method property. 3005 - The installation failed because no value was assigned to the lax.application.name property. 3006 - The installation was unable to access the value assigned to the lax.nl.java.launcher.main.class property. 3007 - The installation failed due to an error specific to the lax.nl.java.launcher.main.class property. 3008 - The installation failed due to an error specific to the lax.nl.java.launcher.main.method property. 3009 - The installation was unable to access the method specified in the lax.nl.launcher.java.main.method property. 4000 - A Java executable could not be found at the directory specified by the java.home system property. 4001 - An incorrect path to the installer jar caused the relauncher to launch incorrectly.
412
7718Install_Windows_ba_client_8_Aug.fm
19
Chapter 19.
413
7718Install_Windows_ba_client_8_Aug.fm
414
7718Install_Windows_ba_client_8_Aug.fm
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 You can use the adlocation option with the query adobjects or restore adobjects commands to indicate whether the Active Directory objects are to be queried or restored from the local Active Directory Deleted Objects container or from a system state backup on the Tivoli Storage Manager server. The adlocation option is only valid for Windows Server 2003 and Windows Server 2008 clients only. The Tivoli Storage Manager client API does not support this option. Query Adobjects Use the query adobjects command to display information about the deleted objects that are located on the local Active Directory domain. On Windows Server 2008 clients, Active Directory object information can also be displayed from full system-state backups on the server. This command is valid for the Windows Server 2003 and Windows Server 2008 clients only 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. 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. 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. Mac OS X-specific information The Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation and User's Guide includes the Mac OS X-specific information. The Tivoli Storage Manager for Mac OS X Backup-Archive Client now supports the NLS languages supported by the Tivoli Storage Manager. 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 64bit binaries
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
415
7718Install_Windows_ba_client_8_Aug.fm
The client packages for Linux on POWER, Linux zSeries, and one of the AIX clients contain 64-bit binaries. 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.
416
7718Install_Windows_ba_client_8_Aug.fm
The stagingdirectory option defines the location where the client can keep any data it generates in order to perform its operations. The data is deleted when processing is complete. Vmbackdir Use the vmbackdir option with the backup VM command to specify the location that VMware Consolidated Backup will use to export and copy the full VM files before Tivoli Storage Manager sends them to the server when performing a full VM backup. Vmbacknodelete Use the vmbacknodelete option with the backup VM command to specify that the full VM backup files copied to the backup proxy should not be deleted at the end of the backup. Vmbackuptype Use the vmbackuptype option with the backup VM or query VM commands to specify the type of VMware backup to complete on the backup proxy. You can specify either a file-level backup or a full VM backup
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
417
7718Install_Windows_ba_client_8_Aug.fm
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 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. You cannot perform the following operations: Generate a backup set with system state data. If you use the system state data backed up with the Tivoli Storage Manager Version 5.5 client to generate a backup set, you must be connected to a Tivoli Storage Manager Version 5.3.6 or later, Version 5.4.1 or later, or Version 5.5.0 server. Restore system state and system services file spaces that were backed up by a Tivoli Storage Manager Version 5.4.x or earlier client. Use a Tivoli Storage Manager Client prior to Version 6.1 to restore system state backed up by a Tivoli Storage Manager Client Version 6.1 or above. The Windows client can be regressed from Tivoli Storage Manager Version 5.5 to Tivoli Storage Manager Version 5.4 without any impact, except that system state backed up by the Tivoli Storage Manager Version 5.5 client cannot be restored by the Tivoli Storage Manager Version 5.4 client. If the system had not yet been backed up by the Tivoli Storage Manager Version 5.5 client, but was still the version backed up at the Tivoli Storage Manager Version 5.4 level, the Tivoli Storage Manager Version 5.4 client would be able to restore the system state; The system state would not be restorable by the Tivoli Storage Manager Version 5.4 client if the system state had already been backed up by the Tivoli Storage Manager Version 5.5 client. Specify systemservices in the domain statement (for example, domain systemservices). Use the backup systemservices command. Use the restore systemservices command in normal production or recovery scenarios. Instead, use restore systemstate <service name> to restore a particular system service. Use the query systemservices command. Use the show systemservices command.
418
7718Install_Windows_ba_client_8_Aug.fm
Ask your Tivoli Storage Manager administrator to rename the existing system object or system state file spaces. Once the migration is complete and you have new backups of the system object or system state data, your Tivoli Storage Manager administrator can delete the renamed file spaces. The file spaces to rename include one or more of the following: SYSTEM OBJECT SYSTEM STATE SYSTEM SERVICES ASR
Ask your Tivoli Storage Manager administrator to delete the existing file spaces (listed above) for your node. Renamed file spaces remain on the server and are managed as stabilized file spaces. These file spaces contain all the original data, which can still be restored until the file spaces are deleted. You can find additional information in the IBM Tivoli Storage Manager for Windows Administrators Guide.
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
419
7718Install_Windows_ba_client_8_Aug.fm
420
7718Install_Windows_ba_client_8_Aug.fm
Language packs
The Tivoli Storage Manager client now makes use of language packs for non-English language support. Each supported language has its own installation package that must be
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
421
7718Install_Windows_ba_client_8_Aug.fm
installed in order to use Tivoli Storage Manager in a supported, non-English language. The Tivoli Storage Manager client is a prerequisite for installing a Tivoli Storage Manager Client Language Pack.
Additional considerations
The Backup-Archive Client, the API, and the Web Client are interdependent. If you select the Backup-Archive Client, you must also select the API. Similarly, if you select the Web client, you must also select the Backup-Archive Client and the API. The Backup-Archive Client component includes the client scheduler files. The installer displays the exact amount of disk space that is required for each program feature. Ensure that there is enough disk space on the destination drive for the files you choose to install. The installation program will not install to a destination drive with insufficient disk space.
Figure 19-1 Installatation of the Tivoli Storage Manager Client Version 6.1.0.0 Main Menu
From the Install Products window select Tivoli Storage Manager Backup-archive Client as shown in Figure 19-2 on page 423.
422
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-2 Install Products window of the Tivoli Storage Manager Client Version 6.1.0.0
The next window is the Choose Setup Language as shown in Figure 19-3. After selecting your preferred language click OK to continue.
Figure 19-3 Installatation of the Tivoli Storage Manager Client Version 6.1.0.0
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
423
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-4 Instal Shield Wizard of the Tivoli Storage Manager Client Version 6.1.0.0
The next window allows you to specify the destination folder (see Figure 19-5 on page 424). You can accept the default or click Change in order to specify your installation destination. Click Next to continue.
Next you cloose the type of install - Typical or Custom. Typical installs the minimum necessary to provide normal backup and archive functions. This includes the Backup-Archive Client, the API Runtime files, and the Web Client. Custom install takes you to the Custom Setup window. From this window, you can click on any program feature icon to modify that feature if it is not mandatory for installation. You can select from the following program features: Backup-Archive Client 424
Tivoli Storage Manager V6.1 Technical Guide
7718Install_Windows_ba_client_8_Aug.fm
Backup-Archive Client GUI Files (Mandatory; cannot be deselected) Backup-Archive Client Web Files (Mandatory; cannot be deselected) Client API Runtime Files (Mandatory; cannot be deselected) Client API SDK Files (Optional) Administrative Client Command Line Files Logical Volume Snapshot Agent (LVSA) (Optional; not enabled by default)
In our lab environment we chose Custom install so you can see the available options as shown in Figure 19-6 on page 425. Click Next to continue.
Figure 19-6 Setup Type for installatation of the Tivoli Storage Manager Client
The Custom Setup window is displayed as shown in Figure 19-7 on page 426. You can select the available features and click Next to continue.
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
425
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-7 Installatation of the Tivoli Storage Manager Client Version 6.1.0.0
After specifying the install options the Install Wizard is ready to install the Tivoli Storage Manager Client as shown in Figure 19-8 on page 426. You can click Install to begin the Client install, Back to go to previous panels and modify your selections, or Cancel to exit the InstallShield Wizard.
Figure 19-8 Install Wizard is ready to begin the Tivoli Storage Manager Client installation
When the install is complete you will be presented with a window as shown in Figure 19-9 on page 427. Click Finish to continue.
426
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-9 Installatation of the Tivoli Storage Manager Client completion window
You will be prompted to restart your system after the Tivoli Storage Manager Client installation as shown in Figure 19-10 on page 427.
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
427
7718Install_Windows_ba_client_8_Aug.fm
Your first choose whether to Create a new options file, Upgrade my options file, or Import from an existing options file for use. Since this is a new client install, the option to Update my options file is greyed out. We select to create a new options file, and click Next to continue as shown in Figure 19-12 on page 428.
Figure 19-12 Select how to proceed with the Client options file
428
7718Install_Windows_ba_client_8_Aug.fm
Next you specify the Client Node Name as shown in Figure 19-13 on page 429. We specified ITSO-BA1. Click Next to continue.
The TSM Client/Server Communications window is shown in Figure 19-14 on page 430. One of the most important purposes of the options file is to specify the communication protocol necessary to establish communications between your backup client and the backup server. For our installation we select TCP/IP as shown in Figure 19-14 on page 430. Click Next to continue.
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
429
7718Install_Windows_ba_client_8_Aug.fm
After specifying TCP/IP, we need to enter the IP address of the Tivoli Storage Manager Server or the address of the server as shown in Figure 19-15 on page 430. We specified the Tivoli Storage Manager server name and accepted the default port number. Click Next to continue.
Figure 19-15 Tivoli Storage Manager server nema or IP address and communication port
430
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-16 shows the recommended Include/Exclude list. You can select the entire list or specific files. When you have made your choice click Next to continue.
Figure 19-16 Installatation of the Tivoli Storage Manager Client Version 6.1.0.0
The Common File Exclusion Selection window presents common file Extensions that you may want to exclude from backup. You can select all the file extensions or specific ones. After you have made your choice click Next to continue (see Figure 19-17 on page 432).
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
431
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-17 Installatation of the Tivoli Storage Manager Client Version 6.1.0.0
The Domain for Backup window is displayed. Here you select to backup all local file systems or specify specific drives. You also specify the type of backup to perform (see Figure 19-18).
After you have made your choices for the Client Options file you are given the option to go back and make changes of apply the changes and save the TSM Client Options to disk (see Figure 19-19 on page 433). Click Apply to continue.
432
7718Install_Windows_ba_client_8_Aug.fm
When the TSM Client Options file has been saved you will be presented with the window in Figure 19-20. Click on Finish to close the wizard.
You can now login the Tivoli Storage Manager client server as shown in Figure 19-21.
Chapter 19. Tivoli Storage Manager V6.1 backup-archive client update and installation
433
7718Install_Windows_ba_client_8_Aug.fm
Figure 19-21 Log in to the Tivoli Storage Manager Client Version 6.1.0.0
Figure 19-22 shows the options you are presented based on the Tivoli Storage Manager Client Options file.
434
7718p05.fm
Part 8
Part
Tivoli Storage Manager V6.1 monitoring, reporting, ISC and administration center
This part of the book contains the minitoring and reporting provided in Tivoli Storage Manager V6.1 along with the ISC and administration center.
435
7718p05.fm
436
7718MonitorReport.fm
20
Chapter 20.
437
7718MonitorReport.fm
438
7718MonitorReport.fm
Figure 20-1 Heath Monitor from the Tivoli Storage Manager Administratiion Center
439
7718MonitorReport.fm
Setup options
There are a couple of options when setting up Monitoring and Reporting. For customers with an already existing licensed ITM setup, Tivoli Storage Manager can make use of this, provided it is at level 6.2 FP1. For customers with no existing ITM setup, Tivoli Storage Manager provides a complete version, which is usable for monitoring Tivoli Storage Manager only. With this option, the Monitoring and Reporting system must comply with the requirements listed on the planning section of the Tivoli Storage Manager documentation: principally that the Monitoring and Reporting system has a server of its own. It is not supported to install Monitoring and Reporting on the same system as the Tivoli Storage Manager 6.1 server (a separate VM or LPAR would be fine though).
7718MonitorReport.fm
Uses Deployment Engine to install all components easily. A new Reporting and Monitoring solution for Tivoli Storage Manager. Will report on any Tivoli Storage Manager server at or later than version 5.3. Compliments and integrates with Tivoli Storage Manager Administration Center. Light enough to be installed to manage a single Tivoli Storage Manager server. Scalable enough to manage a farm of Tivoli Storage Manager servers. Integrate with reporting tools from other IBM products. Integrate with monitoring tools from other IBM products.
441
7718MonitorReport.fm
Does it plug into an existing Tivoli Storage Manager Admin Center installation?
Yes, we recommend to use one server for managing/reporting/monitoring Tivoli Storage Manager. It plugs into Tivoli Storage Manager V6.1 Administration Center only.
7718MonitorReport.fm
change the Tivoli Storage Manager settings on the system to allow the server to use less system memory and resources. Similarly, if the workloads for the other DB2 applications compete for CPU or memory resources with the Tivoli Storage Manager server, the performance of the Tivoli Storage Manager server might be adversely affected in its ability to service the desired client workload or other server operations that are needed. From a best-practices perspective, it might be appropriate to consider using LPAR, WPAR, or other virtual machine support to accomplish this. For example, running the other application that uses DB2 in its own virtualized machine segregates resources and provides more capability for the tuning and allocation of CPU, memory, and other system resources to this application as well as the resources available to Tivoli Storage Manager.
Note for Windows systems: The current restriction that is documented in the Tivoli Storage Manager publications for the installation of other DB2 versions (or applications that deploy and use DB2) on the same Windows system as a Tivoli Storage Manager V6 server is still in place and not affected by the support discussed here. Similar support for Windows systems is currently being evaluated. Assuming that the testing and evaluation do not uncover any issues to prevent it, the target is to remove this restriction towards the end of third quarter of 2009 or in fourth quarter of 2009.
443
7718MonitorReport.fm
Figure 20-3 Tivoli Storage Manager for Reporting and Monitoring installer Welcome panel
Next you select the components you want to install. For our install we select all the components of Tivoli Monitoring and Reporting, as well as the ISC. The components will be installed on the Monitoring and Reporting server. The Tivoli Storage Manager server is separate from this. The only option we do not select here is the Languages option, since we will be using the default English for our example, as shown in Figure 20-4 on page 445.
444
7718MonitorReport.fm
The next window is the DB2 Enterprise Server Edition where you provide the information required to create the DB2 database (see Figure 20-5 on page 446). Enter the DB2 Administrator password and click Next to continue.
445
7718MonitorReport.fm
Figure 20-6 on page 446 shows the Encryption key entry screen. We accepted the default encryption key. Click Next to continue.
446
7718MonitorReport.fm
Figure 20-7 on page 447 shows the Database Access Setup panel. Enter the password for the TEPS and ITMUser user ID. Note it, and click Next to continue.
Figure 20-8 on page 448 shows the Administration Center credential entry screen. Enter the required information and click Next to continue.
447
7718MonitorReport.fm
Figure 20-8 ISC User name and Password for Administration Center credentials
Figure 20-9 on page 449 is the Choose Install Folder window where you specify the location of the Install destination folder. Accept the default or enter the installation directory for your server. Click Next to continue.
448
7718MonitorReport.fm
Figure 20-10 on page 449 shows the Pre-Installation Summary panel. Review the information. If you are satisfied with the information click Install to continue.
449
7718MonitorReport.fm
Figure 20-11 Installing Tivoli Storage Manager for Monitoring and Reporting
Figure 20-12 on page 451 shows the Completion of the Monitoring and Reporting Installation. The panel contains a summary of what was installed. Click Done to complete the install and exit.
450
7718MonitorReport.fm
20.4.1 Downloading
Downloading BIRT is fairly simple, given access to a web browser with internet access. Download the All-In-One package from the BIRT website, which is avaliable from http://download.eclipse.org/birt/downloads/ The actual package we use in the Windows example is approximately 220MB and is v2.5.0 of BIRT, although previous versions are also known to have worked. A redirect link to the code package is http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/gal ileo/R/eclipse-reporting-galileo-win32.zip
451
7718MonitorReport.fm
When the file is downloaded, simply unpack it to the location of your choice. Once this is done, set the java virtual machine location for BIRT to use. There are a couple of different ways to set this (for example, adding the java bin directory of the JVM to the PATH for the system). An ideal way to do it under Windows is to create a shortcut to eclipse.exe, then modify the properties of the shortcut, setting the -vm parameter of eclipse. By setting the JVM this way, you do not affect anything else on the system. Note: BIRT is a java tool, but it does not ship with a JVM (Java Virtual Machine). Without a JVM, it cannot run. The IBM JVM is installed along with the Monitoring and Reporting package from the Tivoli Storage Manager installation, so we may use that to run the BIRT code. The default path of the IBM JVM is C:\Program Files\IBM\Java50\jre\bin on Windows.
452
7718admincenter_updated_July16.fm
21
Chapter 21.
453
7718admincenter_updated_July16.fm
21.1 Introduction
Starting in Tivoli Storage Manager V5.3 the Integrated Solutions Console was introduced, which in the beginning was of limited use to most Tivoli Storage Manager administrators, and from a user design and experience perspective represented a 180 degree shift in how Tivoli Storage Manager management was done. The previous interface in V5.2 and prior was mostly accessed from an object perspective, and the ISC and Administration Center introduced a task driven perspective. This design shift was intuitive for a new administrators, and a challenge for existing more experienced administrators, who struggled with locating tasks with in the GUI hierarchy. This operational gap was handled by extending the life of the ADMIN or WEBADMIN GUI, which was frozen at 5.2.x and its support extended until V5.5 new installations. This release of the new ISC and Administration Center marks the first significant update in functionality since it was first introduced in V5.3, and applies some much anticipated improvements.
Figure 21-1 Down level error when Tivoli Storage Manager server is V6.1 and the ISC/AC is lower
454
7718admincenter_updated_July16.fm
Upgrading involves collecting the configuration information from a previous version of the Administration Center and duplicating it in the new version. Coexistence involves running the Administration Center V6.1 on the same machine at the same time as you run the previous version. To support this coexistence, you need to provide non-default port assignments. For upgrade scenarios involving the possibility of rolling back to the previous version, you can choose to have the same port definitions and run either one version or the other. If your disk space permits, having the two versions of the Administration Center coexist is the recommended upgrade strategy (using different IP ports). It lets users have a functioning Administration Center during the time that it takes for the upgrade to complete. It also ensures that the configuration of the previous Administration Center is still accessible during the upgrade procedure. Upgrade does not uninstall the previous version, which is still functional. After the upgrade completes successfully, you can uninstall the previous Administration Center using the documented process.
455
7718admincenter_updated_July16.fm
456
7718admincenter_updated_July16.fm
message number is also provided. In V6.1, you can obtain detailed information about a message by clicking the link that is associated with the message number. The information is displayed in a new browser window.
457
7718admincenter_updated_July16.fm
Volume Property Forms for DRM or Remote DRM volumes Display pool info for volumes associated with an active data pool (Long) Move DRMEDIA Wizard Ability to overwrite Active Data Pool settings in addition to Copy pool settings Relevant text updates at Welcome and Summary Panels Create Recovery Plan (Prepare) Wizard Ability to overwrite Active Data Pool settings in addition to Copy and Primary pool settings Relevant text updates at Welcome and Summary Panels View Disaster Recovery Media/ View Remote Disaster Recovery Media actions (Off the DRM Servers Table) Update panel description to include active data pools reference in addition to copy pools reference. View Disaster Recovery Media/View Remote Disaster Recovery Media Main Portlets Update portlet table column header from Copy Pool to Destination Pool, referring to both Copy and Active data pools View Disaster Recovery Media/View Remote Disaster Recovery Media Main Portlets -Advanced Filter Form Add new input field for Active-data pool, similar to the one for Copy pool filtering
Changes
The following sub-section discusses changes to the health monitoring feature of the Administration Center.
458
7718admincenter_updated_July16.fm
Next, from the Select Action drop down menu click on View Health Details as shown in Figure 21-3.
459
7718admincenter_updated_July16.fm
Figure 21-3 Choosing View Health Details for the vermont-tsm1 server instance
By selecting to View Health Details you see details for schedule, database and recovery log, current activities such as sessions and processes and activity log messages and storage pool status. All these are shown in Figure 21-4 on page 460.
Figure 21-4 Health monitor panel highlighting multiple areas for review
As seen in Figure 21-4 the actlog portlet shows errors. If you click on and the error link they are summarized, with an additional link on the actual error itself, shown in Figure 21-5 on page 461.
460
7718admincenter_updated_July16.fm
In our scenario we click on the link to ANR0944E and are able to review the manual entry for ANR0944E, as shown in Figure 21-6 on page 461.
Figure 21-6 Error message detail displayed using the hot link supplied in the Health Monitor portlet
Expanding the Storage Device Status portlet, from the Select Action drop down menu, there is a level of control such as dismounting tape volumes, as shown in Figure 21-7 on page 462.
461
7718admincenter_updated_July16.fm
21.3.10 Reporting
Reporting has a new feature which allows the creation of a .CSV file to be downloaded directly to your connecting system. The path to find this is shown in Figure 21-8.
Next, select the Usage Report and from the Select Action drop down menu click Run Report as shown in Figure 21-9.
462
7718admincenter_updated_July16.fm
Next, select the action of Export Data as shown in Figure 21-10 on page 463.
Finally the option to either open or save the file on your local system, as shown in Figure 21-11.
463
7718admincenter_updated_July16.fm
Figure 21-12 Selecting Manage Servers Select Action Create Server Instance process
Then, following this panel we will click Next after reviewing the information, as shown in Figure 21-13.
464
7718admincenter_updated_July16.fm
Figure 21-13 Selecting Next to accept the default in the Create Server Instance process.
In the next panel you provide the address and System Administrator user ID and password. In our lab we will fill in the blank fields for the root login of the AIX Tivoli Storage Manager server Utah, as shown in Figure 21-14 on page 465.
Figure 21-14 Filling in the ip_address, admin ID and password in the Create Server Instance process.
Following this panel, we must create the AIX user ID and password for this instance, as shown in the Example 21-1.
465
7718admincenter_updated_July16.fm
Example 21-1 Setting up a user ID and password in the AIX server prior to the instance creation
# mkuser -a id=1003 pgrp=tsmsrvrs home=/home/tsm2 tsm2 # passwd tsm2 Changing password for "tsm2" tsm2's New password: Enter the new password again:
Next, log in using the user ID and password, and you will be prompted to change the password as that user ID, as shown in Example 21-2.
Example 21-2 Logging into AIX and changing the password for TSM2 new instance creation
You must change your password now and login again! Changing password for "tsm2" tsm2's Old password: tsm2's New password: Fill in the details for the instance in the Configure Instance User ID panel. With AIX (and Unix platforms) you must have the userid, group and directory structure already created on the target Tivoli Storage Manager server, as shown in Figure 21-15 on page 466. Click Next to continue.
Figure 21-15 Inputting the instance ID and password for the Create Server Instance process.
Input the instance path and database paths in the Instance Directories panel, as shown in Figure 21-16. Click Next to continue.
466
7718admincenter_updated_July16.fm
Figure 21-16 Inputting the instance directories for the Create Server Instance process
With the next panel, you continue inputting the instance directories. Notice with this panel how the shaded (colored) areas imply the mandatory fields, and the fields with no shading are optional fields (see Figure 21-17 on page 467). After entering the required information click Next to continue.
Figure 21-17 Input for the instance directory panels for the Create Server Instance process
467
7718admincenter_updated_July16.fm
The next step in this process is filling out the Server Information panel, including the instance name and the language, which we have done as shown in Figure 21-18 on page 468. You also specify how the server starts when the machone boots. Click Next to continue.
Figure 21-18 Server information panel input for the Create Server Instance process
Next you specify a Tivoli Storage Manager administratorto create when configuring the new server instance as shown in Figure 21-19 on page 468. After specifying the required information click Next to continue.
468
7718admincenter_updated_July16.fm
The next configuration panel shown in Figure 21-20 shows the default for tcpport and tcpadminport. Since this is the second instance, and you must change the default tcpport to 1501 (something other than the tcpports currently being used).
The next panel is a summary of the information you specified in the previous panels (see Figure 21-21 on page 469). Review the information, if you are satisfied with the information click Next to create the new server instance.
469
7718admincenter_updated_July16.fm
Figure 21-22 shows that there is insufficient space to create the new server instance.
Figure 21-22 Error shown due to insufficient space during the Create Server Instance process.
We then increase the size of the instance filesystem to allow at least 400MB of free space, and then repeat all of the above scenario from Figure 21-12 on page 464 through Figure 21-21 on page 469. Following this correction, the configuration starts, and then completes successfully, as shown in Figure 21-23 on page 470. When the instance is created click OK.
Figure 21-23 .Completion panel for the Create Server Instance process.
On the Manage Servers panel shown in Figure 21-24 you can see that we have successfully added a second instance UTAH-TSM2.
470
7718admincenter_updated_July16.fm
Figure 21-24 View of the completed instance under the Managed Server listing.
This will open three independent configuration panels, the first one is the Client Nodes configuration panel, as shown in Figure 21-26.
471
7718admincenter_updated_July16.fm
The second configuration panel opened is the Client Node Groups panel, as shown in Figure 21-27 on page 472.
Then, the third panel is for backupsets configuration, as shown in Figure 21-28 on page 472, which will be discussed in greater detail in the section Backupsets on page 475.
Next the following series of screen shots will demonstrate the configuration of a Client Node Group. To start, from the Client Node Groups panel select the All Clent Node Groups tab. From the Select Action drop down menu click Create Node Group as shown in Figure 21-29.
472
7718admincenter_updated_July16.fm
Next, select the Tivoli Storage Manager server instance the client will be associated with, and the new group name. Provide an optional Description as shown in Figure 21-30 on page 473.
Figure 21-30 Client Node Group configuration panel, choosing the server instance for the group.
After filling out the input fields click OK. The result panel appears as shown in Figure 21-31 on page 473.
Next, we move on to the creation of the client node. From the Select Action drop-down menu click Create a Client Node as shown in Figure 21-32.
473
7718admincenter_updated_July16.fm
Next, we fill in the fields required for our node configuration, as shown in Figure 21-33 on page 474. Click OK to continue.
After clicking on OK, the ALL Client Nodes tab shows the completed task with the new client node listed (see Figure 21-34 on page 474).
474
7718admincenter_updated_July16.fm
And reviewing the creation of the client node, select the By Server tab view. This provides a different look to the Administration Center node grouping and summary as shown in Figure 21-35.
Clicking on the arrow next to the Client Node name will expand the section displaying more detailed information. This design has been implemented throughout the new Administration Center interface. Figure 21-36 on page 475 demonstrates behavior changes within the wizard panels with this release. If you right click on the newly created client Riley_E you now have the ability to take action directly from the object. In other areas of the Administration Center, you still have to select the object requiring update, then use the Select Action drop down menu selection.
Figure 21-36 Options now available using right-click with in the Administration Center client node panel
Backupsets
The backup set wizard has two additional panels, one to allow the point-in-time and data type information to be entered the shredding choice was moved to this panel, and another for TOC selection.The TOC panel will only be visited if the data type selection includes file. For entry in the wizard off the new Nodes and Backup Sets page, there will be some additional changes in navigation. After the General panel, the user will be allowed to select the members, the first panel is a choice of nodes or node groups, the second panel is a table of nodes or node groups, depending on the first panel selection. If the selection result is a single node, then the navigation will go to the existing file space selection panels, but if more than one node was selected, the navigation will proceed to the volume selection panel.
475
7718admincenter_updated_July16.fm
All filespaces will be backed up if multiple nodes are selected. The AC cannot handle filespace selection for multiple nodes. Due to some issues with different code pages the AC uses filespace ID in the generate command, and since filespace ID can be different for the same filespace name across nodes, this will not work for multiple nodes. Figure 21-37 on page 476 shows the flow of the backupset wizard navigation panels, which include many changes.
Referencing the flow chart in Figure 21-37, notice the entry from the Backup set tab where we create a backup for a number of client nodes and client node groups. There is a path change when only a single node (either one node from the nodes table, or one node group with only a single node) is selected. When multiple nodes are selected, all file spaces will be backed up, using the BOTH flag for Unicode.
7718admincenter_updated_July16.fm
set, and the retention period information from the server. The expiration date displayed is retention period days after the creation date. If the backup set was generated by selecting a date that is the backup set only contains data that existed on the server on a specified date and time, then the creation date on the server, and used by the Administration Center is the date specified on that command, not the actual day the backup set was created. The backup set will expire retention days after that date on the command, not from the day the command was issued. The retention period and expiration date displayed the collection and details panels will be based on the longest retention period in the collection, since this is how long the volumes will be retained. The collections panel will populate the table when a server is selected and the update table button is pushed. The currently displayed server name will appear above the table. The details panel will have a table with rows for node/data type combinations. Since all the backup sets in the collection have the same name, creation date, volumes and description, these items are displayed above the table with the node names. The details panel retention/expiration information will be displayed above the table as well. A message will be displayed if all backup sets do not have the same retention period. The individual retention periods will only be visible from the client node notebook backup set tab. The details panel table will have at least one row for each node that has a backup set in the selected connection. If a node has multiple data types in the collection, then there will be multiple table rows. For example, a node with an Image and File backup set with this backup set name will have two rows in the table,
Breadcrumb navigation
The new backup set panels, and the existing backup sets contents panel will have bread crumb navigation. Instead of having a close button on the bottom left corner, the upper left corner of the panel will show the path. The user will be able to go back one or two screens by clicking directly on the hyperlink for the desired panel. An example would be the Back Set Contents page enter from the new Backup Sets table. The navigation to the panel would be by selecting a specific backup set collection from the initial page using the hyperlink or details actions, and from the backup set details page, selecting a specific backup set, and the
477
7718admincenter_updated_July16.fm
Display Content action. The upper left will have hyperlinks that will take the user directly back to either the Collections panel or the details panel. The Display content action will have a confirmation message, indicating that this is a long running command and may time-out. This is new for Tivoli Storage Manager V6.1 because this command will cause the backup set to be read, and can take a long time to process. It is very likely it will time out before the response from the server is received in most cases.
1. Click Server Maintenance in the work items list. 2. In the table, click Select Action Create Maintenance Script or Create Custom Maintenance Script.
478
7718admincenter_updated_July16.fm
Path To View and modify To view and modify a script: 1. Click Storage Devices in the work items list. 2. In the Servers table, click a server name. 3. In the server's properties portlet, click the Scripts tab. 4. In the table, select a script. 5. Click Select Action Modify Script. To modify a maintenance script: 1. Click Server Maintenance in the work items list. 2. In the table, select a maintenance script. 3. Click Select Action Modify Maintenance Script.
The following sequence of screen captures visually demonstrates the wizard for the creation of a maintenance script, of which only one is supported at any time. We begin the creation starting with Figure 21-38 on page 479. From the Integrated Solutions Console panel select the Server Maintenance option under the Tivoli Storage Manager in the left hand pane.
Figure 21-38 Selecting the Server Maintenance task in the Administration Center
in the next panel you will see a list of the servers you have added to the console. Select the server you want to add a maintenance script for. From the Select Action drop down menu select Create Maintenance Script as shown in Figure 21-39.
479
7718admincenter_updated_July16.fm
The next panel is the Welcome screen. Click Next to continue as shown in Figure 21-40 on page 480.
480
7718admincenter_updated_July16.fm
In the next panel, clicking Next will present the opportunity to select a predefined script, as shown in Figure 21-41. We will be using the DRM feature, so we select the third option and click Next to continue.
Figure 21-41 Creation of a maintenance script wizard panel for predefined script selection
You proceed to the creation of the Backup Server Database panel, where we are presented with a backup scheme to protect the Tivoli Storage Manager V6.1 database. We select the correct device class, and the default of six daily incrementals, then a weekly full backup as shown in Figure 21-42. Click Next to continue.
481
7718admincenter_updated_July16.fm
Figure 21-42 Selecting the device class for the server database backup
The wizard moves on to DRM processing as shown in Figure 21-43 on page 482. Here you define the library volumes to be moved. Click Next to continue.
Figure 21-43 Library volumes to be moved by DRM with in the server maintenance script wizard
482
7718admincenter_updated_July16.fm
In the next panel you specify the options used to identify the library volumes and the DRM state to be moved within the maintenance script as shown in Figure 21-44 on page 483. Click Next to continue.
Figure 21-44 Library volumes and DRM tostate transition within the server maintenance script wizard
In the next panel you specify where the recovery plan file is written, as shown in Figure 21-45 on page 484. When you have made your selection click Next to continue.
483
7718admincenter_updated_July16.fm
Figure 21-45 Recovery plan configuration panel with in the server maintenance script wizard
In the next panel you choose the appropriate migration details as shown in Figure 21-46. Click Next to continue.
Figure 21-46 Migration configuration panel with in the server maintenance script wizard
484
7718admincenter_updated_July16.fm
In the next panel you specify the expiration process that removes backup and archive data from server storage. After specifying the expiration process parameters as shown in Figure 21-47 on page 485, click Next to continue.
Figure 21-47 Expiration duration configuration panel with in the server maintenance script wizard
In the Reclaim Tapes panel you specify the storage pools to run reclaimation, the unused space capacity percentage that triggers reclaimation, and the time limit for reclaimation. After entering the required data (see Figure 21-48 on page 486) click Next to continue.
485
7718admincenter_updated_July16.fm
Figure 21-48 Reclamation detail configuration in the server maintenance script wizard
In the Schedule Maintenance panel you specify when you want the maintenance script to run on a regular basis. After specifying the options in Figure 21-49 on page 486 click Next to continue.
486
7718admincenter_updated_July16.fm
The Summary page is presented as shown in Figure 21-50. The options you specified in the wizard are summarized. Click Finish to continue.
Clicking Finish will create the script. Next, we view the script from the command line, using the q script f=d Tivoli Storage Manager administrative command, as shown in Figure 21-51.
487
7718admincenter_updated_July16.fm
Figure 21-51 Generated script as a result of using the maintenance creation wizard
488
7718admincenter_updated_July16.fm
You are presented with general information on the maintenance script as shown in Figure 21-53 on page 489. In the left hand pane click on Back Up Database to continue.
489
7718admincenter_updated_July16.fm
The Back Up Database options that were previously entered in Figure 21-42 on page 482 are presented. In this scenario we change the type of backup to Full backup option. Click on the Apply and OK buttons. and then presented with the configuration panel as shown in Figure 21-54.
Figure 21-54 Backup database selection panel using the server maintenance wizard
Following these actions we then return back to the command line and compare the script section which has been altered. First, the incremental database backup lines are shown in Figure 21-55 on page 490.
Figure 21-55 Database backup lines originally created in the maintenance script
Now, we view the newest update to the database backup lines in the server maintenance script as shown in Figure 21-56 on page 491.
490
7718admincenter_updated_July16.fm
Figure 21-56 Results following the modification of the server maintenance script to database backup
In summary, the discussion on maintenance scripts and screen flows are demonstrating some significant improvements in the Tivoli Storage Manager Administration Center feature for V6.1.
491
7718admincenter_updated_July16.fm
modules that need to authenticate console users to back end systems can retrieve those credentials without prompting the user. Each key containing sensitive information can be identified by an application using the credential key name. Before using this module, consult the application documentation or service representative to determine the semantics required for the key. Field descriptions
New - Opens a new panel which displays fields used to create the new credential
information. The information provided depends on the application or system that will be using this information. For example, to authenticate to a remote machine named ServerA, you could set the key name to ServerA, set the credential name to the login username, and set the credential value to the login password. Then a console module can retrieve the username and password using the String ServerA and log the user in without presenting a login prompt.
Figure 21-57 A second login attempt using the same user ID for the ISC is blocked
As a result of this change now enforcing security in the ISC, along with its ability to handle a single signon for other configured applications, it is highly recommended to configure a separate user ID for each administrative user.
492
7718admincenter_updated_July16.fm
Clicking on the Vermont-TSM1 server link we can edit the existing key (see Figure 21-59 on page 493).
Figure 21-59 Clicking on the server link, the exact credential details can be updated
The Edit Credential Storage Key panel allows the ISC user to alter the Tivoli Storage Manager server access credentials by changing the user ID and password for the selected key as shown in Figure 21-60 on page 494.
493
7718admincenter_updated_July16.fm
Figure 21-60 Final Credential Store panel to alter credentials for a server link
From the Credential Store panel you can delete an old Tivoli Storage Manager instance which is no longer required, as shown in Figure 21-61 on page 494.
Figure 21-61 Old Tivoli Storage Manager server link is deleted using the Credential Store panel
494
7718admincenter_updated_July16.fm
This includes the follow modes options; No refresh indicates that the portlet content will not be refreshed automatically. The refresh timer is not displayed in the portlet title bar, but the portlet can still be refreshed manually. Timed refresh indicates that the portlet content is refreshed automatically based on the value of the refresh interval. Smart refresh indicates that after the refresh interval has timed out, the client should query the portlet on the server to determine if it should refresh the content. If the portlet has updates to provide, then the content is updated on the client. Otherwise, no change is made and the timer is started again. Unregister will disable the portlet refresh capabilities for this portlet. The portlet still displays in Manage Global Refresh. Portlet refresh can be subsequently restored by setting this value to one of the other settings. The Manage Global Refresh portlet is shown in Figure 21-62.
In this example, we are changing the tape library refresh from 600 to 1200 seconds, which would reduce the number of queries to all servers for all the AC configured servers. This is shown in Figure 21-63 on page 495.
Figure 21-63 .Changing the global refresh for the tape libraries
495
7718admincenter_updated_July16.fm
Path changes
In V5.3 through V5.5, the Integrated Solutions Console default location was; [ISC root]\Tivoli\dsm\bin\ (Windows) [ISC root]/Tivoli/dsm/bin/ (UNIX and Linux) This has changed for V6.1. to the following paths; [TSM root]\AC\products\tsm\bin (Windows) [TSM root]/AC/products/tsm/bin (UNIX and Linux)
# ./supportUtil.sh User ID: iscadmin Password: Administration Center Support Utility - Main Menu ================================================== 1. 2. 3. 4. 496 Manage Administration Center tracing Manage the maximum memory size the Administration Center can use Manage the Administration Center session timeout setting Collect trace files, logs and system information to send to support
7718admincenter_updated_July16.fm
5. 6. 7. 9.
Generate a heap dump of the Java virtual machine Generate a Java core dump of the Java virtual machine View the log file for this utility Exit
Enter Selection: 3 Administration Center Support Utility - Manage the Session =========================================================== 1. 2. Update the Administration Center session timeout setting View the Administration Center session timeout setting
99. Return to main menu Enter Selection: 1 The session timeout setting determines how long a session can be idle before it times out. After a timeout occurs the user must log in again. The default timeout setting is 30 minutes. The minimum timeout setting is 10 minutes. To cancel this operation enter an empty value.
Enter the new session timeout (minutes): 120 Updating the session timeout to 120 minutes........ Session timeout successfully updated. Restart ISC for changes to take effect. Press Enter to continue . . . Administration Center Support Utility - Manage the Session =========================================================== 1. 2. Update the Administration Center session timeout setting View the Administration Center session timeout setting
99. Return to main menu Enter Selection: 99 Administration Center Support Utility - Main Menu ================================================== 1. 2. 3. 4. 5. 6. 7. 9. Manage Administration Center tracing Manage the maximum memory size the Administration Center can use Manage the Administration Center session timeout setting Collect trace files, logs and system information to send to support Generate a heap dump of the Java virtual machine Generate a Java core dump of the Java virtual machine View the log file for this utility Exit
Enter Selection: 9
497
7718admincenter_updated_July16.fm
Exiting #
498
7718p06.fm
Part 9
Part
499
7718p06.fm
500
7718Upgrade_Planning.fm
22
Chapter 22.
501
7718Upgrade_Planning.fm
502
7718Upgrade_Planning.fm
The upgrade utilities or upgrade wizard extracts data from an existing database and inserts the data into a new Tivoli Storage Manager V6.1 database. Media or the network can be used for the data movement. As a database is moved into the new database structure, the validity of the data is checked against constraints that are enforced in the new database. The upgrade tools automatically correct some errors in the database. Other errors might need to be corrected manually. If you use the wizard, you are guided to perform the upgrade steps in the correct order. If you are performing the upgrade manually using utilities from a command line, follow the procedure carefully. 6. Verify the upgrade by performing basic operations and querying information about the system to confirm that all information transferred correctly. Review the information that compares the methods for performing the upgrade, and the descriptions of the upgrade scenarios, to help you decide how to perform the upgrade process for your servers. Important: At this point you should read the chapter Chapter 16, Install and Upgrade Planning for Tivoli Storage Manager V6.1 on page 251 before going any further. It contains information that you need for a successful upgrade to Tivoli Storage Manager V6.1.
503
7718Upgrade_Planning.fm
Restriction: You cannot install and run the V6.1 server on a system that already has DB2 installed on it, whether DB2 was installed by itself or as part of some other application. The V6.1 server requires the installation and use of the DB2 version that is packaged with the V6.1 server. No other version of DB2 can exist on the system.
IBM AIX 5L V5.1 (32 or 64 bit) AIX V5.2 (32 or 64 bit) PA-RISC: HP-UX 11i V1.0 (32 or 64 bit)
AIX V5.3 (64 bit only) AIX V6.1 (64 bit only)
HP-UX
Linux on Power
Red Hat Enterprise Linux 3 (supported on POWER5 processors only) SUSE Linux Enterprise Server 8/UnitedLinux 1.0 (supported only on processors prior to POWER5) Miracle Linux 4.0 or Asianux 2.0 GNU C libraries 2.2.5-108
Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 SUSE Linux Enterprise Server 9 and 10 Asianux 2.0 - Red Flag DC 5.0 and Haansoft Linux 2006 or Asianux 3.0 V2.3.3 or later of the GNU C libraries that are installed on the target system
504
7718Upgrade_Planning.fm
You must upgrade to this version (or later) to use the upgrade utilities
Red Hat Enterprise Linux 3 (AS,WS, ES) SUSE Linux Enterprise Server (SLES) 8 / UnitedLinux 1.0 V2.2.5-213 of the GNU C libraries
Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 SUSE Linux Enterprise Server 9 and 10 Asianux 2.0 - Red Flag DC 5.0, Miracle Linux 4.0, and Haansoft Linux 2006 or Asianux 3.0 V2.3.3 or later of the GNU C libraries that are installed on the target system Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 SUSE Linux Enterprise Server 9 and 10 Asianux 2.0 - Red Flag DC 5.0, Miracle Linux 4.0, and Haansoft Linux 2006 or Asianux 3.0 V2.3.3 or later of the GNU C libraries installed on the target machine Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 SUSE Linux Enterprise Server 9 and 10 2.3.3 or later of the GNU C libraries that are installed on the target system SPARC 64 bit: Sun Solaris 9 Sun Solaris 10 x86_64: Sun Solaris 9
Linux x86_64
Red Hat Enterprise Linux 3 Red Flag Advanced Server 4.1 SUSE LINUX Enterprise Server 8 V2.2.5-213 of the GNU C libraries
Linux zSeries
SUSE Linux Enterprise Server 8 / UnitedLinux 1.0 Version 2.2.5-108 of the GNU C libraries
Sun Solaris
Microsoft Windows
Windows 2000 Professional Windows 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server
Windows Server 2003 (Standard, Enterprise, or Datacenter) Edition Windows Server 2003 (Standard, Enterprise, or Datacenter) x64 Edition Windows Server 2008 (Standard, Enterprise, or Datacenter) Edition Windows Server 2008 (Standard, Enterprise, or Datacenter) x64 Edition
505
7718Upgrade_Planning.fm
Platform for V5 server HP-UX running on a PA-RISC system Linux running on an Itanium system (IA64) Linux running on a 32-bit x86 system Windows running on an Itanium system (IA64)
Required platform for upgrade to V6.1 HP-UX running on an Itanium system Linux running on an x86_64 system Linux running on an x86_64 system Windows running on an x86_64 system
506
7718Upgrade_Planning.fm
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see <<<< x ref hereEstimating total space requirements for the upgrade process and upgradedserver>> .
Table 22-3 Table 6. Hardware requirements Type of hardware Hardware Disk space Hardware requirements A 64-bit Itanium system.
The following minimum disk space: 5 MB for the /var directory 2 GB for the /opt directory 160 MB for the /tmp directory 300 MB for the /usr directory Additional disk space might be required for database and log files. The size of the database depends on the number of client files to be stored and the method by which the server manages them.
Memory
Software requirements
The following table describes the minimum software requirements.
Table 22-4 Software requirements Type of software Minimum software requirements
Operating System
AIX 5.3 running in a 64-bit kernel environment with the following additional requirements for DB2: AIX 5.3 Technology Level (TL) 6 and Service Pack (SP) 2 plus the fix for APAR IZ03063 Minimum C++ runtime level with the xlC.rte 9.0.0.8 and xlC.aix50.rte 9.0.0.8 filesets. These filesets are included in the June 2008 cumulative fix package for IBM C++ Runtime Environment Components for AIX. AIX 6.1 running in a 64-bit kernel environment requires the following filesets for DB2: Minimum C++ runtime level with the xlC.rte 9.0.0.8 and xlC.aix61.rte.9.0.0.8 filesets. These filesets are included in the June 2008 cumulative fix package for IBM C++ Runtime Environment Components for AIX.
Applications
507
7718Upgrade_Planning.fm
Type of software
Web browser
A Web browser to retrieve an online installation package. The following browsers are supported: Microsoft Internet Explorer 6.0 SP1 Microsoft Internet Explorer 7.0 FireFox 1.5 FireFox 2.0 FireFox 3.0 Mozilla 1.7.8 Your browser must support the server code page. If your browser does not support the server code page, the windows might be unreadable. If your browser meets these requirements but does not correctly display a Tivoli Storage Manager Web-based interface, consider using a different browser.
A configured communication method. If you have an IBM 3570, IBM 3590, or IBM Ultrium tape library or drive, install the most current device driver before you install Tivoli Storage Manager 6.1. You can locate the device drivers at ftp://ftp.software.ibm.com/storage/devdrvr/.
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see <<< xref Estimating total space requirements for the upgrade process and upgraded server on page 29>>>.
Table 22-5 Table 8. Hardware requirements Type of hardware Hardware Hardware requirements
508
7718Upgrade_Planning.fm
Hardware requirements
The following minimum disk space: 5 MB for the /var directory 2 GB for the /opt directory 270 MB for the /tmp directory 300 MB for the /usr directory Additional disk space might be required for database and log files. The size of the database depends on the number of client files to be stored and the method by which the server manages them.
Memory
Software requirements
The following table describes the minimum software requirements. System resources such as semaphores and kernel values might require special configuration and tuning.
Table 22-6
Type of software
Operating System
The HP Itanium system must have operating system 11 iv2 or 11 iv3 with the most current maintenance levels installed. If you are using 11 iV2, you must install PHSS_38140. The latest available service patches for the operating system should be applied. Older levels without patches do not work with the device drivers that Tivoli Storage Manager uses. The HP maxfiles parameter specifies the number of files a process is allowed to open at any given time. The default value for HP is 60. However, this value is very low and can cause server problems. To ensure proper server operation, increase the maxfiles value to at least 512.
IBM Java 1.5 or later. A communication method that is installed and activated (shared memory is the default).
509
7718Upgrade_Planning.fm
A DVD device that is available for the installation process, if you are installing from DVD media. The most current device driver. This must be installed before you install Tivoli Storage Manager. You can locate the device drivers at ftp://ftp.software.ibm.com/ storage/devdrvr/.
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see Estimating total space requirements for upgrade process and server on page 520.
Table 22-7 Hardware requirements for Linux on POWER Type of hardware Hardware requirements
Hardware
Linux on POWER IBM system such as one of the systems listed in the following Linux for Power server solution Web site: http://www-03.ibm.com/systems/power/software/linux/ab out/index.html
510
7718Upgrade_Planning.fm
Type of hardware
Hardware requirements
Disk space
The following minimum disk space: 5 MB for the /var directory 4 GB for the /opt directory 190 MB for the /tmp directory 300 MB for the /usr directory Additional disk space might be required for database and log files. The size of the database depends on the number of client files to be stored and the method by which the server manages them.
Memory
Software requirements
The following table describes the minimum software requirements.
Table 22-8 Software requirements for Linux on Power Type of software Minimum software requirements
Operating System
The Tivoli Storage Manager server on Linux on Power (ppc64 architecture) requires one following operating systems: Red Hat Enterprise Linux 5, Update 3 or later SUSE Linux Enterprise Server 10, Update 2 or later Asianux 3.0
GNU C libraries, Version 2.4-31.30 and later IBM Java 1.5 or later. TCP/IP Version 4 or Version 6, which is standard with Linux Shared memory protocol (with Tivoli Storage Manager Version 6.1 System p client)
511
7718Upgrade_Planning.fm
Type of software
Web browser
A Web browser to obtain the Linux installation packages. The following browsers are supported: Microsoft Internet Explorer 6.0 SP1 Microsoft Internet Explorer 7.0 FireFox 1.5 FireFox 2.0 FireFox 3.0 Mozilla 1.7.8 Your browser must support the server code page. If your browser does not support the server code page, the windows might be unreadable. If your browser meets these requirements but does not correctly display a Tivoli Storage Manager Web-based interface, consider using a different browser.
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see Estimating total space requirements for upgrade process and server on page 520.
Table 22-9 Hardware requirements for Linux on x86_64 Type of hardware Hardware Disk space Hardware requirements
An AMD64 or Intel EMT-64 processor The following minimum values for disk space: 5 MB for the /var directory 4 GB for the /opt directory 190 MB for the /tmp directory 300 MB for the /usr directory Additional disk space might be required for database and log files. The size of the database depends on the number of client files to be stored and the method by which the server manages them.
Memory
Software requirements
Linux x86_64 software requirements on page 513 describes the minimum software requirements.
512
7718Upgrade_Planning.fm
Table 22-10 Linux x86_64 software requirements Type of software Minimum software requirements
Operating System
The Tivoli Storage Manager server on Linux x86_64 requires one of the following operating systems: Red Hat Enterprise Linux 5 SUSE Linux Enterprise Server 10 Asianux 3.0
For Linux x86_64, GNU C libraries, Version 2.3.3-98.38 or later that is installed on the Tivoli Storage Manager system. IBM Java 1.5 or later. TCP/IP Version 4 or Version 6, which is standard with Linux Shared memory protocol (with Tivoli Storage Manager Version 6.1 A Web browser to obtain the Linux installation packages. The following browsers are supported: Microsoft Internet Explorer 6.0 SP1 Microsoft Internet Explorer 7.0 FireFox 1.5 FireFox 2.0 FireFox 3.0 Mozilla 1.7.8Your browser must support the server code page. If your browser does not support the server code page, the windows might be unreadable. If your browser meets these requirements but does not correctly display a Tivoli Storage Manager Web-based interface, consider using a different browser.
Web browser
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see Estimating total space requirements for upgrade process and server on page 520.
Table 22-11 Hardware requirements for Linux on System z Type of hardware Hardware Hardware requirements
An IBM Linux on System z 900, IBM Linux on System z 800, or IBM Linux on System z 990 server with either native logical partitions (LPARS) or VM guests. You can use 64-bit LPARs and VM guests. 64-bit LPARS and VM guests are used by the storage agent to perform LAN-free operation.
513
7718Upgrade_Planning.fm
Hardware requirements
Disk space The following minimum values for disk space: 5 MB for the /var directory 4 GB for the /opt directory 190 MB for the /tmp directory 300 MB for the /usr directory Additional disk space might be required for database and log files. The sizeof the database depends on the number of client files to be stored and themethod by which the server manages them.
Memory
Software requirements
The following table describes the minimum software requirements.
Table 22-12 Software requirements for Linux on System z Type of software Operating System Minimum software requirements
The Tivoli Storage Manager server on Linux on System z (s390x 64-bit architecture) requires one of the following operating systems: Red Hat Enterprise Linux 5, Update 3 or later SUSE Linux Enterprise Server 10, Update 2 or later
Library
Library GNU C library, Version 2.4-31.43.6 is installed on the Tivoli Storage Manager system. IBM Java 1.5 or later. TCP/IP Version 4 or Version 6, which is standard with Linux Shared memory protocol (with Tivoli Storage Manager Version 6.1 A Web browser to obtain the Linux installation packages. The following browsers are supported: Microsoft Internet Explorer 6.0 SP1 Microsoft Internet Explorer 7.0 FireFox 1.5 FireFox 2.0 FireFox 3.0 Mozilla 1.7.8 Your browser must support the server code page. If your browser does not support the server code page, the windows might be unreadable. If your browser meets these requirements but does not correctly display a Tivoli Storage Manager Web-based interface, consider using a different browser.
Web browser
514
7718Upgrade_Planning.fm
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see Estimating total space requirements for upgrade process and server on page 520.
Table 22-13 Hardware requirements for Sun Solaris Type of hardware Operating system Hardware requirements
One of the following processors required: Sun Ultra SPARC-based (sun4u architecture) Sun Ultra SPARC-based processors (sun4v architecture) x86_64-based processors (AMD64 or EM64T architecture
Disk space
The following list is the minimum disk space for Sun Ultra SPARC-based processors (sun4u and sun4v architecture) and for x86_64-based processors (AMD64 or EM64T architecture) for the respective directories and logs: 5 MB for the /var directory 2 GB for the /opt directory 310MB for the /tmp directory 300 MB for the /usr directory Additional disk space might be required for database and log files. The size of the database depends on the number of client files to be stored and the method by which the server manages them.
Memory
Software requirements
The following table describes the minimum software requirements for upgrading the Tivoli Storage Manager V6.1 server on Sun Solaris.
Table 22-14 Software requirements Type of software Minimum software requirements
Operating System
You need one of the following systems: Sun Solaris 10 or later, running in 64-bit mode on a Sun Ultra Sparcsystem with sun4u architecture Sun Solaris 10 or later, running in 64-bit mode on a system withAMD64 or EM64T architecture
515
7718Upgrade_Planning.fm
Type of software
If you have an IBM 3570, 3590 or Ultrium tape library or drive, install the most current device driver before you install Tivoli Storage Manager Version 6.1. You can locate the device drivers at ftp://ftp.software.ibm.com/storage/devdrvr/
Hardware requirements
The following table describes the minimum hardware requirements. For information about estimating the total disk space that is required, see Estimating total space requirements for upgrade process and server on page 520
Table 22-15 Hardware requirements for Windows server Type of hardware Hardware Disk space Hardware requirements
Intel Pentium compatible processor or multiprocessor-based computer At least 3 GB of free disk storage (for a typical installation) 200 MB temporary directory space 200 MB partition size in the C:\ drive Additional disk space might be required for database and log files. The server is installed in the drive you select, and the database and logs can be installed in another drive. At least 2 GB. A minimum of 4 GB for production servers. 8 GB is optimal.
Memory
Software requirements
The following table describes the minimum software requirements.
516
7718Upgrade_Planning.fm
Table 22-16 Software requirements for Windows upgrade Type of software Minimum software requirements
Operating System
One of the following systems: Microsoft Windows Server 2003: Standard, Enterprise, or Datacenter Edition Microsoft Windows Server 2003: Standard, Enterprise or Datacenter x64 Edition (64-bit) Microsoft Windows Storage Server 2003 Microsoft Windows Storage Server 2003 x64 Microsoft Windows Server 2008: Standard, Enterprise, or Datacenter Edition Microsoft Windows Server 2008: Standard, Enterprise, or Datacenter x64 Edition (64-bit)
IBM Java 1.5 or later. Named Pipes TCP/IP Version 4 or Version 6 A Web browser to log in and use the console. The Web browser can be installed on the same or a separate system. The following browsers are supported: Microsoft Internet Explorer 6.0 SP1 Microsoft Internet Explorer 7.0 FireFox 1.5 FireFox 2.0 FireFox 3.0 Mozilla 1.7.8 Your browser must support the server code page. If your browser does not support the server code page, the windows might be unreadable. If your browser meets these requirements but does not correctly display a Tivoli Storage Manager Web-based interface, consider trying a different browser.
System functions
The Windows system functions, such as Device Manager, are supported on the 64-bit Tivoli Storage Manager Console. Normal Windows system functions are available for both the 32-bit and 64-bit server using the Manage Computer function of the Windows system.
517
7718Upgrade_Planning.fm
Media method
You need media to store the data that will be extracted from the V5 database. The media can be tape, or disk space that is defined as a sequential-access disk device class. The space required for the extracted data is the same as the used space in your database. If your database is safely backed up, and you are certain that you no longer need to run the V5 server, after you extract the data you can optionally release the space used by the V5 database and recovery log.
Network method
You must have the working copy of the V5 database and recovery log on 26 IBM Tivoli Storage Manager: Server Upgrade Guide the V5 system. If you are working with a copy of the database that was created for testing the upgrade process, you need enough space to hold the total allocated size of the database; you can use the minimum size for a V5 recovery log.
Related tasks
Estimating total space requirements for the upgrade process and upgraded server on page 29
22.3.2 Space requirements for the Tivoli Storage Manager V6 server system
Before beginning the upgrade process, plan for the space that is required for the database and recovery log. You need unique, empty directories for the following items for the upgraded server: The database The recovery log Active log Archive log Optional: Log mirror for the active log Optional: Secondary archive logs (failover location for archive log)
The instance directory for the server, which is a directory that will contain files specifically for this server instance (the server options file and other server-specific files).
518
7718Upgrade_Planning.fm
Space estimates
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 manage 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. Restriction: 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. Visit the support site for the latest information and recommendations.
519
7718Upgrade_Planning.fm
Active log
The minimum size of 2 GB is large enough to complete the upgrade process. When you begin normal operations with the server, you might need to increase the size of the active log. The required size depends on the amount of concurrent activity that the server handles. A large number of concurrent client sessions might require a larger active log. For example, the server might need an 8 GB or larger active log.
Archive log
The size required depends on the number of objects stored by client nodes over the period of time between full backups of the database. Remembe that a full backup of the database causes obsolete archive log files to be pruned, to recover space. The archive log files that are included in a backup are automatically pruned after two more full database backups have been completed. If you perform a full backup of the database every day, the archive log must be large enough to hold the log files for client activity that occurs over two days. Typically 600 - 4000 bytes of log space are used when an object is stored in the server. Therefore you can estimate a starting size for the archive log using the following calculation: objects stored per day x 3000 bytes per object x 2 days For example: 5,000,000 objects/day x 3000 bytes/object x 2 days = 30,000,000,000 bytes, or 30 GB
22.3.3 Estimating total space requirements for upgrade process and server
In addition to the space required for the upgraded server itself, some additional disk space is needed for the upgrade process. For example, if you are upgrading the server on the same system where it is currently located, you need enough space for two copies of the database during the upgrade process. The space requirements for the upgraded, Tivoli Storage Manager V6.1 server depend on the size of the V5 database and other factors. The space requirements for the upgrade process also depend on how you move the data from the V5 database to the new database. You can
520
7718Upgrade_Planning.fm
move the data to the new database using the media method or the network method, with the following requirements: The media method requires sequential media. The sequential media can be tape or sequential disk device class (FILE device type). The network method requires a network connection between systems, if you are upgrading on a new system. Table 16-3 on page 267 shows basic tips for estimating each item, for each of the main scenarios. Select the scenario then read down the column. Table 16-4 on page 268 shows a sample filled-in work sheet for a 100-GB, V5 database that has 80% space utilization, with the assumption that the database increases by 33 - 50 % when upgraded.
521
7718Upgrade_Planning.fm
Network method Use a high speed link if you are extracting the data to a different system. For upgrading a database greater than 2 - 3 GB, use at least a 1-Gb Ethernet network. If you are extracting the database on the same system, no external network connections are required, however you will have options for the use of shared memory, or namedpipes as your network transport layer.
22.4.1 Performance tips for inserting data into the V6.1 database
The process for inserting the V5 extracted data into the V6.1 database is the longest-running part of an upgrade process, and is the most sensitive to the configuration of the system. On a system that meets the minimum requirements, the insertion process will run, but performance might be slow. For better performance, set up the system as described in the tips. Processors The insertion process is designed to exploit multiple processors or cores (multi-threaded). The insertion process will typically perform better on a system with a relatively small number of fast processors, rather than a system with more slower processors. Much of the activity is I/O interupt related, thus faster processors whould be more effectively utilized. Disk storage The insertion process is designed to exploit high-bandwidth disk storage subsystems. The speed of the process is highly dependent on the disk storage that is used for the source and target disk. For best performance, use multiple LUNs that map to multiple independent disks, or that map to RAID arrays with a large stripe size (for example, 128 KB). Use a different file system on each LUN. Table 22-17 on page 522 shows an example of good usage of LUNs:
Table 22-17 LUN usage
LUN
1 2 3,4,5,6 7
Usage Active log Archive log Database directories Extracted V5 database (needed only if the media method is used to extract the V5 database to a sequential disk device class) Binary file system for each instance
If the disk storage is supplied by a virtualization device (high-end storage controller, or a SAN virtualization device), ensure that none of the virtual LUNs are on the same physical disk drive. Ensure that the directories in use are on different physical disk drives within the virtualization device.
7718Upgrade_Planning.fm
test environment. Then stage the upgrade of additional servers and storage agents. Remember that you library manager server (or server instance) must be upgraded first.
523
7718Upgrade_Planning.fm
22.6 Testing
Tivoli Storage Manager 6.1 has many new features, which have contributed to new hardware and software requirements. There are some major server enhancements which require additional planning considerations include: Integrated Solutions Console and Administration Center Reporting and Monitoring Deduplication Disk structure for DB2, active logs and archive logs, storage pool volumes Disaster recovery using the Disaster Recovery Manager feature Adapting an existing V5.x Tivoli Storage Manager server infrastruction with V6.1 In addition, there are many methods of upgrading, and understanding all your options and the cost of each is important (actual monitrary and downtime costs may vary based on each scenario). For considerations when building test cases for upgrade scenarios go to Testing on page 295.
524
7718Upgrade_Planning.fm
commands and utilities go to Chapter 4, Command, utilities and option changes on page 31. Check SELECT commands that you use regularly. Some parameters and syntax that were previously allowed are not accepted by the database manager program. If you use products from independent software vendors to interface with the server, ensure that the products are compatible with the V6.1 server. Additional information on operational changes can be found in Planning for operational changes on page 297.
525
7718Upgrade_Planning.fm
526
7718UpgradeScenario 29_August.fm
23
Chapter 23.
527
7718UpgradeScenario 29_August.fm
Scenario 1 for upgrading the server: new system, media method Scenario 2 for upgrading the server: new system, network method Scenario 3 for upgrading the server: same system, media method Scenario 4 for upgrading the server: same system, network method
New system
Network method
528
7718UpgradeScenario 29_August.fm
529
7718UpgradeScenario 29_August.fm
DB audit Note: To improve the upgrade time we have discussed the Tivoli Storage Manager database re-organization as an option, this option has an unload/load itself and requires downtime so in the end you will not save time doing this. Applications such as CDP, Content Manager, and Space Manager assume Tivoli Storage Manager server is always available Customer databases may need to backup archive logs hourly Preparing space for the upgrade process Determine the amount and type of space that is required for the upgrade process before beginning the process. Verify that the system has the amount of space that was estimated in the planning step. Use the planning work sheet that you filled in with your information. Refer to Space requirements on page 262.
530
7718UpgradeScenario 29_August.fm
number of days that you set for the REUSEDELAY period for sequential-access storage pools. For important clients that use the server, check that the value for the schedlogretention client option is set to retain the client schedule log for a long enough time. Update the option for clients if needed. The entries in the client schedule log might be useful if the server must revert to the original version. If the retention period for the schedule log is too short, the schedule log information might be deleted too soon. In preparation for the upgrade, prevent activity on the server by disabling new sessions. Cancel any existing sessions. The commands in the following procedure are Tivoli Storage Manager administrative commands. To prevent all clients, storage agents, and other servers from starting new sessions with the server use the commands: disable sessions client disable sessions server Prevent administrative activity from any user ID other than the administrator ID that is being used to perform the upgrade preparation. Lock out other administrator IDs if necessary: lock admin administrator_name Check whether any sessions exist, and notify the users that the server is going to be stopped. To check for existing sessions, use the command: query session Cancel sessions that are still running. Use the command: cancel session Back up storage pools and the server database Immediately before upgrading the server, back up primary storage pools to copy storage pools, and perform a full database backup. Back up primary storage pools to copy storage pools using the BACKUP STGPOOL command. If you have been performing regular backups of the storage pools, this step backs up only the data that was added to the primary storage pools since they were last backed up. Back up the database using the following command. Use either a full or snapshot backup type. backup db type=type devclass=device_class_name The device class that you specify must exist and have volumes that are available to it. For example, to perform a snapshot backup of your database to the TAPECLASS device class using scratch volumes, enter: backup db type=dbsnapshot devclass=tapeclass To use specific volumes instead of scratch volumes, specify the volume names in the command. Consider making two copies of the backup to protect the backup from media failures. Back up configuration information Before installing the new version, back up critical files and information for the server. Store the files in a safe place, because they are needed after the installation of the new software version is completed. You also need these files if you must revert to the previous version after the upgrade.
Chapter 23. Tivoli Storage Manager V6.1 Upgrade Scenarios
531
7718UpgradeScenario 29_August.fm
Back up device configuration information: backup devconfig filenames=file_name Back up volume history information: backup volhistory filenames=file_name Ensure that the volume history includes information about the database backup that you completed in the preceding steps. For example, issue the command: query volhistory type=dbbackup Make copies of these files, which are located in the default directory for the server: server options file, typically named dsmserv.opt dsmserv.dsk Optional make a copy of the accounting log file, dsmaccnt.log Back up any scripts that have been used to perform daily housekeeping for the server. Examine the scripts for changes that are needed after the upgrade. Store the device configuration file, the volume history file, the server options file, and the other files in a safe place. Select a location that is not on the system that is being upgraded. Create a summary of database contents Create a summary of the contents of the original database. After the upgrade, you can use the same commands to compare the results and to confirm that the database contents are intact. Run commands that give a summary of information about your database contents. For example, issue commands that summarize the file spaces being protected, and save the results. See the sample commands for ideas. Stop the server before installing the upgrade Stop all server processes and dismount any tapes that are mounted. Then stop the server. The commands in the following procedure are Tivoli Storage Manager administrative commands. Cancel sessions if any are still running. Use the command: cancel session Allow time for the sessions to be stopped. Some sessions, such as backup by a backup-archive client, might take some time to stop. Determine whether server processes are running. Either cancel processes, or allow them to complete. Use the commands: query process cancel process process_number Allow time for the processes to be stopped. Some processes, such as storage pool migration, might take some time to stop. After all sessions and processes are stopped, determine whether any tapes are mounted. Dismount any tapes that are mounted. Use the commands: query mount dismount volume volume_name Stop the server using the command: halt Installing the upgrade utilities
532
7718UpgradeScenario 29_August.fm
You must install the upgrade utilities on the system where the V5 server is located. The installation package for the utilities must be downloaded from a Web site. You need an upgrade version that is greater than or equal to the level of the Tivoli Storage Manager server you are upgrading. First perform all preparation tasks on the original (source) system. Preparation includes: For the storage pools set reuse delay to the number of days during you want to be able to revert back to the original server if that becomes necessary. For each copy storage pool, set the RECLAIM parameter to 100. Backup and make copies of device configuration, volumehistory and server options files. Backup storage pools and server database, create a summary of the database contents. You can use the DSMUPGRD utility for this. Log on to source server with an administrator ID to install the upgrade utilities on the system where the V5 server is located. and run the executable package. The default location for the installation of the utilities is based on the location where the V5 server was last installed. The package to install is available for download from the FTP downloads site. The upgrade utilities are used to prepare and extract the database from the original server. Note: When we use the upgrade utilities and if we have multiple servers running on the system, we must use the -k option to specify the name of the Windows registry key from which to retrieve information about the server being upgraded.
Do not install the utilities in the same directory as the original server that is to be
upgraded, this is a restriction and is not allowed. The utilities package must be installed whether you are using the upgrade wizard or performing the upgrade manually with utilities. When we use the upgrade utilities and if we have multiple servers running on the system, we must use the -k option to specify the name of the Windows registry key from which to retrieve information about the server being upgraded. For example, if the V5 server was installed using the default path, C:\Program Files\Tivoli\TSM\server create a upgrade folder and the upgrade utilities should be installed in path C:\Program Files\Tivoli\TSM\upgrade. After the upgrade utilities are installed, continue with installing the V6.1 server on the target server. Log on to the target system as an administrator and change to the directory where you placed the executable file. n the next step, the files are extracted to the current directory. Ensure that the file is in the directory where you want the extracted files to be located. Either double-click the executable file, or enter the following command on the command line to extract the installation files. The files are extracted to the current directory. 6.1.0.0-TIV-TSMALL-platform.exeInstall the V6.1 server code on the new system. After the install is check the installations logs in path C:\Program Files\Tivoli\TSM Create the directories for the V6.1 database and logs, and the user ID that will own the server instance. We choose TSM1 as the DB2 user ID. Start the upgrade wizard by double clicking in it or run the command on following path "c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe" to configure the new server and upgrade the V5 database. With the wizard, you complete the following tasks: On the original system, prepare the V5 database.
533
7718UpgradeScenario 29_August.fm
On the new system, create and format an empty database to receive the data. Move the data from the V5 database to the V6.1 database. Configure the new system for database backup.
Complete the post-installation tasks, including backing up the database and verifying the database contents. Note: You need upgrade version that is greater than or equal to the level of the Tivoli Storage Manager server you are upgrading.
534
7718UpgradeScenario 29_August.fm
C:\Program Files\Tivoli\TSM\server, the upgrade utilities are installed in C:\Program Files\Tivoli\TSM\upgrade. Tip: When you use the upgrade utilities, if you have multiple servers running on the system, you must use the -k option to specify the name of the Windows registry key from which to retrieve information about the server being upgraded. The default value for the option is SERVER1. Use the -o option with the DSMUPGRD command to specify the location of the server options file. On the source system run the install.exe, then run the upgrade wizard tool dsmupgdx.exe in the c:\Program Files\Tivoli\TSM\server\ directory. The V6.1 server upgrade window will open. We choose the appropriate language and click OK to continue (see Figure 23-1).
The next window is the Welcome screen. Carefully read the information and before you begin make sure that you have installed the upgrade utilities package in the system where the original version 5.3 or later is located and click Next to continue (see Figure 23-2 on page 536).
535
7718UpgradeScenario 29_August.fm
To validate the user ID and password, a connection will be made to the local system using SSH, RSH, REXEC, or SMB protocol. SMB is the interface used by File and Print Sharing (also known as CIFS). To use the SMB protocol, you must make sure that File and Print Sharing is enabled, and that port 445 is not blocked by your firewall. Additionally, if you are running on Windows Server 2008 or Windows Vista, you may need to disable User Account Control (at least while running this wizard). If you choose not to disable User Account Control, you must make sure one of the other protocols is configured to allow the wizard to proceed The intaller checks if you have administrator rights and if that is succesfully you see the Target System Authentication screen (see Figure 23-3 on page 537). This panel helps to connect to other systems where V5 is installed and asks where the server is to be upgraded and we also fill in the hostname and the administrator ID to establish a connection. Click Next to continue.
536
7718UpgradeScenario 29_August.fm
If you are upgrading a new server, select "Begin a new upgrade process...". If you are restarting an upgrade or continuing an upgrade in progress, select "Continue the upgrade process...", and select the dsmserv.dsk file representing the upgrade you wish to restart or continue. If you have no upgrades in progress, the "Continue" selection is disabled. Here we have the option to begin an upgrade already selected since this is the first upgrade on this server (see Figure 23-4 on page 538). Click Next to continue.
537
7718UpgradeScenario 29_August.fm
Figure 23-4 Tivoli Storage Manager V6.1 server upgrade - Select Upgrade
Here we five options and we will come back to this screen over and over again when a phase is completed during the upgrade process. The only selectable option on this panel here is the Prepare the database for the upgrade where we start the prepare of the selected Tivoli Storage Manager database. If you wish to interrupt the upgrade process, it is best to do it while on this panel. Upon restarting the wizard, you can continue where you left off. If an upgrade phase is not yet allowed, it is disabled. If you select to re-run a phase that has already completed, you must re-run all phases after the phase you select to re-run. For example, if you are ready to begin the Insertion phase, but instead choose to re-run the Prepare phase, you must then complete all steps after the Prepare phase again. You cannot skip a phase (see Figure 23-5 on page 539. Click Next to continue.
538
7718UpgradeScenario 29_August.fm
Figure 23-5 Tivoli Storage Manager 6.1 server upgrade prepare database for upgrade
Then we are asked to select the Tivoli Storage Manager Server instance to upgrade where the dsmserv.dsk and dsmserv.opt file resides (see Figure 23-6 on page 540). Click Next to continue.
539
7718UpgradeScenario 29_August.fm
Figure 23-6 Tivoli Storage Manager 6.1 server upgrade - Select Upgrade
We can see the database and recovery log voumes created during the V5.5 database restore we performed in order to be able to run a test restore. Verify the paths of the database and logs being upgraded are correct and click Next to prepare this database for the upgrade (see Figure 23-7 on page 541).
540
7718UpgradeScenario 29_August.fm
Figure 23-7 Tivoli Storage Manager 6.1 server upgrade - Verify Server Selection
Now we started the Prepare phase... We can see the database prepare content in the Prepare Database window. It is an Echo for looking for the ANR1291 message to set the return code to 0 meaning that the Preparation phase was completed. You can view the full text of a message from the Tivoli Storage Manager Information Center at: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp To display a message, enter the message ID in the Search field and click Go (see Figure 23-8 on page 542). Note: If the upgrade wizard shows a non-zero return code, scroll up and check the messages displayed in the panel, or check the output file for the operation. If there is a success message that is wrapped, then the operation did complete successfully. Under the target machine "C:\Program Files\Tivoli\TSM\server1" we have the prepare.out file were we also can see the contents output from the prepare process
541
7718UpgradeScenario 29_August.fm
Figure 23-8 Tivoli Storage Manager 6.1 server upgrade preparation phase
When you click Next you are brought back to the Select Upgrade Phase window where you select that we want to perform an upgrade. The wizard will come back to this panel as you progress through the upgrade. If you wish to interrupt the upgrade process, it is best to do it while on this panel. Upon restarting the wizard, you can continue where you left off. If a phase is not yet allowed, it is disabled. If you select to re-run a phase that has already completed, you must re-run all phases after the phase you select to re-run. For example, if you are ready to begin the Insertion phase, but instead choose to re-run the Prepare phase, you must then complete all steps after the Prepare phase again. You cannot skip a phase (see Figure 23-9 on page 543). Click Next to continue.
542
7718UpgradeScenario 29_August.fm
Here we can see information that the server upgrade can be performed using one of two methods: media or network (see Figure 23-10 on page 544). In our scenario we select to use the network option. The media method extracts all data from the existing database and stores it on tape or other media. The data is then loaded into the target system from the media. The network method requires that both source and target servers to be up and running. The data is transmitted directly from the source server to the target server over the network. This method requires: Enough disk space to have both the source and target servers up and running at the same time if the upgrade is done on the same server. A network connection of sufficient bandwidth between the source system and the target system. The network method also works if both databases are on the same system. Click Next to continue.
543
7718UpgradeScenario 29_August.fm
When you click Next you are brought back to the Select Upgrade Phase window. Note that the third choice (Extract the existing database to media) and the fifth choice (Insert the data into the new server instance) are not enabled. This is because we are doing the Extract and Insert at the same time and therefore we have the configure the new server instance button already selected (see Figure 23-11 on page 545). As stated previously, the wizard will come back to this panel as you progress through the upgrade. If you wish to interrupt the upgrade process, it is best to do it while on this panel. Upon restarting the wizard, you can continue where you left off. Click Next to continue.
544
7718UpgradeScenario 29_August.fm
Figure 23-11 Tivoli Storage Manager 6.1 server upgrade - Configure the new server instance
The Modify Disk Configuration window indicates this phase of the upgrade process requires that the new database and log directories are available on the target system. If you are reusing disks from the existing database, make any desired or necessary changes to your file systems or disk subsystems before proceeding. Click Next to begin the creation of the new server instance (see Figure 23-12 on page 546).
545
7718UpgradeScenario 29_August.fm
Figure 23-12 Tivoli Storage Manager 6.1 server upgrade - Modify Disk Configuration
In the Instance User ID window specify the user ID and the password of the new instance owner. Note that a user ID can own only one intance so ensure that you select the user ID that does not already own an intance. This user ID must already exist on the system. When we click Next the wizard will attempt to establish a third connection to the local machine (see Figure 23-13 on page 547).
546
7718UpgradeScenario 29_August.fm
Figure 23-13 Tivoli Storage Manager 6.1 server upgrade - Instance User ID
Next specify the instance directory that stores all of the server instance information such as the server options file, trace files, and other files specific to this instance (see Figure 23-14 on page 548). You must manualy create the server instance folder. If you click Choose before creating that folder you will get an error message similar to the following: Directory C:\Program Files\Tivoli\TSM\Server1 was not found or is not accessible
547
7718UpgradeScenario 29_August.fm
Figure 23-14 Tivoli Storage Manager 6.1 server upgrade - Instance Directory
The Tivoli Storage Manager database is stored in a series of directories (containers) managed by the database manager (DB2). To improve data throughput, specify a large number of directories to allow the database manager to spread the workload over multiple disks. There are two ways to specify the database directories: Create a temporary file, and place each database directory on its own line in the file, then specify the location of the file in the top field, or specify each database directory directly in the bottom field, one directory per line. Each database directory must be empty, and, for maximum performance, should reside on its own dedicated disk. We chose to specify a list of four directories per line to use for the Tivoli Storage Manager database (see Figure 23-15 on page 549). Note that you can use up to 128 directories for the database. After specifying the directories click Next to continue.
548
7718UpgradeScenario 29_August.fm
Figure 23-15 Tivoli Storage Manager 6.1 server upgrade - Database Directories
In the Recovery Log Directories panel specify the directories of the database recovery logs (see Figure 23-16 on page 550). The active log directory contains all transactions currently in progress on the server. If the system crashes or the server stops, the active log is all that is required to restart the server. The active log is broken up into files. After all transactions in a log file are completed, the log file is copied to an archive log directory. If a log file cannot be copied to the primary archive log directory, it is copied to the ArchiveLogFailover log directory, if specified. If a log file cannot be copied to either log directory, it remains in the active directory. If the active log fills up, transactions will fail. Therefore, ensure that the archive log directories are online with sufficient space to hold the log files. Logs in the archive log directories can be moved to another location, but these logs must be returned to the archive directory to perform a database restore operation. The mirror log directory contains the same contents as the active log directory, and is used for redundancy in case of disk failure. If your active log directory resides on a disk that is already mirrored or has other RAID protection, you might not need to specify a mirror log directory. After specifying the database recovery log directories click Next to continue.
549
7718UpgradeScenario 29_August.fm
Figure 23-16 Tivoli Storage Manager 6.1 server upgrade - Recovery Log Directories
The Configuration Summary window provides a list of the information you have input previously. It shows the Instance user ID, the Tivoli Storage Manager instance directory, the four database containers defined, and the log files directories (see Figure 23-17 on page 551). Click Next to continue.
550
7718UpgradeScenario 29_August.fm
Figure 23-17 Tivoli Storage Manager 6.1 server upgrade - Configuration Summary
Here we have started the configuration of the instance. The configuration has many steps and will take several minutes. After the configuration is finished we can see the load format was completed with return code 0 (see Figure 23-18 on page 552). Note: What happens to the database backup performed during 'dsmserv format' or 'dsmserv loadformat' is that during the server installation format processing for V6.1, you will see that the server performs a backup of the database. This can be seen by the messages: ANR2976I Offline DB backup for database TSMDB1 started. ANR2974I Offline DB backup for database TSMDB1 completed successfully. This initial backup is required by DB2 in order for Tivoli Storage Manager to set the recovery log processing mode to ROLLFORWARD. At this point, this database backup only contains the server schema (DDL). This database backup is performed to a file in the local filesystem. This database backup is subsequently deleted by Tivoli Storage Manager since it only contains the server schema definitions which can be recreated by Tivoli Storage Manager anyway. After completing the installation and configuration of the Tivoli Storage Manager server, it is recommended that a FULL database backup be performed. This database backup and any subsequent database backups will be tracked in the server volume history, as expected, and used as part of the server disaster recovery manager (DRM) processing.
551
7718UpgradeScenario 29_August.fm
Figure 23-18 Tivoli Storage Manager 6.1 server upgrade - Configure Instance
The last phase is to insert the data into the new server instance (see Figure 23-19 on page 553). Remember that is you cancel the installation step Select the phase of the upgrade to perform the wizard will come back to this panel as you progress through the upgrade. Click Next to continue.
552
7718UpgradeScenario 29_August.fm
Figure 23-19 Tivoli Storage Manager 6.1 server upgrade - insert data into the new server instance
The final step in the server upgrade (see Figure 23-20 on page 554).
553
7718UpgradeScenario 29_August.fm
Figure 23-20 Tivoli Storage Manager 6.1 server upgrade - Load New Database
The contents of the existing database will now be loaded into the new data base. Remember we are using the network method and the new server will be started first, then the existing database will be started and the data will be transferred. Click Next to begin the load process. Data from the existing server will be inserted into the new database (see Figure 23-21 on page 555).
554
7718UpgradeScenario 29_August.fm
Figure 23-21 Tivoli Storage Manager 6.1 server upgrade - Load New Database
Monitor the insertion process by viewing the messages in the display area. The messages can also be viewed after by scrolling the message text in the windows (see Figure 23-22 on page 556).
555
7718UpgradeScenario 29_August.fm
Figure 23-23 on page 557 shows we got the error code 405 on the INSERTDB process and the error code 0 on the EXTRACTDB process.
556
7718UpgradeScenario 29_August.fm
Figure 23-23 Tivoli Storage Manager 6.1 server upgrade - upgrade messages
You can view the full text of a message from the Tivoli Storage Manager Information Center at http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp To display a message, enter the message ID in the Search field and click Go.
ANR1336I INSERTDB: Ready for connections from the source server. Remaining time: 1:00:00 ANR8206I TCP/IP Version 4 administrative driver ready for connection with clients on port 1500. ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1525. ANR1336I INSERTDB: Ready for connections from the source server. Remaining time: 0:59:30
557
7718UpgradeScenario 29_August.fm
ANR0408I Session 1 started for server $UPGRADESOURCE$ (Windows) (Tcp/Ip) for V6 Database Upgrade. ANR1337I A DBSPACE trigger has been removed. Not used in V6.1 ANR1337I A LOGSPACE trigger has been removed. ANR1379I INSERTDB: Read 34,249,632 bytes and inserted 251,422 database entries in 0:00:00 (0.00 megabytes per hour). ANR1379I INSERTDB: Read 606,450,451 bytes and inserted 4,391,709 database entries in 0:05:11 (6690.68 megabytes per hour). ANR1379I INSERTDB: Read 1,085,441,646 bytes and inserted 7,607,483 database entries in 0:10:18 (6029.13 megabytes per hour). ANR1379I INSERTDB: Read 1,325,219,033 bytes and inserted 9,413,251 database entries in 0:15:26 (4910.15 megabytes per hour). ANR1379I INSERTDB: Read 1,575,287,817 bytes and inserted 11,155,415 database entries in 0:20:29 (4399.67 megabytes per hour). ANR1379I INSERTDB: Read 1,821,897,938 bytes and inserted 13,048,509 database entries in 0:25:34 (4076.40 megabytes per hour). ANR1379I INSERTDB: Read 2,084,615,297 bytes and inserted 14,751,729 database entries in 0:30:36 (3898.04 megabytes per hour). ANR0409I Session 1 ended for server $UPGRADESOURCE$ (Windows). ANR0136I Table updating statistics performed successfully for 5 of 5. ANR1524I INSERTDB: Beginning database update phase. ANR1525I INSERTDB: Updated 234 of 4,373,439 database entries in 0:02:15. ANR1525I INSERTDB: Updated 234 of 4,373,439 database entries in 0:07:15. ANR1525I INSERTDB: Updated 4,373,439 of 4,373,439 database entries in 0:11:05 ANR1395I INSERTDB: Process 1, database insert, has completed. ANR1397I INSERTDB: Found 82 database objects. ANR1398I INSERTDB: Processed 82 database objects. ANR1399I INSERTDB: Failed to process 0 database objects. ANR1517I INSERTDB: Processed 15,859,059 database records. ANR1518I INSERTDB: Read 2,207,931,666 bytes. ANR1519I INSERTDB: Elapsed time was 0:55:07. ANR1445I INSERTDB: Throughput was 2291.50 megabytes per hour. ANR1446I RUNSTATS: Table updating statistics started. ANR0136I Table updating statistics performed successfully for 119 of 119. ANR1528I RUNSTATS: Table updating statistics completed in 0:14:43. ANR0369I Stopping the database manager because of a server shutdown.
7718UpgradeScenario 29_August.fm
The Insertion process completed with return code 405. For the INSERTDB, the message ANR1395I indicates success.
Waiting for the new server to initialize... ANR0900I Processing options file C:\Program Files\Tivoli\TSM\server1\dsmserv.opt. ANR7800I DSMSERV generated at 12:07:33 on Mar 12 2009. Tivoli Storage Manager for Windows Version 5, Release 5, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 1000 megabytes. ANR0201I Database assigned capacity is 5000 megabytes. ANR0306I Recovery log volume mount in progress. ANR0285I Database page shadowing started using file dbpgshdw.bdt. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANR1635I The server machine GUID, 23.47.17.a1.e3.cf.11.dd.b7.b4.00.50.56.90.7c.69, has initialized. ANR4726I The NAS-NDMP support module has been loaded. Removed som uncessesary information from the output.. ANR4029I EXTRACTDB: Database checkpoint started. ANR4030I EXTRACTDB: Database checkpoint completed. ANR0610I EXTRACTDB started by ADMINISTRATOR as process 1. ANR0408I Session 1 started for server $UPGRADETARGET$ (Windows) (Tcp/Ip) for V6 Database Upgrade. ANR1392I EXTRACTDB: Extracted 3,736,534 database entries in 197,824 pages and wrote 515,744,948 bytes in 0:05:00 (5892.00 megabytes per hour). ANR1392I EXTRACTDB: Extracted 7,143,650 database entries in 410,279 pages and wrote 1,030,018,805 bytes in 0:10:00 (5892.00 megabytes per hour). ANR1392I EXTRACTDB: Extracted 9,045,569 database entries in 506,661 pages and wrote 1,274,861,977 bytes in 0:15:07 (4822.49 megabytes per hour). ANR1392I EXTRACTDB: Extracted 11,123,470 database entries in 622,107 pages and wrote 1,569,211,751 bytes in 0:20:07 (4461.97 megabytes per hour). ANR1392I EXTRACTDB: Extracted 12,796,983 database entries in 703,265 pages and wrote 1,794,542,333 bytes in 0:25:07 (4087.33 megabytes per hour). ANR1392I EXTRACTDB: Extracted 14,352,904 database entries in 792,509 pages and wrote 2,005,587,569 bytes in 0:30:07 (3809.19 megabytes per hour). ANR0409I Session 1 ended for server $UPGRADETARGET$ (Windows). ANR1382I EXTRACTDB: Process 1, database extract, has completed. ANR1383I EXTRACTDB: Found 124 database objects. ANR1384I EXTRACTDB: Processed 82 database objects. ANR1385I EXTRACTDB: Skipped 42 empty database objects. ANR1386I EXTRACTDB: Failed to process 0 database objects.
Chapter 23. Tivoli Storage Manager V6.1 Upgrade Scenarios
559
7718UpgradeScenario 29_August.fm
Processed 15,859,059 database records. Read 879,821 database pages. Wrote 2,207,931,596 bytes. Elapsed time was 0:34:47. Throughput was 3631.05 megabytes per hour.
Figure 23-24 on page 560 is the Upgrade Complete window. Click Done and review the installation logs.
Figure 23-24 Tivoli Storage Manager 6.1 server upgrade - Upgrade Complete
After the upgrade process is done we start the Tivoli Storage Manager V6.1 server on the new system. We start the server in the foreground with DSMSERV and look for error messages that would indicate options that are not supported with the the Tivoli Storage Manager V6.1 server that was defined in the V5.5 test database. Important: It is possible, after the upgrade to V6.1 is complete, that conditions might cause the need to temporarily revert to the previous version of the server. Successfully reverting to the previous version of the server is possible only if you performed all preparation steps. To understand why it is important to perform all preparation steps, review the procedure for reverting an upgraded server to its previous version in 23.8, How to rollback to V5 if needed or restart the process on page 567.
560
7718UpgradeScenario 29_August.fm
561
7718UpgradeScenario 29_August.fm
Methods
The methods of backup for the Tivoli Storage Mananager V6.1 database are: Full Backup This is typically done through Tivoli Storage Manager Admin Schedule. You can also use server-to-server for device class of backup. Incremental Backup Not quite the same as Tivoli Storage Mananager 5.x incremental backup. You also use server-to-server for device class of backup. Tivoli Storage Manager database Snapshot This typically done through Tivoli Storage Manager Admin Schedule and it does not clear out archive logs. You can also use server-to-server for device class of backup. Note: DB2 Snapshot is not supported in this release
562
7718UpgradeScenario 29_August.fm
563
7718UpgradeScenario 29_August.fm
select count(*) as Number of Client Option Sets from cloptsets select count(*) as Number of Collocation Groups from collocgroup select count(*) as Number of Archive CopyGroups from ar_copygroups select count(*) as Number of Backup CopyGroups from bu_copygroups select count(*) as Number of Data Movers from datamovers select count(*) as Number of Device Classes from devclasses select count(*) as Number of Domains from domains select count(*) as Number of Drives from drives select count(*) as Number of Libraries from libraries select count(*) as Number of Library Volumes from libvolumes select count(*) as Number of Volumes from volumes select count(*) as Number of Management Classes from mgmtclasses select count(*) as Number of Node Groups from nodegroup select count(*) as Number of Device Paths from paths select count(*) as Number of Policy Sets from policysets select count(*) as Number of Client Schedules from client_schedules select count(*) as Number of Admin Schedules from admin_schedules select count(*) as Number of Server Scripts from scripts select count(*) as Number of Servers Defined from servers select count(*) as Number of Servers Groups Defined from server_group select count(*) as Number of Storage Pools Defined from stgpools
564
7718UpgradeScenario 29_August.fm
Update dsmserv.opt ActiveLogDir to point to new directory Halt and restart the Tivoli Storage Manager Server. DB2 automatically moves active logs to new directory. Note the procedure is different for moving the archive logs to a new location. You should specify a new directory for the archive logs in the dsmserv.opt file on the archivelogdir parameter. In this case, however, when Tivoli Storage Manager is restarted, the existing archive logs are not moved but rather are just kept in the old location. New archive logs are written to the new location. The archive logs are then cleared when a database backup is done, and the logs are older than 2 full backups ago Add mirroring to the Tivoli Storage Manager V6 database Make a new empty directory for the log mirrors Update the dsmserv.opt file MirrorLogDir Parameter Stop and restart the Tivoli Storage Manager Server Extend the Tivoli Storage Manager V6 database? Create a new empty directory to contain the database volumes Issue the Extend DBSpace command with the new database directory. Database is dynamically extended; there is no need to restart Tivoli Storage Manager. Recover the database when a disk from the database goes bad using a database restore to the current point in time. Determine a new location with same amount of space Create a text file containing the list of directories for the database Using DB2, drop the DB Do a dsmserv restore db on=filename where filename is the name of the file created in previous step. Restart the Tivoli Storage Manager Server Increase the size of the Active Logs Insure that the location for the active logs has enough space for thenew log size to be used. Edit dsmserv.opt file for the Tivoli Storage Manager Server instance. Change or Add the ActiveLogSize parameter to the file. (Size is in MB; minimum is 2GB, maximum is 128GB) Restart Tivoli Storage Manager New logs will be automatically defined, each 512MB in size until the ActiveLogSize amount is reached. Mirrors, if being used. are also re-defined. Reduce Tivoli Storage Manager V6.1 database after deleting data Create a file containing list of directories that you want to use. Do a full databse backup. Halt the Tivoli Storage Manager server Using DB2, drop the database Do a dsmserv restore db on= command specifying the file you created in the first step. Restart the Tivoli Storage Manager server.
565
7718UpgradeScenario 29_August.fm
SQL example
Example 23-4 is an example of a select command that creates temporary workspace within DB2.
Example 23-4 This is an example of a select command that creates temporary workspace within DB2
select node_name,count(*) as Number_of_Objects, sum(file_size) as Bytes_of_WKLD from contents where node_name='61SOURCE18' and filespace_id=1 and file_name like '\WKLD%' group by node_name
db2 "select TSMDB1.AS_SEGMENTS.PVRPOS as ClipID from TSMDB1.AS_SEGMENTS,TSMDB1.AF_SEGMENTS where TSMDB1.AF_SEGMENTS.BFID=42803004 and TSMDB1.AS_SEGMENTS.VOLID=TSMDB1.AF_SEGMENTS.VOLID and TSMDB1.AS_SEGMENTS.START=TSMDB1.AF_SEGMENTS.START"
566
7718UpgradeScenario 29_August.fm
db2 "select tsmdb1.AF_SEGMENTS.BFID as ObjID from tsmdb1.AF_SEGMENTS,tsmdb1.AS_SEGMENTS where tsmdb1.AS_SEGMENTS.PVRPOS=x'37 ... 542 and tsmdb1.AS_SEGMENTS.VOLID=tsmdb1.AF_SEGMENTS.VOLID and tsmdb1.AS_SEGMENTS.START=tsmdb1.AF_SEGMENTS.START
567
7718UpgradeScenario 29_August.fm
23.9 Debugging
In cases where you need to investigate log messages there are several files where information is available.
568
7718UpgradeScenario 29_August.fm
Example 23-7 Macro with a series of select statements for use to compare the database upgrade
select node_name, count(*) as "Number of Filespaces" from filespaces group by node_name order by 2 select platform_name, count(*) as "Number of Nodes" from nodes group by platform_name select node_name,sum(num_files) as "Number of Backup Files" from occupancy where type='Bkup' group by node_name select node_name,sum(num_files) as "Number of Archive Files" from occupancy where type='Arch' group by node_name select count(*) as "Number of Management Classes" from mgmtclasses select count(*) as "Number of Server Scripts" from script_names select count(*) as "Number of Storage Pools" from stgpools
After running these select statements in a macro, the output of our Tivoli Storage Manager V5.5.2 server is as shown in Example 23-8.
Example 23-8 Select statement output
ANS8000I Server command: 'select node_name, count(*) as "Number of Filespaces" from filespaces group by node_name order by 2' NODE_NAME -----------------BMICHLER BOGDAN_ORACLE BRIGITTE BZIEMANN JONATHAN KARIN LINUX-TEST ORA1 LT-JS NAS1 RAINER TESTPC-081 GERD RS6000_CLIENT Number of Filespaces -------------------1 1 1 1 1 1 1 1 2 2 2 3 8 9
ANS8000I Server command: 'select platform_name, count(*) as "Number of Nodes" from nodes group by platform_name' PLATFORM_NAME ---------------AIX Linux86 Mac NetApp TDPO Linux86 WinNT Number of Nodes --------------2 1 2 1 1 2 9
ANS8000I Server command: 'select node_name,sum(num_files) as "Number of Backup Files" from occupancy where type='Bkup' group by node_name'
569
7718UpgradeScenario 29_August.fm
NODE_NAME Number of Backup Files --------------------------------------BMICHLER 17258 BOGDAN_ORACLE 61 BZIEMANN 118 GERD 48097 JONATHAN 6966 KARIN 6 LINUX-TEST 470 LT-JS 696138 NAS1 5 ORA1 46 RAINER 1974 RS6000_CLIENT 110683 TESTPC-081 195254 ANS8000I Server command: 'select node_name,sum(num_files) as "Number of Archive Files" from occupancy where type='Arch' group by node_name' NODE_NAME Number of Archive Files ---------------------------------------GERD 40852 LT-JS 32 TESTPC-081 38 ANS8000I Server command: 'select count(*) as "Number of Management Classes" from mgmtclasses' Number of Management Classes ---------------------------11 ANS8000I Server command: 'select count(*) as "Number of Server Scripts" from script_names' Number of Server Scripts -----------------------20 ANS8000I Server command: 'select count(*) as "Number of Storage Pools" from stgpools' Number of Storage Pools ----------------------15
Now, after collecting our comparision data, we then procede to perform the manual upgrade steps, as indicated in the process flow that follows. 1. Extract the data from the V5.5.2 server as shown in Example 23-9.
Example 23-9 AIX sample data extraction
# cd /usr/tivoli/tsm/upgrade/bin
570
7718UpgradeScenario 29_August.fm
# /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb ANR7800I DSMSERV generated at 12:32:53 on Mar 11 2009. Tivoli Storage Manager for AIX-RS/6000 Version 5, Release 5, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt. ANR7811I Using instance directory /usr/tivoli/tsm/server/bin. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 1112 megabytes. ANR0201I Database assigned capacity is 2144 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANR1635I The server machine GUID, 00.00.00.00.ac.29.11.dd.a1.26.08.63.c0.a8.6f.0e, has initialized. ANR2283I Database backup trigger defined, but is disabled. ANR4726I The NAS-NDMP support module has been loaded. ANR1794W TSM SAN discovery is disabled by options. ANR1747W The data mover NAS1 was not found on the SAN. The data mover definition has been marked offline. ANR8440E Initialization failed for SCSI library LIB1; will retry in 2 minute(s). ANR1305I Disk volume /usr/tivoli/tsm/server/bin/backup.dsm varied online. ANR1305I Disk volume /usr/tivoli/tsm/server/bin/tcovol01.dsm varied online. ANR1305I Disk volume /usr/tivoli/tsm/server/bin/archive.dsm varied online. ANR1305I Disk volume /usr/tivoli/tsm/server/bin/spcmgmt.dsm varied online. ANR1412W Volume 610AGB access mode is "unavailable". ANR2718W Schedule manager disabled. ANR0129I Database upgrade completed successfully. ANR0993I Server initialization complete. ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use. ANR1444W PREPAREDB: Database upgrade may not be supported for this server because it uses backup sets. ANR1445W PREPAREDB: Database upgrade may not be supported for this server because it uses NAS backups with TOCs. ANR0991I Server shutdown complete. # /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb devclass=dcupgrade manifest=/tsm/upgrade/manifest.txt ANR7800I DSMSERV generated at 12:32:53 on Mar 11 2009. Tivoli Storage Manager for AIX-RS/6000 Version 5, Release 5, Level 2.0
571
7718UpgradeScenario 29_August.fm
Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt. ANR7811I Using instance directory /usr/tivoli/tsm/server/bin. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 1112 megabytes. ANR0201I Database assigned capacity is 2144 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANR1635I The server machine GUID, 00.00.00.00.ac.29.11.dd.a1.26.08.63.c0.a8.6f.0e, has initialized. ANR2283I Database backup trigger defined, but is disabled. ANR4726I The NAS-NDMP support module has been loaded. ANR1794W TSM SAN discovery is disabled by options. ANR1747W The data mover NAS1 was not found on the SAN. The data mover definition has been marked offline. ANR8440E Initialization failed for SCSI library LIB1; will retry in 2 minute(s). ANR1305I Disk volume /usr/tivoli/tsm/server/bin/spcmgmt.dsm varied online. ANR1305I Disk volume /usr/tivoli/tsm/server/bin/archive.dsm varied online. ANR1305I Disk volume /usr/tivoli/tsm/server/bin/backup.dsm varied online. ANR1305I Disk volume /usr/tivoli/tsm/server/bin/tcovol01.dsm varied online. ANR1412W Volume 610AGB access mode is "unavailable". ANR1444W EXTRACTDB: Database upgrade may not be supported for this server because it uses backup sets. ANR1445W EXTRACTDB: Database upgrade may not be supported for this server because it uses NAS backups with TOCs. ANR4029I EXTRACTDB: Database checkpoint started. ANR4030I EXTRACTDB: Database checkpoint completed. ANR0610I EXTRACTDB started by ADMINISTRATOR as process 1. ANR8340I FILE volume /tsm/upgrade/45449177.ost mounted. ANR1360I Output volume /tsm/upgrade/45449177.ost opened (sequence number 1). ANR8439I SCSI library VTL_BIG is ready for operations. ANR8439I SCSI library VTL_SMALL is ready for operations. ANR8439I SCSI library VTL1 is ready for operations. ANR1361I Output volume /tsm/upgrade/45449177.ost closed. ANR1380I EXTRACTDB: Output stream 1 used volume /tsm/upgrade/45449177.ost. ANR1382I EXTRACTDB: Process 1, database extract, has completed. ANR1383I EXTRACTDB: Found 121 database objects. ANR1384I EXTRACTDB: Processed 82 database objects. ANR1385I EXTRACTDB: Skipped 39 empty database objects. ANR1386I EXTRACTDB: Failed to process 0 database objects. ANR1387I EXTRACTDB: Processed 2,999,980 database records. ANR1388I EXTRACTDB: Read 141,121 database pages. ANR1389I EXTRACTDB: Wrote 464,498,292 bytes.
572
7718UpgradeScenario 29_August.fm
ANR1390I EXTRACTDB: Elapsed time was 0:01:41. ANR1391I EXTRACTDB: Throughput was 15754.46 megabytes per hour.
2. Prepare the disk for the database and logs on the Unix system. 3. Issue the DSMSERV LOADFORMAT command, as shown in Example 23-10.
Example 23-10 Preparing the Tivoli Storage ManagerServer instance directories and DB2 environment
$ dsmserv -u tsm2 -i /home/tsm2 loadformat dbdir=/tsm2/dbdir001,/tsm2/dbdir002,/tsm2/dbdir003,/tsm2/dbdir004 activelogsize=8192 activelogdir=/tsm2/actlog archlogdir=/tsm2/archlog mirrorlogdir=/tsm2/activelogm Tivoli Storage Manager for AIX Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I ANR0900I ANR7811I ANR4726I ANR0152I ANR0152I ANR1380I ANR1004I ANR0369I ANR2976I Subsystem process ID is 442498. Processing options file /home/tsm2/dsmserv.opt. Using instance directory /home/tsm2. The ICC support module has been loaded. Database manager successfully started. Database manager successfully started. The buffer pool monitor switch is enabled. Server formatting complete, database ready for loading. Stopping the database manager because of a server shutdown. Offline DB backup for database TSMDB1 started.
ANR2974I Offline DB backup for database TSMDB1 completed successfully. $ Next, we perform the DSMSERV INSERTDB command, as shown in Example 23-11.
Example 23-11 DSMSERV INSERTDB command
$ dsmserv insertdb man=/code/upgradedb/manifest.txt Tivoli Storage Manager for AIX Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7801I Subsystem process ID is 442544. ANR0900I Processing options file /home/tsm2/dsmserv.opt.
Chapter 23. Tivoli Storage Manager V6.1 Upgrade Scenarios
573
7718UpgradeScenario 29_August.fm
ANR7811I Using instance directory /home/tsm2. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0153I Database manager already running. ANR1380I The buffer pool monitor switch is enabled. ANR1636W The server machine GUID changed: old value (), new value (00.00.00.00.4f.96.11.de.82.b2.08.63.09.0c.05.7f). ANR1386I Beginning schema verification for the database insert process. ANR1387I Schema verification for the database insert process has completed. ANR8340I FILE volume /code/upgradedb/45449177.ost mounted. ANR1363I Input volume /code/upgradedb/45449177.ost opened (sequence number 1). ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1502. ANR1337I A DBBACKUP trigger has been removed. ANR1337I A LOGSPACE trigger has been removed. ANR1526I INSERTDB: Building indices and checking table integrity. ANR1364I Input volume /code/gerd-upgradedb/45449177.ost closed. ANR1527I INSERTDB: Checked 82 of 82 database objects in 0:00:43. ANR0136I Table updating statistics performed successfully for 4 of 4. ANR1524I INSERTDB: Beginning database update phase. ANR1525I INSERTDB: Updated 750,338 of 750,338 database entries in 0:00:43. ANR1395I INSERTDB: Process 1, database insert, has completed. ANR1397I INSERTDB: Found 82 database objects. ANR1398I INSERTDB: Processed 82 database objects. ANR1399I INSERTDB: Failed to process 0 database objects. ANR1517I INSERTDB: Processed 2,999,980 database records. ANR1518I INSERTDB: Read 464,498,436 bytes. ANR1519I INSERTDB: Elapsed time was 0:04:00. ANR1445I INSERTDB: Throughput was 6630.00 megabytes per hour. ANR1446I RUNSTATS: Table updating statistics started. ANR0136I Table updating statistics performed successfully for 119 of 119. ANR1528I RUNSTATS: Table updating statistics completed in 0:00:28. ANR0369I Stopping the database manager because of a server shutdown.
After the insertion has completed, we then start the Tivoli Storage Manager Server instance and review the content to ensure we have transferred all our nodes and object pointers. Here is the V6.1 Tivoli Storage Manager Server macro output for comparison after our database upgrade, as seen in Example 23-12 on page 574.
Example 23-12 Select commands run on V6.1 Tivoli Storage Manager Server after insertdb completed
ANS8000I Server command: 'select node_name, count(*) as "Number of Filespaces" from filespaces group by node_name order by 2' NODE_NAME Number of Filespaces --------------------------------------------------------------BMICHLER 1 BOGDAN_ORACLE 1 BRIGITTE 1 BZIEMANN 1 JONATHAN 1 KARIN 1 LINUX-TEST 1 ORA1 1 574
Tivoli Storage Manager V6.1 Technical Guide
7718UpgradeScenario 29_August.fm
2 2 2 3 8 9
ANS8000I Server command: 'select platform_name, count(*) as "Number of Nodes" from nodes group by platform_name' PLATFORM_NAME -----------------AIX Linux86 Mac NetApp TDPO Linux86 WinNT Number of Nodes ---------------1 2 1 1 2 9 2
ANS8000I Server command: 'select node_name,sum(num_files) as "Number of Backup Files" from occupancy where type='Bkup' group by node_name' NODE_NAME Number of Backup Files ----------------------------------------------------------------------BMICHLER 17258 BOGDAN_ORACLE 61 BZIEMANN 118 GERD 48098 JONATHAN 6966 KARIN 6 LINUX-TEST 470 LT-JS 696138 NAS1 5 ORA1 46 RAINER 1974 RS6000_CLIENT 110683 TESTPC-081 195254
ANS8000I Server command: 'select node_name,sum(num_files) as "Number of Archive Files" from occupancy where type='Arch' group by node_name' NODE_NAME Number of Archive Files -----------------------------------------------------------------------GERD 40852 LT-JS 32 TESTPC-081 38
575
7718UpgradeScenario 29_August.fm
ANS8000I Server command: 'select count(*) as "Number of Management Classes" from mgmtclasses' Number of Management Classes ---------------------------11 ANS8000I Server command: 'select count(*) as "Number of Server Scripts" from script_names' Number of Server Scripts -----------------------20 ANS8000I Server command: 'select count(*) as "Number of Storage Pools" from stgpools' Number of Storage Pools -----------------------15 Next, we query for the volume which contains the NAS TOC data to verify that these objects have been transferred when using the Tivoli Storage Manager V6.1.2 INSERTDB utility. First we use the Tivoli Storage Manager command query NASBACKUP * and show the output in Example 23-13.
Example 23-13 Query content against the volume which holds the NAS TOC pointers and data
tsm: RS6000>q vol stgp=TOCPOOL Volume Name -------------------/usr/tivoli/tsm/server/bin/tcovol01.dsm Storage Pool Name ----------TOCPOOL Device Class Name ---------DISK Estimated Capacity --------0.0 M Pct Util ----0.0 Volume Status -------Off-Line
tsm: RS6000>q content /usr/tivoli/tsm/server/bin/tcovol01.dsm Node Name --------------NAS1 NAS1 Type ---Bkup Bkup Filespace Name ---------/vol/vol0 /vol/mixedvol01 FSID ---1 2 Client's Name for File -----------------------/TSM/TOC /TSM/TOC
23.11.1 Summary
This short review demonstrates that in Tivoli Storage Manager V6.1.2 the NAS TOC capabilities have been enabled and are functioning as they should. This review also
576
7718UpgradeScenario 29_August.fm
demonstrates the processes for upgrading from the PREPAREDB, through the EXTRACTDB and into the INSERTDB phases.
577
7718UpgradeScenario 29_August.fm
578
7718p0a.fm
Part 10
Part
10
Appendixes
579
7718p0a.fm
580
7718axODBC.fm
Appendix A.
581
7718axODBC.fm
$ db2set -all [i] DB2_SKIPINSERTED=ON [i] DB2_KEEPTABLELOCK=ON [i] DB2_EVALUNCOMMITTED=ON [i] DB2_SKIPDELETED=ON [i] DB2_PARALLEL_IO=* [g] DB2SYSTEM=utah [g] DB2INSTDEF=tsm1 $ db2set DB2COMM=tcpip $ db2set -all [i] DB2_SKIPINSERTED=ON [i] DB2_KEEPTABLELOCK=ON [i] DB2_EVALUNCOMMITTED=ON [i] DB2_SKIPDELETED=ON [i] DB2COMM=tcpip [i] DB2_PARALLEL_IO=* [g] DB2SYSTEM=utah [g] DB2INSTDEF=tsm1 If you want to activate the changes you need to stop and start DB2 using the db2stop and db2start commands. Trying to stop DB2 will fail while your Tivoli Storage Manager is up and running. Example A-2 shows the SQL1025N message being returned.
Example A-2 SQL1025N, databases are still active.
$ db2stop 06/13/2009 18:52:39 0 0 SQL1025N The database manager was not stopped because databases are still active. SQL1025N The database manager was not stopped because databases are still active
If your Tivoli Storage Manager server is stopped, and you try to you stop and restart your DB2 right now, you receive an ADM7006E error message as shown in Example A-3. You can find the message in the db2diag.log file.
582
7718axODBC.fm
2009-06-06-11.25.48.246673-240 E1194476A497 LEVEL: Error PID : 385174 TID : 258 PROC : db2sysc 0 INSTANCE: tsm1 NODE : 000 EDUID : 258 EDUNAME: db2sysc 0 FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, probe:50 MESSAGE : ADM7006E The SVCENAME DBM configuration parameter was not configured. Update the SVCENAME configuration parameter using the service name defined in the TCP/IP services file.
As we now know that the service name is not configured, use the db2 update dbm command as shown with Example A-4, the service name you configure is DB2_TSM1.
Example A-4 DB2 command: update dbm config
$ db2 update dbm config using svcename DB2_TSM1 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully. $ db2 get dbm cfg | grep SVC TCP/IP Service name (SVCENAME) = DB2_TSM1 Again, if you try to stop and restart DB2 now, you will receive a message (in this case SQL5043N) indicating the configuration is not complete. The exact message is shown in Example A-5 on page 583.
Example A-5 SQL5043N, support for a communication protocol failed
$ db2start 06/13/2009 18:31:11 0 0 SQL5043N Support for one or more communications protocols failed to start successfully. However, core database manager function ality started successfully. SQL1063N DB2START processing was successful. We did not configure the TCP service port so far. So next you need to open the /etc/services file and add the service details. On a Windows machine you configure the service port with the %SYSTEMROOT%\system32\drivers\etc\services file. We decided to configure the DB2_TSM1 service to use port 50000. Just place the statement next to the ports already configured for DB2 usage (do not use any of these ports for ODBC). See Example A-6 for the details.
Example A-6 TSM1 TCPIP service port configured
Example A-7 shows the SQL1063N message being returned by the db2start command. DB2 is up and running and you are finished with the server or target ODBC setup.
583
7718axODBC.fm
$ db2start 06/13/2009 18:56:24 0 0 SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful.
The Install a Product window is presented, as shown with Figure A-2. Click Install New to continue.
584
7718axODBC.fm
The InstallShield Wizard prepares the installation, the progress window shown in Figure A-3 on page 585 is displayed.
The Install Shield Wizard progress is followed by the Windows Installer notification window, see Figure A-4.
On the IBM Data Server Client Setup window, Figure A-5 on page 586, click Next.
585
7718axODBC.fm
After you read the license agreement you select to accept the license terms as shown with Figure A-6 click Next to continue.
On the next window, Figure A-7 on page 587, you stay with the default installation type of Typical and click Next to continue.
586
7718axODBC.fm
Figure A-8 shows that you can create a response file during installation. With this install select Install IBM Data Server Client on this computer and click Next to continue.
Figure A-9 on page 588 allows you to select the installation folder. Stay with the default and click Next again.
587
7718axODBC.fm
By default, operating system security will be enabled with the package installation. As shown with Figure A-10 you could disable this option, here we stay with the default again, click Next to continue.
On the next window, Figure A-11 on page 589, click Install to start the installation of the files.
588
7718axODBC.fm
The installation window, see Figure A-12, informs you about the installation progress.
Once all the files are copied the setup is complete. The notification window, Figure A-13 on page 590, gets displayed. It reminds you to complete some security related post-install steps. In our example we are running with Administrator authority, so we do not need to do anything click Next to continue.
589
7718axODBC.fm
On the final window, Figure A-14, you could select to install additional products, here the IBM Database Add-Ins for Visual Studio 2005. You just click Finish to complete the installation.
You successfully completed the installation of the IBM DB2 Driver for ODBC and CLI, next step is to configure the driver so you can access your Tivoli Storage Manager servers database.
590
7718axODBC.fm
C:\Program Files\tivoli\TSM\db2\BIN>db2 catalog tcpip4 node utah remote utah.itso.ibm.com server 50000 DB20000I The CATALOG TCPIP4 NODE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. C:\Program Files\IBM\SQLLIB\BIN>db2 catalog db tsmdb1 as utahdb1 at node utah DB20000I The CATALOG DATABASE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed. You can immediately verify if the configuration was successful via the db2 connect command, as shown in Example A-9 on page 591.
Example A-9 ODBC configuration verification.
C:\Program Files\tivoli\TSM\db2\BIN>db2 connect to utahdb1 user tsm1 using <password> Database Connection Information Database server SQL authorization ID Local database alias = DB2/AIX64 9.5.2 = TSM1 = TSMDB1
Figure A-15 shows that with the node and database being configured to the local DB2 client, you can already use the DB2 Control Center to display the database. You will be prompted for user ID and password. We do not show that step here.
591
7718axODBC.fm
You have completed the ODBC configuration for client and target machine. After you completed both catalog commands with Example A-8 on page 591 you can already access the database using the Control Center that comes with the IBM DB2 Driver for ODBC and CLI.
C:\Documents and Settings\Administrator>ppm install dbi Downloading ActiveState Package Repository packlist...done Updating ActiveState Package Repository database...done No missing packages to install C:\Documents and Settings\Administrator>ppm install http://cpan.uwinnipeg.ca/PPM Packages/10xx/DBD-DB2.ppd
592
7718axODBC.fm
Downloading DBD-DB2-1.7.1...done Unpacking DBD-DB2-1.7.1...done Generating HTML for DBD-DB2-1.7.1...done Updating files in site area...done 11 files installed Now we just need a small perl script that connects to the database and reads some information out of the database. We save the sample script shown with Example A-11 on page 593 as dbaccess.pl. Once connected to the database, the script reads the available nodes and their platforms from the nodes table and writes them to standard output. More examples and code, for the C programming language or php interpreters, is available from the DB2 installation samples subdirectory.
Example A-11 Simple sample perl script
#!/usr/bin/perl -w # connect to a remote TSM database and collect some information # DB2 Perl Database Interface for LUW # http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21297335 use DBI; use DBD::DB2::Constants; use DBD::DB2; my my my my $database $user $password $schema = = = = "utahdb1"; "tsm1"; "<valid password>"; "tsmdb1";
my $dbh = DBI->connect("dbi:DB2:". $database, $user, $password, {RaiseError => 1}); my $stmt = "SELECT nodename, platform FROM " . $schema . ".nodes;"; my $sth = $dbh->prepare($stmt); $sth->execute(); while( @row = $sth->fetchrow ) { print $row[0] . " " . $row[1] . "\n"; } $dbh->disconnect or warn "Disconnection failed: $DBI::errstr\n"; exit; # Done
Now invoke the perl interpreter against the script. See Example A-12 for the results:
Example A-12 Execute the perl script
C:\tsmtools>perl dbaccess.pl UTAH AIX BUFFALOSTEAK AIX The result is documented with Example A-12, the script can connect to the database and returns the nodes and their platforms.
593
7718axODBC.fm
As shown with Figure A-17 on page 594 you specify to connect to an existing database using ODBC, click Next to continue.
594
7718axODBC.fm
To set up the ODBC connection on Figure A-18 you click Browse to search for existing databases.
Figure A-20 does not yet list the DB2 ODBC drive as an available data source, click Add.
595
7718axODBC.fm
In the Create New data Source window, shown with Figure A-21, select the IBM DB2 ODBC DRIVER and click Finish.
In the next window, as you can see with Figure A-22, specify Data Source Name, in our lab UTAHDB1, and a comment describing the database. Click OK to continue.
From the Data Source Administrator window, Figure A-23 on page 596, select the data source you just created, UTAHDB1. Click OK to proceed.
596
7718axODBC.fm
Again select the UTAHDB data source, see Figure A-24. Click OK to continue.
Once the database connection is specified, as with Figure A-25, click Next to continue.
When asked for authentication details, provide the user ID and make the Password required field active. The user authentication window, Figure A-26, does allow you to immediately test the connection. We do not do this, so click Next to continue.
597
7718axODBC.fm
On the final configuration window, Figure A-27, stay with the defaults and click Finish.
A dialog appears that allows you to save the database you just configured, see Figure A-28 on page 599. In this example you save to folder tsmtools.
598
7718axODBC.fm
When you try to open the database, you are prompted for the credential. Provide the password provided in Figure A-26 and click OK as shown in Figure A-29.
By default the SYSCAT tables branch is expanded, see Figure A-30 on page 600. Click the collapse selector (-).
599
7718axODBC.fm
As with Figure A-31, click the expansion selector (+) for the TSMDB1 database.
From the expanded database tables right-click the Administrators table and click Open, see Figure A-32 on page 601.
600
7718axODBC.fm
You have completethe tasks to allow you to access the Tivoli Storage Managers databases through OpenOffice.
601
7718axODBC.fm
Summary
You can connect to the Tivoli Storage Manager database by programs that support ODBC connections. The ODBC support is now provided by DB2, the Tivoli Storage Manager ODBC driver is no longer required and is no longer supported.
602
7718axDB2commands.fm
Appendix B.
603
7718axDB2commands.fm
# /opt/IBM/db2/V9.5/bin/db2osconf set set set set set msgsys:msginfo_msgmni semsys:seminfo_semmni shmsys:shminfo_shmmax shmsys:shminfo_shmmni rlim_fd_max = 65536 = = = = 3584 4096 30816549273 4096
Total kernel space for IPC: 0.56MB (shm) + 1.27MB (sem) + 1.66MB (msg) == 3.49MB (total)
604
7718axDB2commands.fm
C:\Program Files\IBM\SQLLIB\BIN>db2 catalog db tsmdb1 as utahdb1 at node utah DB20000I The CATALOG DATABASE command completed successfully. DB21056W Directory changes may not be effective until the directory cache is refreshed.
C:\Program Files\Tivoli\TSM\db2\BIN>db2 create database WAREHOUS using codeset utf-8 territory US DB20000I The CREATE DATABASE command completed successfully.
605
7718axDB2commands.fm
606
7718axDB2commands.fm
Database Manager Snapshot Node name Node type remote clients Instance name Number of database partitions in DB2 instance Database manager status Product name Service level Private Sort heap allocated Private Sort heap high water mark Post threshold sorts Piped sorts requested Piped sorts accepted Start Database Manager timestamp Last reset timestamp Snapshot timestamp Remote connections to db manager Remote connections executing in db manager Local connections Local connections executing in db manager Active local databases High water mark for agents registered Agents registered Idle agents Committed private Memory (Bytes) Switch list for db partition number 0 Buffer Pool Activity Information (BUFFERPOOL) Lock Information (LOCK) Sorting Information (SORT) SQL Statement Information (STATEMENT) Table Activity Information (TABLE) Take Timestamp Information (TIMESTAMP) Unit of Work Information (UOW) Agents assigned from pool Agents created from empty pool Agents stolen from another application High water mark for coordinating agents Hash joins after heap threshold exceeded OLAP functions after heap threshold exceeded Total number of gateway connections Current number of gateway connections Gateway connections waiting for host reply Gateway connections waiting for client request = = Database Server with local and = SERVER1 = 1 = Active = DB2 v9.5.201.3237 = special_21101 (WR21421_21101) = = = = = 0 0 Not Collected 2407 2407
= 25 = 23 = 1 = 25755648
= = = = = = = = = = = = = = = = =
ON 06/22/2009 13:45:23.359082 ON 06/22/2009 13:45:40.431420 OFF OFF OFF ON 06/22/2009 13:45:23.359082 OFF 6435 28 0 25 0 0 0 0 0 0
607
7718axDB2commands.fm
Gateway connection pool agents stolen Node Free Free Free Free FCM FCM FCM FCM FCM information corresponds to buffers buffers low water mark channels channels low water mark
Memory usage for database manager: Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) Node number Memory Pool Type Current size (bytes) High water mark (bytes) Configured size (bytes) = = = = = = = = = = = = = = = 0 Other Memory 14614528 15007744 33488896 0 FCMBP Heap 786432 786432 917504 0 Database Monitor Heap 327680 327680 327680
C:\Program Files\Tivoli\TSM\db2\BIN>db2 grant connect on database to useritmuser DB20000I The SQL command completed successfully.
608
7718axDB2commands.fm
C:\Program Files\Tivoli\TSM\db2\BIN>db2 grant createtab on database to user itmuser DB20000I The SQL command completed successfully.
Runstats command
The runstats command updates statistics about the characteristics of a table and associated indexes or statistical views. These characteristics include number of records, number of pages, and average record length. The optimizer uses these statistics when determining access paths to the data including the most efficient means to process the data and whether or not to exploit an index and such for the operation. For a table, this utility should be called when the table has had many updates, or after reorganizing the table. For a statistical view, this utility should be called when changes to underlying tables have substantially affected the rows returned by the view. The view must have been previously enabled for use in query optimization using the ALTER VIEW command. The Tivoli Storage Manager server has a monitor and tuning algorithm that evaluates the workload and changes against the server's tables. As needed it invokes RUNSTATS for a table to update the statistics as necessary. If issues arise with how this monitoring and tuning algorithm work, IBM might recommend manually performing RUNSTATS for one or more tables.
db2start command
The db2start command starts the current database manager instance background processes on a single database partition or on all the database partitions defined in a multi-partitioned database environment. The Tivoli Storage Manager server starts and stops the instance and database whenever the server starts and halts. While the server is running, a db2start is not needed or recommended. Similarly, while the server is running, stopping the database might adversely affect the server including causing current workloads and activity to fail or possibly causing the server to crash. It is important to allow the Tivoli Storage Manager server to manage the starting and stopping of the instance and database. See ODBC target machine configuration on page 582 for sample usage of the command.
609
7718axDB2commands.fm
affect the server including causing current workloads and activity to fail or possibly causing the server to crash. It is important to allow the Tivoli Storage Manager server to manage the starting and stopping of the instance and database.
610
7718axDB2commands.fm
You can use this command and other information available directly from the Tivoli Storage Manager server to diagnose memory and performance related issues. The following call returns database and instance normal values and repeats every 10 seconds: db2mtrk -i -d -v -r 10
Database Partition 0 -- Database TSMDB1 -- Active -- Up 0 days 01:18:45 Logs: Current Log Number Pages Written Method 1 Archive Status Method 1 Next Log to Archive Method 1 First Failure Method 2 Archive Status Method 2 Next Log to Archive Method 2 First Failure Address 0x7FCBFF34 0x7FCFFED4 0x7FCFFF74 0x5634FCE4 StartLSN 0x000041400000 0x000061400000 0x000081400000 0x0000A1400000
2 1605 n/a 2 n/a n/a n/a n/a Size 131072 131072 131072 131072 Pages 131072 131072 131072 131072 Filename S0000002.LOG S0000003.LOG S0000004.LOG S0000005.LOG
611
7718axDB2commands.fm
Once started the db2support welcome screen is presented as shown with Example B-7. Press enter to complete the documentation collection.
Example B-7 db2support command log
_______
D B 2
S u p p o r t
______
This program generates information about a DB2 server, including information about its configuration and system environment. The output of this program will be stored in a file named 'db2support.zip', located in the directory specified on the application command line. If you are experiencing problems with DB2, it may help if this program is run while the problem is occurring. NOTES: 1. By default, this program will not capture any user data from tables or logs to protect the security of your data. 2. For best results, run this program using an ID having SYSADM authority. 3. On Windows systems you should run this utility from a db2 command session. 4. Data collected from program runs. In a information will be instance attachment this program will be from the machine where this client-server environment, database-related from the machine where the database resides via an or connection to the database.
Output file is "C:\Program Files\Tivoli\TSM\db2\BIN\db2support.zip" Time and date of this collection: "10/30/2009 7:56:32 AM Eastern Daylight Time"
Collecting "System files" "db2eventlog.000" "db2systm" "HealthRulesV82.reg" "DB2SYSTM" "db2cli.ini" "SQLDBBAK" "SQLDBDIR" "SQLDBINS" "report.log" Collecting "Detailed operating system and hardware information" Collecting "System resource info (disk, CPU, memory)" Collecting "Operating system and level" Collecting "JDK Level" 612
Tivoli Storage Manager V6.1 Technical Guide
7718axDB2commands.fm
Collecting "DB2 Release Info" LIC1440I License compliance report generated successfully.
Collecting "DB2 install path info" Collecting "Registry info" Collecting "Get dbm cfg" Collecting "db2audit describe" Collecting "Get admin cfg" Collecting "List database directory" Collecting "Sqllib directory listing" Collecting "Sqllib directory listing" SQL Code: "-1027" Collecting "List node directory show detail" SQL Code: "-1027" SQL Code: "-1027" Collecting "List admin node directory show detail" SQL Code: "-1027" SQL Code: "-1311" Collecting "List DCS directory" SQL Code: "-1311" Collecting "Get cli cfg" Collecting "List DCS applications extended" Collecting "Query client" Collecting "List active databases" Collecting "Get db cfg for TSMDB1 " Collecting "List history since 20090930 for db TSMDB1" Collecting "List applications for database TSMDB1 show detail" ...attempting to connect to database: "TSMDB1" Collecting "Buffer pool information" Collecting "Table space information" Collecting "Get snapshot for all applications" Collecting "Select count(*) from sysibm.systables where type='T' and creator <> 'SYSIBM'" Collecting "Select max(stringid) from sysibm.sysxmlstrings" Collecting "Get snapshot for all databases" Collecting "List packages for all show detail" Collecting "List tables for all show detail" Collecting "List indoubt transactions" SQL Code: "-1462" Collecting "List DRDA indoubt transactions" SQL Code: "-1462" Collecting "List command options" Collecting "List nodes"
613
7718axDB2commands.fm
Creating final output archive "db2support.html" "db2_sqllib_directory.txt" "db2_log_directory.txt" "db2supp_system.zip" "admin.supp_cfg" "bp.supp_cfg" "cli.supp_cfg" "db2audit.supp_cfg" "dbm.supp_cfg" "dbm_detailed.supp_cfg" "JDKlevel.supp_cfg" "spcs_bp.supp_cfg" "TSMDB1_db.supp_cfg" "TSMDB1_detailed_db.supp_cfg" "active_db.supp_out" "admin_nodedir.supp_out" "appsnap.supp_out" "db2level.supp_out" "db2licm.supp_out" "db2licm_report.supp_out" "db2set.supp_out" "dbmsnap.supp_out" "dbsnap.supp_out" "db_dir.supp_out" "dcsext.supp_out" "dcs_dir.supp_out" "list_apps.supp_out" "list_cmd_opts.supp_out" "list_DRDA_trans.supp_out" "list_nodes.supp_out" "list_packages.supp_out" "list_tables.supp_out" "list_transactions.supp_out" "nodedir.supp_out" "ODBC_datasources.supp_out" "query_client.supp_out" "tbspc.supp_out" "TSMDB1_list_hist.supp_out" "db2diag.log" "stmm.0.log" "db2optstats.0.log"
You can easily transfer the db2support.zip to your IBM support contact for review. For additional information go to the following for the complete documentation of the command.
614
7718axDB2commands.fm
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2. luw.admin.cmd.doc/doc/r0004503.html
List History File for gtsmdb1 Number of matching file entries = 119
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID -- --- ------------------ ---- --- ------------ ------------ -------------D T 20090618082638 000000000900ed0a000200a4 ---------------------------------------------------------------------------"TSMDB1 "."ADMIN_SQL_TABLES" resides in 1 tablespace(s): 00001 USERSPACE1 ---------------------------------------------------------------------------Comment: DROP TABLE Start Time: 20090618082638 End Time: 20090618082638 Status: A ---------------------------------------------------------------------------EID: 466
615
7718axDB2commands.fm
DDL: CREATE TABLE "TSMDB1 "."ADMIN_SQL_TABLES" ( "ADMIN_SQL_TABNAME" VARCHAR(257) NOT NULL ) COMPRESS YES IN "USERSPACE1" INDEX IN "IDXSPACE1" ; ---------------------------------------------------------------------------Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log Backup ID -- --- ------------------ ---- --- ------------ ------------ -------------D T 20090618082648 000000000900890b00020080 ---------------------------------------------------------------------------"TSMDB1 "."ADM_SCHEDT" resides in 1 tablespace(s): 00001 USERSPACE1 ---------------------------------------------------------------------------Comment: DROP TABLE Start Time: 20090618082648 End Time: 20090618082648 Status: A ---------------------------------------------------------------------------EID: 467
7718axDB2commands.fm
Current Log Number Pages Written Method 1 Archive Status Method 1 Next Log to Archive Method 1 First Failure Method 2 Archive Status Method 2 Next Log to Archive Method 2 First Failure Address 0x7FCBFF34 0x7FCFFED4 0x7FCFFF74 0x5634FCE4 StartLSN 0x000041400000 0x000061400000 0x000081400000 0x0000A1400000
2 1605 n/a 2 n/a n/a n/a n/a Size 131072 131072 131072 131072 Pages 131072 131072 131072 131072 Filename S0000002.LOG S0000003.LOG S0000004.LOG S0000005.LOG
617
7718axDB2commands.fm
Tivoli Storage Manager monitors the state of the database using the health snapshot and other mechanisms that are provided by DB2. There might be cases where the health snapshot or other DB2 documentation indicates that an item or database resource might be in an alert state, indicating that action should be considered to remedy the situation. Tivoli Storage Manager monitors the condition and takes action as appropriate. Not all declared alerts by the DB2 database are acted on. To collect a report on DB2 health monitor indicators submit db2 get health snapshot for database on tsmdb1
Runstats command
The runstats command updates statistics about the characteristics of a table and associated indexes or statistical views. These characteristics include number of records, number of pages, and average record length. The optimizer uses these statistics when determining access paths to the data including the most efficient means to process the data and whether or not to exploit an index and such for the operation. For a table, this utility should be called when the table has had many updates, or after reorganizing the table. For a statistical view, this utility should be called when changes to underlying tables have substantially affected the rows returned by the view. The view must have been previously enabled for use in query optimization using the ALTER VIEW command. The Tivoli Storage Manager server has a monitor and tuning algorithm that evaluates the workload and changes against the server's tables. As needed it invokes RUNSTATS for a table to update the statistics as necessary. If issues arise with how this monitoring and tuning algorithm work, IBM might recommend manually performing RUNSTATS for one or more tables.
618
7718axDB2commands.fm
tsm: TIRAMISU>select * from volumeusage where volume_name like (select distinct volume_name from volumeusage where node_name='CAPITOLA') ANR0162W Supplemental database diagnostic information: -1:42824:-132 ([IBM][CLI Driver][DB2/NT] SQL0132N A LIKE predicate or POSSTR scalar function is not valid because the first operand is not a string expression or the second operand is not a string. A LOCATE or POSITION scalar function is not valid because the first operand is not a string or the second operand is not a string expression. SQLSTATE=42824 ). ANR0516E SQL processing for statement select * from volumeusage where volume_name like ( select distinct volume_name from volumeusage where node_name = 'capitola' ) failed. ANS8001I Return code 3.
Replace use of the LIKE predicate with the in parameter as follows and as customized in Example B-11. select * from volumeusage where volume_name in (select distinct volume_name from volumeusage where node_name='node1')
Example B-11 Use in with nested select commands
tsm: TIRAMISU>select * from volumeusage where volume_name in (select distinct vo lume_name from volumeusage where node_name='CAPITOLA') NODE_NAME: COPY_TYPE: FILESPACE_NAME: STGPOOL_NAME: VOLUME_NAME: FILESPACE_ID: NODE_NAME: COPY_TYPE: FILESPACE_NAME: STGPOOL_NAME: VOLUME_NAME: FILESPACE_ID: CAPITOLA BACKUP \1000000KB_of_10KB FILEPOOL D:\TSM\SERVER1\FILECLASS\0000005A.BFS 3 CAPITOLA BACKUP \1000000KB_of_10KB FILEPOOL D:\TSM\SERVER1\FILECLASS\0000005B.BFS 3
619
7718axDB2commands.fm
tsm: TIRAMISU>select * from actlog where (current_time-date_time) seconds <= 60 seconds ANR0162W Supplemental database diagnostic information: -1:42819:-402 ([IBM][CLI Driver][DB2/NT] SQL0402N The data type of an operand of an arithmetic function or operation "-" is not numeric. SQLSTATE=42819 ). ANR0516E SQL processing for statement select * from actlog where SECOND (current_time-date_time) <= 60 seconds failed. ANS8001I Return code 3.
While the V5 servers did return a result, this is not valid SQL syntax. The select statement from Example B-13 documents correct syntax using the timestampdiff() function. The timestampdiff() function takes a numeric expression as first interval, we use the number 2 which translates to seconds interval. Microseconds would be 1, minutes 4, hours 8 and so on. For a complete description refer to the DB2 reference information manuals.
Example B-13 Corrected statement for time calculation
tsm: TIRAMISU>select * from actlog where char(current_timestamp-date_time)) <= 60 DATE_TIME: MSGNO: SEVERITY: MESSAGE:
timestampdiff(2,
2009-10-29 14:03:11.000000 2017 I ANR2017I Administrator ADMIN issued command: select * from actlog where timestampdiff(2, char(current_timestamp-date_time)) <= 60 (SESSION: 1) ORIGINATOR: SERVER NODENAME: OWNERNAME: SCHEDNAME: DOMAINNAME: SESSID: SERVERNAME: SESSION: 1 PROCESS:
620
7718axDB2commands.fm
tsm: TIRAMISU>select entity,activity,sum(bytes) sum_bytes,sum(end_time-start_tim e) sum_time, sum(affected) sum_affected, sum(failed) sum_failed, sum(mediaw) sum _mediaw from summary su, nodes nd where su.entity=nd.node_name and cast((current _timestamp-start_time)hours as decimal)<24 group by entity,activity ENTITY: ACTIVITY: SUM_BYTES: SUM_TIME: SUM_AFFECTED: SUM_FAILED: SUM_MEDIAW: CAPITOLA BACKUP 27219109316 8400.000000 524236 0 16
tsm: TIRAMISU>select devclass_name, access_strategy, shared from devclasses where access_strategy like 'Random' DEVCLASS_NAME -------------------------------DISK ACCESS_STRATEGY --------------------------------Random SHARED ------NO
621
7718axDB2commands.fm
C:\Program Files\tivoli\TSM\baclient>dsmadmc -errorlogn=errorlog -id=admin -pa=admin -comma -dataonly=y tsm: TIRAMISU>select tabschema,tabname from tables TSMDB1 ,ACTIVITY_SUMMARY TSMDB1 ,ACTLOG TSMDB1 ,ADMINS .. <lines deleted>
For example, if you are writing scripts for automation and need to strip out the additional spaces, you can use the RTRIM scalar function as shown with Example B-17.
Example B-17 RTRIM function
C:\Program Files\tivoli\TSM\baclient>dsmadmc -errorlogn=errorlog -id=admin -pa=admin -comma -dataonly=y tsm: TIRAMISU>select rtrim(tabschema),tabname from tables TSMDB1,ACTIVITY_SUMMARY TSMDB1,ACTLOG TSMDB1,ADMINS .. <lines deleted>
622
7718axRcoverFromLogFull.fm
Appendix C.
623
7718axRcoverFromLogFull.fm
TSM:TSMINST1> ANR8340I FILE volume D:\TSM\FILECLASS\0000000F.BFS mounted. ANR0511I Session 17 opened output volume D:\TSM\FILECLASS\0000000F.BFS. ANR0171I dbieval.c(812): Error detected on 20:15, database in evaluation mode. ANR0175E dbieval.c(905): Space exhausted for one or more of the following: DB, LOG, or instance directory. ANR0162W Supplemental database diagnostic information: -1:57011:-968 -[IBM][CLI Driver][DB2/NT] SQL0968C The file system is full. SQLSTATE=57011 Any subsequent attempt to start the server fails with the out of log space condition as shown with the ANR0130E out of log space condition as shown with Example C-2.
Example C-2 ANR0130E. out of log space
D:\tsm\tsminst1>"c:\Program Files\Tivoli\tsm\server\dsmserv.exe" ANR0900I Processing options file D:\tsm\tsminst1\dsmserv.opt. ANR7800I DSMSERV generated at 13:10:23 on Aug 6 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I ANR0990I ANR0152I ANR0130E The ICC support module has been loaded. Server restart-recovery in progress. Database manager successfully started. rdbdb.c(1386): Server LOG space exhausted.
Now the question is how to recover from this condition as the V5 DUMP/LOAD utilities are not available with the Tivoli Storage Manager V6 server and no database backup is available for restore?
624
7718axRcoverFromLogFull.fm
E:\>mkdir temp_activelog E:\>dir Volume in drive E is MoreSpace Volume Serial Number is 34F1-BF7B Directory of E:\ 10/31/2009 05:51 AM <DIR> temp_activelog 0 File(s) 0 bytes 1 Dir(s) 20,906,221,568 bytes free
C:\Program Files\Tivoli\TSM\db2\BIN>set db2instance=SERVER1 C:\Program Files\Tivoli\TSM\db2\BIN>db2start SQL1063N DB2START processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2 update db cfg for tsmdb1 using newlogpat h e:\temp_activelog DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
C:\Program Files\Tivoli\TSM\db2\BIN>db2 activate db tsmdb1 DB20000I The ACTIVATE DATABASE command completed successfully.
625
7718axRcoverFromLogFull.fm
Note that the current logs files in the old active and archive directories do not change. Example C-6 shows that the old active log files are still under the old active log directory path:
Example C-6 The old active logs
D:\tsm\tsmactivelog>dir Volume in drive D is Server Volume Serial Number is 24DC-C90D Directory of D:\tsm\tsmactivelog 10/31/2009 10/31/2009 10/23/2009 10/23/2009 10/23/2009 10/23/2009 06:05 AM <DIR> . 06:05 AM <DIR> .. 10:43 AM 536,879,104 S0000023.LOG 10:52 AM 536,879,104 S0000024.LOG 11:02 AM 536,879,104 S0000025.LOG 11:48 AM 515,272,704 S0000026.LOG 4 File(s) 2,125,910,016 bytes 2 Dir(s) 154,566,656 bytes free
Example C-7 shows the copies under the new archive log path, renamed to the next volumes in sequence.
Example C-7 The new active log copies
E:\temp_activelog>dir Volume in drive E is MoreSpace Volume Serial Number is 34F1-BF7B Directory of E:\temp_activelog 10/31/2009 10/31/2009 10/31/2009 10/31/2009 10/31/2009 10/31/2009 10/31/2009 07:08 AM <DIR> . 07:08 AM <DIR> .. 06:15 AM 536,879,104 S0000027.LOG 06:38 AM 536,879,104 S0000028.LOG 07:08 AM 536,879,104 S0000029.LOG 07:20 AM 536,879,104 S0000030.LOG 06:05 AM 512 SQLLPATH.TAG 5 File(s) 2,147,516,928 bytes 2 Dir(s) 18,758,701,056 bytes free
Note: The database backups we take here are temporary and will be deleted. The purpose is to prune the archive logs.
Before we procees and start the backup process, we create a directory on the E: drive to temporarily hold the database as shown with Example C-8.
626
7718axRcoverFromLogFull.fm
E:\>md temp_db_backup E:\>dir Volume in drive E is MoreSpace Volume Serial Number is 34F1-BF7B Directory of E:\ 10/31/2009 10/31/2009 07:08 AM <DIR> temp_activelog 08:00 AM <DIR> temp_db_backup 0 File(s) 0 bytes 2 Dir(s) 18,758,701,056 bytes free
Now we start two consecutive database backups as shown with Example C-9. After the second backup, the archive log directory and original active log directory are empty of log files.
Example C-9 Take DB2 backups
C:\Program Files\Tivoli\TSM\db2\BIN>db2stop SQL1064N DB2STOP processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2start SQL1063N DB2START processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2 backup db tsmdb1 to e:\temp_db_backup Backup successful. The timestamp for this backup image is : 20091031080830
C:\Program Files\Tivoli\TSM\db2\BIN>db2 backup db tsmdb1 to e:\temp_db_backup Backup successful. The timestamp for this backup image is : 20091031090213
After the second backup, the archive log directory and the original active log directory are emptied from the log files. The active log files are stored under the new active log directory path we defined above. Keep the backup image timestamps so you can later prune them from DB2. Example C-10 shows the empty original log directory after the second database backup, The archive log directory is also empty at this point in time.
Example C-10 Empty original active log directory
D:\tsm\tsmactivelog>dir Volume in drive D is Server Volume Serial Number is 24DC-C90D Directory of D:\tsm\tsmactivelog 10/31/2009 10/31/2009 09:50 AM <DIR> 09:50 AM <DIR> 0 File(s) . .. 0 bytes
627
7718axRcoverFromLogFull.fm
2 Dir(s)
C:\Program Files\Tivoli\TSM\db2\BIN>db2stop SQL1064N DB2STOP processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2start SQL1063N DB2START processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2 connect to tsmdb1 Database Connection Information Database server SQL authorization ID Local database alias = DB2/NT 9.5.2 = ADMINIST... = TSMDB1
C:\Program Files\Tivoli\TSM\db2\BIN>db2 prune history 20091031080830 with force option and delete DB20000I The PRUNE command completed successfully.
C:\Program Files\Tivoli\TSM\db2\BIN>db2 update database config for tsmdb1 using newlogpath d:\tsm\tsmactivelog DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully. SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, all applications must disconnect from this database before the changes become effective.
C:\Program Files\Tivoli\TSM\db2\BIN>db2 force application all DB20000I The FORCE APPLICATION command completed successfully. DB21024I This command is asynchronous and may not be effective immediately.
628
7718axRcoverFromLogFull.fm
C:\Program Files\Tivoli\TSM\db2\BIN>db2stop SQL1064N DB2STOP processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2start SQL1063N DB2START processing was successful. C:\Program Files\Tivoli\TSM\db2\BIN>db2 connect to tsmdb1 Database Connection Information Database server SQL authorization ID Local database alias = DB2/NT 9.5.2 = ADMINIST... = TSMDB1
D:\tsm\tsminst1>"c:\Program Files\Tivoli\tsm\server\dsmserv.exe" ANR0900I Processing options file D:\tsm\tsminst1\dsmserv.opt. ANR7800I DSMSERV generated at 13:10:23 on Aug 6 2009. Tivoli Storage Manager for Windows Version 6, Release 1, Level 2.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR1380I The buffer pool monitor switch is enabled. ANR1635I The server machine GUID, 6b.9e.90.31.ba.4f.11.de.95.00.02.00.4c.4f.4f.50, has initialized. ANR2100I Activity log process has started. ANR4726I The NAS-NDMP support module has been loaded. ANR1794W TSM SAN discovery is disabled by options. ANR7808W Sun Microsystems Library Attach module libacs.dll is not available from the system. ANR0984I Process 1 for EXPIRE INVENTORY (Automatic) started in the BACKGROUND at 12:34:28. ANR0811I Inventory client file expiration started as process 1. ANR2803I License manager started. ANR8200I TCP/IP Version 4 driver ready for connection with clients on port 1500. ANR2560I Schedule manager started. ANR2828I Server is licensed to support IBM System Storage Archive Manager.
Appendix C. Recover from log exhausted conditions
629
7718axRcoverFromLogFull.fm
is licensed to support Tivoli Storage Manager Basic Edition. is licensed to support Tivoli Storage Manager Extended Edition. initialization complete. STORAGE MANAGER distributed by Tivoli is now ready for use.
We take two more full backups, this time from inside the Tivoli Storage Manager server of course. Example C-15 shows how we take two database backups while we disabled the server for incoming client sessions.
Example C-15 Database backups completing the recovery procedure
TSM:TSMINST1>disable sessions ANR2017I Administrator SERVER_CONSOLE issued command: DISABLE SESSIONS ANR2553I Server now disabled for Client access. TSM:TSMINST1>backup db type=full devc=file ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=full devc=file ANR4559I Backup DB is in progress. ANR0984I Process 4 for DATABASE BACKUP started in the BACKGROUND at 12:49:07. ANR2280I Full database backup started as process 4. .. lines deleted .. ANR4550I Full database backup (process 4) completed. ANR0985I Process 4 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 13:55:36. TSM:TSMINST1>backup db type=full devc=file ANR2017I Administrator SERVER_CONSOLE issued command: BACKUP DB type=full devc=file ANR4559I Backup DB is in progress. ANR0984I Process 5 for DATABASE BACKUP started in the BACKGROUND at 14:31:18. ANR2280I Full database backup started as process 5. .. lines deleted .. ANR4550I Full database backup (process 5) completed. ANR0985I Process 5 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 14:39:45. ANR0136I Table updating statistics performed successfully for 1 of 1. TSM:TSMINST1>enable sessions ANR2017I Administrator SERVER_CONSOLE issued command: ENABLE SESSIONS ANR2552I Server now enabled for Client access.
At this point we are almost complete with the recovery procedure. As a last step we delete the second database backup taken using the DB2 backup db command. Example C-16 shows how we submit the prune command for the backup image with timestamp 20091031090213.
Example C-16 Prune command for backup image
C:\Program Files\Tivoli\TSM\db2\BIN>db2 prune history 20091031090213 with force option and delete DB20000I The PRUNE command completed successfully.
630
7718axRcoverFromLogFull.fm
Summary
We guided you through the complete scenario to recover from a log space exhausted condition using DB2 commands while the Tivoli Storage Manager server is down. However, you should prevent from that in the first place as the procedure might be very time consuming depending on the log space to manage. Make sure to investigate why you got the ANR0130E message and take the necessary precaution steps.
631
7718axRcoverFromLogFull.fm
632
7718bibl.fm
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.
IBM Redbooks
For information about ordering these publications, see How to get Redbooks on page 635. Note that some of the documents referenced here may be available in softcopy only. IBM Tivoli Storage Management Concepts, SG24-7447 IBM Tivoli Storage Manager Implementation Guide, SG24-5416
Other publications
These publications are also relevant as further information sources: IBM Tivoli Storage Manager Server Upgrade Guide, SC23-9554 IBM Tivoli Storage Manager for Windows Backup-Archive Clients Version 6.1, SC23-9792 IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients 6.1, SC23-9791 IBM Tivoli Storage Manager for AIX Installation Guide V6.1, GC23-9781 IBM Tivoli Storage Manager for AIX Administrator's Guide V6.1, SC23-9769 IBM Tivoli Storage Manager for AIX Administrator's Reference V6.1, SC23-9775 IBM Tivoli Storage Manager for SAN for AIX Storage Agent User's Guide V6.1, SC23-9797 IBM Tivoli Storage Manager for HP-UX Installation Guide V6.1, GC23-9782 IBM Tivoli Storage Manager for HP-UX Administrator's Guide V6.1, SC23-9770 IBM Tivoli Storage Manager for HP-UX Administrator's Reference V6.1, SC23-9776 IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent User's Guide V6.1, SC23-9798 IBM Tivoli Storage Manager for Sun Solaris Installation Guide V6.1, GC23-9784 IBM Tivoli Storage Manager for Sun Solaris Administrator's Guide V6.1, SC23-9772 IBM Tivoli Storage Manager for Sun Solaris Administrator's Reference V6.1, SC23-9778 IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent User's Guide V6.1, SC23-9800 IBM Tivoli Storage Manager for Linux Installation Guide V6.1, GC23-9783 IBM Tivoli Storage Manager for Linux Administrator's Guide V6.1, SC23-9771 IBM Tivoli Storage Manager for Linux Administrator's Reference V6.1, SC23-9777 IBM Tivoli Storage Manager for SAN for Linux Storage Agent User's Guide V6.1, SC23-9799 IBM Tivoli Storage Manager for Windows Installation Guide V6.1, GC23-9785
633
7718bibl.fm
IBM Tivoli Storage Manager for Windows Administrator's Guide V6.1, SC23-9773 IBM Tivoli Storage Manager for SAN for Windows Storage Agent User's Guide V6.1, SC23-9553 IBM Tivoli Storage Manager Messages V6.1, GC23-9787 IBM Tivoli Storage Manager Performance and Tuning Guide V6.1, GC23-9788 IBM Tivoli Storage Manager Problem Determination Guide V6.1, GC23-9789 IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation and User's Guide V6.1, SC23-9791 IBM Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide V6.1, SC23-9792 IBM Tivoli Storage Manager for Space Management for UNIX and Linux User's Guide V6.1, SC23-9794 IBM Tivoli Storage Manager Using the Application Program Interface V6.1, SC23-9793 IBM Tivoli Storage Manager for Mail Data Protection for Microsoft Exchange Server Installation and User's Guide V6.1, SC23-9796 IBM Tivoli Storage Manager for Enterprise Resource Planning Data Protection for SAP Installation and User's Guide for Oracle V6.1, SC33-6340 IBM Tivoli Storage Manager for Enterprise Resource Planning Data Protection for SAP Installation and User's Guide for DB2 V6.1, SC33-6341 IBM Tivoli Storage Manager for Advanced Copy Services Data Protection for Snapshot Devices Installation and User's Guide V6.1, SC23-8331
Online resources
These Web sites are also relevant as further information sources: IBM product announcement letters http://www-01.ibm.com/common/ssi/index.wss Additional IBM Tivoli Storage Manager V6.1 products http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appnam e=iSource&supplier=897&letternum=ENUS209-088 Tivoli Storage Manager V6.1 documentation http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp Unix client install media
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
TSM V6.1 product and capacity planning information http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.inst all.doc/t_srv_plan_capacity.html TSM V61. product support site http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.ht ml Cygwin site www.cygwin.org
634
7718bibl.fm
Related publications
635
7718bibl.fm
636
7718IX.fm
Index
A
acrive log data deduplication 265 ACTIVATE DATABASE command 62 active data volumes 125 Active Directory 200 database 202 individual object recovery 415 platform support 202 V6.1 enhancements 201 ACTIVE log 257 Active log 265 considerations 56 active log 390, 549 mirror space 53 size 58 space estimate 52 active log directory 56 ACTIVE log mirror 258 Active log mirror 265 considerations 56 space 520 active-data pool names syntax rules 125 active-data pools 125 Active-Data storage Pools 125 ACTIVEDATASTGPOOL parameter 125 ACTIVELOGDIR 34, 56 ACTIVELOGDIRECTORY option 628 ACTIVELOGSIZE value 625 ActivePerl 5.10 592 adaptive subfile backup 150 adlocation option 415 ADM7006E message 582 ADM7514W message 120 Administration Center 317, 438, 453 client nodes 457 coexist 455 create server instance 464 credential entry 447 DRM support 457 expiration processing 168 Expire Inventory 169 features 456 Health Monotor 458 mesages 456 Reporting 439 reporting CSV file 462 upgrade considerations 455 administration notification log 119 Administrator Center autostart function 341 administrator registration 334 ADP 125 ADSM 6 Advanced Copy Services 17 aggregate size 182 AIX csum command 148 installation 312 AIX configuration database directories 345 AIX install Administration Center 317 administrator registration 334 cleanup 356 command line console wizard 315 component selection 323 configure DB2 database 328 customize 325 database backup 332 database instance 328 db2 update 329 Disk Structure 325 dsmserv format 330 file permissions 313 installation log 325 logs 355 Passport Advantage 313 post install tasks 337 root user 313 time command 332 update_all command 351 upgrade 351 X11 client 314 X11 remote setup 320 AIX server 331 disk structure 325 options file 327 server instance 327 AIX systems upgrade 507 ANALYST privilege 35 announcement letter 11 ANR0130E 624 ANR0130E message 106107, 631 ANR0165I message 173 ANR0166I message 173174 ANR0190I message 174 ANR0191I message 174 ANR0985I message 90 ANR1291 message 541 ANR1336I message 300 ANR1337I A LOGSPACE 558 ANR1525I message 282 ANR2590E message 88 ANR2639E message 103 ANR2968E message 90 ANR2974I message 87, 396
637
7718IX.fm
ANR2976I message 396 ANR4529I message 100 ANR4531I message 100 ANR4794E message 217 ANR4896I message 175 ANR4976W message 94 ANS2837E message 228, 235 API DB2 backup 133 ARCHIVE FAILOVER log 259 Archive failover log space 53 archive failover log 265 ARCHIVE log 258 Archive log considerations 56 space requirements 265 archive log 358 size 58 archive log directory 390 archive log files pruned 520 archive logs new location 565 prune 626 Archive.Objects table 165 ARCHLOGDIR 34, 56 ARIES/NT technology 42 audience xvii AUDITDB facility 43 autoconf tool 27 autoconf utility 28 automatic backup 99 AUTOMATIC STORAGE parameter 54
backupsets bread crumb navigation 477 configuration 471 DRM 478 BC Tier 0 142 BC Tier 1 143 BC Tier 2 143 BC Tier 3 143 BC Tier 4 143 BC Tier 5 144 BC Tier 6 144 BC Tier 7 144 best practices naming 270 BIRT install 452 BIRT editor 451 BIRT package 440 bread crumb navigation 477 BUFPOOLSIZE option 3839, 46
C
cancel session command 303304, 531532 CENTERA device 289 CIFS 536 circular log 103 Client enhancements, additions and changes 8 Version 5.1.5 improvements 8 client install 417 migrating,backup-archive client migrating 417 Client level support 256 Client Node Group 472 client nodes upgrade 524 client option RESOURCEUTILIZATION 60 schedlogretention 303, 531 Client Options file 432 client restore 210 client server login 433 command-line console wizard 315 Common File Exclusion 431 components 4, 364 install,install components 365 Composite Offering Installer 364 compression deduplication 148 configuration backupsets 471 configuration wizard 133, 427, 431 Client Node Name 429 Communications 429 options file 428 TCP/IP communication 430
B
back up storage pools 303, 531 backup 475 device configuration 304, 532 BACKUP ARCHIVE software 421 BACKUP DB command 402 backup db command 303, 531 backup operations 409 backup set wizard 475 backup sets 471 BACKUP STGPOOL command 303, 531 backup systemservices command 418 Backup.Objects table 165 backup/archive client password 417 backup-archive client 414 migration guidelines 417 BACKUPImage parameter 221 backupset concept 476 retention 476 table of content 477
638
7718IX.fm
configure server instance 380 connect 65 console installation wizard 376 convert ussfilespace 302, 530 COPY ACTIVEDATA 292 copy pool protection 124 Credential Store 491 delete 494 csum command 148 Custom install 424 Custom Setup window 424 customize AIX 325 customized reports 451 Cygwin 320 cygwin shell 321
D
daily housekeeping 304, 532 data deduplication 147, 265 disaster recovery 124 data lifecycle 139 data migration 291 Data Protection for Exchange 14 Data Protection for Microsoft Exchange 240 compatibility 241 requirements 240 Data Protection for Microsoft Exchange Server 14 data shredding 293 database 52 activated 62 active log directory 56 ACTIVELOGDIR 56 ARCHLOGDIR 56 Automatic Storage 54 backup 402, 561 commands 64, 604 configuration 53 disk storage 54 extracting to media 296 extraction process 521 FORMAT 402 full backup considerations 53 future growth 519 increase space 113 insert process 261 inserting data 522 insertion process 307 instance directory 271 instance name 271 log file flow 57 log file sizing 57 monitoring 54 page sizes 54 performance 522 query 352 QUERY DB FORMAT=DETAILED 52 raw logical volumes 264 recovery mode 58 reduce size 565 REORG 257
restore 103, 623 schema 566 server upgrade 52 setup tips 519 SMS 54 space estimates 519 space requirements 49 summary information 563 test system 297 transaction activity 59 uncommitted read 45 V6 size estimate 52 database audits 253 database backup 140, 396 example 98 manual 88 database backups verification 98 database capacity 256 database component 44 database directory 389 database expiration processing 291 database instance AIX 328 restart 403 database maintenance 564 DB2 database maintenance 86 database name 271 database operations 519 database reorganization 102 database restore 113 database size planning 364 database sizing formula 264 database space directories 271 database space requirements 264 database upgrade 253 database volume 253 DB.STORAGEPATHS 136 DB2 ACTIVE log 257 automatic backup 99 constraints 43 database and log directories 49 expanded database size 43 kernel parameter 47 log file naming 62 referential integrity 43 reusing current code install 253 rollforward operation 62 striping 53 triggers 43 useful commands 64 user limits 46 DB2 applications 442 DB2 command db2 connect reset 65 db2 drop db db_alias 110
Index
639
7718IX.fm
DB2 commands attach 615 Catalog database 605 connect to 616, 618 Create database 605 db2 64 db2 ? sqlxxxx 616 db2 catalog 591 db2 connect 65, 591 db2 connect reset 65 db2 describe table 69 db2 get db cfg 66 db2 get instance 69 db2 list db directory 69 db2 select 65 db2 update dbm 583 detach 615 Get database manager configuration 606, 617 get database manager configuration 117 get snapshot 606, 618 GRANT 608 list history 615, 618 Runstats 609 set db2instance 610 stop dbm 609 DB2 configuration query 352 DB2 database 41 archive log 358 backup 332 Cached copies 50 log function 357 transition 44 DB2 database backup 133 DB2 Driver for ODBC 590 DB2 instance environment variable 86 DB2 options db2instance 86 DB2 password 372 DB2 system commands db2cc 86 db2cmd 604, 610, 616 db2icrt 604 db2ilist 610 db2level 7071 db2mtrk 610 db2osconf 47, 604 db2set 70, 582, 605 db2start 71, 582, 609 db2stop 71, 582 Db2 system commands db2pd 611 db2 update command 133, 329 DB2 UPDATE DB command 625 DB2 version 504 DB2_VENDOR_INI variable 92 DB2COMM setting 582 db2diag utility 120 db2diag.log 120
db2diag.log file 119, 582 db2icrt command 300, 328, 400 db2osconf system utility 604 db2set ommand 92 db2stop command 120 db2support.zip 614 DB2TSM 372 DBBACKUPTRIGGER command 99 dbdir.txt file 110 DBMEMPERCENT 34 DBMEMPERCENT option 46, 406 DBMEMPERCENT parameter 337 DBPAGESHADOW option 39 DBPAGESHADOWFILE option 39 DBREPORTMODE setting 116 dd storagepool 155 ddtrace utility 27 deduplicated copy storage pool 141 deduplicated storage pools 140 deduplication 139, 148, 156 commands 153 dd storagepool 155 disabling 156 encrypted files 153 hash functions 148 hyperfactor 149 log sizing 61 ratios 149 Single Instance Store 148 space considerations 156 workloads 148 default server 402 DEFINE DBBACKUPTRIGGER 37 DBCOPY 37 DBVOLUME 37 LOGVOLUME 37 DELETE VOLHISTORY command 303, 530 Deployment Engine Initialization 379 remove 410 DEVCLASSES table 621 DEVCONFIG option 281 DFS links 418 diagnostic information 116, 119 diagpath configuration parameter 121 DIAGPATH parameter 119 diffsnapshot 225 diffsnapshot option 414 DiffSnapShot=Latest option 225 disable reclaimation 291 DISABLENQR YES option 160 disabling sessions 303, 531 disaster preparation 43 recovery 43 disaster recovery 220 data deduplication 124 Disaster Recovery Manager 5
640
7718IX.fm
license 123 disaster recovery plan 128 Disaster Recovery solution 144 DISK device class 621 Disk Structure 325 dismount tapes 304, 532 DMS table space 53 DPI protocol 408 DRM ADP 125 DSMSERV RESTORE 128 DRM SET command 126 dsm.opt file 228, 422 dsmapipw command 93 dsmclc migrate command 197 dsmclc migratelist command 197 dsmclc tool 190 dsmcutil command 93 DSMFMT utility 38 dsmformat command 341 dsmhsmclc check command 194 dsmhsmclc command 198 DSMI_ api variable 403 DSMI_CONFIG environment variable 91 dsmicfgx program 342 dsmicfgx wizard 376, 442 dsmicfgx.exe 385 dsmifgx program 95 dsmmfc.exe file 420 DSMSERV AUDITDB 38 DISPLAY DBBACKUPVOLUME 38 DISPLAY DBSPACE 32, 39 DISPLAY LOG 32 DUMPDB 39 EXTEND LOG 39 INSERTDB 33 LOADDB 39 LOADFORMAT 36 REMOVEDB 33 RESTORE DB 36, 39 UNLOADDB 39 dsmserv command 331 DSMSERV DISPLAY DBSPACE 55 DSMSERV FORMAT command 401402 dsmserv format command 87, 330 DSMSERV INSERTDB 282 DSMSERV LOADFORMAT command 573 DSMSERV program 561 DSMSERV REMOVEDB 135 DSMSERV REMOVEDB command 110 dsmserv restore db command 128 DSMSERV utility 404 dsmserv.dsk file 537 dsmserv.opt 281 dsmserv.opt file 103, 110, 625 dsmserv.v6lock file 400 dsmupgdx wizard 442 DSMUPGRD
EXTEND DB 33 EXTEND LOG 33 EXTRACTDB 33 EXTRACTDB utility 503 PREPAREDB 33 PREPAREDB utility 503 QUERYDB 33 dsmupgrd preparedb rollback 567 dsmupgrd preparedb command 300 DSMUPGRD upgrade utilities 503 DSMUPGRD utilities 278, 284, 503 DSMUPGRD utility 278, 305, 533 DUMP/LOAD utilities 624
E
Enterprise Edition 152 environment variable 401 ESTIMATE DBREORGSTATS 37 event retention data 301, 529 Exchange 14 EXPINTERVAL server option 291 expiration algorithm 165 legacy 164 EXPIRATION process 163 expiration process 172, 485 new with v6 165 RESOURCE parameter 168 TYPE parameter 168 expiration processing Administration Center 168 expiration task 171 Expire Inventory window 169 Expiring.Objects table 165 EXTEND DB 280 EXTEND DBSPACE 38, 113 EXTEND DBSPACE command 32, 115, 257 EXTEND LOG 38 extract process 261 EXTRACTDB command 279 extraction physical disk drive 521 extraction process 521
F
failover archive log 520 failover log 409 fallback 302, 530 File and Print Sharing 536 file level recovery 216 file level restore 224 file permissions 313 filel restore 216 Filer logs 223 firewall port 445 536 fix packs 367 ftp site 365 FlexVol volume 224
Index
641
7718IX.fm
FORMAT database 402 full backup 96 full database backup 99 future growth 52
G
gathering logs 411 GENERATE BACKUPSET command 478 get health snapshot command 608 grant auth admin 334
H
hash functions 148 Health Monitor 438, 458 multi-threaded model 458 help non-English online 420 Help command 416 HP-UX passthru driver 26 HP-UX systems upgrade 508 HSM introduction 190 threshold migration 191 HSM for Windows migration jobs 190 V5.4 enhancements hyperfactor 149
I
IBM Autonomic Deployment Engine 373 IBM Tivoli Monitoring 438 IBM Tivoli Storage Manager Client enhancements, additions, and changes 8 disaster preparation and recovery 43 new features overview 7, 10 overview 4, 42, 124 product components 4 product positioning 5 Server enhancements, additions and changes 7 IBM Tivoli Storage Manager Client. see Client IBM Tivoli Storage Manager for ERP 15 IBM Tivoli Storage Manager for Mail 14 IBM Tivoli Storage Manager for Space Management see Tivoli Storage Manager for Space Management IBM Tivoli Storage Manager HSM for Windows see HSM for Windows IBM Tivoli Storage Manager Server. see Server IBM Tivoli Storage Managersee Tivoli Storage Manager IDENTIFY DUPLICATES command 32 Identify Duplicates processes 155 identify processes 155 Iintroduction 148 Incremental backup 562 incremental database backup 99 index_keyseq 620 index_order column 620
Individual Mailbox Restore 242 limitations 243 restoremailbox parameter 243 initial database size 341 INSERTDB ANR1525I message 282 insertdb 568 INSERTDB utility 281, 576 install restriction 366 setup wizard 422 install folder 424 InstallAnywhere 365 InstallAnywhere platform 300 installation 251 installation log 325 installation wizard 368 installer program dsmicfgx.exe 385 instance configuration database backup 396 instance creation 465 instance directory 263, 271, 400, 547 instance startup 331 instance user ID 386 instance wizard database directory 389 Integrated Solution Console 453 Integrated Solutions Console 491 ISC 453 default location 496 default timing 496 enhancements in V7.1 491 multitasking 491 partial refresh 491 preserving scroll location 491 single sign-on 491 startup pages 491 upgrade 455 upgrade considerations 455 url login 456 ISC/AC remote connection 335 ISC/AC server process 335 Itanium system 508, 516
J
JFS2 filesystem 358 JVM 452
K
kernel parameter 47 kernel parameters 48
L
LABEL LIBVOLUME operation 24 language packs 421 library clients 523
642
7718IX.fm
library managers upgrade 523 Linux on System z upgrade 513 Linux system upgrade 510 Local disaster recovery 130 log configuration database log config 56 log directories setup tips 519 log directory 627 log exhausted 624 log file flow 57 log file sizing 57 log files naming 62 log sizing deduplication 61 log space 107 log space condition 624 log space usage 183 log utilization ratio 100 Log volume 253 Logical Volume Snapshot Agent 420 LOGPOOLSIZE option 39 LOGWARNFULLPERCENT 39 LZW-based algorithm 153
MIRRORREAD option 39 MIRRORWRITE option 39 mkdir command 383, 399 Monitor Service 193 Monitoring and Reporting 438 Monitoring and reporting installation 442 Monitoring feature 438 components 440 Monitoring Reporting setup options 440 MOVE DRMEDIA command 126 MOVE DRMEDIA, 125 multiple NICs 253
N
Named Pipes 407 NAS backups 417 NAS devices backup 216 file level recovery 216 NAS filesystems snapdiff option 229 NAS TOC manual upgrade 570 query NASBACKUP * 576 NAS TOC data AIX insertdb 568 extractdb 568 NAS TOC upgrades 568 NDMP 215 IP address 217 IPV4 address 217 SETOPT command 217 NDMP support requirements (Extended Edition only) 420 NetApp FilerView tool 414 NetApp SnapMirror to Tape 216 NetApp Snapshot Difference API 414 network connection 408 network method 263, 543 upgrade network method 277 new server instance 376 no query restore 158 NOMIGRRECL option 292 NOMIGRRECL server option 291 non-root user 46 NQR algorithm 158
M
Mailbox Restore CLI parameters 247 tdpexcc command 246 mailbox restore feature 14 mailboxoriglocation parameter 14 maintenance script edit 488 maintenance plan 478 maintenance script 457 expiration process 485 Manage Global Refresh 494 management classes 457 manual create server 399 MAXSESSIONS option 182 Media method 274 media method 266, 285, 543 media method upgrade 263 memory usage 46 Microsoft Exchange 14 Microsoft Exchange Server 240 migrating processor architecture 418 migration passwords 417 migration considerations processor architectures 418 migration jobs 190 mirror log 549 mirror log directory 390
O
ODBC configuration 591 configuration verification 591 DB2COMM setting 582 ODBC driver package 584 off site data vaulting 145 open database connectivity driver 581 Open File Support 420
Index
643
7718IX.fm
OpenOffice 594 Administrators table 601 operating procedures 297 operational 292 Operational Reporting 441 operational reporting 298 Operational Reporting tool 438 out of log space 624
P
package components 364 package names 365 PA-RISC system 508 Passport Advantage 313 passthru device driver 27 device configuration 27 passthru driver 26 Payloads 365 pcs - l command 48 performance extractioon process 306 TXNGROUPMAX 183 perl sample script 593 perl script 592 planning ACTIVE log mirror 258 ARCHIVE FAILOVER log 259 database capacity 256 database migration 252 performance 272 ppm install DBI command 592 PREPARE command 126 PREPAREDB command 279 primary archive log 390 processor architecture 418 processor architectures 418 product positioning 5 product support site 506 proprietary database 42 ProtecTIER 152 prune command 630
QUERY NODE command 92 query process 532 QUERY PROCESS command 174 query san command 23 QUERY SERVER command 271 query session command 303, 531 QUERY SQLSESSION 38 QUERY STATUS command 116 query stgpool command 155 Query SystemState command 204 QUERYSUMMARY option 210 querysummary option 416 QUERYSUMMARY output 210
R
raw logical volumes 52, 264 RECLAIM parameter 305, 533 RECLAIMDELAY option,server option RECLAIMDELAY 25 RECLAIMPERIOD 26 RECLAIMPERIOD option,server option RECLAIMPERIOD 26 reclamation diable 291 Recovery log space requirements 264 recovery log 44 ROLLFORWARD 396 recovery log process 357 recovery log space 520 naming 271 recovery logs 257 recovery mode 58 recovery plan 129 recovery site scenario 131 Redbooks Web site 635 Contact us xx REDUCE DB 38 REDUCE LOG 38 REGISTER LICENSE command 405, 561 REGISTER NODE command 183 registry keys 402 RELABELSCRATCH parameter 24 rename system object 419 REORG database 257 Reporting Administration Center 439 Deployment Engine 440 Reporting and Monitoring frequently asked questions 441 Reporting feature components 440 reporting monitoring feature 255 Reporting package 438 RESET DBMAXUTILIZATION 38 LOGCONSUMPTION 38 LOGMAXUTILIZATION 38 RESET BUFPOOL 38 restore adobjects command 416
Q
q script f=d 487 Qtree security 235 query adobjects command 415 query archive command 416 query backup command 416 QUERY DB FORMAT=DETAILED 264 QUERY DBSPACE 55, 112 QUERY DBSPACE command 32 QUERY DRMEDIA 126 QUERY DRMEDIA command 125 QUERY LIBRARY command 25 QUERY LOG 112 QUERY LOG command 37, 100 query mount 532 query NASBACKUP * 576
644
7718IX.fm
RESTORE DB command 402 restore systemservices command 418 restore systemstate 418 restore vm 416 restoremailbox parameter 243 riggered backups 99 rollback 567 rollback upgrade 567 ROLLFORWARD 396 rollforward operation 62 ROLLFORWARD recovery 58 rollforward recovery 62 rollforward utility 62 RTRIM function 622 rvoptsetencryptiondisabled option 416
S
SAN Device Mapping 22 SAP 15 snapshot environments 17 SAPOracle 16 schger driver 28 schgr native driver 27 sctl driver 27 sdisk driver 28 SELFTUNEBUFPOOLSIZE 39 Server enhancements, additions and changes 7 Version 5.3 improvements 8 server communication 406 FORMAT database 402 instance user ID 270 server command BACKUP DB 35 PREPARE 35 QUERY DRMSTATUS 35 QUERY NASBACKUP 35 server commands CONVERT ARCHIVE 37 DEFINE VOLUME 35 deleted 37 QUERY DB 35 QUERY LOG 35 QUERY OPTION 35 QUERY PROCESS 35 QUERY SESSION 35 QUERY STATUS 36 UPDATE ADMIN 36 UPDATE DEVCLASS 35 UPDATE VOLHISTORY 35 server configuration port 445 386 TCP/IP 393 server directories,Windows install server directories 383 server instance configure 380 creation 464
initialize 401 manual 399 starting 404 stopping 404 tcpport 469 user ID 327 server instances multiple on system 406 server messages 172, 456 server name 271 server naming 270 server objects expiration process 164 server operations disable for upgrade 294 server option ACTIVELOGSIZE 34 ARCHFAILOVERLOGDIR 34 ARCHLOGDIR 34 DBMEMPERCENT 406 DEDUPREQUIRESBACKUP 34 DEVCONFIG 400 DISKSTGPOOLMEMSIZE 34 MIRRORLOGDIR 34 NDMPPREFDATAINTERFACE 217218 TXNGROUPMAX 182 VOLUMEHISTORY 106, 400 server options TXNGROUPMAX 37 server options file 327 Server Options utility 406 server sommands SETOPT 36 Server utility DSMSERV DISPLAY DBSPACE 107 DSMSERV DISPLAY LOG 108 server utility DSMSERV FORMAT 36 server-connection tasks 457 service port 583 SET SQLDATETIMEFORMAT 38 SQLDISPLAYMODE 38 SQLMATHMODE 38 SET DBRECOVERY command 32, 35, 88, 90, 300 SET DBREPORTMODE 32, 116 SET DRMACTIVEDATASTGPOOL 32, 125 SET LOGMODE 38 set password command 227, 416 SETOPT command 36, 217 setup wizard 422 Seven Tiers of DR 142 shared library config 262 Shared Memory Communication 393 shared memory options 407 SharePoint Services 14 SHMPORT option 407 SHOW LOGV command 59 silent install batch script 382
Index
645
7718IX.fm
silent mode install 381 Single Instance Store 148 single sign-on 491 single signon 492 SMB protocol 384, 536 snap list command 230 Snapdiff DiffSnapShot=Latest option 225 incremental backup 225 SnapDiff API 224, 414 preparation 227 snapdiff option 225, 414 initial backup 226 NAS file system 229 SnapLock volume RECLAIMDELAY 25 SNAPMirror TYPE restrictions 222 SnapMirror image 219 snapmirror log 223 SNAPMirror parameter 221 SnapMirror restore unlike geometry 224 SnapMirror to Tape 219 restore 223 Snapshot 562 snapshot difference performance 236 snapshot operations 16 snapshotproviderfs option 420 snapshotproviderimage option 420 snapshotroot option 225 snmp daemon 408 SNMP subagent 408 space 263 Active log 520 future growth 519 server setup tips 519 upgrade process 520 V5 server 518 space considerations depuplication 156 space estimates database 519 space requirements 262 active log 265 active log mirror 265 archive failover log 265 archive log 265 recovery log 264 tables 266 TSM V6 server 263 upgrade 517 space requirements 518 work sheet 269 SPACETRIGGER commands 35 SQL queries 566 SQL1025N message 582 SQL1063N message 583 SQL5043N message 583
stagingdirectory option 417 stape driver 28 storage agents upgrade 524 storage pool verify 183 storage pool commands 35 storage pools 291 DEVTYPE=FILE 401 Sun Solaris upgrade 515 SYSSTAT function 219 system memory 363 system requirements 254 system state backup 418 System Storage Archive Manager 289
T
tape drive 420 tape library 420 TCP/IP 393 SHMPORT option 407 SSLTCPADMINPORT 407 SSLTCPPORT 407 TCPADMINPORT 407 TCPNODELAY 406 TCPPORT 406 TCPWINDOWSIZE 406 TCP/IP communication 430 TCP/IP options 406 tcpport 469 tdpexcc command 243, 246 telnet session 342 test upgrade 295 The Deployment Engine 365 threshold migration 191 command line client 197 environments 192 options 196 summary 198 tasks 197 THROUGHPUTDATATHRESHOLD option 183 THROUGHPUTTIMETHRESHOLD option 183 timeline 6 timestampdiff function 620 Tivoli Common Reporting 438, 440 Tivoli Event Portal 438 Tivoli Storage Manager Administration Center 453 client V5.3 enhancements 8 components development timeline 6 Extended Edition 5 for products 13 overview release timeline 6 Space Management 192 version compatibility 6 Tivoli Storage Manager Extended Edition 5 Tivoli Storage Manager for ERP 15
646
7718IX.fm
Tivoli Storage Manager for Mail 14, 239 Tivoli Storage Manager for Space Management Tivoli Storage Manager for Storage Area Networks 10 Tivoli Storage Manager HSM for Windows see HSM for Windows Tivoli Storage Manager V6 Upgrade Guide 290 transaction activity 59 transaction group 182 TSM ARCHIVE log 258 proprietary database 42 recovery logs 257 relabel volumes 24 TSM Client install 413 TSM Copy Services Copy Services TSM 17 TSM database 44 TSM Enterprise Edition 152 TSM for Data Retention 289 TSM inventory delete backup 225 TSM V6.1 INSERTDB utility 281 TsmAC 456 tsmdbmgr.opt file 92, 403 tsmddcfg script 28 tsmdlst tool 27 tsmdlst utility 28 tsmservers.xml file 455 TXNBYTELIMIT option 182183 TXNGROUPMAX server option 61 TXNGROUPMAX default 181 TXNGROUPMAX option 182 performance 183 TXNGROUPMAX options log records 182 Typical install 424
U
ulimit values 46 Uncommitted Read 45 UNDO ARCHCONVERSION 38 UNIX DB2 database 46 UNIX client install 421 UPDATE ARCHIVE 38 update_all command 351 Upgrade DB fall-back plan 261 V5 server space 518 upgrade 260, 523 AIX server 507 archive log 549 backup db command 303, 531 client nodes 524
compatibility 523 creation of server instance 545 data shredding 293 DB space 264 DB2 version 504 directories 548 disabling sessions 303, 531 dismount tapes 304, 532 EXTRACTDB utility 280 fallback 302, 530 HP/UX systems 508 hybrid method 289 instance directory 547 instance owner 546 library configuration 254 library managers 523 Linux on System z 513 Linux system 510 LOADFORMAT 281 media method 263, 521, 543 messages 557558 mirror log 549 multiple NICs 253, 262 multiple servers 522523 network method 263, 266, 521, 543 network wizard 284, 287 new system network 284 NOMIGRRECL option 292 prepare.out file 541 PREPAREDB 279 preparing steps 529 problem 530 process restart 567 return code 405 558 rollback 567 same system 285 same system network 287 scenario 528 scenarios 282 server modifications 530 server requirements 504 server upgrade 553 shared library config 262 space requirements 262263, 517 storage agents 524 Sun Solaris 515 system requirements 254 Target System Authentication 536 test 295 test environment 254 time 261 time estimate 521 total space 266 utilities 534 verification 561 Windows systems 516 wizard 284 wizard restart 542 wizard tool 535 upgrade methods 272
Index
647
7718IX.fm
upgrade phase 538 upgrade process space 520 summary 270, 502 upgrade server 351 upgrade utilitie 274 upgrade utilities 305, 523, 532 FTP downloads site 534 upgrade utility 253, 255 resources 506 upgrade utility package 504 upgrade wizard 523 upgrade wizards 300 upgradespace worksheet 269 upgrading external media 275 upgrading ISC 455 User Account Control 384
V
V6.1 database extraction process 306 virtual machine backup 414 vmbackdir option 417 vmbacknodelete option 417 vmbackuptype option 417 volume history backup volhistory 304, 532 volume history file 102, 104 Volume Shadow Copy Service 16 Volume Shadowcopy Service 420 VOLUMEHISTORY option 106 VOLUMEHISTORY server option 103 VTL RELABELSCRATCH 24 VTL devices 22
planning 362 register license 405 registry keys 402 server instance 383 server stop 404 silent mode 381 software 363 system memory 363 system requirements 362 TCP/IP options 406 user account control 384 Windows Registry 417 Windows service server instance 405 Windows system install server 362 Windows systems upgrade 516 wizard media method,upgrade media wizard 283 network method 284 wizard tool 535
X
X11 client 314 X11 environment 320 X11 pre-configured 315 X11 redirection 342 X11 remote setup 320 xterm & command 321
W
Web-client language files 420 Windows install 216 message 404 batch script 382 Client install 426 communication 406 components 367, 371 configuration 383 configure 376 DB2 considerations 362 DB2 password 372 debugging 409 default server 402 disk space 363 first to know 362 initialize server 401 installation folder 370 installation log 375 instance user ID 386 log gathering 411
648
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50# smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5 spine. Now select the Spine width for the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your book by opening the book file with the spine.fm still open and File>Import>Formats the
7718spine.fm
649
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50# smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5 spine. Now select the Spine width for the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your book by opening the book file with the spine.fm still open and File>Import>Formats the
7718spine.fm
650
Back cover
Learn the new features and function in Tivoli Storage Manager V6.1 Detailed installation, upgrade and customization provided Monitoring and reporting enhancement examples
This IBM Redbooks publication provides details of changes, updates, and new functions in IBM Tivoli Storage Manager Version 6.1. We 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. Hence, since 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 therein..