Tivoli Data Protection for R/3 Installation & User s Guide

Transcription

1 Tivoli Data Protection for R/3 Installation & User s Guide Version3Release2

2

3 Tivoli Data Protection for R/3 Installation & User s Guide Version3Release2

4 Note! Before using this information and the product it supports, be sure to read the general information under Notices on page xiii. Third Edition (June 2001) This edition applies to Tivoli Data Protection for R/3 Version 3 Release 2, 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 Schoenaicher Str Boeblingen Germany FAX (Germany): FAX (other countries): (+49) Internet [email protected] Internet Web page: Make sure to include the following in your comment or note: Title and order number of this book 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, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures... Tables... ix xi Notices... xiii Trademarks and Service Marks... xiv Preface... xv Who Should Read This Book... xv Where to Find More Information... xv Contents of the Tivoli Data Protection for R/3 Package... xv Supported Platforms... xv Platform Differences.... xvi Chapter 1. Introducing Tivoli Data Protection for R/ Architecture and Properties of Tivoli Data Protection for R/ The Tivoli Data Protection for R/3 Profile... 5 The Tivoli Data Protection for R/3 Configuration File... 6 Parallel Backup and Restore... 6 Multiple Management Classes... 7 Multiple Redo Log Copies... 7 Individual Tablespace Locking Backup by Version... 8 Alternate/Parallel Backup Paths Alternate/Parallel Backup Servers Incremental Backup Manual Sorting Tivoli Data Protection for R/3 User s Guide iii

6 Frontend/Backend Processing Reporting Tracing Message Logging Improving Performance Chapter 2. Tivoli Storage Manager Setup Tivoli Storage Manager Configuration of Tivoli Storage Manager Server General Prerequisites Storage Device Setup Storage Pool Definition Policy Definition Node Definition Configuration of Tivoli Storage Manager Client General Tivoli Storage Manager Clients on UNIX Systems Tivoli Storage Manager Clients on Windows NT Systems Chapter 3. Setting Up Tivoli Data Protection for R/3 31 Prerequisites SAP R/3 Database Utilities Tivoli Storage Manager Client Installation on AIX CD-ROM Based Installation Directory Based Installation Installation on Compaq Tru64 UNIX Installation on HP-UX iv Version 3 Release 2

7 Installation on Red Hat Linux Installation on Solaris Installation on Windows NT or Windows Customizing Tivoli Data Protection for R/3 and SAP Backup Profile Verifying the Installation Chapter 4. Using Tivoli Data Protection for R/3 to Back Up and Restore Files and Databases General Backup Function Inquire Function Restore Function Tivoli Data Protection for R/3 File Manager SAP R/3 Backup and Recovery Using Tivoli Data Protection for R/3 62 Chapter 5. Backup Strategy and Backup Automation 77 Planning a Backup Strategy for the Operating System Planning a Backup Strategy for Your Oracle Database Planning a Backup Strategy for Backup Protocols and Profiles Planning a Backup Strategy for SAP R/3 System Data Backup Automation SAP R/3 Scheduler Tivoli Storage Manager Schedule UNIX crontab / Windows NT Scheduler Example of a Sequence of Daily Backup Runs Chapter 6. Considerations for Optimizing Backup/Restore Performance General Tivoli Data Protection for R/3 User s Guide v

8 The SAP R/3 Database Server TheNetwork Adaptation of the Network The Backup Server Adaptation of Tivoli Storage Manager Adaptation of Tivoli Data Protection for R/ Parallelism Compression Multiplexing BUFFSIZE Steps for Setting Up Your Environment Chapter 7. Administration Assistant for Tivoli Data Protection for R/ General Prerequisites Installation Installation of the Administration Assistant Server Installation of the Administration Assistant Slave Server Verification of the Installation Authorization of Administration Assistant Users Use of the Administration Assistant Chapter 8. SAP R/3 System Cloning General SAP R/3 System Cloning Example Appendix A. Tivoli Data Protection for R/3 Messages 127 Tivoli Data Protection for R/3 Messages vi Version 3 Release 2

9 Tivoli Data Protection for R/3 File Manager Error Messages Appendix B. Using Tivoli Data Protection for R/3 with RMAN RMAN Setup on UNIX Systems RMAN Setup on Windows NT Systems Appendix C. Migration from Tivoli Data Protection for R/3 Version 2.7 to Version Steps for Migration from Tivoli Data Protection for R/3 Version 2.7 to Version Restore/Recovery of a Backup Made with Tivoli Data Protection for R/3 Version 2.7 (Fallback): Appendix D. Password Handling Configuration Matrix (UNIX) Configuration Matrix (Windows NT) Appendix E. Alternate/Parallel Backup Paths and Backup Servers Parameter Settings - SERVER Statement EXAMPLE 1: Use of Alternate/Parallel Paths for Increased Availability EXAMPLE 2: Use of Alternate/Parallel Paths for Increased Performance EXAMPLE 3: Use of Alternate/Parallel Servers for Disaster Recovery Appendix F. The Tivoli Data Protection for R/3 Profile Keyword Reference Sample Tivoli Data Protection for R/3 Profile for UNIX Tivoli Data Protection for R/3 User s Guide vii

10 Appendix G. Sample Tivoli Storage Manager Profiles (UNIX) Client User Options File Sample (dsm.opt) Client System Options File Sample (dsm.sys) Include/Exclude List Sample Appendix H. Sample Tivoli Storage Manager Profiles (Windows NT) Client User Options File Sample (dsm.opt) Client Options Files Sample (<server>.opt) Include/Exclude List Sample Appendix I. Elements of Backup Schedules (UNIX) 199 Crontab File Sample Full Offline Backup Shell Script Sample Save and Delete Redo Logs Shell Script Sample Appendix J. Elements of Backup Schedule (Windows NT) Schedule Batch Sample Full Offline Backup Batch File Sample Save and Delete Redo Logs Batch File Sample Appendix K. Tips and Hints for BRARCHIVE Hints for BRARCHIVE Version 3.1G or Higher Examples Using MAX_SESSIONS and REDOLOG_COPIES Glossary Index viii Version 3 Release 2

11 Figures 1. Overview of Tivoli Data Protection for R/ File Manager Result of an Inquiry Procedure File Manager Result of an Inquiry Procedure Showing File Names Backup Scenarios Within an SAP R/3 Oracle Environment Backup Automation SAP R/3 DBA Planning Calendar Backup Automation Actions Available for Scheduling Production Backup Example Data Throughput Compression and Multiplexing Example of an SAP R/3 Landscape Administration Assistant Server Setup Specify Ports Administration Assistant Server Setup Host Name Administration Assistant Server Setup Destination Directory Administration Assistant Slave Server Setup Select Option Administration Assistant Slave Server Setup Customize Slave Server Administration Assistant Slave Server Setup Specify Directories Starting Administration Assistant with Netscape Administration Assistant Start Screen Tivoli Data Protection for R/3 User s Guide ix

12 x Version 3 Release 2

13 Tables 1. SAP Backup Profile Parameter Combinations Password Handling Methods Tuning of Network Settings Tuning of SP Switch Buffer Pools Tuning Tivoli Storage Manager Configuration File Attributes File Extensions for Shared Libraries Password Handling for UNIX Password Handling for Windows NT SERVER Statement and Appropriate Profile and Option File Settings. 169 Tivoli Data Protection for R/3 User s Guide xi

14 xii Version 3 Release 2

15 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 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: Tivoli Data Protection for R/3 User s Guide xiii

16 IBM Deutschland Informationssysteme GmbH Department 0215 Pascalstr 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: ADSTAR AIX IBM RS/6000 SP Tivoli 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. 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. xiv Version 3 Release 2

17 Preface Who Should Read This Book This manual is intended for system programmers and administrators who are responsible for implementing a backup solution in the SAP R/3 environment using the Tivoli Storage Manager. It explains the procedures needed to install and customize Tivoli Data Protection for R/3, the interface between SAP R/3 and the Tivoli Storage Manager. The reader should be familiar with SAP R/3 and Oracle documentation. Where to Find More Information For more information about Tivoli Data Protection for R/3, please refer to the Enterprise Solution Development Internet home page at Contents of the Tivoli Data Protection for R/3 Package The Tivoli Data Protection for R/3 package includes this manual and machine readable material on a CD-ROM. See the README file for: A table of contents of the package Up-to-date news Supported Platforms The following platforms are supported: AIX 4.3 HP-UX 11.0 Red Hat Linux 6.1 Solaris 7 Compaq Tru64 UNIX Windows NT (Intel) 4.0 Windows 2000 Tivoli Data Protection for R/3 User s Guide xv

18 Note Unless otherwise stated, references in this publication to UNIX also apply to Linux and references to Windows NT also apply to Windows Platform Differences There are only small differences between the UNIX and Windows NT versions of Tivoli Data Protection for R/3. One of these differences is that UNIX uses the path separator / compared with \ for Windows and that the drive letter is specified for Windows NT. Non trivial differences between the UNIX and Windows NT versions of Tivoli Data Protection for R/3 will be mentioned explicitly. xvi Version 3 Release 2

19 1 Introducing Tivoli Data Protection for R/3 1. Introducing Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 is an intelligent client/server program to manage backing up and restoring SAP R/3 Oracle databases using the Tivoli Storage Manager (see Tivoli Storage Manager Setup on page 17). This chapter gives you an overview and description about the architecture and properties of Tivoli Data Protection for R/3. Architecture and Properties of Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 lets you manage backup storage and processing independently of normal SAP R/3 operations. Tivoli Data Protection for R/3 and Tivoli Storage Manager provide reliable, high performance, repeatable backup and restore processes that let system administrators manage large volumes of data more efficiently. Tivoli Data Protection for R/3 allows system administrators to follow SAP procedures and use the integrated SAP database utilities for backup and restore. These utilities are SAPDBA, BRBACKUP, BRARCHIVE, and BRRESTORE. Other SAP files, for example executables, are backed up using Tivoli Storage Manager standard techniques for file backup and restore such as incremental backup, file filtering, and point-in-time recovery. Tivoli Data Protection for R/3 User s Guide 1

20 Tivoli Data Protection for R/3 supports two different backup/restore scenarios as seen in Figure 1: backup/restore of files (data files, control files, redo logs, profiles) and backup/restore of data blocks. Figure 1. Overview of Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 consists of three components: BACKINT v executable v interface between SAP database utilities and backup library for backup/restore of files v reads/writes database objects (files) from/to disk v receives input parameter from SAP database utilities (e.g., list of database objects to be handled) and routes them to Prole 2 Version 3 Release 2

21 v reads/transfers data from/to the Tivoli Storage Manager API client Prole v permanently running background process v controls backup/restore operations v v v reads and interprets parameters that are specified in the profile reads/writes internal parameters (e.g., Tivoli Storage Manager password) from/to the configuration file connects and sends backup/restore performance data to the Administration Assistant server. 1. Introducing Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 3

22 Backup library libtdp_r3 v shared library v reads/transfers data blocks from/to the Oracle MM API v reads/transfers data from/to the Tivoli Storage Manager API client Tivoli Data Protection for R/3 provides two possibilities for backing up or restoring data to or from the Tivoli Storage Manager. These are: Backup or restore of files Backup or restore of data blocks In the case of a file backup, the communication between the SAP database utilities and Tivoli Data Protection for R/3 will be handled by the SAP BACKINT interface. The entry point for this communication is the BACKINT executable. BACKINT hands over all necessary parameters received from the respective SAP database utility (BRBACKUP, BRARCHIVE, or BRRESTORE) to the background process Prole. This process controls the running backup operation being done by the backup client. The backup client reads the appropriate files from disk and sends them to one or more (of several) Tivoli Storage Manager servers using the Tivoli Data Protection for R/3 API client. In the case of a backup of data blocks (e.g., incremental backup) BRBACKUP calls the Oracle Recovery Manager (RMAN) and starts an Oracle server process. This process reads the data (data blocks) to be backed up from the Oracle database and transfers it to the external Tivoli Data Protection for R/3 backup library libtdp_r3 using the Oracle Media Management API (MM API). In a similar manner as described above, the backup client reads the data blocks and sends them to one or more (of several) Tivoli Data Protection for R/3 servers using the Tivoli Data Protection for R/3 API client. Tivoli Data Protection for R/3 optimizes the data throughput for backup and restore in several ways to minimize downtime and the impact on normal system operation: 4 Version 3 Release 2

23 It sorts the database objects in order to balance the load on the resources used for backup. For restore operations, Tivoli Data Protection for R/3 maintains the same sequence for efficient tape transfer. It is able to handle multiple backup/restore sessions. Each session reads data from and writes data to storage devices in parallel with (and independently of) each other. One session can be established per backup storage device. It utilizes multiple communication paths to Tivoli Storage Manager servers to eliminate network-induced bottlenecks. 1. Introducing Tivoli Data Protection for R/3 Note When Tivoli Data Protection for R/3 is called by one of the SAP database utilities SAPDBA, BRBACKUP, BRARCHIVE, or BRRESTORE to perform a backup or a restore, it always uses the Tivoli Storage Manager API archive and retrieve functions. Tivoli Data Protection for R/3 does not use the Tivoli Storage Manager API backup and restore functions. Tivoli Data Protection for R/3 always performs a backup, regardless of whether files are open or closed. The calling routine (for example, BRBACKUP) is responsible for informing the database controlling routine about which files are to be backed up. This is done using an alter tablespace begin backup. The backup of both the open database files and the redo logs results in a complete backup. The Tivoli Data Protection for R/3 Profile You can customize the way Tivoli Data Protection for R/3 operates with keywords and parameters in a profile that is analyzed by Tivoli Data Protection for R/3 Prole before any Tivoli Storage Manager subcommands are processed. By customizing this profile, you can adapt Tivoli Data Protection for R/3 to your environment s specific needs. Tivoli Data Protection for R/3 User s Guide 5

24 You must modify the profile, as Tivoli Data Protection for R/3 only reads this file (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). The Tivoli Data Protection for R/3 Configuration File Parameters that Tivoli Data Protection for R/3 modifies are stored in a separate binary configuration file for use in later sessions. As well as other information, this file contains the Tivoli Storage Manager passwords in an encrypted form. Be aware that Tivoli Data Protection for R/3 might not be able to run if you change this file. Parallel Backup and Restore Tivoli Data Protection for R/3 backs up and restores Oracle database objects that you specify using the SAP database utilities. The SAP database utilities BRBACKUP, BRARCHIVE, and BRRESTORE pass the database objects (e.g., data files or offline redo logs) as a temporary list of objects to Tivoli Data Protection for R/3. Tivoli Data Protection for R/3 receives control with the parameters that are specified in its profile, reads the temporary file list, and starts multiple sessions. During backup or restore operations, the SAP database utilities generate protocols about every performed action. All messages generated by Tivoli Data Protection for R/3 are also located in these protocols. The profile keyword MAX_SESSIONS specifies the maximum number of parallel sessions Tivoli Data Protection for R/3 will establish. 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. Tivoli Data Protection for R/3 optimizes the data transfer with regard to the physical location of the Oracle objects. Files stored on different volumes are backed up in parallel. 6 Version 3 Release 2

25 Note You should specify as many parallel sessions as there are physical storage devices available at the Tivoli Storage Manager server. Multiple Management Classes The Tivoli Storage Manager server manages data by using management classes. For more information, refer to the Administrator s Guide for Tivoli Storage Manager for a detailed description of Tivoli Storage Manager concepts, including management classes. 1. Introducing Tivoli Data Protection for R/3 In order to take full advantage of Tivoli Data Protection for R/3 s parallel backup and restore capabilities, you should specify one management class for each physical backup device (tape drive). Tivoli Data Protection for R/3 distinguishes between BRBACKUP and BRARCHIVE and uses different management classes for objects that are saved with each utility. Use the profile keywords BRBACKUPMGTCLASS and BRARCHIVEMGTCLASS to specify these management classes. With this feature, Tivoli Data Protection for R/3 can use more than one storage library device at a time. Multiple Redo Log Copies To improve availability and disaster recovery capability, it is recommended that you store multiple copies of the same Oracle redo log on different physical Tivoli Storage Manager volumes during a BRARCHIVE run. If you set the keyword REDOLOG_COPIES to 2, Tivoli Data Protection for R/3 stores two copies of each redo log. You can use this option only if you have defined more than one archive management class (specified with the keyword BRARCHIVEMGTCLASS). Tivoli Data Protection for R/3 User s Guide 7

26 For more detailed information about creating and using REDOLOG_COPIES, see Tips and Hints for BRARCHIVE on page 207. Individual Tablespace Locking To minimize the amount of archived redo logs during online backup operations, Tivoli Data Protection for R/3 can notify the SAP database utility BRBACKUP for which tablespaces it is going to back up files. BRBACKUP locks only those tablespaces. The other tablespaces are available for database transactions. After the files are backed up, the tablespaces are released again and a new cycle starts. Note This mode (util_file_online) is selected with a parameter in the SAPDBA setup (see Using Tivoli Data Protection for R/3 to Back Up and Restore Files and Databases on page 55) or it can be set permanently within the SAP backup profiles (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). Backup by Version Tivoli Data Protection for R/3 has to wait until the requested tablespaces are in begin backup mode. There will be a time delay after the negotiation between BRBACKUP and Tivoli Data Protection for R/3 until the tablespaces are actually prepared for backup and Tivoli Data Protection for R/3 can start the backup process. This function lets you keep a specified number of backups. 8 Version 3 Release 2

27 Keep in Mind The expiration period for your backups in Tivoli Storage Manager must be long enough so that it does not conflict with this feature in Tivoli Data Protection for R/3. Each database backup version consists of a tablespace and the associated redo log backups. Every time a full backup completes successfully, the version count is incremented by 1 and stored in the Tivoli Data Protection for R/3 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 remains. 1. Introducing Tivoli Data Protection for R/3 Notes 1. Backup versioning only works with SAP R/3 3.0C or higher. Older levels of SAPDBA do not pass the necessary control information to Tivoli Data Protection for R/3. Note that backup versioning occurs only in the case of full backups. 2. Partial backups get the same version number as the last successful full backup. When Tivoli Data Protection for R/3 deletes an old full backup, all partial backups with the same version number are also deleted. Tivoli Data Protection for R/3 User s Guide 9

28 CAUTION Tivoli Storage Manager uses the value of the parameter RETVER specified when you define a copy group (see Policy Definition on page 23) to give files an expiration date. If you use Tivoli Data Protection for R/3 versioning, you need to bypass this expiration function. If you use the Tivoli Storage Manager expiration function, you need to turn off Tivoli Data Protection for R/3 versioning. Use only one of these methods to control how long you keep backups. If you use Tivoli Data Protection for R/3 versioning, set the Tivoli Storage Manager parameter RETVER=9999 so that the files are not considered expired and deleted by Tivoli Storage Manager. If you use Tivoli Storage Manager expiration, de-activate Tivoli Data Protection for R/3 versioning by setting MAX_VERSIONS=0. Alternate/Parallel Backup Paths Tivoli Data Protection for R/3 lets you define alternate parallel backup paths. Alternate backup paths improve the availability of the backup/restore process, reduce network-induced bottlenecks, and increase backup/restore performance. In order to use this option, the Tivoli Storage Manager server must be accessible under more than one network address. When you set up this option, Tivoli Data Protection for R/3 uses the configured communication paths for data transfer to the Tivoli Storage Manager server. These paths can be used simultaneously to increase data throughput or to ensure that the backup operation can continue when one or more paths are down. You can specify a number of parallel sessions for each path to adjust to different network speeds and to distribute the load over the network. 10 Version 3 Release 2

29 For each communication path (for example, a Tivoli Storage Manager server network address), you define a set of additional communication parameters (see Alternate/Parallel Backup Paths and Backup Servers on page 167). This client option data is collected under a logical server name that you can choose freely. Under UNIX, it is possible to store all client option data in a single client system option file that is called dsm.sys. Under Windows NT, 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 NT, you need an additional client user option file, dsm.opt. All option files must reside in the same directory. 1. Introducing Tivoli Data Protection for R/3 You use the profile to tell Tivoli Data Protection for R/3 about the communication paths to be used in the SERVER statement. Under the keyword SERVER, specify the logical Tivoli Storage Manager server name. This name establishes the connection between the corresponding sections of the Tivoli Storage Manager client option files and the Tivoli Data Protection for R/3 profile. See Alternate/Parallel Backup Paths and Backup Servers on page 167 for a description of the SERVER statement. This section also contains profile examples of how to use alternate backup paths. Alternate/Parallel Backup Servers You can specify alternate backup servers to increase performance or for disaster recovery purposes. For disaster recovery, the backup data is routed to other Tivoli Storage Manager servers. This function is similar to alternate backup paths, except that now the keyword SERVER refers to physically different Tivoli Storage Manager servers. The backup data is distributed over the configured set of Tivoli Storage Manager servers, however, Tivoli Data Protection for R/3 keeps track of all backups regardless of which server they are stored on. Each server can be accessed again using alternate backup paths. Tivoli Data Protection for R/3 User s Guide 11

30 The USE_AT keyword lets you route backups to specific servers at defined times. You can select the day of the week that any path should be activated. For profile examples of how to use alternate backup servers, see the respective sections in Alternate/Parallel Backup Paths and Backup Servers on page 167. Incremental Backup Manual Sorting SAP R/3 release 4.5A and later permits incremental backups of Oracle databases using Oracle s Recovery Manager (RMAN). An incremental backup saves only those blocks within the database, which have been changed since the last full backup. Incremental backups reduce the total amount of data to be backed up. Depending on the system environment, this may result in decreased backup times. It may lead to a reduced network load and to a reduced need of backup system capacity. Furthermore, this could be of special advantage for large databases which have only a few changes on a daily basis. Tivoli Data Protection for R/3 now supports incremental backups of Oracle databases. To do this, appropriate customizing steps have to be carried out (see Using Tivoli Data Protection for R/3 with RMAN on page 151). You can find additional information about incremental backup strategies in an SAP R/3 environment in your SAP online documentation. Tivoli Data Protection for R/3 allows reading the files to be backed up in an order you specify. This can increase the backup performance, especially on disk subsystems such as ESS or EMC, because it prevents concurrent reading of files which reside on logical volumes of the same physical disks. 12 Version 3 Release 2

31 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 1. Introducing Tivoli Data Protection for R/3 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. The manual sorting can be enabled using the Tivoli Data Protection for R/3 profile keyword SORT_FILE which expects the name of the previously created sortfile as a parameter. Frontend/Backend Processing Reporting Tivoli Data Protection for R/3 provides frontend and backend processing capabilities. With this feature, a program or command can be called before or after Tivoli Data Protection for R/3 runs. Specify the program or command with the profile keywords FRONTEND and BACKEND. The frontend program is called before a backup or restore operation starts. The backend program is called after a backup or restore operation has ended. For statistical purposes, Tivoli Data Protection for R/3 provides information about the number of bytes that are transferred to or from the server and the effective throughput. In addition, Tivoli Data Protection for R/3 calculates an estimated end time and reports which file is currently being processed. Tivoli Data Protection for R/3 User s Guide 13

32 Specify the keyword REPORT with the parameter YES to enable this feature. Tracing Tivoli Data Protection for R/3 can write trace information into a file to help analyze problems. You should contact your Tivoli Data Protection for R/3 support before you use this function. Message Logging When message logging is used with Tivoli Storage Manager Version 3.7 or higher, Tivoli Data Protection for R/3 can send log messages to a configurable Tivoli Storage Manager server. Possible messages include backup and restore progress information and error messages. Use a LOG_SERVER keyword in the profile to enable this feature. Furthermore, Tivoli Data Protection for R/3 is able to send log messages to a network management program via SNMP traps. Such messages include backup and restore progress information and error messages. Use an SNMPTRAP keyword in the profile to enable this feature. Improving Performance Newer releases of Tivoli Data Protection for R/3 are multi-threaded. This design makes use of enlarged internal buffers. Disk I/O to a particular block of these buffers can be carried out independently of network I/O to a different block. On SMP machines these independent parts of the code (threads) run concurrently on different processors. In contrast, older single-threaded releases run only on one processor at a time regardless of how many processors are available. Further detailed descriptions on these subjects can be found in Considerations for Optimizing Backup/Restore Performance on page 91 The multi-threaded Tivoli Data Protection for R/3 version contains the following additional improvements: fast null block compression in Tivoli Data Protection for R/3 14 Version 3 Release 2

33 multiplexing user-adjustable block size for reading from disk and sending data to Tivoli Storage Manager 1. Introducing Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 15

34 16 Version 3 Release 2

35 2 Tivoli Storage Manager Setup This chapter gives an overview of the Storage Manager and explains the procedures for setting it up for working with Tivoli Data Protection for R/3 in an SAP R/3 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 R/3 environment will be explained. Note The following steps and procedures are only samples. The actual values in your specific environment may be different. 2. Tivoli Storage Manager Setup Tivoli Storage Manager Tivoli Storage Manager is the core product of the Tivoli Storage Management product set. It provides a solution for distributed data and storage management in an enterprise network environment. It is the next-generation product based on ADSM (ADSTAR Distributed Storage Manager). Tivoli Storage Manager currently protects and manages data on more than 30 operating platforms, covering mobile, desktop and server systems distributed over the entire world. It is integrated with hundreds of storage devices as well as with LAN, WAN, and emerging SAN infrastructure. The base function provided by Tivoli Storage Manager and its complementary products includes: Tivoli Data Protection for R/3 User s Guide 17

36 Data Protection 1. Operational Backup and Restoration of Data: The backup process creates a copy of the data which protects against operational loss or destruction of file or application information. You can define how often the data is to be backed up (frequency) and how many copies (versions) are to be kept. The restore process places the backup copy of the data into a customer-designated system or workstation 2. Disaster Recovery: This involves all activities for organizing, managing and automating the recovery process after a major loss of IT infrastructure and data across the enterprise. This includes processes for moving data offsite into a secure vault location, for rebuilding IT infrastructure, and for enabling data to be successfully reloaded in an acceptable time frame. Storage Resource Management 1. Vital Record Retention Archive and Retrieval: The archival process creates a copy of a file or a set of files representing an end point of a process for long term storage. Files can remain on the local storage media or can be deleted. The customer controls how long (retention period) an archive copy is to be retained. The retrieval process locates the copies within the archival storage and places them back into a customer-designated system or workstation. 2. Hierarchical Space Management: This process provides automatic and transparent movement of operational data from the user system disk space to a central storage repository. If the user accesses this data, it is dynamically and transparently restored to the client storage. These functions are network based, which means that they are available to the whole network environment. All the functions can be automated to run in a 24x7 lights-out environment. Administration costs are minimized by centralization of all the management of Tivoli Storage Manager components. The Tivoli Storage Manager supports a wide variety of platforms for mobile, small and large systems, and delivers, together with complementary products, many 18 Version 3 Release 2

37 data management functions such as data protection for file and application data, record retention, space management, and disaster recovery. You can find additional information about the Tivoli Storage Manager in the respective manuals such as the Administrator s Reference for Tivoli Storage Manager or the Administrator s Guide for Tivoli Storage Manager. Furthermore, Tivoli Storage Manager publications are available on the Tivoli Storage Manager home page at the following address: Configuration of 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 Before starting the installation, there are important issues about performance that should be considered. The choice of which server to install, network topology, and usage of RS/6000 SP can improve performance within the system landscape, avoiding performance bottlenecks. 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 R/3 system landscape, a single Tivoli Storage Manager server is sufficient. If you plan to use the Storage Manager to back up/restore other 2. Tivoli Storage Manager Setup Tivoli Data Protection for R/3 User s Guide 19

38 clients as well, you should consider either installing the server software on a large machine or using several Tivoli Storage Manager servers. Network topology. Network topologies such as Ethernet, Token Ring, FDDI, Fast Ethernet, and ATM all work 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. 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: Installation of the Tivoli Storage Manager Server 3.7 or higher code with the latest PTFs. Recovery log volume has been allocated and initialized. Recovery log mirror volume has been allocated and initialized. Database volume has been allocated and initialized. Database mirror volume has been allocated and initialized. Additional labeled volumes for the backup and archive storage pools have been allocated and initialized (disks, tapes or combinations). Licenses have been registered. The Tivoli Storage Manager server has been started. For information on installing Tivoli Storage Manager, see the Tivoli Storage Manager Quick Start manual. 20 Version 3 Release 2

39 Note The latest code fixes for Tivoli Storage Manager can be found at: ftp://index.storsys.ibm.com/tivoli-storagemanagement/maintenance 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: 1. Query defined library q library 2. Tivoli Storage Manager Setup 2. Query defined drives q drive 3. Query defined device class q devclass Storage Pool Definition A storage pool is a named collection of storage volumes that are associated with one device class. Each storage pool represents a collection of volumes that are the same media type. The storage pool setup defines the storage hierarchy for the appropriate environment. In an SAP R/3 environment, there are different kinds of data to be backed up. These are: SAP R/3 system data Tivoli Data Protection for R/3 User s Guide 21

40 SAP R/3 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 R/3 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 22 Version 3 Release 2

41 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 estimate. Policy Definition Tivoli Storage Manager policies will be used to specify how files are backed up, archived, migrated from client node storage, and managed in server storage. The 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. 2. Tivoli Storage Manager Setup 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 offline redo 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 Tivoli Data Protection for R/3 User s Guide 23

42 Note If you are planning to use this Tivoli Storage Manager server with multiple SAP R/3 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=9999 define copygroup sap_c21 p_c21 mlog1 type=archive destination=sap_log1 retver=9999 define copygroup sap_c21 p_c21 mlog2 type=archive destination=sap_log2 retver=9999 Tivoli Data Protection for R/3 uses its own version control mechanism for managing SAP R/3 database backups. To do this, Tivoli Data Protection for R/3 backs up all data only to management classes for which an archive copy group has been defined (parameter type set to archive). 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). 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 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. 24 Version 3 Release 2

43 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 upgraded from a previous version of ADSM to Tivoli Storage Manager and you are using more than one tape drive, you should pay special attention to the new node parameter maxnummp. It defines the maximum number of mount points that one node is able to do. The default value is 1. One node can only use more than one mount point if the parameter is correctly set for the desired number of mount points. Configuration of Tivoli Storage Manager Client After the server configuration, you have to configure the clients that will use the Tivoli Storage Manager server. These include the backup/archive client and the Application Programming Interface (API) client. 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 Tivoli Data Protection for R/3. General 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 at all nodes that will interface with Tivoli Storage Manager server. 2. Tivoli Storage Manager Setup In the context of an SAP R/3 system landscape, this means that the Tivoli Storage Manager backup/archive client must be installed on every machine scheduled for a file system backup, for example SAP R/3 application servers and the SAP R/3 database server. The Tivoli Storage Manager API client needs only to be installed on the SAP Tivoli Data Protection for R/3 User s Guide 25

44 R/3 database server machine to enable backup/restore operations of the SAP R/3 database in combination with the backup interface program Tivoli Data Protection for R/3. Note When the Tivoli Storage Manager API client is installed on UNIX 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 Systems on page 151. The setup for the Tivoli Storage Manager client is effected in a UNIX environment by changing the files dsm.opt and dsm.sys and in a Windows NT environment by changing the file <server_a>.opt (server_a is a logical server name, see Tivoli Storage Manager Clients on Windows NT Systems on page 28). After that procedure the include/exclude file has to 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 can be found in Include/Exclude List Sample on page 192 and for Windows NT in Include/Exclude List Sample on page 197. Tivoli Storage Manager Clients on UNIX Systems This section 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 R/3 environment. Follow these steps: 1. Install the Tivoli Storage Manager client software on the SAP R/3 database server machine. 2. Edit the client system options file dsm.sys and set the following values, as appropriate to your installation: 26 Version 3 Release 2

45 Servername server_a TCPPort 1500 TCPServeraddress xxx.xxx.xxx.xxx InclExcl /usr/tivoli/tsm/client/ba/bin/inclexcl.list Compression OFF 3. Specify TCPServeraddress 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 Oracle 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! 2. Tivoli Storage Manager Setup 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 (default) NUMBERFormat 1 (default) REPLACE ON TAPEPROMPT NO TIMEFORMAT 1 (default) Tivoli Data Protection for R/3 User s Guide 27

46 Tivoli Storage Manager Clients on Windows NT Systems This section serves as a quick guide for configuring the Tivoli Storage Manager. It presents a typical list of actions that the Tivoli Storage Manager installer or administrator must perform to prepare Tivoli Storage Manager for operation in an SAP R/3 environment. Follow these steps: 1. Install the Tivoli Storage Manager client software on the SAP R/3 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: Servername server_a TCPPort 1500 TCPServeraddress xxx.xxx.xxx.xxx InclExcl c:\tivoli\tsm\baclient\inclexcl.list Compression OFF In addition, the environment variables DSM_CONFIG and DSMI_CONFIG must point to the corresponding client options file, e.g., c:\tivoli\tsm\baclient\server_a.opt. 3. Specify TCPServeraddress 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 Oracle 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). 28 Version 3 Release 2

47 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. 2. Tivoli Storage Manager Setup Tivoli Data Protection for R/3 User s Guide 29

48 30 Version 3 Release 2

49 3 Setting Up Tivoli Data Protection for R/3 The Tivoli Data Protection for R/3 code is typically delivered on CD-ROMs. You have the option of downloading the latest available version from the home page of the Enterprise Solution Development department: Prerequisites Note If you have been using an older version of Tivoli Data Protection for R/3 in your environment and you want to use Tivoli Data Protection for R/3 version 3.2 instead, see Migration from Tivoli Data Protection for R/3 Version 2.7 to Version 3.2 on page 157 for details of the necessary migration guidelines. There are certain common prerequisites for all UNIX platforms and for Windows NT. The following lists the setup steps which must be carried out initially. SAP R/3 3.0D or higher based on an Oracle database 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 31

50 Tivoli Storage Manager 3.7 or 4.1 server, Tivoli Storage Manager 3.7 or 4.1 client and API. In the respective SAP R/3 release notes it is possible to find out which Tivoli Storage Manager levels can be used. UNIX or Windows NT operating system at the level supported by SAP R/3 and the Tivoli Storage Manager client. The following explains in more detail the prerequisites for SAP R/3 and Tivoli Storage Manager. SAP R/3 Database Utilities Tivoli Data Protection for R/3 can be used for SAP R/3 systems with Oracle databases employing a standard UNIX file system, a Windows NT file system or raw logical volumes. The following SAPDBA database utilities at these minimum levels must be installed on the SAP R/3 database server: v BRBACKUP 3.0D v BRARCHIVE 3.0D v BRCONNECT 3.0D v BRRESTORE 3.0D You should consult SAP support via the Online Service System (OSS) for information concerning which functions are compatible with the appropriate SAP R/3 release. The appropriate modules can be downloaded from the SAP server. Information about this can be found in OSS note A SAPDBA minimum level of 3.0F is required if the SAP R/3 release 3.0D or higher is used in combination with Oracle on raw devices. Tivoli Storage Manager Client The installation and all necessary customizing steps for the Tivoli Storage Manager Clients (Backup/Archive Client for filesystem backups, API Client for interface programs) have to be carried out on the SAP R/3 database server machine (see Configuration of Tivoli Storage Manager Client on page 25). The Tivoli Storage Manager 3.7 or 4.1 client version has to be installed. The client software will be shipped with the server software. 32 Version 3 Release 2

51 Installation on AIX TCP/IP or shared memory (UNIX systems) have to be ready for communication between the Tivoli Storage Manager Client, ADSM Server, or Tivoli Storage Manager Server. After you have ensured that all prerequisites have been met, the installation process can commence. This includes installing the software, customizing the profile, and verifying the installation with a backup and restore run. For backup tests, the SAP database utilities SAPDBA, BRBACKUP, and BRARCHIVE should be used. For restore or recovery it is recommended to use only SAPDBA. The following steps guide you through the Tivoli Data Protection for R/3 installation. To install and customize Tivoli Data Protection for R/3, you must log on as the root user. Note The installation of Tivoli Data Protection for R/3 must be done on the SAP R/3 database server machine. The setup process can be carried out either with the graphical System Management Interface Tool (smit) or with the character based System Management Interface Tool version (smitty). There are two setup scenarios, which are slightly different. The first is a CD-ROM based Tivoli Data Protection for R/3 setup and the second is a setup from an installation directory on a hard disk. CD-ROM Based Installation To install Tivoli Data Protection for R/3 on an AIX machine, you must carry out the following steps: 1. Log in as the root user on the SAP R/3 database server machine. 2. Ensure that the Tivoli Data Protection for R/3 CD-ROM is inserted in the proper CD-ROM drive. 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 33

52 3. Invoke the AIX System Management Interface Tool smitty install_package 4. Select an appropriate value for the INPUT device where the install package resides. This is /dev/cd0 for a CD-ROM based setup and /usr/sys/inst.images for an installation directory based setup. 5. Select the tivoli install package from the package list. 6. To install the Tivoli Data Protection for R/3 for AIX, select the software from the tivoli package. Install and Update Software by Package Name (includes devices and printers) Type or select a value for the entry field. Select Software to install Move cursor to desired item and press Esc+7. Use arrow keys to scroll. ONE OR MORE items can be selected. Press Enter AFTER making all selections. # # # Key: = Already installed # + = No license password required # # tivoli.tdp_r3.aix Tivoli Data Protection for R/3 for AIX F1=Help F2=Refresh F3=Cancel F1 F7=Select F8=Image F10=Exit F5 Enter=Do /=Find n=find Next F9 7. Now, all necessary installation settings have been done. You may view the installation process by setting the PREVIEW only? item to yes (move the cursor to the item and press the Tab key). To start or preview the installation process, press Enter twice. 8. After finishing this procedure, check the status of the setup process. You can do this by checking the status of the Command statement in the upper left of the output screen. 34 Version 3 Release 2

53 COMMAND STATUS Command: OK stdout: yes stderr: no Before command completion, additional instructions may appear below. [TOP] installp -acgnpqqwx -d /usr/sys/inst.images -f File 2>&1 File: tivoli.tdp_r3.aix *************************************************************************** installp PREVIEW: installation will not actually occur. *************************************************************************** Pre-installation Verification [MORE...35] F1=Help F2=Refresh F3=Cancel F6=Command F8=Image F9=Shell F10=Exit /=Find n=find Next Command: OK - everything was successfully done; press the F10 key to close the System Management Interface Tool and go to item 9. Command: failed - an error occurred during the installation process. In this case, check the COMMAND STATUS output screen carefully and correct the problems that occurred. After correction of the error(s), press the F3 key and repeat the installation procedure beginning at item The Tivoli Data Protection for R/3 software will be installed into the /usr/tivoli/tsm/tdp_r3 directory of the SAP R/3 database server machine. Check the README file for a brief description of all the installed files. For proper functionality of Tivoli Data Protection for R/3 a post-installation procedure must be started. During this procedure, a shell script setup.sh will be processed and the following tasks will be performed: Renaming Tivoli Data Protection for R/3 profile (init<sid>.utl) and configuration file (init<sid>.bki) and copying them to the/oracle/sid/dbs directory. This applies 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 35

54 only to new Tivoli Data Protection for R/3 installations, otherwise this step will be skipped. Creating a softlink to the backint executable in the SAP R/3 executables path. Creating an entry in /etc/inittab for the Tivoli Data Protection for R/3 background process called Prole (with parameter for the Administration Assistant server connection). Creating an entry in /etc/services needed for internal Tivoli Data Protection for R/3 communication. The following steps describe the post-installation procedure: 1. Invoke, as the root user, the shell script setup.sh /usr/tivoli/tsm/tdp_r3/setup.sh 2. Enter the system ID (SID) for the SAP R/3 system to be backed up. 3. Enter the path for the SAP R/3 executables. If appropriate, you can use the suggested default by pressing Enter. 4. Enter the path for the Tivoli Data Protection for R/3 profile and configuration file (init<sid>.utl, init<sid>.bki). If appropriate, you can use the suggested default by pressing Enter. 5. You will now be asked if you have already installed a Tivoli Data Protection for R/3 Administration Assistant server on that machine. no: Press n to finish the installation yes: Press y to go on. You will now be asked to enter the hostname and the IP address of the machine, where the Administration Assistant server is installed. Next, you must enter the port used for communication between the Tivoli Data Protection for R/3 background process Prole and the Administration Assistant server. If appropriate, you can use the suggested default by pressing Enter. 36 Version 3 Release 2

55 At this point, the installation procedure of Tivoli Data Protection for R/3 is finished. To ensure that the installation is correct and to enable Tivoli Data Protection for R/3 to run, the following two steps remain to be done: Customizing the profile (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). Verifying the installation (see Verifying the Installation on page 53). Directory Based Installation The installation procedure is very similar to the installation from the CD-ROM. The main difference is the source of the Tivoli Data Protection for R/3 package. In this scenario the package was typically downloaded from a Web page. To prepare for a subsequent installation, the following steps have to be carried out: 1. Log in as the root user on the SAP R/3 database server machine 2. Copy the Tivoli Data Protection package to your installation directory, for example the default installation directory /usr/sys/inst.images cp tivoli.tdp_r3.pkg /usr/sys/inst.images 3. Use the inutoc command to create/update the.toc file (contains necessary install information for smit/smitty). inutoc /usr/sys/inst.images 4. Now you can follow the setup description given in the section CD-ROM Based Installation on page 33, beginning at item 3 Installation on Compaq Tru64 UNIX The following steps guide you through the Tivoli Data Protection for R/3 installation. To install and customize Tivoli Data Protection for R/3, you must log on as the root user. 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 37

56 Note The installation of Tivoli Data Protection for R/3 must be done on the SAP R/3 database server machine. To install Tivoli Data Protection for R/3 on a Compaq Tru64 UNIX machine, you must do the following: 1. Log in as the root user on the SAP R/3 database server machine. 2. Ensure that the Tivoli Data Protection for R/3 CD-ROM is inserted in the proper CD-ROM drive. 3. Mount the CD-ROM. 4. Invoke the following command: /usr/sbin/setld -l <path to install image> tdp_r3<version number> Replace <path to install image> with the absolute path name where the install image resides and replace <version number> with the version number of your install image. 5. The Tivoli Data Protection for R/3 software will be installed into the /usr/tivoli/tsm/tdp_r3 directory of the SAP R/3 database server machine. Check the file README for a brief description of all the installed files. For proper functionality of Tivoli Data Protection for R/3 a post-installation procedure must be started. During this procedure, a shell script setup.sh will be processed and the following tasks will be performed: Renaming Tivoli Data Protection for R/3 profile (init<sid>.utl) and configuration file (init<sid>.bki) and copying them to the/oracle/sid/dbs directory. This applies only to new Tivoli Data Protection for R/3 installations, otherwise this step will be skipped. Creating a softlink to the backint executable in the SAP R/3 executables path. 38 Version 3 Release 2

57 Creating an entry in /etc/inittab for the Tivoli Data Protection for R/3 background process called Prole (with parameter for the Administration Assistant server connection). Creating an entry in /etc/services needed for internal Tivoli Data Protection for R/3 communication. The following steps describe the post-installation procedure: 1. Invoke as the root user the post-installation shell script setup.sh /usr/tivoli/tsm/tdp_r3/setup.sh 2. Enter the system ID (SID) for the SAP R/3 system to be backed up. 3. Enter the path for the SAP R/3 executables. If appropriate, you can use the suggested default by pressing Enter. 4. Enter the path for the Tivoli Data Protection for R/3 profile and configuration file (init<sid>.utl, init<sid>.bki). If appropriate, you can use the suggested default by pressing Enter. 5. You will be asked if you have already installed a Tivoli Data Protection for R/3 Administration Assistant server on that machine. no: Press n to finish the installation. yes: Press y to go on. First, you will be asked to enter the hostname and the IP address of the machine where the Administration Assistant server was installed. Next, you must enter the port which will be used for communication between the Tivoli Data Protection for R/3 background process Prole and the Administration Assistant server. If appropriate, you can use the suggested default by pressing Enter. 3. Setting Up Tivoli Data Protection for R/3 At this point, the installation procedure of Tivoli Data Protection for R/3 is finished. To ensure that the installation is correct and to enable Tivoli Data Protection for R/3 to run, the following two steps remain to be done: Customizing the profile (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). Tivoli Data Protection for R/3 User s Guide 39

58 Verifying the installation (see Verifying the Installation on page 53 ). Installation on HP-UX The following steps guide you through the Tivoli Data Protection for R/3 installation. To install and customize Tivoli Data Protection for R/3, you must log on as the root user. Note The installation of Tivoli Data Protection for R/3 must be done on the SAP R/3 database server machine. To install Tivoli Data Protection for R/3 on an HP-UX machine, you must do the following: 1. Log in as the root user on the SAP R/3 database server machine. 2. Ensure that the Tivoli Data Protection for R/3 CD-ROM is inserted in the proper CD-ROM drive. 3. Mount the CD-ROM. 4. Invoke the following command: /usr/sbin/swinstall -x mount_all_filesystems=false -s <path to inst. image> TDP_R3 Replace <path to inst. image> with the absolute path name where the install image resides and the name of the image i.e. tivoli.tdp_r3.depot 5. The Tivoli Data Protection for R/3 software will be installed into the /opt/tivoli/tsm/tdp_r3 directory of the SAP R/3 database server machine. Check the file README for a brief description of all the installed files. For proper functionality of Tivoli Data Protection for R/3 a post-installation procedure must be started. During this procedure, a shell script setup.sh will be processed and the following tasks will be performed: 40 Version 3 Release 2

59 Renaming Tivoli Data Protection for R/3 profile (init<sid>.utl) and configuration file (init<sid>.bki) and copying them to the/oracle/sid/dbs directory. This applies only to new Tivoli Data Protection for R/3 installations, otherwise this step will be skipped. Creating a softlink to the backint executable in the SAP R/3 executables path. Creating an entry in /etc/inittab for the Tivoli Data Protection for R/3 background process called Prole (with parameter for the Administration Assistant server connection). Creating an entry in /etc/services needed for internal Tivoli Data Protection for R/3 communication. The following steps describe the post-installation procedure: 1. Invoke as the root user the post-installation shell script setup.sh /opt/tivoli/tsm/tdp_r3/setup.sh 2. Enter the system ID (SID) for the SAP R/3 system to be backed up. 3. Enter the path for the SAP R/3 executables. If appropriate, you can use the suggested default by pressing Enter. 4. Enter the path for the Tivoli Data Protection for R/3 profile and configuration file (init<sid>.utl, init<sid>.bki). If appropriate, you can use the suggested default by pressing Enter. 5. You will be asked if you have already installed a Tivoli Data Protection for R/3 Administration Assistant server on that machine. no: Press n to finish the installation. yes: Press y to go on. First, you will be asked to enter the hostname and the IP address of the machine, where the Administration Assistant server was installed. Next, you must enter the port which will be used for communication between the Tivoli Data Protection for R/3 background process Prole and the Administration Assistant server. If appropriate, you can use the suggested default by pressing Enter. 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 41

60 At this point, the installation procedure of Tivoli Data Protection for R/3 is finished. To ensure that the installation is correct and to enable Tivoli Data Protection for R/3 to run, the following two steps remain to be done: Customizing the profile (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). Verifying the installation (see Verifying the Installation on page 53). Installation on Red Hat Linux The following steps guide you through the Tivoli Data Protection for R/3 installation. To install and customize Tivoli Data Protection for R/3, you must log on as the root user. Note The installation of Tivoli Data Protection for R/3 must be done on the R/3 database server machine. To install Tivoli Data Protection for R/3 on a Red Hat Linux machine, you must do the following: 1. Log in as the root user on the R/3 database server machine. 2. Ensure that the Tivoli Data Protection for R/3 CD-ROM is inserted in the proper CD-ROM drive. 3. Mount the CD-ROM. 4. Invoke the following command: /bin/rpm/rpm -i <path to install image>tdp_r3<version number> Replace <path to install image> with the absolute path name where the install image resides and replace <version number> with the version number of your install image. 42 Version 3 Release 2

61 5. The Tivoli Data Protection for R/3 software will be installed into the /opt/tivoli/tsm/tdp_r3 directory of the R/3 database server machine. Check the file README for a brief description of all the installed files. For proper functioning of Tivoli Data Protection for R/3, a post-installation procedure must be started. During this procedure, a shell script setup.sh will be processed and the following tasks will be performed: Renaming Tivoli Data Protection for R/3 profile (init<sid>.utl) and configuration file (init<sid>.bki) and copying them to the /oracle/sid/dbs directory. This applies only to new Tivoli Data Protection for R/3 installations; otherwise this step will be skipped. Creating a softlink to the backint executable in the R/3 executables path. Creating an entry in /etc/inittab for the Tivoli Data Protection for R/3 background process Prole (with parameter for the Administration Assistant server connection). Creating an entry in /etc/services needed for internal Tivoli Data Protection for R/3 communication. The following steps describe the post-installation procedure: 1. Invoke as the root user the post-installation shell script setup.sh /opt/tivoli/tsm/tdp_r3/setup.sh 2. Enter the system ID (SID) for the R/3 system to be backed up. 3. Enter the path for the R/3 executables. If appropriate, you can use the suggested default by pressing Enter. 4. Enter the path for the Tivoli Data Protection for R/3 profile and configuration file (init<sid>.utl,init<sid>.bki). If appropriate, you can use the suggested default by pressing Enter. 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 43

62 5. You will be asked if you have already installed a Tivoli Data Protection for R/3 Administration Assistant server on this machine. no: Press n to finish the installation. yes: Press y to go on. First, you will be asked to enter the hostname and the IP address of the machine where the Administration Assistant server was installed. Next, you must enter the port which will be used for communication between the Tivoli Data Protection for R/3 background process Prole and the Administration Assistant server. If appropriate, you can use the suggested default by pressing Enter. At this point, the installation procedure for Tivoli Data Protection for R/3 is finished. To ensure that the installation is correct and to enable Tivoli Data Protection for R/3 to run, the following two steps remain to be done: Customizing the profile (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). Verifying the installation (see Verifying the Installation on page 53). Installation on Solaris The following steps guide you through the Tivoli Data Protection for R/3 installation. To install and customize Tivoli Data Protection for R/3, you must log on as the root user. Note The installation of Tivoli Data Protection for R/3 must be done on the SAP R/3 database server machine. To install Tivoli Data Protection for R/3 on a Solaris machine, you must do the following: 44 Version 3 Release 2

63 1. Log in as the root user on the SAP R/3 database server machine. 2. Ensure that the Tivoli Data Protection for R/3 CD-ROM is inserted in the proper CD-ROM drive. 3. Mount the CD-ROM. 4. Invoke the following command: /usr/sbin/pkgadd -d <path to install image> tdp_r3.pkg Replace <path to install image> with the absolute path name, where the install image resides. 5. The Tivoli Data Protection for R/3 software will be installed into the /opt/tivoli/tsm/tdp_r3 directory of the SAP R/3 database server machine. Check the file README for a brief description of all the installed files. For proper functionality of Tivoli Data Protection for R/3 a post-installation procedure must be started. During this procedure, a shell script setup.sh will be processed and the following tasks will be performed: Renaming Tivoli Data Protection for R/3 profile (init<sid>.utl) and configuration file (init<sid>.bki) and copying them to the/oracle/sid/dbs directory. This applies only to new Tivoli Data Protection for R/3 installations, otherwise this step will be skipped. Creating a softlink to the backint executable in the SAP R/3 executables path. Creating an entry in /etc/inittab for the Tivoli Data Protection for R/3 background process called Prole (with parameter for the Administration Assistant server connection). Creating an entry in /etc/services needed for internal Tivoli Data Protection for R/3 communication. 3. Setting Up Tivoli Data Protection for R/3 The following steps describe the post-installation procedure: 1. Invoke as the root user the post-installation shell script setup.sh Tivoli Data Protection for R/3 User s Guide 45

64 /opt/tivoli/tsm/tdp_r3/setup.sh 2. Enter the system ID (SID) for the SAP R/3 system to be backed up. 3. Enter the path for the SAP R/3 executables. If appropriate, you can use the suggested default by pressing Enter. 4. Enter the path for the Tivoli Data Protection for R/3 profile and configuration file (init<sid>.utl, init<sid>.bki). If appropriate, you can use the suggested default by pressing Enter. 5. You will be asked if you have already installed a Tivoli Data Protection for R/3 Administration Assistant server on that machine. no: Press n to finish the installation. yes: Press y to go on. First, you will be asked to enter the hostname and the IP address of the machine, where the Administration Assistant server was installed. Next, you must enter the port which will be used for communication between the Tivoli Data Protection for R/3 background processprole and the Administration Assistant server. If appropriate, you can use the suggested default by pressing Enter. At this point, the installation procedure of Tivoli Data Protection for R/3 is finished. To ensure that the installation is correct and to enable Tivoli Data Protection for R/3 to run, the following two steps remain to be done: Customizing the profile (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). Verifying the installation (see Verifying the Installation on page 53). Installation on Windows NT or Windows 2000 The following steps guide you through the Tivoli Data Protection for R/3 installation. To install and customize Tivoli Data Protection for R/3, you must log on as a user with administrator rights. 46 Version 3 Release 2

65 Notes 1. The installation of Tivoli Data Protection for R/3 must be done on the SAP R/3 database server machine. 2. Unless otherwise stated, references to Windows NT also apply to Windows The Tivoli Data Protection for R/3 setup procedure is a guided installation. For a proper setup read all of the guidelines during the setup carefully! The following installation steps are necessary for the installation of Tivoli Data Protection for R/3 on a Windows NT machine: 1. Log in as administrator user on the SAP R/3 database server machine. 2. Ensure that the Tivoli Data Protection for R/3 CD-ROM is inserted in the proper CD-ROM drive. 3. Use the Windows NT Explorer to go to the Tivoli Data Protection for R/3 installation directory. 4. To start the setup procedure, a program called setup.exe is provided in the Tivoli Data Protection for R/3 installation directory. Invoke the setup.exe program with a double mouse click. 5. Enter the default hard disk drive letter to be used for the temporary installation steps. 6. Select your SAP R/3 release level. 7. Select the type of installation (standard is recommended). 8. Select a destination folder/directory for all files of the Tivoli Data Protection for R/3 installation package. 9. Select the destination folder/directory for the Tivoli Data Protection for R/3 executables (backint.exe, backfm.exe). 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 47

66 10. Select the destination folder/directory for the Tivoli Data Protection for R/3 profile (initsid.utl) and configuration file (initsid.bki). 11. Select the destination folder/directory for the Tivoli Data Protection for R/3 Tivoli Storage Manager client option file dsm.opt. 12. The Tivoli Storage Manager API client needs the following environment variables to locate certain files: DSMI_CONFIG Path and name of the client option file for Tivoli Data Protection for R/3. DSMI_DIR Directory where the Tivoli Storage Manager messages file dscameng.txt resides. DSMI_LOG Directory where the Tivoli Storage Manager error log file dsierror.log is created Hence, it is necessary to set the Tivoli Storage Manager API client environment variables according to your system landscape. 13. To finish the Tivoli Data Protection for R/3 setup procedure click the Finish button. 14. You must include the location of the Tivoli Storage Manager API DLLs tsm32.dll and blkhook.dll in the system %PATH% environment variable. 15. If you want to use the Administration Assistant, you have to enter the Administration Assistant server name: prole -install <server_name> <server_port> At this point, the installation procedure of Tivoli Data Protection for R/3 is finished. To ensure that the installation is correct and to enable Tivoli Data Protection for R/3 to run, the following two steps remain to be done: 48 Version 3 Release 2

67 Customizing the profile (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile below). Verifying the installation (see Verifying the Installation on page 53). Customizing Tivoli Data Protection for R/3 and SAP Backup Profile In this section we will discuss customizing the Tivoli Data Protection for R/3 profile (init<sid>.utl) and the SAP Backup profile (init<sid>.sap). These profiles must be customized, because they are not initially suitable for working with Tivoli Data Protection for R/3. The Tivoli Data Protection for R/3 profile, for example, only exists as a sample showing what a typical profile could look like. A detailed description of all possible profile keywords can be found in The Tivoli Data Protection for R/3 Profile on page 175. The Tivoli Data Protection for R/3 profile has to be customized with some fundamental entries so that Tivoli Data Protection for R/3 will work in all cases (backup, restore, inquire, delete). Special customizing, however, such as to obtain enhanced performance, etc., will not be discussed here. For details on this, see Considerations for Optimizing Backup/Restore Performance on page 91. The profiles that must be customized can be found on UNIX systems in the path /oracle/<sid>/dbs and on Window NT systems in the path <drive>:\orant\database. A set of essential Tivoli Data Protection for R/3 profile entries (keyword with an appropriate parameter) must be set or changed. These are: BACKUPIDPREFIX Prefix of the Backup ID which will be used for communications with SAPDBA. Default is SAP. MAX_VERSIONS Defines the maximum number of database backup versions 3. Setting Up Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 User s Guide 49

68 to be kept in backup storage. Default is 0, meaning that Tivoli Data Protection for R/3 versioning is disabled MAX_SESSIONS Number of total parallel sessions which will be established by Tivoli Data Protection for R/3. This number should correspond with the number of simultaneously available tape drives specified for the Tivoli Storage Manager server. Default is 1. CONFIG_FILE Specifies the configuration file (init<sid>.bki) for Tivoli Data Protection for R/3. SERVER Specifies the Tivoli Storage Manager server used. This value must correspond to an entry in the dsm.sys file on UNIX systems. On Windows NT systems, Tivoli Data Protection for R/3 uses a separate Tivoli Storage Manager API client option file for each Tivoli Storage Manager server. Such a file must have the file name server.opt, where server stands for the name you gave the Tivoli Storage Manager server. SESSIONS Number of Tivoli Storage Manager sessions that can be started by Tivoli Data Protection for R/3 for the corresponding server. Default is 1. BRBACKUPMGTCLASS Specifies the Tivoli Storage Manager management class Tivoli Data Protection for R/3 uses when called from BRBACKUP. BRARCHIVEMGTCLASS Specifies the Tivoli Storage Manager management class Tivoli Data Protection for R/3 uses when called from BRARCHIVE. The configuration of the SAP Backup profile, which is part of the SAP R/3 installation, refers to three keywords within that file. These keywords are: 50 Version 3 Release 2

69 backup_dev_type Determines the backup medium that will be used (default is tape). backup_type Identifies the default type of the database backup. This parameter is only used by BRBACKUP (default is offline). util_par_file This parameter specifies where the parameter file, which is required for a backup with an external backup program, is located. Tivoli Data Protection for R/3 supports, for example, the following combinations of the keywords backup_dev_type and backup_type as 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 individual tablespace locking util_file_online online To carry out online backups with individual tablespace locking (see Individual Tablespace Locking on page 8) with the external backup program Tivoli Data Protection for R/3, the SAP Backup profile parameter must be set or changed as shown below: backup_type backup_dev_type util_par_file = online = util_file_online =?/dbs/[email protected] 3. Setting Up Tivoli Data Protection for R/3 The question mark is the official Oracle substitute symbol for the home directory of the database system, for example, /oracle/c21. Password Handling. Before testing to see whether the profiles have been configured correctly, the password handling has to be clarified (see Password Tivoli Data Protection for R/3 User s Guide 51

70 Handling on page 161). You can distinguish between manual password handling and automatic password handling. If you are using manual password handling you must provide the password needed for a client connection to Tivoli Storage Manager which was specified when the node ID was initially registered within Tivoli Storage Manager (see Node Definition on page 24). The password is requested initially and again each time it expires for this node within Tivoli Storage Manager. Normally, you will be prompted for the client password each time Tivoli Data Protection for R/3 starts a Tivoli Storage Manager session. To avoid this, the client password will be stored in encrypted form within the Tivoli Data Protection for R/3 configuration file (init<sid>.bki). This can be done with the following command. For UNIX systems: backint -p /oracle/sid/dbs/init<sid>.utl -f password For Windows NT systems: backint -p <drive>:\orant\database\init<sid>.utl -f password Tivoli Data Protection for R/3 prompts for all required passwords which were set for the appropriate Tivoli Storage Manager (this depends on how many Tivoli Storage Manager servers were declared in the Tivoli Data Protection for R/3 profile) and checks whether the passwords are valid. If a connection between Tivoli Data Protection for R/3 and Tivoli Storage Manager is to be established, Tivoli Data Protection for R/3 reads the password from the configuration file and uses it for registration on the Tivoli Storage Manager server. If you are using automatic password handling, Tivoli Storage Manager generates an encrypted password for the backup client machine during the first Tivoli Storage Manager connection of the backup/archive client and stores it locally on that machine. This generated password will now be used for authorizations of any Tivoli Storage Manager sessions to be established between the server and 52 Version 3 Release 2

71 this client. Furthermore, a new password will be generated automatically if the old password expires. Depending on the password handling method you are choosing, the following table gives an overview of the appropriate settings that have to be made on the Tivoli Storage Manager and Tivoli Data Protection for R/3 side. Table 2. Password Handling Methods Manual Password Handling Tivoli Storage Manager client options file settings Tivoli Data Protection for R/3 profile settings PASSWORDACCESS prompt PASSWORDREQUIRED yes Automatic Password Handling PASSWORDACCESS generate PASSWORDDIR <path> PASSWORDREQUIRED no On UNIX systems, the users <SID>adm and ora<sid> and on Windows NT systems, the users <SID>adm and sapservice<sid> must have read and write permission to the path specified in the PASSWORDDIR keyword in the Tivoli Storage Manager client options file. Verifying the Installation There is no verification procedure provided with Tivoli Data Protection for R/3. 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 (online database backup) brbackup -c -t offline (offline database backup) 3. Setting Up Tivoli Data Protection for R/3 It is also strongly recommended that you do a restore/recovery of the whole SAP R/3 database (using SAPDBA). A good method to prepare for this is to first run a complete offline backup using BRBACKUP. Tivoli Data Protection for R/3 User s Guide 53

72 Step by step scenarios for backup or restore/recovery procedures of an SAP R/3 Oracle database using Tivoli Data Protection for R/3 can be found in the IBM redbook SAP R/3 Data Management with Tivoli Storage Manager, SG Note IBM redbooks can be found at 54 Version 3 Release 2

73 4 Using Tivoli Data Protection for R/3 to Back Up and Restore Files and Databases 4. Backup and Restore General Tivoli Data Protection for R/3 provides a set of necessary functions to do backup/restore operations within an SAP R/3 Oracle database environment. Tivoli Data Protection for R/3 will be invoked with a set of appropriate parameters by the SAP R/3 database utilities (SAPDBA, BRBACKUP, BRARCHIVE, BRRESTORE) with one of the functions defined within the SAP BACKINT interface description. These are: backup inquire restore Also, a Tivoli Data Protection for R/3 delete function is available. The delete function is used as a part of the versioning control mechanism of Tivoli Data Protection for R/3 (see Backup by Version on page 8). The delete function is only called by Tivoli Data Protection for R/3 itself or from the user, not from the SAP R/3 database utilities. Furthermore, it is possible to use Tivoli Data Protection for R/3 to perform backup and restore operations directly from the command line. The command: Tivoli Data Protection for R/3 User s Guide 55

74 backint -? Backup Function displays a list of all possible Tivoli Data Protection for R/3 command line options. The backup function will be normally invoked by the SAP R/3 database utilities BRBACKUP and BRARCHIVE. These programs give Tivoli Data Protection for R/3 an input file (in the case of backup and inquire) containing the names and paths of the database files to be handled. However, it is possible to call Tivoli Data Protection for R/3 directly to back up individual files. See the following example. For UNIX systems: backint -p /oracle/sid/dbs/init<sid>.utl -f backup For Windows NT systems: backint -p <drive>:\orant\database\init<sid>.utl -f backup Note The Tivoli Data Protection for R/3 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. 56 Version 3 Release 2

75 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. Also, this function can be invoked manually from the command line as follows. For UNIX systems: 4. Backup and Restore backint -p /oracle/sid/dbs/init<sid>.utl -f inquire For Windows NT systems: backint -p <drive>:\orant\database\init<sid>.utl -f inquire Tivoli Data Protection for R/3 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 C The backup ID in this case is C (#BACKUP does not belong to the backup ID). The first six characters are the user defined prefix (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). The next 10 digits 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 C /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. Tivoli Data Protection for R/3 User s Guide 57

76 Restore Function The restore function will be normally started by the SAP R/3 database utility BRRESTORE. This program gives Tivoli Data Protection for R/3 an input filename. This file contains the backup ID and the corresponding file names including their paths. However, it is possible to call Tivoli Data Protection for R/3 directly to restore individual files. This function can be invoked from the command line as follows. For UNIX systems: backint -p /oracle/sid/dbs/init<sid>.utl -f restore For Windows NT systems: 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 never restore database files directly, because this could corrupt the SAP R/3 database. Tivoli Data Protection for R/3 File Manager The Tivoli Data Protection for R/3 File Manager is a utility that simplifies the Tivoli Data Protection for R/3 inquire, restore, and delete operations for the user. It can be seen as an add-on to Tivoli Data Protection for R/3. 58 Version 3 Release 2

77 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. 4. Backup and Restore The Tivoli Data Protection for R/3 File Manager uses the standard functions provided by Tivoli Data Protection for R/3 to perform all operations. The Tivoli Data Protection for R/3 File Manager user interface consists of a split character based window. All backup IDs found on all Tivoli Storage Manager servers which were configured within the Tivoli Data Protection for R/3 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 3 on page 61). The Tivoli Data Protection for R/3 File Manager has to be started with the path and name of the Tivoli Data Protection for R/3 profile (the user has to be a member of the dba group). See the following example. For UNIX systems: backfm -p /oracle/sid/dbs/init<sid>.utl For Windows NT systems: backfm -p <drive>:\orant\database\init<sid>.utl The Tivoli Data Protection for R/3 File Manager will now establish a connection to all Tivoli Storage Manager servers which were configured in the Tivoli Data Protection for R/3 profile. The next step is an automatic inquire operation for all backup IDs. The Tivoli Data Protection for R/3 User s Guide 59

78 following figure shows the display of a set of backup IDs located by the Tivoli Data Protection for R/3 File Manager after having finished an inquiry procedure. Figure 2. File Manager Result of an Inquiry Procedure If you mark the backup ID you are interested in and then press the Tab key to 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. 60 Version 3 Release 2

79 4. Backup and Restore Figure 3. File Manager Result of an Inquiry Procedure Showing File Names The following function keys are defined for performing restore or delete 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. Tivoli Data Protection for R/3 User s Guide 61

80 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, see Backup by Version on page 8). For files, the Tivoli Storage Manager expiration date and time is displayed. F8 - Delete Delete the selected backup ID and all corresponding files. This function is available only when the cursor is on top of a backup ID. F10 - Exit Exit from Tivoli Data Protection for R/3 File Manager ENTER - Mark/unmark file Mark or unmark the file below the cursor. To carry out restore or delete 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 or deleted. Single backup IDs can also be deleted, in which case the selected backup ID and its corresponding files will be removed from the Tivoli Storage Manager server. SAP R/3 Backup and Recovery Using Tivoli Data Protection for R/3 The following illustrates how a backup or restore/recovery scenario within an SAP R/3 environment using Tivoli Data Protection for R/3 works. These examples show only a general strategy. Your actual 62 Version 3 Release 2

81 backup/restore scenario may be different. Hence, when performing a real backup/restore consult your SAP online documentation to see how this should be done exactly. The first section describes two procedures, showing how a backup can be started: Full online/offline backup with BRBACKUP Tablespace backup with SAPDBA. Section two shows a restore of an SAP R/3 tablespace and a subsequent recovery of the SAP R/3 database with the help of SAPDBA. 4. Backup and Restore For the following examples, an SAP R/3 system is assumed to be installed on a UNIX 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 R/3 database utilities can store the backed up data on the Tivoli Storage Manager server with the help of Tivoli Data Protection for R/3. Online/Offline Backup with BRBACKUP BRBACKUP is a database utility provided by SAP to perform a backup function of the SAP R/3 Oracle database. You can use BRBACKUP to back up the following objects of an Oracle database: Data files Control files Online redo log files BRBACKUP can be invoked directly from the operating system command level, using the SAPDBA backup function or from the SAP R/3 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: Tivoli Data Protection for R/3 User s Guide 63

82 brbackup -help To start an online backup of the SAP R/3 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 SAP R/3 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 SAP R/3 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 SAP R/3 database instance again. If the earlier SAP R/3 database instance has been stopped, BRBACKUP can be started with the normal offline parameter. brbackup -c -t offline 64 Version 3 Release 2

83 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: Error messages - last letter of a message code is an E Warning messages - last letter of a message code is a W 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: ANS/ANR - ADSM or Tivoli Storage Manager messages BKI - Tivoli Data Protection for R/3 messages BR - BRARCHIVE, BRBACKUP or BRRESTORE messages ORA - Oracle database kernel messages RMAN - Oracle Recovery Manager messages After BRBACKUP has finished, it is recommended that you check the backup protocol for warnings and unexpected errors. The backup protocol 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. 4. Backup and Restore 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 an SAP R/3 Oracle database generally cannot be carried out from within the R/3 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 Tivoli Data Protection for R/3 User s Guide 65

84 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 an SAP R/3 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: ORACLE_SID : C21 ORACLE_HOME : /oracle/c21 DATABASE : open SAPR3 : 45B, 7 times connected a - Startup/Shutdown instance b - Instance information c - Tablespace administration d - Reorganization e - Export/import f - Archive mode g - Additional functions h - Backup database i - Backup offline redo logs j - Restore/Recovery k - DB check/verification l - Show/Cleanup m - User and Security 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: 66 Version 3 Release 2

85 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 j - Backup from disk backup k - Restart backup l - Make part. backups compl. yes 4. Backup and Restore S - Start BRBACKUP q - Return Please select ==> As already mentioned in Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49, the SAP Backup profile initc21.sap has to be correctly customized in view of: The backup type (online, offline) and The backup utility parameter file To check the backup utility parameter file (in case of Tivoli Data Protection for R/3 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: Tivoli Data Protection for R/3 User s Guide 67

86 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 ==> 68 Version 3 Release 2

87 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 Tivoli Data Protection for R/3 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: 4. Backup and Restore BR056I End of database backup: bdbhowho.pnf 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 SAP R/3 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: Check database Tivoli Data Protection for R/3 User s Guide 69

88 Find backup files Restore backup files Find archive files Restore archive files Recover database SAPDBA uses the program BRRESTORE for restoring the database. This program invokes Tivoli Data Protection for R/3 for restoring all the necessary tablespace files or archived redo log files from the appropriate Tivoli Storage Manager server. After the restore has been successfully carried out, the necessary recovery will be performed by SAPDBA. The following describes two possible recovery scenarios: The recovery of a single SAP R/3 tablespace and a complete (full) recovery of the SAP R/3 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 66 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: 70 Version 3 Release 2

89 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 4. Backup and Restore 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 SAP R/3 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 ==> Tivoli Data Protection for R/3 User s Guide 71

90 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 SAP R/3 database must be initiated, such as in the case of loss of several data files. This means that all necessary: data files redo log files 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 SAP R/3 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 70). 72 Version 3 Release 2

91 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 4. Backup and Restore 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). Tivoli Data Protection for R/3 User s Guide 73

92 Full Restore and Recovery DATABASE STATE : mounted RESTORE / RECOVER: disallowed (see status) A - Select a full online/offline backup b - Recover until c - Show status D - Restore and recover Current setting now q - Return Please select ==> A 1-bdbeejyv.aff ALL offline db_to_util_file 2-bdbejsiq.anf ALL online db_to_util_file_online 3-bdbfefgf.anf ALL online db_to_util_file_online 4-bdbfhuiv.anf ALL online db_to_util_file_online 5-bdbfroqz.anf ALL online db_to_util_file_online 6-bdbghtwj.anf ALL online db_to_util_file_online 7-bdbgljpc.anf ALL online db_to_util_file_online 8-bdbgqlxo.aff ALL offline db_to_util_file 9-bdbgwhhw.aff 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 Tivoli Data Protection for R/3. Ensure that the SAP Backup profile initc21.sap is properly customized (see also Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). 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 70. 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 74 Version 3 Release 2

93 redo log files will be restored anyway. Subsequently, the recovery of the database will be commenced. 4. Backup and Restore Tivoli Data Protection for R/3 User s Guide 75

94 76 Version 3 Release 2

95 5 Backup Strategy and Backup Automation This section tells you how to define an appropriate backup strategy for your SAP R/3 system. It is intended as a supplement to your SAP R/3, Oracle and Tivoli Storage Manager documentation. There are several requirements that your strategy must meet. The most important factors you need to consider include: The types of events you wish to protect your SAP R/3 system against How quickly you need to be able to return to normal operation after a failure The intervals and times of day during which backups can be performed The events and points in time you need to be able to recover, depending on the type of outage 5. Backup Strategy and Backup Automation Tivoli Data Protection for R/3 lets you back up SAP R/3 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 SAP R/3 database or the database offline redo logs. Hence, to protect your complete system, against failures affecting SAPDBA or other SAP R/3 system data, you should use standard Tivoli Data Protection for R/3 User s Guide 77

96 Tivoli Storage Manager commands or the Tivoli Storage Manager graphical user interface (GUI) to additionally backup this system data. To be prepared also for the recovery from a severe disaster (such as fire or water), the procedures described below must be embedded into 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: the installation of the operating system 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: user errors statement failures transaction failures media failures that could affect your Oracle database, save the following objects on a regular basis: Data files 78 Version 3 Release 2

97 Control files Online redo logs 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.) 5. Backup Strategy and Backup Automation 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 Tips and Hints for BRARCHIVE on page 207. 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 SAP R/3 system data Oracle system data Operating system data This data should be backed up with the incremental backup function of the Tivoli Storage Manager backup/archive client. Tivoli Data Protection for R/3 User s Guide 79

98 Figure 4 shows the various backup scenarios within an SAP R/3 database server machine. Figure 4. Backup Scenarios Within an SAP R/3 Oracle Environment The database itself is backed up with Tivoli Data Protection for R/3, 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: SAP R/3 data files database control files online redo log files offline redo log files 80 Version 3 Release 2

99 depending on the action started (see previous section). The second part of a BRBACKUP or BRARCHIVE is responsible for backing up the following profiles: init<sid>.dba (SAPDBA profile) init<sid>.ora (Oracle profile) init<sid>.sap (SAP backup profile) init<sid>.utl (Tivoli Data Protection for R/3 profile) and the protocol files back<sid>.log (BRBACKUP summary log) arch<sid>.log (BRARCHIVE summary log) detailed BRBACKUP/BRARCHIVE log reorg<sid>.log (main SAPDBA log) struct<sid>.log (structure log) These profiles and protocols are used by the SAP database utilities whenever backups or restore/recovery are required. 5. Backup Strategy and Backup Automation Unless you use an additional security measure, e.g., an additional file system backup, these profiles or protocol files can only be restored in combination with Tivoli Data Protection for R/3. For this purpose, you can, for example, use the Tivoli Data Protection for R/3 File Manager (see Tivoli Data Protection for R/3 File Manager on page 58). 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 Tivoli Data Protection for R/3 or the Tivoli Data Protection for R/3 File Manager within a reasonable time frame. 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: Tivoli Data Protection for R/3 User s Guide 81

100 UNIX /oracle/sid/sapreorg /oracle/sid/sapbackup /oracle/sid/saparch /oracle/sid/dbs (SAPDBA and structure logs) (BRBACKUP logs) (BRARCHIVE logs) (profiles) Windows NT <drive>:\oracle\sid\sapreorg <drive>:\oracle\sid\sapbackup <drive>:\oracle\sid\saparch <drive>:\orant\database (SAPDBA and structure logs) (BRBACKUP logs) (BRARCHIVE logs) (profiles) Planning a Backup Strategy for SAP R/3 System Data In addition to the backup operations performed with BRBACKUP and BRARCHIVE, you may want to protect your system against the loss of SAP R/3 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 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 Tivoli Data Protection for R/3. This would be all Oracle 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 can be found under Include/Exclude List Sample on page 192 and for Windows NT Include/Exclude List Sample on page Version 3 Release 2

101 The information saved with the BRBACKUP and BRARCHIVE utilities is usually located in the following file systems or directories: UNIX /oracle/sid/saparch/ /oracle/sid/sapdata1/ /oracle/sid/sapdata2/ /oracle/sid/sapdata3/ /oracle/sid/sapdata4/ /oracle/sid/sapdata5/ /oracle/sid/sapdata6/... /oracle/sid/origloga/ /oracle/sid/origlogb/ Windows NT <drive>:\oracle\sid\saparch\ <drive>:\oracle\sid\sapdata1\ <drive>:\oracle\sid\sapdata2\ <drive>:\oracle\sid\sapdata3\ <drive>:\oracle\sid\sapdata4\ <drive>:\oracle\sid\sapdata5\ <drive>:\oracle\sid\sapdata6\... <drive>:\oracle\sid\origloga\ <drive>:\oracle\sid\origlogb\ 5. Backup Strategy and Backup Automation Add these directories to your include/exclude list of your Tivoli Storage Manager backup/archive client. This will prevent you from saving the database data twice. Backup Automation 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. Tivoli Data Protection for R/3 User s Guide 83

102 There are three types of schedulers which can be used to setup a schedule: SAP R/3 scheduler (CCMS) Tivoli Storage Manager scheduler UNIX crontab / Windows NT scheduler The scope of schedule control of the Tivoli Storage Manager scheduler is at an enterprise level. On the other hand, the SAP R/3 scheduler or the UNIX crontab can only be used to set up schedules for the machines on which the SAP R/3 database is installed. The different schedulers will be explained by means of examples in the following sections. SAP R/3 Scheduler Within SAP R/3 the Computer Center Management System (CCMS) provides a scheduler as shown in Figure 5 on page 85 for database administration and backup planning. The scheduler can be started with the transaction code db13 in the SAPGUI command line or with the SAPGUI menu functions (Tools -> CCMS -> DB administration -> DBA scheduling). 84 Version 3 Release 2

103 5. Backup Strategy and Backup Automation Figure 5. Backup Automation SAP R/3 DBA Planning Calendar For every day, one or more actions (see Figure 6 on page 86) can be scheduled by double clicking a field of a calendar day shown in Figure 5 with the mouse pointer. Tivoli Data Protection for R/3 User s Guide 85

104 Figure 6. Backup Automation Actions Available for Scheduling Tivoli Storage Manager Schedule The Tivoli Storage Manager also provides functions for automating client operations by defining a new schedule or updating an existing schedule. Schedule definition work can be done quickly using the GUI based Tivoli Storage Manager Web administrative client. 86 Version 3 Release 2

105 When a schedule is defined, it will be assigned to a specific policy domain (more than one schedule for each policy domain can be defined). For this purpose, the SAP R/3 database client requires a schedule that can execute command files. The command files (for example shell scripts on UNIX) contain sequences of commands that are run at a scheduled start date and time. Information on how to define Tivoli Storage Manager schedules can be found in the Tivoli Storage Manager Administrator s Reference manual. UNIX crontab / Windows NT Scheduler Another possibility of backup automation is offered by the cron jobs for UNIX systems or schedule services for Windows NT. UNIX cron jobs can be scheduled with the so-called 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: 5. Backup Strategy and Backup Automation 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 Elements of Backup Schedules (UNIX) on page 199) from Monday through Friday at 11:30 p.m. which will use the SAP database utility BRBACKUP to save the SAP R/3 database. In this case, the entry in the crontab to start the script will be as follows: * * 1,2,3,4,5 /usr/bin/su - ora<sid> -c "/oracle/sid/sapscripts/backup.ksh" To start automated backup jobs on Windows NT systems, the schedule service must be running. You can start this service with the command: net start schedule Tivoli Data Protection for R/3 User s Guide 87

106 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 Schedule (Windows NT) on page 203). 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 Example of a Sequence of Daily Backup Runs The following figure illustrates the sequence of backup runs you should establish for a daily backup schedule. Figure 7. Production Backup Example This example of automated backup operations shows the following typical tasks Full database backup, e.g., offline or without application load, performed each night. 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. 88 Version 3 Release 2

107 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 to back up the SAP R/3 database (data files) directly to tape. Offline redo logs are migrated (within Tivoli Storage Manager) from disk to tape after the full database backup. SAP R/3 system files are backed up incrementally with the Tivoli Storage Manager backup-archive client. The last backup in the daily cycle is the backup of the Tivoli Storage Manager database. This should always be the case. 5. Backup Strategy and Backup Automation Tivoli Data Protection for R/3 User s Guide 89

108 90 Version 3 Release 2

109 6 Considerations for Optimizing Backup/Restore Performance Protecting against loss of data and minimizing downtime of the SAP R/3 system are the key requirements for defining a best-fit backup/restore process. The definition should start with the restore of the data base. During restore SAP R/3 users cannot perform their work, whereas backups can always be scheduled at times of low system utilization. Thus, restore downtime incurs costs several orders of magnitude higher than backup downtime. The backup process definition has also to follow the restore objectives. Minimizing downtime can be achieved by three measures: Deployment of a suitable method for backup/restore, e.g., full backup daily vs. full backup weekly, online vs. offline. Optimizing for maximum throughput of the data transfer during backup or restore. Offloading inactive data into an external archive to trim the size of the database to the data volume actually used. A companion product to Tivoli Data Protection for R/3 - IBM Content Manager CommonStore for SAP - is available from IBM. It 6. Optimizing Backup/Restore Tivoli Data Protection for R/3 User s Guide 91

110 connects Tivoli Storage Manager to the SAP R/3 ArchiveLink Interface covering the whole range of SAP R/3 archiving functions: inactive data (off-loading) printlists and outgoing documents incoming documents (scan, fax) General Backup/Restore processes involve basically three independent resources, see Figure 8. Figure 8. Data Throughput Client system (SAP R/3 database server) Network 92 Version 3 Release 2

111 Backup system (Tivoli Storage Manager (TSM) server) A continuous stream of data is generated between these components for the backup or restore of data and the weakest link in this chain determines the overall data rate. Before performance concepts are discussed in more detail, the following list describes some rules for designing an efficient backup/restore infrastructure: The weakest link is ultimately the SAP R/3 database server. To help alleviate this problem, parallelism can be deployed for network, backup server, and storage. A backup of data files directly to tape should be employed wherever possible, because it is the fastest method. A dedicated backup server allows sharing of storage resources and yields the most efficient resource utilization. The network between the SAP R/3 database server and backup server should provide sufficient bandwidth, e.g., a minimum of 100 Mb Ethernet. It should be implemented as a backbone separated from the user LAN. The SAP R/3 Database Server For a backup (and corresponding restore), an example of the processes performed on the SAP R/3 database server (client) is listed below: Read data from disk. Transfer data through I/O interface into the client CPU s main memory via operating system functions. Process data by Tivoli Data Protection for R/3. Send data to a network by adding communication protocol framing. Tivoli Data Protection for R/3 provides the following capabilities for optimizing the performance of the client in regard to data rates. Data Compression using a lightweight run-length algorithm. 6. Optimizing Backup/Restore Tivoli Data Protection for R/3 User s Guide 93

112 Blocks of binary nulls get compressed directly at the client with very little CPU overhead. The Tivoli Storage Manager client provides a more efficient compression but with more CPU overhead. File Multiplexing. To compensate for losses in data rate through compression and to load a storage device (usually a tape) to its maximum performance capacity, data can be read from multiple files and folded into one data stream, see Figure below. Figure 9. Compression and Multiplexing The following optimizes overall data throughput. Parallel sessions. Multiple datastreams are generated in parallel, one for each of the corresponding number of storage devices (usually tapes) on the backup server. 94 Version 3 Release 2

113 Note Each session requires a dedicated storage device. The Network File Sequencing. Automatic sorting of files dependent on size and location (on disk) to minimize parallel disk accesses with multiplexing and parallel sessions. The calculated sequence is an optimum for backup as well as for restore. For those configurations in which the file location cannot be determined automatically (intelligent disk subsystems), symbolic file locations can be entered manually to be included in the sorting process (see Manual Sorting on page 12). The network affects the data transport in two ways: The communication protocol adds some overhead which impacts the data rate, but as the database files making up the bulk of the data are usually very large, this overhead is relatively small. The network bandwidth limits the data throughput. Our experience shows that the effectively usable bandwidth is approximately half the theoretical bandwidth of the specific network. For high-speed networks such as Gigabit Ethernet, it is likely that the network adapters of the respective systems limit the effective data throughput rather than the network itself. 6. Optimizing Backup/Restore Tivoli Data Protection for R/3 provides the following capability for optimizing the performance of the network in regard to data throughput: Multiple Paths. Parallel sessions can be assigned to multiple network paths between SAP R/3 database and backup server (see also, Tivoli Data Protection for R/3 User s Guide 95

114 Alternate/Parallel Backup Paths on page 10). Thus, the overall network bandwidth usable for data transfer can be increased to the sum of the parallel paths. Adaptation of the Network The network on a UNIX machine can be configured with the no command. This command sets or displays current network attributes in the kernel. The command must be run again after each start-up or after the network has been reconfigured. Caution The no command does not perform range checking. It therefore accepts all values for the variables. If used incorrectly, the command can cause the system to become inoperable. The following table shows the appropriate network attributes with the recommended values. Table 3. Tuning of Network Settings Attributes Value Description rfc 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 Specifies the maximum buffer size allowed for a socket. The default is bytes. From the point of view of performance recommendations, the sb_max value should correspond to the TCPWindowsize setting within the Tivoli Storage Manager configuration file dsm.sys and should be twice the TCPWindowsize. To adapt these values, the following commands have to be invoked by the root user on the appropriate machine. 96 Version 3 Release 2

115 no -o rfc1323=1 no -o sb_max= Note These changes will be lost at system reboot. To make changes permanent, edit the /etc/rc.net file. If an SP switch is used, the following two values should be adapted as shown in the following table. Table 4. Tuning of SP Switch Buffer Pools Attributes Value Description rpoolsize The receive pool is a buffer pool for incoming data. The size for values is in bytes. spoolsize 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. The Backup Server Further detailed information can be found at The backup server receives the data from the network, removes the communication frames and prepares the data for writing onto backup storage media (usually tapes). Observations show that the CPU load on the backup server for a given data throughput is approximately 60% of that of the client. Therefore, the backup server is not the critical resource from a CPU power point of view. 6. Optimizing Backup/Restore Tivoli Data Protection for R/3 provides the following capabilities for optimizing the performance of the backup server in regard to data rates: Tivoli Data Protection for R/3 User s Guide 97

116 Parallel sessions. Multiple tape drives can be used in parallel to store data and increase overall data throughput. Storage hierarchies If tape drives are already assigned, disks can be used with additional sessions as intermediate storage, which can later be migrated to tape (inherent function of Tivoli Storage Manager). This method is recommended for offline redo log files (which are considerably smaller than data files) to avoid an excessive number of tape mounts. Multiple Servers As with multiple paths, parallel sessions can be routed to multiple Tivoli Storage Manager servers to increase the overall data throughput of the backup server (see also, Alternate/Parallel Backup Servers on page 11). Adaptation of Tivoli Storage Manager The performance adjustments on the Tivoli Storage Manager side can be done by customizing the appropriate configuration files. On the server side, it is the server option file dsmserv.opt, and on the client side the client option file(s) dsm.sys on UNIX systems and <server>.opt on Windows NT systems. The following table shows the corresponding Tivoli Storage Manager configuration file attributes with the recommended values. Table 5. Tuning Tivoli Storage Manager Configuration File Attributes Attributes Value Description 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. 98 Version 3 Release 2

117 Table 5. Tuning Tivoli Storage Manager Configuration File Attributes (continued) Attributes Value Description 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) 32 (others) Additional information can be found at Specifies the size, in kilobytes, which will be used for the TCP/IP sliding window for the client node. This is the size of the buffer used when sending or receiving data. The range of values is 0 to Adaptation of Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 provides some functions for reducing the backup/restore time of an SAP R/3 Oracle database. Appropriate adjustments can be made within the Tivoli Data Protection for R/3 profile (see also The Tivoli Data Protection for R/3 Profile on page 175). Parallelism Parallelism can be deployed to overcome a particular bottleneck. Parallelism can be applied by: Reading data in parallel from multiple disks (parallel sessions) and writing them to multiple tapes (one per session). Reading data from multiple disks and combining them into one data stream (multiplexing) to be written to tape. Thus, high speed tape drives such as the 3590 can be used very efficiently by matching disk read with tape write performance (provided sufficient network bandwidth is available). Transmitting data over parallel network connections (on a session basis). 6. Optimizing Backup/Restore Tivoli Data Protection for R/3 User s Guide 99

118 Writing data in parallel to multiple tapes can also be done by sending it to multiple Tivoli Storage Manager servers. Tivoli Data Protection for R/3 allows you to utilize several simultaneously running sessions to increase drastically the overall data transfer rate to a Tivoli Storage Manager server, according to the MAX_SESSIONS profile keyword (or MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, MAX_RESTORE_SESSIONS) specified. The management class specified in the profile keyword BRBACKUPMGTCLASS will be used when running the BRBACKUP. If it is a BRARCHIVE run, the management class specified in the profile keyword BRARCHIVEMGMTCLASS will be used. When running BRBACKUP, usually the data will be written directly to tape drives on the Tivoli Storage Manager server. This means, the parameter specified in the MAX_SESSIONS keyword must match the number of tape drives used simultaneously. Recommendations on the Tivoli Storage Manager server side that you should pay attention to are: No activation of collocation in the (tape) storage pool The specified number of tape drives should be available when BRBACKUP is running When running BRARCHIVE, either disk or tape storage pools can be utilized. The size of offline redo log files is much smaller compared to the size of database tablespace files backed up by BRBACKUP. The advantage of a disk storage pool is its random access nature: Several sessions of one BRARCHIVE can utilize one or two independent disk storage pool(s) Several sessions of BRARCHIVE runs of several databases can simultaneously utilize one or two independent disk storage pool(s) If your (primary) pools are tape pools, the same considerations for the tape setup as for the disk setup (see BRBACKUP above) apply. 100 Version 3 Release 2

119 For security reasons, the usage of the Tivoli Data Protection for R/3 profile keyword REDOLOG_COPIES with a minimum value of 2 is recommended and a specification of two management classes in the BRARCHIVEMGTCLASSES is also highly recommended. Therefore, if a backup copy of an offline redo log file is lost, Tivoli Data Protection for R/3, when carrying out a restore operation, will be able to automatically retrieve the data to be restored from the pool specified in the second management class (presuming that this storage pool is separate from the storage pool which encountered the problem). Compression Tivoli Data Protection for R/3 is able to do a null block compression before sending data over the network to the Tivoli Storage Manager server. The Tivoli Data Protection for R/3 profile keyword RL_COMPRESSION has to be set to YES (default is NO). This compression has been designed specifically for database files, since they usually contain large portions of null blocks. The compression is very simple and very fast and requires little CPU power. In contrast, the Tivoli Storage Manager compression is much more sophisticated, but also requires many more CPU resources than the simple null block compression. Using the null block compression instead of the Tivoli Storage Manager compression is recommended. Multiplexing In order to increase the data rate to a storage device of the Tivoli Storage Manager server, several files (up to eight) can be multiplexed to one data stream. To do this, the value of the keyword MULTIPLEXING in the Tivoli Data Protection for R/3 profile has to be set correctly (default is 1). 6. Optimizing Backup/Restore For example, MULTIPLEXING 4, causes each session of Tivoli Data Protection for R/3 to read from four files in parallel and to store the data in a special multiplexed file on the Tivoli Storage Manager server. This multiplexed file consists of a mixture of blocks from all four files. The following example illustrates this more specifically. If the average disk read rate is 4.5 MB/s from each disk, the database is backed up with a data rate of 4.5 *4=18MB/s. If each Tivoli Data Protection for R/3 User s Guide 101

120 file is compressible by a factor of two and compression is activated, it can be transferred to a Tivoli Storage Manager server at (4.5 * 4) / 2 = 9 MB/s. With null block compression, but without multiplexing, we could transfer only 4.5 /2 = 2.25 MB/s to one Tivoli Storage Manager server. (This example assumes that the Tivoli Storage Manager server and tape drive are fast enough to cope with this data rate.) Multiplexing reduces the number of Tivoli Storage Manager servers (and tape drives) required. The optimal value for MULTIPLEXING depends very much on the hardware environment, for example, the availability of a fast network (FDDI, Fast Ethernet), of fast tape drives within the tape (media) library, and on the compressibility of the database files. Appropriate MULTIPLEXING values would be expected in the range of 1 to 4. The example above shows some of the typical dependencies between the total backup rate, the disk transfer rate, the compression ratios, and the Tivoli Storage Manager data rate. BUFFSIZE In some environments, disk access at certain block sizes is much faster than at other block sizes. The keyword BUFFSIZE in the Tivoli Data Protection for R/3 profile allows the user to specify a certain block size for disk I/O within the range of 4096 to In most cases it will be expected that the default value (131072) is already close to an optimal value. Steps for Setting Up Your Environment The following describes the recommended steps and the most important tuning possibilities. Based on the multitude of software and hardware parameters involved and the variety of system environments, there cannot be one recipe that fits all. Individual optimizing on a trial and error basis will almost always be involved if tuning is to be done to the maximum possible level. Step 1: Single session optimization (MAX_SESSIONS = 1) 102 Version 3 Release 2

121 a) With RL_COMPRESSION OFF, optimize Network and Backup Server Parameters. b) Set RL_COMPRESSION ON and increase multiplexing MULTIPLEXING=N. The data rate should asymptotically increase with the number of multiplexed files. Increasing MULTIPLEXING creates a proportional increase in load on the database server. Therefore, you should select a MULTIPLEXING value with reasonable gain in data rate (before the curve starts to level off) and not go to the very maximum. Step 2: Increase the number of sessions (MAX_SESSIONS=N) a) As each session requires a dedicated tape drive, you can only increase MAX_SESSIONS to the number of drives available on the backup server. It may be necessary to add more tape drives. b) As you increase the number of sessions you will reach the next bottleneck, which will either be the SAP R/3 database server, the network, or the backup server. Use network and system monitors (CPU, I/O) to determine the source of the bottleneck. Step 3: Add additional network paths (multiple path function) Distribute sessions onto the multiple paths, see Alternate/Parallel Backup Paths and Backup Servers on page 167. Step 4: Optimize the disk layout of your SAP R/3 database server 6. Optimizing Backup/Restore To avoid disk contention caused by multiple read operations, distribute the files of your SAP R/3 database across as many disks as possible. Check for limitations in the bandwidth of the I/O adapters. Add additional adapters if necessary. Tivoli Data Protection for R/3 User s Guide 103

122 As a final measure it may be necessary to increase the CPU power of the SAP R/3 database server or backup server. 104 Version 3 Release 2

123 7 Administration Assistant for Tivoli Data Protection for R/3 7. Administration Assistant The Administration Assistant for Tivoli Data Protection for R/3 consists of a Web browser based graphical interface to support and assist the customizing of Tivoli Data Protection for R/3 and the analyzing of SAP R/3 database backup and restore operations. Objective of the Administration Assistant is to assist in configuration, monitoring, and administration of Tivoli Data Protection for R/3 from local or remote workstations. It gives SAP R/3 administrators the possibility of centralizing the database backup/restore administrative work, especially the monitoring of Tivoli Data Protection for R/3 and SAP R/3 database backup/restore actions from all SAP R/3 database servers within the system landscape. General An SAP R/3 system landscape in the real world typically unites more than one SAP R/3 system. At least one SAP R/3 test system and one SAP R/3 productive system will be used together. A typical example of this is shown in Figure 10 on page 106. Tivoli Data Protection for R/3 User s Guide 105

124 Administration Assistant Server Storage Media Tivoli Storage Manager LAN BACKBONE Administration Assistant Clients (Web Browser) SAP R/3 Database Server SAP R/3 Database Server SAP R/3 Database Server Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 Tivoli Data Protection for R/3 Figure 10. Example of an SAP R/3 Landscape The central Administration Assistant instance is the Administration Assistant Server, which can be installed on any system (UNIX, or Windows). It works as a data collector and data distributor. This means that it collects all incoming backup/restore dependent Administration Assistant data generated by the Tivoli Data Protection for R/3 background process Prole (see also Introducing Tivoli Data Protection for R/3 on page 1) from the SAP R/3 database server. This data will be distributed over a network (LAN) to every Administration Assistant Client node (user frontend, Web browser based) actually connected, and written to various local files stored on the Administration Assistant Server. These files serve as a data source for subsequent reviewing of performance/error analysis of backup/restore functions which have been carried out. They can also hold various Tivoli Data Protection for R/3 configuration states (Tivoli Storage Manager configuration files, Tivoli Data Protection for R/3 profile, SAP backup profile) in form of a configuration history. 106 Version 3 Release 2

125 The Administration Assistant can be understood to be a collection of four programs: System Configuration Performance Monitor Operations Monitor Problem Support The System Configuration Tool lets you customize the SAP backup profile, the Tivoli Data Protection for R/3 profile, and all the necessary Tivoli Storage Manager files. Online documentation guides you through the customization process and gives you descriptions of the parameters and their values. When you have finished, you can copy the Tivoli Data Protection for R/3 profile to another Tivoli Data Protection for R/3 node. The Performance Monitor displays Tivoli Data Protection for R/3 performance information while Tivoli Data Protection for R/3 is performing a backup or restore operation. You can also display saved performance statistics when Tivoli Data Protection for R/3 is not active. The Monitoring Tool runs on all platforms that support Tivoli Data Protection for R/3. The Operations Monitor provides a centralized overview of backup status information for all SAP R/3 systems registered with the central Administration Assistant server. The overview panel shows summaries of the backup status of an SAP R/3 system and the state of the current backup for every system in your SAP R/3 system landscape. Detailed information about all backup runs on a specific SAP R/3 system can also be obtained. Problem Support allows sending a support request directly to the Tivoli Data Protection for R/3 support center. Additionally, a user-specified problem description can be included. This tool automatically tries to attach further information to the mail, such as configuration profiles, error logs, etc. 7. Administration Assistant Tivoli Data Protection for R/3 User s Guide 107

126 Prerequisites The following prerequisites are required before the Administration Assistant can be invoked. 1. A successful installation of Tivoli Data Protection for R/3 (see Setting Up Tivoli Data Protection for R/3 on page 31) 2. A Java Runtime Environment (JRE). Note The version of the JRE must be 1.2 or higher. You can check the version of the installed Java software with the following command from a command line (this is the same for UNIX or Windows): java -version Not all vendors provide the JRE separately. You can install the Java Development Kit (JDK), because the JRE is part of the JDK. Contact the operating system vendor to get the required JRE or JDK software. 3. Additionally, the following two Java packages must be installed: Java Beans Activation Framework (JAF) version 1.1 or higher. Java Mail or higher 4. A fully Java 1.2-capable Web browser is required on the client machine (Java Plug-in 1.2 or higher must be installed). You can use Netscape Navigator Version 4.5 or higher or Microsoft Internet Explorer 5.x. 5. For UNIX systems, the X Window system is required. After ensuring that all these prerequisites are available, the installation process can commence. By subsequently starting the Administration Assistant you can verify the installation. 108 Version 3 Release 2

127 Installation In this section we will discuss the installation and customization of the Administration Assistant. The installation process is divided into two parts. One part looks at the Administration Assistant server installation, the other part is engaged in the Administration Assistant slave server installation. The Administration Assistant slave server is only needed in a Tivoli Data Protection for R/3 version 2.x environment for using the System Configuration Tool. Before you start the installation, there are some things that should be kept in mind. 1. The Administration Assistant server can, in principle, be installed on any machine in an SAP R/3 system landscape. 2. A Tivoli Data Protection for R/3 version 3.1 (or later) environment does not require the Administration Assistant slave server to be installed. In this case, you only need to install the Administration Assistant server. If, however, you want to use the Administration Assistant in a Tivoli Data Protection for R/3 version 2.x environment, the Administration Assistant slave server needs to be installed. 3. In this case, ensure that you observe the following: The installation of the Administration Assistant slave server must be done on the SAP R/3 database server machine. It is recommended that you install the Administration Assistant server first and then all the necessary Administration Assistant slave server(s). The reason is that the Administration Assistant server is the central instance within the Administration Assistant scenario and all slave server installations depend on this instance. Installation of the Administration Assistant Server To assist you with the installation procedure, the Administration Assistant package provides a setup assistant, a so-called installer, which guides you through the installation process. 7. Administration Assistant Tivoli Data Protection for R/3 User s Guide 109

128 Note It is necessary to have system administrator privileges to install the Administration Assistant correctly. The Administration Assistant is delivered as a Java class file named install.class. Note There is no need to set the environment variable CLASSPATH. But if this variable is set in the system environment, the directory where the file install.class resides must be included. You can now start the installation as follows: java install Only the name of the class file (install) has to be given. If only the JRE is installed, the command jre -cp. install must be used. Now, the installer becomes active and it is recommended that you follow the instructions which will be displayed on the screen. When you reach the section specify ports as shown in Figure 11 on page 111 it is important to: Check for free ports in the services file (in most cases the given values are usable) Remember the specified ports for later use 110 Version 3 Release 2

129 7. Administration Assistant Figure 11. Administration Assistant Server Setup Specify Ports Next, the hostname of the Administration Assistant server machine must be specified (or corrected) as shown in Figure 12 on page 112. Tivoli Data Protection for R/3 User s Guide 111

130 Figure 12. Administration Assistant Server Setup Host Name 112 Version 3 Release 2

131 Remember The communication between the Administration Assistant server and clients (Web browser or Java applet) will be done with Java RMI. An RMI communication requires a clear assignment between IP address and alias name for both of the communication clients involved. Each of these clients must be capable of resolving the IP address of the other client to an alias name and vice versa. If you use a DHCP service on the Administration Assistant server machine it may be possible, that this machine has two names. This would be a typical DHCP problem. A clearly defined hostname of the Administration Assistant server is a necessary prerequisite for subsequent communication between clients and this server (server configuration cannot be changed later). 7. Administration Assistant As a result of the above, the recommendation is to use a static IP address instead of one temporarily generated by DHCP. If you are using DHCP be aware, that in the case of a reboot of the Administration Assistant server machine, this machine will be allocated a new IP address and the Administration Assistant will not be able to work. Finally, you have to choose the destination directory to which the application will be installed as shown in Figure 13 on page 114. Tivoli Data Protection for R/3 User s Guide 113

132 Figure 13. Administration Assistant Server Setup Destination Directory The system impact, after the setup process is finished successfully, is: On UNIX systems: Specification of a new entry in the /etc/inittab to start the Administration Assistant automatically (Adma:23:once:+sh "Install directory"/sadma.sh). The expression Install directory will be replaced with the real directory name specified during the setup process. If none was specified, the default installation directory /usr/lpp/bkit will be used. On Windows NT systems: A new NT service. As a result, setup creates an entry in the Windows NT registry under 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services' with the name AdminAssistant. 114 Version 3 Release 2

133 Installation of the Administration Assistant Slave Server Most of the installation steps for the Administration Assistant slave server are similar to those described above for the Administration Assistant server. Note An installation of the Administration Assistant Slave Server is only necessary if you are using Tivoli Data Protection for R/3 version 2.4 or 2.7. This background process on the SAP R/3 database server will be needed by the Administration Assistant Server to access the configuration files (Tivoli Data Protection for R/3 profile, Tivoli Storage Manager client option files, SAP backup profile). It reads/writes these files and send the results to the Administration Assistant server. You can skip this step if you are using a Tivoli Data Protection for R/3 version more recent than Administration Assistant After the start of the installer, it is only necessary to select the desired install option as shown in Figure 14 on page 116. Tivoli Data Protection for R/3 User s Guide 115

134 Figure 14. Administration Assistant Slave Server Setup Select Option When this step has been carried out, the installer continues and finally displays Figure 15 on page Version 3 Release 2

135 7. Administration Assistant Figure 15. Administration Assistant Slave Server Setup Customize Slave Server In this figure you will see three boxes. In the first box you must enter the hostname of the Administration Assistant server. The second box (RMI port of the Administration Assistant main server) gives a default port value which is the same as that shown in Figure 11 on page 111. If the value was not changed during the Administration Assistant server setup it can be used here too. Otherwise you have to adapt it. The third box expects the SAP R/3 system identifier of the machine. If there is more than one SAP R/3 installed on this machine, you can specify these additional system identifiers separated by spaces. To use the Administration Assistant configuration facility, you must specify the paths where the configuration files are located. This is shown in Figure 16 on page 118. Tivoli Data Protection for R/3 User s Guide 117

136 Figure 16. Administration Assistant Slave Server Setup Specify Directories All the necessary input is now completed and the guided installation process will continue. The system impact, after the setup process has been finished successfully, is: On UNIX systems: A new entry in the /etc/inittab to start the Administration Assistant automatically (atsl:23:once:sh "Install directory"/admslave.sh). The expression Install directory will be replaced with the real directory name specified during the setup process which will be in our case the default directory /usr/lpp/admtslave. On Windows NT systems: A new NT service. As a result, setup creates an entry in the Windows NT registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services with the name AdminAssistant-Slave. 118 Version 3 Release 2

137 For both, the Administration Assistant server and the Administration Assistant slave server, the possibility of uninstalling the software from the machine is provided. On UNIX systems the script Uninstall.sh has to be started and on Windows NT systems run the script Uninstall.cmd. It is recommended that you perform the uninstall option only with system administrator privileges. This will allow the Uninstaller to remove the entries either from the inittab on UNIX or from the registry on Windows NT systems. 7. Administration Assistant Verification of the Installation There is no dedicated verification procedure provided with Administration Assistant. To verify and test the installation, it is recommended simply to start the Administration Assistant. The Administration Assistant becomes active when called up in Netscape as seen in Figure 17. For this reason, the hostname of the Administration Assistant server (see Figure 12 on page 112) and the port for the communication (see Figure 11 on page 111) have to be specified with a colon between them. Figure 17. Starting Administration Assistant with Netscape Every time a user starts the Administration Assistant, a Logon panel pops up for identification. The first time, there are no user profiles which belong to a user. Therefore, the initial account has the default user ID ADMIN and the password admin (note that these are case sensitive). Tivoli Data Protection for R/3 User s Guide 119

138 The screen shown in Figure 18 will now appear. Figure 18. Administration Assistant Start Screen You can invoke the functions Operations Monitor, Performance Monitor, System Configuration, Problem Support, and User Administration by a mouse click on the appropriate button. If you are using the Administration Assistant for the first time, you can now proceed to authorize users. 120 Version 3 Release 2

139 Note When connecting to the Administration Assistant with the initial user ID (ADMIN) it is recommended that you change the password of that user immediately. 7. Administration Assistant Authorization of Administration Assistant Users The User Administration function of the Administration Assistant enables you to create user accounts and to grant every user only the permissions he needs for his job. With the user administration function it is possible to create additional accounts with appropriate rights. Rights or user permission can be granted or revoked for a specified user profile. Every account has five authorities. These are: Operations monitor authority - permission to view backup status information of any SAP R/3 system within the system landscape Monitoring authority - permission to monitor jobs Configuration authority - permission to configure Tivoli Data Protection for R/3 Problem Support authority - permission to send support request mail to the Tivoli Data Protection for R/3 hotline. 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. Please refer to the online help for information on how to do this. Tivoli Data Protection for R/3 User s Guide 121

140 Use of the Administration Assistant Registered users of the Administration Assistant are able to start the Configuration facility, Performance Monitor or Operations Monitor corresponding to their rights which are set in the appropriate user profile. Once you have started one of the tools, you can get complete information on how to use it by activating the integrated help function by clicking on the Help button with the mouse. You can find additional detailed information about Tivoli Data Protection for R/3 Administration Assistant in the IBM redbook SAP R/3 Data Management with Tivoli Storage Manager, SG located at the Web page. 122 Version 3 Release 2

141 8 SAP R/3 System Cloning The procedure for cloning an SAP R/3 system explained in this chapter should be used to complement the SAP documentation R/3 Homogeneous System Copy and R/3 Installation on UNIX / Windows NT - Oracle Database. Furthermore, it is recommended that you use the correct SAP documentation for each particular environment. This documentation can be found at in 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. 8. SAP R/3 System Cloning General The SAP R/3 system cloning can be done if there is the necessity for one source R/3 system to be exactly copied to a target R/3 system. In this context, the source R/3 system is also called the original system, from which the data will be exported, and the target R/3 system is also called the destination system, which imports the data from the source R/3 system. SAP names the procedure of cloning an SAP R/3 system either homogeneous system copy or heterogeneous system copy. The difference between these two methods is as follows. In a homogeneous system copy scenario, the source and target systems have the same R/3 release, operating system, and database version. If this is not the case, you will get a heterogeneous system copy. Tivoli Data Protection for R/3 User s Guide 123

142 Further information about these two system copy scenarios can be found in OSS notes and SAP R/3 system cloning is appropriate in the following situations: Setting up an SAP R/3 system landscape (development, quality assurance, and production system) Hardware upgrade Creating multiple SAP R/3 test and/or demo systems Additional information about SAP R/3 system cloning can be found in the IBM redbook SAP R/3 Data Management with Tivoli Storage Manager, SG at the Web site. SAP R/3 System Cloning Example The following procedure is supplied with no warranty of any kind. For SAP specific changes see also OSS note It is assumed that there are two SAP R/3 systems installed and operating on two different machines and that Tivoli Data Protection for R/3 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. Depending on the password access method you are using, there are different things to do. 1. If you are using passwordaccess=generate (automatic password handling, see also Password Handling on page 161) in the Tivoli Storage Manager client option file dsm.sys on UNIX systems or <server>.opt on Windows NT 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: a. Make a backup copy of the client option file on the target system. 124 Version 3 Release 2

143 b. Copy the client option file from the source system to the target system. c. Edit the client option file and add NODENAME source system to the server stanza. d. Reset the Tivoli Storage Manager password for the target system node on the server. e. Set the newly created password on the client, e.g., dsmc q f. Remember to do this as root/administrator. f. Make a backup copy of the init<sid>.utl file on the target system. g. Copy the init<sid>.utl file from the source system to the target system. h. 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. i. Go ahead and restore the database under the SAP considerations. j. After the restore, reset the client option file and init<sid>.utl file to their originals and set the passwords on the target system. k. Reset the passwords on the source system. 8. SAP R/3 System Cloning 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. 2. If you are using passwordaccess=prompt (manual password handling, see also Password Handling on page 161), you only need to set the nodename/password in the init<sid>.utl file. a. Make a backup copy of the init<sid>.utl file on the target system. Tivoli Data Protection for R/3 User s Guide 125

144 b. Copy the init<sid>.utl file from the source system to the target system. c. Edit the init<sid>.utl file on the target system to reflect all the correct file and path names such as for CONFIGFILE, TRACEFILE,... d. As <SID>adm user, on the target system, set the Tivoli Data Protection for R/3 password: For UNIX systems backint -p /oracle/<sid>/dbs/init<sid>.utl -f password For Windows NT systems backint -p <drive>:\orant\database\init<sid>.utl -f password and issue the password at the prompt. e. Restore the database according to the SAP recommendation. f. Reset the init<sid>.utl file and the password on the target system. 126 Version 3 Release 2

145 A Tivoli Data Protection for R/3 Messages This chapter describes the messages issued by Tivoli Data Protection for R/3. The messages begin with the prefix BKI and will be listed in numerical order. For each message, the following information is provided: Message number 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. Explanation User Response Tivoli Data Protection for R/3 User s Guide 127 A. Tivoli Data Protection for R/3 Messages

146 Tivoli Data Protection for R/3 Messages BKI0000E Profile not specified. Explanation: Tivoli Data Protection for R/3 cannot locate the profile. User Response: Ensure that a profile is available. Notice that the BACKINT call must have the following form: backint -p init<sid>.util... BKI0004E Function not defined. Explanation: SAPDBA, BRBACKUP, or BRARCHIVE passed an invalid argument to Tivoli Data Protection for R/3. User Response: Ensure that you have the correct version of SAPDBA, BRBACKUP, or BRARCHIVE installed. See Prerequisites on page 31. Valid functions are: -f backup or -f restore or -f password or -f delete or -f inquire. BKI0005I Start of backint program at:time Explanation: Tivoli Data Protection for R/3 received control from SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE at time. User Response: None BKI0006E Type for backup not defined [type]. Please use file or file_online. Explanation: Tivoli Data Protection for R/3 expects as backup type parameter only file or file_online. User Response: If you start Tivoli Data Protection for R/3 manually to do a backup, ensure that the type option (-t) receives the correct arguments (file or file_online). If your Tivoli Data Protection for R/3 has been invoked by one of the SAP database utilities (e.g., BRBACKUP), ensure that the SAP backup profile init<sid>.sap is customized correctly (see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49). BKI0020I End of backint program at: time Explanation: Tivoli Data Protection for R/3 returned control to SAPDBA, BRBACKUP, BRARCHIVE, or BRRESTORE at time. User Response: none 128 Version 3 Release 2

147 BKI0021I Elapsed time: elapsedtime Explanation: The time needed for the complete backup was elapsedtime. User Response: None BKI0023I Time: current_time Done: saved_bytes(percent)of bytes Estimated end time: end_time Explanation: Tivoli Data Protection for R/3 finished saving a specific object at current_time. The saved_bytes amount of the total number of bytes have been saved. percent shows the percentage. This Tivoli Data Protection for R/3 call will be completed at the estimated end_time. User Response: None BKI0024I Return code is: return code Explanation: Shows the return code of Tivoli Data Protection for R/3. A return code of 0 means no errors or warnings occurred. If the return code is 1, at least one warning was issued by the program. If the return code is 2, at least one error message was issued. User Response: error messages. For return codes other than 0, check the run log for warnings or BKI0027I Time: current_time Objects: current_num of total_num in process: file_name MGMNT-CLASS: management_class TSM Server: server name. Explanation: Tivoli Data Protection for R/3 started saving current_num files at current_time. The total number of files to save is total_num. The file file_name is currently being processed. The files are transferred to the Tivoli Storage Manager server server name, which stores them in the Management Class management_class. User Response: None Tivoli Data Protection for R/3 User s Guide 129 A. Tivoli Data Protection for R/3 Messages

148 BKI0030I Time: current_time Objects: current_num of total_num in process: file_name Size: bytes MB TSM Server: server name. Explanation: Tivoli Data Protection for R/3 completed saving current_num files at current_time. The total number of files to save is total_num. The file file_name is currently being processed. The Tivoli Storage Manager server server name is selected. User Response: None BKI0031W Object not found or not accessible: objectname. Explanation: The object was not found or is not accessible to Tivoli Data Protection for R/3. User Response: Check path and name and the permissions of that object and try again. BKI0032E Error opening file file name: system error description Explanation: A system error occurred during opening of the file file name. system error description will describe the error in more detail. User Response: Read the system error description. BKI0033E Error opening file file name: system error description Explanation: See BKI0032E. User Response: See BKI0032E. BKI0049I Please enter password for node nodename on server server name Explanation: The password for the node nodename on the Tivoli Storage Manager server server name has to be entered for storing it in the Tivoli Data Protection for R/3 configuration file. User Response: server. Enter the password for the corresponding Tivoli Storage Manager BKI0050I Please enter password for node nodename on server server name again Explanation: In order to avoid typing errors, you have to enter the password twice. 130 Version 3 Release 2

149 User Response: Enter the password again. BKI0051I Password successfully verified for node nodename on server server name. Explanation: The password for the node nodename on the Tivoli Storage Manager server server name was changed successfully. User Response: None BKI0052E Password verification for node nodename on server server name failed. Explanation: The password you entered for the node nodename on the Tivoli Storage Manager server server name was wrong. User Response: Enter the password again. If this error still exists, contact your Tivoli Storage Manager administrator. BKI0053I Time: current_time Objects: current_num of total_num done: file_name with: bytes saved with description object_desc. Explanation: Tivoli Data Protection for R/3 completed saving current_num file at current_time. The total number of files to be saved is total_num. The file file_name with the size bytes is saved with the description object_desc. User Response: None BKI0054I Time: current_time Objects: current_num of total_num done: file_name with: bytes restored with description object_desc. Explanation: Tivoli Data Protection for R/3 completed restoring of current_num file at current_time. The total number of files to be restored is total_num. The file file_name with the size bytes is restored with the description object_class. User Response: None BKI0055I Object objectname with size saved with description description. Explanation: The object objectname was saved successfully. User Response: None Tivoli Data Protection for R/3 User s Guide 131 A. Tivoli Data Protection for R/3 Messages

150 BKI0056I Object objectname with size restored with description description. Explanation: The object objectname was restored successfully. User Response: None BKI0059E You have to set the environment variable DSMI_CONFIG to the full filename of the Tivoli Storage Manager client option file dsm.opt. Explanation: Tivoli Storage Manager client option file not found. User Response: Verify that the Tivoli Storage Manager option file dsm.opt is pointed to by DSMI_CONFIG. BKI0060E The parameter parameter is not known. Explanation: The command parameter parameter for Tivoli Data Protection for R/3 is unknown. User Response: Check the specified command parameter and try again. BKI0061W The output file file name is not valid. Explanation: The specified output file file name could not be created. User Response: Check that file name is a valid file name on your operating system. Also check that the application has the appropriate permissions to create the file within the specified directory. The directory must already exist. If the file already exists, rename the old one. BKI0062E The input file file name is not valid. Explanation: Tivoli Data Protection for R/3 is not able to read the input file file name correctly. User Response: Check the path and name of the output file and the appropriate file access permission. BKI0063E The UTL file file name is not valid. Explanation: Tivoli Data Protection for R/3 is not able to read the input file file name correctly. User Response: Check the path and name of the output file and the appropriate file access permission. 132 Version 3 Release 2

151 BKI0064E The option option is unknown. Explanation: A Tivoli Data Protection for R/3 option is invalid or unknown. User Response: Check the specified option(s) and try again. BKI0065E The argument is missing for option option. Explanation: Every Tivoli Data Protection for R/3 option requires an argument. User Response: Insert the missing argument and try again. BKI0101I Session session: Please enter cont to continue or stop to cancel. Explanation: If Tivoli Data Protection for R/3 is running in unattended mode (profile keyword BATCH), it terminates the current run if operator intervention is required. User Response: Enter cont or stop. BKI0102I Your reply: reply. Explanation: Tivoli Data Protection for R/3 indicates the reply you made. User Response: None BKI0400I TDP is waiting for BRBACKUP Explanation: Tivoli Data Protection for R/3 is waiting for BRBACKUP to set a tablespace in the begin/end backup mode. User Response: None BKI0405I TDP waited num_sec sec. for BRBACKUP in util_file_online communication. Explanation: Tivoli Data Protection for R/3 waited num_sec seconds for BRBACKUP to set a tablespace in begin/end backup mode. User Response: None BKI0410E Cannot open or delete switch file file name. Check permissions. Explanation: If Tivoli Data Protection for R/3 is not correctly installed (as the root user on UNIX or administrator group on Windows NT) then Tivoli Data Protection for R/3 is not able to open the necessary communication file to the SAP R/3 system. User Response: Check the file permission. Tivoli Data Protection for R/3 User s Guide 133 A. Tivoli Data Protection for R/3 Messages

152 BKI0411E Maximum time waiting for BRBACKUP expired. Explanation: The SAP database utilities did not respond within the expected time. User Response: Contact your R/3 administrator. BKI0412E BRBACKUP was not able to switch requested tablespace in BEGIN BACKUP mode. Explanation: Tivoli Data Protection for R/3 could not continue the backup, because BRBACKUP was not able to switch the requested tablespace in BEGIN backup mode. This is necessary for locking the tablespace. User Response: Contact your R/3 administrator. BKI0450I Version 2 restore: file Explanation: A restore of data backed up with Tivoli Data Protection for R/3 version 2 was executed. User Response: None BKI0451I This version of Tivoli Data Protection for R/3 will expire on date. Explanation: This is a test version that will expire on date. User Response: None. BKI0452E This version of Tivoli Data Protection for R/3 has expired. Explanation: This is a test version that has expired. User Response: Order a release version of Tivoli Data Protection for R/3 or contact your IBM/Tivoli Sales Representative. BKI0453W This version of Tivoli Data Protection for R/3 will expire in number days. Explanation: This is a test version with a time limit. It will expire in number days. User Response: Order a release version of Tivoli Data Protection for R/3 or contact your IBM/Tivoli Sales Representative before the version expires. BKI0454I *** This copy is NOT FOR RESALE. *** Explanation: This version is not for resale. User Response: None. 134 Version 3 Release 2

153 BKI0455E License file file name does not exist. Explanation: The license file agent.lic was not found where expected. User Response: Make sure that the agent.lic file resides in the same directory as the init<sid>.utl file. BKI0456E Unable to access license file file name. Explanation: Unable to access license file. User Response: Make sure the access permissions allow read/write access. BKI0457E License file file name contains invalid data/checksum. Explanation: The license file is invalid. User Response: Make sure you have the right agent.lic file for the right platform installed. agent.lic files are platform dependent. BKI1000E Syntax error in line line: statement Explanation: The statement statement in the Tivoli Data Protection for R/3 profile is unknown or incorrect. User Response: Correct the error and try again. BKI1001E Syntax error in file file name. Exiting Program. Explanation: Tivoli Data Protection for R/3 has detected an syntax error in the file file name and stops any action. User Response: Correct the error(s) in the file file name and try again. BKI1002E BKI1003W BACKUPIDPREFIX must be number_of_characters characters. Explanation: characters. The length of BACKUPIDPREFIX must be number_of_characters User Response: Enter a BACKUPIDPREFIX with the required length (e.g., SAP, BKI ). Please set REDOLOG_COPIES to a number between 1 and max_copies. Now it is set to act_copies. Explanation: Tivoli Data Protection for R/3 currently supports 1 to 9 copies of offline redo log files. Tivoli Data Protection for R/3 User s Guide 135 A. Tivoli Data Protection for R/3 Messages

154 User Response: Adapt the REDOLOG_COPIES settings in the Tivoli Data Protection for R/3 profile. BKI1004W You should specify the BACKUPIDPREFIX before the TRACEFILE statement, so that the BACKUPIDPREFIX can be used in the tracefile name. Explanation: The BACKUPIDPREFIX is used to build the Name of the tracefile. Therefore, BACKUPIDPREFIX must be specified before the TRACEFILE statement. User Response: Define a 6 characters long BACKUPIDPREFIX in the Tivoli Data Protection for R/3 profile (e.g., SAP, BKI ). BKI1005W The tracefile name trace_filename should be absolute. Explanation: None User Response: Specify an absolute tracefile name, for example /oracle/c21/saptrace/tracefile. BKI1006E The SERVERNAME must be less than max_char characters. Explanation: You have used a SERVERNAME with more than max_char characters. User Response: Use a shorter SERVERNAME. BKI1007E The NODENAME must be less than max_char characters. Explanation: You have used a NODENAME with more than max_char characters. User Response: Use a shorter NODENAME. BKI1008E The MANAGEMENTCLASSNAME must be less than max_char characters. Explanation: You have used a MANAGEMENTCLASSNAME with more than max_char characters. User Response: Use a shorter MANAGEMENTCLASSNAME. BKI1009W Please set MULTIPLEX to a number between 1 and max_multiplex. Now it is set to act_multiplex. Explanation: You have set multiplexing to an unsupported number. Tivoli Data Protection for R/3 now uses act_multiplex. User Response: Set multiplexing to a number between 1 and max_multiplex. 136 Version 3 Release 2

155 BKI1010W The configfile name configuration_filename should be absolute. Explanation: None User Response: Specify an absolute file name, for example /oracle/c21/dbs/initc21.bki. BKI1011W The sortfile name sortfile_filename should be absolute. Explanation: None User Response: Specify an absolute file name, for example /oracle/c21/dbs/sortfile. BKI1012E The configfilename configuration_filename could not be opened. Explanation: Tivoli Data Protection for R/3 is unable to read the file configuration_filename. User Response: This error could have various reasons, try the following: 1. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE). 2. Make sure, that the file access permission are set correctly. BKI1013E Profile not found or permissions denied : profile_filename. Explanation: Tivoli Data Protection for R/3 is unable to open the profile profile_filename. User Response: Ensure that the SAP backup profile init<sid>.sap contains a valid entry util_par_file for the Tivoli Data Protection for R/3 profile. Furthermore, this file must be readable by Tivoli Data Protection for R/3, see Customizing Tivoli Data Protection for R/3 and SAP Backup Profile on page 49 for details. BKI1014I The parameter PERF_MONITOR is no longer supported. Now it is enabled by default. Explanation: For version 2.7 or later of Tivoli Data Protection for R/3, the Performance Monitor of the Administration Assistant can be used by default. Therefore, the profile parameter PERF_MONITOR is no longer needed. User Response: None Tivoli Data Protection for R/3 User s Guide 137 A. Tivoli Data Protection for R/3 Messages

156 BKI1015I The parameter BACKAGENT is no longer needed. Explanation: For version 2.7 or later of Tivoli Data Protection for R/3,, only one executable, called BACKINT, will be provided and needed. The former executable, called BACKAGENT, will no longer supported or needed. User Response: None BKI1016W The trace file name file name could not be opened for writing! Explanation: The trace file could not be opened for writing. User Response: Ensure that you have specified a correct path for the trace file. BKI1017E The server server name is already defined. Please use another name! Explanation: The server you want to configure is already defined. User Response: Specify another server name. Server names have to be unique. BKI1200E Can t read/write file: file name. Explanation: Tivoli Data Protection for R/3 is unable to read or write a datafile (file name) of a tablespace being backed up or restored. User Response: Check the file access permission of the affected file(s). Try again. If the problem still exists, contact the SAP R/3 administrator. BKI1201E There are no Tivoli Storage Manager-Servers available. Explanation: Tivoli Data Protection for R/3 cannot locate a Tivoli Storage Manager server. User Response: Install and specify at least one Tivoli Storage Manager server in the Tivoli Data Protection for R/3 profile (keyword SERVER). BKI1202E You must specify either MAX_SESSIONS or all off MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS and MAX_RESTORE_SESSIONS Explanation: There is a setup error with the SESSIONS parameters within the Tivoli Data Protection for R/3 profile. 138 Version 3 Release 2

157 User Response: Specify either MAX_SESSIONS and one of the more specific parameters MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS or MAX_RESTORE_SESSIONS or all of the three specific session parameters without the MAX_SESSIONS parameter. BKI1203E Not enough sessions available (number of sessions required and number of sessions available). Explanation: The sum of available sessions specified in the various server statements (parameter SESSIONS) does not cover the required number of sessions (parameter MAX_SESSIONS). User Response: Change the values of the corresponding parameters in the Tivoli Data Protection for R/3 profile, so that the condition mentioned in the explanation is fulfilled. BKI1205E If you want num_redo REDOLOGCOPIES on Tivoli Storage Manager-Server servername, you should give me at least num_mc different Archive Management Classes. Explanation: Tivoli Data Protection for R/3 requires that the number of different Archive Management Classes (parameter BRARCHIVEMGTCLASS) on the Tivoli Storage Manager servers is equal to or greater than the number of redo log copies (parameter REDOLOG_COPIES). User Response: Define at least as many different Archive Management Classes as redo log copies requested. BKI1206W If you want num_redo REDOLOGCOPIES on Tivoli Storage Manager-Server server name, you should give me at least num_mc different Archive Management Classes. Explanation: The message appears during a BRBACKUP run. A BRARCHIVE run afterwards would be failed. User Response: Define at least as many different Archive Management Classes as redo log copies requested. BKI1207E Directory backup not supported Explanation: This option is not yet available. User Response: Wait for a future release of Tivoli Data Protection for R/3, which supports this option. Tivoli Data Protection for R/3 User s Guide 139 A. Tivoli Data Protection for R/3 Messages

158 BKI1208E The object file name will be retried [retry_num] Explanation: There was an error with the object file_name. Tivoli Data Protection for R/3 will try to save/restore the object one retry_num times. User Response: Look at the error messages in the Tivoli Data Protection for R/3 protocol and solve the error for the next run. BKI1209E Object not found or not accessible objectname. Explanation: Tivoli Data Protection for R/3 cannot locate the Oracle object objectname. User Response: The backup integrity is affected. Contact the SAP or Tivoli Data Protection for R/3 support. BKI1210E Input file not found or not accessible file name. Explanation: Tivoli Data Protection for R/3 cannot locate the temporary file file name. This file contains the list of Oracle objects to be backed up/restored. It is passed to Tivoli Data Protection for R/3 by BRBACKUP, BRARCHIVE or BRRESTORE. User Response: Ensure, that you have the correct version of SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE installed. See Setting Up Tivoli Data Protection for R/3 on page 31. BKI1211E There is something wrong with your CONFIG_FILE file name. Explanation: There is a problem with your Tivoli Data Protection for R/3 configuration file setup. User Response: Check the file permission and the file name specified in the Tivoli Data Protection for R/3 profile keyword CONFIG_FILE. BKI1212W The file file name was not found in the manual sorting file. Explanation: The file you want to back up was not found in the manual sorting file. User Response: Check and correct the manual sorting file so that it contains all the files you are backing up. BKI1213I Program ended with code = return code Explanation: The return code of the program is displayed. User Response: None. 140 Version 3 Release 2

159 BKI1214E TSM Error: error text Explanation: The specified TSM error occurred. User Response: Check error text and correct the problem. BKI1215I Average transmission rate was number GB/h ( number MB/sec). Explanation: The average transmission rate is displayed. User Response: None. BKI1216E There are no BRBACKUPMGTCLASSES available. Explanation: The BRBACKUPMGTCLASSES you have specified in your init<sid>.utl file are not correct. User Response: Check the management classes on the TSM server and specify correct ones. BKI1217E There are no BRARCHIVEMGTCLASSES available. Explanation: The BRARCHIVEMGTCLASSES you have specified in your init<sid>.utl file are not correct. User Response: Check the management classes on the TSM server and specify correct ones. BKI2000I Successfully connected to PROLE on port portnumber. Explanation: One of the Tivoli Data Protection for R/3 modules BACKINT or the backup library libtdp_r3 initiated a successful connection to the background process Prole on port portnumber. User Response: None BKI2001E Socket error while connecting to PROLE: reason. Explanation: The Tivoli Data Protection for R/3 background process Prole is not running. User Response: Start Prole manually and try again. BKI2002E No valid callback function of type fkt_type supplied. Explanation: Internal Tivoli Data Protection for R/3 error User Response: Contact the Tivoli Data Protection for R/3 support. Tivoli Data Protection for R/3 User s Guide 141 A. Tivoli Data Protection for R/3 Messages

160 BKI2003I File file_name, BID deleted. Explanation: The file file_name with the backup ID BID was deleted from the Tivoli Storage Manager. User Response: None BKI2004E Connection to PROLE lost. Explanation: During Tivoli Data Protection for R/3 operation the connection to Prole was lost. Network problems could be the reason. User Response: Check your network environment and if Prole is still running and try again. BKI2005E Illegal parameter in message from Prole. Exiting... Explanation: This error occurs if the version of Prole and of the executable BACKINT or the backup library libtdp_r3 does not match. User Response: Check the version of Prole and BACKINT/backup library libtdp_r3 you are currently using. BKI2006E General exception in dispatcher. Exiting... Explanation: Internal Tivoli Data Protection for R/3 error. User Response: Contact the Tivoli Data Protection for R/3 support. BKI2007E Unknown Port: port Explanation: is unknown. The port specified for the communication between Prole and Backint User Response: Check the port value specified when Prole was started. Additionally, check the environment variable PROLE_PORT for the Backint environment. These two values must match. BKI2008E Unable to connect to PROLE. Explanation: Internal Tivoli Data Protection for R/3 error. User Response: Contact the Tivoli Data Protection for R/3 support. 142 Version 3 Release 2

161 BKI2009I Deleting all versions with version Number <= version_number. Explanation: All full database backups and their corresponding redo log backups will be deleted from Tivoli Storage Manager storage, if their version number is less than or equal to version_number. User Response: None BKI2010E Error occurred processing FRONTEND Explanation: An error occurred during the frontend processing. User Response: Check the frontend script/program and the settings in the Tivoli Data Protection for R/3 profile (keyword FRONTEND) and try again. BKI2011E Error occurred processing BACKEND. Explanation: An error occurred during the backend processing. User Response: Check the backend script/program and the settings in the Tivoli Data Protection for R/3 profile (keyword BACKEND) and try again. BKI2012E Passwords do not match. Try again. Explanation: The first and second password you entered do not match. User Response: Enter the password correctly. BKI2013I Starting FRONTEND Program. Explanation: The frontend program is executing. User Response: None BKI2014I FRONTEND program finished. Explanation: The frontend program is finished. User Response: None BKI2015I Starting BACKEND program. Explanation: The backend program is executing. User Response: None Tivoli Data Protection for R/3 User s Guide 143 A. Tivoli Data Protection for R/3 Messages

162 BKI2016I BACKEND program finished. Explanation: The backend program is finished. User Response: None BKI2017I Blocksize is set to num_bytes bytes. Explanation: The operational blocksize of Tivoli Data Protection for R/3 is num_bytes bytes. User Response: None BKI2018E Exception in main message loop: description Explanation: An error occurred during processing. The error may contain a descriptive text. User Response: Contact your service representative. BKI2019E Socket error while connecting to Prole on port number for tracing: description Explanation: During processing, a socket error occurred on port number. description may contain the system error text. User Response: representative. Check the description. If the error persists, contact your service BKI2020E Error occurred for trace connection to Prole on port number. Explanation: The network connection that is used for tracing generated an error on port number. User Response: Contact your service representative. BKI2021E Unable to delete file file name : description Explanation: Unable to delete the file file name. description may contain the system error text. User Response: Check the description. If the error persists, contact your service representative. BKI2022E Unable to change mode of file file name : description Explanation: Unable to change mode of file file name. description may contain the system error text. 144 Version 3 Release 2

163 User Response: representative. Check the description. If the error persists, contact your service BKI2023E Error occurred during trace connection to Prole. Tracing will stop now. Explanation: Error occurred during trace connection to Prole. User Response: Tracing will stop. If the problem persists, contact your service representative. BKI4000W The attributes of file file name cannot be restored. Reason: errno (error_num) error_desc. Explanation: The file file name was restored successfully but one or more file attributes (permission, ownership, date/time) of the file file name cannot be restored correctly. User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. An initial solution could be to set the appropriate correct permission for the file file name manually. BKI4001E File file name cannot be created. Reason: errno (error_num) error_desc. Explanation: The file file name to be restored could not be created/written. It is possible, that you do not have the appropriate rights for writing the file file name to the destination path. User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. Furthermore, check the write permission of the user who started the restore. BKI4002E Error during restore of file file name. Reason: errno (error_num) error_desc. Explanation: An error occurs during the restore process of the file file name. User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. BKI4003E Error reading file file name. Only read num_bytes out of all_bytes. Explanation: An error occurs reading the file file name. Only num_bytes of all_bytes could be read. User Response: Try your last action again. If the error still exists please contact the Tivoli Data Protection for R/3 support. Tivoli Data Protection for R/3 User s Guide 145 A. Tivoli Data Protection for R/3 Messages

164 BKI4004E Error writing file filename. Only wrote num_bytes out of all_bytes. Explanation: An error occurs writing the file file name. Only num_bytes of all_bytes could be written. User Response: Try your last action again. If the error still exists please contact the Tivoli Data Protection for R/3 support. BKI4005E Error allocating memory block for file file name. BLOCKSIZE may be too large. Explanation: Tivoli Data Protection for R/3 was not able to request new memory blocks during the backup of file file name. User Response: Verify that you have set a valid value for BLOCKSIZE. If you are not sure what value is valid, comment it out so the default value is used. Furthermore, you can check if you have enough RAM available with your machine. Also, check the memory usage during backup. It may be necessary to stop another application, increase memory, or change the configuration of Tivoli Data Protection for R/3. BKI4006E Error allocating memory block for file file name. BLOCKSIZE may be too large. Explanation: User Response: See BKI4005E. See BKI4005E. BKI5000E Tivoli Storage Manager Error: error_message Explanation: During a connection of Tivoli Data Protection for R/3 to Tivoli Storage Manager server, a Tivoli Storage Manager error error_message occurred. User Response: Use the Tivoli Storage Manager Messages guide and correct the Tivoli Storage Manager server error. Try your last action again. BKI5001E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5002E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. 146 Version 3 Release 2

165 BKI5003E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5004E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5005E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5006E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5007E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5008E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5009E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI5010E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. Tivoli Data Protection for R/3 User s Guide 147 A. Tivoli Data Protection for R/3 Messages

166 BKI5011E Tivoli Storage Manager Error: error_message Explanation: See BKI5000E. User Response: See BKI5000E. BKI7001E Backup file file name already exists. Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7002E Bad mode specified. Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7009E Cannot connect to media manager. Explanation: Tivoli Data Protection for R/3 is not able to connect to the Tivoli Storage Manager server. User Response: Check the Tivoli Storage Manager API environment variables DSMI_DIR and DSMI_CONFIG. BKI7010E Permission denied. Explanation: The permission for a connection to the Tivoli Storage Manager server are not valid. User Response: Check your Tivoli Storage Manager client (API client) permission. For further information contact your Tivoli Storage Manager administrator. BKI7012E Invalid arguments during call of function. Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI7020E Bad handle rman_handle during call of function. Explanation: This is an RMAN internal error. 148 Version 3 Release 2

167 User Response: administrator. See your Oracle documentation or contact your Oracle database BKI7021E Bad flags during call of function. Explanation: This is an RMAN internal error. User Response: See your Oracle documentation or contact your Oracle database administrator. BKI9000E System error: error Explanation: Tivoli Data Protection for R/3 has found the following error: error. Thisisa catch_all error code for unpredictable system errors. User Response: Contact your system representative. BKI9001E Internal error: error Explanation: Tivoli Data Protection for R/3 has found the following internal error: error. User Response: Contact the Tivoli Data Protection for R/3 support. Tivoli Data Protection for R/3 File Manager Error Messages Backint not found! Explanation: The executable BACKINT was not found. This executable is necessary to run Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3 File Manager calls Tivoli Data Protection for R/3, the profile for Tivoli Data Protection for R/3 is required. User Response: Specify the full file name of the Tivoli Data Protection for R/3 profile when starting Tivoli Data Protection for R/3 File Manager, for example: backfm -p /oracle/c21/dbs/initc21.utl. Tivoli Data Protection for R/3 User s Guide 149 A. Tivoli Data Protection for R/3 Messages

168 Backint call was not successful! Explanation: The communication with the Tivoli Storage Manager server failed. User Response: Check that Tivoli Data Protection for R/3 and the Tivoli Storage Manager server(s) work correctly. It must be possible to run Tivoli Data Protection for R/3 directly from the command line, otherwise Tivoli Data Protection for R/3 File Manager will also not work. Cannot open temporary file! Explanation: reasons. User Response: UNIX NT A temporary file could not be opened. This could have several Make sure the directory /tmp is not full and you have write permission for this directory. 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: Please inform your system administrator or the Tivoli Data Protection for R/3 support about this problem. 150 Version 3 Release 2

169 B Using Tivoli Data Protection for R/3 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. RMAN Setup on UNIX Systems Shared libraries have different file extensions on different UNIX 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 6. File Extensions for Shared Libraries Operating System Extension AIX a HP-UX sl B. RMAN Setup Tivoli Data Protection for R/3 User s Guide 151

170 Table 6. File Extensions for Shared Libraries (continued) Operating System Linux Solaris Tru64 UNIX Extension so so so To set up your Tivoli Data Protection for R/3 for use with RMAN under UNIX, follow these steps: 1. Install Tivoli Storage Manager API Client on your SAP R/3 database server (see Configuration of Tivoli Storage Manager Client on page 25). 2. Install Tivoli Data Protection for R/3 on your SAP R/3 database server (see Setting Up Tivoli Data Protection for R/3 on page 31). 3. Set Tivoli Data Protection for R/3 password for Tivoli Storage Manager (see Password Handling on page 51). 4. Set Tivoli Storage Manager API client environment variables (DSMI_DIR, DSMI_CONFIG, DSMI_LOG). 5. Add the path to the library shipped with Tivoli Data Protection for R/3 to the library path environment of your system. 6. Create a softlink in /usr/lib for libobk.<ext> to /usr/tivoli/tsm/tdp_r3/libtdp_r3.<ext>, if not already done by the installer. 7. Link the library shipped with Tivoli Data Protection for R/3 (libtdp_r3) with RMAN. Example for Oracle 8.0 cd $ORACLE_HOME/rdbms/lib ln -s /usr/tivoli/tsm/tdp_r3/libtdp_r3.<ext> /usr/lib/libobk.<ext> make -f ins_rdbms.mk ioracle LLIBMM=/usr/lib/libobk.<ext> 152 Version 3 Release 2

171 Example for Oracle 8.1 cd $ORACLE_HOME/rdbms/lib ln -s /usr/tivoli/tsm/tdp_r3/libtdp_r3.<ext> /usr/lib/libobk.<ext> make -f ins_rdbms.mk ioracle LLIBOBK=/usr/lib/libobk.<ext> 8. 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=/<path>, DSMI_CONFIG=/<path>/<client system options file>, DSMI_LOG=/<path>/dsierror.log,XINT_PROFILE=/<path>/init<SID>.utl, PROLE_PORT=portnumber)" The appropriate Prole port number can be found in the /etc/services file. Troubleshooting 1. Ensure that Oracle has linked the right library /usr/lib/libobk.<ext> linked to /usr/tivoli/tsm/tdp_r3/libtdp_r3.<ext> 2. Remove the library in /$ORACLE_HOME/lib/rdbms/lib/libobk.<ext> 3. Examine the sbtio.log located in the directory specified in the user_dump_dest keyword within the Oracle profile init<sid>.ora. 4. Examine the dsierror.log located in the directory specified with the environment variable DSMI_LOG 5. 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 6. On some operating systems, an additional softlink is needed in /usr/lib for libobk.<ext>.1' to /usr/tivoli/tsm/tdp_r3/libtdp_r3.<ext>. B. RMAN Setup Tivoli Data Protection for R/3 User s Guide 153

172 ln -s /usr/tivoli/tsm/tdp_r3/libtdp_r3.<ext> /usr/lib/libobk.<ext>.1 RMAN Setup on Windows NT Systems To set up your Tivoli Data Protection for R/3 for use with RMAN under Windows NT, follow these steps: 1. Stop the following service: OracleService<SID> 2. Install Tivoli Storage Manager API Client on your SAP R/3 database server (see Configuration of Tivoli Storage Manager Client on page 25). 3. Install Tivoli Data Protection for R/3 on your SAP R/3 database server (see Setting Up Tivoli Data Protection for R/3 on page 31). 4. Set Tivoli Data Protection for R/3 password for Tivoli Storage Manager (see Password Handling on page 51). 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>\dsierror.log,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: OracleStart<SID> Troubleshooting 1. Examine the sbtio.log located in the directory specified in the user_dump_dest keyword within the Oracle profile init<sid>.ora. 154 Version 3 Release 2

173 2. Examine the dsierror.log located in the directory specified with the environment variable DSMI_LOG 3. 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 B. RMAN Setup Tivoli Data Protection for R/3 User s Guide 155

174 156 Version 3 Release 2

175 C Migration from Tivoli Data Protection for R/3 Version 2.7 to Version 3.2 The following migration procedure describes all the necessary steps to be done if you have a running Tivoli Data Protection for R/3 version 2.7 and you want to upgrade to Tivoli Data Protection for R/3 version 3.2. Notes Tivoli Data Protection for R/3 version 3.2 cannot view or restore data backed up with Tivoli Data Protection for R/3 version 2.7 or earlier. This data is still stored on the TSM server, but the restore requires following the steps detailed in this appendix for restore/recovery of a backup made with Tivoli Data Protection for R/3 version 2.7. When data backed up by Tivoli Data Protection for R/3 version 2.7 or earlier is no longer needed, TSM and Tivoli Data Protection for R/3 should be cleaned up by following step 9 on page 159. In all cases, be sure to also check our Web sites ( and for the latest migration information. C. Migration Tivoli Data Protection for R/3 User s Guide 157

176 Steps for Migration from Tivoli Data Protection for R/3 Version 2.7 to Version Start a backup of the offline redo logs and then do an offline backup of your SAP R/3 database with Tivoli Data Protection for R/ Create a new node in your Tivoli Storage Manager server for Tivoli Data Protection for R/3 3.2 backups. 3. If your current API client level is lower than or you have an HP-UX environment, keep your old API client install package. 4. Copy the following files of your Tivoli Data Protection for R/3 2.7 environment to a secure destination: UNIX backint backagent init<sid>.utl init<sid>.bki Windows NT backint.exe backagent.exe init<sid>.utl init<sid>.bki 5. Upgrade your API client to version Install Tivoli Data Protection for R/3 version 3.2 on your SAP R/3 database server (see Setting Up Tivoli Data Protection for R/3 on page 31). 7. Set the Tivoli Data Protection for R/3 Tivoli Storage Manager password for the new node you created in item (2) above. 8. Start an offline backup of your SAP R/3 database with Tivoli Data Protection for R/3 version 3.2 in order to have at least one 158 Version 3 Release 2

177 database backup with this new level of Tivoli Data Protection for R/3 before you go into production. 9. Be aware, that having done the migration steps mentioned above - depending on your retention strategy - at a later point of time cleanup work should be performed in order to free up resources (e.g., tape volumes) still utilized by Tivoli Data Protection for R/3. This cleanup requires you to delete: Tivoli Data Protection for R/3 filespaces within Tivoli Storage Manager (sapdba, bkimux) Tivoli Data Protection for R/3 Tivoli Storage Manager node Tivoli Data Protection for R/3 2.7 executables and profiles (see item 4 above) Restore/Recovery of a Backup Made with Tivoli Data Protection for R/3 Version 2.7 (Fallback): The following procedure describes the situation where there is a need: To restore/recover the database with objects that were backed up with a Tivoli Data Protection for R/3 release lower than 3.1 and to perform such a restore/recovery, using offline redo logs backed up with Tivoli Data Protection for R/3 version 3.1 or higher. 1. Restore all offline redo logs backed up with Tivoli Data Protection for R/3 version 3.1 or higher since your last full backup taken with Tivoli Data Protection for R/3 version If the level was lower than 3.7.2, or you have an HP-UX environment, activate the old API client, which you have kept, as explained above in 3 on page Copy the following files of your Tivoli Data Protection for R/3 3.2 environment, to be replaced after the restore/recovery has been completed, to a secure destination: C. Migration Tivoli Data Protection for R/3 User s Guide 159

178 init<sid>.utl init<sid>.bki 4. Copy the Tivoli Data Protection for R/3 2.7 files you have kept (as explained above in Steps for Migration item 4) to their original location : For UNIX: cp backint /usr/sap/sid/sys/exe/run cp backagent /usr/sap/sid/sys/exe/run cp init<sid>.utl /oracle/sid/dbs cp init<sid>.bki /oracle/sid/dbs For Windows NT: copy backint.exe <drive>:\usr\sap\sid\sys\exe\run copy backagent.exe <drive>:\usr\sap\sid\sys\exe\run copy init<sid>.utl <drive>:\orant\database copy init<sid>.bki <drive>:\orant\database 5. Start the restore/recovery of the appropriate database backup. 6. Now, you should reactivate the Tivoli Data Protection for R/3 version 3.2 and the appropriate API client level. For this purpose, copy the following files of version 3.2 to the paths shown below. For UNIX: cp init<sid>.utl /oracle/sid/dbs cp init<sid>.bki /oracle/sid/dbs For Windows NT: copy init<sid>.utl <drive>:\orant\database copy init<sid>.bki <drive>:\orant\database On UNIX systems create a soft link called backint in the SAP R/3 executables path as follows: ln -s /usr/tivoli/tsm/tdp_r3/backint /usr/sap/sid/sys/exe/run/backint 7. It is recommended that you start an offline backup of the database again after the reactivation of Tivoli Data Protection for R/3 version Version 3 Release 2

179 D Password Handling Consider the following alternatives with their implications: No password required by Tivoli Storage Manager (AUTHENTICATION OFF) This is the simplest method; however, no security can be enforced. Every user connected to this server (authentication is set OFF on the Tivoli Storage Manager server level) can access Tivoli Storage Manager without a password. This method is only recommended if adequate security measures can be established otherwise, for example, if Tivoli Storage Manager is only used for SAP R/3 (no other clients are registered), and the respective authorizations are set in the UNIX system. Manual password generation This method is simple to set up and provides password security, however, it requires a synchronized update of the password in Tivoli Storage Manager (client) and Tivoli Data Protection for R/3 (command line). This method is only recommended during installation and testing together with a sufficiently long expiration period (to avoid having to change the password). It is not recommended for production operation. Password set by Tivoli Storage Manager In this case you do not have to synchronize the passwords manually on the Tivoli Storage Manager server and client sides. The generation and synchronization of passwords is Tivoli Data Protection for R/3 User s Guide 161 D. Password Handling

180 handled by a Tivoli Storage Manager program. Tivoli Storage Manager sets the password automatically on a per node basis according to the expiration specification. This method is recommended for an automated production environment. 162 Version 3 Release 2

181 Configuration Matrix (UNIX) After you have selected the suitable password handling alternative, please follow the configuration matrix to set the keywords/parameters in the different profiles accordingly. Proceed as indicated by the step number. Table 7. Password Handling for UNIX Step Profile/Action Parameter Password No Manual Set by Tivoli Storage Manager 1 Tivoli Storage Manager admin AUTHENTICATION EXPIRATION PERIOD (see note 1) 2 dsm.sys PASSWORDACCESS PASSWORDDIR (see note 5) NODENAME 3 Tivoli Storage Manager client (root user) 4 Tivoli Data Protection for R/3 profile init<sid>.utl 5 Tivoli Data Protection for R/3 cmd line OFF n.a. n.a. n.a. n.a. ON <n days> (see note 2) PROMPT n.a. n.a. SET PASSWORD n.a. <password> (see note 3) For each SERVER statement specify: PASSWORDREQUIRED ADSMNODE For each SERVER statement specify: backint -p initsid.utl -f password See Password Handling on page 51. NO <nodename> n.a. YES <nodename> <password> (see note 1) ON <n days> GENERATE <path> <nodename> n.a. NO (see note 4) <password> Notes: 1. The expiration period applies to a Tivoli Storage Manager server and affects all its clients. Tivoli Data Protection for R/3 User s Guide 163 D. Password Handling

182 2. If you are using manual password generation during testing, make sure that the expiration period is set to a sufficiently long time (> 60 days). 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 in the Tivoli Storage Manager server, and next in the Tivoli Data Protection for R/3 product. 4. ADSMNODE must not be set when NODENAME is set. 5. The user <SID>adm and ora<sid> must have read and write permission for the path specified. Configuration Matrix (Windows NT) After you have selected the suitable password handling alternative, please follow the configuration matrix to set the keywords/parameters in the different profiles accordingly. Proceed as indicated by the sequence number under step. Table 8. Password Handling for Windows NT Step Profile/Action Parameter Password No Manual Set by Tivoli Storage Manager 1 Tivoli Storage Manager admin AUTHENTICATION EXPIRATION PERIOD (see note 1) 2 <server>.opt PASSWORDACCESS PASSWORDDIR (see note 5) NODENAME 3 Tivoli Storage Manager client OFF n.a. n.a. n.a. n.a. ON <n days> (see note 2) PROMPT n.a. n.a. SET PASSWORD n.a. <password> (see note 3) ON <n days> GENERATE <path> <nodename> n.a. 164 Version 3 Release 2

183 Table 8. Password Handling for Windows NT (continued) Step Profile/Action Parameter Password No Manual Set by Tivoli Storage Manager 4 Tivoli Data Protection for R/3 profile init<sid>.utl 5 Tivoli Data Protection for R/3 cmd line For each SERVER statement specify: PASSWORDREQUIRED ADSMNODE For each SERVER statement specify: backint -p initsid.utl -f password See Password Handling on page 51. NO <nodename> n.a. YES <nodename> <password> (see note 1) NO (see note 4) <password> Notes: 1. The expiration period applies to a Tivoli Storage Manager server and affects all its clients. 2. If you are using manual password generation during testing, make sure that the expiration period is set to a sufficiently long time (> 60 days). 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 in the Tivoli Storage Manager server, and next in the Tivoli Data Protection for R/3 product. 4. ADSMNODE must not be set when NODENAME is set. 5. The user <SID>adm and sapservice<sid> must have read and write permission for the path specified. Tivoli Data Protection for R/3 User s Guide 165 D. Password Handling

184 166 Version 3 Release 2

185 E Alternate/Parallel Backup Paths and Backup Servers With Tivoli Data Protection for R/3 we use the term path to denote a connection between a Tivoli Storage Manager client, or better ADSM node, and a Tivoli Storage Manager server. Tivoli Data Protection for R/3 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: Increase throughput by transferring data: v Over multiple paths simultaneously v To and from several servers in parallel Increase the availability of the Tivoli Storage Manager client-to-server communication 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 Tivoli Data Protection for R/3 Profile for UNIX on page 185) and the corresponding definitions in the Tivoli Storage Manager client system option file dsm.sys (UNIX) or <server>.opt (Windows NT). The statement SERVER <server 1..n> denotes Tivoli Storage Manager servers in the Tivoli Data Protection for R/3 profile. This Tivoli Data Protection for R/3 User s Guide 167 E. Backup Paths and Servers

186 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 Tivoli Data Protection for R/3 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). Tivoli Data Protection for R/3 tries to communicate with the Tivoli Storage Manager server using the first path in the profile. If this proves successful, Tivoli Data Protection for R/3 starts the number of parallel sessions as specified for this path; if the attempt was unsuccessful, this path is skipped, and Tivoli Data Protection for R/3 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), Tivoli Data Protection for R/3 terminates the backup job. Parameter Settings - SERVER Statement The SERVER statement appears in the Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3 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. 168 Version 3 Release 2

187 Table 9. SERVER Statement and Appropriate Profile and Option File Settings. Configuration possibilities single path; no password or manual password single path; automatic password by Tivoli Storage Manager several paths/servers; no password or manual password several paths/servers; automatic password by Tivoli Storage Manager Tivoli Data Protection for R/3 profile init<sid>.utl SERVER ADSMNODE SERVER ADSMNODE <server> <node> Note 1. <server> must not be specified SERVER <server 1> ADSMNODE <node 1> v v v SERVER <server n> ADSMNODE <node n> SERVER <server 1> ADSMNODE must not be specified v v v SERVER <server n> ADSMNODE must not be specified Tivoli Storage Manager client option file dsm.sys or <server>.opt Note 2. SERVERNAME <server> TCPSERVERADDRESS <address> NODENAME must not be specified SERVERNAME <server> NODENAME <node> TCPSERVERADDRESS <address> SERVERNAME <server 1> NODENAME must not be specified TCPSERVERADDRESS <address 1> v v v SERVERNAME <server n> NODENAME must not be specified TCPSERVERADDRESS <address n> SERVERNAME <server 1> NODENAME <node 1> TCPSERVERADDRESS <address 1> v v v SERVERNAME <server n> NODENAME <node n> TCPSERVERADDRESS <address n> Notes: 1. The host name is used if ADSMNODE is not specified. 2. Under UNIX dsm.sys is the single client option file for all Tivoli Storage Manager servers, under Windows NT there is a separate client option file <server>.opt for each Tivoli Storage Manager server. Tivoli Data Protection for R/3 User s Guide 169 E. Backup Paths and Servers

188 EXAMPLE 1: Use of Alternate/Parallel Paths for Increased Availability Assume the following configuration: Tivoli Storage Manager server with: v 2 tape drives v 2 LAN connections: Fast Ethernet (TCP/IP address yyy.yyy.yyy.yyy) Token Ring (TCP/IP address xxx.xxx.xxx.xxx) SAP R/3 database server connected to Token Ring and Ethernet. Backup is normally performed using the Token Ring LAN (SERVER statement 1). If the Token Ring is down, the backup should still be performed using the Token Ring connection (SERVER statement 2), although data transfer will take longer. The definitions in the Tivoli Data Protection for R/3 profile could be as shown in the example below. If path 1 is active, Tivoli Data Protection for R/3 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, Tivoli Data Protection for R/3 will start 2 sessions on path 2. Since this equals the MAX_SESSIONS definition as well, backup will be executed using path Version 3 Release 2

189 Tivoli Data Protection for R/3 profile. Example 1 MAX_SESSIONS 2 # 2 tape drives.. SERVER server_a # via Fast ethernet ADSMNODE C21 SESSIONS 2 PASSWORDREQUIRED YES BRBACKUPMGTCLASS mdb BRARCHIVEMGTCLASS mlog1 mlog2 # USE_AT SERVER server_b # via Token Ring ADSMNODE C21 SESSIONS 2 PASSWORDREQUIRED YES BRBACKUPMGTCLASS mdb BRARCHIVEMGTCLASS mlog1 mlog2 # USE_AT Tivoli Data Protection for R/3 User s Guide 171 E. Backup Paths and Servers

190 EXAMPLE 2: Use of Alternate/Parallel Paths for Increased Performance Assume the following configuration: Two Tivoli Storage Manager servers with connections to two FDDI networks: v server_a, TCP/IP address xxx.xxx.xxx.xxx v server_b, TCP/IP address yyy.yyy.yyy.yyy v Each of these servers has: two tape drives An SAP R/3 database server connected to two FDDI networks. Backups are done on both systems every day. The definitions in the Tivoli Data Protection for R/3 profile could be as shown in the example below. Tivoli Data Protection for R/3 profile. Example 2 MAX_SESSIONS 4# 4tape drives.. SERVER server_a # via FDDI ADSMNODE C21 SESSIONS 2 PASSWORDREQUIRED YES BRBACKUPMGTCLASS MDB BRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4 # USE_AT SERVER server_b # via FDDI ADSMNODE C21 SESSIONS 2 PASSWORDREQUIRED YES BRBACKUPMGTCLASS MDB BRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4 # USE_AT Version 3 Release 2

191 EXAMPLE 3: Use of Alternate/Parallel Servers for Disaster Recovery Assume the following configuration: Two Tivoli Storage Manager servers with connections to an FDDI network: v server_a, TCP/IP address xxx.xxx.xxx.xxx v server_b, TCP/IP address yyy.yyy.yyy.yyy Each of these servers with: v four tape drives (MAX_SESSIONS 4). An SAP R/3 database server connected to this FDDI network. Normal backups are to be performed with server a, which is local to the R/3 DB server. Every Friday a disaster recovery backup should be stored on a remote Tivoli Storage Manager server (server b). The definitions in the Tivoli Data Protection for R/3 profile could be as shown in the example below. Tivoli Data Protection for R/3 User s Guide 173 E. Backup Paths and Servers

192 Tivoli Data Protection for R/3 profile. Example 3 MAX_SESSIONS 4# 4tape drives.. SERVER server_a # via FDDI ADSMNODE C21 SESSIONS 4 PASSWORDREQUIRED YES BRBACKUPMGTCLASS MDB BRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4 USE_AT SERVER server_b # via FDDI ADSMNODE C21 SESSIONS 4 PASSWORDREQUIRED YES BRBACKUPMGTCLASS MDB BRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4 USE_AT 5 # for Disaster Recovery 174 Version 3 Release 2

193 F The Tivoli Data Protection for R/3 Profile This section describes the Tivoli Data Protection for R/3 profile, which is used to customize the way Tivoli Data Protection for R/3 operates. A sample profile initsid.utl is provided on the installation medium. The installation procedure for UNIX 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 NT 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. Tivoli Data Protection for R/3 reads the profile before it executes. The following rules apply to the syntax: Every line is analyzed separately. Keywords can start in any column of the line. Keywords must not be preceded by any string, except blanks. If a keyword is encountered several times, the last one is used. File processing ends when the END keyword is encountered or the end of file is reached. All keywords must be in upper case. Tivoli Data Protection for R/3 User s Guide 175 F. The Tivoli Data Protection for R/3 Profile

194 The comment symbol is #. Scanning of the current line stops when the comment symbol is encountered. It is not allowed to put a comment 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 ADSMNODE ORACLE_sid 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 Oracle database system. It should be used if you have several SAP R/3 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 the corresponding SERVER statement. BACKEND pgmname [parameterlist...] Specifies a program pgmname that is called by Tivoli Data Protection for R/3 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): 176 Version 3 Release 2

195 BACKEND write R3 Backup is completed. This sends a message to a remote user when the backup has finished. BACKUPIDPREFIX 6charstring SAP Specifies a 6 character long prefix that is used to build a backup identifier for each archived object. The total length of the backup ID is 16 characters. Tivoli Data Protection for R/3 automatically fills up the remaining 10 characters with a time stamp. The backup ID is needed by the SAP backup utilities. They are stored in the SAP backup protocols and in the description field of the archived data objects in Tivoli Storage Manager. If you do not specify a prefix, the default SAP is used ( = 3 underscores). A typical backup ID is SAP , which reads: 18th September, 1998, time 23:00. BATCH YESNO Specify NO if Tivoli Data Protection for R/3 is running with an operator standing by. Specify YES if Tivoli Data Protection for R/3 is running in unattended mode. In this mode Tivoli Data Protection for R/3 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 commented out in the Tivoli Data Protection for R/3 profile. This keyword has no effect if an RMAN backup/restore is started. BRARCHIVEMGTCLASS management_class [management_class...] Specifies the Tivoli Storage Manager management class(es) Tivoli Data Protection for R/3 uses when called from BRARCHIVE. Each parameter string can consist of up to 30 characters. Tivoli Data Protection for R/3 User s Guide 177 F. The Tivoli Data Protection for R/3 Profile

196 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). This keyword has no effect if an RMAN backup/restore is started. For more detailed information about implementing and using BRARCHIVEMGTCLASS see Tips and Hints for BRARCHIVE on page 207. Keep in Mind This parameter must be defined in the corresponding SERVER statement. BRBACKUPMGTCLASS management_class [management_class...] Specifies the Tivoli Storage Manager management class(es) Tivoli Data Protection for R/3 uses when called using BRBACKUP. The parameter string can consist of up to 30 characters. Keep in Mind This parameter must be defined in the corresponding SERVER statement. BUFFSIZE n This parameter specifies the block size for the buffers passed to the Tivoli Storage Manager API functions. The valid range is from 4096 to Inappropriate values will be adjusted automatically. 178 Version 3 Release 2

197 If not specified the default value is (128 KB) for UNIX systems and (32 KB) for Windows NT. In most cases this parameter has little influence on the performance. CONFIG_FILE path Specifies the configuration file for Tivoli Data Protection for R/3 to store all variable parameters such as passwords, date of last password change, and the current version number. path specifies the full path and the name of the file. This keyword is required. END Specifies the end of the parameter definitions. Tivoli Data Protection for R/3 stops searching the file for keywords when END is encountered. EXITONERROR YESNONUMBER This parameter specifies whether or not Tivoli Data Protection for R/3 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, Tivoli Data Protection for R/3 counts the number of errors (not warnings or retries) and exits after the specified number of errors. This parameter 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. FILE_RETRIES n3 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. This keyword has no effect if an RMAN backup/restore is started. FRONTEND pgmname Specifies a program pgmname that is called by Tivoli Data Protection for R/3 in a backup run before the connection to the Tivoli Storage Manager server is established. pgmname is Tivoli Data Protection for R/3 User s Guide 179 F. The Tivoli Data Protection for R/3 Profile

198 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): 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. This parameter must be specified. 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 n1 Specifies the total number of parallel Tivoli Storage Manager client sessions that Tivoli Data Protection for R/3 establishes. For a direct backup/restore on tape drives, keep the following in mind: The number of sessions must be equal or lower than the number of tape drives available for the backup. For performance reasons, it is recommended to use as many parallel sessions as tape drives available. Note: Make sure that the mountlimit (mountl) parameter in the device class is set to the number of available tape drives. 180 Version 3 Release 2

199 If not specified, the default is MAX_SESSIONS 1. For more detailed information about implementing and using MAX_SESSIONS see Tips and Hints for BRARCHIVE on page 207. Keep in Mind This parameter must correlate to the sum of the number of sessions specified in the SERVER statement. 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. MAX_VERSIONS n0 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 versioning is disabled. Be aware that if you are using VERSIONING you use the same initsid.bki file for BRBACKUP and BRARCHIVE, to avoid an unexpected loss of data. MULTIPLEXING n1 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 compressible a lot and when the CPU load is not too high. We expect optimal values in the range from 1 to 4. Tivoli Data Protection for R/3 User s Guide 181 F. The Tivoli Data Protection for R/3 Profile

200 If not specified the default value of 1 means no multiplexing. This keyword has no effect if an RMAN backup/restore is started. PASSWORDREQUIRED NOYES Specifies if Tivoli Storage Manager requires a password to be supplied by the Tivoli Storage Manager client. This depends on the Tivoli Storage Manager installation. For more information see the Tivoli Storage Manager administrators manuals. If not specified the default is PASSWORDREQUIRED YES. Keep in Mind This parameter must be defined in the corresponding SERVER statement. REDOLOG_COPIES n1 Specifies the number of copies Tivoli Data Protection for R/3 stores for each processed Oracle redo log. If not specified, Tivoli Data Protection for R/3 stores only one copy for the redo logs. Note The number of different BRARCHIVE management classes specified (parameter BRARCHIVEMGTCLASS) must be larger than or equal to the number of redo log copies specified. This keyword has no effect if an RMAN backup/restore is started. For more detailed information about implementing and using REDOLOG_COPIES see Tips and Hints for BRARCHIVE on page Version 3 Release 2

201 REPORT NOYES2 If set to YES, Tivoli Data Protection for R/3 produces some additional information, for example, transferred files. If set to 2, Tivoli Data Protection for R/3 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 NOYES If set to YES Tivoli Data Protection for R/3 performs a null block compression of the data before they are sent over the network. Although the null block compression introduces a small additional CPU load, in most cases it will improve the throughput. If not specified the default value is NO meaning null block compression is not performed. Note RL_COMPRESSION will only be performed if a full database backup (BRBACKUP) was started. The offline redo logs (BRARCHIVE) will not be compressed. SERVER servername Denotes the name of the Tivoli Storage Manager server, to which a path with the subsequent definitions will be established. For alternate paths each path must have its own (logical) server name, even if they refer to one and the same real server (same TCP/IP address for all server names). For alternate servers there must be different TCP/IP addresses for each of the different (real) Tivoli Storage Manager servers. Tivoli Data Protection for R/3 User s Guide 183 F. The Tivoli Data Protection for R/3 Profile

202 SESSIONS n1 n specifies the number of parallel sessions Tivoli Data Protection for R/3 can start for this server. If not specified, the default is SESSIONS 1. Keep in Mind This parameter must be defined in the corresponding SERVER statement. SNMPTRAP hostname community level hostname specifies the name of the machine to which the log messages are to be sent. This parameter must be specified community is the first level which filters messages. You can define your own community. The default is public. level may be one of the following: ERROR, WARNING, or DETAIL. This value determines which messages are sent. ERROR sends only error messages, WARNING sends error and warning messages and DETAIL sends all message types (errors, warnings and informational messages). TRACE OFFON If set to ON, Tivoli Data Protection for R/3 writes trace information into a file called BKItrace within the directory of the caller of Tivoli Data Protection for R/3. Between KB of disk space per call of Tivoli Data Protection for R/3 are required. Note: This parameter should only be used if your Tivoli Data Protection for R/3 support asks you to. If not specified, the default is TRACE OFF. TRACEFILE pathstdout Specifies the trace file for Tivoli Data Protection for R/3 to store all trace information (if TRACE ON), path specifies the full path and the name of file. 184 Version 3 Release 2

203 Note: In an actual trace the string %BID will be replaced by the Backup ID. If not specified, the default is TRACEFILE stdout. USE_AT days Specifies on which days to use this Tivoli Storage Manager server. The days are numbered from 0 (Sunday) to 6 (Saturday). If not specified, the default is to use the Tivoli Storage Manager server on all days. Keep in Mind This parameter must be defined in the corresponding SERVER statement. The following profile keywords are obsolete for Tivoli Data Protection for R/3 version 3.1 and higher: ADSMBUFFSIZE BACKAGENT DISKBUFFSIZE PERF_MONITOR RETRY TCPWAIT TRACEMAX Sample Tivoli Data Protection for R/3 Profile for UNIX This sample Tivoli Data Protection for R/3 profile initsid.utl is included in the Tivoli Data Protection for R/3 installation package. The UNIX and Windows NT versions are identical except for small differences due to naming conventions. Therefore only the UNIX version is shown here. # # # BM Tivoli Data Protection for R/3 interface for R/3 for Oracle # # Sample profile for Tivoli Data Protection for R/3 3.2 for UNIX Tivoli Data Protection for R/3 User s Guide 185 F. The Tivoli Data Protection for R/3 Profile

204 # # # # 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 'Program Description and Installation' manual for a full # description. # # For comment symbol the character '#' can be used. # Everything following this character will be interpreted as comment. # # Tivoli Data Protection for R/3 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. # Default: SAP. Maximum 6 characters. # BACKUPIDPREFIX SAP # # Number of total parallel sessions which will be established by # Tivoli Data Protection for R/3. # Note: this number should correspond with the number # of simultaneously available tape drives specified for the Tivoli Storage # Manager server. # Default: 1. # MAX_SESSIONS 1 # 1 Tivoli Storage Manager client session is default # # Number of parallel sessions which will be established by # Tivoli Data Protection for R/3 for the database backup. # Note: this number should correspond with the number of simultaneously # available tape drives specified for the Tivoli Storage Manager server. # Default: 1. # #MAX_BACK_SESSIONS 1 # 1 Tivoli Storage Manager client session for backup # # Number of parallel sessions which will be established by 186 Version 3 Release 2

205 # Tivoli Data Protection for R/3 for the archive log backup. # Note: this number should correspond with the number of simultaneously # available tape drives specified for the Tivoli Storage Manager server. # Default: 1. # #MAX_ARCH_SESSIONS 1 # 1 Tivoli Storage Manager client session for archive # # Number of parallel sessions which will be established by # Tivoli Data Protection for R/3 for the restore of files. # Note: this number should correspond with the number of simultaneously # available tape drives specified for the Tivoli Storage Manager server. # Default: 1. # #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 Tivoli Data Protection for R/3 should perform a # null block compression of the data before they are transmitted over the # network to Tivoli Storage Manager. The null block compression consumes # only little CPU resources. This compression in # Tivoli Data Protection for R/3 is independent from the Tivoli Storage Manager compressi # Do not compress twice! # 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 useful 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 data transfer (in bytes). The valid range is Tivoli Data Protection for R/3 User s Guide 187 F. The Tivoli Data Protection for R/3 Profile

206 # from 4KB to 256 KB. # The default values have been chosen from our performance experiments in # standard hardware environments. # Default: (128 KB) on UNIX, (32 KB) on Windows NT. # #BUFFSIZE # block size in bytes # # Name of a program that is called by Tivoli Data Protection for R/3 # before the backup task is started. # Default: none. # #FRONTEND pgmname parameterlist # # Name of a program that is called by Tivoli Data Protection for R/3 # 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 Tivoli Data Protection for R/3 is only # activated if the SAP R/3 release is 3.0C and higher and the parameter # MAX_VERSIONS is not 0. # Default: 0. # #MAX_VERSIONS 10 # # 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 NO # don't exit if an error occurs 188 Version 3 Release 2

207 # # 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: NO. # #TRACE YES # # Specify the trace file for Tivoli Data Protection for R/3 to store all # trace information (if TRACE ON), full path and name of file. # Note: for an actual trace the string '%BID' will be replaced by # the current backupid. # (...\/backint_%bid.trace changes to.../backint_sap trace). # Default: stdout. # #TRACEFILE /oracle/c21/dbs/backint_%bid.trace #TRACEFILE /oracle/c21/dbs/backint.trace # # Specify the configuration file for Tivoli Data Protection for R/3 to # store all variable parameters, full path and name of the file. # Default: '%ORACLE_HOME%/database/init%ORACLE_SID%.bki # CONFIG_FILE /oracle/c21/dbs/initc21.bki # # Number of times Tivoli Data Protection for R/3 retries to save/restore # a file in case an error occurs. # Default: 3. # #FILE_RETRIES 3 # # Shall Tivoli Data Protection for R/3 send error/status information # to a Tivoli Storage Manager server. The statement for servername must Tivoli Data Protection for R/3 User s Guide 189 F. The Tivoli Data Protection for R/3 Profile

208 # match one of the servers listed in a SERVER statement. Statements for # verbosity can be ERROR, WARNING, or DETAIL (default is WARNING). # Default: none. # #LOG_SERVER servername [verbosity] #LOG_SERVER server_a WARNING # # Shall Tivoli Data Protection for R/3 send error/status information # to a network management program via SNMP traps? # Default: none. # #SNMPTRAP Hostname community level #SNMPTRAP server_b public DETAIL #************************************************************************** # 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 C21 # Tivoli Storage Manager Nodename BRBACKUPMGTCLASS mdb # Mgmt-Classes BRARCHIVEMGTCLASS mlog1 mlog2 # Mgmt-Classes # USE_AT # Days for backup #SERVER server_b # SESSIONS 1 # PASSWORDREQUIRED YES # ADSMNODE C21 # BRBACKUPMGTCLASS mdb # BRARCHIVEMGTCLASS mlog1 mlog2 # USE_AT #************************************************************************** # USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa # Default: all days #************************************************************************** # # End of profile END 190 Version 3 Release 2

209 G Sample Tivoli Storage Manager Profiles (UNIX) Client User Options File Sample (dsm.opt) ************************************************************************ * Tivoli Distributed Storage Manager * * * * Sample Client User Options file for AIX and SunOS * ************************************************************************ SErvername Replace Tapeprompt DOM server_a On No /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 Tivoli Data Protection for R/3 User s Guide 191 G. Sample Tivoli Storage Manager Profiles (UNIX)

210 Include/Exclude List Sample * * inclexcl.list: * Sample include/exclude list * * Task: * Include/Exclude list of files and directories for Tivoli Storage Manager * 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 file system 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/c21/saparch/.../* * exclude /oracle/c21/sapbackup/.../* * exclude /oracle/c21/sapreorg/.../* (There may be important scripts 192 Version 3 Release 2

211 * located, check it out and decide.) exclude /oracle/c21/sapdata*/.../* exclude /oracle/c21/sapraw*/.../* * * * With the above include/exclude list we implicitly include everything not * excluded above. Especially for SAP R/3 this means including: * /sapmnt/c21 > 270 MB * /usr/sap > 14MB * /oracle/stage > 89 MB * /oracle/c21 > 90 MB * and AIX related > 220 MB * * * Attn. Depending on your SAP R/3 release * and your database layout it might be * necessary to add additional * 'exclude /oracle/c21/sapdata...' * statements. Check the BRBACKUP run * for additional files/directories you * want to exclude. * Tivoli Data Protection for R/3 User s Guide 193 G. Sample Tivoli Storage Manager Profiles (UNIX)

212 194 Version 3 Release 2

213 H Sample Tivoli Storage Manager Profiles (Windows NT) 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. ********************************************************************** * Tivoli Distributed Storage Manager * * * * Sample Client User Option file for Windows NT * ********************************************************************** Replace Tapeprompt DOM InclExcl On No c:\oracle\c21 c:\win32app\ibm\tsm\baclient\inclexcl.sample Client Options Files Sample (<server>.opt) Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3. ************************************************************************* * * SERVER.OPT Tivoli Data Protection for R/3 User s Guide 195 H. Sample Profiles (Windows NT)

214 * * Tivoli Data Protection for R/3 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 TCPBUFFSIZE 31 TCPWINDOWSIZE 32 ************************************************************************* * * DSM.OPT (for Tivoli Data Protection for R/3) * * Tivoli Data Protection for R/3 requires that a file 'dsm.opt' is * present, although its contents is ignored by * Tivoli Data Protection for R/3 This means that this file could be * empty (like here). * The information about a Tivoli Storage Manager server * is obtained from the corresponding client option file <server>.opt. * * Tivoli Data Protection for R/3 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. ************************************************************************* 196 Version 3 Release 2

215 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 Tivoli Data Protection for R/3. Mainly such files are Windows NT 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 * Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3. * ************************************************************************* Exclude *:\...\*.swp Exclude *:\...\*.obj Exclude *:\...\*.csm Exclude *:\...\*.dsk Exclude *:\...\*.bak Exclude *:\...\win386.swp Exclude *:\...\386spart.par Exclude *:\...\pagefile.sys Exclude *:\...\*.par Exclude *:\...\SYSTEM32\CONFIG\*.* Exclude *:\...\SYSTEM32\CONFIG\...\* Exclude *:\IBMBIO.COM Exclude *:\IBMDOS.COM * *Exclude the following Oracle database files: * Exclude *:\oracle\c21\saparch\...\* Exclude *:\oracle\c21\sapbackup\...\* Exclude *:\oracle\c21\sapreorg\...\* Exclude *:\oracle\c21\sapdata*\...\* Tivoli Data Protection for R/3 User s Guide 197 H. Sample Profiles (Windows NT)

216 198 Version 3 Release 2

217 I Elements of Backup Schedules (UNIX) Under UNIX, 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) Tivoli Data Protection for R/3 User s Guide 199 I. Elements of Backup Schedules (UNIX)

218 # 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 # Tivoli Data Protection for R/3. # # ***** NOTE ***** NOTE ***** NOTE ***** # # This script is intended only as a model and should be # carefully tailored to the needs of the specific site. # # ***** NOTE ***** NOTE ***** NOTE ***** # # # For the following examples, the system ID of the Oracle database # is assumed to be "C21". # # Version 3 Release 2

219 # # 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 # /oracle/c21/sapdata2 # /oracle/c21/sapdata3 # /oracle/c21/sapdata4 # /oracle/c21/sapdata5 # /oracle/c21/sapdata6 # 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 Tivoli Data Protection for R/3 # util_par_file = initc21.utl # Tivoli Data Protection for R/3 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, # Tivoli Data Protection for R/3) 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 # carefully tailored to the needs of the specific site. # # ***** NOTE ***** NOTE ***** NOTE ***** # # # Remarks on the parameters of BRARCHIVE: Tivoli Data Protection for R/3 User s Guide 201 I. Elements of Backup Schedules (UNIX)

220 # # -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 Tivoli Data Protection for R/3 # util_par_file = initc21.utl # Tivoli Data Protection for R/3 profile # # COMMAND brarchive -u system/manager -sd -c 202 Version 3 Release 2

221 J Elements of Backup Schedule (Windows NT) To start jobs on a Windows NT system at predefined times, it is necessary to have the Schedule service running. It is started with: net start schedule After the Schedule service is running, jobs are scheduled with the at command. In the example below two jobs backup.cmd and archive.cmd are started. They simply use the SAP tools BRBACKUP and BRARCHIVE to save the data. Schedule Batch 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 ***** NOTE ***** NOTE ***** NOTE ***** rem rem For a full reference of the AT command please see the Windows NT rem help. rem Tivoli Data Protection for R/3 User s Guide 203 J. Elements of Backup Schedule (Windows NT)

222 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 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 Tivoli Data Protection for R/3. rem rem ***** NOTE ***** NOTE ***** NOTE ***** rem rem This script is intended only as a model and should be rem carefully tailored to the needs of the specific site. rem rem ***** NOTE ***** NOTE ***** NOTE ***** rem rem rem For the following examples, the system ID of the 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 c:\oracle\c21\sapdata2 rem c:\oracle\c21\sapdata3 rem c:\oracle\c21\sapdata4 rem c:\oracle\c21\sapdata5 204 Version 3 Release 2

223 rem c:\oracle\c21\sapdata6 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 Tivoli Data Protection for R/3 rem util_par_file = %ORACLE_HOME%\database\initC21.utl rem Tivoli Data Protection for R/3 profile rem COMMAND brbackup -u system/manager -c -m all -t offline Save and Delete Redo Logs Batch File 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 Tivoli Data Protection for R/3) and deletes the redo logs from their rem original location. rem After completing this, the BRARCHIVE protocol is saved separately. rem rem ***** NOTE ***** NOTE ***** NOTE ***** rem rem This script is intended only as a model and should be rem carefully tailored to the needs of the specific site. rem rem ***** NOTE ***** NOTE ***** NOTE ***** rem rem rem 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, Tivoli Data Protection for R/3 User s Guide 205 J. Elements of Backup Schedule (Windows NT)

224 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 Tivoli Data Protection for R/3 rem util_par_file = %ORACLE_HOME%\database\initC21.utl rem Tivoli Data Protection for R/3 profile rem COMMAND brarchive -u system/manager -sd -c 206 Version 3 Release 2

225 K Tips and Hints for BRARCHIVE For a BRARCHIVE run there are two important parameters in the Tivoli Data Protection for R/3 profile: BRARCHIVEMGTCLASS and REDOLOG_COPIES. 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. 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. Tivoli Data Protection for R/3 User s Guide Note A Tivoli Storage Manager management class used by Tivoli Data Protection for R/3 defines v v 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 207 K. Tips and Hints for BRARCHIVE

226 Be aware that Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3. One BRARCHIVE run might trigger via Tivoli Data Protection for R/3 several simultaneously running backup sessions. 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 Tivoli Data Protection for R/3. 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 208 Version 3 Release 2

227 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: automatically by the Tivoli Storage Manager server (see HIGHMIG/LOWMIG values) or 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 with brarchive -sd -c or Tivoli Data Protection for R/3 User s Guide 209 K. Tips and Hints for BRARCHIVE

228 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 Tivoli Data Protection for R/3 to create different backup IDs for the two BRARCHIVE runs. For a better alternative see example 1 on page 214. 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. Tivoli Data Protection for R/3 satisfies the BRARCHIVE request to back up redo log files according to the following rules: 1. Tivoli Data Protection for R/3 produces as many backup copies of each redo log file as are specified with the REDOLOG_COPIES value. 2. Tivoli Data Protection for R/3 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, Tivoli Data Protection for R/3 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), Tivoli Data Protection for R/3 cannot access all BRARCHIVE management classes simultaneously. This means Tivoli Data Protection for R/3 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 210 Version 3 Release 2

229 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. Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3 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. Tivoli Data Protection for R/3 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 212) 6. In case of problems, Tivoli Data Protection for R/3 retries to save the file several times. Tivoli Data Protection for R/3 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 212) 7. Tivoli Data Protection for R/3 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. Tivoli Data Protection for R/3 User s Guide 211 K. Tips and Hints for BRARCHIVE

230 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 Tivoli Data Protection for R/3 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. 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, BRARCHIVE does not wait until all redo log files have been backed-up before starting to delete them. Whenever it receives notification from Tivoli Data Protection for R/3 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 Tivoli Data Protection for R/3 as completed. 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. 212 Version 3 Release 2

231 In order to avoid an unnecessary workload on the SAP Oracle database machine, Tivoli Data Protection for R/3 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: many unwanted tape mounts, thus creating long BRARCHIVE runs and under certain circumstances, an unsuccessful termination of the BRARCHIVE (or other BRBACKUP) run 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: Tivoli Data Protection for R/3 User s Guide 213 K. Tips and Hints for BRARCHIVE

232 1. MAX_SESSIONS 1, REDOLOG_COPIES 2. Two different BRARCHIVEMGTCLASS management classes. Only one Tivoli Data Protection for R/3 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). 2. MAX_SESSIONS 2, REDOLOG_COPIES 2. Two different BRARCHIVEMGTCLASS 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). 3. MAX_SESSIONS 4, REDOLOG_COPIES 2. Two different BRARCHIVEMGTCLASS management classes. 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. 214 Version 3 Release 2

233 4. MAX_SESSIONS 4, REDOLOG_COPIES 4. Four different BRARCHIVEMGTCLASS management classes. This is a very unlikely example for a real production environment. Here, Tivoli Data Protection for R/3 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. Tivoli Data Protection for R/3 User s Guide 215 K. Tips and Hints for BRARCHIVE

234 216 Version 3 Release 2

235 Glossary A B Activate The process of validating the contents of a policy set and copying the policy set to the ACTIVE policy set. Active policy set The policy set that contains the policy rules currently in use by all client nodes assigned to the policy domain. The active policy set is the policy set that was most recently activated for the policy domain. Administration Assistant A Web browser based graphical interface to support and assist the customizing of Tivoli Data Protection for R/3 (System Configuration) and the analyzing of SAP R/3 database backup and restore operations (Operations Monitor, Performance Monitor). Administrative client A program that runs on a file server, workstation, or mainframe that allows administrators to control and monitor the Tivoli Storage Manager server through administrator commands. Compare with backup-archive client. Archive copy group A policy object containing attributes that control the generation, destination, and expiration of archive files. An archive copy group belongs to a management class. Backup-archive client A program that runs on a workstation or file server and provides a means for users to back up, archive, restore, and retrieve files. Compare with administrative client. Backup copy group A policy object containing attributes that control the generation, destination, and expiration of backup files. A backup copy group belongs to a management class. BRARCHIVE An SAP database utility to perform backups of offline redo log files in an SAP R/3 Oracle database environment. BRBACKUP An SAP database utility to do online/offline backups of SAP R/3 Oracle databases. BRBACKUP can be used to back up data files, control files and online redo log files. Glossary Tivoli Data Protection for R/3 User s Guide 217

236 BRCONNECT This ensures, that the database status required for the online/offline backup of an SAP R/3 Oracle database remains unchanged during the backup. BRCONNECT will be started only internally by BRBACKUP/BRARCHIVE. BRRESTORE An SAP database utility to restore an entire Oracle database backup or parts of it, previously backed up with BRBACKUP or BRARCHIVE. Any non-database files and directories which were saved can also be restored. Subdirectories within the sapdata directories will be created automatically, when necessary. C Client options file A file that a client can change, containing a set of processing options that identify the server, communication method, and options for backup, archive, hierarchical storage management, and scheduling. It is also called dsm.opt file. Client system options file A file, used on UNIX clients, containing a set of processing options that identify the Tivoli Storage Manager servers to be contacted for services. This file also specifies communication methods and options for backup, archive, hierarchical storage management, and scheduling. It is also called dsm.sys file. Control file A file associated with a database that maintains the physical structure and time stamps of all files within that database. The control file is updated continuously during database use and must be available for writing, if the database is mounted or opened. Copy group A policy object that contains attributes that control the generation, destination, and expiration of backup and archive files. There are two kinds of copy groups: backup and archive. Copy groups belong to management classes. D Datablock The smallest unit of a database Datafile A datafile is a physical operating system file on disk, which contains data structures of a database, such as tables and indexes. A datafile only belongs to one database and to one tablespace. 218 Version 3 Release 2

237 Device class A named group of storage devices with common characteristics. Each device class has a unique name and represents a device type of disk, file, optical disk, or tape. DISK A device class that is defined by Tivoli Storage Manager at installation. It is used to categorize disk drives, such as internal disk drives. F File space A logical space in a client s storage that can contain a group of files. Clients can restore, retrieve, or delete their file spaces from Tivoli Storage Manager server storage. Tivoli Storage Manager does not necessarily store all the files from a single file space together, but can identify all the files in server storage that came from a single file space. I Include-exclude list A group of include and exclude option statements in a file. Tivoli Storage Manager uses the statements to determine whether to back up or migrate certain files, and to determine the associated management classes to use for backup, archive, and space management. The exclude options identify files that should not be backed up or migrated off the client node. The include options identify files that are exempt from the exclusion rules, or assign a management class to a file or group of files for backup, archive, or space management services. The include-exclude list is defined either in a include-exclude file (for UNIX clients) or in the client options file (for other clients). M Management class A policy object that users can bind to each file to specify how the server manages the file. The management class can contain a backup copy group, an archive copy group, and space management attributes. The copy groups determine how the Tivoli Storage Manager server manages backup versions or archive copies of files. The space management attributes determine whether files are eligible for migration from space manager client nodes to Tivoli Storage Manager storage, and under what conditions. Media Management API An interface provided by Oracle to which vendors are able to write compatible software libraries. This software integrates with Oracle. Thus, an Oracle server Glossary Tivoli Data Protection for R/3 User s Guide 219

238 process is able to issue commands to the media manager to write backup files out to sequential storage (e.g., Tivoli Storage Manager) and read files from sequential storage. N Node A unique name used to identify a server/workstation (client) to the Tivoli Storage Manager server. O Offline redo log If the database is in ARCHIVELOG mode and an online redo log is filled, it is copied to one (or more) archive log destination(s), which is typically the saparch directory in an SAP R/3 environment. This copy is the offline redo log (also called archived redo log). Online redo log The online redo log is a set of two or more files which record all changes made to Oracle datafiles and control files. P Policy domain A policy object that contains policy sets, management classes, and copy groups that are used by a group of client nodes. Policy set A policy object that contains a group of management class definitions that exist for a policy domain. At any one time there can be many policy sets within a policy domain but only one policy set can be active. R Recovery Manager (RMAN) A tool used to back up, restore and recover Oracle databases. It can be used with or without a Recovery Catalog,. If a Recovery Catalog is not used, Recovery Manager decides how to back up, restore and recover the database using the control file of the database. Incremental backups of Oracle databases can only be done with RMAN. 220 Version 3 Release 2

239 Retention The amount of time, in days, that inactive backed up or archived files are kept in the storage pool before they are deleted. Copy group attributes and default retention grace periods for the domain define retention. S SAP BACKINT interface An interface provided by SAP database utilities BRBACKUP, BRARCHIVE and BRRESTORE that can be used to access external backup programs, for example Tivoli Data Protection for R/3. SAPDBA An SAP database tool to provide and simplify the administration of an Oracle database system within an SAP R/3 environment. SAPDBA provides a collection of database management/administration functions, for example tablespace administration, which can only performed outside of an SAP R/3 system. Scratch volume A volume that is available for Tivoli Storage Manager use. The volume is either labeled, or blank or contains no valid data, and is not defined to Tivoli Storage Manager. Storage pool A storage pool is a named collection of storage volumes that are associated with one device class. Each storage pool represents a collection of volumes that are the same media type. For example, a storage pool that is associated with a device class for 8 mm tape contains only 8 mm tape volumes. T Tablespace A database is divided into one or more logical storage units, which are tablespaces. Each tablespace has a set of datafiles exclusively associated with it. Tivoli Data Protection for R/3 File Manager A utility that simplifies the Tivoli Data Protection for R/3 inquire, restore and delete operations. It can be seen as an add-on to Tivoli Data Protection for R/3. Tivoli Storage Manager A client/server program that provides storage management to customers in a multivendor computer environment. Tivoli Storage Manager API A set of functions that applications running on a client platform can call to store, query, and retrieve objects from Tivoli Storage Manager storage. Glossary Tivoli Data Protection for R/3 User s Guide 221

240 U util_file_online A file (datafile) 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 amount of offline redo log files during an online backup can be reduced significantly. V Validate 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. 222 Version 3 Release 2

241 Index A activate glossary definition 217 active policy set glossary definition 217 Administration Assistant authorizing users 121 customizing slave server 116 glossary definition 217 installing 109 installing server 109 installing slave server 115 Java 108 Netscape 119 overview 105 prerequisites 108 slave server, directories 117 specifying destination directory 113 specifying host name 111 specifying server installation option 115 specifying server ports 110 usage of 122 verification of installation 119 Web browser, remote method invocation 108 administrative client glossary definition 217 ADSMBUFFSIZE 185 ADSMNODE profile keyword 176 alternate/parallel backup paths 10 example for availability 170 example for disaster recovery 173 example for performance 172 reasons to use 167 alternate/parallel backup servers 11 archive copy group glossary definition 217 authorizing Administration Assistant users 121 automatic password handling 51 automating backup and archive operations 83 automation, backup 77 availability improvements with alternate/parallel paths and servers 167 B BACKAGENT 185 BACKEND profile keyword 13, 176 backing up AIX system data 82 Oracle database elements 78 SAP R/3 system data 82 user data 82 BACKINT 2, 55 backup 62 automated 83 BRBACKUP 62 messages 65 online/offline 63 profile & protocol file directories, UNIX 81 profile & protocol file directories, Windows NT 81 profiles 80 protocols 80 SAPDBA 62 scenarios 63 strategy for operating system 78 tablespace 65 backup, examples 88 backup, incremental 4, 12, 151 backup and restore, parallel 6 backup-archive client glossary definition 217 backup automation planning 77 backup by version 8 Index Tivoli Data Protection for R/3 User s Guide 223

242 backup copy group glossary definition 217 backup function 56 Tivoli Storage Manager incremental 82 backup library 4 backup paths alternate/parallel 10 profile examples 167 backup/restore general 55 Backup/Restore, performance optimization 91 compression 101 multiplexing 101 null block compression 101 parallelism 99 SAP R/3 Oracle database backup 99 backup scheduler SAP R/3 84 Tivoli Storage Manager 86 UNIX crontab / Windows NT scheduler 87 backup servers alternate/parallel 11 performance optimization 97 profile examples 167 backup sessions 208 backup strategy planning 77 BACKUPIDPREFIX profile keyword 177 BATCH profile keyword 177 BRARCHIVE 55, 99 glossary definition 217 BRARCHIVEMGTCLASS profile keyword 177 BRBACKUP 55, 99 backup of Oracle database 63 glossary definition 217 BRBACKUPMGTCLASS profile keyword 178 BRCONNECT glossary definition 218 BRRESTORE 55 glossary definition 218 BUFFSIZE profile keyword 102, 178 C client performance optimization 93 client options file glossary definition 218 client/server connection paths 167 client system options file glossary definition 218 UNIX example 191 Windows NT example 195 client user options file UNIX example 191 cloning SAP R/3 system 123 compressing data null block 101 Tivoli Storage Manager 101 compression 93, 101 CONFIG_FILE profile keyword 179 configuration matrix for Tivoli Storage Manager password settings 163, 164 control file glossary definition 218 control files, Oracle database 63 copies of redo logs 7 copy group glossary definition 218 crontab scheduling backups with 87 crontab file (UNIX) example 199 customization Administration Assistant 105 customize slave server 116 customizing Tivoli Data Protection for R/3 using the configuration tool 107 with the configuration file 6 with the Tivoli Data Protection for R/3 profile 5 D daily backups Version 3 Release 2

243 data compression hardware vs. software 27, 28 null block 101 Tivoli Storage Manager 101 data files, Oracle database 63 data spaces backing up 78 database server backup processes 93 datablock glossary definition 218 datafile glossary definition 218 defining a backup strategy 77 device class glossary definition 219 disaster recovery with alternate/parallel paths and servers 167 DISK glossary definition 219 DISKBUFFSIZE 185 E END profile keyword 179 error log file 48 error messages 128 Tivoli Data Protection for R/3 File Manager 149 examples alternate/parallel paths for availability 170 alternate/parallel paths for disaster recovery 173 alternate/parallel paths for increased performance 172 client system options file (UNIX) 191 client system options file (Windows NT) 195 client user options file (UNIX) 191 client user options file (Windows NT) 195 crontab file (UNIX) 199 full offline batch backup (Windows NT) 204 include/exclude list (UNIX) 192 include/exclude list (Windows NT) 197 examples (continued) offline backup shell script (UNIX) 200 saving and deleting redo logs (UNIX) 201 saving and deleting redo logs (Windows NT) 205 scheduled batch backup (Windows NT) 203 scheduling backup jobs (UNIX) 199 scheduling backup jobs (Windows NT) 203 specifying MAX_SESSIONS and REDOLOG_COPIES 213 Tivoli Storage Manager profiles for UNIX 191 Tivoli Storage Manager profiles for Windows NT 195 EXITONERROR profile keyword 179 F File Manager 58 error messages 149 function keys 61 inquire, restore, delete functions 58 FILE_RETRIES profile keyword 179 file sorting, manual 12 File space glossary definition 219 files backup 81 log 81 protocol 81 files, backup protocol/profile profile & protocol file directories 81 files, Oracle database 63 FRONTEND profile keyword 13, 179 full offline batch backup Windows NT example 204 G generating passwords 161 Index Tivoli Data Protection for R/3 User s Guide 225

244 H handling Tivoli Storage Manager passwords 161 hardware compression 27, 28 compared with Tivoli Storage Manager client software compression 27, 28 I include-exclude list glossary definition 219 include/exclude list UNIX example 192 Windows NT example 197 incremental backup 4, 12, 151 incremental backup function of Tivoli Storage Manager 82 individual tablespace locking 8 inquire function 57 BRRESTORE 57 SAPDBA 57 installing Administration Assistant 109 Administration Assistant, installation verification 119 Administration Assistant, prerequisites 108 Administration Assistant server 109 Administration Assistant slave server 115 Assistant or slave server 115 installing Tivoli Data Protection for R/3 31 on AIX 33 on AIX from CD ROM 33 on AIX from directory 37 on Compaq Tru64 UNIX 37 on HP-UX 40 on Linux 42 on Solaris 44 on Windows NT 46 prerequisites 31 verifying installation 53 J Java prerequisite for Administration Assistant 108 JDK prerequisite for Administration Assistant installation 108 JRE prerequisite for Administration Assistant installation 108 K keywords 176, 178 ADSMNODE 176 BACKEND 13, 176 BACKUPIDPREFIX 177 BATCH 177 BRARCHIVEMGTCLASS 7, 177, 207 BRBACKUPMGTCLASS 7, 178 BUFFSIZE 102, 178 CONFIG_FILE 179 END 179 EXITONERROR 179 FILE_RETRIES 179 FRONTEND 13, 179 LOG_SERVER 14 MAX_ARCH_SESSIONS 181 MAX_BACK_SESSIONS 181 MAX_RESTORE_SESSIONS 181 MAX_SESSIONS 180, 208 MAX_VERSIONS 181 MULTIPLEXING 101, 181 obsolete 185 PASSWORDREQUIRED 182 REDOLOG_COPIES 7, 182, 207 REPORT 13, 183 RL_COMPRESSION 101, 183 SERVER 183 SESSIONS 184 SNMPTRAP 184 syntax for all keywords 175 TRACE 184 TRACEFILE Version 3 Release 2

245 keywords 176, 178 (continued) USE_AT 185 L library, backup 4 locking individual tablespace 8 LOG_SERVER profile keyword 14, 180 logging messages 14 migration from Tivoli Data Protection for R/3 version 2.7 to migration 2.7 to 3.2 steps 158 mirroring control and redo log files in Oracle 79 monitoring Tivoli Data Protection for R/3 107 multi-threading 14 multiple copies of redo logs 7, 207 multiple paths 95 multiplexing 93, 101 MULTIPLEXING profile keyword 101, 181 M management class glossary definition 219 management classes 7 Tivoli Storage Manager server configuration 23 manual password handling 51 manual sorting of files 12 matrix for setting Tivoli Storage Manager passwords 163, 164 MAX_ARCH_SESSIONS profile keyword 181 MAX_BACK_SESSIONS profile keyword 181 MAX_RESTORE_SESSIONS profile keyword 181 MAX_SESSIONS profile keyword 180 example 213 MAX_VERSIONS profile keyword 181 media management API glossary definition 219 message logging 14 messages general, Tivoli Data Protection for R/3 127 severity levels 127 Tivoli Data Protection for R/3 error 128 Tivoli Data Protection for R/3 FileManager 149 N Netscape, Administration Assistant 119 network performance optimization 95, 96 no authentication required 161 node glossary definition 220 node definition Tivoli Storage Manager server 24 null block data compression 101 O offline backup shell script UNIX example 200 offline redo log glossary definition 220 online redo log glossary definition 220 operating system backup strategy 78 Oracle data spaces backing up 78 Oracle database, backup 63 Oracle database, files 63 Index Tivoli Data Protection for R/3 User s Guide 227

246 Oracle database server concepts 78 overview, Tivoli Data Protection for R/3 1 P parallel backup and restore general description 6 number of parallel sessions to specify 6 parallel backup paths, alternate 10 parallel backup servers, alternate 11 parallel backup sessions 208 parallel sessions 95 parallelism 99 password handling 51 automatic 51 generation of password 51 manual 51 PASSWORDREQUIRED profile keyword 182 passwords Tivoli Storage Manager 161 paths alternate/backup 10 PERF_MONITOR 185 performance improvement adaptation of Tivoli Data Protection for R/3 99 adaptation of Tivoli Storage Manager 98 network adaptation 96 parallelism 99 with alternate/parallel paths and servers 167 with multi-threading 14 performance monitoring 107 performance optimization adaptation of Tivoli Storage Manager 98 Backup/Restore 91 Backup/Restore of SAP R/3 Oracle database 99 backup server 97 buffersize 96 by setting disk buffer sizes 102 client, data rates 93 infrastructure design 92 network adaptation 96 performance optimization (continued) setting up environment 102 TCP enhancement 96 tuning 102 with data compression 101 with multiplexing 101 performance problems 208 planning a backup strategy 77 policy definitions Tivoli Storage Manager server configuration 23 policy domain glossary definition 220 policy set glossary definition 220 ports, Administration Assistant server 110 profile SAP backup 49 profile customization, Tivoli Data Protection for R/3 and SAPDBA 49 profile keywords syntax 175 profiles backup, file directories, UNIX 81 backup, file directories, Windows NT 81 backup of 80 example of Tivoli Storage Manager for UNIX 191 Tivoli Storage Manager example for Windows NT 195 Prole 3 protocol backup, file directories, UNIX 81 backup, file directories, Windows NT 81 protocol, backup backup of 80 R recovery 69 full recovery 72 one tablespace 70 Recovery Manager (RMAN) 4, 151 glossary definition Version 3 Release 2

247 redo log files, Oracle database 63 redo logs 7 deleting promptly 212 redo logs (Oracle) backing up 78 redo logs, recovery 72 REDOLOG_COPIES 7 REDOLOG_COPIES profile keyword 182 example 213 REPORT profile keyword 13, 183 reporting backup statistics 13 restore function 58 BRRESTORE 58 SAPDBA 58 restore/recovery 62, 69 BRRESTORE 69 full recovery 72 loss of several data/tablespace files 72 one tablespace 70 recovery of control files 72 recovery of redo log files 72 SAPDBA 62 retention glossary definition 221 RETRY 185 RL_COMPRESSION profile keyword 101, 183 RMAN 151 and incremental backup 151 S sample Tivoli Data Protection for R/3 profile 185 SAP BACKINT interface glossary definition 221 SAP backup profile 49 SAP R/3, backup 62 SAP R/3 backup scheduler 84 SAP R/3 database server performance optimization 93 SAP R/3 database utilities 32 SAP R/3 Oracle database, Backup/Restore of 99 SAP R/3 system cloning 123 SAP R/3 system landscape and Backup/Restore performance 91 saparch directory 212 SAPDBA 55 database backup 65 glossary definition 221 protocols 80 saving and deleting redo logs UNIX example 201 Windows NT example 205 scheduled batch backup Windows NT example 203 scheduling automatic backups 83 scheduling backup jobs UNIX examples 199 scheduling backups Windows NT examples 203 scheduling function of Tivoli Storage Manager 87 scratch volume glossary definition 221 security settings authorizing Administration Assistant users 121 server installing Administration Assistant server 109 option for installing Assistant or slave server 115 server, hostname specification 111 server, port specification 110 server, slave installing Administration Assistant slave server 115 server, slave, customize 116 server, slave, directories 117 server, specifying directory 113 SERVER profile keyword 183 servers alternate/backup 11 SESSIONS profile keyword 184 setting Tivoli Storage Manager passwords automatically 161 setting Tivoli Storage Manager passwords manually 161 setting up Tivoli Data Protection for R/3 31 Index Tivoli Data Protection for R/3 User s Guide 229

248 setting up Tivoli Data Protection for R/3 31 (continued) CD-ROM installation on AIX 33 customizing Tivoli Data Protection for R/3 and SAPDBA profile 49 directory based installation on AIX 37 installation on AIX 33 installation on Compaq Tru64 UNIX 37 installation on HP-UX 40 installation on Linux 42 installation on Solaris 44 installation on Windows NT 46 prerequisites 31 SAP R/3 database utilities 32 Tivoli Storage Manager client 32 verifying the installation 53 setting up Tivoli Storage Manager 17 simultaneous backup sessions 208 SNMP trap 14 SNMPTRAP profile keyword 184 software compression vs. hardware compression UNIX 27 Windows NT 28 sorting, files 12 specifying a backup strategy 77 specifying management classes 7 storage devices setup Tivoli Storage Manager server 21 storage pool glossary definition 221 storage pool definitions Tivoli Storage Manager server 21 storage pool volumes choosing volumes for backups 207 strategy planning a backup strategy 77 system copy heterogeneous 123 homogeneous 123 T tablespace glossary definition 221 tablespace, backup 65 tablespace locking 8 tape drives backup sessions with limited tape drives 209 using hardware compression with 27, 28 TCPWAIT 185 terminating the backup job 168 threads multi-threading 14 Tivoli Data Protection for R/3 architecture and properties 1 BACKINT 1 backup library 1 components 1 database utilities 1 installation and setup 31 introduction 1 Oracle recovery manager 1 overview 1 Tivoli Data Protection for R/3, migration 157 Tivoli Data Protection for R/3 configuration tool 107 Tivoli Data Protection for R/3 file manager glossary definition 221 Tivoli Data Protection for R/3 File Manager error messages 149 Tivoli Data Protection for R/3 messages 127 Tivoli Data Protection for R/3 monitoring tool 107 Tivoli Data Protection for R/3 profile keyword descriptions 175 keyword rules 175 Tivoli Data Protection for R/3 sample profile 185 Tivoli Storage Manager 17 backup scheduler 86 client 32 client software compression 28 configuration file customization 98 data archival 18 data backup, restoration 18 data compression 101 data space management 18 description 17 glossary definition 221 incremental backup function Version 3 Release 2

249 Tivoli Storage Manager 17 (continued) management classes 7 passwords 161 performance optimization 98 scheduling function 87 setup 17 Tivoli Storage Manager API glossary definition 221 Tivoli Storage Manager client configuration 25 configuration on UNIX systems 26 configuration on Windows NT systems 28 software compression 27 Tivoli Storage Manager passwords authentication off 161 configuration matrix to set keywords 163, 164 generating automatically 161 manual generation 161 Tivoli Storage Manager profiles example for UNIX 191 example for Windows NT 195 Tivoli Storage Manager server configuration 19 configuration, prerequisites 20 management classes 23 node definition 24 performance considerations 19 policy definition 23 storage devices setup 21 storage pool definition 21 TRACE profile keyword 184 TRACEFILE profile keyword 184 TRACEMAX 185 tracing 14 tuning 102 util_file_online 8, 51, 67, 74 (continued) glossary definition 222 utility File Manager 58 V validate glossary definition 222 verifying the Administration Assistant installation 119 verifying the Tivoli Data Protection for R/3 installation 53 versions, backup 8 volume glossary definition 222 W Web browser prerequisite for Administration Assistant 108 Windows NT, backup scheduler 87 U UNIX crontab, backup scheduler 87 USE_AT profile keyword 185 user authorization for Administration Assistant 121 util_file_online 8, 51, 67, 74 Index Tivoli Data Protection for R/3 User s Guide 231

250 232 Version 3 Release 2

251 Readers Comments We d Like to Hear from You Tivoli Data Protection for R/3 Installation & User s Guide Version 3 Release 2 Publication No. SC 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.

252 Readers Comments We d Like to Hear from You SC Fold and Tape Please do not staple Fold and Tape SC 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 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES Fold and Tape Please do not staple Fold and Tape Cut or Fold Along Line Cut or Fold Along Line

253

254 Program Number: 5698 DPR Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber. SC