Null

IBM Tivoli Storage Manager for Enterprise Resource
Planning (5608–APR) V.5.3.
Data Protection for mySAP

Installation & User’s Guide for Oracle
Version 5. Release 3. 0
SC33-6340-05
IBM Tivoli Storage Manager for Enterprise Resource
Planning (5608–APR) V.5.3.

SC33-6340-05
Note!
Before using this information and the product it supports, be sure to read the general information under
“Notices” on page xi.
Sixth Edition (December 2004)

This edition applies to Data Protection for mySAP Version 5 Release 3 Modification Level 0 (program 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.
A form for readers’ comments is provided at the back of this publication. If the form has been removed, address
your comments to:
IBM Deutschland Entwicklung GmbH
Enterprise Solution Development
Dept. 3848, Bldg. 71032-05
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, 2003. 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 . . . . . 18
Messaging . . . . . . . . . . . . . . 18
Tables . . . . . . . . . . . . . . . ix Frontend/Backend Processing . . . . . . . 18
Productivity Options of Data Protection for mySAP 18
Reporting . . . . . . . . . . . . . . 18
Notices . . . . . . . . . . . . . . . xi Monitoring the Backup Status . . . . . . . 18
Trademarks and Service Marks . . . . . . . . xi Performance Analysis . . . . . . . . . . 18
Naming Conventions used in this Documentation xii Tracing . . . . . . . . . . . . . . . 19
Using FlashCopy to Minimize Backup and Restore
Preface . . . . . . . . . . . . . . xiii Windows . . . . . . . . . . . . . . . 19
Who Should Read This Book . . . . . . . . xiii Integration with Data Protection for IBM
How to Read This Book . . . . . . . . . . xiii Enterprise Storage Server (ESS) for mySAP . . . 19
Where to Find More Information . . . . . . . xiii Archiving Inactive Data . . . . . . . . . . 19
Part 1. Data Protection Basics . . . . 1 Part 2. Installing and Using . . . . . 21
Chapter 1. Concepts of Data Protection Chapter 4. Installing or Upgrading Data

for mySAP . . . . . . . . . . . . . 3 Protection for mySAP . . . . . . . . 23
Oracle Backup/Restore and Data Protection for Prerequisites for the Installation of Data Protection
mySAP . . . . . . . . . . . . . . . . 3 for mySAP . . . . . . . . . . . . . . 23
DP for mySAP and BACKINT . . . . . . . 3 Installation Planning for Data Protection for mySAP 24
DP for mySAP and RMAN . . . . . . . . 4 Installing Data Protection for mySAP . . . . . . 25
Initial Installation . . . . . . . . . . . 25
Chapter 2. Developing a Backup Upgrade Installation (Migration) . . . . . . 25
Strategy . . . . . . . . . . . . . . . 5 | TSM API Installation . . . . . . . . . . 25
Installing Data Protection for mySAP on AIX,
Planning a Backup Strategy for the Operating System 5
HP-UX, Linux, Solaris . . . . . . . . . . 25
Planning a Backup Strategy for Your Oracle Database 5
Installing Data Protection for mySAP on
Planning a Backup Strategy for Backup Protocols and
Windows . . . . . . . . . . . . . . 27
Profiles . . . . . . . . . . . . . . . . 7
Post-Installation Steps . . . . . . . . . . . 28
Planning a Backup Strategy for mySAP System Data 8
Review of the TSM Options Files . . . . . . 28
Implementing the Strategy by Scheduling Automated
Set the Password . . . . . . . . . . . 28
Backup Runs . . . . . . . . . . . . . . 9
Verifying the Installation . . . . . . . . . 29
Scheduling Products . . . . . . . . . . . 9
Upgrading (Migration) . . . . . . . . . . 31
Sample Backup Strategy for Daily Backup
Upgrading Data Protection for mySAP . . . . 31
Processing . . . . . . . . . . . . . . 10
Special Installation . . . . . . . . . . . . 31
Silent Installation . . . . . . . . . . . 31
Chapter 3. Introducing Data Protection Console Installation. . . . . . . . . . . 32
for mySAP . . . . . . . . . . . . . 13 Firewall Installation . . . . . . . . . . 32
Scope of Data Protection for mySAP . . . . . . 13 Uninstalling Data Protection for mySAP . . . . . 32
Integration of Data Protection for mySAP with SAP 14 | Uninstalling the old Version of DP for mySAP
Storing Data on a TSM Server . . . . . . . . 15 | from UNIX and Linux . . . . . . . . . . 32
Performance Options of Data Protection for mySAP 16 Uninstalling the old Version of DP for mySAP
Parallel (Multiple) Sessions . . . . . . . . 16 from Windows . . . . . . . . . . . . 33
Multiplexing . . . . . . . . . . . . . 16
Disk Sorting . . . . . . . . . . . . . 16 Chapter 5. Adjusting Your System . . . 35
Multiple (Parallel) Network Paths and Multiple General Performance Considerations . . . . . . 35
(Parallel) Servers . . . . . . . . . . . 16 Database Server Considerations . . . . . . 36
| Incremental Backup . . . . . . . . . . 17 Network Considerations . . . . . . . . . 36
Individual Tablespace Locking . . . . . . . 17 Backup Server Considerations . . . . . . . 37
RL Compression . . . . . . . . . . . . 17 Adjustments to DP for mySAP for Improving
Automation Options of Data Protection for mySAP 17 Performance of Data Transfer . . . . . . . . 37
Selectable Management Classes . . . . . . . 17 Multiplexing . . . . . . . . . . . . . 38
Retain Backups by Version . . . . . . . . 17 Multiple Sessions . . . . . . . . . . . 39
Multiple Redo Log Copies . . . . . . . . 17
© Copyright IBM Corp. 1995, 2003 iii

Multiple Network Paths . . . . . . . . . 40 Part 3. Appendixes . . . . . . . . . 81
Multiple Servers . . . . . . . . . . . . 40
Compression . . . . . . . . . . . . . 41
| Buffer Copies . . . . . . . . . . . . . 41 Appendix A. The Data Protection for
Buffer Size . . . . . . . . . . . . . . 41 mySAP Profile . . . . . . . . . . . 83
Adjustments for Interaction with Other Components 42 Keyword Reference . . . . . . . . . . . . 83
Adjustments for the Administration Assistant . . 42 Sample Data Protection for mySAP Profiles . . . . 92
Adjustments for IBM Tivoli Storage Manager . . 42 | Sample Data Protection for mySAP Profile for
Adjustments for High Availability . . . . . . . 45 | UNIX or Linux . . . . . . . . . . . . 92
Considerations for Using IBM HACMP for AIX 45 Sample Data Protection for mySAP Profile for
Windows . . . . . . . . . . . . . . 96
Chapter 6. Using DP for mySAP with
RMAN . . . . . . . . . . . . . . . 51 Appendix B. Data Protection for
| RMAN Setup on UNIX and Linux Systems . . . . 51 mySAP Messages . . . . . . . . . 101
RMAN Setup on Windows Systems . . . . . . 53 How To Find Message Files (Log Files) . . . . . 101
Data Protection for mySAP Message Explanations 102
Chapter 7. Using DP for mySAP with Data Protection for mySAP File Manager Error
Messages . . . . . . . . . . . . . . . 121
the File Manager . . . . . . . . . . 55
DP for mySAP File Manager . . . . . . . . . 55
Appendix C. Troubleshooting . . . . 123
Problem Resolution during Installation and Setup 123
| Chapter 8. Installing and Using the
Understanding The Setup . . . . . . . . 123
| Administration Assistant for Data Location of Log Files . . . . . . . . . . 125
| Protection for mySAP . . . . . . . . 59 BACKINT Problem Resolution . . . . . . 126
Introducing the Administration Assistant . . . . 59 RMAN Problem Resolution . . . . . . . . 128
| Functions and Features of the Administration Problem Resolution During Operation . . . . . 130
| Assistant . . . . . . . . . . . . . . 59 Reproducable (Repeatable) Problems . . . . 130
| Concepts of the Administration Assistant . . . 59 Random problems . . . . . . . . . . . 131
| Installing or Upgrading the Administration Contacting Your IBM / Tivoli Support . . . . . 131
| Assistant . . . . . . . . . . . . . . . 61 Invoking Data Protection for mySAP manually . . 131
| Prerequisites for the Installation of the Backup Function . . . . . . . . . . . 132
| Administration Assistant . . . . . . . . . 61 Restore Function . . . . . . . . . . . 132
| Installation Planning for the Administration Inquire Function . . . . . . . . . . . 133
| Assistant Server . . . . . . . . . . . . 62 Delete Function . . . . . . . . . . . 133
| Installing the Administration Assistant Server . . 63 | File Manager . . . . . . . . . . . . . 134
| Post-Installation Steps . . . . . . . . . . 64
| Upgrading the Administration Assistant Appendix D. Installation Planning
| (Migration) . . . . . . . . . . . . . 66
Sheet . . . . . . . . . . . . . . . 135
| Migration of the Administration Assistant Server
| Configuration File . . . . . . . . . . . 67
Configuring the Administration Assistant . . . . 67 Appendix E. Alternate/Parallel Backup
Administering Userids . . . . . . . . . . 67 Paths and Backup Servers . . . . . 137
| Configuring for Secure Communication . . . . 67 Parameter Settings - SERVER Statement . . . . 138
EXAMPLE 1: Use of Alternate Paths for
| Chapter 9. Balancing Your System . . . 69 Increased Availability . . . . . . . . . . 139
| Cyclic Procedure for Optimizing your Configuration 69 EXAMPLE 2: Use of Parallel Paths for Increased
| Observations on the DP for mySAP Data Performance . . . . . . . . . . . . . 141
| Throughput . . . . . . . . . . . . . . 69 EXAMPLE 3: Use of Alternate Servers for
| Data Protection for mySAP Performance Sensors . . 70 Disaster Recovery . . . . . . . . . . . 142
| Presentation of the Measurements in the
| Administration Assistant . . . . . . . . . . 71 Appendix F. Preparing Tivoli Storage
| Typical Situations . . . . . . . . . . . 71 Manager for DP for mySAP . . . . . 143
| Simulating Backup and Restore . . . . . . . 75 Configuring the Tivoli Storage Manager Server . . 143
| Drilling Down on Special Situations . . . . . 76 General Considerations for TSM . . . . . . 143
| Transferring Results . . . . . . . . . . 77 Prerequisites . . . . . . . . . . . . . 144
Adjusting your TSM for DP for mySAP . . . 144
Chapter 10. Cloning the mySAP System 79 Configuring the Tivoli Storage Manager Clients 147
What is Cloning ? . . . . . . . . . . . . 79 General Considerations . . . . . . . . . 147
mySAP System Cloning Example . . . . . . . 79 Tivoli Storage Manager Clients on UNIXor
Linux Systems . . . . . . . . . . . . 147
iv Data Protection for mySAP Installation & User’s Guide for Oracle
Tivoli Storage Manager Clients on Windows Sample TSM Profiles for Windows . . . . . . 160
Systems . . . . . . . . . . . . . . 148 Client User Options File Sample (dsm.opt) . . 160
Password Handling . . . . . . . . . . . 149 Client Options Files Sample (<server>.opt) . . 160
| Password Configuration Matrix ( UNIX or Include/Exclude List Sample . . . . . . . 162
| Linux ) . . . . . . . . . . . . . . 150
Password Configuration Matrix (Windows) . . 151 Appendix I. Hints and Tips for SAP
Backup Utilities . . . . . . . . . . 163
Appendix G. Backup Scheduling Hints and Tips for BRARCHIVE . . . . . . . 163
Examples . . . . . . . . . . . . . 153 Hints for BRARCHIVE Version 3.1G or Higher . . 166
UNIX or Linux Crontab Example . . . . . .
. 153 Examples Using MAX_SESSIONS and
| Elements of Backup Schedules for UNIX or Linux 153 REDOLOG_COPIES . . . . . . . . . . . 166
Crontab File Sample . . . . . . . . . . 153 mySAP Backup and Recovery Scenarios Using
Full Offline Backup Shell Script Sample . . . 154 Data Protection for mySAP . . . . . . . . . 167
Save and Delete Redo Logs Shell Script Sample 155 Backup Scenarios . . . . . . . . . . . 168
Windows Scheduling Example. . . . . . . . 155 Restore/Recovery Scenario . . . . . . . . 172
Elements of Backup Schedules for Windows . . . 156
Schedule Batch Sample . . . . . . . . . 156 Appendix J. Hints and Tips for
Full Offline Backup Batch File Sample . . . . 156 Network Settings . . . . . . . . . . 177
Save and Delete Redo Logs Batch File Sample 157
Networks with Large Bandwidth-Delay Product 177
SP Switch (RISC 6000) . . . . . . . . . . 178
Appendix H. Sample Tivoli Storage Network Settings of the Tivoli Storage Manager 178
Manager Profiles . . . . . . . . . . 159
| Sample TSM Profiles for UNIX or Linux . . . . 159 Glossary . . . . . . . . . . . . . 179
Client User Options File Sample (dsm.opt) . . 159
Client System Options File Sample (dsm.sys) 159
Index . . . . . . . . . . . . . . . 183
Include/Exclude List Sample . . . . . . . 159
Contents v
vi Data Protection for mySAP Installation & User’s Guide for Oracle
Figures
1. DP for mySAP with SAPDBA using the BACKINT Interface . . . . . . . . . . . . . . . . . 3
2. DP for mySAP with SAPDBA using the RMAN Interface . . . . . . . . . . . . . . . . . . . 4
3. Backup Scenarios Within a mySAP Oracle Environment . . . . . . . . . . . . . . . . . . . 7
4. Production Backup Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5. Scope of Data Protection for mySAP . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Integration of Data Protection for mySAP with SAP . . . . . . . . . . . . . . . . . . . . 14
7. Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8. Data Transfer for a Backup / Restore . . . . . . . . . . . . . . . . . . . . . . . . . 38
9. Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10. Parallel (Multiple) Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
11. Parallel (Multiple) Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12. Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
13. Null Block Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
14. Sample Environment for HACMP Takeover . . . . . . . . . . . . . . . . . . . . . . . 45
| 15. File Manager — Result of an Inquiry Procedure . . . . . . . . . . . . . . . . . . . . . 56
16. File Manager — Result of an Inquiry Procedure Showing File Names . . . . . . . . . . . . . . 56
17. File Manager — Result of a Redirected Restore Procedure . . . . . . . . . . . . . . . . . . 58
| 18. Example of a mySAP Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . 60
| 19. Optimizing your Configuration with the Administration Assistant . . . . . . . . . . . . . . . 69
| 20. Optimizing your configuration with the AA (Bird’s Perspective) . . . . . . . . . . . . . . . . 70
| 21. Performance Optimizing by Using Sensors . . . . . . . . . . . . . . . . . . . . . . . 70
| 22. Showing Data Throughput and I/O Utilization . . . . . . . . . . . . . . . . . . . . . 71
| 23. Indicating a Disk Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
| 24. Indicating a Network or TSM Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . 73
| 25. Indicating a Balanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 74
| 26. Drilling Down: Replay Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
27. SAP and Data Protection configuration files on UNIX or Linux . . . . . . . . . . . . . . . . 124
28. Problem Isolation for Backint . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
29. Problem Isolation for RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
© Copyright IBM Corp. 1995, 2003 vii

viii Data Protection for mySAP Installation & User’s Guide for Oracle
Tables
1. SAP Backup Profile Parameter Combinations . . . . . . . . . . . . . . . . . . . . . . 29
2. File Extensions for Shared Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 51
| 3. Summary: How to Determine Throughput Rates . . . . . . . . . . . . . . . . . . . . . 76
4. SERVER Statement and Appropriate Profile and Option File Settings. . . . . . . . . . . . . . . 138
5. Password Handling for UNIX or Linux . . . . . . . . . . . . . . . . . . . . . . . . 150
6. Password Handling for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 151
7. Tuning of Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
8. Tuning of SP Switch Buffer Pools . . . . . . . . . . . . . . . . . . . . . . . . . . 178
9. Tuning Tivoli Storage Manager Configuration File Attributes. . . . . . . . . . . . . . . . . 178
© Copyright IBM Corp. 1995, 2003 ix

x Data Protection for mySAP Installation & User’s Guide for Oracle
Notices
References in this publication to IBM® products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended to
state or imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any of
the intellectual property rights of IBM may be used instead of the IBM product,
program, or service. The evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, are the
responsibility of the user.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to
IBM Director of Licensing
IBM Corporation
North Castle drive
Armonk, NY 10504-1785
U.S.A
Any references in this information to non-Tivoli or non-IBM Web sites are provided
for convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for this
product and use of those Web sites is at your own risk.
If you are viewing this information in softcopy form, the photographs and color
illustrations may not appear.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Deutschland Informationssysteme GmbH
Department 0215
Pascalstr. 100
70569 Stuttgart
Germany
Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.
Trademarks and Service Marks

The following terms are trademarks or registered trademarks of International
Business Machines Corporation in the United States or other countries or both:
v AFS
v AIX
v IBM
v RS/6000
v SP
v Tivoli
© Copyright IBM Corp. 1995, 2003 xi

| R/3, mySAP and mySAP.com are registered trademarks of SAP AG in Germany,
| other countries, or both.
Oracle is a registered trademark of Oracle Corporation.
Solaris, Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Incorporated, in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
| Linux® is a trademark of Linus Torvalds in the U.S., other countries, or both.
Microsoft, Windows, Windows NT, and Windows 2000 are registered trademarks of
Microsoft Corporation in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks
of others.
Naming Conventions used in this Documentation

| In this documentation, ’IBM Tivoli Storage Manager for Enterprise Resource
| Planning Data Protection for mySAP’ is usually referred to as ’Data Protection for
| mySAP’ or as ’DP for mySAP’. The product IBM Tivoli Storage Manager is usually
| referred to as Tivoli Storage Manager or TSM.
Note
Unless otherwise stated, references in this publication to UNIX apply to all
supported UNIX-based systems as well as to Linux, and references to
Windows® apply to all supported Windows platforms.
xii Data Protection for mySAP Installation & User’s Guide for Oracle
Preface
Who Should Read This Book
This manual is intended for system programmers and administrators who are
responsible for implementing a backup solution in a mySAP environment using
the Tivoli Storage Manager. It describes the procedures needed to install and
customize Data Protection for mySAP, the interface between mySAP and the Tivoli
Storage Manager. The reader should be familiar with the documentation for
mySAP, Tivoli Storage Manager and Oracle.
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 architecture and properties of Data
Protection for mySAP and the third part (Appendixes) gives samples, profiles and
TSM 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 mySAP 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 Data Protection for mySAP, refer to the Tivoli Internet
home page at http://www.ibm.com/software/tivoli.
Note:
The most up-to-date version of this book is available in the Tivoli Information
Center at http://www.ibm.com/software/tivoli/library.
© Copyright IBM Corp. 1995, 2003 xiii

xiv Data Protection for mySAP Installation & User’s Guide for Oracle
Part 1. Data Protection Basics
© Copyright IBM Corp. 1995, 2003 1

2 Data Protection for mySAP Installation & User’s Guide for Oracle
Chapter 1. Concepts of Data Protection for mySAP
This chapter is meant for users who are new to Data Protection for mySAP. If you
are experienced in Data Protection for mySAP, you might want to move on to the
following chapter.
Oracle Backup/Restore and Data Protection for mySAP

The SAP database administration tools offer all the functions necessary to
| administer a database. The SAPDBA BRTOOLS for Oracle, (BRBACKUP,
BRARCHIVE, BRRESTORE) provide for online or offline, partial or full backup of
tablespaces (done by BRBACKUP), backup of archived redo log files (done by
BRARCHIVE) and system guided restore/recover capabilities (done by
BRRESTORE and BRRECOVER).
Oracle also provides its own administration utility RMAN (Recovery MANager)
which is of specific value when incremental backups are required. Data Protection
| for mySAP is seamlessly integrated with the BRTOOLS and Oracle’s RMAN and is
optimized to handle unattended, 24 hour, 7 days/week production backup/restore
tasks.
DP for mySAP and BACKINT

| Figure 1 shows the interaction between the BRTOOLS, DP for mySAP, and the
| BACKINT Interface in order to do backup / restores.
Figure 1. DP for mySAP with SAPDBA using the BACKINT Interface
| The BRTOOLS use tables in the Oracle database and system data in order to record
the status of the data file backups and logfile backups. This information will allow
mySAP to restore automatically the correct data files and their specific database
transaction log files (redo log files), if necessary. The data files reside in the Oracle
database (Oracle Instance). Data Protection for mySAP runs as a separate process,
independently from the database. It receives the data through the Backint interface
and saves the data to the Tivoli Storage Manager.
A backup run will proceed as follows (see circled numbers):

1. SAPDBA utility BRBACKUP informs Oracle what data has to be backed up and
puts the database into the proper backup state (’online’ or ’offline’).
2. BRBACKUP calls DP for mySAP via the BACKINT interface with a list of all
files to be backed up.
| 3. DP for mySAP reads all requested files from the database and reports back to
| BRBACKUP. BRBACKUP adds these files to the repository containing all
| processed backups.
4. BACKINT saves the data to TSM.
5. SAPDBA updates the file repository, which holds information about the status
of the files.
DP for mySAP and RMAN

| Figure 2 shows the interaction between the BRTOOLS, DP for mySAP, and RMAN
in order to do backup / restores.
Figure 2. DP for mySAP with SAPDBA using the RMAN Interface
| The BRTOOLS use tables in the Oracle database and system data in order to record
the status of the data file backups and logfile backups. This information will allow
mySAP at a later time to restore automatically the correct data files and their
specific database transaction log files. The data files reside in the Oracle database
(Oracle Instance). Data Protection for mySAP runs as a separate process,
independently from the database. It receives the data through the Backint interface
and saves the data to the Tivoli Storage Manager.
A backup run will proceed as follows (see circled numbers):

1. SAPDBA utility BRBACKUP informs Oracle RMAN what data has to be backed
up. The RMAN process puts the database into the proper backup state (’online’
or ’offline’).
2. The Oracle server process loads DP for mySAP and interacts with it through
the Media Management API.
| 3. DP for mySAP reads the requested data from the database and reports back to
| BRBACKUP. BRBACKUP adds these data to the repository containing all
| processed backups.
4. DP for mySAP saves the data to a TSM server.
5. SAPDBA updates the file repository, which holds information about the status
status of the data. RMAN has its own repository, with a control file for a
separate recovery catalog database.
Chapter 2. Developing a Backup Strategy
This chapter helps you define an appropriate backup strategy for your mySAP
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 mySAP 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?
Data Protection for mySAP lets you back up mySAP database data using the SAP
backup interface BACKINT directly to Tivoli Storage Manager storage. However,
these backups, which use the SAP database utilities BRBACKUP and BRARCHIVE,
are only backups of the database or the offline redo logs.
Hence, to protect your complete system against failures affecting SAPDBA or other
mySAP system data, you should use standard Tivoli Storage Manager commands or
the Tivoli Storage Manager graphical user interface (GUI) to additionally backup
| these system data.
To be prepared for recoveries from a severe disaster, the procedures described

below must become an integral part of your overall disaster recovery plan.
Planning a Backup Strategy for the Operating System

In order to be protected against a complete loss of the operating system, it is
imperative that after:
v the installation of the operating system
v updates/upgrades of the operating system
appropriate system backups are made with the operating system dependent
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 user dependent
data.
Planning a Backup Strategy for Your Oracle Database

In order to be able to recover from:
v user errors
v statement failures
v transaction failures
v media failures

that could affect your Oracle database, save the following objects on a regular
basis:
v Data files
v Control files
v Online redo logs
v Offline redo logs
Files belonging to a specific tablespace (data files) are backed up by BRBACKUP.

This is done at the file level, where offline or online backups are possible.
The control file is saved by BRBACKUP whenever a tablespace backup occurs.
Online redo logs are saved by BRBACKUP whenever a full offline database backup
occurs.
Note
Oracle provides mirroring of the control and online redo log files to protect
the running database system against corruption of these active files. (The AIX
LVM facilities can also be used to mirror these files.)
Offline redo logs are saved by BRARCHIVE. You can specify that the redo logs are
to be deleted from their original location when BRARCHIVE completes
successfully. Additional information on BRARCHIVE operations can be found in
Appendix I, “Hints and Tips for SAP Backup Utilities,” on page 163.
Apart from backing up all database relevant data (data files, control file, online
redo log files, and offline redo log files) it is also recommended that you back up
v SAP system data
v Oracle system data
v Operating system data
This data should be backed up with the incremental backup function of the Tivoli
Storage Manager backup-archive client.
Figure 3 on page 7 shows the various backup scenarios within a mySAP database
server machine.
Figure 3. Backup Scenarios Within a mySAP Oracle Environment
The database itself is backed up with Data Protection for mySAP, whereas the SAP,
Oracle and operating system protocols are backed up directly by the Tivoli Storage
Manager.
Planning a Backup Strategy for Backup Protocols and Profiles

Every BRBACKUP and BRARCHIVE run is divided into two parts. The first part
backs up objects such as:
v mySAP data files
v database control files
v online redo log files
v offline redo log files
depending on the action started (see previous section).
The second part of a BRBACKUP or BRARCHIVE is responsible for backing up the

following profiles:
v init<SID>.dba (SAPDBA profile)
v init<SID>.ora (Oracle profile)
v init<SID>.sap (SAP backup profile)
v init<SID>.utl (Data Protection for mySAP profile)
and the protocol files
v back<SID>.log (BRBACKUP summary log)
v arch<SID>.log (BRARCHIVE summary log)
v detailed BRBACKUP/BRARCHIVE log
v reorg<SID>.log (main SAPDBA log)
v struct<SID>.log (structure log)
Chapter 2. Developing a Backup Strategy 7

| These profiles and protocols are required by the BRTOOLS whenever backups or
| restores/recoveries are requested. Unless you also do a file system backup, these
profiles or protocol files can only be restored by Data Protection for mySAP. If one
of these files is lost you can use the Data Protection for mySAP File Manager (see
“DP for mySAP File Manager” on page 55) to restore it before calling BRRESTORE
or BRRECOVER.
In the case of a recovery scenario after a disaster, it may be time consuming to

restore the backup protocols or profiles by means of Data Protection for mySAP or
the Data Protection for mySAP File Manager. Hence, it is recommended that you
back up the directories and file systems containing these files separately.
You can find the files in the following directories:
UNIX or Linux
/oracle/<SID>/sapreorg (SAPDBA and structure logs)

/oracle/<SID>/sapbackup (BRBACKUP logs)
/oracle/<SID>/saparch (BRARCHIVE logs)
/oracle/<SID>/dbs (profiles)
Windows
<drive>:\oracle\<SID>\sapreorg (SAPDBA and structure logs)

<drive>:\oracle\<SID>\sapbackup (BRBACKUP logs)
<drive>:\oracle\<SID>\saparch (BRARCHIVE logs)
<drive>:\orant\database (profiles)
Planning a Backup Strategy for mySAP System Data

In addition to the backup operations performed with BRBACKUP and
BRARCHIVE, you may want to protect your system against the loss of mySAP
system data, user data, or even operating system data that is not stored with
BRBACKUP or BRARCHIVE. You can use the incremental backup capabilities of
the Tivoli Storage Manager backup-archive client to do this.
The Tivoli Storage Manager incremental backup function lets you define an
include-exclude list of files that is applied automatically during incremental backup
operations. This include-exclude list should be used to exclude data already stored
using Data Protection for mySAP. This would be all database relevant data, such as
data files, the control file, and online/offline redo logs. For further information
about include-exclude lists, see your Tivoli Storage Manager manuals, Using the
| Backup-Archive Clients. Examples of include-exclude lists for UNIX or Linux can be
found in “Sample TSM Profiles for UNIX or Linux” on page 159 and for Windows
in “Sample TSM Profiles for Windows” on page 160.
Sample files can be found in your DP for mySAP installation package.
The information saved with the BRBACKUP and BRARCHIVE utilities is usually
located in the following file systems or directories:
UNIX or Linux
/oracle/<SID>/saparch/
/oracle/<SID>/sapdata1/
.
.
.
/oracle/<SID>/origlogA/
/oracle/<SID>/origlogB/
Windows
<drive>:\oracle\<SID>\saparch\
<drive>:\oracle\<SID>\sapdata1\
.
.
.
<drive>:\oracle\<SID>\origlogA\
<drive>:\oracle\<SID>\origlogB\
Add these directories to the list of paths to be excluded in the include-exclude list
of your Tivoli Storage Manager backup-archive client. This will prevent you from
saving the database data twice.
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 mySAP , 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 153.
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/.
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.
Figure 4. Production Backup Example
This example of automated backup operations shows the following typical tasks
v Full database backup, e.g., offline or without application load, performed each
night.
v Offline redo logs 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 mySAP 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 mySAP
| This chapter explains the Data Protection for mySAP architecture and gives an
| introduction to the product features. Even if you are an experienced user of Data
| Protection for mySAP you may want to browse this overview for new features.
| Data Protection for mySAP together with Tivoli Storage Manager provides a
| reliable, high performance, and production-oriented solution that allows you to
| backup and restore your Oracle-based mySAP systems. It is integrated with SAP’s
| backup and recovery utilities SAPDBA, BRBACKUP, BRARCHIVE, BRRESTORE,
| and BRRECOVER, and allows you to follow SAP’s backup and recovery
| procedures. Being optimized for mySAP databases, Data Protection for mySAP
| allows you to manage large volumes of data most efficiently.
|
Scope of Data Protection for mySAP
Figure 5. Scope of Data Protection for mySAP
The SAP utilities for backup and recovery of mySAP databases are focused on the
database objects, where over 90 % of the data on an SAP database server reside.
Thus Data Protection for mySAP will be used for backup and restore of data files,
control files, and online and offline redo logs. (See Figure 5).
Other files such as SAP and Oracle executables can be backed up using the Tivoli
Storage Manager backup-archive client. As a consequence, in the case of a disaster
recovery, you have to make sure that all Oracle and SAP executables are available
before starting restore and recovery of your database using the Data Protection for
mySAP and the SAP utilities.

Integration of Data Protection for mySAP with SAP
Once being configured Data Protection for mySAP operates as an invisible link
between Oracle and the mySAP Database Administration Tools on one hand and
Tivoli Storage Manager on the other.
It provides you with two different adapters supporting different backup and
recovery scenarios:
v backint: an executable that is called directly by SAP. It can be used to perform
full online and offline backups as well as backups of control and redo log files.
v a shared library that is dynamically linked by Oracle’s RMAN (an executable
installed during the Oracle database installation). If a backup is performed using
this library SAP does not communicate with Data Protection for mySAP directly.
It communicates through Oracle’s RMAN process instead. When using RMAN
and this shared library you can perform incremental database backups.
You can configure SAP such that it uses only ″backint″ but you can never
configure it to use only RMAN: backint is always used for the backup of control
and redo log files.
Both adapters - backint and the media management library for Oracle - share a
configuration file init<SID>.utl, which describes how to perform backups and
restores, and which can be used to customize Data Protection for mySAP to your
environment and according to your needs. Both adapters communicate with the
TSM server through an API that is shared with other IBM Tivoli Data Protection
products, and both require that ProLE - a background process that is part of the
Data Protection for mySAP package - is running.
Figure 6. Integration of Data Protection for mySAP with SAP
The Data Protection for mySAP package contains an additional (optional)
component - the Administration Assistant - aimed at increasing the administrator’s
productivity. The functionality covers configuring a DP for mySAP instance, data
| transfer performance monitoring, analysis, and simulation, and monitoring of
| success and failure of backup/restore operations. It allows you to monitor and
| administer all of your Data Protection for mySAP instances remotely.
Storing Data on a TSM Server

Data Protection for mySAP 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’ means backup of data files, ’archive’
| (BRArchive) means the backup of archived redo log files. DP for mySAP
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. In
addition the files sequence from backup is then maintained for restore as well,
which will yield shortest possible restore windows.
For backing up log files it is recommended to use a disk-tape storage hierarchy
and to backup each 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 20 MB 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 mySAP 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 Redo Log Copies” on page 17.
Views of backups on the TSM server can be generated by the SAP administration
tools either by using their own local (detailed) backup log or by inquiring the TSM
server through DP for mySAP. Manual access to the backup repository is provided
through a specific File Manager -backfm - shipped with DP for mySAP. It allows
the administrator to bypass the SAP tools to inquire, delete and restore backups /
files.
Note
DP for mySAP can be configured to use multiple TSM servers to improve
either availability (alternate servers) or performance (multiple servers). DP for
mySAP 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 mySAP profile while they still hold valid backup
data.
Chapter 3. Introducing Data Protection for mySAP 15

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 mySAP backup version control function. Data Protection
for mySAP deletes whole backup generations, i.e. full backups and all related
redo log backups, when the specified number of versions is exceeded.
Note: Since the SAP backup log cannot be updated by DP for mySAP , it may still
contain old backups although they are already deleted (expired).
Performance Options of Data Protection for mySAP

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
thus appears as a bottleneck. Data Protection for mySAP offers a variety of options
to optimize the data transfer rate for each of these components.
Parallel (Multiple) Sessions

Data Protection for mySAP 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 39.
Multiplexing
Multiplexing allows you to simultaneously transfer data from different files
through one session (MULTIPLEXING ) in order to maximize tape performance.
This is useful since tape drives often have higher data transfer rates than the disks
containing the tablespaces of your SAP database. Note that most customers
combine multiplexing and parallel sessions to optimize their overall backup and
restore performance. For more information see on page 88.
Disk Sorting
Data Protection for mySAP deploys Adaptive File Sequencing to minimize the
backup window. It sorts database files in order to avoid simultaneous reading of
files located on the same disk.
Note: Some storage subsystems hide the information required by file sorting. In
order to still provide this sorting function, you can supply the file location
information manually by specifying a manual sort file (SORT_FILE). For more
information see on page 91.
Example: With MULTIPLEXING set to 5 and MAXSESSIONS set to 3 you would

be able to backup 15 files simultaneously to 3 different tapes. Due to disk sorting
these files are chosen such that they are located on separate disks, whenever this is
possible.
Multiple (Parallel) Network Paths and Multiple (Parallel)

Servers
You can configure Data Protection for mySAP 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 mySAP to balance network traffic across all available
network connections to the TSM server. For details see “Multiple Network Paths”
on page 40 and “Multiple Servers” on page 40.
| Incremental Backup
Data Protection for mySAP supports incremental RMAN-backup of an SAP
database. Depending on the system environment, this may result in decreased
backup times.
Individual Tablespace Locking

To minimize the amount of archived redo logs during online backup operations,
Data Protection for mySAP can notify the SAP database utilities for which
tablespaces it is going to back up files. The SAP utilities then switch those
tablespaces into backup mode. After the files are backed up, the tablespaces are
released again and a new cycle starts. This mode (util_file_online) is set with a
parameter in the SAPDBA profile setup. For more information see on page 29.
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 41.
Automation Options of Data Protection for mySAP

Data Protection for mySAP 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 mySAP to backup directly
into a tape storage pool and to archive log files into a disk storage pool. In
addition multiple management classes have to be used in conjunction with
multiple redo log copies. For information how to specify management classes, see
the profile keywords BRARCHIVEMGTCLASS and BRBACKUPMGTCLASS
starting on page 84.
Retain Backups by Version

This function enables you to limit the number of full backups kept on the TSM
server. If you have more than MAX_VERSIONS of full backups on a TSM server
the oldest versions are deleted. This function keeps track of all redo log files,
database control files, partial and incremental backups, depending on a full
backup: All these objects are removed together with a full backup.
Multiple Redo Log Copies

As protection against tape defects and to improve availability and disaster
recovery, you can backup multiple copies of a log file and configure your system
such 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 mySAP automatically switches to another copy and

continues restoring from the log file from that copy. For more detailed information
about creating and using multiple Redo Log Copies, see the profile keyword
REDOLOG_COPIES on page 89.
Alternate Network Paths and Servers

Similar to the configuration of multiple network paths and servers, you can
configure Data Protection for mySAP 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 mySAP 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 mySAP to send different
| classes of log messages to a TSM server.
Frontend/Backend Processing
Data Protection for mySAP allows you to register applications that are executed
before starting a backup/restore operation and after it has completed. For more
information see on pages 84 and 86.
Productivity Options of Data Protection for mySAP
Reporting
Data Protection for mySAP can be configured to produce a report at the end of a
backup. This report provides statistical information such as the number of bytes
that are transferred through the network and the effective data throughput. During
a backup or restore it calculates and displays an estimated end time of the
operation.
By using the Administration Assistant contained in the Data Protection for mySAP
package you are provided with detailed performance reports, that help you to
optimize your systems. In addition you can retrieve backup status informations
such as success or failure of a backup across all of your SAP instances. For more
information see on page 89.
Monitoring the Backup Status

The Administration Assistant contained in the Data Protection for mySAP package
allows you to monitor the backup status of several mySAP database servers via a
graphical user interface. For more details, see Chapter 8, “Installing and Using the
Administration Assistant for Data Protection for mySAP,” on page 59.
Performance Analysis
| The Administration Assistant contained in the Data Protection for mySAP package
| 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 more details,
| see Chapter 9, “Balancing Your System,” on page 69.
| The Administration Assistant contained in the Data Protection for mySAP package
| supports the simulation of both backup and restore operations. This way, the
| effects of configuration changes as well as the restore of a production backup can
| be tested without compromising the productive system. For more details,
| seeChapter 9, “Balancing Your System,” on page 69.
Tracing
Data Protection for mySAP can write trace information into a file to help analyze
problems. You should contact your DP for mySAP support before you use this
function.
Using FlashCopy to Minimize Backup and Restore Windows
Integration with Data Protection for IBM Enterprise Storage

Server (ESS) for mySAP
Although Data Protection for mySAP provides extensive methods to minimize
down-times, your service level agreements for business-critical databases might
demand even faster recovery operations. Data Protection for mySAP together with
the companion product IBM Tivoli Storage Manger for Hardware. Data Protection for
IBM ESS for mySAP allows you to perform FlashCopy backups and FlashBack
restores if you are running your SAP database on an IBM Enterprise Storage Server
(ESS). Using these features you can keep your production downtime at a minimum
by exploiting the FlashCopy capability of the ESS.
More information on Data Protection for IBM ESS for mySAP can be found at:
http://www.ibm.com/software/tivoli/products/storage-mgr-hardware/.
More information on the IBM Enterprise Storage Server can be found at:
http://www.storage.ibm.com/disk/ess/index.html/ess.htm.
Archiving Inactive Data

| DP for mySAP 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 SAP1 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)
1. Note, that the product named ’DB2 CommonStore for SAP’ is database independent and therefore can also be used with Oracle.

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 1, see:

http://www.ibm.com/software/data/commonstore/sap/.
Part 2. Installing and Using

Chapter 4. Installing or Upgrading Data Protection for mySAP
DP for mySAP must be installed on any system that is to be used as mySAP
database server. In order to set up DP for mySAP, do the following:
1. Check if the DP for mySAP package is complete. The package includes this
manual and machine readable material on a CD-ROM. See the Readme file for:
v A table of contents of the package
v Up-to-date news
2. Make sure that the requirements are met.
For details, see “Prerequisites for the Installation of Data Protection for mySAP”
below.
3. Get planning information.
For details, see “Installation Planning for Data Protection for mySAP” on page
24.
4. Install Data Protection for mySAP.
For details, see “Installing Data Protection for mySAP” on page 25.
5. Perform post-installation steps as described in “Post-Installation Steps” on page
28.
6. Verify the installation.
For details, see “Verifying the Installation” on page 29.
If you are going to do an upgrade installation, please turn to “Upgrade Installation

(Migration)” on page 25.
Data Protection for mySAP can be installed and operated for mySAP systems with
Oracle databases employing a standard file system or raw logical volumes.
| Differences Between UNIX or Linux and Windows Systems
| There are only small differences between the UNIX or Linux and Windows
| versions of Data Protection for mySAP. 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 mySAP will be mentioned
explicitly.
Prerequisites for the Installation of Data Protection for mySAP

The following products must be installed before you can start setting up Data
Protection for mySAP:
v Oracle Database,
| v SAP R/3 or mySAP e-business Solution, based onOracle,
v Tivoli Storage Manager (TSM),
v An Operating System at a level supported by mySAP 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
mySAP refer to the Release Notice (RELNOTE).

For information on the functions, product versions, and maintenance levels that are
compatible with your version of SAP R/3 or mySAP, consult SAP support, for
example via the Online Service System (OSS). The appropriate modules can be
downloaded from the SAP server. Information about this can be found in OSS note
19466.
| For information on configuration of the Tivoli Storage Manager API client, refer to
| Appendix F, “Preparing Tivoli Storage Manager for DP for mySAP,” on page 143.
| For DP for mySAP, the Tivoli Storage Manager API Client will be installed with the
| DP for mySAP package.
TCP/IP must be ready for communication between the Tivoli Storage Manager
server and the Tivoli Storage Manager client.
Installation Planning for Data Protection for mySAP

When starting the installation procedure, be prepared to provide the required
information. For your convenience, an installation planning sheet is available in
Appendix D, “Installation Planning Sheet,” on page 135 and in file planning_sheet
| (UNIX and Linux) or planning_sheet.txt (Windows) on the CD-ROM.
The following information must be available when planning for installation:

v Oracle database SID.
v For Windows only: Installation path for Data Protection for mySAP
v For Windows only: Path where the executables for the SAP backup tools reside.
v Tivoli Storage Manager server name. Name or IP address of your TSM server.
v Tivoli Storage Manager 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 146.
v 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 145.
v For Windows only: Full path of client option file for Tivoli Storage Manager
(contents of environment variable DSMI_CONFIG). For details, refer to the Tivoli
Storage Manager documentation.
v For Windows only: Path for 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.
| v Path for Data Protection for mySAP configuration files.
| During the installation, the Data Protection for mySAP configuration files will be
| saved to this path. If old configuration files are found, they are renamed to
| <filename>.nnn, where nnn is a three-digit decimal number.
Note that this path must not contain blanks.
| v Decide whether to use RMAN. For details, refer to Chapter 6, “Using DP for
| mySAP with RMAN,” on page 51.
v Administration Assistant server. Name or IP address of your Administration
Assistant server.
It is recommended but not required that the Administration Assistant is installed
beforehand.
If you do not specify the Administration Assistant server at installation time, it
will not be configured. A procedure for specifying the Administration Assistant
server after the installation is complete is described in “Adjustments for the
Administration Assistant” on page 42.
For more information on the Administration Assistant, refer to Chapter 8,
“Installing and Using the Administration Assistant for Data Protection for
mySAP,” on page 59.
v Administration Assistant server port. Port the Administration Assistant server is
listening to for connect requests from Data Protection for mySAP. If the
Administration Assistant server was started with the default parameters the port
number is 5126.
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 mySAP

| There are three types of installation: initial installation, upgrade installation
| (migration), and TSM API installation.
Initial Installation
Initial installations must always be done from the Data Protection for mySAP
CD-ROM. Refer to the file README.1st in the root path for information on where to
find documents on your CD-ROM, and follow the appropriate installation
description below.
Upgrade Installation (Migration)

If you are going to upgrade from an earlier version of Tivoli Data Protection for
R/3 or Data Protection for mySAP in your environment, you have the option to
either upgrade from the product CD-ROM, or to download the latest version from
the IBM download site:
http://www.ibm.com/software/sysmgmt/products/support/...
...IBMTivoliStorageManagerforEnterpriseResourcePlanning.html
For a specific procedure of upgrading from an earlier version, refer to “Upgrading

(Migration)” on page 31.
| TSM API Installation

| Starting with version 5.3 of DP for mySAP, the Tivoli Storage Manager Client API
| is delivered and installed automatically with DP for mySAP. The API will be
| installed in the following locations:
| v AIX: /usr/tivoli/tsm/client/api
| v Linux: /opt/tivoli/tsm/client/api
| v Solaris: /opt/tivoli/tsm/client/api
| v HP-UX: /opt/tivoli/tsm/client/api
| v Windows: %ProgramFiles%\Tivoli\tsm\api
Installing Data Protection for mySAP on AIX, HP-UX, Linux,

Solaris
| Data Protection for mySAP for these operating systems is delivered as a single
| executable file.
Chapter 4. Installing or Upgrading Data Protection for mySAP 25

| Depending on whether DP for mySAP was obtained from a CD or from the web,
| the name of the single executable file differs.
| v If obtained from a CD, the name is:
| install_tdpr3_ora_<operating system>_<32bit|64bit>.bin
| v if obtained from the web, the name is
| web_tdpr3_ora_<operating system>_<32bit|64bit>.bin
| where
| <operating system> is aix43 for AIX 4.3, or
| aix51 for AIX 5.X, or
| solaris or
| hpux or
| linux
| When you invoke the file, you will be guided through the Data Protection for
| mySAP 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.
| To install Data Protection for mySAP on a UNIX or Linux system, do the

following:
1. Read the Release Notice (RELNOTE) and the README file provided with Data
Protection for mySAP.
2. Log in as root user on the mySAP database server machine.
3. Ensure that you have set the DISPLAY variable correctly as the installer guides
you through the installation via a graphical X-Window.
4. Invoke the installation file for DP for mySAP that fits your operating system
and your Oracle database.
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 mySAP.
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

automatically:
v an entry is created in/etc/inittab to start the background process ProLE
v an entry is created in/etc/services needed for internal communication.
After the installation, the following files are available on your system:
v In the installation path of DP for mySAP:
backint
ProLE
createinfo
backfm
initSID.bki
libtdp_r3.<ext>
archive.ksh
backup.ksh
crontab.sample
dsm.opt
dsm.sys
gensortfile.sh
inclexcl.list
README
RELNOTE
TIPHINTS
a folder named _uninst is created, which contains several files.
v The DP for mySAP configuration files under the SAP directories (typically,
/oracle/SID/dbs) are as follows:
init<SID>.utl, where ’SID’ is replaced by the Oracle database SID provided
during installation
init<SID>.bki, where ’SID’ is replaced by the Oracle database SID provided
during installation
agent.lic (Only after installation from CD-ROM, this is not contained in the
web package).
Installing Data Protection for mySAP on Windows

DP for mySAP for Windows is delivered as a single executable file.
| Depending on whether DP for mySAP was obtained from a CD or from the web,
| the name of the single executable file differs.
| v If obtained from a CD, the name is:
| install_tdpr3_ora_win_<32bit|64bit>.exe
| v if obtained from the web, the name is:
| web_tdpr3_ora_win_<32bit|64bit>.exe
To install DP for mySAP on a Windows system, do the following:

1. Read the RELNOTE and the README file provided with DP for mySAP.
2. Log in as user with administrator authority on the mySAP database server
machine.
| 3. In Windows Explorer, navigate to the directory where the installation package
| is located.
4. Invoke the executable mentioned above 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 mySAP.
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 for the background process ProLE a service is created.
v an entry is created in %WINDIR%\system32\drivers\etc\services needed for
internal communication.
After the installation, the following files are available on your system:
v In the installation path of DP for mySAP:
backint.exe
createinfo.exe
ProLE.exe
orasbt.dll
backfm.exe
archive.cmd
backup.cmd
dsm.opt
server_a.opt
server_b.opt

inclexcl.list
schedule.sample
README
RELNOTE
TIPHINTS
A folder named _uninst is created, which contains several files.
v In the path of the DP for mySAP configuration files:
initSID.bki, where ’SID’ is replaced by the Oracle database SID provided
during installation
initSID.utl, where ’SID’ is replaced by the Oracle database SID provided
during installation
agent.lic (Only after installation from CD-ROM, this is not contained in the
web package).
Post-Installation Steps
After successfully completing the installation dialog for DP for mySAP, you need
to perform the following steps in order to get a properly running system:
1. review the TSM Option file
2. set the password (initial password)
3. verify the installation
Review of the TSM Options Files

The TSM 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 same directory where dsm.opt is located. <servername> is the name
you specified in init<SID>.utl.
Set the Password

DP for mySAP should be installed after the TSM installation has been completed.
TSM provides different password methods to protect data. DP for mySAP must use
the same method as specified within TSM. When DP for mySAP 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 mySAP are set according to this assumption. If a different password
method is set within TSM, refer to “Password Handling” on page 149 in order to
adjust the DP for mySAP parameters.
To be able to work with DP for mySAP, you have to provide DP for mySAP with
the password for the TSM node.
This is a manual step on the shell:
v Log on as Oracle user.
v Enter the following command
for Windows:
backint -p <full path to UTL file>\init<SID>.utl -f password
| for UNIX or Linux:

backint -p <full path to UTL file>/init<SID>.utl -f password
v Enter the password when prompted.
| Note: On HPUX only a password with a maximum of 8 characters is processed.

| Ensure that the password for HPUX clients in the TSM server does not exceed this
| limit.
Verifying the Installation

Preparing the Verification
Before verifying the installation, make sure that:

| v all files in the DP for mySAP installation directory on UNIX or Linux systems
have the owner root, the group system, and execute permissions for all users.
v the sticky bit must not be set for the installed executables.
| v the SAP Backup profile is configured properly. This profile can be found on
| UNIX or Linux systems in the path $ORACLE_HOME/dbs and on Windows systems
| in the path %ORACLE_HOME%\database.
| This configuration refers to three keywords within that profile. These keywords
| are:
backup_type
Identifies the default type of the database backup. This parameter is
only used by BRBACKUP (default is offline).
backup_dev_type
| Determines the backup medium that will be used (default is tape). In
| order to use the backint interface this parameter must be set either to
| util_file or util_file_online (see table below).
util_par_file
This parameter specifies where the parameter file, which is required for
a backup with an external backup program, is located.
DP for mySAP supports, for example, the combinations of the keywords

backup_dev_type and backup_type shown in the table below.
Table 1. SAP Backup Profile Parameter Combinations
Operation backup_dev_type backup_type
Offline backup util_file offline
Online backup util_file online
Online backup with util_file_online online
individual tablespace
locking
To carry out online backups with individual tablespace locking with the external
backup program DP for mySAP, the SAP Backup profile parameter must be set
or changed as shown below:

backup_type = online
backup_dev_type = util_file_online
util_par_file = ?/dbs/init@.utl
The question mark is the official Oracle substitute symbol for the home directory
of the database system. This is specified in the environment variable
ORACLE_HOME.
The @ is the official Oracle substitute symbol for the home directory of the
database system. This is specified in the environment variable ORACLE_SID.
| Executing the Verification for Initial and Upgrade Installations
To verify and test the installation, it is recommended that you try out a small
backup procedure (tablespace backup) using SAPDBA and start a full online or
offline backup using BRBACKUP as shown below.
brbackup -c -t online
brbackup -c -t offline
It is strongly recommended that you do a restore/recovery of the whole mySAP

database (using SAPDBA). A good method to prepare for this is to first run a
complete offline backup using BRBACKUP.
Step by step scenarios for backup or restore/recovery procedures of a mySAP

Oracle database using DP for mySAP can be found in the IBM redbook R/3 Data
Management Techniques Using Tivoli Storage Manager, SG24–5743.
IBM redbooks can be found at http://www.redbooks.ibm.com.
For backup tests, the SAP database utilities SAPDBA, BRBACKUP, and
BRARCHIVE should be used. For restore or recovery it is recommended that only
SAPDBA or BRRECOVER is used.
| Executing the Verification for TSM API Installations
| 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 Linux: rpm -q TIVsm-API
| should respond with:
| TIVsm-API-<version>
| v Solaris: pkginfo TIVsmCapi
| should respond with:
| application TIVsmCapi Tivoli Storage Manager Solaris <version> API Client
| v HP-UX: swlist TIVsm.CLIENT_API
| should repond with:
| TIVsm.CLIENT_API 5.3.X TSM API Client Files <files>
Upgrading (Migration)
Upgrading Data Protection for mySAP

In order to upgrade DP for mySAP from an earlier version of Tivoli Data
Protection for R/3 or DP for mySAP.com, do the following:
1. Check if the DP for mySAP package is complete. The package includes this
manual and machine readable material on a CD-ROM. See the Readme file for
v A table of contents of the package
v Up-to-date news
| Note: If DP for mySAP was obtained for migration from the web, the name of
| the single executable file starts with ’web’.
| If it was obtained from a CD, the name starts with ’install’.
| See “Installing Data Protection for mySAP on AIX, HP-UX, Linux,
| Solaris” on page 25 or “Installing Data Protection for mySAP on
| Windows” on page 27 respectively.
2. Check the release notice (file RELNOTE) 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 mySAP can still be
restored with the version you are going to install.
v Data that was backed up with Tivoli Data Protection for R/3 Version 2.7
must be restored with Tivoli Data Protection for R/3 Version 3.1 or Version
3.2.
v Data that was backed up with Tivoli Data Protection for R/3 Version 3.1 or
Version 3.2 or Data Protection for mySAP.com Version 3.3 can be restored
with Data Protection for mySAP.com Version 3.3. or higher.
3. Make sure that the requirements for the new version of DP for mySAP are met.
For details, see“Prerequisites for the Installation of Data Protection for mySAP”
on page 23.
4. Get or retrieve planning information. For details, see “Installation Planning for
Data Protection for mySAP” 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 the uninstallation procedure, see “Uninstalling
Data Protection for mySAP” on page 32.
7. Install the new version of DP for mySAP. For details, see “Installing Data
Protection for mySAP” on page 25.
8. Verify the installation. For details, see “Verifying the Installation” on page 29.
9. We recommend a full backup after upgrading to the new version.
Special Installation
Silent Installation
Installation can be done from the command line. For a preparation for silent
installation, you have to record the installation options. This can be done by:
install_tdpr3_ora_<operating system> -options-record <filename>
where <operating system> is:

aix43 for AIX 4.3, or

aix51 for AIX 5.x, or
solaris, or
win for Windows.
This creates an options file that can be checked easily and can be modified to be
| used for an installation on various systems.
To do a silent installation, the install package must be called with the recorded
options file:
install_tdpr3_ora_<platform> -options <filename> -silent
where <operating system> is:

aix43 for AIX 4.3, or
aix51 for AIX 5.x, or
solaris, or
win for Windows.
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
command prompt window.
To start the console installation, enter the following command:

| install_tdpr3_ora_<platform> -options <filename> -is:javaconsole -console
In addition, you can also record the installation options in a file. You do this by
issuing following command:
| install_tdpr3_ora_<platform> -options-record <filename> -is:javaconsole -console
Firewall Installation
If you need to install DP for mySAP remotely through a firewall and if the TCP
port for X11 communication is not enabled, use the console installation as
described above in “Console Installation.”
Uninstalling Data Protection for mySAP

Before upgrading the old version of DP for mySAP 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. If you had installed the old
version of Data Protection for mySAP also for databases other than Oracle, you
only have to uninstall that old version of DP for mySAP for Oracle.
| Uninstalling the old Version of DP for mySAP from UNIX and

| Linux
To uninstall the old version of DP for mySAP, perform the following steps:
| 1. Log in as root user on the mySAP database server machine.
2. Make sure that the DISPLAY variable is set correctly as the uninstall procedure
requires a graphical X-Window.
3. Make sure the old version of DP for mySAP is not running.
4. Call the uninstaller executable and follow the instructions of the uninstall
procedure. The executable is located in one of the following directories:
v AIX 32-bit
/usr/tivoli/tsm/tdp_r3/ora/_uninst/uninstaller.bin
v AIX 64-bit:
/usr/tivoli/tsm/tdp_r3/ora64/_uninst/uninstaller.bin
| v other UNIX 32-bit or Linux 32-bit
/opt/tivoli/tsm/tdp_r3/ora/_uninst/uninstaller.bin
| v other UNIX 64-bit or Linux 64-bit
/opt/tivoli/tsm/tdp_r3/ora64/_unist/uninstaller.bin
Uninstalling the old Version of DP for mySAP from Windows

To uninstall the old version of DP for mySAP on a Windows NT or Windows 2000
or Windows 2003 machine, perform the following steps:
| 1. Log on as user with administrator authority on the mySAP database server
machine.
2. Ensure that the old version of DP for mySAP is not running.
3. Select Start → Settings → Control panel.
4. Click on Add/Remove Programs.
5. Select the old version of DP for mySAP and click on Remove.
6. Follow the instructions of the uninstall procedure.

Chapter 5. Adjusting Your System
This chapter is intended to help you find the configuration of Data Protection for
mySAP that best fits your needs.
You may want to adjust Data Protection for mySAP to:

v Optimize the performance of your data protecting environment, or to
v Change the way Data Protection for mySAP interacts with components like
| Tivoli Storage Manager and the DP for mySAP Administration Assistant and
| RMAN.
General Performance Considerations

A simplistic model of the data transfer via Data Protection for mySAP is comprised
of three components (see Figure 7):
v the mySAP database server
v the network
v the TSM server also known as backup server
Figure 7. 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.

Database Server Considerations
In most cases, the production (mySAP database) server is the most critical
component for data transfer when the various techniques of parallelism are
applied (see ’Adjustments to DP for mySAP 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. DP for mySAP allows parallel access to data
base files 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 2 (see “Archiving Inactive Data” on page 19).
| v Size of database files. Using multiplexing with the file interface yields the best
| results when the files to be multiplexed are of the same size. DP for mySAP tries
| to find files of similar sizes for multiplexing. Therefore, we recommend to define
| rules for the sizes of database files ensuring that similar files are of the same size
| and avoiding many different file sizes.
| v Backup types. Online backups save database files, control files, and redo logs
| non-disruptively. On the other hand, more data are saved to redo log files
| during an online backup. The amount of data saved to redo logs during an
| online backup may be decreased when using the file-online mode provided by
| SAP, while such a backup will take longer. Incremental backups will reduce the
| backup time and the amount of data to be sent to the backup server while
| restore time may be increased. For incremental backups, the Oracle RMAN must
| be employed.
| For more details on backup options, refer to your Oracle and SAP
| documentation.
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.
2. Note, that the product named ’DB2 CommonStore for SAP’ is database independent and therefore can also be used with Oracle.
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 J, “Hints and Tips for
Network Settings,” on page 177.
v Multiple Paths. Data Protection for mySAP 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 40.
More hints on network settings are given in Appendix J, “Hints and Tips for
Network Settings,” on page 177.
Backup Server Considerations

Note: For all backup activities, Data Protection for mySAP 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
mySAP can be found in Appendix E, “Alternate/Parallel Backup Paths and Backup
Servers,” on page 137 and Appendix F, “Preparing Tivoli Storage Manager for DP
for mySAP,” on page 143.
Adjustments to DP for mySAP for Improving Performance of Data

Transfer
After the primary installation, Data Protection for mySAP is configured to send
uncompressed backup data to a TSM server via a single session.
Chapter 5. Adjusting Your System 37

Figure 8. Data Transfer for a Backup / Restore
When tuning Data Protection for mySAP, 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 69 or you may want to tune your
| system in the following order:
| 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” on page 39.
| 4. Increase the number of network paths or TSM servers. See “Multiple Network
| Paths” on page 40 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 9. Multiplexing
| The value of keyword MULTIPLEXING defines the number of files read in

| parallel within a single session. Appropriate MULTIPLEXING values are expected
| in the range of 1 to 4. The best value for your environment depends on the I/O
| rate of your disks, the location of your data on the disks, the network capacity, the
| throughput rate of the storage media, and the compression factor to be achieved. A
| way to determine the optimum MULTIPLEXING value is to analyze DP for
| mySAP performance with the Administration Assistant. For details, refer to
| Chapter 9, “Balancing Your System,” on page 69.
| Note: If the value is chosen too high this may result in a noticeable overhead in
| thread management offsetting the performance gain.
| See also keyword MULTIPLEXING on page 88.
Multiple Sessions
Data Protection for mySAP 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 10. Parallel (Multiple) Sessions
The keywords MAX_SESSIONS, MAX_BACK_SESSIONS,

MAX_ARCH_SESSIONS and MAX_RESTORE_SESSIONS are 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 these keywords, refer to page 87.
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
BRBACKUPMGMTCLASS in the DP for mySAP profile (see on page 85).
When setting up the Tivoli Storage Manager, make sure to

v do not activate collocation in the (tape) storage pool defined for the management
class chosen as BRBACKUPMGMTCLASS
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 log file backups, either disk or tape storage pools
can be utilized. These must be available to the management class defined as
BRARCHIVEMGMTCLASS in the Data Protection for mySAP profile (see on page
84).
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 log file. For details, see keyword REDOLOG_COPIES on page 89.
Multiple Network Paths

Data Protection for mySAP allows you to use multiple network connections (paths)
for data transfer between the database server and the backup server.
Figure 11. 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
backup server. For each adapter of the backup server, a server statement must be
entered in the Data Protection for mySAP profile (see keyword SERVER on page
90).
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 E, “Alternate/Parallel Backup Paths and Backup Servers,” on page 137.
Multiple Servers
Data Protection for mySAP allows you to use multiple backup servers.
Figure 12. Multiple Servers
Multiple servers can be used by DP for mySAP 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 mySAP profile (see
keyword SERVER on page 90).
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.
| If used with RMAN, the number of SESSIONS configured for each SERVER must
| be equal or higher than the number of sessions configured for restore
| (MAX_SESSIONS). Otherwise Oracle RMAN may request more objects in parallel
| from the same server than sessions are configured for that server.
The setup for parallel servers is described in detail in Appendix E,

“Alternate/Parallel Backup Paths and Backup Servers,” on page 137.
Compression
Figure 13. Null Block Compression
By compressing zero-byte blocks, a very simple, but fast compression method, Data
Protection for mySAP 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 mySAP compression, refer to keyword
RL_COMPRESSION on page 90.
| Buffer Copies
| Data Protection for mySAP 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 mySAP 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 Linux or <server.opt> on Windows), buffer copies cannot be
| prevented. See also keyword BUFFCOPY on page 85.
Buffer Size
Data Protection for mySAP 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
85.
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 mySAP and the
Administration Assistant. This is usually done during installation of Data
Protection for mySAP. If you entered the Administration Assistant information
during installation, Data Protection for mySAP connects and sends data to the
Administration Assistant during backup and restore runs.
If you did not specify the use of the Administration Assistant during installation of
DP for mySAP, you can set up the connection by following the description given in
“Specifying an Administration Assistant Server” below.
Specifying an Administration Assistant Server

If you need to specify a new Administration Assistant Server, perform the steps
described below on the database server.
| Specifying an Administration Assistant Server on UNIX and Linux

1. Find the entry for daemon ProLE in /etc/inittab. Modify the entry to read:
| /prole -p tdpr3ora | tdpr3ora64 <AA server name> <port>
| where
<AA server name> is the name or IP address of the Administration Assistant
server and
<port> is the port that the Administration Assistant is listening to, the default is
5126.
2. Make sure that DP for mySAP 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 on Windows
Log in as a user with administrator authority. From a command prompt, issue:

| prole -update <AA server name> <port>
where
<AA server name> is the name or IP address of the Administration Assistant server
and
<port> is the port that the Administration Assistant is listening to, the default is
5126.
Adjustments for IBM Tivoli Storage Manager

After the primary installation, Data Protection for mySAP is configured to send
data to a single backup server; manual password handling is assumed and Data
Protection for mySAP 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 mySAP profile.
2. Adapt the TSM options files as described in “Review of the TSM Options Files”
on page 28.
3. Set and save the TSM password for the new server as described in “Set the
Password” on page 28.
Alternate Network Paths and Servers

When setting up multiple network paths and multiple backup servers you may
decide to use them alternatively 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 mySAP will use the first sessions it
can establish, up to the number defined for keyword MAX_SESSIONS (see on
page 87). 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 92).
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. Every 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 mySAP 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 mySAP 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
mySAP 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
for Windows:
backint -p <full path to UTL file>\init<SID>.utl -f password

backint -p <full path to UTL file>/init<SID>.utl -f password
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
| mySAP (command as shown above). 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.
| 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 are planning to use Oracle RMAN and 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 mySAP 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:
| for Windows:
| backint -p <full path to UTL file>\init<SID>.utl -f password
||

| backint -p <full path to UTL file>/init<SID>.utl -f password
||
| 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 149.
Backup Version Control

Data Protection for mySAP 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 and
redo log 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 and redo log 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 88.
Adjustments for High Availability
Considerations for Using IBM HACMP for AIX

This chapter is intended to give a short introduction to the way DP for mySAP
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.
The following figure illustrates the takeover environment:
Figure 14. Sample Environment for HACMP Takeover
DP for mySAP Internals

Files:
v The installation directory is /usr/tivoli/tsm/tdp_r3.
| v Lock files and disk sorting 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 DP configuration files (init<SID>.utl,
| init<SID>.bki) in $ORACLE_HOME/dbs.
Dependencies:
v Both hosts should have the same level of Tivoli Storage Manager API installed.
| v Both hosts must be Data Protection for mySAP.
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:
Backint connects to prole using the following procedure:

v Get the IP address for localhost (should be 127.0.0.1 ).

| v Get the backint service (should be 57322 for the 32 Bit Version and 57324 for the
| 64 Bit Version).
| v Connect to 127.0.0.1:<backint service>.
Installation and Setup

Installation:
A prerequisite for installation is a correct setup of the TSM client. The installation
steps for the TSM Backup/Archive Client for AIX can be found in the
documentation Tivoli Storage Manager Installing the Clients.
Defining DP for mySAP as an HACMP Application: To enable DP for mySAP to

participate in HACMP failover processing, it must be defined as an application to
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.
Start Script
Enter the full pathname of the script that starts the server (for example,
/usr/sbin/cluster/events/utils/start_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 start the server.
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 mySAP 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 mySAP Application to an HACMP Resource
Group
A final step in enabling Data Protection for mySAP 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.
The TSM client application should be added to the same resource group that
contains the file systems it will back up. The file systems defined in the resource
group should also be the ones specified in the domain for this client instance in the
client user options file.
Note that both JFS and NFS file systems can be defined as cluster resources,
although NFS supports only 2 node clusters in a cascading takeover relationship.

Sample Start Script
The only purpose of this script is to update DP for mySAP’s volume information
after a takeover and after all SAP file systems are mounted, because there are more
filesystems and disks available. This file is used by the DP for mySAP disk sorting
function and may have an impact on performance. The start script is used in the
following cases:
v HACMP is started and resource groups are ″activated″
v a failover occurs and the resource group is started on another node
v fallback occurs (a failed node re-enters the cluster) and the resource group is
transferred back to the node re-entering the cluster.
The start 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 the DP for mySAP in an HACMP #
# environment. It should be reviewed and customized to meet your specific client #
# environment #
# #
# #
# Name: start_tdpr3.sh #
# #
# Function: #
# A sample shell script to start the disk sorting function for DP for mySAP #
# #
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
if ["$VERBOSE_LOGGING"="high"]
then
set -x
fi
START_DISKINFO()
{
# It is assumed that ’prole’ is already running
# Start createinfo in the background.
nohup /usr/bin/createinfo &
}
# This starts the disk info process to allow disk sorting for the taken-over SAP instance.
START_DISKINFO
Exit 0
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 R/3. 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 mySAP in an HACMP #
# environment #
# It should be reviewed and customized to meet your specific environment #
# #
# #
# Name: stop_tdpr3.sh #
# #
# Function: A sample shell script to update the disk information after the #
# mySAP instance is unmounted. #
# #
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
if ["$VERBOSE_LOGGING"="high"]
then
set -x
fi
| # Function to update all disk information for DP for mySAP

| START_DISKINFO()
{
# 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 DP for ESS for mySAP, this may leave the ESS in an
| # inconsistent state.
# kill –9 `cat /var/tdp_r3/prole.pid`
# Start createinfo in the background to update the disk information. This should be done
# after all SAP file systems are umounted.
nohup /usr/bin/createinfo &
}
# This starts the disk info process to update the disk information.
START_DISKINFO
Exit 0

Chapter 6. Using DP for mySAP with RMAN
You can use the Recovery Manager (RMAN) to do a backup, restore and recover
operation of an Oracle database. Furthermore, if you want to make incremental
backups, this can only be done with RMAN.
Note
Check the Online Service Support (OSS) system from SAP on how to set up
backup via RMAN on your operating system. Check also for special
considerations for the database version you are using.
Running with RMAN, Data Protection for mySAP is loaded by one or more Oracle
processes as shared library. These Oracle processes will then decide on how many
parallel sessions are opened, when a session is opened and closed, which data
object (e.g. table space) will be included into which session and more. Some of the
above mentioned parameters must be configured for RMAN. Depending on how
you are using RMAN you can configure these parameters either within the RMAN
script or the BR*Tools configuration file (init<SID>.sap).
If you want to use parallel sessions with RMAN make sure you configure at least
the same number of sessions within the Data Protection configuration file as you
configure for RMAN (see also “Multiple Sessions” on page 39 and “Multiple
Servers” on page 40).
| RMAN Setup on UNIX and Linux Systems

| 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 2. File Extensions for Shared Libraries
Operating System Extension
AIX a
HP-UX sl
Linux so
Solaris so
In the following description you have to replace the directory name ora<bit> in
the installation path. Depending on the version of DP for mySAP you have
installed, you must replace it with
ora for the 32–bit version of DP for mySAP
ora64 for the 64–bit version of DP for mySAP.
| To set up your DP for mySAP for use with RMAN under UNIX or Linux, follow
these steps:
1. Install Tivoli Storage Manager API Client on your mySAP database server (see
“Configuring the Tivoli Storage Manager Clients” on page 147).

2. Install DP for mySAP on your mySAP database server (see Chapter 4,
“Installing or Upgrading Data Protection for mySAP,” on page 23).
3. Set DP for mySAP password for Tivoli Storage Manager (see “Modifying the
Handling of the TSM Password” on page 43).
4. Ensure /usr/lib is in the library path environment of your system.
5. Shut down the database and link the library shipped with DP for mySAP
(libtdp_r3) with RMAN as follows:
v in case of Oracle 8.0
cd $ORACLE_HOME/rdbms/lib
ln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libobk.<ext>
make -f ins_rdbms.mk ioracle LLIBMM=/usr/lib/libobk.<ext>

ln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libobk.<ext>
make -f ins_rdbms.mk ioracle LLIBOBK=/usr/lib/libobk.<ext>

ln -s /usr/tivoli/tsm/tdp_r3/ora/libtdp_r3.<ext> /usr/lib/libobk.<ext>
ln -s /usr/lib/libobk.<ext> $ORACLE_HOME/lib/libobk.<ext>
make -f ins_rdbms.mk ioracle LLIBMM=/usr/lib/libobk.<ext>
6. Customize the SAP backup profile init<SID>.sap for use with RMAN. Insert
the following:
backup_dev_type=rman_util
rman_parms="ENV=(XINT_PROFILE=/<path>/init<SID>.utl,PROLE_PORT=portnumber)"
The appropriate Prole port number can be found in the /etc/services file.
Further Hints
1. Ensure that Oracle has linked the right library
/usr/lib/libobk.<ext> linked to
/usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>
2. Remove the library in /$ORACLE_HOME/rdbms/lib/libobk.<ext>.
If you are running a 64–bit Oracle 8.x database system, also check in
/$ORACLE_HOME/rdbms/lib64/.
3. The shared library must have the same bitwidth as the installed Oracle
version: if you have a 64–bit Oracle running on AIX 5.2 64–bit, you need to
install the 64–bit version of DP for mySAP.
If you have a 32–bit Oracle running on a 64–bit AIX 5.1, you need to install
the 32–bit version of DP for mySAP.
Both versions of DP for mySAP can coexist on one machine.
4. Examine the sbtio.log located in the directory specified in the
user_dump_dest keyword within the Oracle profile init<SID>.ora. This file is
usually located at oracle/SID/saptrace/usertrace/sbtio.log.
| 5. Check the log file sbtio.log for lines starting with BKI. The very first message
| for every RMAN session looks like this: ’BKI7060I: Data Protection for mySAP
| 5.3.1 (buildnumber) session: ’. If you cannot find any such message in the file,
the library is not correctly linked with Oracle.
6. On HP-UX 11 64bit you need to add the string -lstd -lstream -lCsup to the
existing line of the file $ORACLE_HOME/lib64/sysliblist and reissue the make
command. A detailed description of the problem cause can be found at HPs
website
(http://docs.hp.com/hpux/onlinedocs/dev/aCC/a_03_30/distributing.htm#DistLink).
7. Examine the dsierror.log located in the directory specified with the
environment variable DSMI_LOG
8. To get a Tivoli Storage Manager API trace file, set the following entries in the
client system options file dsm.sys:
tracefile /<path>/<trace file>
traceflags api api_detail config policy
| 9. On UNIX or Linux operating systems, an additional softlink may help in

/usr/lib for ’libtdp_r3.<ext>.1’ to
/usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>.
ln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libtdp_r3.<ext>.1
10. See also Appendix C, “Troubleshooting,” on page 123.
RMAN Setup on Windows Systems

To set up your DP for mySAP for use with RMAN under Windows, perform these
steps:
1. Stop the service OracleService<SID>
2. Install the Tivoli Storage Manager API Client on your mySAP database server
(see “Configuring the Tivoli Storage Manager Clients” on page 147).
3. Install DP for mySAP on your mySAP database server (see Chapter 4,
“Installing or Upgrading Data Protection for mySAP,” on page 23).
4. Set the DP for mySAP password for Tivoli Storage Manager (see “Modifying
the Handling of the TSM Password” on page 43).
5. Customize the SAP backup profile init<SID>.sap for use with RMAN. Insert
the following:
backup_dev_type=rman_util
rman_parms="ENV=(DSMI_DIR=<drive>:\<path>, DSMI_CONFIG=<drive>:\<path>\
<client options file>,DSMI_LOG=<drive>:\<path>,XINT_PROFILE=<drive>:
\<path>\init<SID>.utl,PROLE_PORT=portnumber)"
The appropriate Prole port number can be found in the file

<drive>:\WINNT\system32\drivers\etc\services
6. Start the following service:
v OracleService<SID>
Further Hints
1. Examine the sbtio.log located in the directory specified in the user_dump_dest
keyword within the Oracle profile init<SID>.ora.
2. If no file sbtio.log exists after an operation with RMAN or no line starting
with the letters ’BKI’ exists within an existing sbtio.log, check if the shared
library orasbt.dll was found and loaded by Oracle. Put the shared library file
orasbt.dll into the directory %ORACLE_HOME%\bin. This is the directory where
oracle.exe resides. Now stop the service OracleService<SID> and restart it.
Chapter 6. RMAN Setup 53

3. Examine the dsierror.log located in the directory specified with the
environment variable DSMI_LOG
4. To get a Tivoli Storage Manager API trace file, set the following entries in the
client options file:
tracefile <drive>:\<path>\<trace file>
traceflags api
5. See also Appendix C, “Troubleshooting,” on page 123.
Chapter 7. Using DP for mySAP with the File Manager
This section describes how to use the File Manager
DP for mySAP File Manager

The DP for mySAP File Manager is a utility that simplifies the DP for mySAP
inquire, restore, and delete operations for the user. It can be seen as an add-on to
DP for mySAP.
Note
Only users with a good knowledge about the restore and recovery
mechanism of Oracle databases should use this tool. The general
recommendation is that you should normally use the tools SAPDBA and
BRRESTORE provided by SAP for restore operations.
The File Manager uses the standard functions provided by DP for mySAP to
| perform all operations. The File Manager user interface consists of a split window,
| which is character based.
| All backup IDs found on all Tivoli Storage Manager servers with the same backup
| ID prefix as configured within the DP for mySAP profile are shown on the left. To
the right of each backup ID, all the files belonging to that backup ID are displayed.
You can select individual backup IDs or multiple files for the restore or delete
operations (see Figure 16 on page 56).
The File Manager has to be started with the path and name of the DP for mySAP
profile (the user must be a member of the dba group). See the following examples:
| For UNIX or Linux systems:

| backfm -p /oracle/SID/dbs/init<SID>.utl [-o <log file directory>]
|
For Windows systems:

| backfm -p <drive>:\orant\database\init<SID>.utl [-o <log file directory>]
| Note: If the -o parameter is specified at startup, the default directory for log files
| will be changed.
| The File Manager requires a correct setup of DP for mySAP particularly with
| regard to the backint executable, thus enabling it to connect to the TSM server
| without errors. To connect to the TSM server the File Manager calls the backint
| executable. If this call fails, the File Manager shows an error message but does not
| analyze what the reason for the failure is. To analyze the error, call backint
| manually with the inquire function (“Inquire Function” on page 133) and check the
| output for error messages.
The File Manager will now establish a connection to all Tivoli Storage Manager
servers which were configured in the DP for mySAP profile. The next step is an

automatic inquire operation for all backup IDs. The following figure shows the
display of a set of backup IDs located by the File Manager after having finished an
inquiry procedure.
If you mark the backup ID you are interested in and then press the Tab key to
|
| Figure 15. File Manager — Result of an Inquiry Procedure
|
move the cursor to the right-hand panel, all file names belonging to the marked
backup ID will be displayed as shown in the figure below.
The following function keys are defined for performing restore or delete
Figure 16. File Manager — Result of an Inquiry Procedure Showing File Names
operations:
Up, Down, Left, Right - Move cursor
Move the highlighted cursor in the direction indicated on the key.
Tab - Switch window side
Move the cursor between the left and right sides of the window.
F2 - Restore
Restore all marked files. Before the restore actually begins, you can specify
a common destination path and you will be asked to confirm the restore
process. If you specify a destination path, all marked files will be restored
to that directory. Otherwise the files will be restored to the directory from
which they were backed up.
F3 - Mark all
All files belonging to the current backup ID will be marked.
F4 - Unmark all
Unmark all files belonging to the current backup ID.
F5 - Refresh
Refresh the list of backup IDs and file names.
F6 - Fileinfo
Opens a separate window to display file information.
For backup IDs, the sequence number is displayed (backup version count,
for more information see on page 88). For files, the Tivoli Storage Manager
expiration date and time is displayed.
| F7 - Redirected Restore
| Redirected Restore operation will perform a restore of the selected files.
| During the restore the Oracle SID in the path and filenames will be
| replaced.
F8 - Delete
| Delete the selected backup ID and all corresponding files.
F10 - Exit
Exit from DP for mySAP File Manager
ENTER - Mark/unmark file
Mark or unmark the file below the cursor.
| For restore operations, the desired files first have to be marked. This can be done
either with the F3 function key to mark all the files that were found or with the
ENTER key to mark only one desired file. Marked files can be identified by the
| symbol ″ * ″ in front of the filename. Only the marked files will be restored.
For every restore a log file will be created in the following location:
v UNIX or Linux: $SAPDATA_HOME/sapbackup/backfm_<timestamp>.log
v Windows: %SAPDATA_HOME%\sapbackup\backfm_<timestamp>.log
| The File Manger can delete backup IDs with all included files. It is not possible to
| delete single files within a backup ID. To delete a backup ID it must be
| highlighted. After pressing F8 you have to confirm the deletion operation. The
| backup ID and all included files are deleted from the TSM server.
Chapter 7. Using DP for mySAP with the File Manager 57

| Redirected restore makes cloning of mySAP systems easier. See also Chapter 10,
| “Cloning the mySAP System,” on page 79. To clone a database you have to restore
| the database files to a different directory structure. In the new structure the Oracle
| SID must be replaced in all path- and filenames. You first have to mark the files for
| restore. This can be done either with the F3 function key to mark all files of a
| backup ID or with the ENTER key to mark only the highlighted file. Marked files
| can be identified by the symbol ″ * ″ in front of the filename. Press F7 to start the
| redirected restore. If you want to also create missing directories you need to
| provide the old and the new SIDs.
Figure 17. File Manager — Result of a Redirected Restore Procedure
For every restore a log file will be created in the following location:
| v UNIX or Linux: $SAPDATA_HOME/sapbackup/backfm_<timestamp>.log
v Windows: %SAPDATA_HOME%\sapbackup\backfm_<timestamp>.log
|
| Chapter 8. Installing and Using the Administration Assistant

for Data Protection for mySAP
| This chapter gives an overview of the Administration Assistant and describes its
| installation and setup. In this document the Administration Assistant sometimes is
| abbreviated as AA.
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 Simulate backup / restore
| v Configure systems
| v Request problem support
| Function Monitor Operations provides a centralized view on the backup status

| information for all mySAP systems registered with the Administration Assistant
| server. Summaries of the backup status of all or a selection of mySAP systems are
| available as well as detailed information on all backup runs of a specific mySAP
| system.
| Function View Performance Data displays performance information while Data

| Protection for mySAP is performing a backup or restore operation. The
| Administration Assistant also saves these performance data and provides a
| graphical presentation for later analysis
| Function Simulate backup / restore lets administrators test configuration changes or

| production restores without changing the productive environment or comprimizing
| production data.
| Function Configure systems allows to customize the SAP backup profiles, the Data
| Protection for mySAP profile, and the IBM Tivoli Storage Manager files for each of
| the mySAP 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.
| Function 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.
| Concepts of the Administration Assistant

| The Administration Assistant is comprised of the Administration Assistant server
| and clients. The Administration Assistant server can be installed on any system
| (Unix, Linux, Windows). It features an http or https server waiting for the clients’
| requests for connections.
| Instances of Data Protection for mySAP connect to the Administration Assistant
| server via TCP/IP. The Data Protection for mySAP ProLE service on the database
| server sends meta data relating to backup and restore operations that the
| Administration Assistant server collects and stores in files. These history data are
| 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 must be running and connected to the Data
| Protection for mySAP ProLE service during the backup and restore operations.
| User profiles ensure that a user can access data of only those mySAP database
| servers he or she has permission for.
| A mySAP system landscape contains several mySAP systems, for example

| production, development, test, and education systems. A single Administration
| Assistant server can monitor many mySAP database servers. A typical example is
| shown in Figure 18.
Figure 18. Example of a mySAP Landscape
| The Administration Assistant client is started from a browser when connecting to

| the http server. It is implemented as a JAVA applet that communicates with the
| Administration Assistant server via an RMI connection.
| If the Administration Assistant server was started in non-secure mode (that is with
| keyword ’nonsecure’ contained in the server configuration file assist.cfg) it
| accepts connect requests to its http port via http from a client. In this case, the
| further communication between client and server is via TCP/IP.
| If the Administration Assistant server was started in secure mode (that is with
| keyword ’nonsecure’ not contained in the server configuration file) it accepts
| connect requests to its https port via https from a client. In this case, the Secure
| Socket Layer (SSL) protocol is employed for all communication between the
| Administration Assistant clients and server.
| The latest SSL protocol (Version 3) can be found at
| http://wp.netscape.com/eng/ssl3/ .
| Latest information on PKI with X.509-certificate can be found on the website of the
| IETF Working Group ’Public Key Infrastructure (X.509) (pkix)’ at:
| http://www.ietf.org/html.charters/pkix-charter.html .
| Installing or Upgrading the Administration Assistant

| In order to set up the Administration Assistant server, do the following:
| 1. Check that the DP for mySAP package is complete. The package includes this
| manual and machine readable material on a CD-ROM. See the Readme file for:
| v A table of contents of the package
| v Up-to-date news
| 2. Make sure that the requirements are met.
| For details, see “Prerequisites for the Installation of the Administration
| Assistant Server” and “Prerequisites for the Administration Assistant Client” on
| page 62.
| 3. Gather planning information.
| For details, see “Installation Planning for the Administration Assistant Server”
| on page 62.
| 4. Install the Administration Assistant Server.
| For details, see “Installing the Administration Assistant Server” on page 63.
| 5. Perform post-installation steps.
| For details, see “Post-Installation Steps” on page 64.
| 6. Set up the Administration Assistant client.
| For details, see “2. Setting up the Administration Assistant Client” on page 65.
| 7. Verify the installation. For details, see “3. Verifying” on page 65.
| If you are going to do an upgrade installation, turn to “Upgrade Installation” on
| page 63.
| Prerequisites for the Installation of the Administration

| Assistant
| Prerequisites for the Installation of the Administration Assistant
| Server
| The following products must be installed before you can start setting up the
| Administration Assistant server:
| v Java Runtime Environment (JRE) or Java Development Kit (JDK)
| v Java Beans Activation Framework (JAF)
| v Java Mail
| For hardware and software prerequisites as well as maintenance levels required by

| the current version of the Administration Assistant, refer to the release notice
| (RELNOTE). TCP/IP must be ready for communication before starting up the
| Administration Assistant server.
| For software versions and maintenance levels of Data Protection for mySAP
| supported by the current version of the Administration Assistant, refer to the
| release notice (RELNOTE).
Chapter 8. Administration Assistant 61

| Prerequisites for the Administration Assistant Client
| Before starting the Administration Assistant client make sure the following
| requirements are met:
| v A fully Java-1.4-capable Web browser with Java plugin.
| v X Window system if the AA server resides on a UNIX or Linux system.
| v A minimum screen size of 1024 x 768
| For software versions and maintenance levels required by the current version of
| the Administration Assistant, refer to the release notice (RELNOTE).
| TCP/IP must be ready for communication before connecting to the Administration
| Assistant server.
| For software versions and maintenance levels of Data Protection for mySAP
| supported by the current version of the Administration Assistant, refer to the
| release notice (RELNOTE).
| Installation Planning for the Administration Assistant Server

| When starting the installation procedure of the Administration Assistant server, be
| prepared to provide the required information listed below:
| v Fully qualified hostname of the Administration Assistant server
| v Installation path for the Administration Assistant
| v http port. Number of http server port accepting http requests from the
| Administration Assistant clients. The default http port number is 80.
| v https port. Number of https server port accepting https requests from the
| Administration Assistant clients when the Administration Assistant server was
| started in secure mode. The default https port number is 443.
| v RMI registry port. Number of a port to be used internally by the Administration
| Assistant server. The Administration Assistant RMI registry port default is 1099.
| v Administration Assistant server port. Number of the port the Administration
| Assistant server is listening on for connect requests from Data Protection for
| mySAP. This port number must be made known to all instances of Data
| Protection for mySAP to be managed and monitored by the Administration
| Assistant server. The Administration Assistant server port default is 5126.
| v Performance data port. Number of the port the Administration Assistant server
| is listening on for performance data from the various instances of Data
| Protection for mySAP. The Administration Assistant performance data port
| default is 5125.
| v The public key infrastructure (PKI) for the secure communication between the
| Administration Assistant clients and server. If you do not plan to use secure
| communication you need not provide this and the followoing information:
| – Keystore name. Keystore containing the private and public keys of your
| Administration Assistant server when running in secure mode. If you do not
| have a public key infrastructure yet the keystore can be created during the
| installation process.
| – Keystore password. Password ensuring the consistency of the keystore. The
| server’s key pair must be protected by the same password.
| – Truststore name. Truststore containing a set of trusted certificates. When
| running in secure mode, the Administration Assistant’s server certificate must
| be verified against this truststore when the server is started.
| – Truststore password. Password ensuring the consistency of the truststore. This
| is only required if a trusted certificate needs to be imported in the truststore
| during the installation process.
| – Certificate file. Path of the certificate file in case you already have a server
| certificate issued by a certificate authority.
| – Certificate creation information. Information on the X.500 distinguished name
| (common name, organizational unit, organization name, locality name, state
| name, and country code) and on the validity period required in case a new
| self-signed certificate is to be created during the installation process. For
| details on this information, refer to the X.500 and X.509 standards.
| – New certificate file name. If the public key of a newly created server key pair
| needs to be distributed to client machines it will be exported to this file.
| – CSR file name. If the newly created server key pair will be used to request a
| certificate signed by a Certificate Authority the Certificate Signing Request
| will be written to this file.
| Installing the Administration Assistant Server

| There are two types of installation: initial installation and upgrade installation
| (migration).
| Initial Installation
| Initial installations must always be done from the DP for mySAP CD-ROM. Refer
| to the file README.1st in the root path for information on where to find documents
| on your CD-ROM, and follow the installation description below.
| Upgrade Installation
| If you want to upgrade from an earlier version of Tivoli Data Protection for
| mySAP Administration Assistant in your environment, you have the option to
| download the latest version from the IBM Tivoli Internet home page at
| http://www.ibm.com/software/tivoli.
| For more information on upgrading from an earlier version, refer to “Upgrading
| the Administration Assistant (Migration)” on page 66.
| The Installation Process

| On the Data Protection for mySAP installation CD there is one package with two
| installation options:
| v The base option and
| v The NLS option.
| The base installation of the Administration Assistant installs the ’English only’
| version of the product. The NLS option contains all currently translated resources.
| If you want to switch between options, you have to de-install the old one and
| reinstall the new.
| To assist you with the installation procedure, the Administration Assistant
| packages provide a setup assistant, a so-called installer that guides through the
| installation process. The package is delivered as Java archive named setup.jar.
| To install the Administration Assistant correctly system administrator privileges are
| required.
| There is no need to set the environment variable CLASSPATH. However, if this
| variable is set in the system environment, the directory where the file setup.jar
| resides must be included.
| Start an installation by specifying the following command:

| java -cp setup.jar run
||
| If the JRE is installed only, you must use the command:

| jre -cp setup.jar run
|
|
| During installation, the following modifications are done to your system

| automatically:
| v All necessary paths (installation, history, OnDoc, log paths) are created.
| Corresponding files are copied into installation- and OnDoc directories.
| v The Administration Assistant startup file (sadmt.cmd for Windows systems and
| sadmt.sh for UNIX and Linux systems) is created and added to the
| Admin.Assistant installation directory.
| v The configuration file assist.cfg containing all relevant configuration
| parameters specified during the installation is created and added to the
| installation directory.
| v File srv.list containing information about connected Data Protection instances
| is created and initialized.
| v On Windows systems a service is installed and automatically started. This
| service starts the AdminAssist.exe
| v On UNIX or Linux systems a new initab entry is created and the
| Admin.Assistant server is started automatically.
| v A keystore is created on request.
| v An X.509 v1 self-signed certificate containing a key pair with the hostname as
| alias is created in the keystore on request.
| v The server’s self-signed certificate is imported in the truststore on request.
| v The server’s self-signed certificate is exported to a certificate file on request.
| v A Certificate Signing Request is created on request.
| Uninstalling the Administration Assistant Server

| To uninstall the Administration Assistant server change to the uninstall directory in
| the Administration Assistant installation directory. These command files open an
| uninstall assistant which guides through the uninstallation process.
| The public key infrastructure will not be modified when uninstalling the
| Administration Assistant Server even if it was originally set up during its
| installation process.To start the deinstallation process, run the following command:
| java -jar uninst.jar
||
| .
| Post-Installation Steps
| After successfully completing the installation dialog of the Administration
| Assistant server, you need to perform the following steps:
| 1. If appropriate, prepare for a secure connection between the Administration
| Assistant clients and server.
| 3. Verify the installation.
| 1. Preparing for a Secure Connection between AA Client and

| Server
| If the necessary information was provided during the installation, your
| Administration Assistant server is prepared for a secure communication with its
| clients after the installation procedure. However, by default it is set up to accept
| http connect requests from the clients. You start a secure Administration Assistant
| server by removing the keyword ’nonsecure’ from the configuration file
| (assist.cfg).
| If you chose to not provide security information during the installation process or
| if you need to change the security setup refer to “Configuring for Secure
| Communication” on page 67.
| 2. Setting up the Administration Assistant Client

| Before connecting to the Administration Assistant server, 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
| index.html in the address. See also “3. Verifying.”
| In order to establish a secure communication between the Administration Assistant
| client and server the client’s Java plugin must be able to verify the certificate
| presented by the Administration Assistant server. 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 in the plugin’s truststore. If you did not exchange the plugin’s
| truststore via the Java Plugin Control Panel file cacerts in the Java security path is
| used as truststore. You modify it with your keystore management tool that may
| differ depending on your platform and provider. With keytool, for example, you
| will have to issue
| keytool -import -a <hostname of AA server> -file <cert_file> -keystore <trustore>
||
|
| Note
| Make sure to remove this trusted certificate from the truststore as soon as the
| officially signed server certificate is available and employed.
|
|
|
| Note
| This setup is not recommended for production environments.
|
|
| 3. Verifying
| Verify the installation of your Administration Assistant by connecting to the
| Administration Assistant server from a client machine.
| If the Administration Assistant server was started with the keyword nonsecure in
| the server configuration file, then connect via
| http://<AA server>:<http port>
||
| Alternatively, you can make the connection via

| http://<AA server>:<http port>/index.html
||
| In the latter case, the Administration Assistant client will not open a new browser
| window.
| If the Administration Assistant server was started without the keyword nonsecure
| in the server configuration file, then connect via

| https://<AA server>:<https port>
|
|
| Alternatively, you can make the connection via

| https://<AA server>:<https port>/index.html
|
|
| 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 to
| change the default password immediately via function ’Administer Users’.
| As soon as an instance of Data Protection for mySAP is started to connect to your

| Administration Assistant server it will be displayed in the list of servers
| automatically. For details how to set up your instance of Data Protection for
| mySAP to connect to a specific Administration Assistant server refer to
| “Adjustments for the Administration Assistant” on page 42.
| Upgrading the Administration Assistant (Migration)

| In order to upgrade the Administration Assistant server to a new version, do the
| following:
| 1. Check that the DP for mySAP package is complete. The package includes both
| this manual and machine readable material on a CD-ROM. See the Readme file
| for:
| v A table of contents of the package
| v Up-to-date news
| 2. Make sure that the requirements for the new version of the Administration
| Assistant are met.
| For details, see “Prerequisites for the Installation of the Administration
| Assistant Server” on page 61 and “Prerequisites for the Administration
| Assistant Client” on page 62 and read the Administration Assistant release
| notice (RELNOTE).
| 3. Gather or retrieve planning information.
| For details, see “Installation Planning for the Administration Assistant Server”
| on page 62.
| 4. Uninstall the old version of the Administration Assistant Server.
| For details, see “Uninstalling the Administration Assistant Server” on page 64.
| 5. Install the new version of the Administration Assistant Server.
| For details, see “Installing the Administration Assistant Server” on page 63.
| 6. Adapt the Administration Assistant server configuration file.
| For details, see “Migration of the Administration Assistant Server Configuration
| File” on page 67 below.
| 7. Perform post-installation steps.
| For details, see “Post-Installation Steps” on page 64.
| For details, see“2. Setting up the Administration Assistant Client” on page 65.
| 9. Verify the installation. For details, see “3. Verifying” on page 65.
| Migration of the Administration Assistant Server Configuration
| File
| If your server configuration file ( for example assist.cfg) came with the version
| 3.3 or a previous one of the Administration Assistant, the Administration Assistant
| server will automatically start in secure mode. If you are going to employ the
| secure communication make sure to setup both client and server accordingly. Refer
| to “1. Preparing for a Secure Connection between AA Client and Server” on page
| 64 and to “2. Setting up the Administration Assistant Client” on page 65 for
| details.
| In order to continue to use a connection via http, insert keyword nonsecure in

| your Administration Assistant server configuration file.
Configuring the Administration Assistant
Administering Userids
| The function Administer Users of the Administration Assistant enables you to create
| user accounts and to grant users permissions.
With the user administration function it is possible to create additional accounts

with appropriate rights. Rights or user permissions can be granted or revoked for a
specific user profile. Every account has seven authorities. These are:
v Configure Logic - permission to configure parts of the internal Operations
Monitor logic
v Configure Groups - permission to configure Operations Monitor display groups
v Operations monitor authority - permission to view backup status information of
any mySAP system within the system landscape
v Monitoring authority - permission to monitor jobs
v Configuration authority - permission to configure DP for mySAP
| v Problem Support authority - permission to send support request mail
v Administration authority - permission to administer all user accounts
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 and its
| clients is realized with the Secure Socket Layer (SSL) protocol. This protocol
| requires that both the server and the client be integrated in a public key
| infrastructure (PKI). Specifically, the Administration Assistant server 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 alias
| for this key pair.
| As the keystore contains the server’s private key precautions must be taken that
| it can be accessed only by authorized personnel.
| v A truststore containing trusted certificates that allow to verify 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 in the truststore, too.
|
| Note
| Make sure to remove this trusted certificate from the truststore as soon as the
| officially signed server certificate is available and employed.
|
|
|
| Note
| This setup is not recommended for production environment.
|
|
| Both the keystore and truststore can be manipulated with your keystore
| management tool that may differ depending on your platform and provider (for
| example keytool by SUN). For setting up the Administration Assistant server for
| secure communication you need to
| v Remove the keyword nonsecure from your server configuration file
| v Specify the appropriate https port number in your server configuration file:
| httpsport=<https port number>
||
| The default https port number is 443.

| v Start the Administration Assistant with the appropriate keystore and truststore.
| You do this by adding the following parameters to the java call in sadmt.cmd
| (UNIX or Linux) or the registry (Windows):
| -Djavax.net.ssl.keyStore=<keystore>
| -Djavax.net.ssl.keyStorePassword=<password for keystore>
| -Djavax.net.ssl.trustStore=<truststore>
||
| If you do not specify any 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.
|
| 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 mySAP Administration Assistant.
|
| Cyclic Procedure for Optimizing your Configuration
| With the Administration Assistant, administrators can analyze performance, modify
| the configuration, and test the effects of configuration changes without having to
| modify the production environment.
|
Figure 19. Optimizing your Configuration with the Administration Assistant
| The optimization cycle starts with a full backup of the database via the file
| interface (via BRBACKUP). The performance data are analyzed with function
| ’View Performance Data’. This may lead to some suggestions on how to change the
| DP for mySAP configuration and / or the infrastructure. These changes are
| temporarily implemented in a test profile with function ’Configure Systems’. With
| function ’Simulate Backup/Restore’, another backup or restore can be simulated to
| test the configuration changes. Then, the administrator uses the function ’View
| Performance Data’ to check whether the modifications yield the desired results.
| You may go through as many cycles of modification and test as are required until
| the results are satisfactory. When this is the case eventually, the configuration
| changes can be easily propagated to the production system. All changes to the
| configuration within this cycle are kept strictly separated from your production
| system, as are the results of the simulation runs.
|
| Observations on the DP for mySAP 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 mySAP configuration options
| contributing to performance read “Adjustments to DP for mySAP 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 20. Optimizing your configuration with the AA (Bird’s Perspective)
| From a bird’s perspective, when doing a backup with DP for mySAP, the data
| packages need to pass the following elements: Data is read from disk, processed by
| DP for mySAP, 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 mySAP
| 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.
|
| Data Protection for mySAP 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 21. Performance Optimizing by Using Sensors
| There are sensors introduced to Data Protection for mySAP 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 mySAP 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
|
Figure 22. Showing Data Throughput and I/O Utilization
| In this panel, you find a 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 76.
| The results of the Data Protection for mySAP 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.
Chapter 9. Balancing Your System 71

| Disk Bottleneck
|
Figure 23. Indicating a Disk Bottleneck
| With a disk bottleneck, data are 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. For an optimization procedure, refer
| to “Cyclic Procedure for Optimizing your Configuration” on page 69.
| Network or TSM Bottleneck
|
Figure 24. Indicating a Network or TSM Bottleneck
| With a network or TSM bottleneck, data are 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 mySAP performance analysis, as will be detailed later.
| 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.
| For a general optimization procedure, refer to “Cyclic Procedure for Optimizing
| your Configuration” on page 69.

| A Balanced Configuration
|
Figure 25. Indicating a Balanced Configuration
| If the threads on both the disk and the network side are similarly busy throughout
| the backup the system is balanced, and the utilization of resources is good. In an
| optimum setup, tapes are kept in streaming mode. That means that the network is
| at least as fast as the tape, and there is no idle time on the network side. Thus, a
| slight network bottleneck is desired.
|
| Note
| Under certain conditions, the degree of imbalance cannot be determined from
| the graphical presentation: Depending on your system characteristics (for
| example system buffering, buffer sizes, etc.), utilization may seem to drop
| near zero in the graphical presentation although the system is fairly balanced
| in reality. In this case, slight modifications can yield a change of bottleneck
| without significant throughput changes. However, whether the system is disk
| or network / tape constrained is always shown correctly.
|
|
| If you are looking to improve overall throughput you may want to add more
| resources and create a balanced system again.
| If you are looking to better exploit the resources you are done.
|
| Note
| A balanced system does not necessarily mean that the data throughput cannot
| be improved any more. Adding new resources can still improve the
| throughput rate.
|
|
| Simulating Backup and Restore
| The Administration Assistant’s function ’Simulate Backup/Restore’ requires a full
| backup of your database using the file interface (via BRBACKUP). Backups done
| using the RMAN interface cannot serve as a basis for simulation. When there are
| two or more eligible backups available the latest one is used as the basis for
| simulation.
| In order to get good results for the simulation of Data Protection for mySAP
| compression, compression should be enabled for the base backup, with parameter
| COMPR_INFO pointing to a valid file in the Data Protection for mySAP profile.
| Both backups and restores can be simulated. Simulating a restore may give you an
| impression how long restoring a backup will take, but it will not affect your
| productive system.
| The administrator may choose to simulate any of the following:

| v Disk I/O
| When simulating disk I/O for a backup, no data are read from disk. They are
| generated in memory instead. When simulating disk I/O for a restore, no data
| are written to disk; they are consumed instead. The disk I/O rate to be used for
| the simulation can be set by the administrator.
| For information on how to determine your current rate, refer to “Determining
| the Actual Disk I/O Rate.”
| v Network transfer and media rates
| When simulating network transfer and media rates for a backup no data are sent
| via the network; they are consumed instead. When simulating network transfer
| and media rates for a restore, no data are expected from the network; they are
| generated in memory instead. Still, a connection to the TSM server is established
| and needs to be maintained during the simulation. Therefore, be sure to
| configure the TSM server so, that the sessions do not time out. See: “5. TSM
| Server Configuration” on page 147.
| The network throughput rate and the media rate for the simulation can be set by
| the administrator. The rate to be used for the simulation is determined by the
| network throughput rate and the media rate set.
| For information on how to determine your current network rate, refer to
| “Determining the Actual Network Throughput Rate” on page 76.
| For information on how to determine the current media rate, refer to
| “Determining the Actual Throughput Rate of Storage Media” on page 76.
| Determining the Actual Disk I/O Rate

| In order to determine the actual disk reading rate, run a simulated backup of type
| ’No data moved to Tivoli Storage Manager’. Both the Tape Transfer Rate and the
| Network Transfer Rate must be set to ’infinite’ in order to make sure there will not
| be a network bottleneck. Compression must be switched off, and function ’View
| Performance Data’ should show 100 % disk utilization.
| The overall throughput you get with this configuration is the rate at which data
| are read from disk.
| In order to determine the actual disk writing rate, run a simulated restore of type
| ’No data moved from Tivoli Storage Manager’. Both the Tape Transfer Rate and the
| Network Transfer Rate must be set to ’infinite’ in order to make sure the system
| will not create a network bottleneck. Compression must be switched off, and
| function ’View Performance Data’ should show 100 % disk utilization.
| are written to disk.
| Keep in mind that an increased disk I/O rate is shown while data are written to
| the file system cache.

| Determining the Actual Throughput Rate of Storage Media
| In order to determine the actual writing rate of a tape, run a simulated backup of
| type ’No data moved from disk’. The Disk Transfer Rate must be set ’infinite’ in
| order to make sure there will not be a disk bottleneck. The number of sessions
| must be set to one, Compression must be switched off, and function ’View
| Performance Data’ should show 100 % disk utilization. The overall throughput you
| get with this configuration is the rate at which data are written to the storage
| media unless the network rate is lower than the media rate.
| In order to determine the actual reading rate of a tape, run a simulated restore of
| type ’No data moved to disk’. The Disk Transfer Rate must be set ’infinite’ in order
| to make sure there will not be a disk bottleneck. The number of sessions must be
| set to one. In order to exclude a CPU bottleneck, make sure that function ’View
| Performance Data’ shows 100 % network utilization.
| are read from the storage media unless the network rate is lower than the media
| rate.
| You may find that the throughput rate does not increase when the number of
| sessions is increased (see ″Determining the Actual Network Throughput Rate″
| below). In this case, the network throughput rate is lower than the media rate, and
| the media rate cannot be determined with the Administration Assistant.
| Determining the Actual Network Throughput Rate

| In order to determine the actual network throughput rate, run a simulated backup
| of type ’No data moved from disk’. The Disk Transfer Rate must be set to ’infinite’
| in order to make sure there will not be a disk bottleneck. Increase the number of
| sessions to the maximum number possible, i.e. the number of tape drives available.
| To be sure that the limiting factor is not the tape transfer rate, the throughput rate
| must be less than the media rate as determined in ’Determining the Actual
| Throughput Rate of Storage Media’ above, multiplied by the number of sessions.
| Function ’View Performance Data’ should show 100% network utilization.
| The overall throughput you get with this configuration is the network throughput
| rate.
| Determining Throughput Rates

| Table 3. Summary: How to Determine Throughput Rates
| Network
| Disk I/O Rate Storage Media Rate Throughput Rate
| Simulation Type No data moved No data moved No data moved
| to/from Tivoli to/from disk to/from disk
| Storage Manager
| Disk Transfer Rate - infinite infinite
| Network Transfer infinite - -
| Rate
| Tape Rate infinite - -
| RL Compression off off off
| Multiplexing 1 1 1
| Number of Sessions 1 1 maximum possible
| number
|
| 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 26. 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.
| Transferring Results
| 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. Note
| that for a restore, some parameter values are determined by the settings of the
| corresponding backup. Among these are:
| v Compression. If compression was switched on during backup, data need 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 was done using multiple servers the same
| servers must be online and available during restore.

| RMAN versus File Interface
| Simulating backup or restore is based on a backup of the production database
| using the file interface (via BRBACKUP). A backup via the RMAN interface cannot
| be used as a basis for simulation. However, modifications found during a
| simulation can also be transferred to the RMAN environment and should yield
| good results there, too.
Chapter 10. Cloning the mySAP System
The procedure for cloning a mySAP system described in this chapter should be
used to complement the SAP documentation R/3 Homogeneous System Copy and R/3
Installation on UNIX / Windows - Oracle Database.
Furthermore, it is recommended that you use the correct SAP documentation for
each particular environment. This documentation can be found at
http://sapnet.sap.com on the SAP Documentation Guides CD-ROM, which is part
of the SAP R/3 installation package or with the help of the SAP technical support.
What is Cloning ?
The mySAP system cloning can be done if there is the necessity for one source
mySAP system to be exactly copied to a target mySAP system. In this context, the
source mySAP system is also called the original system, from which the data will
be exported, and the target mySAP system is also called the destination system,
which imports the data from the source mySAP system.
SAP calls the procedure of cloning a mySAP system either homogeneous system copy
or heterogeneous system copy. In a homogeneous system copy scenario, the source
and target systems have the same mySAP release, operating system, and database
version. If this is not the case, you will get a heterogeneous system copy. Further
information about these two system copy scenarios can be found in OSS notes
86859 and 86860.
mySAP system cloning is appropriate in the following situations:

v Setting up a mySAP system landscape (development, quality assurance, and
production system)
v Hardware upgrade
v Creating multiple mySAP test and/or demo systems
Additional information about mySAP system cloning can be found in the IBM
redbook SAP R/3 Data Management with Tivoli Storage Manager, SG245743. The book
can be downloaded at http://www.redbooks.ibm.com.
mySAP System Cloning Example

The following procedure is supplied with no warranty of any kind. For
SAP-specific changes, see also OSS note 71254.
It is assumed that there are two SAP R/3 systems installed and operating on two
different machines and that DP for mySAP is installed and operating on both
systems. The following describes the necessary changes in order to restore an
Oracle SID to a different machine with a different SID.
The steps you need to perform depend on the password access method you are
using:
v Automatic password handling (see also on page 44)
If you are using passwordaccess=generate in the Tivoli Storage Manager client
| option file dsm.sys on UNIX or Linux systems or <server>.opt on Windows
systems of your source system, you need to make sure that you are using the

same nodename/password that is specified in the Tivoli Storage Manager client
option file on the target system. In order to do that, carry out the following
procedure:
1. Make a backup copy of the client option file on the target system.
2. Copy the client option file from the source system to the target system.
3. Edit the client option file and add NODENAME source system to the server
stanza.
4. Reset the Tivoli Storage Manager password for the target system node on
the server.
5. Set the newly created password on the client, e.g., dsmc q f. Remember to
do this as root/administrator.
6. Make a backup copy of the init<SID>.utl file on the target system.
7. Copy the init<SID>.utl file from the source system to the target system
and rename init<SID>.utl to init<target_SID>.utl.
8. Edit the init<SID>.utl file on the target system to reflect all the correct file
and path names such as for CONFIGFILE and TRACEFILE.
9. Go ahead and restore the database under the SAP considerations.
10. After the restore, reset the client option file and init<SID>.utl file to their
originals and set the passwords on the target system.
11. Reset the passwords on the source system.
Note
Keep in mind that the passwords are stored in different places, while the
only ″original″ password resides on the Tivoli Storage Manager server! You
need to make sure that the client uses the password that is stored on the
server.
v Manual password handling (see also on page 43)

If you are using passwordaccess=prompt, you only need to set the
nodename/password in the init<SID>.utl file:
1. Make a backup copy of the init<SID>.utl file on the target system.
2. Copy the init<SID>.utl file from the source system to the target system and
rename init<SID>.utl to init<target_SID>.utl.
3. Edit the init<SID>.utl file on the target system to reflect all the correct file
and path names such as for CONFIGFILE, TRACEFILE, ...
4. As <SID>adm user, on the target system, set the Data Protection for mySAP
password:
| For UNIX or Linux systems
backint -p /oracle/<SID>/dbs/init<SID>.utl -f password
For Windows systems

backint -p <drive>:\orant\database\init<SID>.utl -f password
and issue the password at the prompt.

5. Restore the database according to the SAP recommendation.
6. Reset the init<SID>.utl file and the password on the target system.
Part 3. Appendixes

Appendix A. The Data Protection for mySAP Profile
This section describes the Data Protection for mySAP profile, which is used to
customize the way Data Protection for mySAP operates. A sample profile
initSID.utl is provided on the installation medium.
| The installation procedure for UNIX or Linux copies and renames the file to
$ORACLE_HOME/dbs/init$ORACLE_SID.utl, where $ORACLE_HOME is the Oracle
home directory and $ORACLE_SID is the Oracle System ID, for example,
/oracle/<SID>/dbs/init<SID>.utl.
The setup for Windows puts all files in an initial setup sub-directory (the default is
C:\Program Files\Tivoli\TDP4SAP for Tivoli Storage Manager). The sample profile
is found there. Before execution, Data Protection for mySAP 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
The following profile keywords are obsolete for Data Protection for mySAP version
5.3.
v ADSMBUFFSIZE
v BACKAGENT
v DISKBUFFSIZE
v PERF_MONITOR
v RETRY
v TCPWAIT
ADSMNODE ORACLE_sid
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, ORACLE_sid
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 mySAP Oracle

database systems in your network with the same name, for example,
<SID>, and they all use the same Tivoli Storage Manager server.
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 DP for mySAP after the
backup function has completed and before program control is returned to
the SAP backup utility.
pgmname is either a fully qualified file name or simply a file name. In the
latter case 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 R3 Backup is 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.
BATCH YES|NO
Specify NO if DP for mySAP is running with an operator standing by.
Specify YES if DP for mySAP is running in unattended mode. In this mode
DP for mySAP terminates the run if operator intervention is required.
The default for the BATCH parameter is YES for the backup run and NO
for the restore run if the BATCH parameter is not present or is commented
out in the DP for mySAP profile.
This parameter has no effect if an RMAN backup/restore is started.
BRARCHIVEMGTCLASS management_class [management_class...]
Specifies the Tivoli Storage Manager management class(es) DP for mySAP
uses when called from BRARCHIVE. Each parameter string can consist of
up to 30 characters.
Note
The number of different BRARCHIVE management classes specified
must be larger or equal than the number of redo log copies specified
(parameter REDOLOG_COPIES).
For more detailed information about implementing and using

BRARCHIVEMGTCLASS see Appendix I, “Hints and Tips for SAP Backup
Utilities,” on page 163.
Keep in Mind
BRBACKUPMGTCLASS management_class [management_class...]

Specifies the Tivoli Storage Manager management class(es) DP for mySAP
uses when called using BRBACKUP. The parameter string can consist of up
to 30 characters.
Keep in Mind
| BUFFCOPY SIMPLE|PREVENT|AUTO
| This optional parameter controls how DP for mySAP 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.
| If set to PREVENT the original data buffers are passed on between Tivoli
| Storage Manager components. This mode cannot be selected while the
| Tivoli Storage Manager client encryption and / or client compression are
| activated.
| If set to AUTO Data Protection for mySAP 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 passed to
the Tivoli Storage Manager API functions. The valid range is from 4096 to
262144. Inappropriate values will be adjusted automatically.
| 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.
| COMPR_INFO path
| Specifies the file where Data Protection for mySAP stores information
| about the compressed size of files. path specifies the full path and name of
| the file.
| When multiplexing is used, Data Protection for mySAP attempts to put
| files of the same size in one multiplexing stream to optimize performance.
| If RL_COMPRESSION is used in addition to multiplexing, the file sizes of
| the compressed files can differ very much from the original file sizes. Data
| Protection for mySAP can collect information about the compressed file
| sizes and use it for further file sorting. This file size information is stored
| in the file specified by the COMPR_INFO parameter.
| If backups shall serve as a basis for simulations (see “Simulating Backup
| and Restore” on page 75), COMPR_INFO must denote a valid file and
| RL_COMPRESSION must be set to YES in order to get meaningful
| simulation results for compression.
Appendix A. The Data Protection for mySAP Profile 85

| When the parameter RL_COMPRESSION is set to NO, this parameter has
| no effect.
| If specified, the info file is written after each backup and the information is
| used by the following backups and simulations. If there is no compression
| information about a file because of a database extension, the uncompressed
| file size is used for file sorting.
CONFIG_FILE <path>/init<SID>.bki
Specifies the configuration file (init<SID>.bki)for DP for mySAP 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.
This parameter is required.
END Specifies the end of the parameter definitions. DP for mySAP stops
searching the file for keywords when END is encountered.
EXITONERROR YES|NO|n
This keyword specifies whether or not DP for mySAP exits on a backup or
restore error during a BRBACKUP/BRRESTORE run. NO means don’t exit
if an error occurs. YES means exit if one file can’t be backed up. If a
number is specified as an argument, DP for mySAP counts the number of
errors (not warnings or retries) and exits after the specified number of
errors.
This keyword works only for the BRBACKUP/BRRESTORE runs.
BRARCHIVE and RMAN runs always exit after the first error.
This parameter is ignored if the BATCH parameter is set to NO.
FCS_FILE path
Specifies the profile for DP for ESS for mySAP. If DP for mySAP and DP
for ESS for mySAP are used together this parameter is mandatory. See the
DP for ESS for mySAP manual for more details. For a stand alone
installation of DP for mySAP this parameter must not be used.
FILE_RETRIES n|3
This parameter specifies the number of retries when a file could not be
saved or restored. If not specified, the default is FILE_RETRIES 3.
FRONTEND pgmname
Specifies a program pgmname that is called by DP for mySAP in a backup
run before the connection to the Tivoli Storage Manager server is
established. pgmname is either a fully qualified file name or simply a file
name. In the latter case 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 R3 Backup 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
log messages to. The name must match one of the servers listed in a
SERVER statement, if you want DP for mySAP 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|1
Specifies the maximum number of parallel Tivoli Storage Manager client
sessions that DP for mySAP establishes for backup, archive (log files) and
restore. Each session transfers one database object or, in the case of an
RMAN backup or restore, a set of data blocks to or from the Tivoli Storage
Manager server by using the Tivoli Storage Manager API client functions.
DP for mySAP optimizes the data transfer with regard to the physical
location of the Oracle objects. Files stored on different volumes are backed
up in parallel. 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. For performance
reasons, it is recommended that you use as many parallel sessions as tape
drives are available.
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.
MAX_SESSIONS see Appendix I, “Hints and Tips for SAP Backup
Keep in Mind
The MAX_SESSIONS value must be less than or equal to the sum of
the SESSIONS values specified in the SERVER statement(s).
MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS,
MAX_RESTORE_SESSIONS
These parameters have the same function as the MAX_SESSIONS
parameter, but they are more specific. They define the number of parallel
sessions used for the BRARCHIVE, BRBACKUP and BRRESTORE
functions. If MAX_SESSIONS is specified with one or more of these
parameters, the more specific parameters overwrite the MAX_SESSIONS
parameter. You must specify them all if you don’t specify the
MAX_SESSIONS parameter.
The MAX_ARCH_SESSIONS defines the number used for archive (backup
of log files). Usually archive does not need as many sessions as (data file)
backup since the volume is much smaller with log files. This value will
overwrite MAX_SESSIONS for archive. It defines the number of parallel
sessions used for restore.
The MAX_BACK_SESSION defines the number of parallel sessions for
(data file) backup.
The MAX_RESTORE_SESSIONS defines the number of parallel sessions
used for restore. For restore, more tape drives may be available than for
backup. Using these additional tape drives may speed up the data transfer
for restore if the backup is written to multiple tapes (tape capacity small
compared to database volume).
This value will overwrite MAX_SESSIONS for restore.
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.
Be aware that if you are using backup version control, you use the same
initSID.bki file for BRBACKUP and BRARCHIVE, to avoid an unexpected
loss of data.
Every time a full backup completes successfully, the version count is
incremented by 1 and stored in the DP for mySAP configuration file. This
value is also assigned to the tablespace files and to all subsequent redo log
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 versions are deleted (together with
the corresponding tablespace and redo log files) until only the specified
maximum number of most recent versions remain.
Notes
v Partial backups get the same version number as the last successful
full backup. When DP for mySAP 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 CONFIGURATION_FILE) and a unique
BACKUPIDPREFIX.
CAUTION
Tivoli Storage Manager uses the value of the parameter RETVER
specified when defining a copy group (see “3. Policy Definition” on
page 145) to give files an expiration date. If you use Data Protection
for mySAP backup version control, you need to bypass this
expiration function. If you use the Tivoli Storage Manager expiration
function, you need to turn off Data Protection for mySAP backup
version control. Use only one of these methods to control how long
you keep backups.
If you use Data Protection for mySAP 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

mySAP versioning by setting MAX_VERSIONS=0.
MULTIPLEXING n|1
Specifies the number of files which are multiplexed into one data stream.
The allowed range is from 1 to 8. The optimal value depends strongly on
the actual hardware environment. Simply speaking, multiplexing makes
sense when fast tapes and fast networks are available, when the database
files are highly compressible and the CPU load is not too high. Optimal
values can be expected in the range from 1 to 4.
If not specified, the default value of 1 means ’no multiplexing’.
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
REDOLOG_COPIES n|1
Specifies the number of copies DP for mySAP stores for each processed
Oracle redo log.
If not specified, DP for mySAP stores only one copy of the redo logs.
How many copies are stored depends on the setting of the keyword
REDOLOG_COPIES. If the keyword is set to 2, for example, two copies
will be created.
This feature can only be used when (at least) as many archive management
classes are defined as numbers of log copies are specified (keyword
BRARCHIVEMGTCLASS).
Note
The number of different BRARCHIVE management classes (keyword
BRARCHIVEMGTCLASS) specified must be greater than or equal to
the number of redo log copies specified.
This keyword has no effect if an RMAN backup/restore is started.

REDOLOG_COPIES see Appendix I, “Hints and Tips for SAP Backup
REPORT NO|YES|2
If set to YES, Data Protection for mySAP produces some additional
information, for example, transferred files.
If set to 2, Data Protection for mySAP generates an additional summary
report containing detailed backup/restore performance statistics. This
summary is displayed at the end of the whole run. The output is sent to
stdout, which is normally the console.
If not specified, the default is REPORT NO.

This keyword has no effect if an RMAN backup/restore is started.
RL_COMPRESSION NO|YES
If set to YES, Data Protection for mySAP 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
(BRBACKUP) was started. The offline log files (BRARCHIVE) 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 mySAP
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, BRARCHIVEMGMTCLASS, BRBACKUPMGMTCLASS,
PASSWORDREQUIRED, SESSIONS, TCP_ADDRESS, and USE_AT. The
server name must be defined in the Tivoli Storage Manager profiles
| dsm.sys ( UNIX or Linux ) or <servername.opt> (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.
Note
Do NOT use any profile keywords or ’ADSM’ or ’TSM’ as
servername.
SESSIONS n|1
n specifies the number of parallel sessions DP for mySAP can start for this
server.
This keyword is required in every server section.
Keep in Mind
SORT_FILE
To perform manual sorting, a so-called sortfile has to be created. The format
of the sortfile is:
Sort file format

/<path>/<filename1> disknumbers
/<path>/<filename2> disknumber
.
.
.
/<path>/<filenameN> disknumber
The disk numbers are counted from 1 to n. They do not have any relation
to the physical disks. You only have to specify the same number for the
files on the same physical disk.
TCP_ADDRESS
Specifies the IP address of this Tivoli Storage Manager server. This
parameter overrides the value for the parameter TCPSERVERADDRESS in
| the Tivoli Storage Manager profile dsm.sys file on UNIX or Linux or in the
servername.opt on Windows.
Note
The parameter TCP_ADDRESS must only be used with Tivoli Storage
Manager API Version 5.2 or higher.
Keep in Mind
The parameter TCP_ADDRESS must be defined in conjunction with
the respective SERVER statement as shown in the sample profile
below.
| 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 mySAP 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 mySAP support asks
you to. Using it can significantly degrade the performance of DP for
mySAP.

TRACEFILE path
Specifies the trace file for DP for mySAP to store all trace information (if
TRACE ON), path specifies the full path and the name of file.
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.
| If you use this keyword make sure that the same TSM server is used for a
| simulation and its corresponding basis production backup. For details on
| simulations see “Simulating Backup and Restore” on page 75.
Keep in Mind
The parameter USE_AT must be defined in conjunction with the
respective SERVER statement as shown in the sample profile below.
The parameter has no effect on actions other than backup.
Sample Data Protection for mySAP Profiles

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

| #--------------------------------------------------------------------------
| #
| # Data Protection for mySAP (R) interface for ORACLE
| #
| # Sample profile for Data Protection for mySAP (R) Version 5.3
| # for UNIX
| #
| #--------------------------------------------------------------------------
| #
| # This file should be renamed to $ORACLE_HOME/dbs/init$ORACLE_SID.utl
| # where $ORACLE_HOME is the home directory of the Oracle database and
| # $ORACLE_SID is the system ID of the Oracle database.
| # Default is ’/oracle/C21/initC21.utl’.
| #
| # See the ’Data Protection for mySAP (R) Installation &
| # User’s Guide’ for a full description.
| #
| # For comment symbol the character ’#’ can be used.
| # Everything following this character will be interpreted as comment.
| #
| # Data Protection for mySAP (R) V5R3 accesses its profile
| # in "read only" mode only. 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 will be used for communication with SAPDBA
| # and stored in the description field of the Tivoli Storage Manager archive
| # function.
| # Must be 6 characters.
| # Default: none.
| #--------------------------------------------------------------------------
| BACKUPIDPREFIX SID___
|
|
| #--------------------------------------------------------------------------
| # Number of total parallel sessions to be established.
| # Note: this number should correspond with the number of simultaneously
| # available tape drives specified for the Tivoli Storage Manager server.
| # The valid range of MAX_SESSIONS is from 1 to 32.
| # Default: none.
| #--------------------------------------------------------------------------
| MAX_SESSIONS 1 # 1 Tivoli Storage Manager client session is default
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established for the database backup.
| # The valid range of MAX_BACK_SESSIONS is from 1 to 32.
| # Default: none.
| #--------------------------------------------------------------------------
| #MAX_BACK_SESSIONS 1 # 1 Tivoli Storage Manager client session for backup
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established for the archive log backup.
| # The valid range of MAX_ARCH_SESSIONS is from 1 to 32.
| # Default: none.
| #--------------------------------------------------------------------------
| #MAX_ARCH_SESSIONS 1 # 1 Tivoli Storage Manager client session for archive
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established for the restore of files.
| # The valid range of MAX_RESTORE_SESSIONS is from 1 to 32.
| # Default: none.
| #--------------------------------------------------------------------------
| #MAX_RESTORE_SESSIONS 1 # 1 Tivoli Storage Manager client session for restore
|
|
| #--------------------------------------------------------------------------
| # Number of backup copies of the archived redo logs.
| # The valid range of REDOLOG_COPIES is from 1 to 9.
| # Default: 1.
| #--------------------------------------------------------------------------
| #REDOLOG_COPIES 2 # 1 is default
|
|
| #--------------------------------------------------------------------------
| # 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 mySAP (R) should not be used together with
| # Tivoli Storage Manager API compression.
| # Default: NO
| #--------------------------------------------------------------------------
| #RL_COMPRESSION YES # NO is default
|
|
| #--------------------------------------------------------------------------
| # Specifies how many files are multiplexed into one data stream
| # to a Tivoli Storage Manager server. Multiplexing is usefull when the data
| # rate to a Tivoli Storage Manager server is higher (fast tapes, fast network)
| # than the I/O rate from a single disk.
| # The valid range of MULTIPLEXING is from 1 to 8.
| # Default: 1 (meaning no multiplexing)
| #--------------------------------------------------------------------------
| #MULTIPLEXING 3 # 1 is default
|
|
| #--------------------------------------------------------------------------
| # 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 NT.
| #--------------------------------------------------------------------------
| BUFFSIZE 131072 # block size in bytes
|
|
| #--------------------------------------------------------------------------
| # This optional parameter controls how Data Protection for mySAP(R) uses
| # the internal buffers for transferring data during a backup.
| # Default: SIMPLE
| #--------------------------------------------------------------------------
| #BUFFCOPY SIMPLE|PREVENT|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 mySAP (R) is only activated
| # if the R/3 release is 3.0C and higher and the parameter MAX_VERSIONS is
| # not 0.
| # The valid range of MAX_VERSIONS is from 0 to 9999.
| # Default: no versioning.
| #--------------------------------------------------------------------------
| #MAX_VERSIONS 4
|
|
| #--------------------------------------------------------------------------
| # Batch processing
| # Default:
| # The default for the BATCH parameter is YES for the backup run and NO for
| # the restore run if the BATCH parameter is COMMENTED OUT in this profile.
| #--------------------------------------------------------------------------
| #BATCH YES # unattended automated operation
| #BATCH NO # manual operation
|
|
| #--------------------------------------------------------------------------
| # Control of error situations
| # The valid range of EXITONERROR is from 0 to 100.
| # Default: NO.
| #--------------------------------------------------------------------------
| #EXITONERROR 3 # don’t exit if an error occurs
|
|
| #--------------------------------------------------------------------------
| # Control of information for reporting purposes, e.g. messages, statistics.
| # Default: NO (no additional data will be reported).
| #--------------------------------------------------------------------------
| #REPORT NO # no additional messages
| #REPORT YES # all additional messages
| #REPORT 2 # all additional messages + summary
|
|
| #--------------------------------------------------------------------------
| # Controls generation of a trace file.
| # Note: we recommend using the trace function only in cooperation with
| # the hotline.
| # Default: OFF.
| #--------------------------------------------------------------------------
| #TRACE OFF
|
|
| #--------------------------------------------------------------------------
| # Specify the full path of the trace file.
| # Note: for an actual trace the string ’%BID’ will be replaced by
| # the current backupid.
| # (.../backint_%BID.trace changes to .../backint_SAP___9809182300.trace).
| # Default: none.
| #--------------------------------------------------------------------------
| #TRACEFILE /oracle/C21/dbs/backint.trace
| #TRACEFILE /oracle/C21/dbs/backint_%BID.trace
|
|
| #--------------------------------------------------------------------------
| # Denotes the maximum size of the trace file in KB.
| # If not specified, the trace file size is unlimited.
| #--------------------------------------------------------------------------
| #TRACEMAX <max. size>
| #--------------------------------------------------------------------------
| # Specify the full path of the configuration file.
| # file.
| # Default: none.
| #--------------------------------------------------------------------------
| CONFIG_FILE /oracle/C21/dbs/initSID.bki
|
|
| #--------------------------------------------------------------------------
| # Number of times to retry saving/restoring a file in case an error occurs.
| # The valid range of FILE_RETRIES is from 0 to 100.
| # Default: 3.
| #--------------------------------------------------------------------------
| #FILE_RETRIES 3
|
|
| #--------------------------------------------------------------------------
| # Denotes if Data Protection for mySAP (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.
| # Values for verbosity can be ERROR, WARNING, or DETAIL.
| # Default: none.
| #--------------------------------------------------------------------------
| #LOG_SERVER servername [verbosity]
| #LOG_SERVER server_a ERROR
|
|
| #--------------------------------------------------------------------------
| # Denotes if Data Protection for mySAP (R) shall use a manual sorting file
| # for disk sorting.

| # Default: none.
| #--------------------------------------------------------------------------
| #SORT_FILE /oracle/C21/dbs/manual_sort_file
|
|
| #--------------------------------------------------------------------------
| # Denotes if Data Protection for mySAP (R) shall use a compressed filesize
| # sorting file for disk sorting.
| # For backup simulations with compression (see manual) this parameter must
| # be set to a valid file.
| # Default: none.
| #--------------------------------------------------------------------------
| #COMPR_INFO /oracle/C21/dbs/initSID.cfi
|
|
| #**************************************************************************
| # Statement for multiple Servers and multiple Paths.
| # may be used multiple times (one for each server).
| #**************************************************************************
|
|
| SERVER server_a # Servername
| SESSIONS 2 # Max sessions
| PASSWORDREQUIRED YES # Use a password
| ADSMNODE NODE # Tivoli Storage Manager Nodename
| BRBACKUPMGTCLASS MDB # Mgmt-Classes
| BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes
| # USE_AT 0 1 2 3 4 5 6 # Days for backup
| # TCP_ADDRESS 192.168.1.1 # IP address to use
|
| #SERVER server_b # Servername
| # SESSIONS 2 # Max sessions
| # PASSWORDREQUIRED YES # Use a password
| # ADSMNODE NODE # Tivoli Storage Manager Nodename
| # BRBACKUPMGTCLASS MDB # Mgmt-Classes
| # BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes
|
| #**************************************************************************
| # 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
| #**************************************************************************
|
|
| #--------------------------------------------------------------------------
| # End of profile
|
|
| END
Sample Data Protection for mySAP Profile for Windows

| #--------------------------------------------------------------------------
| #
| # Data Protection for mySAP (R) interface for ORACLE
| #
| # Sample profile for Data Protection for mySAP (R)
| # Version 5.3 for Windows 2000/2003
| #
| #--------------------------------------------------------------------------
| #
| # See the ’Data Protection for mySAP(R) Installation & User’s Guide’ for
| # a full description.
| #
| # For comment symbol the character ’#’ can be used.
| # Everything following this character will be interpreted as comment.
| #
| # Data Protection for mySAP (R) accesses its profile in "read only" mode
| # only. 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 will be used for communication with SAPDBA
| # and stored in the description field of the Tivoli Storage Manager archive
| # function.
| # Maximum 6 characters.
| # Default: none.
| #--------------------------------------------------------------------------
| BACKUPIDPREFIX SID___
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established.
| # Default: none.
| #--------------------------------------------------------------------------
| MAX_SESSIONS 1 # 1 Tivoli Storage Manager client session
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established for the database backup.
| # Default: none.
| #--------------------------------------------------------------------------
|
| #MAX_BACK_SESSIONS 1 # 1 Tivoli Storage Manager client session for backup
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established for the archive log backup.
| # Default: none.
| #--------------------------------------------------------------------------
| #MAX_ARCH_SESSIONS 1 # 1 Tivoli Storage Manager client session for archive
|
|
| #--------------------------------------------------------------------------
| # Number of parallel sessions to be established for the restore of files.
| # Default: none.
| #--------------------------------------------------------------------------
| #MAX_RESTORE_SESSIONS 1 # 1 Tivoli Storage Manager client session for restore
|
|
| #--------------------------------------------------------------------------
| # Number of backup copies of the archived redo logs.
| # Default: 1.
| #--------------------------------------------------------------------------
| #REDOLOG_COPIES 2 # 1 is default
|
|
| #--------------------------------------------------------------------------
| # 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 mySAP (R) should not be used together with
| # Tivoli Storage Manager API compression.
| # Default: NO
| #--------------------------------------------------------------------------

| #RL_COMPRESSION YES # NO is default
|
|
| #--------------------------------------------------------------------------
| # Specifies how many files are multiplexed into one data stream
| # to a Tivoli Storage Manager server. Multiplexing is usefull when the data
| # rate to a Tivoli Storage Manager server is higher (fast tapes, fast network)
| # than the I/O rate from a single disk.
| # The valid range of MULTIPLEXING is from 1 to 8.
| # Default: 1 (meaning no multiplexing)
| #--------------------------------------------------------------------------
| #MULTIPLEXING 3 # 1 is default
|
|
| #--------------------------------------------------------------------------
| # Specifies the block size for disk I/O (in bytes). The valid range is
| # from 4 KB to 256 KB.
| # The default values have been chosen from our performance experiments in
| # standard hardware environments.
| # Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows NT.
| #--------------------------------------------------------------------------
| BUFFSIZE 32768 # block size in bytes
|
|
| #--------------------------------------------------------------------------
| # This optional parameter controls how Data Protection for mySAP(R) uses
| # the internal buffers for transferring data during a backup.
| # Default: SIMPLE
| #--------------------------------------------------------------------------
| #BUFFCOPY SIMPLE|PREVENT|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 mySAP (R) is only activated
| # if the SAP R/3 release is 3.0C and higher and the parameter
| # MAX_VERSION is not 0.
| # Default: 0.
| #--------------------------------------------------------------------------
| #MAX_VERSIONS 4
|
|
| #--------------------------------------------------------------------------
| # Batch processing
| # Default:
| # The default for the BATCH parameter is YES for the backup run and NO for
| # the restore run if the BATCH parameter is COMMENTED OUT in this profile.
| #--------------------------------------------------------------------------
| #BATCH YES # unattended automated operation
| #BATCH NO # manual operation
|
|
| #--------------------------------------------------------------------------
| # Control of error situations
| # Default: NO.
| #--------------------------------------------------------------------------
| #EXITONERROR 3 # don’t exit if an error occurs
|
|
| #--------------------------------------------------------------------------
| # Control of information for reporting purposes, e.g. messages, statistics.
| # Default: NO (no additional data will be reported).
| #--------------------------------------------------------------------------
| #REPORT NO # no additional messages
| #REPORT YES # all additional messages
| #REPORT 2 # all additional messages + summary
|
|
| #--------------------------------------------------------------------------
| # Controls generation of a trace file.
| # Note: we recommend using the trace function only in cooperation with
| # the hotline.
| # Default: OFF
| #--------------------------------------------------------------------------
| #TRACE OFF
|
| #--------------------------------------------------------------------------
| # Specify the full path of the trace file.
| # Note: for an actual trace the string ’%BID’ will be replaced by
| # the current backupid.
| # (...\backint_%BID.trace changes to ...\backint_SAP___9809182300.trace).
| # Default: none
| #--------------------------------------------------------------------------
| #TRACEFILE x:\oracle\C21\database\backint.trace
| #TRACEFILE x:\oracle\C21\database\backint_%BID.trace
|
|
| #--------------------------------------------------------------------------
| # Denotes the maximum size of the trace file in KB.
| # If not specified, the trace file size is unlimited.
| #--------------------------------------------------------------------------
| #TRACEMAX <max. size>
| #--------------------------------------------------------------------------
| # Specify the full path of the configuration file.
| # Default: none.
| #--------------------------------------------------------------------------
| CONFIG_FILE x:\oracle\C21\database\initSID.bki
|
|
| #--------------------------------------------------------------------------
| # Number of times to retry saving/restoring a file in case an error occurs.
| # The valid range of FILE_RETRIES is from 0 to 100.
| # Default: 3.
| #--------------------------------------------------------------------------
| #FILE_RETRIES 3
|
|
| #--------------------------------------------------------------------------
| # Denotes if Data Protection for mySAP (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.
| # Values for verbosity can be ERROR, WARNING, or DETAIL.
| # Default: none.
| #--------------------------------------------------------------------------
| #LOG_SERVER servername [verbosity]
| #LOG_SERVER server_a ERROR
|
|
| #--------------------------------------------------------------------------
| # Denotes if Data Protection for mySAP (R) shall use a manual sorting file

| # for disk sorting.
| # Default: none.
| #--------------------------------------------------------------------------
| #SORT_FILE x:\oracle\C21\database\manual_sort_file
|
|
| #--------------------------------------------------------------------------
| # Denotes if Data Protection for mySAP (R) shall use a compressed filesize
| # sorting file for disk sorting.
| # For backup simulations with compression (see manual) this parameter must
| # be set to a valid file.
| # Default: none.
| #--------------------------------------------------------------------------
| #COMPR_INFO x:\oracle\C21\database\initSID.cfi
|
|
| #**************************************************************************
| # Statement for multiple Servers and multiple Paths.
| # may be used multiple times (one for each server).
| #**************************************************************************
|
|
| SERVER server_a # Servername
| SESSIONS 2 # Max sessions
| PASSWORDREQUIRED YES # Use a password
| ADSMNODE NODE # Tivoli Storage Manager Nodename
| BRBACKUPMGTCLASS MDB # Mgmt-Classes
| BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes
|
| #SERVER server_b # Servername
| # SESSIONS 2 # Max sessions
| # PASSWORDREQUIRED YES # Use a password
| # ADSMNODE NODE # Tivoli Storage Manager Nodename
| # BRBACKUPMGTCLASS MDB # Mgmt-Classes
| # BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes
|
| #**************************************************************************
| # USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa
| # Default: all days
| #**************************************************************************
|
|
| #--------------------------------------------------------------------------
| # End of profile
|
|
| END
|
Appendix B. Data Protection for mySAP Messages

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

Data Protection for mySAP process results are logged in files. These files are
located in the following paths:
| UNIX or Linux:
v $SAPDATA_HOME/sapbackup for backup and restore runs
v $SAPDATA_HOME/saparch for redo log archive runs
Windows:
v %SAPDATA_HOME%\sapbackup for backup and restore runs
v %SAPDATA_HOME%\saparch for redo log archive runs
All log files written during a backup, restore or archive are listed in summary log
files with start and end timestamps. The summary log files are located in the same
directory as the log files themselves and have the following names:
v back<SID>.log
v rest<SID>.log
v arch<SID>.log
If you are running Oracle RMAN you will also need to look up the file sbtio.log
which is specified by user_dump_dest in the Oracle control files. For most
installations it is located at $SAPDATA_HOME/saptrace/usertrace/sbtio.log. This file
contains all messages issued by the DP for mySAP RMAN connector during
operation of Oracle RMAN.

Data Protection for mySAP Message Explanations
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
BKI0000E Profile not specified. BKI0007E Mode mode requires the environment
variable environment variables to be set.
Explanation: Data Protection for mySAP cannot locate
the profile. Explanation: Not all environment variables required
have been set. At least environment variables where
User Response: Ensure that a profile is available. Note
missing.
that the BACKINT call must have the following form:
backint -p init<SID>.util . User Response: Set the missing environment
variables.
BKI0004E Function not defined.
BKI0008E The environment variable name is not
Explanation: SAPDBA, BRBACKUP, or BRARCHIVE
set correctly. The current value is value.
passed an invalid argument to DP for mySAP.
Explanation: The value of the environment variable
User Response: Ensure that you have the correct
name is wrong.
version of SAPDBA, BRBACKUP, or BRARCHIVE
installed. Valid functions are: -f backup or -f restore or -f User Response: Set name to an appropriate value.
password or -f delete or -f inquire.
BKI0020I End of program at: time
BKI0005I Start of program at: time
Explanation: DP for mySAP returned control to
Explanation: DP for mySAP received control from SAPDBA, BRBACKUP, BRARCHIVE, or BRRESTORE at
SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE at time.
time.
User Response: None.
BKI0021I Elapsed time: elapsedtime
BKI0006E Type for backup not defined [type].
Explanation: The time needed for the complete
Please use ’file’ or ’file_online’.
backup was elapsedtime.
Explanation: DP for mySAP expects as backup type
parameter only file or file_online.
User Response: If you start DP for mySAP manually
BKI0023I Time: current_time
to do a backup, ensure that the type option (-t)
Done: saved_bytes (percent) of bytes
receives the correct arguments (file or file_online). If
Estimated end time: end_time
your DP for mySAP has been invoked by one of the
SAP database utilities (e.g., BRBACKUP), ensure that Explanation: DP for mySAP finished saving a specific
the SAP backup profile init<SID>.sap is customized object at current_time. The saved_bytes amount of the
correctly) . total number of bytes have been saved. percent shows
the percentage. This DP for mySAP call will be
completed at the estimated end_time.
BKI0033E Error opening file file name: system error
description
BKI0024I Return code is: return code
Explanation: See BKI0032E.
Explanation: Shows the return code of DP for mySAP.
User Response: See BKI0032E.
A return code of 0 means no errors or warnings
occurred. If the return code is 1, at least one warning
was issued by the program. If the return code is 2, at BKI0049I Please enter password for node nodename
least one error message was issued. on server server name
User Response: For return codes other than 0, check Explanation: The password for the node nodename on
the run log for warnings or error messages. the Tivoli Storage Manager server server name has to be
entered for storing it in the DP for mySAP
configuration file.
BKI0027I Time: current_time
Objects: current_num of total_num User Response: Enter the password for the
in process: file_name corresponding Tivoli Storage Manager server.
MGMNT-CLASS: management_class
TSM Server: server name.
BKI0050I Please enter password for node nodename
Explanation: DP for mySAP started saving on server server name again
current_num files at current_time. The total number of
Explanation: In order to avoid typing errors, you have
files to save is total_num. The file file_name is currently
to enter the password twice.
being processed. The files are transferred to the Tivoli
Storage Manager server server name, which stores them User Response: Enter the password again.
in the Management Class management_class.
User Response: None. BKI0051I Password successfully verified for node
nodename on server server name.
BKI0030I Time: current_time Explanation: The password for the node nodename on
Objects: current_num of total_num the Tivoli Storage Manager server server name was
in process: file_name changed successfully.
Size: bytes MB
TSM Server: server name. User Response: None.
Explanation: DP for mySAP completed saving

current_num files at current_time. The total number of BKI0052E Password verification for node nodename
files to save is total_num. The file file_name is currently on server server name failed.
being processed. The Tivoli Storage Manager server Explanation: The password you entered for the node
server name is selected. nodename on the Tivoli Storage Manager server server
User Response: None. name was wrong.
User Response: Enter the password again. If this error
BKI0031W Object not found or not accessible: still exists, contact your Tivoli Storage Manager
objectname. administrator.
Explanation: The object was not found or is not

accessible to DP for mySAP. BKI0053I Time: current_time
Objects: current_num of total_num
User Response: Check path and name and the done: file_name with: bytes saved with
permissions of that object and try again. description object_desc.
Explanation: Data Protection for mySAP completed
BKI0032E Error opening file file name: system error saving current_num file at current_time. The total
description number of files to be saved is total_num. The file
file_name with the size bytes is saved with the
Explanation: A system error occurred during opening
description object_desc.
of the file file name. system error description will describe
the error in more detail. User Response: None.
User Response: Read the system error description.
Appendix B. Data Protection for mySAP Messages 103

BKI0054I Time: current_time BKI0061W The output file file name is not valid.
Objects: current_num of total_num
Explanation: The specified output file file name could
done: file_name with: bytes
not be created.
restored with description object_desc.
User Response: Check that file name is a valid file
Explanation: Data Protection for mySAP completed
name on your operating system. Also check that the
restoring of current_num file at current_time. The total
application has the appropriate permissions to create
number of files to be restored is total_num. The file
the file within the specified directory. The directory
file_name with the size bytes is restored with the
must already exist. If the file already exists, rename the
description object_class.
old one.
BKI0062E The input file file name is not valid.
BKI0055I Object objectname with size saved with
Explanation: Data Protection for mySAP is not able to
description description.
read the input file file name correctly.
Explanation: The object objectname was saved
User Response: Check the path and name of the input
successfully.
file and the appropriate file access permission.
BKI0063E The UTL file file name is not valid.
BKI0056I Object objectname with size restored with
Explanation: DP for mySAP is not able to read the
description description.
input file file name correctly.
Explanation: The object objectname was restored
User Response: Check the path and name of the
successfully.
profile (UTL file) and the appropriate file access
User Response: None. permission.
BKI0057I Time: current_time Object objectname with BKI0064E The option option is unknown.
size saved with description description.
Explanation: A DP for mySAP option is invalid or
Explanation: The object objectname was saved unknown.
successfully.
User Response: Check the specified option(s) and try
User Response: None. again.
BKI0058I Time: current_time Object objectname with BKI0065E The argument is missing for option
size restored with description description. option.
Explanation: The object objectname was restored Explanation: Every DP for mySAP option requires an
successfully. argument.
User Response: None. User Response: Insert the missing argument and try
again.
BKI0059E You have to set the environment
variable DSMI_CONFIG to the full BKI0101I Session session: Please enter ’cont’ to
filename of the Tivoli Storage Manager continue or ’stop’ to cancel.
client option file ’dsm.opt’.
Explanation: If DP for mySAP is running in
Explanation: Tivoli Storage Manager client option file unattended mode (profile keyword BATCH), it
not found. terminates the current run if operator intervention is
required.
User Response: Verify that the Tivoli Storage Manager
option file dsm.opt is pointed to by DSMI_CONFIG. User Response: Enter ’cont’ or ’stop’.
BKI0060E The parameter parameter is not known. BKI0102I Your reply: reply.
Explanation: The command parameter parameter for Explanation: Data Protection for mySAP indicates the
Data Protection for mySAP is unknown. reply you made.
User Response: Check the specified command User Response: None.
parameter and try again.
BKI0311E Request canceled by user. BKI0414E Error while requesting tablespace
switch.
Explanation: BACKINT terminated at user’s request.
Explanation: BRBACKUP reported an error while
User Response: None
trying to switch a tablespace in BEGIN or END backup
mode.
BKI0400I TDP is waiting for BRBACKUP
User Response: Contact your mySAP administrator.
Explanation: DP for mySAP is waiting for
BRBACKUP to set a tablespace in the begin/end
BKI0450I Version 2 restore: file
backup mode.
Explanation: A restore of data backed up with DP for
mySAP version 2 was executed.
BKI0405I TDP waited num_sec sec. for
BRBACKUP in util_file_online
communication. BKI0451I This version of Data Protection for
mySAP (R) (will expire on date.
Explanation: DP for mySAP waited num_sec seconds
for BRBACKUP to set a tablespace in begin/end Explanation: This is a test version that will expire on
backup mode. date.
User Response: None. User Response: None.
BKI0410E Cannot open or delete switch file file BKI0452E This version of Data Protection for
name. Check permissions. mySAP (R) has expired.
Explanation: If DP for mySAP is not installed Explanation: This is a test version that has expired.
| correctly (as the root user on UNIX or Linux or
User Response: Order a release version of Data
administrator group on Windows) then DP for mySAP
Protection for mySAP or contact your IBM/Tivoli Sales
is not able to open the necessary communication file to
Representative.
the mySAP system.
User Response: Check the file permission.
BKI0453W This version of Data Protection for
mySAP (R) will expire in number days.
BKI0411E Maximum time waiting for BRBACKUP
Explanation: This is a test version with a time limit. It
expired.
will expire in number days.
Explanation: The SAP database utilities did not
User Response: Order a release version of Data
respond within the expected time.
Protection for mySAP or contact your IBM/Tivoli Sales
User Response: Contact your mySAP administrator. Representative before the version expires.
BKI0412E BRBACKUP wasn’t able to switch BKI0454I *** This copy is NOT FOR RESALE. ***
requested tablespace in BEGIN/END
Explanation: This version is not for resale.
BACKUP mode.
Explanation: DP for mySAP could not continue the
backup, because BRBACKUP was not able to switch the
requested tablespace in BEGIN or END backup mode. BKI0455E License file file name does not exist.
This is necessary for locking the tablespace.
Explanation: The license file agent.lic was not found
User Response: Contact your mySAP administrator. where expected.
User Response: Make sure that the agent.lic file
BKI0413E Error while requesting tablespace resides in the same directory as the init<SID>.utl file.
switch.
Explanation: BRBACKUP could not switch tablespace BKI0456E Unable to access license file file name.
in BEGIN or END backup mode.
Explanation: The license file could not be accessed.
User Response: Contact your mySAP administrator.
User Response: Make sure the access permissions
allow read/write access.

BKI0457E License file file name contains invalid BKI1004W You should specify the
data/checksum. BACKUPIDPREFIX before the
TRACEFILE statement, so that the
Explanation: The license file is invalid.
BACKUPIDPREFIX can be used in the
User Response: Make sure you have the right tracefile name.
agent.lic file for the right platform installed.
Explanation: The BACKUPIDPREFIX is used to build
agent.lic files are platform dependent.
the Name of the tracefile. Therefore,
BACKUPIDPREFIX must be specified before the
| BKI0458I Fake-Mode is activated. TRACEFILE statement.
| Explanation: This message signals that the current User Response: Define a 6-character
| operation is a simulated operation. Simulations can be BACKUPIDPREFIX in the DP for mySAP profile (e.g.,
| performed using the Administration Assistant. SAP___, BKI___)
| User Response: None.

BKI1005W The tracefile name trace_filename should
be absolute.
BKI0459E More than one mux file is found with
the same name detailed backup description. Explanation: None.
Explanation: Two or more data sources with name User Response: Specify an absolute tracefile name, for
detailed backup description exist. example /oracle/C21/saptrace/tracefile .
User Response: Contact your Data Protection for
mySAP administrator. BKI1006E The SERVERNAME must be less than
max_char characters.
BKI1000E Syntax error in line line: statement Explanation: You have used a SERVERNAME with
more than max_char characters.
Explanation: The statement statement in the DP for
mySAP profile is unknown or incorrect. User Response: Use a shorter SERVERNAME.
User Response: Correct the error and try again.
BKI1007E The NODENAME must be less than
BKI1001E Syntax error in file file name. Exiting
Program. Explanation: You have used a NODENAME with
more than max_char characters.
Explanation: DP for mySAP has detected an syntax
error in the file file name and stops any action. User Response: Use a shorter NODENAME.
User Response: Correct the error(s) in the file file name
and try again. BKI1008E The MANAGEMENTCLASSNAME
must be less than max_char characters.
BKI1002E BACKUPIDPREFIX must be Explanation: You have used a
number_of_characters characters. MANAGEMENTCLASSNAME with more than
Explanation: The length of BACKUPIDPREFIX must
be number_of_characters characters. User Response: Use a shorter
MANAGEMENTCLASSNAME.
User Response: Enter a BACKUPIDPREFIX with the
required length (e.g., SAP___, BKI___).
BKI1009W Please set MULTIPLEX to a number
between 1 and max_multiplex. Now it is
BKI1003W Please set REDOLOG_COPIES to a set to act_multiplex.
number between 1 and max_copies. Now
it is set to act_copies. Explanation: You have set multiplexing to an
unsupported number. Data Protection for mySAP now
Explanation: DP for mySAP currently supports 1 to 9 uses act_multiplex.
copies of offline redo log files.
User Response: Set multiplexing to a number between
User Response: Adapt the REDOLOG_COPIES 1 and max_multiplex.
settings in the DP for mySAP profile.
BKI1010W The configfile name
configuration_filename should be absolute.
BKI1016W The trace file name file name could not
Explanation: None.
be opened for writing!
User Response: Specify an absolute file name, for
Explanation: The trace file could not be opened for
example /oracle/C21/dbs/initC21.bki
writing.
User Response: Ensure that you have specified a
BKI1011W The sortfile name sortfile_filename should
correct path for the trace file.
be absolute.
Explanation: None.
BKI1017E The server server name is already
User Response: Specify an absolute file name, for defined. Please use another name!
example /oracle/C21/dbs/sortfile.
Explanation: The server you want to configure is
already defined.
| BKI1012E Configfile not found or permission
User Response: Specify another server name. Server
| denied: configuration_filename.
names have to be unique.
Explanation: Data Protection for mySAP is unable to
read the file configuration_filename.
BKI1019E Failed to respond to a message received
User Response: This error could have various reasons, from XINT.
try the following:
Explanation: This messages indicates an internal error.
1. Check the path of the configuration file. The path
must be specified in the profile (parameter User Response: Contact your Data Protection for
CONFIG_FILE). mySAP support.
2. Make sure that the file access permissions are set
correctly.
BKI1020W The compress info file file name should
be absolute !
BKI1013E Profile not found or permissions denied:
profile_filename. Explanation: The argument for the parameter
COMPR_INFO in the profile is an relative filename.
Explanation: Data Protection for mySAP is unable to
open the profile profile_filename. User Response: Always use an absolute filename as
argument for the parameter COMPR_INFO.
User Response: Ensure that the SAP backup profile
init<SID>.sap contains a valid entry util_par_file for
the DP for mySAP profile. Furthermore, this file must BKI1021E ProLE terminates the connection due to
| be readable by DP for mySAP. See: DP for mySAP a previous error.
| Installation & User’s Guide for Oracle Chapter: ’Installing Explanation: A fatal error has occurred which caused
| Data Protection for mySAP’ for details. a shutdown of the communication channel between the
ProLE process and this application.
BKI1014I The parameter PERF_MONITOR is no User Response: Look for previous error messages to
longer supported. Now it is enabled by detect the root cause of the problem.
default.
Explanation: For version 2.7 or later of Data BKI1022E ProLE terminates the connection due to
Protection for mySAP , the Performance Monitor of the a previous error.
Administration Assistant can be used by default.
Therefore, the profile parameter PERF_MONITOR is no Explanation: See message BKI1021E.
longer needed. User Response: See message BKI1021E.
BKI1023W Could not establish connection to log
BKI1015I The parameter BACKAGENT is no server log server name.
longer needed. | Explanation: In the DP for mySAP profile, log server
Explanation: For version 2.7 or later of Data log server name is specified (keyword LOG_SERVER).
Protection for mySAP.com, only one executable, called However, a connection to the server named could not
BACKINT, will be provided and needed. The former be established. No log records are sent to the log server.
executable, called BACKAGENT, will no longer be User Response:
supported or needed.

v Check that the server name defined with keyword
BKI1205E If you want num_redo
LOG_SERVER is spelled correctly in the Data
REDOLOGCOPIES on Tivoli Storage
Protection for mySAP profile.
Manager-Server servername, you should
v Make sure there is a SERVER section in the profile give me at least num_mc different
for the log server defined with keyword Archive Management Classes.
LOG_SERVER.
Explanation: DP for mySAP requires that the number
v Check the corresponding SERVER section and correct
of different Archive Management Classes (parameter
any setup problems.
BRARCHIVEMGTCLASS) on the Tivoli Storage
v Make sure that the log server named is available. Manager servers is equal to or greater than the number
of redo log copies (parameter REDOLOG_COPIES).
BKI1200E Cannot read/write file: file name. User Response: Define at least as many different
Explanation: DP for mySAP is unable to read or write Archive Management Classes as redo log copies
a data file (file name) of a tablespace being backed up requested.
or restored.
User Response: Check the file access permission of BKI1206W If you want num_redo
the affected file(s). Try again. If the problem still exists, REDOLOGCOPIES on Tivoli Storage
contact the mySAP administrator. Manager Server server name, you should
give me at least num_mc different
Archive Management Classes.
BKI1201E There are no Tivoli Storage Manager
Servers available. Explanation: The message appears during a
BRBACKUP run. A BRARCHIVE run afterwards would
Explanation: DP for mySAP cannot locate a Tivoli fail.
Storage Manager server.
User Response: Define at least as many different
User Response: Install and specify at least one Tivoli Archive Management Classes as log file copies
Storage Manager server in the DP for mySAP profile requested.
(keyword SERVER).
BKI1207E Directory backup not supported
BKI1202E You must specify either
MAX_SESSIONS or all off Explanation: This option is not yet available.
MAX_ARCH_SESSIONS, User Response: Wait for a future release of DP for
MAX_BACK_SESSIONS and mySAP, which supports this option.
MAX_RESTORE_SESSIONS
Explanation: There is a setup error with the BKI1208W The object file name will be retried
SESSIONS parameters within the DP for mySAP [retry_num]
profile.
Explanation: There was an error with the object
User Response: Specify either MAX_SESSIONS and file_name. DP for mySAP will try to save/restore the
one of the more specific parameters object one retry_num times.
MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS or
MAX_RESTORE_SESSIONS or all of the three specific User Response: Look at the error messages in the DP
session parameters without the MAX_SESSIONS for mySAP protocol and correct the error for the next
parameter. run.
BKI1203E Not enough sessions available (number BKI1209E Object not found or not accessible
of sessions required and number of objectname.
sessions available). Explanation: DP for mySAP cannot locate the Oracle
Explanation: The sum of available sessions specified object objectname.
in the various server statements (parameter SESSIONS) User Response: The backup integrity is affected.
does not cover the required number of sessions Contact the SAP or DP for mySAP support.
(parameter MAX_SESSIONS).
User Response: Change the values of the BKI1210E Input file not found or not accessible file
corresponding parameters in the DP for mySAP profile, name.
so that the condition mentioned in the explanation is
fulfilled. Explanation: DP for mySAP cannot locate the
temporary file file name. This file contains the list of
Oracle objects to be backed up/restored. It is passed to
DP for mySAP by BRBACKUP, BRARCHIVE or
BKI1217E There are no BRARCHIVEMGTCLASSES
BRRESTORE.
available.
User Response: Ensure that you have the correct
Explanation: The BRARCHIVEMGTCLASSES you
version of SAPDBA, BRBACKUP, BRARCHIVE or
have specified in your init<SID>.utl file are not correct.
| BRRESTORE installed. See: DP for mySAP Installation &
| User’s Guide for Oracle Chapter: ’Prerequisites for the User Response: Check the management classes on the
| Installation of Data Protection for mySAP’ for details. TSM server and specify correct ones.
BKI1211E There is something wrong with your BKI1222E Version missmatch error. Check setup
CONFIG_FILE file name. (%1$S:%2$S).
Explanation: There is a problem with your DP for Explanation: The version numbers of the installed
mySAP configuration file setup. executables BACKINT and ProLE do not match.
User Response: Check the file permission and the file User Response: Check your setup or contact DP for
name specified in the DP for mySAP profile keyword mySAP support.
CONFIG_FILE.
BKI1223W A problem occurred during send of
BKI1212W The file file name was not found in the performance data to Administration
manual sorting file. Assistant .
Explanation: The file you want to back up was not Explanation: There was a problem sending the
found in the manual sorting file. performance data to the Administration Assistant over
the network.
User Response: Check and correct the manual sorting
file so that it contains all the files you are backing up. User Response: Check your setup or contact DP for
mySAP support.
BKI1213I Program ended with code = return code
BKI1224W Unable to initialize connection to
Explanation: The return code of the program is
Administration Assistant.
displayed.
Explanation: There was a problem initializing the
connection to the Administration Assistant over the
network.
BKI1214E TSM Error: error text
User Response: Check your setup or contact DP for
Explanation: The specified TSM error occurred. mySAP support.
User Response: Check error text and correct the
problem. BKI1227I Average compression factor was number.
Explanation: The data transferred had been
BKI1215I Average transmission rate was number compressed by the factor number.
GB/h (number MB/sec).
User Response: None
Explanation: The average transmission rate is
displayed.
| BKI1228W Server server name can not be used with
User Response: None. | password access method GENERATE in
| this environment. The process is
| running with user ID number but the
BKI1216E There are no BRBACKUPMGTCLASSES | effective user ID is number.
available.
| Explanation: The user ID and the effective user ID of
Explanation: The BRBACKUPMGTCLASSES you have | the process are different. In order to utilize the
specified in your init<SID>.utl file are not correct. | password access method GENERATE the IDs must be
User Response: Check the management classes on the | equal.
TSM server and specify correct ones. | User Response: Change the value for the parameter
| ″PASSWORDACCESS″ in the file dsm.sys (UNIX and
| Linux) or servername.opt (Windows) from ’generate’ to
| ’prompt’. Reset the password for this node at the Tivoli
| Storage Manager server and run backint -f password.
| This prompts you for the password and stores it

| encrypted in the DP for mySAP configfile. Each time
BKI2005E Illegal parameter in message from
| your password expires you have to repeat the last step. ProLE. Exiting...
Explanation: This error occurs if the versions of ProLE
| BKI1229E Value for parameter BUFFSIZE (actual
and the executable BACKINT or the backup library
| cur_number, maximum max_number) is
libtdp_r3 do not match.
| too large for BUFFCOPY mode
| PREVENT.″ User Response: Check the versions of ProLE and
BACKINT/backup library libtdp_r3 you are currently
| Explanation: Explanation: To utilize the BUFFCOPY using.
| mode PREVENT the value for the parameter BUFFSIZE
| must not be larger than max_number.
BKI2006E General exception in dispatcher.
| User Response: There are two ways to resolve this
Exiting...
| error. Edit the profile and either select a BUFFSIZE
| which is less or equal to max_number or set BUFFCOPY Explanation: Internal DP for mySAP error.
| to SIMPLE or AUTO. There is no general
User Response: Contact DP for mySAP support.
| recommendation since it depends on the whole
| environment which change may improve the
| performance more. BKI2007E Unknown Port: port
Explanation: The port specified for communication
BKI2000I Successfully connected to ProLE on port between ProLE and BACKINT is unknown.
portnumber.
User Response: Check the port value specified when
Explanation: One of the Data Protection for mySAP ProLE was started. Additionally, check the environment
modules BACKINT or the backup library libtdp_r3 variable PROLE_PORT for the BACKINT environment.
initiated a successful connection to the background These two values must match.
process ProLE on port portnumber.
User Response: None. BKI2008E Unable to connect to ProLE.
Explanation: Internal DP for mySAP error.
BKI2001E Socket error while connecting to ProLE:
reason. User Response: Contact DP for mySAP support.
Explanation: The DP for mySAP background process

ProLE is not running. BKI2009I Deleting all versions with version
number <= version_number on server
User Response: Start ProLE manually and try again. server_name.
Explanation: All full database backups and their
BKI2002E No valid callback function of type corresponding log file backups will be deleted from
func_type supplied. Tivoli Storage Manager storage, if their version number
is less than or equal to version_number.
Explanation: Internal DP for mySAP error
BKI2010E Error occurred processing FRONTEND

BKI2003I File file_name, BID deleted.
Explanation: An error occurred during the frontend
Explanation: The file file_name with the backup ID
processing.
BID was deleted from the Tivoli Storage Manager.
User Response: Check the frontend script/program
and the settings in the DP for mySAP profile (keyword
FRONTEND) and try again.
BKI2004E Connection to ProLE lost.
Explanation: During Data Protection for mySAP BKI2011E Error occurred processing BACKEND.
operation, the connection to ProLE was lost. Network
Explanation: An error occurred during the backend
problems could be the reason.
processing.
User Response: Check your network environment and
User Response: Check the backend script/program
if ProLE is still running, try again.
and the settings in the DP for mySAP profile (keyword
BACKEND) and try again.
BKI2012E Passwords do not match. Try again. BKI2021E Unable to delete file file name: description
Explanation: The first and second password you Explanation: Unable to delete the file ’file name’.
entered do not match. ’description’ may contain the system error text.
User Response: Enter the password correctly. User Response: Check the ’description’. If the error
persists, contact your service representative.
BKI2013I Starting FRONTEND Program.
BKI2022E Unable to change mode of file file name:
Explanation: The frontend program is executing.
description
Explanation: Unable to change mode of file ’file name’.
’description’ may contain the system error text.
BKI2014I FRONTEND program finished.
User Response: Check the ’description’. If the error
Explanation: The frontend program is finished. persists, contact your service representative.
BKI2023E Error occurred during trace connection
to ProLE. Tracing will stop now.
BKI2015I Starting BACKEND program.
Explanation: Error occurred during trace connection
Explanation: The backend program is executing. to ProLE.
User Response: None. User Response: Tracing will stop. If the problem
persists, contact your service representative.
BKI2016I BACKEND program finished.
Explanation: The backend program is finished. BKI2024E Error in connection to ProLE.
User Response: None. Explanation: The connection to ProLE terminated

unexpectedly. This message might be displayed due to
previous errors or after an unexpected termination of
BKI2017I Blocksize is set to num_bytes bytes. the ProLE process.
Explanation: The operational blocksize of DP for User Response: Check for other error messages and
mySAP is num_bytes bytes. restart ProLE if necessary. Try again. If the problem
User Response: None. persists, contact DP for mySAP support.
BKI2018E Exception in main message loop: BKI2025E Failed to respond to a message received
description from ProLE.
Explanation: An error occurred during processing. Explanation: This is an internal error

The error may contain a descriptive text. User Response: Contact your DP for mySAP support.
User Response: Contact your service representative.
BKI2026E Unexpected exception in handler: handler
BKI2019E Socket error while connecting to ProLE Explanation: This is an internal error.
on port number for tracing: description
User Response: Contact your DP for mySAP support.
Explanation: During processing, a socket error
occurred on port ’number’. ’description’ may contain the
system error text. BKI2027I Using TSM-API version your api version
(compiled with compiled with version).
User Response: Check the ’description’. If the error
persists, contact your service representative. Explanation: Version information about the TSM-API.
User Response: None
BKI2020E Error occurred for trace connection to
ProLE on port number. BKI2028W Unable to terminate session session.
Explanation: The network connection that is used for Explanation: This is an internal error during cleanup
tracing generated an error on port ’number’. that has no effect on the success of the service.
User Response: Contact your service representative. User Response: None

| BKI2029E The requested buffer allocator cannot be BKI4003E Error reading file file name. Only read
| instantiated due to the following num_bytes out of all_bytes.
| incompatibility: expression.
Explanation: An error occurs reading the file file name.
| Explanation: This is an internal DP for mySAP error. Only num_bytes of all_bytes could be read.
| User Response: Contact your DP for mySAP support. User Response: Try your last action again. If the error
still exists, contact DP for mySAP support.
| BKI2031E A buffer allocator cannot
| simultaneously satisfy all of the BKI4004E Error writing file filename. Only wrote
| following properties: list of properties num_bytes out of all_bytes.
| Explanation: This is an internal DP for mySAP error. Explanation: An error occurs writing the file file name.
Only num_bytes of all_bytes could be written.
| User Response: Contact Data Protection for mySAP
| support. User Response: Try your last action again. If the error
still exists, contact DP for mySAP support.
| BKI2033E Cannot instantiate allocator of type
| allocator type with the following BKI4005E Error allocating memory block for file
| additional properties: list of properties file name. BLOCKSIZE may be too large.
| Explanation: This is an internal DP for mySAP error. Explanation: DP for mySAP was not able to request
new memory blocks during the backup of file file name.
| User Response: Contact your Data Protection for
| mySAP support. User Response: Verify that you have set a valid value
for BLOCKSIZE. If you are not sure what value is
valid, comment it out so the default value is used.
BKI4000W The attributes of file file name cannot be
Furthermore, you can check if you have enough RAM
restored. Reason: errno (error_num)
available with your machine. Also, check the memory
error_desc.
usage during backup. It may be necessary to stop
Explanation: The file file name was restored another application, increase memory, or change the
successfully but one or more file attributes (permission, configuration of DP for mySAP.
ownership, date/time) of the file file name cannot be
restored correctly.
BKI4006E Error allocating memory block for file
User Response: Check the error number error_num file name. BLOCKSIZE may be too large.
and the error description error_desc to avoid this
problem in the future. An initial solution could be to
set the appropriate correct permission for the file file User Response: See BKI4005E.
name manually.
BKI4007E File filename cannot be read. Reason:
BKI4001E File file name cannot be created. Reason: errno(errno number) errno text.
errno (error_num) error_desc.
Explanation: Data could not be read due to some
Explanation: The file file name to be restored could not system error. Check errno text for further information. If
be created/written. It is possible, that you do not have this error recurs, this might indicate some hardware
the appropriate rights for writing the file file name to problems.
the destination path.
User Response: Contact your system administrator.
User Response: Check the error number error_num
BKI4008E File filename cannot be opened. Reason:
problem in the future. Furthermore, check the write
errno(errno number) errno text.
permission of the user who started the restore.
| Explanation: DP for mySAP could not open the file
file name due to some system specific problems.
| BKI4002E Error during write of file file name.
Reason: errno (error_num) error_desc. User Response: Contact your system administrator.
Explanation: An error occurs during the restore
process of the file file name.
User Response: Check the error number error_num
problem in the future.
BKI4009E Not enough space to write file file name. BKI5006E Tivoli Storage Manager Error:
Possible reasons: disk full or ulimit error_message
exeeded.
Explanation: The system rejected a request to write
data into file file name. The storage media might not
have enough free space to keep the file or the system
rejected writing the file due to administrative resource BKI5007E Tivoli Storage Manager Error:
constraints such as ulimits. error_message
User Response: Contact your system administrator. Explanation: See BKI5001E.
BKI5000E Tivoli Storage Manager Error:
error_message
Explanation: During a connection of DP for mySAP to error_message
Tivoli Storage Manager server, a Tivoli Storage
Manager error error_message occurred. Explanation: See BKI5001E.
User Response: Use the Tivoli Storage Manager User Response: See BKI5001E.
Messages guide and correct the Tivoli Storage Manager
server error. Try your last action again. BKI5009E Tivoli Storage Manager Error:
error_message
BKI5001E Tivoli Storage Manager Error: Explanation: See BKI5000E.
error_message
Explanation: During a connection of DP for mySAP to
Tivoli Storage Manager server, a Tivoli Storage
Manager error error_message occurred. BKI5010E Tivoli Storage Manager Error:
error_message
User Response: Use the Tivoli Storage Manager
Messages guide and correct the Tivoli Storage Manager Explanation: See BKI5000E.
server error. Try your last action again. User Response: See BKI5000E.
BKI5002E Tivoli Storage Manager Error: BKI5011E Tivoli Storage Manager Error:
error_message error_message
Explanation: See BKI5001E. Explanation: See BKI5000E.
User Response: See BKI5001E. User Response: See BKI5000E.
BKI5003E Tivoli Storage Manager Error: BKI5012E Cannot open TSM API message text file.
error_message Check if DSMI_DIR is set correctly.
Explanation: See BKI5001E. Current value of DSMI_DIR is: value
User Response: See BKI5001E. Explanation: The TSM-API could not be initialized.
User Response: Correct the value of the environment
| BKI5004W Tivoli Storage Manager Error: variable DSMI_DIR.
| error_message
| Explanation: See BKI5001E. BKI5013E Value for name is too long. Current
value: value
| User Response: See BKI5001E.
Explanation: The value of the environment variable
name has too many digits.
error_message User Response: Check if the variable is set correctly.


BKI5014E Tivoli Storage Manager Error: BKI7002E Bad mode specified.
error_message
Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or
User Response: See BKI5000E. contact your Oracle database administrator.
BKI5015W Data description could not be restored, BKI7012E Invalid arguments during call of
because it was backed up with a newer function.
version (objInf=support information)
Explanation: The TSM server hosts backups (i.e. data
User Response: See your Oracle documentation or
description) which were made with a new version of
contact your Oracle database administrator.
backint. Backint ignores this data in the further
processing.
BKI7020E Bad handle rman_handle during call of
User Response: Upgrade backint
function.
| BKI5016I Time: current_time New TSM session
| created: MGMNT-CLASS: User Response: See your Oracle documentation or
| management_class, TSM-Server: contact your Oracle database administrator.
| server_name, type: session_type.
| Explanation: A new session to TSM server server_name BKI7021E Bad flags during call of function.
| has been established at current_time. Data will be stored
| in management class management_class. Explanation: This is an RMAN internal error.
| User Response: None. User Response: See your Oracle documentation or

| BKI5017E Internal Tivoli Storage Manager Error:

| Transaction succeeded although it was BKI7049I The default ProLE port will be used.
| expected to fail. Explanation: The port for the internal communication
| Explanation: An internal Tivoli Storage Manager error of DP for mySAP is set during installation. The
| occurred. message indicates that this port is being used.
| User Response: Retry the action. If the error occurs User Response: None.
| again contact your DP for mySAP support.
BKI7051E The environment variable
| BKI5018E The requested buffer has a size XINT_PROFILE is not set. It must be set
| (current_size bytes) that is smaller than and contain the full qualified path to
| requested requested_size. the *.utl file to be used.
| Explanation: The request for a new buffer returned Explanation: The way DP for mySAP works is
| successful. The buffer, however, has not the requested specified in a profile. When called, DP for mySAP looks
| size. for the environment variable XINT_PROFILE which
must contain the fully qualified path to the profile.
| User Response: Check if the system is running low on
| memory and retry the action. If the error occurs again User Response: Check the environment for
| contact your DP for mySAP support. XINT_PROFILE of the user who started DP for mySAP.
BKI7001E Backup file file name already exists. BKI7053E Service setup failed due to previous
error.
Explanation: The initialization of DP for mySAP failed
User Response: See your Oracle documentation or due to previous errors.
User Response: Check the DP for mySAP log file for
further detailed messages.
| depending on the RMAN setup. On Windows, it is
BKI7055E Service open failed due to previous
| written just once.
error in data mover.
| User Response: None, if the right version is used. If
Explanation: The DP for mySAP command could not
| the version within the log does not match the installed
be started due to previous errors.
| version see ’Troubleshooting’ in Appendix C.
BKI7303W Profiles for DP ESS for mySAP are
different.
BKI7056E Service open failed because configured backup: file name
TSM server could not be accessed. restore: file name
Explanation: The DP for mySAP command could not Explanation: During backup the profile used by DP
be started because the TSM server defined in the profile for IBM ESS for mySAP can be determined
could not be accessed. automatically. For restore and inquire operations the
profile for DP for IBM ESS for mySAP must be
specified in the profile using the parameter FCS_FILE.
For restore DP for IBM ESS for mySAP must use the
same profile as for backup.
BKI7057E Service open failed because all
User Response: Correct the entry for the FCS_FILE
configured sessions are currently in use.
parameter in the profile (init<SID>.utl).
be started because all configured sessions in the profile
BKI7304I Performing DISK ONLY backup
are currently in use.
Explanation: The data for this backup is stored on ESS
| User Response: With Oracle RMAN the number of
disks only and will not be sent to TSM.
| channels configured either in SAP profile or the RMAN
| script must be less or equal to the maximum number of User Response: None
| allowed sessions (MAX_SESSIONS). If multiple servers
| are used see: DP for mySAP Installation & User’s Guide
BKI7305E Error during call to DP ESS for mySAP:
| for Oracle under ’Multiple Servers’ in Chapter
error message
| ’Adjusting Your System’. Also check the DP for mySAP
| log file for further detailed messages. Explanation: DP for IBM ESS for mySAP could not
process the requested operation successfully. Processing
may not stop at this point. Depending on the type of
BKI7058E Service open failed because more than
request (backup to both TSM and ESS disks or to ESS
one file is found with the same name.
disks only, restore of data which is available on both
Explanation: The DP for mySAP command could not TSM and ESS disks or on ESS disks only) there are
be started because two or more files with the same possibilities to recover from this error and continue
name were found. operation.
User Response: Check the DP for mySAP log file for User Response: Use the information from error message
further detailed messages. and the output of DP for IBM ESS for mySAP to
determine the cause of the problem and try again.
BKI7059E Service open failed because cause the
file is not found. BKI7307W DP ESS mySAP reported an error
during FLASHCOPY operation. Do you
want to continue to backup to TSM?
be started because a file specified was not found.
Explanation: The backup was requested to be stored
on both the TSM server and the ESS disks. The
flashcopy operation to ESS disks has failed. Backup can
continue to save data on the TSM server only.
| BKI7060I Data Protection for mySAP
User Response: Enter ’stop’ if you want to solve the
| <version>.<release>.<modification>
cause of this error and to try again. Enter ’cont’ if you
| (<build number>) <build date> session:
want to save this data on the TSM server only.
| process ID
| Explanation: This message is to verify the version of
| the Data Protection for mySAP shared library used for
| backup. On UNIX and Linux systems this message will
| be written multiple times into the log per backup

BKI7308E DISK ONLY backup has failed. BKI7313W Inquire results from DP ESS mySAP are
not available
Explanation: The current backup tried to store data on
ESS disks only and did not finish successfully. Explanation: DP for mySAP was unable to retrieve
information from DP for IBM ESS for mySAP about
User Response: Check the output from DP for IBM
available backups on ESS disks. This message may be
ESS for mySAP prior to this error message to detect the
issued in consequence of message BKI7305E.
root cause of this error and try again.
User Response: Check the output from DP for IBM
ESS for mySAP to determine the cause of the error and
BKI7309W DP ESS mySAP reported an error
try again.
during FLASHCOPY operation. Do you
want to continue to restore from TSM?
BKI7314E The data you want to restore is not
Explanation: The data you wanted to be restored is
available on the TSM server.
located on the TSM server and ESS disks. The
flashcopy operation from ESS disks has failed. The Explanation: If a restore from ESS disks can not be
process can continue to restore data from the TSM finished successfully DP for mySAP tries to continue to
server. restore data from the Tivoli Storage Manager server.
But if the backup was performed on ESS disks only, the
User Response: Enter ’stop’ if you want to resolve the
data can not be found on the TSM server.
cause of this error and to try again. Enter ’cont’ if you
want to restore from the TSM server. User Response: Check the output from DP for IBM
ESS for mySAP prior to this error message to detect the
root cause of this error and try again.
BKI7310W DP ESS mySAP reported an error
during FLASHCOPY operation.
CAUTION: Not all filesystems are | BKI7315W The copy process of the files you want
available. Do you want to retry the | to restore is not yet finished. If you
operation? | continue the files will be restored from
| TSM.
Explanation: In contrast to message BKI7309W not all
file systems are mounted. In this case it is not possible | Explanation: The flashcopy process running in the
to continue the restore from the TSM server. | background has not finished moving the files from the
| source to the target volumes. A flashcopy restore
User Response: Enter ’stop’ if you want to terminate
| (flashback) of these volumes is currently not possible.
this restore process. Enter ’cont’ if you want to retry the
flash copy process. | User Response: After that message you will be asked
| if you want to continue or stop this operation. If you
| want to wait until the flashcopy process has finished
BKI7311I Profile used by DP ESS mySAP:
| choose ’stop’ and the restore attempt will terminate. If
Explanation: The message shows the name of the | you choose ’continue’ Data Protection for mySAP tries
profile used by DP for IBM ESS for mySAP | to restore the data from TSM if available.
User Response: None
BKI7316I The following backup types for the
BACKUPID Backup ID have been found:
BKI7312W Profile for DP ESS mySAP not specified - TSM
in profile. For restore this must be - FLASHCOPY
specified
Explanation: The backup for the backup ID Backup ID
Explanation: For restore and inquire operation in was stored on the Tivoli Storage Manager as well as on
conjunction with DP for IBM ESS for mySAP this ESS disks. For restore both data sources can be used.
parameter is mandatory. Without this parameter a
restore using DP for IBM ESS for mySAP is not User Response: None.
possible and DP for mySAP will continue to
inquire/restore from the TSM server only.
BKI7318E The DP ESS mySAP profile file name is
User Response: Add the parameter FCS_FILE to the not valid.
DP for mySAP profile
Explanation: The profile for DP for IBM ESS for
mySAP specified in init<SID>.utl could not be
accessed.
User Response: Check the file name and the
permissions for this file and try again.
available from the TSM server. So you may continue to
BKI7319I Start TSM restore
restore this data without the flashcopy functionality
Explanation: The restore uses data from Tivoli Storage from TSM server.
Manager.
User Response: Enter ’stop’ if you want to try to
User Response: None restore a different set of files. Enter ’cont’ if you want
to restore this data from TSM server.
BKI7320I Start FLASHCOPY restore.
BKI7324E FLASHCOPY restore of multiple backup
Explanation: The restore uses data from ESS disks.
IDs in one run is not possible.
User Response: None
Explanation: The data requested for this restore
belongs to multiple backup IDs
BKI7321E The DP ESS mySAP profile file name
User Response: Make sure the files you want to
found in parameter FCS_FILE of the DP
restore belong to one single backup ID and try again.
mySAP profile can not be used if you
need to restore this backup.
BKI7535W Error executing command command name.
Explanation: In the DP for mySAP profile the
Reason: errno (error number) explanation.
FCS_FILE parameter is set, however the DP for IBM
ESS for mySAP profile specified either Explanation: The command command name could not
v is not a DP for IBM ESS for mySAP profile be executed successfully.
v does not point to the same DP for IBM ESS for
User Response: Check the explanation explanation and
mySAP configuration file which was used by the
the preceding output of the command execution to
preceding DP for IBM ESS for mySAP splitint
detect the cause of the error.
operation.
User Response: You need
BKI7536I Execute command command name.
v to correct the FCS_FILE parameter thus a valid DP
for IBM ESS for mySAP profile is used, e.g. the file Explanation: The command command name is executed
DP for IBM ESS for mySAP had used when running by the application. This message is followed by the
its flashcopy function in the preceeding brbackup output of the command executed.
task (see preceeding message BKI7303W) User Response: None
v to ensure that if different DP for IBM ESS for
mySAP profiles are used, all use the same control file
(the value of the IDS_CONTROL_FILE parameter in | BKI8201E SIMULATION CANCELED BY
the DP for ESS profile) | PRODUCTION OPERATION!!!
| Explanation: The current operation was a simulation
BKI7322E Request for a partial FLASHCOPY | performed via the Administration Assistant. This
Restore or FLASHCOPY Restore with | simulation was canceled since a production operation
’brrestore -m all’ is not supported. In | (backup or restore) has been started.
case of brrestore attempt rerun with -m | User Response: Check your backup schedule and run
full. | simulations only when no other operations are
Explanation: DP for IBM ESS for mySAP can only | scheduled.
restore the whole content of a backup and not only a
subset of a disk backup as requested. Most likely this is BKI9000E System error: error
caused by running brrestore with the option ’-m all’.
Explanation: DP for mySAP has found the following
User Response: Restore complete backups only, e.g. error: error. This is a ’catch-all’ error code for
run brrestore with the option ’-m full’. unpredictable system errors.
User Response: Contact your service representative.
BKI7323W Request for a partial FLASHCOPY
restore or FLASHCOPY restore with
’brrestore -m all’ is not supported. If BKI9001E Internal error: error
you want to restore the backup: Explanation: DP for mySAP has found the following
- with FLASHCOPY restore enter ’stop’ internal error: error.
and rerun brrestore with ’-m full’
- from TSM enter ’cont’ User Response: Contact Data Protection for mySAP
support.
Explanation: This message has the same reason as
message BKI7322E, but in this case the data is also

BKI9002E Error in stream task: %1$S BKI9200E Additional support information: An
Exception was thrown at position:
Explanation: There was an error in the processing of a
position.
data stream. Data Protection for mySAP will stop
processing. Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
User Response: Contact Data Protection for mySAP
Otherwise contact your Data Protection for mySAP
support.
support
BKI9003E Incompatible components installed:
support.
component name component name
Explanation: The components mentioned in the
BKI9201E Additional support information: An
message text can not be used together. This may be the
result of an incomplete upgrade.
position.
Explanation: This error message typically follows a
BKI9005E A not supported by B. Otherwise contact your Data Protection for mySAP
support
Explanation: The installed version of product B does
not support product A. Most likely you need to User Response: Contact Data Protection for mySAP
upgrade product B. support.
User Response: Contact the Data Protection for
mySAP support. BKI9202E Additional support information: An
position.
BKI9006E Internal error while reading
environment variable: variable. Explanation: This error message typically follows a
Explanation: This is an internal error. Otherwise contact your DP for mySAP support.
User Response: Contact Data Protection for mySAP User Response: Contact Data Protection for mySAP
support. support.
BKI9007W An error occurred while terminating the BKI9203E Additional support information: An
application: the error Exception was thrown at position:
Explanation: While terminating the application, an position.
error occurred. This has no impact on the success of the Explanation: This error message typically follows a
operation. previous error. If so this error message can be ignored.
User Response: None Otherwise contact your Data Protection for mySAP
support
BKI9008E This product requires at least version User Response: Contact Data Protection for mySAP
number of product name to be installed. support.
Explanation: The version of the application product

name is not supported by this application. Most likely BKI9204E Additional support information: An
application product name needs to be upgraded. Exception was thrown at position:
position (text=description).
BKI9009W The following products are not Otherwise contact your Data Protection for mySAP
compatible: product name (product version) support.
and product name (product version).
Explanation: This message is similar to BKI9008E. But support.
in this case it’s not obvious which one of the products
needs to be upgraded. .
User Response: Contact DP for mySAP support
BKI9205E Additional support information: Unable BKI9211E Additional support information: An
to instantiate name at position position. Exception was thrown at position:
position. (State state)
previous error. If so this error message can be ignored. Explanation: This error message typically follows a
Otherwise contact your Data Protection for mySAP previous error. If so this error message can be ignored.
support. Otherwise contact your Data Protection for mySAP
support.
support. User Response: Contact Data Protection for mySAP
support.
BKI9206E Additional support information: Unable
to use actual when expecting expected at BKI9212E Additional support information: No
position position. handler registered for message type type.
Thrown at position: position.
previous error. If so this error message can be ignored. Explanation: This error message typically follows a
Otherwise contact your Data Protection for mySAP previous error. If so this error message can be ignored.
support. Otherwise contact your Data Protection for mySAP
support.
mySAP support. User Response: Contact your Data Protection for
mySAP support.
Exception was thrown at position: BKI9213E Internal error: A memory allocation
position. request failed at position: position.
Explanation: This error message typically follows a Explanation: 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 your Data Protection for mySAP Otherwise contact your Data Protection for
support. mySAP.support.
User Response: Contact your Data Protection for User Response: Contact Data Protection for mySAP
mySAP support. support.
BKI9208E System error errno: errno text at position BKI9214E Additional support information: An
position. exception was thrown from a destructor.
Callstack follows: callstack.
Explanation: A system call failed with errno.
User Response: Check errno and errno text with you
system administrator. If you cannot resolve the
problem, contact Data Protection for mySAP support.
support.
BKI9209E Additional support information: No
support.
handler registered for message type
message. Thrown at position: position.
exception was thrown at position:
position.
support. Explanation: This error message typically follows a
mySAP support.
support.
BKI9210E ESD_AbortDispatchingException thrown
support.
at position: position.
Explanation: An internal error occurred.
mySAP support.

User Response: Check for previous errors and correct
them.
exception was thrown at position:
positien.
BKI9301E Additional support information: State
state does not match state pattern pattern.
Otherwise contact your Data Protection for mySAP Explanation: This error message typically follows a
support. previous error. If so this error message can be ignored.
Otherwise contact your DP for mySAP support.
mySAP support. User Response: Contact your DP for mySAP support.
BKI9217E Additional support information: An BKI9302E Additional support information: Unused

exception was thrown at position: ESD_ReturnChannel destroyed.
position. Dumping callstack: callstack
Explanation: This error message typically follows a Explanation: 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 your Data Protection for mySAP Otherwise contact your DP for mySAP support.
support.
mySAP support.
BKI9306I Dumping callstack: call stack.
BKI9218E Additional support information: An Explanation: This message is always preceded by an

exception was thrown at position: error message indicating the problem. It provides
position. additional information that might help your DP for
mySAP support to analyze the cause of the problem.
previous error. If so this error message can be ignored. User Response: If you need to call Data Protection for
Otherwise contact your Data Protection for mySAP mySAP support, provide the information given in this
support. message together with the error information.

support. BKI9307E Did not find a winsock dll compatible
with version expected version. Version
found is available version
BKI9219E Additional support information: Invalid
error type typeencountered. Explanation: DP for mySAP failed to load the
appropriate winsock dll.
previous error. If so this error message can be ignored. User Response: Contact your system administrator
support. BKI9308E A socket request timed out after
User Response: Contact your DP for mySAP support. processing number of bytes bytes. position.
Explanation: A socket request was issued with a
BKI9220E Additional support information: Second timeout and the requested action could not be
call of call. completed within the time specified. It was cancelled
after processing number of bytes bytes.
previous error. If so this error message can be ignored. User Response: If you need to call DP for mySAP
Otherwise contact your DP for mySAP support. support, provide the information given in this message
together with the error information.
BKI9300E Additional support information:

Aborting ’send’ operation. See previous
error.
Explanation: This error may have been caused by
previous errors.
Data Protection for mySAP File Manager Error Messages
BACKINT not found!
Explanation: The executable BACKINT was not found.
This executable is necessary to run DP for mySAP File
Manager.
User Response: Make sure BACKFM is installed in
the same directory as BACKINT and has the same
permission.
Profile not specified. Please use 'backfm -p

<ParFileName>' !
Explanation: Since DP for mySAP File Manager calls
DP for mySAP, the profile for DP for mySAP is
required.
User Response: Specify the full file name of the DP
for mySAP profile when starting DP for mySAP File
Manager, for example: backfm -p
/oracle/C21/dbs/initC21.utl.
BACKINT call was not successful!

Explanation: The communication with the Tivoli
Storage Manager server failed.
User Response: Check that DP for mySAP and the
Tivoli Storage Manager server(s) work correctly. It must
be possible to run Data Protection for mySAP directly
from the command line, otherwise Data Protection for
mySAP File Manager will also not work.
Cannot open temporary file!

Explanation: A temporary file could not be opened.
This could have several reasons.
User Response:
| UNIX or Linux:
Make sure the directory /tmp is not full and
you have write permission for this directory.
Windows:
Make sure that the current drive is not full.
Unable to allocate memory!

Unable to install SIGWINCH-handler!
Unable to remove Backup IDs!
Unable to install SIGINT-handler!
Can’t get window size!
Explanation: These error messages indicate problems
which usually cannot be resolved by the users
themselves.
User Response: Inform your system administrator or
DP for mySAP support about this problem.

Appendix C. Troubleshooting
This appendix gives you information on how to resolve errors that might occur
during or shortly after installation and during Backup / Restore. In general,
problems related to this product can be distinguished into these 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 mySAP Messages,” on
page 101. 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 mySAP” on page 25. 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 mySAP on Oracle
| shown below in the file /etc/inittab on UNIX or Linux systems:
po32:2:respawn:/usr/tivoli/tsm/tdp_r3/ora/prole -p tdpr3ora aaserver 5126
If running a 64bit Data Protection for mySAP the port name would be tdpr3ora64
instead of tdpr3ora.
Purpose of this entry is to start a daemon process for the programmed operator
which listens on port tdpr3ora for backint and RMAN connections and is able to
forward performance information to an Administration Assistant server. The port
tdpr3ora can also have a different name but must match with the entry in
/etc/services (see below).
The last two arguments specify the location of the Administration Assistant server
and are only needed if you want to use it. aaserver specifies the IP address of the
host on which the AA is running. 5126 is the default port the server is listening.
On Windows systems please verify if a service ProLE Service is running and set to
automatic startup. If this service is not running Data Protection for mySAP will not
work.
| The installer added a line like the following to the file /etc/services on UNIX or
| Linux or to %SYSTEMROOT%\system32\drivers\etc\services on Windows:
tdpr3ora 57321/tcp
tdpr3ora64 57323/tcp
where tdpr3ora is the entry for 32bit and tdpr3ora64 for 64bit Data Protection.
This port should be the same as in /etc/inittab. Also you need it for the

configuration of RMAN in the file init<SID>.sap.
Other than modifying the mentioned files the installer created, the DP for mySAP
| configuration file init<SID>.utl within the directory $ORACLE_HOME/dbs on UNIX
| and Linux or %ORACLE_HOME%\database on Windows systems.
If you want to use SAPs SAPTOOLs (formerly known as SAP DBA) you need to
modify the file init<SID>.sap. Set backup_dev_type = util_file and the variable
util_par_file should contain the full qualified path and file name of the file
init<SID>.utl. See Figure 27 to get an overview of the configuration files on a
| UNIX or Linux system.
Figure 27. SAP and Data Protection configuration files on UNIX or 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 there is no file dsm.sys needed but a file dsm.opt whose
content is not relevant for Data Protection for mySAP. The directory where the file
dsm.opt is contained must also contain files with the name <server>.opt for every
server specified in the init<SID>.utl. There must be an environment variable
DSMI_CONFIG set to an option file within this directory. 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 dscamen.txt resides. Usually
this is the directory c:\Program Files\Tivoli\tsm\api.
| On UNIX or Linux systems the DSMI_* variables don’t 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 where Data Protection for mySAP writes to in order to
store persistent information is the 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 brbackup, brrestore or SAP
Tools in general will also be written into a log file. To locate these log files, see
“How To Find Message Files (Log Files)” on page 101.
Oracle also writes logs of internal operations in the alert log and core files in the
directory specified in the Oracle control files. Usually this is
$SAPDATA_HOME/saptrace/background/alert_<SID>.log.
Appendix C. Troubleshooting 125

BACKINT Problem Resolution
Now that you verified all the settings done by the installer follow the flow shown
in Figure 28 to isolate the problem. No matter if you use the Backint interface or
the RMAN interface of Data Protection for mySAP, make first sure that the
BACKINT interface is working correctly.
Figure 28. Problem Isolation for Backint
After installation (1.1 in Figure 28) set the password (1.2) as described in section
“Set the Password” on page 28. 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 ’BKI0024I: Return code is: 0.’
at the very end of the output. If a problem occurred you should see an error
message.
If you have an Administration Assistant running you may also use the
Configurator of the Administration Assistant. There you can load the configuration
of the node on which you are encountering the problems and let the
Administration Assistant check the configuration.
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 or Linux. 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 in /etc/services on Windows
%SYSTEMROOT%\system32\drivers\etc\services.
Compare the port number from the error message with the port number within
/etc/services. Also have a look in /etc/inittab. If another port was set using
the option -p<PORT>, check this one as well.
If all of this will not help, start the ProLE from another shell prole -p <PORT>
(on Windows: prole -console -p <PORT>) and try with starting backint 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 or Linux ). On Windows, the <server>.opt might
be missing.
v Error Message: BKI5001E: Tivoli Storage Manager Error: ANS1353E (RC53)
Session rejected: Unknown or incorrect ID entered
This message can happen if the node in the server stanza of the UTL file is not
valid on the server. Also have a look into the API reference (e.g. search the
message at tivoli.com)
v HANG: If backint hangs after input of the password the servers IP address in
dsm.sys may be wrong.
When step 1.2 of Figure 28 on page 126 (setting of password) finally succeeded,
proceed with step 1.3 and try to make a backup using backint to verify the settings
are correct. The “Backup Function” on page 132 describes how to do this.
If the backup was successful you will see one message #SAVED<BID><FILENAME> per
file you typed in to be saved and again there will be the message ’BKI0024I:
Return code is: 0.’ Otherwise you should see an error message. In this case try to
resolve it by using the error description in Appendix B, “Data Protection for
mySAP Messages,” on page 101.
Now that you got this far you can be sure your Data Protection for mySAP setup
is fairly complete. Now you only need to assure that the SAPTOOLS and Oracle (if
using RMAN) are correctly configured. Go on with step 1.3 and start brbackup as
described in section “Verifying the Installation” on page 29.

RMAN Problem Resolution
If you successfully configured the BACKINT interface and were able to do a
backup with BRBACKUP using backint you may now proceed with setup of Data
Protection for mySAP for use with Oracle RMAN.
Following graphic Figure 29 will help you to isolate problems that occurred when
using RMAN.
Figure 29. Problem Isolation for RMAN
After you set up Data Protection for mySAP and Oracle to work together (step 1.1
of Figure 29) as described in Chapter 6, “Using DP for mySAP with RMAN,” on
page 51, you may try to startup Oracle using the server manager (svrmgrl on
| UNIX or Linux , and svrmgr30 on Windows) with Oracle 8.x or using SQL Plus
(sqlplus) on Oracle 9.x .
With RMAN the very first place to look at if an error occurred is the file
sbtio.log, located in the directory specified in the user_dump_dest keyword within
the Oracle profile init<SID>.ora.
This file is usually located at $ORACLE_HOME/saptrace/usertrace/sbtio.log. Always
first review the latest messages in this file since the messages issued in the RMAN
log are often not very helpful.
If this log file is not written (2.2) this is a clear sign that Oracle either was unable
to load the shared library containing the RMAN connector of DP for mySAP or
Oracle encountered an error before calling the DP for mySAP library. In both cases
there should be an Oracle error message beginning with ’ORA-’, ’PLS-’ or ’RMAN-’
in the log of brbackup. Try to solve this problem using the documentation from
Oracle and SAP.
If the file sbtio.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 RMAN connector of DP for mySAP is loaded
and has been called by Oracle RMAN. Beginning with version 3.3.10 of DP for
mySAP the first message for every new session should be (2.3):
BKI7060I: Data Protection for mySAP <version and build number> session: 764
If you don’t find this message Oracle has loaded a wrong library. In this case do
following
on Windows:
Remove or rename all occurrences of the file orasbt.dll except the one in DP for
mySAP installation directory. Then copy this one to %ORACLE_HOME%\bin. Stop the
OracleService<SID> and restart it.
| On UNIX or Linux systems:
often the RMAN librarylibtdp_r3.<ext> is not found by the Oracle executable. On
this topic there exists a large number of notes from Oracle at Oracle’s web pages
and also some from SAP in OSS.
Oracle suggests to use a variable SBT_LIBRARY to specify the library. During

development and test of DP for mySAP it turned out as a best practice not to use
the variable SBT_LIBRARY on any platform with Oracle up to 9.2.
Also there are notes at Oracle Metalink or Oracle Technet saying one no longer
needs to issue the make command described in Chapter 6, “Using DP for mySAP
with RMAN,” on page 51. This is not true for all operating system / Oracle
version combinations.
For DP for mySAP we strongly recommend to issue the make command on any
| UNIX or Linux system. Whether Oracle needs this command or not, it will not
destroy anything and when executed successful it justifies the library and the
Oracle executable are compatible.
| So on UNIX or Linux systems review if you issued the make command. Also make
sure the library and/or soft link you typed during the command make -f
ins_rdbms.mk ioracle LLIBMM=<lib or link> is existing and the soft link is valid.
It may also be helpful to add the location of the link or library to the environment
| variable LIBPATH on AIX or LD_LIBRARY_PATH on other UNIX or Linux
| systems.
On Windows based systems the location of orasbt.dll must be in the PATH. Also
make sure to have only one orasbt.dll in your systems PATH. It will be helpful as
well to review the setup procedure according to Chapter 6, “Using DP for mySAP
with RMAN,” on page 51 and the hints given in that chapter. Also check if a core
file is written or if Oracle has written a trace within the saptrace/usertrace
directory.
In (2.4) the file sbtio.log is written and you find an error message starting with
BKI see Appendix B, “Data Protection for mySAP Messages,” on page 101.
Using the backint executable to determine any problems may make it easier

because you can see all messages on the screen. Also you will not disturb Oracle if
something goes wrong. If backint is working as expected then return to problem
determination with RMAN.
Isolating a problem with DP for mySAP and RMAN you may follow the same
steps as in section Backint Problem Resolution. There must be a connection
established to ProLE and TSM server and a password must be set (using backint)
as well. If some of these steps fail you will get exactly the same error messages
with RMAN as you get with backint.
Please also use Appendix B, “Data Protection for mySAP Messages,” on page 101
to review those messages.
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.
Reproducable (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 mySAP ?
2. What did you change at the setup of involved components (Oracle, 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 (init<SID>.utl, init<SID>.sap, dsm.sys, dsm.opt,
/etc/services, /etc/inittab, ...).
| The following UNIX or Linux 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 or Linux 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 Assistance or compare the brbackup
/ brrestore log files.
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 effected 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 (brbackup / brrestore log,
sbtio.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.
Contacting Your IBM / Tivoli Support

When you contact your support try to give a complete description of the problem
you encounter and the environment it occurs in. You should always deliver the
following information:
v The version of DP for mySAP
v The operating system level (incl. 32 or 64bit) and patches that were applied
v Oracle version (incl. 32 or 64bit)
v TSM server version
v OS level for TSM server
v DP for mySAP configuration file (initSID.utl)
including TSM client config files (dsm.sys, dsm.opt)
v SAP Admin Tools log file of the operation in question (brarchive, brrestore)
v If it worked before, have also the change history of the system components
available
In addition to the above information there will be a situation where you need to
deliver additional information.
Your service representative will ask you for this additional information.
Invoking Data Protection for mySAP manually

Data Protection for mySAP is normally invoked with a set of appropriate
parameters by the SAP database utilities (SAP DBA, BRBACKUP, BRARCHIVE,
BRRESTORE). For troubleshooting purposes, however, it is possible to call DP for
mySAP directly from the command line in order to perform data protection
operations manually, thus being able to correct errors. The command:
backint -?

displays a list of all possible Data Protection for mySAP command line options.
Backup Function
The backup function will be normally invoked by the SAP database utilities
BRBACKUP and BRARCHIVE. These programs give DP for mySAP an input file
(in the case of backup and inquire) containing the names and paths of the
database files to be handled.
For troubleshooting, however, it might be necessary to call this function of DP for

mySAP directly to back up individual files. See the following example.

backint -p /oracle/SID/dbs/init<SID>.utl -f backup

backint -p <drive>:\orant\database\init<SID>.utl -f backup
Note
The Data Protection for mySAP profile init<SID>.utl has to be specified with
the path and file name statement as shown above.
The program prompts you to enter one or more file names. Every successful
backup run (collection of one or more files) is allocated its own backup ID within
Tivoli Storage Manager.
| Don’t forget to press CTRL + D on a UNIX or Linux system or CTRL + Z on a

Windows system after you typed in the file name to backup.
Restore Function
The restore function will be normally started by the SAP database utility
BRRESTORE.
For troubleshooting, however, it might be necessary to call this function of DP for

mySAP directly to restore individual files. This function can be invoked from the
command line as follows.

backint -p /oracle/SID/dbs/init<SID>.utl -f restore

backint -p <drive>:\orant\database\init<SID>.utl -f restore
You will be prompted to enter the backup ID and the full file names of the files to
be restored. If the files are to be restored to another directory, it is necessary to
specify the path to the input files.
Caution
If a file is restored directly, any existing file with the same name will be
overwritten without warning. Thus, it is recommended that you restore
database files directly only in a very controlled manner, when it is absolutely
necessary in order to remove an error. In normal operation you should never
restore a database directly, because this could corrupt the mySAP database.
Inquire Function
The inquire function, normally invoked by SAPDBA and BRRESTORE, will be
used to query the Tivoli Storage Manager server for backup IDs or files which
belong to a particular backup ID.
For troubleshooting, however, it might be necessary to invoke this function

manually from the command line as follows.

backint -p /oracle/SID/dbs/init<SID>.utl -f inquire

backint -p <drive>:\orant\database\init<SID>.utl -f inquire
DP for mySAP prompts you to enter the inquiry in one of four formats. These are:
1. #NULL - to display all backup IDs saved so far. A typical line of the response
could be:
#BACKUP JE0___A0DNE9Z74C
The backup ID in this case is JE0___A0DNE9Z74C (#BACKUP does not belong to the
backup ID). The first six characters are the user defined prefix (see
BACKIDPREFIX on page 84). The next 10 characters after this represent a
unique ID of the backup.
2. BackupID - to display all of the files which belong to that backup ID. A typical
result could be:
##BACKUP JE0___A0DNE9Z74C /oracle/C21/dbs/initC21.utl.
3. #NULL filename - to display all of the backup IDs corresponding to this file.
Filename requires an input consisting of path and name of the file.
4. BackupID filename - to verify whether a particular file has been saved under a
certain backup ID. Filename requires an input consisting of path and name of
the file.
Delete Function
The delete function is used as part of the versioning control mechanism of DP for
mySAP and can only be called by DP for mySAP itself or by a user.
The delete function allows you to delete individual files, which might be necessary
for recovering from an error. This function can be invoked from the command line
as follows:

backint -p /oracle/SID/dbs/init<SID>.utl -f delete

backint -p <drive>:\orant\database\init<SID>.utl -f delete
You will be prompted to enter the backup ID and the full file names of the files to
be deleted.
| File Manager
| The File Manager requires a correct setup of DP for mySAP particularly with
| regard to the backint executable, thus enabling it to connect to the TSM server
| without errors. To connect to the TSM server the File Manager calls the backint
| executable. If this call fails, the File Manager shows an error message but does not
| analyze what the reason for the failure is. To analyze the error, backint manually
| with the inquire function (see “Inquire Function” on page 133) and check the
| output for error messages.
Appendix D. Installation Planning Sheet
Before starting the installation procedure, collect the following information:
Oracle database SID:
For Windows only: Path where the SAP DBA tools reside:
TSM server name:
TSM node name:
TSM management classes for database and log file backups:
For Windows only: Path where the Tivoli Storage Manager API resides (contents of
environment variable DSMI_DIR):
For Windows only: Option file of Tivoli Storage Manager (contents of environment variable
DSMI_CONFIG):
For Windows only: Path for Tivoli Storage Manager log files (contents of environment
variable DSMI_LOG):
For Windows only: Installation path for Data Protection for mySAP executables:
Path for Data Protection for mySAP profile: (directory for SAP configuration files)
Administration Assistant Server for Data Protection for mySAP:
Network Address
Port number

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

DP for mySAP attempts to communicate with the Tivoli Storage Manager server
using the first path in the profile. If this proves successful, DP for mySAP starts the
number of parallel sessions as specified for this path; if the attempt was
unsuccessful, this path is skipped, and DP for mySAP continues with the next
path. This continues until as many sessions are active as were specified in the total
session number (MAX_SESSIONS). If this number is never reached (for example,
because several paths were inactive), DP for mySAP terminates the backup job.
Parameter Settings - SERVER Statement

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

Assume the following configuration:
Tivoli Storage Manager server with:
– 2 tape drives
– 2 LAN connections.
A backup is normally performed via network path 1 (SERVER statement 1). If this
is unavailable the backup shall be performed using network path 2 (SERVER
statement 2).
The definitions in the Data Protection for mySAP profile could be as shown in the
example below.
If path 1 is active, DP for mySAP will start the 2 sessions as defined in the
SERVER statement for path 1. Since MAX_SESSIONS is also 2, no more sessions
will be started.
If path 1 is inactive, Data Protection for mySAP will start 2 sessions on path 2.
Since this equals the MAX_SESSIONS definition as well, backup will be executed
using path 2.
Appendix E. Backup Paths and Servers 139

Data Protection for mySAP profile. Example 1
MAX_SESSIONS 2 # 2 tape drives

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

ADSMNODE C21
SESSIONS 2
BRBACKUPMGTCLASS mdb
BRARCHIVEMGTCLASS mlog1 mlog2
# USE_AT 0 1 2 3 4 5 6
EXAMPLE 2: Use of Parallel Paths for Increased Performance
Two Tivoli Storage Manager servers with connections via two network paths:
– server_a, TCP/IP address xxx.xxx.xxx.xxx
– server_b, TCP/IP address yyy.yyy.yyy.yyy
– Each of these servers has:
- two tape drives
A mySAP database server connected to two networks.
Backups are done on both systems every day.
example below.

.
.
ADSMNODE C21
SESSIONS 2
BRBACKUPMGTCLASS MDB
BRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4
# USE_AT 1 2 3 4 5 6 7
SERVER server_b # via network path 2 ADSMNODE C21

SESSIONS 2
# USE_AT 1 2 3 4 5 6 7
Appendix E. Backup Paths and Servers 141

EXAMPLE 3: Use of Alternate Servers for Disaster Recovery
Two Tivoli Storage Manager servers:
– server_a, TCP/IP address xxx.xxx.xxx.xxx
– server_b, TCP/IP address yyy.yyy.yyy.yyy
Each of these servers with:
– four tape drives (MAX_SESSIONS 4).
A mySAP database server connected to this FDDI network.
Normal backups are to be performed with server a, which is local to the mySAP
database server. Every Friday a disaster recovery backup should be stored on a
remote Tivoli Storage Manager server (server b).
example below.

.
.
ADSMNODE C21
SESSIONS 4
USE_AT 1 2 3 4
SERVER server_b # via network path 2

ADSMNODE C21
SESSIONS 4
USE_AT 5 # for Disaster Recovery
Appendix F. Preparing Tivoli Storage Manager for DP for
mySAP
This chapter explains the procedures for setting up TSM for working with Data
Protection for mySAP in an SAP environment. A typical list of actions that the
Tivoli Storage Manager installer or administrator must perform to prepare Tivoli
Storage Manager to work in an SAP environment will be explained.
Note
The following steps and procedures are only samples. The actual values in
your specific environment may be different.
Configuring the Tivoli Storage Manager Server

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

Before starting the installation, some important performance issues should be
considered. The careful choice of the server that is to be installed, the network
topology, and the use of powerful hardware can improve performance within the
system landscape and can avoid performance bottlenecks.
v Host for Tivoli Storage Manager server. The Tivoli Storage Manager server
should be installed on an exclusive machine. This procedure avoids concurrent
processes and disk I/O accessing with other applications. In a single SAP system
landscape, a single Tivoli Storage Manager server is sufficient. If you plan to use
the Storage Manager to back up/restore other clients as well, you should
consider either installing the server software on a large machine or using several
Tivoli Storage Manager servers.
v Network topology. Network topologies such as Ethernet, Token Ring, FDDI and
Fast Ethernet work all well with Tivoli Storage Manager. In general, the fastest
network topology like FDDI or Fast Ethernet should be used to prevent
bottlenecks during backup/restore operations. Tivoli Storage Manager supports
multiple network adapters, increasing server throughput by providing multiple
connections to the same network or several physically distinct networks with the
same server.
v RS/6000® SP™ environment. An RS/6000 SP node can be used for a Tivoli
Storage Manager server. The use of a High Performance Switch network will
improve performance of backup/restore operations on the Tivoli Storage
Manager server.

Prerequisites
It is assumed that the Tivoli Storage Manager server has already been successfully
installed. This means that the following steps have been completed:
v Tivoli Storage Manager server has been installed. For information on the
required release and maintenance level, refer to the DP for mySAP release
notice.
v Recovery log volume has been allocated and initialized.
v Recovery log mirror volume has been allocated and initialized.
v Database volume has been allocated and initialized.
v Database mirror volume has been allocated and initialized.
v Additional labeled volumes for the backup and archive storage pools have been
allocated and initialized (disks, tapes or combinations).
v Licenses have been registered.
v The Tivoli Storage Manager server has been started.
For information on installing Tivoli Storage Manager, see the Tivoli Storage Manager
Quick Start manual.
Note
The latest code fixes for Tivoli Storage Manager can be found at:
ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance
Adjusting your TSM for DP for mySAP
Note
The following steps and procedures are only samples. The actual values in
your specific environment may be different.
In order to adjust the installed TSM to the DP for mySAP, the following activities
must be performed.
1. Storage Device Setup

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

q drive
v Query defined device class

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

define stgpool sap_db <device_class_name> maxscr=20
3. Definition of a storage pool for the first copy of offline redo log files
define stgpool sap_log1 <device_class_name> maxscr=3
4. It is strongly recommended that you back up the offline redo log files twice on
two different Tivoli Storage Manager volumes. For this purpose, you have to
define an additional storage pool for the second copy of offline redo log files.
define stgpool sap_log2 <device_class_name> maxscr=3
Note
When you associate a library tape device, you have to define the maximum
number of scratch volumes (labeled volumes which are empty or contain no
valid data) this storage pool will be allowed to use (parameter maxscr). The
maximum number of scratch tapes depends on the size of the database, the
capacity of the tapes, the number of scratch volumes available and how many
versions of the backup you will keep. Replace these values with your
estimates.
3. Policy Definition
Tivoli Storage Manager policies are used to specify how files are backed up,
archived, migrated from client node storage, and managed in server storage.
A policy definition includes the definition of a policy domain, a policy set,

management classes and copy groups. After the definition phase, you need to assign a
default policy set and validate and activate it.
Appendix F. Preparing Tivoli Storage Manager for DP for mySAP 145

For the policy definition, log on as a Tivoli Storage Manager Administrator using
the Admin Command Line or the Web Admin and invoke the following commands:
1. Policy domain and policy set definition
define domain sap_c21
define policyset sap_c21 p_c21
2. Management Class definition for file system backups, data files, offline redo
logs and copies of offlineredo logs
define mgmtclass sap_c21 p_c21 mdefault
define mgmtclass sap_c21 p_c21 mdb
define mgmtclass sap_c21 p_c21 mlog1
define mgmtclass sap_c21 p_c21 mlog2
Note
If you are planning to use this Tivoli Storage Manager server with
multiple SAP systems, it is recommended that you use a set of different
management classes for each system.
3. Copy Group definition

define copygroup sap_c21 p_c21 mdefault type=backup destination=sap_incr
define copygroup sap_c21 p_c21 mdefault type=archive destination=archivepool
define copygroup sap_c21 p_c21 mdb type=archive destination=sap_db retver=nolimit
define copygroup sap_c21 p_c21 mlog1 type=archive destination=sap_log1 retver=nolimit
define copygroup sap_c21 p_c21 mlog2 type=archive destination=sap_log2 retver=nolimit
DP for mySAP uses its own version control mechanism for managing mySAP
database backups. To do this, DP for mySAP backs up all data only to
management classes for which an archive copy group has been defined
(parameter type set to archive; for a definition, see Glosssary page 179). In
addition, to prevent backed up files within Tivoli Storage Manager being
deleted because of their expiration date (Tivoli Storage Manager deletes expired
files), the copy group parameter retver (specifies the number of days a file is
to be kept) should be set to unlimited (9999 or nolimit).
4. Assigning the default management class
assign defmgmtclass sap_c21 p_c21 mdefault
5. Validating and activating the policy set

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

| For simulations of network transfer and media rates, the TSM server must be
| configured so that sessions do not time out during simulation. This is achieved by
| setting the parameter IdleTimeOut to a value higher than the time required for
| sending the largest table space file to TSM. For example:
| setopt IdleTimeOut 60
||
|
Configuring the Tivoli Storage Manager Clients
After the server configuration, you have to configure the clients that will use the
Tivoli Storage Manager server. These include the backup/archive client for the file
system backups and the Application Programming Interface (API) client for interface
programs. The Tivoli Storage Manager backup/archive client will be used for file
system backups. The API client allows users to enhance existing applications with
backup, archive, restore, and retrieve services. An installed and confirmed API
client is a prerequisite for DP for mySAP..
General Considerations
First of all, if a successful installation of Tivoli Storage Manager backup/archive
client and API client is to be performed, the clients must be installed on all nodes
that will interface with the Tivoli Storage Manager server.
In the context of a mySAP system landscape, this means that the Tivoli Storage
Manager backup/archive client must be installed on every machine scheduled for
a file system backup, for example, mySAP application servers and the mySAP
database server. The Tivoli Storage Manager API client only needs to be installed
on the mySAP database server machine to enable backup/restore operations of the
mySAP database in combination with the backup interface program DP for mySAP.
Tivoli Storage Manager Clients on UNIXor Linux Systems

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

Follow these steps:
1. Install the Tivoli Storage Manager client software on the mySAP database
server machine.
2. Edit the client system options file dsm.sys and set the following values, as
appropriate to your installation:
Servername server_a
TCPPort 1500
TCPServeraddress xxx.xxx.xxx.xxx or servername
InclExcl /usr/tivoli/tsm/client/ba/bin/inclexcl.list
Compression OFF
3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are on

the same machine. This makes TCP/IP communication a little faster.
4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude the
files listed in inclexcl.list. This is optional. You would usually exclude all
database files that were processed by SAPDBA, BRBACKUP, or BRARCHIVE.
5. If you have tape drives with hardware compression attached to the Tivoli
Storage Manager server, you might get better throughput with the hardware
compression than you would with the Tivoli Storage Manager client software
compression (Compression ON).
Note
Do not compress the data twice!
You will need to try Tivoli Storage Manager client software compression in
your environment to determine whether it is of use for you. In general, the
Tivoli Storage Manager client software compression improves performance only
when network throughput is quite small.
6. Edit the client user options file dsm.opt and set the following values:
LANGUAGE AMENG (this is the default value)
NUMBERFormat 1 (this is the default value)
TAPEPROMPT NO
TIMEFORMAT 1 (this is the default value)
Note
| When the Tivoli Storage Manager API client is installed on UNIX or Linux
| systems, ensure that there is a softlink /usr/lib/libApiDS.<ext> pointing to
the libApiDS.<ext> file in the installation directory
(/usr/tivoli/tsm/client/api/bin) of the Tivoli Storage Manager API. For the
meaning of <ext>, see “RMAN Setup on UNIX and Linux Systems” on page
51.
Tivoli Storage Manager Clients on Windows Systems

The setup for the Tivoli Storage Manager client is effected in Windows
environments by changing the file <server_a>.opt (where server_a is the logical
server name in the initSID.utl file, see profile keyword SERVER on page 90).
Subsequently, the include/exclude file must be configured. It defines which files
the Tivoli Storage Manager backup/archive client will include or exclude for any
backup, archive or hierarchical storage procedure. Examples of an include/exclude
file for Windows can be found in “Sample TSM Profiles for Windows” on page
160.
The following serves as a quick guide for configuring the Tivoli Storage Manager.
It presents a typical list of actions that the Tivoli Storage Manager installer or
administrator must perform to prepare Tivoli Storage Manager for operation in a
mySAP environment.
Follow these steps:

1. Install the Tivoli Storage Manager client software on the mySAP database
server machine.
2. For each logical Tivoli Storage Manager server you need a corresponding client
option file. In the following example, the file name must be server_a.opt since
server_a is the logical server name:
TCPPort 1500
TCPServeraddress xxx.xxx.xxx.xxx
InclExcl c:\tivoli\tsm\baclient\inclexcl.list
Compression OFF
In addition, the environment variable DSMI_CONFIG must point to the

corresponding client options file, e.g., c:\tivoli\tsm\api\server_a.opt .
3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are on
the same machine. This makes TCP/IP communication a little faster.
4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude the
files listed in inclexcl.list. This is optional. You would usually exclude all
database files that were processed by SAPDBA, BRBACKUP, or BRARCHIVE.
5. If you have tape drives with hardware compression attached to the Tivoli
Storage Manager server, you might get better throughput with the hardware
compression than you would with the Tivoli Storage Manager client software
compression (Compression ON).
Note
Do not compress the data twice!
You will need to try Tivoli Storage Manager client software compression in
your environment to determine whether it is of use for you. In general, the
Tivoli Storage Manager client software compression improves performance only
when network throughput is quite small.
Password Handling
For a discussion of the password handling methods, please see “Modifying the
Handling of the TSM Password” on page 43.
After selecting the suitable method, follow the steps in the appropriate
configuration matrix below to set the keywords and parameters in the various
profiles accordingly.

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

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

| Under UNIX or Linux, crontab starts jobs (cron.job) at predefined times. In the
example below crontab starts two shell scripts backup.ksh and archive.ksh, which
simply use the SAP tools BRBACKUP and BRARCHIVE to save the data.
Crontab File Sample

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

# o A list of numbers separated by commas
# o An * (asterisk); meaning all allowed values
#
# --------------------------------------------------------------------------
#
# For the following examples, the system ID of the Oracle database
# is assumed to be "C21" and the username "oraC21".
#
# --------------------------------------------------------------------------
# Full database backup, scheduled every Friday at 8:00 p.m.
#
0 20 * * 5 /usr/bin/su - oraC21 -c "/oracle/C21/sapscripts/backup/backup.ksh"
#
# --------------------------------------------------------------------------
# Save redo logs, scheduled twice a day at 11:30 a.m. and at 5:30 p.m.
# Monday through Friday
#
30 11,17 * * 1,2,3,4,5 /usr/bin/su - oraC21 -c "/oracle/C21/sapscripts/backup\
/archive.ksh"
Full Offline Backup Shell Script Sample

#!/bin/ksh
# --------------------------------------------------------------------------
# backup.ksh:
# Sample BRBACKUP shell script
# --------------------------------------------------------------------------
# Task:
# Invokes the SAP R/3 utility BRBACKUP in order to perform a full offline
# backup of all tablespaces
# using IBM’s SAP R/3 Tivoli Storage Manager interface program
# Data Protection for mySAP.
# --------------------------------------------------------------------------
# ***** NOTE ***** NOTE ***** NOTE *****
#
# This script is intended only as a model and should be
#
# ***** NOTE ***** NOTE ***** NOTE *****
# --------------------------------------------------------------------------
#
# For the following examples, the system ID of the Oracle database
# is assumed to be "C21".
#
# --------------------------------------------------------------------------
#
# First, lets do a full offline backup of the Oracle database. This includes
# at least files located in the following file systems:
# /oracle/C21/sapdata1
# Remarks on the parameters of BRBACKUP:

#
# -u system/manager Oracle username/password
# -c run BRBACKUP in unattended mode
# -m all backup all tablespaces
# -t offline perform backup offline
#
# The following should be configured within the SAP backup profile initC21.sap:
#
# backup_dev_type = util_file
# causes BRBACKUP to use the external program Data Protection for mySAP
# util_par_file = initC21.utl
# Data Protection for mySAP profile
#
# --------------------------------COMMAND-----------------------------------
brbackup -u system/manager -c -m all -t offline
Save and Delete Redo Logs Shell Script Sample

#!/bin/ksh
# --------------------------------------------------------------------------
# archive.ksh:
# Sample BRARCHIVE shell script
# --------------------------------------------------------------------------
# Task:
# Invokes the SAP R/3 utility BRARCHIVE in order to save Oracle’s archived
# redo logs (using IBM’s SAP R/3-Tivoli Storage Manager interface program,
# Data Protection for mySAP) and deletes the redo logs from their
# original location.
# After completing this, the BRARCHIVE protocol is saved separately.
# --------------------------------------------------------------------------
# ***** NOTE ***** NOTE ***** NOTE *****
#
# This script is intended only as a model and should be
#
# ***** NOTE ***** NOTE ***** NOTE *****
# --------------------------------------------------------------------------
#
# Remarks on the parameters of BRARCHIVE:
#
# -u system/manager Oracle username/password
# -sd save and delete archived redo logs
# -c run BRARCHIVE in unattended mode
# (-n number of redo logs to be saved, default is 10000,
# which means all available)
#
# The following should be configured within the SAP backup profile initC21.sap:
#
# backup_dev_type = util_file
# causes BRBACKUP to use the external program Data Protection for mySAP
# util_par_file = initC21.utl
# Data Protection for mySAP profile
#
# --------------------------------COMMAND-----------------------------------
brarchive -u system/manager -sd -c
Windows Scheduling Example

To start automated backup jobs on Windows systems, the schedule service must be
running. You can start this service with the command:
net start schedule
If the schedule service is running, jobs can be scheduled with the at command
which can be used to invoke the batch file backup.cmd (the content of backup.cmd
can be found in “Elements of Backup Schedules for Windows” on page 156). If you
want to run this every Friday at 8:00 p.m., the following command must be
invoked:
at 20:00 /every:f cmd /c <drive>:\oracle\SID\sapscripts\backup.cmd
Appendix G. Backup Scheduling Examples 155

Elements of Backup Schedules for Windows
Schedule Batch Sample

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

@echo off
rem Full Offline Backup batch file:
rem ------------------------------------------------------------------------
rem file name: backup.cmd
rem ------------------------------------------------------------------------
rem Sample BRBACKUP batch file
rem ------------------------------------------------------------------------
rem Task:
rem Invokes the SAP R/3 utility BRBACKUP in order to perform a full offline
rem backup of all tablespaces using IBM’s SAP R/3-Tivoli Storage Manager
rem interface program Data Protection for mySAP.
rem ------------------------------------------------------------------------
rem
rem This script is intended only as a model and should be
rem
rem ------------------------------------------------------------------------
rem
rem For the following examples, the system ID of the Oracle database
rem is assumed to be "C21".
rem
rem ------------------------------------------------------------------------
rem
rem First, let’s do a full offline backup of the Oracle database. This
rem includes at least files located in the following file systems:
rem c:\oracle\C21\sapdata1
rem
rem Remarks on the parameters of BRBACKUP:
rem
rem -u system/manager Oracle username/password
rem -c run BRBACKUP in unattended mode
rem -m all backup all tablespaces
rem -t offline perform backup offline
rem
rem The following should be configured within the SAP backup profile
rem initC21.sap:
rem
rem backup_dev_type = util_file
rem causes BRBACKUP to use the external program
rem Data Protection for mySAP
rem util_par_file = %ORACLE_HOME%\database\initC21.utl
rem Data Protection for mySAP profile
rem ------------------------------COMMAND-----------------------------------
brbackup -u system/manager -c -m all -t offline
Save and Delete Redo Logs Batch File Sample

@echo off
rem ------------------------------------------------------------------------
rem file name: archive.cmd
rem ------------------------------------------------------------------------
rem Sample BRARCHIVE batch file
rem ------------------------------------------------------------------------
rem Task:
rem Invokes the SAP R/3 utility BRARCHIVE in order to save Oracle’s archived
rem redo logs (using IBM’s SAP R/3-Tivoli Storage Manager interface program,
rem Data Protection for mySAP).
rem After completing this, the BRARCHIVE protocol is saved separately.
rem ------------------------------------------------------------------------
rem
rem This script is intended only as a model and should be
rem
rem ------------------------------------------------------------------------
rem
rem Remarks on the parameters of BRARCHIVE:
rem
rem -u system/manager Oracle username/password
rem -sd save and delete archived redo logs
rem -c run BRARCHIVE in unattended mode
rem (-n number of redo logs to be saved,
rem default is 10000,
rem which means all available)
rem
rem The following should be configured within the SAP backup profile
rem initC21.sap:
rem
rem backup_dev_type = util_file
rem causes BRBACKUP to use the external program
rem Data Protection for mySAP
rem util_par_file = %ORACLE_HOME%\database\initC21.utl
rem Data Protection for mySAP profile
rem ------------------------------COMMAND-----------------------------------
brarchive -u system/manager -sd -c
Appendix G. Backup Scheduling Examples 157

Appendix H. Sample Tivoli Storage Manager Profiles
| Sample TSM Profiles for UNIX or Linux
Client User Options File Sample (dsm.opt)

************************************************************************
* Tivoli Distributed Storage Manager *
* *
* Sample Client User Options file for AIX and SunOS *
************************************************************************
SErvername server_a
Tapeprompt No
DOM /usr/sap /sapmnt/C21 /usr/sap/trans /oracle/C21
Client System Options File Sample (dsm.sys)

************************************************************************
* Tivoli Distributed Storage Manager *
* *
* Sample Client System Options file for AIX and SunOS *
************************************************************************
SErvername server_a
COMMmethod TCPip
TCPPort 1500
TCPServeraddress loopback
TCPBuffsize 32
TCPWindowsize 24
Compression Off
InclExcl /usr/lpp/tsm/bin/inclexcl.sample
Include/Exclude List Sample

* --------------------------------------------------------------------------
* inclexcl.list:
* Sample include/exclude list
* --------------------------------------------------------------------------
* Task:
* Include/Exclude list of files and directories for TSM incremental backups
* --------------------------------------------------------------------------
* ***** NOTE ***** NOTE ***** NOTE *****
*
* This file is intended only as a model and should be
* carefully tailored to the needs of the specific site.
*
* ***** NOTE ***** NOTE ***** NOTE *****
* --------------------------------------------------------------------------
*
* For all AIX systems
*
exclude /unix
exclude /.../core
exclude /u/.../.*sh_history
exclude /home/.../.*sh_history
*
* Note: It is recommended to perform system backups on a regular
* basis (e.g. using ’smit mksysb’). Consequently, you can exclude
* at least the following directories (which make up about 30 MB).
*
exclude /usr/games/.../*
exclude /usr/bin/.../*
exclude /usr/lbin/.../*
exclude /usr/mbin/.../*
exclude /usr/sbin/.../*
* --------------------------------------------------------------------------
*
* For those using AFS, exclude the cache filesystem or file

*
* exclude /usr/vice/cache/*
* exclude /var/vice/cache/*
* or
* exclude /afscfs
* --------------------------------------------------------------------------
*
* This stuff is either not worthwhile to be included or should be backed up
* using the SAP utilities brbackup/brarchive.
*
exclude /oracle/C11/saparch/.../*
* exclude /oracle/C11/sapbackup/.../*
* exclude /oracle/C11/sapreorg/.../* (There may be important scripts
* located, check it out and decide.)
exclude /oracle/C11/sapdata*/.../*
exclude /oracle/C11/sapraw*/.../*
* --------------------------------------------------------------------------
*
* With the above include/exclude list we implicitly include everything not
| * excluded above. Especially for mySAP(R), this means including:
* /sapmnt/C11 > 270 MB
* /usr/sap > 14 MB
* /oracle/stage > 89 MB
* /oracle/C11 > 90 MB
* and AIX related > 220 MB
* --------------------------------------------------------------------------
Sample TSM Profiles for Windows
Client User Options File Sample (dsm.opt)

The Tivoli Storage Manager client programs require a file dsm.opt containing
standard client user options. The full file name is set in the environment variable
DSM_CONFIG. This file is not provided with the installation.
*************************************************************************
*
| * DSM.OPT (for Data Protection for mySAP(R) technology)
*
| * Data Protection for mySAP(R) technology requires that a file
* ’dsm.opt’ is present, although its contents are ignored.
* This means that this file may be empty (like this file).
* The information about a Tivoli Storage Manager server
* is obtained from the corresponding client option file <server>.opt.
*
| * Data Protection for mySAP(R) technology inspects the environment
* variable DSMI_CONFIG to obtain the full file name of ’dsm.opt’.
*
* Note:
* The standard Tivoli Storage Manager client programs also use a file
* ’dsm.opt’, but the full file name of this client user option file is set
* in the environment variable DSM_CONFIG.
* This file is called the Tivoli Storage Manager client user option file.
* Please see the Tivoli Storage Manager documentation for details.
*************************************************************************
Client Options Files Sample (<server>.opt)

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

Include/Exclude List Sample
This sample include/exclude list is intended for the standard client user option
file. The idea is to exclude files from ordinary Tivoli Storage Manager incremental
| backups that are easy to restore or that are already saved by DP for mySAP.
Mainly such files are Windows system files and Oracle database files.
*************************************************************************
* This Include-Exclude list is used for incremental backups of file
* systems by the Tivoli Storage Manager command-line backup client.
* Therefore the name of this file has to be set under the keyword InclExcl
* in the standard Tivoli Storage Manager client user option file "dsm.opt".
*
* Since the backup of the ORACLE database is done by
| * Data Protection for mySAP(R) technology and not by Tivoli Storage
* Manager command-line backup client, the ORACLE database should be excluded
* from backups by the Tivoli Storage Manager command-line backup client.
*
* Note 1:
* The environment variable DSM_CONFIG contains the full file name of
* the Tivoli Storage Manager client user option file "dsm.opt".
* Note 2:
| * This Include-Exclude is not used by Data Protection for mySAP(R)
* technology.
*
*************************************************************************
Exclude *:\...\*.swp
Exclude *:\...\*.obj
Exclude *:\...\*.csm
Exclude *:\...\*.dsk
Exclude *:\...\*.bak
Exclude *:\...\win386.swp
Exclude *:\...\386spart.par
Exclude *:\...\pagefile.sys
Exclude *:\...\*.par
Exclude *:\...\SYSTEM32\CONFIG\*.*
Exclude *:\...\SYSTEM32\CONFIG\...\*
*
*Exclude the following ORACLE database files:
*
Exclude *:\oracle\C21\saparch\...\*
Exclude *:\oracle\C21\sapbackup\...\*
Exclude *:\oracle\C21\sapreorg\...\*
Exclude *:\oracle\C21\sapdata*\...\*
Appendix I. Hints and Tips for SAP Backup Utilities
Hints and Tips for BRARCHIVE
| For a BRARCHIVE run there are two important parameters in the DP for mySAP
profile: BRARCHIVEMGTCLASS and REDOLOG_COPIES.
v The main purpose of the BRARCHIVEMGTCLASS keyword is to provide the
capability of separating the backup media target for the redo log files from the
backup media target for the Oracle database files.
v The main purpose of the REDOLOG_COPIES keyword is to get multiple backup
copies of the redo log files (REDOLOG_COPIES > 1) on different backup media
through the usage of different Tivoli Storage Manager management classes.
Note
| A Tivoli Storage Manager management class used by DP for mySAP
defines
– to which Tivoli Storage Manager storage pool the Tivoli Storage
Manager server will write the backup data (be it for redo log files or
Oracle database files)
– how long the Tivoli Storage Manager server will keep the backup(s) of
those files
| Be aware that Data Protection for mySAP always uses the archive capabilities of
Tivoli Storage Manager (in the context of backup and restore).
By creating multiple copies, the database administrator will be able to restore and
recover an Oracle database in an SAP R/3 environment even if a database backup
tape and/or a redo log backup tape gets corrupted or lost.
It is assumed that most customers have the requirement of having at least 2

backup copies of each redo log file on separate physical media after the backup
run (BRARCHIVE) of the redo log files.
Some general Tivoli Storage Manager aspects about resource utilization (focus on
tape drives) should be kept in mind when you implement Tivoli Storage Manager
| and Data Protection for mySAP.
| v One BRARCHIVE run might trigger via Data Protection for mySAP several
simultaneously running backup sessions.
v Running several SAP R/3 databases might cause several BRBACKUPs to run
simultaneously.
If this situation had been overseen in the planning and set up stage, it may cause
intermittent BRARCHIVE/BRBACKUP problems. Running more parallel sessions
than the number of available tape drives for the various storage tape pools will
cause severe performance degradation and will also abend some sessions in certain
situations. The utilization of disk storage pools (connected to tape storage) as
interim Tivoli Storage manager storage is one solution for such a tape congestion
problem (see item 2 below).
Depending on the value for MAX_SESSIONS, you can run one or more sessions
| simultaneously when running a backup with Data Protection for mySAP. By

specifying one or more Tivoli Storage Manager management classes in the
keyword BRBACKUPMGTCLASS or BRARCHIVEMGTCLASS you decide which
management classes will be used when running the SAP BRBACKUP or the SAP
BRARCHIVE. Two cases are considered. The management class itself is assumed to
be directly connected to both
1. a tape storage pool (Tivoli Storage Manager)
or
2. a disk storage pool (Tivoli Storage Manager) as interim storage.
In case 1, the Tivoli Storage Manager parameter MOUNTLIMIT in the DEVCLASS

(Tivoli Storage Manager) being referenced by a tape storage pool (Tivoli Storage
Manager) determines how many tape drives can be used simultaneously by this
tape storage pool, presuming that there are enough tape drives available. If there is
a limitation in the number of tape drives being requested by too many parallel
running sessions, you could consider the usage of disk storage pools for the
backup of the redo log files (case 2).
Case 2 has the advantage that several sessions can simultaneously access one disk
storage pool. There is no limitation caused by MOUNTLIMIT. Each disk storage
pool is assumed to be connected to a tape storage pool. The disk storage pool can
be migrated to the appropriate tape storage pool either:
v automatically by the Tivoli Storage Manager server (see HIGHMIG/LOWMIG
values)
or
v at particular times using your own scripts which lower the HIGHMIG to 1 thus
forcing the migration to tape.
For installations where too few tape drives are a constraint, case 2 allows you to
run several BRARCHIVEs for various SAP Oracle databases simultaneously.
Depending on your Tivoli Storage Manager environment (tape drive resources) and
your requirements, you might choose to run the backup of the redo log files
v with ’brarchive -sd -c ’
or
v with ’brarchive -s -c -r init<SID>.utl’
and then ’brarchive -scd -c -r init<SID>.utl2’
This run sequence is only used if there is, for example, only one tape drive
available, no disk storage pool can be used (case 2) as a temporary container,
and an operator would manually exchange tape cartridges. It also causes Data
| Protection for mySAP to create different backup IDs for the two BRARCHIVE
runs. For a better alternative see example 1 on page 166.
The following assumes that the backup of the redo log files will only be done with
’brarchive -sd -c’ (this means only 1 init<SID>.utl is used for 1 Oracle database
instance). Depending on what had been specified in the parameter
MAX_SESSIONS, REDOLOG_COPIES and BRARCHIVEMGTCLASS, different
behavior will be seen when running a BRARCHIVE.
| Data Protection for mySAP satisfies the BRARCHIVE request to back up redo log
files according to the following rules:
| 1. Data Protection for mySAP produces as many backup copies of each redo log
file as are specified with the REDOLOG_COPIES value.
| 2. Data Protection for mySAP requires that, for REDOLOG_COPIES N, at least N
management classes are specified for each Tivoli Storage Manager server (using
parameter BRARCHIVEMGTCLASS).
3. When the value MAX_SESSIONS is larger than REDOLOG_COPIES, DP for
| mySAP starts only N sessions where N is the nearest integer multiple of the
REDOLOG_COPIES with a value either lower than, or equal to the
MAX_SESSIONS value. For example, MAX_SESSIONS 5 and
REDOLOG_COPIES 2 causes only 4 sessions to be started.
4. When fewer sessions (M) are specified than the number of redo log copies (N),
| DP for mySAP cannot access all BRARCHIVE management classes
| simultaneously. This means DP for mySAP will, in the first round, access only
the first M management classes and will store a copy of each file in each of the
classes. In the next round(s) the remaining management classes will be
accessed, until each management class contains one copy of all files.
Example:
A Tivoli Storage Manager environment with 1 tape drive might be a 7305 or a
single drive SCSI library as the 3590_B11. In this case, you should start only 1
session (MAX_SESSIONS 1). In order to get 2 redo log copies
| REDOLOG_COPIES is set to 2. Data Protection for mySAP would begin to back
up in 1 session to the first specified management class. When all redo logs have
| been copied for the first time in Tivoli Storage Manager, then DP for mySAP
starts a new session and performs the backup to the second management class.
In this way, a new tape will be used if each management class is connected to a
different tape storage pool (see also example 1).
| 5. Data Protection for mySAP informs its caller (BRARCHIVE) once whenever it
has successfully finished the multiple backup of any redo log file (see “Hints
for BRARCHIVE Version 3.1G or Higher” on page 166)
| 6. In case of problems, DP for mySAP retries to save the file several times. DP for
| mySAP terminates if a file finally cannot be saved as often as has been
specified. An indicator is set to tell BRARCHIVE which redo log files were not
backed up. This is done to avoid any further workload (unnecessary backup
activities). (see “Hints for BRARCHIVE Version 3.1G or Higher” on page 166)
| 7. Data Protection for mySAP is a Tivoli Storage Manager client and cannot
control what the Tivoli Storage Manager server is doing. When you start
session b after session a, it doesn’t necessarily mean the server will start the
sessions in that order. The session you started later could begin backup
processing earlier, while, for example, the session you started earlier is still in
media wait. In certain situations (see example 3 below) this could mean that
another session (even started later), working with the same management class,
backs up more redo log files than the one that remained in a media wait status
longer.
Caution
To avoid an unexpected loss of data, be aware that if you are using
VERSIONING you use the same initSID.bki file for BRBACKUP and
BRARCHIVE.
| Keep in mind that BRARCHIVE informs Data Protection for mySAP via a list,
which files (redo log files) are to be backed up. Also keep in mind that the order of
the redo log file names determines the subsequent delete behavior of newer
BRARCHIVE releases.
Appendix I. Hints and Tips for SAP Backup Utilities 165

Hints for BRARCHIVE Version 3.1G or Higher
As versions 3.1G and 3.1H of SAP BRARCHIVE behave differently from previous
versions, in that they now allow the saparch directory to be cleaned-up as soon as
possible,
v BRARCHIVE does not wait until all redo log files have been backed-up before
| starting to delete them. Whenever it receives notification from DP for mySAP
about a successful completion of a backup of a redo log file, BRARCHIVE will
delete this redo log file immediately (with the option -sd or -scd) if the backup
of all other preceding redo log files in the supplied list also had been
successfully performed. If, for any reason, the backup for some redo log files
could not be completed in sequence, BRARCHIVE will postpone the deletion
until the backup of the preceding redo log files has been signaled by DP for
mySAP as completed.
v At the end of the backup of the redo log files, if one of the redo log files has not
been successfully backed up, BRARCHIVE will not delete all the following redo
log files even if they have all been successfully backed up. If BRARCHIVE is
restarted later it will start with the backup of the failed redo log file and will
redo the backup of all successive files, which have already been successfully
backed up.
In order to avoid an unnecessary workload on the SAP Oracle database
| machine, DP for mySAP will stop the backups in a session whenever a
temporarily unrecoverable situation has occurred during a backup.
Note
1. At setup time, you must ensure that sessions will not be started unless
enough tape drives are available. Otherwise you may encounter the
following problems:
v many unwanted tape mounts, thus creating long BRARCHIVE runs and
v under certain circumstances, an unsuccessful termination of the
BRARCHIVE (or other BRBACKUP) run
v in the case of an unsuccessful termination, successfully backed up redo
log files would have to be backed up again (see the above hint for SAP
BRARCHIVE 3.1G/3.1H)
2. Specifying arbitrary values for MAX_SESSIONS and REDOLOG_COPIES
and an arbitrary number of management classes can produce unfavorable
run behavior in the Tivoli Storage Manager server specially when tape
media is directly used (case 1).
For example: If there are only 2 tape drives available, MAX_SESSIONS 3,
REDOLOG_COPIES 1, BRARCHIVEMGTCLASS mgmt1 mgmt2 would
probably cause many unwanted tape mounts.
Examples Using MAX_SESSIONS and REDOLOG_COPIES

The following four examples should help to clarify the usage of MAX_SESSIONS
and REDOLOG_COPIES:
1. MAX_SESSIONS 1, REDOLOG_COPIES 2. Two different
BRARCHIVEMGTCLASS management classes.
| Only one DP for mySAP agent (session) will be started. All files are sent to the
first archive management class. After this is done, all files are sent to the
second archive management class. This means the first copy is stored on tape
one, the second copy is stored on tape two (assuming different tape storage
pools are connected to the two archive management classes).
In this case, two sessions will be started. The first session sends all files to the
first archive management class, the second session backs up all files to the
second archive management class. Both sessions run parallel and independently
of each other. Presuming that two tape drives are available, two tapes will be
written, each containing a complete backup set of files (redolog copies).
In this case, four sessions will be started. Sessions one and three access the first
archive management class. They both send the first copy of each file to this first
management class. Similarly, sessions two and four access the second archive
management class and store the second copy of each file on the second
management class.
This scenario makes sense, when at least four tape drives are available, because
only then the four sessions can run in parallel. In this case, four tapes will be
written. Tapes one and three contain the first copy of all files and tapes two
and four contain the second copy of all files.
If only two tape drives are available, you should set up archive management
classes on disk pools instead of tape pools, because then the four sessions can
run in parallel. After the files have been stored on disk, they can be migrated in
an independent step from the two disk pools to two tapes.
4. MAX_SESSIONS 4, REDOLOG_COPIES 4. Four different
This is a very unlikely example for a real production environment. Here, DP for
| mySAP will produce four backup copies of each redo log file.
Again, four sessions will be started. Session one accesses the first archive
management class, session two accesses the second archive management class
and so on. As in case three, at least four tape drives must be available. If not,
four different disk storage pools connected to four different tape storage pools
are needed in order to get the four copies of one redo log file to four different
tapes.
mySAP Backup and Recovery Scenarios Using Data Protection for

mySAP
The backup and restore/recovery scenarios presented in the following sections are
| meant to illustrate a general strategy for using Data Protection for mySAP in a
| mySAP environment. Your actual backup/restore scenario may be quite different.
Hence, when performing a real backup/restore, consult your SAP online
documentation to see how this should be done exactly.
The scenarios in the first section show how a backup can be started:
v Full online/offline backup with BRBACKUP
v Tablespace backup with SAPDBA.
| The second section shows a restore of a mySAP tablespace and a subsequent
| recovery of the mySAP database with the help of SAPDBA.
| In the following examples it is assumed that the mySAP system is installed on a

| UNIX or Linux machine.

Backup Scenarios
A backup is essential for a subsequent restore and recovery. Two backup methods,
one using BRBACKUP directly and the other using BRBACKUP via SAPDBA, will
be described. These SAP database utilities can store the backed up data on the
| Tivoli Storage Manager server with the help of DP for mySAP.
Online/Offline Backup with BRBACKUP

BRBACKUP is a database utility provided by SAP to perform a backup function of
| the mySAP Oracle database. You can use BRBACKUP to back up the following
objects of an Oracle database:
v Data files
v Control files
v Online redo log files
BRBACKUP can be invoked directly from the operating system command level,
| using the SAPDBA backup function or from mySAP within the Computing Center
Management System (CCMS). For further information about BRBACKUP see your
SAP online documentation.
To invoke BRBACKUP it is necessary to log on either as <SID>adm or as ora<SID>.

You can see an overview of all permitted BRBACKUP parameters using the
command:
brbackup -help
| To start an online backup of the mySAP database, the following command has to
be executed:
brbackup -c -t online
The parameter -c is used to enable the backup to run in unattended mode so that
no further user input during the backup operation is required. Command
parameter -t online specifies the backup as an online backup.
Note
| The mySAP database must be running in ARCHIVE mode if you want to
perform online backups. This means the online redo logs, in which all
database changes are recorded, will be archived before they are overwritten.
In a similar manner, an offline backup can be invoked by BRBACKUP. But you

| have to consider whether the mySAP database is running or not.
If the database is running, BRBACKUP first shuts down the database instance.
Therefore, BRBACKUP must be started with the offline_force parameter.
brbackup -c -t offline_force
| If the backup is finished, BRBACKUP starts the mySAP database instance again. If
| the earlier mySAP database instance has been stopped, BRBACKUP can be started
with the normal offline parameter.
brbackup -c -t offline
During the backup, several screen messages will be issued. Each message has its
own message code. By means of this code the messages can be classified into:
v Error messages - last letter of a message code is an ″E″
v Warning messages - last letter of a message code is a ″W″
v Informational messages - last letter of a message code is an ″I″
All these messages codes have a specific prefix. This prefix shows from which
program a message was generated. The various prefixes are:
v ANS/ANR - ADSM or Tivoli Storage Manager messages
| v BKI - Data Protection for mySAP messages
v BR - BRARCHIVE, BRBACKUP or BRRESTORE messages
v ORA - Oracle database kernel messages
v RMAN - Oracle Recovery Manager messages
After BRBACKUP has finished, it is recommended that you check the backup log
for warnings and unexpected errors. The backup log is located in
/oracle/SID/sapbackup (or in /oracle/SID/saparch if it was a BRARCHIVE run).
All the screen messages are included in this file. All entries for successfully backed
up files should be preceded by #SAVED. An error occurred if there are any #ERROR or
#NOTFOUND messages.
If an error occurs, the first step is to check the content of the protocol described
above. First of all, you should locate the error messages and, with use of the
appropriate manual, you can relate the message code to an explanation about the
error that occurred and a recommendation for user response.
Tablespace Backup With SAPDBA

| The management or administration of a mySAP Oracle database generally cannot
be carried out from within the SAP system itself. As a result, SAP has developed a
tool called SAPDBA to provide and simplify the administration of the Oracle
database system. Among other things, SAPDBA provides an extensive backup
function for a full database backup, backup of selected tablespaces, and backup of
offline redo logs. For these backup operations SAPDBA invokes the appropriate
database utilities BRBACKUP or BRARCHIVE. Further information about SAPDBA
can be found in the SAP online documentation.
| The following shows an example backup of a mySAP tablespace, called

PSAPUSER1D.
To invoke SAPDBA, it is necessary to log on as ora<SID> . After SAPDBA starts,

the following screen will appear:

___________________________________________________________________________
SAPDBA V4.5B - SAP Database Administration
___________________________________________________________________________
Oracle version: 8.0.5.2.0
ORACLE_SID : C21
ORACLE_HOME : /oracle/C21
DATABASE : open
SAPR3 : 45B, 7 times connected
a - Startup/Shutdown instance h - Backup database

b - Instance information i - Backup offline redo logs
c - Tablespace administration j - Restore/Recovery
d - Reorganization k - DB check/verification
e - Export/import l - Show/Cleanup
f - Archive mode m - User and Security
g - Additional functions n - SAP Online Help
q - Quit
Please select ==>
To carry out tablespace backup, the Backup database functions have to be started
with the h key which causes the following screen to pop up:
___________________________________________________________________________
Backup database
___________________________________________________________________________
Current value
a - Backup function Normal backup
b - Parameter file initC21.sap
c - Backup device type util_file_online
d - Objects for backup all
e - Backup type online
g - Query only no
h - Special options ...
i - Standard backup yes

j - Backup from disk backup
k - Restart backup
l - Make part. backups compl.
S - Start BRBACKUP
q - Return
Please select ==>
As already mentioned on page 29, the SAP Backup profile initC21.sap has to be
correctly customized in view of:
v The backup type (online, offline) and
v The backup utility parameter file
| To check the backup utility parameter file (in case of DP for mySAP usage, it
should be set to initC21.utl, which is in the /oracle/C21/dbs directory) go to the
Special options ... menu with the h key and the following screen will be
displayed:
___________________________________________________________________________
Backup database: Details
___________________________________________________________________________
Current value
a - Confirm backup parameters no
d - Backup utility parameter file /oracle/C21/dbs/initC21.utl
e - Enter password interactively no
i - Language English
q - Return
Please select ==>
If everything was set correctly, go back with the q key to the Backup database
screen as shown above.
Now you have to specify the object(s) which you want to back up. This can be
done by choosing the Objects for backup option with the d key within the Backup
database menu. The following screen appears:
Format for the desired objects for backup: <item> or <item>,<item>,...
An <item> can be
- "all"
- "all_data"
- "sap_dir"
- "ora_dir"
- a tablespace_name
- an Oracle file id <number> or a range of file ids <number>-<number>
- an absolute file or directory name
Enter objects for backup ==>
Enter the desired name of the tablespace for the backup, in this case psapuser1d. If
you have returned to the Backup database screen you can start the backup
procedure by selecting the Start BRBACKUP function (S key). All the other
parameters which are visible and were not discussed should not be changed. These
are default parameters set by SAPDBA. For further information about this see the
SAPDBA manual.
| After starting the backup procedure BRBACKUP starts DP for mySAP to send the
data files belonging to the tablespace PSAPUSRE1D to the Tivoli Storage Manager
server. The backup is successfully finished if there is a message such as the
following on the screen:

BR056I End of database backup: bdbhowho.pnf 1999-11-08 11.19.42
BR052I BRBACKUP terminated successfully.
SAPDBA: BRBACKUP executed successfully.

Press <return> to continue ...
All the messages displayed on the screen during the backup will be written to a
BRBACKUP log file which will be stored in the /oracle/C21/sapbackup directory
with a unique name as shown in the box above (bdbhowho.pnf). If errors occurred,
check the content of this log file for a detailed error analysis.
The backup is now finished and you can leave the SAPDBA.
Restore/Recovery Scenario
| If you need to do a restore/recovery of the mySAP database as a result of
corruption or loss of data files, the recommendation is to use the SAPDBA
database utility for this action because it guides you, step by step, through all
necessary procedures. For the automatic recovery mode these are:
v Check database
v Find backup files
v Restore backup files
v Find archive files
v Restore archive files
v Recover database
SAPDBA uses the program BRRESTORE for restoring the database. This program
| invokes DP for mySAP for restoring all the necessary tablespace files or archived
redo log files from the appropriate Tivoli Storage Manager server. After the restore
has finished successfully, the necessary recovery will be performed by SAPDBA.
The following describes two possible recovery scenarios: The recovery of a single
| mySAP tablespace and a complete (full) recovery of the mySAP database in case of
a serious disaster.
Recovery of a Tablespace
In this case we assume that we have a problem with a data file which belongs to
the tablespace PSAPUSER1D (for example data file corruption or loss of a data file).
After starting SAPDBA, the initial SAPDBA screen as shown on page 170 appears.
Note
Restore and recovery operations within SAPDBA can only be done in the
so-called expert mode. For information on how to switch to that mode see the
SAPDBA manual.
To perform a tablespace restore/recovery the Restore/Recovery function has to be

started by pressing the j key. The following screen appears:
___________________________________________________________________________
Restore/recovery
___________________________________________________________________________
a - Partial restore and complete recovery (Check and
repair, redo logs and control files are prerequisites)
b - Full restore and recovery
(excl. redo logs, control files incl. if required)
c - Reset database
(incl. redo logs and control files)
d - Restore one tablespace

e - Restore individual file(s)
q - Return
Please select ==>
In this case, only a partial restore (data files for the tablespace PSAPUSER1D) is to be
| carried out, with a complete recovery of the mySAP database subsequently. Thus,
Partial restore and complete recovery is selected by pressing the a key. The
following screen is then displayed:
___________________________________________________________________________
Partial restore and complete recovery

___________________________________________________________________________
Status
a - Check database not finished

b - Find backup files not finished
c - Restore backup files not finished
d - Find archive files not finished
e - Restore archive files not finished
f - Recover database not finished
g - Automatic recovery
q - Return
Please select ==>
All the functions seen in this screen must be carried out in alphabetical order,
unless you use the Automatic recovery function which is activated with the g key.
The Automatic recovery function runs through all of the above functions starting
with Check database and ending with Recover database. If an error occurred
during this process, the automatic recovery stops at the function where the error
occurred.
After beginning the automatic recovery procedure, a number of screen messages

will be seen, most of them only for informational purposes to describe the
progress. In some cases, confirmation in the form of Press <return> to continue
or yes without any further information may be requested. Read all the instructions
on the screens carefully and wherever possible follow the recommendations of
SAPDBA.

Full Recovery
| In some cases, a full recovery of the mySAP database must be initiated, such as in
the case of loss of several data files. This means that all necessary:
v data files
v redo log files
v control files
must be restored and the database subsequently recovered.
As SAPDBA provides a function for carrying out a full restore/recovery, it is

recommended that, as with the partial restore/recovery, you also use SAPDBA to
| perform a guided full recovery of the mySAP database.
In contrast to the partial restore, to start the full recovery select the function Full
restore and recovery by pressing the b key in the following screen (to reach this
screen see “Recovery of a Tablespace” on page 172).
___________________________________________________________________________
Restore/recovery
___________________________________________________________________________
a - Partial restore and complete recovery (Check and
repair, redo logs and control files are prerequisites)
b - Full restore and recovery
(excl. redo logs, control files incl. if required)
c - Reset database
(incl. redo logs and control files)
d - Restore one tablespace

e - Restore individual file(s)
q - Return
Please select ==>
When beginning the full restore/recovery, SAPDBA recommends backing up the

whole database if the database is not damaged. Otherwise, at least a backup of the
redo log files is recommended.
The next step is to select a full online/offline backup previously made. This can be
done with the function Select a full online/offline backup by pressing the A
key. If no backup has been previously carried out, the restore/recovery status is
disallowed (see screen below).
___________________________________________________________________________
Full Restore and Recovery
___________________________________________________________________________
DATABASE STATE : mounted
RESTORE / RECOVER: disallowed (see status)
Current setting
A - Select a full online/offline backup
b - Recover until now
c - Show status
D - Restore and recover
q - Return
Please select ==> A
1-bdbeejyv.aff 1999-10-21 12.20.41 ALL offline db_to_util_file

2-bdbejsiq.anf 1999-10-22 14.19.44 ALL online db_to_util_file_online
3-bdbfefgf.anf 1999-10-26 18.23.49 ALL online db_to_util_file_online
4-bdbfhuiv.anf 1999-10-27 11.52.45 ALL online db_to_util_file_online
5-bdbfroqz.anf 1999-10-29 11.38.01 ALL online db_to_util_file_online
6-bdbghtwj.anf 1999-11-01 17.43.37 ALL online db_to_util_file_online
7-bdbgljpc.anf 1999-11-02 11.19.32 ALL online db_to_util_file_online
8-bdbgqlxo.aff 1999-11-03 12.10.24 ALL offline db_to_util_file
9-bdbgwhhw.aff 1999-11-04 16.36.08 ALL offline db_to_util_file
Please, enter the number of the BRBACKUP run that you want to restore
(q = quit) [9] ==> 9
It is recommended that you use the latest BRBACKUP run for the restore function.
In the above case this is selection 9.
After you have completed this, SAPDBA will try to find archive files using the
| inquire function of DP for mySAP. Ensure that the SAP Backup profile
initC21.sap is properly customized (see also page 29). If SAPDBA returns to the
full restore and recovery screen, the restore/recovery status will have been
changed to allowed.
By selecting restore and recover (by pressing the D key), the restore/recovery
procedure can be started.
All the steps which are now carried out are similar to those in the section
“Recovery of a Tablespace” on page 172. The only difference is that a check of the
database to see which files are missing is not performed, because all data files, all
control files, and all necessary redo log files will be restored anyway.
Subsequently, the recovery of the database will be commenced.

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

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

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

306.ibm.com/software/tivoli/products/storage-mgr-erp/.
Glossary
A and retrieving files to or from the TSM server. Compare
with —> administrative client.
Activate. In Tivoli Storage Manager, the process of Backup copy group. A policy object containing
validating the contents of a policy set and copying the attributes that control the generation, destination, and
policy set to the ACTIVE policy set. expiration of backup files. A backup copy group
belongs to a management class.
Active policy set. In Tivoli Storage Manager, the
policy set that contains the policy rules currently in use Backup Server. A Tivoli Storage Manager server
by all client nodes assigned to the policy domain. The where DP for mySAP.sends the backup data to and
active policy set is the policy set that was most recently retrieves data from for restore.
activated for the policy domain.
Backup Version Control. A feature of Data Protection
Adaptive File Sequencing. During backup, this for mySAP allowing the customer to specify the
feature of Data Protection for mySAP optimizes number of full database backups to be kept on the TSM
performance by calculating a certain sequence of files server. Obsolete database backups are deleted together
to be backed up. This sequence considers the file sizes with all dependent data (for example log files,
to be backed up and the distribution of files on several incremental backups, etc.).
disks.
BRARCHIVE. An SAP database utility to perform
Administration Assistant. A Web browser based backups of offline redo log files in a mySAP Oracle
graphical interface to support and assist the database environment.
customizing of DP for mySAP (System Configuration)
and the analyzing of mySAP database backup and BRBACKUP. An SAP database utility to do
restore operations (Operations Monitor, Performance online/offline backups of mySAP Oracle databases.
Monitor). BRBACKUP can be used to back up data files, control
files and online redo log files.
| Administration Assistant Server Configuration File..
| The file containing the configuration of your BRCONNECT. This ensures, that the database status
| Administration Assistant server. The default file name required for the online/offline backup of a mySAP
| of the server configuration file is assist.cfg, located in Oracle database remains unchanged during the backup.
| the installation path of the Administration Assistant BRCONNECT will be started only internally by
| server. BRBACKUP/BRARCHIVE.
Administrative client. In Tivoli Storage Manager, a BRRESTORE. An SAP database utility to restore an
program that runs on a file server, workstation, or entire Oracle database backup or parts of it, previously
mainframe that allows administrators to control and backed up with BRBACKUP or BRARCHIVE. Any
monitor the Tivoli Storage Manager server through non-database files and directories which were saved
administrator commands. Compare with –> can also be restored. Subdirectories within the sapdata
backup-archive client. directories will be created automatically, when
necessary.
Archive copy group. In Tivoli Storage Manager, a
policy object containing attributes that control the
generation, destination, and expiration of archive files. C
An archive copy group belongs to a management class.
Client options file. A configuration file of the TSM
ARCHIVELOG mode. A database can run in client containing a set of processing options that
ARCHIVELOG mode or in NOARCHIVELOG mode. identify the server, communication method, and
Production systems must run in ARCHIVELOG mode options for backup, archive, hierarchical storage
in order to allow proper backup restore. Test systems management, and scheduling. Its default name is
can run in NOARCHIVELOG mode. | dsm.opt on UNIX or Linux systems and
<servername>.opt on Windows.
B Client system options file. A configuration file of the
| TSM client residing on UNIX or Linux systems,
Backup-archive client. A component of Tivoli Storage containing a set of processing options that identify the
Manager running on a workstation or file server, Tivoli Storage Manager servers to be contacted for
providing a means for backing up, archiving, restoring, services. This file also specifies communication

methods and options for backup, archive, hierarchical
storage management, and scheduling. Its name is
I
dsm.sys.
Include/exclude list. A group of include and exclude
Control file. A file associated with a database that option statements in a file. Tivoli Storage Manager
maintains the physical structure and time stamps of all backup-archive client uses the statements to determine
files within that database. The control file is updated whether to back up or migrate certain files, and to
continuously during database use and must be determine the associated management classes to use for
available for writing, if the database is mounted or backup, archive, and space management. The exclude
opened. options identify files that should not be backed up or
migrated off the client node. The include options
Copy group. A policy object of the TSM server identify files that are exempt from the exclusion rules,
containing attributes that control the generation, or assign a management class to a file or group of files
destination, and expiration of backup and archive files. for backup, archive, or space management services. The
There are two kinds of copy groups: backup and include/exclude list is defined either in an
archive. Copy groups belong to management classes. | include/exclude file (for UNIX or Linux clients) or in
the client options file (for other clients).
D Incremental Backup. An incremental backup saves

only those blocks within the database, which have been
Database Server. The server where the SAP database changed since the last full backup. SAP R/3 release
resides. DP for mySAP and the TSM API must be 4.5.A and later versions permit incremental backups of
installed on this server. Oracle databases using Oracle’s Recovery Manager
RMAN.
Data Protection for mySAP File Manager. A utility
that simplifies the DP for mySAP inquire, restore and
delete operations. It can be seen as an add-on to DP for L
mySAP.
LAN-free backup. Backup to a backup server residing
Data block. The smallest unit of a database on system different from that of the database server.
The database and backup servers are connected via
Data file. A data file is a physical operating system LAN. However, backup data is transferred directly to
file on disk, which contains data structures of a the storage media via SAN.
database, such as tables and indexes. A data file only
belongs to one database and to one tablespace. Local Backup. Backup to a local backup server.
Device class. A named group of storage devices of a Local Backup Server. Backup server residing on the
TSM server with common characteristics. Each device same system as the database server does.
class has a unique name and represents a device type
of disk, file, optical disk, or tape.
M
DISK. A device class that is defined by Tivoli Storage
Manager at installation. It is used to categorize disk Management class. A policy object that users can bind
drives, such as internal disk drives. to each file to specify how the server manages the file.
The management class can contain a backup copy
| DP for mySAP. An abbreviation for ’Data Protection group, an archive copy group, and space management
| for mySAP’, which used in this document. attributes. The copy groups determine how the Tivoli
Storage Manager server manages backup versions or
archive copies of files. The space management
F attributes determine whether files are eligible for
migration from space manager client nodes to Tivoli
| File Manager. See —> Data Protection for mySAP File Storage Manager storage, and under what conditions.
| Manager
Media Management API. An interface provided by
File space. A logical space in a TSM server assigned to Oracle to which vendors are able to write compatible
a specific client. Clients can restore, retrieve, or delete software libraries. This software integrates with Oracle.
contents of their file spaces from Tivoli Storage Thus, an Oracle server process is able to issue
Manager server storage. commands to the media manager to write backup files
Tivoli Storage Manager does not necessarily store all out to sequential storage (e.g., Tivoli Storage Manager)
the files from a single file space together, but can and read files from sequential storage.
identify all the files in server storage that came from a
single file space.
N Remote backup server. Backup server residing on a
system different from that of the database server. Data
as well as control information is sent via LAN.
Node.
1. TSM: A unique name used to identify a Tivoli Retention. The amount of time, in days, that inactive
Storage Manager client to the TSM server. files backed up or archived to a TSM server are kept by
2. SMP: Single machine in a Symmetrical the backup server before they are deleted. Copy group
Multiprocessor (SMP) environment. attributes and default retention grace periods for the
domain define retention.
O
S
Offline redo log. If the database is in ARCHIVELOG
mode and an online redo log is filled, it is copied to SAP BACKINT interface. An interface provided by
one (or more) archive log destination(s), which is SAP database utilities BRBACKUP, BRARCHIVE and
typically the saparch directory in a mySAP BRRESTORE that can be used to access external backup
environment. This copy is the offline redo log (also programs, for example DP for mySAP.
called archived redo log).
SAPDBA. An SAP database tool to provide and
Online redo log. The online redo log is a set of two or simplify the administration of an Oracle database
more files which record all changes made to Oracle system within a mySAP environment. SAPDBA
data files and control files. provides a collection of database
management/administration functions, for example
tablespace administration, which can only be
P performed outside of a mySAP system.
Path. A connection between a Tivoli Storage Manager Scratch volume. A volume that is available for Tivoli
node and a Tivoli Storage Manager server interface. At Storage Manager use. The volume is either labeled, or
the client side, a path is defined by a logical server blank or contains no valid data, and is not defined to
| name listed in the client option file dsm.sys ( UNIX or Tivoli Storage Manager.
| Linux systems) or <servername>.opt (Windows
systems). At the server side, the possible paths are | Server Configuration File. See —> Administration
defined by the network addresses of the Tivoli Storage | Assistant Server Configuration File.
Manager server.
Session. Single TCP/IP connection between a Tivoli
Policy domain. A policy object that contains policy Storage Manager —> node and a Tivoli Storage
sets, management classes, and copy groups that are Manager server. A TSM server may be configured to
used by a group of client nodes. allow a number of sessions from a TSM node to the
server in parallel over the same communication —>
Policy set. A policy object that contains a group of path.
management class definitions that exist for a policy
domain. At any one time there can be many policy sets Storage pool. A storage pool is a named collection of
within a policy domain but only one policy set can be storage volumes that are associated with one device
active. class. Each storage pool represents a collection of
volumes that are the same media type. For example, a
Programmed Operator. See —> ProLE. storage pool that is associated with a device class for
8 mm tape contains only 8 mm tape volumes.
| ProLE. The background process ( UNIX and Linux ) or
service (Windows) controlling backup and restore
operations of DP for mySAP. T
Tablespace. A database is divided into one or more
R logical storage units, which are tablespaces. Each
tablespace has a set of data files exclusively associated
Recovery Manager (RMAN). A tool used to back up, with it.
restore and recover Oracle databases. It can be used
with or without a Recovery Catalog,. If a Recovery Tivoli Storage Manager (TSM). IBM Tivoli Storage
Catalog is not used, Recovery Manager decides how to manager, a client/server program that provides
back up, restore and recover the database using the policy-driven storage management to customers in a
control file of the database. Incremental backups of multivendor computer environment.
Oracle databases can only be done with RMAN.
Remote backup. Backup to a —> remote backup

server.
Glossary 181
Tivoli Storage Manager API. A set of functions that
applications running on a client platform can call to
store, query, and retrieve objects from Tivoli Storage
Manager storage.
U
util_file_online. A (data file) backup using an external
backup program addressed by the BACKINT interface.
If an online backup is running, the backup status is set
and completed dynamically for the tablespaces being
backed up. In this way, the volume of offline redo log
files during an online backup can be reduced
significantly.
V
Validate. In Tivoli Storage Manager, the process of
ensuring that the active policy set contains a default
management class and reports on copy group definition
errors.
Volume. The basic unit of storage for the Tivoli

Storage Manager database, recovery log, and storage
pools. A volume can be an LVM logical volume, a
standard file system file, a tape cartridge, or an optical
cartridge. Each volume is identified by a unique
volume identifier. See —>database volume, —>scratch
volume, and —>storage pool volume.
Index
A archive copy group
glossary definition 179
Backup Server (continued)
performance optimization 37
activate archivelog mode profile examples 137
glossary definition 179 glossary definition 179 backup sessions 163
active policy set authorizing Administration Assistant Backup Status
glossary definition 179 users 67 monitoring 18
Adaptive File Sequencing 16 automating backup and archive backup strategy
glossary definition 179 operations 9 defining 5
Administration Assistant 18, 59 availability improvements for mySAP System data 8
adjusting 42 with alternate/parallel paths and for Operating System 5
authorizing users 67 servers 18, 137 for Oracle Database 5
concepts 59 with multiple redo log copies 17 for Protocols and Profiles 7
configuration tool 59 planning 5
Configure Systems 59 Backup Version Control 17, 44
customizing 59
glossary definition 179 B glossary definition 179
backup-archive client
installing 61 BACKAGENT 83
Java 61 backend processing 18
Backup/Restore
migration 66 BACKEND profile keyword 84
Monitor Operations 59 BACKINT
multiplexing 38
monitoring tool 59 interaction with DP for mySAP 3
BACKUPIDPREFIX profile keyword 84
operations monitoring 59 troubleshooting 126
Balancing you system 69
Overview 59 backup 167
BATCH profile keyword 84
Problem Support 59 automated 9
BRARCHIVE 13
Secure Communication 67 BRBACKUP 167
Simulate backup/restore 59 incremental 6, 8, 11, 17, 51
BRARCHIVEMGTCLASS profile
upgrading 66 messages 169
keyword 17, 84
View performance data 59 of AIX system data 5
BRBACKUP 13
Web browser, remote method of Oracle database elements 5
backup of Oracle database 168
invocation 61 of SAP system data 8
Administration Assistant Client online/offline 168, 172
BRBACKUPMGTCLASS profile
Java 62 parallel 16
keyword 17, 85
prerequisites 62 path 16
BRCONNECT
setting up 65 profile & protocol file directories,
verifying the installation 65 UNIX 8
BRRECOVER 13
Administration Assistant Server 24 profile & protocol file directories,
BRRESTORE 13
initial installation 63 Windows 8
installation planning 62 profiles 7
restore of Oracle database 172
installing 63 protocols 7
BUFFCOPY profile keyword 85
post installation process 64 SAPDBA 167
BUFFSIZE profile keyword 85
prerequisites 61 scenarios 168, 172
secure connection to clients 64 simulating 75, 85, 92
specifying 42 strategy for operating system 5
uninstalling 64 tablespace 169 C
upgrade installation 63 terminating 138 client options file
verifying the installation 65 user data 8 glossary definition 179
Administration Assistant Server backup copy group client system options file
Configuration File glossary definition 179 glossary definition 179
glossary definition 179 backup paths UNIX and Linux example 159
upgrading 67 alternate/parallel 16 Windows example 160
administrative client profile examples 137 client user options file
glossary definition 179 backup scheduler UNIX or Linux example 159
ADSMBUFFSIZE 83 IBM Tivoli Workload scheduler 10 client/server connection paths 137
ADSMNODE profile keyword 83 Linux crontab / Windows cloning
alternate / parallel backup paths 16 scheduler 9 mySAP system 79
alternate path 18 SAP scheduler 9 redirected restore 58
alternate/parallel backup paths Tivoli Storage Manager scheduler 10 CommonStore 19
example for availability 139 UNIX crontab / Windows COMPR_INFO profile keyword 85
example for performance 141 scheduler 9 compression 17, 36
reasons to use 137 Backup Server null block 41
alternate/parallel backup servers 18 alternate/parallel 18 Tivoli Storage Manager 41
example 3 for disaster recovery 142 glossary definition 179 when restoring 77

CONFIG_FILE profile keyword 86 DP for mySAP (continued) examples (continued)
configuration database utilities 13 Tivoli Storage Manager profiles for
optimization 69 glossary definition 180 Windows 160
configuration matrix for Tivoli Storage installing 23 EXITONERROR profile keyword 86
Manager password settings 150, 151 introduction 13
control file messages 101
backing up 6
migration 31
Oracle recovery manager 13
F
FCS_FILE profile keyword 86
Oracle database 168 overview 13
File Manager 55
copy group profile
error messages 121
glossary definition 180 keyword descriptions 83
function keys 56
crontab keyword rules 83
inquire, restore, delete functions 55
file example 153 Windows sample 96
File Sequencing 16
scheduling backups with 9 profiles
File space
customization UNIX or Linux sample 92
Administration Assistant 59 upgrading 23, 31
FILE_RETRIES profile keyword 86
DP for mySAP File Manager
files
error messages 121
backup 8
D DSMI_CONFIG 24
DSMI_LOG 24
log 8
daily backups 10 Oracle database 168
data block profile & protocol file directories 8
glossary definition 180 protocol 8
data compression E FlashCopy
and overall throughput 72 END profile keyword 86 Backup 19
hardware vs. software 148, 149 Enterprise Storage Server 19 Restore 19
null block 41 environment variable frontend processing 18
Tivoli Storage Manager 41 DSMI_CONFIG 24 FRONTEND profile keyword 86
data file DSMI_LOG 24 full offline batch backup
glossary definition 180 error messages 102 Windows example 156
Oracle database 168 DP for mySAP 101
data files DP for mySAP File Manager 121
backing up 6
backup of 7
examples
alternate/parallel paths for
H
HACMP 45
Data Protection for mySAP availability 139
installing and setup 46
see: DP for mySAP 121 alternate/parallel paths for disaster
hardware compression 148, 149
Data Protection for mySAP file manager recovery 142
compared with Tivoli Storage
glossary definition 180 alternate/parallel paths for increased
Manager client software
data spaces performance 141
compression 148, 149
backing up 6 client system options file (UNIX and
data throughput 69, 71 Linux) 159
actual rate 76 client system options file
Database Server (Windows) 160 I
glossary definition 180 client user options file (UNIX or inactive data
performance optimization 36 Linux) 159 archiving of 19
DB2 CommonStore for SAP 19 client user options file include/exclude list 8
delete (Windows) 160 glossary definition 180
troubleshooting 133 crontab file 153 UNIX and Linux example 159
device class full offline batch backup Windows example 162
glossary definition 180 (Windows) 156 incremental backup 17, 51
disaster recovery include/exclude list (UNIX and glossary definition 180
example 3 for disaster recovery 142 Linux) 159 incremental backup function of Tivoli
with alternate/parallel paths and include/exclude list (Windows) 162 Storage Manager 8
servers 137 offline backup shell script 154 individual tablespace locking 17
DISK saving and deleting redo logs (UNIX inquire function
glossary definition 180 or Linux) 155 BRRESTORE 133
disk I/O saving and deleting redo logs SAPDBA 133
actual rate 75 (Windows) 157 installing
disk sorting scheduled batch backup Administration Assistant 61
manual 16 (Windows) 156 Administration Assistant Client,
DISKBUFFSIZE 83 scheduling backup jobs (UNIX or prerequisites 62
DP for IBM ESS for mySAP 19 Linux) 153 Administration Assistant Server 63
DP for mySAP scheduling backup jobs Administration Assistant Server,
architecture and properties 13 (Windows) 156 prerequisites 61
BACKINT 13 specifying MAX_SESSIONS and Administration Assistant, installation
backup library 13 REDOLOG_COPIES 166 verification 65
components 13 Tivoli Storage Manager profiles for installing DP for mySAP 23, 25
Console Installation 32 UNIX or Linux 159 Firewall Installation 32
installing DP for mySAP (continued)
initial installation 25
L N
migration 25 LAN-free backup network
on AIX, HP-UX, Linux, Solaris) 25 glossary definition 180 actual throughput rate 76
on Windows 27 Linux crontab, backup scheduler 9 parameter settings 177
Password handling 28 Local Backup performance optimization 36, 177
planning for Installation 24 glossary definition 180 setup 177
Planning sheet 135 Local Backup Server node
Post Installation Steps 28 glossary definition 180 glossary definition 181
prerequisites 23 locking maxnummp 147
Silent Installation 31 individual tablespace 17 number of mount points 146
TSM API installation 25 log files Tivoli Storage Manager server 146
TSM Option file 28 location 125 null block data compression 41
upgrade installation (migration) 25 LOG_SERVER profile keyword 86
verifying the installation 29 Logging
verifying the TSM API installation 30 Messages 18 O
offline backup shell script
example 154
J M offline redo log 5, 6, 7, 8, 10
Java management classes 17 glossary definition 181
prerequisite for Administration glossary definition 180 online redo log 6, 7, 8
Assistant Client 62 Tivoli Storage Manager server glossary definition 181
prerequisite for Administration configuration 145 operating system backup
Assistant Server 61 manual sorting of files 16 strategy 5
matrix optimizing
for setting Tivoli Storage Manager backup 69
passwords 151 restore 77
K MAX_ARCH_SESSIONS profile Oracle data spaces
keywords keyword 87 backing up 6
ADSMNODE 83 MAX_BACK_SESSIONS profile Oracle database
BACKEND 84 keyword 87 backup 168
BACKUPIDPREFIX 84 MAX_RESTORE_SESSIONS profile files 168
BATCH 84 keyword 87 Oracle database server
BRARCHIVEMGTCLASS 17, 84, 163 MAX_SESSIONS profile keyword 87 concepts 5
BRBACKUPMGTCLASS 17, 85 example 166
BUFFCOPY 85 MAX_VERSIONS profile keyword 88
BUFFSIZE 41, 85
COMPR_INFO 85
media management API
P
CONFIG_FILE 86 parallel backup and restore
messages
END 86 number of parallel sessions to
DP for mySAP 102
EXITONERROR 86 specify 87
logging of 18
FCS_FILE 86 parallel backup paths
severity levels 102
FILE_RETRIES 86 sample 2 for increased
migration
FRONTEND 86 performance 141
DP for mySAP 31
LOG_SERVER 86 parallel backup servers
mirroring control and redo log files in
MAX_ARCH_SESSIONS 87 alternate 18
Oracle 6
MAX_ARCH_SESSIONS 87 parallel backup sessions 163
monitoring DP for mySAP 59
MAX_BACK_SESSIONS 87 parallel path 16
mount points
MAX_RESTORE_SESSIONS 87 example for increased
maximum number per node 147
MAX_SESSIONS 87, 163 performance 141
node parameter maxnummp 147
MAX_VERSIONS 88 parallel sessions 16, 178
multiple copies of redo logs 163
MULTIPLEXING 38, 88 password handling
multiple paths 178
obsolete 83 automatic generation 44
Multiple Redo Log Copies 17
PASSWORDREQUIRED 89 configuration matrix (UNIX or
multiple servers
REDOLOG_COPIES 89, 163 Linux) 150
when restoring 77
REPORT 89 configuration matrix (Windows) 151
multiple sessions 16
RL_COMPRESSION 41, 90 manual generation 43
multiplexing 16, 36, 38
SERVER 90 no password usage 43
when restoring 77
SESSIONS 90 PASSWORDREQUIRED profile
MULTIPLEXING profile keyword 38, 88
SORT_FILE 91 keyword 89
mySAP
syntax for all keywords 83 Path
backup 167
TCP_ADDRESS 91 alternate 18
system cloning 79
TRACE 91 backup 16
system landscape and backup/restore
TRACEFILE 92 glossary definition 181
performance 35
TRACEMAX 92 PERF_MONITOR 83
USE_AT 92 Performance Analysis 18
performance monitoring 69
Administration Assistant 59
Index 185
performance monitoring (continued) redo logs (continued) security settings
using sensors 70 Multiple Copies 17 authorizing Administration Assistant
performance optimization recovery 174 users 67
Backup Server 37 saving and deleting 155, 157 server
backup types 36 UNIX or Linux example 155 installing Administration Assistant
backup/restore 35 Windows example 157 Server 63
by changing buffer size 41 REDOLOG_COPIES profile keyword 89 Server configuration file
by compressing data 41 example 166 glossary definition 181
by multiplexing 38, 72 Remote Backup SERVER profile keyword 90
by setting up proper environment 38 glossary definition 181 servers
by using multiple network paths 40 REPORT profile keyword 89 alternate 18
example 2 141 Reporting 18 alternate/parallel 16
by using multiple servers 40 restore Session
by using multiple sessions 39 BRRESTORE 132 glossary definition 181
CPU power 36, 37 redirected 57, 58 sessions
Dedicated backbone network 36 simulating 75 multiple 16
disk layout 36 troubleshooting 132 parallel 16
general considerations 35 restore/recovery 167, 172 SESSIONS profile keyword 90
I/O paths 36 BRRESTORE 172 setting Tivoli Storage Manager passwords
LAN-free backup 36 full recovery 174 manually 43
Network bandwidth 36 loss of several data/tablespace setting up Tivoli Storage Manager 143
options for 16 files 174 setup
settings for the Tivoli Storage one tablespace 172 understanding for
Manager 178 recovery of control files 174 troubleshooting 123
size of database 36 recovery of redo log files 174 simulating
size of database files 36 SAPDBA 167 backup and restore 75
tuning 38 retention using COMPR_INFO 85
volume manager 36 glossary definition 181 using USE_AT 92
with alternate/parallel paths and RETRY 83 simultaneous backup sessions 163
servers 137 RL compression 17 software compression vs. hardware
performance problems 163 RL_COMPRESSION profile keyword 41, compression
policy 90 UNIX or Linux 148
definition 145 RMAN 51 Windows 149
policy domain and incremental backup 51 SORT_FILE profile keyword 91
glossary definition 181 backup/restore simulation 78 sorting
policy set interaction with DP for mySAP 4 files 16
glossary definition 181 on UNIX or Linux 51 specifying management classes 17
profile keywords Hints 52 storage device setup
syntax 83 on Windows 53 Tivoli Storage Manager server 144
profiles troubleshooting 128 storage pool
backup of 7 glossary definition 181
backup, file directories, UNIX 8 storage pool definitions
backup, file directories, Windows 8
example of Tivoli Storage Manager for
S Tivoli Storage Manager server 145
storage pool volumes
sample DP for mySAP profile
UNIX or Linux 159 choosing volumes for backups 163
UNIX or Linux 92
Tivoli Storage Manager example for strategy
Windows 96
Windows 160 planning a backup strategy 5
SAP (backup) scheduler 9
Programmed Operator system copy
SAP BACKINT interface
glossary definition 181 heterogeneous 79
ProLE 42 homogeneous 79
saparch directory 166
SAPDBA 13
protocol
database backup 169
backup of 7
backup, file directories, UNIX 8
database recovery 172 T
glossary definition 181 tablespace
backup, file directories, Windows 8
protocols 7 backup 169
tablespace backup 167 glossary definition 181
scheduled batch backup locking 17
R Windows example 156 restore 172
recovery 172 scheduling tape drives
full recovery 174 automatic backups 9 backup sessions with limited tape
one tablespace 172 backup jobs 153, 156 drives 164
Recovery Manager (RMAN) 51 function of Tivoli Storage Manager 9 using hardware compression
glossary definition 181 UNIX or Linux examples 153 with 148, 149
redo logs 168 Windows examples 156 TCP_ADDRESS profile keyword 91
backing up 6 Scratch volume TCPWAIT 83
backup of 7 glossary definition 181 terminating the backup job 138
deleting promptly 166
Tivoli Storage Manager upgrading DP for mySAP 23
adjusting to DP for mySAP 144 USE_AT profile keyword 92
backup scheduler 10 user authorization for Administration
client software compression 149 Assistant 67
configuration file customization 178 util_file_online 17, 29, 170, 175
data compression 41 glossary definition 182
glossary definition 181 utility
incremental backup function 8 File Manager 55
management classes 17
node name 24
passwords 43
V
validate
profile example for UNIX or
Linux 159
policy set 146
profile example for Windows 160
verifying the DP for mySAP
scheduling function 9
installation 29
server name 24
verifying the installation of the
setup 143
Administration Assistant 65
Tivoli Storage Manager API
verifying the TSM API installation 30
volume
Tivoli Storage Manager client
configuration 147
configuration on UNIX or Linux 147
configuration on Windows 148
software compression 148 W
Tivoli Storage Manager passwords Web browser
authentication off 43 prerequisite for Administration
automatic generation 44 Assistant 62
configuration matrix to set Windows, backup scheduler 9
keywords 150, 151
manual generation 43
Tivoli Storage Manager server
configuration 143
configuration, prerequisites 144
management classes 145
node definition 146
performance considerations 143
policy definition 145
storage device setup 144
storage pool definition 145
TRACE profile keyword 91
TRACEFILE profile keyword 92
TRACEMAX 83
TRACEMAX profile keyword 92
tracing 19
troubleshooting 123
BACKINT 126
backup function 132
delete function 133
inquire function 133
installation 123
restore function 132
RMAN 128
setup 123
Troubleshooting
using RMAN on Windows 53
tuning 38
U
uninstalling DP for mySAP 32
uninstalling DP for mySAP.com
from UNIX and Linux 32
from Windows 33
UNIX crontab, backup scheduler 9
upgrading
DP for mySAP 31
Index 187
Readers’ Comments — We’d Like to Hear from You
IBM Tivoli Storage Manager for Enterprise Resource Planning (5608–APR) V.5.3.
Publication No. SC33-6340-05
Overall, how satisfied are you with the information in this book?
Very Satisfied Satisfied Neutral Dissatisfied Very

Dissatisfied
Overall satisfaction h h h h h
How satisfied are you that the information in this book is:
Very Satisfied Satisfied Neutral Dissatisfied Very

Dissatisfied
Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h
Please tell us how we can improve this book:
Thank you for your responses. May we contact you? h Yes h No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.
Name Address
Company or Organization
Phone No.
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
SC33-6340-05 Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines Corporation

Attn. Dept. ECJ - BP/003D
6300 Diagonal Highway
Boulder, CO 80301-9151
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
SC33-6340-05 Along Line

Program Number: 5608–APR
Printed in USA
SC33-6340-05

Null

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Null

Uploaded by

Copyright:

Available Formats

IBM Tivoli Storage Manager for Enterprise Resource

Planning (5608–APR) V.5.3.

Data Protection for mySAP

Data Protection for mySAP

Sixth Edition (December 2004)

FAX (Germany): 07031 16 3619

Internet Web page: http://www.ibm.com/software/tivoli

Part 1. Data Protection Basics . . . . 1 Part 2. Installing and Using . . . . . 21

Chapter 1. Concepts of Data Protection Chapter 4. Installing or Upgrading Data

© Copyright IBM Corp. 1995, 2003 iii

© Copyright IBM Corp. 1995, 2003 vii

© Copyright IBM Corp. 1995, 2003 ix

Such information may be available, subject to appropriate terms and conditions,

Trademarks and Service Marks

© Copyright IBM Corp. 1995, 2003 xi

Oracle is a registered trademark of Oracle Corporation.

| Linux® is a trademark of Linus Torvalds in the U.S., other countries, or both.

Naming Conventions used in this Documentation

How to Read This Book

Where to Find More Information

© Copyright IBM Corp. 1995, 2003 xiii

© Copyright IBM Corp. 1995, 2003 1

Oracle Backup/Restore and Data Protection for mySAP

DP for mySAP and BACKINT

Figure 1. DP for mySAP with SAPDBA using the BACKINT Interface

A backup run will proceed as follows (see circled numbers):

© Copyright IBM Corp. 1995, 2003 3

DP for mySAP and RMAN

Figure 2. DP for mySAP with SAPDBA using the RMAN Interface

A backup run will proceed as follows (see circled numbers):

To be prepared for recoveries from a severe disaster, the procedures described

Planning a Backup Strategy for the Operating System

Planning a Backup Strategy for Your Oracle Database

© Copyright IBM Corp. 1995, 2003 5

Files belonging to a specific tablespace (data files) are backed up by BRBACKUP.

The control file is saved by BRBACKUP whenever a tablespace backup occurs.

Planning a Backup Strategy for Backup Protocols and Profiles

The second part of a BRBACKUP or BRARCHIVE is responsible for backing up the

Chapter 2. Developing a Backup Strategy 7

In the case of a recovery scenario after a disaster, it may be time consuming to

You can find the files in the following directories:

/oracle/<SID>/sapreorg (SAPDBA and structure logs)

<drive>:\oracle\<SID>\sapreorg (SAPDBA and structure logs)

Planning a Backup Strategy for mySAP System Data

Sample files can be found in your DP for mySAP installation package.

Implementing the Strategy by Scheduling Automated Backup Runs

| UNIX or Linux crontab / Windows Scheduler

Chapter 2. Developing a Backup Strategy 9

Tivoli Storage Manager Scheduler

Information on how to define Tivoli Storage Manager schedules can be found in

IBM Tivoli Workload Scheduler

Sample Backup Strategy for Daily Backup Processing

Figure 4. Production Backup Example

Chapter 2. Developing a Backup Strategy 11

Figure 5. Scope of Data Protection for mySAP

© Copyright IBM Corp. 1995, 2003 13

Figure 6. Integration of Data Protection for mySAP with SAP

Storing Data on a TSM Server

Chapter 3. Introducing Data Protection for mySAP 15

Performance Options of Data Protection for mySAP

Parallel (Multiple) Sessions

Example: With MULTIPLEXING set to 5 and MAXSESSIONS set to 3 you would