• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Ibm tivoli storage manager for enterprise resource planning data protection for sap installation & user's guide for db2 version 5.5
 

Ibm tivoli storage manager for enterprise resource planning data protection for sap installation & user's guide for db2 version 5.5

on

  • 2,024 views

 

Statistics

Views

Total Views
2,024
Views on SlideShare
2,024
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ibm tivoli storage manager for enterprise resource planning data protection for sap installation & user's guide for db2 version 5.5 Ibm tivoli storage manager for enterprise resource planning data protection for sap installation & user's guide for db2 version 5.5 Document Transcript

    • Tivoli Storage Manager ® for Enterprise Resource PlanningVersion 5.5Data Protection for SAPInstallation and User’s Guide for DB2 SC33-6341-09
    • Tivoli Storage Manager ® for Enterprise Resource PlanningVersion 5.5Data Protection for SAPInstallation and User’s Guide for DB2 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 NoticeThis edition applies to Data Protection for SAP Version 5 Release 5 Modification Level 0 (product number5608–APR) available as a licensed program product, and to all subsequent releases and modifications untilotherwise indicated in new editions.Order publications through your IBM® representative or the IBM branch office serving your area. Publications arenot stocked at the addresses given below.Address comments on this publication to:IBM Deutschland Entwicklung GmbHEnterprise Solution DevelopmentDept. 3848, Bldg. 71032-15Schoenaicher Str. 22071032 BoeblingenGermanyFAX (Germany): 07031 16 3619FAX (other countries): (+49) 7031 16 3619Internet Web page: http://www.ibm.com/software/tivoliMake sure to include the following in your comment or note:v Title and order number of this bookv Page number or topic related to your commentWhen you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in anyway 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 Contractwith IBM Corp.
    • Contents Figures . . . . . . . . . . . . . . vii Alternate Network Paths and Servers . . . . . 17 Messaging . . . . . . . . . . . . . . 17 Tables . . . . . . . . . . . . . . . ix Productivity Options of Data Protection for SAP . . 17 Reporting . . . . . . . . . . . . . . 17 Monitoring the Backup Status . . . . . . . 17 Preface . . . . . . . . . . . . . . . xi Performance Analysis . . . . . . . . . . 17 Who Should Read This Book . . . . . . . . . xi Managing Data on the Backup Server . . . . 18 How to Read This Book . . . . . . . . . . xi | Using Data Protection for Snapshot Devices to Where to Find More Information . . . . . . . xi | Minimize Backup and Restore Windows . . . . . 18 Naming Conventions Used in this Documentation xii Archiving Inactive Data . . . . . . . . . . 18 Contents of the Data Protection for SAP Package . . xii Supported Platforms . . . . . . . . . . . xii Platform Differences . . . . . . . . . . . xii Part 2. Installing and Using Data| Summary of Changes . . . . . . . . . . . xii Protection for SAP . . . . . . . . . 21 Support . . . . . . . . . . . . . . . xiii Chapter 4. Installing or Upgrading Data Part 1. Data Protection Basics . . . . 1 Protection for SAP . . . . . . . . . 23 Prerequisites for the Installation of Data Protection Chapter 1. Concepts of Data Protection for SAP . . . . . . . . . . . . . . . . 23 for SAP . . . . . . . . . . . . . . . 3 Installation Planning for Data Protection for SAP . . 24 DP for SAP and DB2 BACKUP DATABASE and | Installing Data Protection for SAP . . . . . . . 24 RESTORE DATABASE . . . . . . . . . . . 3 | Installing Data Protection for SAP on UNIX (AIX, DP for SAP and Log File Management . . . . . . 5 | Solaris) or Linux . . . . . . . . . . . . 25 DP for SAP and BRARCHIVE / BRRESTORE . . . 5 | Installing Data Protection for SAP on Windows 27 Post-Installation Steps . . . . . . . . . . . 29 Data Protection for SAP and DB2 Log Manager . . . 7 Review of the TSM Options Files . . . . . . 29 Set the Password . . . . . . . . . . . 29 Chapter 2. Developing a Backup Optional: Restart DB2 Instance . . . . . . . 29 Strategy . . . . . . . . . . . . . . . 9 Verifying the Initial and Upgrade Installation . . 30 Types of Failures and the Scope of Data Protection Verifying the TSM API Installation. . . . . . 30 for SAP . . . . . . . . . . . . . . . . 9 Upgrading (Migration) . . . . . . . . . . 30 Trimming the Database Size . . . . . . . . 10 Upgrading Data Protection for SAP . . . . . 30 Transaction Rate . . . . . . . . . . . . 10 Migration of the DP for SAP Profile . . . . . 31 Backup Windows and Recovery Time. . . . . 10 Creation of Configuration Files . . . . . . . 31 Implementing the Strategy by Scheduling Special Installation . . . . . . . . . . . . 32 Automated Backup Runs . . . . . . . . . . 11 Silent Installation . . . . . . . . . . . 32 Scheduling Products . . . . . . . . . . 11 Console Installation. . . . . . . . . . . 33 Sample Backup Strategy for Daily Backup Firewall Installation . . . . . . . . . . 33 Processing . . . . . . . . . . . . . . 12 Uninstalling Data Protection for SAP . . . . . . 33 Uninstalling the Old Version of DP for SAP Chapter 3. Introducing Data Protection under UNIX or Linux . . . . . . . . . . 33 for SAP . . . . . . . . . . . . . . 13 Uninstalling the Old Version of DP for SAP Scope of Data Protection for SAP . . . . . . . 13 under Windows . . . . . . . . . . . . 33 Integration of Data Protection for SAP with SAP . . 14 Storing Data on a TSM Server . . . . . . . . 15 Chapter 5. Adjusting Your System . . . 35 Performance Options of Data Protection for SAP . . 15 General Performance Considerations . . . . . . 35 Parallel (Multiple) Sessions . . . . . . . . 16 Database Server Considerations . . . . . . 36 Multiple (Parallel) Network Paths and Multiple Network Considerations . . . . . . . . . 36 (Parallel) Servers . . . . . . . . . . . 16 Backup Server Considerations . . . . . . . 37 Incremental and Delta Backup . . . . . . . 16 Adjustments to DP for SAP for Improving RL Compression . . . . . . . . . . . . 16 Performance of Data Transfer . . . . . . . . 37 Automation Options of Data Protection for SAP . . 16 Multiplexing . . . . . . . . . . . . . 38 Selectable Management Classes . . . . . . . 16 Multiple Sessions . . . . . . . . . . . 38 Retain Backups by Version . . . . . . . . 16 Multiple Network Paths . . . . . . . . . 39 Multiple DB2 Log File Copies . . . . . . . 16 Multiple Servers . . . . . . . . . . . . 40 © Copyright IBM Corp. 1995, 2007 iii
    • Compression . . . . . . . . . . . . . 40 Administering User IDs . . . . . . . . . 90 Buffer Copies . . . . . . . . . . . . . 41 Configuring for Secure Communication . . . . 91 Buffer Size . . . . . . . . . . . . . . 41 Changing the Password for the Administration Adjustments for Interaction with Other Components 41 Assistant Database User ID . . . . . . . . 92 Adjustments for the Administration Assistant . . 41 | Defining Thresholds . . . . . . . . . . 92 Adjustments for IBM Tivoli Storage Manager . . 42 | Defining the Custom SQL file . . . . . . . 93 Rules for Adjustments in the DP for SAP Environment . . . . . . . . . . . . . . 45 Chapter 9. Balancing Your System . . . 97| Using the VENDOROPT Parameter . . . . . 45 Observations on the DP for SAP Data Throughput 97| Setting Up DB2 to Use the Built-In Log Manager Data Protection for SAP Performance Sensors . . . 98| with DP for SAP. . . . . . . . . . . . 46 Presentation of the Measurements in the Adjustments for High Availability . . . . . . . 48 Administration Assistant . . . . . . . . . . 98 Considerations for Using IBM HACMP for AIX 48 Typical Situations . . . . . . . . . . . 99 Drilling Down on Special Situations . . . . . 102 Chapter 6. Data Protection for SAP Applying Backup Results to Restore . . . . . 102 Backup Object Manager . . . . . . . 53 Backup Object Manager Setup . . . . . . . . 54 Chapter 10. Reporting on Data Managing Backup Objects . . . . . . . . . 55 Protection for SAP Activities . . . . . 105 Backup Object Manager Commands . . . . . 55 Types of Reports . . . . . . . . . . . . 105 Backup Object Manager Command Options . . 58 Reporting on Backup States . . . . . . . 105 Examples . . . . . . . . . . . . . . 61 Reporting on Operations Details . . . . . . 106 Reporting on Backup Operation Trends . . . . 106 Chapter 7. DB2 Redirected Restore Reporting on Failed Actions . . . . . . . 107 Using Backup Object Manager . . . . 63 Reporting on the Performance of Backup Tablespace Definition Information . . . . . . . 64 Operations . . . . . . . . . . . . . 107 Creating Tablespace Definition Information . . . . 65 Prerequisites for Creating Reports . . . . . . 109 Redirected Restore . . . . . . . . . . . . 65 Creating a Report . . . . . . . . . . . . 109 Redirected Restore Prerequisites . . . . . . 65 Requesting a Report from the Administration Redirected Restore in Automatic Mode . . . . 66 Assistant Client . . . . . . . . . . . . 110 Redirected Restore in Interactive Mode . . . . 67 Working with Report Templates . . . . . . 110 Redirected Restore in Batch Mode . . . . . . 68 Generating Reports Using Report Templates . . 110 Redirected Restore Plausibility Checks . . . . . 69 Modifying Report Output . . . . . . . . . 111 Sample Work Flow for Redirected Restore . . . . 70 Automated Tablespace Adaptations . . . . . . 72 Part 3. Appendixes . . . . . . . . 113 Tablespace Scaling . . . . . . . . . . . 72 Tablespace Normalizing . . . . . . . . . 74 Appendix A. The Data Protection for Chapter 8. Installing and Using the SAP Profile . . . . . . . . . . . . 115 Keyword Reference . . . . . . . . . . . 115 Administration Assistant for Data Sample Data Protection for SAP Profiles . . . . 122 Protection for SAP . . . . . . . . . 77 Sample Data Protection for SAP Profile for Introducing the Administration Assistant . . . . 77 UNIX or Linux . . . . . . . . . . . . 122 Functions and Features of the Administration Sample Data Protection for SAP Profile for Assistant . . . . . . . . . . . . . . 77 Windows . . . . . . . . . . . . . . 125 Concepts of the Administration Assistant . . . 78 Installing or Upgrading the Administration Appendix B. Data Protection for SAP Assistant . . . . . . . . . . . . . . . 81 Prerequisites for Installing the Administration (DB2) Messages . . . . . . . . . . 129 Assistant . . . . . . . . . . . . . . 81 How To Find Files Containing Message Output Installation Planning for the Administration (Log Files) . . . . . . . . . . . . . . 129 Assistant Server-Level Components . . . . . 82 Prefix BKI . . . . . . . . . . . . . . 130 Installing the Administration Assistant Server-Level Components . . . . . . . . 82 Appendix C. Troubleshooting . . . . 165 Post-Installation Steps . . . . . . . . . . 85 Problem Resolution During Installation and Setup 165 Starting and Stopping the Administration Understanding the Setup . . . . . . . . 165 Assistant Manually . . . . . . . . . . . 87 Location of Log Files . . . . . . . . . . 167 Upgrading the Administration Assistant General Problem Resolution . . . . . . . . 167 (Migration) . . . . . . . . . . . . . 88 Problem Resolution When Using the Backup Object| Migration of Data from Previous Releases . . . 89 Manager . . . . . . . . . . . . . . . 170 Configuring the Administration Assistant . . . . 90 Problem Resolution During Operation . . . . . 170 Reproducible (Repeatable) Problems . . . . . 171 iv Data Protection for SAP Installation and User’s Guide for DB2
    • Random Problems . . . . . . . . . . . 171 General Considerations for TSM . . . . . . 203 DB2 Vendor Reason Codes . . . . . . . . . 172 Prerequisites . . . . . . . . . . . . . 204 Providing Information to IBM or Tivoli Support 172 Adjusting Tivoli Storage Manager for DP for SAP . . . . . . . . . . . . . . . 204| Appendix D. Using DP for SAP with a Configuring the Tivoli Storage Manager Clients 207| Distributed File System on AIX . . . . 175 General Considerations . . . . . . . . . 207 Tivoli Storage Manager Clients on UNIX or| Setting Up DP for SAP in a Distributed File System 175 Linux Systems . . . . . . . . . . . . 207| Setting Up DP for SAP in a Distributed File System Tivoli Storage Manager Clients on Windows| in an Adaptive Computing Environment . . . . 175 Systems . . . . . . . . . . . . . . 209 Password Handling . . . . . . . . . . . 210 Appendix E. Installation Planning Password Configuration Matrix (UNIX or Linux) 211 Sheets . . . . . . . . . . . . . . 177 Password Configuration Matrix (Windows) . . 212 Data Protection for SAP . . . . . . . . . . 177 Administration Assistant . . . . . . . . . 178 Appendix L. Sample Tivoli Storage Manager Profiles . . . . . . . . . . 213 Appendix F. Alternate or Parallel Sample TSM Profiles for UNIX or Linux . . . . 213 Backup Paths and Backup Servers . . 183 Client User Options File Sample (dsm.opt) . . 213 Parameter Settings - SERVER Statement . . . . 184 Client System Options File Sample (dsm.sys) 213 Example 1: Use of Alternate Paths for Increased Include/Exclude List Sample . . . . . . . 213 Availability . . . . . . . . . . . . . 185 Sample TSM Profiles for Windows . . . . . . 214| Example 2: Use of Parallel Servers for Increased Client User Options File Sample (dsm.opt) . . 214| Performance . . . . . . . . . . . . . 187 Client Options Files Sample (<server>.opt) . . 214 Example 3: Use of Alternate Servers for Disaster Include/Exclude List Sample . . . . . . . 215 Recovery . . . . . . . . . . . . . . 188 Appendix M. Backup Scheduling Appendix G. Tablespace Definition Examples . . . . . . . . . . . . . 217 Information (TDI) . . . . . . . . . . 189 UNIX or Linux Crontab Example . . . . . . . 217 Elements of Backup Schedules for UNIX or Linux 217 Appendix H. Data Protection for SAP Crontab File Sample . . . . . . . . . . 217 Setup Examples . . . . . . . . . . 193 Full Offline Backup Shell Script Sample . . . 218 Sample DB2 Vendor Environment File . . . . . 193 Windows Scheduling Example. . . . . . . . 218 Elements of Backup Schedules for Windows . . . 219 Schedule Batch Sample . . . . . . . . . 219 Appendix I. Reference Material for the Full Offline Backup Batch File Sample . . . . 219 Administration Assistant . . . . . . 195 Sample Command Files for Scheduling Reports 195 Appendix N. Hints and Tips for Sample Shell Script for Scheduling a Report from a UNIX Scheduling Client . . . . . . 195 Network Settings . . . . . . . . . . 221 Sample Command File for Scheduling a Report Networks with Large Bandwidth-Delay Product 221 from a Windows Scheduling Client . . . . . 195 SP Switch (RISC 6000) . . . . . . . . . . 222| Sample Custom SQL File . . . . . . . . . 196 Network Settings of the Tivoli Storage Manager 222 Appendix J. Using DP for SAP to | Appendix O. Internet Protocol Version Back Up and Restore Files and | 6 (IPv6) Support . . . . . . . . . . 223 Databases . . . . . . . . . . . . . 197 Backups and Restores in Non-Partitioned Database Appendix P. Support Information . . . 225 Environments . . . . . . . . . . . . . 197 Using IBM Support Assistant . . . . . . . . 225 Starting Backups in a Non-Partitioned Database Obtaining Fixes. . . . . . . . . . . . . 225 Environment . . . . . . . . . . . . 197 Receiving Weekly Support Updates . . . . . . 226 Starting Restores in a Non-Partitioned Database Contacting IBM Software Support . . . . . . 227 Environment . . . . . . . . . . . . 197 Determining the Business Impact . . . . . . 228 Backups and Restores in Partitioned Database Describing Problems and Gathering Information 228 Environments . . . . . . . . . . . . . 198 Submitting Problems . . . . . . . . . . 228| Using DB2 Single System View (SSV) for Backup 200 Glossary . . . . . . . . . . . . . 231 Appendix K. Preparing Tivoli Storage Manager for DP for SAP . . . . . . . 203 Notices . . . . . . . . . . . . . . 237 Configuring the Tivoli Storage Manager Server . . 203 Trademarks and Service Marks . . . . . . . 237 Contents v
    • Accessibility . . . . . . . . . . . . . . 238 Index . . . . . . . . . . . . . . . 241 Navigating the Interface Using the Keyboard 239 Magnifying What is Displayed on the Screen 239vi Data Protection for SAP Installation and User’s Guide for DB2
    • Figures 1. DB2 Backup Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. DB2 Log File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Log Management with DB2 Log Manager and DP for SAP . . . . . . . . . . . . . . . . . . 7 4. DB2 Backup Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Production Backup Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Scope of Data Protection for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Integration of Data Protection for SAP with DB2 . . . . . . . . . . . . . . . . . . . . . 14 8. Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 9. Data Transfer for a Backup / Restore . . . . . . . . . . . . . . . . . . . . . . . . . 3710. Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3811. Parallel (Multiple) Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3812. Parallel (Multiple) Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3913. Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4014. Null Block Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4115. Sample Environment for HACMP Takeover . . . . . . . . . . . . . . . . . . . . . . . 4916. Data Protection for SAP Backup Object Manager . . . . . . . . . . . . . . . . . . . . . 5417. Redirected Restore Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6318. Tablespace Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7319. Tablespace Normalizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7520. Administration Assistant Components (with Default Port Numbers) . . . . . . . . . . . . . . 7821. Example of an SAP Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . 8022. A Bird’s Eye View of the Data Flow During Backup . . . . . . . . . . . . . . . . . . . . 9723. Performance Optimizing by Using Sensors . . . . . . . . . . . . . . . . . . . . . . . 9824. Showing Data Throughput and I/O Utilization . . . . . . . . . . . . . . . . . . . . . 9825. Indicating a Disk Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9926. Indicating a Network or TSM Bottleneck . . . . . . . . . . . . . . . . . . . . . . . 10027. Indicating a Balanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 10128. Drilling Down: Replay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 10229. Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10630. Operations – Detailed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 10631. Operations Daily Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10732. Operations - Failure Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10733. Performance Report - Graphical Presentation Section . . . . . . . . . . . . . . . . . . . 10834. Performance Report - Tabular Presentation Section . . . . . . . . . . . . . . . . . . . . 10935. SAP and Data Protection for SAP Configuration files on UNIX and Linux. . . . . . . . . . . . . 16636. General Problem Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168© Copyright IBM Corp. 1995, 2007 vii
    • viii Data Protection for SAP Installation and User’s Guide for DB2
    • Tables| 1. File Extensions for Shared Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 25| 2. Database Configuration Parameters Introduced with DB2 V8.2 . . . . . . . . . . . . . . . . 46| 3. Tags for Defining Thresholds in the Custom SQL File . . . . . . . . . . . . . . . . . . . 93| 4. Contents of the Custom SQL File . . . . . . . . . . . . . . . . . . . . . . . . . . 94 5. DB2 Vendor Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 6. Installation Parameters for Data Protection for SAP . . . . . . . . . . . . . . . . . . . . 177 7. Installation Parameters for the Administration Assistant . . . . . . . . . . . . . . . . . . 178 8. SERVER Statement and Appropriate Profile and Option File Settings. . . . . . . . . . . . . . . 184 9. Password Handling for UNIX or Linux . . . . . . . . . . . . . . . . . . . . . . . . 211 10. Password Handling for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 212 11. Tuning of Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 12. Tuning of SP Switch Buffer Pools . . . . . . . . . . . . . . . . . . . . . . . . . . 222 13. Tuning Tivoli Storage Manager Configuration File Attributes. . . . . . . . . . . . . . . . . 222 © Copyright IBM Corp. 1995, 2007 ix
    • x Data Protection for SAP Installation and User’s Guide for DB2
    • 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 © Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • | 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Part 1. Data Protection Basics© Copyright IBM Corp. 1995, 2007 1
    • 2 Data Protection for SAP Installation and User’s Guide for DB2
    • 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. © Copyright IBM Corp. 1995, 2007 3
    • 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 TSM4 Data Protection for SAP Installation and User’s Guide for DB2
    • Concepts of Data Protection for SAP 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 FileDP 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 5
    • Concepts of Data Protection for SAPFigure 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 TSM6 Data Protection for SAP Installation and User’s Guide for DB2
    • Concepts of Data Protection for SAP 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 7
    • Concepts of Data Protection for SAP 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.8 Data Protection for SAP Installation and User’s Guide for DB2
    • 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© Copyright IBM Corp. 1995, 2007 9
    • 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 recovery10 Data Protection for SAP Installation and User’s Guide for DB2
    • Developing a Backup Strategy 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 Administrator’s 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
    • Developing a Backup Strategy 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 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 DB2’s backup and recovery facilities and allows you to follow SAP’s 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.© Copyright IBM Corp. 1995, 2007 13
    • Introducing Data Protection for SAPIntegration 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 administrator’s 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Introducing Data Protection for SAPStoring 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 Chapter 3. Introducing Data Protection for SAP 15
    • Introducing Data Protection for SAP 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 archive16 Data Protection for SAP Installation and User’s Guide for DB2
    • Introducing Data Protection for SAP 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. Chapter 3. Introducing Data Protection for SAP 17
    • Introducing Data Protection for SAP 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Introducing Data Protection for SAPv outgoing documents (e.g. printed output like invoices, bills)v incoming documents (e.g. digitized fax, scanned letters, audio)v local documents (e.g. text, spreadsheets, pictures, graphics)v inactive dataThus TSM can be used as an integrated repository for backups and for archivedinformation.For more information on DB2 CommonStore for SAP , see: http://www.ibm.com/software/data/commonstore/sap/. Chapter 3. Introducing Data Protection for SAP 19
    • 20 Data Protection for SAP Installation and User’s Guide for DB2
    • Part 2. Installing and Using Data Protection for SAP© Copyright IBM Corp. 1995, 2007 21
    • 22 Data Protection for SAP Installation and User’s Guide for DB2
    • 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/.© Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing or Upgrading Data Protection for SAP| 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 Extension| AIX a| HP-UX sl| Linux so| Solaris 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. Chapter 4. Installing or Upgrading Data Protection for SAP 25
    • Installing or Upgrading Data Protection for SAP| 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 VENDOR:/<path>/<library>| LOGARCHOPTn /<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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing or Upgrading Data Protection for SAP| 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%system32driversetcservices 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. Chapter 4. Installing or Upgrading Data Protection for SAP 27
    • Installing or Upgrading Data Protection for SAP| 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 VENDOR:<path>tdpdb2.dll| LOGARCHOPTn <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 (serverpathfilename). 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing or Upgrading Data Protection for SAP| 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 Chapter 4. Installing or Upgrading Data Protection for SAP 29
    • Installing or Upgrading Data Protection for SAP 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 the30 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing or Upgrading Data Protection for SAP 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: Chapter 4. Installing or Upgrading Data Protection for SAP 31
    • Installing or Upgrading Data Protection for SAP 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> -silent32 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing or Upgrading Data Protection for SAP 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. Chapter 4. Installing or Upgrading Data Protection for SAP 33
    • Installing or Upgrading Data Protection for SAP 3. Select Start → Settings → Control panel. 4. Click on Add/Remove Programs. 5. Select the old version of DP for SAP and click on Remove. 6. Follow the instructions of the uninstall procedure.34 Data Protection for SAP Installation and User’s Guide for DB2
    • 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.© Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your System 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 DataTransfer 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: Chapter 5. Adjusting Your System 37
    • Adjusting Your System 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) Sessions38 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your System 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 Chapter 5. Adjusting Your System 39
    • Adjusting Your System 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. Compression40 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your System 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 Chapter 5. Adjusting Your System 41
    • Adjusting Your System 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your System 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. Chapter 5. Adjusting Your System 43
    • Adjusting Your System 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your System 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 file’s 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: Chapter 5. Adjusting Your System 45
    • Adjusting Your System| 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 Description Default| LOGARCHMETH1 Media type of the primary Off| destination for archived log| files| LOGARCHOPT1 Options field for the primary NULL| destination for archived log| files (if required).| LOGARCHMETH2 Media type of the secondary Off| 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.| LOGARCHOPT2 Options field for the NULL| secondary destination for| archived log files (if| required). 46 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your System| Table 2. Database Configuration Parameters Introduced with DB2 V8.2 (continued)| Parameter Description Default| FAILARCHPATH 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.| NUMARCHRETRY 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.| ARCHRETRYDELAY 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.| VENDOROPT 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.|| 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. Chapter 5. Adjusting Your System 47
    • Adjusting Your System| 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your SystemThe following figure illustrates the takeover environment:Figure 15. Sample Environment for HACMP TakeoverDP for SAP InternalsFiles: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 followingprocedure: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 SetupInstallation:A prerequisite for installation is a correct setup of the TSM client. The installationsteps for the TSM Backup/Archive Client for AIX can be found in thedocumentation Tivoli Storage Manager Installing the Clients.Defining DP for SAP as an HACMP Application: To enable DP for SAP toparticipate in HACMP failover processing, it must be defined as an application to Chapter 5. Adjusting Your System 49
    • Adjusting Your System 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Adjusting Your SystemThe TSM client application should be added to the same resource group thatcontains the file systems it will back up. The file systems defined in the resourcegroup should also be the ones specified in the domain for this client instance in theclient 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. Chapter 5. Adjusting Your System 51
    • Adjusting Your System 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 052 Data Protection for SAP Installation and User’s Guide for DB2
    • 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.© Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Data Protection for SAP Backup Object Manager 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 Password: password for Query: q_all | q_db | q_ts | q_log | q_tdi | q_raw for Backup: b_db for 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 <instance> -a <alias name> -n <node number> -u <userid> -p <password> -t <timestamp | timerange> -l <log number | log number range> -k <log chain | log chain range> -f <file name> -d <destination directory> -e <execution profile> -b <buffer size> -s <scaling factor> -N -S <sessions> -B <number of buffers> -P <parallelism> -D <target database> -T <tablespace> -R full | incremental | delta -O -L -C -x -v -m <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 Chapter 6. Data Protection for SAP Backup Object Manager 55
    • Data Protection for SAP Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Data Protection for SAP Backup Object Manager [-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 backupobject that was created by DP for SAP. (For a detailed description of the commandoptions, 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] Chapter 6. Data Protection for SAP Backup Object Manager 57
    • Data Protection for SAP Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Data Protection for SAP Backup Object Managerv -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>. Chapter 6. Data Protection for SAP Backup Object Manager 59
    • Data Protection for SAP Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Data Protection for SAP Backup Object Manager 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 Chapter 6. Data Protection for SAP Backup Object Manager 61
    • Data Protection for SAP Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Chapter 7. DB2 Redirected Restore Using Backup ObjectManager 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.© Copyright IBM Corp. 1995, 2007 63
    • DB2 Redirected Restore Using Backup Object ManagerTablespace 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 Data Protection for SAP Installation and User’s Guide for DB2
    • DB2 Redirected Restore Using Backup Object ManagerCreating 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: Chapter 7. DB2 Redirected Restore Using Backup Object Manager 65
    • DB2 Redirected Restore Using Backup Object Manager – 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 database66 Data Protection for SAP Installation and User’s Guide for DB2
    • DB2 Redirected Restore Using Backup Object Manager 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’ Chapter 7. DB2 Redirected Restore Using Backup Object Manager 67
    • DB2 Redirected Restore Using Backup Object Manager from the main menu. The administrator can also abort the redirected restore from any menu by entering ’a’. 6. 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”). 7. 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. 8. 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. 9. Finally, Backup Object Manager calls the DB2 redirected restore function. 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 Data Protection for SAP Installation and User’s Guide for DB2
    • DB2 Redirected Restore Using Backup Object Manager 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. Chapter 7. DB2 Redirected Restore Using Backup Object Manager 69
    • DB2 Redirected Restore Using Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • DB2 Redirected Restore Using Backup Object Manager 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 SERVER v ADSMNODE v BRBACKUPMGTCLASS v 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> Chapter 7. DB2 Redirected Restore Using Backup Object Manager 71
    • DB2 Redirected Restore Using Backup Object Manager – 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 Data Protection for SAP Installation and User’s Guide for DB2
    • DB2 Redirected Restore Using Backup Object ManagerFigure 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. v - 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. Chapter 7. DB2 Redirected Restore Using Backup Object Manager 73
    • DB2 Redirected Restore Using Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • DB2 Redirected Restore Using Backup Object ManagerFigure 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). Chapter 7. DB2 Redirected Restore Using Backup Object Manager 75
    • DB2 Redirected Restore Using Backup Object Manager 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 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 Monitor operations v View performance data v Configure systems v Request problem support v Manage report templates v 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. © Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant| 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
    • Installing and Using the Administration Assistant 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 Java™applet 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant 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: Chapter 8. Administration Assistant 81
    • Installing and Using the Administration Assistant 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.jar82 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant 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 UNIX or Linux Windows Server sadma.sh sadma.cmd| Database Agent sdba.sh sdba.cmd Database sdb.sh sdb.cmd v The configuration file assist.cfg, containing all relevant configuration parameters specified during the installation, is created and added to the installation directory. Chapter 8. Administration Assistant 83
    • Installing and Using the Administration Assistant 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 Entry in /etc/init.d Server adminAssistant, with parameters start, stop, and status Database Agent databaseAgent, with parameters start, stop, and status Database (Derby) (optional, as alternative to apacheDerby, with parameters start and stop DB2)| Database (DB2) (optional, as alternative to Not applicable| 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 server’s self-signed certificate is imported into the truststore on request. – The server’s 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 users entries. 84 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant 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 Chapter 8. Administration Assistant 85
    • Installing and Using the Administration Assistant 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 client’s 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 plugin’s 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 plugin’s truststore. If you did not replace the plugin’s 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.html86 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant 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 JVM’s 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 JVM’s 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> Chapter 8. Administration Assistant 87
    • Installing and Using the Administration Assistant 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant 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 Chapter 8. Administration Assistant 89
    • Installing and Using the Administration Assistant| 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant 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 server’s hostname is used as an alias for this key pair. Since the keystore contains the server’s private key, precautions must be taken that prevent access by unauthorized persons. v A truststore containing trusted certificates that allow verifying the server’s 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_MACHINESYSTEMCurrentControlSetServices... ...AdminAssistantParametersAppParameters -Djavax.net.ssl.keyStore=<keystore> -Djavax.net.ssl.keyStorePassword=<password for keystore> -Djavax.net.ssl.trustStore=<truststore> Chapter 8. Administration Assistant 91
    • Installing and Using the Administration Assistant 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 Throughput rate (in GB per hour or MB per second)| v Time since the last complete backup (in hours or days)| v Size of all log file backups since the last complete backup (in MB or GB)| v 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant| 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 Value| <sql> An SQL statement that will return data when the threshold is| exceeded.| <programid> 0 (Administration Assistant)| <actionid> 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 Filestdpr3assicustomSQLFile.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: Chapter 8. Administration Assistant 93
    • Installing and Using the Administration Assistant| <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 Definition| # Comment line| <sql> 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> Description of the SQL statement (maximum length: 300 characters)| <programid> Specifies the program that handles the result of the SQL statement.| v programid 0: Administration Assistant| <actionid> Defines the way the result will be handled, depending on the| programid (currently, the only value for actionid is 0):| v (programid 0: Administration Assistant): Send e-mail when| threshold exceeded (SQL statement returns data)| <displaygroup> List of display group IDs separated by commas, or "ALL" for all| display groups.| <system> List of system IDs separated by commas, or "ALL" for all systems.| <backuptype> 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installing and Using the Administration Assistant| 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. Chapter 8. Administration Assistant 95
    • Installing and Using the Administration Assistant96 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 Bird’s Eye View of the Data Flow During Backup From a bird’s 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.© Copyright IBM Corp. 1995, 2007 97
    • Balancing Your SystemData 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Balancing Your System The results of the Data Protection for SAP performance sensors are presented in the Administration Assistant’s 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. Chapter 9. Balancing Your System 99
    • Balancing Your System 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 you are looking to improve overall throughput you may want to v Increase the number of sessions to the TSM server (if the tape is the bottleneck), v Use multiple paths to a TSM server or multiple servers, v 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Balancing Your SystemA Balanced ConfigurationFigure 27. Indicating a Balanced ConfigurationIf the threads on both the disk and the network side are similarly busy throughoutthe backup the system is balanced, and the utilization of resources is good. In anoptimum setup, tapes are kept in streaming mode. That means that the network isat least as fast as the tape, and there is no idle time on the network side. Thus, aslight 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 moreresources 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. Chapter 9. Balancing Your System 101
    • Balancing Your System 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Balancing Your Systemv 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. Chapter 9. Balancing Your System 103
    • Balancing Your System104 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 Operations - Daily Report v Operations - Monthly Report v Operations - Failure Report v 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.© Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Reporting on Data Protection for SAP Activities 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 ReportReporting 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 ReportReporting 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. Chapter 10. Reporting on Data Protection for SAP Activities 107
    • Reporting on Data Protection for SAP Activities Figure 33. Performance Report - Graphical Presentation Section108 Data Protection for SAP Installation and User’s Guide for DB2
    • Reporting on Data Protection for SAP Activities Figure 34. Performance Report - Tabular Presentation SectionPrerequisites 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. Chapter 10. Reporting on Data Protection for SAP Activities 109
    • Reporting on Data Protection for SAP Activities 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Reporting on Data Protection for SAP Activities 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 user’s template path in the Administration Assistant Server component. <userid> is the Administration Assistant account of the template’s 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. Chapter 10. Reporting on Data Protection for SAP Activities 111
    • Reporting on Data Protection for SAP Activities 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Part 3. Appendixes© Copyright IBM Corp. 1995, 2007 113
    • 114 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 FilesTivoliTDP4SAP 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 <-- correct BRARCHIVEMGTCLASS MLOG1 # <-- correct BRARCHIVEMGTCLASS # MLOG1 <-- 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.© Copyright IBM Corp. 1995, 2007 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 Data Protection for SAP Installation and User’s Guide for DB2
    • The Data Protection for SAP Profile 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 Appendix A. The Data Protection for SAP Profile 117
    • The Data Protection for SAP Profile 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 that the mountlimit (mountl) parameter in the device class is set to the number of available tape drives. Make sure that the maxnummp parameter of the node is set to the number of 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 Data Protection for SAP Installation and User’s Guide for DB2
    • The Data Protection for SAP Profile 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 administrator’s 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. Appendix A. The Data Protection for SAP Profile 119
    • The Data Protection for SAP Profile 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 Data Protection for SAP Installation and User’s Guide for DB2
    • The Data Protection for SAP ProfileSESSIONS 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. Appendix A. The Data Protection for SAP Profile 121
    • The Data Protection for SAP Profile 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 &| # User’s 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 Data Protection for SAP Installation and User’s Guide for DB2
    • The Data Protection for SAP Profile| # 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. Appendix A. The Data Protection for SAP Profile 123
    • The Data Protection for SAP Profile| # 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 server_a # Servername, as defined in dsm.sys| SESSIONS 2 # 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 server_b # Servername, as defined in dsm.sys| # SESSIONS 2 # Maximum number of sessions| # to server_b| # PASSWORDREQUIRED YES # Use a password| # ADSMNODE NODE # Tivoli Storage Manager Nodename 124 Data Protection for SAP Installation and User’s Guide for DB2
    • The Data Protection for SAP Profile| # 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|| 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 & User’s 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|| Appendix A. The Data Protection for SAP Profile 125
    • The Data Protection for SAP Profile| #--------------------------------------------------------------------------| # 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:sqllibtdp_r3logtdpr3.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 Data Protection for SAP Installation and User’s Guide for DB2
    • The Data Protection for SAP Profile| # Specify the full path of the configuration file.| # Default: none.| #--------------------------------------------------------------------------| CONFIG_FILE c:sqllibtdp_r3%DB2NODEinitSID.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 server_a # Servername, as defined in dsm.sys| SESSIONS 2 # 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 server_b # Servername, as defined in dsm.sys| # SESSIONS 2 # 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| Appendix A. The Data Protection for SAP Profile 127
    • The Data Protection for SAP Profile128 Data Protection for SAP Installation and User’s Guide for DB2
    • | 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 © Copyright IBM Corp. 1995, 2007 129
    • MessagesPrefix 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 Error Processing cannot continue. W Warning Processing can continue, but problems may occur later. I Information Processing continues. User response is not necessary. v Explanation v User Response Explanation: The time needed for the completeBKI0000E Profile not specified. backup was elapsedtime.Explanation: Cannot locate the profile. User response: None.User response: Ensure that a profile is available.(Oracle) Note that the BACKINT call must have the BKI0023I Time: current_timefollowing form: backint -p init<SID>.utl . Done: saved_bytes (percent) of bytes Estimated end time: end_timeBKI0005I Start of program at: time Explanation: Finished saving a specific object atExplanation: DP for SAP received control from a current_time. The saved_bytes amount of the totalBR*Tools utility at the time denoted. number of bytes have been saved. percent shows the percentage. This call will be completed at the estimatedUser response: None. end_time. User response: None.BKI0007E Mode mode requires the environment variable environment variables to be set. BKI0024I Return code is: return codeExplanation: Not all environment variables requiredhave been set. At least environment variables where Explanation: A return code of 0 means no errors ormissing. warnings occurred. If the return code is 1, at least one warning was issued by the program. If the return codeUser response: Set the missing environment variables. is 2, at least one error message was issued. User response: For return codes other than 0, checkBKI0008E The environment variable name is not the run log for warnings or error messages. set correctly. The current value is value.Explanation: The value of the environment variable BKI0027I Time: current_timename is wrong. Objects: current_num of total_numUser response: Set name to an appropriate value. in process: file_name MGMNT-CLASS: management_class TSM Server: server name.BKI0020I End of program at: time Explanation: DP for SAP started saving current_numExplanation: (Oracle) DP for SAP returned control to a files at current_time. The total number of files to save isBR*Tools utility at the time denoted. (DB2) Program total_num. The file file_name is currently beingtdppasswd ended at the time indicated. processed. The files are transferred to the Tivoli StorageUser response: None. Manager server server name, which stores them in the management class management_class.BKI0021I Elapsed time: elapsedtime User response: None.130 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI0032E Error opening file file name: system error BKI0054I Time: current_time description Objects: current_num of total_num done: file_name with: bytesExplanation: A system error occurred during opening restored with description object_desc.of the file file name. system error description will describethe error in more detail. Explanation: DP for SAP completed restoring of current_num file at current_time. The total number ofUser response: Read the system error description. files to be restored is total_num. The file file_name with the size bytes is restored with the descriptionBKI0049I Please enter password for node nodename object_class. on server server name User response: None.Explanation: The password for the node nodename onthe Tivoli Storage Manager server server name has to be BKI0055I Object objectname with size saved withentered for storing it in the DP for SAP configuration description description.file. Explanation: The object objectname was savedUser response: Enter the password for the successfully.corresponding Tivoli Storage Manager server. User response: None.BKI0050I Please enter password for node nodename on server server name again BKI0056I Object objectname with size restored with description description.Explanation: In order to avoid typing errors, you haveto enter the password twice. Explanation: The object objectname was restored successfully.User response: Enter the password again. User response: None.BKI0051I Password successfully verified for node nodename on server server name. BKI0057I Time: current_time Object objectname with size saved with description description.Explanation: The password for the node nodename onthe Tivoli Storage Manager server server name was Explanation: The object objectname was savedchanged successfully. successfully.User response: None. User response: None.BKI0052E Password verification for node nodename BKI0058I Time: current_time Object objectname with on server server name failed. size restored with description description.Explanation: The password you entered for the node Explanation: The object objectname was restorednodename on the Tivoli Storage Manager server server successfully.name was wrong. User response: None.User response: Enter the password again. If this errorstill exists, contact your Tivoli Storage Manager BKI0059E You have to set the environmentadministrator. variable DSMI_CONFIG to the full filename of the Tivoli Storage ManagerBKI0053I Time: current_time client option file ’dsm.opt’. Objects: current_num of total_num Explanation: Tivoli Storage Manager client option file done: file_name with: bytes saved with not found. description object_desc. User response: Verify that the Tivoli Storage ManagerExplanation: DP for SAP completed saving option file dsm.opt is pointed to by DSMI_CONFIG.current_num file at current_time. The total number offiles to be saved is total_num. The file file_name with thesize bytes is saved with the description object_desc. BKI0060E The parameter parameter is not known.User response: None. Explanation: The command parameter parameter is unknown. User response: Check the specified command parameter and try again. Appendix B. Data Protection for SAP (DB2) Messages 131
    • MessagesBKI0063E The UTL file file name is not valid. BKI0454I *** This copy is NOT FOR RESALE. ***Explanation: Unable to read the input file file name Explanation: This version is not for resale.correctly. User response: None.User response: Check the path and name of theprofile (UTL file) and the appropriate file access BKI0455E License file file name does not exist.permission. Explanation: The license file agent.lic was not found where expected.BKI0064E The option option is unknown. User response: Make sure that the agent.lic fileExplanation: An option is invalid or unknown. resides in the same directory as the init<SID>.utl file.User response: Check the specified option(s) and tryagain. BKI0456E Unable to access license file file name. Explanation: The license file could not be accessed.BKI0065E The argument is missing for option option. User response: Make sure the access permissions allow read/write access.Explanation: Every option requires an argument.User response: Insert the missing argument and try BKI0457E License file file name contains invalidagain. data/checksum. Explanation: The license file is invalid.BKI0101I Session session: Please enter ’cont’ to continue or ’stop’ to cancel. User response: Make sure you have the right agent.lic file for the right platform installed.Explanation: If DP for SAP is running in unattended agent.lic files are platform dependent.mode (profile keyword BATCH), it terminates thecurrent run if operator intervention is required. BKI1000E Syntax error in line line: statementUser response: Enter ’cont’ or ’stop’. Explanation: The statement statement in the DP for SAP profile is unknown or incorrect.BKI0102I Your reply: reply. User response: Correct the error and try again.Explanation: The reply you made is confirmed.User response: None. BKI1001E Syntax error in file file name. Exiting Program.BKI0311E Request canceled by user. Explanation: A syntax error has been detected in theExplanation: (Oracle) BACKINT terminated at user’s file file name and the action has been halted.request. (DB2) Program terminated at user’s request. User response: Correct the error(s) in the file file nameUser response: None and try again.BKI0452E This version of product has expired. BKI1002E BACKUPIDPREFIX must be number_of_characters characters.Explanation: This is a test version that has expired. Explanation: The length of BACKUPIDPREFIX mustUser response: Order a release version of the product be number_of_characters characters.or contact your IBM/Tivoli Sales Representative. User response: Enter a BACKUPIDPREFIX with the required length (e.g., SAP___, BKI___).BKI0453W This version of product will expire in number days. BKI1003W Please set REDOLOG_COPIES to aExplanation: This is a test version with a time limit. It number between 1 and max_copies. Nowwill expire in number days. it is set to act_copies.User response: Order a release version of the product Explanation: DP for SAP currently supports 1 to 9or contact your IBM/Tivoli Sales Representative before copies of offline (redo) log files.the version expires. User response: Adapt the REDOLOG_COPIES settings in the DP for SAP profile.132 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI1004W You should specify the BKI1010W The configfile name BACKUPIDPREFIX before the configuration_filename should be absolute. TRACEFILE statement, so that the Explanation: None. BACKUPIDPREFIX can be used in the tracefile name. User response: Specify an absolute file name, for example /oracle/C21/dbs/initC21.bki orExplanation: The BACKUPIDPREFIX is used to build /db2/C21/dbs/initC21.bkithe Name of the tracefile. Therefore,BACKUPIDPREFIX must be specified before theTRACEFILE statement. BKI1012E Configfile not found or permission denied: configuration_filename.User response: Define a 6-characterBACKUPIDPREFIX in the DP for SAP profile (e.g., Explanation: DP for SAP is unable to read the fileSAP___, BKI___) configuration_filename. User response: This error could have various reasons,BKI1005W The tracefile name trace_filename should try the following: be absolute. 1. Check the path of the configuration file. The path must be specified in the profile (parameterExplanation: None. CONFIG_FILE).User response: Specify an absolute tracefile name, for 2. Make sure that the file access permissions are setexample /oracle/C21/saptrace/tracefile or correctly./db2/C21/saptrace/tracefile . BKI1013E Profile not found or permissions denied:BKI1006E The SERVERNAME must be less than profile_filename. max_char characters. Explanation: DP for SAP is unable to open the profileExplanation: You have used a SERVERNAME with profile_filename.more than max_char characters. User response: (Oracle) Ensure that the SAP backupUser response: Use a shorter SERVERNAME. 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 entryBKI1007E The NODENAME must be less than XINT_PROFILE. Furthermore, this file must be readable max_char characters. by DP for SAP. For details see “Installing DataExplanation: You have used a NODENAME with Protection for SAP” on page 24 and “Problemmore than max_char characters. Resolution During Installation and Setup” on page 165.User response: Use a shorter NODENAME. BKI1016W The trace file name file name could not be opened for writing!BKI1008E The MANAGEMENTCLASSNAME must be less than max_char characters. Explanation: The trace file could not be opened for writing.Explanation: You have used aMANAGEMENTCLASSNAME with more than User response: Ensure that you have specified amax_char characters. correct path for the trace file.User response: Use a shorterMANAGEMENTCLASSNAME. BKI1019E Failed to respond to a message received from XINT.BKI1009W Please set MULTIPLEX to a number Explanation: This messages indicates an internal error. between 1 and max_multiplex. Now it is User response: Contact DP for SAP support. set to act_multiplex.Explanation: You have set multiplexing to an BKI1020W The compress info file file name shouldunsupported number. DP for SAP now uses be absolute !act_multiplex. Explanation: The argument for the parameterUser response: Set multiplexing to a number between COMPR_INFO in the profile is an relative filename.1 and max_multiplex. User response: Always use an absolute filename as argument for the parameter COMPR_INFO. Appendix B. Data Protection for SAP (DB2) Messages 133
    • MessagesBKI1021E component_name terminates the BKI1203E Not enough sessions available (number connection due to a previous error. of sessions required and number of sessions available).Explanation: A serious error has occurred whichcaused a shutdown of the communication channel Explanation: The sum of available sessions specifiedbetween the component_name process and this in the various server statements (parameter SESSIONS)application. does not cover the required number of sessions (parameter MAX_SESSIONS).User response: Look for previous error messages todetect the root cause of the problem. User response: Change the values of the corresponding parameters in the DP for SAP profile, so that the condition mentioned in the explanation isBKI1022E component_name terminates the fulfilled. connection due to a previous error.Explanation: See message BKI1021E. BKI1205E If you want num_redoUser response: See message BKI1021E. REDOLOGCOPIES on Tivoli Storage Manager-Server servername, you should give me at least num_mc differentBKI1023W Could not establish connection to log Archive Management Classes. server log server name. Explanation: DP for SAP requires that the number ofExplanation: In the DP for SAP profile, log server log different Archive Management Classes (parameterserver name is specified (keyword LOG_SERVER). BRARCHIVEMGTCLASS) on the Tivoli StorageHowever, a connection to the server named could not Manager servers is equal to or greater than the numberbe established. No log records are sent to the log server. of redo log or log file copies (parameterUser response: REDOLOG_COPIES).v Check that the server name defined with keyword User response: Define at least as many different LOG_SERVER is spelled correctly in the DP for SAP Archive Management Classes as log file copies profile. requested.v Make sure there is a SERVER section in the profile for the log server defined with keyword BKI1211E There is something wrong with your LOG_SERVER. CONFIG_FILE file name.v Check the corresponding SERVER section and correct any setup problems. Explanation: There is a problem with your DP for SAP configuration file setup.v Make sure that the log server named is available. User response: Check the file permission and the file name specified in the DP for SAP profile keywordBKI1200E Cannot read/write file: file name. CONFIG_FILE.Explanation: The program is unable to read or write adata file (file name) of a tablespace being backed up or BKI1214E TSM Error: error textrestored. Explanation: The specified TSM error occurred.User response: Check the file access permission of theaffected file(s). Try again. If the problem still exists, User response: Check error text and correct thecontact the products administrator. problem. For further information you may want to refer to IBM Tivoli Storage Manager Messages SC32-9090BKI1201E There are no Tivoli Storage Manager Servers available. BKI1215I Average transmission rate was number GB/h (number MB/sec).Explanation: DP for SAP cannot locate a TivoliStorage Manager server. This may be due to a Explanation: The average transmission rate isconfiguration problem or to a problem while trying to displayed.connect to the Tivoli Storage Manager server. Most User response: None.probably, a preceding error message points to the causeof the problem. BKI1216E There are no BRBACKUPMGTCLASSESUser response: Look for and respond to preceding available.error messages. You may also want to check the DP forSAP profile and the IBM Tivoli Storage Manager client Explanation: The BRBACKUPMGTCLASSES you haveoptions and client system options files. specified in your init<SID>.utl file are not correct.134 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesUser response: Check the management classes on the BKI1229E Value for parameter BUFFSIZE (actualTSM server and specify correct ones. cur_number, maximum max_number) is too large for BUFFCOPY modeBKI1217E There are no BRARCHIVEMGTCLASSES PREVENT.″ available. Explanation: To utilize the BUFFCOPY modeExplanation: The BRARCHIVEMGTCLASSES you PREVENT the value for the parameter BUFFSIZE musthave specified in your init<SID>.utl file are not correct. not be larger than max_number.User response: Check the management classes on the User response: In the DP for SAP profile, specify aTSM server and specify correct ones. 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 largeBKI1222E Version mismatch error. Check setup buffers you can set option BUFFCOPY to SIMPLE or (version_1:version_2). AUTO. As a consequence, buffers are copied when dataExplanation: Different components with inconsistent is passed between Tivoli Storage Manager components.versions are used.User response: Check your setup or contact DP for | BKI1230E The following file was not processed:SAP support. | path. | Explanation: The operation was terminated due to aBKI1223W A problem occurred during send of | previous error. As a consequence, the file named could performance data to Administration | not be processed. The cause of the error should be Assistant . | found in an earlier message.Explanation: There was a problem sending the | User response: Check for and respond to precedingperformance data to the Administration Assistant over | error messages.the network.User response: Check your setup or contact DP for | BKI1505E Operation aborted because a differentSAP support. | operation by this database client is | already running.BKI1227I Average compression factor was number. | Explanation: Different concurrent operations of the | same type were started for the same database. This isExplanation: The data transferred had been | not supported. The current operation is aborted.compressed by the factor number. | This message is also issued when a cooperativeUser response: None | operation of two or more participating partitions was | started, but the profile settings used for the variousBKI1228W Server server name can not be used with | partitions do not match. password access method GENERATE in | User response: Wait until the currently running this environment. The process is | operation has ended and try again. Make sure that running with user ID number but the | multiple operations are not started concurrently for a effective user ID is number. | database.Explanation: The user ID and the effective user ID of | If this is a cooperative operation with two or morethe process are different. In order to utilize the | participating partitions, check that the profile settingspassword access method GENERATE the IDs must be | of the various partitions (for example, DEVICE_TYPE,equal. | MAX_VERSIONS, etc.) do not differ. If they do, fix theUser response: Change the value for the parameter | profile settings, cancel the current operation, and start″PASSWORDACCESS″ in the file dsm.sys (UNIX and | the operation again. Also, investigate the possibility ofLinux) or servername.opt (Windows) from ’generate’ to | sharing the same profile among all partitions.’prompt’. Reset the password for this node at the TivoliStorage Manager server and run (for Oracle) backint BKI1506E Failed to execute command command.-f password or (for DB2) backom -c password . This Output follows:prompts you for the password and stores it encryptedin the DP for SAP configfile. Each time your password Explanation: The system tried to execute theexpires you have to repeat the last step. 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 Appendix B. Data Protection for SAP (DB2) Messages 135
    • Messagesmessage, and resolve the problem. database client is an instance of the snapshot backup library representing a single partition of the database.BKI1507E The process needs to run with root User response: None. authority.Explanation: The current process requires root BKI1514I *****> Device client connected.authority. Explanation: This message follows a messageUser response: Start the process under an account BKI1511I and indicates the connection of one of thewith root authority. device clients taking part in the operation. A device client is an instance of the device agent for the storage device.BKI1508E The service service_name has terminated due to a previous error. Please check all User response: None. logs for additional information.Explanation: The cited service is no longer available. BKI1515I Client is logging to file_name.User response: Check the appropriate logs for the Explanation: The client’s log messages are written tocause of its termination. the indicated file. User response: None.BKI1509E Authentication failure. The password specified does not qualify for accessing BKI1517I Deleting target data container defined component. by container_description.Explanation: To access the named component, a Explanation: The data in the container indicated ispassword is required. However, the password provided removed.could not be verified. User response: None.User response: Make sure that the password files usedby the different components of the system match. BKI1518E Internal error: The system is trying to use the same device agent, although theBKI1510I New connection received. synchronization mode is notExplanation: The server received a new connection PARALLEL.request. Explanation: The system has been told to use theUser response: None. same device agent for multiple database clients, but the database indicated serial synchronization mode. This setup is not supported.BKI1511I New type_of_operation operation started for database instance instance, database User response: Contact your IBM support personnel. database_name.Explanation: A connection request resulted in the start BKI1519E A failure occurred during initializationof a new operation of the type indicated. of one or more of the nodes participating in this operation. PleaseUser response: None. check the logs for more information. Explanation: Some problem occurred during theBKI1512E An error occurred during shutdown: initialization of a new operation. The problem may be Error information with any component required for this operation.Explanation: During shutdown of the component, a User response: Check the acsd log file for messagesproblem occurred. The error information is given. BKI1515I to determine the log file names of theUser response: Resolve the problem indicated by the participating agents. Check the log files of eacherror information. component for the cause of the problem.BKI1513I *****> Database client connected: BKI1520E Volume volume_name is shared across Instance instance, database database_name, partitions. Volume sharing is not partition partition_number allowed.Explanation: This message follows a message Explanation: At least two partitions own data residingBKI1511I and indicates the connection of one of the on the volume indicated. This setup is not supported.database clients taking part in the operation. A User response: With the current disk layout of the136 Data Protection for SAP Installation and User’s Guide for DB2
    • Messagesdatabase, the requested function cannot be used. If you current version of the wizard.want to use the function, change the disk layout of the User response: Refer to your user documentation for adatabase so that each data volume is dedicated to a list of the device types that are supported by default.partition. Specify one of the supported types.BKI1521I Retaining number backups BKI1530E Failed to launch the device agent forExplanation: When enforcing profile parameter device_type. Please consult your userMAX_VERSIONS, the indicated number of backups is documentation to make sure that allkept. requirements for the specified device are met.User response: None. Explanation: The system was unable to launch the appropriate device agent for the type indicated becauseBKI1522E The requested meta-information some of its requirements are not met. (subject=″description″) is not available. User response: Refer to your user documentation andExplanation: Some meta-information about each make sure that the system is set up correctly for thebackup is stored in the repository. An error occurred specified device type.when trying to retrieve part of this information.User response: Contact your IBM support personnel. BKI1534E Unexpected version actual_version of the repository located in path. ExpectedBKI1523W Warning: The following containers were version: supported_version reused without being explicitly released: Explanation: The server located the repository in the description path indicated. However, the version of the repositoryExplanation: The containers defined by the located on disk does not match the current version ofdescription are used by the current backup. They were the server.used before by a different backup. This message is User response: Make sure to use the correct instanceexpected in SAN environments where data containers of the server. Ensure that the path of the repository wasare usually kept until they are reused. In this case, this specified correctly. Refer to the release notes for a list ofmessage does not indicate a problem. possible incompatibilities.User response: None. BKI1535E Unexpected characteristicsBKI1525E The process service_name is in an (bitwidth=number) of the repository inconsistent state. Please check for located at path. Expected bitwidth: previous errors and restart the process number afterwards. Explanation: The repository located in the pathExplanation: The process indicated cannot continue indicated was saved to disk using a bit width differentwith inconsistent data. from the bit width the server is using to load the repository.User response: Check the logs for messages pointingto the cause of the inconsistency. After resolving any User response: Make sure to use the correct instanceproblems, restart the process. of the server. Ensure that the path of the repository was specified correctly. Refer to the release notes for a list of possible incompatibilities.BKI1526E A configuration file (profile) must be provided. BKI1536E The repository located at path is notExplanation: An operation was started without valid.providing a profile. Explanation: A repository could not be found at theUser response: Check the user documentation on how location indicated by path.to provide the profile to the current process. Start theprocess again using a valid configuration file. User response: Ensure that the path of the repository was specified correctly. Do not edit any files in the repository path.BKI1529E The device ’device_type’ you entered is not supported by the wizard.Explanation: The device type represents a certain typeof storage device. While using the setup wizard, adevice type was entered that is not supported by the Appendix B. Data Protection for SAP (DB2) Messages 137
    • Messages User response: Run the setup with option -a disableBKI1537E The repository located at path was and then start the installation process again. If the written with an incompatible protocol entries in /etc/inittab should be retained, refer to your (protocol_version). Expected protocol: user documentation for information on how to protocol_version complete the installation manually.Explanation: The repository found at the locationindicated was written to disk using the protocol BKI1542E Failed to uninstall because some of theversion named. However, the server currently supports processes to be uninstalled are stillthe expected protocol version. listed in /etc/inittab. Please re-run theUser response: Ensure that the path of the repository setup after stopping the component bywas specified correctly. Do not edit any files in the calling the setup script with option -arepository path. stop. Explanation: Before uninstalling the product, theBKI1538E Unexpected repository type. The path affected processes must be stopped. This is done by ’path’ does not point to a repository of running the setup script with the option ‘-a stop’, type ″protocol_type″. which will remove the entries from /etc/inittab and stop the processes.Explanation: The repository located in the pathindicated was written to disk using a protocol different User response: Refer to your user documentation forfrom the protocol supported by the server process. information on the uninstall process. Run the setup with the option “-a stop” and then continueUser response: Make sure to use the correct instance uninstalling.of the server. Ensure that the path of the repository wasspecified correctly. Refer to the release notes for a list ofpossible incompatibilities. BKI1543E The component is still referenced within the /etc/inittab. In order to terminate the component rerun the setup script withBKI1539E Root privileges required. Could not option ’-a stop’. change user ID to root. Explanation: The setup utility detected that theExplanation: The requested operation requires root product is still active in the system. Apparently, itsprivileges. However, the process could not acquire entries in /etc/inittab are not yet removed.them. User response: Call this process again with the optionUser response: Make sure the appropriate privileges “-f stop”.(s-bit) are granted to the executable. BKI1544E New entries cannot be added toBKI1540E /etc/inittab entries are limited to 127 /etc/inittab because it already contains characters. Please consult your user too many entries starting with ’ac’. documentation for information on Please refer your user documentation for manually completing the installation a manual setup of this package. procedure. Explanation: During setup, an unusually high numberExplanation: The command line generated by the of entries beginning with “ac” were detected insetup function exceeds 127 characters. This situation /etc/inittab. /etc/inittab was not modified.requires user intervention. The setup function did notupdate /etc/inittab. User response: Determine if these entries are expected, or if they were added due to a problem. IfUser response: Refer to your user documentation for these entries are required, refer to your userinformation on what entries to add to /etc/inittab. documentation for information on how to complete the installation manually.BKI1541E /etc/inittab was not updated because some of the processes have apparently BKI1545E IBM Tivoli Storage Manager for already been added. Please re-run the Advanced Copy Services is currently setup after calling the setup script with running. option -a disable if you want to change to a standard setup. Explanation: This failure happens during (de)installation and indicates that not all TSM for ACSExplanation: During the automatic setup, entries for components could be stopped.this product were detected in /etc/inittab. This is anindication that the product was not previously User response: Check that no backup or restore isuninstalled. currently running and retry the operation. If you have customized the process of starting TSM for ACS, it138 Data Protection for SAP Installation and User’s Guide for DB2
    • Messagesmight be necessary to manually stop it by undoing are running. Check their log files for messages pointingthose customization steps. to problems. Resolve any problems indicated.BKI1546E IBM Tivoli Storage Manager for BKI1553I Component_name is logging to path. Advanced Copy Services was not Explanation: The file denoted is the log file of the started. named component.Explanation: This failure happens during installation User response: If you need to check the log of theand indicates that not all TSM for ACS components indicated component, look for this message to identifycould be started successfully. the log file to examine.User response: Check that all TSM for ACScomponents have the appropriate access rights and BKI1554W The agent ’component_name’ terminatedretry the operation. Contact the support function if the with exit code number.operation continues to fail. Explanation: The process denoted ended with the given exit code.BKI1547E Failed to remove the data associated with the deleted backup backup_id. User response: Check the agent’s log for any messages pointing to a problem. Resolve any problemExplanation: The backup named was deleted. indicated.However, its data could not be removed from therepository and from the storage device. BKI1555I Profile successfully created. PerformingUser response: Look for a previous message pointing additional checks. Make sure to restartto the cause of the problem. Resolve any problems all ACS components to reload theindicated there. Once the cause of this problem is profile.resolved, the daemon will take care of the deletedbackups eventually. Explanation: The setup wizard created a new profile. The profile will be validated.BKI1548E Failed to monitor the data associated User response: Restart the ACS components after the with the deleted backup backup_id. wizard ends, in order to activate the new settings.Explanation: A background daemon is supposed tomonitor the states of backups in order to determine if BKI1556E Some data of backup backup_id aredata needs to be deleted from the storage device. unavailable. It is impossible to restoreHowever, the monitor was not able to access the the data requested.appropriate data. Explanation: The system detected that some of theUser response: Look for a previous message pointing data originally contained in the backup is no longerto the cause of the problem. Resolve any problems available. The occurrence of this message depends onindicated there. Once the cause of this problem is the type of storage device employed. For example, if anresolved the daemon will take care of the deleted earlier backup data was restored from an N-Seriesbackups eventually. device, some data of a later backup will be destroyed. User response: The backup is no longer complete andBKI1549E Failed to load component_name due to the cannot be used for the requested operation. Try the following reason: error_information. operation with a different backup.Explanation: The system was unable to load thenamed component of the product. BKI1557I Device agent is logging to path.User response: Check the error information given in Explanation: The device agent’s log messages arethe message. Resolve any problem indicated. written to the file named. User response: None.BKI1550E Unable to perform required operations for container container_id for time_span. BKI2000I Successfully connected toExplanation: For the data container noted, an component_name on port portnumber.operation to be performed by a background daemonhas been pending for the given time. This might Explanation: The backup library initiated a successfulindicate a problem and may result in storage not being connection to the background process component_namereleased for an extended period. on port portnumber.User response: Make sure the background daemons User response: None. Appendix B. Data Protection for SAP (DB2) Messages 139
    • MessagesBKI2001E Socket error while connecting to BKI2014I FRONTEND program finished. component_name: reason. Explanation: The frontend program is finished.Explanation: The background process component_name User response: None.is not running.User response: Start component_name manually and try BKI2015I Starting BACKEND program.again. Explanation: The backend program is executing.BKI2003I File file_name, BID deleted. User response: None.Explanation: The file file_name with the backup IDBID was deleted from the Tivoli Storage Manager. BKI2016I BACKEND program finished.User response: None. Explanation: The backend program is finished. User response: None.BKI2008E Unable to connect to component_name.Explanation: Internal error. BKI2017I Blocksize is set to num_bytes bytes.User response: Contact DP for SAP support. Explanation: The operational blocksize is num_bytes bytes.BKI2009I Deleting all versions with version User response: None. number <= version_number on server server_name. BKI2022E Unable to change mode of file file name:Explanation: All full database backups and their descriptioncorresponding log file backups will be deleted fromTivoli Storage Manager storage, if their version number Explanation: Unable to change mode of file ’file name’.is less than or equal to version_number. ’description’ may contain the system error text.User response: None. User response: Check the ’description’. If the error persists, contact your service representative.BKI2010E Error occurred processing FRONTEND BKI2024E Error in connection to component_name.Explanation: An error occurred during the frontendprocessing. Explanation: The connection to component_name terminated unexpectedly. This message might beUser response: Check the frontend script/program displayed due to previous errors or after an unexpectedand the settings in the DP for SAP profile (keyword termination of the component_name process.FRONTEND) and try again. User response: Check for other error messages and restart component_name if necessary. Try again. If theBKI2011E Error occurred processing BACKEND. problem persists, contact DP for SAP support.Explanation: An error occurred during the backendprocessing. BKI2025E Failed to respond to a message received from component_name.User response: Check the backend script/programand the settings in the DP for SAP profile (keyword Explanation: This is an internal errorBACKEND) and try again. User response: Contact DP for SAP support.BKI2012E Passwords do not match. Try again. BKI2026E Unexpected exception in handler: handlerExplanation: The first and second password youentered do not match. Explanation: This is an internal error.User response: Enter the password correctly. User response: Contact DP for SAP support.BKI2013I Starting FRONTEND Program. BKI2027I Using TSM API version your API version (compiled with compiled with version).Explanation: The frontend program is executing. Explanation: Version information about the TSM-API.User response: None. User response: None140 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI2028W 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 cleanupthat has no effect on the success of the service. Explanation: An error occurs during the restore process of the file file name.User response: None User response: Check the error number error_num and the error description error_desc to avoid this problem inBKI2029E The requested buffer allocator cannot be the future. instantiated due to the following incompatibility: expression. BKI4005E Error allocating memory block for fileExplanation: This is an internal error. file name. BLOCKSIZE may be too large.User response: Contact DP for SAP support. Explanation: Unable to request new memory blocks during the backup of file file name.BKI2031E A buffer allocator cannot User response: Verify that you have set a valid value simultaneously satisfy all of the for BLOCKSIZE. If you are not sure what value is following properties: list of properties valid, comment it out so the default value is used.Explanation: This is an internal error. Furthermore, you can check if you have enough RAM available with your machine. Also, check the memoryUser response: Contact DP for SAP support. usage during backup. It may be necessary to stop another application, increase memory, or change theBKI2033E Cannot instantiate allocator of type configuration. allocator type with the following additional properties: list of properties BKI4007E File filename cannot be read. Reason:Explanation: This is an internal error. errno(errno number) errno text.User response: Contact DP for SAP support. 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 hardwareBKI4000W The attributes of file file name cannot be problems. restored. Reason: errno (error_num) error_desc. User response: Contact your system administrator.Explanation: The file file name was restoredsuccessfully but one or more file attributes (permission, BKI5000E Tivoli Storage Manager Error:ownership, date/time) of the file file name cannot be error_messagerestored correctly. Explanation: During a connection of DP for SAP toUser response: Check the error number error_num and Tivoli Storage Manager server, a Tivoli Storagethe error description error_desc to avoid this problem in Manager error error_message occurred.the future. An initial solution could be to set the User response: Use the Tivoli Storage Managerappropriate correct permission for the file file name Messages guide and correct the Tivoli Storage Managermanually. server error. Try your last action again.BKI4001E File file name cannot be created. Reason: BKI5001E Tivoli Storage Manager Error: errno (error_num) error_desc. error_messageExplanation: The file file name to be restored could not Explanation: During a connection of DP for SAP tobe created/written. It is possible, that you do not have Tivoli Storage Manager server, a Tivoli Storagethe appropriate rights for writing the file file name to Manager error error_message occurred.the destination path. User response: Use the Tivoli Storage ManagerUser response: Check the error number error_num and Messages guide and correct the Tivoli Storage Managerthe error description error_desc to avoid this problem in server error. Try your last action again.the future. Furthermore, check the write permission ofthe user who started the restore. BKI5002E Tivoli Storage Manager Error: error_message Explanation: See BKI5001E. User response: See BKI5001E. Appendix B. Data Protection for SAP (DB2) Messages 141
    • MessagesBKI5003E Tivoli Storage Manager Error: BKI5012E Cannot open TSM API message text file. error_message Check if DSMI_DIR is set correctly. Current value of DSMI_DIR is: valueExplanation: See BKI5001E. Explanation: The TSM-API could not be initialized.User response: See BKI5001E. User response: Correct the value of the environment variable DSMI_DIR.BKI5004W Tivoli Storage Manager Error: error_message BKI5013E Value for name is too long. CurrentExplanation: See BKI5001E. value: valueUser response: See BKI5001E. Explanation: The value of the environment variable name has too many digits.BKI5005E Tivoli Storage Manager Error: User response: Check if the variable is set correctly. error_messageExplanation: See BKI5001E. BKI5014E Tivoli Storage Manager Error:User response: See BKI5001E. error_message Explanation: See BKI5000E.BKI5006E Tivoli Storage Manager Error: User response: See BKI5000E. error_messageExplanation: See BKI5001E. BKI5015W Data description could not be restored,User response: See BKI5001E. because it was backed up with a newer version (objInf=support information)BKI5007E Tivoli Storage Manager Error: Explanation: The TSM server hosts backups (i.e. data error_message description) which were made with a new version of backint or backom, which ignores this data in furtherExplanation: See BKI5001E. processing.User response: See BKI5001E. User response: Upgrade the product.BKI5008E Tivoli Storage Manager Error: BKI5016I Time: current_time New TSM session error_message created: MGMNT-CLASS:Explanation: See BKI5001E. management_class, TSM-Server: server_name, type: session_type.User response: See BKI5001E. Explanation: A new session to TSM server server_name has been established at current_time. Data will be storedBKI5009E Tivoli Storage Manager Error: in management class management_class. error_message User response: None.Explanation: See BKI5000E.User response: See BKI5000E. BKI5017E Internal Tivoli Storage Manager Error: Transaction succeeded although it wasBKI5010E Tivoli Storage Manager Error: expected to fail. error_message Explanation: An internal Tivoli Storage Manager errorExplanation: See BKI5000E. occurred.User response: See BKI5000E. User response: Retry the action. If the error occurs again contact DP for SAP support.BKI5011E Tivoli Storage Manager Error: error_message BKI5018E The requested buffer has a size (current_size bytes) that is smaller thanExplanation: See BKI5000E. requested requested_size.User response: See BKI5000E. Explanation: The request for a new buffer returned successful. The buffer, however, has not the requested size.142 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesUser response: Check if the system is running low on BKI7058E Service open failed because more thanmemory and retry the action. If the error occurs again one file was found with the same name.contact DP for SAP support. Explanation: The command could not be started because two or more files with the same name wereBKI7048I The default port to connect to found. server_name will be used. User response: Check the product log file for furtherExplanation: A server port for the connection to the detailed messages.named server was not explicitly specified. Therefore,the default port is used. BKI7059E Service open failed because a file wasUser response: Make sure the named server is not found.listening to the default port. In the case of connectionfailures, specify the server port in the profile. Explanation: The command could not be started because a file specified was not found.BKI7049I The default ProLE port will be used. User response: Check the product log file for further detailed messages.Explanation: The port for the internal communicationof DP for SAP is set during installation. The messageindicates that this port is being used. BKI8300I Function_name returned with code return_information.User response: None. Explanation: This message indicates that the named API function ended with the specified returnBKI7051E The environment variable information. XINT_PROFILE is not set. It must be set and contain the fully qualified path to User response: If the return information indicates a the *.utl file to be used. problem, look for preceding error messages in the log files. Otherwise, no response is required.Explanation: The way DP for SAP works is specifiedin a profile. When called, DP for SAP looks for theenvironment variable XINT_PROFILE which must BKI8301E Product_name: Exception caught incontain the fully qualified path to the profile. function function_name. Error information: ’error_information’User response: Check the environment forXINT_PROFILE of the user who started DP for SAP. Explanation: The named product implementing the DB2 Advanced Copy Services API received an error in the named API function. The error information isBKI7053E Service setup failed due to previous shown. error. User response: Analyze the error information to findExplanation: Initialization of the product failed due to the cause of the problem. Resolve any problemsprevious errors. indicated.User response: Check the product log file for furtherdetailed messages. BKI8302E Product_name: Exception caught in function function_name. MoreBKI7055E Service open failed due to previous information may be available in file error in data mover. log_file_name. Error information: ’ error_information’’Explanation: The command could not be started dueto previous errors. Explanation: The named product implementing the DB2 Advanced Copy Services API received an error inUser response: Check the product log file for further the named API function. The error information isdetailed messages. shown. User response: Analyze the error information and theBKI7056E Service open failed because configured appropriate log files to find the cause of the problem. TSM server could not be accessed. Resolve any problems indicated.Explanation: The command could not be startedbecause the TSM server defined in the profile could notbe accessed.User response: Check the product log file for furtherdetailed messages. Appendix B. Data Protection for SAP (DB2) Messages 143
    • MessagesBKI8305E Invalid option option in options string: BKI8312E Error while parsing parameter keyword. ’options_string’. In order for ’value1’ to be valid ’value2’ is required to be an existing directory.Explanation: An invalid option was found whileparsing the options string specified in the db2 Explanation: Value1 was found to be an invalid valuecommand. for the parameter named. For this specific parameter, a file name can be specified whose path must alreadyUser response: Correct the command and try again. exist in the system. User response: Specify the name of a file in anBKI8306E The keyword keyword is not allowed existing path. multiple times within the profile.Explanation: The keyword indicated was found more BKI8313E Product_name: DB2 - TSM interfacethan once in the profile. However, this keyword must problem in function function_name:not be specified multiple times. Invalid value of parameter: valueUser response: Correct the profile. Explanation: The named product implementing the DB2 Advanced Copy Services API detected an interfaceBKI8307E The parameter keyword must be specified problem in the named API function. An invalid value in the profile. was found in one of the API data structures.Explanation: A required keyword is missing in the User response: Contact your IBM support personnel.profile.User response: Correct the profile. BKI8314E Product_name: DB2 - TSM interface problem in function function_name: The session is already in use by a differentBKI8308E Single argument required for parameter operation. keyword. Explanation: The named product implementing theExplanation: The keyword indicated requires a single DB2 Advanced Copy Services API detected an interfacevalue. However, two or more values are found in the problem in the named API function. Either the sessionprofile. handle is used for various operations simultaneously,User response: Correct the profile. or the functions are called in an order not supported by the current version of the library.BKI8309E Missing argument for parameter User response: Contact your IBM support personnel. keyword.Explanation: In the profile, a value is missing for the BKI8315E Function_name: The following object isnamed parameter. not under the control of product_name: pathUser response: Correct the profile. Explanation: The named product implementing the DB2 Advanced Copy Services API detected a problemBKI8310E The keyword keyword is not allowed. in the named API function: The path passed by theExplanation: An invalid keyword was detected in the database is not under the control of the product.profile. User response: Make sure the database to be backedUser response: Correct the profile. up meets the requirements for employing snapshot backups.BKI8311E For parameter keyword, both server and port must be specified. BKI8316E Product_name: DB2 - TSM interface problem in function function_name:Explanation: A value of the named parameter is Empty group list passed by DB2.missing from the profile. Explanation: The named product implementing theUser response: As the value for the specified DB2 Advanced Copy Services API detected an interfaceparameter, specify both server and port. problem in the named API function: The database passed a group list containing no elements. User response: Contact your IBM support personnel.144 Data Protection for SAP Installation and User’s Guide for DB2
    • Messages User response: None.BKI8317W Product_name: Verification of configuration requested by user. No backup started. BKI8322E Interface problem: Current database partition number not listed in theExplanation: The user requested a verification of the partition list.configuration. The backup flow continued withouterrors up to the point where the snapshot would Explanation: The partition list passed by the databaseactually be done and was then cancelled. The system is does not contain the named partition participating inready for a snapshot backup, but no action beyond an operation.verification has been taken so far. User response: Contact your IBM support personnel.User response: None. BKI8323E Product_name: Problem occurred whileBKI8318E Product_name: DB2 - TSM interface processing function_name. Please check problem in function function_name: Not log file log_file_name for more enough space provided to write meta information. Error information: data. ’error_information’Explanation: The named product implementing the Explanation: The named product implementing theDB2 Advanced Copy Services API detected an interface DB2 Advanced Copy Services API received an error inproblem in the named API function: The buffer the named API function. The error information isprovided by the database is too small to contain the shown.requested meta data. User response: Analyze the error information and theUser response: Contact your IBM support personnel. appropriate log files to find the cause of the problem. Resolve any problems indicated.BKI8319W Error while deleting old versions. This problem does not affect the new BKI8324E Product_name: Problem occurred while backup. Error information: processing function_name: Device agent ’error_information’ returned code return_information.Explanation: After a successful backup, the system Explanation: The named product implementing thetries to remove older backups of the database according DB2 Advanced Copy Services API received an errorto the value of profile parameter MAX_VERSIONS. from the device agent in the named API function. TheHowever, a problem occurred while trying to remove device agent’s return information is given.expired backups. The new backup is not affected bythis problem. User response: Check the appropriate log files to find the cause of the problem. Resolve any problemsUser response: Check the appropriate log files in indicated.order to determine the cause of the problem. Resolveany problems indicated. In case the storage device runsout of storage because outdated snapshot backups have BKI8325E Failed to determine hostname.not been removed, delete these snapshot backups Explanation: The system was not able to determinemanually. the host name of the machine. User response: Make sure the system setup allows forBKI8320I Deleting full backup backup_id – querying the hostname via system function backup_key. gethostname(). Ensure that the requirements for doingExplanation: After a successful backup, the system snapshot backups are met.tries to remove older backups of the database accordingto the value of profile parameter MAX_VERSIONS. BKI8326E Failed to create log directory path.During this process, the full backup listed is removed. Explanation: The log path indicated is not available inUser response: None. the system and could also not be created. User response: Check the properties of the pathBKI8321I Deleting partial backup backup_id for indicated and make sure that its properties and the node:host:partition_number. properties of the parent directory are set accordingly.Explanation: After a successful backup, the system Make sure all prerequisites for doing snapshot backupstries to remove older backups of the database according are met.to the value of profile parameter MAX_VERSIONS.During this process, the backup listed for the namedpartition is removed. Appendix B. Data Protection for SAP (DB2) Messages 145
    • MessagesBKI8327E Invalid value specified for parameter BKI8334E Profile section section_name is required keyword: value for function operation.Explanation: A parameter value is not valid. Explanation: The specified profile section is required in order to perform the requested operation. However,User response: Correct the profile or the call as it is not included in the profile.appropriate. User response: Correct the profile.BKI8328E Product_name must be licensed to set parameter keyword to a value of value. BKI8335E Profile section section_name refers to a value for keyword that differs from theExplanation: Selected functions are supported only one used at backup time. Expectedwith a full TSM license. value: value.User response: Correct the profile or the call as Explanation: The profile parameter named must notappropriate. If you need the functionality requested, change its value between backup and restore. However,obtain a full TSM license and install the license file. in the named profile section, the parameter has a value different from the value it had at backup time. ThisBKI8330E Parameter keyword requires ’YES’, ’NO’, value is given in the message. or number. User response: Correct the profile by setting theExplanation: For the named parameter, only numeric indicated parameter to the value indicated in thevalues, “YES”, and “NO” are accepted. message.User response: Correct the profile or the call asappropriate. BKI8336E Invalid value specified for option keyword:valueBKI8331E The parameter keyword1 is not allowed if Explanation: An option value is not valid. keyword2 is set to value. User response: Correct the call.Explanation: There is a dependency betweenparameters keyword1 and keyword2. If the latter is set to BKI8337E Error while parsing profile: Missingthe value named, keyword1 must not be specified. section name.User response: Correct the profile or the call as Explanation: The profile is organized into namedappropriate. sections. However, a section name was not found. User response: Check that the profile name isBKI8332E Failed to parse parameter keyword. File specified correctly or that the default profile is a valid names in the profile need to be fully profile. Refer to your user documentation for the syntax qualified. of the profile or use the profile wizard to create a newExplanation: As the value of the parameter indicated, profile.a fully qualified file name is expected. However, thespecified value is not a fully qualified path. BKI8338E Error while parsing profile: SectionUser response: Correct the profile or the call as section_name is not allowed to be nested.appropriate. Explanation: In the profile, the named section starts before the previous section ends. However, the sectionBKI8333E In order to enable the parameter in question cannot be nested. keyword1 you need to set keyword2 to User response: Correct the profile. value.Explanation: There is a dependency between BKI8339E Error while parsing profile: Profileparameters keyword1 and keyword2. If keyword1 is section section_name is not valid.specified, keyword2 must be given the specific valueindicated in the message. Explanation: An invalid section name was found in the profile.User response: Correct the profile or the call asappropriate. User response: Correct the profile.146 Data Protection for SAP Installation and User’s Guide for DB2
    • Messages User response: None.BKI8340E Error while parsing profile: Profile section section_name must not be specified more than once. BKI8511I The command is: command name.Explanation: In the profile, only a single section with Explanation: This is an information message echoingthe name indicated can be specified. However, during the command.parsing, a second occurrence was detected. User response: None.User response: Correct the profile. 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.Explanation: The required profile section indicatedwas not found in the profile. Valid return codes: 0 The requested action was performedUser response: Correct the profile. successfully. 1 The requested action was performed successfully; however, some warnings wereBKI8343W The parameter keyword1 of keyword2 issued. value2 has changed its value from value1 2 or greater to value3. The requested action could not be performedExplanation: The profile parameter named must not due to errors. In this case, an error messagechange its value between backup and restore. However, should be logged, too.in the named profile section, the parameter has a new User response: None if the return code is 0.value value3 different from the value value1 it had atbackup time. Both values are given in the message. If the return code is greater than 0, analyze the error and/or warning messages. Resolve errors beforeUser response: Check the log file for problems that starting the action again.may result from the change of parameter values. If so,you may want to change the profile, restoringparameter keyword1 to the value it had when creating BKI8513I ’TDP_DIR’ is not set. The temporarythe backup in order to perform a specific operation. path will be used Explanation: The variable TDP_DIR is not set in theBKI8344E Path path is listed more than once for user environment. All run logs will be written to the partitioning. machines temporary directory instead.Explanation: This is a DB2 - TSM interface problem. User response: Define the environment variable TDP_DIR .User response: Contact your IBM support personnel. BKI8514W ’TDP_DIR’ is not set correctly. TheBKI8345E Error while parsing parameter keyword. temporary path will be used. ’path’ is required to be type_information. Explanation: The variable TDP_DIR is set but containsExplanation: A path of the type indicated in the an invalid path. All run logs will be written to themessage is expected as a value of the named parameter. machines temporary directory instead.However, the specified path was not found to be of thecorrect type. User response: Check and reset the environment variable TDP_DIR.User response: Correct the profile or the call asappropriate. BKI8520E No command was specified.BKI8349I Deleting incomplete backup backup_id– Explanation: backom was called without a command. backup_key . User response: Check the command syntax andExplanation: After a successful backup, the system correct the call.tries to remove older backups of the database accordingto the value of profile parameter MAX_VERSIONS.During this process, the incomplete backup listed is BKI8521E Command option command optionremoved. A backup becomes incomplete when parts of requires an argument.its data expire. This can happen when a backup that is Explanation: A command option requiring anmarked “destructively restorable” is restored. argument was specified without an argument. Appendix B. Data Protection for SAP (DB2) Messages 147
    • MessagesUser response: Check the command syntax and v mm is the month, specified as two digits, withcorrect the call. leading zero for the months January to September, v dd is the day of the month, specified as two digits,BKI8522E Invalid command command. with leading zero for days 1 to 9, v hh is the hour of the day, 00 to 23, with leading zeroExplanation: backom was called with an invalid for hours 0 to 9,command. v mm is the minutes of the hour, 00 to 59, withUser response: Check the command syntax and leading zero for minutes 0 to 9,correct the call. v ss is the second of the minute, 00, to 59, with leading zero for seconds 0 to 9.BKI8523E Error during action. Any digits can be replaced by wildcards ’*’ or ’?’,Explanation: An error occurred while performing the wherenamed action. v * means any number of any digits,User response: Look for other error messages in order v ? means exactly one digit of any value.to analyze the problem. User response: Correct the timestamp.BKI8524E Tablespace online restore is not allowed. BKI8529E Invalid log sequence number. Specify itExplanation: Either the database setup or the kind of in the format log sequence format.backup prevents an online tablespace backup. Explanation: The information on the log sequenceUser response: If you need to do a tablespace restore number(s) does not comply with the expected format.it must be done offline. Accepted log sequence numbers are for example ’123’ or ’S0000123.LOG’.BKI8525E The DB2 instance name can consist of at User response: Correct the log sequence number(s). most 8 characters.Explanation: The name given for the DB2 instance BKI8530E Profile file name does not exist or cannotdoes not comply with the DB2 naming conventions. be accessed.User response: Correct the DB2 instance name. Explanation: Either an existing file could not be opened, or a file could not be created.BKI8526E The DB2 database alias can consist of at User response: Check the attributes of the file and/or most 8 characters. its directory. For backup processing, read access isExplanation: The name given for the DB2 alias does required for the files to be backed up. For restorenot comply with the DB2 naming conventions. processing, write access is required for the target location of the files to be restored.User response: Correct the DB2 alias name. BKI8531E Directory file path does not exist orBKI8527E Invalid node. Specify it in the format cannot be accessed. node format. Explanation: A file path cannot be accessed.Explanation: The name given for the DB2 node doesnot comply with the DB2 naming conventions. Node User response: Check the attributes of the file and/ornumbers must be specified in the displayed format, for its directory. For backup processing, read access isexample ’NODE0000’ or ’0000’. required for the files to be backed up. For restore processing, write access is required for the targetUser response: Correct the DB2 node number. location of the files to be restored.BKI8528E Invalid timestamp. It must consist of 14 BKI8532E Invalid log chain number. Specify it in digits with format yyyymmddhhmmss the format log chain format. or digits and wildcards * or ?. Explanation: The information on the log chainExplanation: Specify digits in the format number(s) does not comply with the expected format.’yyyymmddhhmmss’ or mixed with wildcards ’*’ or ’?’. Accepted log chain number(s) are for example ’123’ orwhere: ’C0000123’. file pathv yyyy is the year, specified as four digits, User response: Correct the log chain number(s).148 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI8533E A timestamp range is not allowed for BKI8540I Using component_name at host name:port the command command . number.Explanation: A timestamp range is not allowed for Explanation: The component_name service named iscommand restore database, restore used for the current action.tabelspace, restore tablespace online and restore User response: None.DB2 history file. Only a single timestamp argumentcan be used. BKI8541I Using profile profile path.User response: Correct the timestamp commandoption. Explanation: The profile named is used for the current action.BKI8534E Command option command option is User response: None. missing.Explanation: A command was issued without BKI8542E Profile profile path cannot be read.specifying a required command option. Explanation: The Backup Object Manager tried to useUser response: Check the command syntax and the profile named but the profile was not available orcorrect the call. 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’.BKI8535E Invalid output mode. Specify one of the keywords keyword list. User response: Make sure that the profile is available at the location specified in option ’-e’ on the commandExplanation: Only the listed keyword values are line or in environment variable ’XINT_PROFILE’.allowed with the output mode command option -m. Check the attributes of the profile and theUser response: Correct the output mode command corresponding directory and make sure that the file canoption. be accessed.BKI8536E Wildcard characters are not allowed for BKI8543I Querying TSM for file(s) file list. command command. Explanation: The Backup Object Manager checks if theExplanation: For the BackOM commands ’restore files listed are available on the TSM server(s) specifieddatabase’, ’restore tablespace’, ’restore tablespace in the corresponding profile.online’ and ’restore DB2 history file’ it’s not allowed tospecify the wildcard characters ’*’ and ’?’ in a User response: None.timestamp command option.User response: Correct the timestamp command BKI8545I No image type image(s) found.option. Explanation: A request could not be satisfied because the files to be processed are not available on the TSMBKI8537E The path path is not absolute. server.Explanation: A command line argument requires a User response: Check if the file(s) were specifiedfully qualified path which was not given. correctly in the request.User response: Specify the fully qualified path. BKI8546E Environment variable environment variable is not set or not set correctly.BKI8538E The TDI file name cannot be processed. Explanation: A required environment variable is notExplanation: The TDI file could not be parsed because set at all or has a value that is not allowed.of errors. There are more specific parser error messagesbefore this message occurs. User response: Check the documentation for the appropriate values of the environment variable namedUser response: Check for and respond to preceding and set its value accordingly.error messages in the Backup Object Manager log. BKI8548I Elapsed time: time value. Explanation: After restore and delete, the time elapsed during the action is displayed. User response: None. Appendix B. Data Protection for SAP (DB2) Messages 149
    • MessagesBKI8549E Unable to create file file name. BKI8557E The config file file name could not be created.Explanation: During restore, the file to be restoredcannot be created in the target location. Explanation: DP for SAP tries to create the configuration file named if it is not present at theUser response: Check if there is sufficient space location specified by the DP for SAP profile keywordavailable for the file to be restored. CONFIG_FILE. However, the file cannot be created.Check the attributes of the target directory; write access This may either be caused by an incorrect pathis required. specified by keyword CONFIG_FILE, or the user may not have the appropriate permissions for creating theIf the target file already exists, check that write access file.is granted User response: Make sure the path specified by keyword CONFIG_FILE is correct and the permissionsBKI8550W Environment variable environment are set appropriately. variable for output mode has wrong value. Using default. BKI8558I Setting TSM password for partitionExplanation: The default output mode can be partition number on host host name.overridden by the named environment variable.Accepted values are ″short″, ″normal″, or ″detailed″. Explanation: The DP for SAP TSM password is set onThe system default is ″short″ for actions on DB2 log the host named for the DB2 partition indicated.files, ″normal″ otherwise. User response: None.User response: Specify an appropriate value for theenvironment variable named, or remove the BKI8559W For partition partition number switch toenvironment variable. host host name and issue the command again.BKI8551E Not all data written to file path. Explanation: When verifying the TSM password, theExplanation: Restoring raw or DB2 log file data ended DP for SAP configuration file is modified.before all data retrieved from TSM could be written to If the DP for SAP profile keyword CONFIG_FILEthe file named. points to an NFS mounted (UNIX or Linux) or a sharedThe file is incomplete. (Windows) path accessible to all hosts in a DB2 ESE (EEE) environment, for example the instance home, allUser response: Make sure there is sufficient space for configuration files of the various partitions can bethe data to be restored. modified simultaneously. If, in contrast, keyword CONFIG_FILE points to a local path, only theBKI8552E File file path could not be closed. configuration files of the local partitions can be modified. In this case, the password verification needsExplanation: After restoring raw or DB2 log file data, to be done from each host. The message indicates thethe target file could not be closed. partitions whose associated configuration files are notUser response: Retry the action. 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 hostsBKI8555E Variable ’DB2DBDFT’ or command hosting a partition of the database. option ’alias’ is required. User response: Make sure to verify the TSMExplanation: The password command needs the password(s) for all partitions of the database.name/alias of the database, for which the DP for SAPconfiguration file has to be adapted. BKI8560E Partition partition number not found inUser response: Either set the environment variable the database configuration.DB2DBDFT or provide the command option ’alias’ withthe password command and try again. Explanation: The DB2 partition specified could not be found in the database configuration.BKI8556E Unable to get hostname. User response: Check the configuration of the DB2 ESE(EEE) environment (db2nodes.cfg, environmentExplanation: The machines hostname could not be variable DB2NODE) and try again.determined.User response: Check the TCP/IP configuration of themachine.150 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI8561W Database ’alias’ not listed in the system BKI8589E Query command failed due to an error. database directory. Explanation: The query command failed duringExplanation: The database ’alias’ does not exist. execution. Not all queried objects can be displayed.Because there is a dependency between the alias and User response: Check for and respond to precedingthe settings for DP for SAP there might be problems error messages in the Backup Object Manager log. Induring database backup or restore runs. Nevertheless, the absence of preceding error messages, contact DP forthe DP for SAP configuration file (init<alias>.utl) will SAP support.be created and adapted.User response: Check if the alias specified does match BKI8610I Restoring type ...to an entry in the DB2 system database directory.Further, check the argument for the DP for SAP profile Explanation: The restore of type has started.keyword CONFIG_FILE and if necessary adapt itappropriately. User response: None.BKI8584I Delete command completed successfully. BKI8612I Continuing restore ...Explanation: The object(s) specified with the delete Explanation: The database restore continues.command were successfully deleted from the TSM User response: None.server.User response: None. BKI8613E Terminating restore ... Explanation: An error occurred, and the databaseBKI8585W Delete command completed successfully, restore terminates. but had warning(s). User response: Check for and respond to precedingExplanation: The object(s) specified with the delete error messages in the Backup Object Manager and thecommand were deleted with warning(s) from the TSM shared library run logs. Additional information may beserver. found in the DB2 diagnostic log (db2diag.log).User response: Check the Backup Object Manager logfile for further detailed messages and if required, do BKI8615I Restore command completedthe requested interventions manually. successfully. Explanation: The object(s) specified with the restoreBKI8586I Delete command was aborted. command were successfully restored from the TSMExplanation: The delete command was aborted by the server.user. No object(s) were deleted from the TSM server. User response: None.User response: None BKI8616W Restore command completedBKI8587E Delete command failed due to an error. successfully. Warning(s) encountered.Explanation: The delete command failed during Explanation: The object(s) specified with the restoreexecution. Not all objects were deleted from the TSM command were restored with warning(s) from the TSMserver. server.User response: Check the Backup Object Manager log User response: Check the Backup Object Manager logfile for further detailed messages and try to resolve the file for further detailed messages and if required, doerror which led to the delete failure. Retry the action. If the requested interventions manually.the error still exists, contact the DP for SAP support. BKI8617I Restore command was aborted.BKI8588E Delete command has not been started or Explanation: The restore command was aborted by no delete result information is available. the user. No object(s) were restored from the TSMExplanation: This message indicates that an operation server.did not complete successfully. Typically, some other User response: None.error condition was detected before.User response: Contact the DP for SAP support. Appendix B. Data Protection for SAP (DB2) Messages 151
    • Messages image was generated and stored to TSM, too.BKI8618E Restore command failed due to an error. User response: None.Explanation: The restore command failed duringexecution. Not all objects were restored from the TSMserver. BKI8632W Backup command completed successfully. Warning(s) encountered.User response: Check the Backup Object Manager logfile for further detailed messages and try to resolve the Explanation: The backup operation completederror which led to the restore failure. Retry the action. successfully; the backup image can be used forIf the error still exists, contact the DP for SAP support. restoring. However, some problems occurred. User response: Check the warning messages and takeBKI8619E Restore command has not been started corrective actions if necessary. or no restore result information is available. BKI8633I Backup command was aborted.Explanation: This message indicates that an operationdid not complete successfully. Typically, some other Explanation: The backup operation was cancelled byerror condition was detected before. user interaction. No backup image was created.User response: Check for and respond to preceding User response: None.error messages in the Backup Object Manager log. BKI8634E Backup command failed due to an error.BKI8621I Restoring file file name... Explanation: No backup was made due to previousExplanation: The system started restoring the file errors.indicated. User response: Check for and respond to precedingUser response: None. error messages in the Backup Object Manager log.BKI8622I Deleting type ... BKI8635E The command option option must be a floating point number.Explanation: The deletion of type has started. Explanation: An invalid argument was specified forUser response: None. command option option. User response: Correct the command syntax.BKI8623I Deleting file file name ...Explanation: The system started deleting the file BKI8636E The command option option must be oneindicated. of values.User response: None. Explanation: An invalid argument was specified for command option option.BKI8626W The TDI file name could not be deleted. User response: Correct the command syntax.Explanation: The system tried to remove the TDIimage from TSM, but did not succeed. BKI8637I Type online/offline backup of alias started ...User response: Try to remove the image manuallyusing the Backup Object Manager raw delete facility. Explanation: A backup operation of database alias of type type has started.BKI8630E The command option option must be a User response: None. number.Explanation: An invalid argument was specified for BKI8638I Type online/offline backup of tablespace(s)command option option. tablespace#1,...,tablespace#n of alias started ...User response: Correct the command syntax. Explanation: A backup operation of tablespace(s) tablespace#1 ... tablespace#n of database alias of type typeBKI8631I Backup command completed was started. successfully. User response: None.Explanation: The backup operation completedsuccessfully; the backup image can be used forrestoring. In the case of a full database backup, the TDI152 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI8639I Including log files in backup image ... BKI8652I Detected DB2 version version with number bits.Explanation: The DB2 log files are stored as part ofthe backup image. Explanation: The indicated DB2 version was detected by Backup Object Manager.User response: None. User response: NoneBKI8640I Using number buffers with a size of size ... BKI8653I Using autonomic buffer size and number of buffers ...Explanation: For backup or restore operations, theindicated number of buffers of the size displayed are Explanation: The buffer size and the number ofused. buffers used for backup or restore is automatically determined by DB2.User response: None. User response: NoneBKI8641I Using number session(s) ... BKI8654I Using an autonomic buffer size withExplanation: For backup or restore operations, the number buffers ...indicated number of TSM sessions is used. Explanation: The buffer size used for backup andUser response: None. restore is automatically determined by DB2. The number of buffers to be used was specified in the callBKI8642I Using a degree of parallelism of number to the Backup Object Manager. ... User response: None.Explanation: For backup or restore operations, thedegree of parallelism is displayed. BKI8655I Using an autonomic number of buffersUser response: None. with a size of size ... Explanation: The number of buffers to be used forBKI8643I Using vendor library at lib path ... backup and restore are determined by DB2. The buffer size to be used was specified in the call to the BackupExplanation: For backup or restore operations, the Object Manager.named vendor library is used. User response: None.None. BKI8656I Using an autonomic degree ofBKI8644W Offline backups cannot include log parallelism... files. The option -L is being ignored. Explanation: The number of DB2 processes (UNIX orExplanation: An offline backup operation was started, Linux) or threads (Windows) used for reading orrequesting the DB2 log files to be included. This is not writing data from/to tablespace containers duringpossible with an offline backup. The backup is done backup and restore is determined by DB2.without including DB2 log files. User response: None.User response: Make sure to backup DB2 log filesseparately. BKI8657W Number is not a valid partition number. Assuming partition 0.BKI8651W Your version of DB2 does not support including log files. The option -L is Explanation: The partition number specified in the being ignored. call to Backup Object Manager does not denote a valid partition of the database. Therefore, the defaultExplanation: A backup was started, requesting the partition 0 will be used by DB2 and by Backup ObjectDB2 log files to be included, but your version of DB2 Manager.does not support this feature. For including DB2 logfiles in the backup image, DB2 V.8.2 or later is required. User response: If your database is not partitioned do not specify the partition number for further actions.User response: Make sure to backup DB2 log filesseparately. Appendix B. Data Protection for SAP (DB2) Messages 153
    • Messages for restoring to a different location. Restoring to aBKI8658E Number is not a partition number of the different location is not supported with device database or does not denote a partition containers. on this host. User response: None.Explanation: The partition number specified does notdenote a valid database partition or is not the partitionlocated on the system where Backup Object Manager is BKI8664E Connecting to alias using CLI failed. Thecalled. Backup Object Manager can only operate on return code was return code.partitions residing on the same host. Explanation: The system tried to connect to theUser response: Either change number to a partition database named via the CLI. The operation did notnumber of a local partition, or start Backup Object succeed and returned the error code indicated.Manager from the same host where the partitionresides. User response: Ensure that your database is enabled to accept CLI connections.BKI8659I Creating tablespace definition information ... BKI8665I The backup timestamp is: timestamp.Explanation: The tablespace definition information Explanation: The DB2 backup finished successfully(TDI) is being created in memory. with the timestamp timestamp.User response: None. User response: None.BKI8660I Saving tablespace definition BKI8666I Redirecting tablespace tablespace with ID information ... id.Explanation: The tablespace definition information Explanation: The named tablespace is restored to the(TDI) is being stored on the TSM server. location requested.User response: None. User response: None.BKI8661W Could not create TDI. The backup BKI8667I Tablespace tablespace with ID id was not cannot be used for redirected restore redirected because its container on the with BackOM. source system SID is not located in a path starting with path .Explanation: The system could not collect thetablespace definition information. The backup was Explanation: The named tablespace of type SMS is notmade without TDI. As a result, the backup can be used redirected because the definition of the tablespacefor restoring the system, but it cannot be used for container in the source system does not match therestoring to a different location. database characteristics that Backup Object Manager expects and that are cited in the message. Therefore,User response: Ensure that your database is enabled Backup Object Manager tries to restore the tablespaceto accept CLI connections. to a location identical to the location in the original system.BKI8662W Could not save TDI. The backup cannot User response: Make sure that the tablespace be used for redirected restore with mentioned can be restored to the original location. This BackOM. includes that the user initiating the redirected restore has the appropriate permissions for placing theExplanation: The system could not save the TDI on tablespace container in this location and that theTSM. The backup was made without TDI. As a result, tablespace can be restored without overwriting otherthe backup can be used for restoring the system, but it data.cannot be used for restoring to a different location. In order to avoid this situation in the future, theUser response: Check for and respond to preceding administrator of the source system may want toerror messages in the Backup Object Manager log. recreate the tablespace according to the database characteristics Backup Object Manager expects.BKI8663W The TDI contains device containers. The backup cannot be used for redirected restore with BackOM.Explanation: A backup of a database using devicecontainers was requested. The backup was successful, itcan be used to restore the system, but it cannot be used154 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI8690E Free space test for container path failed. BKI8702E Too many errors. Bailing out. Only free bytes MB free space left but Explanation: The TDI parser encountered a number of required bytes MB required. errors. Restoring is stopped.Explanation: The system requires a tablespace User response: Check for and respond to precedingcontainer of the size indicated at the path named, but error messages in the Backup Object Manager log.there is not sufficient free space available to create it.User response: Try to make available the free space BKI8703E Out of memory.required, for example by1. Removing some files on the volume or file system Explanation: The TDI parser encountered a token that the container shall reside on. cannot be read into the main memory. The TDI image cannot be processed, and restoring is stopped.2. Increasing the size of the file system the container shall reside on. User response: Contact DP for SAP support.3. Shrinking the size of the container requested so that it fits in the free space. BKI8704E Error while reading input file.Note: Backup Object Manager assumes that a small Explanation: The TDI parser tried to read more datapart (0.05%) of the free space will be required by the from disk or from TSM, but did not succeed.operating system for administrative use. As aconsequence, only 99.95% of the free space on the User response: Ensure that the TDI image to bevolume or file system is actually available. processed exists at the expected location and that the system has sufficient privileges to read it.BKI8692E The requested data could not be retrieved. BKI8705E error in line line number.Explanation: The TDI data of a backup image could Explanation: The TDI parser encountered a syntaxnot be retrieved and displayed. error in the line indicated. As a consequence, the TDI image cannot be analyzed.User response: Look for and respond to precedingerror messages. User response: Respond to the error message and correct your TDI image.BKI8693E More than one TDI file matches your query. BKI8706E The container at path is inappropriate for tablespace tablespace.Explanation: More than one TDI file matching thesearch criteria was found on TSM. Explanation: The container at the location indicated cannot be added to the tablespace named because ofUser response: Specify additional BackOM command incompatible properties.options to restrict the result set. User response: Check the properties of the container and the tablespace. Ensure that the IDs of theBKI8700E Internal parser error in TDI parser. containers are unique for the tablespace named.Explanation: An unexpected error occurred in the TDIparser. BKI8707E Missing statement keyword in block blockUser response: Contact DP for SAP support. name near line line number. Explanation: A keyword is missing in the namedBKI8701E This parser cannot process TDI version block ending at the line given. version. User response: Insert the required statement in theExplanation: The current version of Backup Object block.Manager is not compatible with the version the TDIimage was created with. As a consequence, the TDI BKI8708E The [TDI] header block must be thedata cannot be processed. first block.User response: Check the release notes for the Explanation: The TDI image does not start with theappropriate migration procedure. 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. Appendix B. Data Protection for SAP (DB2) Messages 155
    • MessagesBKI8709E The required block block name is BKI8734E The TDI used for redirected restore missing. contains an invalid partition number.Explanation: The named block is missing in your TDI Explanation: There is an invalid partition numberimage. specified in the Node statement of the TDI image.User response: Insert the missing block using valid User response: Provide a valid partition number.values. BKI8736E Tablespace tablespace must have at leastBKI8710W Duplicate block block name ignored at one container. line line number. Explanation: The TDI image defines the tablespaceExplanation: At the line indicated, a block begins named without containers.whose name was encountered before. The system User response: Ensure that there is at least oneignores the duplicate block; it uses the data from the container associated with every tablespace.first occurrence of duplicate blocks.User response: Make sure that block names are BKI8737E Tablespace tablespace has containers withunique within a TDI image. the combined storage too small. Explanation: The number of used pages of theBKI8711W Duplicate statement keyword ignored in tablespace named exceeds the combined size of its line line number. tablespace containers defined in the TDI image.Explanation: At the line indicated, a duplicate User response: Ensure that every tablespace hasstatement was encountered within a block. The system containers of a combined size that is sufficient to holdignores the duplicate statement. the used pages of the tablespace.User response: Make sure to not specify duplicatestatements within a block. BKI8738E The container at path has a page size that is incompatible with its tablespace.BKI8730I Scaling tablespace containers to number Explanation: The container indicated does not have percent ... the same page size as its tablespace according to theExplanation: All tablespace containers will be definitions in the TDI image.increased by the percentage indicated during the User response: Contact DP for SAP supporttablespace container redefinition step.User response: None. BKI8739E The type of the container at path is incompatible with its tablespace.BKI8731I Normalizing tablespace containers ... Explanation: The container indicated cannot be usedExplanation: All containers of a tablespace will be of with its associated tablespace according to thethe same size after redefinition. definitions in the TDI image. SMS tablespaces can only have path containers, and DMS tablespaces must haveUser response: None. file or device containers. User response: Ensure that the appropriate types ofBKI8732E The TDI used for redirected restore containers are used with each tablespace contains an invalid database alias.Explanation: There is an invalid database alias BKI8740E The path path of a container must not bespecified in the alias statement of the TDI image. relative.User response: Provide a valid alias. Explanation: In the TDI image, the named path defining a container does not seem to be a fullyBKI8733E The TDI used for redirected restore qualified path. contains an invalid instance name. User response: Ensure that all paths in your TDI areExplanation: There is an invalid database instance fully qualifiedspecified in the instance statement of the TDI image.User response: Provide a valid instance name.156 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI8741E The container at path would overwrite BKI8747E Not all tablespaces of the original existing files or directories. database are contained in the TDI.Explanation: The TDI image contains the definition of Explanation: At least one tablespace of the originalthe container indicated whose location is already in database is missing in the TDI definitions of the targetuse. This is only allowed when restoring to the source database. However, a new location must be given fordatabase. Restoring to a different location is stopped. all tablespaces of the original database. Therefore, restoring to a different location is stopped.User response: Ensure that all path containers definedin the TDI image point to non-existing paths and all User response: Provide the information on thefile containers point to non-existing files missing tablespaces and their containers.BKI8742E The container at path is a device BKI8748E The TDI does not define enough storage container which is not supported. to hold all the data of the original database.Explanation: In the TDI image, a device container isdefined. However, device containers are not supported Explanation: The target TDI has at least oneby Backup Object Manager. tablespace whose containers are too small to hold the data of the source database.User response: Do not use device containers. User response: Increase the container size or add more containers to the tablespaces.BKI8743I Local TDI check returned return code.Explanation: The TDI with the target database BKI8749E The page size of a tablespace in the TDItablespace definition was checked. If the return code does not match the one of the originalgiven does not equal 0 errors occurred. database.User response: In the case of a non-zero return code, Explanation: The target TDI contains at least onecontact DP for SAP support. tablespace with a matching ID in the source TDI, but their page sizes do not match.BKI8744I TDI replacement check returned return User response: Ensure that tablespaces have the same code. page sizes in both the source and the target TDI.Explanation: The system checked whether thetablespace definitions of the target TDI can replace the BKI8750E The number of used pages of adefinitions of the source TDI. If the return code given tablespace in the TDI does not matchdoes not equal 0 the tablespace definitions of the target the one of the original database.TDI are not valid. Explanation: The target TDI contains at least oneUser response: In the case of a non-zero return code, tablespace with a matching ID in the source TDI, butcontact DP for SAP support. the number of used pages of the target tablespace does not match the number of used pages in the originalBKI8745E The TDI is invalid. database.Explanation: The TDI with the target tablespace User response: Ensure that the number of used pagesdefinitions is not valid. Restoring to a different location of a tablespace is the same in both the source and theis stopped. target TDI.User response: Check the Backup Object Manager logfor the return code of the validation. Check for and BKI8751E The tablespace type in the TDI does notrespond to preceding error messages in the Backup match the one of the original database.Object Manager log. Explanation: The target TDI holds at least one tablespace with a matching ID in the source TDI, butBKI8746I The TDI is valid. the tablespace types are different.Explanation: The TDI with the target tablespace User response: Ensure that the type of a tablespace isdefinition is valid. Processing continues. the same in both the source and the target TDI.User response: None. Appendix B. Data Protection for SAP (DB2) Messages 157
    • Messages of one of the tablespace containers is not allowed. A listBKI8752E BackOM does not support redirected of containers the system tries to create can be found in restore with device containers. the Backup Object Manager log. One of them failed.Explanation: The target TDI contains at least one User response: Check for and respond to further errordefinition of a device container. However, device messages in the Backup Object Manager log.containers are not supported by Backup ObjectManager’s redirected restore function. BKI8760E Not all directories for the containersUser response: Do not use the Backup Object could be created.Manager’s redirected restore facility for devicecontainers. Explanation: The system tried to create the directories to place the containers in, but at least one failed.BKI8753E A container cannot be created at path. User response: Ensure that the system has sufficient privileges to create the directories at the desiredExplanation: Either the location where the tablespace locations.container is to be created does not exist, or thepermissions of the user are not sufficient. BKI8761E The container at path does not have theUser response: Check the location and the minimum size of two extends.permissions. Explanation: A tablespace container to be created must have at least the size of two extends.BKI8755I Getting reference TDI from TSM ... User response: Correct the size of the container to beExplanation: Retrieving the appropriate TDI to be created.used by internal checking routines from the TSMserver. BKI8762I Set tablespace container with ID id andUser response: None. name tablespace_container. Explanation: Backup Object Manager redirects aBKI8756W Could not get reference TDI from TSM. tablespace container to the ID and name indicated. No input validation is done. User response: None.Explanation: The system could not find a TDI imagematching the database backup to be restored on TSM.The restore action will be continued, but the input data BKI8763E The extent size of a tablespace in thecannot be validated before the restore starts. TDI does not match the one of the original database.User response: None. Explanation: The extend sizes of corresponding tablespaces defined in the source and target TDIs mustBKI8757I Performing redirected restore from be equal. However, for at least one tablespace different source alias to target alias... extend sizes are defined in the source and targetExplanation: Redirected restore of source alias to target databases.alias is starting. User response: Define matching extend sizes forUser response: None corresponding tablespaces.BKI8758E The TDI does not contain data for BKI8765I Testing redirected restore from source tablespace tablespace. alias to target alias ...Explanation: A definition of the tablespace named is Explanation: The system is testing whether theexpected to be provided in the TDI, but could not be original database can be restored to the target location.found. It checks whetherUser response: Ensure that all tablespaces of the v the filesystem where the tablespace containers are tosource database are also defined in the target TDI. be created has sufficient free space. (If specified, normalizing and scaling are also considered.) v there are existing files and directories identical to theBKI8759E Redirecting of at least one container containers defined for the target database. This failed. would indicate that a database of same name and ofExplanation: The system tried to create the containers same structure already exists, and data could befor a tablespace, but at least one of them could not be overridden.redirected to a different location. Usually, the location158 Data Protection for SAP Installation and User’s Guide for DB2
    • Messagesv the structures of the source and target databases BKI8773E The interactive modification of the (tablespace types, page sizes, extend sizes) allow for containers failed. a redirected restore. Explanation: You tried to interactively change theUser response: None. location of containers, but this operation failed. User response: Contact DP for SAP support.BKI8766I Check successful. Redirected restore possible with these settings. BKI8776E You are not allowed to delete thisExplanation: The redirected restore test finished container.successfully. Thus, the redirected restore operation canbe started with the options specified for the test run. Explanation: You tried to delete the last container of a tablespace. However, at least one container must beUser response: None. available to every tablespace. User response: Make sure that there is at least oneBKI8767W Warnings occurred. container defined for every tablespace.Explanation: The redirected restore test detected oneor more minor conflicts. These conflicts may or may BKI8798E You cannot continue as there are errors.not prevent a successful redirected restore operation.Nevertheless, it is recommended to resolve them. Explanation: You tried to start a restore operation after redefining the containers interactively, but errorsUser response: Check for and respond to preceding were detected in the input data. The operation cannotwarning messages in the Backup Object Manager log. continue. User response: Check all tablespaces with ’!!’ errorBKI8768E Check failed. Redirected restore not marks in the list and correct the definitions of their possible with these settings. containers. Then continue.Explanation: The redirected restore test detected oneor more major errors which will prevent a successful BKI8799E A container must have a size of at leastredirected restore with these settings. twice the extent size (minimum size forUser response: Check for and respond to preceding this tablespace).error messages in the Backup Object Manager log. Explanation: The container size specified is too small. The minimum size of a container is twice the extentBKI8770I Getting TDI for redirected restore from size. TSM ... User response: Correct the container size.Explanation: The system is retrieving the TDI imagefrom the TSM server. BKI8800I The command is: command.User response: None. Explanation: Displays the command that was issued. The following commands are possible: Backup, Restore,BKI8771E The TDI for the redirected restore could Archive/Retrieve. not be retrieved. User response: None.Explanation: The TDI image specified could not befound. BKI8801I PID of calling process: PID_number.User response: Provide the correct location of the TDI Explanation: Displays the process id of the DB2image. process which called the shared library. User response: None.BKI8772E The selected database has a structure that prevents automatic cloning. BKI8802I Found number backup image(s) on TSMExplanation: You tried to clone an SAP database using server.redirected restore, but the database does not have thedefault directory structure of an SAP database. The Explanation: For restore and delete operations DP forcloning facility of Backup Object Manager redirected SAP queries TSM for backup images by means of arestore cannot be used for this system. timestamp and shows the number of found images.User response: You may use either the interactive or User response: None.the batch mode of Backup Object Manager redirectedrestore. Appendix B. Data Protection for SAP (DB2) Messages 159
    • MessagesBKI8803I The DB2 backup image size for this BKI8812I Committed TSM sessions will be session is about size. deleted.Explanation: The estimated size of the data to be Explanation: During a backup with multiple sessions,backed up is displayed. an error occurred. The backup operation is stopped. TSM sessions already committed during this operationUser response: None. are being deleted from the TSM server in order to prevent them from being considered restorable.BKI8804W The recovery log could not be written. User response: None.Explanation: After every backup or restore, DP forSAP writes a record into the recovery log file BKI8813E Error deleting committed TSM sessions.tdprlf.<SID>.<node_name>.log. It is located in the pathpointed to by environment variable TDP_DIR. Explanation: One or more committed TSM sessions could not be deleted during the postprocessing of theUser response: Check, if the permissions are set failed backup run.correctly and if there is sufficient free space in yourfilesystem. User response: Use the Backup Object Manager to delete the file(s) manually..BKI8805W The restore was cancelled by the user. Existing data not overwritten. BKI8814I Inquire TSM with mask search mask.Explanation: During a restore, the user decided not to Explanation: The string denoted is used to inquireoverwrite existing data. As a result, the action was TSM for backup images.cancelled User response: None.User response: None. BKI8815I Information for Log Manager:BKI8806I product version.release.modification (Beta) DB2_instance DB2_database_name build_number build_data DB2_database_alias log_and_log_chain_number partitionExplanation: Writes version information into theproduct log file. Explanation: The information listed is provided to the DB2 Log Manager.User response: None. User response: None.BKI8807I Archive log file log number of chain log chain number. BKI9001E Internal error: errorExplanation: Writes information about the log file to Explanation: The following internal error: error hasbe archived into the product log file. been encountered.User response: None. User response: Contact DP for SAP support.BKI8808I Retrieve log file log number of chain log BKI9005E A not supported by B. chain number. Explanation: The installed version of product B doesExplanation: Writes information about the log file to not support product A. Most likely you need tobe retrieved into the product log file. upgrade product B.User response: None User response: Contact the DP for SAP support.BKI8810I Cleaning up resources of process BKI9006E Internal error while reading PID_number. environment variable: variable.Explanation: All resources used by the product will be Explanation: This is an internal error.released. User response: Contact DP for SAP support.User response: None.160 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI9007W An error occurred while terminating the BKI9205E Additional support information: Unable application: the error to instantiate name at position position.Explanation: While terminating the application, an Explanation: This error message typically follows aerror occurred. This has no impact on the success of the previous error. If so this error message can be ignored.operation. Otherwise contact DP for SAP support.User response: None User response: Contact DP for SAP support.BKI9200E Additional support information: An BKI9206E Additional support information: Unable exception was thrown at position: to use actual when expecting expected at position. position position.Explanation: This error message typically follows a Explanation: This error message typically follows aprevious error. If so this error message can be ignored. previous error. If so this error message can be ignored.Otherwise contact DP for SAP support Otherwise contact DP for SAP support.User response: Contact DP for SAP support. User response: Contact DP for SAP support.BKI9201E Additional support information: An BKI9207E Additional support information: An Exception was thrown at position: exception was thrown at position: position. position.Explanation: This error message typically follows a Explanation: This error message typically follows aprevious error. If so this error message can be ignored. previous error. If so this error message can be ignored.Otherwise contact DP for SAP support Otherwise contact DP for SAP support.User response: Contact DP for SAP support. User response: Contact DP for SAP support.BKI9202E Additional support information: An BKI9208E System error errno: errno text at position Exception was thrown at position: position. position. Explanation: A system call failed with errno.Explanation: This error message typically follows a User response: Check errno and errno text with youprevious error. If so this error message can be ignored. system administrator. If you cannot resolve theOtherwise contact DP for SAP support. problem, contact DP for SAP support.User response: Contact DP for SAP support. BKI9209E Additional support information: NoBKI9203E Additional support information: An handler registered for message type exception was thrown at position: message. Thrown at position: position. position. Explanation: This error message typically follows aExplanation: This error message typically follows a previous error. If so this error message can be ignored.previous error. If so this error message can be ignored. Otherwise contact DP for SAP support.Otherwise contact DP for SAP support User response: Contact DP for SAP support.User response: Contact DP for SAP support. BKI9210E ESD_AbortDispatchingException thrownBKI9204E Additional support information: An at position: position. Exception was thrown at position: Explanation: An internal error occurred. position (text=description). User response: Contact DP for SAP support.Explanation: This error message typically follows aprevious error. If so this error message can be ignored.Otherwise contact DP for SAP support. BKI9211E Additional support information: An Exception was thrown at position:User response: Contact DP for SAP support. 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. Appendix B. Data Protection for SAP (DB2) Messages 161
    • MessagesBKI9212E Additional support information: No BKI9302E Additional support information: Unused handler registered for message type type. ESD_ReturnChannel destroyed. Thrown at position: position. Dumping callstack: callstackExplanation: This error message typically follows a Explanation: This error message typically follows aprevious error. If so this error message can be ignored. previous error. If so this error message can be ignored.Otherwise contact DP for SAP support. Otherwise contact your DP for SAP support.User response: Contact DP for SAP support. User response: Contact your DP for SAP support.BKI9213E Internal error: A memory allocation BKI9306I Dumping callstack: call stack. request failed at position: position. Explanation: This message is always preceded by anExplanation: This error message indicates an error message indicating the problem. It providesout-of-storage condition. It may occur due to a additional information that might help DP for SAPprevious error, or it may be owed to a large size of the support to analyze the cause of the problem.internal buffers User response: If you need to call DP for SAPUser response: Check for and respond to preceding support, provide the information given in this messageerror messages. You may also want to reduce the size together with the error information.of the internal buffers (keyword BUFFSIZE in the DataProtection for SAP profile). BKI9307E Did not find a winsock dll compatible with version expected version. VersionBKI9219E Additional support information: Invalid found is available version error type typeencountered. Explanation: The product failed to load theExplanation: This error message typically follows a appropriate winsock dll.previous error. If so this error message can be ignored. User response: Contact your system administratorOtherwise contact DP for SAP support.User response: Contact DP for SAP support. BKI9308E A socket request timed out after processing number of bytes bytes position.BKI9220E Additional support information: Second Explanation: A socket request was issued with a call of call. timeout and the requested action could not beExplanation: This error message typically follows a completed within the time specified. It was cancelledprevious error. If so this error message can be ignored. after processing number of bytes bytes.Otherwise contact your DP for SAP support. User response: If you need to call DP for SAPUser response: Contact your DP for SAP support. support, provide the information given in this message together with the error information.BKI9300E Additional support information: Aborting ’send’ operation. See previous BKI9309E Operation terminated due to an explicit error. abort request.Explanation: This error may have been caused by Explanation: An operation was terminated due toprevious errors. customer intervention.User response: Check for previous errors and correct User response: None.them. BKI9310E Could not add backup_id to theBKI9301E Additional support information: State repository at path. state does not match state pattern pattern. Explanation: The system was not able to addExplanation: This error message typically follows a information on the named backup to the repositoryprevious error. If so this error message can be ignored. located in the path indicated.Otherwise contact DP for SAP support. User response: Make sure the repository path is setUser response: Contact your DP for SAP support. correctly. If you need to correct the repository location, restart the server executable afterwards. If the problem persists contact your IBM support personnel.162 Data Protection for SAP Installation and User’s Guide for DB2
    • MessagesBKI9311E Could not find backup_id in the BKI9316E The path ’path’ does not point to a valid repository at path. repository location.Explanation: Information on the backup denoted by Explanation: When starting up, the server could notthe backup ID could not be found in the repository locate its repository.located in the path indicated. User response: Correct the profile or the call asUser response: Make sure the repository path is set appropriate.correctly. If you need to correct the repository location,restart the server executable afterwards. If the problempersists contact your IBM support personnel.BKI9312E backup_id is currently locked in the repository at path.Explanation: The information on the backup denotedby the backup ID is currently locked by a differentprocess. Make sure to run only a single operation usinga specific backup at a time.User response: Wait for the other operation to finishor abort this operation. Then start again. If the problempersists contact your IBM support personnel.BKI9313E Failed to update backup_id in the repository at path.Explanation: The information on the named backupcould not be updated in the repository located at thepath named.User response: Check the logs for other messagespointing to the cause of this problem. Resolve anyproblems indicated. If the problem persists contact yourIBM support personnel.BKI9314E Could not remove backup_id from the repository at path.Explanation: An attempt to remove the informationon the backup named from the repository located at thepath indicated failed.User response: Check the logs for other messagespointing to the cause of this problem. Resolve anyproblems indicated. If the problem persists contact yourIBM 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 toload the repository located at the path named.However, the repository was locked by a differentprocess. This can happen if two server processes try touse the same repository. This is not supported.User response: Make sure each instance of the serveruses its own repository. Appendix B. Data Protection for SAP (DB2) Messages 163
    • Messages164 Data Protection for SAP Installation and User’s Guide for DB2
    • 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%system32driversetcservices on Windows:© Copyright IBM Corp. 1995, 2007 165
    • Troubleshooting tdpr3db2 57322/tcp tdpr3db264 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 machines 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 FilesTivolitsmapi.166 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 cfgGeneral 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: Appendix C. Troubleshooting 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 don’t 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%system32driversetcservices. Compare the port number from the error message with the port number within168 Data Protection for SAP Installation and User’s Guide for DB2
    • 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 missingv 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, proceedwith step 1.3 and try to make a backup using the DB2 backup command to verifythe settings are correct. In Appendix J, “Using DP for SAP to Back Up and RestoreFiles 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 usingthe 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 logtdpdb2.<SID>.<nodename>.log, located in the directory pointed to by theenvironment variable TDP_DIR or, if the variable is not specified, in the systemtemporary directory. If this log file was not written (2.2) this is a clear sign thatDB2 either was unable to load the shared library containing the DB2 connector ofDP for SAP or encountered an error before calling the DP for SAP library. In bothcases there should be a DB2 error message beginning with the prefix ’SQL’displayed on the command line and an entry in the DB2 diagnostic logdb2diag.log (4.3) can be found.For further error analysis DB2 provides a mechanism of displaying detailed errordescriptions. Issue the following command from the command line: db2 ? SQL<number> Appendix C. Troubleshooting 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 today’s 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 Data Protection for SAP Installation and User’s Guide for DB2
    • TroubleshootingReproducible (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. Appendix C. Troubleshooting 171
    • TroubleshootingDB2 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 Explanation User Response 1 The library specified could not be Check the DB2 diagnostic log for loaded. further details. 2 Communication error between Check the Data Protection for SAP shared library and ProLE run log tdpdb2.<SID>.<nodename>.log for further details. 6 Object specified cannot be found There is no backup image on TSM on TSM. matching the given search criteria. 10 Invalid options specified with the Check the options string specified options parameter of the DB2 and check the Data Protection for backup/restore command. SAP run log tdpdb2.<SID>.<nodename>.log for further details. 11 Initialization procedure for shared Check the Data Protection for SAP library failed. run log tdpdb2.<SID>.<nodename>.log and the DB2 diagnostic log for further details. 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. 18 An error occurred during reading Check the Data Protection for SAP or writing data from or to TSM. run log tdpdb2.<SID>.<nodename>.log for further details. 26 An error occurred during deleting Check the Data Protection for SAP data from TSM. run log tdpdb2.<SID>.<nodename>.log for further details. 29 An abort request from DB2 could Check the Data Protection for SAP not be handled correctly. run log tdpdb2.<SID>.<nodename>.log and the DB2 diagnostic log for further details. 30 A severe error occurred. Check the DB2 diagnostic log for further details.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 applied172 Data Protection for SAP Installation and User’s Guide for DB2
    • Troubleshootingv DB2 version (including 32- or 64-bit)v TSM server versionv OS level for TSM serverv 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 If the process worked previously, also have the change history of the system components availableIn addition to the above information there will be a situation in which you need tosupply additional information. Your service representative will ask you for this. Appendix C. Troubleshooting 173
    • 174 Data Protection for SAP Installation and User’s Guide for DB2
    • || 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. © Copyright IBM Corp. 1995, 2007 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| SID’s. 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Appendix E. Installation Planning SheetsData 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 Windows Installation Parameter DB2 database SID: X X TSM server name or IP address: X 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. X X 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. X X 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 FilesTivoliTSMbaclient Path to client option file of Tivoli Storage Manager (contents of environment variable DSMI_CONFIG). For details refer to the Tivoli Storage Manager documentation. X 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. X Default: C:temp Installation path for Data Protection for SAP executables: X Default: C:Program FilesTivoliTSMtdp_r3db2 or C:Program FilesTivoliTSMtdp_r3 db264© Copyright IBM Corp. 1995, 2007 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 X X 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 Data Protection for SAP Installation and User’s Guide for DB2
    • Installation Planning Sheets 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 Prot