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 backint@de.ibm.com 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/init@.utl 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