IBM Tivoli Storage Manager For Enterprise Resource Planning Data Protection For SAP Installation &amp User's Guide For DB2 Version 5.5

Tivoli Storage Manager for Enterprise Resource Planning
Version 5.5
Data Protection for SAP Installation and Users Guide for DB2
SC33-6341-09
Tivoli Storage Manager for Enterprise Resource Planning
Version 5.5
SC33-6341-09
Note! Before using this information and the product it supports, be sure to read the general information under Notices on page 237.
Edition Notice This edition applies to Data Protection for SAP Version 5 Release 5 Modification Level 0 (product number 5608APR) available as a licensed program product, and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications through your IBM representative or the IBM branch office serving your area. Publications are not stocked at the addresses given below. Address comments on this publication to: IBM Deutschland Entwicklung GmbH Enterprise Solution Development Dept. 3848, Bldg. 71032-15 Schoenaicher Str. 220 71032 Boeblingen Germany FAX (Germany): 07031 16 3619 FAX (other countries): (+49) 7031 16 3619 Internet Web page: http://www.ibm.com/software/tivoli Make sure to include the following in your comment or note: v Title and order number of this book v Page number or topic related to your comment When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1995, 2007. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii Tables . . . . . . . . . . . . . . . ix Preface . . . . . . . . . . . . . . . xi
Who Should Read This Book . . . . . . . . How to Read This Book . . . . . . . . . Where to Find More Information . . . . . . Naming Conventions Used in this Documentation Contents of the Data Protection for SAP Package . Supported Platforms . . . . . . . . . . Platform Differences . . . . . . . . . . Summary of Changes . . . . . . . . . . Support . . . . . . . . . . . . . . . xi . xi . xi xii . xii . xii . xii . xii . xiii Alternate Network Paths and Servers . . . Messaging . . . . . . . . . . . . Productivity Options of Data Protection for SAP Reporting . . . . . . . . . . . . Monitoring the Backup Status . . . . . Performance Analysis . . . . . . . . Managing Data on the Backup Server . . Using Data Protection for Snapshot Devices to Minimize Backup and Restore Windows . . . Archiving Inactive Data . . . . . . . . . . . . . . . . . . . . . . . . 17 17 17 17 17 17 18
| |
. 18 . 18
Part 2. Installing and Using Data Protection for SAP . . . . . . . . . 21

Chapter 4. Installing or Upgrading Data Protection for SAP . . . . . . . . . 23
Prerequisites for the Installation of Data Protection for SAP . . . . . . . . . . . . . . . . Installation Planning for Data Protection for SAP . . Installing Data Protection for SAP . . . . . . . Installing Data Protection for SAP on UNIX (AIX, Solaris) or Linux . . . . . . . . . . . . Installing Data Protection for SAP on Windows Post-Installation Steps . . . . . . . . . . . Review of the TSM Options Files . . . . . . Set the Password . . . . . . . . . . . Optional: Restart DB2 Instance . . . . . . . Verifying the Initial and Upgrade Installation . . Verifying the TSM API Installation. . . . . . Upgrading (Migration) . . . . . . . . . . Upgrading Data Protection for SAP . . . . . Migration of the DP for SAP Profile . . . . . Creation of Configuration Files . . . . . . . Special Installation . . . . . . . . . . . . Silent Installation . . . . . . . . . . . Console Installation. . . . . . . . . . . Firewall Installation . . . . . . . . . . Uninstalling Data Protection for SAP . . . . . . Uninstalling the Old Version of DP for SAP under UNIX or Linux . . . . . . . . . . Uninstalling the Old Version of DP for SAP under Windows . . . . . . . . . . . . 23 24 24 25 27 29 29 29 29 30 30 30 30 31 31 32 32 33 33 33 33 33
Part 1. Data Protection Basics . . . . 1

Chapter 1. Concepts of Data Protection for SAP . . . . . . . . . . . . . . . 3
DP for SAP and DB2 BACKUP DATABASE and RESTORE DATABASE . . . . . . . . . DP for SAP and Log File Management . . . . DP for SAP and BRARCHIVE / BRRESTORE . Data Protection for SAP and DB2 Log Manager . . . . . . . . . 3 5 5 7
| | | |
Chapter 2. Developing a Backup Strategy . . . . . . . . . . . . . . . 9

Types of Failures and the Scope of Data Protection for SAP . . . . . . . . . . . . . . . Trimming the Database Size . . . . . . . Transaction Rate . . . . . . . . . . . Backup Windows and Recovery Time. . . . Implementing the Strategy by Scheduling Automated Backup Runs . . . . . . . . . Scheduling Products . . . . . . . . . Sample Backup Strategy for Daily Backup Processing . . . . . . . . . . . . . . 9 . 10 . 10 . 10 . 11 . 11 . 12
Chapter 3. Introducing Data Protection for SAP . . . . . . . . . . . . . . 13

Scope of Data Protection for SAP . . . . . . Integration of Data Protection for SAP with SAP . Storing Data on a TSM Server . . . . . . . Performance Options of Data Protection for SAP . Parallel (Multiple) Sessions . . . . . . . Multiple (Parallel) Network Paths and Multiple (Parallel) Servers . . . . . . . . . . Incremental and Delta Backup . . . . . . RL Compression . . . . . . . . . . . Automation Options of Data Protection for SAP . Selectable Management Classes . . . . . . Retain Backups by Version . . . . . . . Multiple DB2 Log File Copies . . . . . .
Copyright IBM Corp. 1995, 2007
. . . . . . . . . . . .
13 14 15 15 16 16 16 16 16 16 16 16
Chapter 5. Adjusting Your System . . . 35

General Performance Considerations . . Database Server Considerations . . Network Considerations . . . . . Backup Server Considerations . . . Adjustments to DP for SAP for Improving Performance of Data Transfer . . . . Multiplexing . . . . . . . . . Multiple Sessions . . . . . . . Multiple Network Paths . . . . . Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 36 36 37 37 38 38 39 40
iii
| | |
Compression . . . . . . . . . . . . . Buffer Copies . . . . . . . . . . . . . Buffer Size . . . . . . . . . . . . . . Adjustments for Interaction with Other Components Adjustments for the Administration Assistant . . Adjustments for IBM Tivoli Storage Manager . . Rules for Adjustments in the DP for SAP Environment . . . . . . . . . . . . . . Using the VENDOROPT Parameter . . . . . Setting Up DB2 to Use the Built-In Log Manager with DP for SAP. . . . . . . . . . . . Adjustments for High Availability . . . . . . . Considerations for Using IBM HACMP for AIX
40 41 41 41 41 42 45 45 46 48 48
| |
Administering User IDs . . . . . . . . Configuring for Secure Communication . . . Changing the Password for the Administration Assistant Database User ID . . . . . . . Defining Thresholds . . . . . . . . . Defining the Custom SQL file . . . . . .
. 90 . 91 . 92 . 92 . 93
Chapter 9. Balancing Your System . . . 97

Observations on the DP for SAP Data Throughput Data Protection for SAP Performance Sensors . . Presentation of the Measurements in the Administration Assistant . . . . . . . . . Typical Situations . . . . . . . . . . Drilling Down on Special Situations . . . . Applying Backup Results to Restore . . . . 97 . 98 . 98 . 99 . 102 . 102
Chapter 6. Data Protection for SAP Backup Object Manager . . . . . . . 53

Backup Object Manager Setup . . . . . . Managing Backup Objects . . . . . . . Backup Object Manager Commands . . . Backup Object Manager Command Options Examples . . . . . . . . . . . . . . . . . . . . . . 54 55 55 58 61
Chapter 10. Reporting on Data Protection for SAP Activities . . . . . 105

Types of Reports . . . . . . . . . . . Reporting on Backup States . . . . . . Reporting on Operations Details . . . . . Reporting on Backup Operation Trends . . . Reporting on Failed Actions . . . . . . Reporting on the Performance of Backup Operations . . . . . . . . . . . . Prerequisites for Creating Reports . . . . . Creating a Report . . . . . . . . . . . Requesting a Report from the Administration Assistant Client . . . . . . . . . . . Working with Report Templates . . . . . Generating Reports Using Report Templates . Modifying Report Output . . . . . . . . . . . . . 105 105 106 106 107
Chapter 7. DB2 Redirected Restore Using Backup Object Manager . . . . 63

Tablespace Definition Information . . . . Creating Tablespace Definition Information . Redirected Restore . . . . . . . . . Redirected Restore Prerequisites . . . Redirected Restore in Automatic Mode . Redirected Restore in Interactive Mode . Redirected Restore in Batch Mode . . . Redirected Restore Plausibility Checks . . Sample Work Flow for Redirected Restore . Automated Tablespace Adaptations . . . Tablespace Scaling . . . . . . . . Tablespace Normalizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 65 65 65 66 67 68 69 70 72 72 74
. 107 . 109 . 109 . . . . 110 110 110 111
Part 3. Appendixes . . . . . . . . 113

Appendix A. The Data Protection for SAP Profile . . . . . . . . . . . . 115
Keyword Reference . . . . . . . . . Sample Data Protection for SAP Profiles . . Sample Data Protection for SAP Profile for UNIX or Linux . . . . . . . . . . Sample Data Protection for SAP Profile for Windows . . . . . . . . . . . . . . . . . 115 . 122 . 122 . 125
Chapter 8. Installing and Using the Administration Assistant for Data Protection for SAP . . . . . . . . . 77
Introducing the Administration Assistant . . . Functions and Features of the Administration Assistant . . . . . . . . . . . . . Concepts of the Administration Assistant . . Installing or Upgrading the Administration Assistant . . . . . . . . . . . . . . Prerequisites for Installing the Administration Assistant . . . . . . . . . . . . . Installation Planning for the Administration Assistant Server-Level Components . . . . Installing the Administration Assistant Server-Level Components . . . . . . . Post-Installation Steps . . . . . . . . . Starting and Stopping the Administration Assistant Manually . . . . . . . . . . Upgrading the Administration Assistant (Migration) . . . . . . . . . . . . Migration of Data from Previous Releases . . Configuring the Administration Assistant . . . . 77 . 77 . 78 . 81 . 81 . 82 . 82 . 85 . 87 . 88 . 89 . 90
Appendix B. Data Protection for SAP (DB2) Messages . . . . . . . . . . 129

How To Find Files Containing Message Output (Log Files) . . . . . . . . . . . . . Prefix BKI . . . . . . . . . . . . . . 129 . 130
Appendix C. Troubleshooting . . . . 165

Problem Resolution During Installation and Setup Understanding the Setup . . . . . . . . Location of Log Files . . . . . . . . . . General Problem Resolution . . . . . . . . Problem Resolution When Using the Backup Object Manager . . . . . . . . . . . . . . . Problem Resolution During Operation . . . . . Reproducible (Repeatable) Problems . . . . . 165 165 167 167 170 170 171
iv
Random Problems . . . . . . . . . . DB2 Vendor Reason Codes . . . . . . . . Providing Information to IBM or Tivoli Support
. 171 . 172 172
| | | | |
Appendix D. Using DP for SAP with a Distributed File System on AIX . . . . 175
Setting Up DP for SAP in a Distributed File System 175 Setting Up DP for SAP in a Distributed File System in an Adaptive Computing Environment . . . . 175
Appendix E. Installation Planning Sheets . . . . . . . . . . . . . . 177

Data Protection for SAP . Administration Assistant . . . . . . . . . . . . . . . . . 177 . 178
General Considerations for TSM . . . . . . Prerequisites . . . . . . . . . . . . . Adjusting Tivoli Storage Manager for DP for SAP . . . . . . . . . . . . . . . Configuring the Tivoli Storage Manager Clients General Considerations . . . . . . . . . Tivoli Storage Manager Clients on UNIX or Linux Systems . . . . . . . . . . . . Tivoli Storage Manager Clients on Windows Systems . . . . . . . . . . . . . . Password Handling . . . . . . . . . . . Password Configuration Matrix (UNIX or Linux) Password Configuration Matrix (Windows) . .
203 204 204 207 207 207 209 210 211 212
Appendix F. Alternate or Parallel Backup Paths and Backup Servers . . 183

Parameter Settings - SERVER Statement . . . . Example 1: Use of Alternate Paths for Increased Availability . . . . . . . . . . . . . Example 2: Use of Parallel Servers for Increased Performance . . . . . . . . . . . . . Example 3: Use of Alternate Servers for Disaster Recovery . . . . . . . . . . . . . . 184 185 187 188
Appendix L. Sample Tivoli Storage Manager Profiles . . . . . . . . . . 213

Sample TSM Profiles for UNIX or Linux . . . Client User Options File Sample (dsm.opt) . Client System Options File Sample (dsm.sys) Include/Exclude List Sample . . . . . . Sample TSM Profiles for Windows . . . . . Client User Options File Sample (dsm.opt) . Client Options Files Sample (<server>.opt) . Include/Exclude List Sample . . . . . . . 213 . 213 213 . 213 . 214 . 214 . 214 . 215
| |
Appendix G. Tablespace Definition Information (TDI) . . . . . . . . . . 189 Appendix H. Data Protection for SAP Setup Examples . . . . . . . . . . 193
Sample DB2 Vendor Environment File . . . . . 193
Appendix M. Backup Scheduling Examples . . . . . . . . . . . . . 217

UNIX or Linux Crontab Example . . . . . . Elements of Backup Schedules for UNIX or Linux Crontab File Sample . . . . . . . . . Full Offline Backup Shell Script Sample . . Windows Scheduling Example. . . . . . . Elements of Backup Schedules for Windows . . Schedule Batch Sample . . . . . . . . Full Offline Backup Batch File Sample . . . . 217 217 . 217 . 218 . 218 . 219 . 219 . 219
Appendix I. Reference Material for the Administration Assistant . . . . . . 195

Sample Command Files for Scheduling Reports 195 Sample Shell Script for Scheduling a Report from a UNIX Scheduling Client . . . . . . 195 Sample Command File for Scheduling a Report from a Windows Scheduling Client . . . . . 195 Sample Custom SQL File . . . . . . . . . 196
Appendix N. Hints and Tips for Network Settings . . . . . . . . . . 221

Networks with Large Bandwidth-Delay Product SP Switch (RISC 6000) . . . . . . . . . Network Settings of the Tivoli Storage Manager 221 . 222 222
Appendix J. Using DP for SAP to Back Up and Restore Files and Databases . . . . . . . . . . . . . 197
Backups and Restores in Non-Partitioned Database Environments . . . . . . . . . . . . . Starting Backups in a Non-Partitioned Database Environment . . . . . . . . . . . . Starting Restores in a Non-Partitioned Database Environment . . . . . . . . . . . . Backups and Restores in Partitioned Database Environments . . . . . . . . . . . . . Using DB2 Single System View (SSV) for Backup 197 197 197 198 200
| Appendix O. Internet Protocol Version | 6 (IPv6) Support . . . . . . . . . . 223
Appendix P. Support Information . . . 225

Using IBM Support Assistant . . . Obtaining Fixes. . . . . . . . Receiving Weekly Support Updates . Contacting IBM Software Support . Determining the Business Impact . Describing Problems and Gathering Submitting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information . . . . . 225 225 226 227 228 228 228
Glossary . . . . . . . . . . . . . 231 Notices . . . . . . . . . . . . . . 237

Trademarks and Service Marks . . . . . . . 237
Appendix K. Preparing Tivoli Storage Manager for DP for SAP . . . . . . . 203

Configuring the Tivoli Storage Manager Server . . 203
Contents
Accessibility . . . . . . . . . . . . . Navigating the Interface Using the Keyboard Magnifying What is Displayed on the Screen
. 238 239 239
Index . . . . . . . . . . . . . . . 241
vi
Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. DB2 Backup Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 DB2 Log File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Log Management with DB2 Log Manager and DP for SAP . . . . . . . . . . . . . . . . . . 7 DB2 Backup Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Production Backup Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Scope of Data Protection for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Integration of Data Protection for SAP with DB2 . . . . . . . . . . . . . . . . . . . . . 14 Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Data Transfer for a Backup / Restore . . . . . . . . . . . . . . . . . . . . . . . . . 37 Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Parallel (Multiple) Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Parallel (Multiple) Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Null Block Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Sample Environment for HACMP Takeover . . . . . . . . . . . . . . . . . . . . . . . 49 Data Protection for SAP Backup Object Manager . . . . . . . . . . . . . . . . . . . . . 54 Redirected Restore Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Tablespace Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Tablespace Normalizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Administration Assistant Components (with Default Port Numbers) . . . . . . . . . . . . . . 78 Example of an SAP Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 A Birds Eye View of the Data Flow During Backup . . . . . . . . . . . . . . . . . . . . 97 Performance Optimizing by Using Sensors . . . . . . . . . . . . . . . . . . . . . . . 98 Showing Data Throughput and I/O Utilization . . . . . . . . . . . . . . . . . . . . . 98 Indicating a Disk Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Indicating a Network or TSM Bottleneck . . . . . . . . . . . . . . . . . . . . . . . 100 Indicating a Balanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 101 Drilling Down: Replay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Operations Detailed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Operations Daily Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Operations - Failure Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Performance Report - Graphical Presentation Section . . . . . . . . . . . . . . . . . . . 108 Performance Report - Tabular Presentation Section . . . . . . . . . . . . . . . . . . . . 109 SAP and Data Protection for SAP Configuration files on UNIX and Linux. . . . . . . . . . . . . 166 General Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
vii
viii
Tables
| | | |
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. File Extensions for Shared Libraries . . . . . . . . . . . . Database Configuration Parameters Introduced with DB2 V8.2 . . . Tags for Defining Thresholds in the Custom SQL File . . . . . . Contents of the Custom SQL File . . . . . . . . . . . . . DB2 Vendor Reason Codes . . . . . . . . . . . . . . . Installation Parameters for Data Protection for SAP . . . . . . . Installation Parameters for the Administration Assistant . . . . . SERVER Statement and Appropriate Profile and Option File Settings. . Password Handling for UNIX or Linux . . . . . . . . . . . Password Handling for Windows . . . . . . . . . . . . . Tuning of Network Settings . . . . . . . . . . . . . . . Tuning of SP Switch Buffer Pools . . . . . . . . . . . . . Tuning Tivoli Storage Manager Configuration File Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 . 46 . 93 . 94 . 172 . 177 . 178 . 184 . 211 . 212 . 221 . 222 . 222
ix
Preface
Who Should Read This Book
This manual is intended for system programmers and administrators who are responsible for implementing a backup solution in the SAP environment using the Tivoli Storage Manager. It explains the procedures needed to install and customize Data Protection for SAP, the interface between SAP and the Tivoli Storage Manager. The reader should be familiar with SAP, Tivoli Storage Manager, and DB2 documentation. This book describes release v5.5, November 2007.
How to Read This Book

The manual is split into three parts, of which the first is a general introduction into data protection, the second describes the installation, the architecture and properties of Data Protection for SAP, and the third part (Appendixes) gives reference information. If you are a person experienced in data protection, you might want to skip chapters 1 and 2, however you may want to browse chapter 3 for new functions. The information given in part 2 is for system programmers and administrators who know how Data Protection for SAP is embedded in a comprehensive data protecting system. If you are a data protection novice, you might want to start reading the publication from part one on. This way you get introductional information of what protecting your data means and what needs to be considered while setting up a data protection system.
Where to Find More Information

For more information about IBM Tivoli Storage Manager for Enterprise Resource Planning, refer to the Tivoli Internet home page at:
http://www.ibm.com/software/tivoli/products/storage-mgr-erp/
| | |
The most up-to-date version of this book is available in the IBM Tivoli Information Center at
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmerp.doc/dperp.html
In order to access a national language version of this book, make sure you have your browser set to the appropriate language. | | | The release notes for Tivoli Storage Manager for Enterprise Resource Planning V5.5 are also available in the Tivoli Information Center:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmreadme.doc_5.5/relnote_erp550.html
xi
Naming Conventions Used in this Documentation

| | | | | | | | | | | | | | | | | In this documentation, IBM Tivoli Storage Manager for Enterprise Resource Planning. Data Protection for SAP is usually referred to as Data Protection for SAP or as DP for SAP. IBM Tivoli Storage Manager is usually referred to as Tivoli Storage Manager or TSM. SAP AG has discontinued the use of "mySAP" in favor of 'SAP'. Unless otherwise stated, references in this publication toUNIX apply to all supported UNIX-based systems, references to Linux apply to all supported Linux platforms, and references to Windows apply to all supported Windows platforms. The term DB2 refers to any version of the product DB2 for Linux, UNIX, and Windows supported by Data Protection for SAP. Prior versions of this manual used DB2 Universal Database and DB2 UDB for this designation. As of DB2 9, Universal Database and UDB are no longer part of the product designation. In recent versions of this publication, the terms EEE (Enterprise Extended Edition) and ESE (Enterprise Server Edition) have denoted the DB2 version supporting database partitioning. As of DB2 Enterprise 9, this term has been replaced by DPF (Database Partitioning Feature). All of these terms should be considered synonymous.
Contents of the Data Protection for SAP Package

Each platform-related Data Protection for SAP package includes installation packages for Oracle and DB2, as well as for the Administration Assistant, on a CD-ROM or in a CD image downloadable via IBM Passport Advantage. See the README information (at the CD level or in the installation packges) and the Release Note file in the Tivoli Information Center (Where to Find More Information on page xi) for information that updates the topics in this publication. Note: There is a separate package and release note for the Administration Assistant (see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77).
Supported Platforms
For a list of supported platforms see the online Release Note (Where to Find More Information on page xi)..
Platform Differences
There are only small differences between the UNIX or Linux and Windows versions of Data Protection for SAP. One of these differences is that UNIX or Linux uses the path separator / compared with \ for Windows and that the drive letter is specified for Windows. Non-trivial differences between the UNIX or Linux and Windows versions of Data Protection for SAP are mentioned explicitly. | | |
Summary of Changes
The following new functionality has been added to Version 5.5.0. of Data Protection for SAP for DB2:
xii
| | | | | | | | | | | | | | | | | | | | |
v If DB2 V8.2 or higher has been installed and the DB2 instance started, the DP for SAP installation program automatically sets the VENDOROPT parameter in the DB2 configuration and optionally also sets the LOGARCHMETHn and LOGARCHOPTn parameters to enable DB2 log archiving via DP for SAP. v The following enhancements have been added to the Administration Assistant: The internal database can now be a DB2 database. Thresholds can be defined to enable alerting under certain conditions via display indicators and e-mail. v The '-x' option of BackOM can be used in conjunction with the password option '-c password' to modify the password on all partitions of a partitioned database. v Internet Protocol Version 6 (IPv6) is supported by Data Protection for SAP and the Administration Assistant. Unless otherwise noted, any specification of an IP address in this document can be an IPv4 or IPv6 address. For general information, see Appendix O, Internet Protocol Version 6 (IPv6) Support, on page 223. Examples continue to use the IPv4 address format. v Information on the DB2 Single System View (SSV) capability is provided (Using DB2 Single System View (SSV) for Backup on page 200). Other changes include v SAP AG has discontinued the use of "mySAP" in favor of 'SAP'. v Information is provided on storing control files on remote Windows shares (see Implementing Configuration Files on Remote Shares on page 28).
Support
See Appendix P, Support Information, on page 225 for general information concerning provision of support by IBM. Providing Information to IBM or Tivoli Support on page 172 lists the types of information that you should provide to the support function.
Preface
xiii
xiv
Part 1. Data Protection Basics
Chapter 1. Concepts of Data Protection for SAP

This chapter explains how Data Protection for SAP integrates with the backup and restore processes of DB2 and the SAP-DB2 Administration Tools. It is intended as a supplement to your SAP, DB2, and Tivoli Storage Manager documentation. If you are already experienced in Data Protection for SAP for DB2, you may want to move on to the next chapter. DB2 backups are initiated by the DB2 BACKUP DATABASE command. DB2 backups can be done online or offline, partial or full, as a complete, incremental, or as a delta backup. For discussion of these alternatives, please refer to your DB2 documentation. DB2 databases are restored with the DB2 RESTORE DATABASE command. DB2 restores can be partial or full, using complete, incremental, or delta backups. Partial restores can be done online or offline; full restores must be done offline. The archiving of DB2 offline log files is provided by the SAP tool BRARCHIVE. The retrieval of DB2 offline log files is provided by the SAP tool BRRESTORE and by the DP for SAP tool BackOM. As of DB2 version 8.2, offline log files can be archived and retrieved with the DB2 built in Log Manager.
DP for SAP and DB2 BACKUP DATABASE and RESTORE DATABASE

| | | | | The DB2 Command Line Processor (CLP) interprets commands for the DB2 database and passes control to a DB2 Server Process. In the case of DP for SAP, the "LOAD <libraryname>" option causes DB2 to invoke the Data Protection for SAP shared library. This process triggers the backup or restore, loads the library dynamically and communicates with it through the Vendor API. For starting a backup or restore, the DB2 CLP communicates with the DB2 Server Process, providing the Server Process with the relevant information for processing the database.
Concepts of Data Protection for SAP
Figure 1. DB2 Backup Architecture
For a BACKUP DATABASE command, the DB2 Server Process v creates a unique timestamp to identify the backup v loads Data Protection for SAP dynamically as a shared library v reads the data from the database containers v reads the DB2 configuration files v creates data blocks containing the backup image and passes these blocks to the data mover part of DP for SAP The Data Protection for SAP shared library passes the data blocks on to Tivoli Storage Manager (TSM), which writes the data blocks to the storage media (tape or disk). At the end of the backup process, the DB2 Server Process logs the backup in the Recovery History File. For a RESTORE DATABASE command, the DB2 Server Process v loads Data Protection for SAP dynamically as a shared library v requests the backup data from the shared library The Data Protection for SAP shared library v checks with the Tivoli Storage Manager if the backup image is available v retrieves the data blocks from TSM

v passes the data blocks to the DB2 Server Process The DB2 Server Process v restores the DB2 data to the database containers v logs the restore in the Recovery History File
DP for SAP and Log File Management

Starting with DB2 version 8.2, one of two log file management facilities in an SAP enviromment can be chosen for archiving and retrieving log files. These are the SAP-DB2 Administration Tools BRARCHIVE and BRRESTORE and the built-in DB2 Log Manager. Data Protection for SAP supports both of these log management methods, but the built-in DB2 Log Manager in combination with Data Protection for SAP makes archiving and retrieving log files easier and more comfortable.
DP for SAP and BRARCHIVE / BRRESTORE

DB2 log files in an SAP environment can have four different states during their life cycle: v online active The log file is currently being used by DB2 for logging transactions. v online retained The log file is no longer being used for logging transactions, but it contains transactions with data pages that have not yet been written from the buffer pool to disk. It will be needed by DB2 in case of a crash recovery or for roll-back. The DB2 logging user exit is called by DB2 (if configured) to copy a filled online log file to the log_archive directory. Do not use operating system commands for copying online log files. v offline retained The log file is no longer being used by DB2 and does not contain transactions with unwritten data pages. It is not crucial for a crash recovery or a roll-back. After the log file has been successfully copied to the log_archive path DB2 may eventually delete the log file. v archived BRARCHIVE has successfully archived offline retained log files to TSM.
Chapter 1. Concepts of Data Protection
Figure 2. DB2 Log File Management
The SAP-DB2 Administration Tools support the backup of DB2 log files: Filled or closed online log files are immediately copied from the log_dir directory by the DB2 logging user exit to the log_archive directory. Offline log files are backed up from the log_archive directory with the SAP tool BRARCHIVE. Archived retained log files are restored with the SAP tool BRRESTORE. For a detailed description of the DB2 logging user exit functionality and of the SAP-DB2 Administration Tools BRARCHIVE and BRRESTORE, refer to the Database Administration Guide in your SAP documentation. For archiving DB2 log files (BRARCHIVE), the SAP tool v creates a unique timestamp for identification; v loads Data Protection for SAP dynamically as a shared library. The Data Protection for SAP shared library: v reads the data from file v creates data blocks v passes the data blocks on to TSM. Tivoli Storage Manager writes the data blocks to the storage media (preferably disk). The SAP tool logs the archive run in the SAP administration database. For retrieving logs (BRRESTORE), the SAP tool v loads Data Protection for SAP dynamically as a shared library v requests the backup data from the shared library. The Data Protection for SAP shared library v checks with the Tivoli Storage Manager if the requested log file data is available v retrieves the data blocks from TSM

v writes the data blocks to a file on disk. The SAP tool logs the retrieve run in the SAP administration database.
Data Protection for SAP and DB2 Log Manager

DB2 log files in an SAP environment can have four different states during their life cycle: v online active The log file is currently being used by DB2 for logging transactions. v online retained The log file is no longer being used for logging transactions, but it contains transactions with data pages that have not yet been written from the buffer pool to disk. It will be needed by DB2 in case of a crash recovery or for roll-back. Nevertheless, the DB2 Log Manager copies a filled online log file to a possible archive location. Do not use operating system commands for copying online log files! v offline retained The log file is no longer being used by DB2 and does not contain transactions with unwritten data pages. It is not crucial for a crash recovery or a roll-back. Thus, the log file will be archived to location(s) specified in the database configuration and if it was successful, DB2 deletes the log from the database log directory. v archived Filled or closed log files, that were successfully archived to TSM.
Figure 3. Log Management with DB2 Log Manager and DP for SAP
Data Protection for SAP is loaded dynamically by the DB2 Log Manager as a shared library on UNIX or Linux, or as a DLL on Windows, and runs as part of the
Chapter 1. Concepts of Data Protection

DB2 engine. When a log file is ready to be archived (online/offline retained) the DB2 Log Manager starts to archive this file by passing it blockwise to DP for SAP. Data Protection for SAP passes these data to TSM. If a database rollforward recovery was issued, the DB2 Log Manager checks first if the corresponding log files are already located either in the log path or in an overflow log path specified with the DB2 rollforward command. If the log files were not found at one of these locations, the DB2 Log Manager checks with Data Protection for SAP if the corresponding log images can be found on TSM. If yes, Data Protection for SAP retrieves the data from TSM and passes them blockwise to the DB2 Log Manager, who writes the log files to the filesystem. Then, these log files will be applied by special DB2 processes to the database. For a detailed description of the DB2 Log Manager refer to the Administration Guide in your DB2 documentation.
Chapter 2. Developing a Backup Strategy

This chapter helps you define an appropriate backup strategy for your SAP system. If you already have a successful backup strategy in place you may want to move on to the next chapter. The strategy you choose is dependent on your specific requirements. Consider the following questions: v What type of events do you wish to protect your SAP system against? v How large is your database? v What is the transaction rate of your database? v How fast do you need to recover from a failure? v What backup windows are available?
Types of Failures and the Scope of Data Protection for SAP

In case of a corrupted database (user errors or transaction failures), you may want to restore the database to a specific point in time. In this case, it is sufficient to restore the database and configuration files. To do this, a backup image of the database and the corresponding DB2 log files are required. When storage hardware failures occur, you may want to restore the database to the latest possible point in time. In this case, you may also need to restore database executables, SAP system data and user data in addition to the database image and the DB2 log files. For disaster recovery, you will need to restore all operating system data and all of the above. Data Protection for SAP solely covers the backup and restore of SAP database objects, as shown in Figure 4.
Figure 4. DB2 Backup Objects
Developing a Backup Strategy

Please note that there is no provision for backing up online DB2 log files that are required for crash recovery. Therefore, it is recommended to place the DB2 log directory on a mirrored disk. In order to protect the system against the loss of SAP executables, user data, or even operating system data you should use the incremental backup capabilities of the Tivoli Storage Manager backup-archive client with its selective incremental backup capabilities. The Tivoli Storage Manager selective incremental backup function allows you to define an include-exclude list of files that is applied automatically during incremental backup operations. For further information about include-exclude lists, see your Tivoli Storage Manager manuals, using the backup-archive clients. This list should be used to exclude data already stored using Data Protection for SAP, i.e. all database files, such as containers and offline log files. Examples of include-exclude lists for UNIX or Linux can be found in Sample TSM Profiles for UNIX or Linux on page 213 and for Windows in Sample TSM Profiles for Windows on page 214. Sample files can also be found in your Data Protection for SAP installation package. In order to be protected against the complete loss of the operating system, for example in the case of a storage hardware failure, it is imperative that after the installation of the operating system or after updates/upgrades of the operating system, system backups are made with the operating system utilities, e.g. mksysb for AIX. This will allow you to start your system from the backup medium. Base backups should include a configured TCP/IP environment as well as the Tivoli Storage Manager client including the API in order to be able to restore all other data.
Trimming the Database Size

Obviously, backing up and restoring large databases takes longer than backing up and restoring smaller databases. Therefore, you may want to consider off-loading inactive data to an archive. DB2 CommonStore for SAP, a companion product to Data Protection for SAP, provides this functionality. See also Archiving Inactive Data on page 18 and http://www.ibm.com/software/data/commonstore/sap/.
Transaction Rate
Due to high transaction rates, SAP databases usually require frequent database and log file backups.
Backup Windows and Recovery Time

Your backup strategy usually has two main objectives: v Minimize down-time after a failure. v Minimize the impact of backup activity on the application. These are conflicting goals: Generally, recovery is fastest when an up-to-date full backup is available, and only few or no log files need to be applied. Offline backups need the database to go off-line. If your database needs to stay on-line all the time, online backups must be employed. They take more time as they share system resources with the application. It should also be noted that online backups contain inconsistent data. After restoring an online backup, the database must be rolled forward to consistency by applying the log files generated during the backup window. Incremental and delta backups take less time than do full backups, but recovery
10

time is longer: An incremental backup saves the data changed since the latest full backup. For recovery using an incremental backup, the latest full backup and the incremental backup must be restored. A delta backup saves the data since the latest backup. For recovery using a delta backup, the latest full backup and all intermediate delta backups must be restored. Delta backups may be advisable after only limited changes to the data. The longer the intervals between backups, the more log files need to be applied in order to roll forward a database, adding to the time required for recovery. Therefore, choose backup intervals that allow you to guarantee acceptable recovery results while not using up too many database resources.
Implementing the Strategy by Scheduling Automated Backup Runs

To ensure that all your data will be backed up regularly at a certain time, it is recommended that you schedule automated backup and archive operations.
Scheduling Products
There are several products that can be used to set up a schedule, for example: v SAP scheduler (CCMS) v UNIX or Linux crontab / Windows scheduler v Tivoli Storage Manager scheduler v IBM Tivoli Workload Scheduler
SAP Scheduler
Within SAP , the Computer Center Management System (CCMS) provides a scheduler for database administration and backup planning on a single database server. The scheduler can be started from the SAPGUI command line (transaction code db13) or with the SAPGUI menu functions (Tools -> CCMS -> DB administration -> DBA scheduling).
UNIX or Linux crontab / Windows Scheduler

Another possibility of backup automation on the database server level is offered by the cron jobs for UNIX or Linux systems or schedule services for Windows. An example of a cron job can be found in UNIX or Linux Crontab Example on page 217.
Tivoli Storage Manager Scheduler

The Tivoli Storage Manager also provides functions for automating operations of all its clients. Therefore, the scope of control can comprise multiple database servers. Schedule definition work can be done quickly using the GUI based Tivoli Storage Manager Web administrative client. Information on how to define Tivoli Storage Manager schedules can be found in the Tivoli Storage Manager Administrators Reference manual.
IBM Tivoli Workload Scheduler

The IBM Tivoli Workload Scheduler provides event-driven automation, monitoring, and job control for both local and remote systems. More information can be found at http://www.ibm.com/software/tivoli/products/scheduler/.
Chapter 2. Developing a Backup Strategy
11
Sample Backup Strategy for Daily Backup Processing

The following figure illustrates the sequence of backup runs you may want to establish for a daily backup schedule. This example of automated backup operations shows the following typical tasks
Figure 5. Production Backup Example
v Full database backup, e.g., offline or without application load, performed each night. v Offline log files are backed up to disk during online hours. This has the advantage of eliminating the need for extra tape mounts for relatively small files.
Note Backups can be performed to disks as well as to tape environments. Tivoli Storage Manager will manage the data regardless of the storage media. However, it is recommended that the SAP database is directly backed up to tape. v Within Tivoli Storage Manager, archived log files are migrated from disk to tape after the full database backup. v SAP system files are backed up incrementally with the Tivoli Storage Manager backup-archive client. v The last backup in the daily cycle is the backup of the Tivoli Storage Manager database. This should always be done.
12
Chapter 3. Introducing Data Protection for SAP

This chapter explains the Data Protection for SAP architecture and gives an introduction to the product features. Even if you are an experienced user of Data Protection for SAP you may want to browse this overview for new features. Data Protection for SAP together with Tivoli Storage Manager provides a reliable, high performance, and production-oriented solution that allows you to backup and restore your DB2-based SAP systems. It is integrated with DB2s backup and recovery facilities and allows you to follow SAPs backup and recovery procedures. Being optimized for SAP databases, Data Protection for SAP allows you to manage large volumes of data most efficiently.
Scope of Data Protection for SAP
Figure 6. Scope of Data Protection for SAP
Data Protection for SAP and the SAP-DB2 Administration Tools for archiving and retrieving DB2 log files are focussed on the database objects, where over 90 % of the data on an SAP database server reside. Thus Data Protection for SAP will be used for backup and restore of database contents, control files, and offline DB2 log files. (See Figure 6). Other files such as SAP and DB2 executables can be backed up using the IBM Tivoli Storage Manager Backup-Archive Client. As a consequence, in the case of a disaster recovery, you have to make sure that all DB2 and SAP executables are available before starting restore and recovery of your database using Data Protection for SAP and the SAP-DB2 Administration Tools.
13
Introducing Data Protection for SAP
Integration of Data Protection for SAP with SAP

Once configured, Data Protection for SAP operates as an invisible link between DB2 and the SAP-DB2 Administration Tools on one hand and Tivoli Storage Manager on the other. A shared library is dynamically linked by DB2 backup/archive processes and by the SAP utilities.
Figure 7. Integration of Data Protection for SAP with DB2
The Data Protection for SAP package also contains the Administration Assistant, aimed at increasing the administrators productivity. The Administration Assistant typically resides on a different server and communicates with Data Protection for SAP via TCP/IP. It can control several instances of Data Protection for SAP. Its functionality covers configuring an instance of Data Protection for SAP, data transfer performance monitoring and monitoring of the backup status of connected SAP systems as well as the TSM server activity related to these SAP systems. It allows you to monitor and administer all of your Data Protection for SAP instances remotely via an applet running in a Web browser. You may register an SAP instance with the Administration Assistant during installation. For information on how to register at a later time or with a different Administration Assistant, refer to Adjustments for the Administration Assistant on page 41.
14
Storing Data on a TSM Server

Data Protection for SAP transfers data to and from the backup server via a single session or via multiple (parallel) sessions to a TSM server. Each session must have a storage device associated with it. The SAP backup ID is persistently linked with each backup file. This backup ID can be used later to determine all files required for a complete restore.
Note In SAP terminology backup (BRBACKUP) means backup of database contents, archive means the backup of offline DB2 log files. DP for SAP employs the TSM archive function for both backup types. It is highly recommended to use tape storage for the database contents, as this has consistently proven to provide the best data throughput for backup and restore. For backing up log files it is recommended to use a disk-tape storage hierarchy and to backup each DB2 log file right after it is placed into the archive directory. This yields the best protection against data loss and eliminates the necessity to mount a tape for each DB2 log file. Collocation is a function in TSM to ensure that client data is kept together on one tape. We recommend to deactivate collocation for backups with DP for SAP in order to enable parallel sessions to use multiple tape drives in parallel. Collocation must also be deactivated in order to use the multiple log copy function, see Multiple DB2 Log File Copies on page 16. Views of backups on the TSM server are generated by the utility backom. For details, please refer to Chapter 6, Data Protection for SAP Backup Object Manager, on page 53.
Note DP for SAP can be configured to use multiple TSM servers to improve either availability (alternate servers) or performance (multiple servers). DP for SAP accesses only the servers defined in its profile when inquiring for the backup repository. Therefore care has to be taken when removing TSM servers from the DP for SAP profile while they still hold valid backup data. Database backups are usually kept for a specified time until they become obsolete. In order to manage backup storage space efficiently these backups should then be deleted so tapes can be reclaimed. There are two ways to perform this deletion: 1. by setting the archive retention period with TSM, or 2. by using the DP for SAP backup version control function. Data Protection for SAP deletes whole backup generations, i.e. full backups and all related partial and log file backups, when the specified number of versions is exceeded.
Performance Options of Data Protection for SAP

To achieve good data transfer rates for backup and restore you have to make sure that the following three components all have good data transfer rates: the disks on which the database is located, the network between the database host and the TSM server, and the backup storage device containing the backup. Keep in mind that the weakest of these components constrains your backup/restore performance and
15

thus appears as a bottleneck. Data Protection for SAP offers a variety of options to optimize the data transfer rate for each of these components.
Parallel (Multiple) Sessions

Data Protection for SAP allows you to backup or restore data to multiple tape drives in parallel. Parallelism is achieved by using more than one session to send data to a backup server For details see Multiple Sessions on page 38.
Multiple (Parallel) Network Paths and Multiple (Parallel) Servers

You can configure Data Protection for SAP to distribute a backup of a database across two or more TSM servers. Similarly, by providing two or more separate network connections between the SAP database host and the TSM server, you can configure Data Protection for SAP to balance network traffic across all available network connections to the TSM server. For details see Multiple Network Paths on page 39 and Multiple Servers on page 40.
Incremental and Delta Backup

Data Protection for SAP supports incremental and delta backups of DB2 databases. Depending on the system environment, this may result in decreased backup times.
RL Compression
RL Compression is a fast and very effective mechanism to compress a partially filled database. For such a database you can reduce network traffic, decrease the number of tapes required for a backup, and reduce the impact of network induced bottlenecks. For more information see Compression on page 40.
Automation Options of Data Protection for SAP

Data Protection for SAP comes with a variety of options that help improve your administrative productivity.
Selectable Management Classes

You can specify different TSM management classes for backing up and archiving data. It is best practice to configure Data Protection for SAP to backup directly into a tape storage pool and to archive DB2 log files into a disk storage pool. In addition multiple management classes have to be used in conjunction with multiple DB2 log files. For information how to specify management classes, see the profile keywords BRARCHIVEMGTCLASS and BRBACKUPMGTCLASS starting on page 116.
Retain Backups by Version

This function enables you to limit the number of full backups kept on the TSM server. If there is more than a specified number of full backups saved on a TSM server, the oldest version is deleted. This function keeps track of all DB2 log files, database control files, partial, incremental and delta backups, depending on a full backup. All these objects are removed together with a full backup.
Multiple DB2 Log File Copies

For protection against storage hardware failures and to improve availability and disaster recovery, you can backup multiple copies of a log file in a single archive
16

run. You may want to configure your system so that these copies are located on different physical Tivoli Storage Manager volumes or even different TSM servers. If at restore time one log file copy is unavailable Data Protection for SAP automatically switches to another copy and continues restoring the log file from that copy. For more detailed information about creating and using DB2 Log Copies, see the profile keyword REDOLOG_COPIES on page 119.
Alternate Network Paths and Servers

Similar to the configuration of multiple network paths and servers, you can configure Data Protection for SAP to use multiple TSM servers or multiple network connections to one TSM server alternately to improve availability of backup storage. In such a configuration Data Protection for SAP checks all servers and network connections for availability and allows you to perform your backups even if some resources are currently unavailable. Also, you can establish policies to use different TSM servers at different days of the week.
Messaging
You can establish policies that trigger Data Protection for SAP to send different classes of log messages to a TSM server.
Productivity Options of Data Protection for SAP Reporting

At the end of a backup, Data Protection for SAP produces a report providing statistical information such as the number of bytes transferred and the effective data throughput. By using the Administration Assistant program provided with Data Protection for SAP, you have access to detailed performance information that helps you optimize your systems. You can also monitor the backup status across all of your SAP database servers. For more information see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77. The information provided by the Administration Assistant can be included in XML- or HTML-format reports for display and printing. For more information on the creation of reports see Chapter 10, Reporting on Data Protection for SAP Activities, on page 105.
Monitoring the Backup Status

The Administration Assistant allows you to monitor the backup status of multiple SAP database servers via a graphical user interface. For details, see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77.
Performance Analysis
The Administration Assistant provides performance data for all components involved in the data transfer. It supports the analysis of performance information with graphical representations that help to locate bottlenecks and to exploit resources efficiently. For details, see Chapter 9, Balancing Your System, on page 97.
17
Managing Data on the Backup Server

The Backup Object Manager contained in the Data Protection for SAP package allows you to find backup objects on the TSM server, restore, or remove them. For details, refer to Chapter 6, Data Protection for SAP Backup Object Manager, on page 53. | | | | | | | | | | | | | | | | | | | | | | | |
Using Data Protection for Snapshot Devices to Minimize Backup and Restore Windows
Although Data Protection for SAP provides extensive methods to minimize downtime, your service level agreements for business-critical databases might demand even faster recovery operations. Data Protection for SAP, together with an SAP-enabled component of the companion product IBM Tivoli Storage Manager for Advanced Copy Services Data Protection for Snapshot Devices (formerly known as Data Protection for FlashCopy Devices for SAP) allows you to perform backups and restores if you are running your SAP database on IBM FlashCopy devices (such as IBM DS6000 or DS8000, IBM SAN Volume Controller (SVC), IBM Enterprise Storage Server (ESS)), or IBM System Storage N series devices with snapshot capability. By using these features, you can keep your production downtime to a minimum by exploiting the point-in-time copy functions offered by these devices. Starting with DB2 9.5, DB2 offers a functionally restricted version of TSM for ACS known as DB2 Advanced Copy Services, which can be upgraded to an unrestricted level by installing the full TSM for ACS version (V5.5 or higher). In this environment, the software based on TSM for ACS is also called using the DB2 BACKUP DATABASE and RESTORE DATABASE commands, but they contain the keywords "USE SNAPSHOT" rather than the "LOAD <library>" phrase used to call the shared library for DP for SAP. "USE SNAPSHOT" causes DB2 to load and interact with the TSM for ACS Snapshot Backup Library. More information on Data Protection for Snapshot Devices can be found at:
http://www.ibm.com/software/tivoli/products/storage-mgr-advanced-copy-services/
Archiving Inactive Data

DP for SAP is designed for operational backups, i.e. a database image is stored on a bit level. This method is NOT at all recommended for true, long-term archiving. Outdated backups need to be restored into exactly the same environment they were initially taken from in order to access the data from within SAP applications. This would require keeping old versions of SAP, OS, database and TSM to rebuild this environment and cannot be viewed as a reliable process. SAP, instead, provides special archiving functions included in its application modules to generate so-called business documents for displaying information with long term retention requirements. These business documents are format-independent and can be used for auditing and other legal purposes. Archived data can then be removed from the operational database to trim its size and, as a result, reduce the backup / restore windows. Another IBM product, DB2 CommonStore for SAP, connects with the SAP interface ArchiveLink using TSM as an external archive for v inactive data (data retention) v printlists (e.g. reports)
18

v v v v outgoing documents (e.g. printed output like invoices, bills) incoming documents (e.g. digitized fax, scanned letters, audio) local documents (e.g. text, spreadsheets, pictures, graphics) inactive data
Thus TSM can be used as an integrated repository for backups and for archived information. For more information on DB2 CommonStore for SAP , see: http://www.ibm.com/ software/data/commonstore/sap/.
19
20
Part 2. Installing and Using Data Protection for SAP
21
22
Chapter 4. Installing or Upgrading Data Protection for SAP

DP for SAP must be installed on any system that is to be used as an SAP database server. In order to set up DP for SAP, do the following: 1. Check that the DP for SAP package is complete. See the README.1ST file on each CD (or CD image) for a description of the contents. 2. Make sure that the requirements are met. For details, see Prerequisites for the Installation of Data Protection for SAP below. 3. Get planning information. For details, see Installation Planning for Data Protection for SAP on page 24. 4. Install the DP for SAP Administration Assistant. This software is optional but highly recommended. It should be installed prior to Data Protection for SAP so that the latter can connect to it automatically as part of its installation procedure. For details, see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77. 5. Install Data Protection for SAP. For details, see Installing Data Protection for SAP on page 24. 6. Perform post-installation steps. For details, see Post-Installation Steps on page 29. 7. Verify the installation. For details, see Verifying the Initial and Upgrade Installation on page 30. If you are going to do an upgrade installation, see page 24.
Prerequisites for the Installation of Data Protection for SAP

The following products must be installed before you can start setting up Data Protection for SAP: v DB2, v SAP R/3 or SAP e-business Solution, based on DB2, v the SAP-DB2 Administration Tools, (if their DB2 Logfile management is to be used), v Tivoli Storage Manager (TSM), v An operating system at a level supported by SAP and the Tivoli Storage Manager client. For hardware and software prerequisites, as well as product versions supported and maintenance levels required by the current version of Data Protection for SAP and the Administration Assistant, refer to the Release Notes file in the Tivoli Information Center.(see Where to Find More Information on page xi) For information on SAP functions, product versions, and maintenance levels that are compatible with your version of SAP R/3 or SAP, consult SAP support, for example via the SAP Service Marketplace at: http://service sap.com/.
23
Installing or Upgrading Data Protection for SAP

The latest SAP-DB2 Administration Tools must be installed on the SAP database server if it is earlier than DB2 V8.2 or if the SAP Tools DB2 log management is chosen to enable backup or restore of DB2 offline log files. See SAP Notes 141619 and 315352 for additional information. For information on configuration of the Tivoli Storage Manager API client, refer to Appendix K, Preparing Tivoli Storage Manager for DP for SAP, on page 203. TCP/IP must be ready for communication between the Tivoli Storage Manager server and the Tivoli Storage Manager client. | | | | | In case Data Protection for SAP is to be installed on a distributed file system, the root user needs read and write access to the fle system for the duration of the installation. For more information on the installation in a distributed file system, refer to: Appendix D, Using DP for SAP with a Distributed File System on AIX, on page 175.
Installation Planning for Data Protection for SAP

When starting the installation procedure, be prepared to provide the required information. For your convenience, an installation planning table is available in Appendix E, Installation Planning Sheets, on page 177 and in file form in planning_sheet (UNIX and Linux) or planning_sheet.txt (Windows) in the installation directory. There is a separate planning sheet for the Administration Assistant. After you have ensured that all prerequisites have been met and the installation planning steps were followed, the installation process can begin. This includes: 1. Installing the software 2. Performing post-installation steps 3. Verifying the installation with a backup and restore run | | | | | | | | | | | | | | |
Installing Data Protection for SAP

The installation packages are located on the Data Protection for SAP CD-ROMs and also on the IBM public FTP server. Images of the CD-ROMs can also be downloaded via Passport Advantage. Initial installations must always be done from the CD-ROM or image. Refer to the file README.1ST in the root path for information on where to find documents on the CD or image, and follow the appropriate installation description below. If you are going to upgrade from an earlier version of Tivoli Data Protection for R/3 (DB2) or Data Protection for SAP (DB2) in your environment, you have the option to either upgrade from the product CD-ROM or image, or to download the latest version from the IBM FTP server. See http://www.ibm.com/software/sysmgmt/products/support/ IBMTivoliStorageManagerforEnterpriseResourcePlanning.html For the specific procedure for upgrading from an earlier version, refer to Upgrading (Migration) on page 30.
24

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Installing Data Protection for SAP on UNIX (AIX, Solaris) or Linux

Data Protection for SAP for these operating systems is delivered as a single executable file for each platform. These installation packages are provided on a CD or CD image, or also on the IBM FTP server. The packages are named as follows: v For a CD or CD image, the name has the format:
<version>-TIV-TSMERPDB2-<platform>
See the README.1ST file in the root directory of the CD or CD image for a list of its contents. v Packages on the FTP server contain 'FTP' prior to the platform designation. The package files have an extension appropriate to the platform and are executable. When you invoke the file, you will be guided through the Data Protection for SAP setup procedure. To ensure that the setup procedure is carried out properly, read the following description carefully and follow the guidelines on the panels that are displayed during setup. Shared libraries have different file extensions on different UNIX or Linux platforms. Within the following the section, the file extensions of shared libraries are represented as <ext>. Replace this text with the extension applying to your platform:
Table 1. File Extensions for Shared Libraries Operating System AIX HP-UX Linux Solaris Extension a sl so so
To install Data Protection for SAP on a UNIX or Linux system, do the following: 1. Read the Release Notes for Data Protection for SAP (see Where to Find More Information on page xi). 2. Log in as the root user on the SAP database server machine. 3. Ensure that you have set the DISPLAY variable correctly, because the installer guides you through the installation via a graphical X-Window. For alternate ways of installing, see Special Installation on page 32. 4. If DB2 V8.2 or higher is installed, and you want to allow the installation program to make appropriate updates to the DB2 configuration, start the DB2 instance. 5. Invoke the executable mentioned above and follow the instructions of the installation dialog. 6. Check the summary at the end of the installation dialog. In the summary, among other information, you will find the installation path of DP for SAP. Installation results are also logged in the installation log named log.txt located in the installation path.
25

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During installation, the following modifications are done to your system automatically: v An entry is created in /etc/inittab to start the ProLE daemon automatically. v An entry is created in /etc/services for the service tdpr3db2 (32-bit version) or tdpr3db264 (64-bit version). v Environment variable DB2_VENDOR_LIB points to the fully qualified path where the shared library of Data Protection for SAP resides. v Environment variable XINT_PROFILE points to the Data Protection for SAP profile located in the path for configuration files specified during installation. The file name is init<SID>.utl where <SID> is the DB2 database SID specified during installation. v Environment variable TDP_DIR points to the path where Data Protection for SAP saves its configuration files and creates its own process logs. Initially, this path is set to <profile path>/tdplog where <profile path> is the path for DP for SAP profile specified during installation. v If DB2 V8.2 or higher is installed, and the DB2 instance has been started, the installation program does the following: sets the VENDOROPT parameter in the DB2 configuration to the DP for SAP vendor environment file. asks whether DB2 log archiving should be managed via DP for SAP. If the reply is No, the applicable database configuration settings are not modified. If the reply is Yes, the choice of using LOGARCHMETH1, LOGARCHMETH2, or both methods is offered. The following values are then set appropriate to the method(s) selected:
LOGARCHMETHn LOGARCHOPTn VENDOR:/<path>/<library> /<path>/vendor.env
Note: If the DB2 instance has not been started prior to this step, the above actions have no effect and must be performed manually at a later time. See Using the VENDOROPT Parameter on page 45 and Setting Up DB2 to Use the Built-In Log Manager with DP for SAP on page 46 for more information. After the installation, the following files are available on your system: v In the installation path of DP for SAP: README README_TSMERP<version><language>.html TIPHINTS libtdpdb2.a or libtdpdb264.a (AIX) libtdpdb2.so or libtdpdb264.so (Linux or Solaris) ProLE backom createinfo initSID.utl SanFSsetupFS.sh (AIX only) Various sample files A folder named _uninst is also created, which contains several files. agent.lic (only after installation from CD-ROM or CD image. v In the path of the DP for SAP configuration files: init<SID>.utl vendor.env agent.lic (copy of file in installation directory)
26

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Installing Data Protection for SAP on Windows

DP for SAP for Windows is delivered as a single file for each platform. These installation packages are provided on a CD or CD image, or also on the IBM FTP server. The packages are named as follows: v On a CD or within a CD image, the name is:
<version>-TIV-TSMERPDB2-<platform>
The files are executable and have an .exe extension. See the README.1ST file in the root directory of the CD or CD image for a list of its contents. v Packages on the FTP server contain 'FTP' prior to the platform designation. To install DP for SAP on a Windows system, do the following: 1. Read the Release Note provided for DP for SAP (see Where to Find More Information on page xi). 2. Log in as a user with Administrator authority on the SAP database server machine. 3. If DB2 V8.2 or higher is installed, and you want to allow the installation program to make appropriate updates to the DB2 configuration, start the DB2 instance. 4. Invoke the DP for SAP executable and follow the instructions of the installation dialog. 5. Check the summary at the end of the installation dialog. In the summary, among other information, you find the installation path of DP for SAP. Installation results are also logged in the installation log named log.txt located in the installation path. During installation, the following modifications are done to your system: v The ProLE service is installed and started. v An entry is created in: %windir%\system32\drivers\etc\services needed for the service: tdpr3db2; (32-bit version) or tdpr3db264 (64-bit version). v Optionally, the environment variables DSMI_DIR, DSMI_CONFIG, and DSMI_LOG are modified. v Environment variable DB2_VENDOR_LIB points to the fully qualified path where the DLL of DP for SAP resides. v Environment variable XINT_PROFILE points to the DP for SAP profile located in the path specified during installation. The file name is init<SID>.utl where <SID> is the DB2 database SID specified during installation. v Environment variable TDP_DIR points to the path where DP for SAP saves its configuration file and creates its own process logs. Initially, this path is set to <profile path>\tdplog where <profile path> is the path for DP for SAP profile specified during installation. v If DB2 V8.2 or higher is installed, and the DB2 instance has been started, the installation program does the following: sets the VENDOROPT parameter in the DB2 configuration to the DP for SAP vendor environment file. asks whether DB2 log archiving should be managed via DP for SAP. If the reply is No, the applicable database configuration settings are not modified.
27

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the reply is Yes, the choice of using LOGARCHMETH1, LOGARCHMETH2, or both methods is offered. The following values are then set appropriate to the method(s) selected:
LOGARCHMETHn LOGARCHOPTn VENDOR:<path>\tdpdb2.dll <drive>:\<path>\vendor.env
Note: If the DB2 instance has not been started prior to this step, the above actions have no effect and must be performed manually at a later time. See Using the VENDOROPT Parameter on page 45 and Setting Up DB2 to Use the Built-In Log Manager with DP for SAP on page 46 for more information. After the installation, the following files are available on your system: v In the installation path of DP for SAP: README.txt README_TSMERP<version><language>.html TIPHINTS.txt tdpdb2.dll ProLE.exe backom.exe createinfo.exe initSID.utl agent.lic (only after installation from CD-ROM or CD image) Various sample files A folder named _uninst is created, which contains several files. v In the path of the DP for SAP profile: initSID.utl, where SID is replaced by the DB2 database SID provided during installation vendor.env agent.lic (only after installation from CD-ROM, or a CD image)
Implementing Configuration Files on Remote Shares

A process on Microsoft Windows which is started as a regular service runs by default under the ID of the local system account. This means that the process runs on the local system with Administrator privileges, but on remote systems the session is opened without credentials, and therefore no permissions. See Microsoft knowledge base article 132679 for details:
http://support.microsoft.com/kb/132679
This is the reason that ProLE cannot access files residing on a remote share. It is irrelevant whether the share was mapped to a local drive letter or is accessed in UNC notation (\\server\path\filename). As of V5.4, DP for SAP accepts UNC notation for the profile and infile (passed via the backint command line), but not for all the files specified within the profile. These files will be opened by ProLE, which by default has no permission to access remote shares, as explained above. To enable ProLE to access such files on a remote share, the following steps must be performed: 1. Map the share where the configuration files reside to a local drive letter. 2. Modify the profile (.utl) to refer to the pathnames on the mapped drive. 3. Modify the ProLE service such that it no longer runs with a local system account but as an account with permissions to access the mapped drive. Note
28

| | | | that this might have other implications when using a regular account. For example, when the password for this account expires or is changed, the service will no longer be able to start. 4. Restart the ProLE service to activate the changes.
Post-Installation Steps
After successfully completing the installation dialog for DP for SAP, you need to perform the following steps in order to get a properly running system: 1. Review the TSM Option files. 2. Set the initial password. 3. Verify the installation.
Review of the TSM Options Files

The TSM client options files need to be checked in order to make sure that they contain the correct server name as specified in the server statement of the init<SID>.utl file, and that the parameters are set correctly. These depend on the password method selected. (See Modifying the Handling of the TSM Password on page 43). On UNIX or Linux the TSM server definition is typically done in the TSM client system options file (dsm.sys). The server stanza specified in dsm.sys must match the entry in init<SID>.utl. On Windows you have to define a client options file <servername>.opt. This file must be in the directory containing dsm.opt. <servername> is the name you specified in init<SID>.utl.
Set the Password

DP for SAP should be installed after the TSM installation has been completed. TSM provides different password methods to protect data. DP for SAP must use the same method as specified within TSM. When DP for SAP is installed, it is assumed that the password method selected during the TSM installation was manual password handling (PASSWORDACCESS prompt). The default parameters for DP for SAP are set according to this assumption. If a different password method is set within TSM, refer to Password Handling on page 210 in order to adjust the DP for SAP parameters. To be able to work with DP for SAP, you have to provide DP for SAP with the password for the TSM node. This is a manual step:
backom -c password
For more information on the password, refer to Modifying the Handling of the TSM Password on page 43. For more information on backom, see Chapter 6, Data Protection for SAP Backup Object Manager, on page 53.
Optional: Restart DB2 Instance

If your SAP database is a DB2 Version 8.1 FP2 or later, you can restart the DB2 instance in order to promote the DB2 profile registry variable and the contents of
29

the vendor environment file as a default to DB2. However, if you do not want to restart the DB2 instance or if you need to override the defaults of the DB2 instance, you can pass the name of the vendor environment file with each invocation of DB2 BACKUP DATABASE or DB2 RESTORE DATABASE. As of DB2 Version 8.2 (8.1 FP7), you can enter the fully qualified name of the vendor environment file in the database configuration using the VENDOROPT option.
Verifying the Initial and Upgrade Installation

In order to verify the installation of DP for SAP, start a full database backup and restore it afterwards. You can do this either with the DB2 Control Center or directly from the operating system command line with the DB2 CLP. It is also strongly recommended that you do a restore/recovery of the entire SAP database. A good method to prepare for this is to first run a complete offline backup.
Verifying the TSM API Installation

In order to verify the TSM API installation, submit the following command and check the correct system reply: v AIX 32 bit: lslpp -l tivoli.tsm.client.api v AIX 64 bit: lslpp -l tivoli.tsm.client.api.64bit. Both versions should respond with: tivoli.tsm.client.api <version> COMMITTED TSM Client - Application Programming Interface v Solaris: pkginfo TIVsmCapi should respond with: application TIVsmCapi Tivoli Storage Manager Solaris <version> API Client v Linux: rpm -q TIVsm-API should respond with: TIVsm-API-<version>
Upgrading (Migration) Upgrading Data Protection for SAP

Note: The format of the configuration file (.bki) was changed with release V5.4. The software accepts the previous format and converts it automatically. If it is necessary to fall back to a version earlier than 5.4, the old format can be recovered by overwriting the new file with the empty file provided with the previous version and then initializing it (by setting TSM passwords, for example). However, the information about the current backup number will be lost. This means that more backup versions must be retained for a certain period of time than is specified by the MAX_VERSIONS parameter. In order to upgrade DP for SAP from an earlier version of Data Protection for SAP, do the following: 1. Check that the DP for SAP package is complete. The installation packages are provided on CD-ROMs or CD images downloadable from Passport Advantage and are also available on the IBM FTP server. See the release notes file in the
30

Tivoli Information Center (Where to Find More Information on page xi) for information supplementing this manual. 2. Check the readme files and release notes for incompatibilities between your installed version and the new version. Make sure, that data backed up with an older version of Tivoli Data Protection for R/3 or DP for SAP can still be restored with the version you are going to install. For example, data that was backed up with Tivoli Data Protection for R/3 Version 3.1 or 3.2 or DP for SAP.com Version 3.3 can be restored with Data Protection for SAP Version 3.3. or higher., 3. Make sure that the requirements for the new version of DP for SAP are met. For details, see Prerequisites for the Installation of Data Protection for SAP on page 23. 4. Get or retrieve planning information. For details, see Installation Planning for Data Protection for SAP on page 24. 5. We recommend a full backup of the SAP database before upgrading to the new version. 6. Uninstall the old version. For this procedure, see Uninstalling Data Protection for SAP on page 33. 7. Install the new version of DP for SAP. For details, see Installing Data Protection for SAP on page 24. 8. Adapt the DP for SAP profile. For details, see Migration of the DP for SAP Profile. 9. Create the configuration file(s). For details, see Creation of Configuration Files. 10. Perform some post-installation steps. For details, see Post-Installation Steps on page 29. 11. Verify the installation. For details, see Verifying the Initial and Upgrade Installation on page 30. 12. We recommend a full backup after upgrading to the new version.
Migration of the DP for SAP Profile

When uninstalling DP for SAP, the license file, the profile, and the configuration files are left behind. They can be used by the new version of DP for SAP. During installation, you may choose not to change the profile. This way, the configuration and the connection to the TSM server can be reused. However, if you upgrade DP for SAP from version 3.3.10 or lower, you need to adapt the value of keyword CONFIG_FILE in the profile: Old version (UNIX): CONFIG_FILE <path>/init<SID>.bki New version (UNIX): CONFIG_FILE <path>/%DB2NODE/init<SID>.bki Note: The values in bold must not be changed. On Windows systems, the adaptations need to be done accordingly, using the Windows path delimiter \.
Creation of Configuration Files

There are two ways of creating the configuration file:
31

1. When setting the TSM password with the backom utility (see Chapter 6, Data Protection for SAP Backup Object Manager, on page 53) the configuration files for all DB2 partitions are created automatically in the paths <path>/%DB2NODE/, where <path> is the directory denoted by the value of keyword CONFIG_FILE in the profile and the string %DB2NODE is replaced automatically by a DB2 partition name referenced in the DB2 configuration file db2node.cfg. If the directory denoted by the value of keyword CONFIG_FILE is not located in the same network file system where the DB2 configuration file db2nodes.cfg is located, this procedure must be repeated for each machine where a partition of the database resides. If the database is not partitioned, NODE0000 is used as the only DB2 partition name. 2. If you do not want to set the TSM password, you can manually create the required paths: For each database partition, create directory <path>/%DB2NODE/, where <path> is the directory denoted by the value of keyword CONFIG_FILE in the profile and the string %DB2NODE is replaced by one existing node (partition) found in the DB2 configuration (see db2node.cfg). The naming convention for a name to be built from the node (partition) number is a string starting with NODE followed by a four digit partition number, e.g. NODE0000 for partition 0. Then copy the existing file init<SID>.bki into each of these paths. If the directory denoted by the value of keyword CONFIG_FILE in the profile is not located in the same network file system where file db2nodes.cfg is located, this procedure must be repeated for each machine where a partition of the database resides. If the database is not partitioned, NODE0000 must be used as the only DB2 node name.
Special Installation Silent Installation

Installation can be done from the command line. For a preparation for silent installation, you have to have the system generate (record) the installation options in a file using the "- options-record" switch:.
<<package file name> -options-record <options filename>
This creates an options file that can be checked easily and modified for use in installing various systems. To perform a silent installation, the install package is called with the prepared options file as follows:
<package file name> -options <options filename> -silent
32
Note: Options required for a silent installation are dependent on the version of Data Protection for SAP and may vary with different modification levels. Therefore, when installing an upgrade it is recommended to record a new options file before performing a silent installation of this new version.
Console Installation
To support target systems without a window manager, the setup program supports deploying an installation in console mode. An installation running in console mode suppresses the graphical wizard panel display available with a GUI installation. Instead, user data entry and status messages are displayed on the console or in the command prompt window. To start the console installation, enter the following command:
<package file name> [-options-record <options filename>] -is:javaconsole -console
Firewall Installation
If you need to install DP for SAP remotely through a firewall and if the TCP port for X11 communication is not enabled, use the console installation as described in Console Installation.
Uninstalling Data Protection for SAP

Before upgrading the old version of DP for SAP to a higher level, you have to uninstall the old package on your system as described in the following sections. Your profile and configuration files are retained.
Uninstalling the Old Version of DP for SAP under UNIX or Linux

To uninstall the old version of DP for SAP, perform the following steps: 1. Log in as root user 2. Make sure that the DISPLAY variable is set correctly, because the uninstall procedure requires a graphical X-Window. 3. Make sure the old version of DP for SAP is not running. 4. Invoke the executable
<installation path>/_uninst/uninstaller.bin
where <installation path> is the installation path documented in the summary at the end of the installation dialog, and follow the instructions of the uninstall dialog.
Uninstalling the Old Version of DP for SAP under Windows

To uninstall the old version of DP for SAP on a Windows NT, Windows 2000, or Windows 2003 machine, perform the following steps: 1. Log on as user with administrator authority on the SAP database server machine. 2. Ensure that the old version of DP for SAP is not running.
33

3. 4. 5. 6. Select Start Settings Control panel. Click on Add/Remove Programs. Select the old version of DP for SAP and click on Remove. Follow the instructions of the uninstall procedure.
34
Chapter 5. Adjusting Your System

This chapter is intended to help you find the configuration of Data Protection for SAP that best fits your needs. You may want to adjust Data Protection for SAP to: v Optimize the performance of your data protecting environment, or to v Change the way Data Protection for SAP interacts with components like Tivoli Storage Manager, or the Data Protection for SAP Administration Assistant.
General Performance Considerations

A simplistic model of the data transfer via Data Protection for SAP is comprised of three components (see Figure 8): v the SAP database server v the network v the TSM server also known as backup server
Figure 8. Data Transfer
A continuous stream of data is generated between these components for the backup or restore of data. The weakest link in this chain limits the overall data rate. The following general guidelines result from experience gathered with many actual installations and should be considered for designing an efficient backup/restore infrastructure and process.
35
Adjusting Your System
Database Server Considerations

In most cases, the production (SAP database) server is the most critical component for data transfer when the various techniques of parallelism are applied (see Adjustments to DP for SAP for Improving Performance of Data Transfer, below). Special attention should be given to the following items: v CPU power. Data transfer, as well as data compression or employing local or LAN-free backup cause additional load on the CPU of the database server on top of the application load (online backup). In many environments, CPU power of the database server is the most critical constraint. The CPU load for LAN-free backups (Managed System for SAN) can be significantly reduced by deploying a highly efficient data transfer method available with Rel. 5.3. For details, refer to Buffer Copies on page 41. v I/O paths. When setting up your I/O system for maximum data rates, consider using fast disk attachments, for example via internal busses like PCI. File system features, like caching or reading ahead, have an effect on data rates as well and should be adapted to the specific characteristics of backup/restore with its large files and data volumes. v Volume Manager settings. Volume mirroring by Volume Manager can slow down the data transfer during restore significantly. For a fast restore, we recommend to turn off mirroring during the restore. v Disk layout. The file layout of the database can have a significant impact on maximum achievable data rates. The DB2 backup utility allows parallel access to tablespaces during backup and restore. In order to exploit this feature, data should be spread across several disks. v Size of database. The size of a database should be trimmed by offloading inactive data to an external archive. For archive support, refer to the companion product DB2 CommonStore for SAP (see Archiving Inactive Data on page 18).
Network Considerations
Consider the following items when deciding on the network setup: v LAN-free backup. The LAN-free backup is intended to reduce the load on the network and on the TSM server and to yield higher data transfer rates than a network backup. Make sure that the capacity of the fiber channel adapters to the SAN can handle the composite data transfer rates of disk reads and tape writes. v Network bandwidth. Our experience shows that the effective throughput capacity is approximately half of the theoretical network bandwidth. For high-speed networks such as Gigabit Ethernet LAN, the network adapters most likely limit the throughput rather than the network itself. v Network topology. Consider implementing a dedicated backbone network for backup and restore, apart from the user LAN. v TCP options. Make sure to use the TCP options appropriate for your environment. For more specific hints, refer to Appendix N, Hints and Tips for Network Settings, on page 221. v Multiple Paths. Data Protection for SAP allows you to increase the overall throughput rate to the backup server by specifying multiple network paths. For details, see Multiple Network Paths on page 39. More hints on network settings are given in Appendix N, Hints and Tips for Network Settings, on page 221.
36
Backup Server Considerations

Note: For all backup activities, Data Protection for SAP uses the archive function of IBM Tivoli Storage Manager. Consider the following when setting up the TSM server: v Dedicated backup server. A dedicated backup server allows sharing of resources and yields most efficient resource utilization. v CPU power. Observations show that for a given data throughput the CPU load on the backup server is approximately 60% of that on the database server. Therefore, backup server CPU power is not quite as critical as the CPU power of the database server. However, if you are going to allow several clients to access a single TSM server, demands on the TSM server CPU do increase. v Storage hierarchy. Backup of data files (large files) should be directed to tape in order to achieve the highest transfer rates. If disks must be used, it is recommended to use one disk pool per session. Small files like log files should be directed to disk storage first and then be migrated to tape collectively to avoid excessive tape mounts. v Parallel sessions. The TSM server allows using several tape drives in parallel to store data and thus increase overall data throughput. In order to exploit this feature, the corresponding TSM node must be allowed the appropriate number of mount points and the device class must be allowed the appropriate mountlimit. More information on how to set up TSM for cooperation with Data Protection for SAP can be found in Appendix F, Alternate or Parallel Backup Paths and Backup Servers, on page 183 and Appendix K, Preparing Tivoli Storage Manager for DP for SAP, on page 203.
Adjustments to DP for SAP for Improving Performance of Data Transfer

After the primary installation, Data Protection for SAP is configured to send uncompressed backup data to a TSM server via a single session.
Figure 9. Data Transfer for a Backup / Restore
When tuning Data Protection for SAP, there is not a single configuration that is best for all environments. Rather, you will need to experiment with the following adjustments in order to find the configuration that works best for you. You may use function View Performance Data of the Administration Assistant to find out about performance characteristics and how they change with your configuration. For more details on tuning a system with the Administration Assistant refer to Chapter 9, Balancing Your System, on page 97 or you may want to tune your system in the following order:
37

1. Optimize the configuration of the database server, the network, and the TSM server according to your needs. Some hints can be found in General Performance Considerations on page 35. 2. Increase multiplexing. See Multiplexing below. 3. Increase the number of sessions. See Multiple Sessions. 4. Increase the number of network paths or TSM servers. See Multiple Network Paths on page 39 and Multiple Servers on page 40. Usually, when you start employing parallelism, you will see a gain in performance. You will want to find the point when this gain is offset by overhead as you increase the numbers. For example, when you are working with multiple sessions you will find out that for a certain number of sessions adding another tape and another session does not give you any improvement or even decreases performance. This indicates that the network might now be the bottleneck, and you may want to try multiple network paths next.
Multiplexing
In order to better exploit the tape drive used for database backup on the backup server, you may want to try parallel access to data on the database server.
Figure 10. Multiplexing
In a DB2 environment, this feature is provided by the DB2 backup utility via the PARALLELISM parameter of the BACKUP DATABASE and RESTORE DATABASE commands. For details, refer to your DB2 Command Reference.
Multiple Sessions
Data Protection for SAP allows you to make use of several tape drives simultaneously in order to increase the transfer rate to or from a Tivoli Storage Manager server.
Figure 11. Parallel (Multiple) Sessions
38

The keyword MAX_SESSIONS is used for defining the number of parallel sessions to be established with the TSM server for database backup, archive (backup of log files) and restore. For a detailed description of how to use this keyword, refer to page 118. When running a database backup, the data will usually be written directly to tape drives on the Tivoli Storage Manager server. The parameter specified in the MAX_SESSIONS keyword must match the number of tape drives used simultaneously. These must be available to the management class defined as BRBACKUPMGTCLASS in the DP for SAP profile (see on page 116). When setting up the Tivoli Storage Manager, be sure to v not activate collocation in the (tape) storage pool defined for the management class chosen as BRBACKUPMGTCLASS v make available as many tape drives for this management class as the number of sessions defined in MAX_SESSIONS, as multiple accesses to the same tape may slow down data transfer. When running BRARCHIVE for DB2 log file backups, either disk or tape storage pools can be utilized. These must be available to the management class defined as BRARCHIVEMGTCLASS in the Data Protection for SAP profile (see on page 116). If you are using tape pools as (primary) pools for this management class the same considerations as for database backups apply. When using disk storage pools, the following rules apply: v Several sessions of one BRARCHIVE run can utilize one or two independent disk storage pool(s). v Several sessions of BRARCHIVE runs of different databases can simultaneously utilize one or two independent disk storage pool(s). The number of storage pools required depends on the number of backup copies requested for a DB2 log file. For details, see keyword REDOLOG_COPIES on page 119.
Multiple Network Paths

Data Protection for SAP allows you to use multiple network connections (paths) for data transfer between the database server and the backup server.
Figure 12. Parallel (Multiple) Paths
Parallel paths can be used to eliminate network bottlenecks. For each additional path, additional network adapters are required on both the production and the
39

backup server. For each adapter of the backup server, a server statement must be entered in the Data Protection for SAP profile (see keyword SERVER on page 120). Make sure that the value of keyword MAX_SESSIONS is not greater than the sum of all SESSION values of the SERVER statements of servers that are available for concurrent use. The setup for multiple (parallel) network paths is described in detail in Appendix F, Alternate or Parallel Backup Paths and Backup Servers, on page 183.
Multiple Servers
Data Protection for SAP allows you to use multiple backup servers.
Figure 13. Multiple Servers
Multiple servers can be used by DP for SAP to eliminate backup server bottlenecks by distributing backup data among two or more backup servers. Note that for each additional path additional network adapters are required on both the database and the backup server. For each adapter of each backup server, a server statement must be entered in the Data Protection for SAP profile (see keyword SERVER on page 120). Make sure that the value of keyword MAX_SESSIONS is not greater than the sum of all SESSION values of the SERVER statements of servers that are available for concurrent use. The setup for parallel servers is described in detail in Appendix F, Alternate or Parallel Backup Paths and Backup Servers, on page 183.
Compression
40
Figure 14. Null Block Compression
By compressing zero-byte blocks, a very simple, but fast compression method, Data Protection for SAP decreases the amount of data to be sent to the TSM server. Although compression does create some additional CPU load on the database server it might improve performance if the network is the bottleneck. It is efficient with database files usually containing large portions of null blocks. For details on how to activate Data Protection for SAP compression, refer to keyword RL_COMPRESSION on page 120.
Buffer Copies
Data Protection for SAP uses internal buffers to store and exchange data with the IBM Tivoli Storage Manager. When passing data from one component to another, data buffers are copied by default. DP for SAP allows to prevent copying the data buffers by passing on the original data buffers. This reduces the CPU load of the database server. However, if client compression and/or client encryption are activated in the Tivoli Storage Manager options file (dsm.sys or dsm.opt on UNIX or <server>.opt on Windows), buffer copies cannot be prevented. See also keyword BUFFCOPY on page 116.
Buffer Size
Data Protection for SAP allows to tune the size of its internal data buffers. These buffers are used for both reading from disk and passing data to the Tivoli Storage Manager client API. It is recommended to optimize the buffer size for disk I/O. The default buffer sizes are 131072 (128K) for UNIX or Linux and 32768 (32 K) for Windows systems. In most cases, the default settings yield acceptable results. For EMC disk subsystems, the best transfer rates have been achieved when the buffer size was set equal to the stripe size. See also keyword BUFFSIZE on page 117. Before increasing the size of internal buffers make sure that sufficient storage is available for the number of buffers acquired by Data Protection for SAP. This number correlates to the number of sessions requested. By activating compression, the number of buffers is doubled.
Adjustments for Interaction with Other Components Adjustments for the Administration Assistant
In order to make use of the Administration Assistant (highly recommended), you have to set up a connection between Data Protection for SAP and the Administration Assistant. This is usually done during installation of Data Protection for SAP, provided the Administration Assistant was previously installed (also recommended). If you enter the Administration Assistant information during
41

installation of Data Protection for SAP, the latter connects and sends data to the Administration Assistant during backup and restore runs. If you do not specify the use of the Administration Assistant during installation of DP for SAP, you can set up the connection at a later time by following the description given in Specifying the Administration Assistant Server Component. For details on the Administration Assistant, see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77.
Specifying the Administration Assistant Server Component

If you need to specify a new Administration Assistant Server component, perform the following steps on the SAP database server: Specifying an Administration Assistant Server component on UNIX or Linux 1. Find the entry for daemon ProLE in /etc/inittab. Modify the entry to read:
.../prole -p tdpr3db2 | tdpr3db264 <Server component hostname> <port>
where <Server component hostname> is the name or IP address of the host running the Administration Assistant Server component and <port> is the port the Server component is listening to for connects from DP for SAP (default 5126). 2. Make sure that DP for SAP is not running, and use the kill command to stop the ProLE daemon. The ProLE daemon will be restarted automatically with the new parameters. Specifying an Administration Assistant Server component on Windows Log in as a user with administrator authority. From a command prompt, issue:
prole -update -p tdpr3db2 | tdpr3db264 <Server component hostname> <port>
where <Server component hostname> is the name or IP address of the host running the Administration Assistant Server component and <port> is the port that the Server component is listening to to for connects from DP for SAP (default 5126).
Adjustments for IBM Tivoli Storage Manager

After the primary installation, Data Protection for SAP is configured to send data to a single backup server; manual password handling is assumed and Data Protection for SAP backup version control is turned off. The following describes the configuration changes necessary to change these initial settings.
Specifying Another Tivoli Storage Manager Server

To add a new Tivoli Storage Manager server to your configuration, you need to perform the following steps: 1. Add a new server statement to your Data Protection for SAP profile. 2. Adapt the TSM options files as described in Review of the TSM Options Files on page 29.
42

3. Set and save the TSM password for the new server as described in Set the Password on page 29.
Alternate Network Paths and Servers

When setting up multiple network paths and multiple backup servers you may decide to use them alternately instead of in parallel. If the number of available sessions to the various servers as defined in the profile exceeds the maximum number of sessions allowed Data Protection for SAP will use the first sessions it can establish, up to the number defined for keyword MAX_SESSIONS (see on page 118). This will allow backing up data even when some TSM resources, for example a TSM server or a network interface of a TSM server, are unavailable. Obviously, the server(s) used for the backup must be available for restoring the data. You may also control on what days of the week a specific server is to be used (see keyword USE_AT on page 122).
Modifying the Handling of the TSM Password

TSM provides the following choices for password handling: v No password v Manual password handling v Automatic password handling Consider the choices with their implications: No password required No authentication is performed on the TSM server level. Each user connected to the backup server can access Tivoli Storage Manager data without a password. This method is only recommended if adequate security measures can be established otherwise, for example, if Tivoli Storage Manager is only used for SAP and no other clients are registered, and the respective authentication and authorization is performed on the operating system level. Manual password handling For each connection to the TSM server, a password is required. Data Protection for SAP supports manual password handling by storing the encrypted password in its configuration files. As long as the password does not expire and is not changed on the TSM server, Data Protection for SAP automatically uses the stored password when connecting to TSM. Whenever the password expires or is changed in TSM the new password must be set again manually with the command |
backom -c password [-x]
(See Password Command (Verify and Save TSM Password) on page 56). This method provides password security and can be set up easily; however, you need to synchronize password updates in Tivoli Storage Manager (command update node on TSM server) and Data Protection for SAP (command backom -c password). These steps must also be repeated whenever the TSM password expires. Therefore, this method is only recommended during installation and testing, together with a sufficiently long password expiration period; it is not recommended for production operation.
43

If setting the password is to be automated, such as in a script, the option exists to enter this information in the command line: | |
backom -p <full path>/init<SID>.utl -c password serverA:nodeA:passwordA serverB:nodeB:passwordB [-x]
where 'passwordA' is the password for TSM node 'nodeA' on TSM server 'serverA'. Notes: 1. The interactive password prompt is omitted only if the passwords for all server stanzas in the.utl file are specified. 2. There is a potential security risk involved in recording TSM passwords in a script. Automatic password handling For each connection to the TSM server, a password is required. However, after the first connection, the TSM password is managed by Tivoli Storage Manager. The Tivoli Storage Manager client stores the current password locally. When the password expires, the password will be changed and stored automatically. If you schedule your backups or restores from a system user different from the database owner, you need to grant access permissions to your data files on disk for this user. You need to specify the TSM password currently in effect before you start using Data Protection for SAP in order to connect to the server for the first time and whenever the password is changed manually on the TSM server (command update node). You do this with the command |
backom -c password [-x]
(See Password Command (Verify and Save TSM Password) on page 56). This method is recommended for an automated production environment. For details on how to set up any of the password handling methods, refer to Password Handling on page 210.
Backup Version Control

Data Protection for SAP allows you to define the number of backup versions you want to keep in backup storage. Every time a full backup completes successfully, the version count is incremented. Subsequent partial, incremental, delta, and log file backups get the same version number, thus ensuring that the full backup required for restoring them is still kept. After each successful full backup, the number of full backups available in backup storage is checked. If the number of backups to be kept is exceeded, the oldest backup and all corresponding partial, incremental, delta, and log file backups are removed from backup storage. For a partitioned database, backup version control is done on a partition basis. Therefore, make sure that full backups are initiated at the same time for all partitions. If you plan to use this feature, do not employ TSM file expiration at the same time. For details, refer to keyword MAX_VERSIONS on page 118.
44
Rules for Adjustments in the DP for SAP Environment

The data moving functions of Data Protection for SAP are implemented in a shared library accessed by DB2 whenever a backup or restore command is issued. The shared library requires information on the path of the Data Protection for SAP profile and the path of the log files written by Data Protection for SAP. If an action is initiated via the DB2 commands BACKUP DATABASE or RESTORE DATABASE the information required must be specified in a vendor environment file. The name of the vendor environment file is passed to DB2 via the OPTIONS parameter of the BACKUP DATABASE or RESTORE DATABASE commands. | | | Note: Starting with DB2 V8.2, the vendor environment file can be specified in the VENDOROPT database configuration parameter. In this case, use of the OPTIONS keyword for this purpose is no longer necessary. For an example of a vendor environment file for Data Protection for SAP, refer to Appendix H, Data Protection for SAP Setup Examples, on page 193. If an action is initiated via the SAP-DB2 Administration Tools BRARCHIVE or BRRESTORE or via backom the information required must be specified in the environment. It is strongly recommended to keep the information in the vendor environment file and in the system variables in sync at all times. Other rules: v In order to select a different set of DP for SAP environment settings for a DB2 backup or restore, you specify the full path of the vendor environment file in the OPTIONS parameter of the BACKUP DATABASE or RESTORE DATABASE commands. For details, refer to DB2 Command Reference. v In order to select a different DP for SAP profile, modify environment variable XINT_PROFILE to denote the new profile in the vendor environment file v In order to select a different DP for SAP profile for future calls to SAP-DB2 Administration Tools BRARCHIVE or BRRESTORE or to backom, modify environment variable XINT_PROFILE to denote the new profile. v In order to select a different DP for SAP profile for a call to backom, specify the path of the new profile in option e of the backom command. For details, see Chapter 6, Data Protection for SAP Backup Object Manager, on page 53. v In order to change the path for DP for SAP process log files for a call to DB2 commands BACKUP DATABASE or RESTORE DATABASE, modify environment variable TDP_DIR in the vendor environment file and specify the files path in the OPTIONS parameter of the BACKUP DATABASE or RESTORE DATABASE commands. v In order to change the path for DP for SAP process log files for future calls to SAP-DB2 Administration Tools BRARCHIVE or BRRESTORE or to backom, modify environment variable TDP_DIR to denote the new profile. | | | | | |
Using the VENDOROPT Parameter

The following applies if the SAP database is DB2 version 8.2 (8.1 FP7) or higher. In order to select a default set of Data Protection for SAP environment settings for DB2 commands BACKUP DATABASE, RESTORE DATABASE and for the DB2 Log Manager, modify the DB2 database configuration to denote a file containing the settings:
45

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
db2 update db cfg for <SID> using VENDOROPT <vendor environment file>
where <vendor environment file> is the fully qualified path of the file containing Data Protection for SAP environment settings for DB2. Make sure that the environment settings of your system match the settings in this file. This command can be used as an alternative to the db2set command. Its advantages are: v There is no need to restart the DB2 instance. v You can define default values for the OPTIONS parameter of the BACKUP DATABASE and RESTORE DATABASE commands in the DB2 configuration, thus making the OPTIONS parameter of these commands optional. (You can still override the default setting of the database configuration by specifying the OPTIONS parameter.) v The same settings apply to database backup/restore and to log file archive/retrieve. Note: When using the BACKUP DATABASE and RESTORE DATABASE commands with the USE SNAPSHOT option for snapshot-based backup and restore by DB2 ACS or TSM for ACS, the VENDOROPT parameter is currently not examined. In this case, any options other than the default values must be set using the OPTIONS keyword.
Setting Up DB2 to Use the Built-In Log Manager with DP for SAP
To activate log archiving/retrieving with the DB2 Log Manager facility included with DB2 version 8.2, the database configuration of the SAP database has to be adapted. This is offered as an installation option. The following database configuration parameters were introduced in DB2 V8.2:
Table 2. Database Configuration Parameters Introduced with DB2 V8.2 Parameter LOGARCHMETH1 Description Media type of the primary destination for archived log files Default Off
LOGARCHOPT1
Options field for the primary NULL destination for archived log files (if required). Media type of the secondary destination for archived log files. If this path is specified, log files will be archived to both this destination and the destination specified by LOGARCHMETH1. Options field for the secondary destination for archived log files (if required). Off
LOGARCHMETH2
LOGARCHOPT2
NULL
46

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Table 2. Database Configuration Parameters Introduced with DB2 V8.2 (continued) Parameter FAILARCHPATH Description Default
If DB2 is unable to archive NULL log files to both the primary and secondary (if set) archive destinations due to a media problem, then DB2 will try to archive log files to this path. This path must be a disk. Number of retries to archive 5 a log file to the primary or secondary archive destination before trying to archive log files to a failover directory. This is only used if FAILARCHPATH is set. If NUMARCHRETRY is not set, DB2 will continuously retry archiving to the primary or secondary log archive destination. Number of seconds to wait 2 after a failed archive attempt before trying to archive the log file again. Subsequent retries will only take affect if NUMARCHRETRY is at least set to 1. For DP for SAP, specification NULL of a file containing additional parameters that DB2 may need to use to communicate with (vendor) storage systems during backup, restore, archive or retrieve operations. These options are then made available as environment variables.
NUMARCHRETRY
ARCHRETRYDELAY
VENDOROPT
Thus, at least the following two changes to the database configuration are necessary to use the DB2 Log Manager in combination with Data Protection for SAP. 1. Update one of the LOGARCHMETH database configuration parameters (In this example LOGARCHMETH1 will be used - but of course, LOGARCHMETH2 can be used as well) v for UNIX and Linux:
db2 update db cfg for <SID> using LOGARCHMETH1 VENDOR:/<path>/libtdpdb2.a
v for Windows:
db2 update db cfg for <SID> using LOGARCHMETH1 VENDOR:<drive>:\<path>\tdpdb2.dll
2. Update the Data Protection for SAP environment A file containing the environment settings has to be made known to DB2 to enable DB2 to provide this environment for archive or retrieve requests to Data Protection for SAP. This file is an additional requirement.
47

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following example shows the setup needed by DP for SAP for LOGARCHMETH1: v for UNIX and Linux:
db2 update db cfg for <SID> using LOGARCHOPT1 /<path>/vendor.env
v for Windows:
db2 update db cfg for <SID> using LOGARCHOPT1 <drive>:\<path>\vendor.env
When updating the LOGARCHMETH database configuration parameters, the change will take effect on the next log file to be archived. The former database configuration parameters USEREXIT and LOGRETAIN will be integrated into the LOGARCHMETH configuration parameters. During migration to DB2 version 8.2 (or when updating to DB2 version 8.1 FP7, which corresponds to DB2 version 8.2), LOGARCHMETH1 will be set to USEREXIT if the database is using that parameter. All of the other database configuration parameters will be defined with their default values. This means that the old Userexit executable provided with the SAP-DB2 Administration Tools package should still be available to the database until the database administrator decides to change these settings.
Note The database configuration parameters LOGRETAIN and USEREXIT will still be available in DB2 version 8.2, but will be mapped to LOGARCHMETH1.
Note Remember to set up the number of TSM sessions used by DP for SAP properly. Typically, during online database backups log archives will be initiated. Thus, configure DP for SAP in such a way that at least one TSM session, one for the database backup and one for the log archives, is available for each of these operations. When DP for SAP is installed for DB2 V8.2 or higher, the program offers the option of establishing these parameters at that time For a further description of the DB2 Log Manager and its operation in detail, refer to the DB2 Administration Guide.
Adjustments for High Availability Considerations for Using IBM HACMP for AIX
This section is intended to give a short introduction to the way DP for SAP works internally, thus enabling the user to take actions for HACMP fail-over configurations. As an example, we use the following configuration, which should be easily adaptable to others. Here, we use the mutual takeover configuration, where each node can take over the other. If the application server and database server are installed on different hosts, the described actions need to be taken on the database servers only.
48

The following figure illustrates the takeover environment:
Figure 15. Sample Environment for HACMP Takeover
DP for SAP Internals

Files: v The installation directory is /usr/tivoli/tsm/tdp_r3. v Lock files can be found in /var/tdp_r3. v There is only one ProLE running on each host (even after takeover). v Each SAP system has its own Data Protection for SAP configuration files (init<SID>.utl, init<SID>.bki) . These files are located in a directory specified during the installation process. Dependencies: v Both hosts should have the same level of Tivoli Storage Manager API installed. v Both hosts must be Data Protection for SAP. v On both hosts, the dsm.sys file (in /usr/Tivoli/tsm/client/api/bin/dsm.sys) must contain all server names required for takeover. Communication: The Data Protection for SAP dynamic library connects to prole using the following procedure: v Get the IP address for localhost (should be 127.0.0.1 for IPv4). v Get the tdpr3db2 or tdpr3db264 service (should be 57322 for the 32-bit version and 57324 for the 64-bit version). v Connect to 127.0.0.1: <tdpr3db2 or tdpr3db264 service>.
Installation and Setup

Installation: A prerequisite for installation is a correct setup of the TSM client. The installation steps for the TSM Backup/Archive Client for AIX can be found in the documentation Tivoli Storage Manager Installing the Clients. Defining DP for SAP as an HACMP Application: To enable DP for SAP to participate in HACMP failover processing, it must be defined as an application to
49

HACMP. Detailed directions for doing this can be found in the HACMP for AIX Installation Guide, SC23-4278. A summary follows. To configure an application for HACMP: 1. Enter the following to start HACMP for AIX system management:
smit hacmp
2. Select Cluster Configuration > Cluster Resources > Define Application Servers > Add an Application Server. 3. Enter field values as follows: Server Name Enter an ASCII text string that identifies the server (for example, tdpclientgrpA). You use this name to refer to the application server when you define it as a resource during node configuration. The server name can include alphabetic and numeric characters and underscores. Do not use more than 31 characters. Stop Script Enter the full pathname of the script that stops the server (for example, /usr/sbin/cluster/events/utils/stop_tdpr3.sh). This script is called by the cluster event scripts. This script must be in the same location on each cluster node that might stop the server. 4. Press Enter to add this information to the HACMP for AIX ODM. 5. Press F10 after the command completes to leave SMIT and return to the command line. Sample client start and stop scripts are provided later in this chapter. Refer also to the HACMP for AIX Planning Guide V4.4, SC23-4277, for further information about selecting the HACMP node topology and takeover relationships. Note that DP for SAP must be in a resource group having a cascading or rotating takeover relationship. It does not support a concurrent access resource group.
Adding the DP for SAP Application to an HACMP Resource Group

A final step in enabling Data Protection for SAP for HACMP failover is to define it to a cluster resource group. Detailed directions for doing this can be found in the HACMP for AIX Installation Guide. A summary follows. To define the resources that will be part of a resource group: 1. From the Cluster Resources SMIT screen, select the Change/Show Resources/Attributes for a Resource Group option and press Enter. SMIT displays a picklist of defined resource groups. 2. Pick the desired resource group. 3. Press Enter and SMIT displays the Configure a Resource Group screen. 4. Enter values that define all the resources you want to add to this resource group. 5. After entering field values, synchronize cluster resources. 6. Press F10 to exit SMIT or F3 to return to previous SMIT screens to perform other configuration tasks or synchronize the changes you just made. To synchronize the cluster definition, go to the Cluster Resources SMIT screen and select the Synchronize Cluster Resources option.
50

The TSM client application should be added to the same resource group that contains the file systems it will back up. The file systems defined in the resource group should also be the ones specified in the domain for this client instance in the client user options file. Note that both JFS and NFS file systems can be defined as cluster resources, although NFS supports only 2 node clusters in a cascading takeover relationship.
51
Sample Stop Script

Depending on the customer installation, the sample stop script may need to ensure that any backup/restore operation currently in progress is stopped. This means that any processes launched by brbackup/brarchive for this client instance (that may be accessing the shared file system(s)) must also be stopped to free resources like file systems. This may have already been accomplished by the HACMP script that stops the SAP systems. It may also not be desirable in certain installations and should be revised. The stop script is used in the following situations: v HACMP is stopped. v A failover occurs due to a failure of one component of the resource groups. The other members are stopped so that the entire group can be restarted on the target node in the failover. v A fallback occurs and the resource group is stopped on the node currently hosting it to allow transfer back to the node re-entering the cluster. The stop script will be called by HACMP as the root user. Note: This script is not in its final form. It should be considered pseudo code that indicates the functions it will perform.
#!/bin/ksh # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # This sample script is provided for use with DP for SAP in an HACMP # # environment # # It should be reviewed and customized to meet your specific environment # # # # # # Name: stop_tdpr3.sh # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # if ["$VERBOSE_LOGGING"="high"] then set -x fi
# Function to update all disk information for DP for SAP STOP_BACKUP() { # You may want to cancel all backups currently running # Note that this will generate errors in the current backup logs and it will also cancel the # connection to the Admin Assistant. # *** Note that if you are using Data Protecion for Snapshot Devices for SAP, # this may leave your FlashCopy device in an # inconsistent state. # kill 9 `cat /var/tdp_r3/prole.pid`
# This stops any running backup or archive process. STOP_BACKUP Exit 0
52
Chapter 6. Data Protection for SAP Backup Object Manager

This chapter introduces the Data Protection for SAP Backup Object Manager. Backup objects, such as database or tablespace backups and DB2 log files, can be managed with the DP for SAP Backup Object Manager. This utility allows you to v verify and store a TSM password, v find backup objects in TSM, v check the properties of the backup objects in TSM, v remove any backup object from TSM, v backup database and selected tablespaces, v restore database and tablespace backups to the corresponding database, v retrieve files from TSM and restore them to the file system. v do a redirected restore of databases (cloning) The Backup Object Manager is designed to handle DB2 log files archived with Data Protection for SAP and the SAP tool BRARCHIVE as well as those archived with Data Protection for SAP and the DB2 Log Manager provided with DB2 version 8.2. No special customization or setup is necessary. Because a log chain concept was introduced with the DB2 Log Manager, all log files archived on TSM with Data Protection for SAP will be associated to one of these chains by the Backup Object Manager. The SAP-DB2 Administration Tools BRARCHIVE and BRRESTORE do not support the log chain concept. Therefore, log files archived with BRARCHIVE and Data Protection for SAP will be associated with a default, here the first log chain, which is 0 or C0000000. However, log files archived with the DB2 Log Manager and Data Protection for SAP will be associated with the appropriate log chain number and handled by the Backup Object Manager accordingly. For further detailed descriptions concerning the DB2 Log Manager and the log chain concept refer to the Administration Guide in your DB2 documentation.
53
Data Protection for SAP Backup Object Manager

The following graphic shows how the Backup Object Manager interacts with the Tivoli Storage Manager and the SAP database Server:
Figure 16. Data Protection for SAP Backup Object Manager
The Backup Object Manager works with different kinds of data objects, that is, database backups, DB2 log files, and raw files that may comprise any files of the file system. The tasks that can be performed with the Backup Object Manager are processed in different ways: v Requests to verify the TSM password are passed directly to TSM. v Requests to display or delete any data are answered by accessing the TSM server directly, thus working with the data actually available on TSM. v Requests to restore DB2 log files and raw files are also processed via the TSM client. v Requests to backup or restore any DB2 database data are routed to the DB2 agent. The DB2 agent employs the DP for SAP shared library.
Backup Object Manager Setup

The Backup Object Manager can be used as soon as DP for SAP is installed and set up. No additional installation and setup steps are required, because the Backup Object Manager utilizes the settings in the DP for SAP profile and configuration file (see Appendix A, The Data Protection for SAP Profile, on page 115) and the settings of the environment variables XINT_PROFILE, TDP_DIR, and DB2_VENDOR_LIB (refer to Installing Data Protection for SAP on page 24).
54
Managing Backup Objects

The syntax of the Backup Object Manager is as follows: backom [ -? ] displays the syntax help. | Note: For the C shell, enclose the option string in quotes (backom '-?'). backom -h [password|query|backup|restore|delete] displays the command online help.
backom -c command [ command option ...]
where command is one of: for for for for Password: password Query: q_all | q_db | q_ts | q_log | q_tdi | q_raw Backup: b_db Restore: r_db | r_ts | r_log | r_hfile | r_rawr_tdi | rr_db_interactive | rr_db_batch rr_db_clone for Delete: d_db | d_ts | d_log | d_raw where command option is one of:
-i -a -n -u -p -t -l -k -f -d -e -b -s -N -S -B -P -D -T -R -O -L -C -x -v -m <instance> <alias name> <node number> <userid> <password> <timestamp | timerange> <log number | log number range> <log chain | log chain range> <file name> <destination directory> <execution profile> <buffer size> <scaling factor> <sessions> <number of buffers> <parallelism> <target database> <tablespace> full | incremental | delta
<output mode>
Backup Object Manager Commands

There are different types of Backup Object Manager commands: v Password command v Query commands v Backup command v Restore commands v Delete commands
55

The commands and their syntax are described in detail in the following section. Optional command options are listed in brackets [ ], parameter descriptions, that must be replaced, are listed in angle brackets < > .
Password Command (Verify and Save TSM Password)

The password command connects to the backup server, prompts for a new password, and verifies the password entered with the backup server. If the verification is successful the new password is encrypted and stored in the Data Protection for SAP configuration file. Successful password verification requires that the password entered must be the active password for the corresponding node on the TSM server. For information when to use the password command, please refer to Modifying the Handling of the TSM Password on page 43. v Verify and save a TSM password: backom -c password [-x] [-a <DB2 alias name>] [-n <DB2 node number>] [-e <execution profile>]
| | |
Query Commands (List Backup Objects)

The query commands list backup objects that were sent to TSM by DP for SAP. The objects to be displayed can be filtered by using appropriate command options (see also Backup Object Manager Command Options on page 58). v List all backup objects related to DB2 (database or tablespace backups and DB2 log file backups): backom -c q_all [-i <instance>] [-a <database alias>] [-n <node number>] [-t <timestamp | time range>] [-l <log number | log number range>] [-e <execution profile>] [-m <output mode>] [-v] v List database backups: backom -c q_db [-i <instance>] [-a <database alias>] [-n <node number>] [-t <timestamp | time range>] [-e <execution profile>] [-m <output mode>] [-v] v List tablespace backups: backom -c q_ts [-i <instance>] [-a <database alias>] [-n <node number>] [-t <timestamp | time range>] [-e <execution profile>] [-m <output mode>] [-v] v List tablespace definition information (TDI) images related to a full DB2 database backup: backom -c q_tdi -a <database alias> -t <timestamp [-i <instance>] [-n <node number>] [-e <execution profile>] [-m <output mode>] [-v] v List DB2 log file backups: backom -c q_log [-a <database alias>] [-n <node number>] [-t <timestamp | time range>] [-l <log number | log number range>] [-e <execution profile>] [-m <output mode>] [-v] v List backup objects available on TSM (database or tablespace backups, DB2 log file backups, and file backups): backom -c q_raw [-f <file name>] [-e <execution profile>] [-m <output mode>] [-v]
Backup Command (Backup Database Data)

With the Backup Object Manager backup command, you can backup a complete database or selected tablespaces of a database. (For a detailed description of the command options, refer to Backup Object Manager Command Options on page 58.) v Backup the database data denoted by the command options: backom -c b_db -a <database alias [-T <tablespace list>]
56

[-R <backup type>][-i <instance>] [-n <node number>] [-u <userid>] [-p <password>] [-b <buffer size>][-B <number of buffers] [-S <sessions>] [-P <parallelism>] [-e <execution profile>] [-O] [-L] [-v]
Restore Commands (Restore Backup Objects)

With the Backup Object Manager restore commands, you can restore any backup object that was created by DP for SAP. (For a detailed description of the command options, refer to Backup Object Manager Command Options on page 58.) v Restore the database denoted by the command options: backom -c r_db -a <database alias> [-n <node number>] [-u <userid>] [-p <password>] [-t <timestamp>] [-b <buffer size>] [-B <number of buffers>] [-S <sessions>] [-P <parallelism>] [-R <restore type>] [-O] [-e <execution profile>] [-x] [-v] v Restore the database denoted by the command options to a different location (redirected restore) in automatic mode: backom -c rr_db_clone -a <original database alias>,<target database alias> [-i <instance>] [-n <node number] [-u <userid>] [-p <password>] [-t <timestamp>] [-b <buffer size>] [-B <number of buffers>] [-S <sessions>] [-P <parallelism>][-D <target database directory>] [-e <execution profile>] [-s <scaling factor>] [-N] [-C] [-v] For a detailed discussion of the redirected restore function read Chapter 7, DB2 Redirected Restore Using Backup Object Manager, on page 63. v Restore the database denoted by the command options to a different location (redirected restore) in batch mode: backom -c rr_db_batch -a <original database alias>,<target database alias> -f <TDI image> [-i <instance>] [-n <node number>] [-u <userid>] [-p <password>] [-t <timestamp>][-b <buffer size>] [-B <number of buffers>] [-S <sessions>] [-P <parallelism>] [-D <target database directory>][-e <execution profile>] [-s <scaling factor>] [-N][-C] [-v] For a detailed discussion of the redirected restore function read Chapter 7, DB2 Redirected Restore Using Backup Object Manager, on page 63. v Restore the database denoted by the command options to a different location (redirected restore) in interactive mode: backom -c rr_db_interactive -a <original database alias>,<target database alias> [-i <instance>] [-n <node number>] [-u <userid>] [-p <password ] [-t <timestamp>] [-f <modified TDI image] [-b <buffer size>] [-B <number of buffers>] [-S <sessions>][-P <parallelism>] [-D <target database] [-e <execution profile>] [-s <scaling factor>] [-N][-C] [-v] For a detailed discussion of the redirected restore function read Chapter 7, DB2 Redirected Restore Using Backup Object Manager, on page 63. v Restore the tablespaces denoted by the command options: backom -c r_ts -a <database alias> [-n <node number>] [-u <userid>] [-p <password>] [ -t <timestamp>] [-b <buffer size>] [-B <number of buffers>] [-S <sessions>] [-P <parallelism>] [-R <restore type ] [-O] [-e <execution profile>] [-x] [-v] v Restore the DB2 Recovery History File of the database denoted by the command options: backom -c r_hfile -a <database alias> [-n <node number>] [-t <timestamp>] [-u <userid>] [-p <password>] [-b <buffer size>] [-B <number of buffers>] [-S <sessions>] [-P <parallelism>] [-e <execution profile>] [-x] [-v]
57

v Restore the tablespace definition information (TDI) denoted by the command options: backom -c r_tdi -t <timestamp> -a <database alias> [-d <destination directory>] [-e <execution profile>] [-x] [-v] v Retrieve the DB2 log files denoted by the command options: backom -c r_log -a <database alias> -l <log number|log number range> -d <destination directory> [-n <node number>] [-t <timestamp|time range>] [-e <execution profile>] [-x] [-v] v Retrieve the file(s) specified by command option -f to the path specified by command option -d: backom -c r_raw -f <file name> -d <destination directory> [-e <execution profile>] [-x] [-v]
Delete Commands (Remove Backup Objects from TSM)

The Backup Object Manager delete commands remove backup objects from TSM that were sent to TSM by DP for SAP. (For a detailed description of the command options, refer to Backup Object Manager Command Options.) v Delete the database backup(s) specified by the command options from TSM: backom -c d_db -a <database alias> -t <timestamp | time range> [-i <instance>] [-n <node number>] [-e <execution profile>] [-x] [-v] v Delete the tablespace backup(s) specified by the command options from TSM: backom -c d_ts -a <database alias> -t <timestamp|time range> [-i <instance>] [-n <node number>] [-e <execution profile>] [-x] [-v] v Delete the DB2 log file backup(s) specified by the command options from TSM: backom -c d_log -a <database alias> -l <log number|log number range> [-n <node number>] [-t <timestamp|time range>] [-e <execution profile>] [-x] [-v] v Delete the file(s) specified by command option -f from TSM: backom -c d_raw -f <file name> [ -e <execution profile>] [-x] [-v]
Backup Object Manager Command Options

The following options may be specified together with Backup Object Manager commands: v -a <database alias> or -a <original database alias>,<target database alias>. Denotes the name of the database an operation is requested for. In the case of a redirected restore to a different database or of database cloning, the database aliases of both the original and the target databases must be specified, separated by a comma. When a redirected restore is requested specifying a single database alias, the database is restored to the original database. v -b <buffer size> Denotes the size of DB2 backup or restore buffers, in 4 KB allocation units (pages). The minimum is 8 units. The buffer size is limited by the memory available. v -B <number of buffers> Denotes the number of DB2 buffers to be used for backup or restore. The minimum number is 2. The number of buffers is limited by the memory available. v -C If specified for a redirected restore, indicates that Backup Object Manager should only run a test of the setup, but not start copying data. v -d <destination directory> Denotes the destination path for restoring a file to the file system.
58

v -D <target database directory> For a redirected restore, denotes the fully qualified name of the target database directory. This command option is ignored, if the database alias of the target database is the same as the database alias of the original database. v -e <execution profile> Denotes the complete path of the DP for SAP profile to be used with the Backup Object Manager. Overrides the profile name set in environment variable XINT_PROFILE. v -f <file name> Denotes the name of a file in the file system. Unless the file denotes a TDI image, the following wild card characters are accepted: ? denotes any single character * denotes any number of any characters. v -i <DB2 instance> Used in query commands to limit the database or tablespace data to be displayed to a specific DB2 instance. With all other commands, this command option is used to override the DB2 instance name defined in environment variable DB_INSTANCE. v -k <log chain | log chain range> where <log chain range> = <chain1> - <chain2>. Denotes the log chain number(s) of DB2 log file(s). This command option is only of importance for log files archived with DB2 version 8.2 and higher. DB2 log chains can be specified either in the format Cnnnnnnn, where nnnnnnn is a string of 7 decimal digits or in the format mmmmmmm, where mmmmmmm is a string of up to 7 decimal digits denoting the log chain number. v -l <log number | log number range> where <log number range> = <log number 1> - <log number 2> Denotes the log serial number(s) of DB2 log file(s). DB2 log numbers can be specified either in the format Snnnnnnn.log (DB2 log file name), where nnnnnnn is a string of 7 decimal digits, or in the format mmmmmmm, where mmmmmmm is a string of up to 7 decimal digits denoting the log serial number. v -L If specified for a database backup, the DB2 log files are saved to TSM together with the database backup. This option requires DB2 v8.2 or above. v -m <output mode> where <output mode> = short | normal | detailed Denotes the detail of information requested with a query command. The default is short for information related to DB2 log files, normal for all other kinds of information. If you need to override the default values generally, you may set environment variables FULL_OUTPUT (for information on database backups), TABLESPACE_OUTPUT (for information on tablespace backups) and LOG_OUTPUT (for information on DB2 log file backups) to the values desired. v -N If specified, this command option causes all containers of a tablespace to be allocated with the same size during a redirected restore. v -n <node number> Denotes the DB2 node number. For the password command in a DB2 partitioned environment: If for only one DB2 node/partition the password has to be set/changed, specify the command option -n <node number>.
59

If the node/partition number is not specified, the new password is saved to all available node/partitioned based Data Protection for SAP configuration files. For all other commands: If the node number is not specified, node NODE0000 is assumed. v -O If specified when requesting a backup or tablespace restore operation, an online backup or an online tablespace restore is performed. v -p <password> The password of the user ID specified in option -u. v -P <parallelism> Denotes the degree of parallelism within DB2, i.e. the number of buffer manipulator processes reading from or writing to tablespaces at the same time. The minimum parallelism is 1, the maximum is 1024. v -R <backup type> where <backup type> = full | incremental | delta . Denotes the type of backup requested. If no backup type is specified a full backup is performed. v -S <sessions> Denotes the number of I/O sessions that are to be started by DB2. The value of this command option must be less than or equal to the value of the keyword MAX_SESSIONS in the Data Protection for SAP profile. v -s <scaling factor> Denotes the positive floating point factor to be used for resizing all containers of a tablespace during redirected restore. The default is 1, indicating that the new tablespace is exactly the size of the original. v -t <timestamp | time range> where time range = <timestamp1>-<timestamp2> Denotes the time when a backup object was created. For database and tablespace backups, this timestamp matches the timestamp listed in the DB2 Recovery History File. It consists of 14 decimal digits and has the format: yyyymmddhhmmss where yyyy is the year mm is the month of the year, 01 through 12 dd is the day of the month, 01 through 31 hh is the hour of the day, 00 through 23 mm is the minute of the hour, 00 through 59 ss is the second of the minute, 00 through 59. For restore commands, an exact timestamp must be given. For query and delete commands, a time range can be specified, or the timestamp might contain wild card characters. The following wild card characters are accepted: ? denotes any single digit * denotes any number of any digits. If a timestamp is not specified for a query, the result will contain all eligible backup object available on the TSM server. If a timestamp is not specified for a restore, the newest object is retrieved from TSM. v -T <tablespace list> where <tablespace list> = <tablespace>[,<tablespace list>] For a backup request, denotes the names of the tablespace(s) to be backed up. Tablespace names are separated by commas. If there is no tablespace list specified, a full database backup is performed. v -u <userid> Denotes the DB2 user ID used for restoring a DB2 database, tablespace, or recovery history file if it is different from the current login user ID.
60

v -v If set, all log messages will also be displayed on STDOUT. v -x If specified, this option suppresses all confirmation requests. Otherwise, confirmation requests will be issued for restore commands that would overwrite existing data, and for delete requests. In conjunction with the "-c password" option, -x causes the password to be changed on all database partitions.
| |
Examples
The following list contains examples of certain tasks and shows which commands can be used to perform them: v To verify and save a TSM password
backom -c password
v To create a list of all available backup objects sent to TSM by DP for SAP:
backom -c q_all
v To create a list of all DB2 log files for database SAMPLE with a log number greater than 123 and created in November 2002, with normal output detail level:
backom -c q_log -a SAMPLE -l 124-9999999 -t 200211* -m normal backom -c q_log -a SAMPLE -l S0000124.log-S9999999.log -t 200211* -m normal
v To create a list of DB2 log files for log chains 5 to 15 for database SAMPLE with log numbers from 98 to 180 archived between 4 p.m. and 8.30 p.m.:
backom -c q_log -a SAMPLE -k C0000005-C0000015 -l 98-180 -t ????????16*-????????2030*
v To create a list of all tablespace backups for partition NODE0001 of database SAMPLE that were created in November 2002 between 4 p.m. and 5 p.m.:
backom -c q_ts -a SAMPLE -n NODE0001 -t 200211??16*
v To backup online database SAMPLE using 2 I/O sessions and 4 backup buffers:
backom -c b_db -a SAMPLE -S 2 -B 4 -O
v To backup the tablespaces SYSCATSPACE and USERSPACE1 of database SAMPLE using the execution profile initSAMPLE.utl located at /db2/SAMPLE/config:
backom -c b_db -a SAMPLE -T SYSCATSPACE,USERSPACE1 -e /db2/SAMPLE/config/initSAMPLE.utl
v To restore a tablespace of database SAMPLE with the tablespace backup created on November 27, 2002, at 6:32:15 p.m.:
backom -c r_ts -a SAMPLE -t 20021127183215
v To restore database SAMPLE with the latest backup:

backom -c r_db -a SAMPLE
61

v To delete all DB2 log files for database SAMPLE that were created before June 2002:
backom -c d_log -a SAMPLE -t 1900*-20020601000000
v To delete all versions of files containing tmp in their path or file names that were sent to TSM by DP for SAP:
backom -c d_raw -f *tmp*
62
Chapter 7. DB2 Redirected Restore Using Backup Object Manager

Backup Object Manager provides redirected restore functionality based on the redirected restore facility of DB2. With redirected restore, an administrator can v restore a DB2 database to a different location v change the physical database layout of a restored database, including the location of tablespace containers, the number of tablespace containers, their names, and their sizes, v clone a database, changing both the name and the location of the database. With Backup Object Manager, a redirected restore of a database can be performed nearly automatically using a simple set of commands. BackOM also performs some plausibility checks before actually starting the operation.
Figure 17. Redirected Restore Overview
The following modes of redirected restore are provided by Backup Object Manager: v automatic: Restore a database to a different name and location while keeping the general database layout. (However, scaling and normalizing of tablespace containers may be requested with an automatic redirected restore.) v batch: Restore a database to a different location and database layout defined in a configuration file. v interactive: Restore a database to a location and database layout specified by the administrator in a dialog. In all modes, Backup Object Manager can perform some additional automated adaptations to tablespaces, for example tablespace scaling to provide tablespaces with appropriate free space, and tablespace normalizing to optimize the parallel I/O performance of the restored database.
63
DB2 Redirected Restore Using Backup Object Manager
Tablespace Definition Information

In order to perform a redirected restore, Backup Object Manager needs some information about the physical layout of the original database, i.e. the tablespace containers used by the original database. In particular, the size of database managed containers (DMS) must be available in order to create new tablespace containers with sufficient space. Therefore, Backup Object Manager keeps information on all tablespaces of a database backed up for every backup image on TSM. For each tablespace, the following information is collected: v The ID and name of the tablespace v The type of the tablespace, i. e. whether it is system (SMS) or database managed (DMS) v The page size in bytes v The extent size in pages v The number of used pages v The tablespace containers used for the tablespace: The ID of the tablespace container The name of the tablespace container, i.e. the directory containing an SMS container or the file containing a DMS container, respectively The type of the tablespace container, i.e. whether a database managed container is stored in a file or in a raw device For DMS tablespaces, the total number of pages stored in the container. This information on the physical database layout, the Tablespace Definition Information (TDI), is stored in addition to the productive data. The TDI is prerequisite to redirected restore operations with Backup Object Manager. A TDI image is connected to its corresponding DB2 backup by the combination of DB2 instance name, database alias, database node number, and the timestamp of the backup. For easy correlation, the name of the TDI image is constructed in the following way:
<DB2 instance>-<DB2 alias>-<DB2 node number>-<timestamp>.tdf
The TDI is stored in ASCII format in order to allow the administrator to read and edit the file because the information may be valuable for some administrative tasks. For example, the number of used pages can help the administrator to request correct sizes when resizing containers. For details, see Automated Tablespace Adaptations on page 72. Backup Object Manager also calculates the number of total pages and used pages from the data stored for each tablespace container. Editing may be necessary when requesting a redirected restore in batch mode, as described in Redirected Restore in Batch Mode on page 68. A sample TDI file can be found in Appendix G, Tablespace Definition Information (TDI), on page 189.
64
Creating Tablespace Definition Information

A TDI image can be created after a full database backup completed successfully. It is stored on the TSM server, together with the database backup image.
Note Only database backups for which corresponding TDI is available can be used for redirected restore with Backup Object Manager. In order to create TDI for the backup image with an offline database backup, the backup function of the Backup Object Manager must be employed. For example, the following command starts an offline database backup using two sessions:
backom -c b_db -a <database alias> -S 2
When requesting an offline database backup via the DB2 command line interface (CLI), TDI is not created. There are two ways of creating TDI for the backup image with an online database backup: 1. Use the Backup Object Manager backup function. For example, the following command starts an online database backup using two sessions:
backom -c b_db -a <database alias> -S 2 -O
2. When starting an online backup via the DB2 command line interface (CLI), the additional parameter BACKOM_LOCATION must be set in the vendor environment file. If the value of this parameter points to the backom executable the TDI is stored on the TSM server after the backup completed successfully. The following statement must be included in the DB2 vendor environment file: BACKOM_LOCATION=<fully qualified path and name of the backom executable> Now, the known DB2 backup command can be issued via CLI:
db2 backup db <database alias> online load <shared library> open 2 sessions
To check whether a TDI image is available for a Data Protection for SAP backup image, the Backup Object Manager query function can be employed.
Redirected Restore
Backup Object Manager provides different modes of redirected restore, each tailored for a different administrative scenario. These redirected restore modes are explained below.
Redirected Restore Prerequisites

The following characteristics of a database are prerequisite to all flavors of the Backup Object Manager redirected restore function: v A TDI image must be available for the backup to be restored v The database must not have a tablespace container that is a raw device v DMS tablespace containers of the original system are located at:
65

UNIX or Linux: /db2/<SAPSID>/sapdata<n> Windows: <drive>:\db2\<SAPSID>\sapdata<n> where <n> is an integer v <SAPSID> must be the database alias (<SAPSID> must consist of all upper case characters or digits!) v SMS tablespace containers of the original system are located at UNIX or Linux: /db2/<SAPSID>/... Windows: <drive>:\db2\<SAPSID>\...
Redirected Restore in Automatic Mode

Backup Object Manager provides an automatic cloning function, which by default creates an exact copy of the original SAP database in a different location, with the physical database layout (tablespaces, number and size of the tablespace containers) of the target database identical to the source system. The path names of the new tablespace containers are constructed by replacing the original SID with the SID of the target system. Optionally and additionally, the administrator can request adaptations to the sizes of all or selected tablespace containers of the target database in order to optimize the I/O performance. For this, Backup Object Manager provides automated tablespace resizing and automated tablespace normalizing. For more detailed information, see: Automated Tablespace Adaptations on page 72. The Backup Object Manager redirected restore function can also be used to resize table space containers of the source database. This is achieved by requesting a redirected restore, automatic mode, with the same SID set as both the original and the target SID while requesting scaling, normalizing, or both at the same time A redirected restore, automatic mode can be requested by issuing the following command on the target system:
backom -c rr_db_clone -a <DB2 source alias>,<DB2 target alias> -t <timestamp>
(For the complete syntax of the command, refer to Chapter 6, Data Protection for SAP Backup Object Manager, on page 53). For a redirected restore of a database in automatic mode, Backup Object Manager performs the following steps: 1. Backup Object Manager retrieves the TDI for the requested backup from TSM into memory. 2. Backup Object Manager replaces the alias of the source database with the alias of the target database. If no target database alias is specified Backup Object Manager takes the original database alias as target database alias. 3. Using the modified TDI, Backup Object Manager performs some basic plausibility checks as described in section Redirected Restore Plausibility Checks on page 69. 4. Backup Object Manager creates the necessary tablespace containers on the target system, using the modified TDI. If the target database alias is the same as the original database alias the database is restored to the original database
66

alias and SID. When restoring to the original system, Backup Object Manager tries to overwrite the original database. Overwriting the original database requires confirmation by the administrator. 5. Finally, Backup Object Manager calls the DB2 redirected restore function.
Redirected Restore in Interactive Mode

Backup Object Manager provides a dialog for the redirected restore function for SAP databases where menus guide the administrator through the process of redefining table space container layout (adding, deleting, moving and resizing). Backup Object Manager compares the tablespace definitions entered with the layout of the original database as documented in the original TDI and provides immediate feed-back on possible configuration problems. Optionally and additionally, the administrator can request adaptation to the sizes of all or selected tablespace containers of the target database in order to optimize the I/O performance. For this, Backup Object Manager provides automated tablespace resizing and automated tablespace normalizing. For more detailed information, see Automated Tablespace Adaptations on page 72. A redirected restore, interactive mode can be requested by issuing the following command on the target system:
backom -c rr_db_interactive -a <DB2 source alias>,<DB2 target alias>... ...-t <timestamp> -f <target TDI file>
(For the complete syntax of the command, refer to Chapter 6, Data Protection for SAP Backup Object Manager, on page 53). For a redirected restore in interactive mode, the following steps are performed: 1. Backup Object Manager retrieves the TDI for the requested backup from TSM into memory. 2. Backup Object Manager replaces the alias of the source database with the alias of the target database. If no target database alias is specified Backup Object Manager takes the original database alias as target database alias. 3. Backup Object Manager determines if specific containers need to be redefined. 4. Backup Object Manager displays the main menu, showing a sorted list of tablespaces of the database to be restored. Tablespaces or tablespace containers for which problems concerning their locations or sizes were detected are marked either with ! or !! in the following menus.
Note A ! mark in front of an entry indicates a potential problem (warning). The redirected restore can be started, but it is recommended to resolve the problem first. A !! mark in front of an entry indicates a problem (error). The redirected restore will not succeed before the problem is resolved. 5. The administrator can select tablespaces or tablespace containers to be changed by using their IDs. When all modifications of the physical database layout are done and no more errors (!!) are displayed, the redirected restore can be started by entering c
67

from the main menu. The administrator can also abort the redirected restore from any menu by entering a. If requested with option -f, the modified physical database layout of the target database is stored in an ASCII file in the file system. This file can be used afterwards as input for a redirected restore in batch mode at another location, where the same physical changes to the restored database must be applied (see also: Redirected Restore in Batch Mode). Using the TDI just modified by the administrator and the original TDI, Backup Object Manager performs some basic plausibility checks as described in section Redirected Restore Plausibility Checks on page 69. Backup Object Manager creates the necessary tablespace containers on the target system, using the modified TDI. If the target database alias is the same as the original database alias the database is restored to the original database alias and SID. When restoring to the original system, Backup Object Manager tries to overwrite the original database. Overwriting the original database requires confirmation by the administrator. Finally, Backup Object Manager calls the DB2 redirected restore function.
6.
7.
8.
9.
Redirected Restore in Batch Mode

Backup Object Manager provides a batch mode of the redirected restore function where the TDI for the target database is modified before starting the redirected restore. The TDI image to be used must be stored as an ASCII file in the file system. For example, a TDI image created during an interactive redirected restore can be used as target TDI for a redirected restore in batch mode. Refer to Appendix G, Tablespace Definition Information (TDI), on page 189 for a sample TDI file and for the rules to follow when modifying the TDI. An administrator may want to use the batch mode for multiple redirected restores to different locations, but with identical changes of the physical database structure. As with the interactive mode, the original TDI will be used to test whether the changes of tablespace container sizes and locations made by the user are valid. Optionally and additionally, the administrator can request adaptations to the sizes of all or selected tablespace containers of the target database in order to optimize the I/O performance. For this, Backup Object Manager provides automated tablespace resizing and automated tablespace normalizing. For more detailed information, see: Automated Tablespace Adaptations on page 72. In order to start a redirected restore, batch mode, the administrator needs to make sure that the TDI of the target database is available. This can be done by providing the target TDI image of a previous interactive redirected restore as a file in the file system, or by retrieving the original TDI from TSM and modifying it. A TDI image is retrieved from TSM into the file system with the following command:
backom -c r_tdi -a <DB2 source alias> -t <timestamp> -d <target directory of TDI>
(For the complete syntax of the command, refer to: Chapter 6, Data Protection for SAP Backup Object Manager, on page 53).
68

This original TDI image can be renamed and modified. A redirected restore, interactive mode can be requested by issuing the following command on the target system:
backom -c rr_db_batch -a <DB2 source alias>,<DB2 target alias> -t <timestamp,... ...-f <full qualified path and name of target TDI file>
For a redirected restore in batch mode, Backup Object Manager performs the following steps: 1. In the target TDI file provided, Backup Object Manager replaces the alias specified there with the alias of the target database. If no target database alias is specified Backup Object Manager takes the original database alias as target database alias. 2. Backup Object Manager retrieves the original TDI from TSM and tests whether the target TDI defines tablespace containers that are sufficient to replace the original tablespace containers. 3. Using the target TDI and the original TDI, Backup Object Manager performs some basic plausibility checks as described in section Redirected Restore Plausibility Checks. 4. Backup Object Manager creates the necessary tablespace containers on the target system, using the target TDI. If the target database alias is the same as the original database alias the database is restored to the original database alias and SID. When restoring to the original system, Backup Object Manager tries to overwrite the original database. Overwriting the original database requires confirmation by the administrator. 5. Finally, Backup Object Manager calls the DB2 redirected restore function.
Redirected Restore Plausibility Checks

Regardless of the mode of the redirected restore operation (automatic, interactive, batch), Backup Object Manager performs the following checks before the DB2 redirected restore operation is started. v All paths of tablespace containers must be fully qualified. v On Windows, all drives used for storing tablespace containers must be available. v On UNIX or Linux, the volumes used for storing tablespace containers must be available. v There must be sufficient space in the various locations of the tablespace containers in the target system for storing them. v Backup Object Manager tests whether there exist other files or directories at the desired locations of the tablespace containers. A warning is issued when a directory for a SMS container already exists, but is not attached to a different database. An error is issued, when a directory for an SMS container already exists and is attached to a different database a file for a DMS container already exists in the target location v The tablespace containers must be sufficiently large to hold the restored data. For all modes of redirected restore (clone, interactive, batch), Backup Object Manager provides a test-only option that performs validation checking only, without actually starting a restore. This option can be used to determine in advance whether a specific redirected restore will succeed.
69

The Backup Object Manager test-only option is activated by adding the command option -C to a redirected restore command. For example, the following command will test if a redirected restore in batch mode will succeed with the target TDI file provided:
backom -c rr_db_batch -a <DB2 source alias>,<DB2 target alias> -t <timestamp>... ...-f <full qualified path and name of target TDI file> -C
If the test yields that the redirected restore will not succeed check the Backup Object Manager log for error and warning messages.
Sample Work Flow for Redirected Restore

This is a sample work flow for a redirected restore with Data Protection for SAP Backup Object Manager. In order to clone the SAP production database (PRD) to a test system (TST) on a different machine, apply the following procedure: 1. Make sure that the administrator account to be used has the appropriate rights on the target system. For example, it must be given the permission to allocate files of a size greater than 2 GB. 2. Verify that the source database PRD meets the prerequisites for a redirected restore operation as listed in Redirected Restore Prerequisites on page 65. 3. Setup Data Protection for SAP on the target machine. Verify that the following environment variables are set correctly: v XINT_PROFILE pointing to the Data Protection for SAP profile v DB2_VENDOR_LIB, pointing to the Data Protection for SAP shared library v TDP_DIR, denoting the path for Data Protection for SAP process log files 4. For the restore process, customize the Data Protection for SAP profile (initTST.utl) of the test system in the following manner: v Use BACKUPIDPREFIX as specified on the source system: PRD___. v Use the TSM server specified on the source system. This may include adding the appropriate TSM server stanza to the client system options file (dsm.sys) on the test system. v Use the ADSMNODE specified on the source system. v Use BRBACKUPMGTCLASS as specified on the source system. 5. Record the password of the appropriate node on the TSM server:
backom -c password
This creates or updates the Data Protection for SAP configuration file initTST.bki. 6. Check the Data Protection for SAP database backup images on TSM with the command:
backom -c q_db
Verify that the TDI flag is set to yes for the backup image to be restored. For information how to create Tablespace Definition Information (TDI) refer to Creating Tablespace Definition Information on page 65. 7. Call the BackOM built-in check routine by adding option -C to the restore command:
70
backom -c rr_db_clone -a PRD,TST -t <timestamp> -C
This checks for logical and physical integrity of the test system. For example, a free-space check, a check for the existence of files at the location of tablespace containers, etc., is, performed. 8. Start the redirected restore:
backom -c rr_db_clone -a PRD,TST -t <timestamp>
9. If the database is in rollforward pending mode and needs to be recovered, retrieve the required log files manually with BackOM before starting the DB2 rollforward process. Do not use the DB2 rollforward command with automatic log file retrieval in this situation: the log files were archived under the old database name, but the rollforward process would try to find them based on the new name. In order to determine the log numbers and log chain to be retrieved, issue:
backom -c q-log -a PRD
In order to retrieve the log files issue:

backom -c r-log -a PRD -l <log number range> -k <log chain> -d <destination directory>
As the destination directory, the database log directory or a different location may be selected. 10. If the database is in rollforward pending mode, start the DB2 rollforward process. In case the log files were retrieved to a location other than the database log directory, the DB2 rollforward procedure must be started with the 'overflow log path' option denoting the location of the retrieved log files. 11. After the redirected restore has completed successfully and before backing up the new test system, modify the Data Protection for SAP profile initTST.utl to the values of the new test system. This may involve the following keywords: v BACKUPIDPREFIX v v v v SERVER ADSMNODE BRBACKUPMGTCLASS BRARCHIVEMGTCLASS
Note: Be careful not to back up the test system with the BACKUPIDPREFIX of the production system! 12. (DB2 V8.2 or higher) Update the DB2 database configuration of the test system: v Set VENDOROPT to the vendor environment file created during the Data Protection for SAP installation. v If the DB2 Log Manager is used in combination with Data Protection for SAP: Set LOGARCHMETH1 to
VENDOR:/<path of shared library>/<shared library>
71

Set LOGARCHOPT1 to the vendor environment file created during the Data Protection for SAP installation. In combination with this procedure, the sizes of tablespace containers of the TST database can be modified with the scaling and normalizing functions of Backup Object Manager. These functions are detailed in the following section.
Automated Tablespace Adaptations

During the redirected restore operation, Backup Object Manager can adapt the sizes of tablespace containers when creating the containers of the target database. The adaptation of tablespace containers may serve several purposes: Their sizes may be increased in order to provide more space or decreased in order to use storage more efficiently, or they may be allocated with similar sizes in order to make parallel I/O operations more efficient. Both, free space management and efficiency of parallel operations are supported by Backup Object Manager functions: scaling (resizing) and normalizing.
Tablespace Scaling
There must be sufficient free space in a tablespace in order to guarantee continuous functioning of the database. In case of a database restore, the administrative overhead of tablespace adaptation on the target side with respect to space management can be reduced significantly if a redirected restore is done with the Backup Object Manager built-in automated tablespace scaling function. This function allows the redefinition of tablespace containers (location and size). Also, this function may prevent I/O-intensive tablespace rebalancing triggered by DB2.
72
Figure 18. Tablespace Scaling
In the example in Figure 18, the SYSCATSPACE tablespace of the original system has a usage of 98 percent. Disk 1 has still 4 percent of free space while the second container is used 100 percent. As part of the redefinition step of a redirected restore, the administrator may want to increase the free space of this tablespace. The goal is to get an overall filling rate of 70 percent on the target side. To achieve this, the first container could be manually increased to provide 20 percent of free space and the second container could be manually increased to provide 40 percent of free space. The advantage of doing this in combination with a redirected restore is that after restoring, no further administrative tasks are necessary for resizing the tablespace containers. Backup Object Manager simplifies the tablespace resizing process described above by providing an automatic tablespace scaling function. It can be used in combination with any mode of redirected restore facility by specifying the command option -s followed by a floating point sizing factor. The following holds true for the sizing factor: v - A value of 1 indicates that the target tablespace is 100 percent the size of the original; nothing is changed. - A value greater than 1 increases the target tablespace. For example, a value of 1.1 increases the target tablespace by 10 percent to a target value of 110 % of the original v - A value less than 1 decreases the target tablespace. For example, a value of 0.9 decreases the target tablespace by 10 % to a value of 90 % of the original. v
73

Therefore, manual adaptation of the tablespace containers described above can be replaced by the following procedure using Backup Object Manager redirected restore: 1. Issue a Backup Object Manager query to determine the original fill rate of the tablespace:
backom -c q_tdi -a <DB2 source alias> -t <timestamp> -m detailed
2. Calculate the tablespace scaling factor: scaling factor = original fill rate / new fill rate Example: scaling factor = 0.98 / 0.7 = 1.4 3. Issue the Backup Object Manager redirected restore command as follows:
backom -c rr_db_<type> -a <DB2 source alias>,<DB2 target alias> -t <timestamp> ... ...-T SYSCATSPACE -s 1.4
After the redirected restore has completed successfully the SYSCATSPACE tablespace on the target side is increased by 40 percent during tablespace container redefinition. The new overall fill rate of the SYSCATSPACE in the target database is now 70 percent.
Tablespace Normalizing
For an optimal performance of parallel I/O operation of a database, it is desired that all containers of a tablespace are of the same size. During tablespace maintenance, containers may be added or extended from time to time, resulting in different container sizes after some time. Consequently, data is unevenly distributed among the containers, resulting in a poor performance of parallel I/O operations, for example during table scans (sequential prefetching). In case of a database restore, the administrative overhead of tablespace adaptation on the target side with respect to parallel I/O performance optimization can be reduced significantly if a redirected restore is done with the Backup Object Manager built-in automated tablespace normalizing function. This function allows the redefinition of tablespace containers (location and size). Also, this function may prevent I/O-intensive tablespace rebalancing triggered by DB2.
74
Figure 19. Tablespace Normalizing
In the example in figure Figure 19, the tablespace of the original system consists of containers of different sizes. Even though three processes may simultaneously read the data due to sequential prefetching during table scans, the different sizes of the containers and the resulting uneven data distribution will prevent parallel I/O for a part of the scan. The degree of parallelism decreases over time. As part of the redefinition step of a redirected restore, the administrator may want to make all containers of the tablespace the same size. The advantage of doing this in combination with a redirected restore is that after restoring, no further administrative tasks are necessary for resizing the tablespace containers. Backup Object Manager simplifies the tablespace container resizing process described above by providing an automatic tablespace normalizing function. It can be used in combination with any mode of redirected restore facility by specifying the command option -N. Therefore, manual resizing of the tablespace containers as described above can be replaced by the following Backup Object Manager redirected restore command:
backom -c rr_db_<type> -a<DB2 source alias>,<DB2 target alias> -t <timestamp> -N
This will resize each container of a tablespace to the average size of all containers within the same tablespace: New container size = (Overall tablespace size) / (Number of tablespace containers).
75

After the redirected restore has completed successfully, all containers of a tablespace of the target database are of the same size. As a result, the physical layout of the restored database is at an optimum with respect to continuous parallel I/O performance.
76
Chapter 8. Installing and Using the Administration Assistant for Data Protection for SAP
This chapter gives an overview of the Administration Assistant and describes its installation and setup.
Introducing the Administration Assistant Functions and Features of the Administration Assistant
The Administration Assistant provides the following functions: v v v v v v | | | | | Monitor operations View performance data Configure systems Request problem support Manage report templates Administer users
Monitor Operations provides a centralized view of the backup status information for all SAP systems registered with the Administration Assistant server. Summaries of the backup status of all or a selection of SAP systems are available as well as detailed information on all backup runs of a specific SAP system. Thresholds can be defined to enable alerting under certain conditions. View Performance Data displays performance information while Data Protection for SAP is performing a backup or restore operation. The Administration Assistant also saves this performance data and provides a graphical presentation for later analysis. Configure systems allows to customize the SAP backup profiles, the Data Protection for SAP profile, and the IBM Tivoli Storage Manager files for each of the SAP systems registered with the Administration Assistant server. Online information supports the customization process. Additionally, profiles can be copied from one system to others. If configuration changes are performed via the Administration Assistant, a configuration history is maintained, enabling the administrator to easily return to a previous configuration. Request problem support supports sending support requests directly to IBM. Support requests can contain user-specified problem descriptions, but the Administration Assistant also attempts to automatically collect and include further information, such as profiles and error logs. Manage report templates allows the generation and maintenance of templates for producing reports. Administer users supports the definition of user IDs and permissions for accessing the Server component via the Administration Assistant client. Additionally, the Administration Assistant lets the administrator create reports in XML or HTML format from the output of Monitor operations and View performance data.
77
Installing and Using the Administration Assistant

The primary documentation for the Administration Assistant is the integrated online help.
Concepts of the Administration Assistant

The Administration Assistant comprises three server-level components (Server, Database Agent, and Database) and the client component. Operations data is maintained in an internal database. This offers a solution to potential out-of-memory problems in SAP environments with a large number of Data Protection for SAP instances and provides better scalability. The following figure shows the communication relationships of the Administration Assistant components (port numbers shown are defaults).
Figure 20. Administration Assistant Components (with Default Port Numbers)
The server-level components can be installed together on one system (standard installation) or distributed across multiple systems. For example, the Server component can reside in one system and the DB components in a second system, or each component can be installed in a separate system. The distributed installation can help alleviate CPU loading in a single-system configuration in large-scale environments by spreading this load over two or three separate systems. If CPU load is not an issue, the single-system installation will normally be used. Note: The distributed installation requires that all connecting Data Protection for SAP instances be version 5.4 or higher. If a single-system installation is selected, earlier Data Protection for SAP versions can also connect to the Administration Assistant.
78

| | | | | | | | | The internal database used by the Administration Assistant is managed by either the open-source database product Apache Derby or IBM DB2 data server. Apache Derby is bundled with, and installed by, the Administration Assistant. For more information on Apache Derby, see
http://db.apache.org/derby/
If you prefer using the IBM DB2 data server, an existing DB2 installation must be present. It will be configured by the Administration Assistant. For more information on DB2, see
http://www.ibm.com/software/data/db2/
The Server component waits for the clients requests for connections using either the http or https protocols and also for connect requests (via TCP/IP) from the ProLE service of Data Protection for SAP. After connecting to the Server component, ProLE connects to and communicates directly with the Database Agent to send data pertaining and backups and restores performed within its Data Protection for SAP instance. The Database Agent collects this data and stores all information related to the Operations Monitor in the Administration Assistant database via the Database component. This data is accessed when the clients request any of the Administration Assistant monitoring or analysis functions. In order to receive and store the history data, the Administration Assistant server-level components must be running and connected to the Data Protection for SAP ProLE service during the backup and restore operations. The existence of the database-related components is transparent to the client user. Each system hosting an Administration Assistant component can be running UNIX, Linux, or Windows. The Server and Database Agent components maintain separate configuration files (assist.cfg and dbagent.cfg, respectively). User profiles ensure that a client user can access the data of only those SAP database servers for which permission has been granted. The Database Agent forwards performance data to the Administration Assistant Server component, which records it in history files. The retention time for this data is definable at installation time (default 14 days) An SAP system landscape contains several SAP systems, such as production, development, test, and education systems. A single Administration Assistant Server component can monitor many SAP database servers. A typical example is shown in Figure 21 on page 80.
Chapter 8. Administration Assistant
79
Figure 21. Example of an SAP Landscape
The Administration Assistant client is started from a browser by invoking the URL designating the Server component host. The client is implemented as a Javaapplet that communicates with the Server component via a remote method invocation (RMI) connection. If the Administration Assistant Server component is started in non-secure mode (that is, with the keyword nonsecure defined in the Server configuration file assist.cfg), it accepts connect requests from a client to its http port via http. In this case, further communication between the client and server is via TCP/IP. If the Server component is started in secure mode (that is, with the keyword "nonsecure' omitted from the Server configuration file), it accepts connect requests from a client to its https port via https. In this case, the Secure Sockets Layer (SSL) protocol is employed for all communication between the Administration Assistant clients and the Server component. The latest SSL protocol (Version 3) can be found at http://wp.netscape.com/eng/ ssl3/. The latest information on PKI with X.509 certificate can be found on the Web page of the IETF Working Group 'Public Key Infrastructure (X.509) (pkix)' at: http://www.ietf.org/html.charters/pkix-charter.html . XML- or HTML-format reports are created either from the Administration Assistant client via the graphical user interface or via a command-line interface from a scheduling client. The scheduling client is implemented as a Java application that communicates with the Administration Assistant Server component via an RMI connection.
80
Installing or Upgrading the Administration Assistant

In order to set up the Administration Assistant server, do the following: 1. Check that the Administration Assistant package is complete. The package includes machine readable material on a CD-ROM or a CD image downloaded from Passport Advantage. See the Readme information at the CD and package levels for a description of the respective structure and the latest news. The Administration Assistant is provided on each DP for SAP CD or CD image as a file of the format:
<version>-TIV-TSMERPAABASE-MULTI.jar
2. Make sure that the requirements are met. For details, see Prerequisites for Installing the Administration Assistant Server-Level Components and Prerequisites for the Administration Assistant Client. 3. Gather planning information. For details, see Installation Planning for the Administration Assistant Server-Level Components on page 82. 4. Install the Administration Assistant server-level components. For details, see Installing the Administration Assistant Server-Level Components on page 82. 5. Perform post-installation steps. For details, see Post-Installation Steps on page 85. 6. Set up the Administration Assistant client. For details, see 2. Setting up the Administration Assistant Client on page 85. 7. Verify the installation. For details, see 3. Verifying the Installation on page 86. If you are going to do an upgrade installation, refer to Upgrading the Administration Assistant (Migration) on page 88.
Prerequisites for Installing the Administration Assistant

Prerequisites for Installing the Administration Assistant Server-Level Components
| | | | | | | | | | | | The following products must be installed before you can start setting up the Administration Assistant server-level components: v Java Runtime Environment (JRE) or Java Development Kit (JDK) v Java Beans Activation Framework (JAF) v Java Mail v IBM DB2 data server (optional DBMS for Administration Assistant database) If you decide to use the IBM DB2 data server, ensure the following: v On Windows platforms: DB2 must be installed and running v On UNIX and Linux platforms: DB2 must be installed and running Create a new system user for which the DB2 instance should be installed For hardware and software prerequisites, as well as the maintenance levels required by the current version of the Administration Assistant, refer to the release notes for DP for SAP (see Where to Find More Information on page xi). TCP/IP must be ready for communication before starting up the Administration Assistant server-level components.
Prerequisites for the Administration Assistant Client

Before starting the Administration Assistant client make sure the following requirements are met:
81

v A fully Java-capable Web browser with Java plugin. The applet loaded from the Administration Assistant server must be granted the following permissions: Permission to establish a connection to the Administration Assistant server via RMI, for example:
permission java.net.SocketPermission "<Server component hostname>:1024-", "connect";
Permission to switch to a different language:

permission java.util.PropertyPermission "user.language", "write";
v For the presentation of graphics in reports, a browser supporting Scalable Vector Graphics (SVG), for example with the Adobe SVG Viewer, must be available. v X Window system if the Administration Assistant client will be started on a UNIX or Linux system. v A minimum screen resolution of 1024x768 pixels (1280x1024 or higher is recommended). For software versions and maintenance levels required by the current version of the Administration Assistant, refer to the DP for SAP release note. TCP/IP must be ready for communication before connecting to the Server component.
Prerequisites for the Scheduling Client

When selecting the scheduling client, make sure the following requirements are met: v A TCP/IP connection can be established to the Administration Assistant Server component. v A Java VM is available. v For the presentation of graphics in reports, a browser supporting Scalable Vector Graphics (SVG), for example with the Adobe SVG Viewer, is available.
Installation Planning for the Administration Assistant Server-Level Components

See Table 7 on page 178 for a list of planning requirements in table form. This information is also available in the planning_sheet_aa (UNIX or Linux) and planning_sheet_aa.txt. (Windows) files in the Data Protection for SAP installation directory.
Installing the Administration Assistant Server-Level Components

The Administration Assistant installation packages are located on each of the Data Protection for SAP CD-ROMs or CD images, and can also be downloaded from the IBM FTP server. Initial installations must always be done from the CD-ROM or CD image. Refer to the file README.1ST in the root path of the CD or CD image for information on where to find documents, and follow the installation description below. On the CD or in the CD image, the installation package for the Administration Assistant is a single, platform-independent .jar file with the following name:
<version>-TIV-TSMERPAABASE-MULTI.jar
82

If you want to upgrade from an earlier version of Data Protection for SAP Administration Assistant in your environment, you have the option to download the latest version from the IBM FTP server via the product support page http://www.ibm.com/software/sysmgmt/products/support/ .IBMTivoliStorageManagerforEnterpriseResourcePlanning.html For more information on upgrading from an earlier version, refer to Upgrading the Administration Assistant (Migration) on page 88.
Installation Process
To assist you with the installation procedure, the Administration Assistant packages provide a setup assistant that guides you through the installation process. The setup assistant provides the option to install either an English-only version of the Administration Assistant or the multi-language version. To install the Administration Assistant correctly, system administrator privileges are required. If a multi-host installation is desired (which distributes the server-level components over two or three hosts), copy the package file to each target host and perform a 'custom' installation that selects the components for that host. There is no need to set the environment variable CLASSPATH. However, if this variable is set in the system environment, the directory in which the package file resides must be included. During the installation process the administrator must select a language option. In order to switch options after the installation, uninstall the Administration Assistant and install again with the new option. Start the installation by specifying the following command:
java -cp <package file name> run
If only the JRE is installed, you must use the command:

jre -cp <package file name> run
During installation, the following modifications are made to your system automatically: v All necessary paths (installation, history, OnDoc, log paths) are created. Corresponding files are copied into the installation and OnDoc directories. v The Administration Assistant startup files are created and added to the installation directory:
Component Server UNIX or Linux sadma.sh sdba.sh sdb.sh Windows sadma.cmd sdba.cmd sdb.cmd
Database Agent Database
v The configuration file assist.cfg, containing all relevant configuration parameters specified during the installation, is created and added to the installation directory.
83

v The configuration file dbagent.cfg containing all relevant configuration parameters specified during installation of the Database Agent component is created and added to the installation directory. v On Windows systems a service is installed and automatically started. This service starts AAStart.exe and java.exe. v On UNIX or Linux systems a new /etc/init.d entry is created for each Administration Assistant server-level component:
Component Server Database Agent Database (Derby) (optional, as alternative to DB2) Entry in /etc/init.d adminAssistant, with parameters start, stop, and status databaseAgent, with parameters start, stop, and status apacheDerby, with parameters start and stop Not applicable
| |
Database (DB2) (optional, as alternative to Derby)
and the components are started automatically. Note: For automatic start/stop of Administration Assistant components on UNIX or Linux systems, the administrator must create appropriate run level entries. v For an installation using IBM DB2: On Windows systems: - The database tables are created, but no other changes are made. On UNIX and Linux systems: - A DB2 instance for the specified user ($USERNAME) will be created - Some changes to your system will be applied as follows: v An entry in /etc/services is added:
$USERNAME $PORT/tcp # used for Data Protection for SAP - Administration Assistant with DB2 support
| | | | | | | | | | | | | |
v Changes to the created DB2 instance: Set DB2 profile registry variable: DB2COMM=tcpip Set DB2 database manager parameter: SVCENAME=$USERNAME Set DB2 database manager parameter: SPM_NAME=NULL v For an installation using secure communication: A keystore is created on request. An X.509 v1 self-signed certificate containing a key pair with the hostname as an alias is created in the keystore on request. The servers self-signed certificate is imported into the truststore on request. The servers self-signed certificate is exported to a certificate file on request. A Certificate Signing Request is created if desired. When one or more Administration Assistant components have been installed, an overview panel is presented indicating the current status of the installation process and recording the user's entries.
84
Uninstalling the Administration Assistant Server-Level Components

To uninstall the Administration Assistant server-level components, change to the uninstall directory in the Administration Assistant installation directory on each system on which one of the components was installed (potentially two or three systems if a distributed installation was selected for version 5.4 or later). The command files open an uninstall assistant which guides you through the deinstallation process. The public key infrastructure will not be modified when uninstalling the Administration Assistant components, even if it was originally set up during its installation process. To start the deinstallation process, run the following command: |
java -cp uninstall.jar run
Note: The Administration Assistant client component is not physically installed. It executes as a Java applet when the user invokes the URL of the host running the Server component. No action needs to be taken at the client level when uninstalling the Administration Assistant server-level components.
Post-Installation Steps
After successfully completing the installation dialog for the Administration Assistant server-level components, you need to perform the following steps: 1. If appropriate, prepare a secure connection between the Administration Assistant clients and the Server component. 2. Set up the Administration Assistant client. 3. Verify the installation. 4. Set up a scheduling client for reporting
1. Preparing a Secure Connection between the Administration Assistant Server Component and Client
If the necessary information was provided during the installation, the Server component is already configured for secure communication with its clients after the installation procedure. However, by default it is set up to accept unsecure (http) connect requests from the clients. You start a secure Administration Assistant Server component by removing the keyword nonsecure from the configuration file (assist.cfg). If you elect not to provide security information during the installation process, or if you need to change the security setup, refer to Configuring for Secure Communication on page 91.
2. Setting up the Administration Assistant Client

The Administration Assistant client is not an installable component. It executes as a Java applet when the user connects to the Administration Assistant Server component. Before connecting to the Server component, make sure that cookies are not disabled by any means, for example by your browser or by personal firewall settings. Also, ads and pop-up panels must not be blocked unless you use
85

index.html in the address. See also 3. Verifying the Installation for information on how to connect to the Administration Assistant Server component. Make sure all prerequisites of the Administration Assistant Client (see Prerequisites for the Administration Assistant Client on page 81) are met. In order to establish secure communication between the Administration Assistant client and the Server component, the clients Java plugin must be able to verify the certificate presented by the Administration Assistant Server component. In a production environment, the server certificate will be signed by an official certificate authority whose root certificate is contained in the plugins truststore. In this case, there is nothing to be done. If, however, the server identifies itself with a self-signed certificate, this certificate must be imported into the plugins truststore. If you did not replace the plugins truststore via the Java Plugin Control Panel, file cacerts in the Java security path is used as the truststore. You modify it with your keystore management tool, which may differ depending on your platform and provider. With keytool (Sun Microsystems), for example, you need to issue
keytool -import -alias <Server component hostname> -file <cert_file> -keystore <trustore>
Note Be sure to remove the self-signed trusted certificate from the truststore as soon as the officially signed server certificate is available and employed. A setup with self-signed certificates is not recommended for production environments.
3. Verifying the Installation

Verify the installation of the Administration Assistant by connecting to the Administration Assistant Server component from a client machine. If the Server component was started with the keyword 'nonsecure' in the Server configuration file, then connect via
http://<Server component host name>:<http port>
Alternatively, you can make the connection via

http://<Server component host name>:<http port>/index.html
In the latter case, the Administration Assistant client will not open a new browser window. If the Administration Assistant server is started without the keyword 'nonsecure' in the Server configuration file, then connect via
https://<Server component host name>:<https port>
Alternatively, you can make the connection via

https://<Server component host name>:<https port>/index.html
86

In the latter case, the Administration Assistant client will not open a new browser window. For your initial login, use the userid ADMIN with password 'admin'. Make sure you change the default password immediately via the client function Administer Users. As soon as an instance of Data Protection for SAP connects to your Administration Assistant Server component, the instance will be displayed in the list of DP for SAP servers. For details on how to set up your instance of Data Protection for SAP to connect to a specific Server component, refer to Adjustments for the Administration Assistant on page 41.
4. Setting Up a Scheduling Client for Reporting

In order to create reports with templates, a scheduling client server must be set up. This is done by the following steps: 1. Select a system that meets the requirements documented in Prerequisites for the Scheduling Client on page 82. 2. Copy files Admt.jar and NLS.jar from the installation directory of the Administration Assistant Server component to the scheduling client system. Before starting to generate reports, make sure that files Admt.jar and NLS.jar are included in the CLASSPATH and that the JVM is included in the PATH. For a sample script addressing this setup refer to Sample Command Files for Scheduling Reports on page 195. 3. In case the Administration Assistant Server component is started in secure mode, set up a public key infrastructure between the scheduling client and the Server component: In a production environment, the server certificate will be signed by an official certificate authority whose root certificate is contained in the JVMs truststore. In this case, there is nothing to be done. If the server identifies itself with a self-signed certificate, however, this certificate must be imported into the JVMs truststore. By default, the truststore is contained in file cacerts in the Java security path. You modify it with your keystore management tool, which may differ depending on your platform and provider. With keytool, for example, you issue
keytool -import -alias <Server component hostname>... ... -file <cert_file> -keystore <truststore>
Note Be sure to remove the self-signed trusted certificate from the truststore as soon as the officially signed server certificate is available and employed. The setup with self-signed certificates is not recommended for production environments.
Starting and Stopping the Administration Assistant Manually

The Administration Assistant Server component can be started and stopped manually with the following command files in the installation directory: On UNIX and Linux:
sadma.sh start|stop <Server component configuration file>
87

On Windows:
sadma.cmd start|stop <Server component configuration file>
The Administration Assistant Database Agent can be started and stopped with On UNIX and Linux:
sdba.sh start|stop <Database Agent configuration file>
On Windows:
sdba.cmd start|stop <Database Agent configuration file>
| |
If you decided to use the bundled Apache Derby, the Administration Assistant Database component can be started and stopped with On UNIX and Linux:
sdb.sh start|stop
On Windows:
sdb.cmd start|stop
| | |
If you decided to use the IBM DB2 data server, the administrative tasks for starting and stopping the database can be done by the DB2 Control Center or by the DB2 command line. Please refer to the IBM DB2 data server documentation.
Important When the Server or Database Agent components are started, a lock file (.lockAA and .lockDBA, respectively) is created. If either of these components is terminated or restarted using the delivered scripts, the respective lock file is also deleted. If for some reason the lock file still exists when the component is started, the request will fail with an error message. In this case, first verify that the process is not already active. If not, the lock file must be deleted manually and the start request reissued.
Upgrading the Administration Assistant (Migration)

In order to upgrade the Administration Assistant server to a new version, do the following: 1. Check that the Administration Assistant package is complete. The Administration Assistant is provided on each of the DP for SAP CDs or CD images, and can also be downloaded from the IBM FTP server. 2. Make sure that the requirements for the new version of the Administration Assistant are met. For details, see Prerequisites for Installing the Administration Assistant Server-Level Components on page 81 and Prerequisites for the Administration Assistant Client on page 81, and read the DP for SAP release notes (see Where to Find More Information on page xi).
88

3. Gather or retrieve planning information. For details, see Installation Planning for the Administration Assistant Server-Level Components on page 82. 4. If you want to migrate your existing data to the new version, perform the procedure described in Migration of Data from Previous Releases. 5. Uninstall the old version of the Administration Assistant. For details, see Uninstalling the Administration Assistant Server-Level Components on page 85. 6. Install the new version of the Administration Assistant server-level components. For details, see Installing the Administration Assistant Server-Level Components on page 82. 7. Perform the post-installation steps. For details, see Post-Installation Steps on page 85. 8. Set up the Administration Assistant client. For details, see 2. Setting up the Administration Assistant Client on page 85. 9. Verify the installation. For details, see 3. Verifying the Installation on page 86. Note: It is possible to use the Administration Assistant in conjunction with supported Data Protection for SAP versions prior to version 5.4, provided the Administration Assistant is installed on a single host. | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
Migration of Data from Previous Releases

Note: The following procedure must be performed prior to uninstalling the Administration Assistant and installing the new version. Data Protection for SAP does not provide support for transferring data from an installation of the Administration Assistant prior to version 5.4. If desired, the report function can be used to capture data from the prior version before the new version is installed. If you would like to transfer data from the database of an installation of version 5.4 of the Administration Assistant, follow these steps: 1. The export tool is provided on each DP for SAP CD or CD image in the migration directory. This directory contains: v aaDerbyAdaption.jar v prepareExport.sql c. v export.cmd (for use with Windows systems) v export.sh and export ksh (for use with UNIX/Linux systems) Copy these files from the CD (or image) for the new version of the Administration Assistant to your system. 2. If you are using Apache Derby, get information on how to connect to the Apache Derby database. These settings are provided in file assist.cfg and are listed below: v Location of your previous installation of the Administration Assistant v Username to connect to the Apache Derby database v Password to connect to the Apache Derby database v Port to connect to the Apache Derby database v Hostname of your system v Name of the database v Path to file aaDerbyAdaption.jar
89

| | | | | | | | | | | | | | | | | | | | | | | | | | | | v Directory where the data will be exported 3. Start the export script. You will be guided through the export process. If you would like to transfer data from the database of version 5.5 of the Administration Assistant, follow these steps: 1. If you would like to export data from a running Apache Derby database, first get information on how to connect to the database. These settings are provided in file assist.cfg. 2. Change to the utils directory and start the export script by typing the following: v For Apache Derby: On Windows systems:
export.cmd
On UNIX/Linux systems:
export.sh (or export.ksh)
v For DB2 data server: On Windows systems:

export.cmd <database> <user> <export directory>
On UNIX/Linux systems:
export.sh (or export.ksh) <database> <user> <export directory>
As a result, the export directory contains several *.aa files. During the installation process, you will be asked if you would like to import old data. Within this dialog you can enter the export directory you selected during the export. If you would like to reuse your styles and reports, save these directories from the installation directory to another directory. Note: During the installation of Administration Assistant all data in the installation directory will be removed. After the installation process, you can copy these directories back to the installation directory of the Administration Assistant.
Configuring the Administration Assistant Administering User IDs

With the Administer users function, it is possible to create and delete accounts with appropriate rights for using Administration Assistant functions or configuring DP for SAP. User permissions can be granted or revoked. For each SID in the system landscape, the following permissions can be granted: v Simulate backup/restores: to initiate simulations v Configure groups: to configure display groups to be used with function Monitor backup states v Problem support: to send support request mail v Operations monitoring: to view backup status information v User administration: to manage user accounts v Performance monitoring: to view performance data v Configuration: to modify the configuration of Data Protection for SAP
90

Additionally, a user can be granted permission to configure parts of the internal logic of the "Monitor backup states function. When you start the Administration Assistant for the first time, you will need to create profiles for authorized users. Refer to the online help for information on how to do this.
Configuring for Secure Communication

The secure communication between the Administration Assistant Server component and its clients is realized with the Secure Socket Layer (SSL) protocol. This protocol requires that both the server and client be integrated in a public key infrastructure (PKI). Specifically, the Server component requires v An https port to listen on for https connect requests v A keystore containing a key pair it uses to identify itself to the clients and when connecting internally to the RMI registry. The servers hostname is used as an alias for this key pair. Since the keystore contains the servers private key, precautions must be taken that prevent access by unauthorized persons. v A truststore containing trusted certificates that allow verifying the servers signature. If the server certificate was digitally signed by an official certificate authority whose root certificate is available in the truststore by default, there is nothing to be done. If however, the server identifies itself with a self-signed certificate, this certificate must be imported into the truststore as well.
Note Be sure to remove this trusted certificate from the truststore as soon as the officially signed server certificate is available and employed. A setup using self-signed certificates is not recommended for production environments. Both the keystore and truststore can be manipulated with your keystore management tool, which may differ depending on your platform and provider (for example, keytool ). For setting up the Administration Assistant Server component for secure communication you need to v Remove the keyword 'nonsecure' from the Server configuration file (assist.cfg) v Specify the appropriate https port number in the Server configuration file:
httpsport=<https port number>
The default https port number is 443. v Start the Server component with the appropriate keystore and truststore. You do this by adding the parameters to the appropriate 'java' call. The parameters are shown in the shaded area below: for UNIX and Linux: add the parameters to sadma.sh for Windows: add the parameters to sadmt.cmd and to the registry. The Windows registry key is: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\... ...AdminAssistant\Parameters\AppParameters
-Djavax.net.ssl.keyStore=<keystore> -Djavax.net.ssl.keyStorePassword=<password for keystore> -Djavax.net.ssl.trustStore=<truststore>
91

If you do not specify one or more of these parameters, the defaults of your Java virtual machine will be used. v Make sure the required certificates are contained in the keystore and trust store. v Restart the Administration Assistant Server component. | | | | When changing the Administration Assistant server from non-secure to secure mode using a self-signed certificate, remember to also prepare the Administration Assistant clients as described in 2. Setting up the Administration Assistant Client on page 85 and 4. Setting Up a Scheduling Client for Reporting on page 87.
Changing the Password for the Administration Assistant Database User ID

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The program changeSettings.jar was added to the installation directory in the utils subdirectory. The password for accessing the internal Administration Assistant database can be changed via this program as follows: 1. Change to the utils directory and start the program by typing
java cp changeSettings.jar run
2. Select the type of database you are using with the Administration Assistant (Apache Derby or IBM DB2). 3. Enter the directory containing the encrypted password file (pass.enc). 4. Enter the user ID and the existing password. 5. Enter the new password. 6. For Apache Derby only: To apply the new password to the database, check the box provided. Otherwise, the password file is updated but the database change must then be performed manually. 7. Click Next to complete the change.
Defining Thresholds
The Administration Assistant provides for defining limits (thresholds) for various states pertaining to the Administration Assistant environment. The threshold status is shown in the "Monitor Backup States" and "Backup State - Detailed View" panels. Predefined threshold types are: v Backup duration (in minutes or hours) v Backup size (in MB or GB) v v v v Throughput rate (in GB per hour or MB per second) Time since the last complete backup (in hours or days) Size of all log file backups since the last complete backup (in MB or GB) Recovery point objective (maximum time permitted since the last backup, in minutes or hours)
Additional thresholds can be defined using a custom SQL file (see Defining Thresholds Using the Custom SQL File on page 93). When a threshold is exceeded, this is reported in the "Threshold Status" column of the "Monitor Backup States" panel, and an e-mail describing the exception in more detail is sent to any e-mail addresses defined for the threshold. A lifetime parameter associated with each threshold defines the length of time between e-mail notifications, provided the threshold remains in alert status.
92

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For information concerning threshold definitions, see the Administration Assistant Online Help.
Defining Thresholds Using the Custom SQL File

A custom threshold can be defined in the custom SQL file. The corresponding entry has the following values for the indicated tags:
Table 3. Tags for Defining Thresholds in the Custom SQL File Tag <sql> <programid> <actionid> Value An SQL statement that will return data when the threshold is exceeded. 0 (Administration Assistant) 0 (send e-mail when threshold exceeded)
<executionmode> 1 (run periodically) <param> (Optional) One or more e-mail addresses, separated by semicolons. If no e-mail address is given, only a panel indication is given that the threshold has been exceeded. Note: Multiple e-mail addresses are given in a single <param></param> tag pair, not in multiple pairs.
See Defining the Custom SQL file for details concerning the custom SQL file.
Defining the Custom SQL file

Note: The custom SQL file is intended to be implemented or modified only by IBM support personnel with a detailed knowledge of the process involved and the internal Administration Assistant database. This section does not discuss this process in detail. The custom SQL file must be named:
customSQLFile.txt
and placed in the installation directory (or folder) of the Administration Assistant (for example C:\Program Files\tdpr3assi\customSQLFile.txt). The custom SQL file has the following structure:
# CUSTOM SQL FILE Comment <sql>SQL statement</sql><description> ... </param> <sql>SQL statement</sql><description> ... </param> ...
Each entry must be coded in a single line. As an aid to explaining the entry structure, it is shown in the following with each tag set in a separate line:
93

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
<description> <programid> <actionid>
<sql>SQL statement</sql> <description>Description of the SQL statement</description> <programid>0</programid> <actionid>0</actionid> <displaygroup>1,3</displaygroup> <backuptype>2</backuptype> <executionmode>0</executionmode> <param>parameter-value1</param> <param>parameter-value2</param> ... <param>parameter-valuen</param>
The tag definitions are as follows:

Table 4. Contents of the Custom SQL File Tag # <sql> Definition Comment line An SQL statement that defines which data is to be sent. Notes: 1. Only SELECT statements will be executed. 2. A semicolon at the end of the line is not permitted. 3. The maximum line length is 400 characters. Description of the SQL statement (maximum length: 300 characters) Specifies the program that handles the result of the SQL statement. v programid 0: Administration Assistant Defines the way the result will be handled, depending on the programid (currently, the only value for actionid is 0): v <displaygroup> <system> <backuptype> (programid 0: Administration Assistant): Send e-mail when threshold exceeded (SQL statement returns data)
List of display group IDs separated by commas, or "ALL" for all display groups. List of system IDs separated by commas, or "ALL" for all systems. List of backup types separated by commas, or "ALL" for all backup types. v 0: Archive v 1: Partial backup v 2: Incremental backup v 3: Full backup
<executionmode>
executionmode sets the time the entry will be performed (i.e., the SQL statement issued): v 0: Entry will be performed after each backup run v 1: Entry will be performed periodically
<param>
Parameters needed by the programs. The number of parameters depends on the selected program and action. Multiple parameters are coded using repeating <param></param> tag pairs. v (programid 0: Administration Assistant): One parameter, consisting of the e-mail address list (separated by semicolons)
Notes:
94

| | | | | | | | | | | 1. Each entry in the file must be on a single line. 2. If executionmode is 1, the <system>, <displaygroup>, and <backuptype> tags are ignored, and the SQL statement will be executed periodically. 3. If executionmode is 0, the SQL statement will be executed after the backup completes, but only if the system tag matches the system on which the backup was performed, or the displaygroup tag matches the displaygroup the system belongs to. Furthermore, the <backuptype> tag must match the backup type of the backup performed. 4. The <system> and <displaygroup> tags are mutually exclusive. 5. The custom SQL file will be reloaded periodically by the Administration Assistant Server component. The server need not be restarted.
95
96
Chapter 9. Balancing Your System

This chapter describes how to proceed when tuning your system according to your needs. This is done by employing a combination of functions provided in the Data Protection for SAP Administration Assistant.
Observations on the DP for SAP Data Throughput

We observe that overall throughput rates can differ very much among the various installations. This is due to differences in resources (disks, network bandwidth, server platforms, number of tapes, etc.) and configuration. For a more general discussion of performance considerations refer to General Performance Considerations on page 35. For a list of DP for SAP configuration options contributing to performance read Adjustments to DP for SAP for Improving Performance of Data Transfer on page 37. The following discussion will concentrate on selected elements of the data flow. It will show how to use the given resources to their capacity and will give hints where throughput can be improved.
Figure 22. A Birds Eye View of the Data Flow During Backup
From a birds perspective, when doing a backup with DP for SAP, the data packages need to pass the following elements: Data is read from disk, processed by DP for SAP, and sent via a network to some storage media (tape or disk). In an unbalanced system, each of these elements, disk I/O, network bandwidth, and storage media rates may present a bottleneck, at the same time causing other resources to idle. Traditionally, overall data throughput is measured per file or per entire backup. The results are presented as average throughput rates in various log files. Analysis of the causes of insufficient throughput rates is cumbersome, done by relating events documented in a number of different log files to each other. For the same reason, finding potential for a better exploitation of resources is arduous, too. In a first step to support administrators with these tasks, DP for SAP provides performance sensors that indicate whether there is a bottleneck located either in the elements represented in blue (for disk) or in yellow (for network and tape respectively) in the above graphic.
97
Balancing Your System
Data Protection for SAP Performance Sensors

Depending on the configuration of the IBM Tivoli Storage Manager, data packages are either passed from the IBM TSM API Client via a network to the backup server, or they are processed by the IBM TSM API Client and the Storage Agent in a LAN-free environment.
Figure 23. Performance Optimizing by Using Sensors
There are sensors introduced to Data Protection for SAP that observe the incoming and outgoing data streams. They do not only measure the actual throughput, but also the idle time of the I/O threads versus the duration of the backup. This way, they can indicate whether the streams of incoming and outgoing data of Data Protection for SAP are balanced. After starting a backup, it may take some time until the buffers are filled and the effects of a bottleneck will become obvious.
Presentation of the Measurements in the Administration Assistant

The Administration Assistant function View Performance Data provides a
Figure 24. Showing Data Throughput and I/O Utilization
graphical representation of the data throughput rate at any point in time during the backup. Aligned with this, the utilization rates of the disk (presented in blue by the Administration Assistant) and network threads (presented in yellow by the Administration Assistant) are displayed. Alternatively, the free capacity of these threads can be shown. The administrator can choose to have these rates displayed either for the entire backup considering all TSM sessions, or on a per-session basis. Interesting time intervals that need to be further analyzed can be selected for further analysis in replay mode. For details, see Drilling Down on Special Situations on page 102.
98

The results of the Data Protection for SAP performance sensors are presented in the Administration Assistants function View Performance Data. The Administration Assistant collects history data during each backup run for later analysis. In order to find the results, select View Performance Data, then select History Data. In the list of eligible backups, select the backup to be analyzed. Pressing the Review button will take you to the performance data summary panel.
Typical Situations
Following, we discuss some typical graphs you may see when using function View Performance Data of the Administration Assistant.
Disk Bottleneck
Figure 25. Indicating a Disk Bottleneck
With a disk bottleneck, data is processed by the network and TSM server faster than they can be read from disk. As a consequence, overall throughput is limited by the disk I/O rate, and the network thread is idle. As the network threads usually return very fast due to internal buffering, the network utilization might seem to drop to (almost) zero in this case. Both the network and the storage media are not used to their capacity. If tapes are used they are not kept in streaming mode any more. If you are looking to improve overall throughput you may want to v Increase multiplexing in order to accelerate reading from disk, v Switch off data compression if it is employed. If you are looking to better exploit the resources (here: the tape drives) you may want to reduce the number of sessions to the TSM server and the number of tapes for the backup while increasing multiplexing.
99
Network or TSM Bottleneck
Figure 26. Indicating a Network or TSM Bottleneck
With a network or TSM bottleneck, data is read from disk faster than the network and TSM can process them. Consequently, throughput is limited either by the network capacity or by the storage media rate (disk, tape). In order to actually locate the source of the delay further analysis is required. However, some hints can be obtained from the DP for SAP performance analysis. If v v v you are looking to improve overall throughput you may want to Increase the number of sessions to the TSM server (if the tape is the bottleneck), Use multiple paths to a TSM server or multiple servers, Use RL compression in order to reduce the data to be sent to the backup storage
If you are looking to better exploit the resources you may want to reduce multiplexing so that less data is read from disk simultaneously. If the database is configured for file-online backup this will reduce the number of redo logs created during the backup.
100
A Balanced Configuration
Figure 27. Indicating a Balanced Configuration
If the threads on both the disk and the network side are similarly busy throughout the backup the system is balanced, and the utilization of resources is good. In an optimum setup, tapes are kept in streaming mode. That means that the network is at least as fast as the tape, and there is no idle time on the network side. Thus, a slight network bottleneck is desired.
Note Under certain conditions, the degree of imbalance cannot be determined from the graphical presentation: Depending on your system characteristics (for example system buffering, buffer sizes, etc.), utilization may seem to drop near zero in the graphical presentation although the system is fairly balanced in reality. In this case, slight modifications can yield a change of bottleneck without significant throughput changes. However, whether the system is disk or network / tape constrained is always shown correctly. If you are looking to improve overall throughput you may want to add more resources and create a balanced system again. If you are looking to better exploit the resources you are done.
Note A balanced system does not necessarily mean that the data throughput cannot be improved further. Adding new resources can still improve the throughput rate.
101
Drilling Down on Special Situations

When looking at the diagrams in function View Performance Data, you may find points in time when throughput or the utilization of a resource degrades significantly. In order to understand better what happened you may drill down on these time intervals. In most cases you will find that a session is ending or a shorter file was multiplexed with longer files.
Drill-Down
You drill down by selecting a time interval in either of the diagrams of the summary panel with your mouse and choose button Replay Run. Only the selected time interval will be replayed.
Replay Mode
Figure 28. Drilling Down: Replay Mode
In replay mode, you can watch the system working: The processing is replayed for the selected time interval. For each point in time, progress indicators show what files are currently in progress in a session. Transfer rates are displayed and bottlenecks are indicated by session.
Applying Backup Results to Restore

Restore versus Backup
Throughout this chapter, we are mainly dealing with optimizing backups. In most cases, configuration changes and infrastructure problems affect both backup and restore similarly. Therefore, modifications supporting a fast backup while exploiting resources well can generally be applied to the restore analogously. Generally, it is recommended to tune the backup and then run a restore test to verify that restoring still works satisfactorily. Note that for a restore, some parameter values are determined by the settings of the corresponding backup. Among these are:
102

v Compression. If compression was switched on during backup, data needs to be decompressed. v Multiplexing. The same level of multiplexing as was used during backup is automatically applied during restore. v Multiple servers. When a backup is done using multiple servers, the same servers must be online and available during restore.
103
104
Chapter 10. Reporting on Data Protection for SAP Activities

Any configuration and performance information on backup operations done with Data Protection for SAP and the corresponding backup status of SAP database servers can be obtained, monitored, and administered via the Administration Assistant. The Administration Assistant Server and Database Agent components collect status, performance, and configuration data from several SAP database servers and keep it for a limited time. Administrators access the data via a browser. For more information on the features and the concepts of the Administration Assistant, refer to Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77. However, sometimes the information is required when there is no access to the Server component; sometimes the information must be included in other documents or needs to be archived or printed. For these occasions, the Administration Assistant provides the opportunity to create reports in XML or HTML format.
Types of Reports
The reports created with the Administration Assistant basically contain the same information that is displayed by the Administration Assistant functions Monitor Operations and View Performance Data All information available is provided in XML format. Additionally, the Administration Assistant provides style sheets for the translation into the following built-in reports in HTML format: v Status Report v Operations - Detailed Report v v v v Operations - Daily Report Operations - Monthly Report Operations - Failure Report Performance Report
All built-in reports are created in English.
Reporting on Backup States

The Administration Assistant provides information on the backup status of the SAP database servers monitored. Administrators access this information via the function Monitor Operations. Monitor Backup States. Reports containing status information in tabular form are requested from this panel. The overview information provided in the panel Monitor Backup States is provided in the Status Report.
105
Reporting on Data Protection for SAP Activities
Figure 29. Status Report
The Operations Detailed Report provides some more detail.
Reporting on Operations Details

Very detailed information on the latest backup operations for a single SID can be obtained with the Operations - Detailed Report requested from the Backup State Detailed View panel of the Administration Assistant. This panel is reached by selecting a single SID in the Monitor Backup States panel.
Figure 30. Operations Detailed Report
Reporting on Backup Operation Trends

This report type contains general information about the backups of a single SID. Data is represented in graphical and tabular form. Two different report intervals can be chosen: v daily, graphically showing the amount of saved data for a single day , or v monthly (for a time interval comprising several days), graphically showing backup duration, saved data amount, throughput and log file data amount over time.
106

These reports are requested from the Backup State Detailed View panel of the Administration Assistant, to be reached by selecting a single SID in the Monitor Backup States panel.
Figure 31. Operations Daily Report
Reporting on Failed Actions

Information on failed backup operations is provided in the Operations Failure Report to be requested from the Monitor Backup States panel. Administrators can choose to include information on failed backups of log files in this report.
Figure 32. Operations - Failure Report
Reporting on the Performance of Backup Operations

The performance data of a single backup are included in the Performance Report. Data is presented like it is done on the View Performance Data (History Mode) panel, but showing the transfer rate and the utilization of adapters for each session. The report is requested from the View Performance Data (History Mode) panel.
107
Figure 33. Performance Report - Graphical Presentation Section
108
Figure 34. Performance Report - Tabular Presentation Section
Prerequisites for Creating Reports

Creating reports in XML or HTML format is a function of the Administration Assistant. For requirements and a set-up procedure of the Administration Assistant, refer to Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77.
Creating a Report
Reports are requested from the Administration Assistant client using the graphical user interface panels containing the information to be included. Alternatively, reports can be generated from a scheduling client via a command line interface, not requiring any user interaction. Each report created is represented by an XML file, an HTML file and possibly one or more graphic files in SVG format. The HTML and the SVG files are displayed in the browser. All files created can be printed or saved to the local file system using the browser functionality. Additionally, reports, whether manually created or generated with templates, are stored temporarily for 24 hours on the Administration Assistant server in the following subdirectories:
<Administration Assistant install dir>/reports/<report type>_<time stamp>_<userid>/
File system access to the Administration Assistant server is required in order to access reports stored in the report cache.
109
Requesting a Report from the Administration Assistant Client

Administrators request reports by selecting the Create Report button on the panels Monitor Backup States, Backup State - Detailed View, View Performance Data (History Mode), and Available Simulation Results of the graphical user interface of the Administration Assistant client. Reports requested on panels Backup State - Detailed View, View Performance Data (History Mode), and Available Simulation Results always pertain to the single SID currently displayed on the panel. Reports requested from panel Monitor Backup States contain information on all SIDs displayed on the panel. Selections made in the table of systems do not have an impact on the report created. However, active filters or the activation of a display group is reflected in the report. For a report, the administrator can specify a time interval. Backup operations are included in the report if they ended within the specified time interval. Also, some reports allow requesting the inclusion of information on log files.
Working with Report Templates

Before a report can be generated without user interaction, for example by a scheduled script, a template must be created. Templates are created in the same way as reports are requested from the Administration Assistant panels: Whenever a button Create Report is pressed on an Administration Assistant panel the administrator can choose to create a report or the corresponding template. Each template must be given a unique name to be referenced when using the template. The template will be stored in a file with the given name in path
<Administration Assistant install dir>/templates/<userid>/
where
<Administration Assistant install dir>
is the installation path of the Administration Assistant server. The file extension depends on the type of report requested. A single template can be used to generate reports on several SIDs. A template is owned by the user creating it. It cannot be accessed or used from a different account. In order to view, change, or delete owned templates an administrator requests function Manage templates from the View pull-down menu of the Administration Assistant client.
Generating Reports Using Report Templates

Using Report Templates Administration Assistant reports can be started automatically at given points in time using your favorite scheduler. The scheduler must call the scheduler interface 'Sched_Main' which can be started from a scheduling client. For details on how to set up the scheduling client refer to 4. Setting Up a Scheduling Client for Reporting on page 87. The scheduling interface is called with the following syntax:
110
java -cp $CLASSPATH com.ibm.bkit.schedulerIF.Sched_Main <Server component hostname>... ... <RMI registry port> <template name> <userid> <password>... ... directory=<local directory> log=<log path>
where <Server component hostname> is the name or IP address of the host running the Administration Assistant Server component, <RMI registry port> is the number of the RMI registry port of the Administration Assistant Server component, as defined in its configuration file assist.cfg. The default is 1099. <template name> is the name of the appropriate report template to be used. It must be available in the users template path in the Administration Assistant Server component. <userid> is the Administration Assistant account of the templates owner <password> is the password of <userid>. <local directory> is the local path in the system of the scheduling client where the requested reports are to be stored. If the local directory is not specified the reports are not stored in the local file system. In order to access the report the administrator needs file system access to the Administration Assistant server where the report is kept for 24 hours. <log path> is the local path in the system of the scheduling client where the scheduling client saves its own log files. You may want to create a command file setting the correct environment and scheduling one or more reports on the scheduling client system. For sample files refer to Sample Command Files for Scheduling Reports on page 195.
Note If a large number of clients try to connect to the Administration Assistant server simultaneously, some of them may not get a connection immediately. In this case, the scheduling client waits for a random time between 15 and 45 seconds before it tries again. After the second unsuccessful retry, the scheduling client writes an error log and exits.
Modifying Report Output

All report requests result in the information being written to an XML file. Style sheets residing with the Administration Assistant Server component are used to translate the information contained in this file to different types of reports in HTML or SVG format. They determine the appearance and contents of a specific report. The Administration Assistant comes with a number of built-in style sheets that are used to create the different types of reports described above. However, administrators may customize the style sheets to modify the look and content of the HMTL files. To generate a report at least one report-specific style sheet for the transformation from XML to HTML format is necessary. If a report contains graphics each graphic is transformed to an SVG file, requiring a separate style sheet. In this case a single report needs a set of style sheets.
111

The Administration Assistant provides two types of style sheet file sets. One set is contained in file Admt.jar and will be used as default. The second set of style sheet set resides on the Administration Assistant server in directory:
<Admin. Assistant install dir>/styles/
Report content and appearance can be customized according to customer needs by changing the style sheet files in this subdirectory appropriately. The styles directory currently contains four subdirectories ('Overview', 'Detailed', 'History', 'Simulation') specifying reports based on different XML data sources, based on data provided in the corresponding Administration Assistant panels Monitor Backup States, Backup State Detailed View, and View Performance Data (History Mode). The names of these folders are displayed in the list of selectable report types within the Create Report dialogs. Style sheet names must be of the format:
<report_name>_<file format>.xsl
where <file format> denotes the file type, one of HTML or SVG, <report name> denotes the name of the file to be created. For example, Picture1_svg.xsl will generate a file named Picture1.svg. Please note: The name of the HTML file must always be 'report'! For every report type an additional file config.xml exists in the 'styles' subdirectory. This file specifies default settings of the Create Reports dialogs. For example, the Operations Daily Report has a reporting interval of 24 hours. Therefore the end of the time frame does not need to be specified, and the corresponding button will be hidden. All style sheets contained either in file Admt.jar or in the styles directory are displayed for selection in the Create Report dialogs of the Administration Assistant. Style sheets contained in Admt.jar are marked by the addition '(built-in)'. When starting the report generation the customer can specify which style sheet set to be used. If the customizable style sheets are used, the phrase customized style sheets used is shown on the corresponding reports.
112
Part 3. Appendixes
113
114
Appendix A. The Data Protection for SAP Profile

This section describes the Data Protection for SAP profile, which is used to customize the way Data Protection for SAP operates. A sample profile initSID.utl is provided on the installation medium. During installation, the profile is also copied to the profile path if no other profile exists there. The setup for Windows puts all files in an initial setup sub-directory (the default is C:\Program Files\Tivoli\TDP4SAP for Tivoli Storage Manager). The sample profile is found there. Before execution, Data Protection for SAP reads the profile pointed to by environment variable XINT_PROFILE (shared library, BackOM ) or passed as a parameter (BackOM). The following rules apply to the syntax: v Each line is analyzed separately. v Keywords can start in any column of the line. v Keywords must not be preceded by any string, except blanks. v If a keyword is encountered several times, the last one is used. v File processing ends when the END keyword is encountered or the end of file is reached. v The comment symbol is #. Scanning of the current line stops when the comment symbol is encountered. No comment is allowed between the keyword and the value(s). For example:
#BRARCHIVEMGTCLASS MLOG1 BRARCHIVEMGTCLASS MLOG1 BRARCHIVEMGTCLASS # MLOG1 # <-<-<-correct correct WRONG
A few keywords are required in any case, but most are optional. Each of the optional keywords has a preset default value.
Keyword Reference
Note: In the following descriptions, the default value is underlined and applies if the parameter is not specified. ADSMNODE node_name This keyword must not be set when automated password handling is selected. It should be set for manual password handling (see Modifying the Handling of the TSM Password on page 43). If specified, node_name must be registered to the Tivoli Storage Manager server as a Tivoli Storage Manager node. With this option you can assign a different node name to your database system. It should be used if you have several SAP DB2 database systems in your network with the same name, for example, <SID>, and they all use the same Tivoli Storage Manager server.
115
The Data Protection for SAP Profile
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in the sample profile. BACKEND pgmname [parameterlist] Specifies a program pgmname that is called by Data Protection for SAP after the backup function completed and before program control is returned to DB2. If pgmname is not fully qualified the default search path is used to find the program. If not specified, no backend processing is done. Example (for UNIX or Linux):
BACKEND write operator@remotesite Backup of SAP database object completed.
This sends a message to a remote user when the backup has finished. BACKUPIDPREFIX 6-charstring | SAP___ Specifies a 6-character prefix that is used to build a backup identifier for each archived object. All partitions of a partitioned DB2 database should have the same BACKUPIDPREFIX. BRARCHIVEMGTCLASS management_class [management_class...] Specifies the Tivoli Storage Manager management class(es) DP for SAP uses to back up offline DB2 log files. Each parameter string can consist of up to 30 characters. Specify a separate BRARCHIVEMGTCLASS for each log file copy requested. Therefore, the number of different BRARCHIVE management classes specified must be greater than or equal to the number of log file copies (keyword REDOLOG_COPIES on page 119.
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in the sample profile. BRBACKUPMGTCLASS management_class [management_class...] Specifies the Tivoli Storage Manager management class(es) DP for SAP uses to back up the DB2 database. The parameter string can consist of up to 30 characters.
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in the sample profile. BUFFCOPY SIMPLE|PREVENT|AUTO This optional parameter controls how DP for SAP uses the internal buffers for transferring data during a backup. If set to SIMPLE data buffers are copied when they are passed on between Tivoli Storage Manager components. This is the default.
116

If set to PREVENT the original data buffers are passed on between Tivoli Storage Manager components. For this mode, BUFFSIZE is restricted to a maximum of 896 KB. Furthermore, it cannot be selected while the Tivoli Storage Manager client encryption and / or client compression are activated. If set to AUTO Data Protection for SAP will run in PREVENT mode whenever the configuration supports it. Otherwise, SIMPLE mode will be selected automatically. This parameter has no effect on restore operations. BUFFSIZE n|131072 This parameter specifies the block size (in bytes) for the buffers used for the communication with DB2. The size of the buffers passed to the Tivoli Storage Manager API functions is the value of BUFFSIZE increased by approximately 20 Bytes. The valid range is from 4096 (4 KB) to 32 MB. Inappropriate values will be adjusted automatically. If BUFFCOPY is set to PREVENT the value of BUFFSIZE must not exceed 896 KB. If not specified, the default value is 131072 (128 KB) for UNIX or Linux systems and 32768 (32 KB) for Windows systems. In most cases, these values are appropriate. If you plan to increase the size of internal buffers make sure that sufficient storage is available. The number of buffers acquired by Data Protection for SAP correlates to the number of sessions (keyword SESSIONS). By activating RL_COMPRESSION the number of buffers is doubled. CONFIG_FILE <path>/%DB2NODE/init<SID>.bki Specifies the configuration file (init<SID>.bki)for DP for SAP to store all variable parameters such as passwords, date of last password change, and the current version number. A single CONFIG_FILE should never be shared among multiple database instances or partitions. Otherwise backup version control may not be working correctly. During processing, the string %DB2NODE is replaced automatically by the current DB2 node of a partitioned database or by NODE0000 otherwise. This parameter is required. END Specifies the end of the parameter definitions. DP for SAP stops searching the file for keywords when END is encountered.
FRONTEND pgmname [parameterlist] Specifies a program pgmname that is called by Data Protection for SAP in a backup run before the connection to the Tivoli Storage Manager server is established. If pgmname is not fully qualified the default search path is used to find the program. If not specified, no front-end processing is done. Example (for UNIX or Linux):
FRONTEND write operator@remotesite Backup of SAP database object is starting.
This sends a message to a remote user before backup begins. LOG_SERVER servername [verbosity] servername specifies the name of the Tivoli Storage Manager server to send
117

log messages to. The name must match one of the servers listed in a SERVER statement, if you want DP for SAP messages logged in the activity log of the TSM server. verbosity may be any one of the following: ERROR, WARNING, or DETAIL. This value determines which messages are sent. The default value is WARNING, which means that error and warning messages are sent. ERROR sends only error messages. DETAIL sends all message types (errors, warnings, and informational messages). Note that this feature is available only with Tivoli Storage Manager client and server Version 3 or higher. If there is no LOG_SERVER statement in the profile, log messages are not sent to any of the Tivoli Storage Manager servers. MAX_SESSIONS n Specifies the maximum number of parallel Tivoli Storage Manager client sessions that DP for SAP establishes For a direct backup/restore on tape drives, keep the following in mind: the number of sessions must be less than or equal to the number of tape drives available for the backup. Note: Make sure class is set Make sure number of that the mountlimit (mountl) parameter in the device to the number of available tape drives. that the maxnummp parameter of the node is set to the available tape drives.
This keyword is required.
Keep in Mind The value of keyword MAX_SESSIONS must be less than or equal to the sum of the SESSIONS values specified in the SERVER statements of the currently available servers. MAX_VERSIONS n|0 n defines the maximum number of database backup versions to be kept in backup storage. The default setting for this value is 0, meaning that backup version control is disabled. Every time a full backup completes successfully, the version count is incremented by 1 and stored in the DP for SAP configuration file. This value is also assigned to the tablespace files and to all subsequent DB2 log file backups. If the number of versions kept in backup storage is larger than the specified maximum number of backup versions (stored in the parameter MAX_VERSIONS), the oldest version is deleted, together with the corresponding tablespace, incremental and log file backups until only the specified maximum number of most recent versions remain. For partitioned DB2 databases, backup version control is done on a partition basis. Therefore, full backups should always be initiated for all partitions at the same time, for example by the DB2 script db2_all. For details on the db2_all script, see your DB2 documentation.
118
Notes v Partial backups get the same version number as the last successful full backup. When DP for SAP deletes an old full backup, all partial backups with the same version number are also deleted. v Every database instance needs its own configuration file (see parameter CONFIG_FILE) and a unique BACKUPIDPREFIX. v Every database partition needs its own configuration file. Partitions of a partitioned database should have the same BACKUPIDPREFIX.
CAUTION Tivoli Storage Manager uses the value of the parameter RETVER specified when defining a copy group (see 3. Policy Definition on page 205) to give files an expiration date. If you use Data Protection for SAP backup version control, you need to bypass this expiration function. If you use the Tivoli Storage Manager expiration function, you need to turn off DP for SAP backup version control. Use only one of these methods to control how long you keep backups. If you use Data Protection for SAP backup version control, set the Tivoli Storage Manager parameter RETVER=9999 so that the files are not considered expired and are not deleted by Tivoli Storage Manager. If you use Tivoli Storage Manager expiration, deactivate DP for SAP backup version control by setting MAX_VERSIONS=0. PASSWORDREQUIRED NO|YES Specifies if Tivoli Storage Manager requires a password to be supplied by the Tivoli Storage Manager client. This depends on the Tivoli Storage Manager installation. For more information see the Tivoli Storage Manager administrators manuals and Modifying the Handling of the TSM Password on page 43. If not specified, the default is PASSWORDREQUIRED YES, implementing manual password handling.
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in the sample profile. REDOLOG_COPIES n|1 Specifies the number of copies DP for SAP stores for each processed DB2 log file. The valid range is from 1 to 9. If not specified, DP for SAP stores one copy of each log file.
119
Note The number of different BRARCHIVE management classes (keyword BRARCHIVEMGTCLASS on page 116) specified must be greater than or equal to the number of log file copies specified. RL_COMPRESSION NO|YES If set to YES, Data Protection for SAP performs a null block compression of the data before they are sent over the network. Although RL compression introduces additional CPU load, throughput can be improved when the network is the bottleneck. It is not recommended to use RL compression together with the Tivoli Storage Manager API compression. If not specified, the default value is NO meaning null block compression is not performed.
Note RL_COMPRESSION is only performed if a full database backup was started. The offline log files are not compressed SERVER servername Denotes the name of the Tivoli Storage Manager server to which a path will be established. This statement starts a server section in the Data Protection for SAP profile. At least one server section is required. Server sections are located at the end of the profile. A server section ends before a following SERVER keyword, before the END keyword, or at the end of the profile. The following dependent keywords may appear in a server section: ADSMNODE, BRARCHIVEMGTCLASS, BRBACKUPMGTCLASS, PASSWORDREQUIRED, SESSIONS, TCP_ADDRESS, and USE_AT. The server name must be defined in the Tivoli Storage Manager profiles dsm.sys ( UNIX and Linux ) or <servername.opt> (for Windows). In order to set up alternate or parallel paths, each path is denoted by its own logical server name and corresponding server section, although these logical names refer to the same server. In this case, the TSM profiles specify the same TCP/IP address for these server names. In order to set up alternate or parallel servers, each server is represented by one or more server statements and the corresponding server sections (depending on the number of paths to the server). In this case, the TSM profiles specify different TCP/IP addresses for the different servers. Different server names result in different server entries in the View TSM Server Utilization function of the Administration Assistant, while identical server names are considered to point to the same TSM server even if they are specified in different Data Protection for SAP profiles throughout the system landscape.
| | | | |
Note Do NOT use any profile keywords or ADSM or TSM as the servername.
120

SESSIONS n|1 n specifies the number of parallel sessions DP for SAP can start for this server. This keyword is required in every server section.
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in the sample profile. TCP_ADDRESS ip address of server Specifies the IP address of this Tivoli Storage Manager server in dotted decimal notation. This parameter overrides the value for the parameter TCPSERVERADDRESS in the Tivoli Storage Manager client system options file (dsm.sys) on UNIX or Linux or in the client options file (<servername>.opt ) on Windows.
Note The parameter TCP_ADDRESS can only be used with Tivoli Storage Manager API Version 5.2 or higher.
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in the sample profile. TRACE FILEIO_MIN | FILEIO_MAX | COMPR_MIN | COMPR_MAX | MUX_MIN | MUX_MAX | TSM_MIN | TSM_MAX | ASYNC_MIN | ASYNC_MAX | APPLICATION_MIN | APPLICATION_MAX | SYSCALL_MIN | SYSCALL_MAX | COMM_MIN | COMM_MAX | DEADLOCK_MIN | DEADLOCK_MAX | PROLE_MIN | PROLE_MAX | BLAPI_MIN | BLAPI_MAX | SOCKET_DATA | ALL | OFF If the parameter TRACE is specified, DP for SAP writes a trace to the file specified with the parameter TRACEFILE. Arguments to TRACE can be any combination of the possible components and levels separated by spaces. A trace will only be written if both TRACE and TRACEFILE are specified.
Note Do not use this parameter unless your DP for SAP support asks you to. Using it can significantly degrade the performance of DP for SAP. TRACEFILE path Specifies the trace file for DP for SAP to store all trace information (if TRACE ON), path specifies the full path and the name of file.
121
Note If the value of TRACEFILE contains the string %BID this string is replaced by the backup ID to get the path and name of the trace file actually used. For example, specifying /tmp/%BID.trace will yield a trace file /tmp/myBackup.trace for backup ID myBackup. A trace will only be written if both TRACE and TRACEFILE are specified. TRACEMAX n Denotes the maximum size of the trace file in KB. If not specified, the trace file size is unlimited. USE_AT days Specifies on which days the Tivoli Storage Manager server named with the corresponding SERVER keyword will be used. days are numbers from 0 (Sunday) to 6 (Saturday). You may list several numbers, separated by spaces. If not specified, the default is to use the Tivoli Storage Manager server on all days.
Keep in Mind This parameter must be defined in conjunction with the respective SERVER statement, as shown in Example 3: Use of Alternate Servers for Disaster Recovery on page 188. The parameter USE_AT has no effect on actions other than backup.
Sample Data Protection for SAP Profiles

The sample profile (initSID.utl) is included in the DP for SAP installation package. Although the UNIX or Linux and Windows versions are mostly identical we still show both versions below.
Sample Data Protection for SAP Profile for UNIX or Linux

| | | | | | | | | | | | | | | | | | | | | | |
#-------------------------------------------------------------------------# # Data Protection for SAP (R) interface for DB2 UDB # # Sample profile for Data Protection for SAP (R) Version 5.5 # #-------------------------------------------------------------------------# # See the Data Protection for SAP (R) Installation & # Users Guide for a full description. # # For a comment symbol the character # can be used. # Everything following this character will be interpreted as comment. # # Data Protection for SAP (R) accesses its profile # in "read only" mode. All variable parameters like passwords, date of # last password change, current version number will be written into the file # specified with the CONFIG_FILE parameter. The passwords will be encrypted. #-------------------------------------------------------------------------# Prefix of the Backup ID which is used for communication with # the SAP-DB2 Administration Tools and stored in the description field of
122

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
# the Tivoli Storage Manager archive function. # Maximum 6 characters. # Default: none. #-------------------------------------------------------------------------BACKUPIDPREFIX SID___ #-------------------------------------------------------------------------# Number of parallel sessions to be established. # Note: This number must not exceed the number of tape drives simultaneously # available to the node on the Tivoli Storage Manager servers to be accessed. # The valid range of MAX_SESSIONS is from 1 and 32. # Default: none. #-------------------------------------------------------------------------MAX_SESSIONS 1 # Tivoli Storage Manager client sessions #-------------------------------------------------------------------------# Number of backup copies of the DB2 log files. # The valid range of REDOLOG_COPIES is from 1 to 9. # Default: 1. #-------------------------------------------------------------------------#REDOLOG_COPIES 2 #-------------------------------------------------------------------------# Specifies the block size for disk I/O (in bytes). # The default values have been chosen from our performance experiments in # standard hardware environments. # The valid range of BUFFSIZE is from 4KB to 32MB. # Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows. #-------------------------------------------------------------------------BUFFSIZE 131072 # block size in bytes #-------------------------------------------------------------------------# This optional parameter controls how Data Protection for SAP(R) uses # the internal buffers for transferring data during a backup. # Valid values: SIMPLE | PREVENT | AUTO # Default: SIMPLE #-------------------------------------------------------------------------#BUFFCOPY AUTO #-------------------------------------------------------------------------# Name of a program to be called before the backup task is started. # Default: none. #-------------------------------------------------------------------------#FRONTEND pgmname parameterlist #-------------------------------------------------------------------------# Name of a program to be called after the backup task is completed. # Default: none. #-------------------------------------------------------------------------#BACKEND pgmname parameterlist #-------------------------------------------------------------------------# Maximum number of data base backup versions to be kept. # Note: Version control by Data Protection for SAP (R) is only activated # only activated if the parameter MAX_VERSION is not 0. # The valid range of MAX_VERSIONS is from 0 to 9999. # A value of 0 means no versioning. # Default: 0, no versioning. #-------------------------------------------------------------------------#MAX_VERSIONS 4 #-------------------------------------------------------------------------# Specifies whether a null block compression of the data is to be performed # before transmission to Tivoli Storage Manager.
123

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
# Although RL compression introduces additional CPU load, throughput can be # improved when the network is the bottleneck. RL compression in Data # Protection for SAP(R) should not be used together with # Tivoli Storage Manager API compression. # Default: NO #-------------------------------------------------------------------------#RL_COMPRESSION YES # NO is default #-------------------------------------------------------------------------# Controls generation of a trace file. # Note: We recommend using the trace function only in cooperation with # Data Protection for SAP (R) support. # Default: OFF. #-------------------------------------------------------------------------#TRACE OFF #TRACEFILE /db2/C21/sqllib/log/tdpr3.trace #-------------------------------------------------------------------------# Denotes the maximum size of the trace file in KB. # If not specified, the trace file size is unlimited. #-------------------------------------------------------------------------#TRACEMAX <max. size> # trace file size in KB #-------------------------------------------------------------------------# Specify the full path of the configuration file. # Default: none. #-------------------------------------------------------------------------CONFIG_FILE /db2/C21/sqllib/%DB2NODE/initSID.bki #-------------------------------------------------------------------------# Denotes if Data Protection for SAP (R) shall send error/status # information to a Tivoli Storage Manager server. # The servername must match one of the servers listed in a SERVER statement. # Valid values for verbosity are ERROR | WARNING | DETAIL. # Default: none. #-------------------------------------------------------------------------#LOG_SERVER servername [verbosity] #LOG_SERVER server_a ERROR #************************************************************************** # Statement for servers and paths. # Multiple servers may be defined. #************************************************************************** SERVER SESSIONS # Servername, as defined in dsm.sys # Maximum number of sessions # to server_a PASSWORDREQUIRED YES # Use a password ADSMNODE NODE # Tivoli Storage Manager Nodename BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup # TCP_ADDRESS 192.168.1.1 # IP address of network interface # on server_a # Overrides IP address of dsm.sys # USE_AT 0 1 2 3 4 5 6 # Days when server_a is used for # backup #************************************************************************** # USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa # The valid range of USE_AT is from 0 to 6. # Default: all days #************************************************************************** #SERVER # SESSIONS server_b 2 YES NODE # # # # # Servername, as defined in dsm.sys Maximum number of sessions to server_b Use a password Tivoli Storage Manager Nodename server_a 2
# PASSWORDREQUIRED # ADSMNODE
124

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
# BRBACKUPMGTCLASS # BRARCHIVEMGTCLASS # TCP_ADDRESS # Mgmt-Classes for database backup # Mgmt-Classes for redo log backup # IP address of network interface # on server_b # Overrides IP address of dsm.sys # USE_AT 0 1 2 3 4 5 6 # Days when server_b is used for # backup #************************************************************************** # USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa # Default: all days #************************************************************************** MDB MLOG1 MLOG2 192.168.1.1
#-------------------------------------------------------------------------# End of profile END
Sample Data Protection for SAP Profile for Windows

#-------------------------------------------------------------------------# # Data Protection for SAP (R) interface for DB2 UDB # # Sample profile for Data Protection for SAP (R) # Version 5.5 for Windows 2000/2003 # #-------------------------------------------------------------------------# # See the Data Protection for SAP (R) Installation & Users Guide for # a full description. # # For a comment symbol the character # can be used. # Everything following this character will be interpreted as comment. # # Data Protection for SAP (R) accesses its profile in "read only" mode. # All variable parameters like passwords, date of last password # change, current version number will be written into the file specified # with the CONFIG_FILE parameter. The passwords will be encrypted. #-------------------------------------------------------------------------# Prefix of the Backup ID which is used for communication with the # SAP-DB2 Administration Tools and stored in the description field of the # Tivoli Storage Manager archive function. # Must be 6 characters. # Default: none. #-------------------------------------------------------------------------BACKUPIDPREFIX SID___ #-------------------------------------------------------------------------# Number of parallel sessions to be established. # Note: This number must not exceed the number of tape drives simultaneously # available to the node on the Tivoli Storage Manager servers to be accessed. # The valid range of MAX_SESSIONS is from 1 and 32. # Default: none. #-------------------------------------------------------------------------MAX_SESSIONS 1 # Tivoli Storage Manager client sessions #-------------------------------------------------------------------------# Number of backup copies of the DB2 log files. # The valid range of REDOLOG_COPIES is from 1 to 9. # Default: 1. #-------------------------------------------------------------------------#REDOLOG_COPIES 2
125

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
#-------------------------------------------------------------------------# Specifies the block size for disk I/O (in bytes). # The default values have been chosen from our performance experiments in # standard hardware environments. # The valid range of BUFFSIZE is from 4KB to 32MB. # Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows. #-------------------------------------------------------------------------BUFFSIZE 32768 # block size in bytes #-------------------------------------------------------------------------# This optional parameter controls how Data Protection for SAP(R) uses # the internal buffers for transferring data during a backup. # Valid values: SIMPLE | PREVENT | AUTO # Default: SIMPLE #-------------------------------------------------------------------------#BUFFCOPY AUTO #-------------------------------------------------------------------------# Name of a program to be called before the backup task is started. # Default: none. #-------------------------------------------------------------------------#FRONTEND pgmname parameterlist #-------------------------------------------------------------------------# Name of a program to be called after the backup task is completed. # Default: none. #-------------------------------------------------------------------------#BACKEND pgmname parameterlist #-------------------------------------------------------------------------# Maximum number of data base backup versions to be kept. # Note: Version control by Data Protection for SAP (R) is # only activated if the parameter MAX_VERSION is not 0. # The valid range of MAX_VERSIONS is from 0 to 9999. # Default: 0 #-------------------------------------------------------------------------#MAX_VERSIONS 4 #-------------------------------------------------------------------------# Specifies whether a null block compression of the data is to be performed # before transmission to Tivoli Storage Manager. # Although RL compression introduces additional CPU load, throughput can be # improved when the network is the bottleneck. RL compression in Data # Protection for SAP(R) should not be used together with # Tivoli Storage Manager API compression. # Default: NO #-------------------------------------------------------------------------#RL_COMPRESSION YES #-------------------------------------------------------------------------# Controls generation of a trace file. # Note: We recommend using the trace function only in cooperation with # Data Protection for SAP (R) support. # Default: OFF #-------------------------------------------------------------------------#TRACE OFF #TRACEFILE c:\sqllib\tdp_r3\log\tdpr3.trace #-------------------------------------------------------------------------# Denotes the maximum size of the trace file in KB. # If not specified, the trace file size is unlimited. #-------------------------------------------------------------------------#TRACEMAX <max. size> # trace file size in KB #--------------------------------------------------------------------------
126

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
# Specify the full path of the configuration file. # Default: none. #-------------------------------------------------------------------------CONFIG_FILE c:\sqllib\tdp_r3\%DB2NODE\initSID.bki #-------------------------------------------------------------------------# Denotes if Data Protection for SAP (R) shall send # error/status information to a Tivoli Storage Manager server. # The servername must match one of the servers listed in a SERVER statement. # Valid values for verbosity are ERROR | WARNING | DETAIL. # Default: none. #-------------------------------------------------------------------------#LOG_SERVER servername [verbosity] #LOG_SERVER server_a ERROR #************************************************************************** # Statement for servers and paths. # Multiple servers may be defined. #************************************************************************** SERVER SESSIONS # Servername, as defined in dsm.sys # Maximum number of sessions # to server_a PASSWORDREQUIRED YES # Use a password ADSMNODE NODE # Tivoli Storage Manager Nodename BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup # TCP_ADDRESS 192.168.1.1 # IP address of network interface # on server_a # Overrides IP address of dsm.sys # USE_AT 0 1 2 3 4 5 6 # Days when server_a is used for # backup #************************************************************************** # USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa # The valid range of USE_AT is from 0 to 6. # Default: all days #************************************************************************** #SERVER # SESSIONS # Servername, as defined in dsm.sys # Maximum number of sessions # to server_b # PASSWORDREQUIRED YES # Use a password # ADSMNODE NODE # Tivoli Storage Manager Nodename # BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup # BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup # TCP_ADDRESS 192.168.1.1 # IP address of network interface # on server_b # Overrides IP address of dsm.sys # USE_AT 0 1 2 3 4 5 6 # Days when server_b is used for # backup #************************************************************************** # USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa # Default: all days #************************************************************************** #-------------------------------------------------------------------------# End of profile END server_b 2 server_a 2
127
128
Appendix B. Data Protection for SAP (DB2) Messages

This chapter describes how to find message files (log files) and explains the individual messages issued by DP for SAP.
How To Find Files Containing Message Output (Log Files)

Data Protection for SAP process results are logged in files. These files are located in the path indicated by the environment variable TDP_DIR. After the installation, TDP_DIR points to the subdirectory tdplog of the path for the DP for SAP configuration files. If TDP_DIR is not set or if a log file cannot be created in the path pointed to by TDP_DIR, the log files are created in path /tmp (UNIX or Linux) or in the path pointed to by environment variable TEMP (Windows). For information on how to set or change the value of TDP_DIR, refer to Installing Data Protection for SAP on page 24. The following log files are written: v by the Data Protection for SAP shared library: tdpdb2.<SID>.<node name>.log v by the Backup Object Manager: backom.log
129
Messages
Prefix BKI
The messages begin with the prefix BKI and are listed in numerical order. For each message, the following information is provided: v Message number v Severity code The following letters give an indication of the severity of the action that generated the message. The severity codes and their meanings are as follows:
E W I Error Warning Information Processing cannot continue. Processing can continue, but problems may occur later. Processing continues. User response is not necessary.
v Explanation v User Response

BKI0000E Profile not specified. Explanation: The time needed for the complete backup was elapsedtime. User response: None. BKI0023I Time: current_time Done: saved_bytes (percent) of bytes Estimated end time: end_time
Explanation: Cannot locate the profile. User response: Ensure that a profile is available. (Oracle) Note that the BACKINT call must have the following form: backint -p init<SID>.utl . BKI0005I Start of program at: time
Explanation: DP for SAP received control from a BR*Tools utility at the time denoted. User response: None. BKI0007E Mode mode requires the environment variable environment variables to be set.
Explanation: Finished saving a specific object at current_time. The saved_bytes amount of the total number of bytes have been saved. percent shows the percentage. This call will be completed at the estimated end_time. User response: None. BKI0024I Return code is: return code
Explanation: Not all environment variables required have been set. At least environment variables where missing. User response: Set the missing environment variables. BKI0008E The environment variable name is not set correctly. The current value is value.
Explanation: A return code of 0 means no errors or warnings occurred. If the return code is 1, at least one warning was issued by the program. If the return code is 2, at least one error message was issued. User response: For return codes other than 0, check the run log for warnings or error messages. BKI0027I Time: current_time Objects: current_num of total_num in process: file_name MGMNT-CLASS: management_class TSM Server: server name.
Explanation: The value of the environment variable name is wrong. User response: Set name to an appropriate value. BKI0020I End of program at: time
Explanation: (Oracle) DP for SAP returned control to a BR*Tools utility at the time denoted. (DB2) Program tdppasswd ended at the time indicated. User response: None. BKI0021I Elapsed time: elapsedtime
Explanation: DP for SAP started saving current_num files at current_time. The total number of files to save is total_num. The file file_name is currently being processed. The files are transferred to the Tivoli Storage Manager server server name, which stores them in the management class management_class. User response: None.
130
Messages
BKI0032E Error opening file file name: system error description BKI0054I Time: current_time Objects: current_num of total_num done: file_name with: bytes restored with description object_desc.
Explanation: A system error occurred during opening of the file file name. system error description will describe the error in more detail. User response: Read the system error description. BKI0049I Please enter password for node nodename on server server name
Explanation: DP for SAP completed restoring of current_num file at current_time. The total number of files to be restored is total_num. The file file_name with the size bytes is restored with the description object_class. User response: None. BKI0055I Object objectname with size saved with description description.
Explanation: The password for the node nodename on the Tivoli Storage Manager server server name has to be entered for storing it in the DP for SAP configuration file. User response: Enter the password for the corresponding Tivoli Storage Manager server. BKI0050I Please enter password for node nodename on server server name again
Explanation: The object objectname was saved successfully. User response: None. BKI0056I Object objectname with size restored with description description.
Explanation: In order to avoid typing errors, you have to enter the password twice. User response: Enter the password again. BKI0051I Password successfully verified for node nodename on server server name.
Explanation: The object objectname was restored successfully. User response: None. BKI0057I Time: current_time Object objectname with size saved with description description.
Explanation: The password for the node nodename on the Tivoli Storage Manager server server name was changed successfully. User response: None. BKI0052E Password verification for node nodename on server server name failed.
Explanation: The object objectname was saved successfully. User response: None. BKI0058I Time: current_time Object objectname with size restored with description description.
Explanation: The password you entered for the node nodename on the Tivoli Storage Manager server server name was wrong. User response: Enter the password again. If this error still exists, contact your Tivoli Storage Manager administrator. BKI0053I Time: current_time Objects: current_num of total_num done: file_name with: bytes saved with description object_desc.
Explanation: The object objectname was restored successfully. User response: None. BKI0059E You have to set the environment variable DSMI_CONFIG to the full filename of the Tivoli Storage Manager client option file dsm.opt.
Explanation: Tivoli Storage Manager client option file not found. User response: Verify that the Tivoli Storage Manager option file dsm.opt is pointed to by DSMI_CONFIG. BKI0060E The parameter parameter is not known.
Explanation: DP for SAP completed saving current_num file at current_time. The total number of files to be saved is total_num. The file file_name with the size bytes is saved with the description object_desc. User response: None.
Explanation: The command parameter parameter is unknown. User response: Check the specified command parameter and try again.
131
Messages
BKI0063E The UTL file file name is not valid. BKI0454I *** This copy is NOT FOR RESALE. ***
Explanation: Unable to read the input file file name correctly. User response: Check the path and name of the profile (UTL file) and the appropriate file access permission. BKI0064E The option option is unknown.
Explanation: This version is not for resale. User response: None. BKI0455E License file file name does not exist.
Explanation: The license file agent.lic was not found where expected. User response: Make sure that the agent.lic file resides in the same directory as the init<SID>.utl file. BKI0456E Unable to access license file file name.
Explanation: An option is invalid or unknown. User response: Check the specified option(s) and try again. BKI0065E The argument is missing for option option.
Explanation: The license file could not be accessed. User response: Make sure the access permissions allow read/write access. BKI0457E License file file name contains invalid data/checksum.
Explanation: Every option requires an argument. User response: Insert the missing argument and try again. BKI0101I Session session: Please enter cont to continue or stop to cancel.
Explanation: The license file is invalid. User response: Make sure you have the right agent.lic file for the right platform installed. agent.lic files are platform dependent. BKI1000E Syntax error in line line: statement
Explanation: If DP for SAP is running in unattended mode (profile keyword BATCH), it terminates the current run if operator intervention is required. User response: Enter cont or stop. BKI0102I Your reply: reply.
Explanation: The statement statement in the DP for SAP profile is unknown or incorrect. User response: Correct the error and try again. BKI1001E Syntax error in file file name. Exiting Program.
Explanation: The reply you made is confirmed. User response: None. BKI0311E Request canceled by user.
Explanation: (Oracle) BACKINT terminated at users request. (DB2) Program terminated at users request. User response: None BKI0452E This version of product has expired.
Explanation: A syntax error has been detected in the file file name and the action has been halted. User response: Correct the error(s) in the file file name and try again. BKI1002E BACKUPIDPREFIX must be number_of_characters characters.
Explanation: This is a test version that has expired. User response: Order a release version of the product or contact your IBM/Tivoli Sales Representative. BKI0453W This version of product will expire in number days.
Explanation: The length of BACKUPIDPREFIX must be number_of_characters characters. User response: Enter a BACKUPIDPREFIX with the required length (e.g., SAP___, BKI___). BKI1003W Please set REDOLOG_COPIES to a number between 1 and max_copies. Now it is set to act_copies.
Explanation: This is a test version with a time limit. It will expire in number days. User response: Order a release version of the product or contact your IBM/Tivoli Sales Representative before the version expires.
Explanation: DP for SAP currently supports 1 to 9 copies of offline (redo) log files. User response: Adapt the REDOLOG_COPIES settings in the DP for SAP profile.
132
Messages
BKI1004W You should specify the BACKUPIDPREFIX before the TRACEFILE statement, so that the BACKUPIDPREFIX can be used in the tracefile name. BKI1010W The configfile name configuration_filename should be absolute.
Explanation: None. User response: Specify an absolute file name, for example /oracle/C21/dbs/initC21.bki or /db2/C21/dbs/initC21.bki BKI1012E Configfile not found or permission denied: configuration_filename.
Explanation: The BACKUPIDPREFIX is used to build the Name of the tracefile. Therefore, BACKUPIDPREFIX must be specified before the TRACEFILE statement. User response: Define a 6-character BACKUPIDPREFIX in the DP for SAP profile (e.g., SAP___, BKI___) BKI1005W The tracefile name trace_filename should be absolute.
Explanation: DP for SAP is unable to read the file configuration_filename. User response: This error could have various reasons, try the following: 1. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE). 2. Make sure that the file access permissions are set correctly. BKI1013E Profile not found or permissions denied: profile_filename.
Explanation: None. User response: Specify an absolute tracefile name, for example /oracle/C21/saptrace/tracefile or /db2/C21/saptrace/tracefile . BKI1006E The SERVERNAME must be less than max_char characters.
Explanation: You have used a SERVERNAME with more than max_char characters. User response: Use a shorter SERVERNAME. BKI1007E The NODENAME must be less than max_char characters.
Explanation: DP for SAP is unable to open the profile profile_filename. User response: (Oracle) Ensure that the SAP backup profile init<SID>.sap contains a valid entry util_par_file for the DP for SAP profile. (DB2) Ensure that the vendor environment file contains a valid entry XINT_PROFILE. Furthermore, this file must be readable by DP for SAP. For details see Installing Data Protection for SAP on page 24 and Problem Resolution During Installation and Setup on page 165. BKI1016W The trace file name file name could not be opened for writing!
Explanation: You have used a NODENAME with more than max_char characters. User response: Use a shorter NODENAME. BKI1008E The MANAGEMENTCLASSNAME must be less than max_char characters.
Explanation: You have used a MANAGEMENTCLASSNAME with more than max_char characters. User response: Use a shorter MANAGEMENTCLASSNAME. BKI1009W Please set MULTIPLEX to a number between 1 and max_multiplex. Now it is set to act_multiplex.
Explanation: The trace file could not be opened for writing. User response: Ensure that you have specified a correct path for the trace file. BKI1019E Failed to respond to a message received from XINT.
Explanation: This messages indicates an internal error. User response: Contact DP for SAP support. BKI1020W The compress info file file name should be absolute !
Explanation: You have set multiplexing to an unsupported number. DP for SAP now uses act_multiplex. User response: Set multiplexing to a number between 1 and max_multiplex.
Explanation: The argument for the parameter COMPR_INFO in the profile is an relative filename. User response: Always use an absolute filename as argument for the parameter COMPR_INFO.
133
Messages
BKI1021E component_name terminates the connection due to a previous error. BKI1203E Not enough sessions available (number of sessions required and number of sessions available).
Explanation: A serious error has occurred which caused a shutdown of the communication channel between the component_name process and this application. User response: Look for previous error messages to detect the root cause of the problem. BKI1022E component_name terminates the connection due to a previous error.
Explanation: The sum of available sessions specified in the various server statements (parameter SESSIONS) does not cover the required number of sessions (parameter MAX_SESSIONS). User response: Change the values of the corresponding parameters in the DP for SAP profile, so that the condition mentioned in the explanation is fulfilled. BKI1205E If you want num_redo REDOLOGCOPIES on Tivoli Storage Manager-Server servername, you should give me at least num_mc different Archive Management Classes.
Explanation: See message BKI1021E. User response: See message BKI1021E. BKI1023W Could not establish connection to log server log server name.
Explanation: In the DP for SAP profile, log server log server name is specified (keyword LOG_SERVER). However, a connection to the server named could not be established. No log records are sent to the log server. User response: v Check that the server name defined with keyword LOG_SERVER is spelled correctly in the DP for SAP profile. v Make sure there is a SERVER section in the profile for the log server defined with keyword LOG_SERVER. v Check the corresponding SERVER section and correct any setup problems. v Make sure that the log server named is available. BKI1200E Cannot read/write file: file name.
Explanation: DP for SAP requires that the number of different Archive Management Classes (parameter BRARCHIVEMGTCLASS) on the Tivoli Storage Manager servers is equal to or greater than the number of redo log or log file copies (parameter REDOLOG_COPIES). User response: Define at least as many different Archive Management Classes as log file copies requested. BKI1211E There is something wrong with your CONFIG_FILE file name.
Explanation: There is a problem with your DP for SAP configuration file setup. User response: Check the file permission and the file name specified in the DP for SAP profile keyword CONFIG_FILE. BKI1214E TSM Error: error text
Explanation: The program is unable to read or write a data file (file name) of a tablespace being backed up or restored. User response: Check the file access permission of the affected file(s). Try again. If the problem still exists, contact the product's administrator. BKI1201E There are no Tivoli Storage Manager Servers available.
Explanation: The specified TSM error occurred. User response: Check error text and correct the problem. For further information you may want to refer to IBM Tivoli Storage Manager Messages SC32-9090 BKI1215I Average transmission rate was number GB/h (number MB/sec).
Explanation: DP for SAP cannot locate a Tivoli Storage Manager server. This may be due to a configuration problem or to a problem while trying to connect to the Tivoli Storage Manager server. Most probably, a preceding error message points to the cause of the problem. User response: Look for and respond to preceding error messages. You may also want to check the DP for SAP profile and the IBM Tivoli Storage Manager client options and client system options files.
Explanation: The average transmission rate is displayed. User response: None. BKI1216E There are no BRBACKUPMGTCLASSES available.
Explanation: The BRBACKUPMGTCLASSES you have specified in your init<SID>.utl file are not correct.
134
Messages
User response: Check the management classes on the TSM server and specify correct ones. BKI1217E There are no BRARCHIVEMGTCLASSES available. BKI1229E Value for parameter BUFFSIZE (actual cur_number, maximum max_number) is too large for BUFFCOPY mode PREVENT.
Explanation: The BRARCHIVEMGTCLASSES you have specified in your init<SID>.utl file are not correct. User response: Check the management classes on the TSM server and specify correct ones. BKI1222E Version mismatch error. Check setup (version_1:version_2).
Explanation: To utilize the BUFFCOPY mode PREVENT the value for the parameter BUFFSIZE must not be larger than max_number. User response: In the DP for SAP profile, specify a BUFFSIZE less or equal to max_number if you need to prevent copying buffers when passing data between Tivoli Storage Manager components. If you need large buffers you can set option BUFFCOPY to SIMPLE or AUTO. As a consequence, buffers are copied when data is passed between Tivoli Storage Manager components.
Explanation: Different components with inconsistent versions are used. User response: Check your setup or contact DP for SAP support. BKI1223W A problem occurred during send of performance data to Administration Assistant .
| BKI1230E | | | | |
The following file was not processed: path.
Explanation: The operation was terminated due to a previous error. As a consequence, the file named could not be processed. The cause of the error should be found in an earlier message.
Explanation: There was a problem sending the performance data to the Administration Assistant over the network. User response: Check your setup or contact DP for SAP support. BKI1227I Average compression factor was number.
| User response: Check for and respond to preceding | error messages. | BKI1505E | |
Operation aborted because a different operation by this database client is already running.
Explanation: The data transferred had been compressed by the factor number. User response: None BKI1228W Server server name can not be used with password access method GENERATE in this environment. The process is running with user ID number but the effective user ID is number.
| Explanation: Different concurrent operations of the | same type were started for the same database. This is | not supported. The current operation is aborted. | | | | | | | | | | | | | | |
This message is also issued when a cooperative operation of two or more participating partitions was started, but the profile settings used for the various partitions do not match. User response: Wait until the currently running operation has ended and try again. Make sure that multiple operations are not started concurrently for a database. If this is a cooperative operation with two or more participating partitions, check that the profile settings of the various partitions (for example, DEVICE_TYPE, MAX_VERSIONS, etc.) do not differ. If they do, fix the profile settings, cancel the current operation, and start the operation again. Also, investigate the possibility of sharing the same profile among all partitions. BKI1506E Failed to execute command command. Output follows:
Explanation: The user ID and the effective user ID of the process are different. In order to utilize the password access method GENERATE the IDs must be equal. User response: Change the value for the parameter PASSWORDACCESS in the file dsm.sys (UNIX and Linux) or servername.opt (Windows) from generate to prompt. Reset the password for this node at the Tivoli Storage Manager server and run (for Oracle) backint -f password or (for DB2) backom -c password . This prompts you for the password and stores it encrypted in the DP for SAP configfile. Each time your password expires you have to repeat the last step.
Explanation: The system tried to execute the command cited. During execution, an error occurred. The output received from the command shell is listed following the message. User response: Determine the cause of the problem from the command and the output listed in the
135
Messages
message, and resolve the problem. BKI1507E The process needs to run with root authority. database client is an instance of the snapshot backup library representing a single partition of the database. User response: None. BKI1514I *****> Device client connected.
Explanation: The current process requires root authority. User response: Start the process under an account with root authority. BKI1508E The service service_name has terminated due to a previous error. Please check all logs for additional information.
Explanation: This message follows a message BKI1511I and indicates the connection of one of the device clients taking part in the operation. A device client is an instance of the device agent for the storage device. User response: None. BKI1515I Client is logging to file_name.
Explanation: The cited service is no longer available. User response: Check the appropriate logs for the cause of its termination. BKI1509E Authentication failure. The password specified does not qualify for accessing component.
Explanation: The clients log messages are written to the indicated file. User response: None. BKI1517I Deleting target data container defined by container_description.
Explanation: To access the named component, a password is required. However, the password provided could not be verified. User response: Make sure that the password files used by the different components of the system match. BKI1510I New connection received.
Explanation: The data in the container indicated is removed. User response: None. BKI1518E Internal error: The system is trying to use the same device agent, although the synchronization mode is not PARALLEL.
Explanation: The server received a new connection request. User response: None. BKI1511I New type_of_operation operation started for database instance instance, database database_name.
Explanation: The system has been told to use the same device agent for multiple database clients, but the database indicated serial synchronization mode. This setup is not supported. User response: Contact your IBM support personnel. BKI1519E A failure occurred during initialization of one or more of the nodes participating in this operation. Please check the logs for more information.
Explanation: A connection request resulted in the start of a new operation of the type indicated. User response: None. BKI1512E An error occurred during shutdown: Error information
Explanation: Some problem occurred during the initialization of a new operation. The problem may be with any component required for this operation. User response: Check the acsd log file for messages BKI1515I to determine the log file names of the participating agents. Check the log files of each component for the cause of the problem. BKI1520E Volume volume_name is shared across partitions. Volume sharing is not allowed.
Explanation: During shutdown of the component, a problem occurred. The error information is given. User response: Resolve the problem indicated by the error information. BKI1513I *****> Database client connected: Instance instance, database database_name, partition partition_number
Explanation: This message follows a message BKI1511I and indicates the connection of one of the database clients taking part in the operation. A
Explanation: At least two partitions own data residing on the volume indicated. This setup is not supported. User response: With the current disk layout of the
136
Messages
database, the requested function cannot be used. If you want to use the function, change the disk layout of the database so that each data volume is dedicated to a partition. BKI1521I Retaining number backups current version of the wizard. User response: Refer to your user documentation for a list of the device types that are supported by default. Specify one of the supported types. BKI1530E Failed to launch the device agent for device_type. Please consult your user documentation to make sure that all requirements for the specified device are met.
Explanation: When enforcing profile parameter MAX_VERSIONS, the indicated number of backups is kept. User response: None. BKI1522E The requested meta-information (subject=description) is not available.
Explanation: The system was unable to launch the appropriate device agent for the type indicated because some of its requirements are not met. User response: Refer to your user documentation and make sure that the system is set up correctly for the specified device type. BKI1534E Unexpected version actual_version of the repository located in path. Expected version: supported_version
Explanation: Some meta-information about each backup is stored in the repository. An error occurred when trying to retrieve part of this information. User response: Contact your IBM support personnel. BKI1523W Warning: The following containers were reused without being explicitly released: description
Explanation: The containers defined by the description are used by the current backup. They were used before by a different backup. This message is expected in SAN environments where data containers are usually kept until they are reused. In this case, this message does not indicate a problem. User response: None.
Explanation: The server located the repository in the path indicated. However, the version of the repository located on disk does not match the current version of the server. User response: Make sure to use the correct instance of the server. Ensure that the path of the repository was specified correctly. Refer to the release notes for a list of possible incompatibilities. BKI1535E Unexpected characteristics (bitwidth=number) of the repository located at path. Expected bitwidth: number
BKI1525E
The process service_name is in an inconsistent state. Please check for previous errors and restart the process afterwards.
Explanation: The process indicated cannot continue with inconsistent data. User response: Check the logs for messages pointing to the cause of the inconsistency. After resolving any problems, restart the process. BKI1526E A configuration file (profile) must be provided.
Explanation: The repository located in the path indicated was saved to disk using a bit width different from the bit width the server is using to load the repository. User response: Make sure to use the correct instance of the server. Ensure that the path of the repository was specified correctly. Refer to the release notes for a list of possible incompatibilities. BKI1536E The repository located at path is not valid.
Explanation: An operation was started without providing a profile. User response: Check the user documentation on how to provide the profile to the current process. Start the process again using a valid configuration file. BKI1529E The device device_type you entered is not supported by the wizard.
Explanation: A repository could not be found at the location indicated by path. User response: Ensure that the path of the repository was specified correctly. Do not edit any files in the repository path.
Explanation: The device type represents a certain type of storage device. While using the setup wizard, a device type was entered that is not supported by the
137
Messages
BKI1537E The repository located at path was written with an incompatible protocol (protocol_version). Expected protocol: protocol_version User response: Run the setup with option '-a disable' and then start the installation process again. If the entries in /etc/inittab should be retained, refer to your user documentation for information on how to complete the installation manually. BKI1542E Failed to uninstall because some of the processes to be uninstalled are still listed in /etc/inittab. Please re-run the setup after stopping the component by calling the setup script with option '-a stop'.
Explanation: The repository found at the location indicated was written to disk using the protocol version named. However, the server currently supports the expected protocol version. User response: Ensure that the path of the repository was specified correctly. Do not edit any files in the repository path. BKI1538E Unexpected repository type. The path path does not point to a repository of type protocol_type.
Explanation: The repository located in the path indicated was written to disk using a protocol different from the protocol supported by the server process. User response: Make sure to use the correct instance of the server. Ensure that the path of the repository was specified correctly. Refer to the release notes for a list of possible incompatibilities. BKI1539E Root privileges required. Could not change user ID to root.
Explanation: Before uninstalling the product, the affected processes must be stopped. This is done by running the setup script with the option -a stop, which will remove the entries from /etc/inittab and stop the processes. User response: Refer to your user documentation for information on the uninstall process. Run the setup with the option -a stop and then continue uninstalling. BKI1543E The component is still referenced within the /etc/inittab. In order to terminate the component rerun the setup script with option -a stop.
Explanation: The requested operation requires root privileges. However, the process could not acquire them. User response: Make sure the appropriate privileges (s-bit) are granted to the executable. BKI1540E /etc/inittab entries are limited to 127 characters. Please consult your user documentation for information on manually completing the installation procedure.
Explanation: The setup utility detected that the product is still active in the system. Apparently, its entries in /etc/inittab are not yet removed. User response: Call this process again with the option -f stop. BKI1544E New entries cannot be added to /etc/inittab because it already contains too many entries starting with ac. Please refer your user documentation for a manual setup of this package.
Explanation: The command line generated by the setup function exceeds 127 characters. This situation requires user intervention. The setup function did not update /etc/inittab. User response: Refer to your user documentation for information on what entries to add to /etc/inittab. BKI1541E /etc/inittab was not updated because some of the processes have apparently already been added. Please re-run the setup after calling the setup script with option '-a disable' if you want to change to a standard setup.
Explanation: During setup, an unusually high number of entries beginning with ac were detected in /etc/inittab. /etc/inittab was not modified. User response: Determine if these entries are expected, or if they were added due to a problem. If these entries are required, refer to your user documentation for information on how to complete the installation manually. BKI1545E IBM Tivoli Storage Manager for Advanced Copy Services is currently running.
Explanation: During the automatic setup, entries for this product were detected in /etc/inittab. This is an indication that the product was not previously uninstalled.
Explanation: This failure happens during (de)installation and indicates that not all TSM for ACS components could be stopped. User response: Check that no backup or restore is currently running and retry the operation. If you have customized the process of starting TSM for ACS, it
138
Messages
might be necessary to manually stop it by undoing those customization steps. BKI1546E IBM Tivoli Storage Manager for Advanced Copy Services was not started. are running. Check their log files for messages pointing to problems. Resolve any problems indicated. BKI1553I Component_name is logging to path.
Explanation: The file denoted is the log file of the named component. User response: If you need to check the log of the indicated component, look for this message to identify the log file to examine. BKI1554W The agent component_name terminated with exit code number.
Explanation: This failure happens during installation and indicates that not all TSM for ACS components could be started successfully. User response: Check that all TSM for ACS components have the appropriate access rights and retry the operation. Contact the support function if the operation continues to fail. BKI1547E Failed to remove the data associated with the deleted backup backup_id.
Explanation: The process denoted ended with the given exit code. User response: Check the agents log for any messages pointing to a problem. Resolve any problem indicated. BKI1555I Profile successfully created. Performing additional checks. Make sure to restart all ACS components to reload the profile.
Explanation: The backup named was deleted. However, its data could not be removed from the repository and from the storage device. User response: Look for a previous message pointing to the cause of the problem. Resolve any problems indicated there. Once the cause of this problem is resolved, the daemon will take care of the deleted backups eventually. BKI1548E Failed to monitor the data associated with the deleted backup backup_id.
Explanation: The setup wizard created a new profile. The profile will be validated. User response: Restart the ACS components after the wizard ends, in order to activate the new settings. BKI1556E Some data of backup backup_id are unavailable. It is impossible to restore the data requested.
Explanation: A background daemon is supposed to monitor the states of backups in order to determine if data needs to be deleted from the storage device. However, the monitor was not able to access the appropriate data. User response: Look for a previous message pointing to the cause of the problem. Resolve any problems indicated there. Once the cause of this problem is resolved the daemon will take care of the deleted backups eventually. BKI1549E Failed to load component_name due to the following reason: error_information.
Explanation: The system detected that some of the data originally contained in the backup is no longer available. The occurrence of this message depends on the type of storage device employed. For example, if an earlier backup data was restored from an N-Series device, some data of a later backup will be destroyed. User response: The backup is no longer complete and cannot be used for the requested operation. Try the operation with a different backup. BKI1557I Device agent is logging to path.
Explanation: The system was unable to load the named component of the product. User response: Check the error information given in the message. Resolve any problem indicated. BKI1550E Unable to perform required operations for container container_id for time_span.
Explanation: The device agents log messages are written to the file named. User response: None. BKI2000I Successfully connected to component_name on port portnumber.
Explanation: For the data container noted, an operation to be performed by a background daemon has been pending for the given time. This might indicate a problem and may result in storage not being released for an extended period. User response: Make sure the background daemons
Explanation: The backup library initiated a successful connection to the background process component_name on port portnumber. User response: None.
139
Messages
BKI2001E Socket error while connecting to component_name: reason. BKI2014I FRONTEND program finished.
Explanation: The frontend program is finished. User response: None. BKI2015I Starting BACKEND program.
Explanation: The background process component_name is not running. User response: Start component_name manually and try again. BKI2003I File file_name, BID deleted.
Explanation: The backend program is executing. User response: None. BKI2016I BACKEND program finished.
Explanation: The file file_name with the backup ID BID was deleted from the Tivoli Storage Manager. User response: None. BKI2008E Unable to connect to component_name.
Explanation: The backend program is finished. User response: None.
Explanation: Internal error. User response: Contact DP for SAP support. BKI2009I Deleting all versions with version number <= version_number on server server_name.
BKI2017I
Blocksize is set to num_bytes bytes.
Explanation: The operational blocksize is num_bytes bytes. User response: None. BKI2022E Unable to change mode of file file name: description
Explanation: All full database backups and their corresponding log file backups will be deleted from Tivoli Storage Manager storage, if their version number is less than or equal to version_number. User response: None. BKI2010E Error occurred processing FRONTEND
Explanation: Unable to change mode of file file name. description may contain the system error text. User response: Check the description. If the error persists, contact your service representative. BKI2024E Error in connection to component_name.
Explanation: An error occurred during the frontend processing. User response: Check the frontend script/program and the settings in the DP for SAP profile (keyword FRONTEND) and try again. BKI2011E Error occurred processing BACKEND.
Explanation: The connection to component_name terminated unexpectedly. This message might be displayed due to previous errors or after an unexpected termination of the component_name process. User response: Check for other error messages and restart component_name if necessary. Try again. If the problem persists, contact DP for SAP support. BKI2025E Failed to respond to a message received from component_name.
Explanation: An error occurred during the backend processing. User response: Check the backend script/program and the settings in the DP for SAP profile (keyword BACKEND) and try again. BKI2012E Passwords do not match. Try again.
Explanation: This is an internal error User response: Contact DP for SAP support. BKI2026E Unexpected exception in handler: handler
Explanation: The first and second password you entered do not match. User response: Enter the password correctly. BKI2013I Starting FRONTEND Program.
Explanation: This is an internal error. User response: Contact DP for SAP support. BKI2027I Using TSM API version your API version (compiled with compiled with version).
Explanation: The frontend program is executing. User response: None.
Explanation: Version information about the TSM-API. User response: None
140
Messages
BKI2028W Unable to terminate session session. BKI4002E Error during write of file file name. Reason: errno (error_num) error_desc.
Explanation: This is an internal error during cleanup that has no effect on the success of the service. User response: None BKI2029E The requested buffer allocator cannot be instantiated due to the following incompatibility: expression.
Explanation: An error occurs during the restore process of the file file name. User response: Check the error number error_num and the error description error_desc to avoid this problem in the future. BKI4005E Error allocating memory block for file file name. BLOCKSIZE may be too large.
Explanation: This is an internal error. User response: Contact DP for SAP support. BKI2031E A buffer allocator cannot simultaneously satisfy all of the following properties: list of properties
Explanation: Unable to request new memory blocks during the backup of file file name. User response: Verify that you have set a valid value for BLOCKSIZE. If you are not sure what value is valid, comment it out so the default value is used. Furthermore, you can check if you have enough RAM available with your machine. Also, check the memory usage during backup. It may be necessary to stop another application, increase memory, or change the configuration. BKI4007E File filename cannot be read. Reason: errno(errno number) errno text.
Explanation: This is an internal error. User response: Contact DP for SAP support. BKI2033E Cannot instantiate allocator of type allocator type with the following additional properties: list of properties
Explanation: This is an internal error. User response: Contact DP for SAP support. BKI4000W The attributes of file file name cannot be restored. Reason: errno (error_num) error_desc.
Explanation: Data could not be read due to some system error. Check errno text for further information. If this error recurs, this might indicate some hardware problems. User response: Contact your system administrator. BKI5000E Tivoli Storage Manager Error: error_message
Explanation: The file file name was restored successfully but one or more file attributes (permission, ownership, date/time) of the file file name cannot be restored correctly. User response: Check the error number error_num and the error description error_desc to avoid this problem in the future. An initial solution could be to set the appropriate correct permission for the file file name manually. BKI4001E File file name cannot be created. Reason: errno (error_num) error_desc.
Explanation: During a connection of DP for SAP to Tivoli Storage Manager server, a Tivoli Storage Manager error error_message occurred. User response: Use the Tivoli Storage Manager Messages guide and correct the Tivoli Storage Manager server error. Try your last action again. BKI5001E Tivoli Storage Manager Error: error_message
Explanation: The file file name to be restored could not be created/written. It is possible, that you do not have the appropriate rights for writing the file file name to the destination path. User response: Check the error number error_num and the error description error_desc to avoid this problem in the future. Furthermore, check the write permission of the user who started the restore.
Explanation: During a connection of DP for SAP to Tivoli Storage Manager server, a Tivoli Storage Manager error error_message occurred. User response: Use the Tivoli Storage Manager Messages guide and correct the Tivoli Storage Manager server error. Try your last action again. BKI5002E Tivoli Storage Manager Error: error_message
Explanation: See BKI5001E. User response: See BKI5001E.

141
Messages
BKI5003E Tivoli Storage Manager Error: error_message BKI5012E Cannot open TSM API message text file. Check if DSMI_DIR is set correctly. Current value of DSMI_DIR is: value
Explanation: See BKI5001E. User response: See BKI5001E. BKI5004W Tivoli Storage Manager Error: error_message
Explanation: The TSM-API could not be initialized. User response: Correct the value of the environment variable DSMI_DIR. BKI5013E Value for name is too long. Current value: value
Explanation: See BKI5001E. User response: See BKI5001E. BKI5005E Tivoli Storage Manager Error: error_message
Explanation: The value of the environment variable name has too many digits. User response: Check if the variable is set correctly. BKI5014E Tivoli Storage Manager Error: error_message
Explanation: See BKI5000E. User response: See BKI5000E. BKI5015W Data description could not be restored, because it was backed up with a newer version (objInf=support information)
Explanation: The TSM server hosts backups (i.e. data description) which were made with a new version of backint or backom, which ignores this data in further processing. User response: Upgrade the product. BKI5016I Time: current_time New TSM session created: MGMNT-CLASS: management_class, TSM-Server: server_name, type: session_type.
Explanation: A new session to TSM server server_name has been established at current_time. Data will be stored in management class management_class. User response: None. BKI5017E Internal Tivoli Storage Manager Error: Transaction succeeded although it was expected to fail.
Explanation: An internal Tivoli Storage Manager error occurred. User response: Retry the action. If the error occurs again contact DP for SAP support. BKI5018E The requested buffer has a size (current_size bytes) that is smaller than requested requested_size.
Explanation: See BKI5000E. User response: See BKI5000E.
Explanation: The request for a new buffer returned successful. The buffer, however, has not the requested size.
142
Messages
User response: Check if the system is running low on memory and retry the action. If the error occurs again contact DP for SAP support. BKI7048I The default port to connect to server_name will be used. BKI7058E Service open failed because more than one file was found with the same name.
Explanation: The command could not be started because two or more files with the same name were found. User response: Check the product log file for further detailed messages. BKI7059E Service open failed because a file was not found.
Explanation: A server port for the connection to the named server was not explicitly specified. Therefore, the default port is used. User response: Make sure the named server is listening to the default port. In the case of connection failures, specify the server port in the profile. BKI7049I The default ProLE port will be used.
Explanation: The command could not be started because a file specified was not found. User response: Check the product log file for further detailed messages. BKI8300I Function_name returned with code return_information.
Explanation: The port for the internal communication of DP for SAP is set during installation. The message indicates that this port is being used. User response: None. BKI7051E The environment variable XINT_PROFILE is not set. It must be set and contain the fully qualified path to the *.utl file to be used.
Explanation: This message indicates that the named API function ended with the specified return information. User response: If the return information indicates a problem, look for preceding error messages in the log files. Otherwise, no response is required. BKI8301E Product_name: Exception caught in function function_name. Error information: error_information
Explanation: The way DP for SAP works is specified in a profile. When called, DP for SAP looks for the environment variable XINT_PROFILE which must contain the fully qualified path to the profile. User response: Check the environment for XINT_PROFILE of the user who started DP for SAP. BKI7053E Service setup failed due to previous error.
Explanation: The named product implementing the DB2 Advanced Copy Services API received an error in the named API function. The error information is shown. User response: Analyze the error information to find the cause of the problem. Resolve any problems indicated. BKI8302E Product_name: Exception caught in function function_name. More information may be available in file log_file_name. Error information: error_information
Explanation: Initialization of the product failed due to previous errors. User response: Check the product log file for further detailed messages. BKI7055E Service open failed due to previous error in data mover.
Explanation: The command could not be started due to previous errors. User response: Check the product log file for further detailed messages. BKI7056E Service open failed because configured TSM server could not be accessed.
Explanation: The named product implementing the DB2 Advanced Copy Services API received an error in the named API function. The error information is shown. User response: Analyze the error information and the appropriate log files to find the cause of the problem. Resolve any problems indicated.
Explanation: The command could not be started because the TSM server defined in the profile could not be accessed. User response: Check the product log file for further detailed messages.
143
Messages
BKI8305E Invalid option option in options string: options_string. BKI8312E Error while parsing parameter keyword. In order for value1 to be valid value2 is required to be an existing directory.
Explanation: An invalid option was found while parsing the options string specified in the 'db2' command. User response: Correct the command and try again. BKI8306E The keyword keyword is not allowed multiple times within the profile.
Explanation: Value1 was found to be an invalid value for the parameter named. For this specific parameter, a file name can be specified whose path must already exist in the system. User response: Specify the name of a file in an existing path. BKI8313E Product_name: DB2 - TSM interface problem in function function_name: Invalid value of parameter: value
Explanation: The keyword indicated was found more than once in the profile. However, this keyword must not be specified multiple times. User response: Correct the profile. BKI8307E The parameter keyword must be specified in the profile.
Explanation: The named product implementing the DB2 Advanced Copy Services API detected an interface problem in the named API function. An invalid value was found in one of the API data structures. User response: Contact your IBM support personnel. BKI8314E Product_name: DB2 - TSM interface problem in function function_name: The session is already in use by a different operation.
Explanation: A required keyword is missing in the profile. User response: Correct the profile. BKI8308E Single argument required for parameter keyword.
Explanation: The keyword indicated requires a single value. However, two or more values are found in the profile. User response: Correct the profile. BKI8309E Missing argument for parameter keyword.
Explanation: The named product implementing the DB2 Advanced Copy Services API detected an interface problem in the named API function. Either the session handle is used for various operations simultaneously, or the functions are called in an order not supported by the current version of the library. User response: Contact your IBM support personnel. BKI8315E Function_name: The following object is not under the control of product_name: path
Explanation: In the profile, a value is missing for the named parameter. User response: Correct the profile. BKI8310E The keyword keyword is not allowed.
Explanation: An invalid keyword was detected in the profile. User response: Correct the profile. BKI8311E For parameter keyword, both server and port must be specified.
Explanation: The named product implementing the DB2 Advanced Copy Services API detected a problem in the named API function: The path passed by the database is not under the control of the product. User response: Make sure the database to be backed up meets the requirements for employing snapshot backups. BKI8316E Product_name: DB2 - TSM interface problem in function function_name: Empty group list passed by DB2.
Explanation: A value of the named parameter is missing from the profile. User response: As the value for the specified parameter, specify both server and port.
Explanation: The named product implementing the DB2 Advanced Copy Services API detected an interface problem in the named API function: The database passed a group list containing no elements. User response: Contact your IBM support personnel.
144
Messages
BKI8317W Product_name: Verification of configuration requested by user. No backup started. User response: None. BKI8322E Interface problem: Current database partition number not listed in the partition list.
Explanation: The user requested a verification of the configuration. The backup flow continued without errors up to the point where the snapshot would actually be done and was then cancelled. The system is ready for a snapshot backup, but no action beyond verification has been taken so far. User response: None.
Explanation: The partition list passed by the database does not contain the named partition participating in an operation. User response: Contact your IBM support personnel. BKI8323E Product_name: Problem occurred while processing function_name. Please check log file log_file_name for more information. Error information: error_information
BKI8318E
Product_name: DB2 - TSM interface problem in function function_name: Not enough space provided to write meta data.
Explanation: The named product implementing the DB2 Advanced Copy Services API detected an interface problem in the named API function: The buffer provided by the database is too small to contain the requested meta data. User response: Contact your IBM support personnel. BKI8319W Error while deleting old versions. This problem does not affect the new backup. Error information: error_information
Explanation: The named product implementing the DB2 Advanced Copy Services API received an error in the named API function. The error information is shown. User response: Analyze the error information and the appropriate log files to find the cause of the problem. Resolve any problems indicated. BKI8324E Product_name: Problem occurred while processing function_name: Device agent returned code return_information.
Explanation: After a successful backup, the system tries to remove older backups of the database according to the value of profile parameter MAX_VERSIONS. However, a problem occurred while trying to remove expired backups. The new backup is not affected by this problem. User response: Check the appropriate log files in order to determine the cause of the problem. Resolve any problems indicated. In case the storage device runs out of storage because outdated snapshot backups have not been removed, delete these snapshot backups manually. BKI8320I Deleting full backup backup_id backup_key.
Explanation: The named product implementing the DB2 Advanced Copy Services API received an error from the device agent in the named API function. The device agents return information is given. User response: Check the appropriate log files to find the cause of the problem. Resolve any problems indicated. BKI8325E Failed to determine hostname.
Explanation: The system was not able to determine the host name of the machine. User response: Make sure the system setup allows for querying the hostname via system function gethostname(). Ensure that the requirements for doing snapshot backups are met. BKI8326E Failed to create log directory path.
Explanation: After a successful backup, the system tries to remove older backups of the database according to the value of profile parameter MAX_VERSIONS. During this process, the full backup listed is removed. User response: None. BKI8321I Deleting partial backup backup_id for node:host:partition_number.
Explanation: The log path indicated is not available in the system and could also not be created. User response: Check the properties of the path indicated and make sure that its properties and the properties of the parent directory are set accordingly. Make sure all prerequisites for doing snapshot backups are met.
Explanation: After a successful backup, the system tries to remove older backups of the database according to the value of profile parameter MAX_VERSIONS. During this process, the backup listed for the named partition is removed.
145
Messages
BKI8327E Invalid value specified for parameter keyword: value BKI8334E Profile section section_name is required for function operation.
Explanation: A parameter value is not valid. User response: Correct the profile or the call as appropriate. BKI8328E Product_name must be licensed to set parameter keyword to a value of value.
Explanation: The specified profile section is required in order to perform the requested operation. However, it is not included in the profile. User response: Correct the profile. BKI8335E Profile section section_name refers to a value for keyword that differs from the one used at backup time. Expected value: value.
Explanation: Selected functions are supported only with a full TSM license. User response: Correct the profile or the call as appropriate. If you need the functionality requested, obtain a full TSM license and install the license file. BKI8330E Parameter keyword requires YES, NO, or number.
Explanation: The profile parameter named must not change its value between backup and restore. However, in the named profile section, the parameter has a value different from the value it had at backup time. This value is given in the message. User response: Correct the profile by setting the indicated parameter to the value indicated in the message. BKI8336E Invalid value specified for option keyword:value
Explanation: For the named parameter, only numeric values, YES, and NO are accepted. User response: Correct the profile or the call as appropriate. BKI8331E The parameter keyword1 is not allowed if keyword2 is set to value.
Explanation: An option value is not valid. User response: Correct the call. BKI8337E Error while parsing profile: Missing section name.
Explanation: There is a dependency between parameters keyword1 and keyword2. If the latter is set to the value named, keyword1 must not be specified. User response: Correct the profile or the call as appropriate. BKI8332E Failed to parse parameter keyword. File names in the profile need to be fully qualified.
Explanation: The profile is organized into named sections. However, a section name was not found. User response: Check that the profile name is specified correctly or that the default profile is a valid profile. Refer to your user documentation for the syntax of the profile or use the profile wizard to create a new profile. BKI8338E Error while parsing profile: Section section_name is not allowed to be nested.
Explanation: As the value of the parameter indicated, a fully qualified file name is expected. However, the specified value is not a fully qualified path. User response: Correct the profile or the call as appropriate. BKI8333E In order to enable the parameter keyword1 you need to set keyword2 to value.
Explanation: In the profile, the named section starts before the previous section ends. However, the section in question cannot be nested. User response: Correct the profile. BKI8339E Error while parsing profile: Profile section section_name is not valid.
Explanation: There is a dependency between parameters keyword1 and keyword2. If keyword1 is specified, keyword2 must be given the specific value indicated in the message. User response: Correct the profile or the call as appropriate.
Explanation: An invalid section name was found in the profile. User response: Correct the profile.
146
Messages
BKI8340E Error while parsing profile: Profile section section_name must not be specified more than once. User response: None. BKI8511I The command is: command name.
Explanation: In the profile, only a single section with the name indicated can be specified. However, during parsing, a second occurrence was detected. User response: Correct the profile.
Explanation: This is an information message echoing the command. User response: None. BKI8512I Return code is: return code.
BKI8341E
Error while parsing profile: Profile section section_name missing.
Explanation: This message shows the return code of the Backup Object Manager. Valid return codes: 0 The requested action was performed successfully. 1 The requested action was performed successfully; however, some warnings were issued. 2 or greater The requested action could not be performed due to errors. In this case, an error message should be logged, too. User response: None if the return code is 0. If the return code is greater than 0, analyze the error and/or warning messages. Resolve errors before starting the action again. BKI8513I TDP_DIR is not set. The temporary path will be used
Explanation: The required profile section indicated was not found in the profile. User response: Correct the profile. BKI8343W The parameter keyword1 of keyword2 value2 has changed its value from value1 to value3.
Explanation: The profile parameter named must not change its value between backup and restore. However, in the named profile section, the parameter has a new value value3 different from the value value1 it had at backup time. Both values are given in the message. User response: Check the log file for problems that may result from the change of parameter values. If so, you may want to change the profile, restoring parameter keyword1 to the value it had when creating the backup in order to perform a specific operation. BKI8344E Path path is listed more than once for partitioning.
Explanation: The variable TDP_DIR is not set in the user environment. All run logs will be written to the machines temporary directory instead. User response: Define the environment variable TDP_DIR . BKI8514W TDP_DIR is not set correctly. The temporary path will be used.
Explanation: This is a DB2 - TSM interface problem. User response: Contact your IBM support personnel. BKI8345E Error while parsing parameter keyword. path is required to be type_information.
Explanation: A path of the type indicated in the message is expected as a value of the named parameter. However, the specified path was not found to be of the correct type. User response: Correct the profile or the call as appropriate. BKI8349I Deleting incomplete backup backup_id backup_key .
Explanation: The variable TDP_DIR is set but contains an invalid path. All run logs will be written to the machines temporary directory instead. User response: Check and reset the environment variable TDP_DIR. BKI8520E No command was specified.
Explanation: backom was called without a command. User response: Check the command syntax and correct the call. BKI8521E Command option command option requires an argument.
Explanation: After a successful backup, the system tries to remove older backups of the database according to the value of profile parameter MAX_VERSIONS. During this process, the incomplete backup listed is removed. A backup becomes incomplete when parts of its data expire. This can happen when a backup that is marked destructively restorable is restored.
Explanation: A command option requiring an argument was specified without an argument.
147
Messages
User response: Check the command syntax and correct the call. BKI8522E Invalid command command. v v v v v mm is the month, specified as two digits, with leading zero for the months January to September, dd is the day of the month, specified as two digits, with leading zero for days 1 to 9, hh is the hour of the day, 00 to 23, with leading zero for hours 0 to 9, mm is the minutes of the hour, 00 to 59, with leading zero for minutes 0 to 9, ss is the second of the minute, 00, to 59, with leading zero for seconds 0 to 9.
Explanation: backom was called with an invalid command. User response: Check the command syntax and correct the call. BKI8523E Error during action.
Explanation: An error occurred while performing the named action. User response: Look for other error messages in order to analyze the problem. BKI8524E Tablespace online restore is not allowed.
Any digits can be replaced by wildcards * or ?, where v * means any number of any digits, v ? means exactly one digit of any value. User response: Correct the timestamp. BKI8529E Invalid log sequence number. Specify it in the format log sequence format.
Explanation: Either the database setup or the kind of backup prevents an online tablespace backup. User response: If you need to do a tablespace restore it must be done offline. BKI8525E The DB2 instance name can consist of at most 8 characters.
Explanation: The information on the log sequence number(s) does not comply with the expected format. Accepted log sequence numbers are for example 123 or S0000123.LOG. User response: Correct the log sequence number(s). BKI8530E Profile file name does not exist or cannot be accessed.
Explanation: The name given for the DB2 instance does not comply with the DB2 naming conventions. User response: Correct the DB2 instance name. BKI8526E The DB2 database alias can consist of at most 8 characters.
Explanation: Either an existing file could not be opened, or a file could not be created. User response: Check the attributes of the file and/or its directory. For backup processing, read access is required for the files to be backed up. For restore processing, write access is required for the target location of the files to be restored. BKI8531E Directory file path does not exist or cannot be accessed.
Explanation: The name given for the DB2 alias does not comply with the DB2 naming conventions. User response: Correct the DB2 alias name. BKI8527E Invalid node. Specify it in the format node format.
Explanation: The name given for the DB2 node does not comply with the DB2 naming conventions. Node numbers must be specified in the displayed format, for example NODE0000 or 0000. User response: Correct the DB2 node number. BKI8528E Invalid timestamp. It must consist of 14 digits with format yyyymmddhhmmss or digits and wildcards * or ?.
Explanation: A file path cannot be accessed. User response: Check the attributes of the file and/or its directory. For backup processing, read access is required for the files to be backed up. For restore processing, write access is required for the target location of the files to be restored. BKI8532E Invalid log chain number. Specify it in the format log chain format.
Explanation: Specify digits in the format yyyymmddhhmmss or mixed with wildcards * or ?. where: v yyyy is the year, specified as four digits,
Explanation: The information on the log chain number(s) does not comply with the expected format. Accepted log chain number(s) are for example 123 or C0000123. file path User response: Correct the log chain number(s).
148
Messages
BKI8533E A timestamp range is not allowed for the command command . BKI8540I Using component_name at host name:port number.
Explanation: A timestamp range is not allowed for command restore database, restore tabelspace, restore tablespace online and restore DB2 history file. Only a single timestamp argument can be used. User response: Correct the timestamp command option. BKI8534E Command option command option is missing.
Explanation: The component_name service named is used for the current action. User response: None. BKI8541I Using profile profile path.
Explanation: The profile named is used for the current action. User response: None. BKI8542E Profile profile path cannot be read.
Explanation: A command was issued without specifying a required command option. User response: Check the command syntax and correct the call. BKI8535E Invalid output mode. Specify one of the keywords keyword list.
Explanation: The Backup Object Manager tried to use the profile named but the profile was not available or could not be read. The location of the profile is specified via command line as argument to option -e or in environment variable XINT_PROFILE. User response: Make sure that the profile is available at the location specified in option -e on the command line or in environment variable XINT_PROFILE. Check the attributes of the profile and the corresponding directory and make sure that the file can be accessed. BKI8543I Querying TSM for file(s) file list.
Explanation: Only the listed keyword values are allowed with the output mode command option -m. User response: Correct the output mode command option. BKI8536E Wildcard characters are not allowed for command command.
Explanation: For the BackOM commands restore database, restore tablespace, restore tablespace online and restore DB2 history file its not allowed to specify the wildcard characters * and ? in a timestamp command option. User response: Correct the timestamp command option. BKI8537E The path path is not absolute.
Explanation: The Backup Object Manager checks if the files listed are available on the TSM server(s) specified in the corresponding profile. User response: None. BKI8545I No image type image(s) found.
Explanation: A request could not be satisfied because the files to be processed are not available on the TSM server. User response: Check if the file(s) were specified correctly in the request. BKI8546E Environment variable environment variable is not set or not set correctly.
Explanation: A command line argument requires a fully qualified path which was not given. User response: Specify the fully qualified path. BKI8538E The TDI file name cannot be processed.
Explanation: The TDI file could not be parsed because of errors. There are more specific parser error messages before this message occurs. User response: Check for and respond to preceding error messages in the Backup Object Manager log.
Explanation: A required environment variable is not set at all or has a value that is not allowed. User response: Check the documentation for the appropriate values of the environment variable named and set its value accordingly. BKI8548I Elapsed time: time value.
Explanation: After restore and delete, the time elapsed during the action is displayed. User response: None.
149
Messages
BKI8549E Unable to create file file name. BKI8557E The config file file name could not be created.
Explanation: During restore, the file to be restored cannot be created in the target location. User response: Check if there is sufficient space available for the file to be restored. Check the attributes of the target directory; write access is required. If the target file already exists, check that write access is granted BKI8550W Environment variable environment variable for output mode has wrong value. Using default.
Explanation: DP for SAP tries to create the configuration file named if it is not present at the location specified by the DP for SAP profile keyword CONFIG_FILE. However, the file cannot be created. This may either be caused by an incorrect path specified by keyword CONFIG_FILE, or the user may not have the appropriate permissions for creating the file. User response: Make sure the path specified by keyword CONFIG_FILE is correct and the permissions are set appropriately. BKI8558I Setting TSM password for partition partition number on host host name.
Explanation: The default output mode can be overridden by the named environment variable. Accepted values are short, normal, or detailed. The system default is short for actions on DB2 log files, normal otherwise. User response: Specify an appropriate value for the environment variable named, or remove the environment variable. BKI8551E Not all data written to file path.
Explanation: The DP for SAP TSM password is set on the host named for the DB2 partition indicated. User response: None. BKI8559W For partition partition number switch to host host name and issue the command again.
Explanation: Restoring raw or DB2 log file data ended before all data retrieved from TSM could be written to the file named. The file is incomplete. User response: Make sure there is sufficient space for the data to be restored. BKI8552E File file path could not be closed.
Explanation: When verifying the TSM password, the DP for SAP configuration file is modified. If the DP for SAP profile keyword CONFIG_FILE points to an NFS mounted (UNIX or Linux) or a shared (Windows) path accessible to all hosts in a DB2 ESE (EEE) environment, for example the instance home, all configuration files of the various partitions can be modified simultaneously. If, in contrast, keyword CONFIG_FILE points to a local path, only the configuration files of the local partitions can be modified. In this case, the password verification needs to be done from each host. The message indicates the partitions whose associated configuration files are not accessible. In order to avoid this administrative overhead, it is recommended to place the DP for SAP configuration files in a filesystem shared by all hosts hosting a partition of the database. User response: Make sure to verify the TSM password(s) for all partitions of the database. BKI8560E Partition partition number not found in the database configuration.
Explanation: After restoring raw or DB2 log file data, the target file could not be closed. User response: Retry the action. BKI8555E Variable DB2DBDFT or command option alias is required.
Explanation: The password command needs the name/alias of the database, for which the DP for SAP configuration file has to be adapted. User response: Either set the environment variable DB2DBDFT or provide the command option alias with the password command and try again. BKI8556E Unable to get hostname.
Explanation: The DB2 partition specified could not be found in the database configuration. User response: Check the configuration of the DB2 ESE(EEE) environment (db2nodes.cfg, environment variable DB2NODE) and try again.
Explanation: The machines hostname could not be determined. User response: Check the TCP/IP configuration of the machine.
150
Messages
BKI8561W Database alias not listed in the system database directory. BKI8589E Query command failed due to an error.
Explanation: The database alias does not exist. Because there is a dependency between the alias and the settings for DP for SAP there might be problems during database backup or restore runs. Nevertheless, the DP for SAP configuration file (init<alias>.utl) will be created and adapted. User response: Check if the alias specified does match to an entry in the DB2 system database directory. Further, check the argument for the DP for SAP profile keyword CONFIG_FILE and if necessary adapt it appropriately. BKI8584I Delete command completed successfully.
Explanation: The query command failed during execution. Not all queried objects can be displayed. User response: Check for and respond to preceding error messages in the Backup Object Manager log. In the absence of preceding error messages, contact DP for SAP support. BKI8610I Restoring type ...
Explanation: The restore of type has started. User response: None. BKI8612I Continuing restore ...
Explanation: The object(s) specified with the delete command were successfully deleted from the TSM server. User response: None. BKI8585W Delete command completed successfully, but had warning(s).
Explanation: The database restore continues. User response: None. BKI8613E Terminating restore ...
Explanation: An error occurred, and the database restore terminates. User response: Check for and respond to preceding error messages in the Backup Object Manager and the shared library run logs. Additional information may be found in the DB2 diagnostic log (db2diag.log). BKI8615I Restore command completed successfully.
Explanation: The object(s) specified with the delete command were deleted with warning(s) from the TSM server. User response: Check the Backup Object Manager log file for further detailed messages and if required, do the requested interventions manually. BKI8586I Delete command was aborted.
Explanation: The delete command was aborted by the user. No object(s) were deleted from the TSM server. User response: None
Explanation: The object(s) specified with the restore command were successfully restored from the TSM server. User response: None. BKI8616W Restore command completed successfully. Warning(s) encountered.
BKI8587E
Delete command failed due to an error.
Explanation: The delete command failed during execution. Not all objects were deleted from the TSM server. User response: Check the Backup Object Manager log file for further detailed messages and try to resolve the error which led to the delete failure. Retry the action. If the error still exists, contact the DP for SAP support. BKI8588E Delete command has not been started or no delete result information is available.
Explanation: The object(s) specified with the restore command were restored with warning(s) from the TSM server. User response: Check the Backup Object Manager log file for further detailed messages and if required, do the requested interventions manually. BKI8617I Restore command was aborted.
Explanation: This message indicates that an operation did not complete successfully. Typically, some other error condition was detected before. User response: Contact the DP for SAP support.
Explanation: The restore command was aborted by the user. No object(s) were restored from the TSM server. User response: None.
151
Messages
BKI8618E Restore command failed due to an error. image was generated and stored to TSM, too. User response: None. BKI8632W Backup command completed successfully. Warning(s) encountered.
Explanation: The restore command failed during execution. Not all objects were restored from the TSM server. User response: Check the Backup Object Manager log file for further detailed messages and try to resolve the error which led to the restore failure. Retry the action. If the error still exists, contact the DP for SAP support. BKI8619E Restore command has not been started or no restore result information is available.
Explanation: The backup operation completed successfully; the backup image can be used for restoring. However, some problems occurred. User response: Check the warning messages and take corrective actions if necessary. BKI8633I Backup command was aborted.
Explanation: This message indicates that an operation did not complete successfully. Typically, some other error condition was detected before. User response: Check for and respond to preceding error messages in the Backup Object Manager log. BKI8621I Restoring file file name...
Explanation: The backup operation was cancelled by user interaction. No backup image was created. User response: None. BKI8634E Backup command failed due to an error.
Explanation: The system started restoring the file indicated. User response: None. BKI8622I Deleting type ...
Explanation: No backup was made due to previous errors. User response: Check for and respond to preceding error messages in the Backup Object Manager log. BKI8635E The command option option must be a floating point number.
Explanation: The deletion of type has started. User response: None. BKI8623I Deleting file file name ...
Explanation: An invalid argument was specified for command option option. User response: Correct the command syntax.
Explanation: The system started deleting the file indicated. User response: None. BKI8626W The TDI file name could not be deleted.
BKI8636E
The command option option must be one of values.
Explanation: An invalid argument was specified for command option option. User response: Correct the command syntax. BKI8637I Type online/offline backup of alias started ...
Explanation: The system tried to remove the TDI image from TSM, but did not succeed. User response: Try to remove the image manually using the Backup Object Manager raw delete facility. BKI8630E The command option option must be a number.
Explanation: A backup operation of database alias of type type has started. User response: None. BKI8638I Type online/offline backup of tablespace(s) tablespace#1,...,tablespace#n of alias started ...
Explanation: An invalid argument was specified for command option option. User response: Correct the command syntax. BKI8631I Backup command completed successfully.
Explanation: A backup operation of tablespace(s) tablespace#1 ... tablespace#n of database alias of type type was started. User response: None.
Explanation: The backup operation completed successfully; the backup image can be used for restoring. In the case of a full database backup, the TDI
152
Messages
BKI8639I Including log files in backup image ... BKI8652I Detected DB2 version version with number bits.
Explanation: The DB2 log files are stored as part of the backup image. User response: None. BKI8640I Using number buffers with a size of size ...
Explanation: The indicated DB2 version was detected by Backup Object Manager. User response: None BKI8653I Using autonomic buffer size and number of buffers ...
Explanation: For backup or restore operations, the indicated number of buffers of the size displayed are used. User response: None. BKI8641I Using number session(s) ...
Explanation: The buffer size and the number of buffers used for backup or restore is automatically determined by DB2. User response: None BKI8654I Using an autonomic buffer size with number buffers ...
Explanation: For backup or restore operations, the indicated number of TSM sessions is used. User response: None. BKI8642I Using a degree of parallelism of number ...
Explanation: The buffer size used for backup and restore is automatically determined by DB2. The number of buffers to be used was specified in the call to the Backup Object Manager. User response: None. BKI8655I Using an autonomic number of buffers with a size of size ...
Explanation: For backup or restore operations, the degree of parallelism is displayed. User response: None. BKI8643I Using vendor library at lib path ...
Explanation: For backup or restore operations, the named vendor library is used. None. BKI8644W Offline backups cannot include log files. The option -L is being ignored.
Explanation: The number of buffers to be used for backup and restore are determined by DB2. The buffer size to be used was specified in the call to the Backup Object Manager. User response: None. BKI8656I Using an autonomic degree of parallelism...
Explanation: An offline backup operation was started, requesting the DB2 log files to be included. This is not possible with an offline backup. The backup is done without including DB2 log files. User response: Make sure to backup DB2 log files separately. BKI8651W Your version of DB2 does not support including log files. The option -L is being ignored.
Explanation: The number of DB2 processes (UNIX or Linux) or threads (Windows) used for reading or writing data from/to tablespace containers during backup and restore is determined by DB2. User response: None. BKI8657W Number is not a valid partition number. Assuming partition 0.
Explanation: A backup was started, requesting the DB2 log files to be included, but your version of DB2 does not support this feature. For including DB2 log files in the backup image, DB2 V.8.2 or later is required. User response: Make sure to backup DB2 log files separately.
Explanation: The partition number specified in the call to Backup Object Manager does not denote a valid partition of the database. Therefore, the default partition 0 will be used by DB2 and by Backup Object Manager. User response: If your database is not partitioned do not specify the partition number for further actions.
153
Messages
BKI8658E Number is not a partition number of the database or does not denote a partition on this host. for restoring to a different location. Restoring to a different location is not supported with device containers. User response: None. BKI8664E Connecting to alias using CLI failed. The return code was return code.
Explanation: The partition number specified does not denote a valid database partition or is not the partition located on the system where Backup Object Manager is called. Backup Object Manager can only operate on partitions residing on the same host. User response: Either change number to a partition number of a local partition, or start Backup Object Manager from the same host where the partition resides. BKI8659I Creating tablespace definition information ...
Explanation: The system tried to connect to the database named via the CLI. The operation did not succeed and returned the error code indicated. User response: Ensure that your database is enabled to accept CLI connections. BKI8665I The backup timestamp is: timestamp.
Explanation: The tablespace definition information (TDI) is being created in memory. User response: None. BKI8660I Saving tablespace definition information ...
Explanation: The DB2 backup finished successfully with the timestamp timestamp. User response: None. BKI8666I Redirecting tablespace tablespace with ID id.
Explanation: The tablespace definition information (TDI) is being stored on the TSM server. User response: None. BKI8661W Could not create TDI. The backup cannot be used for redirected restore with BackOM.
Explanation: The named tablespace is restored to the location requested. User response: None. BKI8667I Tablespace tablespace with ID id was not redirected because its container on the source system SID is not located in a path starting with path .
Explanation: The system could not collect the tablespace definition information. The backup was made without TDI. As a result, the backup can be used for restoring the system, but it cannot be used for restoring to a different location. User response: Ensure that your database is enabled to accept CLI connections. BKI8662W Could not save TDI. The backup cannot be used for redirected restore with BackOM.
Explanation: The named tablespace of type SMS is not redirected because the definition of the tablespace container in the source system does not match the database characteristics that Backup Object Manager expects and that are cited in the message. Therefore, Backup Object Manager tries to restore the tablespace to a location identical to the location in the original system. User response: Make sure that the tablespace mentioned can be restored to the original location. This includes that the user initiating the redirected restore has the appropriate permissions for placing the tablespace container in this location and that the tablespace can be restored without overwriting other data. In order to avoid this situation in the future, the administrator of the source system may want to recreate the tablespace according to the database characteristics Backup Object Manager expects.
Explanation: The system could not save the TDI on TSM. The backup was made without TDI. As a result, the backup can be used for restoring the system, but it cannot be used for restoring to a different location. User response: Check for and respond to preceding error messages in the Backup Object Manager log. BKI8663W The TDI contains device containers. The backup cannot be used for redirected restore with BackOM.
Explanation: A backup of a database using device containers was requested. The backup was successful, it can be used to restore the system, but it cannot be used
154
Messages
BKI8690E Free space test for container path failed. Only free bytes MB free space left but required bytes MB required. BKI8702E Too many errors. Bailing out.
Explanation: The TDI parser encountered a number of errors. Restoring is stopped. User response: Check for and respond to preceding error messages in the Backup Object Manager log. BKI8703E Out of memory.
Explanation: The system requires a tablespace container of the size indicated at the path named, but there is not sufficient free space available to create it. User response: Try to make available the free space required, for example by 1. Removing some files on the volume or file system the container shall reside on. 2. Increasing the size of the file system the container shall reside on. 3. Shrinking the size of the container requested so that it fits in the free space. Note: Backup Object Manager assumes that a small part (0.05%) of the free space will be required by the operating system for administrative use. As a consequence, only 99.95% of the free space on the volume or file system is actually available. BKI8692E The requested data could not be retrieved.
Explanation: The TDI parser encountered a token that cannot be read into the main memory. The TDI image cannot be processed, and restoring is stopped. User response: Contact DP for SAP support. BKI8704E Error while reading input file.
Explanation: The TDI parser tried to read more data from disk or from TSM, but did not succeed. User response: Ensure that the TDI image to be processed exists at the expected location and that the system has sufficient privileges to read it. BKI8705E error in line line number.
Explanation: The TDI data of a backup image could not be retrieved and displayed. User response: Look for and respond to preceding error messages. BKI8693E More than one TDI file matches your query.
Explanation: The TDI parser encountered a syntax error in the line indicated. As a consequence, the TDI image cannot be analyzed. User response: Respond to the error message and correct your TDI image. BKI8706E The container at path is inappropriate for tablespace tablespace.
Explanation: More than one TDI file matching the search criteria was found on TSM. User response: Specify additional BackOM command options to restrict the result set. BKI8700E Internal parser error in TDI parser.
Explanation: The container at the location indicated cannot be added to the tablespace named because of incompatible properties. User response: Check the properties of the container and the tablespace. Ensure that the IDs of the containers are unique for the tablespace named. BKI8707E Missing statement keyword in block block name near line line number.
Explanation: An unexpected error occurred in the TDI parser. User response: Contact DP for SAP support. BKI8701E This parser cannot process TDI version version.
Explanation: A keyword is missing in the named block ending at the line given. User response: Insert the required statement in the block. BKI8708E The [TDI] header block must be the first block.
Explanation: The current version of Backup Object Manager is not compatible with the version the TDI image was created with. As a consequence, the TDI data cannot be processed. User response: Check the release notes for the appropriate migration procedure.
Explanation: The TDI image does not start with the required header ([TDI] block). Only comments or whitespace are allowed before this block. User response: Ensure that the [TDI] block is the first block in the TDI image.
155
Messages
BKI8709E The required block block name is missing. BKI8734E The TDI used for redirected restore contains an invalid partition number.
Explanation: The named block is missing in your TDI image. User response: Insert the missing block using valid values. BKI8710W Duplicate block block name ignored at line line number.
Explanation: There is an invalid partition number specified in the Node statement of the TDI image. User response: Provide a valid partition number. BKI8736E Tablespace tablespace must have at least one container.
Explanation: At the line indicated, a block begins whose name was encountered before. The system ignores the duplicate block; it uses the data from the first occurrence of duplicate blocks. User response: Make sure that block names are unique within a TDI image. BKI8711W Duplicate statement keyword ignored in line line number.
Explanation: The TDI image defines the tablespace named without containers. User response: Ensure that there is at least one container associated with every tablespace. BKI8737E Tablespace tablespace has containers with the combined storage too small.
Explanation: The number of used pages of the tablespace named exceeds the combined size of its tablespace containers defined in the TDI image. User response: Ensure that every tablespace has containers of a combined size that is sufficient to hold the used pages of the tablespace. BKI8738E The container at path has a page size that is incompatible with its tablespace.
Explanation: At the line indicated, a duplicate statement was encountered within a block. The system ignores the duplicate statement. User response: Make sure to not specify duplicate statements within a block. BKI8730I Scaling tablespace containers to number percent ...
Explanation: All tablespace containers will be increased by the percentage indicated during the tablespace container redefinition step. User response: None. BKI8731I Normalizing tablespace containers ...
Explanation: The container indicated does not have the same page size as its tablespace according to the definitions in the TDI image. User response: Contact DP for SAP support BKI8739E The type of the container at path is incompatible with its tablespace.
Explanation: All containers of a tablespace will be of the same size after redefinition. User response: None. BKI8732E The TDI used for redirected restore contains an invalid database alias.
Explanation: The container indicated cannot be used with its associated tablespace according to the definitions in the TDI image. SMS tablespaces can only have path containers, and DMS tablespaces must have file or device containers. User response: Ensure that the appropriate types of containers are used with each tablespace BKI8740E The path path of a container must not be relative.
Explanation: There is an invalid database alias specified in the alias statement of the TDI image. User response: Provide a valid alias. BKI8733E The TDI used for redirected restore contains an invalid instance name.
Explanation: In the TDI image, the named path defining a container does not seem to be a fully qualified path. User response: Ensure that all paths in your TDI are fully qualified
Explanation: There is an invalid database instance specified in the instance statement of the TDI image. User response: Provide a valid instance name.
156
Messages
BKI8741E The container at path would overwrite existing files or directories. BKI8747E Not all tablespaces of the original database are contained in the TDI.
Explanation: The TDI image contains the definition of the container indicated whose location is already in use. This is only allowed when restoring to the source database. Restoring to a different location is stopped. User response: Ensure that all path containers defined in the TDI image point to non-existing paths and all file containers point to non-existing files BKI8742E The container at path is a device container which is not supported.
Explanation: At least one tablespace of the original database is missing in the TDI definitions of the target database. However, a new location must be given for all tablespaces of the original database. Therefore, restoring to a different location is stopped. User response: Provide the information on the missing tablespaces and their containers. BKI8748E The TDI does not define enough storage to hold all the data of the original database.
Explanation: In the TDI image, a device container is defined. However, device containers are not supported by Backup Object Manager. User response: Do not use device containers. BKI8743I Local TDI check returned return code.
Explanation: The target TDI has at least one tablespace whose containers are too small to hold the data of the source database. User response: Increase the container size or add more containers to the tablespaces. BKI8749E The page size of a tablespace in the TDI does not match the one of the original database.
Explanation: The TDI with the target database tablespace definition was checked. If the return code given does not equal 0 errors occurred. User response: In the case of a non-zero return code, contact DP for SAP support. BKI8744I TDI replacement check returned return code.
Explanation: The target TDI contains at least one tablespace with a matching ID in the source TDI, but their page sizes do not match. User response: Ensure that tablespaces have the same page sizes in both the source and the target TDI. BKI8750E The number of used pages of a tablespace in the TDI does not match the one of the original database.
Explanation: The system checked whether the tablespace definitions of the target TDI can replace the definitions of the source TDI. If the return code given does not equal 0 the tablespace definitions of the target TDI are not valid. User response: In the case of a non-zero return code, contact DP for SAP support. BKI8745E The TDI is invalid.
Explanation: The target TDI contains at least one tablespace with a matching ID in the source TDI, but the number of used pages of the target tablespace does not match the number of used pages in the original database. User response: Ensure that the number of used pages of a tablespace is the same in both the source and the target TDI. BKI8751E The tablespace type in the TDI does not match the one of the original database.
Explanation: The TDI with the target tablespace definitions is not valid. Restoring to a different location is stopped. User response: Check the Backup Object Manager log for the return code of the validation. Check for and respond to preceding error messages in the Backup Object Manager log. BKI8746I The TDI is valid.
Explanation: The target TDI holds at least one tablespace with a matching ID in the source TDI, but the tablespace types are different. User response: Ensure that the type of a tablespace is the same in both the source and the target TDI.
Explanation: The TDI with the target tablespace definition is valid. Processing continues. User response: None.
157
Messages
BKI8752E BackOM does not support redirected restore with device containers. of one of the tablespace containers is not allowed. A list of containers the system tries to create can be found in the Backup Object Manager log. One of them failed. User response: Check for and respond to further error messages in the Backup Object Manager log. BKI8760E Not all directories for the containers could be created.
Explanation: The target TDI contains at least one definition of a device container. However, device containers are not supported by Backup Object Managers redirected restore function. User response: Do not use the Backup Object Managers redirected restore facility for device containers. BKI8753E A container cannot be created at path.
Explanation: The system tried to create the directories to place the containers in, but at least one failed. User response: Ensure that the system has sufficient privileges to create the directories at the desired locations. BKI8761E The container at path does not have the minimum size of two extends.
Explanation: Either the location where the tablespace container is to be created does not exist, or the permissions of the user are not sufficient. User response: Check the location and the permissions. BKI8755I Getting reference TDI from TSM ...
Explanation: A tablespace container to be created must have at least the size of two extends. User response: Correct the size of the container to be created. BKI8762I Set tablespace container with ID id and name tablespace_container.
Explanation: Retrieving the appropriate TDI to be used by internal checking routines from the TSM server. User response: None. BKI8756W Could not get reference TDI from TSM. No input validation is done.
Explanation: Backup Object Manager redirects a tablespace container to the ID and name indicated. User response: None. BKI8763E The extent size of a tablespace in the TDI does not match the one of the original database.
Explanation: The system could not find a TDI image matching the database backup to be restored on TSM. The restore action will be continued, but the input data cannot be validated before the restore starts. User response: None. BKI8757I Performing redirected restore from source alias to target alias...
Explanation: Redirected restore of source alias to target alias is starting. User response: None BKI8758E The TDI does not contain data for tablespace tablespace.
Explanation: The extend sizes of corresponding tablespaces defined in the source and target TDIs must be equal. However, for at least one tablespace different extend sizes are defined in the source and target databases. User response: Define matching extend sizes for corresponding tablespaces. BKI8765I Testing redirected restore from source alias to target alias ...
Explanation: A definition of the tablespace named is expected to be provided in the TDI, but could not be found. User response: Ensure that all tablespaces of the source database are also defined in the target TDI. BKI8759E Redirecting of at least one container failed.
Explanation: The system is testing whether the original database can be restored to the target location. It checks whether v the filesystem where the tablespace containers are to be created has sufficient free space. (If specified, normalizing and scaling are also considered.) v there are existing files and directories identical to the containers defined for the target database. This would indicate that a database of same name and of same structure already exists, and data could be overridden.
Explanation: The system tried to create the containers for a tablespace, but at least one of them could not be redirected to a different location. Usually, the location
158
Messages
v the structures of the source and target databases (tablespace types, page sizes, extend sizes) allow for a redirected restore. User response: None. BKI8766I Check successful. Redirected restore possible with these settings. BKI8773E The interactive modification of the containers failed.
Explanation: You tried to interactively change the location of containers, but this operation failed. User response: Contact DP for SAP support. BKI8776E You are not allowed to delete this container.
Explanation: The redirected restore test finished successfully. Thus, the redirected restore operation can be started with the options specified for the test run. User response: None. BKI8767W Warnings occurred.
Explanation: You tried to delete the last container of a tablespace. However, at least one container must be available to every tablespace. User response: Make sure that there is at least one container defined for every tablespace. BKI8798E You cannot continue as there are errors.
Explanation: The redirected restore test detected one or more minor conflicts. These conflicts may or may not prevent a successful redirected restore operation. Nevertheless, it is recommended to resolve them. User response: Check for and respond to preceding warning messages in the Backup Object Manager log. BKI8768E Check failed. Redirected restore not possible with these settings.
Explanation: You tried to start a restore operation after redefining the containers interactively, but errors were detected in the input data. The operation cannot continue. User response: Check all tablespaces with !! error marks in the list and correct the definitions of their containers. Then continue. BKI8799E A container must have a size of at least twice the extent size (minimum size for this tablespace).
Explanation: The redirected restore test detected one or more major errors which will prevent a successful redirected restore with these settings. User response: Check for and respond to preceding error messages in the Backup Object Manager log. BKI8770I Getting TDI for redirected restore from TSM ...
Explanation: The container size specified is too small. The minimum size of a container is twice the extent size. User response: Correct the container size. BKI8800I The command is: command.
Explanation: The system is retrieving the TDI image from the TSM server. User response: None. BKI8771E The TDI for the redirected restore could not be retrieved.
Explanation: Displays the command that was issued. The following commands are possible: Backup, Restore, Archive/Retrieve. User response: None. BKI8801I PID of calling process: PID_number.
Explanation: The TDI image specified could not be found. User response: Provide the correct location of the TDI image. BKI8772E The selected database has a structure that prevents automatic cloning.
Explanation: Displays the process id of the DB2 process which called the shared library. User response: None. BKI8802I Found number backup image(s) on TSM server.
Explanation: You tried to clone an SAP database using redirected restore, but the database does not have the default directory structure of an SAP database. The cloning facility of Backup Object Manager redirected restore cannot be used for this system. User response: You may use either the interactive or the batch mode of Backup Object Manager redirected restore.
Explanation: For restore and delete operations DP for SAP queries TSM for backup images by means of a timestamp and shows the number of found images. User response: None.
159
Messages
BKI8803I The DB2 backup image size for this session is about size. BKI8812I Committed TSM sessions will be deleted.
Explanation: The estimated size of the data to be backed up is displayed. User response: None. BKI8804W The recovery log could not be written.
Explanation: During a backup with multiple sessions, an error occurred. The backup operation is stopped. TSM sessions already committed during this operation are being deleted from the TSM server in order to prevent them from being considered restorable. User response: None. BKI8813E Error deleting committed TSM sessions.
Explanation: After every backup or restore, DP for SAP writes a record into the recovery log file tdprlf.<SID>.<node_name>.log. It is located in the path pointed to by environment variable TDP_DIR. User response: Check, if the permissions are set correctly and if there is sufficient free space in your filesystem. BKI8805W The restore was cancelled by the user. Existing data not overwritten.
Explanation: One or more committed TSM sessions could not be deleted during the postprocessing of the failed backup run. User response: Use the Backup Object Manager to delete the file(s) manually.. BKI8814I Inquire TSM with mask search mask.
Explanation: During a restore, the user decided not to overwrite existing data. As a result, the action was cancelled User response: None.
Explanation: The string denoted is used to inquire TSM for backup images. User response: None. BKI8815I Information for Log Manager: DB2_instance DB2_database_name DB2_database_alias log_and_log_chain_number partition
BKI8806I
product version.release.modification (Beta) build_number build_data
Explanation: Writes version information into the product log file. User response: None. BKI8807I Archive log file log number of chain log chain number.
Explanation: The information listed is provided to the DB2 Log Manager. User response: None. BKI9001E Internal error: error
Explanation: Writes information about the log file to be archived into the product log file. User response: None. BKI8808I Retrieve log file log number of chain log chain number.
Explanation: The following internal error: error has been encountered. User response: Contact DP for SAP support. BKI9005E A not supported by B.
Explanation: Writes information about the log file to be retrieved into the product log file. User response: None BKI8810I Cleaning up resources of process PID_number.
Explanation: The installed version of product B does not support product A. Most likely you need to upgrade product B. User response: Contact the DP for SAP support. BKI9006E Internal error while reading environment variable: variable.
Explanation: All resources used by the product will be released. User response: None.
Explanation: This is an internal error. User response: Contact DP for SAP support.
160
Messages
BKI9007W An error occurred while terminating the application: the error BKI9205E Additional support information: Unable to instantiate name at position position.
Explanation: While terminating the application, an error occurred. This has no impact on the success of the operation. User response: None BKI9200E Additional support information: An exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9206E Additional support information: Unable to use actual when expecting expected at position position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support User response: Contact DP for SAP support. BKI9201E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9207E Additional support information: An exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support User response: Contact DP for SAP support. BKI9202E Additional support information: An Exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9208E System error errno: errno text at position position.
Explanation: A system call failed with errno. User response: Check errno and errno text with you system administrator. If you cannot resolve the problem, contact DP for SAP support. BKI9209E Additional support information: No handler registered for message type message. Thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9203E Additional support information: An exception was thrown at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support User response: Contact DP for SAP support.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9210E ESD_AbortDispatchingException thrown at position: position.
BKI9204E
Additional support information: An Exception was thrown at position: position (text=description).
Explanation: An internal error occurred. User response: Contact DP for SAP support. BKI9211E Additional support information: An Exception was thrown at position: position. (State state)
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support.
161
Messages
BKI9212E Additional support information: No handler registered for message type type. Thrown at position: position. BKI9302E Additional support information: Unused ESD_ReturnChannel destroyed. Dumping callstack: callstack
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9213E Internal error: A memory allocation request failed at position: position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your DP for SAP support. User response: Contact your DP for SAP support. BKI9306I Dumping callstack: call stack.
Explanation: This error message indicates an out-of-storage condition. It may occur due to a previous error, or it may be owed to a large size of the internal buffers User response: Check for and respond to preceding error messages. You may also want to reduce the size of the internal buffers (keyword BUFFSIZE in the Data Protection for SAP profile). BKI9219E Additional support information: Invalid error type typeencountered.
Explanation: This message is always preceded by an error message indicating the problem. It provides additional information that might help DP for SAP support to analyze the cause of the problem. User response: If you need to call DP for SAP support, provide the information given in this message together with the error information. BKI9307E Did not find a winsock dll compatible with version expected version. Version found is available version
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact DP for SAP support. BKI9220E Additional support information: Second call of call.
Explanation: The product failed to load the appropriate winsock dll. User response: Contact your system administrator BKI9308E A socket request timed out after processing number of bytes bytes position.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact your DP for SAP support. User response: Contact your DP for SAP support. BKI9300E Additional support information: Aborting send operation. See previous error.
Explanation: A socket request was issued with a timeout and the requested action could not be completed within the time specified. It was cancelled after processing number of bytes bytes. User response: If you need to call DP for SAP support, provide the information given in this message together with the error information. BKI9309E Operation terminated due to an explicit abort request.
Explanation: This error may have been caused by previous errors. User response: Check for previous errors and correct them. BKI9301E Additional support information: State state does not match state pattern pattern.
Explanation: An operation was terminated due to customer intervention. User response: None. BKI9310E Could not add backup_id to the repository at path.
Explanation: This error message typically follows a previous error. If so this error message can be ignored. Otherwise contact DP for SAP support. User response: Contact your DP for SAP support.
Explanation: The system was not able to add information on the named backup to the repository located in the path indicated. User response: Make sure the repository path is set correctly. If you need to correct the repository location, restart the server executable afterwards. If the problem persists contact your IBM support personnel.
162
Messages
BKI9311E Could not find backup_id in the repository at path. BKI9316E The path path does not point to a valid repository location.
Explanation: Information on the backup denoted by the backup ID could not be found in the repository located in the path indicated. User response: Make sure the repository path is set correctly. If you need to correct the repository location, restart the server executable afterwards. If the problem persists contact your IBM support personnel. BKI9312E backup_id is currently locked in the repository at path.
Explanation: When starting up, the server could not locate its repository. User response: Correct the profile or the call as appropriate.
Explanation: The information on the backup denoted by the backup ID is currently locked by a different process. Make sure to run only a single operation using a specific backup at a time. User response: Wait for the other operation to finish or abort this operation. Then start again. If the problem persists contact your IBM support personnel. BKI9313E Failed to update backup_id in the repository at path.
Explanation: The information on the named backup could not be updated in the repository located at the path named. User response: Check the logs for other messages pointing to the cause of this problem. Resolve any problems indicated. If the problem persists contact your IBM support personnel. BKI9314E Could not remove backup_id from the repository at path.
Explanation: An attempt to remove the information on the backup named from the repository located at the path indicated failed. User response: Check the logs for other messages pointing to the cause of this problem. Resolve any problems indicated. If the problem persists contact your IBM support personnel. BKI9315E Could not access the repository at path because it is currently locked by another process.
Explanation: When starting up, the server tried to load the repository located at the path named. However, the repository was locked by a different process. This can happen if two server processes try to use the same repository. This is not supported. User response: Make sure each instance of the server uses its own repository.
163
Messages
164
Appendix C. Troubleshooting
This appendix gives you information on how to resolve errors that might occur during or shortly after installation and during backup or restore. In general, problems, related to this product can be divided into the following categories: 1. Setup problems 2. Defects of this product or a product it is interacting with 3. Performance problems This chapter will help you with setup problems and defects. If you encounter a performance problem please proceed with General Performance Considerations on page 35. If an error occurs, always first check the description of the respective error message, issued by the system. Besides being displayed on the screen, the error messages also can be found in log files. For these log files and for a description of the error messages, see Appendix B, Data Protection for SAP (DB2) Messages, on page 129. Solve the problem indicated in the error message and retry the action.
Problem Resolution During Installation and Setup Understanding the Setup

For a description of the installation procedure please follow the section Installing Data Protection for SAP on page 24. When you are done with the Installer please make sure all files are installed as described in that chapter. Also check for an entry similar to the entry for a 32bit Data Protection for SAP on DB2 shown below in the file /etc/inittab on UNIX and Linux systems:
pd32:2:respawn:/usr/tivoli/tsm/tdp_r3/db2/prole -p tdpr3db2 <Server component hostname> 5126
If running a 64-bit Data Protection for SAP, the port name would be tdpr3db264 instead of tdpr3db2. The purpose of this entry is to start a daemon process for ProLE, which listens on port tdpr3db2 for connections with the shared library and is able to forward performance information to an Administration Assistant Server component. The port tdpr3db2 can also have a different name but must match the entry in /etc/services (see below). The last two arguments specify the location of the Administration Assistant Server component and are only needed if you want to use it. <Server component hostname> specifies the IP address of the host on which the Administration Assistant server is running. 5126 is the default port the server is listening to. On Windows systems verify that a service ProLE Service is running and set to automatic startup. If this service is not running Data Protection for SAP will not function properly. The installer adds lines like the following to the file /etc/services on UNIX and Linux or to %SYSTEMROOT%\system32\drivers\etc\services on Windows:
165
Troubleshooting
tdpr3db2 tdpr3db264
57322/tcp 57324/tcp
where tdpr3db2 is the entry for 32bit and tdpr3db264 for 64bit Data Protection for SAP.This port should be the same as in /etc/inittab. Other than modifying the mentioned files the installer created, the initial DP for SAP configuration file init<SID>.utl can be found in the directory to pointed by the environment variable TDP_DIR. The vendor environment file vendor.env must contain the fully qualified path and file name of the file init<SID>.utl and should contain the path where the DP for SAP run logs will be written to (otherwise the machine's temporary directory will be used instead). See Figure 35 for an overview of the configuration files on a UNIX and Linux system.
Figure 35. SAP and Data Protection for SAP Configuration files on UNIX and Linux.
The names of the TSM servers specified in init<SID>.utl must match with the names in the file dsm.sys On Windows systems file dsm.sys is not needed but rather file dsm.opt, whose content is not relevant for Data Protection for SAP. The directory where the file dsm.opt is contained must also contain files with the name <server>.opt for each server specified in the init<SID>.utl. There must be an environment variable DSMI_CONFIG set to an option file within this directory. The best practice is to set DSMI_CONFIG to dsm.opt. Also on Windows the environment variable DSMI_DIR must be set pointing to the directory where the file dscameng.txt resides. Usually this is the directory c:\Program Files\Tivoli\tsm\api.
166
Troubleshooting
On UNIX and Linux systems the DSMI_* variables do not need to be set if you used the default paths for installation of TSM API or TSM Backup Archive Client. But if the variables are set make sure they point to the right files and directories. Also please check if the user you are running your backups with has the right permissions to access all the above mentioned files. Otherwise modify the file read permissions. The only file n which Data Protection for SAP stores persistent information is init<SID>.bki. Please also check the write permission of that file.
Location of Log Files

Everything you see on the screen during operation of DB2 backup, DB2 restore or BackOM in general will also be written into log files. To locate these log files, see How To Find Files Containing Message Output (Log Files) on page 129 DB2 also writes messages of internal operations, events or states in the administration notification log (db2<SID>.nfy) and diagnostic log (db2diag.log) in the directory specified with the DB2 database management configuration parameter DIAGPATH. The DB2 database management configuration can be inquired with the command:
db2 get dbm cfg
General Problem Resolution

During work with Data Protection for SAP you may run into problems during backing up or restoring of your DB2 database. Following graphic will help you to isolate these problems:
167
Troubleshooting
Figure 36. General Problem Isolation
After installation (1.1 in Figure Figure 36) set the password (1.2) as described in chapter Set the Password on page 29. If you use a generated password dont perform this step. If no problems occur you see a message BKI0051I: Password successfully verified for node <nodename> on server <servername> for each server you configured within your init<SID>.utl and a message BKI8512I: Return code is: 0 at the very end of the output. If a problem occurred you should see an error message. Frequent errors at this point (1.2) are: v Error message: BKI2001E: Socket error while connecting to ProLE at <IP address>:<PORT>: Connection refused Check that the ProLE Service is running on Windows or check if the background daemon is running on UNIX. To check for the daemon issue the command:
ps -ef | grep prole
On Windows systems you can either have a look in the Services screen of the Computer Management or issue the command:
net start
to get a list of all running services. Check the entry for UNIX in /etc/services and on Windows in %SYSTEMROOT%\system32\drivers\etc\services. Compare the port number from the error message with the port number within
168
Troubleshooting
/etc/services. Also have a look in /etc/inittab on UNIX. If another port was set using the option -p<PORT>, check this one as well. If all of this does not help, start ProLE from another shell:
prole -p <PORT>
or, on Windows:
prole -console -p <PORT>
and try starting backom again. v Error message: BKI5001E: Tivoli Storage Manager Error: Server not found in configuration file. The TSM Server from the init<SID>.utl does not match with the one specified in the used dsm.sys (on UNIX). On Windows, the <server>.opt might be missing v Error Message: BKI5001E: Tivoli Storage Manager Error: ANS1353E (RC53) Session rejected: Unknown or incorrect ID entered This message can happen if the node in the server stanza of the UTL file is not valid on the server. Also have a look into the API reference (e.g. search the message at tivoli.com) v HANG: If backom hangs after input of the password the servers IP address in dsm.sys may be wrong. When step 1.2 of Figure 36 on page 168 (set password) finally succeeds, proceed with step 1.3 and try to make a backup using the DB2 backup command to verify the settings are correct. In Appendix J, Using DP for SAP to Back Up and Restore Files and Databases, on page 197 it is described how to do this. If the backup was successful you will see a message from DB2:
Backup successful. The timestamp for this backup image is: <timestamp>
Otherwise you should see an error message. In this case try to resolve it by using the error descriptions in Appendix B, Data Protection for SAP (DB2) Messages, on page 129. The first place to look when an error occurs is the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log, located in the directory pointed to by the environment variable TDP_DIR or, if the variable is not specified, in the system temporary directory. If this log file was not written (2.2) this is a clear sign that DB2 either was unable to load the shared library containing the DB2 connector of DP for SAP or encountered an error before calling the DP for SAP library. In both cases there should be a DB2 error message beginning with the prefix SQL displayed on the command line and an entry in the DB2 diagnostic log db2diag.log (4.3) can be found. For further error analysis DB2 provides a mechanism of displaying detailed error descriptions. Issue the following command from the command line:
db2 ? SQL<number>
169
Troubleshooting
whereby SQL<number> has to be replaced with the appropriate message number. Try to resolve this problem using the documentation from DB2. If the file DP for SAP run log exists, search for a message beginning with BKIXXXXY where XXXX is a four digit number and Y one of the letters I, W or E. If you find such a message you can be sure the DB2 connector of DP for SAP is loaded and has been called by DB2. In (3.1) the file tdpdb2.<SID>.<nodename>.log is written and you find an error message starting with BKI (see Appendix B, Data Protection for SAP (DB2) Messages, on page 129.
Problem Resolution When Using the Backup Object Manager

In the case of general problems, you may want to check the following setup: v The executable backom (UNIX or Linux) or backom.exe (Windows) is located in the installation path of DP for SAP. v The environment variable XINT_PROFILE points to the DP for SAP profile. XINT_PROFILE is also specified in the DB2 Vendor INI file. v The environment variable TDP_DIR points to a valid log path with write access and sufficient space for further writing. TPD_DIR is also specified in the DB2 Vendor INI file. v The environment variable DB2_VENDOR_LIB points to the DP for SAP shared library. v In the case of general problems with the redirected restore function, you may want to verify that all prerequisites are met. For details, see Redirected Restore Prerequisites on page 65. Processing results and error messages are logged in different log files. For the types and locations of log files, refer to Location of Log Files on page 167. An additional method to speed up and to simplify analyzing the Backup Object Manager log messages is to employ the verbosity command option -v. It causes all messages which are typically written to the Backup Object Manager log to be seen simultaneously on the screen during the command execution. The error messages logged by Data Protection for SAP are explained in Appendix B, Data Protection for SAP (DB2) Messages, on page 129. If an error occurs, resolve the problem indicated in the error message and retry the action.
Problem Resolution During Operation

This section is intended to support isolation of problems which seem to occur without reason during an operation the system has performed successfully many times before. Computers are deterministic machines. If an operation is performed more than once using the same input in the same environment it will produce the same result. Unfortunately todays computing environments consist of a large number of components containing a huge number of volatile parameters often influencing each other. For problem determination the above abstract assessment results in the following very practical actions depending on if the problem seems to be stochastic or if it can be reproduced.
170
Troubleshooting
Reproducible (Repeatable) Problems

If a problem seems to occur repeatable without reason during an operation the system performed successfully many times before, you should ask yourself: 1. What did you change at the setup of Data Protection for SAP ? 2. What did you change at the setup of involved components (DB2, SAP, TSM, operating system, network, hardware) ? 3. Did you apply any patches or updates to any components in the system ? If you are sure you changed nothing, ask the same questions to your coworkers and system administrators (DBAs, Network admin, TSM admin, etc.). If this is without satisfying result, it may be an option to observe the last modified time stamp of the configuration files (vendor.env, init<SID>.utl, dsm.sys, dsm.opt, /etc/services, /etc/inittab, ...).. The following UNIX command lists you all files in the directory /etc which have been modified during the last 5 days:
find /etc -type f -ctime 5 -print
Also there might be changes to the system that are caused by the system. Samples for such changes are: v disks are running full. Action: Check with UNIX command df v networks slow down. Action: check for reasons like additional hosts, additional applications, defects in software or hardware. Compare runs in the Performance Monitor history view in the Administration Assistant or compare the tdpdb2.<SID>.<nodename>.log. v TSM server is slowing down. Action: check if additional clients and/or additional operations have been added. Have a look in the TSM servers activity log. If you are able to find any changes made to the system roll them back one at a time and try to reproduce the problem. In most cases you will find the one change or set of changes which caused the problem to occur. Now you can decide if you need those changes or can fix their symptoms. Otherwise if you need to implement those changes and can not prevent their symptoms you can now contact support for the affected components.
Random Problems
If a problem seems to occur stochastic (sometimes it works, sometimes it does not) without reason during an operation which the system has performed successfully many times before, you should try to find out: What is different when the problem occurs ? Compare the logs of the application in question ((tdpdb2.<SID>.<nodename>.log, db2diag.log, TSM activity log, etc.) to find out differences between successful and unsuccessful runs. Try to find a pattern for the occurrence of the problem: v Is it always occurring at the same time ? v Is it always occurring after you run some other or the same operation ? v Is it always occurring if some other application / process is running in parallel ? If it is occurring always at the same time review if there are any scheduled processes (virus checker, automatic updates, batch jobs). The above mentioned logs may help you with this.
171
Troubleshooting
DB2 Vendor Reason Codes

The following reason codes are used by Data Protection for SAP and may be displayed or logged by DB2 in the case of problems.
Table 5. DB2 Vendor Reason Codes Reason Code 1 2 Explanation The library specified could not be loaded. Communication error between shared library and ProLE User Response Check the DB2 diagnostic log for further details. Check the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log for further details. There is no backup image on TSM matching the given search criteria. Check the options string specified and check the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log for further details. Check the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log and the DB2 diagnostic log for further details.
6 10
Object specified cannot be found on TSM. Invalid options specified with the options parameter of the DB2 backup/restore command.
11
Initialization procedure for shared library failed.
17
During end processing of either Check the Data Protection for SAP backup/archive or restore/retrieve run log session(s), an error occurred. tdpdb2.<SID>.<nodename>.log for further details. An error occurred during reading or writing data from or to TSM. Check the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log for further details. Check the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log for further details. Check the Data Protection for SAP run log tdpdb2.<SID>.<nodename>.log and the DB2 diagnostic log for further details. Check the DB2 diagnostic log for further details.
18
26
An error occurred during deleting data from TSM.
29
An abort request from DB2 could not be handled correctly.
30
A severe error occurred.
Providing Information to IBM or Tivoli Support

When you contact your support function, try to give a complete description of the problem you encounter and the environment it occurs in. You should always provide the following information: v The version of DP for SAP v The operating system level (including 32- or 64-bit) and patches that were applied
172
Troubleshooting
DB2 version (including 32- or 64-bit) TSM server version OS level for TSM server DP for SAP configuration file(vendor.env, initSID.utl) ) including TSM client config files (dsm.sys, dsm.opt) v Data Protection for SAP profile (initSID.utl) v SAP-DB2 Administration Tools log file output for the operation in question (brarchive, brrestore) v v v v v If the process worked previously, also have the change history of the system components available In addition to the above information there will be a situation in which you need to supply additional information. Your service representative will ask you for this.
173
174
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Appendix D. Using DP for SAP with a Distributed File System on AIX

Note: This chapter formerly referred to the SAN File System, which is being discontinued in favor of the General Purpose File System (GPFS). The chapter now uses the general term distributed file system.
Setting Up DP for SAP in a Distributed File System

If you statically assign all SAP systems to specific hosts (i.e. instances are not moved between hosts), grant the root user read/write access permission to the distributed file system (such as the SAN File System or General Purpose File System) and follow the regular installation process as outlined in Chapter 4, Installing or Upgrading Data Protection for SAP, on page 23. In this case, no additional actions are required. If there is only a single SID located on a host, DP for SAP can be set up without granting the root user a permanent read/write permission for the distributed file system. This is achieved by having the ProLE service run by the db2<SID> userid instead of root. However, for multiple SIDs on a host system, the ProLE service should be run by root, and the root user should have permanent read/write permission for the distributed file system. If this poses a problem in your environment, contact your support function. To make Data Protection for SAP work without granting root permanent access to the distributed file system perform the following steps: 1. Enable root access to the distributed file system. 2. Install Data Protection for SAP using the procedure described in Chapter 4, Installing or Upgrading Data Protection for SAP, on page 23. 3. In file /etc/inittab, replace the line
pd64:345:respawn:/usr/tivoli/tsm/tdp_r3/db264/prole -p...
by
pd64:345:respawn:su - db2<SID> -c /usr/tivoli/tsm/tdp_r3/db264/prole -p...
where <SID> must be the actual SID. 4. Execute the command

init q
5. Disable root access to the distributed file system.
Setting Up DP for SAP in a Distributed File System in an Adaptive Computing Environment

If you plan to use Data Protection for SAP in an Adaptive Computing Environment, a special setup is necessary to fully utilize its benefits.
175
Using DP for SAP with a Distributed File System on AIX

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the Adaptive Computing Environment currently does not allow more than one SID per host, the procedure described here will work without granting the root user additional permissions for the distributed file system. To prepare the installation in the distributed file system, perform the following steps: 1. Log in as root user and perform a regular installation of Data Protection for SAP on one of the systems participating in the distributed file system. Have the installation procedure create the configuration files of Data Protection for SAP in a directory which is not located in the distributed file system (for example /tmp). These files will not be used and can therefore be deleted afterwards. 2. After the successful installation, copy the content of the installation directory
/usr/tivoli/tsm/tdp_r3/db264
to an arbitrary directory in the distributed file system. For example:

mkdir /san/SanFS/tivoli/tdp_r3 cp -r /usr/tivoli/tsm/tdp_r3/db264 /san/SanFS/tivoli/tdp_r3
3. Now each of the different SAP environments can be set up for using Data Protection for SAP for backup and recovery. In the Adaptive Computing Environment, this can be performed from the same host for all participating SIDs. For each SID, log in as the database instance owner and execute the script SanFSsetupSID.sh from the installation path in the distributed file system. For example:
/san/sanFS/tivoli/tdp_r3/db264/SanFSsetupSID.sh
The following information must be provided to the script: a. The system ID (SID) for the SAP system to be backed up. b. The path for the Data Protection for SAP profile and configuration file (init<SID>.utl, init<SID>.bki). c. For a connection to an Administration Assistant server, its hostname or IP address and its server port. 4. The script SanFSsetupSID.sh creates scripts prepareTDPSAP_<SID>.sh. On each host, log in as root user and execute the script prepareTDPSAP_<SID>.sh with the appropriate <SID>. If you place this script in the distributed file system make sure the root users have the appropriate permissions to execute it. 5. Whenever a SID is moved to a different host the script prepareTDPSAP_<SID>.sh must be executed by the root user of the new host.
176
Appendix E. Installation Planning Sheets

Data Protection for SAP
Before starting the installation procedure, collect the following information. Note: The following table is also provided in file form as planning_sheet_db2 for UNIX and Linux and planning_sheet_db2.txt for Windows.
Table 6. Installation Parameters for Data Protection for SAP UNIX or Linux X
Windows Installation Parameter DB2 database SID: X TSM server name or IP address:
X TSM node name: TSM node configured on the TSM server named for the backup of the SID denoted above. For details, refer to 4. Node Definition on page 206.
Tivoli Storage Manager management classes for database and log file backups. Management classes configured for the database backup and for the backup of log files. For details, refer to 3. Policy Definition on page 205.
Default: MDB for database backups, MLOG1 and MLOG2 for log file backups. Path where the Tivoli Storage Manager API resides (contents of environment variable DSMI_DIR): X Default: C:\Program Files\Tivoli\TSM\baclient X Path to client option file of Tivoli Storage Manager (contents of environment variable DSMI_CONFIG). For details refer to the Tivoli Storage Manager documentation.
Path to Tivoli Storage Manager log files (contents of environment variable DSMI_LOG): The TSM API will create the file dsierror.log< in this path. For details, refer to the Tivoli Storage Manager documentation.
Default: C:\temp Installation path for Data Protection for SAP executables: X Default: C:\Program Files\Tivoli\TSM\tdp_r3\db2 or C:\Program Files\Tivoli\TSM\tdp_r3\ db264
177
Installation Planning Sheets

Table 6. Installation Parameters for Data Protection for SAP (continued) UNIX or Linux
Windows Installation Parameter Options: v Use of the Administration Assistant (see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77 and Table 7). The Administration Assistant should be installed prior to Data Protection for SAP so that the interface between the two can be established automatically. v Use of DB2 Log Manager for log archiving (requires DB2 V8.2 or higher)
Administration Assistant
Prior to installing the Administration Assistant for Data Protection for SAP (optional but recommended), collect the following information. Note: The following table is also provided in file form as planning_sheet_aa for UNIX and Linux, and planning_sheet_aa.txt for Windows.
Table 7. Installation Parameters for the Administration Assistant Installation Option Installation Parameter Option: Installation type. Decision as to whether the Administration Assistant is to be installed on a single host ('typical' installation) or distributed across multiple hosts ('custom' installation). If 'custom' is selected, a list of the individual components is presented with appropriate check boxes for selection. A multi-host installation requires that all connecting instances of Data Protection for SAP be version 5.4 or higher. For more information on single- and multi-host installations, see Chapter 8, Installing and Using the Administration Assistant for Data Protection for SAP, on page 77.
|
Default: Single-host Option: Server/client communication mode. Decision as to whether the Administration Assistant Server component and clients communicate in nonsecure mode via HTTP or secure mode via HTTPS
Default: Nonsecure
| | | | | |
Option: Database type. Decision as to which DBMS the Administration Assistant should use. Select either the installation of the bundled Apache Derby package or the use of an existing Apache Derby or IBM DB2 installation.
Default: Installation of Apache Derby as bundled with product.
178

Table 7. Installation Parameters for the Administration Assistant (continued) Installation Option Installation Parameter Option: Data migration. If you want to transfer data from an existing Administration Assistant environment, enter the directory containing the *.aa files.
| | | | | |
Default: No migration. Option: Software language. Decision as to whether to install only the English version of the program or all national language versions.
Default: English-only Parameters applying to the Administration Assistant Server component: Hostname or IP address: Default: Hostname of current system Port number for Data Protection for SAP (ProLE) connect. This port number must be made known to all instances of Data Protection for SAP that are to be managed and monitored by this Server component instance. Default: 5126 Port number for client connect in non-secure mode (HTTP). Default: 80 Port number for client connect in secure mode (HTTPS). Default: 443 RMI registry port number Default: 1099 Port number for performance data from Database Agent Default: 5129 Port number for communication with Database Agent Default: 5128 Parameters applying to the Administration Assistant Database Agent component Hostname or IP address: Default: Hostname of current system Port number for Data Protection for SAP (ProLE) connect Default: 5125 Port number for communication with Administration Assistant Server component Default: 5127
179

Table 7. Installation Parameters for the Administration Assistant (continued) Installation Option Installation Parameter Parameters applying to the Administration Assistant Database component (Apache Derby) Hostname or IP address: Default: Hostname of current system Port number for database connect Default: 1527
| | |
User ID and password to access internal database. The password can later be changed using the bundled program changeSettings.jar in the utils subdirectory of the Administration Assistant installation directory.
| | | | | | | | | |
Parameters applying to the Administration Assistant Database component (IBM DB2) Hostname or IP address: Default: Hostname of current system Port number for database connect Default: 50000 User ID and password of the system user for which the DB2 instance should be installed that the internal database should access. The password can later be changed using the bundled program changeSettings.jar in the utils subdirectory of the Administration Assistant installation directory.
Installation directory (on each host) Default: /opt/tivoli/tsm/tdp_r3_assist on UNIX and Linux, or C:\Program Files\tdpr3assi on Windows. Product Support Product Support Location of mail.jar (Java Mail)
Location of activation.jar (Java Beans Activation Framework):
History file directory (on Server component host) Default: history (in installation directory) History file retention time (days). Can be changed via the Administration Assistant client. Default: 14
180

Table 7. Installation Parameters for the Administration Assistant (continued) Installation Option Installation Parameter Information on the public key infrastructure (PKI): v Keystore name. Keystore containing the private and public keys of the Administration Assistant Server component when running in secure mode. If you do not yet have a public key infrastructure, the keystore can be created during the installation process. v Keystore password. Password ensuring the consistency of the keystore. The servers key pair must be protected by the same password. v Truststore name. Truststore containing a set of trusted certificates. When running in secure mode, the Administration Assistants server certificate must be verified against this truststore when the server is started. v Truststore password. Password ensuring the consistency of the truststore. This is only required if a trusted certificate needs to be imported into the truststore during the installation process. v Certificate file. Path of the certificate file in case you already have a server certificate issued by a Secure certificate authority. Communication v Certificate creation information. Information on the X.500 distinguished name (common name, organizational unit, organization name, locality name, state name, and country code) and on the validity period required in case a new self-signed certificate is to be created during the installation process. For details on this information, refer to the X.500 and X.509 standards. v New certificate file name. If the public key of a newly created server key pair needs to be distributed to client machines it will be exported to this file. v CSR file name. If the newly created server key pair will be used to request a certificate signed by a Certificate Authority, the Certificate Signing Request will be written to this file.
181

Table 7. Installation Parameters for the Administration Assistant (continued) Installation Option Installation Parameter In order to use DB2 Support, this version of the Administration Assistant requires the additional Java package DB2 JDBC Universal Driver The corresponding packages are bundled with your IBM DB2 installation. v db2jcc.jar location: Default: None Internal database managed by DB2 v db2jcc_license_cu.jar location: Default: None The Administration Assistant database is enabled for automatic storage and has a set of one or more associated storage paths. Enter at least one disk or path that DB2 is allowed to assign and allocate for its table space containers. On Windows systems enter a comma separated list of disks, such as C:, G:, X:. On UNIX and Linux systems, enter a comma separated list of paths, such as /db2,/db2/db2_v01 Default: None The name of the internal database is predefined and cannot be changed. Default: AADB Database directory: Default: aaDBSupport (in installation directory) Internal Name of the internal database database managed by Default: 'adminAssistant' Apache Derby Retention time for data in database (days). (To save this data, the backup facilities offered by Derby can be used.) Default: 175 Option: English-only or all languages Documentation Default: English-only
| | | | | | | | | | | | | | | | |
182
Appendix F. Alternate or Parallel Backup Paths and Backup Servers

With Data Protection for SAP, the term path denotes a connection between a Tivoli Storage Manager client, or better TSM node, and a Tivoli Storage Manager server. For each communication path (for example, a Tivoli Storage Manager server network address), you define a set of additional communication parameters. This set of communication parameters is called client option data and is collected under a logical server name that you can choose freely. Under UNIX or Linux, it is possible to store all client option data in a single client system option file that is called dsm.sys. Under Windows, you will need to store the client option data for each logical server in separate client option files that have the file names <servername>.opt. For example, if you have two logical Tivoli Storage Manager servers fast and slow, then you need two client option files fast.opt and slow.opt. For Windows, you need an additional client user option file, dsm.opt. All option files must reside in the same directory. Data Protection for SAP provides the capability for controlling alternate backup paths and alternate backup servers in order to use several communication links between Tivoli Storage Manager clients to: v Increase throughput by transferring data: Over multiple paths simultaneously To and from several servers in parallel v Increase the availability of the Tivoli Storage Manager client-to-server communication v Enable disaster recovery backup to a special (remote) Tivoli Storage Manager server In the profile init<SID>.utl, each path is defined by a server statement and the corresponding definitions in the Tivoli Storage Manager client system option file dsm.sys for UNIX or Linux systems or <server>.opt on Windows systems. The statement SERVER <server 1..n> denotes Tivoli Storage Manager servers in the Data Protection for SAP profile. This corresponds to the statement SERVERNAME <server 1..n> in the Tivoli Storage Manager client option file(s). These servers are identified by their TCPSERVERADDRESS and can be located on one system (multiple paths) or several systems (multiple servers). SESSIONS denotes the number of parallel session DP for SAP will schedule for the given path.
Note If only one path is used, SESSIONS must be equal to MAX_SESSIONS, the parameter identifying the total number of parallel sessions to be used (equivalent to number of tape drives/management classes). DP for SAP attempts to communicate with the Tivoli Storage Manager server using the first path in the profile. If this proves successful, DP for SAP starts the number
183
Alternate or Parallel Backup Paths and Backup Servers

of parallel sessions as specified for this path; if the attempt was unsuccessful, this path is skipped, and DP for SAP continues with the next path. This continues until as many sessions are active as were specified in the total session number (MAX_SESSIONS). If this number is never reached (for example, because several paths were inactive), DP for SAP terminates the backup job.
Parameter Settings - SERVER Statement

The SERVER statement appears in the Data Protection for SAP profile, and there are corresponding keywords in the Tivoli Storage Manager client option file. (Depending on the choice of password handling, some parameters are ignored.) The connection of the sections in the Data Protection for SAP profile and the Tivoli Storage Manager client option file is established from the logical server name, which is defined in the keywords SERVER or SERVERNAME. | | | | Note: The logical server names are also used by the View TSM Server Utilization function of the Administration Assistant. There, a separate entry is generated for each logical server name found in the system landscape, and identical logical server names are considered to represent the same server.
Table 8. SERVER Statement and Appropriate Profile and Option File Settings. Configuration possibilities single path; no password or manual password Data Protection for SAP profile init<SID>.utl SERVER ADSMNODE <server> <node>[1] Tivoli Storage Manager client option file dsm.sys or <server>.opt [2] SERVERNAME <server> TCPSERVERADDRESS <address> NODENAME must not be specified SERVERNAME <server> NODENAME <node> TCPSERVERADDRESS <address> SERVERNAME NODENAME <server 1> must not be specified TCPSERVERADDRESS <address 1> SERVERNAME <server n> NODENAME must not be specified TCPSERVERADDRESS <address n> SERVERNAME NODENAME TCPSERVERADDRESS SERVERNAME NODENAME TCPSERVERADDRESS <server 1> <node 1> <address 1>
single path; automatic password by Tivoli Storage Manager several paths/servers; no password or manual password
SERVER ADSMNODE SERVER ADSMNODE SERVER ADSMNODE
<server> must not be specified <server 1> <node 1>
<server n> <node n>
several paths/servers; automatic password by Tivoli Storage Manager[3]
SERVER ADSMNODE SERVER ADSMNODE
<server 1> must not be specified
<server n> must not be specified
<server n> <node n> <address n>
184

Table 8. SERVER Statement and Appropriate Profile and Option File Settings. (continued) Configuration possibilities several paths/servers; automatic password by Tivoli Storage Manager with Tivoli Storage Manager API 5.2 or higher [4] Data Protection for SAP profile init<SID>.utl SERVER ADSMNODE <server> must not be specified TCP_ADDRESS <address 1> SERVER <server n> ADSMNODE must not be specified TCP_ADDRESS <address n> Tivoli Storage Manager client option file dsm.sys or <server>.opt [2] SERVERNAME <server NODENAME <node> TCPSERVERADDRESS <address>
Notes: [1] [2] If ADSMNODE is not specified, the host name is used. On UNIX or Linux, dsm.sys is the single client option file for all Tivoli Storage Manager servers. On Windows, there is a separate client option file <server>.opt for each Tivoli Storage Manager server. If two different physical machines have the same TSM node name or if multiple paths are defined on one node using several server stanzas, passwordaccess generate may only work for the first stanza that is used after password expiration. During the first client-server contact, the user is prompted for the same password for each server stanza separately, and a copy of the password is stored for each stanza. When the password expires, a new password is generated for the stanza that connects the first client-server contact. All subsequent attempts to connect via other server stanzas will fail, because there is no logical link between their copies of the old password and the updated copy generated by the first stanza used after password expiration. To avoid the problem, update the passwords before they expire, to solve the problem if the passwords have expired, proceed as follows: 1. dsmadmc and update the password on the server. 2. Run dsmc -servername=stanza1 and use the new password to generate a proper entry. 3. Run dsmc -servername=stanza2 and use the new password to generate the proper entry. If you are using Tivoli Storage Manager API 5.2 or higher you can make use of the new parameter TCP_ADDRESS in the Data Protection for SAP profile. This makes the multiple stanzas in the Tivoli Storage Manager client option file for multiple paths obsolete and eliminates the problem when updating the password (see [3]).
[3]
[4]
Example 1: Use of Alternate Paths for Increased Availability

Assume the following configuration: Tivoli Storage Manager server with: 2 tape drives 2 LAN connections.
Appendix F. Backup Paths and Servers
185

A backup is normally performed via network path 1 (SERVER statement 1). If this is unavailable the backup shall be performed using network path 2 (SERVER statement 2). The definitions in the Data Protection for SAP profile could be as shown in the example below. If path 1 is active, DP for SAP will start the 2 sessions as defined in the SERVER statement for path 1. Since MAX_SESSIONS is also 2, no more sessions will be started. If path 1 is inactive, Data Protection for SAP will start 2 sessions on path 2. Since this equals the MAX_SESSIONS definition as well, backup will be executed using path 2. | | | Even if the logical names server_a and server_b actually point to the same TSM server, the Administration Assistant will still consider them to be two different TSM servers.
Data Protection for SAP profile. Example 1

MAX_SESSIONS 2 . . SERVER server_a ADSMNODE SESSIONS PASSWORDREQUIRED BRBACKUPMGTCLASS BRARCHIVEMGTCLASS # USE_AT SERVER server_b ADSMNODE SESSIONS PASSWORDREQUIRED BRBACKUPMGTCLASS BRARCHIVEMGTCLASS # USE_AT # 2 tape drives # via network path 1 C21 2 YES mdb mlog1 mlog2 0 1 2 3 4 5 6 # via network path 2 C21 2 YES mdb mlog1 mlog2 0 1 2 3 4 5 6
186

|
Example 2: Use of Parallel Servers for Increased Performance

Assume the following configuration: Two Tivoli Storage Manager servers with connections via two network paths: server_a, TCP/IP address xxx.xxx.xxx.xxx server_b, TCP/IP address yyy.yyy.yyy.yyy Each of these servers has: - two tape drives A SAP database server connected to two networks. Backups are done on both systems every day. The definitions in the Data Protection for SAP profile could be as shown in the example below.

MAX_SESSIONS 4 . . SERVER server_a ADSMNODE SESSIONS PASSWORDREQUIRED BRBACKUPMGTCLASS BRARCHIVEMGTCLASS # USE_AT SERVER server_b SESSIONS PASSWORDREQUIRED BRBACKUPMGTCLASS BRARCHIVEMGTCLASS # USE_AT # 4 tape drives # via network path 1 C21 2 YES MDB MLOG1 MLOG2 MLOG3 MLOG4 1 2 3 4 5 6 7 # via network path 2 2 YES MDB MLOG1 MLOG2 MLOG3 MLOG4 1 2 3 4 5 6 7 ADSMNODE C21
Appendix F. Backup Paths and Servers
187
Example 3: Use of Alternate Servers for Disaster Recovery

Assume the following configuration: Two Tivoli Storage Manager servers: server_a, TCP/IP address xxx.xxx.xxx.xxx server_b, TCP/IP address yyy.yyy.yyy.yyy Each of these servers with: four tape drives (MAX_SESSIONS 4). A SAP database server connected to this FDDI network. Normal backups are to be performed with server a, which is local to the SAP database server. Every Friday a disaster recovery backup should be stored on a remote Tivoli Storage Manager server (server b). The definitions in the Data Protection for SAP profile could be as shown in the example below.

MAX_SESSIONS 4 . . SERVER server_a ADSMNODE SESSIONS PASSWORDREQUIRED BRBACKUPMGTCLASS BRARCHIVEMGTCLASS USE_AT SERVER server_b ADSMNODE SESSIONS PASSWORDREQUIRED BRBACKUPMGTCLASS BRARCHIVEMGTCLASS USE_AT # 4 tape drives # via network path 1 C21 4 YES MDB MLOG1 MLOG2 MLOG3 MLOG4 1 2 3 4 # via network path 2 C21 4 YES MDB MLOG1 MLOG2 MLOG3 MLOG4 5 # for Disaster Recovery
188
Appendix G. Tablespace Definition Information (TDI)

In order to automate a redirected restore as much as possible, Backup Object Manager needs information on the tablespaces and the tablespace containers used in the original database in order to be able to create the tablespace containers of the target database accordingly. For each tablespace, the following information is required: v The ID and name of the tablespace. v The type of the tablespace, i. e. whether it is system (SMS) or database managed (DMS) v The page size in bytes. v The extent size in pages. v The number of pages used. This number can help the administrator when resizing containers. Backup Object Manager also calculates the numbers of total pages and of usable pages from the data stored for each tablepspace container.) v Information on the tablespace containers used for the tablespace. For each tablespace container, the following information must be available v The ID of the tablespace container. v The name of the tablespace container, i.e. the directory containing an SMS container or the file containing an DMS container, respectively. v The type of the tablespace container, i. e. whether a database managed container is stored in a file or in a raw device. v For DMS tablespaces, the total number of pages stored in the container. The TDI and the DB2 backup images are stored together on the TSM server. They are associated using the combination of the instance name of the database, the database alias, the database node number, and the timestamp of the backup. The name of the TDI is constructed in the following way: <DB2 instance>-<DB2 alias>-<DB2 node number><timestamp>.tdf. The TDI can be retrieved from TSM separately with the Backup Object Manager command r_tdi and can be stored as an ASCII file in a specified file system. The availability of TDI in the filesystem is a prerequiste for the Backup Object Manager redirected restore in batch mode. To prepare for a batch-mode redirected restore, the following changes can be done to the TDI file: v adding or removing of tablespace containers from dedicated tablespaces v modifying names (locations) of tablespace containers
189
Tablespace Definition Information (TDI)

Following, you find a sample TDI file:
; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; IBM Tivoli Storage Manager for Enterprise Resource Planning Data Protection for SAP(R) for DB2 UDB - Tablespace Definition Information You may modify the containers in the tablespace blocks, remove containers, or add new ones. The container statement has the following form: - for an SMS tablespace: Container[<ID>] = "<PATH>" - for a DMS tablespace: Container[<ID>] = <TYPE> | "<PATH>" | <SIZE> Use empty brackets without an <ID> for new containers. <TYPE> can be one of "file" or "device". Note, that a TDI file containing a device container cannot be used for Backup Object Manager redirected restore. You must ensure that each tablespace block has at least one container! DO NOT EDIT ANYTHING ELSE EXCEPT THE CONTAINER STATEMENTS!
[TDI] Version = 1.0 Generator = Data Protection for SAP(R) 5.3.1.0 [Backup] Alias = C21 Instance = DB2C21 Node = 0 Timestamp = 20040530083000 [Tablespace 0 "SYSCATSPACE" dms 4096 32 18784] Container[0] = file | "/db2/C21/sapdata1/SYSCATSPACE.container000" | 20000" [Tablespace 3 "TEMPSPACE" sms 4096 32 1] Container[0] = "/db2/C21/sapdatat/TEMP4" [Tablespace 4 "PSAPUSER1D" dms 4096 32 1056] Container[0] = file | "/db2/C21/sapdata2/PSAPUSER1D.container000" | 4096 Container[1] = file | "/db2/C21/sapdata3/PSAPUSER1D.container001" | 4096 [Tablespace 5 "PSAPUSER1I" dms 4096 32 928] Container[0] = file | "/db2/C21/sapdata4/PSAPUSER1I.container000" | 8192
The [TDI] header block is used to identify the data as TDI and holds some meta-information about it. The Version key holds the version of the TDI syntax. The Generator key denotes some product information. The [Backup] block holds information about the database backup the TDI is associated with. This information must be kept within the TDI file so that it is available even when the file has been renamed. The [Tablespace] block marks the start of the container definitions of a specific tablespace. The block header contains - exactly in this order - the ID of the tablespace, its name, its type, the page size in bytes, the extent size in pages and the number of used pages in the tablespace.
Note Do not change any data within the tablespace block header!
190
Note Each container statement defines one container of a tablespace. Its ID is denoted in square brackets when the line was written by the system. If a new container is to be added to a tablespace, the ID is not yet known. Therefore, the administrator specifies a new container without an ID, just writing empty brackets. For an SMS tablespace, only the fully qualified path is specified. For a DMS tablespace, the type, the location and the size of the container is specified, in exactly this order and separated by a vertical bar (|). The type is given by one of the strings file or device. The size will be interpreted as number of pages unless a unit is specified. In this case, the unit is used. Names of tablespaces and paths must be quoted strings.
Appendix G. Tablespace Definition Information
191
192
Appendix H. Data Protection for SAP Setup Examples

Sample DB2 Vendor Environment File
During installation, a DB2 vendor environment file (vendor.env) is created from the information entered in the installation dialog panels. A sample DB2 vendor environment file is included in the DP for SAP installation package.
Note Ensure that there are no blanks within the paths specified for the vendor-specific environment variables of the vendor environment file. DB2 is currently unable to handle embedded blanks. Note that in the case of a standard Windows installation, the DP for SAP profile is located at
c:\Program Files\Tivoli\tsm\tdp_r3\db2\initSID.utl
Sample DB2 vendor environment file for UNIX or Linux:

XINT_PROFILE=/db2/C21/tdpr3/initC21.utl TDP_DIR=/db2/C21/tdpr3/tdplog BACKOM_LOCATION=/usr/tivoli/tsm/tdp_r3/db264/backom
Sample DB2 vendor environment file for Windows:

XINT_PROFILE=c:\db2\C21\tdpr3\initC21.utl TDP_DIR=c:\db2\C21\tdpr3\tdplog BACKOM_LOCATION=c:\tivoli\tsm\tdp_r3\db2\backom.exe
193
194
Appendix I. Reference Material for the Administration Assistant

Sample Command Files for Scheduling Reports
You may want to create a command file ( .bat or .cmd on Windows or .sh on UNIX systems ) setting the correct environment and scheduling one or more reports on the scheduling client system.
Sample Shell Script for Scheduling a Report from a UNIX Scheduling Client
File scheduledReport.sh is included in your Data Protection for SAP package and is copied to the installation path of the Administration Assistant.
#-------------------------------------------------------------------------# # Tivoli Storage Manager for ERP. Data Protection for SAP (R) # # Sample command file for the Administration Assistant scheduling client # # -------------------------------------------------------------------------# ***** NOTE ***** NOTE ***** NOTE ***** # # This script is provided as a model and should be # carefully tailored to the needs of the specific site. # # ***** NOTE ***** NOTE ***** NOTE ***** #-------------------------------------------------------------------------export CLASSPATH=/reporting/Admt.jar:$CLASSPATH export PATH=/usr/bin:$PATH java -classpath $CLASSPATH com.ibm.bkit.schedulerIF.Sched_Main xxx.xxx.xxx.xxx... ... 1099 myReport ADMIN admin directory=/myreports log=/tmp/reportlogs
Sample Command File for Scheduling a Report from a Windows Scheduling Client
File scheduledReport.cmd is included in your Data Protection for SAP package and is copied to the installation path of the Administration Assistant Server component.
#-------------------------------------------------------------------------# # Tivoli Storage Manager for ERP. Data Protection for SAP (R) # # Sample command file for the Administration Assistant scheduling client # # -------------------------------------------------------------------------# ***** NOTE ***** NOTE ***** NOTE ***** # # This script is provided as a model and should be # carefully tailored to the needs of the specific site. # # ***** NOTE ***** NOTE ***** NOTE ***** #-------------------------------------------------------------------------set CLASSPATH=C:\ProgramFiles\reporting\Admt.jar set PATH=C:\Program Files\IBM\Java142\jre\bin:%PATH% java -cp %CLASSPATH% com.ibm.bkit.schedulerIF.Sched_Main xxx.xxx.xxx.xxx ... ... 1099 myReport ADMIN admin directory=C:\reports log=C:\reportlogs
195
Reference Material for the Administration Assistant

| | | | | | | | | | | | | | | | | | | | | | |
Sample Custom SQL File

# CUSTOM SQL FILE FOR THE ADMINISTRATION ASSISTANT # # This file should only be changed by an IBM Employee # After the changes you have to check this file using CustomSQLFilecheck # # NOTE: Each entry must be coded in one line. The multi-line format # shown below is for illustration purposes only. # # # Sample threshold definition: backup size > 500 GB, display group 1, backup type 2 # <sql>select * from AdminAssistant.tsmrun where amount > 500000000000</sql> <description>Amount over 500 GB</description> <programid>0</programid> <actionid>0</actionid> <displaygroup>1</displaygroup> <backuptype>2</backuptype> <executionmode>0</executionmode> <param>emailAdress@email.com</param> #
196
Appendix J. Using DP for SAP to Back Up and Restore Files and Databases
The following examples show how you can start DB2 database/tablespace backups or restores from the command line using DB2 CLP.
Backups and Restores in Non-Partitioned Database Environments Starting Backups in a Non-Partitioned Database Environment
To start a DB2 backup/restore with Data Protection for SAP, log on as user db2<SID> or <SID>adm. In the following examples, the variable <shared library> stands for the full path of the DP for SAP shared library (UNIX and Linux) or DLL (Windows). DB2 database/tablespace backups can be done as follows: v full online backup (database parameter LOGRETAIN has to be activated)
db2 backup db <dbname> online load <shared library>
v online tablespace backup (database parameter LOGRETAIN has to be activated)

db2 backup db <dbname> online tablespace (tablespace_name#1, ...) load <shared library>
v DB2 offline log files backup with BRARCHIVE For backing up the DB2 offline log files, you should use the program BRARCHIVE, which is part of the SAP-DB2 Administration Tools package.
brarchive -s -d adsm -vndlib <shared library> -out
For a detailed description of the BRARCHIVE functionality, refer to the Database Administration Guide, which is included in your SAP documentation.
Starting Restores in a Non-Partitioned Database Environment

Note: Every successful backup run generates a timestamp that is needed for later restore operations. These timestamps are written to the DB2 Recovery History file (RHF), which can be queried with DB2 commands. The timestamps of backup images currently stored on the TSM server can be queried using the Backup Object Manager query commands. For details, see Managing Backup Objects on page 55. If no timestamp is specified in a restore command, the latest backup image found on Tivoli Storage Manager will be restored. DB2 database/tablespace restores can be done as follows: v full restore to a certain point in time
197
db2 restore db <dbname> load <shared library> taken at <timestamp>
or
backom -c r_db -a <dbname> -t <timestamp>
backom -c r_db -a <dbname> -t <timestamp>
v online tablespace restore

db2 restore db <dbname> tablespace (tablespace_name#1, ...) online load <shared library> taken at <timestamp>
or
backom -c r_ts -a <dbname> -t <timestamp> -O
v Recovery History File restore

db2 restore db <dbname> history file online load <shared library>
or
backom -c r_hfile -a <dbname>
v DB2 offline log files restore with BRRESTORE For restoring DB2 offline log files for a subsequent recovery, you should use the program BRRESTORE, which is part of the SAP-DB2 Administration Tools package. Of course, only those offline log files that were backed up with BRARCHIVE (see above) can be restored with BRRESTORE.
brrestore -a -d adsm -vndlib <shared library> -out
For a detailed description of the BRRESTORE functionality, refer to the Database Administration Guide, which is included in your SAP documentation. Any Data Protection for SAP process results can be checked by analyzing the Data Protection for SAP log files. These log files may contain success, warning, and error messages. For details, refer to Appendix B, Data Protection for SAP (DB2) Messages, on page 129.
Backups and Restores in Partitioned Database Environments

| | | Note: Starting with DB2 V9.5, the Single System View (SSV) function allows backup of all partitions from the catalog partition. For more information, see Using DB2 Single System View (SSV) for Backup on page 200. Partitioned database backups and restores can be made in parallel except for the catalog partition. A requirement of DB2 is to back up and restore the catalog partition separately from all other DB2 partitions. Thus, backup and restore operations of a partitioned database are two-step scenarios, whereby the first step is to backup/restore the catalog partition and the second step to backup and restore all other partitions in parallel.
198
Data Protection for SAP will use the DB2 command db2_all for separation and parallelization of the backup and restore commands. The db2_all command provides special characters for handling partitions and for running commands in parallel or sequentially (see the DB2 Administration Guide for further details). The DB2 db2_all command supports the following special characters or character combinations: v <<+N< execute a command only on partition N v <<-N< execute a command on all partitions except on partition N v " substitute occurrences of () by the machine index and substitute occurrences of ## by the partition number v ; runs the commands in parallel in the background and terminates the command after all remote commands are completed.
All these special characters and the possibilities of DP for SAP help to configure backup and restore runs with DP for SAP in that way, that each partition of the database can be backed up or restores with its special adapted environment. The following examples for partitioned database backups and restores with DP for SAP illustrate possible scenarios: v full offline backup of all database partitions with 2 sessions, starting with the catalog partition (here partition 0) followed by all other partitions in parallel
db2_all <<+0< db2 backup db <SID> load <shared library> open 2 sessions db2_all <<-0<; db2 backup db <SID> load <shared library> open 2 sessions
v full restore of latest backup starting with the catalog partition (here partition 0) followed by all other partitions (here 3 partitions) in parallel using different number of sessions for some of the partitions. Before starting the restore, a temporary environment script, e.g. /db2/<SID>/EEEenv.sh has to be created (the directory /db2/<SID> has to be an NFS share between all hosts where the partitions reside). For the example, it would contain the following: export SESSION0=2 export SESSION1=2 export SESSION2=4 export SESSION3=4 which means, partitions 0 and 1 will be restored with 2 sessions and partitions 2 and 3 will be restored with 4 sessions. Thus, the restore command to be issued would be:
db2_all <<+0<" ./db2/<SID>/EEEenv.sh; db2 restore db <SID> load <shared library> open $SESSION## db2_all <<+0<;" ./db2/<SID>/EEEenv.sh; db2 restore db <SID> load <shared library> open $SESSION##
The string $SESSION## in the db2_all command will be replaced while executing it with the value provided by the environment variables SESSION0 to SESSION3. v full online backup of all database partitions, starting with the catalog partition (here partition 1) followed by all other partitions in parallel using different Data Protection for SAP profiles for each partition. To support this scenario, for each partition one Data Protection for SAP profile (init<SID>.utl) must be created and maintained. Each profile can have different
Appendix J. Backup and Restore
199
settings for TSM node and management class. In this example, the profiles needed would be: init<SID>.utl.1 (profile for partition 1) init<SID>.utl.2 (profile for partition 2) init<SID>.utl.3 (profile for partition 3) init<SID>.utl.4 (profile for partition 4) In addition for each partition a DP for SAP vendor environment file (vendor.env) must be created and maintained. Each vendor environment file has an entry XINT_PROFILE which refers to the corresponding Data Protection for SAP profile, e.g.:
vendor.env.1 vendor.env.2 vendor.env.3 vendor.env.4 (environment (environment (environment (environment for for for for partition partition partition partition 1 2 3 4 -> -> -> -> XINT_PROFILE=/db2/<SID>/vendor.env.1) XINT_PROFILE=/db2/<SID>/vendor.env.2) XINT_PROFILE=/db2/<SID>/vendor.env.3) XINT_PROFILE=/db2/<SID>/vendor.env.4)
Thus, the backup command to be issued would be:

db2_all <<+1<" db2 backup db <SID> online load <shared library> options /db2/<SID>/ vendor.env.## db2_all <<+1<;" db2 backup db <SID> online load <shared library> options /db2/<SID>/ vendor.env.##
The string vendor.env.## in the db2_all command will be replaced while executing it with the values vendor.env.1 - vendor.env.4, whereby the special characters ## will be substituted by the corresponding partition number. | | | | | | | | | | | | | | | | | | | | | | | | |
Using DB2 Single System View (SSV) for Backup

Starting with DB2 V9.5, you can back up multiple database partitions at once using the single system view (SSV) backup. In earlier releases, you need to back up partitioned databases one partition at a time. This procedure is error-prone and time consuming. If you back up a partitioned database one partition at a time, you cannot include in the backup images the log files required to restore and recover. Restoring multiple partitions that were backed up individually is complicated as well, because the backup timestamp for each partition is slightly different. Because of this, identifying all database partitions belonging to the same backup is difficult, and determining the minimum recovery time for the backup that contains these partitions is difficult. Use of db2_all (see Backups and Restores in Partitioned Database Environments on page 198) simplifies the backup of partitioned databases somewhat, but there are still restrictions with the backup and restore operations that complicate the tasks. As of Version 9.5, when you perform a backup operation from the catalog node of a partitioned database, you can specify which partitions to include in the backup, or specify that all the database partitions should be included. The specified partitions will be backed up simultaneously, and the backup timestamp associated with all specified database partitions will be the same. Also, you can include database logs with an SSV backup; including logs in backup images is now the default behavior. Finally, when you restore from an SSV backup image, you can specify to roll forward to end of logs, which is the minimum recovery time calculated by the database manager.
200
For more information refer to the DB2 Command Reference.
Appendix J. Backup and Restore
201
202
Appendix K. Preparing Tivoli Storage Manager for DP for SAP

This chapter gives an overview of the Tivoli Storage Manager and explains the procedures for setting up TSM for working with Data Protection for SAP in an SAP environment. A typical list of actions that the Tivoli Storage Manager installer or administrator must perform to prepare Tivoli Storage Manager to work in an SAP environment will be explained.
Note The following steps and procedures are only samples. The actual values in your specific environment may be different.
Configuring the Tivoli Storage Manager Server

This section shows the procedure for setting up the Tivoli Storage Manager server. General server configurations will be described first and finally specific server configurations, such as setup of storage devices. The Tivoli Storage Manager commands presented in this chapter are shown in full for ease of understanding. In the Tivoli Storage Manager command line interface, short cuts or abbreviations for all commands and parameters can be used for convenience. Tivoli Storage Manager also has a Web-browser-based Graphical User Interface (GUI).
General Considerations for TSM

Before starting the installation, some important performance issues should be considered. The careful choice of the server that is to be installed, the network topology, and the use of powerful hardware can improve performance within the system landscape and can avoid performance bottlenecks. v Host for Tivoli Storage Manager server. The Tivoli Storage Manager server should be installed on an exclusive machine. This procedure avoids concurrent processes and disk I/O accessing with other applications. In a single SAP system landscape, a single Tivoli Storage Manager server is sufficient. If you plan to use the Storage Manager to back up/restore other clients as well, you should consider either installing the server software on a large machine or using several Tivoli Storage Manager servers. v Network topology. Network topologies such as Ethernet, Token Ring, FDDI and Fast Ethernet work all well with Tivoli Storage Manager. In general, the fastest network topology like FDDI or Fast Ethernet should be used to prevent bottlenecks during backup/restore operations. Tivoli Storage Manager supports multiple network adapters, increasing server throughput by providing multiple connections to the same network or several physically distinct networks with the same server. v RS/6000 SP environment. An RS/6000 SP node can be used for a Tivoli Storage Manager server. The use of a High Performance Switch network will improve performance of backup/restore operations on the Tivoli Storage Manager server.
203
Preparing Tivoli Storage Manager for DP for SAP
Prerequisites
It is assumed that the Tivoli Storage Manager server has already been successfully installed. This means that the following steps have been completed: v Tivoli Storage Manager server has been installed. For information on the required release and maintenance level, refer to the DP for SAP release notice. v Recovery log volume has been allocated and initialized. v Recovery log mirror volume has been allocated and initialized. v Database volume has been allocated and initialized. v Database mirror volume has been allocated and initialized. v Additional labeled volumes for the backup and archive storage pools have been allocated and initialized (disks, tapes or combinations). v Licenses have been registered. v The Tivoli Storage Manager server has been started. For information on installing Tivoli Storage Manager, see the Tivoli Storage Manager Quick Start manual.
Note The latest code fixes for Tivoli Storage Manager can be found at: ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance
Adjusting Tivoli Storage Manager for DP for SAP

Note The following steps and procedures are only samples. The actual values in your specific environment may be different. In order to adjust the installed TSM to the DP for SAP, the following activities must be performed.
1. Storage Device Setup

A storage device defines a device class, which will handle one type of media, e.g., tape libraries or jukeboxes. There is a default device class defined for disks called DISK which obviates the need for a redefinition. For proper storage device setup, check the following items established within the Tivoli Storage Manager server during the installation procedure: v Query defined library
q library
v Query defined drives

q drive
v Query defined device class

q devclass
204
2. Storage Pool Definition

A storage pool is a named collection of storage volumes that are associated with one device class. Each storage pool represents a collection of volumes that are the same media type. The storage pool setup defines the storage hierarchy for the appropriate environment. In an SAP environment, there are different kinds of data to be backed up. These are: v SAP system data v SAP database data (containers, offline log files) To separate this data within the Tivoli Storage Manager, you must define appropriate storage pools for each of these data collections. The following section gives examples of how storage pools within Tivoli Storage Manager can be defined in consideration of the requirements mentioned above. To define storage pools within the Tivoli Storage Manager server, log on as Tivoli Storage Manager Administrator using the Admin Command Line or the Web Admin and invoke the following commands: 1. Definition of a storage pool for the SAP system data
define stgpool sap_incr <device_class_name> maxscr=5
2. Definition of a storage pool for the containers

define stgpool sap_db <device_class_name> maxscr=20
3. Definition of a storage pool for the offline log files

define stgpool sap_log1 <device_class_name> maxscr=3
Note When you associate a library tape device, you have to define the maximum number of scratch volumes (labeled volumes which are empty or contain no valid data) this storage pool will be allowed to use (parameter maxscr). The maximum number of scratch tapes depends on the size of the database, the capacity of the tapes, the number of scratch volumes available and how many versions of the backup you will keep. Replace these values with your estimates.
3. Policy Definition
Tivoli Storage Manager policies are used to specify how files are backed up, archived, migrated from client node storage, and managed in server storage. A policy definition includes the definition of a policy domain, a policy set, management classes and copy groups. After the definition phase, you need to assign a default policy set and validate and activate it. For the policy definition, log on as a Tivoli Storage Manager Administrator using the Admin Command Line or the Web Admin and invoke the following commands: 1. Policy domain and policy set definition
205
define domain sap_c21 define policyset sap_c21 p_c21
2. Management Class definition for file system backups, data files, offline log files and copies of offlinelog files
define define define define mgmtclass mgmtclass mgmtclass mgmtclass sap_c21 sap_c21 sap_c21 sap_c21 p_c21 p_c21 p_c21 p_c21 mdefault mdb mlog1 mlog2
Note If you are planning to use this Tivoli Storage Manager server with multiple SAP systems, it is recommended that you use a set of different management classes for each system. 3. Copy Group definition
define define define define define copygroup copygroup copygroup copygroup copygroup sap_c21 sap_c21 sap_c21 sap_c21 sap_c21 p_c21 p_c21 p_c21 p_c21 p_c21 mdefault type=backup destination=sap_incr mdefault type=archive destination=archivepool mdb type=archive destination=sap_db retver=nolimit mlog1 type=archive destination=sap_log1 retver=nolimit mlog2 type=archive destination=sap_log2 retver=nolimit
DP for SAP uses its own version control mechanism for managing SAP database backups. To do this, DP for SAP backs up all data only to management classes for which an archive copy group has been defined (parameter type set to archive; for a definition, see Glossary page 231). In addition, to prevent backed up files within Tivoli Storage Manager being deleted because of their expiration date (Tivoli Storage Manager deletes expired files), the copy group parameter retver (specifies the number of days a file is to be kept) should be set to unlimited (9999 or nolimit). 4. Assigning the default management class
assign defmgmtclass sap_c21 p_c21 mdefault
5. Validating and activating the policy set

validate policyset sap_c21 p_c21 activate policyset sap_c21 p_c21
4. Node Definition
The Tivoli Storage Manager server views its registered clients, application clients, host servers, and source servers as nodes that require services and resources from the server. To register a node within Tivoli Storage Manager, log on as Tivoli Storage Manager administrator using the Admin Command Line or the Web Admin and invoke the following command:
register node C21 passwd domain=sap_c21 maxnummp=8
206
Note If you are using two or more tape drives, you may want to pay special attention to the node parameter maxnummp. It defines the maximum number of mount points that one node can use. The default value is 1. If one node should use more than one mount point, the parameter must be set to the desired number of mount points. This parameter should not be set higher than the total number of drives available on the TSM Server.
Configuring the Tivoli Storage Manager Clients

After the server configuration, you have to configure the clients that will use the Tivoli Storage Manager server. These include the backup-archive client for the file system backups and the Application Programming Interface (API) client for interface programs. The Tivoli Storage Manager backup-archive client will be used for file system backups. The API client allows users to enhance existing applications with backup, archive, restore, and retrieve services. An installed and confirmed API client is a prerequisite for DP for SAP.
General Considerations
First of all, if a successful installation of Tivoli Storage Manager backup/archive client and API client is to be performed, the clients must be installed on all nodes that will interface with the Tivoli Storage Manager server. In the context of an SAP system landscape, this means that the Tivoli Storage Manager backup/archive client must be installed on every machine scheduled for a file system backup, for example, SAP application servers and the SAP database server. The Tivoli Storage Manager API client only needs to be installed on the SAP database server machine to enable backup/restore operations of the SAP database in combination with the backup interface program DP for SAP. | | | | | | | Note: The Administration Assistant uses the logical TSM server names in its View TSM Server Utilization function. Identical logical names are considered to represent the same TSM server, but different entries are generated for each logical server name found in the system landscape. Therefore, it is recommended whenever possible to use identical logical server names when pointing to the same TSM server throughout the system landscape, and to use different logical server names when different TSM servers are addressed.
Tivoli Storage Manager Clients on UNIX or Linux Systems

The setup for the Tivoli Storage Manager client is effected in UNIX or Linux environments by changing the files dsm.opt and dsm.sys. Subsequently, the include/exclude file must be configured. It defines which files the Tivoli Storage Manager backup/archive client will include or exclude for any backup, archive or hierarchical storage procedure. Examples of an include/exclude file for UNIX or Linux can be found in Sample TSM Profiles for UNIX or Linux on page 213. The following serves as a quick guide for configuring the Tivoli Storage Manager. It presents a typical list of actions that the Tivoli Storage Manager installer or administrator must perform to prepare the Tivoli Storage Manager to operate in an SAP environment. Follow these steps:
207

1. Install the Tivoli Storage Manager client software on the SAP database server machine. 2. Edit the client system options file dsm.sys and set the following values, as appropriate to your installation:
Servername TCPPort TCPServeraddress InclExcl Compression server_a 1500 xxx.xxx.xxx.xxx or servername /usr/tivoli/tsm/client/ba/bin/inclexcl.list OFF
3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are on the same machine. This makes TCP/IP communication a little faster. 4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude the files listed in inclexcl.list. This is optional. You may want to exclude all database files that are processed by the DB2 database backup. 5. If you have tape drives with hardware compression attached to the Tivoli Storage Manager server, you might get better throughput with the hardware compression than you would with the Tivoli Storage Manager client software compression (Compression ON). However, it is not recommended to combine the various compression methods. 6. Edit the client user options file dsm.opt and set the following values:
LANGUAGE NUMBERFormat TAPEPROMPT TIMEFORMAT AMENG 1 NO 1 (this is the default value) (this is the default value) (this is the default value)
Note When the Tivoli Storage Manager API client is installed on UNIX or Linux systems, ensure that there is a softlink /usr/lib/libApiDS.a pointing to the libApiDS.a file in the installation directory (/usr/tivoli/tsm/client/api/bin) of the Tivoli Storage Manager API. Starting with Release 5 Version 3, Tivoli Storage Manager clients require an error log. For each process, a single TSM error log can be specified, regardless of the number of TSM server stanzas involved. The TSM error log is determined by the following rules: 1. The TSM error log file is defined with keyword ERRORlogname in the client system options file (dsm.sys): In the presence of a client user options file (dsm.opt), the TSM error log is defined by the ERRORlogname specified in the server stanza of dsm.sys of the server pointed to by dsm.opt. In the absence of a client user options file (dsm.opt), the TSM error log is defined by the ERRORlogname specified in the first server stanza in dsm.sys. 2. If there is no ERRORlogname defined in the appropriate stanza of dsm.sys the TSM error log path is taken from environment variable DSMI_LOG. 3. If there is no error log file or path explicitly defined TSM errors are logged to file dsierror.log in the local path. Make sure that the error log specified can be opened for writing.
208

It is recommended to set up the Tivoli Storage Manager client so that different processes write to separate error logs. Therefore, the error log path should be defined in the environment (DSMI_LOG) if the client options files are shared among processes.
Tivoli Storage Manager Clients on Windows Systems

The setup for the Tivoli Storage Manager client is effected in Windows environments by changing the file <server_a>.opt (where server_a is the logical server name in the initSID.utl file, see profile keyword SERVER on page 120). Subsequently, the include/exclude file must be configured. It defines which files the Tivoli Storage Manager backup/archive client will include or exclude for any backup, archive or hierarchical storage procedure. Examples of an include/exclude file for Windows can be found in Sample TSM Profiles for Windows on page 214. The following serves as a quick guide for configuring the Tivoli Storage Manager. It presents a typical list of actions that the Tivoli Storage Manager installer or administrator must perform to prepare Tivoli Storage Manager for operation in an SAP environment. Follow these steps: 1. Install the Tivoli Storage Manager client software on the SAP database server machine. 2. For each logical Tivoli Storage Manager server you need a corresponding client option file. In the following example, the file name must be server_a.opt since server_a is the logical server name:
TCPPort TCPServeraddress InclExcl Compression 1500 xxx.xxx.xxx.xxx c:\tivoli\tsm\baclient\inclexcl.list OFF
In addition, the environment variable DSMI_CONFIG must point to the corresponding client options file, e.g., c:\tivoli\tsm\api\server_a.opt . 3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are on the same machine. This makes TCP/IP communication a little faster. 4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude the files listed in inclexcl.list. This is optional. You may want to exclude all database files that are processed by the DB2 database backup. 5. If you have tape drives with hardware compression attached to the Tivoli Storage Manager server, you might get better throughput with the hardware compression than you would with the Tivoli Storage Manager client software compression (Compression ON). However, it is not recommended to combine the various compression methods. Starting with Release 5 Version 3, Tivoli Storage Manager clients require an error log. For each process, a single TSM error log can be specified, regardless of the number of TSM client option files <server>.opt involved. The TSM error log is determined by the following rules: 1. The TSM Client log is written to the file specified in the environment (DSMI_LOG). 2. If DSMI_LOG is absent or cannot be written to, the TSM Client log is written to the file specified with keyword ERRORlogname in the client system options file dsm.opt.
209

3. If there is no ERRORlogname in dsm.opt or if it cannot be written to, the TSM Client log is written to file dsierror.log in the local path.
It is recommended to set up the Tivoli Storage Manager client so that different processes write to separate error logs. Therefore, the error log path should be defined in the environment (DSMI_LOG) if the client options files are shared among processes.
Password Handling
For a discussion of the password handling methods, please see Modifying the Handling of the TSM Password on page 43. After selecting the suitable method, follow the steps in the appropriate configuration matrix below to set the keywords and parameters in the various profiles accordingly.
210
Password Configuration Matrix (UNIX or Linux)

After you have selected the suitable password handling alternative, follow the configuration matrix to set the keywords/parameters in the different profiles accordingly. Proceed as indicated by the step number.
Table 9. Password Handling for UNIX or Linux Step Profile/Action Parameter No Password Manual Set by Tivoli Storage Manager ON <n days> GENERATE <path> <nodename> <password> <password> (see note 3)
Tivoli Storage Manager admin dsm.sys
AUTHENTICATION EXPIRATION PERIOD (see note 1) PASSWORDACCESS PASSWORDDIR (see note 5) NODENAME UPDATE NODE (see notes 1, 6) SET PASSWORD (see note 8) For each SERVER statement specify: PASSWORDREQUIRED ADSMNODE backom -c password
OFF n.a. n.a. n.a. n.a. n.a. n.a.
ON <n days> (see note 2) PROMPT n.a. n.a. <password> n.a.
3 4
Tivoli Storage Manager admin Tivoli Storage Manager client (root user) DP for SAP profile (init<SID>.utl)
NO <nodename> n.a.
YES <nodename> <password> (see notes 3,7)
NO (see note 4) <password> (see notes 3,7
6 7
Command line
DP for SAP operation permission on data files for with user other than user: DBA db2<SID> other user
read, write none
read, write none
read, write read, write
Notes: 1. See Tivoli Storage Manager documentation. 2. If you are using manual password generation during testing, make sure that the expiration period is set to a sufficiently long time. 3. This password must be the one that is effective on the TSM server for the node. 4. ADSMNODE must not be set when PASSWORDACCESS generate is set. 5. The users <SID>adm and db2<SID> must have read and write permission for the path specified. 6. This step is only necessary if the password is expired (manual handling only) or needs to be changed on the TSM server. 7. A password must be entered for each server statement in the DP for SAP profile. 8. This step is necessary in case the Tivoli Storage Manager Backup Archive Client is used to access data for the same node.
211
Password Configuration Matrix (Windows)

After you have selected the suitable password handling alternative, follow the configuration matrix to set the keywords/parameters in the different profiles accordingly. Proceed as indicated by the step number.
Table 10. Password Handling for Windows Step Profile/Action Parameter No Password Manual Set by Tivoli Storage Manager ON <n days> GENERATE <path> <nodename> <password> <password> (see note 3) n.a.
Tivoli Storage Manager admin <server>.opt
AUTHENTICATION EXPIRATION PERIOD (see note 1) PASSWORDACCESS PASSWORDDIR (see note 5) NODENAME UPDATE NODE (see notes 1,6) SET PASSWORD (see note 8) For each SERVER statement specify: PASSWORDREQUIRED ADSMNODE backom -c password
OFF n.a. n.a. n.a. n.a. n.a. n.a.
ON <n days> (see note 2) PROMPT n.a. n.a. <password> n.a.
3 4 5
Tivoli Storage Manager admin Tivoli Storage Manager client DP for SAP profile init<SID>.utl
NO <nodename> n.a.
YES <nodename> <password> (see notes 3, 7)
NO (see note 4) <password> (see notes 3, 7)
Command line
Notes: 1. See Tivoli Storage Manager documentation. 2. If you are using manual password generation during testing, make sure that the expiration period is set to a sufficiently long time. 3. For an initial setup this password must be the same as was specified when registering the node to Tivoli Storage Manager. The password must be changed first on the Tivoli Storage Manager server and then in the DP for SAP product. 4. ADSMNODE must not be set when PASSWORDACCESS generate is set. 5. The users <SID>adm and sapservice<SID> must have read and write permission for the path specified . 6. This step is only necessary if the password is expired (manual handling only) or needs to be changed on the TSM server. 7. A password must be entered for each server statement in the DP for SAP profile. 8. This step is necessary in case the Tivoli Storage Manager Backup Archive Client is used to access data for the same node.
212
Appendix L. Sample Tivoli Storage Manager Profiles

Sample TSM Profiles for UNIX or Linux Client User Options File Sample (dsm.opt)
************************************************************************ * Tivoli Storage Manager * * * * Sample Client User Options file for Unix platforms * ************************************************************************ SErvername Replace Tapeprompt DOM server_a On No /usr/sap /sapmnt/C21 /usr/sap/trans /db2/C21
Client System Options File Sample (dsm.sys)

************************************************************************ * IBM Tivoli Storage Manager * * * * Sample Client System Options file for Unix platforms * ************************************************************************ SErvername server_a COMMmethod TCPPort TCPServeraddress TCPBuffsize TCPWindowsize Compression InclExcl SErvername server_b COMMmethod TCPPort TCPServeraddress TCPBuffsize TCPWindowsize Compression InclExcl
TCPip 1500 your_ITSM_server_1 32 24 Off /usr/lpp/adsm/bin/inclexcl.list TCPip 1500 your_ITSM_server_2 32 24 Off /usr/lpp/adsm/bin/inclexcl.list
Include/Exclude List Sample

* --------------------------------------------------------------------------* inclexcl.list: * Sample include/exclude list * --------------------------------------------------------------------------* Task: * Include/Exclude list of files and directories for TSM incremental backups * --------------------------------------------------------------------------* ***** NOTE ***** NOTE ***** NOTE ***** * * This file is intended only as a model and should be * carefully tailored to the needs of the specific site. * * ***** NOTE ***** NOTE ***** NOTE ***** * --------------------------------------------------------------------------* * For all UNIX systems * exclude /unix exclude /.../core exclude /u/.../.*sh_history exclude /home/.../.*sh_history *
213
Sample Tivoli Storage Manager Profiles

* Note: It is recommended to perform system backups on a regular * basis. Consequently, you can exclude at least the following * directories: * exclude /usr/games/.../* exclude /usr/bin/.../* exclude /usr/lbin/.../* exclude /usr/mbin/.../* exclude /usr/sbin/.../* * --------------------------------------------------------------------------* * For those using AFS, exclude the cache filesystem or file * * exclude /usr/vice/cache/* * exclude /var/vice/cache/* * or * exclude /afscfs * --------------------------------------------------------------------------* * This stuff is either not worthwhile to be included or should be backed up * using DB2 backup techniques and the SAP utility brarchive. * exclude /db2/C21/log_archive/C21/* * exclude /db2/C21/sapreorg/.../* (There may be important scripts * located, check it out and decide.) exclude /db2/C21/sapdata*/.../* exclude /db2/C21/sapraw*/.../* * --------------------------------------------------------------------------* * With the above include/exclude list we implicitly include everything not * excluded above. Especially for DP for SAP, this means including: * /sapmnt/C21 > 300 MB * /usr/sap > 50 MB * /db2/C21 > 200 MB * and UNIX related > 350 MB * ---------------------------------------------------------------------------
Sample TSM Profiles for Windows Client User Options File Sample (dsm.opt)
The Tivoli Storage Manager client programs require a file dsm.opt containing standard client user options. The full file name is set in the environment variable DSM_CONFIG. This file is not provided with the installation.
************************************************************************* * * DSM.OPT (for Data Protection for SAP (R) ) * * Data Protection for SAP (R) requires that a file * dsm.opt is present, although its contents are ignored. * This means that this file may be empty (like this file). * The information about a Tivoli Storage Manager server * is obtained from the corresponding client option file <server>.opt. * * Data Protection for SAP (R) inspects the environment * variable DSMI_CONFIG to obtain the full file name of dsm.opt. * * Note: * The standard Tivoli Storage Manager client programs also use a file * dsm.opt, but the full file name of this client user option file is set * in the environment variable DSM_CONFIG. * This file is called the Tivoli Storage Manager client user option file. * Please see the Tivoli Storage Manager documentation for details. *************************************************************************
Client Options Files Sample (<server>.opt)

Data Protection for SAP requires for each Tivoli Storage Manager server a corresponding client option file <server>.opt. All these files must reside in one
214

directory, and this directory must contain a file dsm.opt whose full file name is set in the environment variable DSMI_CONFIG. The contents of this (second) dsm.opt file is ignored by DP for SAP.
************************************************************************* * * SERVER.OPT * * Data Protection for SAP (R) obtains the necessary information about * a Tivoli Storage Manager server server from a client option file * called <server>.opt. For each Tivoli Storage Manager server a * corresponding client option file is required. * * Note: This file contains the client options for the Tivoli Storage Manager * server called server_a. * * Please see the Tivoli Storage Manager documentation for details. * ************************************************************************* COMMmethod TCPIP SLOWINCR NO COMPression OFF *NODEname C21 TCPPort 1500 TCPServeraddress xxx.xxx.xxx.xxx PASSWORDACCESS PROMPT TCPBUFFSIZE 31 TCPWINDOWSIZE 32
Include/Exclude List Sample

This sample include/exclude list is intended for the standard client user option file. The idea is to exclude files from ordinary Tivoli Storage Manager incremental backups that are easy to restore or that are already saved by DP for SAP. Mainly such files are Windows system files and DB2 database files.
************************************************************************* * This Include-Exclude list is used for incremental backups of file * systems by the Tivoli Storage Manager command-line backup client. * Therefore the name of this file has to be set under the keyword InclExcl * in the standard Tivoli Storage Manager client user option file "dsm.opt". * * Since the backup of the DB2 database is done by * Data Protection for SAP(R) and not by Tivoli Storage * Manager command-line backup client, the DB2 database should be excluded * from backups by the Tivoli Storage Manager command-line backup client. * * Note 1: * The environment variable DSM_CONFIG contains the full file name of * the Tivoli Storage Manager client user option file "dsm.opt". * Note 2: * This Include-Exclude is not used by Data Protection for SAP(R) * ************************************************************************* Exclude *:\...\*.swp Exclude *:\...\*.obj Exclude *:\...\*.csm Exclude *:\...\*.dsk Exclude *:\...\*.bak Exclude *:\...\win386.swp Exclude *:\...\386spart.par Exclude *:\...\pagefile.sys Exclude *:\...\*.par Exclude *:\...\SYSTEM32\CONFIG\*.* Exclude *:\...\SYSTEM32\CONFIG\...\* Exclude *:\IBMBIO.COM Exclude *:\IBMDOS.COM * *Exclude the following DB2 database files:
Appendix L. Sample Tivoli Storage Manager Profiles
215

* Exclude *:\db2\C21\log_archive\C21\...\* Exclude *:\db2\C21\sapreorg\...\* Exclude *:\db2\C21\sapdata*\...\*
216
Appendix M. Backup Scheduling Examples

UNIX or Linux Crontab Example
UNIX or Linux cron jobs can be scheduled with the crontab command, which invokes an editing session that allows you to create a crontab file. The cron jobs and the appropriate times are defined within the crontab. The crontab can be customized with the command:
crontab -e
For example, you want a cron job to start a shell script backup.ksh (the content of backup.ksh can be found in Appendix M, Backup Scheduling Examples) from Monday through Friday at 11:30 p.m. which will use DB2 backup to save the SAP database. In this case, the entry in the crontab to start the script will be as follows:
30 23 * * 1,2,3,4,5 /usr/bin/su - db2c21 -c "/db2/C21/sapscripts/backup.ksh"
Elements of Backup Schedules for UNIX or Linux

Under UNIX or Linux , crontab starts jobs (cron.job) at predefined times. In the example below, crontab starts a shell script, backup.ksh, which simply uses the DB2 backup command to save the data.
Crontab File Sample

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # --------------------------------------------------------------------------crontab.sample: Sample crontab file to be included in the root crontab jobs. --------------------------------------------------------------------------Task: Submits backup/archive commands at regularly scheduled intervals using two simple shell scripts containing backup/archive commands and TSM commands. --------------------------------------------------------------------------***** NOTE ***** NOTE ***** NOTE ***** This file is intended only as a model and should be carefully tailored to the needs of the specific site. ***** NOTE ***** NOTE ***** NOTE ***** --------------------------------------------------------------------------Remarks on the crontab file format: Each crontab file entry consists of a line with six fields, separated by spaces and tabs, that contain, respectively: o The minute (0 through 59) o The hour (0 through 23) o The day of the month (1 through 31) o The month of the year (1 through 12) o The day of the week (0 through 6 for Sunday through Saturday) o The shell command Each of these fields can contain the following: o A number in the specified range o Two numbers separated by a dash to indicate an inclusive range o A list of numbers separated by commas
217
Backup Scheduling Examples

# o An * (asterisk); meaning all allowed values # # --------------------------------------------------------------------------# # For the following examples, the system id (alias) of the DB2 database # is assumed to be C21 and the username db2c21. # # --------------------------------------------------------------------------# Full database backup, scheduled every Friday at 8:00 p.m. # 0 20 * * 5 /usr/bin/su - db2c21 -c "/db2/C21/sqllib/scripts/backup.ksh" # # --------------------------------------------------------------------------# Save redo logs, scheduled twice a day at 11:30 a.m. and at 5:30 p.m. # Monday through Friday # 30 11,17 * * 1,2,3,4,5 /usr/bin/su - db2c21 -c "/db2/C21/sqllib/scripts/archive.ksh"
Full Offline Backup Shell Script Sample

#!/bin/ksh # --------------------------------------------------------------------------# backup.ksh: # Sample DB2 backup shell script for 32<64>bit environments # --------------------------------------------------------------------------# Task: # Invokes a DB2 backup in order to perform a full offline backup of # all DB2 tablespaces # --------------------------------------------------------------------------# ***** NOTE ***** NOTE ***** NOTE ***** # # This script is intended only as a model and should be # carefully tailored to the needs of the specific site. # # ***** NOTE ***** NOTE ***** NOTE ***** # --------------------------------------------------------------------------# # For the following examples, the system id (alias) of the DB2 database is # assumed to be C21. # # --------------------------------COMMAND-----------------------------------su - db2c21 -c "db2 backup db C21 load /usr/tivoli/tsm/tdp_r3/db2<64>/libtdpdb2<64>.a"
Windows Scheduling Example

To start automated backup jobs on Windows systems, the schedule service must be running. You can start this service with the command:
net start schedule
If the schedule service is running, jobs can be scheduled with the at command which can be used to invoke the batch file backup.cmd (the content of backup.cmd can be found in Elements of Backup Schedules for Windows on page 219). If you want to run this every Friday at 8:00 p.m., the following command must be invoked:
at 20:00 /every:f cmd /c c::\db2\C21\sapscripts\backup.cmd
218
Elements of Backup Schedules for Windows Schedule Batch Sample

@echo off rem -----------------------------------------------------------------------rem file name: schedule.sample rem -----------------------------------------------------------------------rem Task: rem Submits backup/archive commands at regularly scheduled intervals rem using two simple batch files containing backup/archive commands. rem -----------------------------------------------------------------------rem ***** NOTE ***** NOTE ***** NOTE ***** rem rem This file is intended only as a model and should be rem carefully tailored to the needs of the specific site. rem rem ***** NOTE ***** NOTE ***** NOTE ***** rem -----------------------------------------------------------------------rem For a full reference of the AT command please see the Windows NT rem help. rem -----------------------------------------------------------------------rem rem For the following examples, the system ID of the DB2 database rem is assumed to be "C21". rem rem -----------------------------------------------------------------------rem Full database backup, scheduled every Friday at 8:00 p.m. rem at 20:00 /every:f cmd /c c:\db2\C21\sqllib\scripts\backup.cmd rem rem -----------------------------------------------------------------------rem Save redo logs, scheduled twice a day at 11:30 a.m. and at 5:30 p.m. rem Monday through Friday rem at 11:30 /every:m,t,w,th,f cmd /c c:\db2\C21\sqllib\scripts\archive.cmd rem --------------------- end of schedule.sample ------------------------
Full Offline Backup Batch File Sample

@echo off rem Full Offline Backup batch file: rem -----------------------------------------------------------------------rem file name: backup.cmd rem -----------------------------------------------------------------------rem Sample DB2 backup batch file for 32<64>bit environments rem -----------------------------------------------------------------------rem Task: rem Invokes a DB2 backup in order to perform a full offline backup of rem all DB2 tablespaces rem -----------------------------------------------------------------------rem ***** NOTE ***** NOTE ***** NOTE ***** rem rem This script is intended only as a model and should be rem carefully tailored to the needs of the specific site. rem rem ***** NOTE ***** NOTE ***** NOTE ***** rem -----------------------------------------------------------------------rem rem For the following examples, the system ID of the DB2 database rem is assumed to be "C21". rem rem ------------------------------COMMAND----------------------------------db2 backup db C21 load C:\Program Files\tivoli\tsm\tdp_r3\db2<64>\tdpdb2.dll
Appendix M. Backup Scheduling Examples
219
220
Appendix N. Hints and Tips for Network Settings

Networks with Large Bandwidth-Delay Product
For networks with a large bandwidth-delay product, it is recommended to activate the TCP enhancements specified in RFC1323. For example, the network on an AIX machine can be configured with the no command. This command sets or displays current network attributes in the kernel. For details about the no command, see the man page of no of your operating system. The following table shows the network attributes with their recommended values:
Table 11. Tuning of Network Settings Attributes rfc1323 Value 1 Description Enables TCP enhancements as specified by RFC 1323, TCP Extensions for High Performance. The default is 0. A value of 1 specifies that all TCP connections will attempt to negotiate the RFC enhancements. Specifies the maximum buffer size allowed for a socket. The default is 65536 bytes. From the point of view of performance recommendations, the sb_max value should be twice the TCPWindowsize set within the Tivoli Storage Manager configuration file dsm.sys.
sb_max
131072
To set these values, the following commands should be invoked by the root user on the appropriate machine.
no -o rfc1323=1 no -o sb_max=131072
Caution The no command does not perform range checking. It therefore accepts all values. If used incorrectly, the command can cause the system to become inoperable.
Note These changes will be lost at system reboot. To make changes permanent, edit the /etc/rc.net file.
221
Hints and Tips for Network Settings
SP Switch (RISC 6000)

If an SP switch (RISC 6000) is used, the following two values should be set as shown in the following table:
Table 12. Tuning of SP Switch Buffer Pools Attributes rpoolsize spoolsize Value 1048576 1048576 Description The receive pool is a buffer pool for incoming data. The size for values is in bytes. The send pool is a buffer for outgoing data. The size for values is in bytes.
The buffer pool settings can be changed using the chgcss command. After the changes, it is necessary to reboot the node.
Network Settings of the Tivoli Storage Manager

The performance adjustments on the Tivoli Storage Manager side can be done by customizing the appropriate configuration files: v On the server side, the server option file dsmserv.opt, and v On the client side, the client option file dsm.sys ( UNIX and Linux systems) or server.opt (Windows systems). The following table shows the corresponding Tivoli Storage Manager configuration file attributes with the recommended values.
Table 13. Tuning Tivoli Storage Manager Configuration File Attributes Attributes TCPBuffsize Value 32 Description Specifies the size, in kilobytes, of the buffer used for TCP/IP send requests. This option affects whether or not Tivoli Storage Manager sends the data directly from the session buffer or copies the data to the TCP buffer. A 32K buffer size forces Tivoli Storage Manager to copy data to its communication buffer and flush the buffer when it fills. Specifies whether the server should send small amounts of data or allow TCP/IP to buffer the data. Disallowing buffering may improve throughput but more packets will be sent over the network. Specifies the size, in kilobytes, which will be used for the TCP/IP sliding window for the client node. This is the size of the buffer used when sending or receiving data. The range of values is 0 to 2048.
TCPNODelay
YES
TCPWindowsize
640 (AIX) 63 (others)
Additional information can be found at: http://www-306.ibm.com/software/ tivoli/products/storage-mgr-erp/.
222
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Appendix O. Internet Protocol Version 6 (IPv6) Support

For AIX and Linux as of V5.5, Data Protection for SAP and Data Protection for Snapshot Devices support both IPv4 and IPv6 internal communication. The actual communication to be used depends on the network settings of the adapters employed. There is no option to enforce the use of a specific protocol other than by network configuration. Version 5.5 of Data Protection for SAP and Data Protection for Snapshot Devices support IPv6 in that they will run in an IPv6 environment. They do not take advantage of new IPv6 functionality, however. A server (defined for the purposes of this discussion as any software that opens a listening port) attempts to open 2 sockets, one handling IPv4 connection requests and one IPv6 requests. Connections will be accepted from each socket that could be established. The clients will attempt to connect to whatever addresses are returned by the server until a request is successful. The following profile parameters of Data Protection for SAP v LOG_SERVER v TCP_ADDRESS and Data Protection for Snapshot Devices: v ADMIN_ASSISTANT v PRIMARY_COPYSERVICES_SERVERNAME now accept IPv6 addresses. Also, the command line parameter for the Administration Assistant is IPv6-compatible. It can be specified in either of the forms: v <IPv4 address>:<service or port> v <service or port>@<IPv6 address> All interfaces containing hostnames, IP addresses, or port numbers support both IPv4 and IPv6 address formats. This includes v profile parameters v command line options and arguments v entries by the user during the installation and setup procedures v output in the Administration Assistant windows Note: The specification of IPv6 addresses assumes that Data Protection for SAP is used in an environment in which IPv6 is supported by all hardware and software components involved and has been adequately tested in this environment.
223
224
Appendix P. Support Information

If you have a problem with your IBM software, you want to resolve it quickly. This section describes the following options for obtaining support for IBM software products: v Using IBM Support Assistant v Obtaining Fixes v Receiving Weekly Support Updates on page 226 v Contacting IBM Software Support on page 227
Using IBM Support Assistant

The IBM Support Assistant is a free, stand-alone application that you can install on any workstation. You can then enhance the application by installing product-specific plug-in modules for the IBM products you use. The IBM Support Assistant saves you time searching product, support, and educational resources. The IBM Support Assistant helps you gather support information when you need to open a problem management record (PMR), which you can then use to track the problem. The product-specific plug-in modules provide you with the following resources: v Support links v Education links v Ability to submit problem management reports For more information, see the IBM Support Assistant Web site at http://www.ibm.com/software/support/isa/. If your product does not use IBM Support Assistant, use the links to support topics in your information center. In the navigation frame, check the links for resources listed in the ibm.com and related resources section where you can search the following resources: v Support and assistance (includes search capability of IBM technotes and IBM downloads for interim fixes and workarounds) v Training and certification v IBM developerWorks v IBM Redbooks v General product information If you cannot find the solution to your problem in the information center, search the following Internet resources for the latest information that might help you resolve your problem: v Forums and newsgroups
Obtaining Fixes
A product fix might be available to resolve your problem. To determine what fixes are available for your IBM software product, follow these steps:
225
Support Information
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/ support. 2. Under Find product support, click All IBM software (A-Z). This opens the software product list. 3. In the software product list, click on the product in question. This opens the corresponding support site. 4. Under Solve a problem, click APARs to go to a list of fixes, fix packs, and other service updates. 5. Click the name of a fix to read the description and optionally download the fix. You can also search for a specific fix; for tips on refining your search, click Search tips. 6. In the Find downloads and drivers by product section, select one software category from the Category list. 7. Select one product from the Sub-category list. 8. Type more search terms in the Search within results if you want to refine your search. 9. Click Search. 10. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix. For more information about the types of fixes that are available, see the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/ handbook.html.
Receiving Weekly Support Updates

To receive weekly e-mail notifications about fixes and other software support news, follow these steps: 1. Go to the IBM Software Support Web site at http://www.ibm.com/software/ support. 2. Click My support in the far upper-right corner of the page under Personalized support. 3. If you have already registered for My support, sign in and skip to the next step. If you have not registered, click register now. Complete the registration form using your e-mail address as your IBM ID and click Submit. 4. Click Edit profile. 5. In the Products list, select Software. A second list is displayed. 6. In the second list, select a product segment, for example, Systems management. A third list is displayed. 7. In the third list, select a product sub-segment, for example, Application Performance & Availability. A list of applicable products is displayed. 8. Select the products for which you want to receive updates. 9. Click Add products. 10. After selecting all products that are of interest to you, click Subscribe to e-mail on the Edit profile tab. 11. Select Please send these documents by weekly e-mail. 12. Update your e-mail address as needed. 13. In the Documents list, select Software. 14. Select the types of documents that you want to receive information about. 15. Click Update.
226
Support Information
If you experience problems with the My support feature, you can obtain help in one of the following ways: Online Send an e-mail message to erchelp@ca.ibm.com, describing your problem. By phone Call 1-800-IBM-4You (1-800-426-4968).
Contacting IBM Software Support

IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows, or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online Go to the Passport Advantage Web site at http://www-306.ibm.com/ software/howtobuy/passportadvantage/pao_customers.htm . By phone For the phone number to call in your country, go to the IBM Software Support Web site at http://techsupport.services.ibm.com/guides/ contacts.html and click the name of your geographic region. v For customers with Subscription and Support (S & S) contracts, go to the Software Service Request Web site at https://techsupport.services.ibm.com/ssr/ login. v For customers with IBMLink, CATIA, Linux, OS/390 , System i , System p, System z , and other support agreements, go to the IBM Support Line Web site at http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006. v For IBM Systems (formerly eServer) software products (including, but not limited to, DB2 and WebSphere products that run in System z, System p, and System i environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for IBM Systems software products, go to the IBM Technical Support Advantage Web site at http://www.ibm.com/ servers/eserver/techsupport.html. If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location. To 1. 2. 3. contact IBM Software support, follow these steps: Determining the Business Impact on page 228 Describing Problems and Gathering Information on page 228 Submitting Problems on page 228
227
Support Information
Determining the Business Impact

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria: Severity 1 The problem has a critical business impact. You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Severity 2 The problem has a significant business impact. The program is usable, but it is severely limited. Severity 3 The problem has some business impact. The program is usable, but less significant features (not critical to operations) are unavailable. Severity 4 The problem has minimal business impact. The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented.
Describing Problems and Gathering Information

When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: v What software versions were you running when the problem occurred? v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can you re-create the problem? If so, what steps were performed to re-create the problem? v Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, and so on. v Are you currently using a workaround for the problem? If so, be prepared to explain the workaround when you report the problem.
Submitting Problems
You can submit your problem to IBM Software Support in one of two ways: Online Click Submit and track problems on the IBM Software Support site athttp://www.ibm.com/software/support/probsub.html. Type your information into the appropriate problem submission form. By phone For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook at http://techsupport.services.ibm.com/ guides/contacts.html and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
228
Support Information
Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.
229
230
Glossary A
Activate policy set. In Tivoli Storage Manager, the process of validating the contents of a policy set and copying the policy set to the ACTIVE policy set. Active policy set. In Tivoli Storage Manager, the policy set that contains the policy rules currently in use by all client nodes assigned to the policy domain. The active policy set is the policy set that was most recently activated for the policy domain. Administration Assistant. A Web-browser based graphical interface to support and assist customizing of Data Protection for SAP and analyzing SAP database backup and restore operations The Administration Assistant consists of the Administration Assistant server-level components (Server, Database Agent, Database) and one or more instances of the Administration Assistant client. Administration Assistant client. Part of the Administration Assistant; applet started in a Web browser to access the Administration Assistant Server component. Administration Assistant Database Agent. Administration Assistant server-level component responsible for receiving data from Data Protection for SAP and forwarding it to the Administration Assistant Server component for display as well as to the Administration Assistant Database component for retention. Administration Assistant Database component. Administration Assistant server-level component responsible for storing data received from DP for SAP via the Database Agent in an internal Administration Assistant database. Administration Assistant scheduling client. Part of the Administration Assistant creating reports from a command-line interface using predefined templates. Administration Assistant Server component. Part of the Administration Assistant communicating with the ProLE processes or services of various database servers. Administrators access the Server component via Administration Assistant clients. Administration Assistant Server component configuration file. The file containing the configuration of your Administration Assistant Server component. The default file name of the server configuration file is assist.cfg, located in the installation path of the Administration Assistant Server component.
Administrative client. In Tivoli Storage Manager, a program that runs on a file server, workstation, or mainframe that allows administrators to control and monitor the Tivoli Storage Manager server through administrator commands. Compare with backup-archive client. Apache Derby. An open-source database management system developed by IBM and bundled with the Administration Assistant. It is the default DBMS for the internal Administration Assistant database. API client. See Tivoli Storage Manager API. Archive copy group. In Tivoli Storage Manager, a policy object containing attributes that control the generation, destination, and expiration of archive files. An archive copy group belongs to a management class.
B
BackOM. See Backup Object Manager. Backup-archive client. A component of Tivoli Storage Manager running on a workstation or file server, providing a means for backing up, archiving, restoring, and retrieving files to or from the TSM server. Compare with administrative client. Backup copy group. A policy object containing attributes that control the generation, destination, and expiration of backup files. A backup copy group belongs to a management class. Backup Object Manager (BackOM). A utility provided with Data Protection for SAP for backing up databases and for querying, restoring, and deleting backup objects residing on the TSM server. Backup Server. A Tivoli Storage Manager server where DP for SAP sends the backup data to and retrieves data when restoring. Backup version control. A feature of Data Protection for SAP allowing the customer to specify the number of full database backups to be kept on the TSM server. Obsolete database backups are deleted together with all dependent data (for example DB2 log files, incremental backups, etc.). BRARCHIVE. An SAP-DB2 Administration Tools utility to perform backups of offline log files in an SAP DB2 database environment. BRRESTORE. An SAP-DB2 Administration Tools utility to perform a restore of previously backed up offline log files in an SAP DB2 database environment.
231
Glossary
C
Client options file. A configuration file of the TSM client containing a set of processing options that identify the server, communication method, and options for backup, archive, hierarchical storage management, and scheduling. Its default name is dsm.opt on UNIX or Linux systems and <servername>.opt on Windows. Client system options file. A configuration file of the TSM client residing on UNIX or Linux systems, containing a set of processing options that identify the Tivoli Storage Manager servers to be contacted for services. This file also specifies communication methods and options for backup, archive, hierarchical storage management, and scheduling. Its name is dsm.sys. Cloning of a database. Restore a database to a different location and changing the database alias or SID while leaving the physical layout of the database unchanged. Database cloning can be achieved with the redirected restore function of the Backup Object Manager. Command Line Processor (CLP). A character based interface of DB2 for entering SQL statements and database manager commands (e.g. backup or restore). Configuration File. See Data Protection for SAP configuration file. See Administration Assistant server configuration file. Control Center. A graphical interface of DB2 that shows database objects (such as databases and tables) and their relationship to each other. The Control Center allows administrative tasks (e.g. database backup) provided by the DBA utility to be performed and provides visual explanation and performance monitor tools. Copy group. A policy object of the TSM server containing attributes that control the generation, destination, and expiration of backup and archive files. There are two kinds of copy groups: backup and archive. Copy groups belong to management classes.
ability of log archiving, log retrieving, and managing of multiple log chains. Log files can be archived to disk, tape, TSM, or to vendor devices. Data Protection for SAP configuration file. Binary file containing persistent information used by Data Protection for SAP, such as the TSM client password or the current backup version number. Its default file name is init.<SID>.bki. Data Protection for SAP profile. ASCII file containing option keywords for configuring Data Protection for SAP. Its default file name is init.<SID>.utl. Data block. The smallest unit of a database. Device class. A named group of storage devices of a TSM server with common characteristics. Each device class has a unique name and represents a specific device type such as disk, file, optical disk, or tape. DISK. A device class that is defined by Tivoli Storage Manager at installation. It is used to categorize disk drives. DP for SAP. An abbreviation for Data Protection for SAP, which is used in this document.
F
File space. A logical space in a TSM server assigned to a specific client. Clients can restore, retrieve, or delete contents of their file spaces from Tivoli Storage Manager server storage. Tivoli Storage Manager does not necessarily store all the files from a single file space together, but can identify all the files in server storage that came from a single file space.
I
Include/exclude list. A group of include and exclude option statements in a file. Tivoli Storage Manager backup-archive client uses the statements to determine whether to back up or migrate certain files, and to determine the associated management classes to use for backup, archive, and space management. The exclude options identify files that should not be backed up or migrated off the client node. The include options identify files that are exempt from the exclusion rules, or assign a management class to a file or group of files for backup, archive, or space management services. The include/exclude list is defined either in an include/exclude file (for UNIX or Linux clients) or in the client options file (for other clients).
D
Database Agent. See Administration Assistant Database Agent. Database component. See Administration Assistant Database component. Database server. The server where the SAP database resides. DP for SAP and the TSM API must be installed on this server. DB2 Log Manager. Integrated log management facility of DB2 introduced with DB2 version 8.2. It provides the
L
LAN-free backup. Backup to a backup server residing on system different from that of the database server.
232
Glossary
The database and backup servers are connected via LAN. However, backup data is transferred directly to the storage media via SAN. Local backup. Backup to a local backup server. Local backup server. Backup server residing on the same system as the database server does. Log Manager. See DB2 Log Manager Logretain. DB2 database configuration parameter enabling roll-forward recovery of the database. If logretain is enabled, offline DB2 log files are retained. If the user exit is activated offline log files are archived by calling the configured user exit. Online retained log file. DB2 log file no longer being used for logging transactions, but containing transactions with data pages that have not yet been written from the buffer pool to disk. The DB2 logging user exit is called by DB2 (if configured) to copy a filled or closed online retained log file to the log_archive directory. Online retained log files may be deleted or reused by DB2 when they are no longer needed because all referenced transactions are committed and all changed pages have been written to disk and after the userexit has successfully copied them to the log_archive directory.
P
Partition. DB2: A part of a database that consists of its own data, indexes, configuration files, and transaction logs. A database partition is sometimes called a node or a database node. Path. A connection between a Tivoli Storage Manager node and a Tivoli Storage Manager server interface. On the client side, a path is defined by a logical server name listed in the client option file dsm.sys ( UNIX or Linux systems) or <servername>.opt (Windows systems). At the server side, the possible paths are defined by the network addresses of the Tivoli Storage Manager server. Policy domain. Within Tivoli Storage Manager, a policy object that contains policy sets, management classes, and copy groups that are used by a group of client nodes. Policy set. Within Tivoli Storage Manager, a policy object that contains a group of management class definitions that exist for a policy domain. At any one time there can be many policy sets within a policy domain but only one policy set can be active. ProLE. The background process (UNIX or Linux) or service (Windows) controlling backup and restore operations of DP for SAP.
M
Management class. Within IBM Tivoli Storage Manager, a policy object that users can bind to a file in order to specify how the server manages the file. The management class can contain a backup copy group, an archive copy group, and space management attributes. The copy groups determine how the Tivoli Storage Manager server manages backup versions or archive copies of files. The space management attributes determine whether files are eligible for migration from space manager client nodes to Tivoli Storage Manager storage, and under what conditions.
N
Node. 1. TSM: A unique name used to identify a Tivoli Storage Manager client to the TSM server. 2. SMP: Single machine in a Symmetrical Multiprocessor (SMP) environment. 3. See partition Normalizing of tablespaces. Resizing of tablespace containers during a redirected restore performed by the Backup Object Manager. As a result, all tablespace containers are allocated with the same size. Additionally, the data contained in the tablespace is evenly distributed among the containers. Consequently, parallel access to the data is optimized. Tablespace normalizing can be combined with scaling.
R
Recovery History File. A recovery history file is created with each DB2 database and is automatically updated, for example, whenever one of the following operations is performed: v Backup of a database or tablespace v Restore of a database or tablespace v Rollforward of a database or tablespace v Alter of a tablespace v Load of a table v Drop of a table v Reorganization of a table v Update of table statistics Every DB2 backup operation includes a copy of the recovery history file.
Glossary
O
Offline log file. A log file that is no longer needed by the DB database for roll-back or crash recovery. However, it may be required for a roll-forward recovery. DB2 may call the userexit to copy an offline log file to the log_archive path. Online active log file. Log file which is currently being used by DB2 to log transactions. It is needed for rollback operations and crash recovery.
233
Glossary
Remote backup. Backup to a remote backup server. Remote backup server. Backup server residing on a system different from that of the database server. Retention. The amount of time, in days, that inactive files backed up or archived to a TSM server are kept by the backup server before they are deleted. Copy group attributes and default retention grace periods for the domain define retention. RMI. Remote Method Invocation (Java)
T
Tablespace. An abstraction of a collection of containers into which database objects are stored. A tablespace provides a level of indirection between a database and the tables stored within the database. Tablespace container. A generic term describing an allocation of space to a tablespace. Depending on the tablespace type, the container can be a directory, device, or file. Tablespace Definition Information. Data describing the physical layout of a database required by the Backup Object Manager redirected restore function. These data include information on all tablespaces and their associated tablespace containers. The TDI can be created at the end of a full database backup. TDI. Tablespace Definition Information. Tivoli Storage Manager (TSM). IBM Tivoli Storage manager, a client/server program that provides policy-driven storage management to customers in a multivendor computer environment. Tivoli Storage Manager API. A set of functions that applications running on a client platform can call to store, query, and retrieve objects from Tivoli Storage Manager storage.
S
SAP Note. Document containing service information provided by SAP. SAP Notes can be accessed (with an SAP user ID and password) at the SAP Service Marketplace: http://service.sap.com/notes Scaling of tablespaces. Resizing of tablespace containers during a redirected restore performed by the Backup Object Manager. As a result, all tablespace containers are allocated with their original size increased or decreased by a scaling factor. Tablespace scaling can be combined with normalizing. Scheduling client. See Administration Assistant scheduling client. Scratch volume. A volume that is available for Tivoli Storage Manager use. The volume is either labeled, or blank or contains no valid data, and is not defined to Tivoli Storage Manager. Server configuration file. See Administration Assistant Server component configuration file. Session. Single TCP/IP connection between a Tivoli Storage Manager node and a Tivoli Storage Manager server. A TSM server may be configured to allow a number of sessions from a TSM node to the server in parallel over the same communication path. Shared library. Shared library (UNIX) or dynamic link library (DLL, Windows) implementing the vendor API of DB2 for backup and restore solutions. DP for SAP functionality is partly implemented as a shared library. SID. The system identifier, a unique name of the SAP system, in respect to the database involved. Storage pool. A storage pool is a named collection of storage volumes that are associated with one device class. Each storage pool represents a collection of volumes that are the same media type. For example, a storage pool that is associated with a device class for 8 mm tape contains only 8 mm tape volumes.
U
User exit. The DB2 database manager can call a user exit program to store and retrieve log files and manage the location of archived log files, if the database configuration parameter userexit is activated. Using a user exit program to archive and retrieve log files enables the database for rollforward recovery.
V
Validate. In Tivoli Storage Manager, the process of ensuring that the active policy set contains a default management class and reports on copy group definition errors. Vendor API. An interface provided by DB2 to which vendors are able to write compatible software libraries, which should be shared libraries. Thus, the DB2 process is able to issue commands to the Vendor API to write backup data to sequential storage (e.g., Tivoli Storage Manager) and read files from sequential storage. Vendor Environment File. File used to communicate environment settings to DB2 to be passed on to the shared library. The name of the vendor environment file is passed to DB2 as a parameter of the DB2 'backup database' and 'restore database' commands.
234
Glossary
Volume. The basic unit of storage for the Tivoli Storage Manager database, recovery log, and storage pools. A volume can be an LVM logical volume, a standard file system file, a tape cartridge, or an optical cartridge. Each volume is identified by a unique volume identifier. See database volume, scratch volume, and storage pool volume.
Glossary
235
Glossary
236
Notices
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. 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 of the intellectual property rights of IBM may be used instead of the IBM product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, are the responsibility of the user. IBM may have patents or pending patent applications covering subject matter 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
Any references in this information 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 product and use of those Web sites is at your own risk. If you are viewing this information in softcopy form, the photographs and color illustrations may not appear. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Deutschland Informationssysteme GmbH Department 0215 Pascalstr. 100 70569 Stuttgart Germany
Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.
Trademarks and Service Marks

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both: v AFS v AIX v DB2 v DB2 Universal Database v developerWorks v DS6000 v DS8000 v Enterprise Storage Server
237
Notices
v v v v v v v v v v v v v v v v v v v v v eServer FlashCopy GPFS HACMP IBM ibm.com IBMLink Lotus OS/390 Passport Advantage POWER Rational Redbooks SP System i System p System Storage System z Tivoli TotalStorage WebSphere
| | |
Adobe, the Adobe logo, PostScript, and the PostScript logo are trademarks or registered trademarks of Adobe Systems, Incorporated, in the United States and/or other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, the Windows logo, and Windows 2000 are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
Accessibility
Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, to use software products successfully. Depending on the operating system and its environment, such users can: v use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear what is displayed on the screen. Consult the product documentation of the assistive technology for details on using those technologies with this product. v operate specific or equivalent features using only the keyboard. v magnify what is displayed on the screen. The product documentation includes features to aid accessibility:
238
Notices
v All documentation is available in both HTML and convertible PDF formats to give the maximum opportunity for users to apply screen-reader software. v All images in the documentation are provided with alternative text so that users with vision impairments can understand the contents of the images.
Navigating the Interface Using the Keyboard

Standard shortcut and accelerator keys are used by the product and are documented by the operating system. Refer to the documentation provided by your operating system for more information.
Magnifying What is Displayed on the Screen

You can enlarge information on the product windows using facilities provided by the operating system on which the product is run. For example, in some environments you can lower the resolution of the screen to enlarge the font sizes of the text on the screen. Refer to the documentation provided by your operating system for more information.
Notices
239
240
Index A
accessibility 238 activate policy set 205, 206 glossary definition 231 active policy set glossary definition 231 adaptation of tablespace 72 Adaptive Computing Environment 175 Administration Assistant 17, 77 adjusting 41 administer users 77 administering userids 90 authorizing users 90 concepts 78 configuration tool 78 configure systems 77 configuring 90 customizing 78 Database Agent 78 Database component 78 glossary definition 231 installation planning sheets 178 installing 81 Java 81 manage report templates 77 migration 88 migration of data 89 monitor operations 77 operations monitoring 78 overview 77 problem support 77 reference material 195 secure communication 91 Server component 78 starting and stopping 87 threshold definitions 92 upgrading 88 view performance data 77 Web browser, remote method invocation 81 Administration Assistant client glossary definition 231 Java 81 prerequisites 81 setting up 85 verifying the installation 86 Administration Assistant database changing password for 92 Administration Assistant scheduling cient command line interface 80 Administration Assistant scheduling client glossary definition 231 prerequisites 82 setting up 87 Administration Assistant Scheduling Client creating reports from 110 Administration Assistant Server glossary definition 231 Copyright IBM Corp. 1995, 2007 Administration Assistant Server (continued) specifying 42 Administration Assistant Server component secure connection to clients 85 Administration Assistant Server component configuration file 80, 86, 91 Administration Assistant Server Configuration File glossary definition 231 Administration Assistant server-level components initial installation 82 installation planning 82 installing 82 post installation process 85 prerequisites 81 uninstalling 85 upgrade installation 82 verifying the installation 86 administrative client 11 glossary definition 231 ADSMNODE profile keyword 115 alternate / parallel backup paths 16 alternate path 17 alternate/parallel backup paths example for availability 185 example for performance 187 reasons to use 183 alternate/parallel backup servers 17 example 3 for disaster recovery 188 Apache Derby for Administration Assistant database 79 API client glossary definition 231 archive copy group glossary definition 231 archiving inactive data 18 authorizing Administration Assistant users 90 automating backup and archive operations 11 automation options alternate network paths and servers 17 backup version control 16 messaging 17 multiple DB2 log file copies 16 selectable management classes 16 availability improvements with alternate/parallel paths and servers 17, 183 with multiple DB2 Log Files 16 BackOM glossary definition 231 backup automated 11, 12 database command 4 delta 11 full offline 199 full online 199 incremental 10, 12, 16 objects 55 offline 10, 65 online 10, 65 operation reporting 106 parallel 16 path 16 performance optimization 35 multiplexing 38 start from command line 197 start in non-partitioned environment 197 start in partitioned environment 198 start in partitioned environment via SSV 198 status reporting 105, 106 tape usage 15 terminating 183 version control 16, 44, 119, 206 windows 10 backup copy group glossary definition 231 Backup Object Manager 3, 53 commands 55 glossary definition 231 setup 54 troubleshooting 170 backup paths alternate/parallel 16 profile examples 183 backup results applying to restore 102 backup scheduler IBM Tivoli Workload scheduler 11 SAP scheduler 11 Tivoli Storage Manager scheduler 11 UNIX crontab sample 217 UNIX or Linux crontab / Windows scheduler 11 Windows sample 218 backup server alternate/parallel 17 glossary definition 231 managing data 18 performance optimization 37 profile examples 183 backup status monitoring 17 backup strategy defining 9 planning 9 Sample 12
B
BACKEND profile keyword 116
241
backup version control glossary definition 231 backup-archive client 10, 12, 13 glossary definition 231 BACKUPIDPREFIX profile keyword 116 balancing your system 97 BRARCHIVE 3, 5, 6, 39 glossary definition 231 BRARCHIVEMGTCLASS profile keyword 16, 116 BRBACKUPMGTCLASS profile keyword 16, 116 BRRESTORE 3, 5, 6 glossary definition 231 BUFFCOPY profile keyword 116 buffer copies 41 buffer size 41 BUFFSIZE profile keyword 117
D
data block 4, 6 glossary definition 232 data compression and overall throughput 99 hardware vs. software 208, 209 null block 40 Tivoli Storage Manager 40 Data Protection for SAP installation planning sheets 177 shared library 4 Data Protection for SAP configuration file glossary definition 232 Data Protection for SAP installation packages 24 Data Protection for SAP profile 115 glossary definition 232 UNIX or Linux sample 122 Data Protection for Snapshot Devices 18 data throughput 97, 98 Database Agent glossary definition 232 Database Server glossary definition 232 performance optimization 36 DB2 for Administration Assistant database 79 Single System View (SSV) backup 200 DB2 CommonStore for SAP 18 DB2 Failure Types 9 DB2 log files creating multiple copies 16 DB2 Log Manager 5, 7 glossary definition 232 DB2 vendor environment file sample 193 DB2 Version 8.2 Log Manager 5, 46 rules when using 45 DB2 Version 8.x 29 DB2_VENDOR_LIB 26, 27, 170 Derby for Administration Assistant database 79 device class 37, 118, 204, 205 glossary definition 232 disability 238 disaster recovery example 3 for disaster recovery 188 with alternate/parallel paths and servers 183 disk glossary definition 232 layout 36 distributed file system 175 DMS 64 DP for SAP architecture and properties 13 components 13 console installation 33 database utilities 13 glossary definition 232 installing 23 integration with Administration Assistant 14
C
CD-ROM installation from 28 client options file 29, 209, 214 glossary definition 232 client system options file glossary definition 232 UNIX and Linux example 213 Windows example 214 client user options file UNIX and Linux example 213 client/server connection paths 183 cloning 57, 70 of a database 66 collocation 15, 39 Command Line Processor (CLP) 3 glossary definition 232 command syntax Backup Object Manager 55 CommonStore 10, 18 compression 16, 36 null block 40 Tivoli Storage Manager 40 when restoring 102 CONFIG_FILE profile keyword 117 configuration files creation of 31 glossary definition 232 configuration matrix for Tivoli Storage Manager password settings 211, 212 Control Center glossary definition 232 control file glossary definition 232 copies of log files 16 copy group 119, 205, 206 glossary definition 232 crontab file example 217 scheduling backups with 11 custom SQL file 93 custom SQL file (sample) 196 customer support See Software Support customization Administration Assistant 78
DP for SAP (continued) integration with SAP 14 introduction 13 messages 129 migration 30 overview 13 profile keyword descriptions 115 keyword rules 115 migration 31 Windows sample 125 profiles UNIX or Linux sample 122 reporting 105 scope 13 shared library 14 upgrading 23, 30 DP for SAP installation package 24, 193 drill-down 102 DSMI_CONFIG 27 DSMI_DIR 27 DSMI_LOG 27
E
END profile keyword 117 Enterprise Storage Server 18 environment variable DB2_INSTANCE 59 DB2_VENDOR_LIB 26, 27, 54, 170 DSMI_CONFIG 27 DSMI_DIR 27 DSMI_LOG 27 TDP_DIR 26, 27, 54, 129, 170 XINT_PROFILE 26, 27, 54, 170 error messages 130 DP for SAP 129 examples alternate/parallel paths for availability 185 alternate/parallel paths for disaster recovery 188 alternate/parallel paths for increased performance 187 client system options file (UNIX and Linux) 213 client system options file (Windows) 214 client user options file (UNIX) 213 client user options file (Windows) 214 crontab file 217 full offline batch backup (Windows) 219 include/exclude list (UNIX and Linux) 213 include/exclude list (Windows) 215 offline backup shell script 218 scheduled batch backup (Windows) 219 scheduling backup jobs (UNIX or Linux) 217 scheduling backup jobs (Windows) 219 Tivoli Storage Manager profiles for UNIX and Linux 213
242
examples (continued) Tivoli Storage Manager profiles for Windows 214
F
File space glossary definition 232 fixes, obtaining 225 FlashCopy and snapshots backup 18 devices 18 restore 18 FRONTEND profile keyword full offline backup 199 full offline batch backup Windows example 219 full online backup 199 full restore 199
installing DP for SAP (continued) post installation steps 29 prerequisites 23 silent installation 32 TSM Option file 29 upgrade installation (migration) 24 verifying the installation 30 verifying the TSM API installation 30 integration of Data Protection for SAP with Administration Assistant 14 with SAP 14 IPv6 223
Log Manager built in 46 glossary definition 233 LOG_SERVER profile keyword 117 LOGARCHMETHn configuration parameters 26, 27 logging messages 17 Logretain glossary definition 233
M
management classes 16 glossary definition 233 Tivoli Storage Manager server configuration 205 MAX_SESSIONS profile keyword 118 MAX_VERSIONS profile keyword 118 message file how to find 129 messages 130 logging of 17 severity levels 130 migration DP for SAP 30 of Administration Assistant 88 profile 31 monitoring DP for SAP 78 mount points maximum number per node 207 node parameter maxnummp 207 multiple network paths 39 multiple paths 222 multiple servers 40 when restoring 103 multiple sessions 16, 38 multiplexing 36, 38 when restoring 103 MULTIPLEXING profile keyword 38
117
J
Java prerequisite for Administration Assistant dlient 81 prerequisite for Administration Assistant server 81
H
HACMP 48, 49 adding DP for SAP 50 installing and setup 49 sample stop script 52 hardware compression 208, 209 compared with Tivoli Storage Manager client software compression 208, 209 high availability 48
K
keyboard 238 keywords ADSMNODE 115 BACKEND 116 BACKUPIDPREFIX 116 BRARCHIVEMGTCLASS 16, 116 BRBACKUPMGTCLASS 16, 116 BUFFCOPY 116 BUFFSIZE 41, 117 CONFIG_FILE 117 END 117 FRONTEND 117 LOG_SERVER 117 MAX_SESSIONS 118 MAX_VERSIONS 118 MULTIPLEXING 38 PASSWORDREQUIRED 119 REDOLOG_COPIES 16, 119 RL_COMPRESSION 40, 120 SERVER 120 SESSIONS 121 syntax for all keywords 115 TCP_ADDRESS 121 TRACE 121 TRACEFILE 121 TRACEMAX 122 USE_AT 122
I
IBM support assistant, support assistant, problem resolution, IBM Redbooks, education, software support, support 225 inactive data archiving of 10, 18 include/exclude list glossary definition 232 UNIX and Linux example 213 Windows example 215 incremental backup 10, 16 installation package 24, 193 installing Administration Assistant 81 Administration Assistant client, prerequisites 81 Administration Assistant server-level components 82 Administration Assistant server, prerequisites 81 Administration Assistant, installation verification 86 HACMP 49 installing DP for SAP 23, 24 firewall installation 33 initial installation 24 migration 24 on AIX, Linux, Solaris 25 on Windows 27 password handling 29 planning for installation 24 planning sheet 177
N
network performance optimization 36, 221 settings 221 node glossary definition 233 maxnummp 207 number of mount points 206 Tivoli Storage Manager server 206 non-partitioned environment starting backup 197 starting restore 197 normalizing of tablespaces 74 glossary definition 233 null block data compression 40
L
LAN-free backup 36 glossary definition 232 performance optimization 36 Local backup glossary definition 233 local backup server glossary definition 233 log files creating multiple copies 16 how to find 129 location 167 management 5
O
offline backup shell script example 218 offline log file 3, 6, 10, 12, 24, 120, 197, 198, 205 glossary definition 233
Index
243
online active log file glossary definition 233 online retained log file glossary definition 233 optimizing backup 97 restore 102
P
parallel backup and restore number of parallel sessions to specify 118 parallel backup paths sample 2 for increased performance 187 parallel backup servers alternate 17 parallel path 16 example for increased performance 187 parallel sessions 16, 222 partition 32, 44, 59, 61, 116, 117, 118, 119, 198, 199 glossary definition 233 partitioned environment starting backup / restore 198 password handling automatic generation 44 configuration matrix (UNIX or Linux) 211 configuration matrix (Windows) 212 manual generation 43 no password usage 43 set the password 29 PASSWORDREQUIRED profile keyword 119 path alternate 17 backup 16 glossary definition 233 performance analysis 17 performance monitoring 97 Administration Assistant 78 using sensors 98 performance optimization Backup Server 37 backup/restore 35 balanced configuration 101 by changing buffer size 41 by compressing data 40 by multiplexing 38, 99 by setting up proper environment 37 by using multiple network paths 16, 39 example 2 187 by using multiple servers 16, 40 by using multiple sessions 16, 38 CPU power 36, 37 data transfer 37 dedicated backbone network 36 disk bottleneck 99 disk layout 36 general considerations 35 I/O paths 36 LAN-free backup 36 network bandwidth 36
performance optimization (continued) network or TSM bottleneck 100 options for 15 settings for the Tivoli Storage Manager 222 size of database 36 tuning 37 volume manager 36 with alternate/parallel paths and servers 183 permissions granting for Administration Assistant client 81 platform differences xii supported xii policy definition 205 domain 205 glossary definition 233 set 205 activate 205, 206 glossary definition 233 policy file granting permissions for Administration Assistant client 81 printing reports 17, 105 problem determination describing problems 228 determining business impact 228 submitting problems 228 production system 70 productivity options backup status monitoring 17 managing data on the backup server 18 performance analysis 17 reporting 17 profile keywords syntax 115 profiles example of Tivoli Storage Manager for UNIX and Linux 213 Tivoli Storage Manager example for Windows 214 ProLE 26, 27, 42 glossary definition 233
remote backup server glossary definition 234 remote shares (Windows) implementing configuration files on 28 reports 17 creating 109 modifying the output 111 on backup performance 107 on failed actions 107 prerequisites for 109 types 105 UNIX scheduling sample 195 using templates 110 using the Administration Assistant Client 105, 110 Windows scheduling sample 195 restore applying backup results to 102 database command 4 full restore 199 performance optimization 35 multiplexing 38 redirected 57, 65, 67, 68 start from command line 197 start in non-partitioned environment 197 start in partitioned environment 198 tablespaces 57 retention 15, 18 glossary definition 234 RISC 6000 buffer pool settings 222 RL_COMPRESSION 16 RL_COMPRESSION profile keyword 40, 120
S
sample DP for SAP profile UNIX or Linux 122 Windows 125 SAN File System 175 SAP (backup) scheduler 11 SAP Note glossary definition 234 SAP-DB2 Administration Tools 3, 6, 14 Scaling of tablespaces 72 glossary definition 234 scheduled batch backup Windows example 219 scheduling automatic backups 11 backup jobs 217, 219 function of Tivoli Storage Manager 11 products 11 UNIX or Linux examples 217 Windows examples 219 scheduling client command line interface 80 creating reports 110 glossary definition 234 prerequisites 82 setting up 87 scope of DP for SAP 9, 13
R
recovery time for 10 Recovery History File 4, 5, 57, 60, 197, 198 glossary definition 233 redirected restore 65 automatic mode 66 batch mode 68 interactive mode 67 plausibility checks 69 prerequisite 65 using Backup Object Manager 63 REDOLOG_COPIES 16 profile keyword 119 remote backup glossary definition 234
244
scratch volume 205 glossary definition 234 security settings authorizing Administration Assistant users 90 server installing Administration Assistant components 82 server configuration file glossary definition 234 SERVER profile keyword 120 servers alternate 17 alternate/parallel 16 service marks 237 sessions glossary definition 234 multiple (parallel) 15, 16, 37, 38, 39, 43, 48, 98, 99, 100, 102, 118, 120, 121, 183, 186, 188, 199 single 15, 102 SESSIONS profile keyword 121 setting Tivoli Storage Manager passwords manually 43 setting up Tivoli Storage Manager 203 setup understanding for troubleshooting 165 shared library 4 glossary definition 234 shortcut keys 238 SID 26, 27, 115, 129, 166, 167, 170, 171, 173, 177, 183, 184, 197, 199 glossary definition 234 Single System View (SSV) backup 200 snapshot devices 18 software compression vs. hardware compression UNIX or Linux 208 Windows 209 Software Support contacting 227 describing problems 228 determining business impact 228 receiving weekly updates 226 submitting problems 228 SP Switch buffer pool settings 222 specifying management classes 16 storage device setup Tivoli Storage Manager server 204 storage pool 16, 39, 204, 205 definition 205 glossary definition 234 strategy planning a backup strategy 9 support xiii, 225 SYSCATSPACE 74
T
tablespace 36, 53, 56, 57, 58, 59, 60, 61, 118, 197, 198 automated adaptations 72 container 189 definition information 56, 64, 189
tablespace (continued) creation of 65 glossary definition 234 restore of 58 sample 190 glossary definition 234 normalizing 68, 74, 233 scaling 72, 234 tablespace container glossary definition 234 tape drives using hardware compression with 208, 209 tape usage for backups 15 TCP_ADDRESS profile keyword 121 TDI glossary definition 234 TDP_DIR 26, 27, 170 template for creating reports 110 terminating the backup job 183 test system 70 threshold definitions Administration Assistant 92 via custom SQL file 93 Tivoli Storage Manager adjusting to DP for SAP 204 alternate network paths and servers 43 backup scheduler 11 client software compression 209 configuration file customization 222 data compression 40 expiration function 119 glossary definition 234 management classes 16 network settings 222 options files 29 passwords 43 performance optimization 222 profile example for UNIX and Linux 213 profile example for Windows 214 scheduling function 11 setup 203 Tivoli Storage Manager API client configuration 24 glossary definition 234 installation verification 30 Tivoli Storage Manager client configuration 207 configuration on UNIX or Linux 207 configuration on Windows 209 software compression 208 Tivoli Storage Manager passwords authentication off 43 automatic generation 44 configuration matrix to set keywords 211, 212 manual generation 43 Tivoli Storage Manager server adding 42 configuration 203 configuration, prerequisites 204 management classes 205 node definition 206
Tivoli Storage Manager server (continued) performance considerations 203 policy definition 205 storage device setup 204 storage pool definition 205 storing data on 15 TRACE profile keyword 121 TRACEFILE profile keyword 121 TRACEMAX profile keyword 122 trademarks 237 transaction rate of DP for SAP 10 trimming the database 10 troubleshooting 165 Backup Object Manager 170 IBM support 172 installation 165 random problems 171 reproducible problems 171 setup 165 TSM for Advanced Copy Services 18 tuning 37
U
uninstalling DP for SAP from UNIX 33 from Windows 33 UNIX or Linux crontab, backup scheduler 11 upgrading DP for SAP 23, 24, 30 USE_AT profile keyword 122 user authorization for Administration Assistant 90 user exit 5, 6, 233 glossary definition 234 userids administering 90
V
validate glossary definition 234 policy set 205, 206 vendor API 3, 234 glossary definition 234 vendor environment file 29, 45, 166, 200 glossary definition 234 VENDOROPT configuration parameter 26, 27 verifying installation of the Administration Assistant 86 the DP for SAP installation 30 the TSM API installation 30 volume 16, 36, 204, 205, 234 glossary definition 235 manager settings 36
W
Web browser prerequisite for Administration Assistant 81 Windows, backup scheduler 11 Index
245
X
XINT_PROFILE 26, 27, 59, 170
246
Program Number: 5608APR
Printed in USA
SC33-6341-09

IBM Tivoli Storage Manager For Enterprise Resource Planning Data Protection For SAP Installation &amp User's Guide For DB2 Version 5.5

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IBM Tivoli Storage Manager For Enterprise Resource Planning Data Protection For SAP Installation &amp User's Guide For DB2 Version 5.5

Uploaded by

Copyright:

Available Formats

Tivoli Storage Manager for Enterprise Resource Planning

Tivoli Storage Manager for Enterprise Resource Planning

Part 2. Installing and Using Data Protection for SAP . . . . . . . . . 21

Part 1. Data Protection Basics . . . . 1

Chapter 2. Developing a Backup Strategy . . . . . . . . . . . . . . . 9

Chapter 3. Introducing Data Protection for SAP . . . . . . . . . . . . . . 13

Chapter 5. Adjusting Your System . . . 35

Chapter 9. Balancing Your System . . . 97

Chapter 6. Data Protection for SAP Backup Object Manager . . . . . . . 53

Chapter 10. Reporting on Data Protection for SAP Activities . . . . . 105

Chapter 7. DB2 Redirected Restore Using Backup Object Manager . . . . 63

. 107 . 109 . 109 . . . . 110 110 110 111

Part 3. Appendixes . . . . . . . . 113

Appendix B. Data Protection for SAP (DB2) Messages . . . . . . . . . . 129

Appendix C. Troubleshooting . . . . 165

. 171 . 172 172

Appendix E. Installation Planning Sheets . . . . . . . . . . . . . . 177

Appendix F. Alternate or Parallel Backup Paths and Backup Servers . . 183

Appendix L. Sample Tivoli Storage Manager Profiles . . . . . . . . . . 213

Appendix M. Backup Scheduling Examples . . . . . . . . . . . . . 217

Appendix I. Reference Material for the Administration Assistant . . . . . . 195

Appendix N. Hints and Tips for Network Settings . . . . . . . . . . 221

| Appendix O. Internet Protocol Version | 6 (IPv6) Support . . . . . . . . . . 223

Appendix P. Support Information . . . 225

Glossary . . . . . . . . . . . . . 231 Notices . . . . . . . . . . . . . . 237

Appendix K. Preparing Tivoli Storage Manager for DP for SAP . . . . . . . 203

. 238 239 239

Copyright IBM Corp. 1995, 2007

Copyright IBM Corp. 1995, 2007

How to Read This Book

Where to Find More Information

Copyright IBM Corp. 1995, 2007

Naming Conventions Used in this Documentation

Contents of the Data Protection for SAP Package

Part 1. Data Protection Basics

Copyright IBM Corp. 1995, 2007

Chapter 1. Concepts of Data Protection for SAP

DP for SAP and DB2 BACKUP DATABASE and RESTORE DATABASE

Copyright IBM Corp. 1995, 2007

Concepts of Data Protection for SAP

Figure 1. DB2 Backup Architecture

Concepts of Data Protection for SAP

DP for SAP and Log File Management

DP for SAP and BRARCHIVE / BRRESTORE

Chapter 1. Concepts of Data Protection

Concepts of Data Protection for SAP

Figure 2. DB2 Log File Management

Concepts of Data Protection for SAP

Data Protection for SAP and DB2 Log Manager

Concepts of Data Protection for SAP

Chapter 2. Developing a Backup Strategy

Types of Failures and the Scope of Data Protection for SAP

Figure 4. DB2 Backup Objects

Copyright IBM Corp. 1995, 2007

Developing a Backup Strategy

Trimming the Database Size

Backup Windows and Recovery Time

Developing a Backup Strategy

Implementing the Strategy by Scheduling Automated Backup Runs

UNIX or Linux crontab / Windows Scheduler

Tivoli Storage Manager Scheduler

IBM Tivoli Workload Scheduler