Data Protection for mysap.com Technology Installation & User s Guide for Oracle

Transcription

1 IBM Tioli Storage Manager for Enterprise Resource Planning (5698 APR) Data Protection for mysap.com Technology Installation & User s Guide for Oracle Version 3 Release SC

2

3 IBM Tioli Storage Manager for Enterprise Resource Planning (5698 APR) Data Protection for mysap.com Technology Installation & User s Guide for Oracle Version 3 Release SC

4 Note! Before using this information and the product it supports, be sure to read the general information under Notices on page xi. Fifth Edition (December 2003) This edition applies to Data Protection for mysap.com technology Version 3 Release 3 Modification Leel 10 (product number 5698 DPR), aailable as a licensed program product, and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications through your IBM representatie or the IBM branch office sering your area. Publications are not stocked at the addresses gien below. A form for readers comments is proided at the back of this publication. If the form has been remoed, address your comments to: IBM Deutschland Entwicklung GmbH Enterprise Solution Deelopment Dept. 3848, Bldg Schoenaicher Str Boeblingen Germany FAX (Germany): FAX (other countries): (+49) Internet Web page: Make sure to include the following in your comment or note: Title and order number of this book Page number or topic related to your comment When you send information to IBM, you grant IBM a non-exclusie right to use or distribute the information in any way it beliees appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1995, All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ii Tables ix Notices xi Trademarks and Serice Marks xi Naming Conentions used in this Documentation xii Preface xiii Who Should Read This Book xiii How to Read This Book xiii Where to Find More Information xiii Part 1. Data Protection Basics Chapter 1. Concepts of Data Protection for mysap.com Oracle Backup/Restore and Data Protection for mysap.com DP for mysap.com and BACKINT DP for mysap.com and RMAN Chapter 2. Deeloping a Backup Strategy Planning a Backup Strategy for the Operating System 5 Planning a Backup Strategy for Your Oracle Database 5 Planning a Backup Strategy for Backup Protocols and Profiles Planning a Backup Strategy for mysap.com System Data Part 2. Installing and Using Chapter 3. Introducing Data Protection for mysap.com Scope of Data Protection for mysap.com Integration of Data Protection for mysap.com with SAP Storing data on a TSM Serer Performance Options of Data Protection for mysap.com Parallel Sessions Multiplexing Disk Sorting Parallel Serer and Parallel Path Indiidual Tablespace Locking Incremental Backup RL Compression Automation Options of Data Protection for mysap.com Selectable Management Classes Retain Backups by Version Multiple Redo Log Copies Alternate Serer and Path Frontend/Backend Processing Reporting Message Logging Using FlashCopy to Minimize Backup and Restore Windows Integration with Data Protection for IBM Enterprise Storage Serer (ESS) for mysap.com.19 Archiing Inactie Data Chapter 4. Installing or Upgrading Data Protection for mysap.com Prerequisites for the Installation of Data Protection for mysap.com Installation Planning for Data Protection for mysap.com Installing Data Protection for mysap.com Initial Installation Upgrade Installation (Migration) Installing Data Protection for mysap.com on UNIX (AIX, Solaris, HP-UX, Linux) Installing Data Protection for mysap.com on Windows Post Installation Steps Reiew of the TSM Option File The Password Verifying the Installation Specifying an Administration Assistant Serer..28 Upgrading Data Protection for mysap.com (Migration) Special Installation Silent Installation Console Installation Firewall Installation Uninstalling Data Protection for mysap.com...30 Uninstalling Data Protection for mysap.com from UNIX (AIX, Solaris, HP-UX, Linux)...30 Uninstalling Data Protection for mysap.com from Windows Chapter 5. Adjusting your System Adjustments for Improing Performance of Data Transfer Restore Objecties General Aspects of Data Transfer Optimizing the mysap.com Database Serer (Production Serer) for Data Transfer Optimizing The Network Optimizing The Backup Serer (TSM Serer)..39 Optimizing the Settings for the Tioli Storage Manager Optimizing Your Enironment Adjustments for the Administration Assistant...41 Adjustments for High Aailability Copyright IBM Corp. 1995, 2003 iii

6 Considerations for Using IBM HACMP for AIX 42 Adjustments for Automation Password Adjustments Scheduling Automated Backup Runs Actions used for Adjusting your System Chapter 6. Using Data Protection for mysap.com with RMAN RMAN Setup on UNIX Systems RMAN Setup on Windows Systems Chapter 7. Using Data Protection with the File Manager Data Protection for mysap.com File Manager...59 Chapter 8. Using the Administration Assistant for Data Protection for mysap.com General Prerequisites Installation Installing the Administration Assistant Serer (Base Installation) Installing the Administration Assistant NLS Package (optional) Specifying a new Administration Assistant Serer for Data Protection for mysap.com Verifying the Installation Authorizing Administration Assistant Users...70 Using the Administration Assistant Uninstalling the Administration Assistant Chapter 9. Cloning the mysap.com System What is Cloning? mysap.com System Cloning Example Part 3. Appendixes Appendix A. Alternate/Parallel Backup Paths and Backup Serers Parameter Settings - SERVER Statement EXAMPLE 1: Use of Alternate/Parallel Paths for Increased Aailability EXAMPLE 2: Use of Alternate/Parallel Paths for Increased Performance EXAMPLE 3: Use of Alternate/Parallel Serers for Disaster Recoery Appendix B. The Data Protection for mysap.com Profile Keyword Reference Sample Data Protection for mysap.com Profile for UNIX Sample Data Protection for mysap.com Profile for Windows Appendix C. Preparing Tioli Storage Manager for DP for mysap.com Configuring the Tioli Storage Manager Serer..99 General Considerations for TSM Prerequisites Adjusting your TSM for DP for mysap.com Configuring of Tioli Storage Manager Clients General Considerations Tioli Storage Manager Clients on UNIX Systems Tioli Storage Manager Clients on Windows Systems Appendix D. Sample Tioli Storage Manager Profiles Sample TSM Profiles for UNIX Client User Options File Sample (dsm.opt) Client System Options File Sample (dsm.sys) 107 Include/Exclude List Sample Sample TSM Profiles for Windows Client User Options File Sample (dsm.opt) Client Options Files Sample (<serer>.opt) Include/Exclude List Sample Appendix E. Elements of Backup Schedules Elements of Backup Schedules for UNIX Crontab File Sample Full Offline Backup Shell Script Sample Sae and Delete Redo Logs Shell Script Sample 112 Elements of Backup Schedules for Windows Schedule Batch Sample Full Offline Backup Batch File Sample Sae and Delete Redo Logs Batch File Sample 114 Appendix F. Tips and Hints for SAP Backup Utilities Tips and Hints for BRARCHIVE Hints for BRARCHIVE Version 3.1G or Higher Examples Using MAX_SESSIONS and REDOLOG_COPIES mysap.com Backup and Recoery Scenarios Using Data Protection for mysap.com Backup Scenarios Restore/Recoery Scenario Appendix G. Troubleshooting Problem Resolution during Installation and Setup 131 Understanding The Setup Location of Log Files BACKINT Problem Resolution RMAN Problem Resolution Problem Resolution During Operation Reproducable (Repeatable) Problems Random problems Contacting Your IBM / Tioli Support Inoking Data Protection for mysap.com manually 139 Backup Function Restore Function i Data Protection for mysap.com Technology Installation & User s Guide for Oracle

7 Inquire Function Delete Function Appendix H. Data Protection for mysap.com Messages How To Find Message Files (Log Files) Data Protection for mysap.com Message Explanations Data Protection for mysap.com File Manager Error Messages Appendix I. Installation Planning Sheet Glossary Index Contents

8 i Data Protection for mysap.com Technology Installation & User s Guide for Oracle

9 Figures 1. DP for mysap.com with SAPDBA using the BACKINT Interface DP for mysap.com with SAPDBA using the RMAN Interface Backup Scenarios Within a mysap.com Oracle Enironment Scope of Data Protection for mysap.com Integration of Data Protection for mysap.com with SAP Data Throughput Simplified Data Transfer for a Backup / Restore Multiplexing Parallel Sessions Parallel Paths Parallel Serers Null Block compression Sample Enironment for HACMP Takeoer Production Backup Example File Manager Result of an Inquiry Procedure File Manager Result of an Inquiry Procedure Showing File Names Example of an mysap.com Landscape Administration Assistant Serer Setup (Base Installation) Specify Ports Administration Assistant Serer Setup (Base Installation): Correct Hostname Panel Administration Assistant Serer Setup Destination Directory Starting the Administration Assistant with Netscape Administration Assistant Start Panel SAP and Data Protection configuration files on UNIX Problem Isolation for Backint Problem Isolation for RMAN Copyright IBM Corp. 1995, 2003 ii

10 iii Data Protection for mysap.com Technology Installation & User s Guide for Oracle

11 Tables 1. SAP Backup Profile Parameter Combinations Tuning of Network Settings Tuning of SP Switch Buffer Pools Tuning Tioli Storage Manager Configuration File Attributes Password Handling for UNIX Password Handling for Windows Oeriew of Actions for Adjusting your System File Extensions for Shared Libraries SERVER Statement and Appropriate Profile and Option File Settings Copyright IBM Corp. 1995, 2003 ix

12 x Data Protection for mysap.com Technology Installation & User s Guide for Oracle

13 Notices References in this publication to IBM products, programs, or serices do not imply that IBM intends to make these aailable in all countries in which IBM operates. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any of the intellectual property rights of IBM may be used instead of the IBM product, program, or serice. The ealuation and erification of operation in conjunction with other products, except those expressly designated by IBM, are the responsibility of the user. IBM may hae patents or pending patent applications coering subject matter in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to IBM Director of Licensing IBM Corporation North Castle drie Armonk, NY U.S.A Any references in this information to non-tioli or non-ibm Web sites are proided for conenience only and do not in any manner sere 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 iewing this information in softcopy form, the photographs and color illustrations may not appear. Licensees of this program who wish to hae 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 Stuttgart Germany Such information may be aailable, subject to appropriate terms and conditions, including in some cases payment of a fee. Trademarks and Serice Marks The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both: AFS AIX IBM RS/6000 SP Tioli Copyright IBM Corp. 1995, 2003 xi

14 R/3 and mysap.com are registered trademarks of SAP AG in Germany, other countries, or both. Oracle is a registered trademark of Oracle Corporation. Solaris, Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Incorporated, in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Toralds and others. Microsoft, Windows, Windows NT, and Windows 2000 are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and serice names may be trademarks or serice marks of others. Naming Conentions used in this Documentation In this documentation, Data Protection for mysap.com technology is usually referred to as Data Protection for mysap.com or DP for mysap.com. The product IBM Tioli Storage Manager is usually referred to as Tioli Storage Manager or TSM. Note Unless otherwise stated, references in this publication to UNIX apply to all supported UNIX-based systems as well as to Linux, and references to Windows apply to all supported Windows platforms. xii Data Protection for mysap.com Technology Installation & User s Guide for Oracle

15 Preface Who Should Read This Book How to Read This Book This manual is intended for system programmers and administrators who are responsible for implementing a backup solution in a mysap.com enironment using the Tioli Storage Manager. It describes the procedures needed to install and customize Data Protection for mysap.com, the interface between mysap.com and the Tioli Storage Manager. The reader should be familiar with the documentation for mysap.com, Tioli Storage Manager and Oracle. The manual is split into three parts, of which the first is a general introduction into data protection, the second describes the architecture and properties of Data Protection for mysap.com and the third part (Appendix) gies samples and profiles. If you are a person experienced in data protection, you might want to skip part 1 and turn right away to Part 2. The information gien there is for system programmers and administrators who know how Data Protection for mysap.com is embedded in a comprehensie data protecting system. If you are a noice in data protection, 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 during a setup of a data protection system. Where to Find More Information For more information about Data Protection for mysap.com, refer to the Tioli Internet home page at Note: The most up-to-date ersion of this book is aailable in the Tioli Information Center at Copyright IBM Corp. 1995, 2003 xiii

16 xi Data Protection for mysap.com Technology Installation & User s Guide for Oracle

17 Part 1. Data Protection Basics Copyright IBM Corp. 1995,

18 2 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

19 Chapter 1. Concepts of Data Protection for mysap.com This chapter is meant for users who are new to Data Protection for mysap.com. If you are experienced in Data Protection for mysap.com, you might want to skip the following chapter. Oracle Backup/Restore and Data Protection for mysap.com The SAP database administration tools offer all the functions necessary to administer a database. The SAP DBA BRTOOLS for Oracle, (BRBACKUP, BRARCHIVE, BRRESTORE) proide for online or offline, partial or full backup of tablespaces (done by BRBACKUP), backup of archied redo log files (done by BRARCHIVE) and system guided restore/recoer capabilities (done by BRRESTORE and BRRECOVER). Oracle also proides its own administration utility RMAN (Recoery MANager) which is of specific alue when incremental backups are required. Data Protection for mysap.com is seamlessly integrated with the SAP BRTOOLS and Oracle s RMAN and is optimized to handle unattended, 24 hour, 7 days/week production backup/restore tasks. DP for mysap.com and BACKINT Figure 1 shows the interaction between the SAPDBA Utilities, DP for mysap.com and the BACKINT Interface in order to do backup / restores. Figure 1. DP for mysap.com with SAPDBA using the BACKINT Interface The mysap.com tools (SAPDBA Utilities) use tables in the Oracle database and system data in order to record the status of the data file backups and logfile backups. This information will allow mysap.com to restore automatically the correct data files and their specific database transaction log files (redo log files), if necessary. The data files reside in the Oracle database (Oracle Instance). Data Protection for mysap.com runs as a separate process independent of the database. It receies the data through the Backint interface and saes the data to the Tioli Storage Manager. A backup run will proceed as follows (see circled numbers): Copyright IBM Corp. 1995,

20 1. SAPDBA utility BRBACKUP informs Oracle what data has to be backed up and puts the database into the proper backup state ( online or offline ). 2. BRBACKUP calls DP for mysap.com ia the BACKINT interface with a list of all files to be backed up. 3. DP for mysap.com (ia BACKINT interface) backs up all requested files from the database and reports back to BRBACKUP. BRBACKUP thereby increases its data to include the files that were backed up. (data stream to file repository) 4. BACKINT saes the data to TSM. 5. SAPDBA updates the file repository, which holds information about the status of the files. DP for mysap.com and RMAN Figure 2 shows the interaction between the SAPDBA Utilities, DP for mysap.com and RMAN in order to do backup / restores. Figure 2. DP for mysap.com with SAPDBA using the RMAN Interface The mysap.com Tools (DBA Utilities) use tables in the Oracle database and system data in order to record the status of the data file backups and logfile backups. This information will allow mysap.com at a later time to restore automatically the correct data files and their specific database transaction log files. The data files reside in the Oracle database (Oracle Instance). Data Protection for mysap.com runs as a separate process independent of the database. It receies the data through the Backint interface and saes the data to the Tioli Storage Manager. A backup run will proceed as follows (see circled numbers): 1. SAPDBA utility BRBACKUP informs Oracle RMAN what data has to be backed up. The RMAN process puts the database into the proper backup state ( online or offline ). 2. The Oracle serer process loads DP for mysap.com and interacts with it through the Media Management API. 3. DP for mysap.com backs up all requested files from the database and reports back to BRBACKUP. BRBACKUP thereby increases its data to include the files that were backed up (data stream to file repository). 4. DP for mysap.com saes the data to a TSM serer. 5. SAPDBA updates the file repository, which holds information about the status of the files. RMAN has its own file repository, with a control file for a separate recoery catalog database. 4 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

21 Chapter 2. Deeloping a Backup Strategy This section describes how to define an appropriate backup strategy for your mysap.com system. It is intended as a supplement to your mysap.com, Oracle, and Tioli Storage Manager documentation. There are seeral requirements that your strategy must meet. The most important factors you need to consider include: The types of eents you wish to protect your mysap.com system against How quickly you need to be able to return to normal operation after a failure The interals and times of day during which backups can be performed The eents and points in time you need to be able to recoer, depending on the type of outage Data Protection for mysap.com lets you back up mysap.com database data using the SAP backup interface BACKINT directly to Tioli Storage Manager storage. Howeer, these backups, which use the SAP database utilities BRBACKUP and BRARCHIVE, are only backups of the database or the offline redo logs. Hence, to protect your complete system against failures affecting SAPDBA or other mysap.com system data, you should use standard Tioli Storage Manager commands or the Tioli Storage Manager graphical user interface (GUI) to additionally backup this system data. To be prepared for recoeries from a seere disaster, the procedures described below must become an integral part of your oerall disaster recoery plan. Planning a Backup Strategy for the Operating System In order to be protected against a complete loss of the operating system, it is imperatie that after: the installation of the operating system updates/upgrades of the operating system appropriate system backups are made with the operating system dependent utilities, e.g. mksysb for AIX. This will allow you to start your system from the backup medium. Base backups should include a configured TCP/IP enironment as well as the Tioli 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 recoer from: user errors statement failures transaction failures media failures Copyright IBM Corp. 1995,

22 that could affect your Oracle database, sae the following objects on a regular basis: Data files Control files Online redo logs Offline redo logs Files belonging to a specific tablespace (data files) are backed up by BRBACKUP. This is done at the file leel, where offline or online backups are possible. The control file is saed by BRBACKUP wheneer a tablespace backup occurs. Online redo logs are saed by BRBACKUP wheneer a full offline database backup occurs. Note Oracle proides mirroring of the control and online redo log files to protect the running database system against corruption of these actie files. (The AIX LVM facilities can also be used to mirror these files.) Offline redo logs are saed by BRARCHIVE. You can specify that the redo logs are to be deleted from their original location when BRARCHIVE completes successfully. Additional information on BRARCHIVE operations can be found in Appendix F, Tips and Hints for SAP Backup Utilities, on page 117. Apart from backing up all database releant data (data files, control file, online redo log files, and offline redo log files) it is also recommended that you back up SAP system data Oracle system data Operating system data This data should be backed up with the incremental backup function of the Tioli Storage Manager backup/archie client. Figure 3 on page 7 shows the arious backup scenarios within a mysap.com database serer machine. 6 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

23 Figure 3. Backup Scenarios Within a mysap.com Oracle Enironment The database itself is backed up with Data Protection for mysap.com, whereas the SAP, Oracle and operating system protocols are backed up directly by the Tioli Storage Manager. Planning a Backup Strategy for Backup Protocols and Profiles Eery BRBACKUP and BRARCHIVE run is diided into two parts. The first part backs up objects such as: mysap.com data files database control files online redo log files offline redo log files depending on the action started (see preious section). The second part of a BRBACKUP or BRARCHIVE is responsible for backing up the following profiles: init<sid>.dba (SAPDBA profile) init<sid>.ora (Oracle profile) init<sid>.sap (SAP backup profile) init<sid>.utl (Data Protection for mysap.com profile) and the protocol files back<sid>.log (BRBACKUP summary log) arch<sid>.log (BRARCHIVE summary log) detailed BRBACKUP/BRARCHIVE log reorg<sid>.log (main SAPDBA log) struct<sid>.log (structure log) Chapter 2. Deeloping a Backup Strategy 7

24 These profiles and protocols are used by the SAP database utilities wheneer backups or restores/recoeries are required. Unless you use an additional security method, for example an additional file system backup, these profiles or protocol files can only be restored in combination with Data Protection for mysap.com. For this purpose, you can, for example, use the Data Protection for mysap.com File Manager (see Data Protection for mysap.com File Manager on page 59). In the case of a recoery scenario after a disaster, it may be time consuming to restore the backup protocols or profiles by means of Data Protection for mysap.com or the Data Protection for mysap.com 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 /oracle/<sid>/sapreorg /oracle/<sid>/sapbackup /oracle/<sid>/saparch /oracle/<sid>/dbs (SAPDBA and structure logs) (BRBACKUP logs) (BRARCHIVE logs) (profiles) Windows <drie>:\oracle\<sid>\sapreorg <drie>:\oracle\<sid>\sapbackup <drie>:\oracle\<sid>\saparch <drie>:\orant\database (SAPDBA and structure logs) (BRBACKUP logs) (BRARCHIVE logs) (profiles) Planning a Backup Strategy for mysap.com System Data In addition to the backup operations performed with BRBACKUP and BRARCHIVE, you may want to protect your system against the loss of mysap.com system data, user data, or een operating system data that is not stored with BRBACKUP or BRARCHIVE. You can use the incremental backup capabilities of the Tioli Storage Manager backup/archie client to do this. The Tioli Storage Manager incremental backup function lets you define an include/exclude list of files that is applied automatically during incremental backup operations. This include/exclude list should be used to exclude data already stored using Data Protection for mysap.com. This would be all database releant data, such as data files, the control file, and online/offline redo logs. For further information about include/exclude lists, see your Tioli Storage Manager manuals, Using the Backup-Archie Clients. Examples of include/exclude lists for UNIX can be found in Sample TSM Profiles for UNIX on page 107 and for Windows in Sample TSM Profiles for Windows on page 108. Sample files can be found in your DP for mysap.com installation package. 8 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

25 The information saed with the BRBACKUP and BRARCHIVE utilities is usually located in the following file systems or directories: UNIX /oracle/<sid>/saparch/ /oracle/<sid>/sapdata1/ /oracle/<sid>/sapdata2/ /oracle/<sid>/sapdata3/ /oracle/<sid>/sapdata4/ /oracle/<sid>/sapdata5/ /oracle/<sid>/sapdata6/... /oracle/<sid>/origloga/ /oracle/<sid>/origlogb/ Windows <drie>:\oracle\<sid>\saparch\ <drie>:\oracle\<sid>\sapdata1\ <drie>:\oracle\<sid>\sapdata2\ <drie>:\oracle\<sid>\sapdata3\ <drie>:\oracle\<sid>\sapdata4\ <drie>:\oracle\<sid>\sapdata5\ <drie>:\oracle\<sid>\sapdata6\... <drie>:\oracle\<sid>\origloga\ <drie>:\oracle\<sid>\origlogb\ Add these directories to the list of paths to be excluded in the include/exclude list of your Tioli Storage Manager backup/archie client. This will preent you from saing the database data twice. Chapter 2. Deeloping a Backup Strategy 9

26 10 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

27 Part 2. Installing and Using Copyright IBM Corp. 1995,

28 12 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

29 Chapter 3. Introducing Data Protection for mysap.com Data Protection for mysap.com together with TSM proides a reliable, high performance and production oriented backup and restore solution that allows you to backup and restore your Oracle based mysap.com systems. It is integrated with SAP s backup and recoery utilities BRRECOVER, SAPDBA, BRBACKUP, BRARCHIVE, and BRRESTORE, and allows you to follow SAP s backup and recoery procedures. Being specifically optimized for mysap.com databases, Data Protection for mysap.com allows you to manage large olumes of data most efficiently. This chapter gies you an oeriew of the enironment and functions of Data Protection for mysap.com. It is not the intent of this chapter to explain how to use the SAP utilities. Although the usage of the SAP utilities is sketched in Appendix F, Tips and Hints for SAP Backup Utilities, on page 117, we recommend to read the SAP manuals for BRRECOVER and SAPDBA. Installation and configuration of Data Protection for mysap.com is coered extensiely later in this document (see Chapter 4, Installing or Upgrading Data Protection for mysap.com, on page 21 and Chapter 5, Adjusting your System, on page 31). Copyright IBM Corp. 1995,

30 Scope of Data Protection for mysap.com Figure 4. Scope of Data Protection for mysap.com The SAP utilities for backup and recoery of a mysap.com Oracle databases are focused on the content of the database, where oer 90 % of the data reside. Thus Data Protection for mysap.com will be used for backup and restore of data files, control files, and online and offline redo logs (See Figure 4). Other files such as SAP and Oracle executables can be backed up using the Tioli Storage Manager Backup Archie Client. As a consequence - in case of a disaster recoery - you hae to make sure that all Oracle and SAP executables are aailable before starting restore and recoery of your database using the SAP utilities. Integration of Data Protection for mysap.com with SAP Figure 5 on page 15 shows that once being configured Data Protection for mysap.com operates as an inisible connection between the mysap.com Database Administration Tools and Tioli Storage Manager. It proides you with two different adapters supporting different backup and recoery scenarios: 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. a shared library that is dynamically linked by Oracle s RMAN (an executable installed during the Oracle database installation). If a backup is performed using this library SAP does not communicate with Data Protection for mysap.com directly. It communicates through Oracle s RMAN process instead. When using RMAN and this shared library you can perform incremental database backups. You can configure SAP such that it uses only backint but you can neer configure it to use only RMAN: backint is always used for the backup of control and redo log files. Both adapters - backint and the media management library for Oracle - share a configuration file init<sid>.utl, which describes how to perform backups and 14 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

31 restores, and which can be used to customize Data Protection for mysap.com to your enironment and according to your needs. Both adapters communicate with the TSM Serer through an API that is shared with other IBM Tioli Data Protection products, and both require that ProLE - a background process that is part of the Data Protection for mysap.com package - is running. Figure 5. Integration of Data Protection for mysap.com with SAP Storing data on a TSM Serer The Data Protection for mysap.com package contains an additional (optional) component - the Administration Assistant - aimed at increasing the administrator s productiity. The functionality coers configuring a DP for mysap instance, data transfer performance monitoring and monitoring of success and failure of backup/restore operations. It allows you to monitor and administer all of your Data Protection for mysap.com instances remotely ia an applet running in a web browser. To register an SAP instance to the Administration Assistant Serer simply add the location of the Administration Assistant to the command line arguments of ProLE. DP mysap.com transfers data to/from the TSM serer in one or multiple (parallel) sessions to a TSM serer. Each session must hae a storage deice associated with it. DP mysap.com uses the Archie/Retriee functions in order to backup/restore data to/from TSM. Thus the SAP backup ID can be persistently linked to each backup file ia a file descriptor aailable with the Archie function. This backup ID is ery important, as it is later used by SAP s restore utility to determine all files required for a complete restore. Note: In SAP terminology backup (BRBackup) means backup of data files, archie (BRArchie) means backup of archied redo log files. DP for mysap.com for both backup types uses the TSM Archie function. Chapter 3. Introducing Data Protection for mysap.com 15

32 It is highly recommended to use tape storage for the datafiles of a database, as this has consistently proen to proide 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 redo log file right after it is placed into the archie 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 deactiate collocation for backups with DP for mysap.com in order to enable parallel sessions use multiple tape dries in parallel. Collocation deactiated is also necessary to use the multiple log copy function, see Multiple Redo Log Copies on page 18. Views of backups on the TSM Serer can be generated by the SAP administration tools either by using their own local (detailed) backup log or by inquiring the TSM serer through DP for mysap.com. Manual access to the backup repository is proided through a specific File Manager -backfm - shipped with DP for mysap.com. It allows the administrator to bypass the SAP tools to inquire, delete and restore backups / files. Note: DP for mysap.com can be configured to use multiple TSM serers to improe either aailability (alternate serers) or performance (multiple serers). DP for mysap.com accesses only those serers defined in its profile when inquiring for the backup repository. Therefore care has to be taken when remoing TSM serers from the DP for mysap.com profile while they still hold alid backup data. Database backups are usually kept for a specified time until they become unnecessary. 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: by setting the archie retention period or by using the DP for mysap.com ersioning function, see below, which will delete whole backup generations (full backups plus related redo log backups) when the specified number of ersions is exceeded. Note: Since the SAP backup log cannot be updated by DP for mysap.com, it may still contain old backups although they are already deleted (expired). Performance Options of Data Protection for mysap.com To achiee good data transfer rates for backup and restore you hae to make sure that the following three components all hae good data transfer rates: the disks on which the database is located, the network between the database host and the TSM Serer, and the backup storage deice containing the backup. Keep in mind that the weakest of these components constrains your backup/restore performance and thus appears as a bottleneck. Data Protection for mysap.com offers a ariety of options to optimize the data transfer rate for each of these components (see Appendix B, The Data Protection for mysap.com Profile, on page 81 for a detailed explanation of these parameters and their relationship to the arious bottlenecks). 16 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

33 Parallel Sessions Data Protection for mysap.com allows you to backup or restore data to multiple tape dries in parallel. Parallelism is achieed by using more than one session to send data to a TSM Serer (MAXSESSIONS). For details see the profile keyword on page 85. 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 dries often hae 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 oerall backup and restore performance. For more information see on page 86. Disk Sorting Data Protection for mysap.com deploys Adaptie File Sequencing to minimize the backup window. It sorts database files in order to aoid simultaneous reading of files located on the same disk. Note: Some storage subsystems hide the information required by file sorting. In order to still proide this sorting function, you can supply the file location information manually by specifying a manual sort file (SORT_FILE). For more information see on page 88. Example: With MULTIPLEXING set to 5 and MAXSESSIONS set to 3 you would be able to backup 15 files simultaneously to 3 different tapes. Due to disk sorting these files are chosen such that they are located on separate disks, wheneer this is possible. Parallel Serer and Parallel Path You can configure Data Protection for mysap.com to distribute a backup of a database across two or more TSM Serers. Similarly, by proiding two or more separate network connections between the SAP database host and the TSM Serer, you can configure Data Protection for mysap.com to balance network traffic across all aailable network connections to the TSM Serer. Indiidual Tablespace Locking To minimize the amount of archied redo logs during online backup operations, Data Protection for mysap.com can notify the SAP database utilities for which tablespaces it is going to back up files. The SAP utilities then switch those tablespaces into backup mode. After the files are backed up, the tablespaces are released again and a new cycle starts. This mode (util_file_online) is set with a parameter in the SAPDBA profile setup. For more information see on page 27. Incremental Backup Data Protection for mysap.com supports incremental RMAN-backup of an SAP database. An incremental backup saes only those database blocks that hae been changed since the last full backup. Depending on the system enironment, this may result in decreased backup times. Chapter 3. Introducing Data Protection for mysap.com 17

34 RL Compression RL Compression is a fast and ery effectie 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 on page 37. Automation Options of Data Protection for mysap.com Data Protection for mysap.com comes with a ariety of options that help improe your administratie productiity: Selectable Management Classes You can specify different TSM management classes for backing up and archiing data. It is a best practice to configure Data Protection for mysap.com to backup directly into a tape storage pool and to archie into a disk storage pool. In addition multiple management classes hae to be used in conjunction with multiple redo log copies. For information how to specify management classes, see the profile keywords BRARCHIVEMGTCLASS and BRBACKUPMGTCLASS on pages 82 and following pages. Retain Backups by Version This function enables you to limit the number of full backups kept on the TSM Serer. If you hae more than MAX_VERSIONS of full backups on a TSM Serer the oldest ersions are deleted. This function keeps track of all redo log files, control files, partial backups and incremental backups that depend on a full backup: All these files and the full backup are deleted at the same time. Multiple Redo Log Copies As protection against tape defects and to improe aailability and disaster recoery, you can backup multiple copies of a log file and configure your system such that these copies are located on different physical Tioli Storage Manager olumes or een different TSM Serers. If at restore time one log file copy is unaailable Data Protection for mysap.com 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 on page 87 and Appendix F, Tips and Hints for SAP Backup Utilities, on page 117. Alternate Serer and Path Similar to Parallel Serer and Parallel Path you can configure Data Protection for mysap.com to use multiple TSM Serers or multiple network connections to one TSM Serer alternately to improe aailability of backup storage. In such a configuration Data Protection for mysap.com checks all serers and network connections for aailability and allows you to perform your backups een if some resources are currently unaailable. In conjunction with the parameter USE_AT you can establish policies to use different TSM Serers at different days of the week. For more information see on pages 88 and 90 Frontend/Backend Processing Data Protection for mysap.com 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 82 and Data Protection for mysap.com Technology Installation & User s Guide for Oracle

35 Reporting Data Protection for mysap.com can be configured to produce a report at the end of a backup. This report proides statistical information such as the number of bytes that are transferred through the network and the effectie data throughput. During a backup or restore it calculates and displays an estimated end time of the operation. By using the Administration Assistant contained in the Data Protection for mysap.com package you are proided with detailed performance reports, that help you optimizing your systems. In addition you can retriee backup status informations such as success or failure of a backup across all of your SAP instances. For more information see on page 87 Message Logging You can establish policies that force Data Protection for mysap.com to send different classes of log messages to a TSM Serer or to SNMP traps Using FlashCopy to Minimize Backup and Restore Windows Integration with Data Protection for IBM Enterprise Storage Serer (ESS) for mysap.com Although Data Protection for mysap.com proides extensie methods to optimize your data throughput, your serice leel agreements for business-critical databases might demand een faster recoery operations. Data Protection for mysap.com together with the companion product Data Protection for ESS for mysap.com allow you to perform FlashCopy backups and FlashBack restores if you are running your SAP database on an ESS. Using these features you can keep your production downtime at a minimum by exploiting the FlashCopy capability of the IBM Enterprise Storage Serer. Archiing Inactie Data The SAP tools with DP for mysap.com are designed for operational backups, i.e. a database image is stored on a bit leel. This method is NOT at all recommended for true, long-term archiing. Outdated backups need to be restored into exactly the same enironment they were initially taken from in order to access the data from within SAP applications. This would require keeping old ersions of SAP, OS, database and TSM to rebuild this enironment and cannot be iewed as a reliable process. SAP, instead, proides special archiing 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. Archied data can then be remoed from the operational database to trim its size and, as a result, reduce the backup / restore windows. SAP offers a different interface ArchieLink for data and document archiing. Another IBM product CommonStore connects this ArchieLink interface to TSM as the external archie for - inactie data (data retention) - printlists (e.g. reports, Note: some reports can be used for data retention) - outgoing documents (e.g. printed output like inoices, bills) - incoming documents (e.g. digitized fax, scanned letters, audio) Chapter 3. Introducing Data Protection for mysap.com 19

36 - local documents (e.g. text, spreadsheets, pictures, graphics) - inactie data Thus TSM can be used as an integrated repository for backups and for archied information. 20 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

37 Chapter 4. Installing or Upgrading Data Protection for mysap.com Data Protection for mysap.com must be installed on any system that is to be used as mysap.com database serer. In order to set up Data Protection for mysap.com, do the following: 1. Check if the DP for mysap.com package is complete. The package includes this manual and machine readable material on a CD-ROM. See the Readme file for: A table of contents of the package Up-to-date news 2. Make sure that the requirements are met. For details, see Prerequisites for the Installation of Data Protection for mysap.com below. 3. Get planning information. For details, see Installation Planning for Data Protection for mysap.com on page Install Data Protection for mysap.com. For details, see Installing Data Protection for mysap.com on page Perform Post Installation steps as described in Post Installation Steps on page Verify the installation. For details, see Verifying the Installation on page 27. UNIX and Windows systems Data Protection for mysap.com can be installed and operated for mysap.com systems with Oracle databases employing a standard file system or raw logical olumes. There are only small differences between the UNIX and Windows ersions of Data Protection for mysap.com. One of these differences is that UNIX uses the path separator / compared with \ for Windows and that the drie letter is specified for Windows. Non-triial differences between the UNIX and Windows ersions of Data Protection for mysap.com will be mentioned explicitly. Prerequisites for the Installation of Data Protection for mysap.com The following products must be installed before you can start setting up Data Protection for mysap.com: Oracle Database SAP R/3 or mysap.com e-business Solution, based on Oracle Tioli Storage Manager (TSM) Make sure to hae it properly set up for the use with Data Protection for mysap.com (see Appendix C, Preparing Tioli Storage Manager for DP for mysap.com, on page 99). TSM Client UNIX or Windows Operating System at the leel supported by mysap.com and the Tioli Storage Manager client Copyright IBM Corp. 1995,

38 For Hardware and Software Prerequisites as well as product ersions supported and maintenance leels required by the current ersion of Data Protection for mysap.com, refer to the Release Notice (RELNOTE). For information on the functions, product ersions, and maintenance leels that are compatible with your ersion of SAP R/3 or mysap.com, consult SAP support, for example ia the Online Serice System (OSS). The appropriate modules can be downloaded from the SAP serer. Information about this can be found in OSS note For information on the installation and configuration of the Tioli Storage Manager API client, refer to Appendix C, Preparing Tioli Storage Manager for DP for mysap.com, on page 99. For Data Protection for mysap.com, the Tioli Storage Manager API Client must be installed on the local system. TCP/IP must be ready for communication between the Tioli Storage Manager serer and the Tioli Storage Manager client. Installation Planning for Data Protection for mysap.com When starting the installation procedure, be prepared to proide the required information. For your conenience, an Installation Planning Sheet is aailable in Appendix I, Installation Planning Sheet, on page 163 and in file planning_sheet (UNIX) or planning_sheet.txt (Windows) on the CD-ROM. The following items must be considered when planning for installation: Oracle database SID. Path where the executables for the SAP backup tools reside. Tioli Storage Manager serer name. Name or IP address of your TSM serer. Tioli Storage Manager node name. TSM node configured on the TSM serer named for the backup of the SID denoted aboe. For details, refer to 4. Node Definition on page 102. Tioli Storage Manager management classes for database and log file backups. Management classes configured for the database backup and for the backup of log files. For details, refer to 3. Policy Definition on page 101. For Windows only: Path where the Tioli Storage Manager API (specifically the messages file dscameng.txt) resides (contents of enironment ariable DSMI_DIR). For details, refer to the Tioli Storage Manager documentation. For Windows only: Full path of client option file for Tioli Storage Manager (contents of enironment ariable DSMI_CONFIG). For details, refer to the Tioli Storage Manager documentation. For Windows only: Path for Tioli Storage Manager log files (contents of enironment ariable DSMI_LOG). The TSM API will create the file dsierror.log in this path. For details, refer to the Tioli Storage Manager documentation. For Windows only: Installation path for Data Protection for mysap.com. Path for Data Protection for mysap.com configuration files. During the installation, configuration files for Data Protection for mysap.com will be saed to this path. If old configuration files are found, they are renamed to <filename>.nnn, where nnn is a three-digit decimal number. Note that this path must not contain blanks. 22 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

39 Prepare for using the RMAN Support (see Chapter 6, Using Data Protection for mysap.com with RMAN, on page 55 ). Prepare for using the Administration Assistant for Data Protection for mysap.com. You will need the name or IP address of your Administration Assistant serer. It is recommended but not required that the Administration Assistant is installed beforehand. If you do not specify the Administration Assistant serer at installation time, it will not be configured. A procedure for specifying the Administration Assistant serer after the installation is complete is described in Specifying an Administration Assistant Serer on page 28. For more information on the Administration Assistant, refer to Chapter 8, Using the Administration Assistant for Data Protection for mysap.com, on page 63. After you hae ensured that all prerequisites hae been met and the installation planning steps were followed, the installation process can begin. This includes: 1. Installing the software 2. Performing Post Installation Steps 3. Verifying the installation with a Backup and Restore run Installing Data Protection for mysap.com There are two types of installation: initial installation and upgrade installation (migration). Initial Installation The Data Protection for mysap.com program is usually deliered on CD-ROMs and initial installations must always be made from CD-ROM. Refer to the file README.1st in the root path for information on where to find documents on your CD-ROM and follow the installation description below. Upgrade Installation (Migration) If you are going to upgrade from an earlier ersion of Tioli Data Protection for R/3 or Data Protection for mysap.com in your enironment, you hae the option to download the latest ersion from the IBM Tioli Internet home page at For more information on upgrading from an earlier ersion, refer to Upgrading Data Protection for mysap.com (Migration) on page 29. Installing Data Protection for mysap.com on UNIX (AIX, Solaris, HP-UX, Linux) Data Protection for mysap.com for UNIX systems is deliered as a single executable file named install_tdpr3_ora_<operating system>_<xx>bit.bin where <xx> is 32 or 64 <operating system> is aix43 for AIX 4.3, or aix51 for AIX 5.X, or solaris or hpux or linux Chapter 4. Installing or Upgrading Data Protection for mysap.com 23

40 When you inoke the file, you will be guided through the Data Protection for mysap.com setup procedure. To ensure that the setup procedure is carried out properly, read the following description carefully and follow the guidelines on the panels that are displayed during setup. To install Data Protection for mysap.com on a UNIX system, do the following: 1. Read the Release Notice (RELNOTE) and the README file proided with Data Protection for mysap.com. 2. Log in as root user on the mysap.com database serer machine. 3. The installer guides you through the installation ia a graphical X-Window. Ensure that you hae set the DISPLAY ariable correctly. 4. Inoke the installation file for Data Protection for mysap.com that fits your operating system and your Oracle database. 5. Check the summary at the end of the installation dialog. In the summary, among other information, you find the installation path of Data Protection for mysap.com. 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: an entry is created in/etc/inittab to start the background process prole an entry is created in/etc/serices needed for internal communication. After the installation, the following files are aailable on your system: In the installation path of Data Protection for mysap.com: backint prole createinfo backfm backint3.cat initsid.bki libtdp_r3.<ext> archie.ksh backup.ksh crontab.sample dsm.opt dsm.sys gensortfile.sh inclexcl.list README RELNOTE TIPHINTS a folder named _uninst is created, which contains seeral files. The DP for mysap.com configuration files under the SAP directories (typically, /oracle/sid/dbs) are as follows: init<sid>.utl, where SID is replaced by the Oracle database SID proided during installation init<sid>.bki, where SID is replaced by the Oracle database SID proided during installation agent.lic (Only after installation from CD-ROM, this is not contained in the web package). The configuration of Data Protection for mysap.com is done with the following basic performance setting: 24 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

41 Multiplexing 1 Parallel Sessions 1 To tailor the settings to your requirements, see Appendix B, The Data Protection for mysap.com Profile, on page 81. Installing Data Protection for mysap.com on Windows Data Protection for mysap.com for Windows is deliered as a single executable file named install_tdpr3_ora_win_<xx>bit.exe where <xx> is 32 or 64 When you inoke the file, you will be guided through the Data Protection for mysap.com setup procedure. To ensure that the setup procedure is carried out properly, read the following description carefully and follow the guidelines on the panels that are displayed during setup. To install Data Protection for mysap.com on a Windows system, do the following: 1. Read the RELNOTE and the README file proided with Data Protection for mysap.com 2. Log in as user with administrator authority on the mysap.com database serer machine. 3. In Windows Explorer, naigate to the directory where the installation package is located 4. Inoke the executable mentioned aboe and follow the instructions of the installation dialog. 5. Check the summary at the end of the installation dialog. In the summary, among other information, you find the installation path of Data Protection for mysap.com. 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: for the background process prole a serice is created. an entry is created in %WINDIR%\system32\driers\etc\serices needed for internal communication. After the installation, the following files are aailable on your system: In the installation path of Data Protection for mysap.com: backint.exe createinfo.exe prole.exe orasbt.dll backint3_en_us.dll backfm.exe archie.cmd backup.cmd dsm.opt serer_a.opt serer_b.opt inclexcl.list schedule.sample README RELNOTE Chapter 4. Installing or Upgrading Data Protection for mysap.com 25

42 TIPHINTS a folder named _uninst is created, which contains seeral files. In the path of the Data Protection for mysap.com configuration files: initsid.bki, where SID is replaced by the Oracle database SID proided during installation initsid.utl, where SID is replaced by the Oracle database SID proided during installation agent.lic (Only after installation from CD-ROM, this is not contained in the web package). Post Installation Steps After successfully completing the installation dialog for Data Protection for mysap.com, you need to perform following steps in order to hae a properly running system: reiew the TSM Option file set the password (initial password) erify the installation Reiew of the TSM Option File After the installation is completed, the TSM Option File needs to be checked in order to make sure that it contains the correct serer name as specified in the init<sid>.utl file. Furthermore it must be made sure, that the file contains the correct parameters. These depend on the password method, which was selected. (See Password Handling Methods on page 47). On UNIX the TSM serer definition is done in the dsm.sys file. The serer stanza specified in dsm.sys must match the entry in init<sid>.utl. On Windows you hae to define a file <serername>.opt. This file must be in the same directory where dsm.opt is located. <serername> is the name you specified in init<sid>.utl. The Password Data Protection for mysap.com should be installed after the TSM installation has been completed. TSM proides two different password methods to protect data. Data Protection for mysap.com must use the same method as specified within TSM. When Data Protection for mysap.com is installed it is assumed, that the password method, selected during the TSM installation, was manual password handling ( PASSWORDACCESS prompt). The default parameters for Data Protection for mysap.com are set on this assumption. If for TSM a different password method is set, refer to Password Handling Methods on page 47 in order to adjust the Data Protection for mysap.com parameters. To be able to work with Data Protection for mysap.com, you hae to proide Data Protection for mysap.com with the password for the TSM node. This is a manual step on the shell: Log on as Oracle user. Enter the following command for Windows: backint -p <full path to UTL file>\init<sid>.utl -f password for Unix 26 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

43 backint -p <full path to UTL file>/init<sid>.utl -f password Enter the password when prompted. Verifying the Installation Preparing the Verification Before erifying the installation, make sure that: all files in the Data Protection for mysap.com installation directory on UNIX systems hae the owner root, the group system, and execute permissions for all users. the sticky bit must not be set for the installed executables. the SAP Backup profile is configured properly. This profile, which must be configured, can be found on UNIX systems in the path $ORACLE_HOME/dbs and on Windows systems in the path %ORACLE_HOME%\database. This configuration refers to three keywords within that profile. These keywords are: backup_type Identifies the default type of the database backup. This parameter is only used by BRBACKUP (default is offline). backup_de_type Determines the backup medium that will be used (default is tape). util_par_file This parameter specifies where the parameter file, which is required for a backup with an external backup program, is located. Data Protection for mysap.com supports, for example, the combinations of the keywords backup_de_type and backup_type shown in the table below. Table 1. SAP Backup Profile Parameter Combinations Operation backup_de_type backup_type Offline backup util_file offline Online backup util_file online Online backup with indiidual tablespace locking util_file_online online To carry out online backups with indiidual tablespace locking with the external backup program Data Protection for mysap.com, the SAP Backup profile parameter must be set or changed as shown below: backup_type backup_de_type util_par_file = online = util_file_online =?/dbs/init@.utl The question mark is the official Oracle substitute symbol for the home directory of the database system. This is specified in the enironment ariable ORACLE_HOME. is the official Oracle substitute symbol for the home directory of the database system. This is specified in the enironment ariable ORACLE_SID. Executing the Verification To erify and test the installation, it is recommended that you try out a small Chapter 4. Installing or Upgrading Data Protection for mysap.com 27

44 backup procedure (tablespace backup) using SAPDBA and start a full online or offline backup using BRBACKUP as shown below. brbackup -c -t online (online database backup) brbackup -c -t offline (offline database backup) It is strongly recommended that you do a restore/recoery of the whole mysap.com database (using SAPDBA). A good method to prepare for this is to first run a complete offline backup using BRBACKUP. Step by step scenarios for backup or restore/recoery procedures of a mysap.com Oracle database using Data Protection for mysap.com can be found in the IBM redbook R/3 Data Management Techniques Using Tioli Storage Manager, SG For backup tests, the SAP database utilities SAPDBA, BRBACKUP, and BRARCHIVE should be used. For restore or recoery it is recommended that only SAPDBA or BRRECOVER is used. Note IBM redbooks can be found at Specifying an Administration Assistant Serer If you need to specify a new Administration Assistant Serer, perform the steps described below. Specifying an Administration Assistant Serer on UNIX (AIX, Solaris) 1. Find the entry for daemon prole in /etc/inittab. Modify the entry to read: /prole -p tdpr3ora tdpr3ora64 <AA serer name> <port> where <AA serer name> is the name or IP address of the Administration Assistant serer and <port> is the port that the Administration Assistant is listening to, the default is Make sure that Data Protection for mysap.com 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 Serer on Windows From a command prompt, issue: prole -update <AA serer name> <port> where <AA serer name> is the name or IP address of the Administration Assistant serer and <port> is the port that the Administration Assistant is listening to, the default is Data Protection for mysap.com Technology Installation & User s Guide for Oracle

45 Upgrading Data Protection for mysap.com (Migration) Special Installation In order to upgrade Data Protection for mysap.com from an earlier ersion of Tioli Data Protection for R/3 or Data Protection for mysap.com, do the following: 1. Before upgrading check RELNOTE for incompatibilities between your installed ersion and the new ersion. Make sure, that data which was backed up with an older ersion of Tioli Data Protection for R/3 or Data Protection for mysap.com can be restored with the ersion you want to install. Data that was backed up with Tioli Data Protection for R/3 Version 2.7 must be restored with Tioli Data Protection for R/3 Version 3.1. or Version 3.2 Data that was backed up with Tioli Data Protection for R/3 Version 3.1 or 3.2 or Data Protection for mysap.com Version 3.3 can be restored with Data Protection for mysap.com Version 3.3. or higher 2. We recommend a full backup before upgrading to the new ersion. 3. Uninstall the old ersion. For the uninstallation procedure, see Uninstalling Data Protection for mysap.com on page 30 below. 4. Install the current ersion. For the installation procedure, turn back to the beginning of this Chapter 4, Installing or Upgrading Data Protection for mysap.com, on page We recommend a full backup after upgrading to the new ersion Silent Installation Installation can be done with one single command line. For preparations, you hae to record the installation options. This can be done by: install_tdpr3_ora_<platform> -options-record <filename>. The created option file can easily be checked and can be modified to be used for an installation on different systems (for example Oracle <SID>). To use the silent install function, the install package must be called with the recorded option file: install_tdpr3_ora_<platform> -options <filename> -silent Console Installation To support target systems, that do not hae 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 aailable with a GUI installation. Instead, user data entry and status messages are displayed on the console or command prompt window. To start the console installation, two parameters are necessary: -is:jaaconsole -console install_tdpr3_ora_<platform> -options <filename> -is jaaconsole -console In addition, you can also record the installation options in a file. You do this by issuing following command: install_tdpr3_ora_<platform> -options-record <filename> -is jaaconsole -console. Chapter 4. Installing or Upgrading Data Protection for mysap.com 29

46 Firewall Installation (For a remote installation through a firewall). If the TCP port for X11 communication is not enabled, use the console install as described aboe in Console Installation on page 29 Uninstalling Data Protection for mysap.com Before upgrading Data Protection for mysap.com to a higher leel, you hae to uninstall the old package on your system as described in the following sections. Your configuration files are retained. If you hae installed Data Protection for mysap.com also for databases other than Oracle, you only hae to uninstall Data Protection for mysap.com for Oracle. Uninstalling Data Protection for mysap.com from UNIX (AIX, Solaris, HP-UX, Linux) To uninstall Data Protection for mysap.com, perform the following steps: 1. Log in as root user on the mysap.com database serer machine. 2. Make sure that the DISPLAY ariable is set correctly as the uninstall procedure requires a graphical X-Window. 3. Make sure Data Protection for mysap.com 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: AIX 32-bit /usr/tioli/tsm/tdp_r3/ora/_uninst/uninstaller.bin AIX 64-bit: /usr/tioli/tsm/tdp_r3/ora64/_uninst/uninstaller.bin other UNIX 32-bit /opt/tioli/tsm/tdp_r3/ora/_uninst/uninstaller.bin other UNIX 64-bit /opt/tioli/tsm/tdp_r3/ora64/_unist/uninstaller.bin Uninstalling Data Protection for mysap.com from Windows To uninstall Data Protection for mysap.com on a Windows NT or Windows 2000 machine, perform the following steps: 1. Log on as user with administrator authority on the mysap.com database serer machine. 2. Ensure that Data Protection for mysap.com is not running. 3. Select Start Settings Control panel. 4. Click on Add/Remoe Programs. 5. Select Data Protection for mysap.com and click on Remoe. 6. Follow the instructions of the uninstall procedure. 30 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

47 Chapter 5. Adjusting your System After you hae erified the installation of Data Protection for mysap.com, adjusting your system to your specific needs and oerall system configuration is adisable. These adjustments are of two natures: Optimizing the performance of your data protecting enironment Preparing Data Protection for mysap.com to interact with other programs like Administration Assistant and RMAN. Adjustments for Improing Performance of Data Transfer Restore Objecties Protecting against loss of data and minimizing downtime of the mysap.com system are the key requirements for defining a best-fit backup/restore process. The definition of a performance optimized system should start with the restore of the database as restore downtime incurs costs which are seeral orders of magnitude higher than backup downtime. During restore, mysap.com users cannot perform their work, whereas backups run concurrently with application load. Therefore, the backup process definition has to be goerned by the restore objecties. Minimizing downtime can be achieed by three key measures: Deployment of a best suited method for backup/restore, for example: full backup daily s. weekly (less logs to recoer) online s. offline backups (application work can continue during backup) FlashCopy backup s. direct backup ( zero impact on application) Optimizing for maximum throughput of the data transfer during backup or restore on the basis of three different techniques: local backup (production and backup serer on same system) remote (LAN) backup (production and backup serer on different systems connected ia LAN) LAN-free backup (production serer transfers backup data directly to storage ia SAN and meta data to backup serer ia LAN) Offloading inactie data into an external archie to trim the size of the database to the data olume actually used. A companion product to Data Protection for mysap.com - IBM Content Manager CommonStore for SAP - is aailable from IBM. It connects Tioli Storage Manager to the mysap.com ArchieLink Interface coering the whole range of mysap.com archiing functions: inactie data (off-loading) printlists and outgoing documents incoming documents (scan, fax) Copyright IBM Corp. 1995,

48 General Aspects of Data Transfer The following discussion focusses mainly on optimizing data transfers between Database (production) serer and backup serer. A simplistic model (see Figure 6) shows three independent components inoled in the data transfer and which are discussed below : mysap.com database serer (see Optimizing the mysap.com Database Serer (Production Serer) for Data Transfer on page 33) Network (see Optimizing The Network on page 38) TSM serer (backup serer) (see Optimizing The Backup Serer (TSM Serer) on page 39) A continuous stream of data is generated between these components for the backup or restore of data and the weakest link in this chain determines the oerall data rate. Figure 6. Data Throughput 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: The production (mysap.com database) serer is ultimately the most critical component for data transfer. Bottlenecks in network and backup serer can be remoed through parallelism. Special attention should be gien to disk layout (database should be spread across as many disks as possible) I/O paths CPU power (data transfer takes cycles) Volume mirroring (by Volume Manager) can slow down the data transfer during restore significantly. For short restore time it is recommended to turn off mirroring during the restore. 32 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

49 When using a LAN-free configuration (Managed System for SAN), the Storage Agent will cause additional load on the production serer CPU. As a rule of thumb, the load will double compared to data transfers to a remote backup serer (LAN). The network between production serer and backup serer should proide sufficient bandwidth. For example, use Gigabit Ethernet LAN. A dedicated backbone network should be implemented for backup/restore separate from the user LAN. A dedicated backup serer allows sharing of resources and yields most efficient resource utilization. Backup of data files (large files) should be directed to tape as this yields the highest transfer rates. Using disks to compensate for a sufficient number of tape dries will affect the throughput. 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 migrated to tape collectiely to aoid excessie tape mounts. Optimizing the mysap.com Database Serer (Production Serer) for Data Transfer The following typical steps are performed on the mysap.com database serer for a backup process (for restore correspondingly): Read data from disk Transfer data through I/O interface into the client CPU s main memory ia operating system functions Process data by Data Protection for mysap.com Send data ia TSM API to TSM serer through a communication method (mostly TCP/IP) Optimizing Data Transfer through File Configuration (Input/Output) The basis of an optimized data transfer is an optimized file configuration. To achiee this, recommendations for setting up an optimum I/O configuration should be considered, e.g., disk attachment, internal busses like PCI, in order to maximize the bandwidth for data transfers. The file layout of the database can hae a significant impact on maximum achieable data rates. Data should be spread across as many disks as possible. File system features, like caching or reading ahead, hae an effect on data rates as well and should be adapted to the specific characteristics of backup/restore with its large files and data olumes. The following graphic shows a simplified model of data transfer from disk thru the network to the mysap.com database serer and from there to the backup storage media. Figure 7. Simplified Data Transfer for a Backup / Restore Chapter 5. Adjusting Your System 33

50 Optimizing Data Transfer through Data Protection for mysap.com Data Protection for mysap.com proides the following features for optimizing performance of data transfer to the TSM: Adaptie File Sequencing (when called from SAP DBA ia backint interface) This feature makes use of your optimized I/O configuration. An optimal sequence for the files to be backed up or restored is computed automatically to minimize backup and restore windows. In order to aoid parallel disk accesses, a file/disk correspondence is determined by automatically checking the disk layout at regular interals. If automatic detection is not possible as it is the case for most intelligent disk subsystems, e.g. IBM Enterprise Storage Serer, EMC SYMMETRIX, etc., symbolic file locations can be entered manually (see keyword SORTFILE on page 88 ). Parallel sessions Multiple datastreams are generated in parallel, one for each of the corresponding number of storage deices (usually tapes) on the backup serer. File multiplexing (when called from SAP DBA ia backint interface) For backup, multiple files are read from disk in parallel and merged into a single data stream (session). For restore, this data stream is demultiplexed and data is written into the respectie original files. This function is used to achiee optimum single session throughput and tape utilization. Data compression (using a lightweight run-length algorithm) Blocks of consecutie binary nulls in the data stream from/to disks are compressed/decompressed. Compression factors between 1.3 and 4 hae been obsered in real installations. This feature should be deployed when the network is the bottleneck for data transfer with the backup serer and the production serer has a sufficiently powerful CPU to take on the additional load. Settings for the mysap.com database serer Data Protection for mysap.com functions and features are actiated by setting the corresponding parameters in the Data Protection for mysap.com profile (see Appendix B, The Data Protection for mysap.com Profile, on page 81). Block Size Data Protection for mysap.com allows specification of the block size for disk I/O as transfer rates depend on disk subsystem characteristics. The block size can be set by the keyword BUFFSIZE (range from 4096 to ) in the Data Protection for mysap.com profile. In most configurations the default settings (32768 for Windows, for UNIX) yield acceptable results. For EMC disk subsystems, the best transfer rates hae been achieed when setting BUFFSIZE equal to stripe size. Parallelism Data Protection for mysap.com is highly configurable. It offers the ability to read the data in parallel streams. The data may be transferred using parallel paths to the TSM serer or een sent to different TSM serers in parallel. All of these methods can be combined. When applying parallelism to remoe bottlenecks, you can do this in seeral components: 34 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

51 reading data from multiple disks in parallel (multiplexing) within a single session (one tape drie) transferring data to multiple tape dries in parallel (parallel sessions) distributing sessions oer multiple parallel network connections (parallel paths) transferring data to/from multiple parallel backup serers (parallel serers) These four components are described below: Multiplexing The following graphic shows multiplexing: Figure 8. Multiplexing Multiplexing is used to minimize the number of storage deices on the backup serer side. The alue for the keyword MULTIPLEXING determines the number of files read in parallel within one session. The optimum alue should be determined through tests on a specific system (see also Optimizing Your Enironment on page 40). An appropriate range is between 1 and 4 (default 1). Note: Setting MULTIPLEXING too high may cause noticeable oerhead in thread management on the system and offset performance gain in throughput. If the aerage disk read rate is 4.5 MB/s from each disk, the database is backed up with a data rate of 4.5 * 4 = 18 MB/s. If each file is compressible by a factor of two and compression is actiated, it can be transferred to a Tioli Storage Manager serer at (4.5 * 4) / 2 = 9 MB/s. With null block compression, but without multiplexing, we could transfer only 4.5 / 2 = 2.25 MB/s to one Tioli Storage Manager serer. (This example assumes that the Tioli Storage Manager serer and tape drie are fast enough to cope with this data rate.) Multiplexing reduces the number of Tioli Storage Manager serers (and tape dries) required. The optimal alue for MULTIPLEXING depends ery much on the hardware enironment, for example, the aailability of a fast network (FDDI, Fast Ethernet), of fast tape dries within the tape (media) library, and on the compressibility of the database files. Appropriate MULTIPLEXING alues are expected in the range of 1 to 4. The example aboe shows some of the typical dependencies between the total backup rate, the disk transfer rate, the compression ratios, and the Tioli Storage Manager data rate. Parallel Sessions The following graphic shows you the setup of parallel sessions. Multiple tape dries are used to transfer backup / restore data in parallel. This way Data Protection for mysap.com allows you to make use of seeral tape dries in Chapter 5. Adjusting Your System 35

52 parallel in order to increase the transfer rate to/from a Tioli Storage Manager serer. Figure 9. Parallel Sessions The keywords MAX_SESSIONS, MAX_BACK_SESSIONS, MAX_ARCH_SESSIONS and MAX_RESTORE_SESSIONS are used for defining the number of parallel sessions for data file backup, archie (backup of log files) and restore. For a detailed description of how to use these keywords, see page 85. Note: Testing should be performed to determine the actual throughput gain as multiple accesses to the same tape may slow down data transfer. In customer installations throughput increases of up to 30% hae been obsered. Parallel sessions are closely related to TSM management classes. If RMAN is used, the number of configured sessions must be equal or higher than the number of configured RMAN channels (see also Chapter 6, Using Data Protection for mysap.com with RMAN, on page 55). The management class specified in the profile keyword BRBACKUPMGTCLASS will be used when running the BRBACKUP. For BRARCHIVE runs, the management class specified in the profile keyword BRARCHIVEMGMTCLASS will be used. When running BRBACKUP, the data will usually be written directly to tape dries on the Tioli Storage Manager serer. This means that the parameter specified in the MAX_SESSIONS keyword must match the number of tape dries used simultaneously. When setting up the Tioli Storage Manager, make sure to: do not actiate collocation in the (tape) storage pool defined for the management class chosen as BRBACKUPMGMTCLASS; make aailable as many tape dries for this management class as the number of sessions defined in MAX_SESSIONS. When running BRARCHIVE, either disk or tape storage pools can be utilized. The size of offline redo log files is much smaller compared to the size of database tablespace files backed up by BRBACKUP. If you are using tape pools as (primary) pools, the same considerations for the tape setup as for the disk setup (see BRBACKUP aboe) apply. The adantage of a disk storage pool is its random access nature: Seeral sessions of one BRARCHIVE can utilize one or two independent disk storage pool(s) Seeral sessions of BRARCHIVE runs of seeral databases can simultaneously utilize one or two independent disk storage pool(s) 36 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

53 Parallel Path The following graphic depicts how multiple parallel network connections (paths) are used for distributing the backup / restore workload, thus increasing performance. Figure 10. Parallel Paths Parallel paths can be used by Data Protection for mysap.com to eliminate network bottlenecks. For each additional path, additional network adapters are required on both the production and backup serer. The setup for parallel paths is described in detail in Appendix A, Alternate/Parallel Backup Paths and Backup Serers, on page 75. Parallel Serers The following graphic shows how multiple parallel backup serers are used for distributing the backup / restore workload, thus increasing performance. Figure 11. Parallel Serers Parallel serers can be used by Data Protection for mysap.com to eliminate backup serer bottlenecks. Note that for each additional path additional network adapters are required on both the production and backup serer. The setup for Parallel Serers is described in detail in Appendix A, Alternate/Parallel Backup Paths and Backup Serers, on page 75. If used with RMAN, the number of sessions configured for each serer must be equal or higher than the number of sessions configured for restore. Otherwise Oracel RMAN may request more objects in parallel from the same serer than sessions are configured for that serer. Compression Chapter 5. Adjusting Your System 37

54 By compressing zero-byte blocks, a ery simple but fast compression method, throughput is increased. This compression method is efficient with database files that usually contain large portions of null blocks.. This compression is done before sending data oer the network to the Tioli Storage Manager serer. The Data Protection for mysap.com profile keyword RL_COMPRESSION must be set to YES (default is NO). This compression has been designed specifically for database files, since they usually contain large portions of null blocks. Figure 12. Null Block compression Optimizing The Network The network affects the data transport in two ways: The communication protocol adds some oerhead which impacts the data rate, but as the database files making up the bulk of the data are usually ery large, this oerhead is relatiely small. The network bandwidth limits the data throughput. Our experience shows that the effectiely usable bandwidth is approximately half the theoretical bandwidth of the specific network. For high-speed networks such as Gigabit Ethernet, it is likely that the network adapters of the respectie systems limit the effectie data throughput rather than the network itself. For optimizing the performance of the network in regard to data throughput Data Protection for mysap.com proides the capability of Multiple (Network) Paths. Parallel sessions can be assigned to multiple network paths between mysap.com database and the backup serer (see also, Appendix A, Alternate/Parallel Backup Paths and Backup Serers, on page 75). Thus, the oerall network bandwidth usable for data transfer can be increased to the sum of the parallel paths. Settings for Network Parameters The network on a UNIX machine can be configured with the no command. This command sets or displays current network attributes in the kernel. The command must be run again after each start-up or after the network has been reconfigured. For details about the no command, see the man page of no of your operating system. Caution The no command does not perform range checking. It therefore accepts all alues for the ariables. If used incorrectly, the command can cause the system to become inoperable. The following table shows the appropriate network attributes with the recommended alues. 38 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

55 Table 2. Tuning of Network Settings Attributes Value Description rfc Enables TCP enhancements as specified by RFC 1323, TCP Extensions for High Performance. The default is 0. A alue of 1 specifies that all TCP connections will attempt to negotiate the RFC enhancements. sb_max Specifies the maximum buffer size allowed for a socket. The default is bytes. From the point of iew of performance recommendations, the sb_max alue should correspond to the TCPWindowsize setting within the Tioli Storage Manager configuration file dsm.sys and should be twice the TCPWindowsize. To adapt these alues, the following commands hae to be inoked by the root user on the appropriate machine. no -o rfc1323=1 no -o sb_max= Note These changes will be lost at system reboot. To make changes permanent, edit the /etc/rc.net file. If an SP switch (RISC 6000) is used, the following two alues should be adapted as shown in the following table. Table 3. Tuning of SP Switch Buffer Pools Attributes Value Description rpoolsize The receie pool is a buffer pool for incoming data. The size for alues is in bytes. spoolsize The send pool is a buffer for outgoing data. The size for alues is in bytes. The buffer pool settings can be changed using the chgcss command. After the changes, it is necessary to reboot the node. Optimizing The Backup Serer (TSM Serer) The backup serer receies the data from the network, remoes the communication frames and prepares the data for writing onto backup storage media (usually tapes). Obserations show that the CPU load on the backup serer for a gien data throughput is approximately 60% of that on the client. Therefore, the backup serer is not the critical resource from a CPU power point of iew. Data Protection for mysap.com proides the following capabilities for optimizing the performance of the backup serer in regard to data rates: Parallel sessions. Multiple tape dries can be used in parallel to store data and increase oerall data throughput. See also under MAX_SESSIONS in Appendix B, The Data Protection for mysap.com Profile, on page 81. Storage hierarchies Chapter 5. Adjusting Your System 39

56 If tape dries are already assigned, disks can be used with additional sessions as intermediate storage, which can later be migrated to tape (inherent function of Tioli Storage Manager). This method is recommended for log files (which are considerably smaller than data files) to aoid an excessie number of tape mounts. Multiple Serers As with multiple paths, parallel sessions can be routed to multiple Tioli Storage Manager serers to increase the oerall data throughput of the backup serer (see also on page 88). Optimizing the Settings for the Tioli Storage Manager The performance adjustments on the Tioli Storage Manager side can be done by customizing the appropriate configuration files. On the serer side, it is the serer option file dsmser.opt, and on the client side the client option file(s) dsm.sys on UNIX systems and <serer>.opt on Windows systems. The following table shows the corresponding Tioli Storage Manager configuration file attributes with the recommended alues. Table 4. Tuning Tioli Storage Manager Configuration File Attributes Attributes Value Description TCPBuffsize 32 Specifies the size, in kilobytes, of the buffer used for TCP/IP send requests. This option affects whether or not Tioli Storage Manager sends the data directly from the session buffer or copies the data to the TCP buffer. A 32K buffer size forces Tioli Storage Manager to copy data to its communication buffer and flush the buffer when it fills. TCPNODelay YES Specifies whether the serer should send small amounts of data or allow TCP/IP to buffer the data. Disallowing buffering may improe throughput but more packets will be sent oer 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 receiing data. The range of alues is 0 to Additional information can be found at Optimizing Your Enironment Based on the multitude of software and hardware parameters affecting performance and considering the ariety of system enironments as well as objecties, there cannot be one set of alues for the parameters which fits all. Indiidual optimizing on a trial and error basis will almost always be necessary if tuning is to be done to the maximum possible leel. The following list presents a best practice sequence of steps recommended for tuning: Single session optimization Start out with following parameter setting: MAX_SESSIONS=1, MULTIPLEXING=1, RL_COMPRESSION OFF 40 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

57 Step 1: Step 2: Optimize Volume Manager settings (AIX-VMtune), BUFFSIZE, network options, and TSM serer parameters as described in the preious sections of this chapter. Increase MULTIPLEXING to 2,3,4 The data rate should asymptotically increase with the MULTIPLEXING alue until either the network or the tape drie limits the throughput. Increasing MULTIPLEXING will cause an increase of CPU load: proportional to the data rate transferred by Data Protection for mysap.com additional system oerhead for thread management. Therefore, a multiplexing alue should be selected that still shows a reasonable gain in throughput (before the multiplexing data rate cure starts to leel off) Multisession Optimization Step 3: Step 4: Step 5: Increase MAX_SESSION to 2,3,4... The data rate should increase asymptotically with the number of sessions. Note: Sessions can only be increased to the maximum number of tape dries assigned to this backup as each session requires a dedicated tape drie. Monitor network and database serer (CPU, I/O) utilization to determine the bottleneck. The necessary actions result from where the bottleneck is and may include: Optimization of disk layout of the mysap.com database, see Step 4 Turning run length compression on (RL_COMPRESSION Y); note that this will increase the CPU load on the mysap.com database serer Increasing network bandwidth by using parallel paths, see Step 5 Increasing the maximum number of sessions by adding more tape dries on the backup serer Increasing the CPU power of the mysap.com database serer Add additional network paths (multiple path function) and distribute the sessions onto the multiple paths, see Appendix A, Alternate/Parallel Backup Paths and Backup Serers, on page 75. Optimize the disk layout of your mysap.com database serer. To aoid disk contention caused by multiple read operations, distribute the files of your mysap.com database across as many disks as possible. Check for limitations in the bandwidth of the I/O adapters. Add additional adapters if necessary. Adjustments for the Administration Assistant If you want to make use of the Administration Assistant (highly recommended), you hae to set up a connection between Data Protection for mysap.com and the Administration Assistant. This is usually done during installation of Data Protection for mysap.com. Chapter 5. Adjusting Your System 41

58 Adjustments for High Aailability If you hae not specified the use of the Administration Assistant during installation of Data Protection for mysap.com, you can set up the connection by following the description gien in Specifying an Administration Assistant Serer on page 28 If you hae specified the use of the Administration Assistant during installation of Data Protection for mysap.com, the Administration Assistant can be installed. For information see Installation on page 65. Considerations for Using IBM HACMP for AIX This chapter is intended to gie a short introduction to the way Data Protection for mysap.com works internally, thus enabling the user to take actions for HACMP fail-oer configurations. As an example, we use the following configuration, which should be easily adaptable to others. Here, we use the mutual takeoer configuration, where each node can take oer the other. If the application serer and database serer are installed on different hosts, the described actions need to be taken on the database serers only. The following figure illustrates the takeoer enironment: Figure 13. Sample Enironment for HACMP Takeoer Data Protection for mysap.com Internals Files: The installation directory is /usr/tioli/tsm/tdp_r3. Lock files and disk sorting files can be found in /ar/tdp_r3. There is only one prole running on each host (een after takeoer). Each SAP system has its own DP configuration files (init<sid>.utl, init<sid>.bki) in /oracle/<sid>/dbs. Dependencies: Both hosts should hae the same leel of Tioli Storage Manager API installed. Both hosts must hae the same leel of Tioli Data Protection for R/3 installed. On both hosts, the dsm.sys file (in /usr/tioli/tsm/client/api/bin/dsm.sys) must contain all serer names required for takeoer. 42 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

59 Communication: Backint connects to prole using the following procedure: Get the IP address for localhost (should be ). Get the backint serice (should be for the 32 Bit Version and for the 64 Bit Version). Connect to : Installation and Setup Installation: A prerequisite for installation is a correct setup of the TSM client. The installation steps for the TSM Backup/Archie Client for AIX can be found in the documentation Tioli Storage Manager Installing the Clients. Defining Data Protection for mysap.com as an HACMP Application: To enable Data Protection for mysap.com to participate in HACMP failoer 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, SC 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 Serers > Add an Application Serer. 3. Enter field alues as follows: Serer Name Enter an ASCII text string that identifies the serer (for example, tdpclientgrpa). You use this name to refer to the application serer when you define it as a resource during node configuration. The serer 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 serer (for example, /usr/sbin/cluster/eents/utils/start_tdpr3.sh). This script is called by the cluster eent scripts. This script must be in the same location on each cluster node that might start the serer. Stop Script Enter the full pathname of the script that stops the serer (for example, /usr/sbin/cluster/eents/utils/stop_tdpr3.sh). This script is called by the cluster eent scripts. This script must be in the same location on each cluster node that might stop the serer. 4. Press Enter to add this information to the HACMP for AIX ODM. 5. Press F10 after the command completes to leae SMIT and return to the command line. Sample client start and stop scripts are proided later in this chapter. Refer also to the HACMP for AIX Planning Guide V4.4, SC , for further information about selecting the HACMP node topology and takeoer relationships. Chapter 5. Adjusting Your System 43

60 Note that Data Protection for mysap.com must be in a resource group haing a cascading or rotating takeoer relationship. It does not support a concurrent access resource group. Adding the Data Protection for mysap.com Application to an HACMP Resource Group A final step in enabling Data Protection for mysap.com for HACMP failoer 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 alues that define all the resources you want to add to this resource group. 5. After entering field alues, synchronize cluster resources. 6. Press F10 to exit SMIT or F3 to return to preious 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 takeoer relationship. 44 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

61 Sample Start Script The only purpose of this script is to update Data Protection for mysap.com s olume information after a takeoer and after all SAP file systems are mounted, because there are more filesystems and disks aailable. This file is used by the Data Protection for mysap.com disk sorting function and may hae an impact on performance. The start script is used in the following cases: HACMP is started and resource groups are actiated a failoer occurs and the resource group is started on another node fallback occurs (a failed node re-enters the cluster) and the resource group is transferred back to the node re-entering the cluster. The start script will be called by HACMP as the root user. Note: This script is not in its final form. It should be considered pseudo code that indicates the functions it will perform. #!/bin/ksh # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # This sample script is proided for use with the DP for mysap.com in an HACMP # # enironment. It should be reiewed and customized to meet your specific client # # enironment # # # # # # Name: start_tdpr3.sh # # # # Function: # # A sample shell script to start the disk sorting function for DP for mysap.com # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # if ["$VERBOSE_LOGGING"="high"] then set -x fi START_DISKINFO() { # It is assumed that prole is already running # Start createinfo in the background. nohup /usr/bin/createinfo & } # This starts the disk info process to allow disk sorting for the taken-oer SAP instance. START_DISKINFO Exit 0 Chapter 5. Adjusting Your System 45

62 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/brarchie 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 hae already been accomplished by the HACMP script that stops R/3. It may also not be desirable in certain installations and should be reised. The stop script is used in the following situations: HACMP is stopped a failoer 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 failoer. 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 proided for use with DP for mysap.com in an HACMP # # enironment # # It should be reiewed and customized to meet your specific enironment # # # # # # Name: stop_tdpr3.sh # # # # Function: A sample shell script to update the disk information after the # # mysap.com instance is unmounted. # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # if ["$VERBOSE_LOGGING"="high"] then set -x fi # Function to update all disk information for TDP for R/3 START_DISKINFO() { # You may want to cancel all backups currently running # Note that this will generate errors in the current backup logs and it will also cancel the # connection to the Admin Assistant. # *** Note that if you are using TDP for ESS for R/3, this may leae the ESS in an inconsistent # state. # kill 9 `cat /ar/tdp_r3/prole.pid` # Start createinfo in the background to update the disk information. This should be done # after all SAP file systems are umounted. nohup /usr/bin/createinfo & } # This starts the disk info process to update the disk information. START_DISKINFO Exit 0 46 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

63 Adjustments for Automation Password Adjustments Password Handling Methods Before you can start using Data Protection for mysap.com, you need to define which password handling method you want to use. You can choose between using no password manual password handling automatic password handling Consider the following alternaties with their implications: No password required by Tioli Storage Manager (AUTHENTICATION OFF) This is the simplest method; howeer, no security can be enforced. Eery user connected to this serer (authentication is set OFF on the Tioli Storage Manager serer leel) can access Tioli Storage Manager without a password. This method is only recommended if adequate security measures can be established otherwise, for example, if Tioli Storage Manager is only used for mysap.com (no other clients are registered), and the respectie authorizations are set in the UNIX system. Manual password generation This method is simple to set up and proides password security, howeer, it requires a synchronized update of the password in Tioli Storage Manager (client) and Data Protection for mysap.com (command line). Additionally, it requires a manual update of the password in DP for mysap.com wheneer the password expires on the TSM Serer. This method is only recommended during installation and testing together with a sufficiently long expiration period (to aoid haing to change the password). It is not recommended for production operation. If you want to use manual password handling, you must proide the password needed for a client connection to Tioli Storage Manager which was specified when the node ID was initially registered within Tioli Storage Manager (see 4. Node Definition on page 102). The password is requested initially and again each time it expires for this node within Tioli Storage Manager. Normally, you are prompted for the client password each time Data Protection for mysap.com starts a Tioli Storage Manager session. This can be aoided if the client password is stored in encrypted form within the Data Protection for mysap.com configuration file (init<sid>.bki). This can be done with the following command: For UNIX systems: backint -p /oracle/<sid>/dbs/init<sid>.utl -f password For Windows systems: backint -p <drie>:\orant\database\init<sid>.utl -f password Chapter 5. Adjusting Your System 47

64 Data Protection for mysap.com prompts for all required passwords which were set for the appropriate Tioli Storage Manager (this depends on how many Tioli Storage Manager serers were declared in the Data Protection for mysap.com profile) and checks whether the passwords are alid. If a connection between Data Protection for mysap.com and Tioli Storage Manager is to be established, Data Protection for mysap.com reads the password from the configuration file and uses it for registration on the Tioli Storage Manager serer. Automatic Password Handling (Password set by Tioli Storage Manager) In this case you do not hae to synchronize the passwords manually on the Tioli Storage Manager serer and client sides. The generation and synchronization of passwords is handled by a Tioli Storage Manager program. Tioli Storage Manager sets the password automatically on a per-node basis according to the expiration specification. This method is recommended for an automated production enironment. If you are using automatic password handling, you need to: 1. update the password on the Tioli Storage Manager serer 2. log on once using the aboe password function on the client node When the password expires, a new password will be generated automatically. Note: If parallel path is used, no password access generate is possible. 48 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

65 Table 5. Password Handling for UNIX Password Configuration Matrix (UNIX) After you hae selected the suitable password handling alternatie, follow the configuration matrix to set the keywords/parameters in the different profiles accordingly. Proceed as indicated by the step number. Step Profile/Action Parameter Password No Manual Set by Tioli Storage Manager 1 Tioli Storage Manager admin AUTHENTICATION EXPIRATION PERIOD (see note 1) 2 dsm.sys PASSWORDACCESS PASSWORDDIR (see note 5) NODENAME 3 Tioli Storage Manager client (root user) 4 Data Protection for mysap.com profile (init<sid>.utl) 5 Data Protection for mysap.com command line OFF n.a. n.a. n.a. n.a. ON <n days> (see note 2) PROMPT n.a. n.a. ON <n days> GENERATE <path> <nodename> SET PASSWORD n.a. n.a. <password> (see note 3) For each SERVER statement specify: PASSWORDREQUIRED ADSMNODE For each SERVER statement specify: backint -p init<sid>.utl -f password (Command see on page 47). NO <nodename> n.a. YES <nodename> <password> (see note 1) NO (see note 4) <password> Notes: 1. See Tioli Storage Manager documentation. 2. If you are using manual password generation during testing, make sure that the expiration period is set to a sufficiently long time (> 60 days). 3. For an initial setup, this password must be the same as was specified when registering the node to Tioli Storage Manager. The password must be changed first on the Tioli Storage Manager serer and then in the Data Protection for mysap.com product. 4. ADSMNODE must not be set when PASSWORDACCESS generate is set. 5. The users <SID>adm and ora<sid> must hae read and write permission for the path specified in the PASSWORDDIR keyword in the Tioli Storage Manager client options file. Chapter 5. Adjusting Your System 49

66 Table 6. Password Handling for Windows Password Configuration Matrix (Windows) After you hae selected the suitable password handling alternatie, follow the configuration matrix to set the keywords/parameters in the different profiles accordingly. Proceed as indicated by the step number. Step Profile/Action Parameter Password 1 Tioli Storage Manager admin AUTHENTICATION EXPIRATION PERIOD (see note 1) 2 <serer>.opt PASSWORDACCESS PASSWORDDIR (see note 5) NODENAME 3 Tioli Storage Manager client 4 Data Protection for mysap.com profile init<sid>.utl 5 Data Protection for mysap.com command line No Manual Set by Tioli Storage Manager OFF n.a. n.a. n.a. n.a. ON <n days> (see note 2) PROMPT n.a. n.a. ON <n days> GENERATE <path> <nodename> SET PASSWORD n.a. n.a. <password> (see note 3)n.a. For each SERVER statement specify: PASSWORDREQUIRED ADSMNODE For each SERVER statement specify: backint -p init<sid>.utl -f password See Password Handling Methods on page 47. NO <nodename> n.a. YES <nodename> <password> (see note 1) NO (see note 4) <password> Notes: 1. See Tioli Storage Manager documentation. 2. If you are using manual password generation during testing, make sure that the expiration period is set to a sufficiently long time (> 60 days). 3. For an initial setup this password must be the same as was specified when registering the node to Tioli Storage Manager. The password must be changed first on the Tioli Storage Manager serer and then in the Data Protection for mysap.com product. 4. ADSMNODE must not be set when PASSWORDACCESS generate is set. 5. The users <SID>adm and sapserice<sid> must hae read and write permission for the path specified in the PASSWORDDIR keyword in the Tioli Storage Manager client options file. 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 archie operations. There are seeral products that can be used to set up a schedule, for example: SAP scheduler (CCMS) Tioli Storage Manager scheduler UNIX crontab / Windows scheduler The schedulers will be explained by means of examples below. 50 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

67 The scope of schedule control of the Tioli Storage Manager scheduler is at an enterprise leel, while the SAP scheduler or the UNIX crontab can only be used to set up schedules for the machines on which the mysap.com database is installed. SAP Scheduler Within mysap.com, the Computer Center Management System (CCMS) proides a scheduler for database administration and backup planning. The scheduler can be started from the SAPGUI command line using transaction code db13 or with the SAPGUI menu functions (Tools -> CCMS -> DB administration -> DBA scheduling). Tioli Storage Manager Scheduler The Tioli Storage Manager also proides functions for automating client operations by defining a new schedule or updating an existing schedule. Schedule definition work can be done quickly using the GUI based Tioli Storage Manager Web administratie client. When a schedule is defined, it will be assigned to a specific policy domain (more than one schedule for each policy domain can be defined). For this purpose, the mysap.com database client requires a schedule that can execute command files. The command files (for example shell scripts on UNIX) contain sequences of commands that are run at a scheduled start date and time. Information on how to define Tioli Storage Manager schedules can be found in the Tioli Storage Manager Administrator s Reference manual. UNIX crontab / Windows Scheduler Another possibility of backup automation is offered by the cron jobs for UNIX systems or schedule serices for Windows. UNIX cron jobs can be scheduled with the so-called crontab command, which inokes 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 E, Elements of Backup Schedules, on page 111) from Monday through Friday at 11:30 p.m. which will use the SAP database utility BRBACKUP to sae the mysap.com database. In this case, the entry in the crontab to start the script will be as follows: * * 1,2,3,4,5 /usr/bin/su - ora<sid> -c "/oracle/sid/sapscripts/backup.ksh" To start automated backup jobs on Windows systems, the schedule serice must be running. You can start this serice with the command: net start schedule If the schedule serice is running, jobs can be scheduled with the at command which can be used to inoke the batch file backup.cmd (the content of backup.cmd Chapter 5. Adjusting Your System 51

68 can be found in Elements of Backup Schedules for Windows on page 113). If you want to run this eery Friday at 8:00 p.m., the following command must be inoked: at 20:00 /eery:f cmd /c <drie>:\oracle\sid\sapscripts\backup.cmd Example of a Sequence of Daily Backup Runs The following figure illustrates the sequence of backup runs you should establish for a daily backup schedule. Figure 14. Production Backup Example This example of automated backup operations shows the following typical tasks Full database backup, e.g., offline or without application load, performed each night. Offline redo logs backed up to disk during online hours. This has the adantage of eliminating the need for extra tape mounts for relatiely small files. Note Backups can be performed to disks as well as to tape enironments. Tioli Storage Manager will manage the data regardless of the storage media. Howeer, it is recommended that the mysap.com database (data files) is directly backed up to tape. Offline redo logs are migrated (within Tioli Storage Manager) from disk to tape after the full database backup. SAP system files are backed up incrementally with the Tioli Storage Manager backup-archie client. The last backup in the daily cycle is the backup of the Tioli Storage Manager database. This should always be the case. 52 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

69 Actions used for Adjusting your System Following find a list of actions to be taken in order to adjust your Data Protection system components to your specific needs. The table shows the components to adjust and lists the possible actiities. Table 7. Oeriew of Actions for Adjusting your System Components mysap.com Database serer What to do Change settings in DP for mysap.com profile. See Settings for the mysap.com database serer on page 34 and Appendix B, The Data Protection for mysap.com Profile, on page 81. Network Use alternate/parallel sessions (see on page 85). Use multiple network paths (see Appendix A, Alternate/Parallel Backup Paths and Backup Serers, on page 75). Use no command (see Settings for Network Parameters on page 38). TSM Serer (Backup Serer) Use alternate/parallel sessions (see on page 85). TSM Enironment Use storage hierarchies (see on page 39). Use multiple TSM Serers (see on page 88). Customize configuration file (see Optimizing the Settings for the Tioli Storage Manager on page 40). Follow best practice sequence (see on page 40). Administration Assistant During the installation of DP a connection between DP and AA should be established High Aailability (HACMP) Automation Password If not specified during installation of DP, follow Specifying an Administration Assistant Serer on page 28. Define DP as application to HACMP Use SAP Scheduler, TSM Scheduler or Unix crontab resp. Windows Scheduler (see Scheduling Automated Backup Runs on page 50). Decide what method to use and follow steps described in Password Handling Methods on page 47. Chapter 5. Adjusting Your System 53

70 54 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

71 Chapter 6. Using Data Protection for mysap.com with RMAN You can use the Recoery Manager (RMAN) to do a backup, restore and recoer operation of an Oracle database. Furthermore, if you want to make incremental backups, this can only be done with RMAN. Note Check the Online Serice Support (OSS) system from SAP on how to set up backup ia RMAN on your operating system. Check also for special considerations for the database ersion you are using. Running with RMAN, Data Protection for mysap.com is loaded by one or more Oracle processes as shared library. These Oracle processes will then decide on how many parallel sessions are opened, when a session is opened and closed, which data object (e.g. table space) will be included into which session and more. Some of the aboe mentioned parameters must be configured for RMAN. Depending on how you are using RMAN you can configure these parameters either within the RMAN script or the BR*Tools configuration file (init<sid>.sap). If you want to use parallel sessions with RMAN make sure you configure at least the same number of sessions within the Data Protection configuration file as you configure for RMAN (see also item Parallel sessions on page 35 and item Parallel Serers on page 37). RMAN Setup on UNIX Systems Shared libraries hae different file extensions on different UNIX platforms. Within the following the section, the file extensions of shared libraries are represented as <ext>. Replace this text with the extension applying to your platform: Table 8. File Extensions for Shared Libraries Operating System AIX HP-UX Linux Solaris Extension a sl so so In the following description you hae to replace the directory name ora<bit> in the installation path. Depending on the ersion of Data Protection for mysap.com you hae installed, you must replace it with ora for the 32 bit ersion of Data Protection for mysap.com ora64 for the 64 bit ersion of Data Protection for mysap.com. To set up your Data Protection for mysap.com for use with RMAN under UNIX, follow these steps: 1. Install Tioli Storage Manager API Client on your mysap.com database serer (see Configuring of Tioli Storage Manager Clients on page 103). Copyright IBM Corp. 1995,

72 2. Install Data Protection for mysap.com on your mysap.com database serer (see Chapter 4, Installing or Upgrading Data Protection for mysap.com, on page 21). 3. Set Data Protection for mysap.com password for Tioli Storage Manager (see Password Handling Methods on page 47). 4. Ensure /usr/lib is in the library path enironment of your system. 5. Shut down the database and link the library shipped with Data Protection for mysap.com (libtdp_r3) with RMAN as follows: in case of Oracle 8.0 cd $ORACLE_HOME/rdbms/lib ln -s /usr/tioli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libobk.<ext> make -f ins_rdbms.mk ioracle LLIBMM=/usr/lib/libobk.<ext> in case of Oracle 8.1 cd $ORACLE_HOME/rdbms/lib ln -s /usr/tioli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libobk.<ext> make -f ins_rdbms.mk ioracle LLIBOBK=/usr/lib/libobk.<ext> in case of Oracle 9.2 cd $ORACLE_HOME/rdbms/lib ln -s /usr/tioli/tsm/tdp_r3/ora/libtdp_r3.<ext> /usr/lib/libobk.<ext> ln -s /usr/lib/libobk.<ext> $ORACLE_HOME/lib/libobk.<ext> make -f ins_rdbms.mk ioracle LLIBMM=/usr/lib/libobk.<ext> 6. Customize the SAP backup profile init<sid>.sap for use with RMAN. Insert the following: backup_de_type=rman_util rman_parms="env=(xint_profile=/<path>/init<sid>.utl,prole_port=portnumber)" The appropriate Prole port number can be found in the /etc/serices file. Further Hints 1. Ensure that Oracle has linked the right library /usr/lib/libobk.<ext> linked to /usr/tioli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> 2. Remoe 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 hae the same bitwidth as the installed Oracle ersion: if you hae a 64 bit Oracle running on AIX bit, you need to install the 64 bit ersion of Data Protection for mysap.com. If you hae a 32 bit Oracle running on a 64 bit AIX 5.1, you need to install the 32 bit ersion of Data Protection for mysap.com. Both ersions of Data Protection for mysap.com 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 ery first message for eery RMAN session looks like this: BKI7060I: Data Protection for 56 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

73 mysap.com (buildnumber) session:. If you cannot find any such message in the file, the library is not correctly linked with Oracle. 6. On HP-UX 11 64bit you need to add the string -lstd -lstream -lcsup to the existing line of the file $ORACLE_HOME/lib64/sysliblist and reissue the make command. A detailed description of the problem cause can be found at HPs website ( 7. Examine the dsierror.log located in the directory specified with the enironment ariable DSMI_LOG 8. To get a Tioli Storage Manager API trace file, set the following entries in the client system options file dsm.sys: tracefile /<path>/<trace file> traceflags api api_detail config policy 9. On UNIX operating systems, an additional softlink may help in /usr/lib for libtdp_r3.<ext>.1 to /usr/tioli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext>. ln -s /usr/tioli/tsm/tdp_r3/ora<bit>/libtdp_r3.<ext> /usr/lib/libtdp_r3.<ext> See also Appendix G, Troubleshooting, on page 131. RMAN Setup on Windows Systems To set up your Data Protection for mysap.com for use with RMAN under Windows, perform these steps: 1. Stop the serice OracleSerice<SID> 2. Install the Tioli Storage Manager API Client on your mysap.com database serer (see Configuring of Tioli Storage Manager Clients on page 103). 3. Install Data Protection for mysap.com on your mysap.com database serer (see Chapter 4, Installing or Upgrading Data Protection for mysap.com, on page 21). 4. Set the Data Protection for mysap.com password for Tioli Storage Manager (see Password Handling Methods on page 47). 5. Customize the SAP backup profile init<sid>.sap for use with RMAN. Insert the following: backup_de_type=rman_util rman_parms="env=(dsmi_dir=<drie>:\<path>, DSMI_CONFIG=<drie>:\<path>\<client options file>, DSMI_LOG=<drie>:\<path>\dsierror.log,XINT_PROFILE=<drie>:\<path>\init<SID>.utl, PROLE_PORT=portnumber)" The appropriate Prole port number can be found in the file <drie>:\winnt\system32\driers\etc\serices 6. Start the following serice: OracleSerice<SID> Further Hints 1. Examine the sbtio.log located in the directory specified in the user_dump_dest keyword within the Oracle profile init<sid>.ora. 2. If no file sbtio.log exists after an operation with RMAN or no line starting with the letters BKI exists within an existing sbtio.log, check if the shared library orasbt.dll was found and loaded by Oracle. Put the shared library file Chapter 6. RMAN Setup 57

74 orasbt.dll into the directory %ORACLE_HOME%\bin. This is the directory where oracle.exe resides. Now stop the serice OracleSerice<SID> and restart it. 3. Examine the dsierror.log located in the directory specified with the enironment ariable DSMI_LOG 4. To get a Tioli Storage Manager API trace file, set the following entries in the client options file: tracefile <drie>:\<path>\<trace file> traceflags api 5. See also Appendix G, Troubleshooting, on page Data Protection for mysap.com Technology Installation & User s Guide for Oracle

75 Chapter 7. Using Data Protection with the File Manager This section describes how to use the File Manager Data Protection for mysap.com File Manager The Data Protection for mysap.com File Manager is a utility that simplifies the Data Protection for mysap.com inquire, restore, and delete operations for the user. It can be seen as an add-on to Data Protection for mysap.com. Note Only users with a good knowledge about the restore and recoery mechanism of Oracle databases should use this tool. The general recommendation is that you should normally use the tools SAPDBA and BRRESTORE proided by SAP for restore operations. The Data Protection for mysap.com File Manager uses the standard functions proided by Data Protection for mysap.com to perform all operations. The Data Protection for mysap.com File Manager user interface consists of a split character based window. All backup IDs found on all Tioli Storage Manager serers which were configured within the Data Protection for mysap.com 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 indiidual backup IDs or multiple files for the restore or delete operations (see Figure 16 on page 60). The Data Protection for mysap.com File Manager has to be started with the path and name of the Data Protection for mysap.com profile (the user must be a member of the dba group). See the following examples. For UNIX systems: backfm -p /oracle/sid/dbs/init<sid>.utl For Windows systems: backfm -p <drie>:\orant\database\init<sid>.utl The Data Protection for mysap.com File Manager will now establish a connection to all Tioli Storage Manager serers which were configured in the Data Protection for mysap.com 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 Data Protection for mysap.com File Manager after haing finished an inquiry procedure. Copyright IBM Corp. 1995,

76 Figure 15. File Manager Result of an Inquiry Procedure If you mark the backup ID you are interested in and then press the Tab key to moe 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. Figure 16. File Manager Result of an Inquiry Procedure Showing File Names The following function keys are defined for performing restore or delete operations: Up, Down, Left, Right - Moe cursor Moe the highlighted cursor in the direction indicated on the key. 60 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

77 Tab - Switch window side Moe 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 ersion count, for more information see on page 85). For files, the Tioli Storage Manager expiration date and time is displayed. F8 - Delete Delete the selected backup ID and all corresponding files. This function is aailable only when the cursor is on top of a backup ID. F10 - Exit Exit from Data Protection for mysap.com File Manager ENTER - Mark/unmark file Mark or unmark the file below the cursor. To carry out restore or delete operations, the desired files first hae to be marked. This can be done either with the F3 function key to mark all the files that were found or with the ENTER key to mark only one desired file. Marked files can be identified by the symbol * in front of the filename. Only the marked files will be restored or deleted. Single backup IDs can also be deleted, in which case the selected backup ID and its corresponding files will be remoed from the Tioli Storage Manager serer. Chapter 7. Using Data Protection with the File Manager 61

78 62 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

79 Chapter 8. Using the Administration Assistant for Data Protection for mysap.com The Administration Assistant for Data Protection for mysap.com consists of a Web browser based graphical interface to support and assist the customizing of Data Protection for mysap.com and the analyzing of mysap.com database backup and restore operations. The Administration Assistant facilitates the configuration, monitoring, and administration of Data Protection for mysap.com from local or remote workstations. It gies mysap.com administrators the possibility of centralizing the database backup/restore administratie work, especially the monitoring of Data Protection for mysap.com and mysap.com database backup/restore actions from all mysap.com database serers within the system landscape. General A mysap.com system landscape in the real world typically unites more than one mysap.com system. At least one mysap.com test system and one mysap.com production system will be used together. A typical example of this is shown in Figure 17. Figure 17. Example of an mysap.com Landscape The central Administration Assistant instance is the Administration Assistant Serer, which can be installed on any system (UNIX or Windows). It acts as a data collector and data distributor. This means that it collects all incoming Copyright IBM Corp. 1995,

80 backup/restore dependent Administration Assistant data generated by the Data Protection for mysap.com background process Prole from the mysap.com database serer. This data will be distributed oer a network (LAN) to eery Administration Assistant Client node (user frontend, Web browser based) actually connected, and written to arious local files stored on the Administration Assistant Serer. These files sere as a data source for subsequent reiewing of performance/error analysis of backup/restore functions which hae been carried out. They can also hold arious Data Protection for mysap.com configuration states (Tioli Storage Manager configuration files, Data Protection for mysap.com profile, SAP backup profile) in form of a configuration history. The Administration Assistant can be understood to be a collection of four programs: System Configuration Performance Monitor Operations Monitor Problem Support The System Configuration Tool lets you customize the SAP backup profile, the Data Protection for mysap.com profile, and all the necessary Tioli Storage Manager files. Online documentation guides you through the customization process and gies you descriptions of the parameters and their alues. When you hae finished, you can copy the Data Protection for mysap.com profile to another Data Protection for mysap.com node. The Performance Monitor displays Data Protection for mysap.com performance information while Data Protection for mysap.com is performing a backup or restore operation. You can also display saed performance statistics when Data Protection for mysap.com is not actie. The Monitoring Tool runs on all platforms that support Data Protection for mysap.com. The Operations Monitor proides a centralized oeriew of backup status information for all mysap.com systems registered with the central Administration Assistant serer. The oeriew panel shows summaries of the backup status of an mysap.com system and the state of the current backup for eery system in your mysap.com system landscape. Detailed information about all backup runs on a specific mysap.com system can also be obtained. Problem Support allows sending support requests directly to a Tioli support center. Support requests can include user-specified problem descriptions. The tool automatically attempts to attach further information to the mail, such as configuration profiles and error logs. Prerequisites The following prerequisites are required before the Administration Assistant can be inoked: Data Protection for mysap.com must hae been installed successfully (see Chapter 4, Installing or Upgrading Data Protection for mysap.com, on page 21). 64 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

81 Jaa Runtime Enironment (JRE) ersion 1.3 or higher. To check the ersion of the installed Jaa software on UNIX or Windows, use the following command from a command line: jaa -ersion Not all endors proide the JRE separately. You can install the Jaa Deelopment Kit (JDK), because the JRE is part of the JDK. Contact the operating system endor to get the required JRE or JDK software. Additionally, the following two Jaa packages must be installed: Jaa Beans Actiation Framework (JAF) ersion 1.1 or higher. Jaa Mail or higher A fully Jaa 1.3-capable Web browser is required on the client machine (Jaa Plug-in 1.3 or higher must be installed). You can use Netscape Naigator Version 6.2 or higher or Microsoft Internet Explorer 5.5 or higher or Mozilla 1.1 or higher. For UNIX systems, the X Window system is required. For the Administration Assistant, a minimum screensize of 1024 x 768 has to be set. After ensuring that all these prerequisites are aailable, the installation process can commence. By subsequently starting the Administration Assistant you can erify the installation. Installation In this section we will discuss the installation and customization of the Administration Assistant. The installation process is subdiided into two parts: During the base installation of the Administration Assistant serer, the English ersion of the Administration Assistant serer is installed only. The NLS package, which contains all currently translated resources, can be installed at a later point in time. For the NLS package, the base installation is required. Installing the Administration Assistant Serer (Base Installation) To assist you with the installation procedure, the Administration Assistant package proides a setup assistant, a so-called installer that guides you through the installation process. Note It is necessary to hae system administrator priileges to install the Administration Assistant correctly. Both the base and NLS package of the Administration Assistant (base & NLS) are deliered as Jaa class files named install.class. Chapter 8. Administration Assistant 65

82 Note There is no need to set the enironment ariable CLASSPATH. Howeer, if this ariable is set in the system enironment, the directory where the file install.class resides must be included. For installation, perform the following 4 actiities: 1. jaa install 2. Only the name of the class file (install) has to be gien. If the JRE is installed only, you must use the command jre -cp. install 3. Now, the installer becomes actie. Follow the instructions proided on the panels of the installation tool. In the panel Specify ports (see Figure 18) it is important to: Check for free ports in the serices file (in most cases the gien alues are usable) Remember the specified ports for later use Figure 18. Administration Assistant Serer Setup (Base Installation) Specify Ports 66 Data Protection for mysap.com Technology Installation & User s Guide for Oracle

83 In the panel Correct Hostname, the host name of the Administration Assistant serer machine must be specified (or corrected) as shown in Figure 19. Figure 19. Administration Assistant Serer Setup (Base Installation): Correct Hostname Panel Remember The communication between the Administration Assistant serer and clients (Web browser or Jaa applet) will be done with Jaa RMI. An RMI communication requires a clear assignment between IP address and alias name for both of the communication clients inoled. Each of these clients must be capable of resoling the IP address of the other client to an alias name and ice ersa. If you use a DHCP serice on the Administration Assistant serer machine, it may be possible that this machine has two names. This would be a typical DHCP problem. A clearly defined host name of the Administration Assistant serer is a necessary prerequisite for subsequent communication between clients and this serer (serer configuration cannot be changed later). As a result of the aboe, the recommendation is to use a static IP address instead of one temporarily generated by DHCP. If you are using DHCP, be aware that in the case of a reboot of the Administration Assistant serer machine, this machine will be allocated a new IP address and the Administration Assistant will not be able to work. 4. On the panel Choose Destination Location, you hae to specify the destination directory to which the application will be installed as shown in Figure 20 on page 68. Chapter 8. Administration Assistant 67

84 Figure 20. Administration Assistant Serer Setup Destination Directory After this step, the installation is successfully completed. The system impact, after the setup process is finished successfully, is: On UNIX systems: Specification of a new entry in the /etc/inittab to start the Administration Assistant automatically (Adma:23:once:+sh "Install directory"/sadma.sh). The expression Install directory will be replaced with the real directory name specified during the setup process. If none was specified, the default installation directory /usr/lpp/bkit will be used. On Windows systems: A new serice. As a result, setup creates an entry in the Windows registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Serices with the name AdminAssistant. Installing the Administration Assistant NLS Package (optional) To install the Administration Assistant serer NLS extension you need to: Start the installer. Specifiy the directory where the base application has been installed. The installer will guide you through the rest of the installation process. After the setup process has finished successfully, do the following to ensure that the NLS extension works properly: On UNIX systems: Stop the current Administration Assistant serer process using kill <process ID> and restart it. On Windows systems: Stop the Administration Assistant Serice and restart it. Specifying a new Administration Assistant Serer for Data Protection for mysap.com If during the installation of Data Protection for mysap.com a connection to the Administration Assistant was not established, you need to create such a connection now. To do this, follow the actions described in Specifying an Administration Assistant Serer on page Data Protection for mysap.com Technology Installation & User s Guide for Oracle

85 Verifying the Installation A dedicated erification procedure for the Administration Assistant is not needed. To erify and test the installation, you can simply start the Administration Assistant and start working with it, for example, by authorizing the users. To start the Administration Assistant, enter its URL in the Location field of the Web browser (see Figure 21). Note that the host name of the Administration Assistant serer (see Figure 19 on page 67) and the port used for communication (see Figure 18 on page 66) must be separated by a colon. Figure 21. Starting the Administration Assistant with Netscape Each time a user starts the Administration Assistant, a Logon panel pops up for identification (see Figure 22). When the Administration Assistant is started for the first time, no user profiles for specific users are aailable. In this case, the initial account must be used. This account has the default user ID ADMIN and the password admin. (Note that these are case sensitie). Note When you log on to the Administration Assistant with the initial user ID, it is recommended that you change the password of that user immediately. Figure 22. Administration Assistant Start Panel Chapter 8. Administration Assistant 69