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

Tivoli Storage Manager
®

for Enterprise Resource Planning

Version 5.5

Data Protection for SAP
Installation 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 Notice
This edition applies to Data Protection for SAP Version 5 Release 5 Modification Level 0 (product number
5608–APR) available as a licensed program product, and to all subsequent releases and modifications until
otherwise indicated in new editions.
Order publications through your IBM® representative or the IBM branch office serving your area. Publications are
not stocked at the addresses given below.
Address comments on this publication to:
IBM Deutschland Entwicklung GmbH
Enterprise Solution Development
Dept. 3848, Bldg. 71032-15
Schoenaicher Str. 220
71032 Boeblingen
Germany

FAX (Germany): 07031 16 3619
FAX (other countries): (+49) 7031 16 3619

Internet Web page: http://www.ibm.com/software/tivoli
Make sure to include the following in your comment or note:
v Title and order number of this book
v Page number or topic related to your comment
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1995, 2007. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Figures . . . . . . . . . . . . . . vii 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 239

vi 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 . . . . . . . . . . . . . . . . . . . . . . . . . 37
10. Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
11. Parallel (Multiple) Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
12. Parallel (Multiple) Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
13. Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
14. Null Block Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
15. Sample Environment for HACMP Takeover . . . . . . . . . . . . . . . . . . . . . . . 49
16. Data Protection for SAP Backup Object Manager . . . . . . . . . . . . . . . . . . . . . 54
17. Redirected Restore Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
18. Tablespace Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
19. Tablespace Normalizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
20. Administration Assistant Components (with Default Port Numbers) . . . . . . . . . . . . . . 78
21. Example of an SAP Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
22. A Bird’s Eye View of the Data Flow During Backup . . . . . . . . . . . . . . . . . . . . 97
23. Performance Optimizing by Using Sensors . . . . . . . . . . . . . . . . . . . . . . . 98
24. Showing Data Throughput and I/O Utilization . . . . . . . . . . . . . . . . . . . . . 98
25. Indicating a Disk Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
26. Indicating a Network or TSM Bottleneck . . . . . . . . . . . . . . . . . . . . . . . 100
27. Indicating a Balanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 101
28. Drilling Down: Replay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
29. Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
30. Operations – Detailed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
31. Operations Daily Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
32. Operations - Failure Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
33. Performance Report - Graphical Presentation Section . . . . . . . . . . . . . . . . . . . 108
34. Performance Report - Tabular Presentation Section . . . . . . . . . . . . . . . . . . . . 109
35. SAP and Data Protection for SAP Configuration files on UNIX and Linux. . . . . . . . . . . . . 166
36. 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.


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 requests the backup data from the shared library

The Data Protection for SAP shared library
v checks with the Tivoli Storage Manager if the backup image is available
v retrieves the data blocks from TSM



v passes the data blocks to the DB2 Server Process

The DB2 Server Process
v restores the DB2 data to the database containers
v logs the restore in the Recovery History File

DP for SAP and Log File Management
Starting with DB2 version 8.2, one of two log file management facilities in an SAP
enviromment can be chosen for archiving and retrieving log files. These are the
SAP-DB2 Administration Tools BRARCHIVE and BRRESTORE and the built-in
DB2 Log Manager.

Data Protection for SAP supports both of these log management methods, but the
built-in DB2 Log Manager in combination with Data Protection for SAP makes
archiving and retrieving log files easier and more comfortable.

DP for SAP and BRARCHIVE / BRRESTORE
DB2 log files in an SAP environment can have four different states during their life
cycle:
v online active
The log file is currently being used by DB2 for logging transactions.
v online retained
The log file is no longer being used for logging transactions, but it contains
transactions with data pages that have not yet been written from the buffer pool
to disk. It will be needed by DB2 in case of a crash recovery or for roll-back.
The DB2 logging user exit is called by DB2 (if configured) to copy a filled online
log file to the log_archive directory.
Do not use operating system commands for copying online log files.
v offline retained
The log file is no longer being used by DB2 and does not contain transactions
with unwritten data pages. It is not crucial for a crash recovery or a roll-back.
After the log file has been successfully copied to the log_archive path DB2 may
eventually delete the log file.
v archived
BRARCHIVE has successfully archived offline retained log files to TSM.

Chapter 1. Concepts of Data Protection 5


Figure 2. DB2 Log File Management

The SAP-DB2 Administration Tools support the backup of DB2 log files: Filled or
closed online log files are immediately copied from the log_dir directory by the
DB2 logging user exit to the log_archive directory. Offline log files are backed up
from the log_archive directory with the SAP tool BRARCHIVE. Archived retained
log files are restored with the SAP tool BRRESTORE.

For a detailed description of the DB2 logging user exit functionality and of the
SAP-DB2 Administration Tools BRARCHIVE and BRRESTORE, refer to the
Database Administration Guide in your SAP documentation.

For archiving DB2 log files (BRARCHIVE), the SAP tool
v creates a unique timestamp for identification;
v loads Data Protection for SAP dynamically as a shared library.

The Data Protection for SAP shared library:
v reads the data from file
v creates data blocks
v passes the data blocks on to TSM.

Tivoli Storage Manager writes the data blocks to the storage media (preferably
disk).

The SAP tool logs the archive run in the SAP administration database.

For retrieving logs (BRRESTORE), the SAP tool
v requests the backup data from the shared library.

The Data Protection for SAP shared library
v checks with the Tivoli Storage Manager if the requested log file data is available
v retrieves the data blocks from TSM



v writes the data blocks to a file on disk.

The SAP tool logs the retrieve run in the SAP administration database.

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

Figure 3. Log Management with DB2 Log Manager and DP for SAP

Data Protection for SAP is loaded dynamically by the DB2 Log Manager as a
shared library on UNIX or Linux, or as a DLL on Windows, and runs as part of the

Chapter 1. Concepts of Data Protection 7


DB2 engine. When a log file is ready to be archived (online/offline retained) the
DB2 Log Manager starts to archive this file by passing it blockwise to DP for SAP.
Data Protection for SAP passes these data to TSM.

If a database rollforward recovery was issued, the DB2 Log Manager checks first if
the corresponding log files are already located either in the log path or in an
overflow log path specified with the DB2 rollforward command. If the log files
were not found at one of these locations, the DB2 Log Manager checks with Data
Protection for SAP if the corresponding log images can be found on TSM. If yes,
Data Protection for SAP retrieves the data from TSM and passes them blockwise to
the DB2 Log Manager, who writes the log files to the filesystem. Then, these log
files will be applied by special DB2 processes to the database.

For a detailed description of the DB2 Log Manager refer to the Administration Guide
in your DB2 documentation.


Chapter 2. Developing a Backup Strategy
This chapter helps you define an appropriate backup strategy for your SAP
system. If you already have a successful backup strategy in place you may want to
move on to the next chapter.

The strategy you choose is dependent on your specific requirements. Consider the
following questions:
v What type of events do you wish to protect your SAP system against?
v How large is your database?
v What is the transaction rate of your database?
v How fast do you need to recover from a failure?
v What backup windows are available?

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

Data Protection for SAP solely covers the backup and restore of SAP database
objects, as shown in Figure 4.

Figure 4. DB2 Backup Objects


Developing a Backup Strategy

Please note that there is no provision for backing up online DB2 log files that are
required for crash recovery. Therefore, it is recommended to place the DB2 log
directory on a mirrored disk.

In order to protect the system against the loss of SAP executables, user data, or
even operating system data you should use the incremental backup capabilities of
the Tivoli Storage Manager backup-archive client with its selective incremental
backup capabilities.

The Tivoli Storage Manager selective incremental backup function allows you to
define an include-exclude list of files that is applied automatically during
incremental backup operations. For further information about include-exclude lists,
see your Tivoli Storage Manager manuals, using the backup-archive clients. This
list should be used to exclude data already stored using Data Protection for SAP,
i.e. all database files, such as containers and offline log files. Examples of
include-exclude lists for UNIX or Linux can be found in “Sample TSM Profiles for
UNIX or Linux” on page 213 and for Windows in “Sample TSM Profiles for
Windows” on page 214. Sample files can also be found in your Data Protection for
SAP installation package.

In order to be protected against the complete loss of the operating system, for
example in the case of a storage hardware failure, it is imperative that after the
installation of the operating system or after updates/upgrades of the operating
system, system backups are made with the operating system utilities, e.g. mksysb
for AIX®. This will allow you to start your system from the backup medium. Base
backups should include a configured TCP/IP environment as well as the Tivoli
Storage Manager client including the API in order to be able to restore all other
data.

Trimming the Database Size
Obviously, backing up and restoring large databases takes longer than backing up
and restoring smaller databases. Therefore, you may want to consider off-loading
inactive data to an archive. DB2 CommonStore for SAP, a companion product to
Data Protection for SAP, provides this functionality. See also “Archiving Inactive
Data” on page 18 and http://www.ibm.com/software/data/commonstore/sap/.

Transaction Rate
Due to high transaction rates, SAP databases usually require frequent database and
log file backups.

Backup Windows and Recovery Time
Your backup strategy usually has two main objectives:
v Minimize down-time after a failure.
v Minimize the impact of backup activity on the application.

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



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


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.


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.


Introducing Data Protection for SAP

Integration of Data Protection for SAP with SAP
Once configured, Data Protection for SAP operates as an invisible link between
DB2 and the SAP-DB2 Administration Tools on one hand and Tivoli Storage
Manager on the other. A shared library is dynamically linked by DB2
backup/archive processes and by the SAP utilities.

Figure 7. Integration of Data Protection for SAP with DB2

The Data Protection for SAP package also contains the Administration Assistant,
aimed at increasing the 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.



Storing Data on a TSM Server
Data Protection for SAP transfers data to and from the backup server via a single
session or via multiple (parallel) sessions to a TSM server. Each session must have
a storage device associated with it. The SAP backup ID is persistently linked with
each backup file. This backup ID can be used later to determine all files required
for a complete restore.

Note
In SAP terminology ’backup’ (BRBACKUP) means backup of database
contents, ’archive’ means the backup of offline DB2 log files. DP for SAP
employs the TSM archive function for both backup types.

It is highly recommended to use tape storage for the database contents, as this has
consistently proven to provide the best data throughput for backup and restore.
For backing up log files it is recommended to use a disk-tape storage hierarchy
and to backup each DB2 log file right after it is placed into the archive directory.
This yields the best protection against data loss and eliminates the necessity to
mount a tape for each DB2 log file.

Collocation is a function in TSM to ensure that client data is kept together on one
tape. We recommend to deactivate collocation for backups with DP for SAP in
order to enable parallel sessions to use multiple tape drives in parallel. Collocation
must also be deactivated in order to use the multiple log copy function, see
“Multiple DB2 Log File Copies” on page 16.

Views of backups on the TSM server are generated by the utility backom. For
details, please refer to Chapter 6, “Data Protection for SAP Backup Object
Manager,” on page 53.

Note
DP for SAP can be configured to use multiple TSM servers to improve either
availability (alternate servers) or performance (multiple servers). DP for SAP
accesses only the servers defined in its profile when inquiring for the backup
repository. Therefore care has to be taken when removing TSM servers from
the DP for SAP profile while they still hold valid backup data.

Database backups are usually kept for a specified time until they become obsolete.
In order to manage backup storage space efficiently these backups should then be
deleted so tapes can be reclaimed. There are two ways to perform this deletion:
1. by setting the archive retention period with TSM, or
2. by using the DP for SAP backup version control function. Data Protection for
SAP deletes whole backup generations, i.e. full backups and all related partial
and log file backups, when the specified number of versions is exceeded.

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


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

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

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

Incremental and Delta Backup
Data Protection for SAP supports incremental and delta backups of DB2 databases.
Depending on the system environment, this may result in decreased backup times.

RL Compression
RL Compression is a fast and very effective mechanism to compress a partially
filled database. For such a database you can reduce network traffic, decrease the
number of tapes required for a backup, and reduce the impact of network induced
bottlenecks. For more information see “Compression” on page 40.

Automation Options of Data Protection for SAP
Data Protection for SAP comes with a variety of options that help improve your
administrative productivity.

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

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

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



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.



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)



v 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 data

Thus TSM can be used as an integrated repository for backups and for archived
information.

For more information on DB2 CommonStore for SAP , see: http://www.ibm.com/
software/data/commonstore/sap/.


Part 2. Installing and Using Data Protection for SAP


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/.


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.



| 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


| 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)


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

Recommended

Recommended

More Related Content

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

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

More from Banking at Ho Chi Minh city

More from Banking at Ho Chi Minh city (20)

Recently uploaded

Recently uploaded (20)

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