Data Protection for mySAP.com Technology Installation & User's Guide …publib.boulder.ibm.com/tividd/td/ITSMERP/SC33-6340-03/en... · 2007-09-29 · in new editions. Order publications

IBM Tivoli Storage Manager for Enterprise ResourcePlanning (5698–APR)

Data Protection for mySAP.com®

TechnologyInstallation & User’s Guide for OracleVersion 3 Release 3. 1

SC33-6340-03

��

IBM Tivoli Storage Manager for Enterprise ResourcePlanning (5698–APR)

Data Protection for mySAP.com®

TechnologyInstallation & User’s Guide for OracleVersion 3 Release 3. 1

SC33-6340-03

��

Fourth Edition (March 2003)

This edition applies to Data Protection for mySAP.com technology Version 3 Release 3 (product number 5698–DPR),available as a licensed program product, and to all subsequent releases and modifications until otherwise indicatedin new editions.

Order publications through your IBM representative or the IBM branch office serving your area. Publications arenot 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, addressyour comments to:

IBM Deutschland Entwicklung GmbHEnterprise Solution DevelopmentDept. 3848, Bldg. 71032-05Schoenaicher Str. 22071032 BoeblingenGermany

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

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

Make sure to include the following in your comment or note:v Title and order number of this book

v Page number or topic related to your comment

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1995, 2003. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Note!Before using this information and the product it supports, be sure to read the general information under“Notices” on page ix.

http://www.ibm.com/software/tivoli

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

Notices . . . . . . . . . . . . . . . ixTrademarks and Service Marks . . . . . . . . ix

Preface . . . . . . . . . . . . . . . xiWho Should Read This Book. . . . . . . . . xiWhere to Find More Information . . . . . . . xiNaming Conventions used in this Documentation. . xiContents of the Data Protection for mySAP.comPackage . . . . . . . . . . . . . . . . xiSupported Platforms . . . . . . . . . . . xiPlatform Differences . . . . . . . . . . . xii

Chapter 1. Introducing Data Protectionfor mySAP.com . . . . . . . . . . . 1Architecture and Properties of Data Protection formySAP.com. . . . . . . . . . . . . . . 1

The Data Protection for mySAP.com Profile . . . 3The Data Protection for mySAP.com ConfigurationFile . . . . . . . . . . . . . . . . 4

Parallel Backup and Restore . . . . . . . . . 4Multiple Management Classes . . . . . . . . 4Multiple Redo Log Copies . . . . . . . . . . 5Individual Tablespace Locking . . . . . . . . 5Backup by Version . . . . . . . . . . . . 5Alternate/Parallel Backup Paths . . . . . . . . 6Alternate/Parallel Backup Servers . . . . . . . 7Incremental Backup . . . . . . . . . . . . 7Manual Sorting . . . . . . . . . . . . . 8Frontend/Backend Processing . . . . . . . . 8Reporting . . . . . . . . . . . . . . . 8Message Logging . . . . . . . . . . . . . 8Tracing . . . . . . . . . . . . . . . . 9Improving Performance. . . . . . . . . . . 9

Chapter 2. Tivoli Storage ManagerSetup . . . . . . . . . . . . . . . 11Tivoli Storage Manager . . . . . . . . . . 11Configuration of Tivoli Storage Manager Server . . 12

General . . . . . . . . . . . . . . . 12Prerequisites . . . . . . . . . . . . . 12Storage Device Setup . . . . . . . . . . 13Storage Pool Definition . . . . . . . . . 13Policy Definition. . . . . . . . . . . . 14Node Definition . . . . . . . . . . . . 15

Configuration of Tivoli Storage Manager Clients . . 16General . . . . . . . . . . . . . . . 16Tivoli Storage Manager Clients on UNIX Systems 17Tivoli Storage Manager Clients on WindowsSystems . . . . . . . . . . . . . . 17

Chapter 3. Setting Up Data Protectionfor mySAP.com . . . . . . . . . . . 19Prerequisites . . . . . . . . . . . . . . 19

mySAP.com Database Utilities . . . . . . . 19Tivoli Storage Manager Client . . . . . . . 20

Installation on UNIX (AIX, Solaris, HP-UX, Linux) 20Installation on Windows . . . . . . . . . . 22Customizing Data Protection for mySAP.com andSAP Backup Profiles . . . . . . . . . . . 25Password Handling. . . . . . . . . . . . 26Verifying the Installation . . . . . . . . . . 27Upgrading or Deinstalling Data Protection formySAP.com . . . . . . . . . . . . . . 28

Deinstallation on UNIX (AIX, Solaris, HP-UX,Linux) . . . . . . . . . . . . . . . 28Deinstallation on Windows . . . . . . . . 29

Chapter 4. Using Data Protection formySAP.com to Back Up and RestoreFiles and Databases . . . . . . . . . 31General . . . . . . . . . . . . . . . . 31Backup Function. . . . . . . . . . . . . 31Inquire Function. . . . . . . . . . . . . 32Restore Function. . . . . . . . . . . . . 32

Data Protection for mySAP.com File Manager . . 33mySAP.com Backup and Recovery Using DataProtection for mySAP.com . . . . . . . . 35

Chapter 5. Backup Strategy andBackup Automation . . . . . . . . . 45Planning a Backup Strategy for the OperatingSystem . . . . . . . . . . . . . . . . 45Planning a Backup Strategy for Your OracleDatabase . . . . . . . . . . . . . . . 45Planning a Backup Strategy for Backup Protocolsand Profiles . . . . . . . . . . . . . . 47Planning a Backup Strategy for mySAP.com SystemData . . . . . . . . . . . . . . . . . 48Backup Automation . . . . . . . . . . . 49

SAP Scheduler . . . . . . . . . . . . 49Tivoli Storage Manager Scheduler . . . . . . 50UNIX crontab / Windows Scheduler . . . . . 50

Example of a Sequence of Daily Backup Runs . . . 51

Chapter 6. Considerations forOptimizing Backup/RestorePerformance . . . . . . . . . . . . 53Data Transfer . . . . . . . . . . . . . . 53The mySAP.com Database Server . . . . . . . 55

Settings for the mySAP.com database server . . 56The Network . . . . . . . . . . . . . . 59

Settings for Network Parameters . . . . . . 59The Backup Server . . . . . . . . . . . . 60

Settings for the Tivoli Storage Manager . . . . 61

© Copyright IBM Corp. 1995, 2003 iii

||

||

||

Optimizing Your Environment . . . . . . . . 61

Chapter 7. Administration Assistant forData Protection for mySAP.com . . . . 63General . . . . . . . . . . . . . . . . 63Prerequisites . . . . . . . . . . . . . . 64Installation . . . . . . . . . . . . . . 65

Installing the Administration Assistant Server(Base Installation) . . . . . . . . . . . 65Installing the Administration Assistant NLSPackage . . . . . . . . . . . . . . 69

Specifying a new Administration Assistant Serverfor Data Protection for mySAP.com . . . . . . 69Verifying the Installation . . . . . . . . . . 70Authorizing Administration Assistant Users . . . 71Using the Administration Assistant . . . . . . 71Uninstalling the Administration Assistant . . . . 72

Chapter 8. mySAP.com System Cloning 73General . . . . . . . . . . . . . . . . 73mySAP.com System Cloning Example . . . . . 73

Chapter 9. Considerations for UsingIBM HACMP for AIX . . . . . . . . . 75Data Protection for mySAP.com Internals . . . . 75

Files . . . . . . . . . . . . . . . . 75Dependencies. . . . . . . . . . . . . 75Communication . . . . . . . . . . . . 75

Installation and Setup . . . . . . . . . . . 76Installation . . . . . . . . . . . . . 76Defining Data Protection for mySAP.com as anHACMP Application . . . . . . . . . . 76Adding the Data Protection for mySAP.comApplication to an HACMP Resource Group . . 77Sample Start Script . . . . . . . . . . . 77Sample Stop Script . . . . . . . . . . . 78

Appendix A. Data Protection formySAP.com Messages . . . . . . . . 81How To Find Message Files (Log Files) . . . . . 81Data Protection for mySAP.com MessageExplanations . . . . . . . . . . . . . . 82Data Protection for mySAP.com File Manager ErrorMessages . . . . . . . . . . . . . . . 98

Appendix B. Using Data Protection formySAP.com with RMAN . . . . . . . 99RMAN Setup on UNIX Systems . . . . . . . 99RMAN Setup on Windows Systems . . . . . . 101

Appendix C. Migration from EarlierReleases . . . . . . . . . . . . . 103

Appendix D. Password Handling . . . 105

Configuration Matrix (UNIX) . . . . . . . . 106Configuration Matrix (Windows) . . . . . . . 106

Appendix E. Alternate/Parallel BackupPaths and Backup Servers . . . . . 109Parameter Settings - SERVER Statement . . . . 110

EXAMPLE 1: Use of Alternate/Parallel Paths forIncreased Availability . . . . . . . . . . 111EXAMPLE 2: Use of Alternate/Parallel Paths forIncreased Performance . . . . . . . . . 113EXAMPLE 3: Use of Alternate/Parallel Serversfor Disaster Recovery . . . . . . . . . . 114

Appendix F. The Data Protection formySAP.com Profile . . . . . . . . . 115Keyword Reference . . . . . . . . . . . 115Sample Data Protection for mySAP.com Profile forUNIX . . . . . . . . . . . . . . . . 122

Appendix G. Sample Tivoli StorageManager Profiles (UNIX) . . . . . . . 127Client User Options File Sample (dsm.opt) . . . 127Client System Options File Sample (dsm.sys) . . . 127Include/Exclude List Sample . . . . . . . . 127

Appendix H. Sample Tivoli StorageManager Profiles (Windows) . . . . . 129Client User Options File Sample (dsm.opt) . . . 129Client Options Files Sample (<server>.opt) . . . 129Include/Exclude List Sample . . . . . . . . 130

Appendix I. Elements of BackupSchedules (UNIX). . . . . . . . . . 131Crontab File Sample . . . . . . . . . . . 131Full Offline Backup Shell Script Sample . . . . 132Save and Delete Redo Logs Shell Script Sample 132

Appendix J. Elements of BackupSchedules (Windows) . . . . . . . . 135Schedule Batch Sample . . . . . . . . . . 135Full Offline Backup Batch File Sample . . . . . 135Save and Delete Redo Logs Batch File Sample . . 136

Appendix K. Tips and Hints forBRARCHIVE . . . . . . . . . . . . 139Hints for BRARCHIVE Version 3.1G or Higher . . 142Examples Using MAX_SESSIONS andREDOLOG_COPIES . . . . . . . . . . . 142

Glossary . . . . . . . . . . . . . 145

Index . . . . . . . . . . . . . . . 149

iv Data Protection for mySAP.com Technology Installation & User’s Guide for Oracle

|||

Figures

1. Overview of Data Protection for mySAP.com for Oracle . . . . . . . . . . . . . . . . . . . 22. File Manager — Result of an Inquiry Procedure . . . . . . . . . . . . . . . . . . . . . 343. File Manager — Result of an Inquiry Procedure Showing File Names . . . . . . . . . . . . . . 344. Backup Scenarios Within a mySAP.com Oracle Environment . . . . . . . . . . . . . . . . . 475. Production Backup Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516. Data Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547. Compression and Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . 568. Example of an mySAP.com Landscape . . . . . . . . . . . . . . . . . . . . . . . . 639. Administration Assistant Server Setup (Base Installation) — Specify Ports. . . . . . . . . . . . . 67

10. Administration Assistant Server Setup (Base Installation): Correct Hostname Panel. . . . . . . . . . 6811. Administration Assistant Server Setup – Destination Directory . . . . . . . . . . . . . . . . 6912. Starting the Administration Assistant with Netscape . . . . . . . . . . . . . . . . . . . . 7013. Administration Assistant Start Panel . . . . . . . . . . . . . . . . . . . . . . . . . 7114. Sample Environment for HACMP Takeover . . . . . . . . . . . . . . . . . . . . . . . 75

© Copyright IBM Corp. 1995, 2003 v

||||

||||

vi Data Protection for mySAP.com Technology Installation & User’s Guide for Oracle

Tables

1. SAP Backup Profile Parameter Combinations . . . . . . . . . . . . . . . . . . . . . . 262. Required Settings for Password Handling . . . . . . . . . . . . . . . . . . . . . . . 273. Tuning of Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594. Tuning of SP Switch Buffer Pools . . . . . . . . . . . . . . . . . . . . . . . . . . 605. Tuning Tivoli Storage Manager Configuration File Attributes . . . . . . . . . . . . . . . . . 616. File Extensions for Shared Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 997. Password Handling for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068. Password Handling for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 1079. SERVER Statement and Appropriate Profile and Option File Settings. . . . . . . . . . . . . . . 110

© Copyright IBM Corp. 1995, 2003 vii

||

viii Data Protection for mySAP.com Technology Installation & User’s Guide for Oracle

Notices

References in this publication to IBM® products, programs, or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program, or service is not intended tostate or imply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe any ofthe intellectual property rights of IBM may be used instead of the IBM product,program, or service. The evaluation and verification of operation in conjunctionwith other products, except those expressly designated by IBM, are theresponsibility of the user.

IBM may have patents or pending patent applications covering subject matter inthis document. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, toIBM Director of LicensingIBM CorporationNorth Castle driveArmonk, NY 10504-1785U.S.A

Any references in this information to non-Tivoli or non-IBM Web sites are providedfor convenience only and do not in any manner serve as an endorsement of thoseWeb sites. The materials at those Web sites are not part of the materials for thisproduct and use of those Web sites is at your own risk.

If you are viewing this information in softcopy form, the photographs and colorillustrations may not appear.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:IBM Deutschland Informationssysteme GmbHDepartment 0215Pascalstr. 10070569 StuttgartGermany

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

Trademarks and Service MarksThe following terms are trademarks or registered trademarks of InternationalBusiness Machines Corporation in the United States or other countries or both:v AFSv AIXv IBMv RS/6000v SPv Tivoli

© Copyright IBM Corp. 1995, 2003 ix

mySAP.com is a registered trademark of SAP AG in Germany, other countries, orboth.

Oracle is a registered trademark of Oracle Corporation.

Solaris, Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Incorporated, in the United States, othercountries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Linux is a registered trademark of Linus Torvalds and others.

Microsoft, Windows, Windows NT, and Windows 2000 are registered trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marksof others.

x Data Protection for mySAP.com Technology Installation & User’s Guide for Oracle

||

|

Preface

Who Should Read This BookThis manual is intended for system programmers and administrators who areresponsible for implementing a backup solution in a mySAP.com environmentusing the Tivoli® Storage Manager. It describes the procedures needed to installand customize Data Protection for mySAP.com, the interface between mySAP.comand the Tivoli Storage Manager. The reader should be familiar with mySAP.comand Oracle documentation.

Where to Find More InformationFor more information about Data Protection for mySAP.com, refer to the TivoliInternet home page at http://www.ibm.com/software/tivoli.

Note:The most up-to-date version of this book is available in the Tivoli InformationCenter at http://www.ibm.com/software/tivoli/library.

Naming Conventions used in this DocumentationIn this documentation, Data Protection for mySAP.com technology is usuallyreferred to as Data Protection for mySAP.com or DP for mySAP.com.

Contents of the Data Protection for mySAP.com PackageThe Data Protection for mySAP.com package includes this manual and machinereadable material on a CD-ROM. See the README file for:v A table of contents of the packagev Up-to-date news

Supported PlatformsThe following platforms are supported:AIX® 4.3.3 and 5.1HP-UX 11.0, 11iRed Hat Linux 6.1SuSE Linux 7Solaris 7, 8Windows NT (Intel) 4.0Windows 2000

NoteUnless otherwise stated, references in this publication to UNIX® apply to allsupported UNIX-based systems as well as to Linux, and references toWindows® apply to Windows NT and Windows 2000.

© Copyright IBM Corp. 1995, 2003 xi

||


http://www.ibm.com/software/tivoli/library

Platform DifferencesThere are only small differences between the UNIX and Windows versions of DataProtection for mySAP.com. One of these differences is that UNIX uses the pathseparator ″/″ compared with ″\″ for Windows and that the drive letter is specifiedfor Windows. Non-trivial differences between the UNIX and Windows versions ofData Protection for mySAP.com will be mentioned explicitly.

xii Data Protection for mySAP.com Technology Installation & User’s Guide for Oracle

Chapter 1. Introducing Data Protection for mySAP.com

Data Protection for mySAP.com is an intelligent client/server program to managebacking up and restoring mySAP.com Oracle databases using the Tivoli StorageManager (TSM) (see Chapter 2, “Tivoli Storage Manager Setup”, on page 11).

This chapter gives you an overview and description of the architecture andproperties of Data Protection for mySAP.com.

Architecture and Properties of Data Protection for mySAP.comData Protection for mySAP.com lets you manage backup storage and processingindependently of normal mySAP.com operations. Data Protection for mySAP.comand Tivoli Storage Manager provide reliable, high performance, repeatable backupand restore processes that let system administrators manage large volumes of datamore efficiently.

Data Protection for mySAP.com allows system administrators to follow SAPprocedures and use the integrated SAP database utilities for backup and restore.These utilities are SAPDBA, BRBACKUP, BRARCHIVE, and BRRESTORE. OtherSAP files, for example executables, are backed up using Tivoli Storage Managerstandard techniques for file backup and restore such as incremental backup, filefiltering, and versioning.

Data Protection for mySAP.com supports two different backup/restore scenarios asseen in Figure 1 on page 2: backup/restore of files (data files, control files, redologs, profiles) and backup/restore of data blocks.

© Copyright IBM Corp. 1995, 2003 1

Data Protection for mySAP.com consists of three components:v BACKINT

– executable– interface between SAP database utilities and backup library for

backup/restore of files– reads/writes database objects (files) from/to disk– receives input parameter from SAP database utilities (e.g., list of database

objects to be handled) and routes them to Prole

– reads/transfers data from/to the Tivoli Storage Manager API clientv Prole

– permanently running background process– controls backup/restore operations– 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– collects and sends backup/restore performance data to the Administration

Assistant server.v Backup library

– shared library– reads/transfers data blocks from/to the Oracle MM API– reads/transfers data from/to the Tivoli Storage Manager API client

Figure 1. Overview of Data Protection for mySAP.com for Oracle

2 Data Protection for mySAP.com Technology Installation & User’s Guide for Oracle

Data Protection for mySAP.com provides two possibilities for backing up orrestoring data to or from the Tivoli Storage Manager. These are:v Backup or restore of filesv Backup or restore of data blocks

In the case of a file backup, the communication between the SAP database utilitiesand Data Protection for mySAP.com will be handled by the SAP BACKINTinterface. The entry point for this communication is the BACKINT executable.BACKINT hands over all necessary parameters received from the respective SAPdatabase utility (BRBACKUP, BRARCHIVE, or BRRESTORE) to the backgroundprocess Prole. This process controls the running backup operation being done bythe backint client. The backup client reads the appropriate files from disk andsends them to one or more (of several) Tivoli Storage Manager servers using theData Protection for mySAP.com API client.

In the case of a backup of data blocks (e.g., incremental backup) BRBACKUP callsthe Oracle Recovery Manager (RMAN) and starts an Oracle server process. Thisprocess reads the data (data blocks) to be backed up from the Oracle database andtransfers it to the external Data Protection for mySAP.com backup librarylibtdp_r3 using the Oracle Media Management API (MM API). In a similarmanner as described above, the backup client reads the data blocks and sendsthem to one or more (of several) Tivoli Storage Manager servers using the TivoliStorage Manager API client.

Data Protection for mySAP.com optimizes the data throughput for backup andrestore in several ways to minimize downtime and the impact on normal systemoperation:v It sorts the database objects in order to balance the load on the resources used

for backup. For restore operations, Data Protection for mySAP.com maintains thesame sequence for efficient tape transfer.

v It is able to handle multiple backup/restore sessions. Each session reads datafrom and writes data to storage devices in parallel with (and independently of)each other.One session can be established per backup storage device.

v It utilizes multiple communication paths to Tivoli Storage Manager servers toeliminate network-induced bottlenecks.

NoteWhen Data Protection for mySAP.com is called by one of the SAP databaseutilities SAPDBA, BRBACKUP, BRARCHIVE, or BRRESTORE to perform abackup or restore, it always uses the Tivoli Storage Manager API archive andretrieve functions. Data Protection for mySAP.com does not use the TivoliStorage Manager API backup and restore functions.

Data Protection for mySAP.com always performs a backup, regardless of whetherfiles are open or closed. The calling routine (for example, BRBACKUP) isresponsible for informing the database controlling routine about which files are tobe backed up. This is done using an alter tablespace begin backup. The backup ofboth the open database files and the redo logs results in a complete backup.

The Data Protection for mySAP.com ProfileYou can customize the way Data Protection for mySAP.com operates withkeywords and parameters in a profile that is analyzed by Data Protection for

Chapter 1. Introducing Data Protection for mySAP.com 3

mySAP.com Prole before any Tivoli Storage Manager subcommands are processed.By customizing this profile, you can adapt Data Protection for mySAP.com to yourenvironment’s specific needs (see “Customizing Data Protection for mySAP.comand SAP Backup Profiles” on page 25).

The Data Protection for mySAP.com Configuration FileParameters that Data Protection for mySAP.com modifies are stored in a separatebinary configuration file for use in later sessions. In addition to other information,this file contains the Tivoli Storage Manager password in an encrypted form. Beaware that Data Protection for mySAP.com might not be able to run if you changethis file manually.

Parallel Backup and RestoreData Protection for mySAP.com backs up and restores Oracle database objects thatyou specify using the SAP database utilities.

The SAP database utilities BRBACKUP, BRARCHIVE, and BRRESTORE pass thedatabase objects (e.g., data files or offline redo logs) as a temporary list of objectsto Data Protection for mySAP.com. Data Protection for mySAP.com receives controlwith the parameters that are specified in its profile, reads the temporary file list,and starts multiple sessions. During backup or restore operations, the SAPdatabase utilities generate protocols about every performed action. All messagesgenerated by Data Protection for mySAP.com are also located in these protocols.

The profile keyword MAX_SESSIONS specifies the maximum number of parallelsessions Data Protection for mySAP.com will establish. Each session transfers onedatabase object or, in the case of an RMAN backup or restore, a set of data blocksto or from the Tivoli Storage Manager server by using the Tivoli Storage ManagerAPI client functions. Data Protection for mySAP.com optimizes the data transferwith regard to the physical location of the Oracle objects. Files stored on differentvolumes are backed up in parallel.

NoteYou should specify as many parallel sessions as there are physical storagedevices available at the Tivoli Storage Manager server.

Multiple Management ClassesThe Tivoli Storage Manager server manages data by using management classes.For more information, refer to the Administrator’s Guide for Tivoli Storage Managerfor a detailed description of Tivoli Storage Manager concepts, includingmanagement classes.

In order to take full advantage of Data Protection for mySAP.com’s parallel backupand restore capabilities, you should specify one management class for eachphysical backup device (tape drive). Data Protection for mySAP.com distinguishesbetween BRBACKUP and BRARCHIVE and uses different management classes forobjects that are saved with each utility. Use the profile keywordsBRBACKUPMGTCLASS and BRARCHIVEMGTCLASS to specify these managementclasses.


With this feature, Data Protection for mySAP.com can use more than one storagelibrary device at a time.

Multiple Redo Log Copies

As a protection against tape defects or to improve availability or disaster recovery,multiple copies of log files can be stored during one BRARCHIVE run on differentphysical Tivoli Storage Manager volumes. If a log file is not accessible during arestore, Data Protection for mySAP.com will automatically attempt to retrieve thefile from another copy.

How many copies are stored depends on the setting of the keywordREDOLOG_COPIES. If the keyword is set to 2, for example, two copies will becreated.

This feature can only be used when (at least) as many archive management classesare defined as numbers of log copies are specified (keywordBRARCHIVEMGTCLASS).

For more detailed information about creating and using REDOLOG_COPIES, seeAppendix K, “Tips and Hints for BRARCHIVE”, on page 139.

Individual Tablespace LockingTo minimize the amount of archived redo logs during online backup operations,Data Protection for mySAP.com can notify the SAP database utility BRBACKUP forwhich tablespaces it is going to back up files. BRBACKUP locks only thosetablespaces. The other tablespaces are available for database transactions. After thefiles are backed up, the tablespaces are released again and a new cycle starts.

NoteThis mode (util_file_online) is selected with a parameter in the SAPDBAsetup (see Chapter 4, “Using Data Protection for mySAP.com to Back Up andRestore Files and Databases”, on page 31) or it can be set permanently withinthe SAP backup profiles (see “Customizing Data Protection for mySAP.comand SAP Backup Profiles” on page 25).

Data Protection for mySAP.com has to wait until the requested tablespaces are inbegin backup mode. There will be a time delay after the negotiation betweenBRBACKUP and Data Protection for mySAP.com until the tablespaces are actuallyprepared for backup and Data Protection for mySAP.com can start the backupprocess.

Backup by VersionThis function lets you keep a specified number of backups.

Keep in MindThe expiration period for your backups in Tivoli Storage Manager must belong enough so that it does not conflict with this feature in Data Protectionfor mySAP.com.


|||||

|||

|||

||

Every time a full backup completes successfully, the version count is incrementedby 1 and stored in the Data Protection for mySAP.com configuration file. Thisvalue is also assigned to the tablespace files and to all subsequent redo logbackups. If the number of versions kept in backup storage is larger than thespecified maximum number of backup versions (stored in the parameterMAX_VERSIONS), the oldest versions are deleted (together with the correspondingtablespace and redo log files) until only the specified maximum number of mostrecent versions remain.

Notes

v Partial backups get the same version number as the last successful fullbackup. When Data Protection for mySAP.com deletes an old full backup,all partial backups with the same version number are also deleted.

v Every database instance needs its own configuration file (see parameterCONFIGURATION_FILE) and a unique BACKUPIDPREFIX.

CAUTIONTivoli Storage Manager uses the value of the parameter RETVER specifiedwhen defining a copy group (see “Policy Definition” on page 14) to give filesan expiration date. If you use Data Protection for mySAP.com versioning, youneed to bypass this expiration function. If you use the Tivoli Storage Managerexpiration function, you need to turn off Data Protection for mySAP.comversioning. Use only one of these methods to control how long you keepbackups.

If you use Data Protection for mySAP.com versioning, set the Tivoli StorageManager parameter RETVER=9999 so that the files are not considered expiredand are not deleted by Tivoli Storage Manager.

If you use Tivoli Storage Manager expiration, deactivate Data Protection formySAP.com versioning by setting MAX_VERSIONS=0.

Alternate/Parallel Backup PathsData Protection for mySAP.com 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. Inorder to use this option, the Tivoli Storage Manager server must be accessibleunder more than one network address. When you set up this option, DataProtection for mySAP.com uses the configured communication paths for datatransfer to the Tivoli Storage Manager server. These paths can be usedsimultaneously to increase data throughput or to ensure that the backup operationcan continue when one or more paths are down. You can specify a number ofparallel sessions for each path to adjust to different network speeds and todistribute the load over the network.

For each communication path (for example, a Tivoli Storage Manager servernetwork address), you define a set of additional communication parameters (seeAppendix E, “Alternate/Parallel Backup Paths and Backup Servers”, on page 109).This client option data is collected under a logical server name that you can choosefreely. Under UNIX, it is possible to store all client option data in a single clientsystem option file that is called dsm.sys. Under Windows, you will need to store


||

the client option data for each logical server in separate client option files that havethe file names <servername>.opt. For example, if you have two logical TivoliStorage Manager servers fast and slow, then you need two client option filesfast.opt and slow.opt. For Windows, you need an additional client user optionfile, dsm.opt. All option files must reside in the same directory.

You use the profile to tell Data Protection for mySAP.com about thecommunication paths to be used in the SERVER statement. Under the keywordSERVER, specify the logical Tivoli Storage Manager server name. This nameestablishes the connection between the corresponding sections of the Tivoli StorageManager client option files and the Data Protection for mySAP.com profile.

See Appendix E, “Alternate/Parallel Backup Paths and Backup Servers”, onpage 109 for a description of the SERVER statement. This section also containsprofile examples of how to use alternate backup paths.

Alternate/Parallel Backup ServersYou can specify alternate backup servers to increase performance or for disasterrecovery purposes. For disaster recovery, the backup data is routed to other TivoliStorage Manager servers. This function is similar to alternate backup paths, exceptthat now the keyword SERVER refers to physically different Tivoli StorageManager servers. The backup data is distributed over the configured set of TivoliStorage Manager servers, however, Data Protection for mySAP.com keeps track ofall backups regardless of which server they are stored on. Each server can beaccessed again using alternate backup paths.

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 respectivesections in Appendix E, “Alternate/Parallel Backup Paths and Backup Servers”, onpage 109.

Incremental BackupSAP R/3 release 4.5A and later permits incremental backups of Oracle databasesusing Oracle’s Recovery Manager (RMAN). An incremental backup saves onlythose blocks within the database, which have been changed since the last fullbackup.

Incremental backups reduce the total amount of data to be backed up. Dependingon the system environment, this may result in decreased backup times. It may leadto a reduced network load and to a reduced need of backup system capacity.Furthermore, this could be of special advantage for large databases which haveonly a few changes on a daily basis.

Data Protection for mySAP.com supports incremental backups of Oracle databases.To do this, appropriate customizing steps have to be carried out (see Appendix B,“Using Data Protection for mySAP.com with RMAN”, on page 99).

You can find additional information about incremental backup strategies in an SAPenvironment in your SAP online documentation.


Manual SortingData Protection for mySAP.com allows reading the files to be backed up in anorder you specify. This can increase the backup performance, especially on disksubsystems such as ESS or EMC, because it prevents concurrent reading of fileswhich reside on logical volumes of the same physical disks.

To perform manual sorting, a so-called sortfile has to be created. The format of thesortfile is:

Sort file format/<path>/<filename1> disknumbers/<path>/<filename2> disknumber

.

.

./<path>/<filenameN> disknumber

The disk numbers are counted from 1 to n. They do not have any relation to thephysical disks. You only have to specify the same number for the files on the samephysical disk.

The manual sorting can be enabled using the Data Protection for mySAP.comprofile keyword SORT_FILE which expects the name of the previously createdsortfile as a parameter.

Frontend/Backend ProcessingData Protection for mySAP.com provides frontend and backend processingcapabilities. With this feature, a program or command can be called before or afterData Protection for mySAP.com runs. Specify the program or command with theprofile keywords FRONTEND and BACKEND.

The frontend program is called before a backup or restore operation starts. Thebackend program is called after a backup or restore operation has ended.

ReportingFor statistical purposes, Data Protection for mySAP.com provides informationabout the number of bytes that are transferred to or from the server and theeffective throughput. In addition, Data Protection for mySAP.com calculates anestimated end time and reports which file is currently being processed.

Specify the keyword REPORT with the parameter YES to enable this feature.

Message LoggingData Protection for mySAP.com can send log messages to a configurable TivoliStorage Manager server. Possible messages include backup and restore progressinformation and error messages. Use a LOG_SERVER keyword in the profile toenable this feature.


Furthermore, Data Protection for mySAP.com is able to send log messages to anetwork management program via SNMP traps. Such messages include backupand restore progress information and error messages. Use an SNMPTRAP keywordin the profile to enable this feature.

TracingData Protection for mySAP.com can write trace information into a file to helpanalyze problems. You should contact your Data Protection for mySAP.comsupport before you use this function.

Improving PerformanceNewer releases of Data Protection for mySAP.com are multi-threaded. This designmakes use of enlarged internal buffers. Disk I/O to a particular block of thesebuffers can be carried out independently of network I/O to a different block. OnSMP machines, these independent parts of the code (threads) run concurrently ondifferent processors. In contrast, older single-threaded releases run only on oneprocessor at a time regardless of how many processors are available. Furtherdetailed descriptions on these subjects can be found in Chapter 6, “Considerationsfor Optimizing Backup/Restore Performance”, on page 53.

Multi-threaded versions of Data Protection for mySAP.com contains the followingadditional features:v RL compressionv multiplexingv user-adjustable block size for reading from disk and sending data to Tivoli

Storage Manager


|


Chapter 2. Tivoli Storage Manager Setup

This chapter gives an overview of the Tivoli Storage Manager and explains theprocedures for setting it up for working with Data Protection for mySAP.com in anSAP environment. A typical list of actions that the Tivoli Storage Manager installeror administrator must perform to prepare Tivoli Storage Manager to work in anSAP environment will be explained.

NoteThe following steps and procedures are only samples. The actual values inyour specific environment may be different.

Tivoli Storage ManagerTivoli Storage Manager is the core product of the Tivoli Storage Managementproduct set. It provides a solution for distributed data and storage management inan enterprise network environment. Tivoli Storage Manager currently protects andmanages data on more than 30 operating platforms, covering mobile, desktop andserver systems distributed over the entire world. It is integrated with hundreds ofstorage devices as well as with LAN, WAN, and SAN infrastructure.

The base function provided by Tivoli Storage Manager and its complementaryproducts includes:

Data Protection

1. Operational Backup and Restoration of Data: The backup process creates a copyof the data which protects against operational loss or destruction of file orapplication information. You can define how often the data is to be backedup (frequency) and how many copies (versions) are to be kept. The restoreprocess places the backup copy of the data into a customer-designatedsystem or workstation

2. Disaster Recovery: This involves all activities for organizing, managing andautomating the recovery process after a major loss of IT infrastructure anddata across the enterprise. This includes processes for moving data offsiteinto a secure vault location, for rebuilding IT infrastructure, and forenabling data to be successfully reloaded in an acceptable time frame.

Storage Resource Management

1. Vital Record Retention Archive and Retrieval: The archival process creates acopy of a file or a set of files representing an end point of a process for longterm 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 beretained. The retrieval process locates the copies within the archival storageand places them back into a customer-designated system or workstation.

2. Hierarchical Space Management: This process provides automatic andtransparent movement of operational data from the user system disk spaceto a central storage repository. If the user accesses this data, it isdynamically and transparently restored to the client storage.

These functions are network based, which means that they are available to thewhole network environment. All the functions can be automated to run in a 24x7


lights-out environment. Administration costs are minimized by centralization of allthe management of Tivoli Storage Manager components. The Tivoli StorageManager supports a wide variety of platforms for mobile, small and large systems,and delivers, together with complementary products, many data managementfunctions 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 therespective manuals such as the Administrator’s Reference for Tivoli Storage Manager orthe Administrator’s Guide for Tivoli Storage Manager.

Tivoli Storage Manager publications are also available on the Tivoli StorageManager home page at http://www.ibm.com/software/tivoli/products/storage-mgr

Configuration of Tivoli Storage Manager ServerThis section shows the procedure for setting up the Tivoli Storage Manager server.General server configurations will be described first and finally specific serverconfigurations, such as setup of storage devices.

The Tivoli Storage Manager commands presented in this chapter are shown in fullfor ease of understanding. In the Tivoli Storage Manager command line interface,short cuts or abbreviations for all commands and parameters can be used forconvenience. Tivoli Storage Manager also has a Web-browser-based Graphical UserInterface (GUI).

GeneralBefore starting the installation, some important performance issues should beconsidered. The careful choice of the server that is to be installed, the networktopology, and the use of powerful hardware can improve performance within thesystem landscape and can avoid performance bottlenecks.v Host for Tivoli Storage Manager server. The Tivoli Storage Manager server

should be installed on an exclusive machine. This procedure avoids concurrentprocesses and disk I/O accessing with other applications. In a single SAP systemlandscape, a single Tivoli Storage Manager server is sufficient. If you plan to usethe Storage Manager to back up/restore other clients as well, you shouldconsider either installing the server software on a large machine or using severalTivoli Storage Manager servers.

v Network topology. Network topologies such as Ethernet, Token Ring, FDDI, FastEthernet, and ATM all work well with Tivoli Storage Manager. In general, thefastest network topology like FDDI or Fast Ethernet should be used to preventbottlenecks during backup/restore operations. Tivoli Storage Manager supportsmultiple network adapters, increasing server throughput by providing multipleconnections to the same network or several physically distinct networks with thesame server.

v RS/6000® SP™ environment. An RS/6000 SP node can be used for a TivoliStorage Manager server. The use of a High Performance Switch network willimprove performance of backup/restore operations on the Tivoli StorageManager server.

PrerequisitesIt is assumed that the Tivoli Storage Manager server has already been successfullyinstalled. This means that the following steps have been completed:


v Tivoli Storage Manager server has been installed. For information on therequired release and maintenance level, refer to the Data Protection formySAP.com release notice.

v Recovery log volume has been allocated and initialized.v Recovery log mirror volume has been allocated and initialized.v Database volume has been allocated and initialized.v Database mirror volume has been allocated and initialized.v Additional labeled volumes for the backup and archive storage pools have been

allocated and initialized (disks, tapes or combinations).v Licenses have been registered.v The Tivoli Storage Manager server has been started.

For information on installing Tivoli Storage Manager, see the Tivoli Storage ManagerQuick Start manual.

NoteThe latest code fixes for Tivoli Storage Manager can be found at:ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance

Storage Device SetupA 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 calledDISK which obviates the need for a redefinition.

For proper storage device setup, check the following items established within theTivoli Storage Manager server during the installation procedure:1. Query defined library

q library

2. Query defined drives

q drive

3. Query defined device class

q devclass

Storage Pool DefinitionA storage pool is a named collection of storage volumes that are associated withone device class. Each storage pool represents a collection of volumes that are thesame media type. The storage pool setup defines the storage hierarchy for theappropriate environment.

In a mySAP.com environment, there are different kinds of data to be backed up.These are:v SAP system datav mySAP.com database data (data files, online/offline redo log, control files)

To separate this data within the Tivoli Storage Manager, you must defineappropriate storage pools for each of these data collections. The following section

Chapter 2. Tivoli Storage Manager Setup 13

gives examples of how storage pools within Tivoli Storage Manager can be definedin consideration of the requirements mentioned above.

To define storage pools within the Tivoli Storage Manager server, log on as TivoliStorage Manager Administrator using the Admin Command Line or the Web Adminand invoke the following commands:1. Definition of a storage pool for the SAP system data

define stgpool sap_incr <device_class_name> maxscr=5

2. Definition of a storage pool for the data files

define stgpool sap_db <device_class_name> maxscr=20

3. Definition of a storage pool for the first copy of offline redo log files

define stgpool sap_log1 <device_class_name> maxscr=3

4. It is strongly recommended that you back up the offline redo log files twice ontwo different Tivoli Storage Manager volumes. For this purpose, you have todefine an additional storage pool for the second copy of offline redo log files.

define stgpool sap_log2 <device_class_name> maxscr=3

NoteWhen you associate a library tape device, you have to define the maximumnumber of scratch volumes (labeled volumes which are empty or contain novalid data) this storage pool will be allowed to use (parameter maxscr). Themaximum number of scratch tapes depends on the size of the database, thecapacity of the tapes, the number of scratch volumes available and how manyversions of the backup you will keep. Replace these values with yourestimates.

Policy DefinitionTivoli Storage Manager policies are used to specify how files are backed up,archived, migrated from client node storage, and managed in server storage.

A policy definition includes the definition of a policy domain, a policy set,management classes and copy groups. After the definition phase, you need to assign adefault policy set and validate and activate it.

For the policy definition, log on as a Tivoli Storage Manager Administrator usingthe Admin Command Line or the Web Admin and invoke the following commands:1. Policy domain and policy set definition

define domain sap_c21define policyset sap_c21 p_c21

2. Management Class definition for file system backups, data files, offline redologs and copies of offlineredo logs


define mgmtclass sap_c21 p_c21 mdefaultdefine mgmtclass sap_c21 p_c21 mdbdefine mgmtclass sap_c21 p_c21 mlog1define mgmtclass sap_c21 p_c21 mlog2

NoteIf you are planning to use this Tivoli Storage Manager server withmultiple SAP systems, it is recommended that you use a set of differentmanagement classes for each system.

3. Copy Group definition

define copygroup sap_c21 p_c21 mdefault type=backup destination=sap_incrdefine copygroup sap_c21 p_c21 mdefault type=archive destination=archivepooldefine copygroup sap_c21 p_c21 mdb type=archive destination=sap_db retver=9999define copygroup sap_c21 p_c21 mlog1 type=archive destination=sap_log1 retver=9999define copygroup sap_c21 p_c21 mlog2 type=archive destination=sap_log2 retver=9999

Data Protection for mySAP.com uses its own version control mechanism formanaging mySAP.com database backups. To do this, Data Protection formySAP.com backs up all data only to management classes for which an archivecopy group has been defined (parameter type set to archive). In addition, toprevent backed up files within Tivoli Storage Manager being deleted because oftheir expiration date (Tivoli Storage Manager deletes expired files), the copygroup 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_c21activate policyset sap_c21 p_c21

Node DefinitionThe Tivoli Storage Manager server views its registered clients, application clients,host servers, and source servers as nodes that require services and resources fromthe server.

To register a node within Tivoli Storage Manager, log on as Tivoli Storage Manageradministrator using the Admin Command Line or the Web Admin and invoke thefollowing command:

register node C21 passwd domain=sap_c21 maxnummp=8


NoteIf you are using two or more tape drives, you may want to pay specialattention to the node parameter maxnummp. It defines the maximum number ofmount points that one node can use. The default value is 1. If one nodeshould use more than one mount point, the parameter must be set to thedesired number of mount points.

Configuration of Tivoli Storage Manager ClientsAfter the server configuration, you have to configure the clients that will use theTivoli Storage Manager server. These include the backup/archive client and theApplication Programming Interface (API) client. The Tivoli Storage Managerbackup/archive client will be used for file system backups. The API client allowsusers to enhance existing applications with backup, archive, restore, and retrieveservices. An installed and confirmed API client is a prerequisite for Data Protectionfor mySAP.com.

GeneralFirst of all, if a successful installation of Tivoli Storage Manager backup/archiveclient and API client is to be performed, the clients must be installed on all nodesthat will interface with the Tivoli Storage Manager server.

In the context of a mySAP.com system landscape, this means that the TivoliStorage Manager backup/archive client must be installed on every machinescheduled for a file system backup, for example, mySAP.com application serversand the mySAP.com database server. The Tivoli Storage Manager API client onlyneeds to be installed on the mySAP.com database server machine to enablebackup/restore operations of the mySAP.com database in combination with thebackup interface program Data Protection for mySAP.com.

NoteWhen the Tivoli Storage Manager API client is installed on UNIX systems,ensure that there is a softlink /usr/lib/libApiDS.<ext> pointing to thelibApiDS.<ext> file in the installation directory(/usr/tivoli/tsm/client/api/bin) of the Tivoli Storage Manager API. For themeaning of <ext>, see “RMAN Setup on UNIX Systems” on page 99.

The setup for the Tivoli Storage Manager client is effected in UNIX environmentsby changing the files dsm.opt and dsm.sys and in Windows environments bychanging the file <server_a>.opt (where server_a is a logical server name, see“Tivoli Storage Manager Clients on Windows Systems” on page 17). Subsequently,the include/exclude file must be configured. It defines which files the TivoliStorage Manager backup/archive client will include or exclude for any backup,archive or hierarchical storage procedure. Examples of an include/exclude file forUNIX can be found in Appendix G, “Sample Tivoli Storage Manager Profiles(UNIX)”, on page 127 and for Windows in Appendix H, “Sample Tivoli StorageManager Profiles (Windows)”, on page 129.


|||||

Tivoli Storage Manager Clients on UNIX SystemsThis section serves as a quick guide for configuring the Tivoli Storage Manager. Itpresents a typical list of actions that the Tivoli Storage Manager installer oradministrator must perform to prepare the Tivoli Storage Manager to operate in anSAP environment.

Follow these steps:1. Install the Tivoli Storage Manager client software on the mySAP.com database

server machine.2. Edit the client system options file dsm.sys and set the following values, as

appropriate to your installation:

Servername server_aTCPPort 1500TCPServeraddress xxx.xxx.xxx.xxxInclExcl /usr/tivoli/tsm/client/ba/bin/inclexcl.listCompression OFF

3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are onthe same machine. This makes TCP/IP communication a little faster.

4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude thefiles listed in inclexcl.list. This is optional. You would usually exclude alldatabase files that were processed by SAPDBA, BRBACKUP, or BRARCHIVE.

5. If you have tape drives with hardware compression attached to the TivoliStorage Manager server, you might get better throughput with the hardwarecompression than you would with the Tivoli Storage Manager client softwarecompression (Compression ON).

NoteDo not compress the data twice!

You will need to try Tivoli Storage Manager client software compression inyour environment to determine whether it is of use for you. In general, theTivoli Storage Manager client software compression improves performance onlywhen network throughput is quite small.

6. Edit the client user options file dsm.opt and set the following values:

LANGUAGE AMENG (this is the default value)NUMBERFormat 1 (this is the default value)TAPEPROMPT NOTIMEFORMAT 1 (this is the default value)

Tivoli Storage Manager Clients on Windows SystemsThis section serves as a quick guide for configuring the Tivoli Storage Manager. Itpresents a typical list of actions that the Tivoli Storage Manager installer oradministrator must perform to prepare Tivoli Storage Manager for operation in amySAP.com environment.

Follow these steps:1. Install the Tivoli Storage Manager client software on the mySAP.com database

server machine.


2. For each logical Tivoli Storage Manager server you need a corresponding clientoption file. In the following example, the file name must be server_a.opt sinceserver_a is the logical server name:

Servername server_aTCPPort 1500TCPServeraddress xxx.xxx.xxx.xxxInclExcl c:\tivoli\tsm\baclient\inclexcl.listCompression OFF

In addition, the environment variables DSM_CONFIG and DSMI_CONFIG must pointto the corresponding client options file, e.g.,c:\tivoli\tsm\baclient\server_a.opt .

3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are onthe same machine. This makes TCP/IP communication a little faster.

4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude thefiles listed in inclexcl.list. This is optional. You would usually exclude alldatabase files that were processed by SAPDBA, BRBACKUP, or BRARCHIVE.

5. If you have tape drives with hardware compression attached to the TivoliStorage Manager server, you might get better throughput with the hardwarecompression than you would with the Tivoli Storage Manager client softwarecompression (Compression ON).

NoteDo not compress the data twice!

You will need to try Tivoli Storage Manager client software compression inyour environment to determine whether it is of use for you. In general, theTivoli Storage Manager client software compression improves performance onlywhen network throughput is quite small.


Chapter 3. Setting Up Data Protection for mySAP.com

The Data Protection for mySAP.com code is typically delivered on CD-ROM andinitial installations must be done from CD-ROM.

If you have already installed a version of Data Protection for mySAP.com, youhave the option to download the latest version from the IBM Tivoli Internet homepage at http://www.ibm.com/software/tivoli.

NoteIf you have been using an older version of Data Protection for mySAP.com inyour environment and you want switch to the most recent version, refer toAppendix C, “Migration from Earlier Releases”, on page 103 for detailedmigration guidelines.

Before you can install an upgrade of Data Protection for mySAP.com on anyplatform, you need to deinstall the old package on your system. Thedeinstallation procedures are described in “Upgrading or Deinstalling DataProtection for mySAP.com” on page 28.

PrerequisitesThere are certain common prerequisites for all UNIX platforms and for Windows.These are the initial setup steps that must be performed:v SAP R/3 3.0C or higher based on an Oracle databasev Tivoli Storage Manager 4.1 (server, client, and API)

To find out which Tivoli Storage Manager levels can be used, see the relevantData Protection for mySAP.com release notes.

v UNIX or Windows operating system at the level supported by mySAP.com andthe Tivoli Storage Manager client.

The following sections explain in more detail the prerequisites for mySAP.com andTivoli Storage Manager.

mySAP.com Database UtilitiesData Protection for mySAP.com can be used for mySAP.com systems with Oracledatabases employing a standard UNIX file system, a Windows file system or rawlogical volumes.v The following SAPDBA database utilities at these minimum levels must be

installed on the mySAP.com database server:– BRBACKUP 3.0C– BRARCHIVE 3.0C– BRCONNECT 3.0C– BRRESTORE 3.0C

Contact SAP support via the Online Service System (OSS) to find out whichfunctions are compatible with a specific SAP R/3 or mySAP.com release. Theappropriate modules can be downloaded from the SAP server (see OSS note19466 for more information).


||

|||

||||

|||

||

||||||

||||


v SAPDBA 3.0C or higher is required if SAP R/3 release 3.0C or higher is used inconjunction with Oracle on raw devices.

Tivoli Storage Manager ClientThe installation and all necessary customizing steps for the Tivoli Storage ManagerClients (Backup/Archive Client for file system backups, API Client for interfaceprograms) must be performed on the mySAP.com database server machine (see“Configuration of Tivoli Storage Manager Clients” on page 16). The Tivoli StorageManager 4.1 client or higher must be installed. The client software is shipped withthe server software.

TCP/IP (UNIX systems) has to be ready for communication between the TivoliStorage Manager Client and Tivoli Storage Manager Server.

After you have ensured that all prerequisites have been met, the installationprocess can begin. 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, andBRARCHIVE should be used. For restore or recovery it is recommended that onlySAPDBA is used.

Installation on UNIX (AIX, Solaris, HP-UX, Linux)Data Protection for mySAP.com for UNIX systems is delivered as a singleexecutable file named

install_tdpr3_ora_<operating system>.binwhere<operating system> is aix43 for AIX 4.3, or

aix51 for AIX 5.1, orsolaris orhpux orlinux

When you invoke the file, you will be guided through the Data Protection formySAP.com setup procedure. To ensure that the setup procedure is carried outproperly, read the following description carefully and follow the guidelines on thepanels that are displayed during setup.

Perform the following steps to install Data Protection for mySAP.com on a UNIXmachine:1. Log in as root user on the mySAP.com database server machine.2. Make sure that you use the file that fits to your Oracle database.3. The installer guides you through the installation via a graphical X-Window.

Ensure that you have set the DISPLAY variable correctly.4. Invoke the Data Protection for mySAP.com executable file that fits your Oracle

database.5. The “Welcome” panel comes up. Click on Next.6. Read the license agreement carefully and decide whether to accept it or not.

Click on Next.7. Enter the Oracle SID. This is the name of the Oracle instance for which you

want to use Data Protection for mySAP.com. Click on Next.8. The installer needs the location of two directories:


||

||

|

||

||

|||||

||||

||

|

|

||

||

|

||

||

|

v Directory for executables.This is the directory where the SAP BR-Tools are located. In the directory,the installer creates soft links to the backint and backfm executables.

v Directory for the configuration files:This is the directory where the Oracle instance configuration file(init<SID>.ora) and the SAP configuration file for backup/restore(init<SID>.sap) are located. The installer will copy the following files intothat directory: init<SID>.utl, init<SID>.bki, agent.lic

Noteagent.lic is not included if you have downloaded the installationpackage from the Web.<SID>must be replaced by the Oracle SID.If the configuration files were already installed by an earlierinstallation, the files will not be overwritten.

Click on Next.9. If you want Data Protection for mySAP.com to connect to the Administration

Assistant Server you have to specify the connection information:v Network address of the Administration Assistant

You can either specify the IP address or the host name.v Port number of the Administration Assistant

NoteIf you don’t specify a Network address Data Protection for mySAP.comwon’t connect to the Administration Assistant.For more information about the Administration Assistant see Chapter 7,“Administration Assistant for Data Protection for mySAP.com”, onpage 63.

Click on Next.10. On the next panel, you can decide if you want the installer to help you with

the connection settings for the TSM server:If you select No, the current settings will be retained, these are either thedefault settings or the values you set for an earlier release of Data Protectionfor mySAP.com.If you select Yes, the installer will update the Data Protection for mySAP.comconfiguration file init<SID>.utl with the information you provide in thesefields:v TSM server

Enter the TSM server name. This name must also exists in the TSM filedsm.sys.

v TSM node namev Backup management classes

TSM management classes used by a brbackup runv Archive management classes

TSM management classes used by a brarchive run

Click on Next.

Chapter 3. Setting Up Data Protection for mySAP.com 21

|||

||||||

|||||||||

|

||

||

||

|||||||||

|

||||||||

|||

|

||

||

|

11. If you want to install the RMAN support, click on Yes otherwise, click No.For more information about RMAN support, see Appendix B, “Using DataProtection for mySAP.com with RMAN”, on page 99.

12. Click on Next until the installation is complete.

During the installation, the following files are updated automatically:v an entry will be created in/etc/inittab to start the background process prolev an entry will be created in/etc/services needed for internal communication.

After the installation, the TSM password handling method is set toPASSWORDACCESS promptIf you want to use a different method, refer to “Password Handling” on page 26.

The configuration of Data Protection for mySAP.com is done with the followingbasic performance setting:v Multiplexing 1

v Parallel Sessions 1

To tailor the settings to your requirements, see “Customizing Data Protection formySAP.com and SAP Backup Profiles” on page 25.

To be able to work with Data Protection for mySAP.com, you have to provide DataProtection for mySAP.com with the password for the TSM node.This is a manual step on the shell:13. Log on as Oracle user.14. Enter the following command

backint -p <full path to UTL file>init<SID>.utl -f password

Enter the password when prompted.

Installation on WindowsData Protection for mySAP.com for Windows is delivered as a single executable filenamed install_tdpr3_ora_win_32bit.exe.

When you invoke the file, you will be guided through the Data Protection formySAP.com setup procedure. To ensure that the setup procedure is carried outproperly, read the following description carefully and follow the guidelines on thepanels that are displayed during setup.

Perform the following steps to install Data Protection for mySAP.com on aWindows system:1. Log in as administrator user on the mySAP.com database server machine.2. In Windows Explorer, navigate to the directory where the installation package

is located.3. To start the setup procedure, double-click on the executable.4. The “Welcome” panel comes up. Click on Next.5. Read the License Agreement carefully and decide wether to accept it or not.

Click on Next.6. Enter the Oracle SID. This is the name of the Oracle instance for which you

want to use Data Protection for mySAP.com. Click on Next.7. Enter the installation path for Data Protection for mySAP.com. Click on Next.8. The installer needs the location of these three directories:


|||

|

|

|

|

|||

||

|

|

||

|||

|

|

|

|

||

|

||

|

|

||

||

|

|

v Directory for executables.This is the directory where the SAP BR-Tools are located. The installer willcopy the following executables into that directory:backintbackfm

v Directory for the configuration files:This is the directory where the Oracle instance configuration file(init<SID>.ora) and the SAP configuration file for backup/restore(init<SID>.sap) are located.The installer will copy the following files into that directory: init<SID>.utl,init<SID>.bki, agent.lic

Noteagent.lic is not included if you have downloaded the installationpackage from the Web. <SID>will be replaced by the Oracle SID. Ifthe configuration files were already installed by an earlier installationthe files will not be overwritten.

v Directory for the TSM configuration file:The TSM API looks for its option file dsm.opt in this directory. The installerwill copy the following sample files into that directory:dsm.optserver_a.optserver_b.opt

Click Next.9. If you want Data Protection for mySAP.com to connect to the Administration

Assistant server, you have to specify the connection information:v Network address of the Administration Assistant

You can specify either the IP address or the host namev Port number of the Administration Assistant

NoteIf you don’t specify a Network address, Data Protection for mySAP.comwon’t connect to the Administration Assistant.For more information about the Administration Assistant see Chapter 7,“Administration Assistant for Data Protection for mySAP.com”, onpage 63.

Click on Next.10. For proper operation of the TSM API, the following environment variables

should be set:

DSMI_DIRTSM client installation directory.

DSMI_CONFIGThe variable must be set to the TSM API configuration file dsm.optwith fully qualified path.

DSMI_LOGA temporary directory where TSM API writes its error log file to.


|||

||

|||||||

||||||||

|||

|||

|

||

||

||

|||||||||

|

||

||

|||

||

Use the radio button to decide if the installer updates the environmentvariables as specified in the panel or if they are to be left unchanged.

11. On the next panel, you can decide if you want the installer to help you withthe connection settings for the TSM server:If you select No, the current settings will be retained, these are either thedefault settings or the values you set for an earlier release of Data Protectionfor mySAP.com.If you select Yes, the installer will update the Data Protection for mySAP.comconfiguration file init<SID>.utl and the file server_a.opt with theinformation you provide in these fields:

TSM ServerEnter the TSM server name. You can specify either the IP address orthe host name.

TSM node name

backup management classesTSM management classes used by a brbackup run

archive management classesTSM management classes used by a brarchive run

Click on Next.12. Click Next until the installation is complete.

During the installation, the following files are updated automatically:v an entry will be created in/etc/inittab to start the background process prolev an entry will be created in/etc/services needed for internal communication.

After the installation, the TSM password handling method is set toPASSWORDACCESS promptIf you want to use a different method, refer to “Password Handling” on page 26.

The configuration of Data Protection for mySAP.com is done with the followingbasic performance setting:v Multiplexing 1

v Parallel Sessions 1

To tailor the settings to your requirements, see “Customizing Data Protection formySAP.com and SAP Backup Profiles” on page 25.

To be able to work with Data Protection for mySAP.com, you have to provide DataProtection for mySAP.com with the password for the TSM node.This is a manual step on the shell:13. Log on as Oracle user.14. Enter the following command:

backint -p <full path to UTL file>init<SID>.utl -f password

Enter the password when prompted.


||

||||||||

|||

|

||

||

|

|

|

|

|

|||

||

|

|

||

|||

|

|

|

|

Customizing Data Protection for mySAP.com and SAP Backup ProfilesIn this section we will discuss customizing the Data Protection for mySAP.comprofile (init<SID>.utl) and the SAP Backup profile (init<SID>.sap). These profilesmust be customized, because they are not initially suitable for working with DataProtection for mySAP.com.The installed profile only exists as a sample showing what a typical profile couldlook like.

A detailed description of all possible profile keywords can be found in Appendix F,“The Data Protection for mySAP.com Profile”, on page 115.

The Data Protection for mySAP.com profile has to be customized with somefundamental entries so that Data Protection for mySAP.com will work in all cases

(backup, restore, inquire, delete). Special customizing, however, such as to obtainenhanced performance, etc., will not be discussed here. For details on this, seeChapter 6, “Considerations for Optimizing Backup/Restore Performance”, onpage 53.

The profiles that must be customized can be found on UNIX systems in the path/oracle/<SID>/dbs and on Windows systems in the path<drive>:\orant\database.

A set of essential Data Protection for mySAP.com profile entries (keyword with anappropriate parameter) must be set or changed. These are:

BACKUPIDPREFIXPrefix of the ’Backup ID’ that will be used for the communication withSAPDBA. The default is ’SAP___’. A good value would be ’SID___’ (theSID of the database instance to backup followed by three underscorecharacters). If more than one database instance will be handled on thesame maschine, every instance should use its own profile. Do not use thesame BACKUPIDPREFIX more than once on a machine.

BRARCHIVEMGTCLASSSpecifies the Tivoli Storage Manager management class Data Protection formySAP.com uses when called from BRARCHIVE.

BRBACKUPMGTCLASSSpecifies the Tivoli Storage Manager management class Data Protection formySAP.com uses when called from BRBACKUP.

CONFIG_FILESpecifies the configuration file (init<SID>.bki) for Data Protection formySAP.com. The CONFIG_FILE should never be shared among multipledatabase instances. Otherwise versioning may not work correctly.

MAX_SESSIONSNumber of total parallel sessions which will be established by DataProtection for mySAP.com. This number should correspond with thenumber of simultaneously available tape drives specified for the TivoliStorage Manager server. Default is ’1’.

MAX_VERSIONSDefines the maximum number of database backup versions to be kept inbackup storage. Default is ’0’, meaning that Data Protection formySAP.com versioning is disabled


|||||

||

SERVERSpecifies the Tivoli Storage Manager server used. This value mustcorrespond to an entry in the dsm.sys file on UNIX systems. On Windowssystems, Data Protection for mySAP.com uses a separate Tivoli StorageManager API client option file for each Tivoli Storage Manager server. Sucha file must have the file name server.opt, where server stands for the nameyou gave the Tivoli Storage Manager server.

SESSIONSNumber of Tivoli Storage Manager sessions that can be started by DataProtection for mySAP.com for the corresponding server. Default is ’1’.

The configuration of the SAP Backup profile, which is part of the mySAP.cominstallation, refers to three keywords within that file. These keywords are:

backup_dev_typeDetermines the backup medium that will be used (default is tape).

backup_typeIdentifies the default type of the database backup. This parameter is onlyused by BRBACKUP (default is offline).

util_par_fileThis parameter specifies where the parameter file, which is required for abackup with an external backup program, is located.

Data Protection for mySAP.com supports, for example, the combinations of thekeywords backup_dev_type and backup_type shown in the table below.

Table 1. SAP Backup Profile Parameter Combinations

Operation backup_dev_type backup_type

Offline backup util_file offline

Online backup util_file online

Online backup withindividual tablespacelocking

util_file_online online

To carry out online backups with individual tablespace locking (see “IndividualTablespace Locking” on page 5) with the external backup program Data Protectionfor mySAP.com, the SAP Backup profile parameter must be set or changed asshown below:

backup_type = onlinebackup_dev_type = util_file_onlineutil_par_file = ?/dbs/[email protected]

The question mark is the official Oracle substitute symbol for the home directoryof the database system, for example, /oracle/C21.

Password HandlingBefore testing to see whether the profiles have been configured correctly, thepassword handling has to be clarified (see Appendix D, “Password Handling”, onpage 105). You can choose between manual password handling and automatic passwordhandling.


If you are using manual password handling, you must provide the password neededfor a client connection to Tivoli Storage Manager which was specified when thenode ID was initially registered within Tivoli Storage Manager (see “NodeDefinition” on page 15). The password is requested initially and again each time itexpires for this node within Tivoli Storage Manager. Normally, you will beprompted for the client password each time Data Protection for mySAP.com startsa Tivoli Storage Manager session. To avoid this, the client password can be storedin encrypted form within the Data Protection for mySAP.com 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 systems:

backint -p <drive>:\orant\database\init<SID>.utl -f password

Data Protection for mySAP.com prompts for all required passwords which were setfor the appropriate Tivoli Storage Manager (this depends on how many TivoliStorage Manager servers were declared in the Data Protection for mySAP.comprofile) and checks whether the passwords are valid. If a connection between DataProtection for mySAP.com and Tivoli Storage Manager is to be established, DataProtection for mySAP.com reads the password from the configuration file and usesit for registration on the Tivoli Storage Manager server.

If you are using automatic password handling, you need to:1. update the password on the Tivoli Storage Manager server2. log on once using the above password function on the client node

When the password expires, a new password will be generated automatically.

Depending on the password handling method you want to use, you have to makethe following settings on the Tivoli Storage Manager and on the Data Protectionfor mySAP.com side:

Table 2. Required Settings for Password Handling

Manual Password HandlingAutomatic PasswordHandling

Tivoli Storage Manager clientoptions file settings

PASSWORDACCESS promptPASSWORDACCESS generatePASSWORDDIR <path>

Data Protection formySAP.com profile settings

PASSWORDREQUIRED yes PASSWORDREQUIRED no

On UNIX systems, the users <SID>adm and ora<SID>, and on Windows systems,the users <SID>adm and sapservice<SID> must have read and write permission tothe path specified in the PASSWORDDIR keyword in the Tivoli Storage Managerclient options file.

Verifying the InstallationBefore verifying the installation, make sure that all files in the Data Protection formySAP.com installation directory on UNIX systems have the owner root, the groupsystem, and execute permissions for all users.The sticky bit must not be set except for BACKAGENT, if data backed up with


|

|

|

|

|||

||

||||

|||||

||||

|||||

Data Protection for mySAP.com Version 2.7 needs to be restored. For furtherinformation see: Appendix C, “Migration from Earlier Releases”, on page 103. Forthis function to work properly, issue the following commands:

chown root backagentchgrp dba backagentchmod 4750 backagent

There is no verification procedure provided with Data Protection for mySAP.com.To verify and test the installation, it is recommended that you try out a smallbackup procedure (tablespace backup) using SAPDBA and start a full online oroffline backup using BRBACKUP as shown below.

brbackup -c -t online (online database backup)brbackup -c -t offline (offline database backup)

It is also strongly recommended that you do a restore/recovery of the wholemySAP.com database (using SAPDBA). A good method to prepare for this is tofirst run a complete offline backup using BRBACKUP.

Step by step scenarios for backup or restore/recovery procedures of an mySAP.comOracle database using Data Protection for mySAP.com can be found in the IBMredbook SAP R/3 Data Management with Tivoli Storage Manager, SG245743.

NoteIBM redbooks can be found at http://www.redbooks.ibm.com

Upgrading or Deinstalling Data Protection for mySAP.comBefore upgrading Data Protection for mySAP.com to a higher level, you have todeinstall the old package on your system as described in the following sections.Your configuration files are retained. If you have installed Data Protection formySAP.com for databases other than Oracle, you only have to deinstall DataProtection for mySAP.com for Oracle.

The installation of the new package is described in Chapter 3, “Setting Up DataProtection for mySAP.com”, on page 19.

Deinstallation on UNIX (AIX, Solaris, HP-UX, Linux)Perform the following steps to deinstall Data Protection for mySAP.com on a UNIXmachine:1. Log in as the root user on the mySAP.com database server machine.2. Ensure that Data Protection for mySAP.com is not running.3. The uninstaller guides you through the deinstallation procedure via a graphical

X-Window. Ensure that you have set the DISPLAY variable correctly.4. Call the uninstaller executable and follow the instructions of the deinstall

procedure. The executable is located in one of the following directories:v Solaris 32-bit:

/opt/tivoli/tsm/tdp_r3/ora/_unist/uninstaller.bin

v Solaris 64-bit:/opt/tivoli/tsm/tdp_r3/ora64/_unist/uninstaller.bin


|||

||

||

|

|

|

|

v other UNIX 32-bit:/usr/tivoli/tsm/tdp_r3/ora/_unist/uninstaller.bin

v other UNIX 64-bit/usr/tivoli/tsm/tdp_r3/ora64/_unist/uninstaller.bin

Deinstallation on WindowsPerform the following steps to deinstall Data Protection for mySAP.com on aWindows NT or Windows 2000 machine:1. Log in as the administrator user on the mySAP.com database server machine.2. Ensure that Data Protection for mySAP.com is not running.3. Select Start → Settings → Control Panel.4. Click on Add/Remove Programs.5. Select DP for mySAP.com Technology and click on Remove.6. Follow the instruction of the deinstall procedure.


|

|

|

|

|

||

|

|

|

|

|

|


Chapter 4. Using Data Protection for mySAP.com to Back Upand Restore Files and Databases

GeneralData Protection for mySAP.com provides a set of functions that are needed forbackup and restore operations within an mySAP.com Oracle database environment.Data Protection for mySAP.com will be invoked with a set of appropriateparameters by the SAP database utilities (SAPDBA, BRBACKUP, BRARCHIVE,BRRESTORE) with one of the functions defined within the SAP BACKINT interfacedescription. These are:v backupv inquirev restore

A delete function is also available. It is used as part of the versioning controlmechanism of Data Protection for mySAP.com (see “Backup by Version” on page 5)and can only be called by Data Protection for mySAP.com itself or by a user butnot by any of the SAP database utilities.

Furthermore, it is possible to use Data Protection for mySAP.com to performbackup and restore operations directly from the command line. The command:

backint -?

displays a list of all possible Data Protection for mySAP.com command lineoptions.

Backup FunctionThe backup function will be normally invoked by the SAP database utilitiesBRBACKUP and BRARCHIVE. These programs give Data Protection formySAP.com an input file (in the case of backup and inquire) containing the namesand paths of the database files to be handled. However, it is possible to call DataProtection for mySAP.com directly to back up individual files. See the followingexample.

For UNIX systems:

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


backint -p <drive>:\orant\database\init<SID>.utl -f backup

NoteThe Data Protection for mySAP.com profile init<SID>.utl has to be specifiedwith the path and file name statement as shown above.


The program prompts you to enter one or more file names. Every successfulbackup run (collection of one or more files) is allocated its own backup ID withinTivoli Storage Manager.

Inquire FunctionThe inquire function, normally invoked by SAPDBA and BRRESTORE, will beused to query the Tivoli Storage Manager server for backup IDs or files whichbelong to a particular backup ID. Also, this function can be invoked manually fromthe command line as follows.

For UNIX systems:

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


backint -p <drive>:\orant\database\init<SID>.utl -f inquire

Data Protection for mySAP.com prompts you to enter the inquiry in one of fourformats. These are:1. #NULL - to display all backup IDs saved so far. A typical line of the response

could be:#BACKUP C21___9910291715

The backup ID in this case is C21___9910291715 (#BACKUP does not belong to thebackup ID). The first six characters are the user defined prefix (see“Customizing Data Protection for mySAP.com and SAP Backup Profiles” onpage 25). The next 10 characters after this represent a unique ID of the backup.

2. BackupID - to display all of the files which belong to that backup ID. A typicalresult could be:#BACKUP C21___9910291316 /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 acertain backup ID. Filename requires an input consisting of path and name ofthe file.

Restore FunctionThe restore function will be normally started by the SAP database utilityBRRESTORE. This program gives Data Protection for mySAP.com an inputfilename. This file contains the backup ID and the corresponding file namesincluding their paths. However, it is possible to call Data Protection formySAP.com directly to restore individual files. This function can be invoked fromthe command line as follows.

For UNIX systems:

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



backint -p <drive>:\orant\database\init<SID>.utl -f restore

You will be prompted to enter the backup ID and the full file names of the files tobe restored. If the files are to be restored to another directory, it is necessary tospecify the path to the input files.

CautionIf a file is restored directly, any existing file with the same name will beoverwritten without warning. Thus, it is recommended that you never restoredatabase files directly, because this could corrupt the mySAP.com database.

Data Protection for mySAP.com File ManagerThe Data Protection for mySAP.com File Manager is a utility that simplifies theData Protection for mySAP.com inquire, restore, and delete operations for the user.It can be seen as an add-on to Data Protection for mySAP.com.

NoteOnly users with a good knowledge about the restore and recoverymechanism of Oracle databases should use this tool. The generalrecommendation is that you should normally use the tools SAPDBA andBRRESTORE provided by SAP for restore operations.

The Data Protection for mySAP.com File Manager uses the standard functionsprovided by Data Protection for mySAP.com to perform all operations. The DataProtection for mySAP.com File Manager user interface consists of a split characterbased window.

All backup IDs found on all Tivoli Storage Manager servers which were configuredwithin the Data Protection for mySAP.com profile are shown on the left. To theright 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 deleteoperations (see Figure 3 on page 34).

The Data Protection for mySAP.com File Manager has to be started with the pathand name of the Data Protection for mySAP.com profile (the user must be amember of the dba group). See the following examples.

For UNIX systems:

backfm -p /oracle/SID/dbs/init<SID>.utl


backfm -p <drive>:\orant\database\init<SID>.utl

The Data Protection for mySAP.com File Manager will now establish a connectionto all Tivoli Storage Manager servers which were configured in the Data Protectionfor mySAP.com profile. The next step is an automatic inquire operation for allbackup IDs. The following figure shows the display of a set of backup IDs located

Chapter 4. Backup and Restore 33

by the Data Protection for mySAP.com File Manager after having finished aninquiry 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 markedbackup ID will be displayed as shown in the figure below.

The following function keys are defined for performing restore or deleteoperations:

Figure 2. File Manager — Result of an Inquiry Procedure

Figure 3. File Manager — Result of an Inquiry Procedure Showing File Names


Up, Down, Left, Right - Move cursorMove the highlighted cursor in the direction indicated on the key.

Tab - Switch window sideMove the cursor between the left and right sides of the window.

F2 - RestoreRestore all marked files. Before the restore actually begins, you can specifya common destination path and you will be asked to confirm the restoreprocess. If you specify a destination path, all marked files will be restoredto that directory. Otherwise the files will be restored to the directory fromwhich they were backed up.

F3 - Mark allAll files belonging to the current backup ID will be marked.

F4 - Unmark allUnmark all files belonging to the current backup ID.

F5 - RefreshRefresh the list of backup IDs and file names.

F6 - FileinfoOpens a separate window to display file information.

For backup IDs, the sequence number is displayed (backup version count,see “Backup by Version” on page 5). For files, the Tivoli Storage Managerexpiration date and time is displayed.

F8 - DeleteDelete the selected backup ID and all corresponding files. This function isavailable only when the cursor is on top of a backup ID.

F10 - ExitExit from Data Protection for mySAP.com File Manager

ENTER - Mark/unmark fileMark 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 werefound or with the ENTER key to mark only one desired file. Marked files can beidentified by the symbol ″* ″ in front of the filename. Only the marked files will berestored or deleted. Single backup IDs can also be deleted, in which case theselected backup ID and its corresponding files will be removed from the TivoliStorage Manager server.

mySAP.com Backup and Recovery Using Data Protection formySAP.com

The backup and restore/recovery scenarios presented in the following sections aremeant to illustrate a general strategy for using Data Protection for mySAP.com in amySAP.com environment. Your actual backup/restore scenario may be quitedifferent. Hence, when performing a real backup/restore, consult your SAP onlinedocumentation to see how this should be done exactly.

The scenarios in the first section show how a backup can be started:v Full online/offline backup with BRBACKUPv Tablespace backup with SAPDBA.


|||||

The second section shows a restore of an mySAP.com tablespace and a subsequentrecovery of the mySAP.com database with the help of SAPDBA.

In the following examples it is assumed that the mySAP.com system is installed ona UNIX machine.

Backup ScenariosA backup is essential for a subsequent restore and recovery. Two backup methods,one using BRBACKUP directly and the other using BRBACKUP via SAPDBA, willbe described. These SAP database utilities can store the backed up data on theTivoli Storage Manager server with the help of Data Protection for mySAP.com.

Online/Offline Backup with BRBACKUP:BRBACKUP is a database utility provided by SAP to perform a backup function ofthe mySAP.com Oracle database. You can use BRBACKUP to back up the followingobjects of an Oracle database:v Data filesv Control filesv Online redo log files

BRBACKUP can be invoked directly from the operating system command level,using the SAPDBA backup function or from mySAP.com within the ComputingCenter Management System (CCMS). For further information about BRBACKUPsee 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 thecommand:

brbackup -help

To start an online backup of the mySAP.com database, the following command hasto be executed:

brbackup -c -t online

The parameter -c is used to enable the backup to run in unattended mode so thatno further user input during the backup operation is required. Commandparameter -t online specifies the backup as an online backup.

NoteThe mySAP.com database must be running in ARCHIVE mode if you want toperform online backups. This means the online redo logs, in which alldatabase changes are recorded, will be archived before they are overwritten.

In a similar manner, an offline backup can be invoked by BRBACKUP. But youhave to consider whether the mySAP.com database is running or not.

If the database is running, BRBACKUP first shuts down the database instance.Therefore, BRBACKUP must be started with the offline_force parameter.

brbackup -c -t offline_force


If the backup is finished, BRBACKUP starts the mySAP.com database instanceagain. If the earlier mySAP.com database instance has been stopped, BRBACKUPcan be started with the normal offline parameter.

brbackup -c -t offline

During the backup, several screen messages will be issued. Each message has itsown message code. By means of this code the messages can be classified into:v Error messages - last letter of a message code is an ″E″

v Warning messages - last letter of a message code is a ″W″

v Informational messages - last letter of a message code is an ″I″

All these messages codes have a specific prefix. This prefix shows from whichprogram a message was generated. The various prefixes are:v ANS/ANR - ADSM or Tivoli Storage Manager messagesv BKI - Data Protection for mySAP.com messagesv BR - BRARCHIVE, BRBACKUP or BRRESTORE messagesv ORA - Oracle database kernel messagesv RMAN - Oracle Recovery Manager messages

After BRBACKUP has finished, it is recommended that you check the backupprotocol 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 backedup files should be preceded by #SAVED. An error occurred if there are any #ERROR or#NOTFOUND messages.

If an error occurs, the first step is to check the content of the protocol describedabove. First of all, you should locate the error messages and, with use of theappropriate manual, you can relate the message code to an explanation about theerror that occurred and a recommendation for user response.

Tablespace Backup With SAPDBA:The management or administration of an mySAP.com Oracle database generallycannot be carried out from within the SAP system itself. As a result, SAP hasdeveloped a tool called SAPDBA to provide and simplify the administration of theOracle database system. Among other things, SAPDBA provides an extensivebackup function for a full database backup, backup of selected tablespaces, andbackup of offline redo logs. For these backup operations SAPDBA invokes theappropriate database utilities BRBACKUP or BRARCHIVE. Further informationabout SAPDBA can be found in the SAP online documentation.

The following shows an example backup of an mySAP.com tablespace, calledPSAPUSER1D.

To invoke SAPDBA, it is necessary to log on as ora<SID> . After SAPDBA starts,the following screen will appear:


___________________________________________________________________________SAPDBA V4.5B - SAP Database Administration

___________________________________________________________________________Oracle version: 8.0.5.2.0ORACLE_SID : C21ORACLE_HOME : /oracle/C21DATABASE : openSAPR3 : 45B, 7 times connected

a - Startup/Shutdown instance h - Backup databaseb - Instance information i - Backup offline redo logsc - Tablespace administration j - Restore/Recoveryd - Reorganization k - DB check/verificatione - Export/import l - Show/Cleanupf - Archive mode m - User and Securityg - Additional functions n - SAP Online Help

q - Quit

Please select ==>

To carry out tablespace backup, the Backup database functions have to be startedwith the h key which causes the following screen to pop up:

___________________________________________________________________________Backup database

___________________________________________________________________________Current value

a - Backup function Normal backupb - Parameter file initC21.sapc - Backup device type util_file_onlined - Objects for backup alle - Backup type onlineg - Query only noh - Special options ...

i - Standard backup yesj - Backup from disk backupk - Restart backupl - Make part. backups compl.

S - Start BRBACKUPq - Return

Please select ==>

As already mentioned in “Customizing Data Protection for mySAP.com and SAPBackup Profiles” on page 25, the SAP Backup profile initC21.sap has to becorrectly customized in view of:v The backup type (online, offline) andv The backup utility parameter file

To check the backup utility parameter file (in case of Data Protection formySAP.com 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 keyand the following screen will be displayed:


___________________________________________________________________________Backup database: Details

___________________________________________________________________________Current value

a - Confirm backup parameters nod - Backup utility parameter file /oracle/C21/dbs/initC21.utle - Enter password interactively noi - Language English

q - Return

Please select ==>

If everything was set correctly, go back with the q key to the Backup databasescreen as shown above.

Now you have to specify the object(s) which you want to back up. This can bedone by choosing the Objects for backup option with the d key within the Backupdatabase menu. The following screen appears:

Format for the desired objects for backup: <item> or <item>,<item>,...An <item> can be- "all"- "all_data"- "sap_dir"- "ora_dir"- a tablespace_name- an Oracle file id <number> or a range of file ids <number>-<number>- an absolute file or directory name

Enter objects for backup ==>

Enter the desired name of the tablespace for the backup, in this case psapuser1d. Ifyou have returned to the Backup database screen you can start the backupprocedure by selecting the Start BRBACKUP function (S key). All the otherparameters which are visible and were not discussed should not be changed. Theseare default parameters set by SAPDBA. For further information about this see theSAPDBA manual.

After starting the backup procedure BRBACKUP starts Data Protection formySAP.com to send the data files belonging to the tablespace PSAPUSRE1D to theTivoli Storage Manager server. The backup is successfully finished if there is amessage such as the following on the screen:


BR056I End of database backup: bdbhowho.pnf 1999-11-08 11.19.42BR052I 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 aBRBACKUP log file which will be stored in the /oracle/C21/sapbackup directorywith 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 ScenarioIf you need to do a restore/recovery of the mySAP.com database as a result ofcorruption or loss of data files, the recommendation is to use the SAPDBAdatabase utility for this action because it guides you, step by step, through allnecessary procedures. For the automatic recovery mode these are:v Check databasev Find backup filesv Restore backup filesv Find archive filesv Restore archive filesv Recover database

SAPDBA uses the program BRRESTORE for restoring the database. This programinvokes Data Protection for mySAP.com for restoring all the necessary tablespacefiles or archived redo log files from the appropriate Tivoli Storage Manager server.After the restore has finished successfully, the necessary recovery will beperformed by SAPDBA.

The following describes two possible recovery scenarios: The recovery of a singlemySAP.com tablespace and a complete (full) recovery of the mySAP.com databasein 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 tothe tablespace PSAPUSER1D (for example data file corruption or loss of a data file).

After starting SAPDBA, the initial SAPDBA screen as shown on page 38 appears.

NoteRestore and recovery operations within SAPDBA can only be done in theso-called expert mode. For information on how to switch to that mode see theSAPDBA manual.

To perform a tablespace restore/recovery the Restore/Recovery function has to bestarted by pressing the j key. The following screen appears:


___________________________________________________________________________

Restore/recovery___________________________________________________________________________

a - Partial restore and complete recovery (Check andrepair, 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 tablespacee - Restore individual file(s)q - Return

Please select ==>

In this case, only a partial restore (data files for the tablespace PSAPUSER1D) is to becarried out, with a complete recovery of the mySAP.com 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 finishedb - Find backup files not finishedc - Restore backup files not finishedd - Find archive files not finishede - Restore archive files not finishedf - Recover database not finished

g - Automatic recovery

q - Return

Please select ==>

All the functions seen in this screen must be carried out in alphabetical order,unless you use the Automatic recovery function which is activated with the g key.The Automatic recovery function runs through all of the above functions startingwith Check database and ending with Recover database. If an error occurredduring this process, the automatic recovery stops at the function where the erroroccurred.

After beginning the automatic recovery procedure, a number of screen messageswill be seen, most of them only for informational purposes to describe theprogress. In some cases, confirmation in the form of Press <return> to continueor yes without any further information may be requested. Read all the instructionson the screens carefully and wherever possible follow the recommendations ofSAPDBA.


Full Recovery:In some cases, a full recovery of the mySAP.com database must be initiated, suchas in the case of loss of several data files. This means that all necessary:v data filesv redo log filesv control files

must be restored and the database subsequently recovered.

As SAPDBA provides a function for carrying out a full restore/recovery, it isrecommended that, as with the partial restore/recovery, you also use SAPDBA toperform a guided full recovery of the mySAP.com database.

In contrast to the partial restore, to start the full recovery select the function Fullrestore and recovery by pressing the b key in the following screen (to reach thisscreen see “Recovery of a Tablespace” on page 40).

___________________________________________________________________________

Restore/recovery___________________________________________________________________________

a - Partial restore and complete recovery (Check andrepair, 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 tablespacee - Restore individual file(s)q - Return

Please select ==>

When beginning the full restore/recovery, SAPDBA recommends backing up thewhole database if the database is not damaged. Otherwise, at least a backup of theredo log files is recommended.

The next step is to select a full online/offline backup previously made. This can bedone with the function Select a full online/offline backup by pressing the Akey. If no backup has been previously carried out, the restore/recovery status isdisallowed (see screen below).


___________________________________________________________________________Full Restore and Recovery

___________________________________________________________________________DATABASE STATE : mountedRESTORE / RECOVER: disallowed (see status)

Current settingA - Select a full online/offline backupb - Recover until nowc - Show statusD - Restore and recover

q - Return

Please select ==> A

1-bdbeejyv.aff 1999-10-21 12.20.41 ALL offline db_to_util_file2-bdbejsiq.anf 1999-10-22 14.19.44 ALL online db_to_util_file_online3-bdbfefgf.anf 1999-10-26 18.23.49 ALL online db_to_util_file_online4-bdbfhuiv.anf 1999-10-27 11.52.45 ALL online db_to_util_file_online5-bdbfroqz.anf 1999-10-29 11.38.01 ALL online db_to_util_file_online6-bdbghtwj.anf 1999-11-01 17.43.37 ALL online db_to_util_file_online7-bdbgljpc.anf 1999-11-02 11.19.32 ALL online db_to_util_file_online8-bdbgqlxo.aff 1999-11-03 12.10.24 ALL offline db_to_util_file9-bdbgwhhw.aff 1999-11-04 16.36.08 ALL offline db_to_util_file

Please, enter the number of the BRBACKUP run that you want to restore(q = quit) [9] ==> 9

It is recommended that you use the latest BRBACKUP run for the restore function.In the above case this is selection 9.

After you have completed this, SAPDBA will try to find archive files using theinquire function of Data Protection for mySAP.com. Ensure that the SAP Backupprofile initC21.sap is properly customized (see also “Customizing Data Protectionfor mySAP.com and SAP Backup Profiles” on page 25). If SAPDBA returns to thefull restore and recovery screen, the restore/recovery status will have beenchanged to allowed.

By selecting restore and recover (by pressing the D key), the restore/recoveryprocedure can be started.

All the steps which are now carried out are similar to those in the section“Recovery of a Tablespace” on page 40. The only difference is that a check of thedatabase to see which files are missing is not performed, because all data files, allcontrol files, and all necessary redo log files will be restored anyway.Subsequently, the recovery of the database will be commenced.



Chapter 5. Backup Strategy and Backup Automation

This section describes how to define an appropriate backup strategy for yourmySAP.com system. It is intended as a supplement to your mySAP.com, Oracle,and Tivoli Storage Manager documentation.

There are several requirements that your strategy must meet. The most importantfactors you need to consider include:v The types of events you wish to protect your mySAP.com system againstv How quickly you need to be able to return to normal operation after a failurev The intervals and times of day during which backups can be performedv The events and points in time you need to be able to recover, depending on the

type of outage

Data Protection for mySAP.com lets you back up mySAP.com database data usingthe SAP backup interface BACKINT directly to Tivoli Storage Manager storage.However, these backups, which use the SAP database utilities BRBACKUP andBRARCHIVE, are only backups of the database or the database offline redo logs.

Hence, to protect your complete system against failures affecting SAPDBA or othermySAP.com system data, you should use standard Tivoli Storage Managercommands or the Tivoli Storage Manager graphical user interface (GUI) toadditionally backup this system data.

To even be prepared for recoveries from severe disasters (such as fire or waterdamage), the procedures described below must become an integral part of youroverall disaster recovery plan.

Planning a Backup Strategy for the Operating SystemIn order to be protected against a complete loss of the operating system, it isimperative that after:v the installation of the operating systemv updates/upgrades of the operating system

appropriate system backups are made with the operating system dependentutilities, e.g. mksysb for AIX.

This will allow you to start your system from the backup medium. Base backupsshould include a configured TCP/IP environment as well as the Tivoli StorageManager client including the API in order to be able to restore all user dependentdata.

Planning a Backup Strategy for Your Oracle DatabaseIn order to be able to recover from:v user errorsv statement failuresv transaction failuresv media failures


||||

|

that could affect your Oracle database, save the following objects on a regularbasis:v Data filesv Control filesv Online redo logsv 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 backupoccurs.

NoteOracle provides mirroring of the control and online redo log files to protectthe running database system against corruption of these active files. (The AIXLVM facilities can also be used to mirror these files.)

Offline redo logs are saved by BRARCHIVE. You can specify that the redo logs areto be deleted from their original location when BRARCHIVE completessuccessfully. Additional information on BRARCHIVE operations can be found inAppendix K, “Tips and Hints for BRARCHIVE”, on page 139.

Apart from backing up all database relevant data (data files, control file, onlineredo log files, and offline redo log files) it is also recommended that you back upv SAP system datav Oracle system datav Operating system data

This data should be backed up with the incremental backup function of the TivoliStorage Manager backup/archive client.

Figure 4 on page 47 shows the various backup scenarios within a mySAP.comdatabase server machine.


The database itself is backed up with Data Protection for mySAP.com, whereas theSAP, Oracle and operating system protocols are backed up directly by the TivoliStorage Manager.

Planning a Backup Strategy for Backup Protocols and ProfilesEvery BRBACKUP and BRARCHIVE run is divided into two parts. The first partbacks up objects such as:v mySAP.com data filesv database control filesv online redo log filesv offline redo log files

depending on the action started (see previous section).

The second part of a BRBACKUP or BRARCHIVE is responsible for backing up thefollowing profiles:v init<SID>.dba (SAPDBA profile)v init<SID>.ora (Oracle profile)v init<SID>.sap (SAP backup profile)v init<SID>.utl (Data Protection for mySAP.com profile)

and the protocol filesv back<SID>.log (BRBACKUP summary log)v arch<SID>.log (BRARCHIVE summary log)v detailed BRBACKUP/BRARCHIVE logv reorg<SID>.log (main SAPDBA log)

Figure 4. Backup Scenarios Within a mySAP.com Oracle Environment

Chapter 5. Backup Strategy and Backup Automation 47

v struct<SID>.log (structure log)

These profiles and protocols are used by the SAP database utilities wheneverbackups or restore/recovery are required.

Unless you use an additional security measure, e.g., an additional file systembackup, these profiles or protocol files can only be restored in combination withData Protection for mySAP.com. For this purpose, you can, for example, use theData Protection for mySAP.com File Manager (see “Data Protection for mySAP.comFile Manager” on page 33).

In the case of a recovery scenario after a disaster, it may be time consuming torestore the backup protocols or profiles by means of Data Protection formySAP.com or the Data Protection for mySAP.com File Manager within areasonable time frame. Hence, it is recommended that you back up the directoriesand file systems containing these files separately.

You can find the files in the following directories:

UNIX

/oracle/SID/sapreorg (SAPDBA and structure logs)/oracle/SID/sapbackup (BRBACKUP logs)/oracle/SID/saparch (BRARCHIVE logs)/oracle/SID/dbs (profiles)

Windows

<drive>:\oracle\SID\sapreorg (SAPDBA and structure logs)<drive>:\oracle\SID\sapbackup (BRBACKUP logs)<drive>:\oracle\SID\saparch (BRARCHIVE logs)<drive>:\orant\database (profiles)

Planning a Backup Strategy for mySAP.com System DataIn addition to the backup operations performed with BRBACKUP andBRARCHIVE, you may want to protect your system against the loss of mySAP.comsystem data, user data, or even operating system data that is not stored withBRBACKUP or BRARCHIVE. You can use the incremental backup capabilities ofthe Tivoli Storage Manager backup/archive client to do this.

The Tivoli Storage Manager incremental backup function lets you define aninclude/exclude list of files that is applied automatically during incremental backupoperations. This include/exclude list should be used to exclude data already storedusing Data Protection for mySAP.com. This would be all database relevant data,such as data files, the control file, and online/offline redo logs. For furtherinformation about include/exclude lists, see your Tivoli Storage Manager manuals,Using the Backup-Archive Clients. Examples of include/exclude lists for UNIX can befound in Appendix G, “Sample Tivoli Storage Manager Profiles (UNIX)”, onpage 127 and for Windows in Appendix H, “Sample Tivoli Storage ManagerProfiles (Windows)”, on page 129.


The information saved with the BRBACKUP and BRARCHIVE utilities is usuallylocated 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<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\

Add these directories to the list of paths to be excluded in the include/exclude listof your Tivoli Storage Manager backup/archive client. This will prevent you fromsaving the database data twice.

Backup AutomationTo ensure that all your data will be backed up regularly at a certain time, it isrecommended that you schedule automated backup and archive operations.

There are several products that can be used to set up a schedule, for example:v SAP scheduler (CCMS)v Tivoli Storage Manager schedulerv UNIX crontab / Windows scheduler

The schedulers will be explained by means of examples below.

The scope of schedule control of the Tivoli Storage Manager scheduler is at anenterprise level, while the SAP scheduler or the UNIX crontab can only be used toset up schedules for the machines on which the mySAP.com database is installed.

SAP SchedulerWithin mySAP.com, the Computer Center Management System (CCMS) provides ascheduler for database administration and backup planning. The scheduler can be


|||

|

started from the SAPGUI command line using transaction code db13 or with theSAPGUI menu functions (Tools -> CCMS -> DB administration -> DBAscheduling).

Tivoli Storage Manager SchedulerThe Tivoli Storage Manager also provides functions for automating clientoperations by defining a new schedule or updating an existing schedule.

Schedule definition work can be done quickly using the GUI based Tivoli StorageManager Web administrative client.

When a schedule is defined, it will be assigned to a specific policy domain (morethan one schedule for each policy domain can be defined). For this purpose, themySAP.com database client requires a schedule that can execute command files.The command files (for example shell scripts on UNIX) contain sequences ofcommands that are run at a scheduled start date and time.

Information on how to define Tivoli Storage Manager schedules can be found inthe Tivoli Storage Manager Administrator’s Reference manual.

UNIX crontab / Windows SchedulerAnother possibility of backup automation is offered by the cron jobs for UNIXsystems or schedule services for Windows.

UNIX cron jobs can be scheduled with the so-called crontab command, whichinvokes an editing session that allows you to create a crontab file. The cron jobsand the appropriate times are defined within the crontab. The crontab can becustomized with the command:

crontab -e

For example, you want a cron job to start a shell script backup.ksh (the content ofbackup.ksh can be found in Appendix I, “Elements of Backup Schedules (UNIX)”,on page 131) from Monday through Friday at 11:30 p.m. which will use the SAP

database utility BRBACKUP to save the mySAP.com database. In this case, theentry in the crontab to start the script will be as follows:

30 23 * * 1,2,3,4,5 /usr/bin/su - ora<SID> -c "/oracle/SID/sapscripts/backup.ksh"

To start automated backup jobs on Windows systems, the schedule service must berunning. You can start this service with the command:

net start schedule

If the schedule service is running, jobs can be scheduled with the at commandwhich can be used to invoke the batch file backup.cmd (the content of backup.cmdcan be found in Appendix J, “Elements of Backup Schedules (Windows)”, onpage 135). If you want to run this every Friday at 8:00 p.m., the followingcommand must be invoked:

at 20:00 /every:f cmd /c <drive>:\oracle\SID\sapscripts\backup.cmd


Example of a Sequence of Daily Backup RunsThe following figure illustrates the sequence of backup runs you should establishfor a daily backup schedule.

This example of automated backup operations shows the following typical tasksv Full database backup, e.g., offline or without application load, performed each

night.v Offline redo logs backed up to disk during online hours. This has the advantage

of eliminating the need for extra tape mounts for relatively small files.

NoteBackups can be performed to disks as well as to tape environments. TivoliStorage Manager will manage the data regardless of the storage media.However, it is recommended that the mySAP.com database (data files) isdirectly backed up to tape.

v Offline redo logs are migrated (within Tivoli Storage Manager) from disk to tapeafter the full database backup.

v SAP system files are backed up incrementally with the Tivoli Storage Managerbackup-archive client.

v The last backup in the daily cycle is the backup of the Tivoli Storage Managerdatabase. This should always be the case.

Figure 5. Production Backup Example



Chapter 6. Considerations for Optimizing Backup/RestorePerformance

Protecting against loss of data and minimizing downtime of the mySAP.comsystem are the key requirements for defining a best-fit backup/restore process.

The definition should start with the restore of the database as restore downtimeincurs cost several orders of magnitude higher than backup downtime. Duringrestore, mySAP.com users cannot perform their work, whereas backups runconcurrently with application load.

Therefore, the backup process definition has to be governed by the restoreobjectives.

Minimizing downtime can be achieved by three key measures:v Deployment of a best suited method for backup/restore, for example:

– full backup daily vs weekly (less logs to recover)– online vs offline (application work can continue during backup)– FlashCopy backup vs direct backup (’zero impact’ on application)

v Optimizing for maximum throughput of the data transfer during backup orrestore on the basis of three different techniques:– local backup (production and backup server on same system)– remote (LAN) backup (production and backup server on different systems

connected via LAN)– LAN-free backup (production server transfers backup data directly to storage

via SAN and meta data to backup server via LAN)v Offloading inactive data into an external archive to trim the size of the database

to the data volume actually used

A companion product to Data Protection for mySAP.com - IBM Content ManagerCommonStore for SAP - is available from IBM. It connects Tivoli Storage Manager tothe mySAP.com ArchiveLink Interface covering the whole range of mySAP.comarchiving functions:v inactive data (off-loading)v printlists and outgoing documentsv incoming documents (scan, fax)

Data TransferThe following discussion focusses mainly on optimizing data transfers betweenproduction server and backup server. A simplistic model (see Figure 6 on page 54)shows three independent components involved in the data transfer:v production server (mySAP.com database server)v networkv backup server (Tivoli Storage Manager server)


||

||||

||

|

|

|

|

|

||

|

||

||

||

|||

|

|

|

A continuous stream of data is generated between these components for thebackup or restore of data and the weakest link in this chain determines theoverall data rate.

The following general guidelines result from experience gathered with many actualinstallations and should be considered for designing an efficient backup/restoreinfrastructure and process:v The production (mySAP.com database) server is ultimately the most critical

component for data transfer. Bottlenecks in network and backup server can beremoved through parallelism. Special attention should be given to– CPU power (data transfer takes cycles)– I/O paths– disk layout (database should be spread across as many disks as possible)

v Volume mirroring (by Volume Manager) can slow down the data transfer duringrestore significantly. For short restore time it is recommended to turn offmirroring during the restore.

v When using a LAN-free configuration (Managed System for SAN), the StorageAgent will cause additional load on the production server CPU. As a rule ofthumb, the load will double compared to data transfers to a remote backupserver (LAN).

v The network between production server and backup server should providesufficient bandwidth, e.g., for a LAN - Gigabit Ethernet. A dedicated backbonenetwork should be implemented for backup/restore separate from the userLAN.

v A dedicated backup server allows sharing of resources and yields most efficientresource utilization.

v Backup of data files (large files) should be directed directly to tape as this yieldsthe highest transfer rates. Use of disk to compensate for sufficient number of

Figure 6. Data Throughput


|

|||

||||

|||

|||

|

|

|

|||

||||

||||

||

||

tape drives always will sacrifice throughput. If disk must be used, it isrecommended to use one disk pool per session.

v Small files like log files should be directed to disk storage first and thenmigrated to tape in larger pieces to avoid excessive tape mounts.

The mySAP.com Database ServerThe following typical steps are performed in the mySAP.com database server for abackup process (for restore correspondingly):v Read data from diskv Transfer data through I/O interface into the client CPU’s main memory via

operating system functionsv Process data by Data Protection for mySAP.comv Send data via TSM API to TSM server through a communication method (mostly

TCP/IP)

Data Protection for mySAP.com provides the following features for optimizing datatransfer performance on the client:v Adaptive file sequencing (when called from SAP DBA via backint interface)

An optimal sequence for the files to be backed up/restore is automaticallycomputed to minimize backup and restore windows. In order to avoid paralleldisk accesses, a file-disk correspondence is determined by automaticallychecking the disk layout at regular intervals.If automatic detection is not possible like for most intelligent disk subsystems,e.g. IBM Enterprise Storage Server, EMC SYMMETRIX, etc., symbolic filelocations can be entered manually (see “Manual Sorting” on page 8).

v Data compression using a light-weight run-length algorithmBlocks of consecutive binary nulls in the data stream from/to disks arecompressed/decompressed. Compression factors between 1.3 and 4 have beenobserved in real installations.This feature should be deployed when the network is the bottleneck for datatransfer with the backup server and the production server has a sufficientlypowerful CPU to take on the additional load.

v File multiplexing (when called from SAP DBA via backint interface)For backup, multiple files are read from disk in parallel and merged into asingle data stream (session). For restore, this data stream is demultiplexed anddata is written into the respective original files.This function is used to achieve optimum single session throughput/tapeutilization.

v Parallel sessionsMultiple datastreams are generated in parallel, one for each of the correspondingnumber of storage devices (usually tapes) on the backup server.

Chapter 6. Optimizing Backup/Restore 55

||

||

||

|

||

|

||

||

||||||||

|||||||

||||||

|||

|

Settings for the mySAP.com database serverData Protection for mySAP.com functions and features are activiated by setting thecorresponding parameters in the Data Protection for mySAP.com profile (seeAppendix F, “The Data Protection for mySAP.com Profile”, on page 115).

Input/Output ConfigurationSystem-specific recommendations for setting up an optimum I/O configurationshould be considered, e.g., disk attachment, internal busses like PCI, in order tomaximize the bandwidth for data transfers.

The file layout of the database can have a significant impact on maximumachievable data rates. Data should be spread across as many disks as possible.

File system features, like caching or read ahead, have an effect on data rates aswell and should be adapted to the specific characteristics of backup/restore withits large files and data volumes.

Block SizeData Protection for mySAP.com allows specification of the block size for disk I/Oas transfer rates depend on disk subsystem characteristics.

The block size can be set by the keyword BUFFSIZE (range from 4096 to 262144) inthe Data Protection for mySAP.com profile.

In most configurations the default settings (32768 for Windows, 131072 for UNIX)yield acceptable results.

For EMC disk subsystems, the best transfer rates have been achieved when settingBUFFSIZE equal to stripe size.

Figure 7. Compression and Multiplexing


|

||||

|

|||

||||

||

|||

|||

||

||

||

CompressionData Protection for mySAP.com can do a null block compression before sending dataover the network to the Tivoli Storage Manager server. The Data Protection formySAP.com profile keyword RL_COMPRESSION must be set to YES (default is NO).This compression has been designed specifically for database files, since theyusually contain large portions of null blocks.

ParallelismParallelism can be applied to remove bottlenecks in several components:v reading data from multiple disks in parallel (multiplexing) within a single

session (one tape drive)v transferring data in multiple tape drives in parallel (parallel sessions)v distributing sessions over multiple parallel network connections (parallel paths)v transferring data to/from multiple parallel backup servers (parallel servers)

Multiplexing: Multiplexing is used to minimize the number of storage devices onthe backup server side. The value for the keyword MULTIPLEXING determines thenumber of files read in parallel within one session.

The optimum value should be determined through tests on a specific system (seealso “Optimizing Your Environment” on page 61). An appropriate range is between1 and 4 (default 1).

Note: Setting MULTIPLEXING too high may cause noticeable overhead in threadmanagement on the system and offset performance gain in throughput.

If the average disk read rate is 4.5 MB/s from each disk, the database is backed upwith a data rate of 4.5 * 4 = 18 MB/s. If each file is compressible by a factor of twoand compression is activated, it can be transferred to a Tivoli Storage Managerserver at (4.5 * 4) / 2 = 9 MB/s . With null block compression, but withoutmultiplexing, we could transfer only 4.5 / 2 = 2.25 MB/s to one Tivoli StorageManager server. (This example assumes that the Tivoli Storage Manager server andtape drive are fast enough to cope with this data rate.)

Multiplexing reduces the number of Tivoli Storage Manager servers (and tapedrives) required. The optimal value for MULTIPLEXING depends very much onthe hardware environment, for example, the availability of a fast network (FDDI,Fast Ethernet), of fast tape drives within the tape (media) library, and on thecompressibility of the database files. Appropriate MULTIPLEXING values would beexpected in the range of 1 to 4.

The example above shows some of the typical dependencies between the totalbackup rate, the disk transfer rate, the compression ratios, and the Tivoli StorageManager data rate.

Parallel Sessions: Data Protection for mySAP.com allows you to specify parallelsessions to increase the transfer rate to/from a Tivoli Storage Manager server. Thefollowing parameters can be set:

MAX_SESSIONSsets the number of parallel sessions for backup, archive (log files), andrestore.

MAX_BACK_SESSIONSdefines the number of parallel sessions for (data file) backup. This valuewill overwrite MAX_SESSIONS for backup.


||||||

||

||

|

|

|

|||

|||

||

|||||||

||||||

|||

|||

|||

|||

MAX_ARCH_SESSIONSdefines the number of parallel sessions used for archive (backup of logfiles). Usually archive does not need as many sessions as (data file) backupsince the volume is much smaller with log files. This value will overwriteMAX_SESSIONS for archive.

MAX_RESTORE_SESSIONSdefines the number of parallel sessions used for restore.For restore, more tape drives may be available than for backup. Usingthese additional tape drives may speed up the data transfer for restore ifthe backup is written to multiple tapes (tape capacity small compared todatabase volume).This value will overwrite MAX_SESSIONS for restore.

Note: Testing should be performed to determine the actual throughputgain as multiple accesses to same tape may slow down data transfer.In practical installations throughput increases of up to 30% havebeen observed.

Parallel sessions are closely related to TSM management classes.

The management class specified in the profile keyword BRBACKUPMGTCLASSwill be used when running the BRBACKUP. If it is a BRARCHIVE run, themanagement class specified in the profile keyword BRARCHIVEMGMTCLASS willbe used.

The management classes used must have as many tape drives as defined by thesession parameters.

When running BRBACKUP, the data will usually be written directly to tape driveson the Tivoli Storage Manager server. This means that the parameter specified inthe MAX_SESSIONS keyword must match the number of tape drives usedsimultaneously. Recommendations on the Tivoli Storage Manager server side thatyou should pay attention to are:v No activation of collocation in the (tape) storage poolv 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. Thesize of offline redo log files is much smaller compared to the size of databasetablespace files backed up by BRBACKUP. If you are using tape pools as (primary)pools, the same considerations for the tape setup as for the disk setup (seeBRBACKUP above) apply.

The advantage of a disk storage pool is its random access nature:v Several sessions of one BRARCHIVE can utilize one or two independent disk

storage pool(s)v Several sessions of BRARCHIVE runs of several databases can simultaneously

utilize one or two independent disk storage pool(s)

Parallel Paths: Parallel paths can be used by the Data Protection for mySAP.comto eliminate network bottlenecks. For each additional path, additional networkadapters are required on both the production and backup server. The setup forparallel paths is described in detail in Appendix E, “Alternate/Parallel BackupPaths and Backup Servers”, on page 109.


|||||

|||||||

||||

|

||||

||

||||||||

|||||

|||||

|||||

Parallel Servers: Parallel servers can be used by the Data Protection formySAP.com to eliminate backup server bottlenecks. Note that for each additionalpath additional network adapters are required on both the production and backupserver. The setup for Parallel Servers is described in detail in Appendix E,“Alternate/Parallel Backup Paths and Backup Servers”, on page 109.

The NetworkThe network affects the data transport in two ways:v 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.

v The network bandwidth limits the data throughput. Our experience shows thatthe effectively usable bandwidth is approximately half the theoretical bandwidthof the specific network. For high-speed networks such as Gigabit Ethernet, it islikely that the network adapters of the respective systems limit the effective datathroughput rather than the network itself.

Data Protection for mySAP.com provides the following capability for optimizingthe performance of the network in regard to data throughput:v Multiple Paths.

Parallel sessions can be assigned to multiple network paths between mySAP.comdatabase and backup server (see also, “Alternate/Parallel Backup Paths” onpage 6). Thus, the overall network bandwidth usable for data transfer can beincreased to the sum of the parallel paths.

Settings for Network ParametersThe network on a UNIX machine can be configured with the no command. Thiscommand sets or displays current network attributes in the kernel. The commandmust be run again after each start-up or after the network has been reconfigured.

CautionThe no command does not perform range checking. It therefore accepts allvalues for the variables. If used incorrectly, the command can cause thesystem to become inoperable.

The following table shows the appropriate network attributes with therecommended values.

Table 3. Tuning of Network Settings

Attributes Value Description

rfc1323 1 Enables TCP enhancements as specified by RFC1323, TCP Extensions for High Performance. Thedefault is 0. A value of 1 specifies that all TCPconnections will attempt to negotiate the RFCenhancements.

sb_max 131072 Specifies the maximum buffer size allowed for asocket. The default is 65536 bytes. From the point ofview of performance recommendations, the sb_maxvalue should correspond to the TCPWindowsizesetting within the Tivoli Storage Managerconfiguration file dsm.sys and should be twice theTCPWindowsize.


|||||

|

To adapt these values, the following commands have to be invoked by the rootuser on the appropriate machine.

no -o rfc1323=1no -o sb_max=131072

NoteThese changes will be lost at system reboot. To make changes permanent, editthe /etc/rc.net file.

If an SP switch (RISC 6000) is used, the following two values should be adapted asshown in the following table.

Table 4. Tuning of SP Switch Buffer Pools


rpoolsize 1048576 The receive pool is a buffer pool for incoming data.The size for values is in bytes.

spoolsize 1048576 The send pool is a buffer for outgoing data. The sizefor values is in bytes.

The buffer pool settings can be changed using the chgcss command. After thechanges, it is necessary to reboot the node.

Further detailed information can be found athttp://www.rs6000.ibm.com/support/sp/perf

The Backup ServerThe backup server receives the data from the network, removes the communicationframes and prepares the data for writing onto backup storage media (usuallytapes). Observations show that the CPU load on the backup server for a given datathroughput is approximately 60% of that on the client. Therefore, the backup serveris not the critical resource from a CPU power point of view.

Data Protection for mySAP.com provides the following capabilities for optimizingthe performance of the backup server in regard to data rates:v Parallel sessions.

Multiple tape drives can be used in parallel to store data and increase overalldata throughput.

v Storage hierarchiesIf tape drives are already assigned, disks can be used with additional sessions asintermediate storage, which can later be migrated to tape (inherent function ofTivoli Storage Manager). This method is recommended for log files (which areconsiderably smaller than data files) to avoid an excessive number of tapemounts.

v Multiple ServersAs with multiple paths, parallel sessions can be routed to multiple Tivoli StorageManager servers to increase the overall data throughput of the backup server(see also, “Alternate/Parallel Backup Servers” on page 7).


||

|

|

Settings for the Tivoli Storage ManagerThe performance adjustments on the Tivoli Storage Manager side can be done bycustomizing the appropriate configuration files. On the server side, it is the serveroption file dsmserv.opt, and on the client side the client option file(s) dsm.sys onUNIX systems and <server>.opt on Windows systems.

The following table shows the corresponding Tivoli Storage Manager configurationfile attributes with the recommended values.

Table 5. Tuning Tivoli Storage Manager Configuration File Attributes


TCPBuffsize 32 Specifies the size, in kilobytes, of the buffer used forTCP/IP send requests. This option affects whether ornot Tivoli Storage Manager sends the data directlyfrom the session buffer or copies the data to the TCPbuffer. A 32K buffer size forces Tivoli StorageManager to copy data to its communication bufferand flush the buffer when it fills.

TCPNODelay YES Specifies whether the server should send smallamounts of data or allow TCP/IP to buffer the data.Disallowing buffering may improve throughput butmore packets will be sent over the network.

TCPWindowsize 640 (AIX)32 (others)

Specifies the size, in kilobytes, which will be usedfor the TCP/IP sliding window for the client node.This is the size of the buffer used when sending orreceiving data. The range of values is 0 to 2048.

Additional information can be found at http://www.tivoli.com/storage

Optimizing Your EnvironmentBased on the multitude of software and hardware parameters affectingperformance and considering the variety of system environments as well asobjectives, there cannot be one set of values for the parameters which ’fits all’.Individual optimizing on a trial and error basis will almost always be necessary iftuning is to be done to the maximum possible level.

The following list presents a ’best practice’ sequence of steps recommended fortuning:

Single session optimizationMAX_SESSIONS=1, MULTIPLEXING=1, RL_COMPRESSION OFF

Step 1:Optimize Volume Manager settings (AIX-VMtune), BUFFSIZE, networkoptions, and TSM server parameters as described in the previous sectionsof this chapter.

Step 2:Increase MULTIPLEXING to 2,3,4The data rate should asymptotically increase with the MULTIPLEXINGvalue until either the network or the tape drive limits the throughput.

Increasing MULTIPLEXING will cause an increase of CPU load:v proportional to the data rate transferred by Data Protection for

mySAP.com


|||||

||

||

||||

||||

|

||

v additional system overhead for thread management. Therefore, amultiplexing value should be selected that still shows a reasonable gainin throughput (before the multiplexing data rate curve starts to level off)

Multisession Optimization

Step 3:Increase MAX_SESSION to 2,3,4....The data rate should increase asymptotically with the number of sessions.

Note: Sessions can only be increased to the maximum number of tapedrives assigned to this backup as each session requires a dedicatedtape drive.

Monitor network and database server (CPU, I/O) utilization to determinethe bottleneck.

The necessary actions result from where the bottleneck is and may include:v Optimization of disk layout of the mySAP.com database, see Step 4

v Turning run length compression on (RL_COMPRESSION Y); note thatthis will increase the CPU load on the mySAP.com database server

v Increasing network bandwidth by using parallel paths, see Step 5

v Increasing the maximum number of sessions by adding more tape driveson the backup server

v Increasing the CPU power of the mySAP.com database server

Step 4:Add additional network paths (multiple path function) and distribute thesessions onto the multiple paths, see Appendix E, “Alternate/ParallelBackup Paths and Backup Servers”, on page 109.

Step 5:Optimize the disk layout of your mySAP.com database server.To avoid disk contention caused by multiple read operations, distribute thefiles of your mySAP.com database across as many disks as possible. Checkfor limitations in the bandwidth of the I/O adapters. Add additionaladapters if necessary.


|||

|

|||

|||||

|

|

||

|

||

|

||||

||||||

Chapter 7. Administration Assistant for Data Protection formySAP.com

The Administration Assistant for Data Protection for mySAP.com consists of a Webbrowser based graphical interface to support and assist the customizing of DataProtection for mySAP.com and the analyzing of mySAP.com database backup andrestore operations.

The Administration Assistant facilitates the configuration, monitoring, andadministration of Data Protection for mySAP.com from local or remoteworkstations. It gives mySAP.com administrators the possibility of centralizing thedatabase backup/restore administrative work, especially the monitoring of DataProtection for mySAP.com and mySAP.com database backup/restore actions fromall mySAP.com database servers within the system landscape.

GeneralA mySAP.com system landscape in the real world typically unites more than onemySAP.com system. At least one mySAP.com test system and one mySAP.comproduction system will be used together. A typical example of this is shown inFigure 8.

The central Administration Assistant instance is the Administration Assistant Server,which can be installed on any system (UNIX or Windows). It acts as a datacollector and data distributor. This means that it collects all incomingbackup/restore dependent Administration Assistant data generated by the Data

Figure 8. Example of an mySAP.com Landscape


Protection for mySAP.com background process Prole (see also Chapter 1,“Introducing Data Protection for mySAP.com”, on page 1) from the mySAP.comdatabase server.

This data will be distributed over a network (LAN) to every AdministrationAssistant Client node (user frontend, Web browser based) actually connected, andwritten to various local files stored on the Administration Assistant Server.

These files serve as a data source for subsequent reviewing of performance/erroranalysis of backup/restore functions which have been carried out. They can alsohold various Data Protection for mySAP.com configuration states (Tivoli StorageManager configuration files, Data Protection for mySAP.com profile, SAP backupprofile) in form of a configuration history.

The Administration Assistant can be understood to be a collection of fourprograms:v System Configurationv Performance Monitorv Operations Monitorv Problem Support

The System Configuration Tool lets you customize the SAP backup profile, the DataProtection for mySAP.com profile, and all the necessary Tivoli Storage Managerfiles. Online documentation guides you through the customization process andgives you descriptions of the parameters and their values. When you havefinished, you can copy the Data Protection for mySAP.com profile to another DataProtection for mySAP.com node.

The Performance Monitor displays Data Protection for mySAP.com performanceinformation while Data Protection for mySAP.com is performing a backup orrestore operation. You can also display saved performance statistics when DataProtection for mySAP.com is not active. The Monitoring Tool runs on all platformsthat support Data Protection for mySAP.com.

The Operations Monitor provides a centralized overview of backup statusinformation for all mySAP.com systems registered with the central AdministrationAssistant server. The overview panel shows summaries of the backup status of anmySAP.com system and the state of the current backup for every system in yourmySAP.com system landscape. Detailed information about all backup runs on aspecific mySAP.com system can also be obtained.

Problem Support allows sending support requests directly to a Tivoli support center.Support requests can include user-specified problem descriptions. The toolautomatically attempts to attach further information to the mail, such asconfiguration profiles and error logs.

PrerequisitesThe following prerequisites are required before the Administration Assistant can beinvoked:1. Data Protection for mySAP.com must have been installed successfully (see

Chapter 3, “Setting Up Data Protection for mySAP.com”, on page 19).


2. Java Runtime Environment (JRE) version 1.3 or higher.To check the version of the installed Java™ software on UNIX or Windows, usethe following command from a command line:

java -version

Not all vendors provide the JRE separately. You can install the JavaDevelopment Kit (JDK), because the JRE is part of the JDK. Contact theoperating system vendor to get the required JRE or JDK software.

3. Additionally, the following two Java packages must be installed:v Java Beans Activation Framework (JAF) version 1.1 or higher.v Java Mail 1.1.3 or higher

4. A fully Java 1.3-capable Web browser is required on the client machine (JavaPlug-in 1.3 or higher must be installed). You can use Netscape NavigatorVersion 6.2 or higher or Microsoft® Internet Explorer 5.5 or higher or Mozilla1.1 or higher .

5. For UNIX systems, the X Window system is required.

After ensuring that all these prerequisites are available, the installation process cancommence. By subsequently starting the Administration Assistant you can verifythe installation.

InstallationIn this section we will discuss the installation and customization of theAdministration Assistant.

The installation process is subdivided into two parts:v During the base installation of the Administration Assistant server, the English

version of the Administration Assistant server is installed only.v The NLS package, which contains all currently translated resources, can be

installed at a later point in time. For the NLS package, the base installation isrequired.

Installing the Administration Assistant Server (BaseInstallation)

To assist you with the installation procedure, the Administration Assistant packageprovides a setup assistant, a so-called installer that guides you through theinstallation process.

NoteIt is necessary to have system administrator privileges to install theAdministration Assistant correctly.

Both the base and NLS package of the Administration Assistant (base & NLS) aredelivered as Java class files named install.class.

Chapter 7. Administration Assistant 65

||

|

||

|||

||

NoteThere is no need to set the environment variable CLASSPATH. However, if thisvariable is set in the system environment, the directory where the fileinstall.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 the JRE is installedonly, you must use the command

jre -cp . install

Now, the installer becomes active. Follow the instructions provided on the panelsof the installation tool.

In the panel Specify ports (see Figure 9 on page 67) it is important to:v Check for free ports in the services file (in most cases the given values are

usable)v Remember the specified ports for later use


In the panel Correct Hostname, the host name of the Administration Assistant servermachine must be specified (or corrected) as shown in Figure 10 on page 68.

Figure 9. Administration Assistant Server Setup (Base Installation) — Specify Ports


|

||

RememberThe communication between the Administration Assistant server and clients(Web browser or Java applet) will be done with Java RMI. An RMIcommunication requires a clear assignment between IP address and aliasname for both of the communication clients involved.

Each of these clients must be capable of resolving the IP address of the otherclient to an alias name and vice versa. If you use a DHCP service on theAdministration Assistant server machine, it may be possible that this machinehas two names. This would be a typical DHCP problem. A clearly definedhost name of the Administration Assistant server is a necessary prerequisitefor subsequent communication between clients and this server (serverconfiguration cannot be changed later).

As a result of the above, the recommendation is to use a static IP address insteadof one temporarily generated by DHCP. If you are using DHCP, be aware that inthe case of a reboot of the Administration Assistant server machine, this machinewill be allocated a new IP address and the Administration Assistant will not beable to work.

On the panel Choose Destination Location, you have to specify the destinationdirectory to which the application will be installed as shown in Figure 11 onpage 69.

Figure 10. Administration Assistant Server Setup (Base Installation): Correct Hostname Panel


|

||

The system impact, after the setup process is finished successfully, is:v On UNIX systems: Specification of a new entry in the /etc/inittab to start the

Administration Assistant automatically (Adma:23:once:+sh "Installdirectory"/sadma.sh). The expression ″Install directory″ will be replaced withthe real directory name specified during the setup process. If none was specified,the default installation directory /usr/lpp/BkiT will be used.

v On Windows systems: A new service. As a result, setup creates an entry in theWindows registry under’HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services’ with the nameAdminAssistant.

Installing the Administration Assistant NLS PackageTo install the Administration Assistant server NLS extension you need to:v Start the installer.v Specifiy the directory where the base application has been installed.

The installer will guide you through the rest of the installation process.

After the setup process has finished successfully, do the following to ensure thatthe NLS extension works properly:v On UNIX systems: Stop the current Administration Assistant server process

using kill <process ID> and restart it.v On Windows systems: Stop the Administration Assistant Service and restart it.

Specifying a new Administration Assistant Server for Data Protectionfor mySAP.com

If you need to specify a new Administration Assistant Server for Data Protectionfor mySAP.com, perform the steps described below.

Specifying an Administration Assistant Server on UNIX

1. Find the entry for daemon prole in /etc/inittab. Modify the entry to read:

Figure 11. Administration Assistant Server Setup – Destination Directory


|

|

|

|

||

||

|

||

|

|

/prole -p <tdpr3ora> | tdpr3ora64> <AA server name> <port>

where<AA server name> is the name or IP address of the Administration Assistantserver and<port> is the port that the Administration Assistant is listening to, the default is5126.

2. Make sure that Data Protection for mySAP.com is not running and use the killcommand to stop the prole daemon. The prole daemon will be restartedautomatically with the new parameters.

Specifying an Administration Assistant Server on Windows

From a command prompt, issueprole -update <AA server name> <port>

where<AA server name> is the name or IP address of the Administration Assistant serverand<port> is the port that the Administration Assistant is listening to, the default is5126.

Verifying the InstallationA dedicated verification procedure for the Administration Assistant is not needed.To verify and test the installation, you can simply start the AdministrationAssistant and start working with it, for example, by authorizing the users.

To start the Administration Assistant, enter its URL in the Location field of theNetscape browser (see Figure 12). Note that the host name of the AdministrationAssistant server (see Figure 10 on page 68) and the port used for communication(see Figure 9 on page 67) must be separated by a colon.

Each time a user starts the Administration Assistant, a Logon panel pops up foridentification (see Figure 13 on page 71). When the Administration Assistant isstarted for the first time, no user profiles for specific users are available. In thiscase, the initial account must be used. This account has the default user ID ADMINand the password admin. (Note that these are case sensitive).

NoteWhen you log on to the Administration Assistant with the initial user ID, it isrecommended that you change the password of that user immediately.

Figure 12. Starting the Administration Assistant with Netscape


|

|||

|

|||||

|||

|

|

|

|||||

|

|||

||||

Once you are logged on, you can invoke the functions Operations Monitor,Performance Monitor, System Configuration, Problem Support, and User Administrationby selecting the appropriate item from the ’My Work’ portfolio.

If you are using the Administration Assistant for the first time, you can nowproceed to authorize users.

Authorizing Administration Assistant UsersThe User Administration function of the Administration Assistant enables you tocreate user accounts and to grant users only those permissions they need for theirjobs.

With the user administration function it is possible to create additional accountswith appropriate rights. Rights or user permissions can be granted or revoked for aspecific user profile. Every account has five authorities. These are:v Operations monitor authority - permission to view backup status information of

any mySAP.com system within the system landscapev Monitoring authority - permission to monitor jobsv Configuration authority - permission to configure Data Protection for

mySAP.comv Problem Support authority - permission to send support request mail to the

Data Protection for mySAP.com hotline.v Administration authority - permission to administer all user accounts

When you start the Administration Assistant for the first time, you will need tocreate profiles for authorized users. Refer to the online help for information onhow to do this.

Using the Administration AssistantDepending on the rights set in their user profiles, authorized users of theAdministration Assistant can start the Configuration facility, the Performance Monitor,or the Operations Monitor.

Figure 13. Administration Assistant Start Panel


|||

|||

The Administration Assistant has an integrated help function that providesdetailed information on how the it can be used. The help function can be accessedby clicking on the Help button.

Detailed information about the Data Protection for mySAP.com AdministrationAssistant is also available in the IBM redbook SAP R/3 Data Management with TivoliStorage Manager, SG245743, which can be downloaded fromhttp://www.redbooks.ibm.com.

Uninstalling the Administration AssistantTo uninstall the Administration Assistant server proceed as follows:v On UNIX systems, run the script Uninstall.sh.v On Windows systems, use the script Uninstall.cmd.

Do not use the ADD/REMOVE Software Utility on Windows systems!Otherwise the service will not be removed properly!

It is recommended that you perform the uninstall option only with systemadministrator privileges. This will allow the Uninstaller to remove the entries eitherfrom the inittab on UNIX or from the registry on Windows systems.


||

Chapter 8. mySAP.com System Cloning

The procedure for cloning an mySAP.com system described in this chapter shouldbe used to complement the SAP documentation R/3 Homogeneous System Copy andR/3 Installation on UNIX / Windows - Oracle Database.

Furthermore, it is recommended that you use the correct SAP documentation foreach particular environment. This documentation can be found athttp://sapnet.sap.com on the SAP Documentation Guides CD-ROM, which is partof the SAP R/3 installation package or with the help of the SAP technical support.

GeneralThe mySAP.com system cloning can be done if there is the necessity for one sourcemySAP.com system to be exactly copied to a target mySAP.com system. In this context,the source mySAP.com system is also called the original system, from which thedata will be exported, and the target mySAP.com system is also called thedestination system, which imports the data from the source mySAP.com system.

SAP calls the procedure of cloning an mySAP.com system either homogeneoussystem copy or heterogeneous system copy. In a homogeneous system copy scenario,the source and target systems have the same mySAP.com release, operating system,and database version. If this is not the case, you will get a heterogeneous systemcopy. Further information about these two system copy scenarios can be found inOSS notes 86859 and 86860.

mySAP.com system cloning is appropriate in the following situations:v Setting up an mySAP.com system landscape (development, quality assurance,

and production system)v Hardware upgradev Creating multiple mySAP.com test and/or demo systems

Additional information about mySAP.com system cloning can be found in the IBMredbook SAP R/3 Data Management with Tivoli Storage Manager, SG245743. The bookcan be downloaded at http://www.redbooks.ibm.com.

mySAP.com System Cloning ExampleThe following procedure is supplied with no warranty of any kind. ForSAP-specific changes, see also OSS note 71254.

It is assumed that there are two SAP R/3 systems installed and operating on twodifferent machines and that Data Protection for mySAP.com is installed andoperating on both systems. The following describes the necessary changes in orderto restore an Oracle SID to a different machine with a different SID.

The steps you need to perform depend on the password access method you areusing:v Automatic password handling (see also Appendix D, “Password Handling”, on

page 105)If you are using passwordaccess=generate in the Tivoli Storage Manager clientoption file dsm.sys on UNIX systems or <server>.opt on Windows systems of


your source system, you need to make sure that you are using the samenodename/password that is specified in the Tivoli Storage Manager client optionfile on the target system. In order to do that, carry out the following procedure:1. Make a backup copy of the client option file on the target system.2. Copy the client option file from the source system to the target system.3. Edit the client option file and add NODENAME source system to the server

stanza.4. Reset the Tivoli Storage Manager password for the target system node on

the server.5. Set the newly created password on the client, e.g., dsmc q f. Remember to

do this as root/administrator.6. Make a backup copy of the init<SID>.utl file on the target system.7. Copy the init<SID>.utl file from the source system to the target system

and rename init<SID>.utl to init<target_SID>.utl.8. Edit the init<SID>.utl file on the target system to reflect all the correct file

and path names such as for CONFIGFILE and TRACEFILE.9. Go ahead and restore the database under the SAP considerations.10. After the restore, reset the client option file and init<SID>.utl file to their

originals and set the passwords on the target system.11. Reset the passwords on the source system.

NoteKeep in mind that the passwords are stored in different places, while theonly ″original″ password resides on the Tivoli Storage Manager server! Youneed to make sure that the client uses the password that is stored on theserver.

v Manual password handling (see also Appendix D, “Password Handling”, onpage 105)If you are using passwordaccess=prompt, you only need to set thenodename/password in the init<SID>.utl file:1. Make a backup copy of the init<SID>.utl file on the target system.2. Copy the init<SID>.utl file from the source system to the target system and

rename init<SID>.utl to init<target_SID>.utl.3. Edit the init<SID>.utl file on the target system to reflect all the correct file

and path names such as for CONFIGFILE, TRACEFILE, ...4. As <SID>adm user, on the target system, set the Data Protection for

mySAP.com password:For UNIX systems

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

For Windows systems

backint -p <drive>:\orant\database\init<SID>.utl -f password

and issue the password at the prompt.5. Restore the database according to the SAP recommendation.6. Reset the init<SID>.utl file and the password on the target system.


||

||

Chapter 9. Considerations for Using IBM HACMP for AIX

This chapter is intended to give a short introduction to the way Data Protection formySAP.com works internally, thus enabling the user to take actions for HACMPfail-over configurations. As an example, we use the following configuration, whichshould be easily adaptable to others. Here, we use the ’mutual takeover’configuration, where each node can take over the other. If the application serverand database server are installed on different hosts, the described actions need tobe taken on the database servers only.

The following figure illustrates the takeover environment:

Data Protection for mySAP.com Internals

Filesv The installation directory is /usr/tivoli/tsm/tdp_r3.v Lock files and disk sorting files can be found in /var/tdp_r3.v There is only one prole running on each host (even after takeover).v Each SAP system has its own TDP configuration files (init<SID>.utl,

init<SID>.bki) in /oracle/<SID>/dbs.

Dependenciesv Both hosts should have the same level of Tivoli Storage Manager API installed.v Both hosts must have the same level of Tivoli Data Protection for R/3 installed.v On both hosts, the dsm.sys file (in /usr/Tivoli/tsm/client/api/bin/dsm.sys)

must contain all server names required for takeover.

Communicationbackint connects to prole using the following procedure:v Get the IP address for localhost (should be 127.0.0.1 ).v Get the backint service (should be 57321, the default).

Figure 14. Sample Environment for HACMP Takeover


v Connect to 127.0.0.1:57321.

Installation and Setup

InstallationA prerequisite for installation is a correct setup of the TSM client. The installationsteps for the TSM Backup/Archive Client for AIX can be found in thedocumentation Tivoli Storage Manager Installing the Clients.

Defining Data Protection for mySAP.com as an HACMPApplication

To enable TDP for R/3 to participate in HACMP failover processing, it must bedefined as an application to HACMP. Detailed directions for doing this can befound in the HACMP for AIX Installation Guide, SC23-4278. A summary follows.

To configure an application for HACMP:1. Enter the following to start HACMP for AIX system management:

smit hacmp

2. Select Cluster Configuration > Cluster Resources > Define Application Servers> Add an Application Server.

3. Enter field values as follows:

Server NameEnter an ASCII text string that identifies the server (for example,tdpclientgrpA). You use this name to refer to the application serverwhen you define it as a resource during node configuration. The servername can include alphabetic and numeric characters and underscores.Do not use more than 31 characters.

Start ScriptEnter the full pathname of the script that starts the server (for example,/usr/sbin/cluster/events/utils/start_tdpr3.sh). This script is called bythe cluster event scripts. This script must be in the same location oneach cluster node that might start the server.

Stop ScriptEnter the full pathname of the script that stops the server (for example,/usr/sbin/cluster/events/utils/stop_tdpr3.sh). This script is called bythe cluster event scripts. This script must be in the same location oneach cluster node that might stop the server.

4. Press Enter to add this information to the HACMP for AIX ODM.5. Press F10 after the command completes to leave SMIT and return to the

command line.

Sample client start and stop scripts are provided later in this chapter.

Refer also to the HACMP for AIX Planning Guide V4.4, SC23-4277, for furtherinformation about selecting the HACMP node topology and takeover relationships.Note that Data Protection for mySAP.com must be in a resource group having acascading or rotating takeover relationship. It does not support a concurrent accessresource group.


Adding the Data Protection for mySAP.com Application to anHACMP Resource Group

A final step in enabling Data Protection for mySAP.com for HACMP failover is todefine it to a cluster resource group. Detailed directions for doing this can befound in the HACMP for AIX Installation Guide. A summary follows.

To define the resources that will be part of a resource group:1. From the Cluster Resources SMIT screen, select the Change/Show

Resources/Attributes for a Resource Group option and press Enter. SMITdisplays a picklist of defined resource groups.

2. Pick the desired resource group.3. Press Enter and SMIT displays the Configure a Resource Group screen.4. Enter values that define all the resources you want to add to this resource

group.5. After entering field values, synchronize cluster resources.6. Press F10 to exit SMIT or F3 to return to previous SMIT screens to perform

other configuration tasks or synchronize the changes you just made. Tosynchronize the cluster definition, go to the Cluster Resources SMIT screen andselect the Synchronize Cluster Resources option.

The TSM client application should be added to the same resource group thatcontains the file systems it will back up. The file systems defined in the resourcegroup should also be the ones specified in the domain for this client instance in theclient user options file.

Note that both JFS and NFS file systems can be defined as cluster resources,although NFS supports only 2 node clusters in a cascading takeover relationship.

Sample Start ScriptThe only purpose of this script is to update Data Protection for mySAP.com’svolume information after a takeover and after all SAP file systems are mounted,because there are more filesystems and disks available. This file is used by theData Protection for mySAP.com disk sorting function and may have an impact onperformance. The start script is used in the following cases:v HACMP is started and resource groups are ″activated″

v a failover occurs and the resource group is started on another nodev fallback occurs (a failed node re-enters the cluster) and the resource group is

transferred back to the node re-entering the cluster.

The start script will be called by HACMP as the root user.

Note: This script is not in its final form. It should be considered pseudo code thatindicates the functions it will perform.

Chapter 9. Considerations for Using IBM HACMP for AIX 77

#!/bin/ksh# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## This sample script is provided for use with the TDP for R/3 in an HACMP environment ## It should be reviewed and customized to meet your specific client environment ## ## ## Name: start_tdpr3.sh ## ## Function: A sample shell script to start the disk sorting function for TDP for R/3. ## ## ## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

if ["$VERBOSE_LOGGING"="high"]then

set -xfi

START_DISKINFO(){# It is assumed that ’prole’ is already running# Start createinfo in the background.

nohup /usr/bin/createinfo &}

# This starts the disk info process to allow disk sorting for the taken-over SAP instance.START_DISKINFO

Exit 0

Sample Stop ScriptDepending on the customer installation, the sample stop script may need to ensurethat any backup/restore operation currently in progress is stopped. This meansthat any processes launched by brbackup/brarchive for this client instance (thatmay be accessing the shared file system(s)) must also be stopped to free resourceslike file systems. This may have already been accomplished by the HACMP scriptthat stops R/3. It may also not be desirable in certain installations and should berevised.

The stop script is used in the following situations:v HACMP is stoppedv a failover occurs due to a failure of one component of the resource groups. The

other members are stopped so that the entire group can be restarted on thetarget node in the failover.

v A fallback occurs and the resource group is stopped on the node currentlyhosting it to allow transfer back to the node re-entering the cluster.

The stop script will be called by HACMP as the root user.

Note: This script is not in its final form. It should be considered pseudo code thatindicates the functions it will perform.


#!/bin/ksh# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## This sample script is provided for use with TDP for R/3 in an HACMP environment ## It should be reviewed and customized to meet your specific environment ## ## ## Name: stop_tdpr3.sh ## ## Function: A sample shell script to update the disk information after the SAP ## instance is unmounted. ## ## ## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

if ["$VERBOSE_LOGGING"="high"]then

set -xfi

# Function to update all disk information for TDP for R/3START_DISKINFO(){# You may want to cancel all backups currently running# Note that this will generate errors in the current backup logs and it will also cancel the# connection to the Admin Assistant.# *** Note that if you are using TDP for ESS for R/3, this may leave the ESS in an inconsistent# state.# kill –9 `cat /var/tdp_r3/prole.pid`# Start createinfo in the background to update the disk information. This should be done# after all SAP file systems are umounted.

nohup /usr/bin/createinfo &}

# This starts the disk info process to update the disk information.START_DISKINFO

Exit 0

Chapter 9. Considerations for Using IBM HACMP for AIX 79


Appendix A. Data Protection for mySAP.com Messages

This chapter describes how to find message files (log files) and explains theindividual messages issued by Data Protection for mySAP.com.

How To Find Message Files (Log Files)Data Protection for mySAP.com process results are logged in files. These files arelocated in the following paths:

UNIX:v $ORACLE_HOME/sapbackup for backup and restore runsv $ORACLE_HOME/saparch for redo log archive runs

Windows:v %ORACLE_HOME%/sapbackup for backup and restore runsv %ORACLE_HOME%/saparch for redo log archive runs

All log files written during a backup, restore or archive are listed in summary logfiles with start and end timestamps. The summary log files are located in the samedirectory as the log files themselves and have the following names:v back<SID>.log

v rest<SID>.log

v arch<SID>.log


Data Protection for mySAP.com Message ExplanationsThe messages begin with the prefix BKI and are listed in numerical order.

For each message, the following information is provided:v Message numberv Severity code

The following letters give an indication of the severity of the action thatgenerated the message. The severity codes and their meanings are as follows:

E Error Processing cannot continue.W Warning Processing can continue, but problems may occur later.I Information Processing continues. User response is not necessary.

v Explanationv User Response

BKI0000E Profile not specified.

Explanation: Data Protection for mySAP.com cannotlocate the profile.

User Response: Ensure that a profile is available. Notethat the BACKINT call must have the following form:backint -p init<SID>.util ...

BKI0004E Function not defined.

Explanation: SAPDBA, BRBACKUP, or BRARCHIVEpassed an invalid argument to Data Protection formySAP.com.

User Response: Ensure that you have the correctversion of SAPDBA, BRBACKUP, or BRARCHIVEinstalled. See “Prerequisites” on page 19. Validfunctions are: -f backup or -f restore or -f password or -fdelete or -f inquire.

BKI0005I Start of program at: time

Explanation: Data Protection for mySAP.com receivedcontrol from SAPDBA, BRBACKUP, BRARCHIVE orBRRESTORE at time.

User Response: None.

BKI0006E Type for backup not defined [type].Please use ’file’ or ’file_online’.

Explanation: Data Protection for mySAP.com expectsas backup type parameter only file or file_online.

User Response: If you start Data Protection formySAP.com manually to do a backup, ensure that thetype option (-t) receives the correct arguments (file orfile_online). If your Data Protection for mySAP.com hasbeen invoked by one of the SAP database utilities (e.g.,BRBACKUP), ensure that the SAP backup profileinit<SID>.sap is customized correctly (see“Customizing Data Protection for mySAP.com and SAP

Backup Profiles” on page 25).

BKI0007E Mode mode requires the environmentvariable environment variables to be set.

Explanation: Not all environment variables requiredhave been set. At least environment variables wheremissing.

User Response: Set the missing environmentvariables.

BKI0008E The environment variable name is notset correctly. The current value is value.

Explanation: The value of the environment variablename is wrong.

User Response: Set name to an appropriate value.

BKI0020I End of program at: time

Explanation: Data Protection for mySAP.com returnedcontrol to SAPDBA, BRBACKUP, BRARCHIVE, orBRRESTORE at time.


BKI0021I Elapsed time: elapsedtime

Explanation: The time needed for the completebackup was elapsedtime.


BKI0023I Time: current_timeDone: saved_bytes (percent) of bytesEstimated end time: end_time

Explanation: Data Protection for mySAP.com finishedsaving a specific object at current_time. The saved_bytesamount of the total number of bytes have been saved.percent shows the percentage. This Data Protection for


||

mySAP.com call will be completed at the estimatedend_time.


BKI0024I Return code is: return code

Explanation: Shows the return code of Data Protectionfor mySAP.com. A return code of 0 means no errors orwarnings occurred. If the return code is 1, at least onewarning was issued by the program. If the return codeis 2, at least one error message was issued.

User Response: For return codes other than 0, checkthe run log for warnings or error messages.

BKI0027I Time: current_timeObjects: current_num of total_numin process: file_nameMGMNT-CLASS: management_classTSM Server: server name.

Explanation: Data Protection for mySAP.com startedsaving current_num files at current_time. The totalnumber of files to save is total_num. The file file_name iscurrently being processed. The files are transferred tothe Tivoli Storage Manager server server name, whichstores them in the Management Class management_class.


BKI0030I Time: current_timeObjects: current_num of total_numin process: file_nameSize: bytes MBTSM Server: server name.

Explanation: Data Protection for mySAP.comcompleted saving current_num files at current_time. Thetotal number of files to save is total_num. The filefile_name is currently being processed. The TivoliStorage Manager server server name is selected.


BKI0031W Object not found or not accessible:objectname.

Explanation: The object was not found or is notaccessible to Data Protection for mySAP.com.

User Response: Check path and name and thepermissions of that object and try again.

BKI0032E Error opening file file name: system errordescription

Explanation: A system error occurred during openingof the file file name. system error description will describethe error in more detail.

User Response: Read the system error description.

BKI0033E Error opening file file name: system errordescription

Explanation: See BKI0032E.

User Response: See BKI0032E.

BKI0049I Please enter password for node nodenameon server server name

Explanation: The password for the node nodename onthe Tivoli Storage Manager server server name has to beentered for storing it in the Data Protection formySAP.com configuration file.

User Response: Enter the password for thecorresponding Tivoli Storage Manager server.

BKI0050I Please enter password for node nodenameon server server name again

Explanation: In order to avoid typing errors, you haveto enter the password twice.

User Response: Enter the password again.

BKI0051I Password successfully verified for nodenodename on server server name.

Explanation: The password for the node nodename onthe Tivoli Storage Manager server server name waschanged successfully.


BKI0052E Password verification for node nodenameon server server name failed.

Explanation: The password you entered for the nodenodename on the Tivoli Storage Manager server servername was wrong.

User Response: Enter the password again. If this errorstill exists, contact your Tivoli Storage Manageradministrator.

BKI0053I Time: current_timeObjects: current_num of total_numdone: file_name with: bytes saved withdescription object_desc.

Explanation: Data Protection for mySAP.comcompleted saving current_num file at current_time. Thetotal number of files to be saved is total_num. The filefile_name with the size bytes is saved with thedescription object_desc.


Appendix A. Data Protection for mySAP.com Messages 83

BKI0054I Time: current_timeObjects: current_num of total_numdone: file_name with: bytesrestored with description object_desc.

Explanation: Data Protection for mySAP.comcompleted restoring of current_num file at current_time.The total number of files to be restored is total_num.The file file_name with the size bytes is restored with thedescription object_class.


BKI0055I Object objectname with size saved withdescription description.

Explanation: The object objectname was savedsuccessfully.


BKI0056I Object objectname with size restored withdescription description.

Explanation: The object objectname was restoredsuccessfully.


BKI0057I Time: current_time Object objectname withsize saved with description description.

Explanation: The object objectname was savedsuccessfully.


BKI0058I Time: current_time Object objectname withsize restored with description description.

Explanation: The object objectname was restoredsuccessfully.


BKI0059E You have to set the environmentvariable DSMI_CONFIG to the fullfilename of the Tivoli Storage Managerclient option file ’dsm.opt’.

Explanation: Tivoli Storage Manager client option filenot found.

User Response: Verify that the Tivoli Storage Manageroption file dsm.opt is pointed to by DSMI_CONFIG.

BKI0060E The parameter parameter is not known.

Explanation: The command parameter parameter forData Protection for mySAP.com is unknown.

User Response: Check the specified commandparameter and try again.

BKI0061W The output file file name is not valid.

Explanation: The specified output file file name couldnot be created.

User Response: Check that file name is a valid filename on your operating system. Also check that theapplication has the appropriate permissions to createthe file within the specified directory. The directorymust already exist. If the file already exists, rename theold one.

BKI0062E The input file file name is not valid.

Explanation: Data Protection for mySAP.com is notable to read the input file file name correctly.

User Response: Check the path and name of theoutput file and the appropriate file access permission.

BKI0063E The UTL file file name is not valid.

Explanation: Data Protection for mySAP.com is notable to read the input file file name correctly.

User Response: Check the path and name of theoutput file and the appropriate file access permission.

BKI0064E The option option is unknown.

Explanation: A Data Protection for mySAP.com optionis invalid or unknown.

User Response: Check the specified option(s) and tryagain.

BKI0065E The argument is missing for optionoption.

Explanation: Every Data Protection for mySAP.comoption requires an argument.

User Response: Insert the missing argument and tryagain.

BKI0101I Session session: Please enter ’cont’ tocontinue or ’stop’ to cancel.

Explanation: If Data Protection for mySAP.com isrunning in unattended mode (profile keyword BATCH),it terminates the current run if operator intervention isrequired.

User Response: Enter ’cont’ or ’stop’.

BKI0102I Your reply: reply.

Explanation: Data Protection for mySAP.com indicatesthe reply you made.



|||

||

|

|||

||

|

BKI0311E Request canceled by user.

Explanation: BACKINT terminated at user’s request.

User Response: None

BKI0400I TDP is waiting for BRBACKUP

Explanation: Data Protection for mySAP.com iswaiting for BRBACKUP to set a tablespace in thebegin/end backup mode.


BKI0405I TDP waited num_sec sec. forBRBACKUP in util_file_onlinecommunication.

Explanation: Data Protection for mySAP.com waitednum_sec seconds for BRBACKUP to set a tablespace inbegin/end backup mode.


BKI0410E Cannot open or delete switch file filename. Check permissions.

Explanation: If Data Protection for mySAP.com is notinstalled correctly (as the root user on UNIX oradministrator group on Windows) then Data Protectionfor mySAP.com is not able to open the necessarycommunication file to the mySAP.com system.

User Response: Check the file permission.

BKI0411E Maximum time waiting for BRBACKUPexpired.

Explanation: The SAP database utilities did notrespond within the expected time.

User Response: Contact your mySAP.comadministrator.

BKI0412E BRBACKUP wasn’t able to switchrequested tablespace in BEGIN/ENDBACKUP mode.

Explanation: Data Protection for mySAP.com couldnot continue the backup, because BRBACKUP was notable to switch the requested tablespace in BEGIN orEND backup mode. This is necessary for locking thetablespace.


BKI0413E Error while requesting tablespaceswitch.

Explanation: BRBACKUP could not switch tablespacein BEGIN or END backup mode.


BKI0414E Error while requesting tablespaceswitch.

Explanation: BRBACKUP reported an error whiletrying to switch a tablespace in BEGIN or END backupmode.


BKI0450I Version 2 restore: file

Explanation: A restore of data backed up with DataProtection for mySAP.com version 2 was executed.


BKI0451I This version of Data Protection formySAP.com technology (R) will expireon date.

Explanation: This is a test version that will expire ondate.


BKI0452E This version of Data Protection formySAP.com technology (R) has expired.

Explanation: This is a test version that has expired.

User Response: Order a release version of DataProtection for mySAP.com or contact your IBM/TivoliSales Representative.

BKI0453W This version of Data Protection formySAP.com technology (R) will expirein number days.

Explanation: This is a test version with a time limit. Itwill expire in number days.

User Response: Order a release version of DataProtection for mySAP.com or contact your IBM/TivoliSales Representative before the version expires.

BKI0454I *** This copy is NOT FOR RESALE. ***

Explanation: This version is not for resale.


BKI0455E License file file name does not exist.

Explanation: The license file agent.lic was not foundwhere expected.

User Response: Make sure that the agent.lic fileresides in the same directory as the init<SID>.utl file.


||||

|||||

||

|||

||

||

|||

|||

||

BKI0456E Unable to access license file file name.

Explanation: The license file could not be accessed.

User Response: Make sure the access permissionsallow read/write access.

BKI0457E License file file name contains invaliddata/checksum.

Explanation: The license file is invalid.

User Response: Make sure you have the rightagent.lic file for the right platform installed.agent.lic files are platform dependent.

BKI0459E More than one mux file is found withthe same name detailed backup description.

Explanation: Two or more data sources with namedetailed backup description exist.

User Response: Contact your Data Protection formySAP Technology administrator.

BKI1000E Syntax error in line line: statement

Explanation: The statement statement in the DataProtection for mySAP.com profile is unknown orincorrect.

User Response: Correct the error and try again.

BKI1001E Syntax error in file file name. ExitingProgram.

Explanation: Data Protection for mySAP.com hasdetected an syntax error in the file file name and stopsany action.

User Response: Correct the error(s) in the file file nameand try again.

BKI1002E BACKUPIDPREFIX must benumber_of_characters characters.

Explanation: The length of BACKUPIDPREFIX mustbe number_of_characters characters.

User Response: Enter a BACKUPIDPREFIX with therequired length (e.g., SAP___, BKI___).

BKI1003W Please set REDOLOG_COPIES to anumber between 1 and max_copies. Nowit is set to act_copies.

Explanation: Data Protection for mySAP.com currentlysupports 1 to 9 copies of offline redo log files.

User Response: Adapt the REDOLOG_COPIESsettings in the Data Protection for mySAP.com profile.

BKI1004W You should specify theBACKUPIDPREFIX before theTRACEFILE statement, so that theBACKUPIDPREFIX can be used in thetracefile name.

Explanation: The BACKUPIDPREFIX is used to buildthe Name of the tracefile. Therefore,BACKUPIDPREFIX must be specified before theTRACEFILE statement.

User Response: Define a 6-characterBACKUPIDPREFIX in the Data Protection formySAP.com profile (e.g., SAP___, BKI___).

BKI1005W The tracefile name trace_filename shouldbe absolute.

Explanation: None.

User Response: Specify an absolute tracefile name, forexample /oracle/C21/saptrace/tracefile .

BKI1006E The SERVERNAME must be less thanmax_char characters.

Explanation: You have used a SERVERNAME withmore than max_char characters.

User Response: Use a shorter SERVERNAME.

BKI1007E The NODENAME must be less thanmax_char characters.

Explanation: You have used a NODENAME withmore than max_char characters.

User Response: Use a shorter NODENAME.

BKI1008E The MANAGEMENTCLASSNAMEmust be less than max_char characters.

Explanation: You have used aMANAGEMENTCLASSNAME with more thanmax_char characters.

User Response: Use a shorterMANAGEMENTCLASSNAME.

BKI1009W Please set MULTIPLEX to a numberbetween 1 and max_multiplex. Now it isset to act_multiplex.

Explanation: You have set multiplexing to anunsupported number. Data Protection for mySAP.comnow uses act_multiplex.

User Response: Set multiplexing to a number between1 and max_multiplex.


|||

||

||

BKI1010W The configfile nameconfiguration_filename should be absolute.

Explanation: None.

User Response: Specify an absolute file name, forexample /oracle/C21/dbs/initC21.bki

BKI1011W The sortfile name sortfile_filename shouldbe absolute.

Explanation: None.

User Response: Specify an absolute file name, forexample /oracle/C21/dbs/sortfile.

BKI1012E The configfilename configuration_filenamecould not be opened.

Explanation: Data Protection for mySAP.com is unableto read the file configuration_filename.

User Response: This error could have various reasons,try the following:1. Check the path of the configuration file. The path

must be specified in the profile (parameterCONFIG_FILE).

2. Make sure that the file access permissions are setcorrectly.

BKI1013E Profile not found or permissions denied:profile_filename.

Explanation: Data Protection for mySAP.com is unableto open the profile profile_filename.

User Response: Ensure that the SAP backup profileinit<SID>.sap contains a valid entry util_par_file forthe Data Protection for mySAP.com profile.Furthermore, this file must be readable by DataProtection for mySAP.com. See “Customizing DataProtection for mySAP.com and SAP Backup Profiles” onpage 25 for details.

BKI1014I The parameter PERF_MONITOR is nolonger supported. Now it is enabled bydefault.

Explanation: For version 2.7 or later of DataProtection for mySAP.com, the Performance Monitor ofthe Administration Assistant can be used by default.Therefore, the profile parameter PERF_MONITOR is nolonger needed.


BKI1015I The parameter BACKAGENT is nolonger needed.

Explanation: For version 2.7 or later of DataProtection for mySAP.com, only one executable, calledBACKINT, will be provided and needed. The former

executable, called BACKAGENT, will no longer besupported or needed.


BKI1016W The trace file name file name could notbe opened for writing!

Explanation: The trace file could not be opened forwriting.

User Response: Ensure that you have specified acorrect path for the trace file.

BKI1017E The server server name is alreadydefined. Please use another name!

Explanation: The server you want to configure isalready defined.

User Response: Specify another server name. Servernames have to be unique.

BKI1019E Failed to respond to a message receivedfrom XINT.

Explanation: This messages indicates an internal error.

User Response: Contact Data Protection formySAP.com technology support.

BKI1023W Could not establish connection to logserver log server name.

Explanation: In the Data Protection for mySAP.comtechnology profile, log server log server name isspecified (keyword LOG_SERVER). However, aconnection to the server named could not beestablished. No log records are sent to the log server.

User Response:

v Check that the server name defined with keywordLOG_SERVER is spelled correctly in the DataProtection for mySAP.com profile.

v Make sure there is a SERVER section in the profilefor the log server defined with keywordLOG_SERVER.

v Check the corresponding SERVER section and correctany setup problems.

v Make sure that the log server named is available.

BKI1200E Cannot read/write file: file name.

Explanation: Data Protection for mySAP.com is unableto read or write a data file (file name) of a tablespacebeing backed up or restored.

User Response: Check the file access permission ofthe affected file(s). Try again. If the problem still exists,contact the mySAP.com administrator.


|||

|

||

|||

|||||

|

|||

|||

||

|

BKI1201E There are no Tivoli Storage ManagerServers available.

Explanation: Data Protection for mySAP.com cannotlocate a Tivoli Storage Manager server.

User Response: Install and specify at least one TivoliStorage Manager server in the Data Protection formySAP.com profile (keyword SERVER).

BKI1202E You must specify eitherMAX_SESSIONS or all offMAX_ARCH_SESSIONS,MAX_BACK_SESSIONS andMAX_RESTORE_SESSIONS

Explanation: There is a setup error with theSESSIONS parameters within the Data Protection formySAP.com profile.

User Response: Specify either MAX_SESSIONS andone of the more specific parametersMAX_ARCH_SESSIONS, MAX_BACK_SESSIONS orMAX_RESTORE_SESSIONS or all of the three specificsession parameters without the MAX_SESSIONSparameter.

BKI1203E Not enough sessions available (numberof sessions required and number ofsessions available).

Explanation: The sum of available sessions specifiedin the various server statements (parameter SESSIONS)does not cover the required number of sessions(parameter MAX_SESSIONS).

User Response: Change the values of thecorresponding parameters in the Data Protection formySAP.com profile, so that the condition mentioned inthe explanation is fulfilled.

BKI1205E If you want num_redoREDOLOGCOPIES on Tivoli StorageManager-Server servername, you shouldgive me at least num_mc differentArchive Management Classes.

Explanation: Data Protection for mySAP.com requiresthat the number of different Archive ManagementClasses (parameter BRARCHIVEMGTCLASS) on theTivoli Storage Manager servers is equal to or greaterthan the number of redo log copies (parameterREDOLOG_COPIES).

User Response: Define at least as many differentArchive Management Classes as redo log copiesrequested.

BKI1206W If you want num_redoREDOLOGCOPIES on Tivoli StorageManager Server server name, you shouldgive me at least num_mc differentArchive Management Classes.

Explanation: The message appears during aBRBACKUP run. A BRARCHIVE run afterwards wouldfail.

User Response: Define at least as many differentArchive Management Classes as log file copiesrequested.

BKI1207E Directory backup not supported

Explanation: This option is not yet available.

User Response: Wait for a future release of DataProtection for mySAP.com, which supports this option.

BKI1208W The object file name will be retried[retry_num]

Explanation: There was an error with the objectfile_name. Data Protection for mySAP.com will try tosave/restore the object one retry_num times.

User Response: Look at the error messages in theData Protection for mySAP.com protocol and correct theerror for the next run.

BKI1209E Object not found or not accessibleobjectname.

Explanation: Data Protection for mySAP.com cannotlocate the Oracle object objectname.

User Response: The backup integrity is affected.Contact the SAP or Data Protection for mySAP.comsupport.

BKI1210E Input file not found or not accessible filename.

Explanation: Data Protection for mySAP.com cannotlocate the temporary file file name. This file contains thelist of Oracle objects to be backed up/restored. It ispassed to Data Protection for mySAP.com byBRBACKUP, BRARCHIVE or BRRESTORE.

User Response: Ensure that you have the correctversion of SAPDBA, BRBACKUP, BRARCHIVE orBRRESTORE installed. See Chapter 3, “Setting Up DataProtection for mySAP.com”, on page 19.

BKI1211E There is something wrong with yourCONFIG_FILE file name.

Explanation: There is a problem with your DataProtection for mySAP.com configuration file setup.

User Response: Check the file permission and the file


name specified in the Data Protection for mySAP.comprofile keyword CONFIG_FILE.

BKI1212W The file file name was not found in themanual sorting file.

Explanation: The file you want to back up was notfound in the manual sorting file.

User Response: Check and correct the manual sortingfile so that it contains all the files you are backing up.

BKI1213I Program ended with code = return code

Explanation: The return code of the program isdisplayed.


BKI1214E TSM Error: error text

Explanation: The specified TSM error occurred.

User Response: Check error text and correct theproblem.

BKI1215I Average transmission rate was numberGB/h (number MB/sec).

Explanation: The average transmission rate isdisplayed.


BKI1216E There are no BRBACKUPMGTCLASSESavailable.

Explanation: The BRBACKUPMGTCLASSES you havespecified in your init<SID>.utl file are not correct.

User Response: Check the management classes on theTSM server and specify correct ones.

BKI1217E There are no BRARCHIVEMGTCLASSESavailable.

Explanation: The BRARCHIVEMGTCLASSES youhave specified in your init<SID>.utl file are not correct.

User Response: Check the management classes on theTSM server and specify correct ones.

BKI1222E Version missmatch error. Check setup(%1$S:%2$S).

Explanation: The version numbers of the installedexecutables BACKINT and PROLE do not match.

User Response: Check your setup or contact DataProtection for mySAP.com support.

BKI1223W A problem occurred during send ofperformance data to AdministrationAssistant .

Explanation: There was a problem sending theperformance data to the Administration Assistant overthe network.


BKI1224W Unable to initialize connection toAdministration Assistant.

Explanation: There was a problem initializing theconnection to the Administration Assistant over thenetwork.


BKI2000I Successfully connected to PROLE onport portnumber.

Explanation: One of the Data Protection formySAP.com modules BACKINT or the backup librarylibtdp_r3 initiated a successful connection to thebackground process PROLE on port portnumber.


BKI2001E Socket error while connecting toPROLE: reason.

Explanation: The Data Protection for mySAP.combackground process PROLE is not running.

User Response: Start PROLE manually and try again.

BKI2002E No valid callback function of typefunc_type supplied.

Explanation: Internal Data Protection for mySAP.comerror

User Response: Contact Data Protection formySAP.com support.

BKI2003I File file_name, BID deleted.

Explanation: The file file_name with the backup IDBID was deleted from the Tivoli Storage Manager.


BKI2004E Connection to PROLE lost.

Explanation: During Data Protection for mySAP.comoperation the connection to PROLE was lost. Networkproblems could be the reason.

User Response: Check your network environment andif PROLE is still running and try again.


||||

|||

||

BKI2005E Illegal parameter in message fromPROLE. Exiting...

Explanation: This error occurs if the versions ofPROLE and the executable BACKINT or the backuplibrary libtdp_r3 do not match.

User Response: Check the versions of PROLE andBACKINT/backup library libtdp_r3 you are currentlyusing.

BKI2006E General exception in dispatcher.Exiting...

Explanation: Internal Data Protection for mySAP.comerror.


BKI2007E Unknown Port: port

Explanation: The port specified for communicationbetween PROLE and BACKINT is unknown.

User Response: Check the port value specified whenPROLE was started. Additionally, check theenvironment variable PROLE_PORT for the BACKINTenvironment. These two values must match.

BKI2008E Unable to connect to PROLE.

Explanation: Internal Data Protection for mySAP.comerror.


BKI2009I Deleting all versions with versionnumber <= version_number on serverserver_name.

Explanation: All full database backups and theircorresponding log file backups will be deleted fromTivoli Storage Manager storage, if their version numberis less than or equal to version_number.


BKI2010E Error occurred processing FRONTEND

Explanation: An error occurred during the frontendprocessing.

User Response: Check the frontend script/programand the settings in the Data Protection for mySAP.comprofile (keyword FRONTEND) and try again.

BKI2011E Error occurred processing BACKEND.

Explanation: An error occurred during the backendprocessing.

User Response: Check the backend script/programand the settings in the Data Protection for mySAP.comprofile (keyword BACKEND) and try again.

BKI2012E Passwords do not match. Try again.

Explanation: The first and second password youentered do not match.

User Response: Enter the password correctly.

BKI2013I Starting FRONTEND Program.

Explanation: The frontend program is executing.


BKI2014I FRONTEND program finished.

Explanation: The frontend program is finished.


BKI2015I Starting BACKEND program.

Explanation: The backend program is executing.


BKI2016I BACKEND program finished.

Explanation: The backend program is finished.


BKI2017I Blocksize is set to num_bytes bytes.

Explanation: The operational blocksize of DataProtection for mySAP.com is num_bytes bytes.


BKI2018E Exception in main message loop:description

Explanation: An error occurred during processing.The error may contain a descriptive text.

User Response: Contact your service representative.

BKI2019E Socket error while connecting to PROLEon port number for tracing: description

Explanation: During processing, a socket erroroccurred on port ’number’. ’description’ may contain thesystem error text.

User Response: Check the ’description’. If the errorpersists, contact your service representative.


|||

BKI2020E Error occurred for trace connection toPROLE on port number.

Explanation: The network connection that is used fortracing generated an error on port ’number’.


BKI2021E Unable to delete file file name: description

Explanation: Unable to delete the file ’file name’.’description’ may contain the system error text.


BKI2022E Unable to change mode of file file name:description

Explanation: Unable to change mode of file ’file name’.’description’ may contain the system error text.


BKI2023E Error occurred during trace connectionto PROLE. Tracing will stop now.

Explanation: Error occurred during trace connectionto PROLE.

User Response: Tracing will stop. If the problempersists, contact your service representative.

BKI2024E Error in connection to PROLE.

Explanation: The connection to PROLE terminatedunexpectedly. This message might be displayed due toprevious errors or after an unexpected termination ofthe PROLE process.

User Response: Check for other error messages andrestart PROLE if necessary. Try again. If the problempersists, contact Data Protection for mySAP.comsupport.

BKI2025E Failed to respond to a message receivedfrom PROLE.

Explanation: This is an internal error

User Response: Contact Data Protection formySAP.comsupport.

BKI2026E Unexpected exception in handler: handler

Explanation: This is an internal error.


BKI2027I Using TSM-API version your api version(compiled with compiled with version).

Explanation: Version information about the TSM-API.

User Response: None

BKI2028W Unable to terminate session session.

Explanation: This is an internal error during cleanupthat has no effect on the success of the service.

User Response: None

BKI4000W The attributes of file file name cannot berestored. Reason: errno (error_num)error_desc.

Explanation: The file file name was restoredsuccessfully but one or more file attributes (permission,ownership, date/time) of the file file name cannot berestored correctly.

User Response: Check the error number error_numand the error description error_desc to avoid thisproblem in the future. An initial solution could be toset the appropriate correct permission for the file filename manually.

BKI4001E File file name cannot be created. Reason:errno (error_num) error_desc.

Explanation: The file file name to be restored could notbe created/written. It is possible, that you do not havethe appropriate rights for writing the file file name tothe destination path.

User Response: Check the error number error_numand the error description error_desc to avoid thisproblem in the future. Furthermore, check the writepermission of the user who started the restore.

BKI4002E Error during restore of file file name.Reason: errno (error_num) error_desc.

Explanation: An error occurs during the restoreprocess of the file file name.

User Response: Check the error number error_numand the error description error_desc to avoid thisproblem in the future.

BKI4003E Error reading file file name. Only readnum_bytes out of all_bytes.

Explanation: An error occurs reading the file file name.Only num_bytes of all_bytes could be read.

User Response: Try your last action again. If the errorstill exists, contact Data Protection for mySAP.comsupport.


BKI4004E Error writing file filename. Only wrotenum_bytes out of all_bytes.

Explanation: An error occurs writing the file file name.Only num_bytes of all_bytes could be written.

User Response: Try your last action again. If the errorstill exists, contact Data Protection for mySAP.comsupport.

BKI4005E Error allocating memory block for filefile name. BLOCKSIZE may be too large.

Explanation: Data Protection for mySAP.com was notable to request new memory blocks during the backupof file file name.

User Response: Verify that you have set a valid valuefor BLOCKSIZE. If you are not sure what value isvalid, comment it out so the default value is used.Furthermore, you can check if you have enough RAMavailable with your machine. Also, check the memoryusage during backup. It may be necessary to stopanother application, increase memory, or change theconfiguration of Data Protection for mySAP.com.

BKI4006E Error allocating memory block for filefile name. BLOCKSIZE may be too large.



BKI4007E File filename cannot be read. Reason:errno(errno number) errno text.

Explanation: Data could not be read due to somesystem error. Check errno text for further information. Ifthis error recurs, this might indicate some hardwareproblems.

User Response: Contact your system administrator.

BKI4008E File filename cannot be opened. Reason:errno(errno number) errno text.

Explanation: Data Protection for mySAP Technologycould not open the file file namedue to some systemspecific problems.


BKI4009E Not enough space to write file file name.Possible reasons: disk full or ulimitexeeded.

Explanation: The system rejected a request to writedata into file file name. The storage media might nothave enough free space to keep the file or the systemrejected writing the file due to administrative resourceconstraints such as ulimits.


BKI5000E Tivoli Storage Manager Error:error_message

Explanation: During a connection of Data Protectionfor mySAP.com to Tivoli Storage Manager server, aTivoli Storage Manager error error_message occurred.

User Response: Use the Tivoli Storage ManagerMessages guide and correct the Tivoli Storage Managerserver error. Try your last action again.























|||

|||

|

||||

|||||

|













BKI5012E Cannot open TSM API message text file.Check if DSMI_DIR is set correctly.Current value of DSMI_DIR is: value

Explanation: The TSM-API could not be initialized.

User Response: Correct the value of the environmentvariable DSMI_DIR.

BKI5013E Value for name is too long. Currentvalue: value

Explanation: The value of the environment variablename has too many digits.

User Response: Check if the variable is set correctly.




BKI5015W Data description could not be restored,because it was backed up with a newerversion (objInf=support information)

Explanation: The TSM server hosts backups (i.e. datadescription) which were made with a new version ofbackint. Backint ignores this data in the furtherprocessing.

User Response: Upgrade backint

BKI7001E Backup file file name already exists.

Explanation: This is an RMAN internal error.

User Response: See your Oracle documentation orcontact your Oracle database administrator.

BKI7002E Bad mode specified.



BKI7012E Invalid arguments during call offunction.



BKI7020E Bad handle rman_handle during call offunction.



BKI7021E Bad flags during call of function.



BKI7049I The default ProLE port will be used.

Explanation: The port for the internal communicationof Data Protection for mySAP.com is set duringinstallation. The message indicates that this port isbeing used.


BKI7051E The environment variableXINT_PROFILE is not set. It must be setand contain the full qualified path tothe *.utl file to be used.

Explanation: The way Data Protection for mySAP.comworks is specified in a profile. When called, DataProtection for mySAP.com looks for the environmentvariable XINT_PROFILE which must contain the fullyqualified path to the profile.

User Response: Check the environment forXINT_PROFILE of the user who started Data Protectionfor mySAP.com.


|||

|

|

||||

||||

|

||

||||

|

|||||

|||||

|||

BKI7053E Service setup failed due to previouserror.

Explanation: The initialization of Data Protection formySAP.com failed due to previous errors.

User Response: Check the Data Protection formySAP.com log file for further detailed messages.

BKI7055E Service open failed due to previouserror in data mover.

Explanation: The Data Protection for mySAP.comcommand could not be started due to previous errors.


BKI7056E Service open failed because configuredTSM server could not be accessed.

Explanation: The Data Protection for mySAP.comcommand could not be started because the TSM serverdefined in the profile could not be accessed.


BKI7057E Service open failed because allconfigured sessions are currently in use.

Explanation: The Data Protection for mySAP.comcommand could not be started because all configuredsessions in the profile are currently in use.


BKI7058E Service open failed because more thanone file is found with the same name.

Explanation: The Data Protection for mySAP.comcommand could not be started because two or morefiles with the same name were found.


BKI7059E Service open failed because cause thefile is not found.

Explanation: The Data Protection for mySAP.comcommand could not be started because a file specifiedwas not found.


BKI9000E System error: error

Explanation: Data Protection for mySAP.com hasfound the following error: error. This is a ’catch-all’error code for unpredictable system errors.


BKI9001E Internal error: error

Explanation: Data Protection for mySAP.com hasfound the following internal error: error.


BKI9002E Error in stream task: %1$S

Explanation: There was an error in the processing of adata stream. Data Protection for mySAP.com will stopprocessing.


BKI9005E A not supported by B.

Explanation: The installed version of product B doesnot support product A. Most likely you need toupgrade product B.

User Response: Contact the Data Protection formySAP.com support.

BKI9006E Internal error while readingenvironment variable: variable.

Explanation: This is an internal error.


BKI9007W An error occurred while terminating theapplication: the error

Explanation: While terminating the application, anerror occurred. This has no impact on the success of theoperation.

User Response: None

BKI9200E Additional support information: AnException was thrown at position:position.

Explanation: This error message typically follows aprevious error. If so this error message can be ignored.Otherwise contact your Data Protection for mySAP.comsupport



|||

||

||

|||

|||

||

|||

|||

||

|||

|||

||

|||

|||

||

||||

||||

||





Explanation: This error message typically follows aprevious error. If so this error message can be ignored.Otherwise contact your Data Protection for mySAP.comsupport.





BKI9204E Additional support information: AnException was thrown at position:position (text=description).



BKI9205E Additional support information: Unableto instantiate name at position position.



BKI9206E Additional support information: Unableto use actual when expecting expected atposition position.






BKI9208E System error errno: errno text at positionposition.

Explanation: A system call failed with errno.

User Response: Check errno and errno text with yousystem administrator. If you cannot resolve theproblem, contact Data Protection for mySAP.comsupport.

BKI9209E Additional support information: Nohandler registered for message typemessage. Thrown at position: position.



BKI9210E ESD_AbortDispatchingException thrownat position: position.

Explanation: An internal error occurred.


BKI9211E Additional support information: AnException was thrown at position:position. (State state)



||||

||||

||

||||

||||

||

||||

||||

||

||||

||||

||

|||

||||

||

||||

||||

||

||||

||||

||

||||

||||


BKI9212E Additional support information: Nohandler registered for message type type.Thrown at position: position.



BKI9213E Internal error: A memory allocationrequest failed at position: position.



BKI9214E Additional support information: Anexception was thrown from a destructor.Callstack follows: callstack.



BKI9215E Additional support information: Anexception was thrown at position:positien.






BKI9217E Additional support information: Anexception was thrown at position:position.






BKI9219E Additional support information: Invaliderror type typeencountered.



BKI9220E Additional support information: Secondcall of call.



BKI9300E Additional support information: ″send″continued at client’s request.

Explanation: This error may have been caused byprevious errors.

User Response: Check for previous errors and correctthem.

BKI9301E Additional support information: Statestate does not match state pattern pattern.



||

||||

||||

||

||||

||||

||

||||

||||

||

||||

||||

||

||||

||||

||

||||

||||

||

|||

||||

||

|||

||||

||


BKI9302E Additional support information: UnusedESD_ReturnChannel destroyed.Dumping callstack: callstack



BKI9306I Dumping callstack: call stack.

Explanation: This message is always preceded by anerror message indicating the problem. It providesadditional information that might help your DataProtection for mySAP.com support to analyze the causeof the problem.

User Response: If you need to call Data Protection formySAP.com support, provide the information given inthis message together with the error information.

BKI9307E Did not find a winsock dll compatiblewith version expected version. Versionfound is available version

Explanation: Data Protection for mySAP.com failed toload the appropriate winsock dll.

User Response: Contact your system administrator

BKI9308E A socket request timed out afterprocessing number of bytes bytes. position.

Explanation: A socket request was issued with atimeout and the requested action could not becompleted within the time specified. It was cancelledafter processing number of bytes bytes.

User Response: If you need to call Data Protection formySAP.com support, provide the information given inthis message together with the error information.


||||

||||

||

||

|||||

|||

||||

||

|

|||

||||

|||

Data Protection for mySAP.com File Manager Error Messages

BACKINT not found!

Explanation: The executable BACKINT was not found.This executable is necessary to run Data Protection formySAP.com File Manager.

User Response: Make sure BACKFM is installed inthe same directory as BACKINT and has the samepermission.

Profile not specified. Please use 'backfm -p<ParFileName>' !

Explanation: Since Data Protection for mySAP.comFile Manager calls Data Protection for mySAP.com, theprofile for Data Protection for mySAP.com is required.

User Response: Specify the full file name of the DataProtection for mySAP.com profile when starting DataProtection for mySAP.com File Manager, for example:backfm -p /oracle/C21/dbs/initC21.utl.

BACKINT call was not successful!

Explanation: The communication with the TivoliStorage Manager server failed.

User Response: Check that Data Protection formySAP.com and the Tivoli Storage Manager server(s)work correctly. It must be possible to run DataProtection for mySAP.com directly from the commandline, otherwise Data Protection for mySAP.com FileManager will also not work.

Cannot open temporary file!

Explanation: A temporary file could not be opened.This could have several reasons.

User Response:

UNIX Make sure the directory /tmp is not full andyou have write permission for this directory.

WindowsMake sure that the current drive is not full.

Unable to allocate memory!Unable to install SIGWINCH-handler!Unable to remove Backup IDs!Unable to install SIGINT-handler!Can’t get window size!

Explanation: These error messages indicate problemswhich usually cannot be resolved by the usersthemselves.

User Response: Inform your system administrator orData Protection for mySAP.com support about thisproblem.


Appendix B. Using Data Protection for mySAP.com withRMAN

You can use the Recovery Manager (RMAN) to do a backup, restore and recoveroperation of an Oracle database. Furthermore, if you want to make incrementalbackups, this can only be done with RMAN.

NoteCheck the Online Service Support (OSS) system from SAP on how to set upbackup via RMAN on your operating system. Check also for specialconsiderations for the database version you are using.

RMAN Setup on UNIX SystemsShared libraries have different file extensions on different UNIX platforms. Withinthe following the section, the file extensions of shared libraries are represented as’<ext>’. Replace this text with the extension applying to your platform:

Table 6. File Extensions for Shared Libraries

Operating System Extension

AIX a

HP-UX sl

Linux so

Solaris so

In the following description you have to replace the directory name ora<bit> inthe installation path. Depending on the version of Data Protection for mySAP.comyou have installed, you must replace it withora32 for the 32–bit version of Data Protection for mySAP.comora64 for the 64–bit version of Data Protection for mySAP.com.

To set up your Data Protection for mySAP.com for use with RMAN under UNIX,follow these steps:1. Install Tivoli Storage Manager API Client on your mySAP.com database server

(see “Configuration of Tivoli Storage Manager Clients” on page 16).2. Install Data Protection for mySAP.com on your mySAP.com database server

(see Chapter 3, “Setting Up Data Protection for mySAP.com”, on page 19).3. Set Data Protection for mySAP.com password for Tivoli Storage Manager (see

“Password Handling” on page 26).4. Add the path to the library shipped with Data Protection for mySAP.com to the

library path environment of your system.5. Create a softlink in /usr/lib for ’libobk.<ext>’ to

/usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>, if not already done by theinstaller.

6. Link the library shipped with Data Protection for mySAP.com (libtdp_r3) withRMAN.

7. Shut down the database and do the following as Oracle user:


Example for Oracle 8.0cd $ORACLE_HOME/rdbms/libln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libobk.<ext>make -f ins_rdbms.mk ioracle LLIBMM=/usr/lib/libobk.<ext>

Example for Oracle 8.1cd $ORACLE_HOME/rdbms/libln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libobk.<ext>make -f ins_rdbms.mk ioracle LLIBOBK=/usr/lib/libobk.<ext>

8. Customize the SAP backup profile init<SID>.sap for use with RMAN. Insertthe following:

backup_dev_type=rman_utilrman_parms="ENV=(system,XINT_PROFILE=/<path>/init<SID>.utl,PROLE_PORT=portnumber)"

The appropriate Prole port number can be found in the /etc/services file.

Troubleshooting

1. Ensure that Oracle has linked the right library/usr/lib/libobk.<ext> linked to/usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>

2. Remove the library in /$ORACLE_HOME/rdbms/lib/libobk.<ext>.If you are running a 64–bit Oracle database system, also check in/$ORACLE_HOME/rdbms/lib64/.

3. The shared library must have the same bitwidth as the installed Oracle version:if you have a 64–bit Oracle running on AIX 4.3.3 64–bit, you need to install the64–bit version of Data Protection for mySAP.com.If you have a 32–bit Oracle running on a 64–bit AIX 4.3.3, you need to installthe 32–bit version of Data Protection for mySAP.com.Both versions of Data Protection for mySAP.com can coexist on one maschine.

4. Examine the sbtio.log located in the directory specified in the user_dump_destkeyword within the Oracle profile init<SID>.ora. This file is usually located atoracle/SID/saptrace/usertrace/sbtio.log.

5. Check the log file sbtio.log for lines starting with BKI. The first message forevery new service, for example, has the message ID BKI2027I. If you cannotfind any such message in the file, the library is not correctly linked with Oracle.

6. Examine the dsierror.log located in the directory specified with theenvironment variable DSMI_LOG

7. To get a Tivoli Storage Manager API trace file, set the following entries in theclient system options file dsm.sys:

tracefile /<path>/<trace file>traceflags api

8. On UNIX operating systems, an additional softlink may help in /usr/lib for’libtdp_r3.<ext>.1’ to /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>.

ln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libtdp_r3.<ext>.1


||||||

|||

|||

RMAN Setup on Windows SystemsTo set up your Data Protection for mySAP.com for use with RMAN underWindows, perform these steps:1. Stop the service OracleService<SID>2. Install the Tivoli Storage Manager API Client on your mySAP.com database

server (see “Configuration of Tivoli Storage Manager Clients” on page 16).3. Install Data Protection for mySAP.com on your mySAP.com database server

(see Chapter 3, “Setting Up Data Protection for mySAP.com”, on page 19).4. Set the Data Protection for mySAP.com password for Tivoli Storage Manager

(see “Password Handling” on page 26).5. Customize the SAP backup profile init<SID>.sap for use with RMAN. Insert

the following:

backup_dev_type=rman_utilrman_parms="ENV=(DSMI_DIR=<drive>:\<path>, DSMI_CONFIG=<drive>:\<path>\<client options file>,DSMI_LOG=<drive>:\<path>\dsierror.log,XINT_PROFILE=<drive>:\<path>\init<SID>.utl,PROLE_PORT=portnumber)"

The appropriate Prole port number can be found in the file<drive>:\WINNT\system32\drivers\etc\services

6. Start the following service:v OracleService<SID>

Troubleshooting

1. Examine the sbtio.log located in the directory specified in the user_dump_destkeyword within the Oracle profile init<SID>.ora.

2. If no file sbtio.log exists after an operation with RMAN or no line startingwith the letters ’BKI’ exists within an existing sbtio.log, check if the sharedlibrary orasbt.dll was found and loaded by Oracle. Put the shared library fileorasbt.dll into the directory %ORACLE_HOME%\bin. This is the directory whereoracle.exe resides. Now stop the service OracleService<SID> and restart it.

3. Examine the dsierror.log located in the directory specified with theenvironment variable DSMI_LOG

4. To get a Tivoli Storage Manager API trace file, set the following entries in theclient options file:

tracefile <drive>:\<path>\<trace file>traceflags api

Appendix B. RMAN Setup 101

|||||


Appendix C. Migration from Earlier Releases

Data Protection for mySAP.com Version 3.3. can be used to restore data that wasbacked up with Tivoli Data Protection for R/3 Version 3.1 to 3.2 or Data Protectionfor mySAP.com Version 3.3.

Data that was backed up with Tivoli Data Protection for R/3 Version 2.7 must berestored with Tivoli Data Protection for R/3 Version 3.1 or 3.2.


|

|

|||

||


Appendix D. Password Handling

Consider the following alternatives with their implications:

No password required by Tivoli Storage Manager (AUTHENTICATION OFF)This is the simplest method; however, no security can be enforced. Everyuser connected to this server (authentication is set OFF on the TivoliStorage Manager server level) can access Tivoli Storage Manager without apassword.

This method is only recommended if adequate security measures can beestablished otherwise, for example, if Tivoli Storage Manager is only usedfor mySAP.com (no other clients are registered), and the respectiveauthorizations are set in the UNIX system.

Manual password generationThis method is simple to set up and provides password security, however,it requires a synchronized update of the password in Tivoli StorageManager (client) and Data Protection for mySAP.com (command line). Thismethod is only recommended during installation and testing together witha sufficiently long expiration period (to avoid having to change thepassword). It is not recommended for production operation.

Password set by Tivoli Storage ManagerIn this case you do not have to synchronize the passwords manually onthe Tivoli Storage Manager server and client sides. The generation andsynchronization of passwords is handled by a Tivoli Storage Managerprogram. Tivoli Storage Manager sets the password automatically on aper-node basis according to the expiration specification. This method isrecommended for an automated production environment.


Configuration Matrix (UNIX)After you have selected the suitable password handling alternative, follow theconfiguration matrix to set the keywords/parameters in the different profilesaccordingly. Proceed as indicated by the step number.

Table 7. Password Handling for UNIX

Step Profile/Action Parameter Password

No Manual Set by TivoliStorage

Manager

1 Tivoli StorageManager admin

AUTHENTICATIONEXPIRATION PERIOD(see note 1)

OFFn.a.

ON<n days>(see note 2)

ON<n days>

2 dsm.sys PASSWORDACCESSPASSWORDDIR(see note 5)NODENAME

n.a.n.a.

n.a.

PROMPTn.a.

n.a.

GENERATE<path>

<nodename>

3 Tivoli StorageManager client(root user)

SET PASSWORD n.a. <password>(see note 3)

n.a.

4 Data Protection formySAP.com profile(init<SID>.utl)

For each SERVER statementspecify:PASSWORDREQUIREDADSMNODE

NO<nodename>

YES<nodename>

NO(see note 4)

5 Data Protection formySAP.comcommand line

For each SERVER statementspecify:backint -p initSID.utl

-f passwordSee “Password Handling” onpage 26.

n.a. <password>(see note 1)

<password>

Notes:

1. See Tivoli Storage Manager documentation.2. If you are using manual password generation during testing, make sure that

the expiration period is set to a sufficiently long time (> 60 days).3. For an initial setup, this password must be the same as was specified when

registering the node to Tivoli Storage Manager. The password must be changedfirst on the Tivoli Storage Manager server and then in the Data Protection formySAP.com product.

4. ADSMNODE must not be set when PASSWORDACCESS generate is set.5. The users <SID>adm and ora<SID> must have read and write permission for the

path specified.

Configuration Matrix (Windows)After you have selected the suitable password handling alternative, follow theconfiguration matrix to set the keywords/parameters in the different profilesaccordingly. Proceed as indicated by the step number.


|

Table 8. Password Handling for Windows

Step Profile/Action Parameter Password

No Manual Set by TivoliStorage

Manager

1 Tivoli StorageManager admin

AUTHENTICATIONEXPIRATION PERIOD(see note 1)

OFFn.a.

ON<n days>(see note 2)

ON<n days>

2 <server>.opt PASSWORDACCESSPASSWORDDIR(see note 5)NODENAME

n.a.n.a.

n.a.

PROMPTn.a.

n.a.

GENERATE<path>

<nodename>

3 Tivoli StorageManager client

SET PASSWORD n.a. <password>(see note 3)

n.a.

4 Data Protection formySAP.com profileinit<SID>.utl

For each SERVER statementspecify:PASSWORDREQUIREDADSMNODE

NO<nodename>

YES<nodename>

NO(see note 4)

5 Data Protection formySAP.comcommand line

For each SERVER statementspecify:backint -p initSID.utl

-f passwordSee “Password Handling” onpage 26.

n.a. <password>(see note 1)

<password>

Notes:

1. See Tivoli Storage Manager documentation.2. If you are using manual password generation during testing, make sure that

the expiration period is set to a sufficiently long time (> 60 days).3. For an initial setup this password must be the same as was specified when

registering the node to Tivoli Storage Manager. The password must be changedfirst on the Tivoli Storage Manager server and then in the Data Protection formySAP.com product.

4. ADSMNODE must not be set when PASSWORDACCESS generate is set.5. The users <SID>adm and sapservice<SID> must have read and write permission

for the path specified.

Appendix D. Password Handling 107

|


Appendix E. Alternate/Parallel Backup Paths and BackupServers

With Data Protection for mySAP.com we use the term ″path″ to denote aconnection between a Tivoli Storage Manager client, or better ADSM ″node″, and aTivoli Storage Manager server.

Data Protection for mySAP.com provides the capability for controlling alternatebackup paths and alternate backup servers in order to use several communicationlinks between Tivoli Storage Manager clients to:v Increase throughput by transferring data:

– Over multiple paths simultaneously– To and from several servers in parallel

v Increase the availability of the Tivoli Storage Manager client-to-servercommunication

v Enable disaster recovery backup to a special (remote) Tivoli Storage Managerserver

In the profile init<SID>.utl, each path is defined by a server statement (see also“Sample Data Protection for mySAP.com Profile for UNIX” on page 122) and thecorresponding definitions in the Tivoli Storage Manager client system option filedsm.sys (UNIX) or <server>.opt (Windows).

The statement SERVER <server 1..n> denotes Tivoli Storage Manager servers in theData Protection for mySAP.com profile. This corresponds to the statementSERVERNAME <server 1..n> in the Tivoli Storage Manager client option file(s). Theseservers are identified by their TCPSERVERADDRESS and can be located on one system(multiple paths) or several systems (multiple servers).

SESSIONS denotes the number of parallel session Data Protection for mySAP.comwill schedule for the given path.

NoteIf only 1 path is used, SESSIONS must be equal to MAX_SESSIONS, the parameteridentifying the total number of parallel sessions to be used (equivalent tonumber of tape drives/management classes).

Data Protection for mySAP.com attempts to communicate with the Tivoli StorageManager server using the first path in the profile. If this proves successful, DataProtection for mySAP.com starts the number of parallel sessions as specified forthis path; if the attempt was unsuccessful, this path is skipped, and Data Protectionfor mySAP.com continues with the next path. This continues until as many sessionsare active as were specified in the total session number (MAX_SESSIONS). If thisnumber is never reached (for example, because several paths were inactive), DataProtection for mySAP.com terminates the backup job.


Parameter Settings - SERVER StatementThe SERVER statement appears in the Data Protection for mySAP.com profile, andthere are corresponding keywords in the Tivoli Storage Manager client option file.(Depending on the choice of password handling, some parameters are ignored.)The connection of the sections in the Data Protection for mySAP.com profile andthe Tivoli Storage Manager client option file is established from the logical servername, which is defined in the keywords SERVER or SERVERNAME.

Table 9. SERVER Statement and Appropriate Profile and Option File Settings.

Configuration possibilities Data Protection for mySAP.comprofile init<SID>.utl

Tivoli Storage Manager client optionfile dsm.sys or <server>.opt [2]

single path; no password or manualpassword

SERVER <server>ADSMNODE <node>[1]

SERVERNAME <server>TCPSERVERADDRESS <address>NODENAME must not be

specified

single path; automatic password byTivoli Storage Manager

SERVER <server>ADSMNODE must not be

specified

SERVERNAME <server>NODENAME <node>TCPSERVERADDRESS <address>

several paths/servers; no passwordor manual password

SERVER <server 1>ADSMNODE <node 1>

•••

SERVER <server n>ADSMNODE <node n>

SERVERNAME <server 1>NODENAME must not be

specifiedTCPSERVERADDRESS <address 1>

•••

SERVERNAME <server n>NODENAME must not be

specifiedTCPSERVERADDRESS <address n>

several paths/servers; automaticpassword by Tivoli StorageManager[3]

SERVER <server 1>ADSMNODE must not be

specified•••

SERVER <server n>ADSMNODE must not be

specified

SERVERNAME <server 1>NODENAME <node 1>TCPSERVERADDRESS <address 1>

•••

SERVERNAME <server n>NODENAME <node n>TCPSERVERADDRESS <address n>

Notes:

[1] If ADSMNODE is not specified, the host name is used.

[2] On UNIX, dsm.sys is the single client option file for all Tivoli StorageManager servers. On Windows, there is a separate client option file<server>.opt for each Tivoli Storage Manager server.

[3] If two different physical machines have the same TSM node name or ifmultiple paths are defined on one node using several server stanzas,passwordaccess generate may only work for the first stanza that is usedafter password expiration.During the first client-server contact, the user is prompted for the samepassword for each server stanza separately, and a copy of the password isstored for each stanza. When the password expires, a new password isgenerated for the stanza that connects the first client-server contact.All subsequent attempts to connect via other server stanzas will fail,because there is no logical link between their copies of the old password


|

||

||||

|||||||||||

and the updated copy generated by the first stanza used after passwordexpiration.To avoid the problem, update the passwords before they expire, to solvethe problem if the passwords have expired, proceed as follows:1. dsmadmc and update the password on the server.2. Run dsmc -servername=stanza1 and use the new password to generate

a proper entry.3. Run dsmc -servername=stanza2 and use the new password to generate

the proper entry.

EXAMPLE 1: Use of Alternate/Parallel Paths for IncreasedAvailability

Assume the following configuration:Tivoli Storage Manager server with:– 2 tape drives– 2 LAN connections:

Fast Ethernet (TCP/IP address yyy.yyy.yyy.yyy)Token Ring (TCP/IP address xxx.xxx.xxx.xxx)

mySAP.com database server connected to Token Ring and Ethernet.

A backup is normally performed using the Ethernet LAN (SERVER statement 1). Ifthe Ethernet is down, the backup should be performed using the Token Ringconnection (SERVER statement 2), although data transfer will take longer.

The definitions in the Data Protection for mySAP.com profile could be as shown inthe example below.

If path 1 is active, Data Protection for mySAP.com will start the 2 sessions asdefined in the SERVER statement for path 1. Since MAX_SESSIONS is also 2, nomore sessions will be started.

If path 1 is inactive, Data Protection for mySAP.com will start 2 sessions on path 2.Since this equals the MAX_SESSIONS definition as well, backup will be executedusing path 2.

Appendix E. Backup Paths and Servers 111

||||

|

||

||

Data Protection for mySAP.com profile. Example 1

MAX_SESSIONS 2 # 2 tape drives..SERVER server_a # via Fast ethernet

ADSMNODE C21SESSIONS 2PASSWORDREQUIRED YESBRBACKUPMGTCLASS mdbBRARCHIVEMGTCLASS mlog1 mlog2

# USE_AT 0 1 2 3 4 5 6

SERVER server_b # via Token RingADSMNODE C21SESSIONS 2PASSWORDREQUIRED YESBRBACKUPMGTCLASS mdbBRARCHIVEMGTCLASS mlog1 mlog2

# USE_AT 0 1 2 3 4 5 6


EXAMPLE 2: Use of Alternate/Parallel Paths for IncreasedPerformance

Assume the following configuration:Two Tivoli Storage Manager servers with connections to two FDDI networks:

– server_a, TCP/IP address xxx.xxx.xxx.xxx– server_b, TCP/IP address yyy.yyy.yyy.yyy– Each of these servers has:

- two tape drivesAn mySAP.com database server connected to two FDDI networks.

Backups are done on both systems every day.



MAX_SESSIONS 4 # 4 tape drives..SERVER server_a # via FDDI

ADSMNODE C21SESSIONS 2PASSWORDREQUIRED YESBRBACKUPMGTCLASS MDBBRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4

# USE_AT 1 2 3 4 5 6 7

SERVER server_b # via FDDIADSMNODE C21SESSIONS 2PASSWORDREQUIRED YESBRBACKUPMGTCLASS MDBBRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4

# USE_AT 1 2 3 4 5 6 7

Appendix E. Backup Paths and Servers 113

EXAMPLE 3: Use of Alternate/Parallel Servers for DisasterRecovery

Assume the following configuration:Two Tivoli Storage Manager servers with connections to an FDDI network:– server_a, TCP/IP address xxx.xxx.xxx.xxx– server_b, TCP/IP address yyy.yyy.yyy.yyyEach of these servers with:– four tape drives (MAX_SESSIONS 4).An mySAP.com database server connected to this FDDI network.

Normal backups are to be performed with server a, which is local to themySAP.com database server. Every Friday a disaster recovery backup should bestored on a remote Tivoli Storage Manager server (server b).



MAX_SESSIONS 4 # 4 tape drives..SERVER server_a # via FDDI

ADSMNODE C21SESSIONS 4PASSWORDREQUIRED YESBRBACKUPMGTCLASS MDBBRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4USE_AT 1 2 3 4

SERVER server_b # via FDDIADSMNODE C21SESSIONS 4PASSWORDREQUIRED YESBRBACKUPMGTCLASS MDBBRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4USE_AT 5 # for Disaster Recovery


Appendix F. The Data Protection for mySAP.com Profile

This section describes the Data Protection for mySAP.com profile, which is used tocustomize the way Data Protection for mySAP.com operates. A sample profileinitSID.utl is provided on the installation medium. The installation procedure forUNIX copies and renames the file to $ORACLE_HOME/dbs/init$ORACLE_SID.utl,where $ORACLE_HOME is the Oracle home directory and $ORACLE_SID is theOracle System ID, for example, /oracle/<SID>/dbs/init<SID>.utl. The setup forWindows puts all files in an initial setup sub-directory (the default is C:\ProgramFiles\Tivoli\TDP4SAP for Tivoli Storage Manager). The sample profile is foundthere. Data Protection for mySAP.com reads the profile before it executes.

The following rules apply to the syntax:v Each line is analyzed separately.v Keywords can start in any column of the line.v Keywords must not be preceded by any string, except blanks.v If a keyword is encountered several times, the last one is used.v File processing ends when the END keyword is encountered or the end of file is

reached.v All keywords must be in upper case.v The comment symbol is #. Scanning of the current line stops when the comment

symbol is encountered. No comment is allowed between the keyword and thevalue(s). For example:

#BRARCHIVEMGTCLASS MLOG1 <-- correctBRARCHIVEMGTCLASS MLOG1 # <-- correctBRARCHIVEMGTCLASS # MLOG1 <-- WRONG

A few keywords are required in any case, but most are optional. Each of theoptional keywords has a preset default value.

Keyword ReferenceThe following profile keywords are obsolete for Data Protection for mySAP.comversion 3.1 and higher:v ADSMBUFFSIZEv BACKAGENTv DISKBUFFSIZEv PERF_MONITORv RETRYv TCPWAITv TRACEMAX

ADSMNODE ORACLE_sidIf specified, ORACLE_sid must be registered to the Tivoli Storage Managerserver as a Tivoli Storage Manager node. With this option you can assign adifferent node name to your database system. It should be used if youhave several mySAP.com Oracle database systems in your network withthe same name, for example, <SID>, and they all use the same TivoliStorage Manager server.


Keep in MindThis parameter must be defined in conjunction with the respectiveSERVER statement, as shown in the sample profile.

BACKEND pgmname [parameterlist ...]Specifies a program pgmname that is called by Data Protection formySAP.com after the backup function has completed and before programcontrol is returned to the SAP backup utility.

pgmname is either a fully qualified file name or simply a file name. In thelatter case the default search path is used to find the program.

If not specified, no backend processing is done.

Example (for UNIX):BACKEND write operator@remotesite R3 Backup is completed.

This sends a message to a remote user when the backup has finished.

BACKUPIDPREFIX 6charstring SAP___Specifies a 6-character prefix that is used to build a backup identifier foreach archived object. The total length of the backup ID is 16 characters.

BATCH YES|NOSpecify NO if Data Protection for mySAP.com is running with an operatorstanding by.

Specify YES if Data Protection for mySAP.com is running in unattendedmode. In this mode Data Protection for mySAP.com terminates the run ifoperator intervention is required.

The default for the BATCH parameter is YES for the backup run and NOfor the restore run if the BATCH parameter is not present or is commentedout in the Data Protection for mySAP.com profile.

This parameter has no effect if an RMAN backup/restore is started.

BRARCHIVEMGTCLASS management_class [management_class...]Specifies the Tivoli Storage Manager management class(es) Data Protectionfor mySAP.com uses when called from BRARCHIVE. Each parameterstring can consist of up to 30 characters.

NoteThe number of different BRARCHIVE management classes specifiedmust be larger or equal than the number of redo log copies specified(parameter REDOLOG_COPIES).


For more detailed information about implementing and usingBRARCHIVEMGTCLASS see Appendix K, “Tips and Hints forBRARCHIVE”, on page 139.


||


BRBACKUPMGTCLASS management_class [management_class...]Specifies the Tivoli Storage Manager management class(es) Data Protectionfor mySAP.com uses when called using BRBACKUP. The parameter stringcan consist of up to 30 characters.


BUFFSIZE n|131072This parameter specifies the block size for the buffers passed to the TivoliStorage Manager API functions. The valid range is from 4096 to 262144.Inappropriate values will be adjusted automatically.

If not specified, the default value is 131072 (128 KB) for UNIX systems and32768 (32 KB) for Windows systems. In most cases, this parameter has littleinfluence on performance.

COMPR_INFO pathSpecifies the file where Data Protection for mySAP.com stores informationabout the compressed size of files. path specifies the full path and the nameof the file.

When multiplexing is used, Data Protection for mySAP.com attempts toput files of the same size in one multiplexing stream to optimizeperformance.If RL_COMPRESSION is used in addition to multiplexing, the file size ofthe compressed files can vary strongly from the original file size. DataProtection for mySAP.com can collect information about the compressedfile size and use it for further file sorting. This information is stored in thefile specified by the COMPR_INFO parameter.When the parameter RL_COMPRESSION is set to NO, this parameter hasno effect.The info file will be written after each backup and the information will beused by the following backups. If there is no information about a filebecause of a database extension, the uncompressed file size is used for filesorting.

CONFIG_FILE pathSpecifies the configuration file for Data Protection for mySAP.com to storeall variable parameters such as passwords, date of last password change,and the current version number. path specifies the full path and the nameof the file.

This parameter is required.

END Specifies the end of the parameter definitions. Data Protection formySAP.com stops searching the file for keywords when END isencountered.

EXITONERROR YES|NO|NUMBERThis keyword specifies whether or not Data Protection for mySAP.com

Appendix F. The Data Protection for mySAP.com Profile 117

||||

||||||||||||||

exits on a backup or restore error during a BRBACKUP/BRRESTORE run.NO means don’t exit if an error occurs. YES means exit if one file can’t bebacked up. If a number is specified as an argument, Data Protection formySAP.com counts the number of errors (not warnings or retries) and exitsafter the specified number of errors.

This keyword works only for the BRBACKUP/BRRESTORE runs.BRARCHIVE and RMAN runs always exit after the first error.

This parameter is ignored if the BATCH parameter is set to NO.

FILE_RETRIES n|3This parameter specifies the number of retries when a file could not besaved or restored. If not specified, the default is FILE_RETRIES 3.


FRONTEND pgmnameSpecifies a program pgmname that is called by Data Protection formySAP.com in a backup run before the connection to the Tivoli StorageManager server is established. pgmname is either a fully qualified file nameor simply a file name. In the latter case the default search path is used tofind the program.

If not specified, no front-end processing is done.

Example (for UNIX):FRONTEND write operator@remotesite R3 Backup is starting.

This sends a message to a remote user before backup begins.

LOG_SERVER servername [verbosity]servername specifies the name of the Tivoli Storage Manager server to sendlog messages to. The name must match one of the servers listed in aSERVER statement. This parameter must be specified.

verbosity may be any one of the following: ERROR, WARNING, orDETAIL. This value determines which messages are sent. The default valueis WARNING, which means that error and warning messages are sent.ERROR sends only error messages. DETAIL sends all message types(errors, warnings, and informational messages).

Note that this feature is available only with Tivoli Storage Manager clientand server Version 3 or higher. If there is no LOG_SERVER statement inthe profile, log messages are not sent to any of the Tivoli Storage Managerservers.

MAX_SESSIONS n|1Specifies the total number of parallel Tivoli Storage Manager client sessionsthat Data Protection for mySAP.com establishes. For a directbackup/restore on tape drives, keep the following in mind: the number ofsessions must be less than or equal to the number of tape drives availablefor the backup. For performance reasons, it is recommended that you useas many parallel sessions as tape drives are available.

Note: Make sure that the mountlimit (mountl) parameter in the deviceclass is set to the number of available tape drives.

If not specified, the default is MAX_SESSIONS 1.


For more detailed information about implementing and usingMAX_SESSIONS see Appendix K, “Tips and Hints for BRARCHIVE”, onpage 139.

Keep in MindThe MAX_SESSIONS value must be less than or equal to the sum ofthe SESSIONS values specified in the SERVER statement(s).

MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS,MAX_RESTORE_SESSIONS

These parameters have the same function as the MAX_SESSIONSparameter, but they are more specific. They define the number of parallelsessions used for the BRARCHIVE, BRBACKUP and BRRESTOREfunctions. If MAX_SESSIONS is specified with one or more of theseparameters, the more specific parameters overwrite the MAX_SESSIONSparameter. You must specify them all if you don’t specify theMAX_SESSIONS parameter.

MAX_VERSIONS n|0n defines the maximum number of database backup versions to be kept inbackup storage. The default setting for this value is 0, meaning thatversioning is disabled.

Be aware that if you are using versioning, you use the same initSID.bkifile for BRBACKUP and BRARCHIVE, to avoid an unexpected loss of data.

MULTIPLEXING n|1Specifies the number of files which are multiplexed into one data stream.The allowed range is from 1 to 8. The optimal value depends strongly onthe actual hardware environment. Simply speaking, multiplexing makessense when fast tapes and fast networks are available, when the databasefiles are highly compressible and the CPU load is not too high. Optimalvalues can be expected in the range from 1 to 4.

If not specified, the default value of 1 means ’no multiplexing’.


PASSWORDREQUIRED NO|YESSpecifies if Tivoli Storage Manager requires a password to be supplied bythe Tivoli Storage Manager client. This depends on the Tivoli StorageManager installation. For more information see the Tivoli Storage Manageradministrators manuals.

If not specified the default is PASSWORDREQUIRED YES.


REDOLOG_COPIES n|1Specifies the number of copies Data Protection for mySAP.com stores foreach processed Oracle redo log.

If not specified, Data Protection for mySAP.com stores only one copy of theredo logs.


||

NoteThe number of different BRARCHIVE management classes (keywordBRARCHIVEMGTCLASS) specified must be greater than or equal tothe number of redo log copies specified.

This keyword has no effect if an RMAN backup/restore is started.

For more detailed information about implementing and usingREDOLOG_COPIES see Appendix K, “Tips and Hints for BRARCHIVE”,on page 139.

REPORT NO|YES|2If set to YES, Data Protection for mySAP.com produces some additionalinformation, for example, transferred files.

If set to 2, Data Protection for mySAP.com generates an additionalsummary report containing detailed backup/restore performance statistics.This summary is displayed at the end of the whole run. The output is sentto stdout, which is normally the console.

If not specified, the default is REPORT NO.

This keyword has no effect if an RMAN backup/restore is started.

RL_COMPRESSION NO|YESIf set to YES, Data Protection for mySAP.com performs a null blockcompression of the data before they are sent over the network. AlthoughRL compression introduces additional CPU load, throughput can beimproved when the network is the bottleneck. It is not recommended touse RL compression together with the Tivoli Storage Manager APIcompression.

If not specified, the default value is NO meaning null block compression isnot performed.

NoteRL_COMPRESSION will only be performed if a full database backup(BRBACKUP) was started. The offline log files (BRARCHIVE) will notbe compressed.

SERVER servernameDenotes the name of the Tivoli Storage Manager server to which a pathwith the subsequent definitions will be established. For alternate paths,each path must have its own (logical) server name, even if they refer toone and the same real server (same TCP/IP address for all server names).For alternate servers, there must be different TCP/IP addresses for each ofthe different (real) Tivoli Storage Manager servers.

SESSIONS n|1n specifies the number of parallel sessions Data Protection for mySAP.comcan start for this server.

If not specified, the default is SESSIONS 1.


|||||


SNMPTRAP hostname community levelhostname specifies the name of the machine to which the log messages areto be sent. This field must be specified.

community is the first level that filters messages. You can define your owncommunity.

level may be one of the following: ERROR, WARNING, or DETAIL. Thisvalue determines which messages are sent. ERROR sends only errormessages, WARNING sends error and warning messages, and DETAILsends all message types (errors, warnings and informational messages).The default is WARNING.

TRACE FILEIO_MIN | FILEIO_MAX | COMPR_MIN | COMPR_MAX |MUX_MIN | MUX_MAX | TSM_MIN | TSM_MAX | ASYNC_MIN |ASYNC_MAX | APPLICATION_MIN | APPLICATION_MAX | SYSCALL_MIN| SYSCALL_MAX | COMM_MIN | COMM_MAX | DEADLOCK_MIN |DEADLOCK_MAX | PROLE_MIN | PROLE_MAX | BLAPI_MIN |BLAPI_MAX | ALL | OFF

If the parameter TRACE is specified, Data Protection for mySAP.comwrites a trace to the file specified with the parameter TRACEFILE.Arguments to TRACE can be any combination of the possible componentsand levels separated by spaces.

NoteDo not use this parameter unless your Data Protection formySAP.com support asks you to. Using it can significantly degradethe performance of Data Protection for mySAP.com.

A trace will only be written if both TRACE and TRACEFILE are specified.

TRACEFILE path|Specifies the trace file for Data Protection for mySAP.com to store all traceinformation (if TRACE ON), path specifies the full path and the name offile.

Note: In an actual trace the string %BID will be replaced by the BackupID.

A trace will only be written if both TRACE and TRACEFILE are specified.

USE_AT daysSpecifies on which days this Tivoli Storage Manager server will be used.The days are numbered from 0 (Sunday) to 6 (Saturday).

If not specified, the default is to use the Tivoli Storage Manager server onall days.


|||||||||||

|||||||

|

Keep in MindThe parameter USE_AT must be defined in conjunction with therespective SERVER statement as shown in the sample profile below.The parameter has no effect on actions other than backup.

Sample Data Protection for mySAP.com Profile for UNIXThis sample profile (initSID.utl) is included in the Data Protection formySAP.com installation package. The UNIX and Windows versions are identicalexcept for small differences due to naming conventions. Therefore, only the UNIXversion is shown here.#--------------------------------------------------------------------------## Data Protection for mySAP.com(R) technology interface for ORACLE## Sample profile for Data Protection for mySAP.com(R) technology# Version 3.3 for UNIX##--------------------------------------------------------------------------## This file should be renamed to $ORACLE_HOME/dbs/init$ORACLE_SID.utl# where $ORACLE_HOME is the home directory of the Oracle database and# $ORACLE_SID is the system ID of the Oracle database.# Default is ’/oracle/C21/initC21.utl’.## See the ’Data Protection for mySAP.com(R) Technology Installation&# User’s Guide’ for a full description.## For comment symbol the character ’#’ can be used.# Everything following this character will be interpreted as comment.## Data Protection for mySAP.com(R) technology V3R3 accesses its profile# in "read only" mode only. All variable parameters like passwords, date of# last password change, current version number will be written into the file# specified with the CONFIG_FILE parameter. The passwords will be encrypted.

#--------------------------------------------------------------------------# Prefix of the ’Backup ID’ which will be used for communication with SAPDBA# and stored in the description field of the Tivoli Storage Manager archive# function.# Must be 6 characters.# Default: none.#--------------------------------------------------------------------------BACKUPIDPREFIX SID___

#--------------------------------------------------------------------------# Number of total parallel sessions to be established.# Note: this number should correspond with the number of simultaneously# available tape drives specified for the Tivoli Storage Manager server.# The valid range of MAX_SESSIONS is from 1 to 32.# Default: none.#--------------------------------------------------------------------------MAX_SESSIONS 1 # 1 Tivoli Storage Manager client session is default

#--------------------------------------------------------------------------# Number of parallel sessions to be established for the database backup.# Note: this number should correspond with the number of simultaneously# available tape drives specified for the Tivoli Storage Manager server.# The valid range of MAX_BACK_SESSIONS is from 1 to 32.# Default: none.#--------------------------------------------------------------------------#MAX_BACK_SESSIONS 1 # 1 Tivoli Storage Manager client session for backup


||||||||||||||||||||||||||||||||||||||||||||||||||||||

#--------------------------------------------------------------------------# Number of parallel sessions to be established for the archive log backup.# Note: this number should correspond with the number of simultaneously# available tape drives specified for the Tivoli Storage Manager server.# The valid range of MAX_ARCH_SESSIONS is from 1 to 32.# Default: none.#--------------------------------------------------------------------------#MAX_ARCH_SESSIONS 1 # 1 Tivoli Storage Manager client session for archive

#--------------------------------------------------------------------------# Number of parallel sessions to be established for the restore of files.# Note: this number should correspond with the number of simultaneously# available tape drives specified for the Tivoli Storage Manager server.# The valid range of MAX_RESTORE_SESSIONS is from 1 to 32.# Default: none.#--------------------------------------------------------------------------#MAX_RESTORE_SESSIONS 1 # 1 Tivoli Storage Manager client session for restore

#--------------------------------------------------------------------------# Number of backup copies of the archived redo logs.# The valid range of REDOLOG_COPIES is from 1 to 9.# Default: 1.#--------------------------------------------------------------------------#REDOLOG_COPIES 2 # 1 is default

#--------------------------------------------------------------------------# Specifies whether a null block compression of the data is to be performed# before transmission to Tivoli Storage Manager.# Although RL compression introduces additional CPU load, throughput can be# improved when the network is the bottleneck. RL compression in Data# Protection for mySAP.com(R) technology should not be used together with# Tivoli Storage Manager API compression.# Default: NO#--------------------------------------------------------------------------#RL_COMPRESSION YES # NO is default

#--------------------------------------------------------------------------# Specifies how many files are multiplexed into one data stream# to a Tivoli Storage Manager server. Multiplexing is usefull when the data# rate to a Tivoli Storage Manager server is higher (fast tapes, fast network)# than the I/O rate from a single disk.# The valid range of MULTIPLEXING is from 1 to 8.# Default: 1 (meaning no multiplexing)#--------------------------------------------------------------------------#MULTIPLEXING 3 # 1 is default

#--------------------------------------------------------------------------# Specifies the block size for disk I/O (in bytes).# The default values have been chosen from our performance experiments in# standard hardware environments.# The valid range of BUFFSIZE is from 4KB to 32MB.# Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows NT.#--------------------------------------------------------------------------BUFFSIZE 131072 # block size in bytes

#--------------------------------------------------------------------------# Name of a program to be called before the backup task is started.# Default: none.#--------------------------------------------------------------------------#FRONTEND pgmname parameterlist

#--------------------------------------------------------------------------# Name of a program to be called after the backup task is completed.


||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

# Default: none.#--------------------------------------------------------------------------#BACKEND pgmname parameterlist

#--------------------------------------------------------------------------# Maximum number of data base backup versions to be kept.# Note: Version control by Data Protection for mySAP.com(R) technology is# only activated if the R/3 release is 3.0C and higher and the parameter# MAX_VERSIONS is not 0.# The valid range of MAX_VERSIONS is from 0 to 9999.# Default: no versioning.#--------------------------------------------------------------------------#MAX_VERSIONS 4

#--------------------------------------------------------------------------# Batch processing# Default:# The default for the BATCH parameter is YES for the backup run and NO for# the restore run if the BATCH parameter is COMMENTED OUT in this profile.#--------------------------------------------------------------------------#BATCH YES # unattended automated operation#BATCH NO # manual operation

#--------------------------------------------------------------------------# Control of error situations# The valid range of EXITONERROR is from 0 to 100.# Default: NO.#--------------------------------------------------------------------------#EXITONERROR 3 # don’t exit if an error occurs

#--------------------------------------------------------------------------# Control of information for reporting purposes, e.g. messages, statistics.# Default: NO (no additional data will be reported).#--------------------------------------------------------------------------#REPORT NO # no additional messages#REPORT YES # all additional messages#REPORT 2 # all additional messages + summary

#--------------------------------------------------------------------------# Controls generation of a trace file.# Note: we recommend using the trace function only in cooperation with# the hotline.# Default: OFF.#--------------------------------------------------------------------------#TRACE OFF

#--------------------------------------------------------------------------# Specify the full path of the trace file.# Note: for an actual trace the string ’%BID’ will be replaced by# the current backupid.# (.../backint_%BID.trace changes to .../backint_SAP___9809182300.trace).# Default: none.#--------------------------------------------------------------------------#TRACEFILE /oracle/C21/dbs/backint.trace#TRACEFILE /oracle/C21/dbs/backint_%BID.trace

#--------------------------------------------------------------------------# Specify the full path of the configuration file.# file.# Default: none.#--------------------------------------------------------------------------CONFIG_FILE /oracle/C21/dbs/initSID.bki

#--------------------------------------------------------------------------


||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

# Number of times to retry saving/restoring a file in case an error occurs.# The valid range of FILE_RETRIES is from 0 to 100.# Default: 3.#--------------------------------------------------------------------------#FILE_RETRIES 3

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP.com(R) technology shall send# error/status information to a Tivoli Storage Manager server.# The servername must match one of the servers listed in a SERVER statement.# Values for verbosity can be ERROR, WARNING, or DETAIL.# Default: none.#--------------------------------------------------------------------------#LOG_SERVER servername [verbosity]#LOG_SERVER server_a ERROR

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP.com(R) technology shall send# error/status information to a network management program via SNMP traps.# Default: none.#--------------------------------------------------------------------------#SNMPTRAP Hostname community level#SNMPTRAP server_a public detail

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP.com(R) technology shall use a manual# sorting file for disk sorting.# Default: none.#--------------------------------------------------------------------------#SORT_FILE /oracle/C21/dbs/manual_sort_file

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP.com(R) technology shall use a# compressed filesize sorting file for disk sorting.# Default: none.#--------------------------------------------------------------------------#COMPR_INFO /oracle/C21/dbs/initSID.cfi

#**************************************************************************# Statement for multiple Servers and multiple Paths.# may be used multiple times (one for each server).#**************************************************************************

SERVER server_a # ServernameSESSIONS 2 # Max sessionsPASSWORDREQUIRED YES # Use a passwordADSMNODE NODE # Tivoli Storage Manager NodenameBRBACKUPMGTCLASS MDB # Mgmt-ClassesBRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes

# USE_AT 0 1 2 3 4 5 6 # Days for backup

#SERVER server_b # Servername# SESSIONS 2 # Max sessions# PASSWORDREQUIRED YES # Use a password# ADSMNODE NODE # Tivoli Storage Manager Nodename# BRBACKUPMGTCLASS MDB # Mgmt-Classes# BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes# USE_AT 0 1 2 3 4 5 6 # Days for backup

#**************************************************************************# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa# The valid range of USE_AT is from 0 to 6.# Default: all days#**************************************************************************


||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

#--------------------------------------------------------------------------# End of profile

END


|||||

Appendix G. Sample Tivoli Storage Manager Profiles (UNIX)

Client User Options File Sample (dsm.opt)************************************************************************* Tivoli Distributed Storage Manager ** ** Sample Client User Options file for AIX and SunOS *************************************************************************

SErvername server_aTapeprompt NoDOM /usr/sap /sapmnt/C21 /usr/sap/trans /oracle/C21

Client System Options File Sample (dsm.sys)************************************************************************* Tivoli Distributed Storage Manager ** ** Sample Client System Options file for AIX and SunOS *************************************************************************

SErvername server_aCOMMmethod TCPipTCPPort 1500TCPServeraddress loopbackTCPBuffsize 32TCPWindowsize 24Compression OffInclExcl /usr/lpp/tsm/bin/inclexcl.sample

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


||||||||||||||||||||||||||||||||||||

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


||||||||||||||||||||||||

Appendix H. Sample Tivoli Storage Manager Profiles(Windows)

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

Client Options Files Sample (<server>.opt)Data Protection for mySAP.com requires for each Tivoli Storage Manager server acorresponding client option file <server>.opt. All these files must reside in onedirectory, and this directory must contain a file dsm.opt whose full file name is setin the environment variable DSMI_CONFIG. The contents of this (second) dsm.optfile is ignored by Data Protection for mySAP.com.*************************************************************************** SERVER.OPT** Data Protection for mySAP.com(R) technology obtains the necessary* information about a Tivoli Storage Manager server ’server’ from a* client option file called ’<server>.opt’.* For each Tivoli Storage Manager server a corresponding client option file* is required.** Note: This file contains the client options for the Tivoli Storage Manager* server called ’server_a’.** Please see the Tivoli Storage Manager documentation for details.**************************************************************************COMMmethod TCPIPSLOWINCR NOCOMPression OFFNODEname C21TCPPort 1500TCPServeraddress xxx.xxx.xxx.xxxPASSWORDACCESS PROMPTTCPBUFFSIZE 31TCPWINDOWSIZE 32


||||||||||||||||||||

|

|||||||||||||||||||||||||

Include/Exclude List SampleThis sample include/exclude list is intended for the standard client user optionfile. The idea is to exclude files from ordinary Tivoli Storage Manager incrementalbackups that are easy to restore or that are already saved by Data Protection formySAP.com. Mainly such files are Windows system files and Oracle database files.************************************************************************** This Include-Exclude list is used for incremental backups of file* systems by the Tivoli Storage Manager command-line backup client.* Therefore the name of this file has to be set under the keyword InclExcl* in the standard Tivoli Storage Manager client user option file "dsm.opt".** Since the backup of the ORACLE database is done by* Data Protection for mySAP.com(R) technology and not by Tivoli Storage* Manager command-line backup client, the ORACLE database should be excluded* from backups by the Tivoli Storage Manager command-line backup client.** Note 1:* The environment variable DSM_CONFIG contains the full file name of* the Tivoli Storage Manager client user option file "dsm.opt".* Note 2:* This Include-Exclude is not used by Data Protection for mySAP.com(R)* technology.**************************************************************************Exclude *:\...\*.swpExclude *:\...\*.objExclude *:\...\*.csmExclude *:\...\*.dskExclude *:\...\*.bakExclude *:\...\win386.swpExclude *:\...\386spart.parExclude *:\...\pagefile.sysExclude *:\...\*.parExclude *:\...\SYSTEM32\CONFIG\*.*Exclude *:\...\SYSTEM32\CONFIG\...\*Exclude *:\IBMBIO.COMExclude *:\IBMDOS.COM**Exclude the following ORACLE database files:*Exclude *:\oracle\C21\saparch\...\*Exclude *:\oracle\C21\sapbackup\...\*Exclude *:\oracle\C21\sapreorg\...\*Exclude *:\oracle\C21\sapdata*\...\*


|

|||||||||||||||||||||||||||||||||||||||

Appendix I. Elements of Backup Schedules (UNIX)

Under UNIX, crontab starts jobs (cron.job) at predefined times. In the examplebelow crontab starts two shell scripts backup.ksh and archive.ksh, which simplyuse the SAP tools BRBACKUP and BRARCHIVE to save the data.

Crontab File Sample# --------------------------------------------------------------------------# crontab.sample:# Sample crontab file to be included in the root crontab jobs.# --------------------------------------------------------------------------# Task:# Submits backup/archive commands at regularly scheduled intervals# using two simple shell scripts containing SAP backup/archive commands.# --------------------------------------------------------------------------# ***** NOTE ***** NOTE ***** NOTE *****## This file is intended only as a model and should be# carefully tailored to the needs of the specific site.## ***** NOTE ***** NOTE ***** NOTE *****# --------------------------------------------------------------------------## Remarks on the crontab file format:## Each crontab file entry consists of a line with six fields, separated# by spaces and tabs, that contain, respectively:# o The minute (0 through 59)# o The hour (0 through 23)# o The day of the month (1 through 31)# o The month of the year (1 through 12)# o The day of the week (0 through 6 for Sunday through Saturday)# o The shell command# Each of these fields can contain the following:# o A number in the specified range# o Two numbers separated by a dash to indicate an inclusive range# o A list of numbers separated by commas# o An * (asterisk); meaning all allowed values## --------------------------------------------------------------------------## For the following examples, the system ID of the Oracle database# is assumed to be "C21" and the username "oraC21".## --------------------------------------------------------------------------# Full database backup, scheduled every Friday at 8:00 p.m.#0 20 * * 5 /usr/bin/su - oraC21 -c "/oracle/C21/sapscripts/backup/backup.ksh"## --------------------------------------------------------------------------# Save redo logs, scheduled twice a day at 11:30 a.m. and at 5:30 p.m.# Monday through Friday#30 11,17 * * 1,2,3,4,5 /usr/bin/su - oraC21 -c "/oracle/C21/sapscripts/backup\/archive.ksh"


|

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

# Remarks on the parameters of BRBACKUP:## -u system/manager Oracle username/password# -c run BRBACKUP in unattended mode# -m all backup all tablespaces# -t offline perform backup offline## The following should be configured within the SAP backup profile initC21.sap:## backup_dev_type = util_file# causes BRBACKUP to use the external program Data Protection for mySAP.com# util_par_file = initC21.utl# Data Protection for mySAP.com profile## --------------------------------COMMAND-----------------------------------brbackup -u system/manager -c -m all -t offline

Save and Delete Redo Logs Shell Script Sample#!/bin/ksh# --------------------------------------------------------------------------# archive.ksh:# Sample BRARCHIVE shell script# --------------------------------------------------------------------------# Task:# Invokes the SAP R/3 utility BRARCHIVE in order to save Oracle’s archived# redo logs (using IBM’s SAP R/3-Tivoli Storage Manager interface program,# Data Protection for mySAP.com) and deletes the redo logs from their# original location.# After completing this, the BRARCHIVE protocol is saved separately.# --------------------------------------------------------------------------# ***** NOTE ***** NOTE ***** NOTE *****## This script is intended only as a model and should be# carefully tailored to the needs of the specific site.#


# ***** NOTE ***** NOTE ***** NOTE *****# --------------------------------------------------------------------------## Remarks on the parameters of BRARCHIVE:## -u system/manager Oracle username/password# -sd save and delete archived redo logs# -c run BRARCHIVE in unattended mode# (-n number of redo logs to be saved, default is 10000,# which means all available)## The following should be configured within the SAP backup profile initC21.sap:## backup_dev_type = util_file# causes BRBACKUP to use the external program Data Protection for mySAP.com# util_par_file = initC21.utl# Data Protection for mySAP.com profile## --------------------------------COMMAND-----------------------------------brarchive -u system/manager -sd -c

Appendix I. Elements of Backup Schedules (UNIX) 133


Appendix J. Elements of Backup Schedules (Windows)

To start jobs on a Windows system at predefined times, it is necessary to have theSchedule service running. It is started with:

net start schedule

After the Schedule service is running, jobs are scheduled with the at command. Inthe following example, two jobs, backup.cmd and archive.cmd, are started. Theysimply use the SAP tools BRBACKUP and BRARCHIVE to save the data.

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

Full Offline Backup Batch File Sample@echo offrem Full Offline Backup batch file:rem ------------------------------------------------------------------------rem file name: backup.cmdrem ------------------------------------------------------------------------rem Sample BRBACKUP batch filerem ------------------------------------------------------------------------rem Task:rem Invokes the SAP R/3 utility BRBACKUP in order to perform a full offlinerem backup of all tablespaces using IBM’s SAP R/3-Tivoli Storage Managerrem interface program Data Protection for mySAP.com.rem ------------------------------------------------------------------------rem ***** NOTE ***** NOTE ***** NOTE *****rem


rem This script is intended only as a model and should berem carefully tailored to the needs of the specific site.remrem ***** NOTE ***** NOTE ***** NOTE *****rem ------------------------------------------------------------------------remrem For the following examples, the system ID of the Oracle databaserem is assumed to be "C21".remrem ------------------------------------------------------------------------remrem First, let’s do a full offline backup of the Oracle database. Thisrem includes at least files located in the following file systems:rem c:\oracle\C21\sapdata1rem c:\oracle\C21\sapdata2rem c:\oracle\C21\sapdata3rem c:\oracle\C21\sapdata4rem c:\oracle\C21\sapdata5rem c:\oracle\C21\sapdata6remrem Remarks on the parameters of BRBACKUP:remrem -u system/manager Oracle username/passwordrem -c run BRBACKUP in unattended moderem -m all backup all tablespacesrem -t offline perform backup offlineremrem The following should be configured within the SAP backup profilerem initC21.sap:remrem backup_dev_type = util_filerem causes BRBACKUP to use the external programrem Data Protection for mySAP.comrem util_par_file = %ORACLE_HOME%\database\initC21.utlrem Data Protection for mySAP.com profilerem ------------------------------COMMAND-----------------------------------brbackup -u system/manager -c -m all -t offline

Save and Delete Redo Logs Batch File Sample@echo offrem ------------------------------------------------------------------------rem file name: archive.cmdrem ------------------------------------------------------------------------rem Sample BRARCHIVE batch filerem ------------------------------------------------------------------------rem Task:rem Invokes the SAP R/3 utility BRARCHIVE in order to save Oracle’s archivedrem redo logs (using IBM’s SAP R/3-Tivoli Storage Manager interface program,rem Data Protection for mySAP.com) and deletes the redo logs from theirrem original location.rem After completing this, the BRARCHIVE protocol is saved separately.rem ------------------------------------------------------------------------rem ***** NOTE ***** NOTE ***** NOTE *****remrem This script is intended only as a model and should berem carefully tailored to the needs of the specific site.remrem ***** NOTE ***** NOTE ***** NOTE *****rem ------------------------------------------------------------------------remrem Remarks on the parameters of BRARCHIVE:remrem -u system/manager Oracle username/passwordrem -sd save and delete archived redo logsrem -c run BRARCHIVE in unattended mode


rem (-n number of redo logs to be saved,rem default is 10000,rem which means all available)remrem The following should be configured within the SAP backup profilerem initC21.sap:remrem backup_dev_type = util_filerem causes BRBACKUP to use the external programrem Data Protection for mySAP.comrem util_par_file = %ORACLE_HOME%\database\initC21.utlrem Data Protection for mySAP.com profilerem ------------------------------COMMAND-----------------------------------brarchive -u system/manager -sd -c

Appendix J. Elements of Backup Schedules (Windows) 137


Appendix K. Tips and Hints for BRARCHIVE

For a BRARCHIVE run there are two important parameters in the Data Protectionfor mySAP.com profile: BRARCHIVEMGTCLASS and REDOLOG_COPIES.v The main purpose of the BRARCHIVEMGTCLASS keyword is to provide the

capability of separating the backup media target for the redo log files from thebackup media target for the Oracle database files.

v The main purpose of the REDOLOG_COPIES keyword is to get multiple backupcopies of the redo log files (REDOLOG_COPIES > 1) on different backup mediathrough the usage of different Tivoli Storage Manager management classes.

NoteA Tivoli Storage Manager management class used by Data Protection formySAP.com defines– to which Tivoli Storage Manager storage pool the Tivoli Storage

Manager server will write the backup data (be it for redo log files orOracle database files)

– how long the Tivoli Storage Manager server will keep the backup(s) ofthose files

Be aware that Data Protection for mySAP.com always uses the archive capabilitiesof Tivoli Storage Manager (in the context of backup and restore).

By creating multiple copies, the database administrator will be able to restore andrecover an Oracle database in an SAP R/3 environment even if a database backuptape and/or a redo log backup tape gets corrupted or lost.

It is assumed that most customers have the requirement of having at least 2backup copies of each redo log file on separate physical media after the backuprun (BRARCHIVE) of the redo log files.

Some general Tivoli Storage Manager aspects about resource utilization (focus ontape drives) should be kept in mind when you implement Tivoli Storage Managerand Data Protection for mySAP.com.v One BRARCHIVE run might trigger via Data Protection for mySAP.com several

simultaneously running backup sessions.v Running several SAP R/3 databases might cause several BRBACKUPs to run

simultaneously.

If this situation had been overseen in the planning and set up stage, it may causeintermittent BRARCHIVE/BRBACKUP problems. Running more parallel sessionsthan the number of available tape drives for the various storage tape pools willcause severe performance degradation and will also abend some sessions in certainsituations. The utilization of disk storage pools (connected to tape storage) asinterim Tivoli Storage manager storage is one solution for such a tape congestionproblem (see item 2 below).

Depending on the value for MAX_SESSIONS, you can run one or more sessionssimultaneously when running a backup with Data Protection for mySAP.com. Byspecifying one or more Tivoli Storage Manager management classes in the


keyword BRBACKUPMGTCLASS or BRARCHIVEMGTCLASS you decide whichmanagement classes will be used when running the SAP BRBACKUP or the SAPBRARCHIVE. Two cases are considered. The management class itself is assumed tobe directly connected to both1. a tape storage pool (Tivoli Storage Manager)

or2. a disk storage pool (Tivoli Storage Manager) as interim storage.

In case 1, the Tivoli Storage Manager parameter MOUNTLIMIT in the DEVCLASS(Tivoli Storage Manager) being referenced by a tape storage pool (Tivoli StorageManager) determines how many tape drives can be used simultaneously by thistape storage pool, presuming that there are enough tape drives available. If there isa limitation in the number of tape drives being requested by too many parallelrunning sessions, you could consider the usage of disk storage pools for thebackup of the redo log files (case 2).

Case 2 has the advantage that several sessions can simultaneously access one diskstorage pool. There is no limitation caused by MOUNTLIMIT. Each disk storagepool is assumed to be connected to a tape storage pool. The disk storage pool canbe migrated to the appropriate tape storage pool either:v automatically by the Tivoli Storage Manager server (see HIGHMIG/LOWMIG

values)or

v at particular times using your own scripts which lower the HIGHMIG to 1 thusforcing the migration to tape.

For installations where too few tape drives are a constraint, case 2 allows you torun several BRARCHIVEs for various SAP Oracle databases simultaneously.

Depending on your Tivoli Storage Manager environment (tape drive resources) andyour requirements, you might choose to run the backup of the redo log filesv with ’brarchive -sd -c ’

orv with ’brarchive -s -c -r init<SID>.utl’

and then ’brarchive -scd -c -r init<SID>.utl2’This run sequence is only used if there is, for example, only one tape driveavailable, no disk storage pool can be used (case 2) as a temporary container,and an operator would manually exchange tape cartridges. It also causes DataProtection for mySAP.com to create different backup IDs for the twoBRARCHIVE runs. For a better alternative see example 1 on page 143.

The following assumes that the backup of the redo log files will only be done with’brarchive -sd -c’ (this means only 1 init<SID>.utl is used for 1 Oracle databaseinstance). Depending on what had been specified in the parameterMAX_SESSIONS, REDOLOG_COPIES and BRARCHIVEMGTCLASS, differentbehavior will be seen when running a BRARCHIVE.

Data Protection for mySAP.com satisfies the BRARCHIVE request to back up redolog files according to the following rules:1. Data Protection for mySAP.com produces as many backup copies of each redo

log file as are specified with the REDOLOG_COPIES value.


2. Data Protection for mySAP.com requires that, for REDOLOG_COPIES N, atleast N management classes are specified for each Tivoli Storage Managerserver (using parameter BRARCHIVEMGTCLASS).

3. When the value MAX_SESSIONS is larger than REDOLOG_COPIES, DataProtection for mySAP.com starts only N sessions where N is the nearest integermultiple of the REDOLOG_COPIES with a value either lower than, or equal tothe MAX_SESSIONS value. For example, MAX_SESSIONS 5 andREDOLOG_COPIES 2 causes only 4 sessions to be started.

4. When fewer sessions (M) are specified than the number of redo log copies (N),Data Protection for mySAP.com cannot access all BRARCHIVE managementclasses simultaneously. This means Data Protection for mySAP.com will, in thefirst round, access only the first M management classes and will store a copy ofeach file in each of the classes. In the next round(s) the remaining managementclasses will be accessed, until each management class contains one copy of allfiles.Example:A Tivoli Storage Manager environment with 1 tape drive might be a 7305 or asingle drive SCSI library as the 3590_B11. In this case, you should start only 1session (MAX_SESSIONS 1). In order to get 2 redo log copiesREDOLOG_COPIES is set to 2. Data Protection for mySAP.com would begin toback up in 1 session to the first specified management class. When all redo logshave been copied for the first time in Tivoli Storage Manager, then DataProtection for mySAP.com starts a new session and performs the backup to thesecond management class. In this way, a new tape will be used if eachmanagement class is connected to a different tape storage pool (see alsoexample 1).

5. Data Protection for mySAP.com informs its caller (BRARCHIVE) once wheneverit has successfully finished the multiple backup of any redo log file (see “Hintsfor BRARCHIVE Version 3.1G or Higher” on page 142)

6. In case of problems, Data Protection for mySAP.com retries to save the fileseveral times. Data Protection for mySAP.com terminates if a file finally cannotbe saved as often as has been specified. An indicator is set to tell BRARCHIVEwhich redo log files were not backed up. This is done to avoid any furtherworkload (unnecessary backup activities). (see “Hints for BRARCHIVE Version3.1G or Higher” on page 142)

7. Data Protection for mySAP.com is a Tivoli Storage Manager client and cannotcontrol what the Tivoli Storage Manager server is doing. When you startsession b after session a, it doesn’t necessarily mean the server will start thesessions in that order. The session you started later could begin backupprocessing earlier, while, for example, the session you started earlier is still inmedia wait. In certain situations (see example 3 below) this could mean thatanother session (even started later), working with the same management class,backs up more redo log files than the one that remained in a media wait statuslonger.

CautionTo avoid an unexpected loss of data, be aware that if you are usingVERSIONING you use the same initSID.bki file for BRBACKUP andBRARCHIVE.

Appendix K. Tips and Hints for BRARCHIVE 141

Keep in mind that BRARCHIVE informs Data Protection for mySAP.com via a list,which files (redo log files) are to be backed up. Also keep in mind that the order ofthe redo log file names determines the subsequent delete behavior of newerBRARCHIVE releases.

Hints for BRARCHIVE Version 3.1G or HigherAs versions 3.1G and 3.1H of SAP BRARCHIVE behave differently from previousversions, in that they now allow the saparch directory to be cleaned-up as soon aspossible,v BRARCHIVE does not wait until all redo log files have been backed-up before

starting to delete them. Whenever it receives notification from Data Protectionfor mySAP.com about a successful completion of a backup of a redo log file,BRARCHIVE will delete this redo log file immediately (with the option -sd or-scd) if the backup of all other preceding redo log files in the supplied list alsohad been successfully performed. If, for any reason, the backup for some redolog files could not be completed in sequence, BRARCHIVE will postpone thedeletion until the backup of the preceding redo log files has been signaled byData Protection for mySAP.com as completed.

v At the end of the backup of the redo log files, if one of the redo log files has notbeen successfully backed up, BRARCHIVE will not delete all the following redolog files even if they have all been successfully backed up. If BRARCHIVE isrestarted later it will start with the backup of the failed redo log file and willredo the backup of all successive files, which have already been successfullybacked up.In order to avoid an unnecessary workload on the SAP Oracle databasemachine, Data Protection for mySAP.com will stop the backups in a sessionwhenever a temporarily unrecoverable situation has occurred during a backup.

Note

1. At setup time, you must ensure that sessions will not be started unlessenough tape drives are available. Otherwise you may encounter thefollowing problems:v many unwanted tape mounts, thus creating long BRARCHIVE runs andv under certain circumstances, an unsuccessful termination of the

BRARCHIVE (or other BRBACKUP) runv in the case of an unsuccessful termination, successfully backed up redo

log files would have to be backed up again (see the above hint for SAPBRARCHIVE 3.1G/3.1H)

2. Specifying arbitrary values for MAX_SESSIONS and REDOLOG_COPIESand an arbitrary number of management classes can produce unfavorablerun behavior in the Tivoli Storage Manager server specially when tapemedia is directly used (case 1).For example: If there are only 2 tape drives available, MAX_SESSIONS 3,REDOLOG_COPIES 1, BRARCHIVEMGTCLASS mgmt1 mgmt2 wouldprobably cause many unwanted tape mounts.

Examples Using MAX_SESSIONS and REDOLOG_COPIESThe following four examples should help to clarify the usage of MAX_SESSIONSand REDOLOG_COPIES:


1. MAX_SESSIONS 1, REDOLOG_COPIES 2. Two differentBRARCHIVEMGTCLASS management classes.Only one Data Protection for mySAP.com agent (session) will be started. Allfiles are sent to the first archive management class. After this is done, all filesare sent to the second archive management class. This means the first copy isstored on tape one, the second copy is stored on tape two (assuming differenttape storage pools are connected to the two archive management classes).

2. MAX_SESSIONS 2, REDOLOG_COPIES 2. Two differentBRARCHIVEMGTCLASS management classes.In this case, two sessions will be started. The first session sends all files to thefirst archive management class, the second session backs up all files to thesecond archive management class. Both sessions run parallel and independentlyof each other. Presuming that two tape drives are available, two tapes will bewritten, each containing a complete backup set of files (redolog copies).

3. MAX_SESSIONS 4, REDOLOG_COPIES 2. Two differentBRARCHIVEMGTCLASS management classes.In this case, four sessions will be started. Sessions one and three access the firstarchive management class. They both send the first copy of each file to this firstmanagement class. Similarly, sessions two and four access the second archivemanagement class and store the second copy of each file on the secondmanagement class.This scenario makes sense, when at least four tape drives are available, becauseonly then the four sessions can run in parallel. In this case, four tapes will bewritten. Tapes one and three contain the first copy of all files and tapes twoand four contain the second copy of all files.If only two tape drives are available, you should set up archive managementclasses on disk pools instead of tape pools, because then the four sessions canrun in parallel. After the files have been stored on disk, they can be migrated inan independent step from the two disk pools to two tapes.

4. MAX_SESSIONS 4, REDOLOG_COPIES 4. Four differentBRARCHIVEMGTCLASS management classes.This is a very unlikely example for a real production environment. Here, DataProtection for mySAP.com will produce four backup copies of each redo logfile.Again, four sessions will be started. Session one accesses the first archivemanagement class, session two accesses the second archive management classand so on. As in case three, at least four tape drives must be available. If not,four different disk storage pools connected to four different tape storage poolsare needed in order to get the four copies of one redo log file to four differenttapes.

Appendix K. Tips and Hints for BRARCHIVE 143


Glossary

AActivate. The process of validating the contents of apolicy set and copying the policy set to the ACTIVEpolicy set.

Active policy set. The policy set that contains thepolicy rules currently in use by all client nodesassigned to the policy domain. The active policy set isthe policy set that was most recently activated for thepolicy domain.

Administration Assistant. A Web browser basedgraphical interface to support and assist thecustomizing of Data Protection for mySAP.com (SystemConfiguration) and the analyzing of mySAP.comdatabase backup and restore operations (OperationsMonitor, Performance Monitor).

Administrative client. In Tivoli Storage Manager, aprogram that runs on a file server, workstation, ormainframe that allows administrators to control andmonitor the Tivoli Storage Manager server throughadministrator commands. Compare withbackup-archive client.

Archive copy group. A policy object containingattributes that control the generation, destination, andexpiration of archive files. An archive copy groupbelongs to a management class.

BBackup-archive client. A program that runs on aworkstation or file server and provides a means forusers to back up, archive, restore, and retrieve files.Compare with administrative client.

Backup copy group. A policy object containingattributes that control the generation, destination, andexpiration of backup files. A backup copy groupbelongs to a management class.

Backup Object Manager. A utility for querying,creating, restoring, and deleting backup objects onTSM.

BRARCHIVE. An SAP database utility to performbackups of offline redo log files in an mySAP.comOracle database environment.

BRBACKUP. An SAP database utility to doonline/offline backups of mySAP.com Oracle databases.BRBACKUP can be used to back up data files, controlfiles and online redo log files.

BRCONNECT. This ensures, that the database statusrequired for the online/offline backup of anmySAP.com Oracle database remains unchanged duringthe backup. BRCONNECT will be started onlyinternally by BRBACKUP/BRARCHIVE.

BRRESTORE. An SAP database utility to restore anentire Oracle database backup or parts of it, previouslybacked up with BRBACKUP or BRARCHIVE. Anynon-database files and directories which were savedcan also be restored. Subdirectories within the sapdatadirectories will be created automatically, whennecessary.

CClient options file. A file that a client can change,containing a set of processing options that identify theserver, communication method, and options for backup,archive, hierarchical storage management, andscheduling. It is also called dsm.opt file.

Client system options file. A file, used on UNIXclients, containing a set of processing options thatidentify the Tivoli Storage Manager servers to becontacted for services. This file also specifiescommunication methods and options for backup,archive, hierarchical storage management, andscheduling. It is also called dsm.sys file.

Control file. A file associated with a database thatmaintains the physical structure and time stamps of allfiles within that database. The control file is updatedcontinuously during database use and must beavailable for writing, if the database is mounted oropened.

Copy group. A policy object that contains attributesthat control the generation, destination, and expirationof backup and archive files. There are two kinds ofcopy groups: backup and archive. Copy groups belongto management classes.

DData block. The smallest unit of a database

Data file. A data file is a physical operating systemfile on disk, which contains data structures of adatabase, such as tables and indexes. A data file onlybelongs to one database and to one tablespace.

Device class. A named group of storage devices withcommon characteristics. Each device class has a uniquename and represents a device type of disk, file, opticaldisk, or tape.


|||

DISK. A device class that is defined by Tivoli StorageManager at installation. It is used to categorize diskdrives, such as internal disk drives.

FFile space. A logical space in a client’s storage thatcan contain a group of files. Clients can restore,retrieve, or delete their file spaces from Tivoli StorageManager server storage. Tivoli Storage Manager doesnot necessarily store all the files from a single file spacetogether, but can identify all the files in server storagethat came from a single file space.

IInclude/exclude list. A group of include and excludeoption statements in a file. Tivoli Storage Manager usesthe statements to determine whether to back up ormigrate certain files, and to determine the associatedmanagement classes to use for backup, archive, andspace management. The exclude options identify filesthat should not be backed up or migrated off the clientnode. The include options identify files that are exemptfrom the exclusion rules, or assign a management classto a file or group of files for backup, archive, or spacemanagement services. The include/exclude list isdefined either in an include/exclude file (for UNIXclients) or in the client options file (for other clients).

MManagement class. A policy object that users can bindto each file to specify how the server manages the file.The management class can contain a backup copygroup, an archive copy group, and space managementattributes. The copy groups determine how the TivoliStorage Manager server manages backup versions orarchive copies of files. The space managementattributes determine whether files are eligible formigration from space manager client nodes to TivoliStorage Manager storage, and under what conditions.

Media Management API. An interface provided byOracle to which vendors are able to write compatiblesoftware libraries. This software integrates with Oracle.Thus, an Oracle server process is able to issuecommands to the media manager to write backup filesout to sequential storage (e.g., Tivoli Storage Manager)and read files from sequential storage.

NNode. A unique name used to identify aserver/workstation (client) to the Tivoli StorageManager server.

OOffline redo log. If the database is in ARCHIVELOGmode and an online redo log is filled, it is copied toone (or more) archive log destination(s), which istypically the saparch directory in an mySAP.comenvironment. This copy is the offline redo log (alsocalled archived redo log).

Online redo log. The online redo log is a set of two ormore files which record all changes made to Oracledata files and control files.

PPolicy domain. A policy object that contains policysets, management classes, and copy groups that areused by a group of client nodes.

Policy set. A policy object that contains a group ofmanagement class definitions that exist for a policydomain. At any one time there can be many policy setswithin a policy domain but only one policy set can beactive.

RRecovery Manager (RMAN). A tool used to back up,restore and recover Oracle databases. It can be usedwith or without a Recovery Catalog,. If a RecoveryCatalog is not used, Recovery Manager decides how toback up, restore and recover the database using thecontrol file of the database. Incremental backups ofOracle databases can only be done with RMAN.

Retention. The amount of time, in days, that inactivebacked up or archived files are kept in the storage poolbefore they are deleted. Copy group attributes anddefault retention grace periods for the domain defineretention.

SSAP BACKINT interface. An interface provided bySAP database utilities BRBACKUP, BRARCHIVE andBRRESTORE that can be used to access external backupprograms, for example Data Protection for mySAP.com.

SAPDBA. An SAP database tool to provide andsimplify the administration of an Oracle databasesystem within an mySAP.com environment. SAPDBAprovides a collection of databasemanagement/administration functions, for exampletablespace administration, which can only performedoutside of an mySAP.com system.

Scratch volume. A volume that is available for TivoliStorage Manager use. The volume is either labeled, orblank or contains no valid data, and is not defined toTivoli Storage Manager.


Storage pool. A storage pool is a named collection ofstorage volumes that are associated with one deviceclass. Each storage pool represents a collection ofvolumes that are the same media type. For example, astorage pool that is associated with a device class for8 mm tape contains only 8 mm tape volumes.

TTablespace. A database is divided into one or morelogical storage units, which are tablespaces. Eachtablespace has a set of data files exclusively associatedwith it.

Data Protection for mySAP.com File Manager. Autility that simplifies the Data Protection formySAP.com inquire, restore and delete operations. Itcan be seen as an add-on to Data Protection formySAP.com.

Tivoli Storage Manager. A client/server program thatprovides storage management to customers in amultivendor computer environment.

Tivoli Storage Manager API. A set of functions thatapplications running on a client platform can call tostore, query, and retrieve objects from Tivoli StorageManager storage.

Uutil_file_online. A (data file) backup using an externalbackup program addressed by the BACKINT interface.If an online backup is running, the backup status is setand completed dynamically for the tablespaces beingbacked up. In this way, the volume of offline redo logfiles during an online backup can be reducedsignificantly.

VValidate. The process of ensuring that the activepolicy set contains a default management class andreports on copy group definition errors.

Volume. The basic unit of storage for the TivoliStorage Manager database, recovery log, and storagepools. A volume can be an LVM logical volume, astandard file system file, a tape cartridge, or an opticalcartridge. Each volume is identified by a uniquevolume identifier. See database volume, scratchvolume, and storage pool volume.

Glossary 147


Index

Aactivate

glossary definition 145active policy set

glossary definition 145Administration Assistant

authorizing users 71glossary definition 145initial log-on 70installing 65installing server 65installing slave server 69Java 64Netscape 70overview 63prerequisites 64specifying destination directory 68specifying host name 67specifying server ports 66usage of 71verifying the installation 70Web browser, remote method

invocation 64Administration Assistant Server 69administrative client

glossary definition 145ADSMBUFFSIZE 115ADSMNODE profile keyword 115alternate/parallel backup paths 6

example for availability 111example for disaster recovery 114example for performance 113reasons to use 109

alternate/parallel backup servers 7archive copy group

glossary definition 145authorizing Administration Assistant

users 71automatic password handling 26automating backup and archive

operations 49automation, backup 45availability improvements

with alternate/parallel paths andservers 109

BBACKAGENT 115BACKEND profile keyword 8, 116backing up

AIX system data 45Oracle database elements 45SAP system data 48user data 48

BACKINT 2, 31backup 35

automated 49BRBACKUP 35messages 37

backup (continued)online/offline 36profile & protocol file directories,

UNIX 48profile & protocol file directories,

Windows 48profiles 47protocols 47SAPDBA 35scenarios 36strategy for operating system 45tablespace 37

backup and restore, parallel 4backup automation

planning 45backup by version 5backup copy group

glossary definition 145backup function 31

Tivoli Storage Managerincremental 48

backup library 2Backup Object Manager

glossary definition 145backup paths

alternate/parallel 6profile examples 109

backup schedulerSAP 49Tivoli Storage Manager 50UNIX crontab / Windows

scheduler 50backup servers

alternate/parallel 7performance optimization 60profile examples 109

backup sessions 139backup strategy

planning 45backup-archive client

glossary definition 145backup, examples 51backup, incremental 3, 7, 99backup/restore

general 31Backup/Restore, performance

optimization 53compression 57multiplexing 57mySAP.com Oracle database

backup 57null block compression 57parallelism 57

BACKUPIDPREFIX profile keyword 25,116

BATCH profile keyword 116BRARCHIVE 31, 57

glossary definition 145BRARCHIVEMGTCLASS profile

keyword 4, 25, 116BRBACKUP 31, 57

BRBACKUP (continued)backup of Oracle database 36glossary definition 145

BRBACKUPMGTCLASS profilekeyword 4, 25, 117

BRCONNECTglossary definition 145

BRRESTORE 31glossary definition 145

BUFFSIZE profile keyword 117

Cclient

performance optimization 55client options file

glossary definition 145client system options file

glossary definition 145UNIX example 127Windows example 129

client user options fileUNIX example 127

client/server connection paths 109cloning SAP R/3 system 73COMPR_INFO profile keyword 117compressing data

null block 57Tivoli Storage Manager 57

compression 55, 57CONFIG_FILE profile keyword 25, 117configuration file 23configuration matrix for Tivoli Storage

Manager password settings 106control file

glossary definition 145control files, Oracle database 36copies of redo logs 5copy group

glossary definition 145crontab

scheduling backups with 50crontab file (UNIX)

example 131customization

Administration Assistant 63customizing Data Protection for

mySAP.comusing the configuration tool 64with the configuration file 4with the profile 3

Ddaily backups 51data block

glossary definition 145data compression

hardware vs. software 17, 18null block 57


data compression (continued)Tivoli Storage Manager 57

data fileglossary definition 145

data files, Oracle database 36Data Protection for mySAP.com

architecture and properties 1BACKINT 1backup library 1components 1database utilities 1installation

prerequisites 19installation and setup 19introduction 1Oracle recovery manager 1overview 1profile

keyword descriptions 115keyword rules 115sample 122

setupprerequisites 19

Data Protection for mySAP.comconfiguration tool 64

Data Protection for mySAP.com filemanager

glossary definition 147Data Protection for mySAP.com File

Managererror messages 98

Data Protection for mySAP.commessages 81

Data Protection for mySAP.commonitoring tool 64

Data Protection for mySAP.com,migration 103

data spacesbacking up 46

database serverbackup processes 55

defining a backup strategy 45deinstalling

Data Protection for mySAP.com 19device class

glossary definition 145disaster recovery

with alternate/parallel paths andservers 109

DISKglossary definition 146

DISKBUFFSIZE 115

EEND profile keyword 117error log file 23error messages 82

Data Protection for mySAP.com FileManager 98

examplesalternate/parallel paths for

availability 111alternate/parallel paths for disaster

recovery 114alternate/parallel paths for increased

performance 113

examples (continued)client system options file (UNIX) 127client system options file

(Windows) 129client user options file (UNIX) 127client user options file

(Windows) 129crontab file (UNIX) 131full offline batch backup

(Windows) 135include/exclude list (UNIX) 127include/exclude list (Windows) 130offline backup shell script

(UNIX) 132saving and deleting redo logs

(UNIX) 132saving and deleting redo logs

(Windows) 136scheduled batch backup

(Windows) 135scheduling backup jobs (UNIX) 131scheduling backup jobs

(Windows) 135specifying MAX_SESSIONS and

REDOLOG_COPIES 142Tivoli Storage Manager profiles for

UNIX 127Tivoli Storage Manager profiles for

Windows 129EXITONERROR profile keyword 117

FFile Manager 33

error messages 98function keys 34inquire, restore, delete functions 33

file sorting, manual 8File space

glossary definition 146FILE_RETRIES profile keyword 118files

backup 48log 48protocol 48

files, backup protocol/profileprofile & protocol file directories 48

files, Oracle database 36FRONTEND profile keyword 8, 118full offline batch backup

Windows example 135

Hhandling Tivoli Storage Manager

passwords 105hardware compression 17, 18

compared with Tivoli StorageManager client softwarecompression 17, 18

Iinclude/exclude list

glossary definition 146UNIX example 127

include/exclude list (continued)Windows example 130

incremental backup 3, 7, 99incremental backup function of Tivoli

Storage Manager 48individual tablespace locking 5inquire function 32

BRRESTORE 32SAPDBA 32

installingAdministration Assistant 65Administration Assistant server 65Administration Assistant slave

server 69Administration Assistant, installation

verification 70Administration Assistant,

prerequisites 64installing Data Protection for

mySAP.com 19, 20on Windows 22verifying installation 27

JJava

prerequisite for AdministrationAssistant 64

JDKprerequisite for Administration

Assistant installation 65JRE

prerequisite for AdministrationAssistant installation 65

Kkeywords

ADSMNODE 115BACKEND 8, 116BACKUPIDPREFIX 25, 116BATCH 116BRARCHIVEMGTCLASS 4, 5, 25,

116, 139BRBACKUPMGTCLASS 4, 25, 117BUFFSIZE 117COMPR_INFO 117CONFIG_FILE 25, 117END 117EXITONERROR 117FILE_RETRIES 118FRONTEND 8, 118LOG_SERVER 8, 118MAX_ARCH_SESSIONS 119MAX_BACK_SESSIONS 119MAX_RESTORE_SESSIONS 119MAX_SESSIONS 25, 118, 139MAX_VERSIONS 25, 119MULTIPLEXING 57, 119obsolete 115PASSWORDREQUIRED 119REDOLOG_COPIES 5, 119, 139REPORT 8, 120RL_COMPRESSION 57, 120SERVER 26, 120SESSIONS 26, 120


keywords (continued)SNMPTRAP 121syntax for all keywords 115TRACE 121TRACEFILE 121USE_AT 121

Llibrary, backup 2locking

individual tablespace 5log files

creating multiple copies 5LOG_SERVER profile keyword 8, 118logging messages 8

Mmanagement class

glossary definition 146management classes 4

Tivoli Storage Manager serverconfiguration 14

manual password handling 26manual sorting of files 8matrix

for setting Tivoli Storage Managerpasswords 106

MAX_ARCH_SESSIONS profilekeyword 119

MAX_BACK_SESSIONS profilekeyword 119

MAX_RESTORE_SESSIONS profilekeyword 119

MAX_SESSIONS profile keyword 25,118

example 142MAX_VERSIONS profile keyword 25,

119media management API

glossary definition 146message logging 8messages

Data Protection for mySAP.com 82Data Protection for mySAP.com

FileManager 98general, Data Protection for

mySAP.com 81severity levels 82

migrationfrom Tivoli Data Protection for R/3

Version 2.7 103from Tivoli Data Protection for R/3

Version3.1 or Version 3.2 103mirroring control and redo log files in

Oracle 46monitoring Data Protection for

mySAP.com 64mount points

maximum number per node 16node parameter maxnummp 16

multi-threading 9multiple copies of redo logs 139multiple paths 59multiplexing 55, 57

MULTIPLEXING profile keyword 57,119

mySAP.com database serverperformance optimization 55

mySAP.com database utilities 19mySAP.com Oracle database,

Backup/Restore of 57mySAP.com system landscape and

backup/restore performance 53mySAP.com, backup 35

NNetscape, Administration Assistant 70network

performance optimization 59network parameters

settings 59no authentication required 105node

glossary definition 146node definition

number of mount points 15Tivoli Storage Manager server 15

node parametermaxnummp 16

null block data compression 57

Ooffline backup shell script

UNIX example 132offline redo log

glossary definition 146online redo log

glossary definition 146operating system backup

strategy 45Oracle data spaces

backing up 46Oracle database server

concepts 45Oracle database, backup 36Oracle database, files 36overview, Data Protection for

mySAP.com 1

Pparallel backup and restore

general description 4number of parallel sessions to

specify 4parallel backup paths, alternate 6parallel backup servers, alternate 7parallel backup sessions 139parallel sessions 59parallelism 57password handling 26

automatic 26generating passwords 26, 105manual 26

PASSWORDREQUIRED profilekeyword 119

passwordsTivoli Storage Manager 105

pathsalternate/backup 6

PERF_MONITOR 115performance improvement

parallelism 57settings for Data Protection for

mySAP.com 56settings for the Tivoli Storage

Manager 61with alternate/parallel paths and

servers 109with multi-threading 9

performance monitoring 64performance optimization

backup server 60backup/restore 53Backup/Restore of mySAP.com Oracle

databases 56client, data rates 55infrastructure design 53setting up environment 61settings for the Tivoli Storage

Manager 61tuning 61with data compression 57with multiplexing 57

performance problems 139planning a backup strategy 45policy definitions

Tivoli Storage Manager serverconfiguration 14

policy domainglossary definition 146

policy setglossary definition 146

ports, Administration Assistantserver 66

profileSAP backup 25

profile customization, Data Protection formySAP.com and SAPDBA 25

profile keywordssyntax 115

profilesbackup of 47backup, file directories, UNIX 48backup, file directories, Windows 48example of Tivoli Storage Manager for

UNIX 127Tivoli Storage Manager example for

Windows 129Prole 2, 70protocol

backup, file directories, UNIX 48backup, file directories, Windows 48

protocol, backupbackup of 47

Rrecovery 40

full recovery 42one tablespace 40

Recovery Manager (RMAN) 3, 99glossary definition 146

redo log files, Oracle database 36

Index 151

redo logscreating multiple copies 5deleting promptly 142

redo logs (Oracle)backing up 46

redo logs, recovery 42REDOLOG_COPIES 5REDOLOG_COPIES profile

keyword 119example 142

REPORT profile keyword 8, 120reporting backup statistics 8restore function 32

BRRESTORE 32SAPDBA 32

restore/recovery 35, 40BRRESTORE 40full recovery 42loss of several data/tablespace

files 42one tablespace 40recovery of control files 42recovery of redo log files 42SAPDBA 35

retentionglossary definition 146

RETRY 115RL_COMPRESSION profile keyword 57,

120RMAN 99

and incremental backup 99

Ssample Data Protection for mySAP.com

profile 122SAP (backup) scheduler 49SAP BACKINT interface

glossary definition 146SAP backup profile 25SAP R/3 system cloning 73saparch directory 142SAPDBA 31

database backup 37glossary definition 146protocols 47

saving and deleting redo logsUNIX example 132Windows example 136

scheduled batch backupWindows example 135

scheduling automatic backups 49scheduling backup jobs

UNIX examples 131scheduling backups

Windows examples 135scheduling function of Tivoli Storage

Manager 50scratch volume

glossary definition 146security settings

authorizing Administration Assistantusers 71

serverinstalling Administration Assistant

server 65SERVER profile keyword 26, 120

server, hostname specification 67server, port specification 66server, slave

installing Administration Assistantslave server 69

server, specifying directory 68servers

alternate/backup 7SESSIONS profile keyword 26, 120setting Tivoli Storage Manager passwords

automatically 105setting Tivoli Storage Manager passwords

manually 105setting up Data Protection for

mySAP.com 19customizing the Data Protection for

mySAP.com and SAPDBAprofiles 25

Installation on UNIX 20installation on Windows 22mySAP.com database utilities 19Tivoli Storage Manager client 20verifying the installation 27

setting up Tivoli Storage Manager 11simultaneous backup sessions 139SNMP trap 8SNMPTRAP profile keyword 121software compression vs. hardware

compressionUNIX 17Windows 18

sorting, files 8specifying a backup strategy 45specifying management classes 4storage device setup

Tivoli Storage Manager server 13storage pool

glossary definition 147storage pool definitions

Tivoli Storage Manager server 13storage pool volumes

choosing volumes for backups 139strategy

planning a backup strategy 45system copy

heterogeneous 73homogeneous 73

Ttablespace

glossary definition 147tablespace locking 5tablespace, backup 37tape drives

backup sessions with limited tapedrives 140

using hardware compressionwith 17, 18

TCPWAIT 115terminating the backup job 109threads

multi-threading 9Tivoli Storage Manager 11

backup scheduler 50client 20client software compression 18

Tivoli Storage Manager (continued)configuration file customization 61data archival 11data backup, restoration 11data compression 57data space management 11description 11glossary definition 147incremental backup function 48management classes 4passwords 105performance optimization 61scheduling function 50setup 11

Tivoli Storage Manager APIglossary definition 147

Tivoli Storage Manager clientconfiguration 16configuration on UNIX systems 17configuration on Windows

systems 17software compression 17

Tivoli Storage Manager passwordsauthentication off 105configuration matrix to set

keywords 106generating automatically 105manual generation 105

Tivoli Storage Manager profilesexample for UNIX 127example for Windows 129

Tivoli Storage Manager serverconfiguration 12configuration, prerequisites 12management classes 14node definition 15performance considerations 12policy definition 14storage device setup 13storage pool definition 13

TRACE profile keyword 121TRACEFILE profile keyword 121TRACEMAX 115tracing 9tuning 61

UUNIX crontab, backup scheduler 50USE_AT profile keyword 121user authorization for Administration

Assistant 71util_file_online 5, 26, 38, 43

glossary definition 147utility

File Manager 33

Vvalidate

glossary definition 147verifying the Data Protection for

mySAP.com installation 27verifying the installation of the

Administration Assistant 70versions, backup 5


volumeglossary definition 147

WWeb browser

prerequisite for AdministrationAssistant 65

Windows, backup scheduler 50

Index 153


Readers’ Comments — We’d Like to Hear from You

IBM Tivoli Storage Manager for Enterprise Resource Planning (5698–APR)Data Protection for mySAP.com® TechnologyInstallation & User’s Guide for OracleVersion 3 Release 3. 1

Publication No. SC33-6340-03

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied VeryDissatisfied

Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied VeryDissatisfied

Accurate h h h h h

Complete h h h h h

Easy to find h h h h h

Easy to understand h h h h h

Well organized h h h h h

Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.

Readers’ Comments — We’d Like to Hear from YouSC33-6340-03

SC33-6340-03

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

International Business Machines CorporationAttn. Dept. ECJ - BP/003D6300 Diagonal HighwayBoulder, CO 80301-9151

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

Program Number: 5698–DPR

Printed in U.S.A.

SC33-6340-03

Documents

Data Protection for mySAP.com Technology Installation & User's Guide …publib.boulder.ibm.com/tividd/td/ITSMERP/SC33-6340-03/en... · 2007-09-29 · in new editions. Order publications