Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

Transcription

1 IBM Tioli Storage Manager for Hardware (5698-APH) Version Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle Version 1 Release 2.10 SC

2

3 IBM Tioli Storage Manager for Hardware (5698-APH) Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle Version 1 Release 2.10 SC

4 Note! Before using this information and the product it supports, be sure to read the general information under Notices on page xi. Fourth Edition (December 2003) This edition applies to Version 1 Release 2 Modification Leel 10 of Data Protection for IBM ESS for mysap.com Technology, Program Number 5698-ESR, 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 Schönaicher Str Böblingen 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 document 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 2001, 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 Summary of Changes xiii Preface x Who Should Read This Document x Where to Find More Information xi Contents of the DP for ESS Package xi Supported Platforms xi Naming Conentions xi Chapter 1. Introduction Understanding DP for ESS Operating Enironment Functions of DP for ESS Understanding the mysap.com Oracle Database Administration Tools Understanding Data Protection for mysap.com Technology Introducing Data Protection for mysap.com Technology Understanding the Administration Assistant for DP for mysap.com Understanding DP for mysap.com and the Tioli Storage Manager Serer Chapter 2. General Preparations for Installing DP for ESS Oeriew brbackup Part brbackup Part Oerall Disk Layout Considerations Specific Customization Requirements Profile Considerations Chapter 3. Installing and Customizing DP for ESS Installation Requirements Hardware Requirements Software Requirements Enironment Requirements General Installation Approach for the Required Products Other Steps Prior to Installing DP for ESS Setting Up the NFS File Systems Aspects of Using the IBM Subsystem Deice Drier (SDD) Setting Up ESS Source/Target Volumes Installing DP for ESS Customizing and Initializing DP for ESS Customizing the DP for ESS Profile Checking Enironment Variables Initializing DP for ESS Customizing the mysap.com DBA Tool Enironment Preparing for SQLNET Usage Customizing the mysap.com DBA Tool Profile 43 Uninstalling DP for ESS Chapter 4. Backup Methods Database Backups With ESS FlashCopy Sample Usage of brbackup Effectie FLASHCOPY_TYPE Value Using Backup Scripts Requirements for ESS Source/Target Volumes..53 Complete Database Backup Disk-Only Backup DP for mysap.com FCS_FILE Parameter...56 Database Backups Without FlashCopy Backup...56 Backups of the Offline Redo Logs How to Start the Backups Automated Backup Start ia Schedules Tioli Storage Manager Schedules UNIX crontab Backup Strategy and Automation Chapter 5. Restore Methods General Oeriew Restore/Recoery Method Using Tioli Storage Manager Backup Type Objects Using the mysap.com DBA Tools Using the DP for mysap.com File Manager...63 Restore/Recoery Method Using the FlashCopy Backup Type Objects with a FlashBack Restore..63 FlashBack Restore Complete Database Restore Implications of a FlashBack Restore Products Suited for Use for FlashBack Restore..65 Need for Pre- and Post-Restore Actiities...69 Role of the FCS_FILE Parameter for a FlashBack Restore Restore/Recoery Steps Important Information for Profiles FlashBack Restore Considerations What is FlashBack Restore? Why Use FlashBack Restore? When Not to Use FlashBack Restore FlashBack Restore Limitations Understanding the Limitations Description of FlashBack Restore Limitations..79 FlashBack Restore Rerun Capabilities What is a FlashBack Restore Rerun? Conditions for a FlashBack Restore Rerun...83 Copyright IBM Corp. 2001, 2003 iii

6 Reasons for a FlashBack Restore Rerun FlashBack Restore Rerun Limitations Sample FlashBack Restore Scenarios Scenario Descriptions Chapter 6. Description and Usage of the DP for ESS Commands Functions of the DP for ESS Command splitint 97 Split Function Description Usage Syntax Resync Function Description Usage Syntax Withdraw Function Description Usage Syntax Unmount Function Description Usage Syntax Flashback Function Description Usage Syntax Inquire Function Description Usage Syntax Password Function Description Usage Syntax Query Function Description Usage Syntax Summary of splitint Functions Command Options Summary DP for ESS Command tdpessora Description Usage Syntax Backup and Restore Cycles Backup Cycle Restore Cycle Common Information for the Backup and Restore Cycles DP for ESS FlashCopy Agent PSI (Progress Status Indicator) BSI (Backup Status Indicator) RSI (Restore Status Indicator) Chapter 7. The DP for ESS Profile (.fcs) Location and Naming Conentions Structure of the DP for ESS Profile Parameters of the DP for ESS Profile Structure of the DP for ESS Target Volumes File 138 Parameters of the DP for ESS Target Volumes File 138 Chapter 8. DP for ESS Functionality for AIX LVM Mirrored Enironments Oeriew Adantages of the Special Handling of AIX LVM Mirrored Enironments Functional Oeriew FlashCopy Backup Process FlashBack Restore Process DP for ESS and Copy Sets in an AIX LVM Mirror Enironment Supported AIX LVM Mirrored Enironments and DP for ESS Symmetrical Enironment Asymmetrical Enironment Requirements for Proper Setup and Customization with AIX LVM Mirrors Copy Set Parameter DP for ESS Parameters Needed for FlashBack Restore Structure of the DP for ESS Target Volumes File 153 Parameters of the DP for ESS Target Volumes File 154 Sample Using the DP for ESS Functionality for AIX LVM Mirrored Enironments Using the DP for ESS Commands for Backups (Sample) Running the FlashBack Restore/Recoery (Sample) DP for ESS Files Used for the Preceding Backup and Restore/Recoery Commands (Sample) AIX LVM Mirror/Copy Examples Example 1: Ideal Configuration, Symmetrical Setup Example 2: Symmetrical Configuration with Stale Physical Partitions in One ESS Unit Example 3: Symmetrical Configuration with Stale Physical Partitions in Both ESS Units Example 4: Asymmetrical Configuration with Insufficient Target Volumes Example 5: Asymmetrical Configuration with Sufficient Target Volumes Example 6: Asymmetrical Configuration with Sufficient Target Volumes But Stale Physical Partitions Example 7: Symmetrical Configuration with LVs (Different Mirror Numbers) in the Same ESS Appendix A. Samples Sample of an Oerall Disk Layout Sample NFS Serer Setup on the Production System Sample NFS Client Setup on the Backup System 171 Sample Tioli Storage Manager Client Options Files Sample Client User Options File (dsm.opt) Sample Client System Options File (dsm.sys) 172 Include/Exclude List Sample i Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

7 Sample DP for mysap.com Profile Sample DP for ESS Profile Sample DP for ESS Target Volumes File Sample DP for ESS Target Volumes File (Mirror Setup) Sample mysap.com DBA Tool Profile Sample of tnsnames.ora Sample of listener.ora Sample DP for mysap.com Installation and Customization Sample DP for ESS Installation and Customization 192 Sample R/3 Installation and Customization Sample splitint Usage Case 1: Backup with Target Withdrawal in brbackup Run Case 2: Backup without Subsequent Unmount or Withdraw Case 3: Backup with Delayed Withdrawal Outside brbackup Run Case 4: Backup with Unmounting of File Systems or Withdraw in brbackup Run Case 5: Backup With Unmount Case 6: Setup Test with the Query Function Case 7: Disk-Only Backup With Delayed Withdrawal Outside brbackup Run (Positie Example) Case 8: Disk-Only Backup and ESS INCR/COPY Backup Run (Negatie Example). 206 Case 9: Disk-Only and ESS Incremental Backup Run (Positie Example) Sample brbackup FlashCopy Shell Script DP for ESS (Oracle) Messages Appendix C. Summary of Log and Trace Files mysap.com DBA Tool Logs (brbackup/brarchie/brrestore) DP for ESS Logs and Traces IBM Enterprise Storage Serer DP for mysap.com AIX Operating System Appendix D. Scripts Supporting FlashBack Restore PreRestore.sh PostRestore.sh Appendix E. Migration from Preious DP for ESS Releases Check Backup Cycle Perform Enironmental Changes Upgrade Interfacing Products Adjust Profiles and Backup Commands/Scripts 248 Appendix F. Special Recoery Procedures Restore/Recoery after Tablespace Extension (Current DB Control Files Aailable): Case Restore/Recoery after Tablespace Extension (Current DB Control Files Aailable): Case Appendix B. Data Protection for IBM ESS for mysap.com Technology (Oracle) Messages Glossary Index Contents

8 i Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

9 Figures 1. Oerall DP for ESS Enironment Flow of Flashcopy/Backup/Withdraw Operations Oeriew of DP for mysap.com Oeriew of the Backup Scenario Control File/Profile Relationships Without DP for ESS Control File/Profile Relationships With DP for ESS Example of an InstallShield panel Offline_Mirror Backup with 2 Volume Groups (VG1 and VG2) Online_Mirror Backup with 2 Volume Groups (VG1 and VG2) Oeriew of Tools for FlashBack Restore Restore/Recoery Actiities with FlashBack Restore DP for ESS and Copy Sets in an AIX LVM Mirror Enironment for Oracle Ideal Configuration, Symmetrical Setup Symmetrical Configuration with Stale Physical Partitions in One ESS Unit Symmetrical Configuration with Stale Physical Partitions in Both ESS Units Asymmetrical Configuration with Insufficient Target Volumes Asymmetrical Configuration with Sufficient Target Volumes Asymmetrical Configuration with Sufficient Target Volumes But Stale PP(s) Symmetrical Configuration with LVs (Different Mirror Numbers) in the Same ESS Disk Layout Used in Sample Installation smitty Panel for Exporting Directories smitty Panel For Mounting NFS Files 171 Copyright IBM Corp. 2001, 2003 ii

10 iii Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

11 Tables 1. Related Publications x 2. Effectie FLASHCOPY_TYPE Value Determination Summary of Function Usage for DP for ESS Command splitint Combinations of Backup Type Status (Tioli Storage Manager and FlashCopy) as Reported by tdpessora Splitint Actions Required to Reset the Backup Cycle Possible Progress Status Indicator (PSI) Values Possible Backup Status Indicator (BSI) Values Possible Restore Status Indicator (RSI) Values DP for ESS Profile Parameters ( global Topic) DP for ESS Profile Parameters ( shark_data Topic) Parameters of the shark_olumes_set_1 Topic Parameters of the DP for ESS target olumes file for AIX LVM mirrored enironments Adjustments Required when Migrating to DP for ESS Copyright IBM Corp. 2001, 2003 ix

12 x Data Protection for IBM ESS for mysap.com Technology Installation and 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 Enterprise Storage Serer FlashCopy IBM RS/6000 Tioli Copyright IBM Corp. 2001, 2003 xi

14 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. 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. xii Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

15 Summary of Changes The following new functionality has been added to ersion of DP for ESS for mysap.com Technology for Oracle (hereafter DP for ESS ): Support for the SAP SPLITINT Interface for Oracle. The older Split Mirror Backup interface and the Shortened Backup Processing Feature (SBPF) are no longer supported. The functionality of both is integrated into the new interface, and the DP for ESS program idscntl has therefore been renamed to splitint. Note: For existing installations upgrading to DP for ESS : In conjunction with the aboe program name change, the parameters split_cmd and resync_cmd hae effectiely been deleted and two new parameters, split_options and split_resync, hae been introduced. The required migration associated with these changes is described in Appendix E, Migration from Preious DP for ESS Releases, on page 247. Support for FlashCopy restore (also known as FlashBack Restore). To support the FlashBack Restore, a new FCS_FILE parameter has been introduced for DP for mysap.com. Employ selected FlashCopy V2 functionality: incremental FlashCopy (see Incremental FlashCopy Backup and Restore on page 6 FlashCopy across different logical subsystems (eliminates an ESS olume setup restriction) Existing functionality has been changed ( unmount function) and extended with the new split (formerly flashcopy ) and resync functions. Additional changes: A capability for a diskonly FlashCopy Backup is proided. Added a new command (tdpessora) to proide information for the restore/recoery process. Increased the range of supported platforms to include AIX 5.2, and deleted AIX as a supported platform. Added a paragraph listing enironments that are not supported (see Enironment Requirements on page 31). Changes in setup requirements: all olume groups of the production system containing ESS olumes must be set up with paths if SDD is installed (see Aspects of Using the IBM Subsystem Deice Drier (SDD) on page 35). Samples in the appendixes hae been added or modified as follows: Sample splitint (formerly idscntl) usage, cases 1 to 6 (modified) Sample splitint usage, cases 7 to 9 (new) PreRestore.sh (new) PostRestore.sh (new) This reision also includes maintenance and editorial changes. Technical changes or additions to the text and illustrations are indicated by a ertical bar to the left of the change. Copyright IBM Corp. 2001, 2003 xiii

16 xi Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

17 Preface Who Should Read This Document This manual is intended for system programmers and administrators who are responsible for implementing a backup solution in the mysap.com Technology 1 enironment using Data Protection for IBM ESS for mysap.com Technology (hereafter referred to as DP for ESS). It proides information to install, configure, and administer DP for ESS with Oracle databases. In this publication, it is assumed that you hae an understanding of the following: UNIX operating system IBM ESS storage subsystem AIX operating system and its Logical Volume Manager (LVM) R/3 DBA tools for Oracle DBMS and mysap.com Technology DBA tools Oracle database administration Data Protection for R/3 and Data Protection for mysap.com Technology Tioli Storage Manager Backup-Archie Client Tioli Storage Manager Application Program Interface The following publications proide additional information. Table 1. Related Publications Title Order Number Tioli Storage Manager for AIX Administrator s Guide V.5.2 GC Tioli Storage Manager for AIX Administrator s Reference V.5.2 GC Tioli Storage Manager Messages V.5.2 GC Tioli Storage Manager Using the Application Program Interface GC V.5.2 Tioli Storage Manager for UNIX Backup-Archie Clients GC Installation and User s Guide V.5.2 Data Protection for mysap.com Technology Installation and SC User s Guide for Oracle BC SAP Database Administration: Oracle Aailable from SAP AG BC-BRS SPLITINT Interface for Oracle Databases Aailable from SAP AG Split Mirror Backup Procedure (used prior to DP for ESS Aailable from SAP AG ). IDES Installation Release 4.6C Aailable from SAP AG R/3 Installation on UNIX Oracle Database Aailable from SAP AG R/3 Data Management Techniques Using Tioli Storage Manager IBM Total Storage Enterprise Storage Serer: Implementing CopySerices in an Open Enironment User s Guide, 2105 Models E10, E20, F10, and F20 Tioli Redbook SG SG SC In older releases/documentation, the term SAP R/3 is used. Copyright IBM Corp. 2001, 2003 x

18 Table 1. Related Publications (continued) Title IBM Subsystem Deice Drier Installation and User s Guide Order Number Online manual (see link under Aspects of Using the IBM Subsystem Deice Drier (SDD) on page 35). Where to Find More Information For more information about DP for ESS and the latest fixes, please refer to the home page at Contents of the DP for ESS Package The DP for ESS package includes this manual and machine readable material on a CD-ROM. See the README file for: A table of contents of the package Up-to-date news Supported Platforms The following platforms are supported: AIX /64 bit AIX /64 bit See the README file for the latest information on additionally supported platforms. Naming Conentions Data Protection for IBM ESS for mysap.com Technology is abbreiated in this document as DP for ESS. Data Protection for mysap.com Technology is abbreiated in this document as DP for mysap.com. mysap.com Technology is abbreiated in this document as mysap.com. The following files are often referred to simply by their extensions: mysap.com DBA profile (.sap) DP for ESS profile (.fcs) DP for ESS target olumes file (.fct) DP for ESS configuration file (.fcp) DP for mysap.com profile (.utl) DP for mysap.com configuration file (.bki) By conention, modified ersions of these files to sere specific purposes are distinguished by a suffix to the extension, such as.fcsc, and not to the base name. xi Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

19 Chapter 1. Introduction Understanding DP for ESS Data Protection for IBM ESS for mysap.com Technology (hereafter DP for ESS) minimizes the impact on mysap.com Oracle database serers while allowing automated database backups to the Tioli Storage Manager Serer. Integrated in the mysap.com DBA tools 2, DP for ESS off-loads the transfer of backup data from the database serer. The Oracle database must reside on an ESS storage subsystem. DP for ESS V1R1 proides options to implement high-efficiency backup and restore of business-critical databases, while irtually eliminating backup-related downtime or user disruption on the production host and significantly reducing database restore time. This section describes the operating enironment and functions of DP for ESS. Operating Enironment The operating enironment consists of the Oracle DBMS executing on an AIX serer attached to an IBM Enterprise Storage Serer (ESS). This AIX serer is the production system. Another AIX serer, the backup system, is also attached to the same ESS to back up ESS FlashCopy copies of the production system to the Tioli Storage Manager serer. This is done by the concerted action of the programs of the products mysap.com DBA tool (brbackup), DP for ESS (splitint), and Data Protection for mysap.com Technology (backint/prole). As of DP for ESS ersion and DP for mysap.com (3.3.10), it is possible to: suppress the backup of the files on the FlashCopy disk copies to the Tioli Storage Manager serer (disk-only backup) in order to accelerate the backup process allow a restore from the FlashCopy copies to the database disks of the production system (FlashBack Restore) To facilitate the control of disk-copy backups as well as the restore of disk copies with DP for ESS , a new component (tdpessora) and sample scripts (PreRestore.sh and PostRestore.sh) hae been introduced. DP for ESS requires Data Protection for mysap.com Technology (hereafter DP for mysap.com) in order to perform the actual backup or restore to or from the Tioli Storage Manager serer call DP for ESS for a Flashback Restore. The following figure depicts the hardware and software enironment in which DP for ESS operates. 2. Often referred to as the SAP DBA tools, or BR*Tools. Copyright IBM Corp. 2001,

20 Figure 1. Oerall DP for ESS Enironment The products and hardware elements shown in Figure 1 hae to be aailable on the production and backup systems. Prior to any inolement of DP for ESS, the production system will hae access to the Oracle DB running the mysap.com application transactions. The backup system at this time will hae the software products installed but no access to any Oracle DB files. Role of brbackup 2 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

21 Once brbackup (on the backup system ) has been started with the parameters to do a FlashCopy, it will first interact with the Oracle DB on the production system ia SQLNET to get the Oracle DB information and then call DP for ESS, which, with its components (CORE, IDS, and LVM), will ensure that brbackup will get all the olumes (IBM ESS target olumes) with the files brbackup needs to run a full Oracle DB backup. brbackup will also ensure the backup of certain profiles and control files of the production system that will be accessed on the backup system ia NFS. When performing the backup, brbackup will call DP for mysap.com to perform the actual backup. brbackup normally runs as a batch job; howeer, as with other SAP DBA tools, it can also be called as a function within the interactie tool sapdba. Restore of a complete DB will be done interactiely by running brrestore on the production system, which will call DP for mysap.com (backint) to interface with DP for ESS, calling the flashback function if requested. Role of splitint The split function of splitint can be used by brbackup for FlashCopy operations; there are other functions (such as unmount, withdraw, password, and inquire) that can be requested when calling splitint as a command not under control of brbackup. Optionally, after the call for the backup has completed, brbackup can call the resync function of splitint to perform resynchronization. splitint is structured in 3 component layers: CORE, LVM, and IDS. The CORE component has the following tasks: acts as a direct interface to brbackup reads/checks the DP for ESS profile performs enironment checks performs housekeeping functions for handling temporary and permanent files containing information for the other components used in the arious stages in one functional run or in subsequent functional runs (these files will reside in NFS directories) creating/deleting log and trace files (these files will reside in NFS directories) controls the proper sequence of functions (split, unmount, and withdraw); for details, see Backup and Restore Cycles on page 121 interacts with the LVM and IDS components to exchange information ia rexec, runs/controls an splitint instance on the production system wheneer a FlashCopy is required (see brbackup and its split_options profile statement, pointing to the DP for ESS profile). The IDS component has the following tasks: interacts with the primary ESS Copy Serices serer ia a TCP connection, using the ESS Copy Serices CLI, to gather information about source and target olumes issue the FlashCopy/withdraw requests to the primary ESS Copy Serices serer returns the status of its performed tasks to CORE for controlling and reporting purposes. Chapter 1. Introduction 3

22 The LVM component performs the following tasks interacts with the operating system to gather information about the olumes and file systems of the Oracle DB files planned for use in a later step by brbackup for which backup is requested proides, on the backup system, resources such as olume groups and file systems such that files can be read in the succeeding backup call. optionally (when the brbackup profile parameter split_resync=yes is set), runs the resynchronization to remoe the system resources receied aboe (unmount file systems and export olume groups), and withdraw the relationship between the ESS source and target olumes if the effectie FLASHCOPY_TYPE was NOCOPY. Use of TCP/IP TCP/IP will be used by splitint when it is running an rexec from the backup system on the production system to perform the actual ESS Flashcopy creating/reading/writing its log, trace, and temporary files in NFS directories brbackup when creating/writing its run log files (normally in the /oracle/<sid>/sapbackup directory reading its profile (normally located in the $ORACLE_HOME/dbs directory) DP for mysap.com when requested by brbackup to back up certain control files, profiles and log files reading/updating its profile (.utl) and configuration file (.bki). At product installation time, all these files must reside in NFS directories so that the SAP DBA tools sapdba, brbackup, and brrestore, and DP for mysap.com and DP for ESS can access the files depending on the function they must perform at the time: sapdba/brrestore when restoring the DB files from the Tioli Storage Manager serer to the production system; in the interest of a fast restore, high-speed connections are required. Note: sapdba cannot be used to request DP for ESS to run a disk (ESS target olume) restore. brarchie when backing up/restoring the redo log files between the production system and Tioli Storage Manager serer. See Software Requirements on page 31 for a detailed list of applications required by DP for ESS. Functions of DP for ESS This section proides an oeriew of DP for ESS functions. DP for ESS proides certain inherent functions, referred to as actie functions. As an agent operating in conjunction with mysap.com DBA tool brbackup and DP for mysap.com, it also proides additional, passie functions: Actie functions High-aailability Oracle database backup using ESS FlashCopy deices 4 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

23 Integration with mysap.com DBA backup tool (brbackup) functions to support running ESS Copy Serices functions (FlashCopy 3, withdraw, etc.) Keep the progress of the DP for ESS functions in a housekeeping file to monitor the proper sequential usage of the functions. Send information to the DP for mysap.com Administration Assistant while DP for ESS is running Quick Oracle database restore using the ESS FlashCopy deices Passie functions Seamless augmentation of the functions of DP for mysap.com. Centrally administered and scheduled backup operations Integration with Tioli Storage Manager Media Management functions When first introduced, DP for ESS was primarily designed based on the requirements of the SAP split-mirror architecture. This allowed brbackup and idscntl (the predecessor of splitint) to create FlashCopy copies and the files with those copies to be backed up to a Tioli Storage Manager serer. The lack of an interface in this architecture for restoring the FlashCopy copies back to the database disks of the production system has been resoled with an interface between DP for mysap.com (starting with ersion ) and DP for ESS with splitint (starting with ersion ). High-Aailability Oracle Database Backup Using ESS Flashcopy Volumes DP for ESS accomplishes high-aailability backup of an Oracle database on an Enterprise Storage Serer by using FlashCopy deices. DP for ESS, a co-product of DP for mysap.com, integrates with the Enterprise Storage Serer FlashCopy olumes to allow the high-performance, database-aware FlashCopy backups of Oracle databases on a secondary host machine (also referred to in this document as the backup system) while the production application remains online and fully aailable to users. While DP for ESS initiates the FlashCopy operation, creating target olumes from the source olumes of the production database and making target olumes and file systems on the secondary host machine (backup system) aailable, DP for mysap.com can back up the FlashCopy olumes there. Because the backup operation is conducted from the FlashCopy disk copy (target olumes) 4, most processing occurs on the backup system. As a result, the inaccessibility of the production database is minimized and the production host continues to dedicate processor time to the production database. This greatly reduces any performance impact on the production database serer. DP for ESS works on requests (split and, optionally, resync, which will result in an ESS FlashCopy and optionally unmount/withdraw) from the mysap.com DBA tool brbackup. The actual backup is done by DP for mysap.com, again on request (backup) of the mysap.com DBA tool brbackup. In R/3 and mysap.com documentation, the term split-mirror backup is used to request a FlashCopy disk copy within a storage subsystem, which can later be used for the back up as described aboe. Such a split_mirror backup (hereafter also referred to as a FlashCopy backup) can, as a result, create: 3. Using the NOCOPY, COPY, or INCR functionality. 4. In the mysap.com and R/3 documentation, this copy is referred to as a split-mirror copy. Chapter 1. Introduction 5

24 2 complete backup sets, one as a disk copy (on ESS target olumes) and one copy on tape in the Tioli Storage Manager serer, or 1 complete backup set, either as a disk copy only or on tape in the Tioli Storage Manager serer For details, see Chapter 4, Backup Methods, on page 47. Should a restore/recoery be required, this must be done on the production system with the mysap.com DBA tool sapdba/brrestore, which will call DP for mysap.com. DP for mysap.com will restore the data from the Tioli Storage Manager ia the LAN or, if requested, call the DP for ESS flashback function to restore the disk copy. Note: If you plan to restore the disk copy, only brrestore should be used (see Chapter 5, Restore Methods, on page 61 for details). High-Aailability Oracle Database Restore Using ESS FlashCopy DP for ESS accomplishes high-aailability restores of an Oracle database on an Enterprise Storage Serer by using ESS FlashCopy deices. The program uses the ESS FlashCopy olumes of a preiously taken FlashCopy Backup to allow the high-perfoce, database-aware FlashCopy Restore of Oracle databases on the production system in case of production system failure. While DP for ESS initiates the FlashCopy Restore operation, the production system will be cleaned up (all DB file systems will be unmounted, all DB olume groups will be exported). After the cleanup, splitint will initiate the FlashCopy from the target olumes (from a preiously taken FlashCopy backup) to the production system source olumes. Then, all DB olume groups will be imported and all DB file systems re-mounted. The DB recoery and production work need not wait for the completion of the ESS background copy initiated by DP for ESS. This greatly reduces the downtime of the production database serer. Depending on the installed ESS microcode leel, an ESS FlashCopy with COPY or INCR (incremental) will be used for the restore (see Installation Requirements on page 29 for details). Incremental FlashCopy Backup and Restore DP for ESS now allows controlled disk-copy backups of an Oracle database using the Enterprise Storage Serer Incremental FlashCopy feature. This feature makes it possible to perform a background copy between the ESS source and target olumes without haing to copy all the tracks in the process. This results in improed perfoce for the Oracle Serers that are configured to the ESS. Incremental FlashCopy applies only to the storage hardware leel copy (the FlashCopy made between the ESS source and target olumes). It does not apply to the application leel copy (the backup copy of the database to the Tioli Storage Manager Serer). An incremental FlashCopy (see RMAN interface on page 16) cannot be performed when the entire Oracle database is backed up to the Tioli Storage Manager Serer. An incremental FlashCopy backup is inoked with the alue INCR for the FLASHCOPY_TYPE in the DP for ESS profile (.fcs). For more information, see Effectie FLASHCOPY_TYPE Value on page Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

25 Integration with mysap.com DBA Backup Tool (brbackup) Functions DP for ESS proides a set of necessary functions to prepare the enironment on the backup host for a backup of primarily the database files of the production system. Such a backup (online or offline) must be started on the backup system by using the mysap.com DBA tool brbackup. 5 With , DP for ESS utilitzes a new functionality of the mysap.com DBA tool brbackup that is based on the extended SPLITINT Architecture of SAP. This functionality allows significantly shorter backup windows on the production system. Note: DP for ESS or higher will no longer support the SBPF (Shortened Backup Processing Feature), which also helped to reduce the backup window time. This feature, howeer, was based on an interim and undocumented SAP DBA split mirror interface that will be withdrawn by SAP starting in It has been integrated into the new extended SPLITINT architecture. In order to start the FlashCopy backup on the backup system, enter either: brbackup -t offline_mirror... or brbackup -t online_mirror... using a customized mysap.com DBA profile as laid out in Customizing the mysap.com DBA Tool Profile on page 43. Once such a brbackup request is started, it will essentially: determine the layout of the database running on the production system (tablespace files, DB control files, and, in case of an offline backup, online redo log files) call the split function of splitint (DP for ESS) to create disk copies of the DB olumes on the production system and make them aailable on the backup system. call the backup (part 1) function to back up, using backint (DP for mysap.com), the database files from the disk copies to the Tioli Storage Manager serer. This backup can be suppressed if the disk-only parameter (-d) is specified in the split_options statement. call backint (DP for mysap.com) again (part 2) to back up certain profiles and run logs to the Tioli Storage Manager serer optionally (if split_resync=yes is specified in the mysap.com DBA profile), perform resynchronizaiton tasks by calling splitint again to either perform the splitint unmount function (to unmount file systems and ary off the VGs) if the effectie FLASHCOPY_TYPE was INCR or COPY, so that the disk copy on the ESS olumes can be used in a subsequent FlashBack Restore, or perform the splitint withdraw function (which includes the splitint unmount functionality and withdraw the ESS source/target relationship, if the effectie FLASHCOPY_TYPE was NOCOPY. 5. This is a component of the mysap.com DBA toolset, which also includes sapdba, brarchie, and brrestore. Chapter 1. Introduction 7

26 Detailed information about the use of the arious DP for ESS profile parameters, the DP for ESS diskonly (-d) parameter, and the effectie FLASHCOPY_TYPE is gien in Database Backups With ESS FlashCopy on page 47. The DBA can use tdpessora (DP for ESS) to check on the aailability of backups that were done with brbackup. The following figure depicts the interactions of the arious products on the production/backup systems the flow of the arious program calls: brbackup-initiated calls calls by brbackup-initiated programs to other programs; this also includes the exchange of information ia generated files, etc.) Figure 2. Flow of Flashcopy/Backup/Withdraw Operations 8 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

27 A complete backup cycle 6 of a brbackup backup request, customized to run FlashCopy backups, comprises the following steps: 1. Using an Oracle client for an Oracle remote connection, determine all tablespace files that make up the Oracle database on the production system and enter the names in a list. Add all DB control files, and in the case of an offline backup also the online redo log files, to the file list. 2. Get olume and file system information from the list created in step 1 using the DP for ESS program splitint. In order to do this, the work items listed below will be performed: a. The following steps are performed by splitint on the backup system: read the DP for ESS profile check whether the latest backup cycle has reached a state which allows a new backup cycle to be started; at least an unmount state is required. If not, force termination of brbackup (RC > 0). Check the RSI (Restore Status Indicator). If the alue is RSI_START: terminate (an ESS FlashCopy for a preious FlashBack Restore has not yet completed) RSI_INVALID: issue a warning, reset the RSI, and continue anything else: continue create a new backup cycle start an rexec splitint on the production system with the list receied from brbackup and continually check the information that splitint returns. b. The following steps are now performed by splitint on the production system: for each file in the file list, determine its corresponding disks (source olumes), using DP for ESS LVM routines. look for a suitable target olume (specified in the DP for ESS profile). If the size of the source olume does not match a counterpart target olume, the FlashCopy request to the primary Copy Serices serer located within an ESS cluster will not be initiated. create an exchange file (with olume/mountpoint information), which is used later on the backup system. 3. Request the database to be set to backup mode; this will be propagated through to brbackup on the backup system, which will either initiate the database shutdown, in case of an offine_mirror backup, or set all tablespaces into BEGIN BACKUP mode, in case of an online_mirror backup. When the backup mode is established, brbackup signals splitint on the backup system that the database is now ready for a (FlashCopy) backup, which in turn starts splitint again on the production system. 4. Request the FlashCopy of the database olumes (source/target) by calling the DP for ESS program splitint. a. The following steps are performed by splitint on the production system: 1) reset the BSI (Backup Status Indicator) to BSI_START 2) prior to the FlashCopy, flush buffered data 3) set the current backup cycle to the FlashCopy state 6. A backup cycle needs to be completed in order to start a new brbackup request. Chapter 1. Introduction 9

28 4) generate, from the database olumes of the production system, an image copy 7 from the source to the target olumes 5) terminate execution on the production system b. Only if the effectie FLASHCOPY_TYPE is set to COPY or INCR, initiate the DP for ESS FlashCopy agent (fc_agent) on the backup system to monitor the FlashCopy progress in the ESS periodically and record the result in the DP for ESS FlashCopy agent log file. More information on the DP for ESS FlashCopy agent and the BSI can be found in the section Backup and Restore Cycles on page Request the Oracle database on the production system to be reset to the DB state it was in prior to the backup run. This will either start the database again, in case of an offline_mirror backup set all the tablespaces into END BACKUP, in case of an online_mirror backup Check the RC for 0 and terminate it not Mount the disks (target olumes) on the backup system after an image copy (FlashCopy) is aailable, with the following actions: a. Check whether the actions on the production system were successful. If not, force termination of brbackup (RC > 0). b. Ealuate the exchange file and, based on the information found therein, import olume groups, run fsck, and mount file systems. c. Set the current backup cycle entry to the mount state (PSI_MOUNT_DONE). d. Return control to brbackup with RC 0 if the FlashCopy/mount was successful. 7. Perform the backup of the Oracle database to the Tioli Storage Manager Serer (backup part 1). brbackup calls backint (DP for mysap.com) for this purpose. In addition, brbackup informs DP for ESS (splitint) about the backup ID used and successful completion of the backup to the Tioli Storage Manager serer. It also proides information about the DP for ESS profile used (.fcs) and the one specified with the FCS_FILE parameter in the DP for mysap.com profile. Note: If the disk-only parameter was set (split_options =... -d... ), DP for mysap.com will suppress the backup to the Tioli Storage Manager serer. Howeer, due to the existence of the disk copies, it will signal to brbackup that the backup was successful. With a second backup call (backup part 2), request DP for mysap.com to back up a number of log and control files (which are shared between the two systems). 8. Optionally, request to perform resynchronization 8 work. brbackup calls splitint -f resync if split_resync=yes is specified in the brbackup profile. The status of the current backup cycle will be set to PSI_UNMOUNT_DONE or PSI_WITHDRAW_DONE. 7. Call the CLI to initiate the work in the ESS needed to coer a NOCOPY, COPY, or INCR request. 8. This is an SAP term. The actual work content in the DP for ESS enironment is more properly referred to as cleanup actiity. The term cleanup will be therefore also be used in the remainder of this document.. 10 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

29 When called by brbackup, the DP for ESS splitint -f resync function will perform the following depending on the effectie FLASHCOPY_TYPE used in the brbackup request: in case FLASHCOPY_TYPE COPY or INCR was used, run a splitint -f unmount to unmount all file systems used ary off and export all olume groups used set the PSI for the backup cycle to PSI_UNMOUNT_DONE Note: The target olumes of this backup are in a safe state, such that the data on the olumes cannot be intentionally or accidentally changed 9. The target olumes can be used for a FlashBack Restore (once the fc_agent detects that the FlashCopy tasks running in the ESS hae completed the disk copy operation. Use tdpessora to erify the FlashCopy status ok. 10 in case FLASHCOPY_TYPE NOCOPY was used, run a splitint -f withdraw to unmount all file systems used ary off and export all olume groups used withdraw the ESS source/target relationship set the PSI for the backup cycle to PSI_WITHDRAW_DONE. In either case, the backup system sees a completed backup cycle, which allows a new brbackup to be started. Note: Instead of the split_resync=yes functionality, you might prefer to run a script as shown in Sample splitint Usage on page 199. Integration with mysap.com Restore Tool (brrestore) Functions As of , DP for ESS proides the capability to restore ESS target olumes, which were created in the DP for ESS FlashCopy backup, to the original ESS source olumes. This process is referred to as a FlashBack Restore. In contrast to the FlashCopy backup, all database restore actiities with DP for ESS need to be started on the production system. When DP for ESS is called for a restore by brrestore (preferred) or backfm, splitint interactiely works together with DP for mysap.com (backint) in order to proide information as to which backup leels are aailable for a restore prompt the administrator as to which backup leel and which backup type (if aailable) to select for a restore. Possible types are Tioli Storage Manager and FlashCopy. restore and recoer, based on the alues entered by the administrator A backup leel will be shown by DP for ESS as a FlashCopy type if all of the following conditions hae been met: the backup was done using DP for ESS using the FlashCopy backup function the FlashCopy backup was done with the effectie DP for ESS profile parameter FLASHCOPY_TYPE alue COPY or INCR 9. If such change were made, the ESS olumes become inalid for a future FlashBack Restore. 10. The status after the ESS background copy has completed the copy of the ESS olumes. Chapter 1. Introduction 11

30 the BSI (backup status indicator) shows a alue of BSI_DISKONLY that will be set in the DP for ESS FlashCopy agent initiated as described in step 4.b. For more information about the BSI and DP for ESS FlashCopy agent, see Backup and Restore Cycles on page 121. tdpessora shows an ok status for the FlashCopy (for details, see DP for ESS Command tdpessora on page 117). Note: Een if the DP for ESS backup run has already completed successfully after being started with brbackup -t online_mirror or -t offline_mirror, it might happen that a FlashBack Restore is not yet possible. This is because the ESS background copy process for all ESS olumes is still running and thus the FlashCopy agent (see step 4.b) could not yet set the BSI to one of the two required alues. Only FlashCopy type backups of a database are used in a DP for ESS FlashBack Restore. Seamless Augmentation of the Functions of DP for mysap.com On the production system, DP for mysap.com can work ia a LAN in conjunction with the mysap.com DBA tools brbackup to back up the Oracle database ia a LAN/SAR brarchie to back up the redo log files to a Tioli Storage Manager serer brtools/brrecoer/sapdba/brrestore to restore the database and redo log files from a Tioli Storage Manager serer Note: For restore of FlashCopy backups, you should use only brrestore (preferred) or backfm. On request of the mysap.com DBA tool brbackup, DP for mysap.com running on another system (backup system) can perform the backup of the database from the ESS FlashCopy target olumes, which are FlashCopy images of the ESS source olumes on the production system. Centrally Administered and Scheduled Backup Operations Unattended Oracle backups can be scheduled ia crontab or from the Tioli Storage Manager serer. You can select when the backups occur without waiting for off-peak hours or maintenance downtime. Type of Backup DP for ESS has been designed to support brbackup (started with -t offline_mirror or -t online_mirror on the backup system) for running full online or offline backups. Other backup types are not supported when the backups are started on the backup system. Integration with DP for mysap.com (backint) The backint functionality (starting with ) has been extended to allow the following in conjunction with DP for ESS: FlashCopy copies can be used for fast restores initiated by either brrestore or backfm (for details, see Chapter 5, Restore Methods, on page 61). Disk-only backups can be done using brbackup. The files on the FlashCopy copies will be reported to brbackup as successfully backed up, but the backup to Tioli Storage Manager will be suppressed. DP for mysap.com has a new parameter (FCS_FILE), allowing it to call DP for ESS. For details on disk-only backups and FCS_FILE, see Chapter 4, Backup Methods, on page Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

31 Note: You should use the FCS_FILE parameter only if DP for ESS is installed and customized. Any restore requests from backups done without DP for ESS will be handled transparently. Integration with the Complementary Tool of DP for mysap.com (backfm) Starting with DP for ESS and DP for mysap.com , the DP for mysap.com tool backfm can now be used to restore backup objects from not only a Tioli Storage Manager serer but also FlashCopy copies. For details, see Chapter 5, Restore Methods, on page 61 Integration with Tioli Storage Manager Media Management Functions Working together with DP for mysap.com, all Tioli Storage Manager storage deices and media management capabilities can be utilized. You can share the deices used for other backups or gie Oracle exclusie use of certain deices and media. Life cycle management of the media and generation of tape copies for off-site aulting are supported. Understanding the mysap.com Oracle Database Administration Tools mysap.com proides a set of Oracle database administration tools (brbackup, brarchie, brrestore, sapdba), which are intended to facilitate the database administrator s work. Along with these tools, SAP has defined an architecture which allows the integration of external data protection products (like DP for mysap.com) to perform highly sophisticated backup and restore of Oracle data to and from a data protection serer (such as the Tioli Storage Manager). the inolement of an external program (such as DP for ESS) or scripts to create, by means of an ESS FlashCopy of the source olumes, an image copy on the target olumes (in mysap.com terms, to split the disk mirrors) 11 and to free up allocated system resources such as file systems, olume groups, and ESS source/target olumes (in mysap.com terms, to resynchronize the disks again later for a new split) 12 on request of the mysap.com DBA tool brbackup. brbackup deals with Oracle to get information about the database structure set tablespaces in BACKUP MODE or reset BACKUP MODE in the case of online backups Once the external program has initiated the task for the disk copy operation (e.g., ESS FlashCopy) and returns control, brbackup will inoke an external program such as DP for mysap.com to perform a backup. While Figure 2 on page 8 illustrates how brbrackup calls DP for ESS and DP for mysap.com, Figure 3 on page 15 shows the general flow of how brbackup works together with DP for mysap.com. the restore on request of sapdba and/or brrestore. The different restore methods are described in Chapter 5, Restore Methods, on page This functionality can be actiated by using brbackup with either offline_mirror or online_mirror to properly call the splitint program of DP for ESS. 12. This functionality can be actiated by using the mysap.com profile statement split_resync=yes to properly call the splitint program of DP for ESS. Chapter 1. Introduction 13

32 The connection to the data protection product DP for mysap.com as well as to DP for ESS is done by customizing the mysap.com DBA tool profile. Understanding Data Protection for mysap.com Technology Introducing Data Protection for mysap.com Technology Data Protection for mysap.com Technology (DP for mysap.com) is an intelligent client/serer program to manage backing up and restoring mysap.com Oracle databases using the Tioli Storage Manager (see Understanding DP for mysap.com and the Tioli Storage Manager Serer on page 17). This section gies you an oeriew and description of the architecture and properties of DP for mysap.com. Architecture and Properties of DP for mysap.com DP for mysap.com lets you manage backup storage and processing independently of normal SAP mysap.com operations. DP for mysap.com and Tioli Storage Manager proide reliable, high perfoce, repeatable backup and restore processes that let system administrators manage large olumes of data more efficiently. DP for mysap.com allows system administrators to follow SAP procedures and use the integrated mysap.com database utilities for backup and restore. These utilities are sapdba, brbackup, brarchie, and brrestore. Other SAP files, for example executables, are backed up using standard Tioli Storage Manager techniques for file backup and restore such as incremental backup, file filtering, and image recoery. DP for mysap.com supports two different backup/restore scenarios as seen in Figure 3 on page 15: backup/restore of files (data files, control files, redo logs, profiles) and backup/restore of data blocks. Note: This is true when running on the production system. When running on the backup system: backup/restore of offline redo logs, and backup/restore of data blocks () are not supported. 14 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

33 Figure 3. Oeriew of DP for mysap.com DP for mysap.com consists of three components: backint executable interface between mysap.com database utilities and backup library for backup/restore of files reads/writes database objects (files) from/to disk receies input parameter from SAP database utilities (e.g., list of database objects to be handled) and routes them to prole reads/transfers data from/to the Tioli Storage Manager API client exchanges information with DP for ESS in the backup process when running with DP for ESS on the backup system when called for restore, calls DP for ESS to exchange information and starts DP for ESS to restore to the production system from FlashCopy copies (only if the FCS_FILE parameter is set in the DP for mysap.com profile (.utl)). prole peently running background process controls backup/restore operations reads and interprets parameters that are specified in the profile reads/writes internal parameters (e.g., Tioli Storage Manager password) from/to the configuration file connects and sends backup/restore performance data to the Administration Assistant serer. Backup library libtdp_r3 shared library reads/transfers data blocks from/to the Oracle MM API reads/transfers data from/to the Tioli Storage Manager API client Chapter 1. Introduction 15

34 DP for mysap.com proides two possibilities for backing up or restoring data to or from the Tioli Storage Manager. These are: Backup or restore of files Backup or restore of data blocks In the case of a file backup, the communication between the mysap.com database utilities and DP for mysap.com is handled by the mysap.com backint interface. The entry point for this communication is the backint executable. backint hands oer all necessary parameters receied from the respectie mysap.com database utility (brbackup, brarchie, brrestore) to the background process prole. This process controls the running backup operation being done by the backup client. The backup client reads the appropriate files from disk and sends them to one or more Tioli Storage Manager serers using the DP for mysap.com API client. RMAN interface (applies only to backups done on the production system): In the case of a backup of data blocks (e.g., incremental backup) brbackup calls the Oracle Recoery Manager (RMAN) and starts an Oracle serer process. This process reads the data (data blocks) to be backed up from the Oracle database and transfers it to the external DP for mysap.com backup library libtdp_r3 using the Oracle Media Management API (MM API). In a similar manner as described aboe, the backup client reads the data blocks and sends them to one or more Tioli Storage Manager serers using the DP for mysap.com API client. DP for mysap.com optimizes the data throughput for backup and restore in seeral ways in order to minimize downtime and the impact on normal system operation: It sorts the database objects in order to balance the load on the resources used for backup. For restore operations, DP for mysap.com maintains the same sequence for efficient tape transfer. It is able to handle multiple backup/restore sessions. Each session reads data from and writes data to storage deices in parallel with (and independently of) each other. One session can be established per backup storage deice. It utilizes multiple communication paths to Tioli Storage Manager serers to eliminate network-induced bottlenecks. Note When DP for mysap.com is called by one of the mysap.com database utilities sapdba, brbackup, brarchie, or brrestore to perform a backup or a restore, it always uses the Tioli Storage Manager API archie and retriee functions. DP for mysap.com does not use the Tioli Storage Manager API backup and restore functions. DP for mysap.com always performs a backup, regardless of whether files are open or closed. The calling routine (for example, brbackup) is responsible for informing the database controlling routine about which files are to be backed up. This is done using an alter tablespace begin backup. The backup of both the open database files and the redo logs results in a complete backup. Starting with ersion , DP for mysap.com offers the option of initiating the restore from the FlashCopy copies on behalf of a restore request from either brrestore or backfm. 16 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

35 For more information on and for installing DP for mysap.com, see Data Protection for mysap.com Technology Installation and User s Guide for Oracle. Understanding the Administration Assistant for DP for mysap.com The Administration Assistant for Data Protection for mysap.com Technology consists of a Web-browser-based graphical interface to support and assist the customizing of Data Protection for mysap.com Technology and the analyzing of mysap.com database backup and restore operations. The objectie of the Administration Assistant is to assist in configuration, monitoring, and administration of Data Protection for mysap.com Technology 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 Technology and mysap.com database backup/restore actions from all mysap.com database serers within the system landscape. DP for ESS can, on request, send all of its runtime information for a FlashCopy backup to the Administration Assistant. To request this information be sent, you need to customize the parameters SUPPORT_ADMIN_ASSISTANT and PROLE_SERVICE_NAME in the DP for ESS profile (see Chapter 7, The DP for ESS Profile (.fcs), on page 133). More information about the Administration Assistant can be found in the Data Protection for mysap.com Technology Installation and User s Guide for Oracle. Understanding DP for mysap.com and the Tioli Storage Manager Serer Tioli Storage Manager is a client/serer program that proides storage management serices in a multiendor, multiplatform computer enironment. DP for mysap.com is a so-called API client specifically deeloped to work in conjunction with the mysap.com DBA tools on the one hand and the Tioli Storage Manager serer on the other. This allows many of the oerall Tioli Storage Manager functions to be utilized: Reduces Network Complexity Tioli Storage Manager reduces network complexity with interfaces and functions that span network enironments. This proides consistency across different operating systems and hardware. Increases Administrator Productiity Tioli Storage Manager can reduce the cost of network administration by allowing administrators to perform these actions: Automate repetitie processes Schedule unmanned processes Administer Tioli Storage Manager from anywhere in the network Reduces the Risk of Data Loss Many users do not back up their data. Other users apply stand-alone backup techniques with diskettes and tapes as the only protection for business data. These backup systems often produce disappointing results during recoery operations. Tioli Storage Manager schedules routine backups that enable users to recoer from accidental data deletion without administrator inolement. Chapter 1. Introduction 17

36 The Tioli Storage Manager Serer proides the following serices: Backup and Restore Serices Backup and restore serices allow backup-archie clients to generate backup copies of data at specified interals and restore the data from these copies when required. These serices protect against workstation or file serer media failure, accidental file deletion, data corruption, data andalism, or site-wide disasters. Archie and Retrieal Serices Archie and retrieal serices proide backup-archie clients with image copies of data for long-term storage. DP for mysap.com uses these serices to generate backup copies of data at specific interals and restore the data from these copies when required. These serices protect against workstation or file serer media failure, accidental file deletion, data corruption, data andalism, or site-wide disasters. Automation Serices Tioli Storage Manager administrators can increase productiity by automating common storage administration tasks. Administration Serices Tioli Storage Manager administration serices proide support for routine monitoring, administration, and accounting. Administrators can manage the serer from another system or the same system. The Tioli Storage Manager utilities allow the administrator to perform these functions: Define deices Label tape olumes Add additional clients Format storage olumes Set client and serer options Tioli Storage Manager monitors scheduled operations and maintains status information in the database. An administrator can export data to remoable media. This data can be imported by another serer, making the export and import features a conenient utility for moing serer data. The administrator can specify the accounting option generated at the end of each client session. Security Serices Security serices control user access to Tioli Storage Manager data, storage, policy definitions, and administratie commands. Disaster Recoery Serices Disaster recoery serices help the administrator implement a comprehensie backup and recoery procedure for important business applications, data, and records. 18 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

37 Chapter 2. General Preparations for Installing DP for ESS Oeriew In general, it is ery helpful prior to the installation of an operating system and arious products within a computer enironment to hae done a careful layout of the disk configuration you are using. It is therefore all the more imperatie that you hae done such planning in adance if you are considering using application-drien, sophisticated image backup/restore processes (such as the ESS Copy Serices FlashCopy in a two-system enironment) to aoid unnecessary re-installation work unplanned behaior of FlashCopy backups conflicting situations when performing a restore of FlashCopy disks. The two-system enironment consists of a production system (which contains the mysap.com database serer) and a backup system. The production system will hae a disk setup for the mysap.com database such that the database files will be allocated on so-called ESS source olumes; the backup system will only see the database disks (target olumes) after a FlashCopy has been done on the production system. When asking for a FlashCopy disk backup, the initiating mysap.com backup tool brbackup must be started on the backup system. When requesting a restore, the initiating programs (brrestore or backfm) must be started on the production system (for details, see Chapter 5, Restore Methods, on page 61. Understanding the behaior of the mysap.com DBA tool brbackup allows you to set up the disk enironment properly. A complete backup run of brbackup can be broken up into two parts: brbackup Part 1 1. To prepare (ia the splitint interface calling task DP for ESS) the enironment on the backup system for the current backup process (see 2.). Via DP for ESS, brbackup causes a FlashCopy process to be initiated for all ESS olumes with the following files: all the tablespace files the database control file(s): for SAP R/3 4.5B, only the first file specified in the control_files section of $ORACLE_HOME/dbs/init<SID>.ora 13 for later R/3 releases such as 4.6D, all files specified in the control_files section redo log files (only in case of an offline_mirror brbackup request): for R/3 4.5B, the first member of each group usually in /oracle/<sid>/origloga and /oracle/<sid>/origlogb 13. $ORACLE_HOME will be replaced with the alue of the enironment ariable encountered with the currently used Oracle release. Copyright IBM Corp. 2001,

38 for later R/3 releases such as 4.6D, all members of each log-file group usually in /oracle/<sid>/origloga, /oracle/<sid>/origlogb, /oracle/<sid>/mirrloga, /oracle/<sid>/mirrlogb Note: Wheneer a FlashBack Restore becomes necessary at a later time, all the ESS olumes that were part of the FlashCopy process will be restored together. 2. To call DP for mysap.com, ia its backint architecture, to run the backup to the Tioli Storage Manager serer. The files being backed up from the backup system are the same as if the backup would be running on the production system using the LAN/SAN (assumption util_type util_file would hae been used). Nearly all files inoled in Part 1 Step 1 will be the subject of the backup in Part 1 Step 2; these include all the tablespace files the first control file (listed in $ORACLE_HOME/dbs/init<SID>.ora) will be backed up and in case of an offline_mirror brbackup request only the origlog files will be backed up. in case of an online_mirror brbackup request, a special file (/oracle/<sid>/sapbackup/cntrl<sid>.dbf); this (NFS-) file is temporarily created by brbackup for the duration of the backup only. Note: This allows a later restore (on the production system) to hae always the same set of files aailable, regardless of whether it had been a FlashCopy backup on the backup system or a backup on the production system (with the exception of the preiously discussed special file). Because the totality of these files (with the exception of the special file aboe) will be the subject of the FlashCopy disk process, some rules must be followed: The aboe files (or the underlying physical olumes) must be on hardware such as an ESS, on so-called source olumes, which will be copied to target olumes as a result of a FlashCopy request (for details about the setup and usage of the olume groups (VGs) see section Specific Customization Requirements on page 22). No other files from other applications should be allocated on the set of the aboe physical olumes, to aoid any complications for these files in case of a disk-to-disk restore such as FlashBack Restore (a reerse FlashCopy on an ESS, restoring the target olumes to the original source olumes). The brbackup behaior for the scope of Part 1 is also shown in Figure 8 on page 55 and Figure 9 on page 55. brbackup Part 2 Part 2 is a run performing a backup of a small set of files (profiles, brbackup run log files, etc.); the physical olumes on which these files reside are not part of the FlashCopy operation (as in Part 1). Howeer, these files and their directories must be accessible from the production and backup systems. For this reason, these files hae to be made aailable ia an NFS setup (see Setting Up the NFS File Systems on page 35). 14. By calling the DP for mysap.com program. 20 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

39 Combined with other requirements such as database performance, etc., the planning of the oerall disk enironment could now be undertaken as discussed in Oerall Disk Layout Considerations the next section. Oerall Disk Layout Considerations For planning purposes, it is adisable to subdiide the disk enironment (spread oer the 2 systems) into the following categories, which in AIX are made up of one or more olume groups (except for the NFS_disk category). See Figure 4 on page Local disks on the production system (p_disk category) Besides the OS disks, you will also hae here the disks where Oracle and mysap.com executables will be placed during Oracle/mySAP.com installation. 2. ESS source olumes (disks) on the production system (db_disk category) These will contain all files, such as tablespace files, online redo logs, and the database control file, that are the subject of part 1 of brbackup as described preiously. All the disks that make up the olume groups in which those files reside must be ESS logical olumes, which become the ESS source olumes in the FlashCopy operation. At least the same number of target olumes must be planned and made aailable for the planned subsequent FlashCopy operations. Those olumes will become aailable, with the image copies, on the backup system after the FlashCopy has been initiated by brbackup using DP for ESS (see Integration with mysap.com DBA Backup Tool (brbackup) Functions on page 7). 3. Shared disks on the production system (NFS_disk category) Via NFS mount, the backup system must hae access to certain directories of the production system such as /oracle/<sid>/sapbackup $ORACLE_HOME/dbs /oracle/<sid>/sapreorg These directories, being part of the local disk setup of the production system, will be exported on the production system such that they can be NFS-mounted on the backup system). These directories are used by the mysap.com DBA tools, DP for mysap.com, and DP for ESS. 4. Supplementary local disks on the production system (p_db_disk category) These will contain the offline redo log directory (or a local archie file system). If R/3 releases such as 4.6D hae an Oracle database control file within the aboe directory or file system, you should, for reasons of performance, resource utilization, and integrity of the FlashCopy/backup process, moe this control file to file systems that are allocated in the db_disk category. 5. Local disks on the backup system (b_disk category) Besides the OS disks, you will also hae here the disks where Oracle and mysap.com executables will be placed during their respectie installations. 6. Disks for the Tioli Storage Manager serer (optional, TSM_disk category) If the Tioli Storage Manager serer is planned to run on the backup host, you will plan for an additional disk category (TSM_disk category) for the Tioli Storage Manager DB/log/storage disks. Chapter 2. General Preparations for Installation 21

40 Figure 4. Oeriew of the Backup Scenario The aboe layout does not preent you from using disks of the categories 1, 3, 4, 5, and 6 in the ESS too. It is just to isualize the arious categories you will hae to deal with and to highlight the role of FlashCopy source/target olume pairs (2) which will be the ones for the FlashCopy/withdraw 15 process. Following the aboe approach, you ensure that brbackup and DP for mysap.com on the backup system will find all files which must be backed up to Tioli Storage Manager. Sample of an Oerall Disk Layout on page 167 demonstrates in detail how the disks could be set up. Disclaimer Higher releases/ersions of R/3 and/or Oracle might hae new or renamed file systems. The user must adapt the proisions of this document to such changes. Specific Customization Requirements With respect to running brarchie on the production system brbackup when requesting an offline/online FlashCopy backup on the backup system an offline/online backup on the production system ia the LAN sapdba/brrestore and brtools/brrecoer on the production system it is strongly recommended, on both production and backup systems, to use a common profile directory, ia NFS mount ($ORACLE_HOME/dbs) only one common TDP Client node name a common sapbackup directory as an NFS repository, to facilitate backup/restore for the R/3 tools and aoid restore/recoery problems. 15. The R/3 or mysap.com documentation refers to this using the generalized terms split-mirror and resynchronize. 22 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

41 In planning to utilize the DP for mysap.com backup ersion control function, you must set up the enironment so that brbackup (calling DP for mysap.com on the backup system) and brarchie (calling DP for mysap.com on the production system) will use the same file (init.<sid>.bki) specified in the CONFIG_FILE parameter in the DP for mysap.com profile (normally init<sid>.utl). Further customization requirements to plan for are: The Oracle Client software must also be installed on the backup serer. The Oracle home directory structure must correspond to the SAP standard installation required by brbackup. Default directories used by brbackup will be $ORACLE_HOME/dbs /oracle/<sid>/sapbackup /oracle/<sid>/sapreorg where ORACLE_HOME, depending on the Oracle release used, can be: /oracle/<sid> /oracle/<sid>/816_32 /oracle/<sid>/920_64 or or etc. The following mysap.com directories of the production system must be mounted on the backup system as NFS wheneer brbackup or splitint runs are planned on the backup system: $ORACLE_HOME/dbs /oracle/<sid>/sapbackup /oracle/<sid>/sapreorg Important Note Starting with Oracle 8i, ORACLE_HOME includes the Oracle release in the directory name. For release 9, it is typically /oracle/<sid>/920_64, and dbs and bin are in that directory. Howeer sapbackup, sapreorg, and the sapdata directories are still under /oracle/<sid>, which is defined by a new enironment ariable SAPDATA_HOME, so that the aboe section (and others) would be as follows for Oracle 8i or later: $ORACLE_HOME/dbs $SAPDATA_HOME/sapbackup $SAPDATA_HOME/sapreorg Establish seeral olume groups (VGs) within the db_disk category to coer the arious requirements associated with an offline_mirror or online_mirror brbackup run. Since brbackup creates different file lists for offline_mirror and online_mirror backups, and these lists are the basis for DP for ESS to identify the ESS source olumes, a minimum of 2 VGs are required to aoid conflicts within the backup process. The result of the different file lists is shown in Figure 9 on page 55). Since the online redo log file systems will only be backed up within an offline_mirror brbackup request, they must be kept separate from those file systems (and their underlying olume groups) which are backed up within the online_mirror and ice ersa. To aoid haing the online redo log file systems be inoled within the online_mirror backup, 2 VGs as a minimum within the db_disk category are required. The contents of the 2 VGs would become as follows, for example: Chapter 2. General Preparations for Installation 23

42 1. One VG (e.g. g<sid>redolog) containing the online redo log file systems /oracle/<sid>/origloga, /oracle/<sid>/origlogb, /oracle/<sid>/mirrloga /oracle/<sid>/mirrlogb and For safety/performance reasons or een disk-to-disk restore procedures you might split this VG into 2 VGs to hae the origlog file systems separated from the mirrlog file systems. 2. One VG (e.g. g<sid>database) containing the file systems with the data of the database /oracle/<sid>/sapdata1 /oracle/<sid>/sapdata2 /oracle/<sid>/sapdata3... /oracle/<sid>/sapdatan There are no reasons not to subdiide the aboe VG into more than one VG too. Ensure that within the db_disk category each jfslog LV with all its LPs is allocated non-striped to one OS disk (AIX physical olume) only No other files or file systems from other applications than the mysap.com application should be allocated on the disks of the db_disk category. Such a wrong allocation can create problems during the FlashCopy backup and within restore runs if planned for a disk-to-disk restore/recoery. Ensure that the Oracle DB control files backed up in Part 1 Step 1 within the flashcopy process (see brbackup Part 1 on page 19) reside within the scope of the file systems whose files are always part of the flashcopy backup be it an offline_mirror or an online_mirror. /oracle/<sid>/sapdatax (with x =1 to n) file systems are the candidates for a suitable placement. In mysap.com usually 3 control files specified in init<sid>.ora are used; those could be then allocated e.g.: /oracle/<sid>/sapdata1/cntrl/cntrl<sid>.dbf /oracle/<sid>/sapdata2/cntrl/cntrl<sid>.dbf /oracle/<sid>/sapdata3/cntrl/cntrl<sid>.dbf Note: To actiate the change, you need to adjust init <SID>.ora and shut down and restart the DB. The Oracle and mysap.com DBA tool profiles (normally init<sid>.ora, init<sid>.sap) should be aailable in $ORACLE_HOME/dbs. The directory /usr/sap/<sid>/sys/exe/run must be accessible from the backup serer and should contain at least the programs brbackup, brconnect, and brtools (and optionally brarchie and brrestore). Important: Running the mysap.com DBA tools on the backup and production systems requires that the user IDs ( ora<sid>, <sid>adm ), and user ID numbers group IDs (dba, oper, sapsys), and group ID numbers match on both systems. Profile Considerations Today, without utilizing the FlashCopy/withdraw functions of the ESS, you can run the traditional backups with the mysap.com DBA tools sapdba and brbackup using DP for mysap.com in the so-called one-system enironment. Figure 5 on page Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

43 page 25 illustrates the arious profiles and control files needed for such backups and also restores. While all, with the exception of init<sid>.bki, are customized at setup time (see Data Protection for mysap.com Technology Installation and User s Guide for Oracle), it is the init<sid>.bki control file in which DP for mysap.com keeps control information about ersions (if MAXVERSION is nonzero) and password (if PASSWORDREQUIRED is set to YES). Figure 5. Control File/Profile Relationships Without DP for ESS Chapter 2. General Preparations for Installation 25

44 Utilizing the ESS capabilities, such as FlashCopy/withdraw, for disk copy backups with succeeding backups to external media (using Tioli Storage Manager and DP for mysap.com), you inole a two-system enironment (see Figure 6 on page 27), in which the arious control files and profiles contain information needed from both systems. The ideal setup is to hae certain mysap.com DBA, the DP for mysap.com, and DP for ESS profiles and control files set up in NFS directories, so that all mysap.com DBA tools (sapdba, brbackup, brarchie, brrestore) use the same profile and control files, regardless of which system the mysap.com DBA tool 16 has been started on. In addition, DP for mysap.com and DP for ESS use the same profiles, regardless of whether they were started on the production or backup system by the mysap.com DBA tool. Such a setup will allow the DP for ESS with its FlashCopy function to be integrated transparently into mysap.com DBA tools in such a way that the DB administrator can, as he is accustomed to, perform all mysap.com DBA tasks, such as: administering an Oracle DB on the production system initiating backups with ESS Copy Serices capabilities on the backup system using DP for ESS and DP for mysap.com, or initiating backups without ESS Copy Serices capabilities on the production system without DP for ESS but with DP for mysap.com. running and controlling backups of the redo logs on the production system restoring/recoering the database on the production system on the basis of the objects that were backed up To enable different backup requests on the production and backup systems, and also to satisfy the restore capability on the production system, for a Tioli Storage Manager restore as well as a FlashBack Restore, the files with types.sap,.utl, and.fcs can hae different names, but the names need to be unique: idssae init<sid>.fcp init<sid>.fct init<sid>.bki In Figure 6 on page 27, this requirement for uniqueness is indicated by a black triangle in the upper right corner of the file s symbol. Unique naming is necessary so that, in the backup and restore cases, both DP for mysap.com and DP for ESS can get the information that must be unique for these requests. The FCS_FILE parameter must point to an appropriate DP for ESS profile (.fcs) to fulfill the aforementioned requirements (for idssae,.fcp, fct). To enable the FlashBack Restore capability, the DP for ESS profile (.fcs), which is pointed to by the DP for mysap.com profile (.utl) FCS_FILE parameter, must connect to the same idssae file that was used by DP for ESS in its profile (.fcs) when doing the FlashCopy backup. In order for the FlashBack Restore to work, the files init<sid>.bki and init<sid>.fcp must hae alues such that passwords used in the backup or restore request are alid. 16. Keep in mind that the FlashCopy disk backup can be started only on the backup system. 26 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

45 The following figure shows the relationships of the profiles of the mysap.com DBA tool, DP for mysap.com and the TDP API with DP for ESS for a two-system enironment and using FlashBack Restore: Figure 6. Control File/Profile Relationships With DP for ESS To guarantee haing a proper setup of the profiles for a potential FlashBack Restore when the backup is made, DP for mysap.com (when running on the backup system at the request of brbackup) causes a brbackup run to fail if the FCS_FILE parameter in the DP for mysap.com profile is not properly specified and you are using FLASHCOPY_TYPE COPY or INCR, which implies you are considering the creation of a disk copy that could be used for a FlashBack Restore. For a FlashBack Restore: the FCS_FILE parameter must be properly specified. Otherwise, you will not be able to run the FlashBack Restore. Chapter 2. General Preparations for Installation 27

46 28 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

47 Chapter 3. Installing and Customizing DP for ESS Note For current information concerning installation of DP for ESS, refer to the README file shipped on the product installation media. Installation Requirements This chapter proides the information needed to plan and perform the installation and customization of DP for ESS. For the purposes of planning such an installation, Installation requirements Hardware Software Enironment are shown first. Prior to installation and customization of DP for ESS, other product installation and actiities should be done and are discussed in the sections General installation approach for the required products Other steps prior to installing DP for ESS Setting up the NFS file systems Setting up ESS source and target olumes The actual installation and customization of DP for ESS is discussed in Installing DP for ESS Customizing and initializing DP for ESS Customizing the DP for ESS profile Initializing DP for ESS Information on how to actiate the mysap.com tool to use DP for ESS in conjunction with DP for mysap.com for FlashCopy-based backups is proided in Customizing the mysap.com DBA tool enironment Preparing for SQLNET usage Customizing the mysap.com DBA tool profile If you hae completed the actiities required in the aboe line items, you can start to run FlashCopy-based backups on the backup system as shown in Chapter 4, Backup Methods, on page 47 and Sample splitint Usage on page 199. The following requirements must be met for DP for ESS to install successfully. Also, check the README files for the latest information on hardware/software requirements. Hardware Requirements Two RS/6000 systems (one for the production side and one for the backup side) Note: Three RS/6000 systems are required when planning for a high aailability enironment where a primary and takeoer system with HACMP will become established with HACMP; each of both needs to play the role of Copyright IBM Corp. 2001,

48 the production system depending on which is currently the actie system. The takeoer system cannot be the backup system. IBM Enterprise Storage Serer with FlashCopy LIC Feature Note: In case AIX LVM mirroring is planned, 2 dedicated ESS units, each with the FlashCopy LIC feature, are required, one for each mirror copyset. For details, see Chapter 8, DP for ESS Functionality for AIX LVM Mirrored Enironments, on page 141. IBM Enterprise Storage Serer (ESS) with microcode leel or later, or IBM Enterprise Storage Serer (ESS) with microcode leel or later (hereafter referred to as FlashCopy V2 ), which proides the following enhancements: lifting of the requirement that an ESS source/target pair be in the same LSS within an ESS unit (utilized by DP for ESS and higher) an incremental FlashCopy function to shorten the copy processes running in the ESS background IBM Enterprise Storage Serer (ESS) with microcode 2.3.x or later, to enable DP for ESS or higher to use the Incremental FlashCopy function to shorten the copies running in the ESS background. Disk space: 100 MB for each DP for ESS ersion leel in use For each PreRestore.sh run, disk space is required 17 (by default, the samples use /oracle/<sid>/sapreorg), which needs to be cleaned up by the DBA after he has ensured that the restore and recoery were successful. The size depends on the actual size of the files in your enironment. Memory: 256 MB Howeer, check the mysap.com DB serer memory requirements, which normally are in the range 1-2 GB, depending on workload objecties. Both the production and backup systems are connected to the ESS ia SCSI or Fibre Channel adapters. The ESS is configured so that the following two conditions are met: The ESS source olumes for the production database are accessible to the production machine. The ESS target olumes for the FlashCopy of the production database are accessible to the backup machine. Note: The ESS source and target olumes must not be accessible concurrently to the same system. The RS/6000 systems hae a LAN connection to the ESS primary Copy Serices serer. A LAN connection exists between the production system and the Tioli Storage Manager Serer. A LAN connection exists between the backup system and the Tioli Storage Manager Serer (if the Tioli Storage Manager Serer does not reside on the backup system). A LAN connection for the NFS setup exists between the production and backup systems. 17. For backup and restore of all current control files and online redo log files (all members of all groups). 30 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

49 Software Requirements Note: The leels shown specify the minimum required. For the latest supported leels, check the README file or refer to the Web page. The following software must be installed and configured on both the backup and production systems: AIX with one of the following leels 5.1 with maintenance leel fix package 3 (AIX ) and PTF U for APAR IY with maintenance leel fix package 1 (AIX ) and PTF U for APAR IY44637 AIX base components must be installed with the U.S. English (en_us) NLS language aailable. This can be checked with locale a for the aailability of locale en_us.iso Tioli Storage Manager Backup-Archie Client Version 4.2 (or higher). Any higher supported leel is recommended. DP for mysap.com (AIX Version) or higher Tioli Storage Manager API Version 4.2 (or higher); leel as required by DP for mysap.com. Note: The Tioli Storage Manager API is included in the Backup-Archie Client and Serer package. SAP R/3, Release 4.5B to 4.6D or mysap.com e-business solutions like SAP BW together with the released Oracle 8 or Oracle 9 leel (only on the production system) SAP DBA tools kernel release 6.20 with a minimum patch leel of 118. ESS Copy Serices Command Line Interface (CLI) for AIX. The CLI code leel must correspond to that of the microcode installed in the ESS clusters. See Hardware Requirements on page 29, including the requirement for FlashCopy V2. Jaa Runtime for AIX, Version 1.1.8, 1.3.0, or In addition the following software must be installed and configured: on the backup system: R/3 or mysap.com DBA tools (brbackup etc) and an Oracle client both with the same leel as used on the production system. On the backup system or a dedicated Tioli Storage Manager serer you need Tioli Storage Manager Serer Version 4.2 (or higher). Any higher supported leel is recommended. Enironment Requirements DP for ESS requires that specific configurations exist prior to installation. The following enironment requirements must be met before installing DP for ESS: SAP database support and tools are installed on the production and backup machines. The Oracle Serer is installed on the production machine and the Oracle Client. including SQLNET, on the backup machine. Chapter 3. Installing DP for ESS 31

50 The Oracle database files to be backed up reside completely on the ESS subsystem and are isible to the production machine. The Oracle database files are located on a Journaled File System. There is no DP for ESS FlashCopy backup support implemented for an Oracle database installed: on raw deices 18 in striped AIX LVM enironments in mirrored AIX LVM enironments (for exceptions, see Chapter 8, DP for ESS Functionality for AIX LVM Mirrored Enironments, on page 141) using the jfs2 file system inline logs using jfs2 file systems with concurrent I/O Certain directories on the production side must be made aailable ia NFS to the backup side (see Setting Up the NFS File Systems on page 35). DP for ESS uses the rexec command on the backup system to process commands on the production system. For this, the rexecd daemon must be configured and started on the production system. Space is required when executing DP for ESS on the production and backup systems. In order to aoid an uncontrolled termination of DP for ESS (or the called system commands) due to lack of space, DP for ESS issues a warning message (IDS1310W) if one of the file systems of the following directories has less than 50 MB free space: $HOME (e.g. /oracle/a01) $ORACLE_HOME/dbs (e.g. /oracle/a01/920_64/dbs) the directory of the IDS_CONTROL_FILE (e.g. /oracle/a01/sapbackup/idssae) the directory specified with LOG_TRACE_DIR (e.g. /oracle/a01/sapbackup/logtraces) /tmp / If the aailable space is less than 5 MB, DP for ESS terminates with an error message (IDS1311E); in this case, the affected file systems first need to be increased prior to rerunning DP for ESS. General Installation Approach for the Required Products It is recommended that the prerequisite products be installed and customized in the following sequence: mysap.com and Oracle on the production and backup systems 19 For practical reasons, we hae added for this and the next item what was used in our test enironment (see Sample R/3 Installation and Customization on page 193). Oracle DBMS on the production and backup systems 19 The purpose of installing Oracle on the backup system is to proide the executable components in the most straightforward manner. It would be, of course, be required if access ia Oracle to the database represented by the ESS target olumes is desired. Howeer, DP for ESS does not require such 18. See details of supported AIX/LVM enironments in the current README or get this information using the Internet channels. 19. Ensure that you hae identified the ESS source olumes to be used for the Oracle database on the production system and the ESS target olumes to be used later after a FlashCopy on the backup system. 32 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

51 functionality, and SAP technical consultants with adanced AIX and Oracle knowledge could select an abbreiated installation, combined with the requirements and installation steps shown in the documentation for mysap.com Oracle installation on UNIX as shown in the following. For quick bringup of mysap.com and Oracle on the backup system: Perform the following steps: 1. Ensure the leel of installed AIX components is as specified in the mysap.com system requirements. 2. Establish required local file systems /oracle/<sid>/, /usr/sap/<sid>, and /sapmnt/<sid>. 3. Create user ora<sid> and <sid>adm (see also the specifics under Establish the Enironment System ). 4. Copy the Oracle and mysap.com executables from the production system into the appropriate file systems on the backup system. 5. Ensure that the ownerships of all copied files are as required. 6. Copy the following Oracle files from the production system to the backup system. To set up the SAP enironment for user ora<sid> on the backup system, rename the files with the hostname (of the backup system) and make further adjustments as required:.sapen_<hostname>.sh.sapen_<hostname>.csh.dben_<hostname>.sh.dben_<hostname>.csh.profile.cshrc.login All files are located in the $HOME directory of user ora<sid> (normally /oracle/<sid>). 7. Actiate Asynchronous I/O. 8. Run the script rootpre.sh. 9. Copy the files tnsnames.ora, listener.ora, and sqlnet.ora in $ORACLE_HOME/network/admin from the production to the backup system for SQLNET/sqlplus use; modify them if required. The aboe list does not claim to be exhaustie and must be adapted by the user to newer Oracle or mysap.com releases if required. Tioli Storage Manager products Tioli Storage Manager Serer on your target system (might not apply if already aailable or on a different host) TDP Backup-Archie clients and the Tioli Storage Manager API on the production and backup systems. For information regarding installation procedures for these software applications, see Tioli Storage Manager for UNIX Using the Backup-Archie Clients and Tioli Storage Manager Using the Application Program Interface. Samples for the customized Tioli Storage Manager Client option files can be found in Sample Tioli Storage Manager Client Options Files on page 172. DP for mysap.com on the production and backup systems For information regarding installation, see the sections Installation on AIX, and Customizing Data Protection for mysap.com and SAP Backup Profile in the Data Protection for mysap.com Technology Installation and User s Guide for Oracle. You can find samples of the two profiles as they hae been used in our test setup: Chapter 3. Installing DP for ESS 33

52 Sample DP for mysap.com Profile on page 173 Sample mysap.com DBA Tool Profile on page 187 Note: A DP for ESS FlashBack Restore can be done only when the FCS_FILE parameter (introduced with DP for mysap.com ersion ) has been properly defined. It is recommended to wait with customization of DP for mysap.com on the backup system until you hae done the NFS setup as described Setting Up the NFS File Systems on page 35. DP for mysap.com downward compatibility: In order to allow the restore of data on the production system that was backed up on a different system (in the case of DP for ESS, on the backup system), the downward compatibility of DP for mysap.com must be strictly obsered. In general, TDP for R/3 has downward restore compatibility unless otherwise stated in the product. If possible, keep the DP for mysap.com leels the same on both systems. Neer hae the backup system running a higher leel than on the production system. If multiple DP for mysap.com leels are required on the backup system: When dealing with seeral production systems (each one being by itself a dedicated R/3 DB serer), you might need to run different DP for mysap.com leels on the backup system that is the common backup system for the arious production systems. In this case you hae to do some steps manually for the releant <SID> (on production and backup systems) after running the DP for mysap.com setup script (and prior to installing a new DP for mysap.com leel): Create a maintenance leel directory under the directory /usr/tioli/tsm/tdp_r3, such as /usr/tioli/tsm/tdp_r3/ora/ /usr/tioli/tsm/tdp_r3/ora64/ Copy (with the -p option) the files backint createinfo libtdp_r3.a prole to the new maintenance leel directory. (e.g. for ersion , 32-bit) (e.g. for ersion , 64-bit) Note: Oracle RMAN is not supported on the backup system when running brbackup with DP for ESS and DP for mysap.com. For each maintenance leel you hae installed, you will need an entry in /etc/inittab for starting the correct ersion of prole: prole3310:2:respawn:/usr/tioli/tsm/tdp_r3/ora/ /prole -p <prole port> where <prole port> represents the TCP/IP port which is used by this ersion of prole. For each different ersion you hae to define a separate port number. Make sure that the following files are linked to the new directory /usr/sap/<sid>/sys/exe/run/backint -> /usr/tioli/tsm/tdp_r3/ora/ /backint /usr/sap/<sid>/sys/exe/run/backfm -> /usr/tioli/tsm/tdp_r3/ora/ /backfm /usr/bin/createinfo -> /usr/tioli/tsm/tdp_r3/ora/ /createinfo For each maintenance leel you hae installed, you will need to set the enironment ariable in the Oracle users profile: 34 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

53 PROLE_PORT=<prole_port> to the corresponding prole port you hae defined in /etc/inittab If you followed the aboe sequence, you should be able at this point on the production system to run the mysap.com DBA tools together with DP for mysap.com; you can perform the backup/restore ia the LAN to the Tioli Storage Manager Serer using the mysap.com tools. Other Steps Prior to Installing DP for ESS Setting Up the NFS File Systems It is recommended to do this step prior to installation and customization of DP for ESS in order to facilitate the oerall installation/customization process. To simplify the implementation and to facilitate later operations control, the following directories of the production system should be mounted on the backup system: /oracle/<sid>/sapreorg /oracle/<sid>/sapbackup $ORACLE_HOME/dbs If additional directories (such as the one you will specify in the DP for ESS profile) will be shared, you hae to add them to the aboe list. Howeer, if you choose a similar directory structure as shown in Sample DP for ESS Profile on page 178, no additional directories other than the aboe ones are necessary. Details on how to set up the aboe directories for NFS use are shown in: Sample NFS Serer Setup on the Production System on page 170 and Sample NFS Client Setup on the Backup System on page 171 Aspects of Using the IBM Subsystem Deice Drier (SDD) DP for ESS proides basic support for the IBM Subsystem Deice Drier (SDD), also referred to as multipathing. SDD resides on the host serer(s) (production and backup systems) with the natie deice drier for the IBM ESS storage subsystem. SDD uses redundant connections between the host serer and disk storage in an IBM ESS storage subsystem to proide enhanced performance and data aailability. By installing and configuring SDD, the user can hae seeral hdisk deices defined to a single SDD deice (path deice). Each path deice represents a unique physical deice (LUN) on the same IBM ESS storage subsystem. There can be up to 32 different paths to the same physical deice (an ESS logical olume) when using DP for ESS. The following SDD configurations hae been tested and are supported: SDD is not installed on the production system, and the olume group containing the Oracle database has AIX hdisk deices. SDD is installed on the production system, and the olume group containing the Oracle database has path deices. Chapter 3. Installing DP for ESS 35

54 Note Starting with DP for ESS 1.2.3, if SDD is installed and multiple paths to the ESS olumes are used, all olume groups that hae physical olumes within an ESS unit must be set up with SDD paths to aoid serious problems at FlashBack Restore time. Termination will be forced at backup time if this requirement is not met. See also Appendix E, Migration from Preious DP for ESS Releases, on page 247. SDD is installed on the backup system, the ESS hdisk deice olume group is conerted to a SDD path olume group by DP for ESS. SDD is not installed on the backup system, the ESS hdisk deice olume group is kept unchanged A configuration in which SDD is installed on the production system and the olume group containing the Oracle database has a mixture of hdisk and path deices is not supported. This enironment is not recommended when using SDD. A olume group with mixed deices needs to be fixed using dopgfix. For more information on SDD, refer to Setting Up ESS Source/Target Volumes To make ESS olumes accessible in AIX, the ESS Specialist Web Interface must be used by the ESS Administrator. Setting up ESS olumes for later ESS FlashCopy operations requires that the olumes that will become source and target be in the same LSS (logical subsystem) of the ESS and that the size of a source olume match the size of the planned target olume. Note: If FlashCopy V2 is installed (see Hardware Requirements on page 29) and you are using DP for ESS or higher, an ESS source/target olume pair need no longer be in the same LSS within an ESS unit. In customization, the target olumes you plan to use must be set up in the file identifying the ESS target olumes by serial number (see Table 11 on page 139). Generally, you should spread the olumes of one ESS serer across as many LSS as possible. Attach the source olumes to one RS/6000 system (production system) and the target olumes to the other RS/6000 system (backup system). When the FlashCopy takes place, your copy will always appear on the serer that is the backup system. Note: Do not attach the ESS source and target olumes to both systems. To check, on the AIX system, the ESS olumes you hae receied, you can issue: lsde -Cc disk and check for the olumes of type Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

55 Installing DP for ESS Shared Usage of Target Volumes DP for ESS was designed such that a dedicated set of target olumes must be proided for each database instance (identified by an SID ). If an installation plans (for backup purposes only, implying that FLASHCOPY_TYPE NOCOPY is used) to use one common set of target olumes for multiple database instances, the following rules (in addition to the preiously mentioned LSS and size requirements) must be followed: The brbackup executions (-t offline_mirror or online_mirror) for the arious database instances (SIDs) must run in sequence and always show a successful completed backup cycle for one database instance (e.g., SID=TST) before running the brbackup for a different database instance (e.g., SID=PRD). The backup cycle of each brbackup must be completed with a DP for ESS splitint -f withdraw. This can be done either within the brbackup run using split_resync=yes or after the brbackup run by issuing the DP for ESS command splitint -f withdraw manually. A control mechanism 20 must be in place to ensure that succeeding brbackup runs will be started only if the preceding brbackup terminated successfully. Important: If the customer fails to exercise stringent control oer the sequence of brbackup runs for the different database instances when using shared target olumes, this can hae a decidedly negatie impact on all brbackup runs inoled. Of course, sharing target set olumes in conjunction with disk copy backups (FLASHCOPY_TYPE COPY or INCR) is counterproductie. DP for ESS cannot detect such improper use. The following steps guide you through the DP for ESS installation. To install and customize DP for ESS, you must log in as user ID root. Installation Notes Installation of DP for ESS must be done at least twice, once on the production database serer machine referred to as the production system, and once on the backup system on which brbackup with FlashCopy disk backups is planned to run. Using multiple database instances requires installing DP for ESS on each production system and once on the common backup system. Each production system running DP for ESS to a common backup system must use a different Oracle SID. The ersion/maintenance leel of DP for ESS (splitint) used for the FlashCopy of one database instance (SID) must be the same on the production and backup systems. After the installation of DP for ESS, you must run setup.sh for each specific database instance (SID) on the production system, as well as on the backup system. The aboe approach permits the production systems to hae different ersion/maintenance leels. 20. There are arious possibilities for a customer to establish such a mechanism, such as the use of job scheduling products, controlled lock files, etc. Chapter 3. Installing DP for ESS 37

56 DP for ESS ersion 1.2 will be installed by means of InstallShield, other than in preious ersions where it was installed under AIX with the own install utility installp from the AIX system management interface tool named smitty. It is recommended that you uninstall an earlier ersion package of DP for ESS to remoe the old files. To uninstall from a ersion earlier than 1.2 do the following: 1. Log in as user ID root on the production (or backup) system. 2. Inoke the AIX system management interface tool: smitty. 3. Choose the menu Software Installation and Maintenance. 4. Choose the menu Software Maintenance and Utilities. 5. Choose the menu Remoe Installed Software. 6. Press F4 to choose from a list of packages. 7. Choose the package to be uninstalled, for example: tioli.tsm.tdpessr3.oracle.aix52.32bit 8. You will be asked to remoe the directories named as the earlier ersion. If you only want to install the new package but to keep parts of your database instances working with the earlier ersion, you hae to answer with no here. The following steps guide you through the DP for ESS installation: 1. Log in as user ID root on the production (or backup) system. 2. DP for ESS for mysap.com install package is deliered as a single executable file named install_tdpessr3_ora.bin on CD-ROMs. You may also download the latest aailable ersion from the Tioli homepage at If you are going to install from the CD-ROM, ensure that it is inserted in the proper CD-ROM drie. 3. Ensure that the enironment ariable DISPLAY is set to host:display. Where host identifies the host name of the X Serer to be contacted and display is the display number. 4. Inoke the executable install_tdpessr3_ora.bin and follow the instructions of the InstallShield. The following figure shows a sample panel of the InstallShield procedure. 38 Data Protection for IBM ESS for mysap.com Technology Installation and User s Guide for Oracle

57 Figure 7. Example of an InstallShield panel 5. Check the summary at the last InstallShield dialog panel for successfully installation. If an error occurs during the installation process, check for the error message in the output panel carefully and correct the problems. After correcting the error(s) repeat the installation procedure beginning at step The DP for ESS software will be installed into the directory /usr/tioli/tsm/tdpessr3/oracle. Check the README file for a brief description of all installed files. The aboe directory contains the DP for ESS executables, which are accessed by the setup.sh script described in the following. For the proper functioning of DP for ESS, a post-installation procedure must be started. During this procedure, a shell script setup.sh will be processed and the following tasks performed: Rename the DP for ESS profile (init<sid>.fcs) and copy it to the /oracle/<sid>/920_64/dbs directory. This applies only to new installations; otherwise this step is omitted. Copy the splitint executable to a ersion/maintenance leel directory. Create a softlink to the splitint executable in the mysap.com executables path. The following steps describe the post-installation procedure: 1. Using user ID root, inoke the post-installation shell script: /usr/tioli/tsm/tdpessr3/oracle/setup.sh 2. Enter the system ID (SID) for the mysap.com system to be backed up. 3. Enter the path for the mysap.com executables, normally found in /usr/sap/<sid>/sys/exe/run If appropriate, you can use the suggested default by pressing Enter. 4. Enter the path for the DP for ESS profile (init<sid>.fcs). If appropriate, you can use the suggested default by pressing Enter. As already discussed, this must be an NFS directory. See also Oerall Disk Layout Considerations on page 21. Chapter 3. Installing DP for ESS 39