Tivoli Storage Manager for Resource Planning - IBM ® Storage Manager for Enterprise Resource...

Tivoli® Storage Manager

for Enterprise Resource Planning

Data Protection for SAP

Installation and User’s Guide for Oracle

Version 5.5

SC33-6340-09

��

Edition Notice

This edition applies to Data Protection for SAP Version 5 Release 5 Modification Level 0 (program number

5608–APR), available as a licensed program product, and to all subsequent releases and modifications until

otherwise indicated in new editions.

Order publications through your IBM® representative or the IBM branch office serving your area. Publications are

not stocked at the addresses given below.

Address comments on this publication to:

IBM Deutschland Entwicklung GmbH

Enterprise Solution Development

Dept. 3848, Bldg. 71032-15

Schoenaicher Str. 220

71032 Boeblingen

Germany

FAX (Germany): 07031 16 3619

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

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

Make sure to include the following in your comment or note:

v Title and order number of this book

v Page number or topic related to your comment

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any

way it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1995, 2007. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Note!

Before using this information and the product it supports, be sure to read the general information under

“Notices” on page 219.

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

Contents

Figures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . xi

Who Should Read This Book . . . . . . . . . xi

How to Read This Book . . . . . . . . . . xi

Where to Find More Information . . . . . . . xi

Naming Conventions Used in This Documentation xii

Contents of the Data Protection for SAP Package . . xii

Supported Platforms . . . . . . . . . . . xii

Platform Differences . . . . . . . . . . . xii

Summary of Changes . . . . . . . . . . . xii

Support . . . . . . . . . . . . . . . xiii

Part 1. Data Protection Basics . . . . 1

Chapter 1. Concepts of Data Protection

for SAP . . . . . . . . . . . . . . . 3

Oracle Backup/Restore and Data Protection for SAP 3

Data Protection for SAP and BACKINT . . . . 3

Data Protection for SAP and RMAN . . . . . 4

Chapter 2. Developing a Backup

Strategy . . . . . . . . . . . . . . . 7

Planning a Backup Strategy for the Operating System 7

Planning a Backup Strategy for Your Oracle Database 7

Planning a Backup Strategy for Backup Protocols and

Profiles . . . . . . . . . . . . . . . . 9

Planning a Backup Strategy for SAP System Data . . 10

Implementing the Strategy by Scheduling

Automated Backup Runs . . . . . . . . . . 11

Scheduling Products . . . . . . . . . . 11

Sample Backup Strategy for Daily Backup

Processing . . . . . . . . . . . . . . 12

Chapter 3. Introducing Data Protection

for SAP . . . . . . . . . . . . . . 15

Scope of Data Protection for SAP . . . . . . . 15

Integration of Data Protection for SAP with SAP . . 16

Storing Data on a TSM Server . . . . . . . . 17

Performance Options of Data Protection for SAP . . 18

Parallel (Multiple) Sessions . . . . . . . . 18

Multiplexing . . . . . . . . . . . . . 18

Disk Sorting . . . . . . . . . . . . . 18

Multiple (Parallel) Network Paths and Multiple

(Parallel) Servers . . . . . . . . . . . 18

Incremental Backup . . . . . . . . . . 18

Individual Tablespace Locking . . . . . . . 19

RL Compression . . . . . . . . . . . . 19

Automation Options of Data Protection for SAP . . 19

Selectable Management Classes . . . . . . . 19

Retain Backups by Version . . . . . . . . 19

Multiple Redo Log Copies . . . . . . . . 19

Alternate Network Paths and Servers . . . . . 19

Messaging . . . . . . . . . . . . . . 20

Frontend/Backend Processing . . . . . . . 20

Productivity Options of Data Protection for SAP . . 20

Reporting . . . . . . . . . . . . . . 20

Monitoring the Backup Status . . . . . . . 20

Performance Analysis . . . . . . . . . . 20

Tracing . . . . . . . . . . . . . . . 20

Using Data Protection for Snapshot Devices to

Minimize Backup and Restore Windows . . . . . 21

Archiving Inactive Data . . . . . . . . . . 21

Part 2. Installing and Using Data

Protection for SAP . . . . . . . . . 23

Chapter 4. Installing or Upgrading Data


Prerequisites for the Installation of Data Protection

for SAP . . . . . . . . . . . . . . . . 25

Installation Planning for Data Protection for SAP . . 26

Installing Data Protection for SAP . . . . . . . 26

Installing Data Protection for SAP on UNIX (AIX,

HP-UX, Solaris) or Linux . . . . . . . . . 27

Installing Data Protection for SAP on Windows 29

Post-Installation Steps . . . . . . . . . . . 32

Review of the TSM Options Files . . . . . . 32

Set the Password . . . . . . . . . . . 32

Verifying the Installation . . . . . . . . . 33

Upgrading (Migration) . . . . . . . . . . 34

Upgrading Data Protection for SAP . . . . . 34

Special Installation . . . . . . . . . . . . 35

Silent Installation . . . . . . . . . . . 35

Console Installation . . . . . . . . . . . 35

Firewall Installation . . . . . . . . . . 36

Uninstalling Data Protection for SAP . . . . . . 36

Uninstalling the Old Version of DP for SAP

under UNIX or Linux . . . . . . . . . . 36

Uninstalling the Old Version of DP for SAP

under Windows . . . . . . . . . . . . 36

Chapter 5. Adjusting Your System . . . 39

General Performance Considerations . . . . . . 39

Database Server Considerations . . . . . . 40

Network Considerations . . . . . . . . . 40

Backup Server Considerations . . . . . . . 41

Adjustments to DP for SAP for Improving

Performance of Data Transfer . . . . . . . . 41

Multiplexing . . . . . . . . . . . . . 42

Multiple Sessions . . . . . . . . . . . 43

Multiple Network Paths . . . . . . . . . 44

Multiple Servers . . . . . . . . . . . . 44

Compression . . . . . . . . . . . . . 45

Disk Sorting . . . . . . . . . . . . . 45

© Copyright IBM Corp. 1995, 2007 iii

||

||

| | |

| | | | | | |

Buffer Copies . . . . . . . . . . . . . 46

Buffer Size . . . . . . . . . . . . . . 46

Adjustments for Interaction with Other Components 46

Adjustments for the Administration Assistant . . 46

Adjustments for IBM Tivoli Storage Manager . . 47

Adjustments for High Availability . . . . . . . 50

Considerations for Using IBM HACMP for AIX 50

Chapter 6. Using DP for SAP with the

File Manager . . . . . . . . . . . . 55

DP for SAP File Manager . . . . . . . . . . 55

Chapter 7. Cloning the SAP System . . 59

What is Cloning? . . . . . . . . . . . . 59

SAP System Cloning Example . . . . . . . . 59

Chapter 8. Installing and Using the

Administration Assistant for Data


Introducing the Administration Assistant . . . . 63

Functions and Features of the Administration

Assistant . . . . . . . . . . . . . . 63

Concepts of the Administration Assistant . . . 64

Installing or Upgrading the Administration

Assistant . . . . . . . . . . . . . . . 67

Prerequisites for Installing the Administration

Assistant . . . . . . . . . . . . . . 67

Installation Planning for the Administration

Assistant Server-Level Components . . . . . 68

Installing the Administration Assistant

Server-Level Components . . . . . . . . 68

Post-Installation Steps . . . . . . . . . . 71

Starting and Stopping the Administration

Assistant Manually . . . . . . . . . . . 73

Upgrading the Administration Assistant

(Migration) . . . . . . . . . . . . . 74

Migration of Data from Previous Releases . . . 75

Configuring the Administration Assistant . . . . 76

Administering User IDs . . . . . . . . . 76

Configuring for Secure Communication . . . . 77

Changing the Password for the Administration

Assistant Database User ID . . . . . . . . 78

Defining Thresholds . . . . . . . . . . 78

Defining the Custom SQL file . . . . . . . 79

Chapter 9. Balancing Your System . . . 83

Cyclic Procedure for Optimizing your Configuration 83

Observations on the DP for SAP Data Throughput 83

Data Protection for SAP Performance Sensors . . . 84

Presentation of the Measurements in the

Administration Assistant . . . . . . . . . . 85

Typical Situations . . . . . . . . . . . 85

Simulating Backup and Restore . . . . . . . 89

Drilling Down on Special Situations . . . . . 91

Applying Backup Results to Restore . . . . . 91

Chapter 10. Reporting on Data

Protection for SAP Activities . . . . . 93

Types of Reports . . . . . . . . . . . . . 93

Reporting on Backup States . . . . . . . . 93

Reporting on Operations Details . . . . . . 94

Reporting on Backup Operation Trends . . . . 94

Reporting on Failed Actions . . . . . . . . 95

Reporting on the Performance of Backup

Operations . . . . . . . . . . . . . 95

Reporting on Simulations . . . . . . . . . 97

Prerequisites for Creating Reports . . . . . . . 97

Creating a Report . . . . . . . . . . . . 98

Requesting a Report from the Administration

Assistant Client . . . . . . . . . . . . 98

Working with Report Templates . . . . . . 98

Generating Reports Using Report Templates . . 99

Modifying Report Output . . . . . . . . . 100

Part 3. Appendixes . . . . . . . . 103

Appendix A. The Data Protection for

SAP Profile . . . . . . . . . . . . 105

Keyword Reference . . . . . . . . . . . 105

Sample Data Protection for SAP Profiles . . . . 115

Sample Data Protection for SAP Profile for

UNIX or Linux . . . . . . . . . . . . 115

Sample Data Protection for SAP Profile for

Windows . . . . . . . . . . . . . . 119

Appendix B. Data Protection for SAP

(Oracle) Messages . . . . . . . . . 125

How To Find Files Containing Message Output

(Log Files) . . . . . . . . . . . . . . 125

Prefix BKI . . . . . . . . . . . . . . 126

Appendix C. Troubleshooting . . . . 151

Problem Resolution During Installation and Setup 151

Understanding the Setup . . . . . . . . 151

Location of Log Files . . . . . . . . . . 153

BACKINT Problem Resolution . . . . . . 153

RMAN Problem Resolution . . . . . . . . 155

Problem Resolution During Operation . . . . . 158

Reproducible (Repeatable) Problems . . . . . 158

Random Problems . . . . . . . . . . . 158

Providing Information to IBM or Tivoli Support 159

Invoking Data Protection for SAP Manually . . . 159

Backup Function . . . . . . . . . . . 159

Restore Function . . . . . . . . . . . 160

Inquire Function . . . . . . . . . . . 161

Delete Function . . . . . . . . . . . 161

File Manager . . . . . . . . . . . . . 162

Appendix D. Using DP for SAP with a

Distributed File System on AIX . . . . 163

Setting Up DP for SAP in a Distributed File System 163

Setting Up DP for SAP in a Distributed File System

in an Adaptive Computing Environment . . . . 163

Setting up DP for SAP with Oracle RMAN in a

Distributed File System in an Adaptive Computing

Environment . . . . . . . . . . . . . 164

iv Data Protection for SAP Installation and User’s Guide for Oracle

||

||||

| | | | | | | | | | | |

Appendix E. Installation Planning

Sheets . . . . . . . . . . . . . . 167

Data Protection for SAP . . . . . . . . . . 167

Administration Assistant . . . . . . . . . 168

Appendix F. Reference Material for the

Administration Assistant . . . . . . 173

Sample Command Files for Scheduling Reports 173

Sample Shell Script for Scheduling a Report

from a UNIX Scheduling Client . . . . . . 173

Sample Command File for Scheduling a Report

from a Windows Scheduling Client . . . . . 173

Sample Custom SQL File . . . . . . . . . 174

Appendix G. Alternate or Parallel

Backup Paths and Backup Servers . . 175

Parameter Settings - SERVER Statement . . . . 176

Example 1: Use of Alternate Paths for Increased

Availability . . . . . . . . . . . . . 177

Example 2: Use of Parallel Servers for Increased

Performance . . . . . . . . . . . . . 179

Example 3: Use of Alternate Servers for Disaster

Recovery . . . . . . . . . . . . . . 180

Appendix H. Preparing Tivoli Storage

Manager for DP for SAP . . . . . . . 181

Configuring the Tivoli Storage Manager Server . . 181

General Considerations for TSM . . . . . . 181

Prerequisites . . . . . . . . . . . . . 182

Adjusting Tivoli Storage Manager for DP for

SAP . . . . . . . . . . . . . . . 182

Configuring the Tivoli Storage Manager Clients 185

General Considerations . . . . . . . . . 185

Tivoli Storage Manager Clients on UNIX or

Linux Systems . . . . . . . . . . . . 185

Tivoli Storage Manager Clients on Windows

Systems . . . . . . . . . . . . . . 187

Password Handling . . . . . . . . . . . 188

Password Configuration Matrix (UNIX or

Linux) . . . . . . . . . . . . . . . 189

Password Configuration Matrix (Windows) . . 190

Appendix I. Backup Scheduling

Examples . . . . . . . . . . . . . 191

UNIX or Linux Crontab Example . . . . . . . 191

Elements of Backup Schedules for UNIX or Linux 191

Crontab File Sample . . . . . . . . . . 191

Full Offline Backup Shell Script Sample . . . 192

Save and Delete Redo Logs Shell Script Sample 192

Windows Scheduling Example . . . . . . . . 193

Elements of Backup Schedules for Windows . . . 193

Schedule Batch Sample . . . . . . . . . 193

Full Offline Backup Batch File Sample . . . . 194

Save and Delete Redo Logs Batch File Sample 195

Appendix J. Sample Tivoli Storage

Manager Profiles . . . . . . . . . . 197

Sample TSM Profiles for UNIX or Linux . . . . 197

Client User Options File Sample (dsm.opt) . . 197

Client System Options File Sample (dsm.sys) 197

Include/Exclude List Sample . . . . . . . 197

Sample TSM Profiles for Windows . . . . . . 198

Client User Options File Sample (dsm.opt) . . 198

Client Options Files Sample (<server>.opt) . . 198

Include/Exclude List Sample . . . . . . . 199

Appendix K. Hints and Tips for

BR*Tools . . . . . . . . . . . . . 201

Hints and Tips for BRARCHIVE . . . . . . . 201

Cooperation of Data Protection for SAP with

BRARCHIVE . . . . . . . . . . . . 201

Multiple Redo Log Copies . . . . . . . . 201

Messages . . . . . . . . . . . . . . 202

Appendix L. Hints and Tips for

Network Settings . . . . . . . . . . 205

Networks with Large Bandwidth-Delay Product 205

SP Switch (RISC 6000) . . . . . . . . . . 206

Network Settings of the Tivoli Storage Manager 206

Appendix M. Internet Protocol Version

6 (IPv6) Support . . . . . . . . . . 207

Appendix N. Support Information . . . 209

Using IBM Support Assistant . . . . . . . . 209

Obtaining Fixes . . . . . . . . . . . . . 209

Receiving Weekly Support Updates . . . . . . 210

Contacting IBM Software Support . . . . . . 211

Determining the Business Impact . . . . . . 212

Describing Problems and Gathering Information 212

Submitting Problems . . . . . . . . . . 212

Glossary . . . . . . . . . . . . . 215

Notices . . . . . . . . . . . . . . 219

Trademarks and Service Marks . . . . . . . 219

Accessibility . . . . . . . . . . . . . . 220

Navigating the Interface Using the Keyboard 221

Magnifying What is Displayed on the Screen 221

Index . . . . . . . . . . . . . . . 223

Contents v

||

|||

| | |

vi Data Protection for SAP Installation and User’s Guide for Oracle

Figures

1. DP for SAP with BR*Tools using the BACKINT Interface . . . . . . . . . . . . . . . . . . . 3

2. DP for SAP with BR*Tools using the RMAN Interface . . . . . . . . . . . . . . . . . . . . 5

3. Backup Scenarios Within an SAP Oracle Environment . . . . . . . . . . . . . . . . . . . . 9

4. Production Backup Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5. Scope of Data Protection for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6. Integration of Data Protection for SAP with SAP . . . . . . . . . . . . . . . . . . . . . 16

7. Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8. Data Transfer for a Backup / Restore . . . . . . . . . . . . . . . . . . . . . . . . . 42

9. Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

10. Parallel (Multiple) Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

11. Parallel (Multiple) Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

12. Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

13. Null Block Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

14. Sample Environment for HACMP Takeover . . . . . . . . . . . . . . . . . . . . . . . 50

15. File Manager — Result of an Inquiry Procedure . . . . . . . . . . . . . . . . . . . . . 56

16. File Manager — Result of an Inquiry Procedure Showing File Names . . . . . . . . . . . . . . 56

17. File Manager — Result of a Redirected Restore Procedure . . . . . . . . . . . . . . . . . . 58

18. Administration Assistant Components (with Default Port Numbers) . . . . . . . . . . . . . . 64

19. Example of an SAP Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

20. Optimizing your Configuration with the Administration Assistant . . . . . . . . . . . . . . . 83

21. A Bird’s Eye View of the Data Flow During Backup . . . . . . . . . . . . . . . . . . . . 84

22. Performance Optimizing by Using Sensors . . . . . . . . . . . . . . . . . . . . . . . 84

23. Showing Data Throughput and I/O Utilization . . . . . . . . . . . . . . . . . . . . . 85

24. Indicating a Disk Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

25. Indicating a Network or TSM Bottleneck . . . . . . . . . . . . . . . . . . . . . . . . 87

26. Indicating a Balanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 88

27. Drilling Down: Replay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

28. Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

29. Operations – Detailed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

30. Operations Daily Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

31. Operations - Failure Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

32. Performance Report - Graphical Presentation Section . . . . . . . . . . . . . . . . . . . . 96

33. Performance Report - Tabular Presentation Section . . . . . . . . . . . . . . . . . . . . 97

34. Simulation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

35. SAP and Data Protection for SAP configuration files on UNIX or Linux . . . . . . . . . . . . . 152

36. Problem Isolation for Backint . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

37. Problem Isolation for RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

© Copyright IBM Corp. 1995, 2007 vii

||

viii Data Protection for SAP Installation and User’s Guide for Oracle

Tables

1. File Extensions for Shared Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 27

2. SAP Backup Profile Parameter Combinations . . . . . . . . . . . . . . . . . . . . . . 33

3. Tags for Defining Thresholds in the Custom SQL File . . . . . . . . . . . . . . . . . . . 79

4. Contents of the Custom SQL File . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5. Summary: How to Determine Throughput Rates . . . . . . . . . . . . . . . . . . . . . 90

6. Installation Parameters for Data Protection for SAP . . . . . . . . . . . . . . . . . . . . 167

7. Installation Parameters for the Administration Assistant . . . . . . . . . . . . . . . . . . 168

8. SERVER Statement and Appropriate Profile and Option File Settings. . . . . . . . . . . . . . . 176

9. Password Handling for UNIX or Linux . . . . . . . . . . . . . . . . . . . . . . . . 189

10. Password Handling for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 190

11. Prefixes when using BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

12. Tuning of Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

13. Tuning of SP Switch Buffer Pools . . . . . . . . . . . . . . . . . . . . . . . . . . 206

14. Tuning Tivoli Storage Manager Configuration File Attributes . . . . . . . . . . . . . . . . . 206

© Copyright IBM Corp. 1995, 2007 ix

||

||||

x Data Protection for SAP Installation and User’s Guide for Oracle

Preface

Who Should Read This Book

This manual is intended for system programmers and administrators who are

responsible for implementing a backup solution in an SAP environment using the

Tivoli Storage Manager. It describes the procedures needed to install and customize

Data Protection for SAP, the interface between SAP and the Tivoli Storage

Manager. The reader should be familiar with the documentation for SAP, Tivoli

Storage Manager, and Oracle.

This book describes release V5.5, November 2007.

How to Read This Book

The manual is split into three parts, of which the first is a general introduction into

data protection, the second describes the installation, the architecture and

properties of Data Protection for SAP, and the third part (Appendixes) gives

reference information.

If you are a person experienced in data protection, you may want to skip

chapters 1 and 2, however you may want to browse chapter 3 for new functions.

The information given in part 2 is for system programmers and administrators

who know how Data Protection for SAP is embedded in a comprehensive data

protecting system.

If you are a data protection novice, you might want to start reading the

publication from part one on. This way you get introductional information of what

protecting your data means and what needs to be considered while setting up a

data protection system.

Where to Find More Information

For more information about IBM Tivoli Storage Manager for Enterprise Resource

Planning, refer to the Tivoli Internet home page at:

http://www.ibm.com/software/tivoli/products/storage-mgr-erp/

The most up-to-date version of this book is available in the IBM Tivoli Information

Center at

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmerp.doc/dperp.html

In order to access a national language version of this book, make sure you have

your browser set to the appropriate language.

The release notes for Tivoli Storage Manager for Enterprise Resource Planning V5.5

are also available in the Tivoli Information Center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmreadme.doc_5.5/relnote_erp550.html

© Copyright IBM Corp. 1995, 2007 xi

|||

|||


http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmerp.doc/dperp.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmreadme.doc_5.5/relnote_erp550.html

Naming Conventions Used in This Documentation

"IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection for

SAP″ is usually referred to as ″Data Protection for SAP ″ or ″DP for SAP ″

SAP AG has discontinued the use of "mySAP" in favor of 'SAP'.

Unless otherwise stated, references in this publication toUNIX® apply to all

supported UNIX-based systems, references to Linux® apply to all supported Linux

platforms, and references to Windows® apply to all supported Windows platforms.

Contents of the Data Protection for SAP Package

Data Protection for SAP is available as machine readable material on 3 CD-ROMs

or images of these CDs downloadable via IBM Passport Advantage®. See the

release note file in the Tivoli Information Center (“Where to Find More

Information” on page xi) for information that updates the topics in this

publication,:

Supported Platforms

For a list of supported platforms see the online Release Note (“Where to Find More

Information” on page xi)..

Platform Differences

There are only small differences between the UNIX or Linux and Windows

versions of Data Protection for SAP. One of these differences is that UNIX or Linux

uses the path separator ″/″ compared with ″\″ for Windows and that the drive

letter is specified for Windows. Non-trivial differences between the UNIX or Linux

and Windows versions of Data Protection for SAP are mentioned explicitly.

Summary of Changes

The following new functionality has been added to Version 5.5.0. of Data

Protection for SAP for Oracle:

v Thresholds can be defined in the Administration Assistant. See “Defining

Thresholds” on page 78.

v The Administration Assistant database can now be managed by IBM DB2® as an

alternative to Apache Derby.

v Internet Protocol Version 6 (IPv6) is supported by Data Protection for SAP and

the Administration Assistant. Unless otherwise noted, any specification of an IP

address in this document can be an IPv4 or IPv6 address. For general

information, see Appendix M, “Internet Protocol Version 6 (IPv6) Support,” on

page 207. Examples continue to use the IPv4 address format.

Other changes include

v SAP AG has discontinued the use of "mySAP" in favor of 'SAP'.

v The RMAN information previously included as a separate chapter has been

distributed to other sections of the book as appropriate.

v Information is provided on storing control files on remote Windows shares (see

“Implementing Configuration Files on Remote Shares” on page 31).

xii Data Protection for SAP Installation and User’s Guide for Oracle

|

||

||

||

|||||

|

|

||

||

Support

See Appendix N, “Support Information,” on page 209 for general information

concerning provision of support by IBM. “Providing Information to IBM or Tivoli

Support” on page 159 lists the types of information that you should provide to the

support function.

Preface xiii

xiv Data Protection for SAP Installation and User’s Guide for Oracle

Part 1. Data Protection Basics

© Copyright IBM Corp. 1995, 2007 1

2 Data Protection for SAP Installation and User’s Guide for Oracle

Chapter 1. Concepts of Data Protection for SAP

This chapter is meant for users who are new to Data Protection for SAP. If you are

experienced in Data Protection for SAP, you might want to move on to the

following chapter.

Oracle Backup/Restore and Data Protection for SAP

The SAP database administration tools offer all the functions necessary to

administer a database. The BR*Tools for Oracle, (BRBACKUP, BRARCHIVE,

BRRESTORE, BRRECOVER) provide for online or offline, partial or full backup of

tablespaces (done by BRBACKUP), backup of archived redo log files (done by

BRARCHIVE) and system-guided restore and recover capabilities (done by

BRRESTORE and BRRECOVER).

Oracle also provides its own administration utility RMAN (Recovery MANager)

which is of specific value when incremental backups are required. Data Protection

for SAP is seamlessly integrated with SAP’s BR*Tools and Oracle’s RMAN and is

optimized to handle unattended, 24-hour, 7-days-per-week production backup and

restore tasks.

Data Protection for SAP and BACKINT

Figure 1 shows the interaction between BR*Tools, Data Protection for SAP, and the

BACKINT interface in order to do backups or restores.

The BR*Tools use tables in the Oracle database and system data in order to record

the status of the data file backups and logfile backups. This information will allow

SAP to automatically restore the correct data files and their specific database

transaction log files (redo log files), if necessary. The data files reside in the Oracle

database (Oracle Instance). Data Protection for SAP runs as a separate process,

independently from the database. It receives the data through the BACKINT

interface and saves the data to the Tivoli Storage Manager.

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

Figure 1. DP for SAP with BR*Tools using the BACKINT Interface


1. BR*Tools utility BRBACKUP informs Oracle what data has to be backed up and

puts the database into the proper backup state (’online’ or ’offline’).

2. BRBACKUP calls DP for SAP via the BACKINT interface with a list of all files

to be backed up.

3. DP for SAP reads all requested files from the database and reports back to

BRBACKUP. BRBACKUP adds these files to the repository containing all

processed backups.

4. BACKINT saves the data to TSM.

5. The BR*Tools update the file repository containing information on the status of

the files.

Data Protection for SAP and RMAN

You can use the Recovery Manager (RMAN) to do a backup, restore and recover

operation of an Oracle database. Furthermore, if you want to make incremental

backups, this can only be done with RMAN.

Note

Check the SAP support information, for example the SAP Service Marketplace

at:

http://service.sap.com/ ,

on how to set up backup via RMAN on your operating system. Check also

for special considerations for the database version you are using.

When running with RMAN, Data Protection for SAP is loaded by one or more

Oracle processes as a shared library. These Oracle processes will then decide on

how many parallel sessions are opened, when a session is opened and closed,

which data object (e.g. table space) will be included into which session, and so on.

Some of the above mentioned parameters must be configured for RMAN.

Depending on how you are using RMAN, you can configure these parameters

either within the RMAN script or the BR*Tools configuration file (init<SID>.sap).

If you want to use parallel sessions with RMAN, make sure you configure at least

the same number of sessions within the Data Protection for SAP configuration file

as you configure for RMAN (see also “Multiple Sessions” on page 43 and

“Multiple Servers” on page 44).

Figure 2 on page 5 shows the interaction between BR*Tools, Data Protection for

SAP, Oracle RMAN, and DP for SAP in order to do backups or restores.

Concepts of Data Protection for SAP


|

||||

|||||||||

|||||||

||||

|||

The BR*Tools use tables in the Oracle database and system data in order to record

the status of the database and redo log backups.. This information will allow SAP

to automatically restore the correct data and their corresponding redo logs. The

data files reside in the Oracle database (Oracle Instance).

Data Protection for SAP runs as a linked library controlled by the Oracle Server

Process.

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

1. BR*Tools utility BRBACKUP informs Oracle RMAN what data has to be backed

up. The RMAN process puts the database into the proper backup state (’online’

or ’offline’).

2. The Oracle server process loads DP for SAP and interacts with it through the

Media Management API.

3. DP for SAP reads the requested data from the database and reports back to

BRBACKUP. BRBACKUP adds this data to the repository containing all

processed backups.

4. DP for SAP saves the data to a TSM server.

5. BR*Tools update the repository containing information on the status of the

data. RMAN has its own repository, with a control file for a separate recovery

catalog database.

Figure 2. DP for SAP with BR*Tools using the RMAN Interface


Chapter 1. Concepts of Data Protection 5

|

|||||||

||

|

|||

||

|||

|

|||

Chapter 2. Developing a Backup Strategy

This chapter helps you define an appropriate backup strategy for your SAP

system. If you already have a successful backup strategy in place you may want to

move on to the next chapter.

The strategy you choose is dependent on your specific requirements. Consider the

following questions:

v What type of events do you wish to protect your SAP system against?

v How large is your database?

v What is the transaction rate of your database?

v How fast do you need to recover from a failure?

v What backup windows are available?

Data Protection for SAP allows you to back up SAP database data directly to Tivoli

Storage Manager. However, these backups deal only with the database and the

offline redo logs.

Hence, to protect your complete system against failures affecting BR*Tools or other

SAP system data, you should use the IBM Tivoli Storage Manager Backup-Archive

Client to additionally backup these system data.

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

below must become an integral part of your overall disaster recovery plan.

Planning a Backup Strategy for the Operating System

In order to be protected against a complete loss of the operating system, it is

imperative that after:

v the installation of the operating system

v updates/upgrades of the operating system

appropriate system backups are made with the operating system dependent

utilities, for example mksysb for AIX®,

This will allow you to start your system from the backup medium. Base backups

should include a configured TCP/IP environment as well as the Tivoli Storage

Manager client including the API in order to be able to restore all user dependent

data.

Planning a Backup Strategy for Your Oracle Database

In order to be able to recover from:

v user errors

v statement failures

v transaction failures

v media failures

that could affect your Oracle database, save the following objects on a regular

basis:

v Data files


v Control files

v Online redo logs

v Offline redo logs

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

This is done at the file level, where offline or online backups are possible.

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

Online redo logs are saved by BRBACKUP whenever a full offline database backup

occurs.

Note

Oracle provides mirroring of the control and online redo log files to protect

the running database system against corruption of these active files. (The AIX

LVM facilities can also be used to mirror these files.)

Offline redo logs are saved by BRARCHIVE. You can specify that the redo logs be

deleted from their original location when BRARCHIVE completes successfully.

Additional information on BRARCHIVE operations can be found in Appendix K,

“Hints and Tips for BR*Tools,” on page 201.

Apart from backing up all database relevant data (data files, control file, online

redo log files, and offline redo log files) it is also recommended that you back up

v SAP system data

v Oracle system data

v Operating system data

This data should be backed up with the incremental backup function of the Tivoli

Storage Manager backup-archive client.

Figure 3 on page 9 shows the various backup scenarios within an SAP database

server machine.

Developing a Backup Strategy


The database itself is backed up with Data Protection for SAP, whereas the SAP,

Oracle and operating system protocols are backed up directly by the Tivoli Storage

Manager.

Planning a Backup Strategy for Backup Protocols and Profiles

Every BRBACKUP and BRARCHIVE run is divided into two parts. The first part

backs up objects such as:

v SAP data files

v database control files

v online redo log files

v offline redo log files

depending on the action started (see previous section).

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

following profiles:

v init<SID>.dba (BR*Tools profile)

v init<SID>.ora (Oracle profile)

v init<SID>.sap (BR*Tools Initialization profile)

v init<SID>.utl (Data Protection for SAP profile)

and the protocol files

v back<SID>.log (BRBACKUP summary log)

v arch<SID>.log (BRARCHIVE summary log)

v detailed BRBACKUP/BRARCHIVE log

v reorg<SID>.log (main BR*Tools log)

v struct<SID>.log (structure log)

Figure 3. Backup Scenarios Within an SAP Oracle Environment


Chapter 2. Developing a Backup Strategy 9

These profiles and protocols are required by the BR*Tools whenever backups or

restores/recoveries are requested. Unless you also do a file system backup, these

profiles or protocol files can only be restored by Data Protection for SAP. If one of

these files is lost you can use the Data Protection for SAP File Manager (see “DP

for SAP File Manager” on page 55) to restore it before calling BRRESTORE or

BRRECOVER.

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

restore the backup protocols or profiles by means of Data Protection for SAP or the

Data Protection for SAP File Manager. Hence, it is recommended that you back up

the directories and file systems containing these files separately.

You can find the files in the following directories:

UNIX or Linux

/oracle/<SID>/sapreorg (BR*Tools and structure logs)

/oracle/<SID>/sapbackup (BRBACKUP logs)

/oracle/<SID>/saparch (BRARCHIVE logs)

/oracle/<SID>/dbs (profiles)

Windows

<drive>:\oracle\<SID>\sapreorg (BR*Tools and structure logs)

<drive>:\oracle\<SID>\sapbackup (BRBACKUP logs)

<drive>:\oracle\<SID>\saparch (BRARCHIVE logs)

<drive>:\orant\database (profiles)

Planning a Backup Strategy for SAP System Data

In addition to the backup operations performed with BRBACKUP and

BRARCHIVE, you may want to protect your system against the loss of SAP system

data, user data, or even operating system data that is not stored with BRBACKUP

or BRARCHIVE. You can use the incremental backup capabilities of the Tivoli

Storage Manager backup-archive client to do this.

The Tivoli Storage Manager incremental backup function lets you define an

include-exclude list of files that is applied automatically during incremental backup

operations. This include-exclude list should be used to exclude data already stored

using Data Protection for SAP. This would be all database relevant data, such as

data files, the control file, and online/offline redo logs. For further information

about include-exclude lists, see your Tivoli Storage Manager manuals, Using the

Backup-Archive Clients. Examples of include-exclude lists for UNIX or Linux can be

found in “Sample TSM Profiles for UNIX or Linux” on page 197 and for Windows

in “Sample TSM Profiles for Windows” on page 198.

Sample files can be found in your Data Protection for SAP installation package.

The information saved with the BRBACKUP and BRARCHIVE utilities is usually

located in the following file systems or directories:



UNIX or Linux

/oracle/<SID>/saparch/

/oracle/<SID>/sapdata1/






.

.

.

/oracle/<SID>/origlogA/

/oracle/<SID>/origlogB/

Windows

<drive>:\oracle\<SID>\saparch\

<drive>:\oracle\<SID>\sapdata1\






.

.

.

<drive>:\oracle\<SID>\origlogA\

<drive>:\oracle\<SID>\origlogB\

Add these directories to the list of paths to be excluded in the include-exclude list

of your Tivoli Storage Manager backup-archive client. This will prevent you from

saving the database data twice.

Implementing the Strategy by Scheduling Automated Backup Runs

To ensure that all your data will be backed up regularly at a certain time, it is

recommended that you schedule automated backup and archive operations.

Scheduling Products

There are several products that can be used to set up a schedule, for example:

v SAP scheduler (CCMS)

v UNIX or Linux crontab / Windows scheduler

v Tivoli Storage Manager scheduler

v IBM Tivoli Workload Scheduler

SAP Scheduler

Within SAP , the Computer Center Management System (CCMS) provides a

scheduler for database administration and backup planning on a single database

server. The scheduler can be started from the SAPGUI command line (transaction

code db13) or with the SAPGUI menu functions (Tools -> CCMS -> DB

administration -> DBA scheduling).

UNIX or Linux crontab / Windows Scheduler

Another possibility of backup automation on the database server level is offered by

the cron jobs for UNIX or Linux systems or schedule services for Windows.



An example of a cron job can be found in “UNIX or Linux Crontab Example” on

page 191.

Tivoli Storage Manager Scheduler

The Tivoli Storage Manager also provides functions for automating operations of

all its clients. Therefore, the scope of control can comprise multiple database

servers.

Schedule definition work can be done quickly using the GUI based Tivoli Storage

Manager Web administrative client.

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

the Tivoli Storage Manager Administrator’s Reference manual.

IBM Tivoli Workload Scheduler

The IBM Tivoli Workload Scheduler provides event-driven automation, monitoring,

and job control for both local and remote systems. More information can be found

at http://www.ibm.com/software/tivoli/products/scheduler/.

Sample Backup Strategy for Daily Backup Processing

The following figure illustrates the sequence of backup runs you may want to

establish for a daily backup schedule. This example of automated backup operations shows the following typical tasks

v Full database backup, e.g., offline or without application load, performed each

night.

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

advantage of eliminating the need for extra tape mounts for relatively small

files.

Figure 4. Production Backup Example



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

Note

Backups can be performed to disks as well as to tape environments. Tivoli

Storage Manager will manage the data regardless of the storage media.

However, it is recommended that the SAP database is directly backed up to

tape.

v Within Tivoli Storage Manager, archived log files are migrated from disk to tape

after the full database backup.

v SAP system files are backed up incrementally with the Tivoli Storage Manager

backup-archive client.

v The last backup in the daily cycle is the backup of the Tivoli Storage Manager

database. This should always be done.



Chapter 3. Introducing Data Protection for SAP

This chapter explains the Data Protection for SAP architecture and gives an

introduction to the product features. Even if you are an experienced user of Data

Protection for SAP you may want to browse this overview for new features.

Data Protection for SAP together with Tivoli Storage Manager provides a reliable,

high performance, and production-oriented solution that allows you to backup and

restore your Oracle-based SAP systems. It is integrated with SAP’s backup and

recovery utilities BRBACKUP, BRARCHIVE, BRRESTORE, and BRRECOVER, and

allows you to follow SAP’s backup and recovery procedures. Being optimized for

SAP databases, Data Protection for SAP allows you to manage large volumes of

data most efficiently.

Scope of Data Protection for SAP

The SAP utilities for backup and recovery of SAP databases are focused on the

database objects, where over 90% of the data on an SAP database server reside.

Thus Data Protection for SAP will be used for backup and restore of data files,

control files, and online and offline redo logs. (See Figure 5).

Other files such as SAP and Oracle executables can be backed up using the IBM

Tivoli Storage Manager Backup-Archive Client. As a consequence, in the case of a

disaster recovery, you have to make sure that all Oracle and SAP executables are

available before starting restore and recovery of your database using Data

Protection for SAP and the BR*Tools.

Figure 5. Scope of Data Protection for SAP


Integration of Data Protection for SAP with SAP

Once configured, Data Protection for SAP operates as an invisible link between

Oracle and BR*Tools on one hand and Tivoli Storage Manager on the other.

It provides you with two different adapters supporting different backup and

recovery scenarios:

v backint: an executable that is called directly by SAP. It can be used to perform

full online and offline backups as well as backups of control and redo log files.

v a shared library that is dynamically linked by Oracle’s RMAN (an executable

installed during the Oracle database installation). If a backup is performed using

this library, SAP does not communicate with Data Protection for SAP directly. It

communicates through Oracle’s RMAN process instead. When using RMAN and

this shared library, you can perform incremental database backups.

Both adapters - backint and the media management library for Oracle - share a

profile init<SID>.utl, which describes how to perform backups and restores, and

which can be used to customize Data Protection for SAP to your environment and

according to your needs. Both adapters communicate with the TSM server through

an API that is shared with other IBM Tivoli Data Protection products, and both

require that ProLE - a background process that is part of the Data Protection for

SAP package - is running.

The Data Protection for SAP package also contains the Administration Assistant,

aimed at increasing the administrator’s productivity. The Administration Assistant

typically resides on a different server and communicates with Data Protection for

SAP via TCP/IP. It can control several instances of Data Protection for SAP. Its

functionality covers configuring an instance of Data Protection for SAP, data

Figure 6. Integration of Data Protection for SAP with SAP

Introducing Data Protection for SAP


transfer performance monitoring and monitoring of the backup status of connected

SAP systems as well as the TSM server activity related to these SAP systems.

It allows you to monitor and administer all of your Data Protection for SAP

instances remotely via an applet running in a Web browser. You may register an

SAP instance with the Administration Assistant during installation. For information

on how to register at a later time or with a different Administration Assistant, refer

to “Adjustments for the Administration Assistant” on page 46.

Storing Data on a TSM Server

Data Protection for SAP transfers data to and from the backup server via a single

session or via multiple (parallel) sessions to a TSM server. Each session must have

a storage device associated with it. The SAP backup ID is persistently linked with

each backup file. This backup ID can be used later to determine all files required

for a complete restore.

Note

In SAP terminology ’backup’ (BRBACKUP) means backup of data files,

’archive’ (BRARCHIVE) means the backup of archived redo log files. DP for

SAP employs the TSM archive function for both backup types.

It is highly recommended to use tape storage for the database contents, as this has

consistently proven to provide the best data throughput for backup and restore. In

addition the files sequence from backup is then maintained for restore as well,

which will yield shortest possible restore windows.For backing up log files it is recommended to use a disk-tape storage hierarchy

and to backup each log file right after it is placed into the archive directory. This

yields the best protection against data loss and eliminates the necessity to mount a

tape for each 20 MB file.

Collocation is a function in TSM to ensure that client data is kept together on one

tape. We recommend to deactivate collocation for backups with DP for SAP in

order to enable parallel sessions to use multiple tape drives in parallel. Collocation

must also be deactivated in order to use the multiple log copy function, see

“Multiple Redo Log Copies” on page 19.

Views of backups on the TSM server can be generated by the SAP administration

tools either by using their own local (detailed) backup log or by inquiring the TSM

server through DP for SAP. Manual access to the backup repository is provided

through a specific File Manager -backfm - shipped with DP for SAP. It allows the

administrator to bypass the SAP tools to inquire, delete and restore backups / files.

Note

DP for SAP can be configured to use multiple TSM servers to improve either

availability (alternate servers) or performance (multiple servers). DP for SAP

accesses only the servers defined in its profile when inquiring for the backup

repository. Therefore care has to be taken when removing TSM servers from

the DP for SAP profile while they still hold valid backup data.


Chapter 3. Introducing Data Protection for SAP 17

Database backups are usually kept for a specified time until they become obsolete.

In order to manage backup storage space efficiently these backups should then be

deleted so tapes can be reclaimed. There are two ways to perform this deletion:

1. by setting the archive retention period with TSM, or

2. by using the DP for SAP backup version control function. Data Protection for

SAP deletes whole backup generations, i.e. full backups and all related redo log

backups, when the specified number of versions is exceeded.

Note: Since the SAP backup log cannot be updated by DP for SAP , it may still

contain old backups although they are already deleted (expired).

Performance Options of Data Protection for SAP

To achieve good data transfer rates for backup and restore you have to make sure

that the following three components all have good data transfer rates: the disks on

which the database is located, the network between the database host and the TSM

server, and the backup storage device containing the backup. Keep in mind that

the weakest of these components constrains your backup/restore performance and

thus appears as a bottleneck. Data Protection for SAP offers a variety of options to

optimize the data transfer rate for each of these components.

Parallel (Multiple) Sessions

Data Protection for SAP allows you to backup or restore data to multiple tape

drives in parallel. Parallelism is achieved by using more than one session to send

data to a backup server For details see “Multiple Sessions” on page 43.

Multiplexing

Multiplexing allows you to simultaneously transfer data from different files

through one session (MULTIPLEXING ) in order to maximize tape performance.

This is useful since tape drives often have higher data transfer rates than the disks

containing the tablespaces of your SAP database. Note that most customers

combine multiplexing and parallel sessions to optimize their overall backup and

restore performance. For more information see on page 111.

Disk Sorting

Data Protection for SAP deploys Adaptive File Sequencing to minimize the backup

window. It sorts database files in order to avoid simultaneous reading of files

located on the same disk.

Multiple (Parallel) Network Paths and Multiple (Parallel)

Servers

You can configure Data Protection for SAP to distribute a backup of a database

across two or more TSM servers. Similarly, by providing two or more separate

network connections between the SAP database host and the TSM server, you can

configure Data Protection for SAP to balance network traffic across all available

network connections to the TSM server. For details see “Multiple Network Paths”

on page 44 and “Multiple Servers” on page 44.

Incremental Backup

Data Protection for SAP supports incremental RMAN backup of an SAP database.

Depending on the system environment, this may result in decreased backup times.



Individual Tablespace Locking

To minimize the amount of archived redo logs during online backup operations,

Data Protection for SAP can notify the SAP database utilities for which tablespaces

it is going to back up files. The SAP utilities then switch those tablespaces into

backup mode. After the files are backed up, the tablespaces are released again and

a new cycle starts. This mode (util_file_online) is set with a parameter in the

BR*Tools profile setup. For more information see on page 33.

RL Compression

RL Compression is a fast and very effective mechanism to compress a partially

filled database. For such a database you can reduce network traffic, decrease the

number of tapes required for a backup, and reduce the impact of network induced

bottlenecks. For more information see “Compression” on page 45.

Automation Options of Data Protection for SAP

Data Protection for SAP comes with a variety of options that help improve your

administrative productivity.

Selectable Management Classes

You can specify different TSM management classes for backing up and archiving

data. It is best practice to configure Data Protection for SAP to backup directly into

a tape storage pool and to archive log files into a disk storage pool. In addition

multiple management classes have to be used in conjunction with multiple redo

log copies. For information how to specify management classes, see the profile

keywords BRARCHIVEMGTCLASS and BRBACKUPMGTCLASS starting on page

106.

Retain Backups by Version

This function enables you to limit the number of full backups kept on the TSM

server. If you have more than MAX_VERSIONS of full backups on a TSM server

the oldest versions are deleted. This function keeps track of all redo log files,

database control files, partial and incremental backups, depending on a full

backup. All these objects are removed together with a full backup.

Multiple Redo Log Copies

As protection against tape defects and to improve availability and disaster

recovery, you can backup multiple copies of a log file and configure your system

such that these copies are located on different physical Tivoli Storage Manager

volumes or even different TSM servers. If at restore time one log file copy is

unavailable Data Protection for SAP automatically switches to another copy and

continues restoring from the log file from that copy. For more detailed information

about creating and using multiple Redo Log Copies, see the profile keyword

REDOLOG_COPIES on page 112.

Alternate Network Paths and Servers

Similar to the configuration of multiple network paths and servers, you can

configure Data Protection for SAP to use multiple TSM servers or multiple network

connections to one TSM server alternately to improve availability of backup

storage. In such a configuration Data Protection for SAP checks all servers and

network connections for availability and allows you to perform your backups even

if some resources are currently unavailable. Also, you can establish policies to use

different TSM servers at different days of the week.



Messaging

You can establish policies that trigger Data Protection for SAP to send different

classes of log messages to a TSM server.

Frontend/Backend Processing

Data Protection for SAP allows you to register applications that are executed before

starting a backup/restore operation and after it has completed. For more

information see on pages 106 and 108.

Productivity Options of Data Protection for SAP

Reporting

At the end of a backup, Data Protection for SAP produces a report providing

statistical information such as the number of bytes transferred and the effective

data throughput. For more information on report levels, see keyword REPORT on

page 112.

By using the Administration Assistant program provided with Data Protection for

SAP, you have access to detailed performance information that helps you optimize

your systems. You can also monitor the backup status across all of your SAP

database servers. For more information see Chapter 8, “Installing and Using the

Administration Assistant for Data Protection for SAP,” on page 63.

The information provided by the Administration Assistant can be included in

XML- or HTML-format reports for display and printing. For more information on

the creation of reports see Chapter 10, “Reporting on Data Protection for SAP

Activities,” on page 93. In addition you can retrieve backup status information

such as success or failure of a backup across all of your SAP instances.

Monitoring the Backup Status

The Administration Assistant allows you to monitor the backup status of multiple

SAP database servers via a graphical user interface. For details, see Chapter 8,

“Installing and Using the Administration Assistant for Data Protection for SAP,”

on page 63.

Performance Analysis

The Administration Assistant provides performance data for all components

involved in the data transfer. It supports the analysis of performance information

with graphical representations that help to locate bottlenecks and to exploit

resources efficiently. For details, see Chapter 9, “Balancing Your System,” on page

83.

The Administration Assistant supports the simulation of both backup and restore

operations. In this way, the effects of configuration changes as well as the restore

of a production backup can be tested without compromising the productive

system. For details, see Chapter 9, “Balancing Your System,” on page 83.

Tracing

Data Protection for SAP can write trace information to a file to help analyze

problems. You should contact your DP for SAP support before you use this

function.



Using Data Protection for Snapshot Devices to Minimize Backup and

Restore Windows

Although Data Protection for SAP provides extensive methods to minimize

downtime, your service level agreements for business-critical databases might

demand even faster recovery operations. Data Protection for SAP, together with an

SAP-enabled component of the companion product IBM Tivoli Storage Manager for

Advanced Copy Services Data Protection for Snapshot Devices (formerly known as Data

Protection for FlashCopy Devices for SAP) allows you to perform backups and

restores if you are running your SAP database on IBM FlashCopy® devices (such as

IBM DS6000™ or DS8000™, IBM SAN Volume Controller (SVC), IBM Enterprise

Storage Server® (ESS)), or IBM System Storage™ N series devices with snapshot

capability. By using these features, you can keep your production downtime to a

minimum by exploiting the point-in-time copy functions offered by these devices.

More information on Data Protection for Snapshot Devices can be found at:

http://www.ibm.com/software/tivoli/products/storage-mgr-advanced-copy-services/

.

Archiving Inactive Data

DP for SAP is designed for operational backups, i.e. a database image is stored on

a bit level. This method is NOT at all recommended for true, long-term archiving.

Outdated backups need to be restored into exactly the same environment they

were initially taken from in order to access the data from within SAP applications.

This would require keeping old versions of SAP, OS, database and TSM to rebuild

this environment and cannot be viewed as a reliable process.SAP, instead, provides special archiving functions included in its application

modules to generate so-called business documents for displaying information with

long term retention requirements. These business documents are

format-independent and can be used for auditing and other legal purposes.

Archived data can then be removed from the operational database to trim its size

and, as a result, reduce the backup / restore windows.

Another IBM product, DB2 CommonStore for SAP,1 connects with the SAP

interface ’ArchiveLink’ using TSM as an external archive for

v inactive data (data retention)

v printlists (e.g. reports)

v outgoing documents (e.g. printed output like invoices, bills)

v incoming documents (e.g. digitized fax, scanned letters, audio)

v local documents (e.g. text, spreadsheets, pictures, graphics)

v inactive data

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

information.

For more information on DB2 CommonStore for SAP

1, see: http://www.ibm.com/software/data/commonstore/sap/.

1. The ’DB2 CommonStore for SAP’ product is database independent and therefore can also be used with Oracle.



|

|

|||||||||||

|

|

|

http://www.ibm.com/software/tivoli/products/storage-mgr-advanced-copy-services/

http://www.ibm.com/software/data/commonstore/sap/

http://www.ibm.com/software/data/commonstore/sap/

Part 2. Installing and Using Data Protection for SAP


Chapter 4. Installing or Upgrading Data Protection for SAP

DP for SAP must be installed on any system that is to be used as an SAP database

server. In order to set up DP for SAP, do the following:

1. Check that the DP for SAP package is complete. See the README.1ST file on

each CD (or CD image) for a description of the contents.

2. Make sure that the requirements are met.

For details, see “Prerequisites for the Installation of Data Protection for SAP”

below.

3. Get planning information.

For details, see “Installation Planning for Data Protection for SAP” on page 26.

4. Install the DP for SAP Administration Assistant. This software is optional but

highly recommended. It should be installed prior to Data Protection for SAP so

that the latter can connect to it automatically as part of its installation

procedure.

For details, see Chapter 8, “Installing and Using the Administration Assistant

for Data Protection for SAP,” on page 63.

5. Install Data Protection for SAP.

For details, see “Installing Data Protection for SAP” on page 26.

6. Perform post-installation steps as described in “Post-Installation Steps” on page

32.

7. Verify the installation.For details, see “Verifying the Installation” on page 33.

If you are going to do an upgrade installation, see page 26.

Data Protection for SAP can be installed and operated for SAP systems with Oracle

databases employing a standard file system or raw logical volumes.

Differences Between UNIX or Linux and Windows Systems

There are only small differences between the UNIX or Linux and Windows

versions of Data Protection for SAP. One of these differences is that UNIX or Linux

uses the path separator ″/″ compared with ″\″ for Windows and that the drive

letter is specified for Windows. Non-trivial differences between the UNIX or Linux

and Windows versions of Data Protection for SAP will be mentioned explicitly.

Prerequisites for the Installation of Data Protection for SAP

The following products must be installed before you can start setting up Data

Protection for SAP:

v Oracle Database,

v SAP R/3 or SAP e-business Solution, based on Oracle,

v Tivoli Storage Manager (TSM),

v An operating system at a level supported by SAP and the Tivoli Storage

Manager client.

For hardware and software prerequisites, as well as product versions supported

and maintenance levels required by the current version of Data Protection for SAP


and the Administration Assistant, refer to the Release Notes file in the Tivoli

Information Center.(see “Where to Find More Information” on page xi)

For information on SAP functions, product versions, and maintenance levels that

are compatible with your version of SAP R/3 or SAP, consult SAP support, for

example via the SAP Service Marketplace at: http://service sap.com/.

For information on configuration of the Tivoli Storage Manager API client, refer to

Appendix H, “Preparing Tivoli Storage Manager for DP for SAP,” on page 181.

TCP/IP must be ready for communication between the Tivoli Storage Manager

server and the Tivoli Storage Manager client.

In case Data Protection for SAP is to be installed on a distributed file system, the

root user needs read and write access to the fle system for the duration of the

installation. For more information on the installation in a distributed file system,

refer to: Appendix D, “Using DP for SAP with a Distributed File System on AIX,”

on page 163.

Installation Planning for Data Protection for SAP

When starting the installation procedure, be prepared to provide the required

information. For your convenience, an installation planning table is available in

Appendix E, “Installation Planning Sheets,” on page 167 and in file form in

planning_sheet (UNIX and Linux) or planning_sheet.txt (Windows) in the

installation directory. There is a separate planning sheet for the Administration

Assistant.

After you have ensured that all prerequisites have been met and the installation

planning steps were followed, the installation process can begin. This includes:

1. Installing the software

2. Performing post-installation steps

3. Verifying the installation with a backup and restore run

Installing Data Protection for SAP

The installation packages are located on the Data Protection for SAP CD-ROMs

and also on the IBM public FTP server. Images of the CD-ROMs can also be

downloaded via Passport Advantage.

Initial installations must always be done from the CD-ROM or image. Refer to the

file README.1ST in the root path for information on where to find documents on the

CD or image, and follow the appropriate installation description below.

If you are going to upgrade from an earlier version of Tivoli Data Protection for

R/3 or Data Protection for SAP in your environment, you have the option to either

upgrade from the product CD-ROM or image, or to download the latest version

from the IBM FTP server. See

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforEnterpriseResourcePlanning.html

For the specific procedure for upgrading from an earlier version, refer to

“Upgrading (Migration)” on page 34.

Installing or Upgrading Data Protection for SAP


|||||

|

|||

|||

||||||

||

Installing Data Protection for SAP on UNIX (AIX, HP-UX,

Solaris) or Linux

Data Protection for SAP for these operating systems is delivered as a single

executable file for each platform. These installation packages are provided on a CD

or CD image, or also on the IBM FTP server.

The packages are named as follows:

v For a CD or CD image, the name has the format:

<version>-TIV-TSMERPORA-<platform>

See the README.1ST file in the root directory of the CD or CD image for a list

of its contents.

v Packages on the FTP server contain 'FTP' prior to the platform designation.

The package files have an extension appropriate to the platform and are

executable.

When you invoke the file, you will be guided through the Data Protection for SAP

setup procedure. To ensure that the setup procedure is carried out properly, read

the following description carefully and follow the guidelines on the panels that are

displayed during setup.

Shared libraries have different file extensions on different UNIX or Linux

platforms. Within the following the section, the file extensions of shared libraries

are represented as ’<ext>’. Replace this text with the extension applying to your

platform:

Table 1. File Extensions for Shared Libraries

Operating System Extension

AIX a

HP-UX sl

Linux so

Solaris so

In the following description you have to replace the directory name ora<bit> in

the installation path. Depending on the version of DP for SAP you have installed,

you must replace it with

Directory name Bit-width version of DP for SAP

ora 32

ora64 64

To install Data Protection for SAP on a UNIX or Linux system, do the following:

1. Read the Release Notes for Data Protection for SAP (see “Where to Find More

Information” on page xi).

2. Log in as the root user on the SAP database server machine.

3. (RMAN) If you will also install the RMAN interface, install Tivoli Storage

Manager API Client on your SAP database server (see “Configuring the Tivoli

Storage Manager Clients” on page 185).

4. Ensure that you have set the DISPLAY variable correctly, because the installer

guides you through the installation via a graphical X-Window.


Chapter 4. Installing or Upgrading Data Protection for SAP 27

|

|

|||

|

|

|

||

|

||

||||

||||

||

||

||

||

||

|||

|||

|||

||

|||

|

||

|

|||

||

For alternate ways of installing, see “Special Installation” on page 35.

5. Invoke the installation file for DP for SAP that fits your operating system and

your Oracle database.

6. If the RMAN interface was elected:

a. Set the DP for SAP password for Tivoli Storage Manager (see “Modifying

the Handling of the TSM Password” on page 48).

b. Ensure /usr/lib is in the library path environment of your system.

c. Customize the SAP backup profile init<SID>.sap for use with RMAN.

Insert the following:

backup_dev_type=rman_util

rman_parms="ENV=(XINT_PROFILE=<path>/init<SID>.utl,PROLE_PORT=<portnumber>,&BR_INFO)"

The appropriate ProLE port number can be found in the /etc/services file.

Look for port name tdpr3ora or tdpr3ora64.

7. If RMAN support was not selected during the installation process, include the

following links:

cd $ORACLE_HOME/rdbms/lib

ln -s /usr/tivoli/tsm/tdp_r3/ora/libtdp_r3.<ext> /usr/lib/libobk.<ext>

ln -s /usr/lib/libobk.<ext> $ORACLE_HOME/lib/libobk.<ext>

8. Check the summary at the end of the installation dialog. In the summary,

among other information, you will find the installation path of DP for SAP.

Installation results are also logged in the installation log named log.txt located

in the installation path.

During installation, the following modifications are done to your system

automatically:

v an entry is created in /etc/inittab to start the background process ProLE

v an entry is created in /etc/services needed for internal communication.

After the installation, the following files are available on your system:

v In the installation path of DP for SAP:backintprolecreateinfo

backfm

initSID.bkilibtdp_r3.<ext>

archive.ksh

backup.ksh

crontab.sample

dsm.optdsm.sys

gensortfile.sh

SanFSsetupFS.sh (AIX only)inclexcl.list

README

README_TSMERP<version><language>.html

TIPHINTS

agent.lic (Only after installation from CD-ROM or CD image. This file is not

present in the packages available on the FTP server.)A folder named _uninst is also created, which contains several files.



|

||

|

||

|

||

||||

||

||

|||||

||||

||

|

|

|

|||||||||||||||||||||

v The DP for SAP configuration files under the SAP directories (typically,

/oracle/SID/dbs) are as follows:

init<SID>.utl

init<SID>.bkiagent.lic (copy of file in installation directory).

Verifying the RMAN Setup on UNIX and Linux Systems

If you elected to implement the RMAN interface, perform the following steps:

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>This does not apply when setting up Oracle RMAN with Data Protection for

SAP installed in a distributed filesystem. For information on the setup with a

distributed filesystem, refer to “Setting up DP for SAP with Oracle RMAN in a

Distributed File System in an Adaptive Computing Environment” on page 164.

2. Remove the library in /$ORACLE_HOME/rdbms/lib/libobk.<ext>.If you are running a 64–bit Oracle 8.x database system, also check in

/$ORACLE_HOME/rdbms/lib64/.

3. The shared library must have the same bitwidth as the installed Oracle version:

if you have a 64–bit Oracle running on AIX 5.2 64–bit, you need to install the

64–bit version of DP for SAP.

If you have a 32–bit Oracle running on a 64–bit AIX 5.1, you need to install the

32–bit version of DP for SAP.

Both versions of DP for SAP can coexist on one machine.

4. Examine the sbtio.log located in the directory specified in the user_dump_dest

keyword within the Oracle profile init<SID>.ora. This file is usually located at

oracle/SID/saptrace/usertrace/sbtio.log.

5. Check the log file sbtio.log for lines starting with BKI. The first message for

each RMAN session is:

BKI7060I: Data Protection for SAP <version and build number> session: process ID

If you cannot find 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 the

environment variable DSMI_LOG or in the file denoted by keyword

ERRORlogname in the first stanza of file dsm.sys.

7. To get a Tivoli Storage Manager API trace file, set the following entries in the

client system options file dsm.sys:

tracefile /<path>/<trace file>

traceflags api api_detail config policy

8. On UNIX or Linux operating systems, an additional softlink may help in

/usr/lib for ’libtdp_r3.<ext>.1’ to /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>.

ln -s /usr/tivoli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libtdp_r3.<ext>.1

9. See also “RMAN Problem Resolution” on page 155.

Installing Data Protection for SAP on Windows

DP for SAP for Windows is delivered as a single executable file for each platform.

These installation packages are provided on a CD or CD image, or also on the IBM

FTP server.



|||||

||

|||||||

|||

|||

||

|

|||

|||

||

|||

||

||||

|||

|||

|

|

|||

The packages are named as follows:

v On a CD or within a CD image, the name is:

<version>-TIV-TSMERPORA-<platform>

The files are executable and have an ’.exe’ extension.

See the README.1ST file in the root directory of the CD or CD image for a list

of its contents.

v Packages on the FTP server contain 'FTP' prior to the platform designation.

To install DP for SAP on a Windows system, do the following:

1. Read the Release Note provided for DP for SAP (see “Where to Find More

Information” on page xi).

2. Log in as a user with Administrator authority on the SAP database server

machine.

3. If the RMAN interface is to be installed:

a. Stop the service OracleService<SID>.

b. Install the Tivoli Storage Manager API Client on your SAP database server

(see “Configuring the Tivoli Storage Manager Clients” on page 185).4. In Windows Explorer, navigate to the directory where the installation package

is located.

5. Invoke the DP for SAP executable and follow the instructions of the installation

dialog.

6. If the RMAN interface was elected:

a. Set the DP for SAP password for Tivoli Storage Manager (see “Modifying

the Handling of the TSM Password” on page 48).

b. Customize the SAP backup profile init<SID>.sap for use with RMAN.

Insert the following:

backup_dev_type=rman_util

rman_parms="ENV=(DSMI_DIR=<drive>:\<path>, DSMI_CONFIG=<drive>:\<path>\

<client options file>,DSMI_LOG=<drive>:\<path>,XINT_PROFILE=<drive>:

\<path>\init<SID>.utl,PROLE_PORT=<portnumber>,&BR_INFO)"

The appropriate ProLE port number can be found in the file

<drive>:\WINNT\system32\drivers\etc\services

Look for port name tdpr3ora or tdpr3ora64.

c. Restart: OracleService<SID>.7. Check the summary at the end of the installation dialog. In the summary,

among other information, you find the installation path of DP for SAP.

Installation results are also logged in the installation log named log.txt

located in the installation path.

During installation, the following modifications are done to your system:

v for the background process ProLE a service is created.

v an entry is created in %WINDIR%\system32\drivers\etc\services needed for

internal communication.

After the installation, the following files are available on your system:

v In the installation path of DP for SAP:backint.exe

createinfo.exe



|

|

|

|

||

|

|

||

||

|

|

||

||

||

|

||

||

||||||

|

|

|

|

||||

|

|

||

|

|||

prole.exe

orasbt.dll

backfm.exearchive.cmd

backup.cmd

dsm.opt

server_a.opt

server_b.optinclexcl.list

schedule.sample

README.txtREADME_TSMERP<version><language>.htmlTIPHINTS

agent.lic (Only after installation from CD-ROM or image. Not present on the

FTP server.)A folder named _uninst is created, which contains several files.

v In the path of the DP for SAP configuration files:

initSID.bkiinitSID.utlagent.lic (Only after installation from CD-ROM or image. Not present in the

Web package.)

Verifying the RMAN Setup on Windows Systems

If you elected to implement the RMAN interface, perform the following steps:

1. Examine the sbtio.log located in the directory specified in the user_dump_dest

keyword within the Oracle profile init<SID>.ora.. If no file sbtio.log exists

after an operation with RMAN or no line starting with the letters ’BKI’ exists

within an existing sbtio.log,

a. Check if the shared library orasbt.dll was found and loaded by Oracle.

b. Put the shared library file orasbt.dll into the directory %ORACLE_HOME%\bin.

This is the directory where oracle.exe resides.

c. Stop the service OracleService<SID> and restart it.2. Examine the dsierror.log located in the directory specified with the

environment variable DSMI_LOG.

3. To get a Tivoli Storage Manager API trace file, set the following entries in the

client options file:

tracefile <drive>:\<path>\<trace file>

traceflags api

4. See also “RMAN Problem Resolution” on page 155.

Implementing Configuration Files on Remote Shares

A process on Microsoft® Windows which is started as a regular service runs by

default under the ID of the ’local system account’. This means that the process

runs on the local system with Administrator privileges, but on remote systems the

session is opened without credentials, and therefore no permissions. See Microsoft

knowledge base article 132679 for details:

http://support.microsoft.com/kb/132679

This is the reason that ProLE cannot access files residing on a remote share. It is

irrelevant whether the share was mapped to a local drive letter or is accessed in

UNC notation (\\server\path\filename). As of V5.4, DP for SAP accepts UNC

notation for the profile and infile (passed via the backint command line), but not



||||||||||||||||

|||||

||

||||

|

||

|

||

||

||||

|

||||||

|

||||

for all the files specified within the profile. These files will be opened by ProLE,

which by default has no permission to access remote shares, as explained above.

To enable ProLE to access such files on a remote share, the following steps must be

performed:

1. Map the share where the configuration files reside to a local drive letter.

2. Modify the profile (.utl) to refer to the pathnames on the mapped drive.

3. Modify the ProLE service such that it no longer runs with a ’local system

account’ but as an account with permissions to access the mapped drive. Note

that this might have other implications when using a regular account. For

example, when the password for this account expires or is changed, the service

will no longer be able to start.

4. Restart the ProLE service to activate the changes.

Post-Installation Steps

After successfully completing the installation dialog for DP for SAP, you need to

perform the following steps in order to get a properly running system:

1. Review the TSM Option files.

2. Set the initial password.

3. Verify the installation.

Review of the TSM Options Files

The TSM client options files need to be checked in order to make sure that they

contain the correct server name as specified in the server statement of the

init<SID>.utl file, and that the parameters are set correctly. These depend on the

password method selected. (See “Modifying the Handling of the TSM Password”

on page 48).

On UNIX or Linux the TSM server definition is typically done in the TSM client

system options file (dsm.sys). The server stanza specified in dsm.sys must match

the entry in init<SID>.utl.

On Windows you have to define a client options file <servername>.opt. This file

must be in the directory containing dsm.opt. <servername> is the name you

specified in init<SID>.utl.

Set the Password

DP for SAP should be installed after the TSM installation has been completed. TSM

provides different password methods to protect data. DP for SAP must use the

same method as specified within TSM. When DP for SAP is installed, it is assumed

that the password method selected during the TSM installation was manual

password handling (PASSWORDACCESS prompt). The default parameters for DP for

SAP are set according to this assumption. If a different password method is set

within TSM, refer to “Password Handling” on page 188 in order to adjust the DP

for SAP parameters.

To be able to work with DP for SAP, you have to provide DP for SAP with the

password for the TSM node.This is a manual step on the shell:

v Log on as the Oracle user.

v Enter the following command

for Windows:



||

||

|

|

|||||

|

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

for UNIX or Linux:

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

Note: On Windows, the path can also be specified in UNC notation (for

example: -p \\SERVER_A\dpsap\init<SID>.utl

v Enter the password when prompted.

Note: On HP-UX only, the password is limited to 8 characters. Ensure that the

TSM password for HP-UX clients does not exceed this limit.

Verifying the Installation

Preparing for the Verification

Before verifying the installation, make sure that:

v the SAP Backup profile is configured properly. This profile can be found on

UNIX or Linux systems in the path $ORACLE_HOME/dbs and on Windows systems

in the path %ORACLE_HOME%\database.

This configuration refers to the following keywords within that profile:

backup_type

Identifies the default type of the database backup. This parameter is

only used by BRBACKUP (default is offline).

backup_dev_type

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

order to use the backint interface this parameter must be set either to

'util_file' or 'util_file_online' (see table below). For RMAN, this

parameter is set to 'rman_util'

util_par_file

This parameter specifies where the parameter file, which is required for

a backup with an external backup program, is located.

rman_parms

When backup_dev_type is set to "rman_util", this parameter defines

various parameters required for RMAN operation.

DP for SAP supports, for example, the combinations of the keywords

backup_dev_type and backup_type shown in the table below.

Table 2. SAP Backup Profile Parameter Combinations

Operation backup_dev_type backup_type

Offline backup util_file offline

Online backup util_file online

Online backup with

individual tablespace

locking

util_file_online online

Online backup via RMAN rman_util online



|||

|||

To carry out online backups with individual tablespace locking with the external

backup program DP for SAP, the SAP Backup profile parameter must be set or

changed as shown below:

backup_type = online

backup_dev_type = util_file_online

util_par_file = <ORACLE_HOME>/dbs/init<SID>.utl

Executing the Verification for Initial and Upgrade Installations

To verify and test the installation, it is recommended that you try out a small

backup procedure (tablespace backup) using BR*Tools and start a full online or

offline backup using BRBACKUP as shown below.

brbackup -c -t online

brbackup -c -t offline

It is strongly recommended that you do a restore/recovery of the complete SAP

database (using BR*Tools). A good method to prepare for this is to first run a

complete offline backup using BRBACKUP.

Step by step scenarios for backup or restore/recovery procedures of an SAP Oracle

database using DP for SAP can be found in the IBM Redbooks® publication R/3

Data Management Techniques Using Tivoli Storage Manager, SG24–5743.

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

For backup tests, the BR*Tools utilities BRBACKUP and BRARCHIVE should be

used. For restore or recovery it is recommended that only BRRECOVER be used.

Upgrading (Migration)

Upgrading Data Protection for SAP

Note: The format of the configuration file (.bki) was changed with release V5.4.

The software accepts the previous format and converts it automatically.

If it is necessary to fall back to a version earlier than 5.4, the old format can

be recovered by overwriting the new file with the empty file provided with

the previous version and then initializing it (by setting TSM passwords, for

example). However, the information about the current backup number will

be lost. This means that more backup versions must be retained for a certain

period of time than is specified by the MAX_VERSIONS parameter.

In order to upgrade DP for SAP from an earlier version of Data Protection for SAP,

do the following:

1. Check that the DP for SAP package is complete. The installation packages are

provided on CD-ROMs or CD images downloadable from Passport Advantage

and are also available on the IBM FTP server. See the release notes file in the

Tivoli Information Center (“Where to Find More Information” on page xi) for

information supplementing this manual.

2. Check the readme files and release notes for incompatibilities between your

installed version and the new version. Make sure, that data backed up with an

older version of Tivoli Data Protection for R/3 or DP for SAP can still be

restored with the version you are going to install. ,



v Data that was backed up with Tivoli Data Protection for R/3 Version 2.7

must be restored with Tivoli Data Protection for R/3 Version 3.1 or Version

3.2.

v Data that was backed up with Tivoli Data Protection for R/3 Version 3.1 or

Version 3.2 or Data Protection for SAP.com Version 3.3 can be restored with

Data Protection for SAP.com Version 3.3. or higher. 3. Make sure that the requirements for the new version of DP for SAP are met.

For details, see “Prerequisites for the Installation of Data Protection for SAP”

on page 25.

4. Get or retrieve planning information. For details, see “Installation Planning for

Data Protection for SAP” on page 26.

5. We recommend a full backup of the SAP database before upgrading to the

new version.

6. Uninstall the old version. For this procedure, see “Uninstalling Data Protection

for SAP” on page 36.

7. Install the new version of DP for SAP. For details, see “Installing Data

Protection for SAP” on page 26.

8. Verify the installation. For details, see “Verifying the Installation” on page 33.

9. We recommend a full backup after upgrading to the new version.

10. Following an upgrade and subsequent RMAN setup on Windows, start (or

restart) service OracleService<SID> in order to activate the new DP for SAP

environment.

Special Installation

Silent Installation

Installation can be done from the command line. For a preparation for silent

installation, you have to have the system generate (record) the installation options

in a file using the "- options-record" switch:.

<package file name> -options-record <options filename>

This creates an options file that can be checked easily and modified for use in

installing various systems.

To perform a silent installation, the install package is called with the prepared

options file as follows:

<package file name> -options <filename> -silent

Note:

Options required for a silent installation are dependent on the version of Data

Protection for SAP and may vary with different modification levels.

Therefore, when installing an upgrade it is recommended to record a new

options file before performing a silent installation of this new version.

Console Installation

To support target systems without a window manager, the setup program supports

deploying an installation in console mode. An installation running in console mode



suppresses the graphical wizard panel display available with a GUI installation.

Instead, user data entry and status messages are displayed on the console or in the

command prompt window.

To start the console installation, enter the following command:

<package file name> -options <filename> -is:javaconsole -console

In addition, you can also record the installation options in a file. You do this by

issuing following command:

<package file name> -options-record <filename> -is:javaconsole -console

Firewall Installation

If you need to install DP for SAP remotely through a firewall and if the TCP port

for X11 communication is not enabled, use the console installation as described in

“Console Installation” on page 35.

Uninstalling Data Protection for SAP

Before upgrading the old version of DP for SAP to a higher level, you have to

uninstall the old package on your system as described in the following sections.

Your profile and configuration files are retained. If you had installed the old

version of Data Protection for SAP also for databases other than Oracle, you only

have to uninstall that old version of DP for SAP for Oracle.

Uninstalling the Old Version of DP for SAP under UNIX or

Linux

To uninstall the old version of DP for SAP, perform the following steps:

1. Log in as root user on the SAP database server machine.

2. Make sure that the DISPLAY variable is set correctly, because the uninstall

procedure requires a graphical X-Window.

3. Make sure the old version of DP for SAP is not running.

4. Call the uninstaller executable and follow the instructions of the uninstall

procedure. The executable is located in one of the following directories:

v AIX 32-bit

/usr/tivoli/tsm/tdp_r3/ora/_uninst/uninstaller.bin

v AIX 64-bit:

/usr/tivoli/tsm/tdp_r3/ora64/_uninst/uninstaller.bin

v other UNIX 32-bit or Linux 32-bit

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

v other UNIX 64-bit or Linux 64-bit

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

Uninstalling the Old Version of DP for SAP under Windows

To uninstall the old version of DP for SAP on a Windows NT®, Windows 2000, or

Windows 2003 machine, perform the following steps:

1. Log on as user with administrator authority on the SAP database server

machine.

2. Ensure that the old version of DP for SAP is not running.



3. Select Start → Settings → Control panel.

4. Click on Add/Remove Programs.

5. Select the old version of DP for SAP and click on Remove.

6. Follow the instructions of the uninstall procedure.



Chapter 5. Adjusting Your System

This chapter is intended to help you find the configuration of Data Protection for

SAP that best fits your needs.

You may want to adjust Data Protection for SAP to:

v Optimize the performance of your data protecting environment, or to

v Change the way Data Protection for SAP interacts with components like Tivoli

Storage Manager, RMAN, or the Data Protection for SAP Administration

Assistant.

General Performance Considerations

A simplistic model of the data transfer via Data Protection for SAP is comprised of

three components (see Figure 7):

v the SAP database server

v the network

v the TSM server also known as backup server

A continuous stream of data is generated between these components for the

backup or restore of data. The weakest link in this chain limits the overall data

rate.

The following general guidelines result from experience gathered with many actual

installations and should be considered for designing an efficient backup/restore

infrastructure and process.

Figure 7. Data Transfer


Database Server Considerations

In most cases, the production (SAP database) server is the most critical component

for data transfer when the various techniques of parallelism are applied (see

’Adjustments to DP for SAP for Improving Performance of Data Transfer’, below).

Special attention should be given to the following items:

v CPU power. Data transfer, as well as data compression or employing local or

LAN-free backup cause additional load on the CPU of the database server on

top of the application load (online backup). In many environments, CPU power

of the database server is the most critical constraint. The CPU load for LAN-free

backups (Managed System for SAN) can be significantly reduced by deploying a

highly efficient data transfer method available with Rel. 5.3. For details, refer to

“Buffer Copies” on page 46.

v I/O paths. When setting up your I/O system for maximum data rates, consider

using fast disk attachments, for example via internal busses like PCI. File system

features, like caching or reading ahead, have an effect on data rates as well and

should be adapted to the specific characteristics of backup/restore with its large

files and data volumes.

v Volume Manager settings. Volume mirroring by Volume Manager can slow

down the data transfer during restore significantly. For a fast restore, we

recommend to turn off mirroring during the restore.

v Disk layout. The file layout of the database can have a significant impact on

maximum achievable data rates. DP for SAP allows parallel access to database

files during backup and restore. In order to exploit this feature, data should be

spread across several disks.

v Size of database. The size of a database should be trimmed by offloading

inactive data to an external archive. For archive support, refer to the companion

product DB2 CommonStore for SAP

2 (see “Archiving Inactive Data” on page 21).

v Size of database files. Using multiplexing with the file interface yields the best

results when the files to be multiplexed are of the same size. DP for SAP tries to

find files of similar sizes for multiplexing. Therefore, we recommend to define

rules for the sizes of database files ensuring that similar files are of the same size

and avoiding many different file sizes.

v Backup types. Online backups save database files, control files, and redo logs

non-disruptively. On the other hand, more data is saved to redo log files during

an online backup. The amount of data saved to redo logs during an online

backup may be decreased when using the file-online mode provided by SAP,

while such a backup will take longer. Incremental backups will reduce the

backup time and the amount of data to be sent to the backup server while

restore time may be increased. For incremental backups, Oracle RMAN must be

employed.

For details on backup options, refer to your Oracle and SAP documentation.

Network Considerations

Consider the following items when deciding on the network setup:

v LAN-free backup. The LAN-free backup is intended to reduce the load on the

network and on the TSM server and to yield higher data transfer rates than a

network backup. Make sure that the capacity of the fiber channel adapters to the

SAN can handle the composite data transfer rates of disk reads and tape writes.

v Network bandwidth. Our experience shows that the effective throughput

capacity is approximately half of the theoretical network bandwidth. For

2. This product is database independent and therefore can also be used with Oracle.

Adjusting Your System


high-speed networks such as Gigabit Ethernet LAN, the network adapters most

likely limit the throughput rather than the network itself.

v Network topology. Consider implementing a dedicated backbone network for

backup and restore, apart from the user LAN.

v TCP options. Make sure to use the TCP options appropriate for your

environment. For more specific hints, refer to Appendix L, “Hints and Tips for

Network Settings,” on page 205.

v Multiple Paths. Data Protection for SAP allows you to increase the overall

throughput rate to the backup server by specifying multiple network paths. For

details, see “Multiple Network Paths” on page 44.

More hints on network settings are given in Appendix L, “Hints and Tips for

Network Settings,” on page 205.

Backup Server Considerations

Note: For all backup activities, Data Protection for SAP uses the archive function of

IBM Tivoli Storage Manager.

Consider the following when setting up the TSM server:

v Dedicated backup server. A dedicated backup server allows sharing of resources

and yields most efficient resource utilization.

v CPU power. Observations show that for a given data throughput the CPU load

on the backup server is approximately 60% of that on the database server.

Therefore, backup server CPU power is not quite as critical as the CPU power of

the database server. However, if you are going to allow several clients to access

a single TSM server, demands on the TSM server CPU do increase.

v Storage hierarchy. Backup of data files (large files) should be directed to tape in

order to achieve the highest transfer rates. If disks must be used, it is

recommended to use one disk pool per session.

Small files like log files should be directed to disk storage first and then be

migrated to tape collectively to avoid excessive tape mounts.

v Parallel sessions. The TSM server allows using several tape drives in parallel to

store data and thus increase overall data throughput. In order to exploit this

feature, the corresponding TSM node must be allowed the appropriate number

of mount points and the device class must be allowed the appropriate

mountlimit.

More information on how to set up TSM for cooperation with Data Protection for

SAP can be found in Appendix G, “Alternate or Parallel Backup Paths and Backup

Servers,” on page 175 and Appendix H, “Preparing Tivoli Storage Manager for DP

for SAP,” on page 181.

Adjustments to DP for SAP for Improving Performance of Data

Transfer

After the primary installation, Data Protection for SAP is configured to send

uncompressed backup data to a TSM server via a single session.


Chapter 5. Adjusting Your System 41

When tuning Data Protection for SAP, there is not a single configuration that is

best for all environments. Rather, you will need to experiment with the following

adjustments in order to find the configuration that works best for you. You may

use function ’View Performance Data’ of the Administration Assistant to find out

about performance characteristics and how they change with your configuration.

For more details on tuning a system with the Administration Assistant refer to

Chapter 9, “Balancing Your System,” on page 83 or you may want to tune your

system in the following order:

1. Optimize the configuration of the database server, the network, and the TSM

server according to your needs. Some hints can be found in “General

Performance Considerations” on page 39.

2. Increase multiplexing. See ″Multiplexing″ below.

3. Increase the number of sessions. See “Multiple Sessions” on page 43.

4. Increase the number of network paths or TSM servers. See “Multiple Network

Paths” on page 44 and “Multiple Servers” on page 44.

Usually, when you start employing parallelism, you will see a gain in performance.

You will want to find the point when this gain is offset by overhead as you

increase the numbers.

For example, when you are working with multiple sessions you will find out that

for a certain number of sessions adding another tape and another session does not

give you any improvement or even decreases performance. This indicates that the

network might now be the bottleneck, and you may want to try multiple network

paths next.

Multiplexing

In order to better exploit the tape drive used for database backup on the backup

server, you may want to try parallel access to data on the database server.

The value of keyword MULTIPLEXING defines the number of files read in

parallel within a single session. Appropriate MULTIPLEXING values are expected

in the range of 1 to 4. The best value for your environment depends on the I/O

rate of your disks, the location of your data on the disks, the network capacity, the

Figure 8. Data Transfer for a Backup / Restore

Figure 9. Multiplexing



throughput rate of the storage media, and the compression factor to be achieved. A

way to determine the optimum MULTIPLEXING value is to analyze DP for SAP

performance with the Administration Assistant. For details, refer to Chapter 9,

“Balancing Your System,” on page 83.

Note: If the value is chosen too high this may result in a noticeable overhead in

thread management offsetting the performance gain.See also keyword MULTIPLEXING on page 111.

Multiple Sessions

Data Protection for SAP allows you to make use of several tape drives

simultaneously in order to increase the transfer rate to or from a Tivoli Storage

Manager server.

The keywords MAX_SESSIONS, MAX_BACK_SESSIONS,

MAX_ARCH_SESSIONS and MAX_RESTORE_SESSIONS are used for defining

the number of parallel sessions to be established with the TSM server for database

backup, archive (backup of log files) and restore. For a detailed description of how

to use these keywords, refer to page 109.

When running a database backup, the data will usually be written directly to tape

drives on the Tivoli Storage Manager server. The parameter specified in the

MAX_SESSIONS keyword must match the number of tape drives used

simultaneously. These must be available to the management class defined as

BRBACKUPMGTCLASS in the DP for SAP profile (see on page 107).

When setting up the Tivoli Storage Manager, be sure to

v not activate collocation in the (tape) storage pool defined for the management

class chosen as BRBACKUPMGTCLASS

v make available as many tape drives for this management class as the number of

sessions defined in MAX_SESSIONS, as multiple accesses to the same tape may

slow down data transfer.

When running BRARCHIVE for log file backups, either disk or tape storage pools

can be utilized. These must be available to the management class defined as

BRARCHIVEMGTCLASS in the Data Protection for SAP profile (see on page 106).

If you are using tape pools as (primary) pools for this management class the same

considerations as for database backups apply. When using disk storage pools, the

following rules apply:

v Several sessions of one BRARCHIVE run can utilize one or two independent

disk storage pool(s).

v Several sessions of BRARCHIVE runs of different databases can simultaneously

utilize one or two independent disk storage pool(s).

Figure 10. Parallel (Multiple) Sessions



|

|

|

The number of storage pools required depends on the number of backup copies

requested for a log file. For details, see keyword REDOLOG_COPIES on page 112.

Multiple Network Paths

Data Protection for SAP allows you to use multiple network connections (paths)

for data transfer between the database server and the backup server.

Parallel paths can be used to eliminate network bottlenecks. For each additional

path, additional network adapters are required on both the production and the

backup server. For each adapter of the backup server, a server statement must be

entered in the Data Protection for SAP profile (see keyword SERVER on page 112).

Make sure that the value of keyword MAX_SESSIONS is not greater than the sum

of all SESSION values of the SERVER statements of servers that are available for

concurrent use.

The setup for multiple (parallel) network paths is described in detail in

Appendix G, “Alternate or Parallel Backup Paths and Backup Servers,” on page

175.

Multiple Servers

Data Protection for SAP allows you to use multiple backup servers.

Multiple servers can be used by DP for SAP to eliminate backup server bottlenecks

by distributing backup data among two or more backup servers.

Figure 11. Parallel (Multiple) Paths

Figure 12. Multiple Servers



Note that for each additional path additional network adapters are required on

both the database and the backup server. For each adapter of each backup server, a

server statement must be entered in the Data Protection for SAP profile (see

keyword SERVER on page 112).

Make sure that the value of keyword MAX_SESSIONS is not greater than the sum

of all SESSION values of the SERVER statements of servers that are available for

concurrent use.

If used with RMAN, the number of SESSIONS configured for each SERVER must

be greater than or equal to the number of sessions configured for restore

(MAX_SESSIONS). Otherwise Oracle RMAN may request more objects in parallel

from the same server than sessions are configured for that server.

The setup for parallel servers is described in detail in Appendix G, “Alternate or

Parallel Backup Paths and Backup Servers,” on page 175.

Compression

By compressing zero-byte blocks, a very simple, but fast compression method, Data

Protection for SAP decreases the amount of data to be sent to the TSM server.

Although compression does create some additional CPU load on the database

server it might improve performance if the network is the bottleneck. It is efficient

with database files usually containing large portions of null blocks. For details on

how to activate Data Protection for SAP compression, refer to keyword

RL_COMPRESSION on page 112.

Disk Sorting

With Adaptive File Sequencing, Data Protection for SAP tries to ensure that read

operations from disk are truly parallel. For example, with MULTIPLEXING set to 5

and MAX_SESSIONS set to 3, Data Protection for SAP can backup 15 files at a time

to 3 different tapes. Due to disk sorting, the 15 files are selected from different

disks whenever possible.

However, some storage subsystems hide the information required for disk sorting.

In this case, the administrator can supply information on the locations of files by

providing a manual sort file. For more information refer to keyword SORT_FILE

on page 113.

The information required for sorting is determined by the 'createinfo' program. As

of V5.4, 'createinfo' is no longer run automatically on UNIX or Linux (since most

customers use storage subsystems). If performance suffers or customers want to

retain the previous functionality (because of directly attached disks), this can be

achieved by starting the 'prole' process with the 'c' option.

Figure 13. Null Block Compression



1. As user root, modify the entry in /etc/inittab (add '-c'), for example

.../tivoli/tsm/tdp_r3/ora/prole -p tdpr3ora -c ....

2. Activate the change with 'init q'.

This simplifies, or even eliminates the need for, the start/stop scripts for HACMP™

takeover.

Buffer Copies

Data Protection for SAP uses internal buffers to store and exchange data with the

IBM Tivoli Storage Manager. When passing data from one component to another,

data buffers are copied by default. DP for SAP allows to prevent copying the data

buffers by passing on the original data buffers. This reduces the CPU load of the

database server. However, if client compression and/or client encryption are

activated in the Tivoli Storage Manager options file (dsm.sys or dsm.opt on UNIX

or Linux or <server>.opt on Windows), buffer copies cannot be prevented.

See also keyword BUFFCOPY on page 107.

Buffer Size

Data Protection for SAP allows to tune the size of its internal data buffers. These

buffers are used for both reading from disk and passing data to the Tivoli Storage

Manager client API.

It is recommended to optimize the buffer size for disk I/O. The default buffer sizes

are 131072 (128K) for UNIX or Linux and 32768 (32 K) for Windows systems. In

most cases, the default settings yield acceptable results.

For EMC disk subsystems, the best transfer rates have been achieved when the

buffer size was set equal to the stripe size.

See also keyword BUFFSIZE on page 107.

Before increasing the size of internal buffers make sure that sufficient storage is

available for the number of buffers acquired by Data Protection for SAP. This

number correlates to the number of sessions requested. By activating compression,

the number of buffers is doubled.

Adjustments for Interaction with Other Components

Adjustments for the Administration Assistant

In order to make use of the Administration Assistant (highly recommended), you

have to set up a connection between Data Protection for SAP and the

Administration Assistant. This is usually done during installation of Data

Protection for SAP, provided the Administration Assistant was previously installed

(also recommended). If you enter the Administration Assistant information during

installation of Data Protection for SAP, the latter connects and sends data to the

Administration Assistant during backup and restore runs.

If you do not specify the use of the Administration Assistant during installation of

DP for SAP, you can set up the connection at a later time by following the

description given in “Specifying the Administration Assistant Server Component”

on page 47.

For details on the Administration Assistant, see Chapter 8, “Installing and Using

the Administration Assistant for Data Protection for SAP,” on page 63.



Specifying the Administration Assistant Server Component

If you need to specify a new Administration Assistant Server component, perform

the following steps on the SAP database server:

Specifying an Administration Assistant Server component on UNIX or Linux

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

.../prole -p tdpr3ora | tdpr3ora64 <Server component hostname> <port>

where

<Server component hostname> is the name or IP address of the host running the

Administration Assistant Server component and

<port> is the port the Server component is listening to for connects from DP for

SAP (default 5126).

2. Make sure that DP for SAP is not running, and use the kill command to stop

the ProLE daemon. The ProLE daemon will be restarted automatically with the

new parameters.

Specifying an Administration Assistant Server component on Windows

Log in as a user with administrator authority. From a command prompt, issue:

prole -update -p tdpr3ora | tdpr3ora64 <Server component hostname> <port>

where<Server component hostname> is the name or IP address of the host running the

Administration Assistant Server component and

<port> is the port that the Server component is listening to to for connects from

DP for SAP (default 5126).

Adjustments for IBM Tivoli Storage Manager

After the primary installation, Data Protection for SAP is configured to send data

to a single backup server; manual password handling is assumed and Data

Protection for SAP backup version control is turned off. The following describes

the configuration changes necessary to change these initial settings.

Specifying Another Tivoli Storage Manager Server

To add a new Tivoli Storage Manager server to your configuration, you need to

perform the following steps:

1. Add a new server statement to your Data Protection for SAP profile.

2. Adapt the TSM options files as described in “Review of the TSM Options Files”

on page 32.

3. Set and save the TSM password for the new server as described in “Set the

Password” on page 32.

Alternate Network Paths and Servers

When setting up multiple network paths and multiple backup servers you may

decide to use them alternately instead of in parallel. If the number of available

sessions to the various servers as defined in the profile exceeds the maximum

number of sessions allowed Data Protection for SAP will use the first sessions it

can establish, up to the number defined for keyword MAX_SESSIONS (see on

page 109). This will allow backing up data even when some TSM resources, for



example a TSM server or a network interface of a TSM server, are unavailable.

Obviously, the server(s) used for the backup must be available for restoring the

data.

You may also control on what days of the week a specific server is to be used (see

keyword USE_AT on page 114).

Modifying the Handling of the TSM Password

TSM provides the following choices for password handling:

v No password

v Manual password handling

v Automatic password handling

Consider the choices with their implications:

No password required

No authentication is performed on the TSM server level. Each user

connected to the backup server can access Tivoli Storage Manager data

without a password.

This method is only recommended if adequate security measures can be

established otherwise, for example, if Tivoli Storage Manager is only used

for SAP and no other clients are registered, and the respective

authentication and authorization is performed on the operating system

level.

Manual password handling

For each connection to the TSM server, a password is required. Data

Protection for SAP supports manual password handling by storing the

encrypted password in its configuration files. As long as the password

does not expire and is not changed on the TSM server, Data Protection for

SAP automatically uses the stored password when connecting to TSM.

Whenever the password expires or is changed in TSM the new password

must be set again manually with the command

for Windows:


for UNIX or Linux:




This method provides password security and can be set up easily;

however, you need to synchronize password updates in Tivoli Storage

Manager (command update node on TSM server) and Data Protection for

SAP (command as shown above). These steps must also be repeated

whenever the TSM password expires. Therefore, this method is only

recommended during installation and testing, together with a sufficiently

long password expiration period; it is not recommended for production

operation.

If setting the password is to be automated, such as in a script, the option

exists to enter this information in the command line:



backint -p <full path>/init<SID>.utl

-f password serverA:nodeA:passwordA serverB:nodeB:passwordB

where 'passwordA' is the password for TSM node 'nodeA' on TSM server

'serverA'.

Notes:

1. The interactive password prompt is omitted only if the passwords for

all server stanzas in the.utl file are specified.

2. There is a potential security risk involved in recording TSM passwords

in a script.

Automatic password handling

For each connection to the TSM server, a password is required. However,

after the first connection, the TSM password is managed by Tivoli Storage

Manager. The Tivoli Storage Manager client stores the current password

locally. When the password expires, the password will be changed and

stored automatically.If you are planning to use Oracle RMAN and schedule your backups or

restores from a system user different from the database owner, you need to

grant access permissions to your data files on disk for this user.

You need to specify the TSM password currently in effect before you start

using Data Protection for SAP in order to connect to the server for the first

time and whenever the password is changed manually on the TSM server

(command update node). You do this with the command:

for Windows:


for UNIX or Linux:


This method is recommended for an automated production environment.



For details on how to set up any of the password handling methods, refer to

“Password Handling” on page 188.

Backup Version Control

Data Protection for SAP allows you to define the number of backup versions you

want to keep in backup storage. Every time a full backup completes successfully,

the version count is incremented. Subsequent partial, incremental and redo log

backups get the same version number, thus ensuring that the full backup required

for restoring them is still kept.

After each successful full backup, the number of full backups available in backup

storage is checked. If the number of backups to be kept is exceeded, the oldest

backup and all corresponding partial, incremental and redo log backups are

removed from backup storage.



For a partitioned database, backup version control is done on a partition basis.

Therefore, make sure that full backups are initiated at the same time for all

partitions.

If you plan to use this feature, do not employ TSM file expiration at the same time.

For details, refer to keyword MAX_VERSIONS on page 110.

Adjustments for High Availability

Considerations for Using IBM HACMP for AIX

This section is intended to give a short introduction to the way DP for SAP works

internally, thus enabling the user to take actions for HACMP fail-over

configurations. As an example, we use the following configuration, which should

be easily adaptable to others. Here, we use the ’mutual takeover’ configuration,

where each node can take over the other. If the application server and database

server are installed on different hosts, the described actions need to be taken on

the database servers only.

The following figure illustrates the takeover environment:

DP for SAP Internals

Files:

v The installation directory is /usr/tivoli/tsm/tdp_r3.

v Lock files and disk sorting files can be found in /var/tdp_r3.

v There is only one ProLE running on each host (even after takeover).

v Each SAP system has its own Data Protection for SAP configuration files

(init<SID>.utl, init<SID>.bki) in $ORACLE_HOME/dbs.

Dependencies:

v Both hosts should have the same level of Tivoli Storage Manager API installed.

v Both hosts must be Data Protection for SAP.

v On both hosts, the dsm.sys file (in /usr/Tivoli/tsm/client/api/bin/dsm.sys)

must contain all server names required for takeover.

Communication:

Figure 14. Sample Environment for HACMP Takeover



Backint connects to ProLE using the following procedure:

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

v Get the backint service (should be 57321 for the 32-bit version and 57323 for the

64-bit version).

v Connect to 127.0.0.1:<backint service>.

Installation and Setup

Installation:

A prerequisite for installation is a correct setup of the TSM client. The installation

steps for the TSM Backup/Archive Client for AIX can be found in the

documentation Tivoli Storage Manager Installing the Clients.

Defining DP for SAP as an HACMP Application: To enable DP for SAP to

participate in HACMP failover processing, it must be defined as an application to

HACMP. Detailed directions for doing this can be found in the HACMP for AIX

Installation Guide, SC23-4278. A summary follows.

To configure an application for HACMP:

1. Enter the following to start HACMP for AIX system management:

smit hacmp

2. Select Cluster Configuration > Cluster Resources > Define Application Servers

> Add an Application Server.

3. Enter field values as follows:

Server Name

Enter an ASCII text string that identifies the server (for example,

tdpclientgrpA). You use this name to refer to the application server

when you define it as a resource during node configuration. The server

name can include alphabetic and numeric characters and underscores.

Do not use more than 31 characters.

Start Script

Enter the full pathname of the script that starts the server (for example,

/usr/sbin/cluster/events/utils/start_tdpr3.sh). This script is called by

the cluster event scripts. This script must be in the same location on

each cluster node that might start the server.

Stop Script

Enter the full pathname of the script that stops the server (for example,

/usr/sbin/cluster/events/utils/stop_tdpr3.sh). This script is called by

the cluster event scripts. This script must be in the same location on

each cluster node that might stop the server.4. Press Enter to add this information to the HACMP for AIX ODM.

5. Press F10 after the command completes to leave SMIT and return to the

command line.

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

Refer also to the HACMP for AIX Planning Guide V4.4, SC23-4277, for further

information about selecting the HACMP node topology and takeover relationships.

Note that DP for SAP must be in a resource group having a cascading or rotating

takeover relationship. It does not support a concurrent access resource group.



Adding the DP for SAP Application to an HACMP Resource

Group

A final step in enabling Data Protection for SAP for HACMP failover is to define it

to a cluster resource group. Detailed directions for doing this can be found in the

HACMP for AIX Installation Guide. A summary follows.

To define the resources that will be part of a resource group:

1. From the Cluster Resources SMIT screen, select the Change/Show

Resources/Attributes for a Resource Group option and press Enter. SMIT

displays a picklist of defined resource groups.

2. Pick the desired resource group.

3. Press Enter and SMIT displays the Configure a Resource Group screen.

4. Enter values that define all the resources you want to add to this resource

group.

5. After entering field values, synchronize cluster resources.

6. Press F10 to exit SMIT or F3 to return to previous SMIT screens to perform

other configuration tasks or synchronize the changes you just made. To

synchronize the cluster definition, go to the Cluster Resources SMIT screen and

select the Synchronize Cluster Resources option.

The TSM client application should be added to the same resource group that

contains the file systems it will back up. The file systems defined in the resource

group should also be the ones specified in the domain for this client instance in the

client user options file.

Note that both JFS and NFS file systems can be defined as cluster resources,

although NFS supports only 2 node clusters in a cascading takeover relationship.



Sample Stop Script

Depending on the customer installation, the sample stop script may need to ensure

that any backup/restore operation currently in progress is stopped. This means

that any processes launched by brbackup/brarchive for this client instance (that

may be accessing the shared file system(s)) must also be stopped to free resources

like file systems. This may have already been accomplished by the HACMP script

that stops the SAP systems. It may also not be desirable in certain installations and

should be revised.

The stop script is used in the following situations:

v HACMP is stopped.

v A failover occurs due to a failure of one component of the resource groups. The

other members are stopped so that the entire group can be restarted on the

target node in the failover.

v A fallback occurs and the resource group is stopped on the node currently

hosting it to allow transfer back to the node re-entering the cluster.

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

Note: This script is not in its final form. It should be considered pseudo code that

indicates the functions it will perform.

#!/bin/ksh

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

# This sample script is provided for use with DP for SAP 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 -x

fi

# Function to update all disk information for DP for SAP

STOP_PROCESSING()

{

# 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 Data Protecion for Snapshot Devices for SAP,

# this may leave your FlashCopy device in an

# inconsistent state.

# kill –9 `cat /var/tdp_r3/prole.pid ̀

# This stops any running backup or archive process.

STOP_PROCESSING

Exit 0



Chapter 6. Using DP for SAP with the File Manager

This section describes how to use the File Manager.

DP for SAP File Manager

The DP for SAP File Manager is a supplementary tool that simplifies the DP for

SAP inquire, restore, and delete operations for the user.

Note

Only users with a good knowledge of the restore and recovery mechanism of

Oracle databases should use this tool. The general recommendation is that

you should normally use the BR*Tools provided by SAP for restore

operations.

The File Manager uses the standard functions provided by DP for SAP to perform

all operations. The File Manager user interface consists of a split window, which is

character based.

All backup IDs found on all Tivoli Storage Manager servers with the same backup

ID prefix as configured within the DP for SAP profile are shown on the left. To the

right of each backup ID, all the files belonging to that backup ID are displayed.

You can select individual backup IDs or multiple files for the restore or delete

operations (see Figure 16 on page 56).

The File Manager has to be started with the path and name of the DP for SAP

profile (the user must be a member of the dba group). See the following examples:

For UNIX or Linux systems:

backfm -p /oracle/SID/dbs/init<SID>.utl [-o <log file directory>]

For Windows systems:

backfm -p <drive>:\orant\database\init<SID>.utl [-o <log file directory>]

Note: If the -o parameter is specified at startup, the default directory for log files

will be changed.

The File Manager requires a correct setup of DP for SAP particularly with regard

to the backint executable, thus enabling it to connect to the TSM server without

errors. To connect to the TSM server the File Manager calls the backint executable.

If this call fails, the File Manager shows an error message but does not analyze

what the reason for the failure is. To analyze the error, call backint manually with

the inquire function (“Inquire Function” on page 161) and check the output for

error messages.

The File Manager will now establish a connection to all Tivoli Storage Manager

servers which were configured in the DP for SAP profile. The next step is an


automatic inquire operation for all backup IDs. The following figure shows the

display of a set of backup IDs located by the File Manager after having finished an

inquiry procedure.

If you mark the backup ID you are interested in and then press the Tab key to

move the cursor to the right-hand panel, all file names belonging to the marked

backup ID will be displayed as shown in the figure below. The following function keys are defined for performing restore or delete

operations:

Figure 15. File Manager — Result of an Inquiry Procedure

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

Using DP for SAP with the File Manager


Up, Down, Left, Right - Move cursor

Move the highlighted cursor in the direction indicated on the key.

Tab - Switch window side

Move the cursor between the left and right sides of the window.

F2 - Restore

Restore all marked files. Before the restore actually begins, you can specify

a common destination path and you will be asked to confirm the restore

process. If you specify a destination path, all marked files will be restored

to that directory. Otherwise the files will be restored to the directory from

which they were backed up.

F3 - Mark all

All files belonging to the current backup ID will be marked.

F4 - Unmark all

Unmark all files belonging to the current backup ID.

F5 - Refresh

Refresh the list of backup IDs and file names.

F6 - Fileinfo

Opens a separate window to display file information.

For backup IDs, the sequence number is displayed (backup version count,

for more information see on page 110). For files, the Tivoli Storage

Manager expiration date and time is displayed.

F7 - Redirected Restore

Restores the selected files to a new location. A new directory structure is

created. The new path names are derived from the original paths by

replacing the original SID with the target SID. Filenames are not modified.

F8 - Delete

Delete the selected backup ID and all corresponding files.

F10 - Exit

Exit from DP for SAP File Manager

ENTER - Mark/unmark file

Mark or unmark the file below the cursor.

For restore operations, the desired files first have to be marked. This can be done

either with the F3 function key to mark all the files that were found or with the

ENTER key to mark only one desired file. Marked files can be identified by the

symbol ″ * ″ in front of the filename. Only the marked files will be restored.

For every restore a log file will be created in the following location:

v UNIX or Linux: $SAPDATA_HOME/sapbackup/backfm_<timestamp>.log

v Windows: %SAPDATA_HOME%\sapbackup\backfm_<timestamp>.log

The File Manager can delete backup IDs with all included files. It is not possible to

delete single files within a backup ID. To delete a backup ID it must be

highlighted. After pressing F8 you have to confirm the deletion operation. The

backup ID and all included files are deleted from the TSM server.

Redirected restore makes cloning of SAP systems easier. See also Chapter 7,

“Cloning the SAP System,” on page 59. To clone a database you need to restore the

database files to a different directory structure. In the path names of the new


Chapter 6. Using DP for SAP with the File Manager 57

directory structure, the Oracle SID is replaced by the new SID. Please note that the

file names are left untouched by this function.

You first have to mark the files for restore. This can be done either with the F3

function key to mark all files of a backup ID or with the ENTER key to mark only

the highlighted file. Marked files can be identified by the symbol ″ * ″ in front of

the filename. Press F7 to start the redirected restore.

For every restore a log file will be created in the following location:

v UNIX or Linux: $SAPDATA_HOME/sapbackup/backfm_<timestamp>.log

v Windows: %SAPDATA_HOME%\sapbackup\backfm_<timestamp>.log

Figure 17. File Manager — Result of a Redirected Restore Procedure



Chapter 7. Cloning the SAP System

The procedure for cloning an SAP system described in this chapter should be used

to complement the SAP documentation R/3 Homogeneous System Copy and R/3

Installation on UNIX / Windows - Oracle Database.

Furthermore, it is recommended that you use the correct SAP documentation for

each particular environment. This documentation can be found at

http://sapnet.sap.com on the SAP Documentation Guides CD-ROM, which is part

of the SAP R/3 installation package or with the help of the SAP technical support.

What is Cloning?

The SAP system cloning can be done if there is the necessity for one source SAP

system to be exactly copied to a target SAP system. In this context, the source SAP

system is also called the original system, from which the data will be exported,

and the target SAP system is also called the destination system, which imports the

data from the source SAP system.

SAP calls the procedure of cloning an SAP system either homogeneous system copy

or heterogeneous system copy. In a homogeneous system copy scenario, the source

and target systems have the same SAP release, operating system, and database

version. If this is not the case, you will get a heterogeneous system copy. Further

information about these two system copy scenarios can be found in SAP Notes

86859 and 86860.

SAP system cloning is appropriate in the following situations:

v Setting up an SAP system landscape (development, quality assurance, and

production system)

v Hardware upgrade

v Creating multiple SAP test and/or demo systems

Additional information about SAP system cloning can be found in the IBM

Redbooks publication SAP R/3 Data Management Techniques Using Tivoli Storage

Manager, SG24-5743. The book can be downloaded at http://www.redbooks.ibm.com.

SAP System Cloning Example

The following procedure is supplied with no warranty of any kind. For

SAP-specific changes, see also SAP Note 71254.

It is assumed that there are two SAP R/3 systems installed and operating on two

different machines and that DP for SAP is installed and operating on both systems.

The following describes the necessary changes in order to restore an Oracle SID to

a different machine with a different SID.

The steps you need to perform depend on the password access method you are

using:

v Automatic password handling (see also on page 49)

If you are using passwordaccess=generate in the Tivoli Storage Manager client

option file dsm.sys on UNIX or Linux systems or <server>.opt on Windows


systems of your source system, you need to make sure that you are using the

same nodename/password that is specified in the Tivoli Storage Manager client

option file on the target system. In order to do that, carry out the following

procedure:

1. Make a backup copy of the client option file on the target system.

2. Copy the client option file from the source system to the target system.

3. Edit the client option file and add NODENAME source system to the server

stanza.

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

the server.

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

do this as root/administrator.

6. Make a backup copy of the init<SID>.utl file on the target system.

7. Copy the init<SID>.utl file from the source system to the target system

and rename init<SID>.utl to init<target_SID>.utl.

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

and path names such as for CONFIGFILE and TRACEFILE.

9. Go ahead and restore the database under the SAP considerations.

10. After the restore, reset the client option file and init<SID>.utl file to their

originals and set the passwords on the target system.

11. Reset the passwords on the source system.

Note

Keep in mind that the passwords are stored in different places, while the

only ″original″ password resides on the Tivoli Storage Manager server! You

need to make sure that the client uses the password that is stored on the

server.

v Manual password handling (see also on page 48)

If you are using passwordaccess=prompt, you only need to set the

nodename/password in the init<SID>.utl file:

1. Make a backup copy of the init<SID>.utl file on the target system.

2. Copy the init<SID>.utl file from the source system to the target system and

rename init<SID>.utl to init<target_SID>.utl.

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

and path names such as for CONFIGFILE, TRACEFILE, ...

4. As <SID>adm user, on the target system, set the Data Protection for SAP

password:

For UNIX or Linux systems

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

For Windows systems

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

and issue the password at the prompt.

Note: On Windows, the profile path can also be specified in UNC notation

(for example: -p \\SERVER_A\ora nt\database\init<SID>.utl

5. Restore the database according to the SAP recommendation.

Cloning the SAP System


6. Reset the init<SID>.utl file and the password on the target system.


Chapter 7. Cloning the SAP System 61

Chapter 8. Installing and Using the Administration Assistant

for Data Protection for SAP

This chapter gives an overview of the Administration Assistant and describes its

installation and setup.

Introducing the Administration Assistant

Functions and Features of the Administration Assistant

The Administration Assistant provides the following functions:

v Monitor operations

v View performance data

v Simulate backup / restore

v Configure systems

v Request problem support

v Manage report templates

v Administer users

Monitor Operations provides a centralized view of the backup status information for

all SAP systems registered with the Administration Assistant server. Summaries of

the backup status of all or a selection of SAP systems are available as well as

detailed information on all backup runs of a specific SAP system. Thresholds can

be defined to enable alerting under certain conditions.

View Performance Data displays performance information while Data Protection for

SAP is performing a backup or restore operation. The Administration Assistant

also saves this performance data and provides a graphical presentation for later

analysis.

Simulate backup / restore lets administrators test configuration changes or production

restores without changing the productive environment or compromising

production data. This function is provided for Oracle databases in combination

with the BACKINT interface.

Configure systems allows to customize the SAP backup profiles, the Data Protection

for SAP profile, and the IBM Tivoli Storage Manager files for each of the SAP

systems registered with the Administration Assistant server. Online information

supports the customization process. Additionally, profiles can be copied from one

system to others. If configuration changes are performed via the Administration

Assistant, a configuration history is maintained, enabling the administrator to

easily return to a previous configuration.

Request problem support supports sending support requests directly to IBM. Support

requests can contain user-specified problem descriptions, but the Administration

Assistant also attempts to automatically collect and include further information,

such as profiles and error logs.

Manage report templates allows the generation and maintenance of templates for

producing reports.


|||||

Administer users supports the definition of user IDs and permissions for accessing

the Server component via the Administration Assistant client.

Additionally, the Administration Assistant lets the administrator create reports in

XML or HTML format from the output of Monitor operations, View performance data,

and Simulate backup / restore.

The primary documentation for the Administration Assistant is the integrated

online help.

Concepts of the Administration Assistant

The Administration Assistant comprises three server-level components (Server,

Database Agent, and Database) and the client component. Operations data is

maintained in an internal database. This offers a solution to potential

out-of-memory problems in SAP environments with a large number of Data

Protection for SAP instances and provides better scalability.

The following figure shows the communication relationships of the Administration

Assistant components (port numbers shown are defaults).

The server-level components can be installed together on one system (standard

installation) or distributed across multiple systems. For example, the Server

component can reside in one system and the DB components in a second system,

or each component can be installed in a separate system. The distributed

installation can help alleviate CPU loading in a single-system configuration in

Figure 18. Administration Assistant Components (with Default Port Numbers)

Installing and Using the Administration Assistant


large-scale environments by spreading this load over two or three separate

systems. If CPU load is not an issue, the single-system installation will normally be

used.

Note: The distributed installation requires that all connecting Data Protection for

SAP instances be version 5.4 or higher. If a single-system installation is

selected, earlier Data Protection for SAP versions can also connect to the

Administration Assistant.

The internal database used by the Administration Assistant is managed by either

the open-source database product Apache Derby or IBM DB2 data server.3 Apache

Derby is bundled with, and installed by, the Administration Assistant. For more

information on Apache Derby, see

http://db.apache.org/derby/

If you prefer using the IBM DB2 data server, an existing DB2 installation must be

present. It will be configured by the Administration Assistant. For more

information on DB2, see

http://www.ibm.com/software/data/db2/

The Server component waits for the clients’ requests for connections using either

the http or https protocols and also for connect requests (via TCP/IP) from the

ProLE service of Data Protection for SAP. After connecting to the Server

component, ProLE connects to and communicates directly with the Database Agent

to send data pertaining and backups and restores performed within its Data

Protection for SAP instance. The Database Agent collects this data and stores all

information related to the Operations Monitor in the Administration Assistant

database via the Database component. This data is accessed when the clients

request any of the Administration Assistant monitoring or analysis functions. In

order to receive and store the history data, the Administration Assistant

server-level components must be running and connected to the Data Protection for

SAP ProLE service during the backup and restore operations. The existence of the

database-related components is transparent to the client user.

Each system hosting an Administration Assistant component can be running UNIX,

Linux, or Windows. The Server and Database Agent components maintain separate

configuration files (assist.cfg and dbagent.cfg, respectively).

User profiles ensure that a client user can access the data of only those SAP

database servers for which permission has been granted.

The Database Agent forwards performance data to the Administration Assistant

Server component, which records it in history files. The retention time for this data

is definable at installation time (default 14 days)

An SAP system landscape contains several SAP systems, such as production,

development, test, and education systems. A single Administration Assistant Server

component can monitor many SAP database servers. A typical example is shown in

Figure 19 on page 66.

3. The use of DB2 is in no way dependent on use of the DB2 version of Data Protection for SAP. A DB2 Administration Assistant

database can also be used in an Oracle environment.


Chapter 8. Administration Assistant 65

||||

|

|||

|

http://db.apache.org/derby/

http://www.ibm.com/software/data/db2/

The Administration Assistant client is started from a browser by invoking the URL

designating the Server component host. The client is implemented as a Java™applet

that communicates with the Server component via a remote method invocation

(RMI) connection.

If the Administration Assistant Server component is started in non-secure mode

(that is, with the keyword ’nonsecure’ defined in the Server configuration file

assist.cfg), it accepts connect requests from a client to its http port via http. In

this case, further communication between the client and server is via TCP/IP.

If the Server component is started in secure mode (that is, with the keyword

"nonsecure' omitted from the Server configuration file), it accepts connect requests

from a client to its https port via https. In this case, the Secure Sockets Layer (SSL)

protocol is employed for all communication between the Administration Assistant

clients and the Server component.

The latest SSL protocol (Version 3) can be found at http://wp.netscape.com/eng/ssl3/.

The latest information on PKI with X.509 certificate can be found on the Web page

of the IETF Working Group 'Public Key Infrastructure (X.509) (pkix)' at:

http://www.ietf.org/html.charters/pkix-charter.html .

XML- or HTML-format reports are created either from the Administration Assistant

client via the graphical user interface or via a command-line interface from a

scheduling client. The scheduling client is implemented as a Java application that

communicates with the Administration Assistant Server component via an RMI

connection.

Figure 19. Example of an SAP Landscape



http://wp.netscape.com/eng/ssl3/

http://wp.netscape.com/eng/ssl3/

http://www.ietf.org/html.charters/pkix-charter.html

Installing or Upgrading the Administration Assistant

In order to set up the Administration Assistant server, do the following:

1. Check that the Administration Assistant package is complete. The package

includes machine readable material on a CD-ROM or a CD image downloaded

from Passport Advantage. See the Readme information at the CD and package

levels for a description of the respective structure and the latest news. The

Administration Assistant is provided on each DP for SAP CD or CD image as a

file of the format:

<version>-TIV-TSMERPAABASE-MULTI.jar

2. Make sure that the requirements are met. For details, see “Prerequisites for

Installing the Administration Assistant Server-Level Components” and

“Prerequisites for the Administration Assistant Client.”

3. Gather planning information. For details, see “Installation Planning for the

Administration Assistant Server-Level Components” on page 68.

4. Install the Administration Assistant server-level components. For details, see

“Installing the Administration Assistant Server-Level Components” on page 68.

5. Perform post-installation steps. For details, see “Post-Installation Steps” on page

71.

6. Set up the Administration Assistant client. For details, see “2. Setting up the

Administration Assistant Client” on page 71.

7. Verify the installation. For details, see “3. Verifying the Installation” on page 72.

If you are going to do an upgrade installation, refer to “Upgrading the

Administration Assistant (Migration)” on page 74.

Prerequisites for Installing the Administration Assistant

Prerequisites for Installing the Administration Assistant

Server-Level Components

The following products must be installed before you can start setting up the

Administration Assistant server-level components:

v Java Runtime Environment (JRE) or Java Development Kit (JDK)

v Java Beans Activation Framework (JAF)

v Java Mail

v IBM DB2 data server (optional DBMS for Administration Assistant database)

If you decide to use the IBM DB2 data server, ensure the following:

v On Windows platforms:

– DB2 must be installed and runningv On UNIX and Linux platforms:

– DB2 must be installed and running

– Create a new system user for which the DB2 instance should be installed

For hardware and software prerequisites, as well as the maintenance levels

required by the current version of the Administration Assistant, refer to the release

notes for DP for SAP (see “Where to Find More Information” on page xi). TCP/IP

must be ready for communication before starting up the Administration Assistant

server-level components.

Prerequisites for the Administration Assistant Client

Before starting the Administration Assistant client make sure the following

requirements are met:



||

|

|

|

|

|

|

|

|

|

|

v A fully Java-capable Web browser with Java plugin. The applet loaded from the

Administration Assistant server must be granted the following permissions:

– Permission to establish a connection to the Administration Assistant server

via RMI, for example:

permission java.net.SocketPermission "<Server component hostname>:1024-", "connect";

– Permission to switch to a different language:

permission java.util.PropertyPermission "user.language", "write";

v For the presentation of graphics in reports, a browser supporting Scalable Vector

Graphics (SVG), for example with the Adobe SVG Viewer, must be available.

v X Window system if the Administration Assistant client will be started on a

UNIX or Linux system.

v A minimum screen resolution of 1024x768 pixels (1280x1024 or higher is

recommended).

For software versions and maintenance levels required by the current version of

the Administration Assistant, refer to the DP for SAP release note.

TCP/IP must be ready for communication before connecting to the Server

component.

Prerequisites for the Scheduling Client

When selecting the scheduling client, make sure the following requirements are

met:

v A TCP/IP connection can be established to the Administration Assistant Server

component.

v A Java VM is available.

v For the presentation of graphics in reports, a browser supporting Scalable Vector

Graphics (SVG), for example with the Adobe® SVG Viewer, is available.

Installation Planning for the Administration Assistant

Server-Level Components

See Table 7 on page 168 for a list of planning requirements in table form. This

information is also available in the planning_sheet_aa (UNIX or Linux) and

planning_sheet_aa.txt. (Windows) files in the Data Protection for SAP installation

directory.

Installing the Administration Assistant Server-Level

Components

The Administration Assistant installation packages are located on each of the Data

Protection for SAP CD-ROMs or CD images, and can also be downloaded from the

IBM FTP server.

Initial installations must always be done from the CD-ROM or CD image. Refer to

the file README.1ST in the root path of the CD or CD image for information on

where to find documents, and follow the installation description below.

On the CD or in the CD image, the installation package for the Administration

Assistant is a single, platform-independent .jar file with the following name:

<version>-TIV-TSMERPAABASE-MULTI.jar



If you want to upgrade from an earlier version of Data Protection for SAP

Administration Assistant in your environment, you have the option to download

the latest version from the IBM FTP server via the product support page

http://www.ibm.com/software/sysmgmt/products/support/.IBMTivoliStorageManagerforEnterpriseResourcePlanning.html

For more information on upgrading from an earlier version, refer to “Upgrading

the Administration Assistant (Migration)” on page 74.

Installation Process

To assist you with the installation procedure, the Administration Assistant

packages provide a setup assistant that guides you through the installation process.

The setup assistant provides the option to install either an English-only version of

the Administration Assistant or the multi-language version.

To install the Administration Assistant correctly, system administrator privileges

are required.

If a multi-host installation is desired (which distributes the server-level components

over two or three hosts), copy the package file to each target host and perform a

'custom' installation that selects the components for that host.

There is no need to set the environment variable CLASSPATH. However, if this

variable is set in the system environment, the directory in which the package file

resides must be included.

During the installation process the administrator must select a language option. In

order to switch options after the installation, uninstall the Administration Assistant

and install again with the new option.

Start the installation by specifying the following command:

java -cp <package file name> run

If only the JRE is installed, you must use the command:

jre -cp <package file name> run

During installation, the following modifications are made to your system

automatically:

v All necessary paths (installation, history, OnDoc, log paths) are created.

Corresponding files are copied into the installation and OnDoc directories.

v The Administration Assistant startup files are created and added to the

installation directory:

Component UNIX or Linux Windows

Server sadma.sh sadma.cmd

Database Agent sdba.sh sdba.cmd

v The configuration file assist.cfg, containing all relevant configuration

parameters specified during the installation, is created and added to the

installation directory.



|

v The configuration file dbagent.cfg containing all relevant configuration

parameters specified during installation of the Database Agent component is

created and added to the installation directory.

v On Windows systems a service is installed and automatically started. This

service starts AAStart.exe and java.exe.

v On UNIX or Linux systems a new /etc/init.d entry is created for each

Administration Assistant server-level component:

Component Entry in /etc/init.d

Server adminAssistant, with parameters start, stop,

and status

Database Agent databaseAgent, with parameters start, stop,

and status

Database (Derby) (optional, as alternative to

DB2)

apacheDerby, with parameters start and stop

Database (DB2) (optional, as alternative to

Derby)

Not applicable

and the components are started automatically.

Note: For automatic start/stop of Administration Assistant components on

UNIX or Linux systems, the administrator must create appropriate run

level entries.

v For an installation using IBM DB2:

– On Windows systems:

- The database tables are created, but no other changes are made.– On UNIX and Linux systems:

- A DB2 instance for the specified user ($USERNAME) will be created

- Some changes to your system will be applied as follows:

v An entry in /etc/services is added:

$USERNAME $PORT/tcp # used for Data Protection for SAP - Administration Assistant with DB2 support

v Changes to the created DB2 instance:

– Set DB2 profile registry variable: DB2COMM=tcpip

– Set DB2 database manager parameter: SVCENAME=$USERNAME

– Set DB2 database manager parameter: SPM_NAME=NULL

v For an installation using secure communication:

– A keystore is created on request.

– An X.509 v1 self-signed certificate containing a key pair with the hostname as

an alias is created in the keystore on request.

– The server’s self-signed certificate is imported into the truststore on request.

– The server’s self-signed certificate is exported to a certificate file on request.

– A Certificate Signing Request is created if desired.

When one or more Administration Assistant components have been installed, an

overview panel is presented indicating the current status of the installation process

and recording the user's entries.



|||

|

|

|

|

|

|

|

|||

|

|

|

|

Uninstalling the Administration Assistant Server-Level

Components

To uninstall the Administration Assistant server-level components, change to the

uninstall directory in the Administration Assistant installation directory on each

system on which one of the components was installed (potentially two or three

systems if a distributed installation was selected for version 5.4 or later). The

command files open an uninstall assistant which guides you through the

deinstallation process.

The public key infrastructure will not be modified when uninstalling the

Administration Assistant components, even if it was originally set up during its

installation process.

To start the deinstallation process, run the following command:

java -cp uninstall.jar run

Note: The Administration Assistant client component is not physically installed. It

executes as a Java applet when the user invokes the URL of the host

running the Server component. No action needs to be taken at the client

level when uninstalling the Administration Assistant server-level

components.

Post-Installation Steps

After successfully completing the installation dialog for the Administration

Assistant server-level components, you need to perform the following steps:

1. If appropriate, prepare a secure connection between the Administration

Assistant clients and the Server component.

2. Set up the Administration Assistant client.

3. Verify the installation.

4. Set up a scheduling client for reporting

1. Preparing a Secure Connection between the Administration

Assistant Server Component and Client

If the necessary information was provided during the installation, the Server

component is already configured for secure communication with its clients after

the installation procedure. However, by default it is set up to accept unsecure

(http) connect requests from the clients. You start a secure Administration Assistant

Server component by removing the keyword ’nonsecure’ from the configuration

file (assist.cfg).

If you elect not to provide security information during the installation process, or if

you need to change the security setup, refer to “Configuring for Secure

Communication” on page 77.

2. Setting up the Administration Assistant Client

The Administration Assistant client is not an installable component. It executes as a

Java applet when the user connects to the Administration Assistant Server

component.

Before connecting to the Server component, make sure that cookies are not

disabled by any means, for example by your browser or by personal firewall

settings. Also, ads and pop-up panels must not be blocked unless you use



|

index.html in the address. See also “3. Verifying the Installation” for information

on how to connect to the Administration Assistant Server component.

Make sure all prerequisites of the Administration Assistant Client (see

“Prerequisites for the Administration Assistant Client” on page 67) are met.

In order to establish secure communication between the Administration Assistant

client and the Server component, the client’s Java plugin must be able to verify the

certificate presented by the Administration Assistant Server component. In a

production environment, the server certificate will be signed by an official

certificate authority whose root certificate is contained in the plugin’s truststore. In

this case, there is nothing to be done.

If, however, the server identifies itself with a self-signed certificate, this certificate

must be imported into the plugin’s truststore. If you did not replace the plugin’s

truststore via the Java Plugin Control Panel, file cacerts in the Java security path

is used as the truststore. You modify it with your keystore management tool,

which may differ depending on your platform and provider. With keytool (Sun

Microsystems), for example, you need to issue

keytool -import -alias <Server component hostname> -file <cert_file> -keystore <trustore>

Note

Be sure to remove the self-signed trusted certificate from the truststore as

soon as the officially signed server certificate is available and employed. A

setup with self-signed certificates is not recommended for production

environments.

3. Verifying the Installation

Verify the installation of the Administration Assistant by connecting to the

Administration Assistant Server component from a client machine. If the Server

component was started with the keyword 'nonsecure' in the Server configuration

file, then connect via

http://<Server component host name>:<http port>

Alternatively, you can make the connection via

http://<Server component host name>:<http port>/index.html

In the latter case, the Administration Assistant client will not open a new browser

window.

If the Administration Assistant server is started without the keyword 'nonsecure'

in the Server configuration file, then connect via

https://<Server component host name>:<https port>

Alternatively, you can make the connection via

https://<Server component host name>:<https port>/index.html



In the latter case, the Administration Assistant client will not open a new browser

window.

For your initial login, use the userid ADMIN with password 'admin'. Make sure

you change the default password immediately via the client function Administer

Users.

As soon as an instance of Data Protection for SAP connects to your Administration

Assistant Server component, the instance will be displayed in the list of DP for

SAP servers. For details on how to set up your instance of Data Protection for SAP

to connect to a specific Server component, refer to “Adjustments for the

Administration Assistant” on page 46.

4. Setting Up a Scheduling Client for Reporting

In order to create reports with templates, a scheduling client server must be set up.

This is done by the following steps:

1. Select a system that meets the requirements documented in “Prerequisites for

the Scheduling Client” on page 68.

2. Copy files Admt.jar and NLS.jar from the installation directory of the

Administration Assistant Server component to the scheduling client system.

Before starting to generate reports, make sure that files Admt.jar and NLS.jar

are included in the CLASSPATH and that the JVM is included in the PATH. For

a sample script addressing this setup refer to “Sample Command Files for

Scheduling Reports” on page 173.

3. In case the Administration Assistant Server component is started in secure

mode, set up a public key infrastructure between the scheduling client and the

Server component:

In a production environment, the server certificate will be signed by an official

certificate authority whose root certificate is contained in the JVM’s truststore.

In this case, there is nothing to be done.

If the server identifies itself with a self-signed certificate, however, this

certificate must be imported into the JVM’s truststore. By default, the truststore

is contained in file cacerts in the Java security path. You modify it with your

keystore management tool, which may differ depending on your platform and

provider. With keytool, for example, you issue

keytool -import -alias <Server component hostname>...

... -file <cert_file> -keystore <truststore>

Note

Be sure to remove the self-signed trusted certificate from the truststore as

soon as the officially signed server certificate is available and employed.

The setup with self-signed certificates is not recommended for production

environments.

Starting and Stopping the Administration Assistant Manually

The Administration Assistant Server component can be started and stopped

manually with the following command files in the installation directory:

On UNIX and Linux:

sadma.sh start|stop <Server component configuration file>



On Windows:

sadma.cmd start|stop <Server component configuration file>

The Administration Assistant Database Agent can be started and stopped with

On UNIX and Linux:

sdba.sh start|stop <Database Agent configuration file>

On Windows:

sdba.cmd start|stop <Database Agent configuration file>

If you decided to use the bundled Apache Derby, the Administration Assistant

Database component can be started and stopped with

On UNIX and Linux:

sdb.sh start|stop

On Windows:

sdb.cmd start|stop

If you decided to use the IBM DB2 data server, the administrative tasks for starting

and stopping the database can be done by the DB2 Control Center or by the DB2

command line. Please refer to the IBM DB2 data server documentation.

Important

When the Server or Database Agent components are started, a lock file

(.lockAA and .lockDBA, respectively) is created. If either of these components

is terminated or restarted using the delivered scripts, the respective lock file

is also deleted. If for some reason the lock file still exists when the component

is started, the request will fail with an error message. In this case, first verify

that the process is not already active. If not, the lock file must be deleted

manually and the start request reissued.

Upgrading the Administration Assistant (Migration)

In order to upgrade the Administration Assistant server to a new version, do the

following:

1. Check that the Administration Assistant package is complete. The

Administration Assistant is provided on each of the DP for SAP CDs or CD

images, and can also be downloaded from the IBM FTP server.

2. Make sure that the requirements for the new version of the Administration

Assistant are met.

For details, see “Prerequisites for Installing the Administration Assistant

Server-Level Components” on page 67 and “Prerequisites for the

Administration Assistant Client” on page 67, and read the DP for SAP release

notes (see “Where to Find More Information” on page xi).



||

|||

3. Gather or retrieve planning information. For details, see “Installation Planning

for the Administration Assistant Server-Level Components” on page 68.

4. If you want to migrate your existing data to the new version, perform the

procedure described in “Migration of Data from Previous Releases.”

5. Uninstall the old version of the Administration Assistant. For details, see

“Uninstalling the Administration Assistant Server-Level Components” on page

71.

6. Install the new version of the Administration Assistant server-level components.

For details, see “Installing the Administration Assistant Server-Level

Components” on page 68.

7. Perform the post-installation steps. For details, see “Post-Installation Steps” on

page 71.

8. Set up the Administration Assistant client. For details, see “2. Setting up the

Administration Assistant Client” on page 71.

9. Verify the installation. For details, see “3. Verifying the Installation” on page 72.

Note: It is possible to use the Administration Assistant in conjunction with

supported Data Protection for SAP versions prior to version 5.4, provided

the Administration Assistant is installed on a single host.

Migration of Data from Previous Releases

Note: The following procedure must be performed prior to uninstalling the

Administration Assistant and installing the new version.

Data Protection for SAP does not provide support for transferring data from an

installation of the Administration Assistant prior to version 5.4. If desired, the

report function can be used to capture data from the prior version before the new

version is installed.

If you would like to transfer data from the database of an installation of version

5.4 of the Administration Assistant, follow these steps:

1. The export tool is provided on each DP for SAP CD or CD image in the

migration directory. This directory contains:

v aaDerbyAdaption.jar

v prepareExport.sql c.

v export.cmd (for use with Windows systems)

v export.sh and export ksh (for use with UNIX/Linux systems)

Copy these files from the CD (or image) for the new version of the

Administration Assistant to your system.

2. If you are using Apache Derby, get information on how to connect to the

Apache Derby database. These settings are provided in file assist.cfg and are

listed below:

v Location of your previous installation of the Administration Assistant

v Username to connect to the Apache Derby database

v Password to connect to the Apache Derby database

v Port to connect to the Apache Derby database

v Hostname of your system

v Name of the database

v Path to file aaDerbyAdaption.jar



||

|

||

||||

||

||

|

|

|

|

||

|||

|

|

|

|

|

|

|

v Directory where the data will be exported3. Start the export script. You will be guided through the export process.

If you would like to transfer data from the database of version 5.5 of the

Administration Assistant, follow these steps:

1. If you would like to export data from a running Apache Derby database, first

get information on how to connect to the database. These settings are provided

in file assist.cfg.

2. Change to the utils directory and start the export script by typing the

following:

v For Apache Derby:

– On Windows systems:

export.cmd

– On UNIX/Linux systems:

export.sh (or export.ksh)

v For DB2 data server:

On Windows systems:

export.cmd <database> <user> <export directory>

On UNIX/Linux systems:

export.sh (or export.ksh) <database> <user> <export directory>

As a result, the export directory contains several *.aa files. During the installation

process, you will be asked if you would like to import old data. Within this dialog

you can enter the export directory you selected during the export.

If you would like to reuse your styles and reports, save these directories from the

installation directory to another directory.

Note: During the installation of Administration Assistant all data in the installation

directory will be removed.

After the installation process, you can copy these directories back to the installation

directory of the Administration Assistant.

Configuring the Administration Assistant

Administering User IDs

With the Administer users function, it is possible to create and delete accounts with

appropriate rights for using Administration Assistant functions or configuring DP

for SAP. User permissions can be granted or revoked.

For each SID in the system landscape, the following permissions can be granted:

v Simulate backup/restores: to initiate simulations

v Configure groups: to configure display groups to be used with function

″Monitor backup states″

v Problem support: to send support request mail

v Operations monitoring: to view backup status information

v User administration: to manage user accounts

v Performance monitoring: to view performance data

v Configuration: to modify the configuration of Data Protection for SAP



|

|

||

|||

||

|

|

|

|

|

|

|

|

|

|

|||

||

||

||

Additionally, a user can be granted permission to configure parts of the internal

logic of the "Monitor backup states″ function.

When you start the Administration Assistant for the first time, you will need to

create profiles for authorized users. Refer to the online help for information on

how to do this.

Configuring for Secure Communication

The secure communication between the Administration Assistant Server

component and its clients is realized with the Secure Socket Layer (SSL) protocol.

This protocol requires that both the server and client be integrated in a public key

infrastructure (PKI). Specifically, the Server component requires

v An https port to listen on for https connect requests

v A keystore containing a key pair it uses to identify itself to the clients and when

connecting internally to the RMI registry. The server’s hostname is used as an

alias for this key pair. Since the keystore contains the server’s private key,

precautions must be taken that prevent access by unauthorized persons.

v A truststore containing trusted certificates that allow verifying the server’s

signature. If the server certificate was digitally signed by an official certificate

authority whose root certificate is available in the truststore by default, there is

nothing to be done. If however, the server identifies itself with a self-signed

certificate, this certificate must be imported into the truststore as well.

Note

Be sure to remove this trusted certificate from the truststore as soon as the

officially signed server certificate is available and employed. A setup using

self-signed certificates is not recommended for production environments.

Both the keystore and truststore can be manipulated with your keystore

management tool, which may differ depending on your platform and provider (for

example, keytool ). For setting up the Administration Assistant Server component

for secure communication you need to

v Remove the keyword 'nonsecure' from the Server configuration file (assist.cfg)

v Specify the appropriate https port number in the Server configuration file:

httpsport=<https port number>

The default https port number is 443.

v Start the Server component with the appropriate keystore and truststore. You do

this by adding the parameters to the appropriate 'java' call. The parameters are

shown in the shaded area below:

– for UNIX and Linux: add the parameters to sadma.sh

– for Windows: add the parameters to sadmt.cmd and to the registry. The

Windows registry key is:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\......AdminAssistant\Parameters\AppParameters

-Djavax.net.ssl.keyStore=<keystore>

-Djavax.net.ssl.keyStorePassword=<password for keystore>

-Djavax.net.ssl.trustStore=<truststore>



If you do not specify one or more of these parameters, the defaults of your Java

virtual machine will be used.

v Make sure the required certificates are contained in the keystore and trust store.

v Restart the Administration Assistant Server component.

When changing the Administration Assistant server from non-secure to secure

mode using a self-signed certificate, remember to also prepare the Administration

Assistant clients as described in “2. Setting up the Administration Assistant Client”

on page 71 and “4. Setting Up a Scheduling Client for Reporting” on page 73.

Changing the Password for the Administration Assistant

Database User ID

The program changeSettings.jar was added to the installation directory in the

utils subdirectory. The password for accessing the internal Administration

Assistant database can be changed via this program as follows:

1. Change to the utils directory and start the program by typing

java –cp changeSettings.jar run

2. Select the type of database you are using with the Administration Assistant

(Apache Derby or IBM DB2).

3. Enter the directory containing the encrypted password file (pass.enc).

4. Enter the user ID and the existing password.

5. Enter the new password.

6. For Apache Derby only: To apply the new password to the database, check the

box provided. Otherwise, the password file is updated but the database change

must then be performed manually.

7. Click ’Next’ to complete the change.

Defining Thresholds

The Administration Assistant provides for defining limits (thresholds) for various

states pertaining to the Administration Assistant environment. The threshold status

is shown in the "Monitor Backup States" and "Backup State - Detailed View"

panels.

Predefined threshold types are:

v Backup duration (in minutes or hours)

v Backup size (in MB or GB)

v Throughput rate (in GB per hour or MB per second)

v Time since the last complete backup (in hours or days)

v Size of all log file backups since the last complete backup (in MB or GB)

v Recovery point objective (maximum time permitted since the last backup, in

minutes or hours)

Additional thresholds can be defined using a custom SQL file (see “Defining

Thresholds Using the Custom SQL File” on page 79).

When a threshold is exceeded, this is reported in the "Threshold Status" column of

the "Monitor Backup States" panel, and an e-mail describing the exception in more

detail is sent to any e-mail addresses defined for the threshold. A lifetime parameter

associated with each threshold defines the length of time between e-mail

notifications, provided the threshold remains in alert status.



||||

|||

|

|||

||

|

|

|

|||

|

|

||||

|

|

|

|

|

|

||

||

|||||

For information concerning threshold definitions, see the Administration Assistant

Online Help.

Defining Thresholds Using the Custom SQL File

A custom threshold can be defined in the custom SQL file. The corresponding

entry has the following values for the indicated tags:

Table 3. Tags for Defining Thresholds in the Custom SQL File

Tag Value

<sql> An SQL statement that will return data when the threshold is

exceeded.

<programid> 0 (Administration Assistant)

<actionid> 0 (send e-mail when threshold exceeded)

<executionmode> 1 (run periodically)

<param> (Optional) One or more e-mail addresses, separated by semicolons. If

no e-mail address is given, only a panel indication is given that the

threshold has been exceeded.

Note: Multiple e-mail addresses are given in a single

<param></param> tag pair, not in multiple pairs.

See “Defining the Custom SQL file” for details concerning the custom SQL file.

Defining the Custom SQL file

Note: The custom SQL file is intended to be implemented or modified only by

IBM support personnel with a detailed knowledge of the process involved

and the internal Administration Assistant database. This section does not

discuss this process in detail.

The custom SQL file must be named:

customSQLFile.txt

and placed in the installation directory (or folder) of the Administration Assistant

(for example C:\Program Files\tdpr3assi\customSQLFile.txt).

The custom SQL file has the following structure:

# CUSTOM SQL FILE Comment

<sql>SQL statement</sql><description> ... </param>

<sql>SQL statement</sql><description> ... </param>

...

Each entry must be coded in a single line.

As an aid to explaining the entry structure, it is shown in the following with each

tag set in a separate line:



||

|||

||

||

|||

||

||

||

||||||||

|

||||

|

|

||

|

|||||||

|

||

<sql>SQL statement</sql>

<description>Description of the SQL statement</description>

<programid>0</programid>

<actionid>0</actionid>

<displaygroup>1,3</displaygroup>

<backuptype>2</backuptype>

<executionmode>0</executionmode>

<param>parameter-value1</param>

<param>parameter-value2</param>

...

<param>parameter-valuen</param>

The tag definitions are as follows:

Table 4. Contents of the Custom SQL File

Tag Definition

# Comment line

<sql> An SQL statement that defines which data is to be sent.

Notes:

1. Only SELECT statements will be executed.

2. A semicolon at the end of the line is not permitted.

3. The maximum line length is 400 characters.

<description> Description of the SQL statement (maximum length: 300 characters)

<programid> Specifies the program that handles the result of the SQL statement.

v programid 0: Administration Assistant

<actionid> Defines the way the result will be handled, depending on the

programid (currently, the only value for actionid is 0):

v (programid 0: Administration Assistant): Send e-mail when

threshold exceeded (SQL statement returns data)

<displaygroup> List of display group IDs separated by commas, or "ALL" for all

display groups.

<system> List of system IDs separated by commas, or "ALL" for all systems.

<backuptype> List of backup types separated by commas, or "ALL" for all backup

types.

v 0: Archive

v 1: Partial backup

v 2: Incremental backup

v 3: Full backup

<executionmode> executionmode sets the time the entry will be performed (i.e., the SQL

statement issued):

v 0: Entry will be performed after each backup run

v 1: Entry will be performed periodically

<param> Parameters needed by the programs. The number of parameters

depends on the selected program and action. Multiple parameters are

coded using repeating <param></param> tag pairs.

v (programid 0: Administration Assistant):

– One parameter, consisting of the e-mail address list (separated by

semicolons)

Notes:



|||||||||||||

|

||

||

||

||

|

|

|

|

||

||

|

|||

||

|||

||

|||

|

|

|

|

|||

|

|

||||

|

|||

|

1. Each entry in the file must be on a single line.

2. If executionmode is 1, the <system>, <displaygroup>, and <backuptype> tags

are ignored, and the SQL statement will be executed periodically.

3. If executionmode is 0, the SQL statement will be executed after the backup

completes, but only if the system tag matches the system on which the backup

was performed, or the displaygroup tag matches the displaygroup the system

belongs to. Furthermore, the <backuptype> tag must match the backup type of

the backup performed.

4. The <system> and <displaygroup> tags are mutually exclusive.

5. The custom SQL file will be reloaded periodically by the Administration

Assistant Server component. The server need not be restarted.



|

||

|||||

|

||

Chapter 9. Balancing Your System

This chapter describes how to proceed when tuning your system according to your

needs. This is done by employing a combination of functions provided in the Data

Protection for SAP Administration Assistant.

Cyclic Procedure for Optimizing your Configuration

With the Administration Assistant, administrators can analyze performance, modify

the configuration, and test the effects of configuration changes without having to

modify the production environment.

The optimization cycle starts with a full backup of the database via the file

interface (via BRBACKUP). The performance data is analyzed with function ’View

Performance Data’. This may lead to some suggestions on how to change the DP

for SAP configuration and / or the infrastructure. These changes are temporarily

implemented in a test profile with function ’Configure Systems’. With function

’Simulate Backup/Restore’, another backup or restore can be simulated to test the

configuration changes. Then, the administrator uses the function ’View

Performance Data’ to check whether the modifications yield the desired results.

You may go through as many cycles of modification and test as are required until

the results are satisfactory. When this is the case eventually, the configuration

changes can be easily propagated to the production system. All changes to the

configuration within this cycle are kept strictly separated from your production

system, as are the results of the simulation runs.

Observations on the DP for SAP Data Throughput

We observe that overall throughput rates can differ very much among the various

installations. This is due to differences in resources (disks, network bandwidth,

server platforms, number of tapes, etc.) and configuration. For a more general

discussion of performance considerations refer to “General Performance

Considerations” on page 39. For a list of DP for SAP configuration options

contributing to performance read “Adjustments to DP for SAP for Improving

Performance of Data Transfer” on page 41. The following discussion will

concentrate on selected elements of the data flow. It will show how to use the

given resources to their capacity and will give hints where throughput can be

Figure 20. Optimizing your Configuration with the Administration Assistant


improved.

From a bird’s perspective, when doing a backup with DP for SAP, the data

packages need to pass the following elements: Data is read from disk, processed by

DP for SAP, and sent via a network to some storage media (tape or disk). In an

unbalanced system, each of these elements, disk I/O, network bandwidth, and

storage media rates may present a bottleneck, at the same time causing other

resources to idle. Traditionally, overall data throughput is measured per file or per

entire backup. The results are presented as average throughput rates in various log

files. Analysis of the causes of insufficient throughput rates is cumbersome, done

by relating events documented in a number of different log files to each other. For

the same reason, finding potential for a better exploitation of resources is arduous,

too. In a first step to support administrators with these tasks, DP for SAP provides

performance sensors that indicate whether there is a bottleneck located either in

the elements represented in blue (for disk) or in yellow (for network and tape

respectively) in the above graphic.

Data Protection for SAP Performance Sensors

Depending on the configuration of the IBM Tivoli Storage Manager, data packages

are either passed from the IBM TSM API Client via a network to the backup

server, or they are processed by the IBM TSM API Client and the Storage Agent in

a LAN-free environment.

There are sensors introduced to Data Protection for SAP that observe the incoming

and outgoing data streams. They do not only measure the actual throughput, but

also the idle time of the I/O threads versus the duration of the backup. This way,

they can indicate whether the streams of incoming and outgoing data of Data

Protection for SAP are balanced.

After starting a backup, it may take some time until the buffers are filled and the

effects of a bottleneck will become obvious.

Figure 21. A Bird’s Eye View of the Data Flow During Backup

Figure 22. Performance Optimizing by Using Sensors

Balancing Your System


Presentation of the Measurements in the Administration Assistant

The Administration Assistant function ’View Performance Data’ provides a

graphical representation of the data throughput rate at any point in time during

the backup. Aligned with this, the utilization rates of the disk (presented in blue

by the Administration Assistant) and network threads (presented in yellow by the

Administration Assistant) are displayed. Alternatively, the free capacity of these

threads can be shown. The administrator can choose to have these rates displayed

either for the entire backup considering all TSM sessions, or on a per-session basis.

Interesting time intervals that need to be further analyzed can be selected for

further analysis in replay mode. For details, see “Drilling Down on Special

Situations” on page 91.

The results of the Data Protection for SAP performance sensors are presented in

the Administration Assistant’s function ’View Performance Data’. The

Administration Assistant collects history data during each backup run for later

analysis. In order to find the results, select ’View Performance Data’, then select

’History Data’. In the list of eligible backups, select the backup to be analyzed.

Pressing the ’Review’ button will take you to the performance data summary

panel.

Typical Situations

Following, we discuss some typical graphs you may see when using function

’View Performance Data’ of the Administration Assistant.

Figure 23. Showing Data Throughput and I/O Utilization


Chapter 9. Balancing Your System 85

Disk Bottleneck

With a disk bottleneck, data is processed by the network and TSM server faster

than they can be read from disk. As a consequence, overall throughput is limited

by the disk I/O rate, and the network thread is idle. As the network threads

usually return very fast due to internal buffering, the network utilization might

seem to drop to (almost) zero in this case. Both the network and the storage media

are not used to their capacity. If tapes are used they are not kept in streaming

mode any more.

If you are looking to improve overall throughput you may want to

v Increase multiplexing in order to accelerate reading from disk,

v Switch off data compression if it is employed.

If you are looking to better exploit the resources (here: the tape drives) you may

want to reduce the number of sessions to the TSM server and the number of tapes

for the backup while increasing multiplexing. For an optimization procedure, refer

to “Cyclic Procedure for Optimizing your Configuration” on page 83.

Figure 24. Indicating a Disk Bottleneck



Network or TSM Bottleneck

With a network or TSM bottleneck, data is read from disk faster than the network

and TSM can process them. Consequently, throughput is limited either by the

network capacity or by the storage media rate (disk, tape). In order to actually

locate the source of the delay further analysis is required. However, some hints can

be obtained from the DP for SAP performance analysis, as will be detailed in

“Simulating Backup and Restore” on page 89.

If you are looking to improve overall throughput you may want to

v Increase the number of sessions to the TSM server (if the tape is the bottleneck),

v Use multiple paths to a TSM server or multiple servers,

v Use RL compression in order to reduce the data to be sent to the backup storage

If you are looking to better exploit the resources you may want to reduce

multiplexing so that less data is read from disk simultaneously. If the database is

configured for file-online backup this will reduce the number of redo logs created

during the backup.

For a general optimization procedure, refer to “Cyclic Procedure for Optimizing

your Configuration” on page 83.

Figure 25. Indicating a Network or TSM Bottleneck



A Balanced Configuration

If the threads on both the disk and the network side are similarly busy throughout

the backup the system is balanced, and the utilization of resources is good. In an

optimum setup, tapes are kept in streaming mode. That means that the network is

at least as fast as the tape, and there is no idle time on the network side. Thus, a

slight network bottleneck is desired.

Note

Under certain conditions, the degree of imbalance cannot be determined from

the graphical presentation: Depending on your system characteristics (for

example system buffering, buffer sizes, etc.), utilization may seem to drop

near zero in the graphical presentation although the system is fairly balanced

in reality. In this case, slight modifications can yield a change of bottleneck

without significant throughput changes. However, whether the system is disk

or network / tape constrained is always shown correctly.

If you are looking to improve overall throughput you may want to add more

resources and create a balanced system again.

If you are looking to better exploit the resources you are done.

Note

A balanced system does not necessarily mean that the data throughput cannot

be improved further. Adding new resources can still improve the throughput

rate.

Figure 26. Indicating a Balanced Configuration



Simulating Backup and Restore

The Administration Assistant’s function ’Simulate Backup/Restore’ requires a full

backup of your database using the file interface (via BRBACKUP). Backups done

using the RMAN interface cannot serve as a basis for simulation. When there are

two or more eligible backups available the latest one is used as the basis for

simulation.

In order to get good results for the simulation of Data Protection for SAP

compression, compression should be enabled for the base backup, with parameter

COMPR_INFO pointing to a valid file in the Data Protection for SAP profile.

Both backups and restores can be simulated. Simulating a restore may give you an

impression how long restoring a backup will take, but it will not affect your

productive system.

The administrator may choose to simulate any of the following:

v Disk I/OWhen simulating disk I/O for a backup, no data is read from disk. They are

generated in memory instead. When simulating disk I/O for a restore, no data is

written to disk; they are consumed instead. The disk I/O rate to be used for the

simulation can be set by the administrator.

For information on how to determine your current rate, refer to “Determining

the Actual Disk I/O Rate.”

v Network transfer and media ratesWhen simulating network transfer and media rates for a backup no data is sent

via the network; they are consumed instead. When simulating network transfer

and media rates for a restore, no data is expected from the network; they are

generated in memory instead. Still, a connection to the TSM server is established

and needs to be maintained during the simulation. Therefore, be sure to

configure the TSM server so, that the sessions do not time out. See: “5. TSM

Server Configuration” on page 185.The network throughput rate and the media rate for the simulation can be set by

the administrator. The rate to be used for the simulation is determined by the

network throughput rate and the media rate set.

For information on how to determine your current network rate, refer to

“Determining the Actual Network Throughput Rate” on page 90.

For information on how to determine the current media rate, refer to

“Determining the Actual Throughput Rate of Storage Media” on page 90.

v Configuration changesWhen simulating configuration changes, the performance relevant parameters in

the DP for SAP profile can be modified and tested in order to find the optimum

configuration within a given infrastructure. For backup, data is read from disk

and written to a special file space in TSM, thus not affecting productive backups.

For restore, data is retrieved from the TSM server and written to disk before

they are deleted. For a discussion of the parameters of the Data Protection for

SAP profile that affect data throughput, see: “Adjustments to DP for SAP for

Improving Performance of Data Transfer” on page 41.

Determining the Actual Disk I/O Rate

In order to determine the actual disk reading rate, run a simulated backup of type

’No data moved to Tivoli Storage Manager’. Both the Tape Transfer Rate and the

Network Transfer Rate must be set to ’infinite’ in order to make sure there will not

be a network bottleneck. Compression must be switched off, and function ’View

Performance Data’ should show 100 % disk utilization.

The overall throughput you get with this configuration is the rate at which data is

read from disk.



In order to determine the actual disk writing rate, run a simulated restore of type

’No data moved from Tivoli Storage Manager’. Both the Tape Transfer Rate and the

Network Transfer Rate must be set to ’infinite’ in order to make sure the system

will not create a network bottleneck. Compression must be switched off, and

function ’View Performance Data’ should show 100 % disk utilization.

The overall throughput you get with this configuration is the rate at which data is

written to disk.Keep in mind that an increased disk I/O rate is shown while data is written to the

file system cache.

Determining the Actual Throughput Rate of Storage Media

In order to determine the actual writing rate of a tape, run a simulated backup of

type ’No data moved from disk’. The Disk Transfer Rate must be set ’infinite’ in

order to make sure there will not be a disk bottleneck. The number of sessions

must be set to one, Compression must be switched off, and function ’View

Performance Data’ should show 100 % disk utilization. The overall throughput you

get with this configuration is the rate at which data is written to the storage media

unless the network rate is lower than the media rate.In order to determine the actual reading rate of a tape, run a simulated restore of

type ’No data moved to disk’. The Disk Transfer Rate must be set ’infinite’ in order

to make sure there will not be a disk bottleneck. The number of sessions must be

set to one. In order to exclude a CPU bottleneck, make sure that function ’View

Performance Data’ shows 100 % network utilization.The overall throughput you get with this configuration is the rate at which data is

read from the storage media unless the network rate is lower than the media rate.

You may find that the throughput rate does not increase when the number of

sessions is increased (see ″Determining the Actual Network Throughput Rate″

below). In this case, the network throughput rate is lower than the media rate, and

the media rate cannot be determined with the Administration Assistant.

Determining the Actual Network Throughput Rate

In order to determine the actual network throughput rate, run a simulated backup

of type ’No data moved from disk’. The Disk Transfer Rate must be set to ’infinite’

in order to make sure there will not be a disk bottleneck. Increase the number of

sessions to the maximum number possible, i.e. the number of tape drives available.

To be sure that the limiting factor is not the tape transfer rate, the throughput rate

must be less than the media rate as determined in ’Determining the Actual

Throughput Rate of Storage Media’ above, multiplied by the number of sessions.

Function ’View Performance Data’ should show 100% network utilization.

The overall throughput you get with this configuration is the network throughput

rate.

Determining Throughput Rates

Table 5. Summary: How to Determine Throughput Rates

Disk I/O Rate Storage Media Rate

Network

Throughput Rate

Simulation Type No data moved

to/from Tivoli

Storage Manager

No data moved

to/from disk

No data moved

to/from disk

Disk Transfer Rate - infinite infinite

Network Transfer

Rate

infinite - -

Tape Rate infinite - -

RL Compression off off off



Table 5. Summary: How to Determine Throughput Rates (continued)

Disk I/O Rate Storage Media Rate

Network

Throughput Rate

Multiplexing 1 1 1

Number of Sessions 1 1 maximum possible

number

Drilling Down on Special Situations

When looking at the diagrams in function ’View Performance Data’, you may find

points in time when throughput or the utilization of a resource degrades

significantly. In order to understand better what happened you may drill down on

these time intervals.

In most cases you will find that a session is ending or a shorter file was

multiplexed with longer files.

Drill-Down

You drill down by selecting a time interval in either of the diagrams of the

summary panel with your mouse and choose button ’Replay Run’. Only the

selected time interval will be replayed.

Replay Mode

In replay mode, you can watch the system working: The processing is replayed for

the selected time interval. For each point in time, progress indicators show what

files are currently in progress in a session. Transfer rates are displayed and

bottlenecks are indicated by session.

Applying Backup Results to Restore

Restore versus Backup

Throughout this chapter, we are mainly dealing with optimizing backups.In most cases, configuration changes and infrastructure problems affect both

Figure 27. Drilling Down: Replay Mode



backup and restore similarly. Therefore, modifications supporting a fast backup

while exploiting resources well can generally be applied to the restore analogously.

Generally, it is recommended to tune the backup and then run a restore test (for

example a productive restore simulation) to verify that restoring still works

satisfactorily.

Note that for a restore, some parameter values are determined by the settings of

the corresponding backup. Among these are:

v Compression. If compression was switched on during backup, data needs to be

decompressed.

v Multiplexing. The same level of multiplexing as was used during backup is

automatically applied during restore.

v Multiple servers. When a backup is done using multiple servers, the same

servers must be online and available during restore.

RMAN versus File Interface

Simulating backup or restore is based on a backup of the production database

using the file interface (via BRBACKUP). A backup via the RMAN interface cannot

be used as a basis for simulation. However, modifications found during a

simulation can also be transferred to the RMAN environment and should yield

good results there as well.



Chapter 10. Reporting on Data Protection for SAP Activities

Any configuration and performance information on backup operations done with

Data Protection for SAP and the corresponding backup status of SAP database

servers can be obtained, monitored, and administered via the Administration

Assistant. The Administration Assistant Server and Database Agent components

collect status, performance, and configuration data from several SAP database

servers and keep it for a limited time. Administrators access the data via a

browser. For more information on the features and the concepts of the

Administration Assistant, refer to Chapter 8, “Installing and Using the

Administration Assistant for Data Protection for SAP,” on page 63.

However, sometimes the information is required when there is no access to the

Server component; sometimes the information must be included in other

documents or needs to be archived or printed. For these occasions, the

Administration Assistant provides the opportunity to create reports in XML or

HTML format.

Types of Reports

The reports created with the Administration Assistant basically contain the same

information that is displayed by the Administration Assistant functions Monitor

Operations, View Performance Data and Simulate Backup/Restore.

All information available is provided in XML format. Additionally, the

Administration Assistant provides style sheets for the translation into the following

built-in reports in HTML format:

v Status Report

v Operations - Detailed Report

v Operations - Daily Report

v Operations - Monthly Report

v Operations - Failure Report

v Performance Report

v Simulation Report

All built-in reports are created in English.

Reporting on Backup States

The Administration Assistant provides information on the backup status of the

SAP database servers monitored. Administrators access this information via the

function Monitor Operations. Monitor Backup States. Reports containing status

information in tabular form are requested from this panel. The overview

information provided in the panel Monitor Backup States is provided in the Status

Report.


The Operations – Detailed Report provides some more detail.

Reporting on Operations Details

Very detailed information on the latest backup operations for a single SID can be

obtained with the Operations - Detailed Report requested from the Backup State -

Detailed View panel of the Administration Assistant. This panel is reached by

selecting a single SID in the Monitor Backup States panel.

Reporting on Backup Operation Trends

This report type contains general information about the backups of a single SID.

Data is represented in graphical and tabular form. Two different report intervals

can be chosen:

v daily, graphically showing the amount of saved data for a single day , or

v monthly (for a time interval comprising several days), graphically showing

backup duration, saved data amount, throughput and log file data amount over

time.

Figure 28. Status Report

Figure 29. Operations – Detailed Report

Reporting on Data Protection for SAP Activities


These reports are requested from the Backup State – Detailed View panel of the

Administration Assistant, to be reached by selecting a single SID in the Monitor

Backup States panel.

Reporting on Failed Actions

Information on failed backup operations is provided in the Operations – Failure

Report to be requested from the Monitor Backup States panel. Administrators can

choose to include information on failed backups of log files in this report.

Reporting on the Performance of Backup Operations

The performance data of a single backup are included in the Performance Report.

Data is presented like it is done on the View Performance Data (History Mode) panel,

but showing the transfer rate and the utilization of adapters for each session. The

report is requested from the View Performance Data (History Mode) panel.

Figure 30. Operations Daily Report

Figure 31. Operations - Failure Report


Chapter 10. Reporting on Data Protection for SAP Activities 95

Figure 32. Performance Report - Graphical Presentation Section



Reporting on Simulations

An overview of simulation parameters and results for a single SID is contained in

the Simulation Report. It is requested from the Available Simulation Results panel

and shows basically a screen capture of this panel.

Prerequisites for Creating Reports

Creating reports in XML or HTML format is a function of the Administration

Assistant. For requirements and a set-up procedure of the Administration

Assistant, refer to Chapter 8, “Installing and Using the Administration Assistant for

Data Protection for SAP,” on page 63.

Figure 33. Performance Report - Tabular Presentation Section

Figure 34. Simulation Report



Creating a Report

Reports are requested from the Administration Assistant client using the graphical

user interface panels containing the information to be included.

Alternatively, reports can be generated from a scheduling client via a command

line interface, not requiring any user interaction.

Each report created is represented by an XML file, an HTML file and possibly one

or more graphic files in SVG format. The HTML and the SVG files are displayed in

the browser.

All files created can be printed or saved to the local file system using the browser

functionality. Additionally, reports, whether manually created or generated with

templates, are stored temporarily for 24 hours on the Administration Assistant

server in the following subdirectories:

<Administration Assistant install dir>/reports/<report type>_<time stamp>_<userid>/

File system access to the Administration Assistant server is required in order to

access reports stored in the report cache.

Requesting a Report from the Administration Assistant Client

Administrators request reports by selecting the Create Report button on the panels

Monitor Backup States, Backup State - Detailed View, View Performance Data (History

Mode), and Available Simulation Results of the graphical user interface of the

Administration Assistant client.

Reports requested on panels Backup State - Detailed View, View Performance Data

(History Mode), and Available Simulation Results always pertain to the single SID

currently displayed on the panel. Reports requested from panel Monitor Backup

States contain information on all SIDs displayed on the panel. Selections made in

the table of systems do not have an impact on the report created. However, active

filters or the activation of a display group is reflected in the report.

For a report, the administrator can specify a time interval. Backup operations are

included in the report if they ended within the specified time interval.

Also, some reports allow requesting the inclusion of information on log files.

Working with Report Templates

Before a report can be generated without user interaction, for example by a

scheduled script, a template must be created. Templates are created in the same

way as reports are requested from the Administration Assistant panels: Whenever

a button Create Report is pressed on an Administration Assistant panel the

administrator can choose to create a report or the corresponding template.

Each template must be given a unique name to be referenced when using the

template. The template will be stored in a file with the given name in path

<Administration Assistant install dir>/templates/<userid>/

where

<Administration Assistant install dir>



is the installation path of the Administration Assistant server. The file extension

depends on the type of report requested.

A single template can be used to generate reports on several SIDs.

A template is owned by the user creating it. It cannot be accessed or used from a

different account.

In order to view, change, or delete owned templates an administrator requests

function ’Manage templates’ from the View pull-down menu of the Administration

Assistant client.

Generating Reports Using Report Templates

Using Report Templates Administration Assistant reports can be started

automatically at given points in time using your favorite scheduler. The scheduler

must call the scheduler interface 'Sched_Main' which can be started from a

scheduling client. For details on how to set up the scheduling client refer to “4.

Setting Up a Scheduling Client for Reporting” on page 73.

The scheduling interface is called with the following syntax:

java -cp $CLASSPATH com.ibm.bkit.schedulerIF.Sched_Main <Server component hostname>...

... <RMI registry port> <template name> <userid> <password>...

... directory=<local directory> log=<log path>

where

<Server component hostname> is the name or IP address of the host running the

Administration Assistant Server component,

<RMI registry port> is the number of the RMI registry port of the Administration

Assistant Server component, as defined in its configuration file assist.cfg. The

default is 1099.<template name> is the name of the appropriate report template to be used. It must

be available in the user’s template path in the Administration Assistant Server

component.<userid> is the Administration Assistant account of the template’s owner<password> is the password of <userid>.<local directory> is the local path in the system of the scheduling client where

the requested reports are to be stored. If the local directory is not specified the

reports are not stored in the local file system. In order to access the report the

administrator needs file system access to the Administration Assistant server where

the report is kept for 24 hours.<log path> is the local path in the system of the scheduling client where the

scheduling client saves its own log files.

You may want to create a command file setting the correct environment and

scheduling one or more reports on the scheduling client system. For sample files

refer to “Sample Command Files for Scheduling Reports” on page 173.



Note

If a large number of clients try to connect to the Administration Assistant

server simultaneously, some of them may not get a connection immediately.

In this case, the scheduling client waits for a random time between 15 and 45

seconds before it tries again. After the second unsuccessful retry, the

scheduling client writes an error log and exits.

Modifying Report Output

All report requests result in the information being written to an XML file. Style

sheets residing with the Administration Assistant Server component are used to

translate the information contained in this file to different types of reports in

HTML or SVG format. They determine the appearance and contents of a specific

report.

The Administration Assistant comes with a number of built-in style sheets that are

used to create the different types of reports described above. However,

administrators may customize the style sheets to modify the look and content of

the HMTL files.

To generate a report at least one report-specific style sheet for the transformation

from XML to HTML format is necessary. If a report contains graphics each graphic

is transformed to an SVG file, requiring a separate style sheet. In this case a single

report needs a set of style sheets.

The Administration Assistant provides two types of style sheet file sets. One set is

contained in file Admt.jar and will be used as default. The second set of style sheet

set resides on the Administration Assistant server in directory:

<Admin. Assistant install dir>/styles/

Report content and appearance can be customized according to customer needs by

changing the style sheet files in this subdirectory appropriately.

The styles directory currently contains four subdirectories ('Overview', 'Detailed',

'History', 'Simulation') specifying reports based on different XML data sources,

based on data provided in the corresponding Administration Assistant panels

Monitor Backup States, Backup State - Detailed View, View Performance Data (History

Mode), and Available Simulation Results. The names of these folders are displayed in

the list of selectable report types within the Create Report dialogs.

Style sheet names must be of the format:

<report_name>_<file format>.xsl

where<file format> denotes the file type, one of HTML or SVG,

<report name> denotes the name of the file to be created.

For example, Picture1_svg.xsl will generate a file named Picture1.svg.

Please note: The name of the HTML file must always be 'report'!

For every report type an additional file config.xml exists in the 'styles'

subdirectory. This file specifies default settings of the Create Reports dialogs. For



example, the Operations – Daily Report has a reporting interval of 24 hours.

Therefore the end of the time frame does not need to be specified, and the

corresponding button will be hidden.

All style sheets contained either in file Admt.jar or in the styles directory are

displayed for selection in the Create Report dialogs of the Administration

Assistant. Style sheets contained in Admt.jar are marked by the addition '(built-in)'.

When starting the report generation the customer can specify which style sheet set

to be used. If the customizable style sheets are used, the phrase ’customized style

sheets used’ is shown on the corresponding reports.



Part 3. Appendixes


Appendix A. The Data Protection for SAP Profile

This section describes the Data Protection for SAP profile, which is used to

customize the way Data Protection for SAP operates. A sample profile initSID.utl is

provided on the installation medium.

The installation procedure for UNIX or Linux copies and renames the file to

$ORACLE_HOME/dbs/init$ORACLE_SID.utl, where $ORACLE_HOME is the Oracle

home directory and $ORACLE_SID is the Oracle System ID, for example,

/oracle/<SID>/dbs/init<SID>.utl.

The setup for Windows puts all files in an initial setup sub-directory (the default is

C:\Program Files\Tivoli\TDP4SAP for Tivoli Storage Manager). The sample profile

is found there.

The following rules apply to the syntax:

v Each line is analyzed separately.

v Keywords can start in any column of the line.

v Keywords must not be preceded by any string, except blanks.

v If a keyword is encountered several times, the last one is used.

v File processing ends when the END keyword is encountered or the end of file is

reached.

v The comment symbol is #. Scanning of the current line stops when the comment

symbol is encountered. No comment is allowed between the keyword and the

value(s). For example:

#BRARCHIVEMGTCLASS MLOG1 <-- correct

BRARCHIVEMGTCLASS MLOG1 # <-- correct

BRARCHIVEMGTCLASS # MLOG1 <-- WRONG

A few keywords are required in any case, but most are optional. Each of the

optional keywords has a preset default value.

Note: The backint program on Windows systems accepts the value of the profile

name ('-p' option) in Universal Naming Convention (UNC) format (for

example: '\\SERVER_A\profiles\init<SID>.utl'). However, any file

specifications within the profile must use the 'drive:path' syntax.

See also “Implementing Configuration Files on Remote Shares” on page 31.

Keyword Reference

The following profile keywords are obsolete for Data Protection for SAP version

5.3.

v ADSMBUFFSIZE

v BACKAGENT

v DISKBUFFSIZE

v PERF_MONITOR

v RETRY

v TCPWAIT


|

Note: In the following descriptions, the default value is underlined and applies if

the parameter is not specified.

ADSMNODE ORACLE_sid

This keyword must not be set when automated password handling is

selected. It should be set for manual password handling (see “Modifying

the Handling of the TSM Password” on page 48). If specified, ORACLE_sid

must be registered to the Tivoli Storage Manager server as a Tivoli Storage

Manager node. With this option you can assign a different node name to

your database system. It should be used if you have several SAP Oracle

database systems in your network with the same name, for example,

<SID>, and they all use the same Tivoli Storage Manager server.

Keep in Mind

This parameter must be defined in conjunction with the respective

SERVER statement, as shown in the sample profile.

BACKEND pgmname [parameterlist]

Specifies a program pgmname that is called by Data Protection for SAP after

the backup function has completed and before program control is returned

to the SAP backup utility.

If pgmname is not fully qualified the default search path is used to find the

program.

If not specified, no backend processing is done.

Example (for UNIX or Linux):

BACKEND write operator@remotesite Backup of SAP database object completed.

This sends a message to a remote user when the backup has finished.

BACKUPIDPREFIX 6-charstring | SAP___

Specifies a 6-character prefix that is used to build a backup identifier for

each archived object.

BATCH YES|NO

Specify NO if DP for SAP is running with an operator standing by.

Specify YES if DP for SAP is running in unattended mode. In this mode

DP for SAP terminates the run if operator intervention is required.

The default for the BATCH parameter is YES for the backup run and NO

for the restore run if the BATCH parameter is not present or is commented

out in the DP for SAP profile.

This parameter has no effect if an RMAN backup/restore is started.

BRARCHIVEMGTCLASS management_class [management_class...]

Specifies the Tivoli Storage Manager management class(es) DP for SAP

uses when called from BRARCHIVE. Each parameter string can consist of

up to 30 characters.

Specify a separate BRARCHIVEMGTCLASS for each log file copy

requested. Therefore, the number of different BRARCHIVE management

classes specified must be greater than or equal to the number of redo log

copies (keyword REDOLOG_COPIES on page 112.

The Data Protection for SAP Profile


For more detailed information about implementing and using

BRARCHIVEMGTCLASS see Appendix K, “Hints and Tips for BR*Tools,”

on page 201.

Keep in Mind



BRBACKUPMGTCLASS management_class [management_class...]

Specifies the Tivoli Storage Manager management class(es) DP for SAP

uses when called using BRBACKUP. The parameter string can consist of up

to 30 characters.

Keep in Mind



BUFFCOPY SIMPLE|PREVENT|AUTO

This optional parameter controls how DP for SAP uses the internal buffers

for transferring data during a backup.

If set to SIMPLE data buffers are copied when they are passed on between

Tivoli Storage Manager components. This is the default.

If set to PREVENT the original data buffers are passed on between Tivoli

Storage Manager components. For this mode, BUFFSIZE is restricted to a

maximum of 896 KB. Furthermore, it cannot be selected while the Tivoli

Storage Manager client encryption and / or client compression are

activated.

If set to AUTO Data Protection for SAP will run in PREVENT mode

whenever the configuration supports it. Otherwise, SIMPLE mode will be

selected automatically.

This parameter has no effect on restore operations.

BUFFSIZE n|131072

This parameter specifies the block size (in bytes) for the buffers used for

disk I/O. The size of the buffers passed to the Tivoli Storage Manager API

functions is the value of BUFFSIZE increased by approximately 20 Bytes.

The valid range is from 4096 (4 KB) to 32 MB. Inappropriate values will be

adjusted automatically.

If BUFFCOPY is set to PREVENT the value of BUFFSIZE must not exceed

896 KB.

If not specified, the default value is 131072 (128 KB) for UNIX or Linux

systems and 32768 (32 KB) for Windows systems. In most cases, these

values are appropriate. If you plan to increase the size of internal buffers

make sure that sufficient storage is available. The number of buffers

acquired by Data Protection for SAP correlates to the number of files

multiplexed in a data stream (keyword MULTIPLEXING) multiplied by the

number of sessions (keyword SESSIONS). By activating

RL_COMPRESSION the number of buffers is doubled.


Appendix A. The Data Protection for SAP Profile 107

COMPR_INFO path

Specifies the file where Data Protection for SAP stores information about

the compressed size of files. path specifies the full path and name of the

file.

When multiplexing is used, Data Protection for SAP attempts to put files of

the same size in one multiplexing stream to optimize performance. If

RL_COMPRESSION is used in addition to multiplexing, the file sizes of

the compressed files can differ very much from the original file sizes. Data

Protection for SAP can collect information about the compressed file sizes

and use it for further file sorting. This file size information is stored in the

file specified by the COMPR_INFO parameter.If backups shall serve as a basis for simulations (see “Simulating Backup

and Restore” on page 89), COMPR_INFO must denote a valid file and

RL_COMPRESSION must be set to YES in order to get meaningful

simulation results for compression.

When the parameter RL_COMPRESSION is set to NO, this parameter has

no effect.If specified, the info file is written after each backup and the information is

used by the following backups and simulations. If there is no compression

information about a file because of a database extension, the uncompressed

file size is used for file sorting.

CONFIG_FILE <path>/init<SID>.bki

Specifies the configuration file (init<SID>.bki)for DP for SAP to store all

variable parameters such as passwords, date of last password change, and

the current version number. A single CONFIG_FILE should never be

shared among multiple database instances or partitions. Otherwise backup

version control may not be working correctly.

This parameter is required.

END Specifies the end of the parameter definitions. DP for SAP stops searching

the file for keywords when END is encountered.

EXITONERROR YES|NO|n

This keyword specifies whether or not DP for SAP exits on a backup or

restore error during a BRBACKUP/BRRESTORE run. NO means do not

exit if an error occurs. YES means exit if one file cannot be backed up. If a

number is specified as an argument, DP for SAP counts the number of

errors (not warnings or retries) and exits after the specified number of

errors.

This keyword works only for the BRBACKUP/BRRESTORE runs.

BRARCHIVE and RMAN runs always exit after the first error.

This parameter is ignored if the BATCH parameter is set to NO.

FCS_FILE path

Specifies the profile for Data Protection for Snapshot Devices. If DP for

SAP and DP for Snapshot Devices are used together, this parameter is

mandatory. See the DP for Snapshot Devices manual for details. For a

stand-alone installation of DP for SAP, this parameter must not be used.

FILE_RETRIES n|3

This parameter specifies the number of retries when a file could not be

saved or restored.




FRONTEND pgmname [parameterlist]

Specifies a program pgmname that is called by Data Protection for SAP in a

backup run before the connection to the Tivoli Storage Manager server is

established.If pgmname is not fully qualified the default search path is used to find the

program.

If not specified, no front-end processing is done.

Example (for UNIX or Linux):

FRONTEND write operator@remotesite Backup of SAP database object is starting.

This sends a message to a remote user before backup begins.

LOG_SERVER servername [verbosity]

servername specifies the name of the Tivoli Storage Manager server to send

log messages to. The name must match one of the servers listed in a

SERVER statement, if you want DP for SAP messages logged in the activity

log of the TSM server.

verbosity may be any one of the following: ERROR, WARNING, or

DETAIL. This value determines which messages are sent. The default value

is WARNING, which means that error and warning messages are sent.

ERROR sends only error messages. DETAIL sends all message types

(errors, warnings, and informational messages).

Note that this feature is available only with Tivoli Storage Manager client

and server Version 3 or higher. If there is no LOG_SERVER statement in

the profile, log messages are not sent to any of the Tivoli Storage Manager

servers.

MAX_SESSIONS n|1

Specifies the maximum number of parallel Tivoli Storage Manager client

sessions that DP for SAP establishes for backup, archive (redo logs) and

restore.Each session transfers one database object or, in the case of an RMAN

backup or restore, a set of data blocks to or from the Tivoli Storage

Manager server by using the Tivoli Storage Manager API client functions.

DP for SAP optimizes the data transfer with regard to the physical location

of the Oracle objects. Files stored on different volumes are backed up in

parallel if multiple sessions are configured.

A maximum of 32 parallel sessions may be configured.

For a direct backup/restore on tape drives, keep the following in mind: the

number of sessions must be less than or equal to the number of tape drives

available for the backup.

Note: Make sure that the mountlimit (mountl) parameter in the device

class is set to the number of available tape drives.Make sure that the maxnummp parameter of the node is set to the

number of available tape drives.

This keyword is required.


MAX_SESSIONS see Appendix K, “Hints and Tips for BR*Tools,” on page

201.



Keep in Mind

The value of keyword MAX_SESSIONS must be less than or equal to

the sum of the SESSIONS values specified in the SERVER statements

of the currently available servers.

MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS,

MAX_RESTORE_SESSIONS, MAX_CONTROL_SESSIONS

These parameters have the same function as the MAX_SESSIONS

parameter, but they are more specific.

Keywords MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, and

MAX_RESTORE_SESSIONS define the number of parallel sessions used for

the BRARCHIVE, BRBACKUP and BRRESTORE functions. If

MAX_SESSIONS is specified with one or more of these parameters, the

more specific parameters override the MAX_SESSIONS parameter. You

must specify them all if you do not specify the MAX_SESSIONS parameter.

Keyword MAX_ARCH_SESSIONS defines the number used for archive

(backup of log files). Usually archive does not need as many sessions as

(data file) backup since the volume is much smaller with log files. This

value overrides the value of MAX_SESSIONS for the backup of database

files.

Keyword MAX_BACK_SESSION defines the number of parallel sessions

for (data file) backup. This value overwrites the value of MAX_SESSIONS

for the backup of database files.

Keyword MAX_CONTROL_SESSIONS defines the number of parallel

sessions used for backing up the control files after a database or redo log

backup. If MAX_CONTROL_SESSIONS is not specified the number of

sessions used for the control file backup is the same as for the

corresponding database or redo log backup. Typically, for a control file

backup, the number of sessions can be reduced in order to avoid

unnecessary tape mounts.

This value overwrites the value of MAX_ARCH_SESSIONS or

MAX_BACK_SESSIONS for the backup of control files.

Keyword MAX_RESTORE_SESSIONS defines the number of parallel

sessions used for restore. For restore, more tape drives may be available

than for backup. Using additional tape drives may speed up the data

transfer for restore if the backup was written to a sufficiently large number

of tapes.

This value overwrites the value of MAX_SESSIONS for restore.

For the valid range as well as the rules for keywords

MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS,

MAX_CONTROL_SESSIONS, and MAX_RESTORE_SESSIONS refer to

keyword MAX_SESSIONS.

MAX_VERSIONS n|0

n defines the maximum number of database backup versions to be kept in

backup storage. The default setting for this value is 0, meaning that backup

version control is disabled.

Be aware that if you are using backup version control, you use the same

initSID.bki file for BRBACKUP and BRARCHIVE, to avoid an unexpected

loss of data.



Every time a full backup completes successfully, the version count is

incremented by 1 and stored in the DP for SAP configuration file. This

value is also assigned to the tablespace files and to all subsequent redo log

backups. If the number of versions kept in backup storage is larger than

the specified maximum number of backup versions (stored in the

parameter MAX_VERSIONS), the oldest versions are deleted (together with

the corresponding tablespace and redo log files) until only the specified

maximum number of most recent versions remain.

Notes

v Partial backups get the same version number as the last successful

full backup. When DP for SAP deletes an old full backup, all

partial backups with the same version number are also deleted.

v Every database instance needs its own configuration file (see

parameter CONFIGURATION_FILE) and a unique

BACKUPIDPREFIX.

CAUTION

Tivoli Storage Manager uses the value of the parameter RETVER

specified when defining a copy group (see “3. Policy Definition” on

page 183) to give files an expiration date. If you use Data Protection

for SAP backup version control, you need to bypass this expiration

function. If you use the Tivoli Storage Manager expiration function,

you need to turn off Data Protection for SAP backup version control.

Use only one of these methods to control how long you keep

backups.

If you use Data Protection for SAP backup version control, set the

Tivoli Storage Manager parameter RETVER=9999 so that the files are

not considered expired and are not deleted by Tivoli Storage

Manager.

If you use Tivoli Storage Manager expiration, deactivate DP for SAP

versioning by setting MAX_VERSIONS=0.

MULTIPLEXING n|1

Specifies the number of files which are multiplexed into one data stream.

The allowed range is from 1 to 8. The optimal value depends strongly on

the actual hardware environment. Simply speaking, multiplexing makes

sense when fast tapes and fast networks are available, when the database

files are highly compressible and the CPU load is not too high. Optimal

values can be expected in the range from 1 to 4.

If not specified, the default value of 1 means ’no multiplexing’.


PASSWORDREQUIRED NO|YES

Specifies if Tivoli Storage Manager requires a password to be supplied by

the Tivoli Storage Manager client. This depends on the Tivoli Storage

Manager installation. For more information see the Tivoli Storage Manager

administrator’s manuals and “Modifying the Handling of the TSM

Password” on page 48.



If not specified, the default is PASSWORDREQUIRED YES, implementing

manual password handling.

Keep in Mind



REDOLOG_COPIES n|1

Specifies the number of copies DP for SAP stores for each processed Oracle

redo log. The valid range is from 1 to 9. If not specified, DP for SAP stores

one copy of the redo logs.

Note

The number of different BRARCHIVE management classes (keyword

BRARCHIVEMGTCLASS on page 106) specified must be greater than

or equal to the number of log file copies specified.


REDOLOG_COPIES see Appendix K, “Hints and Tips for BR*Tools,” on

page 201.

REPORT NO|YES|2

If set to YES, Data Protection for SAP produces some additional

information, for example, transferred files.

If set to 2, Data Protection for SAP generates an additional summary report

containing detailed backup/restore performance statistics. This summary is

displayed at the end of the whole run. The output is sent to stdout, which

is normally the console.

If not specified, the default is REPORT NO.

This keyword has no effect if an RMAN backup/restore is started.

RL_COMPRESSION NO|YES

If set to YES, Data Protection for SAP performs a null block compression of

the data before they are sent over the network. Although RL compression

introduces additional CPU load, throughput can be improved when the

network is the bottleneck. It is not recommended to use RL compression

together with the Tivoli Storage Manager API compression.

If not specified, the default value is NO meaning null block compression is

not performed.

Note

RL_COMPRESSION is only performed if a full database backup

(BRBACKUP) was started. The offline log files (BRARCHIVE) are not

compressed

SERVER servername

Denotes the name of the Tivoli Storage Manager server to which a path

will be established.

This statement starts a server section in the Data Protection for SAP profile.

At least one server section is required.



Server sections are located at the end of the profile. A server section ends

before a following SERVER keyword, before the END keyword, or at the

end of the profile.The following dependent keywords may appear in a server section:

ADSMNODE, BRARCHIVEMGTCLASS, BRBACKUPMGTCLASS,

PASSWORDREQUIRED, SESSIONS, TCP_ADDRESS, and USE_AT. The

server name must be defined in the Tivoli Storage Manager profiles

dsm.sys ( UNIX and Linux ) or <servername.opt> (for Windows).In order to set up alternate or parallel paths, each path is denoted by its

own logical server name and corresponding server section, although these

logical names refer to the same server. In this case, the TSM profiles

specify the same TCP/IP address for these server names.In order to set up alternate or parallel servers, each server is represented

by one or more server statements and the corresponding server sections

(depending on the number of paths to the server). In this case, the TSM

profiles specify different TCP/IP addresses for the different servers.

Different server names result in different server entries in the ″View TSM

Server Utilization″ function of the Administration Assistant, while identical

server names are considered to point to the same TSM server even if they

are specified in different Data Protection for SAP profiles throughout the

system landscape.

Note

Do NOT use any profile keywords or ’ADSM’ or ’TSM’ as the

servername.

SESSIONS n|1

n specifies the number of parallel sessions DP for SAP can start for this

server.

This keyword is required in every server section.

Keep in Mind



SORT_FILE

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

of the sortfile is:

Sort file format

/<path>/<filename1> disknumbers

/<path>/<filename2> disknumber

.

.

.

/<path>/<filenameN> disknumber

The disk numbers are counted from 1 to n. They do not have any relation

to the physical disks. You only have to specify the same number for the

files on the same physical disk.



|

|||||

TCP_ADDRESS

Specifies the IP address of this Tivoli Storage Manager server in dotted

decimal notation. This parameter overrides the value for the parameter

TCPSERVERADDRESS in the Tivoli Storage Manager client system options

file (dsm.sys) on UNIX or Linux or in the client options file

(<servername>.opt ) on Windows.

Note

The parameter TCP_ADDRESS can only be used with Tivoli Storage

Manager API Version 5.2 or higher.

Keep in Mind

The parameter TCP_ADDRESS must be defined in conjunction with

the respective SERVER statement as shown in the sample profile

below.

TRACE FILEIO_MIN | FILEIO_MAX | COMPR_MIN | COMPR_MAX |

MUX_MIN | MUX_MAX | TSM_MIN | TSM_MAX | ASYNC_MIN |

ASYNC_MAX | APPLICATION_MIN | APPLICATION_MAX | SYSCALL_MIN

| SYSCALL_MAX | COMM_MIN | COMM_MAX | DEADLOCK_MIN |

DEADLOCK_MAX | PROLE_MIN | PROLE_MAX | BLAPI_MIN |

BLAPI_MAX | SOCKET_DATA | ALL | OFF

If the parameter TRACE is specified, DP for SAP writes a trace to the file

specified with the parameter TRACEFILE. Arguments to TRACE can be

any combination of the possible components and levels separated by

spaces.

A trace will only be written if both TRACE and TRACEFILE are specified.

Note

Do not use this parameter unless your DP for SAP support asks you

to. Using it can significantly degrade the performance of DP for SAP.

TRACEFILE path

Specifies the trace file for DP for SAP to store all trace information (if

TRACE ON), path specifies the full path and the name of file.

Note

If the value of TRACEFILE contains the string ’%BID’ this string is

replaced by the backup ID to get the path and name of the trace file

actually used. For example, specifying ’/tmp/%BID.trace’ will yield a

trace file ’/tmp/myBackup.trace’ for backup ID ’myBackup’.

A trace will only be written if both TRACE and TRACEFILE are specified.

TRACEMAX n

Denotes the maximum size of the trace file in KB. If not specified, the trace

file size is unlimited.

USE_AT days

Specifies on which days the Tivoli Storage Manager server named with the



corresponding SERVER keyword will be used. ’days’ are numbers from 0

(Sunday) to 6 (Saturday). You may list several numbers, separated by

spaces.

If not specified, the default is to use the Tivoli Storage Manager server on

all days.

If you use this keyword make sure that the same TSM server is used for a

simulation and its corresponding basis production backup. For details on

simulations see “Simulating Backup and Restore” on page 89.

Keep in Mind

The parameter USE_AT must be defined in conjunction with the

respective SERVER statement as shown in the sample profile below.

The parameter has no effect on actions other than backup.

Sample Data Protection for SAP Profiles

The sample profile (initSID.utl) is included in the DP for SAP installation

package. Although the UNIX or Linux and Windows versions are mostly identical

we still show both versions below.

Sample Data Protection for SAP Profile for UNIX or Linux

#--------------------------------------------------------------------------

#

# Data Protection for SAP (R) interface for ORACLE

#

# Sample profile for Data Protection for SAP (R) Version 5.5

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

#

# See the ’Data Protection for SAP (R) Installation &

# User’s Guide’ for a full description.

#

# For a comment symbol the character ’#’ can be used.

# Everything following this character will be interpreted as comment.

#

# Data Protection for SAP (R) V5R5 accesses its profile

# in "read only" mode. 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

# BR*Tools and stored in the description field of the Tivoli Storage Manager

# archive function.

# Must be 6 characters.

# Default: none.

#--------------------------------------------------------------------------

BACKUPIDPREFIX SID___

#--------------------------------------------------------------------------

# Number of parallel sessions to be established.

# Note: This number must not exceed the number of tape drives simultaneously

# available to the node on the Tivoli Storage Manager servers to be accessed.

# The valid range of MAX_SESSIONS is from 1 and 32.



||||||||||||||||||||||||||||||||||||||||

# Default: none.

#--------------------------------------------------------------------------

MAX_SESSIONS 1 # Tivoli Storage Manager client sessions

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the database backup.


# available to the node for a database backup on the Tivoli Storage Manager

# servers to be accessed.

# The valid range of MAX_BACK_SESSIONS is from 1 to 32.

# Default: MAX_SESSIONS.

#--------------------------------------------------------------------------

#MAX_BACK_SESSIONS 1 # Tivoli Storage Manager client sessions for backup

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the redo log backup.


# available to the node for a redo log backup on the Tivoli Storage Manager


# The valid range of MAX_ARCH_SESSIONS is from 1 to 32.


#--------------------------------------------------------------------------

#MAX_ARCH_SESSIONS 1 # Tivoli Storage Manager client sessions for archive

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the backup of control

# files. This number is typically used to reduce the number of sessions

# to be used for the control file backup after another backup operation.

# The valid range of MAX_CONTROL_SESSIONS is from 1 to 32.

# Default: MAX_BACK_SESSIONS or MAX_ARCH_SESSIONS, depending on the type of

# the control file backup.

#--------------------------------------------------------------------------

#MAX_CONTROL_SESSIONS 1 # Tivoli Storage Manager client sessions for control

# file backup.

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the restore of files.


# available to the node for restore processing backup on the Tivoli Storage

# Manager servers to be accessed.

# The valid range of MAX_RESTORE_SESSIONS is from 1 to 32.


#--------------------------------------------------------------------------

#MAX_RESTORE_SESSIONS 1 # Tivoli Storage Manager client sessions for restore

#--------------------------------------------------------------------------

# Number of backup copies of redo logs.

# The valid range of REDOLOG_COPIES is from 1 to 9.

# Default: 1.

#--------------------------------------------------------------------------

#REDOLOG_COPIES 2

#--------------------------------------------------------------------------

# 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 SAP (R) should not be used together with

# Tivoli Storage Manager API compression.

# Default: NO

#--------------------------------------------------------------------------

#RL_COMPRESSION YES

#--------------------------------------------------------------------------

# Specifies how many files are read simultaneously and 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 of a single disk.

# The valid range of MULTIPLEXING is from 1 to 8.

# Default: 1 (meaning no multiplexing)

#--------------------------------------------------------------------------

#MULTIPLEXING 2

#--------------------------------------------------------------------------

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

#--------------------------------------------------------------------------

BUFFSIZE 131072 # block size in bytes

#--------------------------------------------------------------------------

# This optional parameter controls how Data Protection for SAP(R) uses

# the internal buffers for transferring data during a backup.

# Valid values: SIMPLE | PREVENT | AUTO

# Default: SIMPLE

#--------------------------------------------------------------------------

#BUFFCOPY AUTO

#--------------------------------------------------------------------------

# Name of a program to be called before the backup task is started.

# Default: none.

#--------------------------------------------------------------------------

#FRONTEND pgmname parameterlist

#--------------------------------------------------------------------------

# Name of a program to be called after the backup task is completed.

# Default: none.

#--------------------------------------------------------------------------

#BACKEND pgmname parameterlist

#--------------------------------------------------------------------------

# Maximum number of data base backup versions to be kept.

# Note: Version control by Data Protection for SAP (R) is only activated

# if the R/3 release is 3.0C and higher and the parameter MAX_VERSIONS is

# not 0.

# The valid range of MAX_VERSIONS is from 0 to 9999.

# A value of 0 means no versioning.

# Default: 0, no versioning.

#--------------------------------------------------------------------------

#MAX_VERSIONS 4

#--------------------------------------------------------------------------

# Indicates whether processing is to be done unattended or whether human

# intervention is allowed.

# Default:

# YES for backup processing

# NO for restore processing

#--------------------------------------------------------------------------

#BATCH YES # unattended automated operation

#BATCH NO # manual operation

#--------------------------------------------------------------------------

# Control of error situations: Indicates whether and when database backups

# and restore operations should be ended when an error occurs during

# unattended processing.

# Valid values:

# YES: Exit if a single file cannot be backed up or restored.

# NO: Do not exit when an error occurs.



||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

# the number of errors resulting in exiting the processing.

# The valid range of EXITONERROR is from 0 to 100.

# Default: NO.

#--------------------------------------------------------------------------

#EXITONERROR 3 # exit after 3 errors

#--------------------------------------------------------------------------

# 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

# Data Protection for SAP (R) support.

# Default: OFF.

#--------------------------------------------------------------------------

#TRACE OFF

#--------------------------------------------------------------------------

# The full path of the trace file.

# Note: for an actual trace the string ’%BID’ will be replaced by

# the current backupid.

# (.../backint_%BID.trace changes to .../backint_SAP___9809182300.trace).

# Default: none.

#--------------------------------------------------------------------------

#TRACEFILE /oracle/C21/dbs/backint.trace

#TRACEFILE /oracle/C21/dbs/backint_%BID.trace

#--------------------------------------------------------------------------

# Denotes the maximum size of the trace file in KB.

# If not specified, the trace file size is unlimited.

#--------------------------------------------------------------------------

#TRACEMAX <max size> # trace file size in KB

#--------------------------------------------------------------------------

# Specify the full path of the configuration 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 SAP (R) shall send error/status

# information to a Tivoli Storage Manager server.

# The servername must match one of the servers listed in a SERVER statement.

# Valid values for verbosity are ERROR | WARNING | DETAIL.

# Default: none.

#--------------------------------------------------------------------------

#LOG_SERVER servername [verbosity]

#LOG_SERVER server_a ERROR

#--------------------------------------------------------------------------

# Denotes if Data Protection for SAP (R) shall use a manual sorting file

# for disk sorting.

# Default: none.



||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

#--------------------------------------------------------------------------

#SORT_FILE /oracle/C21/dbs/manual_sort_file

#--------------------------------------------------------------------------

# Denotes if Data Protection for SAP (R) shall use a compressed filesize

# sorting file for disk sorting.

# For backup simulations with compression (see manual) this parameter must

# be set to a valid file.

# Default: none.

#--------------------------------------------------------------------------

#COMPR_INFO /oracle/C21/dbs/initSID.cfi

#**************************************************************************

# Statement for servers and paths.

# Multiple servers may be defined.

#**************************************************************************

SERVER server_a # Servername, as defined in dsm.sys

SESSIONS 2 # Maximum number of sessions

# to server_a

PASSWORDREQUIRED YES # Use a password

ADSMNODE NODE # Tivoli Storage Manager Nodename

BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup

BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup

# TCP_ADDRESS 192.168.1.1 # IP address of network interface

# on server_a

# Overrides IP address of dsm.sys

# USE_AT 0 1 2 3 4 5 6 # Days when server_a is used 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

#**************************************************************************

#SERVER server_b # Servername, as defined in dsm.sys

# SESSIONS 2 # Maximum number of sessions

# to server_b

# PASSWORDREQUIRED YES # Use a password

# ADSMNODE NODE # Tivoli Storage Manager Nodename

# BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup

# BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup


# on server_b


# USE_AT 0 1 2 3 4 5 6 # Days when server_b is used for

# backup

#**************************************************************************


# Default: all days

#**************************************************************************

#--------------------------------------------------------------------------

# End of profile

END

Sample Data Protection for SAP Profile for Windows

#--------------------------------------------------------------------------

#

# Data Protection for SAP (R) interface for ORACLE

#

# Sample profile for Data Protection for SAP (R)

# Version 5.5 for Windows 2000/2003

#



||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

|

#--------------------------------------------------------------------------

#

# See the ’Data Protection for SAP (R) Installation & User’s Guide’ for

# a full description.

#

# For a comment symbol the character ’#’ can be used.

# Everything following this character will be interpreted as comment.

#

# Data Protection for SAP (R) accesses its profile in "read only" mode.

# 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

# BR*Tools and stored in the description field of the Tivoli Storage Manager

# archive function.

# Must be 6 characters.

# Default: none.

#--------------------------------------------------------------------------

BACKUPIDPREFIX SID___

#--------------------------------------------------------------------------

# Number of parallel sessions to be established.


# available to the node on the Tivoli Storage Manager servers to be accessed.

# The valid range of MAX_SESSIONS is from 1 and 32.

# Default: none.

#--------------------------------------------------------------------------

MAX_SESSIONS 1 # Tivoli Storage Manager client sessions

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the database backup.


# available to the node for a database backup on the Tivoli Storage Manager


# The valid range of MAX_BACK_SESSIONS is from 1 to 32.


#--------------------------------------------------------------------------

#MAX_BACK_SESSIONS 1 # Tivoli Storage Manager client sessions for backup

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the redo log backup.


# available to the node for a redo log backup on the Tivoli Storage Manager


# The valid range of MAX_ARCH_SESSIONS is from 1 to 32.


#--------------------------------------------------------------------------

#MAX_ARCH_SESSIONS 1 # Tivoli Storage Manager client sessions for archive

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the backup of control

# files. This number is typically used to reduce the number of sessions

# to be used for the control file backup after another backup operation.

# The valid range of MAX_CONTROL_SESSIONS is from 1 to 32.

# Default: MAX_BACK_SESSIONS or MAX_ARCH_SESSIONS, depending on the type of

# the control file backup.

#--------------------------------------------------------------------------

#MAX_CONTROL_SESSIONS 1 # Tivoli Storage Manager client sessions for control

# file backup.

#--------------------------------------------------------------------------

# Number of parallel sessions to be established for the restore of files.


# available to the node for restore processing backup on the Tivoli Storage

# Manager servers to be accessed.

# The valid range of MAX_RESTORE_SESSIONS is from 1 to 32.




#--------------------------------------------------------------------------

#MAX_RESTORE_SESSIONS 1 # Tivoli Storage Manager client sessions for restore

#--------------------------------------------------------------------------

# Number of backup copies of redo logs.

# The valid range of REDOLOG_COPIES is from 1 to 9.

# Default: 1.

#--------------------------------------------------------------------------

#REDOLOG_COPIES 2

#--------------------------------------------------------------------------

# 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 SAP (R) should not be used together with

# Tivoli Storage Manager API compression.

# Default: NO

#--------------------------------------------------------------------------

#RL_COMPRESSION YES

#--------------------------------------------------------------------------

# Specifies how many files are read simultaneously and 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 of a single disk.

# The valid range of MULTIPLEXING is from 1 to 8.

# Default: 1 (meaning no multiplexing)

#--------------------------------------------------------------------------

#MULTIPLEXING 2

#--------------------------------------------------------------------------

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

#--------------------------------------------------------------------------

BUFFSIZE 32768 # block size in bytes

#--------------------------------------------------------------------------

# This optional parameter controls how Data Protection for SAP(R) uses

# the internal buffers for transferring data during a backup.

# Valid values: SIMPLE | PREVENT | AUTO

# Default: SIMPLE

#--------------------------------------------------------------------------

#BUFFCOPY AUTO

#--------------------------------------------------------------------------

# Name of a program to be called before the backup task is started.

# Default: none.

#--------------------------------------------------------------------------

#FRONTEND pgmname parameterlist

#--------------------------------------------------------------------------

# Name of a program to be called after the backup task is completed.

# Default: none.

#--------------------------------------------------------------------------

#BACKEND pgmname parameterlist

#--------------------------------------------------------------------------

# Maximum number of data base backup versions to be kept.

# Note: Version control by Data Protection for SAP (R) is only activated



# if the SAP R/3 release is 3.0C and higher and the parameter

# not 0.

# The valid range of MAX_VERSIONS is from 0 to 9999.

# A value of 0 means no versioning.

# Default: 0, no versioning.

#--------------------------------------------------------------------------

#MAX_VERSIONS 4

#--------------------------------------------------------------------------

# Indicates whether processing is to be done unattended or whether human

# intervention is allowed.

# Default:

# YES for backup processing

# NO for restore processing

#--------------------------------------------------------------------------

#BATCH YES # unattended automated operation

#BATCH NO # manual operation

#--------------------------------------------------------------------------

# Control of error situations: Indicates whether and when database backups

# and restore operations should be ended when an error occurs during

# unattended processing.

# Valid values:

# YES: Exit if a single file cannot be backed up or restored.

# NO: Do not exit when an error occurs.

# the number of errors resulting in exiting the processing.

# The valid range of EXITONERROR is from 0 to 100.

# Default: NO.

#--------------------------------------------------------------------------

#EXITONERROR 3 # exit after 3 errors

#--------------------------------------------------------------------------

# 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

# Data Protection for SAP (R) support.

# Default: OFF.

#--------------------------------------------------------------------------

#TRACE OFF

#--------------------------------------------------------------------------

# The full path of the trace file.

# Note: for an actual trace the string ’%BID’ will be replaced by

# the current backupid.

# (...\backint_%BID.trace changes to ...\backint_SAP___9809182300.trace).

# Default: none.

#--------------------------------------------------------------------------

#TRACEFILE x:\oracle\C21\database\backint.trace

#TRACEFILE x:\oracle\C21\database\backint_%BID.trace

#--------------------------------------------------------------------------

# Denotes the maximum size of the trace file in KB.

# If not specified, the trace file size is unlimited.

#--------------------------------------------------------------------------

#TRACEMAX <max. size> # trace file size in KB

#--------------------------------------------------------------------------

# Specify the full path of the configuration file.

# Default: none.



#--------------------------------------------------------------------------

CONFIG_FILE x:\oracle\C21\database\initSID.bki

#--------------------------------------------------------------------------

# Number of times to retry saving/restoring a file in case an error occurs.

# The valid range of FILE_RETRIES is from 0 to 100.

# Default: 3.

#--------------------------------------------------------------------------

#FILE_RETRIES 3

#--------------------------------------------------------------------------

# Denotes if Data Protection for SAP (R) shall send error/status

# information to a Tivoli Storage Manager server.

# The servername must match one of the servers listed in a SERVER statement.

# Valid values for verbosity are ERROR | WARNING | DETAIL.

# Default: none.

#--------------------------------------------------------------------------

#LOG_SERVER servername [verbosity]

#LOG_SERVER server_a ERROR

#--------------------------------------------------------------------------

# Denotes if Data Protection for SAP (R) shall use a manual sorting file

# for disk sorting.

# Default: none.

#--------------------------------------------------------------------------

#SORT_FILE x:\oracle\C21\database\manual_sort_file

#--------------------------------------------------------------------------

# Denotes if Data Protection for SAP (R) shall use a compressed filesize

# sorting file for disk sorting.

# For backup simulations with compression (see manual) this parameter must

# be set to a valid file.

# Default: none.

#--------------------------------------------------------------------------

#COMPR_INFO x:\oracle\C21\database\initSID.cfi

#**************************************************************************

# Statement for servers and paths.

# Multiple servers may be defined.

#**************************************************************************

SERVER server_a # Servername, as defined in dsm.sys

SESSIONS 2 # Maximum number of sessions

# to server_a

PASSWORDREQUIRED YES # Use a password

ADSMNODE NODE # Tivoli Storage Manager Nodename

BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup

BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup


# on server_a


# USE_AT 0 1 2 3 4 5 6 # Days when server_a is used for

# backup

#**************************************************************************


# The valid range of USE_AT is from 0 to 6.

# Default: all days

#**************************************************************************

#SERVER server_b # Servername, as defined in dsm.sys

# SESSIONS 2 # Maximum number of sessions

# to server_b

# PASSWORDREQUIRED YES # Use a password

# ADSMNODE NODE # Tivoli Storage Manager Nodename

# BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup

# BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for redo log backup




# on server_b


# USE_AT 0 1 2 3 4 5 6 # Days when server_b is used for

# backup

#**************************************************************************


# Default: all days

#**************************************************************************

#--------------------------------------------------------------------------

# End of profile

END



Appendix B. Data Protection for SAP (Oracle) Messages

This chapter describes how to find message files (log files) and explains the

individual messages issued by DP for SAP.

How To Find Files Containing Message Output (Log Files)

Data Protection for SAP process results are logged in files. These files are located

in the following paths:

UNIX or Linux:

v $SAPDATA_HOME/sapbackup for backup and restore runs

v $SAPDATA_HOME/saparch for redo log archive runs

Windows:

v %SAPDATA_HOME%\sapbackup for backup and restore runs

v %SAPDATA_HOME%\saparch for redo log archive runs

All log files written during a backup, restore or archive are listed in summary log

files with start and end timestamps. The summary log files are located in the same

directory as the log files themselves and have the following names:

v back<SID>.log

v rest<SID>.log

v arch<SID>.log

If you are running Oracle RMAN you will also need to look up the file sbtio.log,

which is specified by user_dump_dest in the Oracle control files. For most

installations it is defined as $SAPDATA_HOME/saptrace/usertrace/sbtio.log. This

file contains all messages issued by the DP for SAP RMAN connector during

operation of Oracle RMAN.


Prefix BKI

The messages begin with the prefix BKI and are listed in numerical order.

For each message, the following information is provided:

v Message number

v Severity code

The following letters give an indication of the severity of the action that

generated the message. The severity codes and their meanings are as follows:

E Error Processing cannot continue.

W Warning Processing can continue, but problems may occur later.

I Information Processing continues. User response is not necessary.

v Explanation

v User Response

BKI0000E Profile not specified.

Explanation: Cannot locate the profile.

User response: Ensure that a profile is available.

(Oracle) Note that the BACKINT call must have the

following form: backint -p init<SID>.utl .

BKI0004E Function not defined.

Explanation: BRTOOLS, BRBACKUP, or BRARCHIVE

passed an invalid argument to DP for SAP.

User response: Ensure that you have the correct

version of BR*Tools installed. Valid functions are: -f

backup or -f restore or -f password or -f delete or -f inquire.

BKI0005I Start of program at: time

Explanation: DP for SAP received control from a

BR*Tools utility at the time denoted.

User response: None.

BKI0006E Type for backup not defined [type].

Please use ’file’ or ’file_online’.

Explanation: DP for SAP expects as the backup type

parameter only file or file_online.

User response: If you start DP for SAP manually to

do a backup, ensure that the type option (-t) receives

the correct arguments (file or file_online). If your DP

for SAP has been invoked by one of the SAP database

utilities (e.g., BRBACKUP), ensure that the SAP backup

profile init<SID>.sap is customized correctly) .

BKI0007E Mode mode requires the environment

variable environment variables to be set.

Explanation: Not all environment variables required

have been set. At least environment variables where

missing.

User response: Set the missing environment variables.

BKI0008E The environment variable name is not

set correctly. The current value is value.

Explanation: The value of the environment variable

name is wrong.

User response: Set name to an appropriate value.

BKI0020I End of program at: time

Explanation: (Oracle) DP for SAP returned control to a

BR*Tools utility at the time denoted. (DB2) Program

tdppasswd ended at the time indicated.


BKI0021I Elapsed time: elapsedtime

Explanation: The time needed for the complete

backup was elapsedtime.


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

Explanation: Finished saving a specific object at

current_time. The saved_bytes amount of the total

number of bytes have been saved. percent shows the

percentage. This call will be completed at the estimated

end_time.


BKI0024I Return code is: return code

Explanation: A return code of 0 means no errors or

warnings occurred. If the return code is 1, at least one

warning was issued by the program. If the return code

is 2, at least one error message was issued.

Messages


User response: For return codes other than 0, check

the run log for warnings or error messages.

BKI0027I Time: current_time

Objects: current_num of total_numin process: file_nameMGMNT-CLASS: management_classTSM Server: server name.

Explanation: DP for SAP started saving current_num

files at current_time. The total number of files to save is

total_num. The file file_name is currently being

processed. The files are transferred to the Tivoli Storage

Manager server server name, which stores them in the

management class management_class.


BKI0032E Error opening file file name: system error

description

Explanation: A system error occurred during opening

of the file file name. system error description will describe

the error in more detail.

User response: Read the system error description.

BKI0049I Please enter password for node nodename

on server server name

Explanation: The password for the node nodename on

the Tivoli Storage Manager server server name has to be

entered for storing it in the DP for SAP configuration

file.

User response: Enter the password for the

corresponding Tivoli Storage Manager server.

BKI0050I Please enter password for node nodename

on server server name again

Explanation: In order to avoid typing errors, you have

to enter the password twice.

User response: Enter the password again.

BKI0051I Password successfully verified for node

nodename on server server name.

Explanation: The password for the node nodename on

the Tivoli Storage Manager server server name was

changed successfully.


BKI0052E Password verification for node nodename

on server server name failed.

Explanation: The password you entered for the node

nodename on the Tivoli Storage Manager server server

name was wrong.

User response: Enter the password again. If this error

still exists, contact your Tivoli Storage Manager

administrator.

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

Explanation: DP for SAP completed saving

current_num file at current_time. The total number of

files to be saved is total_num. The file file_name with the

size bytes is saved with the description object_desc.


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

Explanation: DP for SAP completed restoring of

current_num file at current_time. The total number of

files to be restored is total_num. The file file_name with

the size bytes is restored with the description

object_class.


BKI0055I Object objectname with size saved with

description description.

Explanation: The object objectname was saved

successfully.


BKI0056I Object objectname with size restored with

description description.

Explanation: The object objectname was restored

successfully.


BKI0057I Time: current_time Object objectname with

size saved with description description.

Explanation: The object objectname was saved

successfully.


BKI0058I Time: current_time Object objectname with

size restored with description description.

Explanation: The object objectname was restored

successfully.


Messages

Appendix B. Data Protection for SAP (Oracle) Messages 127

BKI0059E You have to set the environment

variable DSMI_CONFIG to the full

filename of the Tivoli Storage Manager

client option file ’dsm.opt’.

Explanation: Tivoli Storage Manager client option file

not found.

User response: Verify that the Tivoli Storage Manager

option file dsm.opt is pointed to by DSMI_CONFIG.

BKI0060E The parameter parameter is not known.

Explanation: The command parameter parameter is

unknown.

User response: Check the specified command

parameter and try again.

BKI0061W The output file file name is not valid.

Explanation: The specified output file file name could

not be created.

User response: Check that file name is a valid file

name on your operating system. Also check that the

application has the appropriate permissions to create

the file within the specified directory. The directory

must already exist. If the file already exists, rename the

old one.

BKI0062E The input file file name is not valid.

Explanation: Unable to read the input file file name

correctly.

User response: Check the path and name of the input

file and the appropriate file access permission.

BKI0063E The UTL file file name is not valid.

Explanation: Unable to read the input file file name

correctly.

User response: Check the path and name of the

profile (UTL file) and the appropriate file access

permission.

BKI0064E The option option is unknown.

Explanation: An option is invalid or unknown.

User response: Check the specified option(s) and try

again.

BKI0065E The argument is missing for option

option.

Explanation: Every option requires an argument.

User response: Insert the missing argument and try

again.

BKI0101I Session session: Please enter ’cont’ to

continue or ’stop’ to cancel.

Explanation: If DP for SAP is running in unattended

mode (profile keyword BATCH), it terminates the

current run if operator intervention is required.

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

BKI0102I Your reply: reply.

Explanation: The reply you made is confirmed.


BKI0311E Request canceled by user.

Explanation: (Oracle) BACKINT terminated at user’s

request. (DB2) Program terminated at user’s request.

User response: None

BKI0400I TDP is waiting for BRBACKUP

Explanation: DP for SAP is waiting for BRBACKUP to

set a tablespace in the begin/end backup mode.


BKI0405I TDP waited num_sec sec. for

BRBACKUP in util_file_online

communication.

Explanation: DP for SAP waited num_sec seconds for

BRBACKUP to set a tablespace in begin/end backup

mode.


BKI0410E Cannot open or delete switch file file

name. Check permissions.

Explanation: If DP for SAP is not installed correctly

(as the root user on UNIX or Linux or administrator

group on Windows) then DP for SAP is not able to

open the necessary communication file to the SAP

system.

User response: Check the file permission.

BKI0411E Maximum time waiting for BRBACKUP

expired.

Explanation: The SAP database utilities did not

respond within the expected time.

User response: Contact your SAP administrator.

BKI0412E BRBACKUP wasn’t able to switch

requested tablespace in BEGIN/END

BACKUP mode.

Explanation: DP for SAP could not continue the

backup, because BRBACKUP was not able to switch the

Messages


requested tablespace in BEGIN or END backup mode.

This is necessary for locking the tablespace.


BKI0413E Error while requesting tablespace

switch.

Explanation: BRBACKUP could not switch tablespace

in BEGIN or END backup mode.


BKI0414E Error while requesting tablespace

switch.

Explanation: BRBACKUP reported an error while

trying to switch a tablespace in BEGIN or END backup

mode.


BKI0450I Version 2 restore: file

Explanation: A restore of data backed up with DP for

SAP version 2 was executed.


BKI0452E This version of product has expired.

Explanation: This is a test version that has expired.

User response: Order a release version of the product

or contact your IBM/Tivoli Sales Representative.

BKI0453W This version of product will expire in

number days.

Explanation: This is a test version with a time limit. It

will expire in number days.

User response: Order a release version of the product

or contact your IBM/Tivoli Sales Representative before

the version expires.

BKI0454I *** This copy is NOT FOR RESALE. ***

Explanation: This version is not for resale.


BKI0455E License file file name does not exist.

Explanation: The license file agent.lic was not found

where expected.

User response: Make sure that the agent.lic file

resides in the same directory as the init<SID>.utl file.

BKI0456E Unable to access license file file name.

Explanation: The license file could not be accessed.

User response: Make sure the access permissions

allow read/write access.

BKI0457E License file file name contains invalid

data/checksum.

Explanation: The license file is invalid.

User response: Make sure you have the right

agent.lic file for the right platform installed.

agent.lic files are platform dependent.

BKI0458I Fake-Mode is activated.

Explanation: This message signals that the current

operation is a simulated operation. Simulations can be

performed using the Administration Assistant.


BKI0459E More than one mux file is found with

the same name detailed backup description.

Explanation: Two or more data sources with name

detailed backup description exist.

User response: Contact the product administrator.

BKI1000E Syntax error in line line: statement

Explanation: The statement statement in the DP for

SAP profile is unknown or incorrect.

User response: Correct the error and try again.

BKI1001E Syntax error in file file name. Exiting

Program.

Explanation: A syntax error has been detected in the

file file name and the action has been halted.

User response: Correct the error(s) in the file file name

and try again.

BKI1002E BACKUPIDPREFIX must be

number_of_characters characters.

Explanation: The length of BACKUPIDPREFIX must

be number_of_characters characters.

User response: Enter a BACKUPIDPREFIX with the

required length (e.g., SAP___, BKI___).

BKI1003W Please set REDOLOG_COPIES to a

number between 1 and max_copies. Now

it is set to act_copies.

Explanation: DP for SAP currently supports 1 to 9

copies of offline (redo) log files.

Messages


User response: Adapt the REDOLOG_COPIES settings

in the DP for SAP profile.

BKI1004W You should specify the

BACKUPIDPREFIX before the

TRACEFILE statement, so that the

BACKUPIDPREFIX can be used in the

tracefile name.

Explanation: The BACKUPIDPREFIX is used to build

the Name of the tracefile. Therefore,

BACKUPIDPREFIX must be specified before the

TRACEFILE statement.

User response: Define a 6-character

BACKUPIDPREFIX in the DP for SAP profile (e.g.,

SAP___, BKI___)

BKI1005W The tracefile name trace_filename should

be absolute.

Explanation: None.

User response: Specify an absolute tracefile name, for

example /oracle/C21/saptrace/tracefile or

/db2/C21/saptrace/tracefile .

BKI1006E The SERVERNAME must be less than

max_char characters.

Explanation: You have used a SERVERNAME with

more than max_char characters.

User response: Use a shorter SERVERNAME.

BKI1007E The NODENAME must be less than


Explanation: You have used a NODENAME with

more than max_char characters.

User response: Use a shorter NODENAME.

BKI1008E The MANAGEMENTCLASSNAME

must be less than max_char characters.

Explanation: You have used a

MANAGEMENTCLASSNAME with more than


User response: Use a shorter

MANAGEMENTCLASSNAME.

BKI1009W Please set MULTIPLEX to a number

between 1 and max_multiplex. Now it is

set to act_multiplex.

Explanation: You have set multiplexing to an

unsupported number. DP for SAP now uses

act_multiplex.

User response: Set multiplexing to a number between

1 and max_multiplex.

BKI1010W The configfile name

configuration_filename should be absolute.

Explanation: None.

User response: Specify an absolute file name, for

example /oracle/C21/dbs/initC21.bki or

/db2/C21/dbs/initC21.bki

BKI1011W The sortfile name sortfile_filename should

be absolute.

Explanation: None.

User response: Specify an absolute file name, for

example /oracle/C21/dbs/sortfile.

BKI1012E Configfile not found or permission

denied: configuration_filename.

Explanation: DP for SAP is unable to read the file

configuration_filename.

User response: This error could have various reasons,

try the following:

1. Check the path of the configuration file. The path

must be specified in the profile (parameter

CONFIG_FILE).

2. Make sure that the file access permissions are set

correctly.

BKI1013E Profile not found or permissions denied:

profile_filename.

Explanation: DP for SAP is unable to open the profile

profile_filename.

User response: (Oracle) Ensure that the SAP backup

profile init<SID>.sap contains a valid entry

util_par_file for the DP for SAP profile. (DB2) Ensure

that the vendor environment file contains a valid entry

XINT_PROFILE. Furthermore, this file must be readable

by DP for SAP. For details see “Installing Data

Protection for SAP” on page 26 and “Problem

Resolution During Installation and Setup” on page 151.

BKI1016W The trace file name file name could not

be opened for writing!

Explanation: The trace file could not be opened for

writing.

User response: Ensure that you have specified a

correct path for the trace file.

BKI1019E Failed to respond to a message received

from XINT.

Explanation: This messages indicates an internal error.

User response: Contact DP for SAP support.

Messages


BKI1020W The compress info file file name should

be absolute !

Explanation: The argument for the parameter

COMPR_INFO in the profile is an relative filename.

User response: Always use an absolute filename as

argument for the parameter COMPR_INFO.

BKI1021E component_name terminates the

connection due to a previous error.

Explanation: A serious error has occurred which

caused a shutdown of the communication channel

between the component_name process and this

application.

User response: Look for previous error messages to

detect the root cause of the problem.

BKI1022E component_name terminates the

connection due to a previous error.

Explanation: See message BKI1021E.

User response: See message BKI1021E.

BKI1023W Could not establish connection to log

server log server name.

Explanation: In the DP for SAP profile, log server log

server name is specified (keyword LOG_SERVER).

However, a connection to the server named could not

be established. No log records are sent to the log server.

User response:

v Check that the server name defined with keyword

LOG_SERVER is spelled correctly in the DP for SAP

profile.

v Make sure there is a SERVER section in the profile

for the log server defined with keyword

LOG_SERVER.

v Check the corresponding SERVER section and correct

any setup problems.

v Make sure that the log server named is available.

BKI1200E Cannot read/write file: file name.

Explanation: The program is unable to read or write a

data file (file name) of a tablespace being backed up or

restored.

User response: Check the file access permission of the

affected file(s). Try again. If the problem still exists,

contact the product's administrator.

BKI1201E There are no Tivoli Storage Manager

Servers available.

Explanation: DP for SAP cannot locate a Tivoli

Storage Manager server. This may be due to a

configuration problem or to a problem while trying to

connect to the Tivoli Storage Manager server. Most

probably, a preceding error message points to the cause

of the problem.

User response: Look for and respond to preceding

error messages. You may also want to check the DP for

SAP profile and the IBM Tivoli Storage Manager client

options and client system options files.

BKI1202E You must specify either

MAX_SESSIONS, or all three specific

session options

(MAX_ARCH_SESSIONS,

MAX_BACK_SESSIONS, and

MAX_RESTORE_SESSIONS).

Explanation: Information on the number of Tivoli

Storage Manager client sessions to be established by DP

for SAP is missing from the profile.

User response: In the DP for SAP profile, either

specify a value for keyword MAX_SESSIONS, or

specify values for the three specific session parameters

(MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, and

MAX_RESTORE_SESSIONS).

Any of the specific options can be specified in

combination with MAX_SESSIONS. Then, it overrides

the value of MAX_SESSIONS for the specific function.

BKI1203E Not enough sessions available (number

of sessions required and number of

sessions available).

Explanation: The sum of available sessions specified

in the various server statements (parameter SESSIONS)

does not cover the required number of sessions

(parameter MAX_SESSIONS).

User response: Change the values of the

corresponding parameters in the DP for SAP profile, so

that the condition mentioned in the explanation is

fulfilled.

BKI1205E If you want num_redo

REDOLOGCOPIES on Tivoli Storage

Manager-Server servername, you should

give me at least num_mc different

Archive Management Classes.

Explanation: DP for SAP requires that the number of

different Archive Management Classes (parameter

BRARCHIVEMGTCLASS) on the Tivoli Storage

Manager servers is equal to or greater than the number

of redo log or log file copies (parameter

REDOLOG_COPIES).

User response: Define at least as many different

Archive Management Classes as log file copies

requested.

Messages


BKI1206W If you want num_redo

REDOLOGCOPIES on Tivoli Storage

Manager Server server name, you should

give me at least num_mc different

Archive Management Classes.

Explanation: The message appears during a

BRBACKUP run. A BRARCHIVE run afterwards would

fail.

User response: Define at least as many different

Archive Management Classes as log file copies

requested.

BKI1207E Directory backup not supported

Explanation: This option is not yet available.

User response: Wait for a future release of DP for SAP,

which supports this option.

BKI1208W The object file name will be retried

[retry_num]

Explanation: An error occurred while processing

object file_name. DP for SAP is repeating the action

according to the number of retries specified in the

profile. retry_num is the current retry count.

User response: If the problem persists check for and

respond to preceding error messages

BKI1209E Object not found or not accessible

objectname.

Explanation: The object cannot be located.

User response: The backup integrity is affected.

Contact SAP or DP for SAP support.

BKI1210E Input file not found or not accessible file

name.

Explanation: DP for SAP cannot locate the temporary

file named. This file contains the list of Oracle objects

to be backed up or restored. It is passed to DP for SAP

by one of the BR*Tools utilities.

User response: Ensure that you have the correct

version of BR*Tools installed. For details, check with

the release notes (RELNOTE).

BKI1211E There is something wrong with your

CONFIG_FILE file name.

Explanation: There is a problem with your DP for

SAP configuration file setup.

User response: Check the file permission and the file

name specified in the DP for SAP profile keyword

CONFIG_FILE.

BKI1212W The file file name was not found in the

manual sorting file.

Explanation: The file you want to back up was not

found in the manual sorting file.

User response: Check and correct the manual sorting

file so that it contains all the files you are backing up.

BKI1214E TSM Error: error text

Explanation: The specified TSM error occurred.

User response: Check error text and correct the

problem. For further information you may want to

refer to IBM Tivoli Storage Manager Messages SC32-9090

BKI1215I Average transmission rate was number

GB/h (number MB/sec).

Explanation: The average transmission rate is

displayed.


BKI1216E There are no BRBACKUPMGTCLASSES

available.

Explanation: The BRBACKUPMGTCLASSES you have

specified in your init<SID>.utl file are not correct.

User response: Check the management classes on the

TSM server and specify correct ones.

BKI1217E There are no BRARCHIVEMGTCLASSES

available.

Explanation: The BRARCHIVEMGTCLASSES you

have specified in your init<SID>.utl file are not correct.

User response: Check the management classes on the

TSM server and specify correct ones.

BKI1222E Version mismatch error. Check setup

(version_1:version_2).

Explanation: Different components with inconsistent

versions are used.

User response: Check your setup or contact DP for

SAP support.

BKI1223W A problem occurred during send of

performance data to Administration

Assistant .

Explanation: There was a problem sending the

performance data to the Administration Assistant over

the network.

User response: Check your setup or contact DP for

SAP support.

Messages


BKI1227I Average compression factor was number.

Explanation: The data transferred had been

compressed by the factor number.

User response: None

BKI1228W Server server name can not be used with

password access method GENERATE in

this environment. The process is

running with user ID number but the

effective user ID is number.

Explanation: The user ID and the effective user ID of

the process are different. In order to utilize the

password access method GENERATE the IDs must be

equal.

User response: Change the value for the parameter

″PASSWORDACCESS″ in the file dsm.sys (UNIX and

Linux) or servername.opt (Windows) from ’generate’ to

’prompt’. Reset the password for this node at the Tivoli

Storage Manager server and run (for Oracle) backint

-f password or (for DB2) backom -c password . This

prompts you for the password and stores it encrypted

in the DP for SAP configfile. Each time your password

expires you have to repeat the last step.

BKI1229E Value for parameter BUFFSIZE (actual

cur_number, maximum max_number) is

too large for BUFFCOPY mode

PREVENT.″

Explanation: To utilize the BUFFCOPY mode

PREVENT the value for the parameter BUFFSIZE must

not be larger than max_number.

User response: In the DP for SAP profile, specify a

BUFFSIZE less or equal to max_number if you need to

prevent copying buffers when passing data between

Tivoli Storage Manager components. If you need large

buffers you can set option BUFFCOPY to SIMPLE or

AUTO. As a consequence, buffers are copied when data

is passed between Tivoli Storage Manager components.

BKI1230E The following file was not processed:

path.

Explanation: The operation was terminated due to a

previous error. As a consequence, the file named could

not be processed. The cause of the error should be

found in an earlier message.

User response: Check for and respond to preceding

error messages.

BKI1505E Operation aborted because a different

operation by this database client is

already running.

Explanation: Different concurrent operations of the

same type were started for the same database. This is

not supported. The current operation is aborted.

This message is also issued when a cooperative

operation of two or more participating partitions was

started, but the profile settings used for the various

partitions do not match.

User response: Wait until the currently running

operation has ended and try again. Make sure that

multiple operations are not started concurrently for a

database.

If this is a cooperative operation with two or more

participating partitions, check that the profile settings

of the various partitions (for example, DEVICE_TYPE,

MAX_VERSIONS, etc.) do not differ. If they do, fix the

profile settings, cancel the current operation, and start

the operation again. Also, investigate the possibility of

sharing the same profile among all partitions.

BKI1506E Failed to execute command command.

Output follows:

Explanation: The system tried to execute the

command cited. During execution, an error occurred.

The output received from the command shell is listed

following the message.

User response: Determine the cause of the problem

from the command and the output listed in the

message, and resolve the problem.

BKI1507E The process needs to run with root

authority.

Explanation: The current process requires root

authority.

User response: Start the process under an account

with root authority.

BKI1508E The service service_name has terminated

due to a previous error. Please check all

logs for additional information.

Explanation: The cited service is no longer available.

User response: Check the appropriate logs for the

cause of its termination.

BKI1509E Authentication failure. The password

specified does not qualify for accessing

component.

Explanation: To access the named component, a

password is required. However, the password provided

could not be verified.

User response: Make sure that the password files used

by the different components of the system match.

Messages


|||

||||

||

||||

|||

| | | |

| | | |

| | | | | | |

BKI1510I New connection received.

Explanation: The server received a new connection

request.


BKI1511I New type_of_operation operation started

for database instance instance, database

database_name.

Explanation: A connection request resulted in the start

of a new operation of the type indicated.


BKI1512E An error occurred during shutdown:

Error information

Explanation: During shutdown of the component, a

problem occurred. The error information is given.

User response: Resolve the problem indicated by the

error information.

BKI1513I *****> Database client connected:

Instance instance, database database_name,

partition partition_number

Explanation: This message follows a message

BKI1511I and indicates the connection of one of the

database clients taking part in the operation. A

database client is an instance of the snapshot backup

library representing a single partition of the database.


BKI1514I *****> Device client connected.

Explanation: This message follows a message

BKI1511I and indicates the connection of one of the

device clients taking part in the operation. A device

client is an instance of the device agent for the storage

device.


BKI1515I Client is logging to file_name.

Explanation: The client’s log messages are written to

the indicated file.


BKI1517I Deleting target data container defined

by container_description.

Explanation: The data in the container indicated is

removed.


BKI1518E Internal error: The system is trying to

use the same device agent, although the

synchronization mode is not

PARALLEL.

Explanation: The system has been told to use the

same device agent for multiple database clients, but the

database indicated serial synchronization mode. This

setup is not supported.

User response: Contact your IBM support personnel.

BKI1519E A failure occurred during initialization

of one or more of the nodes

participating in this operation. Please

check the logs for more information.

Explanation: Some problem occurred during the

initialization of a new operation. The problem may be

with any component required for this operation.

User response: Check the acsd log file for messages

BKI1515I to determine the log file names of the

participating agents. Check the log files of each

component for the cause of the problem.

BKI1520E Volume volume_name is shared across

partitions. Volume sharing is not

allowed.

Explanation: At least two partitions own data residing

on the volume indicated. This setup is not supported.

User response: With the current disk layout of the

database, the requested function cannot be used. If you

want to use the function, change the disk layout of the

database so that each data volume is dedicated to a

partition.

BKI1521I Retaining number backups

Explanation: When enforcing profile parameter

MAX_VERSIONS, the indicated number of backups is

kept.


BKI1522E The requested meta-information

(subject=″description″) is not available.

Explanation: Some meta-information about each

backup is stored in the repository. An error occurred

when trying to retrieve part of this information.


BKI1523W Warning: The following containers were

reused without being explicitly released:

description

Explanation: The containers defined by the

description are used by the current backup. They were

used before by a different backup. This message is

Messages


expected in SAN environments where data containers

are usually kept until they are reused. In this case, this

message does not indicate a problem.


BKI1525E The process service_name is in an

inconsistent state. Please check for

previous errors and restart the process

afterwards.

Explanation: The process indicated cannot continue

with inconsistent data.

User response: Check the logs for messages pointing

to the cause of the inconsistency. After resolving any

problems, restart the process.

BKI1526E A configuration file (profile) must be

provided.

Explanation: An operation was started without

providing a profile.

User response: Check the user documentation on how

to provide the profile to the current process. Start the

process again using a valid configuration file.

BKI1529E The device ’device_type’ you entered is

not supported by the wizard.

Explanation: The device type represents a certain type

of storage device. While using the setup wizard, a

device type was entered that is not supported by the

current version of the wizard.

User response: Refer to your user documentation for a

list of the device types that are supported by default.

Specify one of the supported types.

BKI1530E Failed to launch the device agent for

device_type. Please consult your user

documentation to make sure that all

requirements for the specified device

are met.

Explanation: The system was unable to launch the

appropriate device agent for the type indicated because

some of its requirements are not met.

User response: Refer to your user documentation and

make sure that the system is set up correctly for the

specified device type.

BKI1534E Unexpected version actual_version of the

repository located in path. Expected

version: supported_version

Explanation: The server located the repository in the

path indicated. However, the version of the repository

located on disk does not match the current version of

the server.

User response: Make sure to use the correct instance

of the server. Ensure that the path of the repository was

specified correctly. Refer to the release notes for a list of

possible incompatibilities.

BKI1535E Unexpected characteristics

(bitwidth=number) of the repository

located at path. Expected bitwidth:

number

Explanation: The repository located in the path

indicated was saved to disk using a bit width different

from the bit width the server is using to load the

repository.





BKI1536E The repository located at path is not

valid.

Explanation: A repository could not be found at the

location indicated by path.

User response: Ensure that the path of the repository

was specified correctly. Do not edit any files in the

repository path.

BKI1537E The repository located at path was

written with an incompatible protocol

(protocol_version). Expected protocol:

protocol_version

Explanation: The repository found at the location

indicated was written to disk using the protocol

version named. However, the server currently supports

the expected protocol version.

User response: Ensure that the path of the repository

was specified correctly. Do not edit any files in the

repository path.

BKI1538E Unexpected repository type. The path

’path’ does not point to a repository of

type ″protocol_type″.

Explanation: The repository located in the path

indicated was written to disk using a protocol different

from the protocol supported by the server process.





BKI1539E Root privileges required. Could not

change user ID to root.

Explanation: The requested operation requires root

Messages


privileges. However, the process could not acquire

them.

User response: Make sure the appropriate privileges

(s-bit) are granted to the executable.

BKI1540E /etc/inittab entries are limited to 127

characters. Please consult your user

documentation for information on

manually completing the installation

procedure.

Explanation: The command line generated by the

setup function exceeds 127 characters. This situation

requires user intervention. The setup function did not

update /etc/inittab.

User response: Refer to your user documentation for

information on what entries to add to /etc/inittab.

BKI1541E /etc/inittab was not updated because

some of the processes have apparently

already been added. Please re-run the

setup after calling the setup script with

option '-a disable' if you want to change

to a standard setup.

Explanation: During the automatic setup, entries for

this product were detected in /etc/inittab. This is an

indication that the product was not previously

uninstalled.

User response: Run the setup with option '-a disable'

and then start the installation process again. If the

entries in /etc/inittab should be retained, refer to your

user documentation for information on how to

complete the installation manually.

BKI1542E Failed to uninstall because some of the

processes to be uninstalled are still

listed in /etc/inittab. Please re-run the

setup after stopping the component by

calling the setup script with option '-a

stop'.

Explanation: Before uninstalling the product, the

affected processes must be stopped. This is done by

running the setup script with the option ‘-a stop’,

which will remove the entries from /etc/inittab and

stop the processes.

User response: Refer to your user documentation for

information on the uninstall process. Run the setup

with the option “-a stop” and then continue

uninstalling.

BKI1543E The component is still referenced within

the /etc/inittab. In order to terminate the

component rerun the setup script with

option ’-a stop’.

Explanation: The setup utility detected that the

product is still active in the system. Apparently, its

entries in /etc/inittab are not yet removed.

User response: Call this process again with the option

“-f stop”.

BKI1544E New entries cannot be added to

/etc/inittab because it already contains

too many entries starting with ’ac’.

Please refer your user documentation for

a manual setup of this package.

Explanation: During setup, an unusually high number

of entries beginning with “ac” were detected in

/etc/inittab. /etc/inittab was not modified.

User response: Determine if these entries are

expected, or if they were added due to a problem. If

these entries are required, refer to your user

documentation for information on how to complete the

installation manually.

BKI1545E IBM Tivoli Storage Manager for

Advanced Copy Services is currently

running.

Explanation: This failure happens during

(de)installation and indicates that not all TSM for ACS

components could be stopped.

User response: Check that no backup or restore is

currently running and retry the operation. If you have

customized the process of starting TSM for ACS, it

might be necessary to manually stop it by undoing

those customization steps.

BKI1546E IBM Tivoli Storage Manager for

Advanced Copy Services was not

started.

Explanation: This failure happens during installation

and indicates that not all TSM for ACS components

could be started successfully.

User response: Check that all TSM for ACS

components have the appropriate access rights and

retry the operation. Contact the support function if the

operation continues to fail.

BKI1547E Failed to remove the data associated

with the deleted backup backup_id.

Explanation: The backup named was deleted.

However, its data could not be removed from the

repository and from the storage device.

User response: Look for a previous message pointing

to the cause of the problem. Resolve any problems

indicated there. Once the cause of this problem is

resolved, the daemon will take care of the deleted

backups eventually.

Messages


BKI1548E Failed to monitor the data associated

with the deleted backup backup_id.

Explanation: A background daemon is supposed to

monitor the states of backups in order to determine if

data needs to be deleted from the storage device.

However, the monitor was not able to access the

appropriate data.

User response: Look for a previous message pointing

to the cause of the problem. Resolve any problems

indicated there. Once the cause of this problem is

resolved the daemon will take care of the deleted

backups eventually.

BKI1549E Failed to load component_name due to the

following reason: error_information.

Explanation: The system was unable to load the

named component of the product.

User response: Check the error information given in

the message. Resolve any problem indicated.

BKI1550E Unable to perform required operations

for container container_id for time_span.

Explanation: For the data container noted, an

operation to be performed by a background daemon

has been pending for the given time. This might

indicate a problem and may result in storage not being

released for an extended period.

User response: Make sure the background daemons

are running. Check their log files for messages pointing

to problems. Resolve any problems indicated.

BKI1553I Component_name is logging to path.

Explanation: The file denoted is the log file of the

named component.

User response: If you need to check the log of the

indicated component, look for this message to identify

the log file to examine.

BKI1554W The agent ’component_name’ terminated

with exit code number.

Explanation: The process denoted ended with the

given exit code.

User response: Check the agent’s log for any

messages pointing to a problem. Resolve any problem

indicated.

BKI1555I Profile successfully created. Performing

additional checks. Make sure to restart

all ACS components to reload the

profile.

Explanation: The setup wizard created a new profile.

The profile will be validated.

User response: Restart the ACS components after the

wizard ends, in order to activate the new settings.

BKI1556E Some data of backup backup_id are

unavailable. It is impossible to restore

the data requested.

Explanation: The system detected that some of the

data originally contained in the backup is no longer

available. The occurrence of this message depends on

the type of storage device employed. For example, if an

earlier backup data was restored from an N-Series

device, some data of a later backup will be destroyed.

User response: The backup is no longer complete and

cannot be used for the requested operation. Try the

operation with a different backup.

BKI1557I Device agent is logging to path.

Explanation: The device agent’s log messages are

written to the file named.


BKI2000I Successfully connected to

component_name on port portnumber.

Explanation: One of the DP for SAP modules

BACKINT or the backup library libtdp_r3 initiated a

successful connection to the background process

component_name on port portnumber.


BKI2001E Socket error while connecting to

component_name: reason.

Explanation: The background process component_name

is not running.

User response: Start component_name manually and try

again.

BKI2003I File file_name, BID deleted.

Explanation: The file file_name with the backup ID

BID was deleted from the Tivoli Storage Manager.


BKI2007E Unknown Port: port

Explanation: The port specified for communication

between component_name and BACKINT or the backup

library is unknown.

User response: Check the port value specified when

component_name was started. Additionally, check the

environment variable PROLE_PORT for the BACKINT

environment. These two values must match.

Messages


BKI2008E Unable to connect to component_name.

Explanation: Internal error.


BKI2009I Deleting all versions with version

number <= version_number on server

server_name.

Explanation: All full database backups and their

corresponding log file backups will be deleted from

Tivoli Storage Manager storage, if their version number

is less than or equal to version_number.


BKI2010E Error occurred processing FRONTEND

Explanation: An error occurred during the frontend

processing.

User response: Check the frontend script/program

and the settings in the DP for SAP profile (keyword

FRONTEND) and try again.

BKI2011E Error occurred processing BACKEND.

Explanation: An error occurred during the backend

processing.

User response: Check the backend script/program

and the settings in the DP for SAP profile (keyword

BACKEND) and try again.

BKI2012E Passwords do not match. Try again.

Explanation: The first and second password you

entered do not match.

User response: Enter the password correctly.

BKI2013I Starting FRONTEND Program.

Explanation: The frontend program is executing.


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 is num_bytes

bytes.


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.

User response: Check the ’description’. If the error

persists, contact your service representative.

BKI2024E Error in connection to component_name.

Explanation: The connection to component_name

terminated unexpectedly. This message might be

displayed due to previous errors or after an unexpected

termination of the component_name process.

User response: Check for other error messages and

restart component_name if necessary. Try again. If the

problem persists, contact DP for SAP support.

BKI2025E Failed to respond to a message received

from component_name.

Explanation: This is an internal error


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 cleanup

that has no effect on the success of the service.

User response: None

Messages


BKI2029E The requested buffer allocator cannot be

instantiated due to the following

incompatibility: expression.



BKI2031E A buffer allocator cannot

simultaneously satisfy all of the

following properties: list of properties



BKI2033E Cannot instantiate allocator of type

allocator type with the following

additional properties: list of properties



BKI4000W The attributes of file file name cannot be

restored. Reason: errno (error_num)

error_desc.

Explanation: The file file name was restored

successfully but one or more file attributes (permission,

ownership, date/time) of the file file name cannot be

restored correctly.

User response: Check the error number error_num and

the error description error_desc to avoid this problem in

the future. An initial solution could be to set the

appropriate correct permission for the file file name

manually.

BKI4001E File file name cannot be created. Reason:

errno (error_num) error_desc.

Explanation: The file file name to be restored could not

be created/written. It is possible, that you do not have

the appropriate rights for writing the file file name to

the destination path.



the future. Furthermore, check the write permission of

the user who started the restore.

BKI4002E Error during write of file file name.

Reason: errno (error_num) error_desc.

Explanation: An error occurs during the restore

process of the file file name.



the future.

BKI4005E Error allocating memory block for file

file name. BLOCKSIZE may be too large.

Explanation: Unable to request new memory blocks

during the backup of file file name.

User response: Verify that you have set a valid value

for BLOCKSIZE. If you are not sure what value is

valid, comment it out so the default value is used.

Furthermore, you can check if you have enough RAM

available with your machine. Also, check the memory

usage during backup. It may be necessary to stop

another application, increase memory, or change the

configuration.

BKI4007E File filename cannot be read. Reason:

errno(errno number) errno text.

Explanation: Data could not be read due to some

system error. Check errno text for further information. If

this error recurs, this might indicate some hardware

problems.

User response: Contact your system administrator.

BKI4008E File filename cannot be opened. Reason:

errno(errno number) errno text.

Explanation: Could not open the file file name due to

some system specific problems.


BKI4009E Not enough space to write file file name.

Possible reasons: disk full or ulimit

exceeded.

Explanation: The system rejected a request to write

data into file file name. The storage media might not

have enough free space to keep the file or the system

rejected writing the file due to administrative resource

constraints such as ulimits.


BKI5000E Tivoli Storage Manager Error:

error_message

Explanation: During a connection of DP for SAP to

Tivoli Storage Manager server, a Tivoli Storage

Manager error error_message occurred.

User response: Use the Tivoli Storage Manager

Messages guide and correct the Tivoli Storage Manager

server error. Try your last action again.


error_message

Explanation: During a connection of DP for SAP to

Tivoli Storage Manager server, a Tivoli Storage

Manager error error_message occurred.

Messages


User response: Use the Tivoli Storage Manager

Messages guide and correct the Tivoli Storage Manager

server error. Try your last action again.


error_message

Explanation: See BKI5001E.

User response: See BKI5001E.


error_message



BKI5004W Tivoli Storage Manager Error:

error_message




error_message




error_message




error_message




error_message




error_message




error_message




error_message



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 environment

variable DSMI_DIR.

BKI5013E Value for name is too long. Current

value: value

Explanation: The value of the environment variable

name has too many digits.

User response: Check if the variable is set correctly.


error_message



BKI5015W Data description could not be restored,

because it was backed up with a newer

version (objInf=support information)

Explanation: The TSM server hosts backups (i.e. data

description) which were made with a new version of

backint or backom, which ignores this data in further

processing.

User response: Upgrade the product.

BKI5016I Time: current_time New TSM session

created: MGMNT-CLASS:

management_class, TSM-Server:

server_name, type: session_type.

Explanation: A new session to TSM server server_name

has been established at current_time. Data will be stored

in management class management_class.


Messages


BKI5017E Internal Tivoli Storage Manager Error:

Transaction succeeded although it was

expected to fail.

Explanation: An internal Tivoli Storage Manager error

occurred.

User response: Retry the action. If the error occurs

again contact DP for SAP support.

BKI5018E The requested buffer has a size

(current_size bytes) that is smaller than

requested requested_size.

Explanation: The request for a new buffer returned

successful. The buffer, however, has not the requested

size.

User response: Check if the system is running low on

memory and retry the action. If the error occurs again

contact DP for SAP support.

BKI7048I The default port to connect to

server_name will be used.

Explanation: A server port for the connection to the

named server was not explicitly specified. Therefore,

the default port is used.

User response: Make sure the named server is

listening to the default port. In the case of connection

failures, specify the server port in the profile.

BKI7049I The default ProLE port will be used.

Explanation: The port for the internal communication

of DP for SAP is set during installation. The message

indicates that this port is being used.


BKI7051E The environment variable

XINT_PROFILE is not set. It must be set

and contain the fully qualified path to

the *.utl file to be used.

Explanation: The way DP for SAP works is specified

in a profile. When called, DP for SAP looks for the

environment variable XINT_PROFILE which must

contain the fully qualified path to the profile.

User response: Check the environment for

XINT_PROFILE of the user who started DP for SAP.

BKI7053E Service setup failed due to previous

error.

Explanation: Initialization of the product failed due to

previous errors.

User response: Check the product log file for further

detailed messages.

BKI7055E Service open failed due to previous

error in data mover.

Explanation: The command could not be started due

to previous errors.


detailed messages.

BKI7056E Service open failed because configured

TSM server could not be accessed.

Explanation: The command could not be started

because the TSM server defined in the profile could not

be accessed.


detailed messages.

BKI7057E Service open failed because all

configured sessions are currently in use.


because all configured sessions in the profile are

currently in use.

User response: With Oracle RMAN the number of

channels configured either in SAP profile or the RMAN

script must be less or equal to the maximum number of

allowed sessions (MAX_SESSIONS). If multiple servers

are used see: “Multiple Servers” on page 44 for further

details. Also check the DP for SAP log file for further

detailed messages.

BKI7058E Service open failed because more than

one file was found with the same name.


because two or more files with the same name were

found.


detailed messages.

BKI7059E Service open failed because a file was

not found.


because a file specified was not found.


detailed messages.

BKI7060I product

<version>.<release>.<modification>

(<build number>) <build date> session:

process ID

Explanation: This message is to verify the version of

the shared library used for backup. On UNIX and

Linux systems this message will be written multiple

times into the log per backup depending on the RMAN

setup. On Windows, it is written just once.

Messages


User response: None, if the right version is used. If

the version within the log does not match the installed

version, see "RMAN Problem Resolution" in the Data

Protection for SAP Installation and User's Guide.

BKI7303W Profiles for Data Protection for Snapshot

Devices are different.

backup: file name

restore: file name

Explanation: During backup the profile used by DP

for Snapshot Devices can be determined automatically.

For restore and inquire operations the profile for DP for

Snapshot Devices must be specified in the profile using

the parameter FCS_FILE. For restore DP for Snapshot

Devices must use the same profile as for backup.

User response: Correct the entry for the FCS_FILE

parameter in the profile (init<SID>.utl).

BKI7304I Performing DISK ONLY backup

Explanation: The data for this backup is stored on

snapshot-type disks only and will not be sent to TSM.

User response: None

BKI7305E Error during call to Data Protection for

Snapshot Devices error message

Explanation: DP for Snapshot Devices could not

process the requested operation successfully. Processing

may not stop at this point. Depending on the type of

request (backup to both TSM and snapshot disks or to

snapshot disks only, restore of data which is available

in both modes) there are possibilities to recover from

this error and continue operation.

User response: Use the information from error message

and the output of DP for Snapshot Devices to

determine the cause of the problem and try again.

BKI7307W Data Protection for Snapshot Devices

reported an error during a snapshot-type

operation. Do you want to continue to

backup to TSM?

Explanation: The backup was requested to be stored

on both the TSM server and the snapshot-type disks.

The snapshot operation has failed. Backup can continue

to save data on the TSM server only.

User response: Enter ’stop’ if you want to solve the

cause of this error and to try again. Enter ’cont’ if you

want to save this data on the TSM server only.

BKI7308E DISK ONLY backup has failed.

Explanation: The current backup tried to store data on

snapshot-type disks only and did not finish

successfully.

User response: Check the output from DP for

Snapshot Devices prior to this error message to detect

the root cause of this error and try again.



operation. Do you want to continue to

restore from TSM?

Explanation: The data you wanted to be restored is

located on the TSM server and on snapshot-type disks.

The snapshot operation has failed. The process can

continue to restore data from the TSM server.

User response: Enter ’stop’ if you want to resolve the

cause of this error and to try again. Enter ’cont’ if you

want to restore from the TSM server.



operation. CAUTION: Not all

filesystems are available. Do you want

to retry the operation?

Explanation: In contrast to message BKI7309W not all

file systems are mounted. In this case it is not possible

to continue the restore from the TSM server.

User response: Enter ’stop’ if you want to terminate

this restore process. Enter ’cont’ if you want to retry the

snapshot process.

BKI7311I Profile used by DP for Snapshot

Devices:

Explanation: The message shows the name of the

profile used by DP for Snapshot Devices.

User response: None

BKI7312W Profile for DP for Snapshot Devices not

specified in profile. For restore this

must be specified

Explanation: For restore and inquire operation in

conjunction with DP for Snapshot Devices this

parameter is mandatory. Without this parameter a

restore using DP for Snapshot Devices is not possible

and DP for SAP will continue to inquire/restore from

the TSM server only.

User response: Add the parameter FCS_FILE to the

DP for SAP profile

BKI7313W Inquire results from DP for Snapshot

Devices are not available

Explanation: DP for SAP was unable to retrieve

information from DP for Snapshot Devices about

available backups on snapshot-type disks. This message

may be issued in consequence of message BKI7305E.


Messages


Snapshot Devices to determine the cause of the error

and try again.

BKI7314E The data you want to restore is not

available on the TSM server.

Explanation: If a restore from snapshot-type disks can

not be finished successfully DP for SAP tries to

continue to restore data from the Tivoli Storage

Manager server. But if the backup was performed on

snapshot disks only, the data can not be found on the

TSM server.


Snapshot Devices prior to this error message to detect

the root cause of this error and try again.

BKI7315W The copy process of the files you want

to restore is not yet finished. If you

continue the files will be restored from

TSM.

Explanation: The snapshot process running in the

background has not finished moving the files from the

source to the target volumes. A snapshot restore of

these volumes is currently not possible.

User response: After that message you will be asked if

you want to continue or stop this operation. If you

want to wait until the snapshot process has finished

choose ’stop’ and the restore attempt will terminate. If

you choose ’continue’ an attempt is made to restore the

data from TSM if available.

BKI7316I The following backup types for the

BACKUPID Backup ID have been found:

- TSM

- Snapshot

Explanation: The backup for the backup ID Backup ID

was stored on the Tivoli Storage Manager as well as on

snapshot-type disks. For restore both data sources can

be used.


BKI7318E The DP for Snapshot Devices profile file

name is not valid.

Explanation: The profile for DP for Snapshot Devices

specified in init<SID>.utl could not be accessed.

User response: Check the file name and the

permissions for this file and try again.

BKI7319I Start TSM restore

Explanation: The restore uses data from Tivoli Storage

Manager.

User response: None

BKI7320I Start restore from snapshot.

Explanation: The restore is using data from

snapshot-type disks.

User response: None

BKI7321E The DP for Snapshot Devices profile file

name found in parameter FCS_FILE of

the DP SAP profile can not be used if

you need to restore this backup.

Explanation: In the DP for SAP profile the FCS_FILE

parameter is set, however the DP for Snapshot Devices

profile specified either

v is not a DP for Snapshot Devices profile

v does not point to the same DP for Snapshot Devices

configuration file which was used by the preceding

DP for Snapshot Devices splitint operation.

User response: You need

v to correct the FCS_FILE parameter thus a valid DP

for Snapshot Devices profile is used, e.g. the file DP

for Snapshot Devices had used when running its

snapshot function in the preceding brbackup task

(see preceding message BKI7303W)

v to ensure that if different DP for Snapshot Devices

SAP profiles are used, all use the same control file

(the value of the IDS_CONTROL_FILE parameter in

the DP for Snapshot Devices profile)

BKI7322E Request for a partial restore or restore

from snapshot with ’brrestore -m all’ is

not supported. In case of brrestore

attempt rerun with -m full.

Explanation: DP for Snapshot Devices can only restore

the whole content of a backup and not only a subset of

a disk backup as requested. Most likely this is caused

by running brrestore with the option ’-m all’.

User response: Restore complete backups only, e.g.

run brrestore with the option ’-m full’.

BKI7323W Request for a partial restore or restore

from snapshot with ’brrestore -m all’ is

not supported. If you want to restore the

backup:

- with a snapshot-type restore enter

’stop’ and rerun brrestore with ’-m full’

- from TSM enter ’cont’

Explanation: This message has the same reason as

message BKI7322E, but in this case the data is also

available from the TSM server. So you may continue to

restore this data without the snapshot functionality

from TSM server.

User response: Enter ’stop’ if you want to try to

restore a different set of files. Enter ’cont’ if you want

to restore this data from TSM server.

Messages


BKI7324E Restore of multiple backup IDs in one

run from a snapshot is not possible.

Explanation: The data requested for this restore

belongs to multiple backup IDs

User response: Make sure the files you want to restore

belong to one single backup ID and try again.

BKI7535W Error executing command command name.

Reason: errno (error number) explanation.

Explanation: The command command name could not

be executed successfully.

User response: Check the explanation explanation and

the preceding output of the command execution to

detect the cause of the error.

BKI7536I Execute command command name.

Explanation: The command command name is executed

by the application. This message is followed by the

output of the command executed.

User response: None

BKI8201E SIMULATION CANCELED BY

PRODUCTION OPERATION!!!

Explanation: The current operation was a simulation

performed via the Administration Assistant. This

simulation was canceled since a production operation

(backup or restore) has been started.

User response: Check your backup schedule and run

simulations only when no other operations are

scheduled.

BKI8300I Function_name returned with code

return_information.

Explanation: This message indicates that the named

API function ended with the specified return

information.

User response: If the return information indicates a

problem, look for preceding error messages in the log

files. Otherwise, no response is required.

BKI8306E The keyword keyword is not allowed

multiple times within the profile.

Explanation: The keyword indicated was found more

than once in the profile. However, this keyword must

not be specified multiple times.

User response: Correct the profile.

BKI8307E The parameter keyword must be specified

in the profile.

Explanation: A required keyword is missing in the

profile.


BKI8308E Single argument required for parameter

keyword.

Explanation: The keyword indicated requires a single

value. However, two or more values are found in the

profile.


BKI8309E Missing argument for parameter

keyword.

Explanation: In the profile, a value is missing for the

named parameter.


BKI8310E The keyword keyword is not allowed.

Explanation: An invalid keyword was detected in the

profile.


BKI8311E For parameter keyword, both server and

port must be specified.

Explanation: A value of the named parameter is

missing from the profile.

User response: As the value for the specified

parameter, specify both server and port.

BKI8312E Error while parsing parameter keyword.

In order for ’value1’ to be valid ’value2’ is

required to be an existing directory.

Explanation: Value1 was found to be an invalid value

for the parameter named. For this specific parameter, a

file name can be specified whose path must already

exist in the system.

User response: Specify the name of a file in an

existing path.

BKI8317W Product_name: Verification of

configuration requested by user. No

backup started.

Explanation: The user requested a verification of the

configuration. The backup flow continued without

errors up to the point where the snapshot would

actually be done and was then cancelled. The system is

ready for a snapshot backup, but no action beyond

verification has been taken so far.

Messages



BKI8319W Error while deleting old versions. This

problem does not affect the new

backup. Error information:

’error_information’

Explanation: After a successful backup, the system

tries to remove older backups of the database according

to the value of profile parameter MAX_VERSIONS.

However, a problem occurred while trying to remove

expired backups. The new backup is not affected by

this problem.

User response: Check the appropriate log files in

order to determine the cause of the problem. Resolve

any problems indicated. In case the storage device runs

out of storage because outdated snapshot backups have

not been removed, delete these snapshot backups

manually.

BKI8320I Deleting full backup backup_id –

backup_key.




During this process, the full backup listed is removed.


BKI8321I Deleting partial backup backup_id for

node:host:partition_number.




During this process, the backup listed for the named

partition is removed.


BKI8322E Interface problem: Current database

partition number not listed in the

partition list.

Explanation: The partition list passed by the database

does not contain the named partition participating in

an operation.


BKI8325E Failed to determine hostname.

Explanation: The system was not able to determine

the host name of the machine.

User response: Make sure the system setup allows for

querying the hostname via system function

gethostname(). Ensure that the requirements for doing

snapshot backups are met.

BKI8326E Failed to create log directory path.

Explanation: The log path indicated is not available in

the system and could also not be created.

User response: Check the properties of the path

indicated and make sure that its properties and the

properties of the parent directory are set accordingly.

Make sure all prerequisites for doing snapshot backups

are met.

BKI8327E Invalid value specified for parameter

keyword: value

Explanation: A parameter value is not valid.

User response: Correct the profile or the call as

appropriate.

BKI8328E Product_name must be licensed to set

parameter keyword to a value of value.

Explanation: Selected functions are supported only

with a full TSM license.


appropriate. If you need the functionality requested,

obtain a full TSM license and install the license file.

BKI8330E Parameter keyword requires ’YES’, ’NO’,

or number.

Explanation: For the named parameter, only numeric

values, “YES”, and “NO” are accepted.


appropriate.

BKI8331E The parameter keyword1 is not allowed if

keyword2 is set to value.

Explanation: There is a dependency between

parameters keyword1 and keyword2. If the latter is set to

the value named, keyword1 must not be specified.


appropriate.

BKI8332E Failed to parse parameter keyword. File

names in the profile need to be fully

qualified.

Explanation: As the value of the parameter indicated,

a fully qualified file name is expected. However, the

specified value is not a fully qualified path.


appropriate.

Messages


BKI8333E In order to enable the parameter

keyword1 you need to set keyword2 to

value.

Explanation: There is a dependency between

parameters keyword1 and keyword2. If keyword1 is

specified, keyword2 must be given the specific value

indicated in the message.


appropriate.

BKI8334E Profile section section_name is required

for function operation.

Explanation: The specified profile section is required

in order to perform the requested operation. However,

it is not included in the profile.


BKI8335E Profile section section_name refers to a

value for keyword that differs from the

one used at backup time. Expected

value: value.

Explanation: The profile parameter named must not

change its value between backup and restore. However,

in the named profile section, the parameter has a value

different from the value it had at backup time. This

value is given in the message.

User response: Correct the profile by setting the

indicated parameter to the value indicated in the

message.

BKI8336E Invalid value specified for option

keyword:value

Explanation: An option value is not valid.

User response: Correct the call.

BKI8337E Error while parsing profile: Missing

section name.

Explanation: The profile is organized into named

sections. However, a section name was not found.

User response: Check that the profile name is

specified correctly or that the default profile is a valid

profile. Refer to your user documentation for the syntax

of the profile or use the profile wizard to create a new

profile.

BKI8338E Error while parsing profile: Section

section_name is not allowed to be nested.

Explanation: In the profile, the named section starts

before the previous section ends. However, the section

in question cannot be nested.


BKI8339E Error while parsing profile: Profile

section section_name is not valid.

Explanation: An invalid section name was found in

the profile.



section section_name must not be

specified more than once.

Explanation: In the profile, only a single section with

the name indicated can be specified. However, during

parsing, a second occurrence was detected.



section section_name missing.

Explanation: The required profile section indicated

was not found in the profile.


BKI8343W The parameter keyword1 of keyword2

value2 has changed its value from value1

to value3.

Explanation: The profile parameter named must not

change its value between backup and restore. However,

in the named profile section, the parameter has a new

value value3 different from the value value1 it had at

backup time. Both values are given in the message.

User response: Check the log file for problems that

may result from the change of parameter values. If so,

you may want to change the profile, restoring

parameter keyword1 to the value it had when creating

the backup in order to perform a specific operation.

BKI8345E Error while parsing parameter keyword.

’path’ is required to be type_information.

Explanation: A path of the type indicated in the

message is expected as a value of the named parameter.

However, the specified path was not found to be of the

correct type.


appropriate.

BKI8349I Deleting incomplete backup backup_id–

backup_key .




During this process, the incomplete backup listed is

removed. A backup becomes incomplete when parts of

its data expire. This can happen when a backup that is

marked “destructively restorable” is restored.

Messages



BKI9001E Internal error: error

Explanation: The following internal error: error has

been encountered.


BKI9003E Incompatible components installed:

component name component name

Explanation: The components mentioned in the

message text can not be used together. This may be the

result of an incomplete upgrade.


BKI9005E A not supported by B.

Explanation: The installed version of product B does

not support product A. Most likely you need to

upgrade product B.

User response: Contact the DP for SAP support.

BKI9006E Internal error while reading

environment variable: variable.



BKI9007W An error occurred while terminating the

application: the error

Explanation: While terminating the application, an

error occurred. This has no impact on the success of the

operation.

User response: None

BKI9008E This product requires at least version

number of product name to be installed.

Explanation: The version of the application product

name is not supported by this application. Most likely

application product name needs to be upgraded.


BKI9009W The following products are not

compatible: product name (product version)

and product name (product version).

Explanation: This message is similar to BKI9008E. But

in this case it’s not obvious which one of the products

needs to be upgraded. .

User response: Contact DP for SAP support

BKI9200E Additional support information: An

exception was thrown at position:

position.

Explanation: This error message typically follows a

previous error. If so this error message can be ignored.

Otherwise contact DP for SAP support



Exception was thrown at position:

position.







position.



Otherwise contact DP for SAP support.




position.







position (text=description).





BKI9205E Additional support information: Unable

to instantiate name at position position.





Messages


BKI9206E Additional support information: Unable

to use actual when expecting expected at

position position.







position.





BKI9208E System error errno: errno text at position

position.

Explanation: A system call failed with errno.

User response: Check errno and errno text with you

system administrator. If you cannot resolve the

problem, contact DP for SAP support.

BKI9209E Additional support information: No

handler registered for message type

message. Thrown at position: position.





BKI9210E ESD_AbortDispatchingException thrown

at position: position.

Explanation: An internal error occurred.




position. (State state)





BKI9212E Additional support information: No

handler registered for message type type.

Thrown at position: position.





BKI9213E Internal error: A memory allocation

request failed at position: position.

Explanation: This error message indicates an

out-of-storage condition. It may occur due to a

previous error, or it may be owed to a large size of the

internal buffers

User response: Check for and respond to preceding

error messages. You may also want to reduce the size

of the internal buffers (keyword BUFFSIZE in the Data

Protection for SAP profile).


exception was thrown from a destructor.

Callstack follows: callstack.







position.







position.







position.





BKI9219E Additional support information: Invalid

error type typeencountered.





Messages


BKI9220E Additional support information: Second

call of call.



Otherwise contact your DP for SAP support.

User response: Contact your DP for SAP support.

BKI9300E Additional support information:

Aborting ’send’ operation. See previous

error.

Explanation: This error may have been caused by

previous errors.

User response: Check for previous errors and correct

them.

BKI9301E Additional support information: State

state does not match state pattern pattern.





BKI9302E Additional support information: Unused

ESD_ReturnChannel destroyed.

Dumping callstack: callstack



Otherwise contact your DP for SAP support.


BKI9306I Dumping callstack: call stack.

Explanation: This message is always preceded by an

error message indicating the problem. It provides

additional information that might help DP for SAP

support to analyze the cause of the problem.

User response: If you need to call DP for SAP

support, provide the information given in this message

together with the error information.

BKI9307E Did not find a winsock dll compatible

with version expected version. Version

found is available version

Explanation: The product failed to load the

appropriate winsock dll.

User response: Contact your system administrator

BKI9308E A socket request timed out after

processing number of bytes bytes position.

Explanation: A socket request was issued with a

timeout and the requested action could not be

completed within the time specified. It was cancelled

after processing number of bytes bytes.

User response: If you need to call DP for SAP

support, provide the information given in this message

together with the error information.

BKI9309E Operation terminated due to an explicit

abort request.

Explanation: An operation was terminated due to

customer intervention.


BKI9310E Could not add backup_id to the

repository at path.

Explanation: The system was not able to add

information on the named backup to the repository

located in the path indicated.

User response: Make sure the repository path is set

correctly. If you need to correct the repository location,

restart the server executable afterwards. If the problem

persists contact your IBM support personnel.

BKI9311E Could not find backup_id in the

repository at path.

Explanation: Information on the backup denoted by

the backup ID could not be found in the repository

located in the path indicated.

User response: Make sure the repository path is set

correctly. If you need to correct the repository location,

restart the server executable afterwards. If the problem


BKI9312E backup_id is currently locked in the

repository at path.

Explanation: The information on the backup denoted

by the backup ID is currently locked by a different

process. Make sure to run only a single operation using

a specific backup at a time.

User response: Wait for the other operation to finish

or abort this operation. Then start again. If the problem


BKI9313E Failed to update backup_id in the

repository at path.

Explanation: The information on the named backup

could not be updated in the repository located at the

path named.

Messages


User response: Check the logs for other messages

pointing to the cause of this problem. Resolve any

problems indicated. If the problem persists contact your

IBM support personnel.

BKI9314E Could not remove backup_id from the

repository at path.

Explanation: An attempt to remove the information

on the backup named from the repository located at the

path indicated failed.

User response: Check the logs for other messages

pointing to the cause of this problem. Resolve any

problems indicated. If the problem persists contact your

IBM support personnel.

BKI9315E Could not access the repository at ’path’

because it is currently locked by another

process.

Explanation: When starting up, the server tried to

load the repository located at the path named.

However, the repository was locked by a different

process. This can happen if two server processes try to

use the same repository. This is not supported.

User response: Make sure each instance of the server

uses its own repository.

BKI9316E The path ’path’ does not point to a valid

repository location.

Explanation: When starting up, the server could not

locate its repository.


appropriate.

Messages


Appendix C. Troubleshooting

This appendix gives you information on how to resolve errors that might occur

during or shortly after installation and during backup or restore. In general,

problems, related to this product can be divided into the following categories:

1. Setup problems

2. Defects of this product or a product it is interacting with

3. Performance problems

This chapter will help you with setup problems and defects. If you encounter a

performance problem please proceed with “General Performance Considerations”

on page 39.

If an error occurs, always first check the description of the respective error

message, issued by the system. Besides being displayed on the screen, the error

messages also can be found in log files. For these log files and for a description of

the error messages, see Appendix B, “Data Protection for SAP (Oracle) Messages,”

on page 125. Solve the problem indicated in the error message and retry the action.

Problem Resolution During Installation and Setup

Understanding the Setup

For a description of the installation procedure, see “Installing Data Protection for

SAP” on page 26. When you have completed the installation, make sure all files

are installed as described in that section. Also check for an entry similar to the

entry for a 32bit Data Protection for SAP on Oracle shown below in the

file /etc/inittab on UNIX or Linux systems:

po32:2:respawn:/usr/tivoli/tsm/tdp_r3/ora/prole -p tdpr3ora <Server component hostname> 5126

If running a 64-bit Data Protection for SAP, the port name would be tdpr3ora64

instead of tdpr3ora

The purpose of this entry is to start a daemon process for ProLE, which listens on

port tdpr3ora for backint and RMAN connections and is able to forward

performance information to an Administration Assistant Server component. The

port tdpr3ora can also have a different name but must match the entry in

/etc/services (see below).

The last two arguments specify the location of the Administration Assistant Server

component and are only needed if you want to use the Administration Assistant.

<Server component hostname> specifies the name or IP address of the host on

which the Administration Assistant Server component is running. 5126 is the

default port the Server component is listening to.

On Windows systems verify that service ProLE Service is running and set to

automatic startup. If this service is not running, Data Protection for SAP will not

function properly.


The installer adds lines like the following to the file /etc/services on UNIX or

Linux or to %SYSTEMROOT%\system32\drivers\etc\services on Windows:

tdpr3ora 57321/tcp

tdpr3ora64 57323/tcp

where tdpr3ora is the entry for 32-bit and tdpr3ora64 for 64-bit Data Protection for

SAP versions..

This port should be the same as in /etc/inittab. Also you need it for the

configuration of RMAN in the file init<SID>.sap.

Other than modifying the mentioned files the installer created, the DP for SAP

configuration file init<SID>.utl within the directory $ORACLE_HOME/dbs on UNIX

and Linux or %ORACLE_HOME%\database on Windows systems.

If you want to use the SAP BR*Tools (formerly known as SAP DBA), you need to

modify the file init<SID>.sap. Set backup_dev_type = util_file and variable

util_par_file to the fully qualified path and file name of init<SID>.utl. See

Figure 35 for an overview of the configuration files on a UNIX or Linux system.

The names of the TSM servers specified in init<SID>.utl must match the names

in file dsm.sys.

On Windows systems, file udsm.opt is used in place of dsm.sys, but the content is

not relevant for Data Protection for SAP. The directory that contains file dsm.opt

must also contain files with the name <server>.opt for each server specified in

init<SID>.utl. There must be an environment variable DSMI_CONFIG set to an

Figure 35. SAP and Data Protection for SAP configuration files on UNIX or Linux

Troubleshooting


option file within this directory. The recommended practice is to set

DSMI_CONFIG to dsm.opt. Also on Windows, the environment variable

DSMI_DIR must be set pointing to the directory where the file dscamen.txt resides.

Usually this is the directory c:\Program Files\Tivoli\tsm\api.

On UNIX or Linux systems the DSMI_* variables do not need to be set if you used

the default paths for installation of TSM API or TSM Backup Archive Client. If the

variables are set, however, make sure they point to the right files and directories.

Also check if the user ID that runs the backups has the correct permissions to

access all of the above mentioned files. Otherwise, modify the file read

permissions. The only file to which Data Protection for SAP writes persistent

information is init<SID>.bki. Also check the write permissions for this file.

Location of Log Files

Everything you see on the screen during operation of brbackup, brrestore or SAP

Tools in general will also be written into a log file. To locate these log files, see

“How To Find Files Containing Message Output (Log Files)” on page 125.

Oracle also writes logs of internal operations in the alert log and core files in the

directory specified in the Oracle control files. Usually this is $SAPDATA_HOME/saptrace/background/alert_<SID>.log.

BACKINT Problem Resolution

Now that you verified all the settings done by the installer follow the flow shown

in Figure 36 on page 154 to isolate the problem. No matter if you use the Backint

interface or the RMAN interface of Data Protection for SAP, make first sure that

the BACKINT interface is working correctly.

Troubleshooting

Appendix C. Troubleshooting 153

After installation (1.1 in Figure 36) set the password (1.2) as described in section

“Set the Password” on page 32. If you use a generated password don’t perform

this step. If no problems occur you see a message ’BKI0051I: Password successfully

verified for node <NODENAME> on server <SERVERNAME>’ for each server you

configured within your init<SID>.utl and a message ’BKI0024I: Return code is: 0.’

at the very end of the output. If a problem occurred you should see an error

message.

If you have an Administration Assistant running you may also use the

Configurator of the Administration Assistant. There you can load the configuration

of the node on which you are encountering the problems and let the

Administration Assistant check the configuration.

Frequent errors at this point (1.2) are:

v Error message: BKI2001E: Socket error while connecting to ProLE at

<IP-Address>:<PORT>: Connection refused.Check that the ProLE Service is running on Windows or check if the background

daemon is running on UNIX or Linux. To check for the daemon issue the

command:

ps -ef | grep prole

Figure 36. Problem Isolation for Backint

Troubleshooting


On Windows systems you can either have a look in the Services screen of the

Computer Management or issue the command:

net start

to get a list of all running services.

Check the entry in /etc/services on Windows %SYSTEMROOT%\system32\drivers\etc\services.Compare the port number from the error message with the port number within

/etc/services. Also have a look in /etc/inittab. If another port was set using

the option -p<PORT>, check this one as well.

If all of this will not help, start the ProLE from another shell

prole -p <PORT>

or on Windows:

prole -console -p <PORT>

and try starting backint again.

v Error message: BKI5001E: Tivoli Storage Manager Error: Server not found in

configuration file.

The TSM Server from the init<SID>.utl does not match with the one specified

in the used dsm.sys (on UNIX or Linux ). On Windows, the <server>.opt might

be missing.

v Error Message: BKI5001E: Tivoli Storage Manager Error: ANS1353E (RC53)

Session rejected: Unknown or incorrect ID entered

This message can happen if the node in the server stanza of the UTL file is not

valid on the server. Also have a look into the API reference (e.g. search the

message at tivoli.com)

v HANG: If backint hangs after input of the password, the server's IP address in

dsm.sys may be wrong.

When step 1.2 of Figure 36 on page 154 (setting of password) finally succeeded,

proceed with step 1.3 and try to make a backup using backint to verify the settings

are correct. The “Backup Function” on page 159 describes how to do this.

If the backup was successful you will see one message #SAVED<BID><FILENAME> per

file you typed in to be saved and again there will be the message ’BKI0024I:

Return code is: 0.’ Otherwise you should see an error message. In this case try to

resolve it by using the error description in Appendix B, “Data Protection for SAP

(Oracle) Messages,” on page 125.

At this point, you can be confident that the Data Protection for SAP setup is

largely complete. You only need to assure that the BR*Tools and Oracle (if using

RMAN) are correctly configured. Go on with step 1.3 and start brbackup as

described in section “Verifying the Installation” on page 33.

RMAN Problem Resolution

The following graphic Figure 37 on page 156 will help you to isolate problems that

occur when using RMAN.

Troubleshooting


After you set up Data Protection for SAP and Oracle to work together (step 1.1 of

Figure 37) as described in Chapter 4, “Installing or Upgrading Data Protection for

SAP,” on page 25, you can try to startup Oracle using the server manager (svrmgrl

on UNIX or Linux , and svrmgr30 on Windows) with Oracle 8.x or using SQL Plus

(sqlplus) on Oracle 9.x.

With RMAN, the first place to look if an error occurs is the file sbtio.log, located

in the directory specified in the user_dump_dest keyword within the Oracle

profile init<SID>.ora. This file is usually located at $ORACLE_HOME/saptrace/usertrace/sbtio.log. Always review the latest messages in this file first, since the

messages issued in the RMAN log are often not very helpful.

If this log file is not written (2.2) this is a clear sign that Oracle either was unable

to load the shared library containing the RMAN connector of DP for SAP or

encountered an error before calling the DP for SAP library. In both cases there

should be an Oracle error message beginning with ’ORA-’, ’PLS-’ or ’RMAN-’ in

the log of brbackup. Try to resolve this problem using the documentation from

Oracle and SAP.

If the file sbtio.log exists, search for a message beginning with ’BKIXXXXY’ where

’XXXX’ is a four digit number and ’Y’ one of the letters ’I’, ’W’ or ’E’. If you find

such a message you can be sure the RMAN connector of DP for SAP is loaded and

has been called by Oracle RMAN. The first message for every new session should

be (2.3):

Figure 37. Problem Isolation for RMAN

Troubleshooting


BKI7060I: Data Protection for SAP <version and build number> session: 764

If you do not find this message, Oracle has loaded a wrong library. In this case do

following

Windows:

1. Remove or rename all occurrences of the file orasbt.dll except the one in the

DP for SAP installation directory. Then copy this one to %ORACLE_HOME%\bin.

2. Stop the OracleService<SID> and restart it.

UNIX or Linux: Often the RMAN librarylibtdp_r3.<ext> is not found by the

Oracle executable. There are a large number of notes on this subject from Oracle at

Oracle’s Web pages and also some SAP Notes.

Oracle suggests to use a variable SBT_LIBRARY to specify the library. During

development and test of DP for SAP, it turned out as a best practice not to use the

variable SBT_LIBRARY on any platform with Oracle up to 9.2.

Also there are notes at Oracle Metalink or Oracle Technet saying one no longer

needs to issue the make command described in Chapter 4, “Installing or Upgrading

Data Protection for SAP,” on page 25. This is not true for all combinations of

operating system and Oracle version. For DP for SAP, we strongly recommend to

issue the make command on any UNIX or Linux system. Whether Oracle needs this

command or not, it will not destroy anything When executed successfully, it

confirms that the library and Oracle executable are compatible.

Therefore, on UNIX or Linux systems review if you issued the make command.

Also make sure the library and/or soft link you entered during the command

make -f ins_rdbms.mk ioracle LLIBMM=<lib or link>

exists and that the soft link is valid. It may also be helpful to add the location of

the link or library to the environment variable LIBPATH on AIX or

LD_LIBRARY_PATH on other UNIX or Linux systems.

On Windows based systems, the location of orasbt.dll must be in the PATH. Also,

ensure that you have only one orasbt.dll in your system's PATH. It will be

helpful as well to review the setup procedure according to Chapter 4, “Installing or

Upgrading Data Protection for SAP,” on page 25 and the information given in that

chapter. Also, check if a core file is written or if Oracle has written a trace within

the saptrace/usertrace directory.

In (2.4) the file sbtio.log is written and you find an error message starting with

BKI see Appendix B, “Data Protection for SAP (Oracle) Messages,” on page 125.

Using the backint executable to determine any problems may make it easier

because you can see all messages on the screen. Also, you will not disturb Oracle if

something goes wrong. If backint is working as expected, return to problem

determination with RMAN.

When isolating a problem with DP for SAP and RMAN, you can follow the same

steps as in “BACKINT Problem Resolution” on page 153. There must be a

connection established to ProLE and the TSM server, and a password must be set

(using backint) as well. If some of these steps fail, you will get exactly the same

error messages with RMAN as you get with backint. Use Appendix B, “Data

Protection for SAP (Oracle) Messages,” on page 125 to review these messages.

Troubleshooting


Problem Resolution During Operation

This section is intended to support isolation of problems which seem to occur

without reason during an operation the system has performed successfully many

times before. Computers are deterministic machines. If an operation is performed

more than once using the same input in the same environment it will produce the

same result. Unfortunately today’s computing environments consist of a large

number of components containing a huge number of volatile parameters often

influencing each other. For problem determination the above abstract assessment

results in the following very practical actions depending on if the problem seems

to be stochastic or if it can be reproduced.

Reproducible (Repeatable) Problems

If a problem seems to occur repeatable without reason during an operation the

system performed successfully many times before, you should ask yourself:

1. What did you change at the setup of Data Protection for SAP ?

2. What did you change at the setup of involved components (Oracle, SAP, TSM,

operating system, network, hardware) ?

3. Did you apply any patches or updates to any components in the system ?

If you are sure you changed nothing, ask the same questions to your coworkers

and system administrators (DBAs, Network admin, TSM admin, etc.). If this is

without satisfying result, it may be an option to observe the last modified time

stamp of the configuration files (init<SID>.utl, init<SID>.sap, dsm.sys, dsm.opt,

/etc/services, /etc/inittab, ...).

The following UNIX or Linux command lists you all files in the directory /etc

which have been modified during the last 5 days:

find /etc -type f -ctime 5 -print

Also there might be changes to the system that are caused by the system. Samples

for such changes are:

v disks are running full. Action: Check with UNIX or Linux command df

v networks slow down. Action: check for reasons like additional hosts, additional

applications, defects in software or hardware. Compare runs in the Performance

Monitor history view in the Administration Assistant or compare the brbackup

/ brrestore log files.

v TSM server is slowing down. Action: check if additional clients and/or

additional operations have been added. Have a look in the TSM servers activity

log.

If you are able to find any changes made to the system roll them back one at a

time and try to reproduce the problem. In most cases you will find the one change

or set of changes which caused the problem to occur. Now you can decide if you

need those changes or can fix their symptoms. Otherwise if you need to implement

those changes and can not prevent their symptoms you can now contact support

for the affected components.

Random Problems

If a problem seems to occur stochastic (sometimes it works, sometimes it does not)

without reason during an operation which the system has performed successfully

many times before, you should try to find out:

What is different when the problem occurs ?

Troubleshooting


Compare the logs of the application in question (brbackup / brrestore log,

sbtio.log, TSM activity log, etc.) to find out differences between successful and

unsuccessful runs. Try to find a pattern for the occurrence of the problem:

v Is it always occurring at the same time ?

v Is it always occurring after you run some other or the same operation ?

v Is it always occurring if some other application / process is running in parallel ?

If it is occurring always at the same time review if there are any scheduled

processes (virus checker, automatic updates, batch jobs). The above mentioned logs

may help you with this.

Providing Information to IBM or Tivoli Support

When you contact your support function, try to give a complete description of the

problem you encounter and the environment it occurs in. You should always

provide the following information:

v The version of DP for SAP

v The operating system level (including 32- or 64-bit) and patches that were

applied

v Oracle version (including 32- or 64-bit)

v TSM server version

v OS level for TSM server

v DP for SAP configuration file (initSID.utl)

including TSM client config files (dsm.sys, dsm.opt)

v Data Protection for SAP profile (initSID.utl)

v BR*Tools output for the operation in question (brarchive, brrestore)

v If the process worked previously, also have the change history of the system

components available

In addition to the above information there will be a situation in which you need to

supply additional information. Your service representative will ask you for this.

Invoking Data Protection for SAP Manually

Data Protection for SAP is usually invoked with a set of appropriate parameters by

the BR*Tools utilities. For troubleshooting purposes, however, it is possible to call

DP for SAP directly from the command line in order to perform data protection

operations manually, thus being able to correct errors. The command:

backint -?

displays a list of all possible Data Protection for SAP command line options.

Note: For the C shell, enclose the option string in quotes (backint '-?').

Backup Function

The backup function will be normally invoked by the SAP database utilities

BRBACKUP and BRARCHIVE. These programs give DP for SAP an input file (in

the case of backup and inquire) containing the names and paths of the database

files to be handled.

For troubleshooting, however, it might be necessary to call this function of DP for

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

Troubleshooting


|


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


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

Note

The Data Protection for SAP profile init<SID>.utl has to be specified with

the path and file name statement as shown above.

The program prompts you to enter one or more file names. Every successful

backup run (collection of one or more files) is allocated its own backup ID within

Tivoli Storage Manager.

Don’t forget to press CTRL + D on a UNIX or Linux system or CTRL + Z on a

Windows system after you typed in the file name to backup.

Restore Function

The restore function will be normally started by the SAP database utility

BRRESTORE.

For troubleshooting, however, it might be necessary to call this function of DP for

SAP directly to restore individual files. This function can be invoked from the

command line as follows.


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


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

You will be prompted to enter the backup ID and the full file names of the files to

be restored. If the files are to be restored to another directory, it is necessary to

specify the path to the input files.

Caution

If a file is restored directly, any existing file with the same name will be

overwritten without warning. Thus, it is recommended that you restore

database files directly only in a very controlled manner, when it is absolutely

necessary in order to remove an error. In normal operation you should never

restore a database directly, because this could corrupt the SAP database.

Troubleshooting


Inquire Function

The inquire function, normally invoked by BR*Tools and BRRESTORE, will be

used to query the Tivoli Storage Manager server for backup IDs or files which

belong to a particular backup ID.

For troubleshooting, however, it might be necessary to invoke this function

manually from the command line as follows.


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


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

DP for SAP prompts you to enter the inquiry in one of four formats. These are:

1. #NULL - to display all backup IDs saved so far. A typical line of the response

could be:

#BACKUP JE0___A0DNE9Z74C

The backup ID in this case is JE0___A0DNE9Z74C (#BACKUP does not belong to the

backup ID). The first six characters are the user defined prefix (see

BACKIDPREFIX on page 106). The next 10 characters after this represent a

unique ID of the backup.

2. BackupID - to display all of the files which belong to that backup ID. A typical

result could be:

##BACKUP JE0___A0DNE9Z74C /oracle/C21/dbs/initC21.utl.

3. #NULL filename - to display all of the backup IDs corresponding to this file.

Filename requires an input consisting of path and name of the file.

4. BackupID filename - to verify whether a particular file has been saved under a

certain backup ID. Filename requires an input consisting of path and name of

the file.

Delete Function

The delete function is used as part of the versioning control mechanism of DP for

SAP and can only be called by DP for SAP itself or by a user.

The delete function allows you to delete individual files, which might be necessary

for recovering from an error. This function can be invoked from the command line

as follows:


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


backint -p <drive: or UNC name>\orant\database\init<SID>.utl -f delete

You will be prompted to enter the backup ID and the full file names of the files to

be deleted.

Troubleshooting


File Manager

The File Manager requires a correct setup of DP for SAP particularly with regard

to the backint executable, thus enabling it to connect to the TSM server without

errors. To connect to the TSM server the File Manager calls the backint executable.

If this call fails, the File Manager shows an error message but does not analyze

what the reason for the failure is. To analyze the error, backint manually with the

inquire function (see “Inquire Function” on page 161) and check the output for

error messages.

Troubleshooting


Appendix D. Using DP for SAP with a Distributed File System

on AIX

Note: This chapter formerly referred to the SAN File System, which is being

discontinued in favor of the General Purpose File System (GPFS™). The

chapter now uses the general term distributed file system.

Setting Up DP for SAP in a Distributed File System

If you statically assign all SAP systems to specific hosts (i.e. instances are not

moved between hosts), grant the root user read/write access permission to the

distributed file system (such as the SAN File System or General Purpose File

System) and follow the regular installation process as outlined in Chapter 4,

“Installing or Upgrading Data Protection for SAP,” on page 25. In this case, no

additional actions are required.

If there is only a single SID located on a host, DP for SAP can be set up without

granting the root user a permanent read/write permission for the distributed file

system. This is achieved by having the ProLE service run by the ora<SID> userid

instead of root.However, for multiple SIDs on a host system, the ProLE service should be run by

root, and the root user should have permanent read/write permission for the

distributed file system. If this poses a problem in your environment, contact your

support function.

To make Data Protection for SAP work without granting root permanent access to

the distributed file system perform the following steps:

1. Enable root access to the distributed file system.

2. Install Data Protection for SAP using the procedure described in Chapter 4,

“Installing or Upgrading Data Protection for SAP,” on page 25.

3. In file /etc/inittab, replace the line

po64:345:respawn:/usr/tivoli/tsm/tdp_r3/ora64/prole -p...

by

po64:345:respawn:su - ora<SID> -c /usr/tivoli/tsm/tdp_r3/ora64/prole -p...

where <SID> must be the actual SID.

4. Execute the command

init q

5. Disable root access to the distributed file system.

Setting Up DP for SAP in a Distributed File System in an Adaptive

Computing Environment

If you plan to use Data Protection for SAP in an Adaptive Computing

Environment, a special setup is necessary to fully utilize its benefits.


|

|

|

|||

||

||||||

||||||||

||

|

||

|

|||

|

|||

|

|

|||

|

||

|

||

Since the Adaptive Computing Environment currently does not allow more than

one SID per host, the procedure described here will work without granting the root

user additional permissions for the distributed file system.

To prepare the installation in the distributed file system, perform the following

steps:

1. Log in as root user and perform a regular installation of Data Protection for

SAP on one of the systems participating in the distributed file system. Have the

installation procedure create the configuration files and links to the executables

of Data Protection for SAP in a directory which is not located in the distributed

file system (for example /tmp). These files will not be used and can therefore

be deleted afterwards.

2. After the successful installation, copy the content of the installation directory

/usr/tivoli/tsm/tdp_r3/ora64

to an arbitrary directory in the distributed file system. For example:

mkdir /san/SanFS/tivoli/tdp_r3

cp -r /usr/tivoli/tsm/tdp_r3/ora64 /san/SanFS/tivoli/tdp_r3

3. Now each of the different SAP environments can be set up for using Data

Protection for SAP for backup and recovery. In the Adaptive Computing

Environment, this can be performed from the same host for all participating

SID’s. For each SID, log in as the database instance owner and execute the

script ’SanFSsetupSID.sh’ from the installation path in the distributed file

system.

For example:

/san/sanFS/tivoli/tdp_r3/ora64/SanFSsetupSID.sh

The following information must be provided to the script:

a. The system ID (SID) for the SAP system to be backed up.

b. The path for the Data Protection for SAP executables unless the default is

used.

c. The path for the Data Protection for SAP profile and configuration file

(init<SID>.utl, init<SID>.bki).

d. For a connection to an Administration Assistant server, its hostname or IP

address and its server port.4. The script SanFSsetupSID.sh creates scripts prepareTDPSAP_<SID>.sh. On each

host, log in as root user and execute the script prepareTDPSAP_<SID>.sh with

the appropriate <SID>. If you place this script in the distributed file system

make sure the root users have the appropriate permissions to execute it.

5. Whenever a SID is moved to a different host the script

’prepareTDPSAP_<SID>.sh’ must be executed by the root user of the new host.

Setting up DP for SAP with Oracle RMAN in a Distributed File System

in an Adaptive Computing Environment

The script SanFSsetupSID.sh does not create the link /usr/lib/libobk.a to the DP

for SAP shared library. Therefore, when configuring Oracle to use the Data

Protection for SAP shared library (see: “Verifying the RMAN Setup on UNIX and

Linux Systems” on page 29) specify the full path and name of the library located

Using DP for SAP with a Distributed File System on AIX


|||

||

||||||

|

|||

|

||||

|||||||

|||

|

|

||

||

||

||||

||

||

|

||||

in the directory residing in the distributed file system. Add this directory to the

library path environment of the database instance owner.

Note

Do not link Oracle with the library in /usr/lib. Otherwise, after the instance

is moved to a different host your database may fail to start.


Appendix D. distributed file system 165

|||

||||||

Appendix E. Installation Planning Sheets

Data Protection for SAP

Before starting the installation procedure, collect the following information.

Note: The following table is also provided in file form as planning_sheet_oracle

for UNIX and Linux and planning_sheet_oracle.txt for Windows.

Table 6. Installation Parameters for Data Protection for SAP

UNIX

or

Linux Windows Installation Parameter

X X

Oracle database SID:

X X

Path where the SAP BR*Tools reside:

Default: /usr/sap/<SID>/SYS/exe/run or C:\oracle\<SID>\sapmnt\SYS\exe\run

X X

TSM server name or IP address:

X X

TSM node name: TSM node configured on the TSM server named for the backup of the SID

denoted above. For details, refer to “4. Node Definition” on page 184.

X X

Tivoli Storage Manager management classes for database and redo log backups. Management

classes configured for the database backup and for the backup of redo logs. For details, refer to

“3. Policy Definition” on page 183.

Default: MDB for database backups, MLOG1 and MLOG2 for redo log backups.

X

Path where the Tivoli Storage Manager API resides (contents of environment variable

DSMI_DIR):

Default: C:\Program Files\Tivoli\TSM\baclient

X

Path to client option file of Tivoli Storage Manager (contents of environment variable

DSMI_CONFIG). For details refer to the Tivoli Storage Manager documentation.

X

Path to Tivoli Storage Manager log files (contents of environment variable DSMI_LOG): The

TSM API will create the file dsierror.log< in this path. For details, refer to the Tivoli Storage

Manager documentation.

Default: C:\temp


|

Table 6. Installation Parameters for Data Protection for SAP (continued)

UNIX

or

Linux Windows Installation Parameter

X

Installation path for Data Protection for SAP executables:

Default: C:\Program Files\Tivoli\TSM\tdp_r3\ora or C:\Program Files\Tivoli\TSM\tdp_r3\ora64

X X

Path for Data Protection for SAP configuration files (directory for SAP configuration files).

During the installation, the Data Protection for SAP configuration files will be saved to this

path. If old configuration files are found, they are renamed to <filename>.nnn, where nnn is a

three-digit decimal number.This path must not contain blanks.

Default: /oracle/<SID>/dbs or C:\orant\database

X X

Options:

v Use of Oracle RMAN.

v Use of the Administration Assistant (see Chapter 8, “Installing and Using the Administration

Assistant for Data Protection for SAP,” on page 63 and Table 7). The Administration Assistant

should be installed prior to Data Protection for SAP so that the interface between the two can

be established automatically.

Administration Assistant

Prior to installing the Administration Assistant for Data Protection for SAP

(optional but recommended), collect the following information.

Note: The following table is also provided in file form as planning_sheet_aa for

UNIX and Linux, and planning_sheet_aa.txt for Windows.

Table 7. Installation Parameters for the Administration Assistant

Installation

Option Installation Parameter

Option: Installation type.

Decision as to whether the Administration Assistant is to be installed on a single host ('typical'

installation) or distributed across multiple hosts ('custom' installation). If 'custom' is selected, a list

of the individual components is presented with appropriate check boxes for selection. A multi-host

installation requires that all connecting instances of Data Protection for SAP be version 5.4 or

higher. For more information on single- and multi-host installations, see Chapter 8, “Installing and

Using the Administration Assistant for Data Protection for SAP,” on page 63.

Default: Single-host

Option: Server/client communication mode.

Decision as to whether the Administration Assistant Server component and clients communicate in

nonsecure mode via HTTP or secure mode via HTTPS

Default: Nonsecure

Installation Planning Sheets


|

Table 7. Installation Parameters for the Administration Assistant (continued)

Installation


Option: Database type.

Decision as to which DBMS the Administration Assistant should use. Select either the installation

of the bundled Apache Derby package or the use of an existing Apache Derby or IBM DB2

installation.

Default: Installation of Apache Derby as bundled with product.

Option: Data migration.

If you want to transfer data from an existing Administration Assistant environment, enter the

directory containing the *.aa files.

Default: No migration.

Option: Software language.

Decision as to whether to install only the English version of the program or all national language

versions.

Default: English-only

Parameters applying to the Administration Assistant Server component:

Hostname or IP address:

Default: Hostname of current system

Port number for Data Protection for SAP (ProLE) connect. This port number must be made known

to all instances of Data Protection for SAP that are to be managed and monitored by this Server

component instance.

Default: 5126

Port number for client connect in non-secure mode (HTTP).

Default: 80

Port number for client connect in secure mode (HTTPS).

Default: 443

RMI registry port number

Default: 1099

Port number for performance data from Database Agent

Default: 5129

Port number for communication with Database Agent

Default: 5128


Appendix E. Installation Planning Sheets 169

|

|

|||

|

|

|

|

||

|

|


Installation


Parameters applying to the Administration Assistant Database Agent component



Port number for Data Protection for SAP (ProLE) connect

Default: 5125

Port number for communication with Administration Assistant Server component

Default: 5127

Parameters applying to the Administration Assistant Database component (Apache Derby)



Port number for database connect

Default: 1527

User ID and password to access internal database. The password can later be changed using the

bundled program changeSettings.jar in the utils subdirectory of the Administration Assistant

installation directory.

Parameters applying to the Administration Assistant Database component (IBM DB2)



Port number for database connect

Default: 50000

User ID and password of the system user for which the DB2 instance should be installed that the

internal database should access. The password can later be changed using the bundled program

changeSettings.jar in the utils subdirectory of the Administration Assistant installation directory.

Installation directory (on each host)

Default: /opt/tivoli/tsm/tdp_r3_assist on UNIX and Linux, or C:\Program Files\tdpr3assi on

Windows.

Product

Support

Location of mail.jar (Java Mail)

Product

Support

Location of activation.jar (Java Beans Activation Framework):



|||

|

|

|

|

|

|

|||

|


Installation


History file directory (on Server component host)

Default: history (in installation directory)

History file retention time (days). Can be changed via the Administration Assistant client.

Default: 14

Secure

Communication

Information on the public key infrastructure (PKI):

v Keystore name. Keystore containing the private and public keys of the Administration Assistant

Server component when running in secure mode. If you do not yet have a public key

infrastructure, the keystore can be created during the installation process.

v Keystore password. Password ensuring the consistency of the keystore. The server’s key pair must

be protected by the same password.

v Truststore name. Truststore containing a set of trusted certificates. When running in secure mode,

the Administration Assistant’s server certificate must be verified against this truststore when the

server is started.

v Truststore password. Password ensuring the consistency of the truststore. This is only required if a

trusted certificate needs to be imported into the truststore during the installation process.

v Certificate file. Path of the certificate file in case you already have a server certificate issued by a

certificate authority.

v Certificate creation information. Information on the X.500 distinguished name (common name,

organizational unit, organization name, locality name, state name, and country code) and on the

validity period required in case a new self-signed certificate is to be created during the

installation process. For details on this information, refer to the X.500 and X.509 standards.

v New certificate file name. If the public key of a newly created server key pair needs to be

distributed to client machines it will be exported to this file.

v CSR file name. If the newly created server key pair will be used to request a certificate signed by

a Certificate Authority, the Certificate Signing Request will be written to this file.


Appendix E. Installation Planning Sheets 171


Installation


Internal

database

managed by

DB2

In order to use DB2 Support, this version of the Administration Assistant requires the additional

Java package

DB2 JDBC Universal Driver

The corresponding packages are bundled with your IBM DB2 installation.

v db2jcc.jar location:Default: None

v db2jcc_license_cu.jar location:Default: None

The Administration Assistant database is enabled for automatic storage and has a set of one or

more associated storage paths. Enter at least one disk or path that DB2 is allowed to assign and

allocate for its table space containers.

On Windows systems enter a comma separated list of disks, such as C:, G:, X:.

On UNIX and Linux systems, enter a comma separated list of paths, such as /db2,/db2/db2_v01

Default: None

The name of the internal database is predefined and cannot be changed.

Default: AADB

Internal

database

managed by

Apache Derby

Database directory:

Default: aaDBSupport (in installation directory)

Name of the internal database

Default: 'adminAssistant'

Retention time for data in database (days). (To save this data, the backup facilities offered by

Derby can be used.)

Default: 175

Documentation

Option: English-only or all languages

Default: English-only



||||

||

|

|

||

||

|||

|

|

|

|

|

Appendix F. Reference Material for the Administration

Assistant

Sample Command Files for Scheduling Reports

You may want to create a command file ( .bat or .cmd on Windows or .sh on

UNIX systems ) setting the correct environment and scheduling one or more

reports on the scheduling client system.

Sample Shell Script for Scheduling a Report from a UNIX

Scheduling Client

File scheduledReport.sh is included in your Data Protection for SAP package and

is copied to the installation path of the Administration Assistant.

#--------------------------------------------------------------------------

#

# Tivoli Storage Manager for ERP. Data Protection for SAP (R)

#

# Sample command file for the Administration Assistant scheduling client

#

# --------------------------------------------------------------------------

# ***** NOTE ***** NOTE ***** NOTE *****

#

# This script is provided as a model and should be

# carefully tailored to the needs of the specific site.

#

# ***** NOTE ***** NOTE ***** NOTE *****

#--------------------------------------------------------------------------

export CLASSPATH=/reporting/Admt.jar:$CLASSPATH

export PATH=/usr/bin:$PATH

java -classpath $CLASSPATH com.ibm.bkit.schedulerIF.Sched_Main xxx.xxx.xxx.xxx...

... 1099 myReport ADMIN admin directory=/myreports log=/tmp/reportlogs

Sample Command File for Scheduling a Report from a

Windows Scheduling Client

File scheduledReport.cmd is included in your Data Protection for SAP package and

is copied to the installation path of the Administration Assistant Server component.

#--------------------------------------------------------------------------

#

# Tivoli Storage Manager for ERP. Data Protection for SAP (R)

#

# Sample command file for the Administration Assistant scheduling client

#

# --------------------------------------------------------------------------

# ***** NOTE ***** NOTE ***** NOTE *****

#

# This script is provided as a model and should be


#

# ***** NOTE ***** NOTE ***** NOTE *****

#--------------------------------------------------------------------------

set CLASSPATH=C:\ProgramFiles\reporting\Admt.jar

set PATH=C:\Program Files\IBM\Java142\jre\bin:%PATH%

java -cp %CLASSPATH% com.ibm.bkit.schedulerIF.Sched_Main xxx.xxx.xxx.xxx ...

... 1099 myReport ADMIN admin directory=C:\reports log=C:\reportlogs


Sample Custom SQL File

# CUSTOM SQL FILE FOR THE ADMINISTRATION ASSISTANT

#

# This file should only be changed by an IBM Employee

# After the changes you have to check this file using CustomSQLFilecheck

#

# NOTE: Each entry must be coded in one line. The multi-line format

# shown below is for illustration purposes only.

#

#

# Sample threshold definition: backup size > 500 GB, display group 1, backup type 2

#

<sql>select * from AdminAssistant.tsmrun where amount > 500000000000</sql>

<description>Amount over 500 GB</description>

<programid>0</programid>

<actionid>0</actionid>

<displaygroup>1</displaygroup>

<backuptype>2</backuptype>

<executionmode>0</executionmode>

<param>[email protected]</param>

#

Reference Material for the Administration Assistant


|

||||||||||||||||||||||

Appendix G. Alternate or Parallel Backup Paths and Backup

Servers

With Data Protection for SAP, the term ″path″ denotes a connection between a

Tivoli Storage Manager client, or better TSM ″node″, and a Tivoli Storage Manager

server.

For each communication path (for example, a Tivoli Storage Manager server

network address), you define a set of additional communication parameters. This

set of communication parameters is called client option data and is collected under

a logical server name that you can choose freely. Under UNIX or Linux, it is

possible to store all client option data in a single client system option file that is

called dsm.sys. Under Windows, you will need to store the client option data for

each logical server in separate client option files that have the file names

<servername>.opt. For example, if you have two logical Tivoli Storage Manager

servers fast and slow, then you need two client option files fast.opt and slow.opt.

For Windows, you need an additional client user option file, dsm.opt. All option

files must reside in the same directory.

Data Protection for SAP provides the capability for controlling alternate backup

paths and alternate backup servers in order to use several communication links

between Tivoli Storage Manager clients to:

v Increase throughput by transferring data:

– Over multiple paths simultaneously

– To and from several servers in parallelv Increase the availability of the Tivoli Storage Manager client-to-server

communication

v Enable disaster recovery backup to a special (remote) Tivoli Storage Manager

server

In the profile init<SID>.utl, each path is defined by a server statement (see also

“Sample Data Protection for SAP Profiles” on page 115) and the corresponding

definitions in the Tivoli Storage Manager client system option file dsm.sys for

UNIX or Linux systems or <server>.opt on Windows systems.

The statement SERVER <server 1..n> denotes Tivoli Storage Manager servers in the

Data Protection for SAP profile. This corresponds to the statement SERVERNAME

<server 1..n> in the Tivoli Storage Manager client option file(s). These servers are

identified by their TCPSERVERADDRESS and can be located on one system (multiple

paths) or several systems (multiple servers).

SESSIONS denotes the number of parallel session DP for SAP will schedule for the

given path.

Note

If only one path is used, SESSIONS must be equal to MAX_SESSIONS, the

parameter identifying the total number of parallel sessions to be used

(equivalent to number of tape drives/management classes).


DP for SAP attempts to communicate with the Tivoli Storage Manager server using

the first path in the profile. If this proves successful, DP for SAP starts the number

of parallel sessions as specified for this path; if the attempt was unsuccessful, this

path is skipped, and DP for SAP continues with the next path. This continues until

as many sessions are active as were specified in the total session number

(MAX_SESSIONS). If this number is never reached (for example, because several

paths were inactive), DP for SAP terminates the backup job.

Parameter Settings - SERVER Statement

The SERVER statement appears in the Data Protection for SAP profile, and there

are corresponding keywords in the Tivoli Storage Manager client option file.

(Depending on the choice of password handling, some parameters are ignored.)

The connection of the sections in the Data Protection for SAP profile and the Tivoli

Storage Manager client option file is established from the logical server name,

which is defined in the keywords SERVER or SERVERNAME.

Note: The logical server names are also used by the ″View TSM Server Utilization″

function of the Administration Assistant. There, a separate entry is generated

for each logical server name found in the system landscape, and identical

logical server names are considered to represent the same server.

Table 8. SERVER Statement and Appropriate Profile and Option File Settings.

Configuration possibilities Data Protection for SAP profile

init<SID>.utl

Tivoli Storage Manager client option

file dsm.sys or <server>.opt

[2]

single path; no password or manual

password

SERVER <server>

ADSMNODE <node>[1]

SERVERNAME <server>

TCPSERVERADDRESS <address>

NODENAME must not be

specified

single path; automatic password by

Tivoli Storage Manager

SERVER <server>

ADSMNODE must not be

specified

SERVERNAME <server>

NODENAME <node>


several paths/servers; no password

or manual password

SERVER <server 1>

ADSMNODE <node 1>

•

•

•

SERVER <server n>

ADSMNODE <node n>

SERVERNAME <server 1>


specified

TCPSERVERADDRESS <address 1>

•

•

•

SERVERNAME <server n>


specified

TCPSERVERADDRESS <address n>

several paths/servers; automatic

password by Tivoli Storage

Manager[3]

SERVER <server 1>


specified

•

•

•

SERVER <server n>


specified

SERVERNAME <server 1>

NODENAME <node 1>

TCPSERVERADDRESS <address 1>

•

•

•

SERVERNAME <server n>

NODENAME <node n>

TCPSERVERADDRESS <address n>

Alternate or Parallel Backup Paths and Backup Servers


||||

Table 8. SERVER Statement and Appropriate Profile and Option File Settings. (continued)

Configuration possibilities Data Protection for SAP profile

init<SID>.utl

Tivoli Storage Manager client option

file dsm.sys or <server>.opt

[2]

several paths/servers; automatic

password by Tivoli Storage Manager

with Tivoli Storage Manager API 5.2

or higher

[4]

SERVER <server>


specified

TCP_ADDRESS <address 1>

•

•

•

SERVER <server n>


specified

TCP_ADDRESS <address n>

SERVERNAME <server

NODENAME <node>


Notes:

[1] If ADSMNODE is not specified, the host name is used.

[2] On UNIX or Linux, dsm.sys is the single client option file for all Tivoli

Storage Manager servers. On Windows, there is a separate client option file

<server>.opt for each Tivoli Storage Manager server.

[3] If two different physical machines have the same TSM node name or if

multiple paths are defined on one node using several server stanzas,

passwordaccess generate may only work for the first stanza that is used

after password expiration.

During the first client-server contact, the user is prompted for the same

password for each server stanza separately, and a copy of the password is

stored for each stanza. When the password expires, a new password is

generated for the stanza that connects the first client-server contact.

All subsequent attempts to connect via other server stanzas will fail,

because there is no logical link between their copies of the old password

and the updated copy generated by the first stanza used after password

expiration.

To avoid the problem, update the passwords before they expire, to solve

the problem if the passwords have expired, proceed as follows:

1. dsmadmc and update the password on the server.

2. Run dsmc -servername=stanza1 and use the new password to generate

a proper entry.

3. Run dsmc -servername=stanza2 and use the new password to generate

the proper entry.

[4] If you are using Tivoli Storage Manager API 5.2 or higher you can make

use of the new parameter TCP_ADDRESS in the Data Protection for SAP

profile. This makes the multiple stanzas in the Tivoli Storage Manager

client option file for multiple paths obsolete and eliminates the problem

when updating the password (see [3]).

Example 1: Use of Alternate Paths for Increased Availability

Assume the following configuration:

Tivoli Storage Manager server with:

– 2 tape drives

– 2 LAN connections.


Appendix G. Backup Paths and Servers 177

A backup is normally performed via network path 1 (SERVER statement 1). If this

is unavailable the backup shall be performed using network path 2 (SERVER

statement 2).

The definitions in the Data Protection for SAP profile could be as shown in the

example below.

If path 1 is active, DP for SAP will start the 2 sessions as defined in the SERVER

statement for path 1. Since MAX_SESSIONS is also 2, no more sessions will be

started.

If path 1 is inactive, Data Protection for SAP will start 2 sessions on path 2. Since

this equals the MAX_SESSIONS definition as well, backup will be executed using

path 2.

Even if the logical names server_a and server_b actually point to the same TSM

server, the Administration Assistant will still consider them to be two different

TSM servers.

Data Protection for SAP profile. Example 1

MAX_SESSIONS 2 # 2 tape drives

.

.

SERVER server_a # via network path 1

ADSMNODE C21

SESSIONS 2

PASSWORDREQUIRED YES

BRBACKUPMGTCLASS mdb

BRARCHIVEMGTCLASS mlog1 mlog2

# USE_AT 0 1 2 3 4 5 6

SERVER server_b # via network path 2

ADSMNODE C21

SESSIONS 2


BRBACKUPMGTCLASS mdb

BRARCHIVEMGTCLASS mlog1 mlog2

# USE_AT 0 1 2 3 4 5 6



|||

Example 2: Use of Parallel Servers for Increased Performance


Two Tivoli Storage Manager servers with connections via two network paths:

– server_a, TCP/IP address xxx.xxx.xxx.xxx

– server_b, TCP/IP address yyy.yyy.yyy.yyy

– Each of these servers has:

- two tape drives A SAP database server connected to two networks.

Backups are done on both systems every day.


example below.



.

.


ADSMNODE C21

SESSIONS 2


BRBACKUPMGTCLASS MDB

BRARCHIVEMGTCLASS MLOG1 MLOG2 MLOG3 MLOG4

# USE_AT 1 2 3 4 5 6 7

SERVER server_b # via network path 2 ADSMNODE C21

SESSIONS 2




# USE_AT 1 2 3 4 5 6 7


Appendix G. Backup Paths and Servers 179

|

Example 3: Use of Alternate Servers for Disaster Recovery


Two Tivoli Storage Manager servers:

– server_a, TCP/IP address xxx.xxx.xxx.xxx

– server_b, TCP/IP address yyy.yyy.yyy.yyy

Each of these servers with:

– four tape drives (MAX_SESSIONS 4). A SAP database server connected to this FDDI network.

Normal backups are to be performed with server a, which is local to the SAP

database server. Every Friday a disaster recovery backup should be stored on a

remote Tivoli Storage Manager server (server b).


example below.



.

.


ADSMNODE C21

SESSIONS 4




USE_AT 1 2 3 4

SERVER server_b # via network path 2

ADSMNODE C21

SESSIONS 4




USE_AT 5 # for Disaster Recovery



Appendix H. Preparing Tivoli Storage Manager for DP for SAP

This chapter explains the procedures for setting up TSM for working with Data

Protection for SAP in an SAP environment. A typical list of actions that the Tivoli

Storage Manager installer or administrator must perform to prepare Tivoli Storage

Manager to work in an SAP environment will be explained.

Note

The following steps and procedures are only samples. The actual values in

your specific environment may be different.

Configuring the Tivoli Storage Manager Server

This section shows the procedure for setting up the Tivoli Storage Manager server.

General server configurations will be described first and finally specific server

configurations, such as setup of storage devices.

The Tivoli Storage Manager commands presented in this chapter are shown in full

for ease of understanding. In the Tivoli Storage Manager command line interface,

short cuts or abbreviations for all commands and parameters can be used for

convenience. Tivoli Storage Manager also has a Web-browser-based Graphical User

Interface (GUI).

General Considerations for TSM

Before starting the installation, some important performance issues should be

considered. The careful choice of the server that is to be installed, the network

topology, and the use of powerful hardware can improve performance within the

system landscape and can avoid performance bottlenecks.

v Host for Tivoli Storage Manager server. The Tivoli Storage Manager server

should be installed on an exclusive machine. This procedure avoids concurrent

processes and disk I/O accessing with other applications. In a single SAP system

landscape, a single Tivoli Storage Manager server is sufficient. If you plan to use

the Storage Manager to back up/restore other clients as well, you should

consider either installing the server software on a large machine or using several

Tivoli Storage Manager servers.

v Network topology. Network topologies such as Ethernet, Token Ring, FDDI and

Fast Ethernet work all well with Tivoli Storage Manager. In general, the fastest

network topology like FDDI or Fast Ethernet should be used to prevent

bottlenecks during backup/restore operations. Tivoli Storage Manager supports

multiple network adapters, increasing server throughput by providing multiple

connections to the same network or several physically distinct networks with the

same server.

v RS/6000® SP™ environment. An RS/6000 SP node can be used for a Tivoli

Storage Manager server. The use of a High Performance Switch network will

improve performance of backup/restore operations on the Tivoli Storage

Manager server.


Prerequisites

It is assumed that the Tivoli Storage Manager server has already been successfully

installed. This means that the following steps have been completed:

v Tivoli Storage Manager server has been installed. For information on the

required release and maintenance level, refer to the DP for SAP release notice.

v Recovery log volume has been allocated and initialized.

v Recovery log mirror volume has been allocated and initialized.

v Database volume has been allocated and initialized.

v Database mirror volume has been allocated and initialized.

v Additional labeled volumes for the backup and archive storage pools have been

allocated and initialized (disks, tapes or combinations).

v Licenses have been registered.

v The Tivoli Storage Manager server has been started.

For information on installing Tivoli Storage Manager, see the Tivoli Storage Manager

Quick Start manual.

Note

The latest code fixes for Tivoli Storage Manager can be found at:

ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance

Adjusting Tivoli Storage Manager for DP for SAP

Note

The following steps and procedures are only samples. The actual values in

your specific environment may be different.

In order to adjust the installed TSM to the DP for SAP, the following activities

must be performed.

1. Storage Device Setup

A storage device defines a device class, which will handle one type of media, e.g.,

tape libraries or jukeboxes. There is a default device class defined for disks called

DISK which obviates the need for a redefinition.

For proper storage device setup, check the following items established within the

Tivoli Storage Manager server during the installation procedure:

v Query defined library

q library

v Query defined drives

q drive

v Query defined device class

q devclass

Preparing Tivoli Storage Manager for DP for SAP


2. Storage Pool Definition

A storage pool is a named collection of storage volumes that are associated with

one device class. Each storage pool represents a collection of volumes that are the

same media type. The storage pool setup defines the storage hierarchy for the

appropriate environment.

In an SAP environment, there are different kinds of data to be backed up. These

are:

v SAP system data

v SAP database data (data files, online/offline redo log, control files)

To separate this data within the Tivoli Storage Manager, you must define

appropriate storage pools for each of these data collections. The following section

gives examples of how storage pools within Tivoli Storage Manager can be defined

in consideration of the requirements mentioned above.

To define storage pools within the Tivoli Storage Manager server, log on as Tivoli

Storage Manager Administrator using the Admin Command Line or the Web Admin

and invoke the following commands:

1. Definition of a storage pool for the SAP system data

define stgpool sap_incr <device_class_name> maxscr=5

2. Definition of a storage pool for the data files

define stgpool sap_db <device_class_name> maxscr=20

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

define stgpool sap_log1 <device_class_name> maxscr=3

4. It is strongly recommended that you back up the offline redo log files twice on

two different Tivoli Storage Manager volumes. For this purpose, you have to

define an additional storage pool for the second copy of offline redo log files.

define stgpool sap_log2 <device_class_name> maxscr=3

Note

When you associate a library tape device, you have to define the maximum

number of scratch volumes (labeled volumes which are empty or contain no

valid data) this storage pool will be allowed to use (parameter maxscr). The

maximum number of scratch tapes depends on the size of the database, the

capacity of the tapes, the number of scratch volumes available and how many

versions of the backup you will keep. Replace these values with your

estimates.

3. Policy Definition

Tivoli Storage Manager policies are used to specify how files are backed up,

archived, migrated from client node storage, and managed in server storage.

A policy definition includes the definition of a policy domain, a policy set,

management classes and copy groups. After the definition phase, you need to assign a

default policy set and validate and activate it.


Appendix H. Preparing Tivoli Storage Manager for DP for SAP 183

For the policy definition, log on as a Tivoli Storage Manager Administrator using

the Admin Command Line or the Web Admin and invoke the following commands:

1. Policy domain and policy set definition

define domain sap_c21

define policyset sap_c21 p_c21

2. Management Class definition for file system backups, data files, offline redo

logs and copies of offlineredo logs

define mgmtclass sap_c21 p_c21 mdefault

define mgmtclass sap_c21 p_c21 mdb

define mgmtclass sap_c21 p_c21 mlog1

define mgmtclass sap_c21 p_c21 mlog2

Note

If you are planning to use this Tivoli Storage Manager server with

multiple SAP systems, it is recommended that you use a set of different

management classes for each system.

3. Copy Group definition

define copygroup sap_c21 p_c21 mdefault type=backup destination=sap_incr

define copygroup sap_c21 p_c21 mdefault type=archive destination=archivepool

define copygroup sap_c21 p_c21 mdb type=archive destination=sap_db retver=nolimit

define copygroup sap_c21 p_c21 mlog1 type=archive destination=sap_log1 retver=nolimit

define copygroup sap_c21 p_c21 mlog2 type=archive destination=sap_log2 retver=nolimit

DP for SAP uses its own version control mechanism for managing SAP database

backups. To do this, DP for SAP backs up all data only to management classes

for which an archive copy group has been defined (parameter type set to

archive; for a definition, see Glossary page 215). In addition, to prevent backed

up files within Tivoli Storage Manager being deleted because of their expiration

date (Tivoli Storage Manager deletes expired files), the copy group parameter

retver (specifies the number of days a file is to be kept) should be set to

unlimited (9999 or nolimit).

4. Assigning the default management class

assign defmgmtclass sap_c21 p_c21 mdefault

5. Validating and activating the policy set

validate policyset sap_c21 p_c21

activate policyset sap_c21 p_c21

4. Node Definition

The Tivoli Storage Manager server views its registered clients, application clients,

host servers, and source servers as nodes that require services and resources from

the server.

To register a node within Tivoli Storage Manager, log on as Tivoli Storage Manager

administrator using the Admin Command Line or the Web Admin and invoke the

following command:

register node C21 passwd domain=sap_c21 maxnummp=8



Note

If you are using two or more tape drives, you may want to pay special

attention to the node parameter maxnummp. It defines the maximum number of

mount points that one node can use. The default value is 1. If one node

should use more than one mount point, the parameter must be set to the

desired number of mount points. This parameter should not be set higher

than the total number of drives available on the TSM Server.

5. TSM Server Configuration

For simulations of network transfer and media rates, the TSM server must be

configured so that sessions do not time out during simulation. This is achieved by

setting the parameter IdleTimeOut to a value higher than the time required for

sending the largest table space file to TSM. For example:

setopt IdleTimeOut 60

Configuring the Tivoli Storage Manager Clients

After the server configuration, you have to configure the clients that will use the

Tivoli Storage Manager server. These include the backup-archive client for the file

system backups and the Application Programming Interface (API) client for interface

programs. The Tivoli Storage Manager backup-archive client will be used for file

system backups. The API client allows users to enhance existing applications with

backup, archive, restore, and retrieve services. An installed and confirmed API

client is a prerequisite for DP for SAP.

General Considerations

First of all, if a successful installation of Tivoli Storage Manager backup/archive

client and API client is to be performed, the clients must be installed on all nodes

that will interface with the Tivoli Storage Manager server.

In the context of an SAP system landscape, this means that the Tivoli Storage

Manager backup/archive client must be installed on every machine scheduled for

a file system backup, for example, SAP application servers and the SAP database

server. The Tivoli Storage Manager API client only needs to be installed on the

SAP database server machine to enable backup/restore operations of the SAP

database in combination with the backup interface program DP for SAP.

Note: The Administration Assistant uses the logical TSM server names in its ″View

TSM Server Utilization″ function. Identical logical names are considered to

represent the same TSM server, but different entries are generated for each

logical server name found in the system landscape. Therefore, it is

recommended whenever possible to use identical logical server names when

pointing to the same TSM server throughout the system landscape, and to

use different logical server names when different TSM servers are addressed.

Tivoli Storage Manager Clients on UNIX or Linux Systems

The setup for the Tivoli Storage Manager client is effected in UNIX or Linux

environments by changing the files dsm.opt and dsm.sys. Subsequently, the

include/exclude file must be configured. It defines which files the Tivoli Storage

Manager backup/archive client will include or exclude for any backup, archive or



|||||||

hierarchical storage procedure. Examples of an include/exclude file for UNIX or

Linux can be found in “Sample TSM Profiles for UNIX or Linux” on page 197.

The following serves as a quick guide for configuring the Tivoli Storage Manager.

It presents a typical list of actions that the Tivoli Storage Manager installer or

administrator must perform to prepare the Tivoli Storage Manager to operate in an

SAP environment.

Follow these steps:

1. Install the Tivoli Storage Manager client software on the SAP database server

machine.

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

appropriate to your installation:

Servername server_a

TCPPort 1500

TCPServeraddress xxx.xxx.xxx.xxx or servername

InclExcl /usr/tivoli/tsm/client/ba/bin/inclexcl.list

Compression OFF

3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are on

the same machine. This makes TCP/IP communication a little faster.

4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude the

files listed in inclexcl.list. This is optional. You may want to exclude all

database files that are processed by the BR*Tools.

5. If you have tape drives with hardware compression attached to the Tivoli

Storage Manager server, you might get better throughput with the hardware

compression than you would with the Tivoli Storage Manager client software

compression (Compression ON). However, it is not recommended to combine the

various compression methods.

You will need to try Tivoli Storage Manager client software compression in

your environment to determine whether it is of use for you. In general, the

Tivoli Storage Manager client software compression improves performance only

when network throughput is quite small.

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

LANGUAGE AMENG (this is the default value)

NUMBERFormat 1 (this is the default value)

TAPEPROMPT NO

TIMEFORMAT 1 (this is the default value)

Note

When the Tivoli Storage Manager API client is installed on UNIX or Linux

systems, ensure that there is a softlink /usr/lib/libApiDS.<ext> pointing to

the libApiDS.<ext> file in the installation directory (/usr/tivoli/tsm/client/api/bin) of the Tivoli Storage Manager API. For the meaning of <ext>, see

Chapter 4, “Installing or Upgrading Data Protection for SAP,” on page 25.

Starting with Release 5 Version 3, Tivoli Storage Manager clients require an error

log. For each process, a single TSM error log can be specified, regardless of the

number of TSM server stanzas involved. The TSM error log is determined by the

following rules:

1. The TSM error log file is defined with keyword ERRORlogname in the client

system options file (dsm.sys): In the presence of a client user options file



(dsm.opt), the TSM error log is defined by the ERRORlogname specified in the

server stanza of dsm.sys of the server pointed to by dsm.opt. In the absence of

a client user options file (dsm.opt), the TSM error log is defined by the

ERRORlogname specified in the first server stanza in dsm.sys.

2. If there is no ERRORlogname defined in the appropriate stanza of dsm.sys the

TSM error log path is taken from environment variable DSMI_LOG.

3. If there is no error log file or path explicitly defined TSM errors are logged to

file dsierror.log in the local path.

Make sure that the error log specified can be opened for writing.

It is recommended to set up the Tivoli Storage Manager client so that different

processes write to separate error logs. Therefore, the error log path should be

defined in the environment (DSMI_LOG) if the client options files are shared

among processes.

Tivoli Storage Manager Clients on Windows Systems

The setup for the Tivoli Storage Manager client is effected in Windows

environments by changing the file <server_a>.opt (where server_a is the logical

server name in the initSID.utl file, see profile keyword SERVER on page 112).

Subsequently, the include/exclude file must be configured. It defines which files

the Tivoli Storage Manager backup/archive client will include or exclude for any

backup, archive or hierarchical storage procedure. Examples of an include/exclude

file for Windows can be found in “Sample TSM Profiles for Windows” on page

198.

The following serves as a quick guide for configuring the Tivoli Storage Manager.

It presents a typical list of actions that the Tivoli Storage Manager installer or

administrator must perform to prepare Tivoli Storage Manager for operation in an

SAP environment.

Follow these steps:

1. Install the Tivoli Storage Manager client software on the SAP database server

machine.

2. For each logical Tivoli Storage Manager server you need a corresponding client

option file. In the following example, the file name must be server_a.opt since

server_a is the logical server name:

TCPPort 1500

TCPServeraddress xxx.xxx.xxx.xxx

InclExcl c:\tivoli\tsm\baclient\inclexcl.list

Compression OFF

In addition, the environment variable DSMI_CONFIG must point to the

corresponding client options file, e.g., c:\tivoli\tsm\api\server_a.opt .

3. Specify TCPServeraddress 127.0.0.1 or loopback if the server and client are on

the same machine. This makes TCP/IP communication a little faster.

4. Specify InclExcl if you want Tivoli Storage Manager to include or exclude the

files listed in inclexcl.list. This is optional. You may want to exclude all

database files that are processed by the BR*Tools.

5. If you have tape drives with hardware compression attached to the Tivoli

Storage Manager server, you might get better throughput with the hardware



compression than you would with the Tivoli Storage Manager client software

compression (Compression ON). However, it is not recommended to combine the

various compression methods.

You will need to try Tivoli Storage Manager client software compression in

your environment to determine whether it is of use for you. In general, the

Tivoli Storage Manager client software compression improves performance only

when network throughput is quite small.

Starting with Release 5 Version 3, Tivoli Storage Manager clients require an error

log. For each process, a single TSM error log can be specified, regardless of the

number of TSM client option files <server>.opt involved. The TSM error log is

determined by the following rules:

1. The TSM Client log is written to the file specified in the environment

(DSMI_LOG).

2. If DSMI_LOG is absent or cannot be written to, the TSM Client log is written

to the file specified with keyword ERRORlogname in the client system options

file dsm.opt.

3. If there is no ERRORlogname in dsm.opt or if it cannot be written to, the TSM

Client log is written to file dsierror.log in the local path.

It is recommended to set up the Tivoli Storage Manager client so that different

processes write to separate error logs. Therefore, the error log path should be

defined in the environment (DSMI_LOG) if the client options files are shared

among processes.

Password Handling

For a discussion of the password handling methods, please see “Modifying the

Handling of the TSM Password” on page 48.

After selecting the suitable method, follow the steps in the appropriate

configuration matrix below to set the keywords and parameters in the various

profiles accordingly.



Password Configuration Matrix (UNIX or Linux)

After you have selected the suitable password handling alternative, follow the

configuration matrix to set the keywords/parameters in the different profiles

accordingly. Proceed as indicated by the step number.

Table 9. Password Handling for UNIX or Linux

Step Profile/Action Parameter Password

No Manual Set by Tivoli

Storage

Manager

1 Tivoli Storage

Manager admin

AUTHENTICATION

EXPIRATION PERIOD(see note 1)

OFF

n.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 Storage

Manager admin

UPDATE NODE

(see notes 1, 6)

n.a. <password> <password>

4 Tivoli Storage

Manager client

(root user)

SET PASSWORD

(see note 8)

n.a. n.a. <password>(see note 3)

5 DP for SAP profile

(init<SID>.utl)

For each SERVER statement

specify:PASSWORDREQUIRED

ADSMNODE

NO

<nodename>

YES

<nodename>

NO

(see note 4)

6 DP for SAP command

line


specify:backint -p init<SID>.utl -f

passwordSee: “Modifying the Handling of

the TSM Password” on page 48.

n.a.

<password>

(see notes 3,7)

<password>(see notes 3,7

7 DP for SAP with

Oracle RMAN

operation with user

other than DBA

permission on data files for

user:

ora<SID>other user

read, write

none

read, write

none

read, writeread, write

Notes:

1. See Tivoli Storage Manager documentation.

2. If you are using manual password generation during testing, make sure that

the expiration period is set to a sufficiently long time.

3. This password must be the one that is effective on the TSM server for the node.

4. ADSMNODE must not be set when PASSWORDACCESS generate is set.

5. The users <SID>adm and ora<SID> must have read and write permission for the

path specified in the PASSWORDDIR keyword in the Tivoli Storage Manager

client options file.

6. This step is only necessary if the password is expired (manual handling only)

or needs to be changed on the TSM server.

7. A password must be entered for each server statement in the DP for SAP

profile.

8. This step is necessary in case the Tivoli Storage Manager Backup Archive Client

is used to access data for the same node.



Password Configuration Matrix (Windows)

After you have selected the suitable password handling alternative, follow the

configuration matrix to set the keywords/parameters in the different profiles

accordingly. Proceed as indicated by the step number.

Table 10. Password Handling for Windows

Step Profile/Action Parameter Password

No Manual Set by Tivoli

Storage

Manager

1 Tivoli Storage

Manager admin

AUTHENTICATION

EXPIRATION 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 Storage

Manager client

SET PASSWORD n.a. n.a. <password>

(see note 3) n.a.

4 DP for SAP profile

init<SID>.utl


specify:

PASSWORDREQUIRED

ADSMNODE

NO<nodename>

YES<nodename>

NO

(see note 4)

5 DP for SAP command

line


specify:backint -p init<SID>.utl -f

passwordSee: “Modifying the Handling of

the TSM Password” on page 48.

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.

3. For an initial setup this password must be the same as was specified when

registering the node to Tivoli Storage Manager. The password must be changed

first on the Tivoli Storage Manager server and then in the DP for SAP product.

4. ADSMNODE must not be set when PASSWORDACCESS generate is set.

5. The users <SID>adm and sapservice<SID> must have read and write permission

for the path specified in the PASSWORDDIR keyword in the Tivoli Storage

Manager client options file.

6. This step is only necessary if the password is expired (manual handling only)

or needs to be changed on the TSM server.

7. A password must be entered for each server statement in the DP for SAP

profile.

8. This step is necessary in case the Tivoli Storage Manager Backup Archive Client

is used to access data for the same node.



Appendix I. Backup Scheduling Examples

UNIX or Linux Crontab Example

UNIX or Linux cron jobs can be scheduled with the crontab command, which

invokes an editing session that allows you to create a crontab file. The cron jobs

and the appropriate times are defined within the crontab. The crontab can be

customized with the command:

crontab -e

For example, you want a cron job to start a shell script backup.ksh (the content of

backup.ksh can be found in Appendix I, “Backup Scheduling Examples”) from

Monday through Friday at 11:30 p.m. which will use the SAP database utility

BRBACKUP to save the SAP database. In this case, the entry in the crontab to start

the script will be as follows:

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

Elements of Backup Schedules for UNIX or Linux

Under UNIX or Linux , crontab starts jobs (cron.job) at predefined times. In the

example below crontab starts two shell scripts backup.ksh and archive.ksh, which

simply use the SAP tools BRBACKUP and BRARCHIVE to save the data.

Crontab File Sample

# --------------------------------------------------------------------------

# crontab.sample:

# Sample crontab file to be included in the root crontab jobs.

# --------------------------------------------------------------------------

# Task:

# Submits backup/archive commands at regularly scheduled intervals

# using two simple shell scripts containing SAP backup/archive commands.

# --------------------------------------------------------------------------

# ***** NOTE ***** NOTE ***** NOTE *****

#

# This file is intended only as a model and should be


#

# ***** 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 ’C11’ and the username ’oraC11’.

#

# --------------------------------------------------------------------------

# Full database backup, scheduled every Friday at 8:00 p.m.

#

0 20 * * 5 /usr/bin/su - oraC11 -c "/oracle/C11/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 - oraC11 -c "/oracle/C11/sapscripts/backup/archive.ksh"

Full Offline Backup Shell Script Sample

#!/bin/ksh

# --------------------------------------------------------------------------

# backup.ksh:

# Sample BRBACKUP shell script

# --------------------------------------------------------------------------

# Task:

# Invokes the SAP utility brbackup in order to perform a full offline

# backup of all tablespaces using Data Protection for SAP (R) technology.

# --------------------------------------------------------------------------

# ***** NOTE ***** NOTE ***** NOTE *****

#

# This script is intended only as a model and should be


#

# ***** NOTE ***** NOTE ***** NOTE *****

# --------------------------------------------------------------------------

#

# For the following examples, the system id of the ORACLE database

# is assumed to be ’C11’.

#

# --------------------------------------------------------------------------

#

# First, lets do a full offline backup of the ORACLE database. This includes

# at least files located in the following filesystems:

# /oracle/C11/sapdata0





#

# Remarks on the parameters:

#

# -u system/manager Oracle username/password

# -c run brbackup in quiet mode

# -m all backup all tablespaces

# -t offline perform backup offline

#

# The following should be configured within the SAP profile initC11.sap:

#

# backup_dev_type = util_file

# causes brbackup to use the external program backint

# util_par_file = initC11.utl

# Data Protection for SAP 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 utility brarchive in order to save ORACLE’s archived

# redo logs (using Data Protection for SAP (R) ) and deletes the redo

# logs from their original location. After completing this, the brarchive

# protocol is saved separately.

# --------------------------------------------------------------------------

# ***** NOTE ***** NOTE ***** NOTE *****

#

Backup Scheduling Examples


# This script is intended only as a model and should be


#

# ***** NOTE ***** NOTE ***** NOTE *****

# --------------------------------------------------------------------------

#

# Remarks on the parameters:

#

# -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 profile initC11.sap:

#

# backup_dev_type = util_file

# causes brbackup to use the external program backint

# util_par_file = initC11.utl

# Data Protection for SAP profile

#

# --------------------------------COMMAND-----------------------------------

brarchive -u system/manager -c -sd

Windows Scheduling Example

To start automated backup jobs on Windows systems, the schedule service must be

running. You can start this service with the command:

net start schedule

If the schedule service is running, jobs can be scheduled with the at command

which can be used to invoke the batch file backup.cmd (the content of backup.cmd

can be found in “Elements of Backup Schedules for Windows”). If you want to run

this every Friday at 8:00 p.m., the following command must be invoked:

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

Elements of Backup Schedules for Windows

Schedule Batch Sample

@echo off

rem ------------------------------------------------------------------------

rem file name: schedule.sample

rem ------------------------------------------------------------------------

rem Task:

rem Submits backup/archive commands at regularly scheduled intervals

rem using two simple batch files containing SAP backup/archive commands.

rem ------------------------------------------------------------------------

rem ***** NOTE ***** NOTE ***** NOTE *****

rem

rem This file is intended only as a model and should be

rem carefully tailored to the needs of the specific site.

rem


rem ------------------------------------------------------------------------

rem For a full reference of the AT command please see the Windows NT

rem help.

rem ------------------------------------------------------------------------

rem

rem For the following examples, the system ID of the ORACLE database

rem is assumed to be "C21".

rem

rem ------------------------------------------------------------------------

rem Full database backup, scheduled every Friday at 8:00 p.m.

rem


Appendix I. Backup Scheduling Examples 193

at 20:00 /every:f cmd /c c:\oracle\C21\sapscripts\backup\backup.cmd

rem

rem ------------------------------------------------------------------------

rem Save redo logs, scheduled twice a day at 11:30 a.m. and at 5:30 p.m.

rem Monday through Friday

rem

at 11:30 /every:m,t,w,th,f cmd /c c:\oracle\C21\sapscripts\backup\archive.cmd

rem --------------------- end of schedule.sample ------------------------

Full Offline Backup Batch File Sample

@echo off

rem Full Offline Backup batch file:

rem ------------------------------------------------------------------------

rem file name: backup.cmd

rem ------------------------------------------------------------------------

rem Sample BRBACKUP batch file

rem ------------------------------------------------------------------------

rem Task:

rem Invokes the SAP utility BRBACKUP in order to perform a full offline

rem backup of all tablespaces using Data Protection for SAP (R)

rem ------------------------------------------------------------------------


rem

rem This script is intended only as a model and should be


rem


rem ------------------------------------------------------------------------

rem

rem For the following examples, the system ID of the ORACLE database

rem is assumed to be "C21".

rem

rem ------------------------------------------------------------------------

rem

rem First, let’s do a full offline backup of the ORACLE database. This

rem includes at least files located in the following file systems:

rem c:\oracle\C21\sapdata0





rem

rem Remarks on the parameters of BRBACKUP:

rem

rem -u system/manager ORACLE username/password

rem -c run BRBACKUP in quiet mode

rem -m all backup all tablespaces

rem -t offline perform backup offline

rem

rem The following should be configured within the SAP profile

rem initC21.sap:

rem

rem backup_dev_type = util_file

rem causes BRBACKUP to use the external program

rem Data Protection for SAP (R)

rem util_par_file = %ORACLE_HOME%\database\initC21.utl

rem Data Protection for SAP (R) profile

rem ------------------------------COMMAND-----------------------------------

brbackup -u system/manager -c -m all -t offline



Save and Delete Redo Logs Batch File Sample

@echo off

rem ------------------------------------------------------------------------

rem file name: archive.cmd

rem ------------------------------------------------------------------------

rem Sample BRArchive batch file

rem ------------------------------------------------------------------------

rem Task:

rem Invokes the SAP utility BRArchive in order to save ORACLE’s archived

rem redo logs (using Data Protection for SAP (R) ) and deletes the redo

rem logs from their original location. After completing this, the BRArchive

rem protocol is saved separately.

rem ------------------------------------------------------------------------


rem

rem This script is intended only as a model and should be


rem


rem ------------------------------------------------------------------------

rem

rem Remarks on the parameters of BRArchive:

rem

rem -u system/manager ORACLE username/password

rem -sd save and delete archived redo logs

rem -c run BRArchive in quiet mode

rem (-n number of redo logs to be saved,

rem default is 10000,

rem which means all available)

rem

rem The following should be configured within the SAP profile

rem initC21.sap:

rem

rem backup_dev_type = util_file

rem causes BRBACKUP to use the external program

rem Data Protection for SAP (R)

rem util_par_file = %ORACLE_HOME%\database\initC21.utl

rem Data Protection for SAP (R) profile

rem ------------------------------COMMAND-----------------------------------

brarchive -u system/manager -sd -c


Appendix I. Backup Scheduling Examples 195

Appendix J. Sample Tivoli Storage Manager Profiles

Sample TSM Profiles for UNIX or Linux

Client User Options File Sample (dsm.opt)

************************************************************************

* IBM Tivoli Storage Manager *

* *

* Sample Client User Options file for Unix platforms *

************************************************************************

SErvername server_a

Tapeprompt No

DOM /usr/sap /sapmnt/C11 /usr/sap/trans /oracle/C11

Client System Options File Sample (dsm.sys)

************************************************************************

* IBM Tivoli Storage Manager *

* *

* Sample Client System Options file for Unix platforms *

************************************************************************

SErvername server_a

COMMmethod TCPip

TCPPort 1500

TCPServeraddress your_ITSM_server_1

TCPBuffsize 32

TCPWindowsize 24

Compression Off

InclExcl /usr/lpp/adsm/bin/inclexcl.list

SErvername server_b

COMMmethod TCPip

TCPPort 1500

TCPServeraddress your_ITSM_server_2

TCPBuffsize 32

TCPWindowsize 24

Compression Off

InclExcl /usr/lpp/adsm/bin/inclexcl.list

Include/Exclude List Sample

* --------------------------------------------------------------------------

* inclexcl.list:

* Sample include/exclude list

* --------------------------------------------------------------------------

* Task:

* Include/Exclude list of files and directories for TSM incremental backups

* --------------------------------------------------------------------------

* ***** NOTE ***** NOTE ***** NOTE *****

*

* This file is intended only as a model and should be

* carefully tailored to the needs of the specific site.

*

* ***** NOTE ***** NOTE ***** NOTE *****

* --------------------------------------------------------------------------

*

* For all AIX systems

*

exclude /unix

exclude /.../core

exclude /u/.../.*sh_history

exclude /home/.../.*sh_history

*

* Note: It is recommended to perform system backups on a regular


* basis (e.g. using ’smit mksysb’). Consequently, you can exclude

* at least the following directories (which make up about 30 MB).

*

exclude /usr/games/.../*

exclude /usr/bin/.../*

exclude /usr/lbin/.../*

exclude /usr/mbin/.../*

exclude /usr/sbin/.../*

* --------------------------------------------------------------------------

*

* For those using AFS, exclude the cache filesystem or file

*

* exclude /usr/vice/cache/*

* exclude /var/vice/cache/*

* or

* exclude /afscfs

* --------------------------------------------------------------------------

*

* This stuff is either not worthwhile to be included or should be backed up

* using SAP’s BR*Tools 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 DP for SAP (R), this means including:

* /sapmnt/C11 > 270 MB

* /usr/sap > 14 MB

* /oracle/stage > 89 MB

* /oracle/C11 > 90 MB

* and OS related > 220 MB

* --------------------------------------------------------------------------

Sample TSM Profiles for Windows

Client User Options File Sample (dsm.opt)

The Tivoli Storage Manager client programs require a file dsm.opt containing

standard client user options. The full file name is set in the environment variable

DSM_CONFIG. This file is not provided with the installation.

*************************************************************************

*

* DSM.OPT (for Data Protection for SAP (R) )

*

* Data Protection for SAP (R) 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 SAP (R) 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 SAP requires for each Tivoli Storage Manager server a

corresponding client option file <server>.opt. All these files must reside in one

Sample Tivoli Storage Manager Profiles


directory, and this directory must contain a file dsm.opt whose full file name is set

in the environment variable DSMI_CONFIG. The contents of this (second) dsm.opt

file is ignored by DP for SAP.

*************************************************************************

*

* SERVER.OPT

*

* Data Protection for SAP (R) obtains the necessary information about

* a Tivoli Storage Manager server ’server’ from a client option file

* called ’<server>.opt’. For each Tivoli Storage Manager server a

* corresponding client option file is required.

*

* Note: This file contains the client options for the Tivoli Storage Manager

* server called ’server_a’.

*

* Please see the Tivoli Storage Manager documentation for details.

*

*************************************************************************

COMMmethod TCPIP

SLOWINCR NO

COMPression OFF

*NODEname C21

TCPPort 1500

TCPServeraddress xxx.xxx.xxx.xxx

PASSWORDACCESS PROMPT

TCPBUFFSIZE 31

TCPWINDOWSIZE 32

Include/Exclude List Sample

This sample include/exclude list is intended for the standard client user option

file. The idea is to exclude files from ordinary Tivoli Storage Manager incremental

backups that are easy to restore or that are already saved by DP for SAP. 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 SAP (R) 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 SAP (R).

*

*************************************************************************

Exclude *:\...\*.swp

Exclude *:\...\*.obj

Exclude *:\...\*.csm

Exclude *:\...\*.dsk

Exclude *:\...\*.bak

Exclude *:\...\win386.swp

Exclude *:\...\386spart.par

Exclude *:\...\pagefile.sys

Exclude *:\...\*.par

Exclude *:\...\SYSTEM32\CONFIG\*.*

Exclude *:\...\SYSTEM32\CONFIG\...\*

Exclude *:\IBMBIO.COM

Exclude *:\IBMDOS.COM

*

*Exclude the following ORACLE database files:


Appendix J. Sample Tivoli Storage Manager Profiles 199

*

Exclude *:\oracle\C21\saparch\...\*

Exclude *:\oracle\C21\sapbackup\...\*

Exclude *:\oracle\C21\sapreorg\...\*

Exclude *:\oracle\C21\sapdata*\...\*



Appendix K. Hints and Tips for BR*Tools

The BR*Tools are a collection of utilities to simplify the administration of an Oracle

database system within an SAP environment. For details on setting up and using

the BR*Tools, refer to the SAP documentation, for example the current SAP

Database Guide: Oracle.

Hints and Tips for BRARCHIVE

Cooperation of Data Protection for SAP with BRARCHIVE

BRARCHIVE is a utility within BR*Tools called to backup redo logs. To save each

redo log to Tivoli Storage Manager, BRARCHIVE calls Data Protection for SAP

either via the BACKINT interface or via RMAN.

BRARCHIVE keeps a list of redo logs to be saved. Redo logs that were successfully

saved by Data Protection for SAP may be deleted from the file system immediately

by BRARCHIVE. However, BRARCHIVE deletes redo log files only in the order of

the list. As a consequence, if the requested number of backup copies cannot be

saved for a redo log, this and all later redo logs are kept. When BRARCHIVE is

started again, these redo logs will be saved again even if some were successfully

saved earlier.

Data Protection for SAP informs BRARCHIVE on the redo logs that were saved

successfully to TSM. If a problem occurs Data Protection for SAP retries several

times saving the redo log in question. When a redo log cannot be saved to the

number of copies requested Data Protection for SAP terminates with an error. Data

Protection for SAP does not try to save redo logs with a higher sequence number

because they will be saved in a later BRARCHIVE run anyway.

Multiple Redo Log Copies

Data Protection for SAP can save a number of copies of each redo log using

different management classes of the IBM Tivoli Storage Manager. By creating

multiple redo log copies on separate physical media, the administrator can restore

and recover a database even if a backup tape gets corrupted. The following

keywords listed in the Data Protection for SAP profile are relevant in this context:

v Keyword BRARCHIVEMGTCLASS denotes the IBM Tivoli Storage Manager

management classes to be used when saving redo logs. With the use of different

management classes, the backup media targets of redo logs can be separated

from the backup media targets of the database objects. Also, different redo log

copies can be saved to different backup media.

v With keyword REDOLOG_COPIES, the administrator can initiate the creation of

multiple backup copies of each redo log. By creating multiple copies on separate

physical media, the database administrator is able to restore and recover an

Oracle database in an SAP environment even if a backup tape gets corrupted or

lost.

v Keyword MAX_SESSIONS denotes the maximum number of sessions to IBM

Tivoli Storage Manager a single instance of Data Protection for SAP may open.

Data Protection for SAP satisfies a request to back up redo log files according to

the following rules:


v Data Protection for SAP creates as many backup copies of each redo log as are

specified for keyword REDOLOG_COPIES.

v Data Protection for SAP requires that there are as many archive management

classes defined (keyword BRARCHIVEMGTCLASS) as there are redo log copies

requested. For maximum safety, it is crucial that the different management

classes are linked to different storage pools within TSM so that the various redo

log copies will end up on different backup media.

v Data Protection for SAP requires that the maximum number of sessions

(keyword MAX_SESSIONS) is greater than or equal to the number of redo log

copies requested if RMAN is employed. Although possible, a setup with a

smaller number of sessions is not recommended with the BACKINT interface

either.

v Data Protection for SAP is a client to IBM Tivoli Storage Manager and cannot

control in what order TSM will process the requests. Therefore, an administrator

cannot rely on sessions to be processed in the order they were started in by Data

Protection for SAP.

Managing TSM Sessions

If redo logs are saved directly to a tape pool the number of TSM sessions

established must not exceed the number of tape drives available. Otherwise,

intermittent BRARCHIVE and BRBACKUP problems and performance degradation

might occur due to numerous tape mounts and media waits. Administrators

should also consider that BRARCHIVE may process redo logs while a database

backup is running, or several BRARCHIVE processes may run at the same time,

with their combined sessions then easily exceeding the number of tape drives

available.

Therefore, it is recommended to save redo logs to disk storage pools and

eventually have TSM migrate them to tape.

Versioning

If Data Protection for SAP versioning is active (keyword MAX_VERSIONS)

versioning information is kept in the configuration file init<SID>.bki. The version

number is increased only after successful backups. Therefore, using the same

configuration file init.bki for both backing up the database (BRBACKUP) and the

redo logs (BRARCHIVE) is crucial to avoiding the unexpected loss of redo log

backups.

Messages

During BR*Tools processing, logs containing all issued messages are written to

paths /oracle/<SID>/sapbackup (for BRBACKUP) or /oracle/<SID>/saparch (for

BRARCHIVE). The prefixes of the messages logged indicate the issuing

components. For an explanation of the various messages, refer to the

documentation of the issuing component. When employing BR*Tools with Data

Protection for SAP, the following prefixes can be expected:

Table 11. Prefixes when using BR*Tools

Prefix Issuing Component

ANS / ANR IBM Tivoli Storage Manager

BKI Data Protection for SAP

BR BR*Tools

ORA Oracle database kernel

RMAN Oracle Recovery Manager (RMAN)

Hints and Tips for BR*Tools



Appendix K. Hints and Tips for BR*Tools 203

Appendix L. Hints and Tips for Network Settings

Networks with Large Bandwidth-Delay Product

For networks with a large bandwidth-delay product, it is recommended to activate

the TCP enhancements specified in RFC1323.

For example, the network on an AIX machine can be configured with the no

command. This command sets or displays current network attributes in the kernel.

For details about the no command, see the man page of no of your operating

system.

The following table shows the network attributes with their recommended values:

Table 12. Tuning of Network Settings

Attributes Value Description

rfc1323 1 Enables TCP enhancements as specified by RFC

1323, TCP Extensions for High Performance. The

default is 0. A value of 1 specifies that all TCP

connections will attempt to negotiate the RFC

enhancements.

sb_max 131072 Specifies the maximum buffer size allowed for a

socket. The default is 65536 bytes. From the point of

view of performance recommendations, the sb_max

value should be twice the TCPWindowsize set within

the Tivoli Storage Manager configuration file

dsm.sys.

To set these values, the following commands should be invoked by the root user on

the appropriate machine.

no -o rfc1323=1

no -o sb_max=131072

Caution

The no command does not perform range checking. It therefore accepts all

values. If used incorrectly, the command can cause the system to become

inoperable.

Note

These changes will be lost at system reboot. To make changes permanent, edit

the /etc/rc.net file.


SP Switch (RISC 6000)

If an SP switch (RISC 6000) is used, the following two values should be set as

shown in the following table:

Table 13. Tuning of SP Switch Buffer Pools


rpoolsize 1048576 The receive pool is a buffer pool for incoming data.

The size for values is in bytes.

spoolsize 1048576 The send pool is a buffer for outgoing data. The size

for values is in bytes.

The buffer pool settings can be changed using the chgcss command. After the

changes, it is necessary to reboot the node.

Network Settings of the Tivoli Storage Manager

The performance adjustments on the Tivoli Storage Manager side can be done by

customizing the appropriate configuration files:

v On the server side, the server option file dsmserv.opt, and

v On the client side, the client option file dsm.sys ( UNIX and Linux systems) or

server.opt (Windows systems).

The following table shows the corresponding Tivoli Storage Manager configuration

file attributes with the recommended values.

Table 14. Tuning Tivoli Storage Manager Configuration File Attributes


TCPBuffsize 32 Specifies the size, in kilobytes, of the buffer used for

TCP/IP send requests. This option affects whether or

not Tivoli Storage Manager sends the data directly

from the session buffer or copies the data to the TCP

buffer. A 32K buffer size forces Tivoli Storage

Manager to copy data to its communication buffer

and flush the buffer when it fills.

TCPNODelay YES Specifies whether the server should send small

amounts of data or allow TCP/IP to buffer the data.

Disallowing buffering may improve throughput but

more packets will be sent over the network.

TCPWindowsize 640 (AIX)

63 (others)

Specifies the size, in kilobytes, which will be used

for the TCP/IP sliding window for the client node.

This is the size of the buffer used when sending or

receiving data. The range of values is 0 to 2048.

Additional information can be found at: http://www-306.ibm.com/software/tivoli/products/storage-mgr-erp/.

Hints and Tips for Network Settings




Appendix M. Internet Protocol Version 6 (IPv6) Support

For AIX and Linux as of V5.5, Data Protection for SAP and Data Protection for

Snapshot Devices support both IPv4 and IPv6 internal communication. The actual

communication to be used depends on the network settings of the adapters

employed. There is no option to enforce the use of a specific protocol other than by

network configuration.

Version 5.5 of Data Protection for SAP and Data Protection for Snapshot Devices

support IPv6 in that they will run in an IPv6 environment. They do not take

advantage of new IPv6 functionality, however.

A server (defined for the purposes of this discussion as any software that opens a

listening port) attempts to open 2 sockets, one handling IPv4 connection requests

and one IPv6 requests. Connections will be accepted from each socket that could

be established. The clients will attempt to connect to whatever addresses are

returned by the server until a request is successful.

The following profile parameters of Data Protection for SAP

v LOG_SERVER

v TCP_ADDRESS

and Data Protection for Snapshot Devices:

v ADMIN_ASSISTANT

v PRIMARY_COPYSERVICES_SERVERNAME

now accept IPv6 addresses. Also, the command line parameter for the

Administration Assistant is IPv6-compatible. It can be specified in either of the

forms:

v <IPv4 address>:<service or port>

v <service or port>@<IPv6 address>

All interfaces containing hostnames, IP addresses, or port numbers support both

IPv4 and IPv6 address formats. This includes

v profile parameters

v command line options and arguments

v entries by the user during the installation and setup procedures

v output in the Administration Assistant windows

Note: The specification of IPv6 addresses assumes that Data Protection for SAP is

used in an environment in which IPv6 is supported by all hardware and

software components involved and has been adequately tested in this

environment.


|

|

|||||

|||

|||||

|

|

|

|

|

|

|||

|

|

||

|

|

|

|

|||||

Appendix N. Support Information

If you have a problem with your IBM software, you want to resolve it quickly. This

section describes the following options for obtaining support for IBM software

products:

v “Using IBM Support Assistant”

v “Obtaining Fixes”

v “Receiving Weekly Support Updates” on page 210

v “Contacting IBM Software Support” on page 211

Using IBM Support Assistant

The IBM Support Assistant is a free, stand-alone application that you can install on

any workstation. You can then enhance the application by installing

product-specific plug-in modules for the IBM products you use.

The IBM Support Assistant saves you time searching product, support, and

educational resources. The IBM Support Assistant helps you gather support

information when you need to open a problem management record (PMR), which

you can then use to track the problem.

The product-specific plug-in modules provide you with the following resources:

v Support links

v Education links

v Ability to submit problem management reports

For more information, see the IBM Support Assistant Web site at

http://www.ibm.com/software/support/isa/.

If your product does not use IBM Support Assistant, use the links to support topics

in your information center. In the navigation frame, check the links for resources

listed in the ibm.com® and related resources section where you can search the

following resources:

v Support and assistance (includes search capability of IBM technotes and IBM

downloads for interim fixes and workarounds)

v Training and certification

v IBM developerWorks®

v IBM Redbooks

v General product information

If you cannot find the solution to your problem in the information center, search

the following Internet resources for the latest information that might help you

resolve your problem:

v Forums and newsgroups

Obtaining Fixes

A product fix might be available to resolve your problem. To determine what fixes

are available for your IBM software product, follow these steps:


http://www-306.ibm.com/software/support/isa

1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.

2. Under Find product support, click All IBM software (A-Z). This opens the

software product list.

3. In the software product list, click on the product in question. This opens the

corresponding support site.

4. Under Solve a problem, click APARs to go to a list of fixes, fix packs, and

other service updates.

5. Click the name of a fix to read the description and optionally download the

fix. You can also search for a specific fix; for tips on refining your search, click

Search tips.

6. In the Find downloads and drivers by product section, select one software

category from the Category list.

7. Select one product from the Sub-category list.

8. Type more search terms in the Search within results if you want to refine

your search.

9. Click Search.

10. From the list of downloads returned by your search, click the name of a fix to

read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM

Software Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

Receiving Weekly Support Updates

To receive weekly e-mail notifications about fixes and other software support news,

follow these steps:

1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.

2. Click My support in the far upper-right corner of the page under

Personalized support.

3. If you have already registered for My support, sign in and skip to the next

step. If you have not registered, click register now. Complete the registration

form using your e-mail address as your IBM ID and click Submit.

4. Click Edit profile.

5. In the Products list, select Software. A second list is displayed.

6. In the second list, select a product segment, for example, Systems

management. A third list is displayed.

7. In the third list, select a product sub-segment, for example, Application

Performance & Availability. A list of applicable products is displayed.

8. Select the products for which you want to receive updates.

9. Click Add products.

10. After selecting all products that are of interest to you, click Subscribe to

e-mail on the Edit profile tab.

11. Select Please send these documents by weekly e-mail.

12. Update your e-mail address as needed.

13. In the Documents list, select Software.

14. Select the types of documents that you want to receive information about.

15. Click Update.

Support Information


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


http://techsupport.services.ibm.com/guides/handbook.html

http://techsupport.services.ibm.com/guides/handbook.html



If you experience problems with the My support feature, you can obtain help in

one of the following ways:

Online

Send an e-mail message to [email protected], describing your problem.

By phone

Call 1-800-IBM-4You (1-800-426-4968).

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM

software maintenance contract, and you must be authorized to submit problems to

IBM. The type of software maintenance contract that you need depends on the

type of product you have:

v For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as DB2 and WebSphere® products that

run on Windows, or UNIX operating systems), enroll in Passport Advantage in

one of the following ways:

Online

Go to the Passport Advantage Web site at http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm .

By phone

For the phone number to call in your country, go to the IBM Software

Support Web site at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

v For customers with Subscription and Support (S & S) contracts, go to the

Software Service Request Web site at https://techsupport.services.ibm.com/ssr/login.

v For customers with IBMLink™, CATIA, Linux, OS/390® , System i™ , System p™,

System z™ , and other support agreements, go to the IBM Support Line Web site

at http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

v For IBM Systems (formerly eServer™) software products (including, but not

limited to, DB2 and WebSphere products that run in System z, System p, and

System i environments), you can purchase a software maintenance agreement by

working directly with an IBM sales representative or an IBM Business Partner.

For more information about support for IBM Systems software products, go to

the IBM Technical Support Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call

1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to

the contacts page of the IBM Software Support Handbook on the Web at

http://techsupport.services.ibm.com/guides/contacts.html and click the name of

your geographic region for phone numbers of people who provide support for

your location.

To contact IBM Software support, follow these steps:

1. “Determining the Business Impact” on page 212

2. “Describing Problems and Gathering Information” on page 212

3. “Submitting Problems” on page 212

Support Information

Appendix N. Support Information 211

http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

http://techsupport.services.ibm.com/guides/contacts.html


https://techsupport.services.ibm.com/ssr/login

https://techsupport.services.ibm.com/ssr/login

http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006

http://www.ibm.com/servers/eserver/techsupport.html

http://www.ibm.com/servers/eserver/techsupport.html


Determining the Business Impact

When you report a problem to IBM, you are asked to supply a severity level.

Therefore, you need to understand and assess the business impact of the problem

that you are reporting. Use the following criteria:

Severity 1

The problem has a critical business impact. You are unable to use the

program, resulting in a critical impact on operations. This condition

requires an immediate solution.

Severity 2

The problem has a significant business impact. The program is usable, but

it is severely limited.

Severity 3

The problem has some business impact. The program is usable, but less

significant features (not critical to operations) are unavailable.

Severity 4

The problem has minimal business impact. The problem causes little impact

on operations, or a reasonable circumvention to the problem was

implemented.

Describing Problems and Gathering Information

When describing a problem to IBM, be as specific as possible. Include all relevant

background information so that IBM Software Support specialists can help you

solve the problem efficiently. To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can you re-create the problem? If so, what steps were performed to re-create the

problem?

v Did you make any changes to the system? For example, did you make changes

to the hardware, operating system, networking software, and so on.

v Are you currently using a workaround for the problem? If so, be prepared to

explain the workaround when you report the problem.

Submitting Problems

You can submit your problem to IBM Software Support in one of two ways:

Online

Click Submit and track problems on the IBM Software Support site

athttp://www.ibm.com/software/support/probsub.html. Type your

information into the appropriate problem submission form.

By phone

For the phone number to call in your country, go to the contacts page of

the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate

documentation, IBM Software Support creates an Authorized Program Analysis

Report (APAR). The APAR describes the problem in detail. Whenever possible,

IBM Software Support provides a workaround that you can implement until the

APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the

Support Information


http://www.ibm.com/software/support/probsub.html



Software Support Web site daily, so that other users who experience the same

problem can benefit from the same resolution.

Support Information

Appendix N. Support Information 213

Glossary

A

Activate policy set. In Tivoli Storage Manager, the

process of validating the contents of a policy set and

copying the policy set to the ACTIVE policy set.

Active policy set. In Tivoli Storage Manager, the

policy set that contains the policy rules currently in use

by all client nodes assigned to the policy domain. The

active policy set is the policy set that was most recently

activated for the policy domain.

Adaptive File Sequencing. During backup with the

file interface BACKINT, this feature of Data Protection

for SAP optimizes performance by calculating a certain

sequence of files to be backed up. This sequence

considers the file sizes to be backed up and the

distribution of files on several disks.

Administration Assistant. A Web-browser based

graphical interface to support and assist customizing of

Data Protection for SAP, simulating changes to the

configuration and infrastructure, and analyzing SAP

database backup and restore operations The

Administration Assistant consists of the Administration

Assistant server-level components (Server, Database

Agent, Database) and one or more instances of the

Administration Assistant client.

Administration Assistant client. Part of the

Administration Assistant; applet started in a Web

browser to access the Administration Assistant Server

component.

Administration Assistant Database Agent.

Administration Assistant server-level component

responsible for receiving data from Data Protection for

SAP and forwarding it to the Administration Assistant

Server component for display as well as to the

Administration Assistant Database component for

retention.

Administration Assistant Database component.

Administration Assistant server-level component

responsible for storing data received from DP for SAP

via the Database Agent in an internal Administration

Assistant database.

Administration Assistant scheduling client. Part of

the Administration Assistant creating reports from a

command-line interface using predefined templates.

Administration Assistant Server component. Part of

the Administration Assistant communicating with the

ProLE processes or services of various database servers.Administrators access the Server component via

Administration Assistant clients.

Administration Assistant Server component

configuration file. The file containing the

configuration of your Administration Assistant Server

component. The default file name of the server

configuration file is assist.cfg, located in the

installation path of the Administration Assistant Server

component.

Administrative client. In Tivoli Storage Manager, a

program that runs on a file server, workstation, or

mainframe that allows administrators to control and

monitor the Tivoli Storage Manager server through

administrator commands. Compare with

backup-archive client.

Apache Derby. An open-source database management

system developed by IBM and bundled with the

Administration Assistant. It is the default DBMS for the

internal Administration Assistant database.

API client. See Tivoli Storage Manager API.

Archive copy group. In Tivoli Storage Manager, a

policy object containing attributes that control the

generation, destination, and expiration of archive files.

An archive copy group belongs to a management class.

ARCHIVELOG mode. A database can run in

ARCHIVELOG mode or in NOARCHIVELOG mode.

Production systems must run in ARCHIVELOG mode

in order to allow proper backup restore. Test systems

can run in NOARCHIVELOG mode.

B

Backup-archive client. A component of Tivoli Storage

Manager running on a workstation or file server,

providing a means for backing up, archiving, restoring,

and retrieving files to or from the TSM server. Compare

with administrative client.

Backup copy group. A policy object containing

attributes that control the generation, destination, and

expiration of backup files. A backup copy group

belongs to a management class.

Backup Server. A Tivoli Storage Manager server

where DP for SAP sends the backup data to and

retrieves data when restoring.

Backup version control. A feature of Data Protection

for SAP allowing the customer to specify the number of

full database backups to be kept on the TSM server.

Obsolete database backups are deleted together with all

dependent data (for example log files, incremental

backups, etc.).


BRARCHIVE. An SAP database utility to perform

backups of offline redo log files in an SAP Oracle

database environment.

BRBACKUP. An SAP database utility to do

online/offline backups of SAP Oracle databases.

BRBACKUP can be used to back up data files, control

files and online redo log files.

BRCONNECT. This SAP database utility ensures, that

the database status required for the online/offline

backup of an SAP Oracle database remains unchanged

during the backup. BRCONNECT will be started

internally by BRBACKUP and BRARCHIVE.

BRRESTORE. An SAP database utility to restore an

entire Oracle database backup or parts of it, previously

backed up with BRBACKUP or BRARCHIVE. Any

non-database files and directories which were saved

can also be restored. Subdirectories within the sapdata

directories will be created automatically, when

necessary.

BR*Tools. Utilities provided by SAP to simplify the

administration of an Oracle database system within an

SAP environment.

C

Client options file. A configuration file of the TSM

client containing a set of processing options that

identify the server, communication method, and

options for backup, archive, hierarchical storage

management, and scheduling. Its default name is

dsm.opt on UNIX or Linux systems and

<servername>.opt on Windows.

Client system options file. A configuration file of the

TSM client residing on UNIX or Linux systems,

containing a set of processing options that identify the

Tivoli Storage Manager servers to be contacted for

services. This file also specifies communication

methods and options for backup, archive, hierarchical

storage management, and scheduling. Its name is

dsm.sys.

Cloning of a database. Restore a database to a

different location and changing the database alias or

SID while leaving the physical layout of the database

unchanged.

Control file. A file associated with a database that

maintains the physical structure and time stamps of all

files within that database. The control file is updated

continuously during database use and must be

available for writing, if the database is mounted or

opened.

Configuration File. See Data Protection for SAP

configuration file.See Administration Assistant server configuration file.

Copy group. A policy object of the TSM server

containing attributes that control the generation,

destination, and expiration of backup and archive files.

There are two kinds of copy groups: backup and

archive. Copy groups belong to management classes.

D

Database Agent. See Administration Assistant Database

Agent.

Database component. See Administration Assistant

Database component.

Database server. The server where the SAP database

resides. DP for SAP and the TSM API must be installed

on this server.

Data Protection for SAP configuration file. Binary

file containing persistent information used by Data

Protection for SAP, such as the TSM client password or

the current backup version number. Its default file

name is init.<SID>.bki.

Data Protection for SAP File Manager. A utility that

simplifies the DP for SAP inquire, restore and delete

operations. It can be seen as an add-on to DP for SAP.

Data Protection for SAP profile. ASCII file containing

option keywords for configuring Data Protection for

SAP. Its default file name is init.<SID>.utl.

Data block. The smallest unit of a database.

Data file. A physical operating system file on disk

containing data structures of a database, such as tables

and indexes. A data file belongs to a specific tablespace

in a database.

Device class. A named group of storage devices of a

TSM server with common characteristics. Each device

class has a unique name and represents a specific

device type such as disk, file, optical disk, or tape.

DISK. A device class that is defined by Tivoli Storage

Manager at installation. It is used to categorize disk

drives.

DP for SAP. An abbreviation for ’Data Protection for

SAP’, which is used in this document.

F

File Manager. See Data Protection for SAP File

Manager

File space. A logical space in a TSM server assigned to

a specific client. Clients can restore, retrieve, or delete

contents of their file spaces from Tivoli Storage

Manager server storage.Tivoli Storage Manager does not necessarily store all

Glossary


the files from a single file space together, but can

identify all the files in server storage that came from a

single file space.

I

Include/exclude list. A group of include and exclude

option statements in a file. Tivoli Storage Manager

backup-archive client uses the statements to determine

whether to back up or migrate certain files, and to

determine the associated management classes to use for

backup, archive, and space management. The exclude

options identify files that should not be backed up or

migrated off the client node. The include options

identify files that are exempt from the exclusion rules,

or assign a management class to a file or group of files

for backup, archive, or space management services. The

include/exclude list is defined either in an

include/exclude file (for UNIX or Linux clients) or in

the client options file (for other clients).

Incremental backup. An incremental backup saves

only those blocks within the database, which have been

changed since the last full backup. SAP R/3 release

4.5.A and later versions permit incremental backups of

Oracle databases using Oracle’s Recovery Manager

RMAN.

L

LAN-free backup. Backup to a backup server residing

on system different from that of the database server.

The database and backup servers are connected via

LAN. However, backup data is transferred directly to

the storage media via SAN.

Local backup. Backup to a local backup server.

Local backup server. Backup server residing on the

same system as the database server does.

M

Management class. Within IBM Tivoli Storage

Manager, a policy object that users can bind to a file in

order to specify how the server manages the file. The

management class can contain a backup copy group, an

archive copy group, and space management attributes.

The copy groups determine how the Tivoli Storage

Manager server manages backup versions or archive

copies of files. The space management attributes

determine whether files are eligible for migration from

space manager client nodes to Tivoli Storage Manager

storage, and under what conditions.

Media Management API. An interface provided by

Oracle to which vendors are able to write compatible

software libraries. This software integrates with Oracle.

Thus, an Oracle server process is able to issue

commands to the media manager to write backup files

out to sequential storage (e.g., Tivoli Storage Manager)

and read files from sequential storage.

N

Node.

1. TSM: A unique name used to identify a Tivoli

Storage Manager client to the TSM server.

2. SMP: Single machine in a Symmetrical

Multiprocessor (SMP) environment.

O

Offline redo log. If the database is in ARCHIVELOG

mode and an online redo log is filled, it is copied to

one (or more) archive log destination(s), which is

typically the saparch directory in an SAP environment.

This copy is the offline redo log (also called archived

redo log).

Online redo log. The online redo log is a set of two or

more files that record all changes made to Oracle data

files and control files.

P

Path. A connection between a Tivoli Storage Manager

node and a Tivoli Storage Manager server interface. On

the client side, a path is defined by a logical server

name listed in the client option file dsm.sys ( UNIX or

Linux systems) or <servername>.opt (Windows

systems). At the server side, the possible paths are

defined by the network addresses of the Tivoli Storage

Manager server.

Policy domain. Within Tivoli Storage Manager, a

policy object that contains policy sets, management

classes, and copy groups that are used by a group of

client nodes.

Policy set. Within Tivoli Storage Manager, a policy

object that contains a group of management class

definitions that exist for a policy domain. At any one

time there can be many policy sets within a policy

domain but only one policy set can be active.

ProLE. The background process (UNIX or Linux) or

service (Windows) controlling backup and restore

operations of DP for SAP.

R

Recovery Manager (RMAN). A tool used to back up,

restore and recover Oracle databases. It can be used

with or without a Recovery Catalog,. If a Recovery

Catalog is not used, Recovery Manager decides how to

back up, restore and recover the database using the

control file of the database. Incremental backups of

Oracle databases can only be done with RMAN.

Glossary

Glossary 217

Remote backup. Backup to a remote backup server.

Remote backup server. Backup server residing on a

system different from that of the database server.

Retention. The amount of time, in days, that inactive

files backed up or archived to a TSM server are kept by

the backup server before they are deleted. Copy group

attributes and default retention grace periods for the

domain define retention.

RMI. Remote Method Invocation (Java)

S

SAP BACKINT interface. An interface provided by

BR*Tools utilities that can be used to access external

backup programs, for example DP for SAP.

SAP Note. Document containing service information

provided by SAP. SAP Notes can be accessed (with an

SAP user ID and password) at the SAP Service

Marketplace:

http://service.sap.com/notes

Scheduling client. See Administration Assistant

scheduling client.

Scratch volume. A volume that is available for Tivoli

Storage Manager use. The volume is either labeled, or

blank or contains no valid data, and is not defined to

Tivoli Storage Manager.

Server configuration file. See Administration

Assistant Server component configuration file.

Session. Single TCP/IP connection between a Tivoli

Storage Manager node and a Tivoli Storage Manager

server. A TSM server may be configured to allow a

number of sessions from a TSM node to the server in

parallel over the same communication path.

Storage pool. A storage pool is a named collection of

storage volumes that are associated with one device

class. Each storage pool represents a collection of

volumes that are the same media type. For example, a

storage pool that is associated with a device class for

8 mm tape contains only 8 mm tape volumes.

T

Tablespace. A database is divided into one or more

logical storage units, which are tablespaces. Each

tablespace has a set of data files exclusively associated

with it.

Tivoli Storage Manager (TSM). IBM Tivoli Storage

manager, a client/server program that provides

policy-driven storage management to customers in a

multivendor computer environment.

Tivoli Storage Manager API. A set of functions that

applications running on a client platform can call to

store, query, and retrieve objects from Tivoli Storage

Manager storage.

U

util_file_online. A (data file) backup using an external

backup program addressed by the BACKINT interface.

If an online backup is running, the backup status is set

and completed dynamically for the tablespaces being

backed up. In this way, the volume of offline redo log

files during an online backup can be reduced

significantly.

V

Validate. In Tivoli Storage Manager, the process of

ensuring that the active policy set contains a default

management class and reports on copy group definition

errors.

Volume. The basic unit of storage for the Tivoli

Storage Manager database, recovery log, and storage

pools. A volume can be an LVM logical volume, a

standard file system file, a tape cartridge, or an optical

cartridge. Each volume is identified by a unique

volume identifier. See database volume, scratch

volume, and storage pool volume.

Glossary


Notices

References in this publication to IBM® products, programs, or services do not

imply that IBM intends to make these available in all countries in which IBM

operates. Any reference to an IBM product, program, or service is not intended to

state or imply that only that IBM product, program, or service may be used. Any

functionally equivalent product, program, or service that does not infringe any of

the intellectual property rights of IBM may be used instead of the IBM product,

program, or service. The evaluation and verification of operation in conjunction

with other products, except those expressly designated by IBM, are the

responsibility of the user.

IBM may have patents or pending patent applications covering subject matter in

this document. The furnishing of this document does not give you any license to

these patents. You can send license inquiries, in writing, to

IBM Director of Licensing

IBM Corporation

North Castle drive

Armonk, NY 10504-1785

U.S.A

Any references in this information to non-Tivoli or non-IBM Web sites are provided

for convenience only and do not in any manner serve as an endorsement of those

Web sites. The materials at those Web sites are not part of the materials for this

product and use of those Web sites is at your own risk.

If you are viewing this information in softcopy form, the photographs and color

illustrations may not appear.

Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange information between independently created programs

and other programs (including this one) and (ii) the mutual use of the information

which has been exchanged, should contact:

IBM Deutschland Informationssysteme GmbH

Department 0215

Pascalstr. 100

70569 Stuttgart

Germany

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

including in some cases payment of a fee.

Trademarks and Service Marks

The following terms are trademarks or registered trademarks of International

Business Machines Corporation in the United States or other countries or both:

v AFS

v AIX

v DB2

v developerWorks

v DS6000

v DS8000

v Enterprise Storage Server

v eServer


||||||||

v FlashCopy

v GPFS

v HACMP

v IBM

v ibm.com

v IBMLink

v Lotus

v OS/390

v Passport Advantage

v Rational

v Redbooks

v RS/6000

v SP

v System i

v System p

v System Storage

v System z

v Tivoli

v WebSphere

Adobe, the Adobe logo, PostScript, and the PostScript logo are trademarks or

registered trademarks of Adobe Systems, Incorporated, in the United States and/or

other countries.

Java and all Java-based trademarks and logos are trademarks or registered

trademarks of Sun Microsystems, Inc., in the United States, other countries, or

both.

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

countries.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft, Windows, Windows NT, the Windows logo, and Windows 2000 are

trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks

of others.

Accessibility

Accessibility features help users with physical disabilities, such as restricted

mobility or limited vision, to use software products successfully. Depending on the

operating system and its environment, such users can:

v use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen. Consult the product

documentation of the assistive technology for details on using those technologies

with this product.

v operate specific or equivalent features using only the keyboard.

v magnify what is displayed on the screen.

The product documentation includes features to aid accessibility:

v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader software.


|||||||||||||||||||

|||

v All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Navigating the Interface Using the Keyboard

Standard shortcut and accelerator keys are used by the product and are

documented by the operating system. Refer to the documentation provided by

your operating system for more information.

Magnifying What is Displayed on the Screen

You can enlarge information on the product windows using facilities provided by

the operating system on which the product is run. For example, in some

environments you can lower the resolution of the screen to enlarge the font sizes of

the text on the screen. Refer to the documentation provided by your operating

system for more information.

Notices 221

Index

Aaccessibility 220

activate policy set 183, 184

glossary definition 215

active policy setglossary definition 215

Adaptive Computing Environment 163

Adaptive File Sequencing 18


Administration Assistant 20, 63

adjusting 46

administer users 63

administering userids 76

authorizing users 76

concepts 64

configuration tool 64

configure systems 63

configuring 76

customizing 64

Database Agent 64

Database component 64


installation planning sheets 168

installing 67

Java 67

manage report templates 63

migration 74

migration of data 75

monitor operations 63

operations monitoring 64

overview 63

problem support 63

reference material 173

secure communication 77

Server component 64

simulate backup/restore 63

starting and stopping 73

threshold definitions 78

upgrading 74

view performance data 63

Web browser, remote method

invocation 67

Administration Assistant clientglossary definition 215

Java 67

prerequisites 67

setting up 71

verifying the installation 72

Administration Assistant databasechanging password for 78

Administration Assistant scheduling cientcommand line interface 66

Administration Assistant scheduling

clientglossary definition 215

prerequisites 68

setting up 73

Administration Assistant Scheduling

Clientcreating reports from 99

Administration Assistant Serverglossary definition 215

specifying 47

Administration Assistant Server

componentsecure connection to clients 71


component configuration file 66, 72, 77


Configuration Fileglossary definition 215

Administration Assistant server-level

componentsinitial installation 68

installation planning 68

installing 68

post installation process 71

prerequisites 67

uninstalling 71

upgrade installation 68


administrative client 12


ADSMBUFFSIZE 105

ADSMNODE profile keyword 106

alternate / parallel backup paths 18

alternate path 19

alternate/parallel backup pathsexample for availability 177

example for performance 179

reasons to use 175

alternate/parallel backup servers 19

example 3 for disaster recovery 180

Apache Derbyfor Administration Assistant

database 65

API clientglossary definition 215

archive copy groupglossary definition 215

archivelog modeglossary definition 215

archivinginactive data 21

authorizing Administration Assistant

users 76

automating backup and archive

operations 11

automation optionsalternate network paths and

servers 19

backup version control 19

frontend/backend processing 20

messaging 20

multiple redo log copies 19

selectable management classes 19

availability improvementswith alternate/parallel paths and

servers 19, 175

with multiple redo log copies 19

BBACKAGENT 105

backend processing 20

BACKEND profile keyword 106

BACKINTinteraction with DP for SAP 3

troubleshooting 153

backupautomated 11, 12

incremental 4, 8, 10, 13, 18

of AIX system data 7

of Oracle database elements 7

of SAP system data 10

operation reporting 94

parallel 18

path 18

performance optimization 39

multiplexing 42

profile and protocol file directories,

UNIX or Linux 10

profile and protocol file directories,

Windows 10

profiles 9

protocols 9

simulating 89, 108, 115

status reporting 93, 94

strategy for operating system 7

tape usage 17

terminating 176

user data 10

version control 19, 49, 111, 184

backup copy groupglossary definition 215

backup pathsalternate/parallel 18

profile examples 175

backup resultsapplying to restore 91

backup schedulerIBM Tivoli Workload scheduler 12

SAP scheduler 11

Tivoli Storage Manager scheduler 12

UNIX or Linux crontab / Windows

scheduler 11

UNIX or Linux sample 191

Windows sample 193

backup serveralternate/parallel 19



profile examples 175

backup statusmonitoring 20

backup strategydefining 7

for operating system 7

for Oracle database 7

for Protocols and Profiles 9

for SAP System data 10

planning 7

Sample 12


backup version controlglossary definition 215

backup_dev_type 33

backup_type 33

backup-archive client 8, 10, 11, 13, 15


BACKUPIDPREFIX profile keyword 106

balancing your system 83

BATCH profile keyword 106

BR*Tools 3, 15


protocols 9

BRARCHIVE 15, 43, 202


Hints and Tips 201

BRARCHIVEMGTCLASS 201

BRARCHIVEMGTCLASS profile

keyword 19, 106

BRBACKUP 15, 202


BRBACKUPMGTCLASS profile

keyword 19, 107

BRCONNECTglossary definition 216

BRRECOVER 15

BRRESTORE 15


BUFFCOPY profile keyword 107

buffer copies 46

buffer size 46

BUFFSIZE profile keyword 107

Cclient options file 32, 187, 189, 190, 198


client system options fileglossary definition 216

UNIX and Linux example 197

Windows example 198

client user options fileUNIX and Linux example 197

client/server connection paths 175

cloningredirected restore 57

SAP system 59

cloning of SAP system (example) 59

collocation 17, 43

CommonStore 21

COMPR_INFO profile keyword 108

compression 19, 40

null block 45

Tivoli Storage Manager 45

when restoring 92

CONFIG_FILE profile keyword 108

configurationoptimization 83

configuration filesglossary definition 216

configuration matrix for Tivoli Storage

Manager password settings 189, 190

control filebacking up 7


copy group 111, 183, 184


crontabfile example 191

scheduling backups with 11

custom SQL file 79

custom SQL file (sample) 174

customer supportSee Software Support

customizationAdministration Assistant 64

Ddata block


data compressionand overall throughput 86

hardware vs. software 186, 187

null block 45

Tivoli Storage Manager 45

data fileglossary definition 216

data filesbacking up 7

backup of 9

Data Protection for SAPinstallation planning sheets 167

Data Protection for SAP configuration fileglossary definition 216

Data Protection for SAP file managerglossary definition 216

Data Protection for SAP installation

packages 26

Data Protection for SAP profile 105


keyword reference 105

UNIX or Linux sample 115

Data Protection for Snapshot Devices 21

data spacesbacking up 7

data throughput 83, 85

actual rate 90

Database Agentglossary definition 216

Database Serverglossary definition 216


DB2for Administration Assistant

database 65

DB2 CommonStore for SAP 21

deletetroubleshooting 161

Derbyfor Administration Assistant

database 65

device class 41, 109, 182, 183


disability 220

disaster recoveryexample 3 for disaster recovery 180

with alternate/parallel paths and

servers 175

diskglossary definition 216

layout 40

disk I/Oactual rate 89

disk sorting 45

manual 18

DISKBUFFSIZE 105

distributed file system 163

with RMAN 164

DP for SAParchitecture and properties 15

BACKINT 15

backup library 15

components 15

console installation 35

database utilities 15


installing 25

integration with Administration

Assistant 16

integration with SAP 16

introduction 15

messages 125

migration 34

Oracle recovery manager 15

overview 15

profilekeyword descriptions 105

keyword rules 105

Windows sample 119

profilesUNIX or Linux sample 115

reporting 93

scope 15

upgrading 25, 34

DP for SAP installation package 26

drill-down 91

EEND profile keyword 108

Enterprise Storage Server 21

error messages 126

DP for SAP 125

examplesalternate/parallel paths for

availability 177

alternate/parallel paths for disaster

recovery 180

alternate/parallel paths for increased

performance 179

client system options file (UNIX and

Linux) 197

client system options file

(Windows) 198

client user options file (UNIX) 197

client user options file

(Windows) 198

crontab file 191

full offline batch backup

(Windows) 194

include/exclude list (UNIX and

Linux) 197

include/exclude list (Windows) 199

offline backup shell script 192

saving and deleting redo logs (UNIX

or Linux) 192

saving and deleting redo logs

(Windows) 195

scheduled batch backup

(Windows) 193


examples (continued)scheduling backup jobs (UNIX or

Linux) 191

scheduling backup jobs

(Windows) 193

Tivoli Storage Manager profiles for

UNIX and Linux 197

Tivoli Storage Manager profiles for

Windows 198

EXITONERROR profile keyword 108

FFCS_FILE profile keyword 108

File Manager 55

function keys 56

inquire, restore, delete functions 55

troubleshooting 162

file sequencing 18

File spaceglossary definition 216

FILE_RETRIES profile keyword 108

filesbackup 10

log 10

profile and protocol file

directories 10

protocol 10

fixes, obtaining 209

FlashCopy and snapshotsbackup 21

devices 21

restore 21

frontend processing 20

FRONTEND profile keyword 109

full offline batch backupWindows example 194

HHACMP 50, 51

adding DP for SAP 52

installing and setup 51

sample stop script 53

hardware compression 186, 187

compared with Tivoli Storage

Manager client software

compression 186, 187

high availability 50

Hints and TipsBRARCHIVE 201

IIBM support assistant, support assistant,

problem resolution, IBM Redbooks,

education, software support,

support 209

inactive dataarchiving of 21

include/exclude list 10


UNIX and Linux example 197

Windows example 199

incremental backup 4, 18


incremental backup function of Tivoli

Storage Manager 10

individual tablespace locking 19

Init<SID>.sap 152

Init<SID>.utl 152

inquire functionBR*Tools 161

BRRESTORE 161

installation package 26

installingAdministration Assistant 67

Administration Assistant client,

prerequisites 67

Administration Assistant server-level

components 68

Administration Assistant server,

prerequisites 67

Administration Assistant, installation

verification 72

HACMP 51

installing DP for SAP 25, 26

firewall installation 36

initial installation 26

migration 26

on AIX, HP-UX, Linux, Solaris 27

on Windows 29

password handling 32

planning for installation 26

planning sheet 167

post installation steps 32

prerequisites 25

silent installation 35

TSM Option file 32

upgrade installation (migration) 26


integration of Data Protection for SAPwith Administration Assistant 16

with SAP 16

IPv6 207

JJava

prerequisite for Administration

Assistant dlient 67


Assistant server 67

Kkeyboard 220

keywordsADSMNODE 106

BACKEND 106

BACKUPIDPREFIX 106

BATCH 106

BRARCHIVEMGTCLASS 19, 106

BRBACKUPMGTCLASS 19, 107

BUFFCOPY 107

BUFFSIZE 46, 107

COMPR_INFO 108

CONFIG_FILE 108

END 108

EXITONERROR 108

FCS_FILE 108

FILE_RETRIES 108

keywords (continued)FRONTEND 109

LOG_SERVER 109

MAX_ARCH_SESSIONS 110

MAX_BACK_SESSIONS 110

MAX_CONTROL_SESSIONS 110

MAX_RESTORE_SESSIONS 110

MAX_SESSIONS 109

MAX_VERSIONS 110

MULTIPLEXING 42, 111

obsolete 105

PASSWORDREQUIRED 111

REDOLOG_COPIES 112

REPORT 112

RL_COMPRESSION 45, 112

SERVER 112

SESSIONS 113

SORT_FILE 113

syntax for all keywords 105

TCP_ADDRESS 114

TRACE 114

TRACEFILE 114

TRACEMAX 114

USE_AT 114

LLAN-free backup 40



Local backupglossary definition 217

local backup serverglossary definition 217

lockingindividual tablespace 19

log fileslocation 153

LOG_SERVER profile keyword 109

loggingmessages 20

Mmanagement classes 19


Tivoli Storage Manager server

configuration 183

manual sorting of files 18

MAX_ARCH_SESSIONS profile

keyword 110

MAX_BACK_SESSIONS profile

keyword 110

MAX_CONTROL_SESSIONS profile

keyword 110

MAX_RESTORE_SESSIONS profile

keyword 110

MAX_SESSIONS 201

MAX_SESSIONS profile keyword 109

MAX_VERSIONS 202

MAX_VERSIONS profile keyword 110

media management APIglossary definition 217

messages 126

logging of 20

severity levels 126

Index 225

messages (continued)when using BR*Tools 202

migrationDP for SAP 34

of Administration Assistant 74

mirroring control and redo log files in

Oracle 8

monitoring DP for SAP 64

mount pointsmaximum number per node 185

node parameter maxnummp 185

multiple copies of redo logs 201

multiple network paths 44

multiple paths 206

multiple redo log copies 19, 201

multiple servers 44

when restoring 92

multiple sessions 18, 43

multiplexing 18, 40, 42

when restoring 92

MULTIPLEXING profile keyword 42,

111

Nnetwork

actual throughput rate 90

performance optimization 40, 205

settings 205

nodeglossary definition 217

maxnummp 185

number of mount points 184

Tivoli Storage Manager server 184

null block data compression 45

Ooffline backup shell script

example 192

offline log file 112

offline redo log 7, 9, 10


online redo log 7, 8, 9, 10


operating system backupstrategy 7

optimizingbackup 83

restore 91

Oracle data spacesbacking up 7

Oracle database serverconcepts 7

Pparallel backup and restore

number of parallel sessions to

specify 110

parallel backup pathssample 2 for increased

performance 179

parallel backup serversalternate 19

parallel path 18

parallel path (continued)example for increased

performance 179

parallel sessions 18, 206

partition 50, 108

password handlingautomatic generation 49

configuration matrix (UNIX or

Linux) 189

configuration matrix (Windows) 190

manual generation 48

no password usage 48

set the password 32

PASSWORDREQUIRED profile

keyword 111

pathalternate 19

backup 18


PERF_MONITOR 105

performance analysis 20

performance monitoring 83

Administration Assistant 64

using sensors 84

performance optimizationBackup Server 41

backup types 40

backup/restore 39

balanced configuration 88

by changing buffer size 46

by compressing data 19, 45

by disk sorting 18

by multiplexing 18, 42, 86

by setting up proper environment 42

by using multiple network paths 18,

44

example 2 179

by using multiple servers 18, 44

by using multiple sessions 18, 43

CPU power 40, 41

data transfer 41

dedicated backbone network 40

disk bottleneck 86

disk layout 40

general considerations 39

I/O paths 40

LAN-free backup 40

network bandwidth 40

network or TSM bottleneck 87

options for 18

settings for the Tivoli Storage

Manager 206

size of database 40

size of database files 40

tuning 42

volume manager 40

with alternate/parallel paths and

servers 175

permissionsgranting for Administration Assistant

client 67

platformdifferences xii

supported xii

policydefinition 183

domain 183

policy (continued)glossary definition 217

set 183

activate 183, 184


policy filegranting permissions for

Administration Assistant client 67

printing reports 20, 93

problem determinationdescribing problems 212

determining business impact 212

submitting problems 212

productivity optionsbackup status monitoring 20

performance analysis 20

reporting 20

tracing 20

profile keywordssyntax 105

profilesbackup of 9

backup, file directories, UNIX or

Linux 10

backup, file directories, Windows 10

example of Tivoli Storage Manager for

UNIX and Linux 197

Tivoli Storage Manager example for

Windows 198

ProLE 47, 151


protocolbackup of 9

backup, file directories, UNIX or

Linux 10

backup, file directories, Windows 10

RRecovery Manager (RMAN) 4


redo log copies 19

redo logs 12

backing up 7

backup of 9

multiple copies 19

saving and deleting 192, 195

UNIX or Linux example 192

Windows example 195

REDOLOG_COPIES 201

profile keyword 112

remote backupglossary definition 218

remote backup serverglossary definition 218

remote shares (Windows)implementing configuration files

on 31

REPORT profile keyword 112

reports 20

creating 98

modifying the output 100

on backup performance 95

on failed actions 95

on simulations 97

prerequisites for 97

types 93


reports (continued)UNIX scheduling sample 173

using templates 98, 99

using the Administration Assistant

Client 93, 98

Windows scheduling sample 173

restoreapplying backup results to 91

BRRESTORE 160


multiplexing 42

redirected 57

simulating 89

troubleshooting 160

retention 18, 21


RETRY 105

RISC 6000buffer pool settings 206

RL_COMPRESSION 19

RL_COMPRESSION profile keyword 45,

112

RMAN 4

and incremental backup 4

backup/restore simulation 92

interaction with DP for SAP 4

on UNIX or Linux 29

Hints 29

troubleshooting 155

with distributed file system 164

rman_parms 33

Ssample DP for SAP profile

UNIX or Linux 115

Windows 119

SAN File System 163

SAPconfiguration of TSM server 185

system cloning 59

SAP (backup) scheduler 11

SAP BACKINT interfaceglossary definition 218

SAP Noteglossary definition 218

SAP system cloning (example) 59

scheduled batch backupWindows example 193

schedulingautomatic backups 11

backup jobs 191, 193

function of Tivoli Storage

Manager 11

products 11

UNIX or Linux examples 191

Windows examples 193

scheduling clientcommand line interface 66

creating reports 99


prerequisites 68

setting up 73

scopeof DP for SAP 15

scratch volume 183


security settingsauthorizing Administration Assistant

users 76

serverinstalling Administration Assistant

components 68

server configuration fileglossary definition 218

SERVER profile keyword 112

serversalternate 19

alternate/parallel 18

sessionsglossary definition 218

multiple (parallel) 17, 18, 41, 42, 43,

45, 47, 85, 86, 87, 89, 90, 91, 109, 110,

112, 113, 175, 176, 178, 180

single 17, 91

SESSIONS profile keyword 113

setting Tivoli Storage Manager passwords

manually 48

setting up Tivoli Storage Manager 181

shortcut keys 220

SID 29, 31, 105, 106, 125, 153, 154, 155,

156, 157, 158, 159, 160, 167, 175, 176

simulatingbackup and restore 89

using COMPR_INFO 108

using USE_AT 115

simulationreporting on 97

snapshotdevices 21

software compression vs. hardware

compressionUNIX or Linux 186

Windows 187

Software Supportcontacting 211

describing problems 212

determining business impact 212

receiving weekly updates 210

submitting problems 212

SORT_FILE profile keyword 113

sortingfiles 18

SP Switchbuffer pool settings 206

specifying management classes 19

storage device setupTivoli Storage Manager server 182

storage pool 19, 43, 182, 183

definition 183


strategyplanning a backup strategy 7

support xiii, 209

system copyheterogeneous 59

homogeneous 59

Ttablespace 110


locking 19

tape drivesusing hardware compression

with 186, 187

tape usagefor backups 17

TCP_ADDRESS profile keyword 114

TCPWAIT 105

templatefor creating reports 99

terminating the backup job 176

threshold definitionsAdministration Assistant 78

via custom SQL file 79

Tivoli Storage Manageradjusting to DP for SAP 182

alternate network paths and

servers 47

backup scheduler 12

client software compression 187

configuration file customization 206

data compression 45

expiration function 111


incremental backup function 10

management classes 19

network settings 206

options files 32

passwords 48


profile example for UNIX and

Linux 197

profile example for Windows 198

scheduling function 11

sessions 202

setup 181

Tivoli Storage Manager APIclient configuration 26


Tivoli Storage Manager clientconfiguration 185

configuration on UNIX or Linux 185

configuration on Windows 187

software compression 186

Tivoli Storage Manager passwordsauthentication off 48

automatic generation 49

configuration matrix to set

keywords 189, 190

manual generation 48

Tivoli Storage Manager serveradding 47

configuration 181

configuration, prerequisites 182

management classes 183

node definition 184

performance considerations 181

policy definition 183

storage device setup 182

storage pool definition 183

storing data on 17

TRACE profile keyword 114

TRACEFILE profile keyword 114

TRACEMAX 105

TRACEMAX profile keyword 114

tracing 20

troubleshooting 151

BACKINT 153

Index 227

troubleshooting (continued)backup function 159

delete function 161

File Manager 162

IBM support 159

inquire function 161

installation 151

random problems 158

reproducible problems 158

restore function 160

RMAN 155

setup 151

using RMAN on Windows 31

TSM for Advanced Copy Services 21

TSM serverconfiguration for SAP 185

tuning 42

Uuninstalling DP for SAP

from UNIX and Linux 36

from Windows 36

UNIX or Linux crontab, backup

scheduler 11

upgradingDP for SAP 25, 26, 34

USE_AT profile keyword 114

user authorization for Administration

Assistant 76

useridsadministering 76

util_file_online 19, 33


util_par_file 33, 152

utilityFile Manager 55

Vvalidate


policy set 183, 184

verifyinginstallation of the Administration

Assistant 72

verifying the DP for SAP installation 33

versioning 202

volume 15, 19, 40, 182, 183, 218


manager settings 40

WWeb browser


Assistant 67

Windows, backup scheduler 11


��

Program Number: 5608–APR

Printed in USA

SC33-6340-09

Tivoli Storage Manager for Resource Planning - IBM ® Storage Manager for Enterprise Resource...

Documents

Transcript of Tivoli Storage Manager for Resource Planning - IBM ® Storage Manager for Enterprise Resource...