VERITAS NetBackup 6.0 for SAP

Transcription

1 VERITAS NetBackup 6.0 for SAP System Administrator s Guide for UNIX and Linux N15265B September 2005

2 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. VERITAS Legal Notice Copyright 2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, and NetBackup are trademarks or registered trademarks of VERITAS Software Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright , RSA Data Security, Inc. Created All rights reserved. VERITAS Software Corporation 350 Ellis Street Mountain View, CA USA Phone Fax Third-Party Copyrights For a list of third-party copyrights, see the NetBackup Release Notes appendix. ii NetBackup for SAP System Administrator s Guide for UNIX and Linux

3 Contents Preface ix Getting Help ix Finding NetBackup Documentation ix Accessing the VERITAS Technical Support Web Site x Contacting VERITAS Licensing xi Accessibility Features xi Comment on the Documentation xii Chapter 1. Introduction NetBackup for SAP Features NetBackup for SAP Overview Technical Overview Sequence of Operation NetBackup for SAP on Oracle Databases Using NetBackup for SAP on Oracle Databases Without RMAN Using NetBackup for SAP on Oracle Databases With RMAN SAP Tools Overview NetBackup for SAP on MaxDB Databases Chapter 2. Installation Verifying the Installation Prerequisites Operating System and Platform Compatibility NetBackup Software Database Software iii

4 Cluster Software Installing NetBackup for SAP Remote Installation of NetBackup for SAP Loading the NetBackup for SAP Files onto the Server Pushing the Software to All Clients Currently Specified in an SAP Policy Type 17 Pushing the Software to New or Selected Clients Local Installation of NetBackup for SAP Linking NetBackup for SAP with backint (Oracle Databases without RMAN Only) Linking the Oracle Database with the SBT Library (Oracle Databases with RMAN Only) Chapter 3. Configuration User Interface Terminology Notes Configuring the Maximum Jobs Per Client Configuring Backup Policies Adding a New Policy Description of Attributes Adding Schedules Types of Backup Schedules Schedule Properties Adding Clients Adding Backup Selections Creating Scripts Modifying the Backup Scripts Script Parameters Modifying the Configuration Files Files to Configure Relationships Between Files Modifying the initsid.utl File iv NetBackup for SAP System Administrator s Guide for UNIX and Linux

5 Modifying the initsid.sap File (NetBackup for SAP on Oracle Databases Only) Modifying the bsi.env File (NetBackup for SAP on MaxDB Databases) Testing Configuration Settings Testing Multiple Drives and Files Chapter 4. Using NetBackup for SAP Performing a Backup Method 1: Using NetBackup for SAP to Perform a Backup Automatic Backup Manual Backup Method 2: Using SAP to Perform a Backup (NetBackup for SAP on Oracle Databases Only) SAPDBA Offline Backup brbackup Online Backup Performing an Archive Method 1: Using the NetBackup Multiple Copies Feature Examples Method 2: Using Two brarchive Commands in Sequence Examples Performing a Restore Using the SAPDBA Utility (NetBackup for SAP on Oracle Databases Only) Redirecting a Restore to a Different Client (NetBackup for SAP on Oracle Databases Only) Redirected Restore Sample Environment Chapter 5. NetBackup for SAP on MaxDB Databases Configuration Creating a Backup Medium Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores. 72 Contents v

6 Performing a Backup Performing a Query Performing a Restore Performing Backups and Restores Using Parallel Medium Groups Chapter 6. Troubleshooting Setting the Debug Level NetBackup Reports Enabling Logging Accessing the Log Files bphdb Directory on the Client backint Directory on the Client NetBackup Server Reports sapdba Logs and Messages Backup and Restore Log Files Archive Log Files Minimizing Timeout Failures on Large Database Restores Appendix A. backint Command Line Appendix B. backint -i in_file Contents Appendix C. backint -o out_file Contents Information Returned for a Backup Information Returned for a Restore Information Returned for an Inquiry Appendix D. Environment Variables Appendix E. bp.conf File Appendix F. Parameters Used in initsid.utl vi NetBackup for SAP System Administrator s Guide for UNIX and Linux

7 backint_dir work_directory backup_stream_buffersize size bplist_filter script_path client client_machine_name custom_sort_file file_path drives number_of_drives fail_backup inquiry_query_period months master_time_offset minutes media_notify_script script_path policy policy_name policy2 policy_name restore_filter script_path restore_stream_buffersize size retry_backup number_of_retries schedule schedule_name schedule2 schedule_name server server_name sleep seconds sort_backup_type value sort_backup_type custom sort_backup_type device sort_backup_type drive sort_backup_type size (Default) sort_restore_type value sort_restore_type custom sort_restore_type drive sort_restore_type image (Default) switch_list control_file_path switch_log control_file_path Contents vii

8 switch_sem control_file_path Appendix G. Using NetBackup for SAP to Back Up SAPDB Creating Backup Environment Configuration Files backint for SAPDB Configuration File Adapter Program Configuration File NetBackup for SAP Configuration File, initsid.utl Defining a Backup Medium in SAPDB Performing a Backup Performing a Restore Index viii NetBackup for SAP System Administrator s Guide for UNIX and Linux

9 Preface This guide describes how to install, configure, and use NetBackup for SAP on UNIX and Linux platforms. Throughout the NetBackup for SAP documentation, the term UNIX refers to both UNIX and Linux platforms. For information about the NetBackup server software, see one of the following platform-specific manuals: NetBackup System Administrator s Guide for UNIX and Linux, Volumes I and II NetBackup System Administrator s Guide for Windows, Volumes I and II Getting Help You can find answers to questions and get help from the NetBackup documentation and from the VERITAS technical support web site. Finding NetBackup Documentation A list of the entire NetBackup documentation set appears as an appendix in the NetBackup Release Notes. All NetBackup documents are included in PDF format on the NetBackup Documentation CD. For definitions of NetBackup terms, consult the online glossary. To access the NetBackup online glossary 1. In the NetBackup Administration Console, click Help > Help Topics. 2. Click the Contents tab. 3. Click Glossary of NetBackup Terms. Use the scroll function to navigate through the glossary. ix

10 Getting Help Accessing the VERITAS Technical Support Web Site The address for the VERITAS Technical Support Web site is The VERITAS Support Web site lets you do any of the following: Obtain updated information about NetBackup for SAP, including system requirements, supported platforms, and supported peripherals Contact the VERITAS Technical Support staff and post questions to them Get the latest patches, upgrades, and utilities View the NetBackup for SAP Frequently Asked Questions (FAQ) page Search the knowledge base for answers to technical support questions Receive automatic notice of product updates Find out about NetBackup for SAP training Read current white papers related to NetBackup for SAP From you can complete various tasks to obtain specific types of support for NetBackup for SAP: 1. Subscribe to the VERITAS notification service to be informed of software alerts, newly published documentation, Beta programs, and other services. a. From the main page, select a product family and a product. b. Under Support Resources, click Notifications. Your customer profile ensures you receive the latest VERITAS technical information pertaining to your specific interests. 2. Locate the telephone support directory at by clicking the Phone Support icon. A page appears that contains VERITAS support numbers from around the world. Note Telephone support for NetBackup for SAP is only available with a valid support contract. To contact VERITAS for technical support, dial the appropriate phone number listed on the Technical Support Guide included in the product box and have your product license information ready for quick navigation to the proper support group. 3. Contact technical support using . x NetBackup for SAP System Administrator s Guide for UNIX and Linux

11 Accessibility Features a. From the main page, click the Support icon. A wizard guides you to do the following: Select a language of your preference Select a product and a platform Provide additional contact and product information, and your message Associate your message with an existing technical support case b. After providing the required information, click Send Message. Contacting VERITAS Licensing For license information, you can contact us as follows: Call and select option 3 Fax questions to In the Americas, send to [email protected]. In the Asia and Pacific areas, send to [email protected]. In all other areas, send to [email protected]. Accessibility Features NetBackup contains features that make the user interface easier to use by people who are visually impaired and by people who have limited dexterity. Accessibility features include: Support for assistive technologies such as screen readers and voice input (Windows servers only) Support for keyboard (mouseless) navigation using accelerator keys and mnemonic keys For more information, see the NetBackup Installation Guide. Preface xi

12 Comment on the Documentation Comment on the Documentation Let us know what you like and dislike about the documentation. Were you able to find the information you needed quickly? Was the information clearly presented? You can report errors and omissions or tell us what you would find useful in future versions of our manuals and online help. Please include the following information with your comment: The title and product version of the manual on which you are commenting The topic (if relevant) on which you are commenting Your comment Your name your comment to Please only use this address to comment on product documentation. See Getting Help in this preface for information on how to contact Technical Support about our software. We appreciate your feedback. xii NetBackup for SAP System Administrator s Guide for UNIX and Linux

13 Introduction 1 NetBackup for SAP integrates the database backup and recovery capabilities of SAP with the backup and recovery management capabilities of NetBackup. NetBackup for SAP supports SAP environments based on the following databases: Oracle databases. In an Oracle environment, you can use the Oracle database either with or without the recovery manager (RMAN). SAP DB and MaxDB TM databases. This documentation describes using NetBackup for SAP with both SAP DB and MaxDB databases. For readability, the remainder of this manual uses only the term MaxDB to describe these database platforms. The SAP DB name refers to the 7.4 and earlier releases. The MaxDB name refers to the 7.5 and later releases. This chapter explains the differences and similarities between using NetBackup for SAP in each environment. For example, one major difference is that the SAP tools are supported only for Oracle databases. This chapter includes the following topics: NetBackup for SAP features NetBackup for SAP overview Note This manual differentiates between SAP on an Oracle database and SAP on a MaxDB database only when necessary to explain differences between using NetBackup for SAP with these specific databases. For most tasks, NetBackup for SAP operates the same way in each environment. 1

14 NetBackup for SAP Features NetBackup for SAP Features The following list shows NetBackup for SAP s main features and introduces some terms used in the NetBackup for SAP documentation. For more information on general NetBackup terminology, see the NetBackup System Administration Guide, Volume I. Feature Media and device management Scheduling facilities Multiplexed backups and restores Transparent execution of both SAP and regular file system backup and restore operations Sharing the same Media Manager and disk storage units used for other file backups Centralized and networked backup operations Description All devices supported by Media Manager are available to NetBackup for SAP. NetBackup scheduling facilities on the master server can be used to schedule automatic and unattended SAP backups. This also lets you choose the times when these operations can occur. For example, to prevent interference with normal daytime operations, you can schedule your database backups to occur only at night. NetBackup for SAP lets you take advantage of NetBackup s multiplexing capabilities. Multiplexing directs multiple data streams to one backup device, thereby reducing the time necessary to complete the operation. All backups and restores run simultaneously and transparently without any action from the NetBackup administrator. The database administrator can run database backup and restore operations through NetBackup. Alternatively, if you are using NetBackup for SAP on an Oracle database, you can use SAP Tools as if NetBackup were not present. An administrator or any other authorized user can use NetBackup to run database backups and restores. It is possible to share the same devices and media used for other backups or to give SAP exclusive use of certain devices and media. From the NetBackup master server, you can schedule database backups or start them manually for any client. The SAP databases can also reside on hosts that are different from the devices on which NetBackup stores the backups. 2 NetBackup for SAP System Administrator s Guide for UNIX and Linux

15 NetBackup for SAP Features Feature Graphical user interfaces Parallel backup and restore operations Description NetBackup provides the following graphical user interfaces for client users and administrators: NetBackup Administration Console for Java NetBackup Administration Console for Windows A database administrator or NetBackup administrator can start backup or restore operations for SAP from the NetBackup graphical user interface on the master server. NetBackup for SAP supports the parallel backup and restore capabilities of the SAP Tools. For example, this permits the user to run more than one tape device at a time for a single SAP backup or restore, thereby reducing the time necessary to complete the operation. Chapter 1, Introduction 3

16 NetBackup for SAP Overview NetBackup for SAP Overview The following sections provide a technical overview and explain the sequence of operation for NetBackup for SAP. Technical Overview The following example network shows the major components in a NetBackup for SAP configuration. The server that is hosting the Oracle or the MaxDB database must be a NetBackup client, and it must have NetBackup for SAP installed. NetBackup for SAP Environment on an Oracle or MaxDB Database System hosting the Oracle or MaxDB database Oracle or MaxDB database NetBackup for SAP supplies: backint Interface Sample script files Additional required NetBackup software: NetBackup Client Network (TCP/IP) NetBackup master server or remote media server Media Manager or disk storage unit NetBackup software: NetBackup Master Server NetBackup Media Server (if system is a media server) NetBackup for SAP assumes either an Oracle or a MaxDB database as the underlying database. The following additional components are present depending on the underlying database: 4 NetBackup for SAP System Administrator s Guide for UNIX and Linux

17 NetBackup for SAP Overview In an Oracle environment, the SAP tools perform database-related tasks. The brbackup, brarchive, and brrestore utilities communicate with NetBackup through the NetBackup for SAP backint interface. The sapdba component of SAP tools accesses the backup catalog used by NetBackup in order to determine the status of the valid backups. In a MaxDB environment, you initiate backups and restores through the MaxDB administrative interface. This interface can be the Database Manager Graphical User Interface (DBM GUI), the Database Manager Command Line Interface (DBM CLI), and the Web Database Manager (Web DBM). Chapter 1, Introduction 5

18 NetBackup for SAP Overview Sequence of Operation NetBackup users or schedules start database backups or restores by selecting an SAP script. A NetBackup process called bphdb starts the SAP script on the client if the backup is initiated by a policy on the master server. The SAP application then starts the requested operation on the databases. The following figure shows the sequence of operation: NetBackup for SAP Operations Database Files SAP Tools or MaxDB Administrative Interface (DBM CLI) NetBackup for SAP backint NetBackup XBSA API Script Command Line NetBackup Client bphdb NetBackup Master Server Scheduler NetBackup For a backup, brbackup calls the NetBackup for SAP backint interface. The backint interface calls the XBSA API to interface with NetBackup. A restore works similarly except that the NetBackup for SAP backint interface calls the XBSA API, causing NetBackup to retrieve the data from secondary storage and send it to the client. NetBackup for SAP on Oracle Databases The following sections provide an overview of the software in a NetBackup for SAP on Oracle database environment. You can use NetBackup for SAP on Oracle databases either with or without the recovery manager (RMAN). The following subsections explain the components in Oracle environments with and without RMAN. 6 NetBackup for SAP System Administrator s Guide for UNIX and Linux

19 NetBackup for SAP Overview Using NetBackup for SAP on Oracle Databases Without RMAN The following figure shows the components found in a NetBackup for SAP on Oracle database environment: Software Components in a NetBackup for SAP on Oracle Database Environment Oracle Database SAP Environment sapdba SAP Tools brbackup brrestore brarchive brconnect NetBackup for SAP backint Interface NetBackup XBSA API Using NetBackup for SAP on Oracle Databases With RMAN NetBackup for SAP implements the Oracle Defined SBT interface, which integrates the SAP tools with RMAN. You do not need to use RMAN to use NetBackup for SAP on Oracle databases, but the benefits of using RMAN backups are as follows: RMAN supports incremental backups, which are backups of only those blocks that have changed since the previous backup. This reduces the number of blocks that are backed up. Unused and unchanged database blocks are not backed up. RMAN detects logical errors in database blocks during backup processing. The BEGIN BACKUP and END BACKUP commands are not needed for online backups because RMAN performs a block-by-block check to verify data consistency. This reduces the amount of redo log information. You can use RMAN s verify command to verify backups. The following diagram shows a NetBackup for SAP on Oracle database environment that includes RMAN: Chapter 1, Introduction 7

20 NetBackup for SAP Overview Software Components in a NetBackup for SAP on Oracle Database Environment with RMAN SAP Tools Oracle Database Phase 2 Phase 1 RMAN Oracle Server libobk (liborasap) (NetBackup for Oracle) Control Files Profiles Log Files backint NetBackup for SAP NetBackup Media Manager or Disk Storage Unit Local Disk If you are in a NetBackup for SAP on Oracle database environment with RMAN, the backup consists of two phases: Phase 1 backs up the Oracle database files. Phase 2 backs up the SAP control, log, and configuration files. 8 NetBackup for SAP System Administrator s Guide for UNIX and Linux

21 NetBackup for SAP Overview SAP Tools Overview The SAP Environment consists of many modules and applications. One component is the SAP tools. You can use the SAP tools whether or not you also use RMAN. The following table shows the software included in the SAP tools. SAP Tools Software Component sapdba brbackup brarchive brrestore SAP script Function sapdba is a menu-driven utility, with menus designed to reflect the user s point of view. sapdba provides easy access to brbackup, brarchive, and brrestore for database backups and restores. The tool can restore a backup of an entire database or reset the database to a previous state. This command brings database servers online or offline, checks the status of SAP files, and places database tablespaces into BACKUP mode to guarantee their data consistency. The brbackup command provides online and offline backups. It also keeps a profile and log of each backup. brbackup uses the NetBackup software, through NetBackup for SAP, for the following actions: SAP datafile backups Datafile and online log backups Error handling This command archives Oracle offline redo log files by communicating with the NetBackup for SAP backint interface. These files are copied by Oracle in its archiving directory. The brarchive command ensures that duplicates of these logs are available and that original files are not deleted prematurely. This command also keeps a profile and log of each archive. This command recovers database data files, control files, and online redo log files through the NetBackup for SAP backint interface. The brrestore command ensures that sufficient space is available prior to restoring these files, and it removes files that will be overwritten during the recovery. This command also provides a query mode. This is a small script that contains SAP commands such as brbackup and brrestore. Chapter 1, Introduction 9

22 NetBackup for SAP Overview NetBackup for SAP on MaxDB Databases The following figure shows the components found in a NetBackup for SAP on MaxDB database environment. Software Components for a NetBackup for SAP on MaxDB Database Environment DBM CLI DBM GUI Web DBM MaxDB Server MaxDB Instance Named Pipes NetBackup for SAP (backint) NetBackup 10 NetBackup for SAP System Administrator s Guide for UNIX and Linux

23 Installation 2 This chapter describes how to perform the following tasks: Verifying the installation prerequisites for NetBackup for SAP. Perform this task before installing this agent. Installing NetBackup for SAP. Enabling functions specific to NetBackup for SAP. Verifying the Installation Prerequisites Before installing NetBackup for SAP, verify that you are installing the agent on a supported operating system or platform and that requirements are met for the NetBackup software, the database agent, and, if applicable, the cluster software. These requirements apply for remote and local installations. Operating System and Platform Compatibility Verify that NetBackup for SAP will be installed on an operating system or platform supported by NetBackup. A compatibility list for database agents is available on the Technical Support web site. To verify compatibility 1. Go to the Technical Support web page: 2. From the Select Product Family list, click NetBackup Products. 3. From the Select Product list in the right pane, click NetBackup Enterprise Server. 4. Under Support Resources, click Compatibility and Reference. 11

24 Verifying the Installation Prerequisites 5. In the list of documents, click NetBackup Enterprise Server (tm)/ Server x.x Database Agent Compatibility (updated date). For x.x, look for the current release. For date, look for the most recent date. For information on supported cluster environments for NetBackup for SAP, see NetBackup (tm) x.x Cluster Compatibility (updated date). 6. Click on the link for the PDF document, which is a downloadable file that enables you to view the supported database spreadsheet for this release. 7. Read the document and verify that the software in your environment is compatible with the NetBackup and NetBackup for SAP software. NetBackup Software Verify that the following requirements are met for the NetBackup server and client software: The NetBackup server software is installed and operational on the NetBackup server. The NetBackup server platform can be any of those that NetBackup supports. For installation information, see the NetBackup Installation Guide. The NetBackup client software is installed on the client where you will be backing up the databases. The version of the NetBackup client and the version of NetBackup for SAP to be installed must be the same (for example, 6.0). There must be adequate disk space on each machine upon which you are installing NetBackup for SAP. Less than two megabytes of additional disk space is required in the /usr/openv/netbackup directory. However, more disk space might be needed at run time. Make sure that you have configured backup media in a Media Manager or disk storage unit. The amount of backup media required depends on the devices used, the sizes of the databases that you are backing up, the amount of data that you are archiving, the size of your backups, and the frequency of backups or archives. For information on using Media Manager, see the NetBackup Media Manager System Administrator s Guide. Database Software Verify the following regarding the database software on the NetBackup client: 12 NetBackup for SAP System Administrator s Guide for UNIX and Linux

25 Verifying the Installation Prerequisites SAP vendor software must be installed and operational. One or more SAP instances must exist. For information on installing SAP and creating instances, see your SAP documentation. Cluster Software Verify the following requirements if you are installing the NetBackup for SAP software on a NetBackup server configured in a NetBackup cluster: The SAP vendor software is installed and operational on each node to which NetBackup can failover. The NetBackup server software is installed and configured to work in a NetBackup cluster. Follow the instructions in the NetBackup Installation Guide, including running the cluster_config script after the NetBackup server software has been installed. You only need to run the cluster_config script after you install the NetBackup server software. You do not need to run cluster_config after installing NetBackup for SAP on a NetBackup server that is part of a NetBackup cluster. The following additional information also pertains to cluster environments: Make sure you install the NetBackup client software and the NetBackup for SAP software on each node to which NetBackup can failover. Run commands such as bpplclients and update_dbclients from the active NetBackup master or media server. If you plan to perform a remote installation, in which you push the database agent software to clients located in a cluster, specify the individual node names, not the virtual names, in the client list. Chapter 2, Installation 13

26 Installing NetBackup for SAP Installing NetBackup for SAP You can install the database agent software in one of the following ways: A remote installation. The user loads the software onto a master server or a media server and then pushes the database software out to the clients. You can perform an initial or upgrade remote installation in this manner. Remote Installation of NetBackup for SAP on page 14 describes this procedure. A local installation. The user loads and installs the software onto the local machine only. Local Installation of NetBackup for SAP on page 22 describes this procedure. Remote Installation of NetBackup for SAP During a remote installation, you load the NetBackup for SAP files onto either a UNIX master server or media server, and then you push the software to the clients to install it. Loading the NetBackup for SAP Files onto the Server To load the NetBackup for SAP files on a UNIX server 1. Review Verifying the Installation Prerequisites on page 11. If you are installing NetBackup for SAP on a clustered NetBackup server, be sure to read Cluster Software on page (Conditional) Perform this step only if you are installing on a server that is part of a NetBackup cluster. a. Freeze the active NetBackup node. When you install NetBackup for SAP, install the software on all the inactive nodes first, then install on the active node. For information on how to freeze the active node in your specific cluster environment, see the NetBackup High Availability System Administrator s Guide. b. Decide which of the inactive nodes to install the software on first. In the next step, you log in to the first machine and commence the installation process. Because you need to perform the installation on all inactive nodes first, make sure that the first machine you select is an inactive node. 3. Log in as the root user on the master or media server. If you are already logged in, but are not the root user, run the following command: 14 NetBackup for SAP System Administrator s Guide for UNIX and Linux

27 Installing NetBackup for SAP su - root 4. Verify that a registered and valid license key for NetBackup for SAP resides on the master server. You can obtain master server license information from either the master server or the media server. To view or add license keys, perform one of the following actions: From the master or media server, run the following command: /usr/openv/netbackup/bin/admincmd/get_license_key When the system prompts you, type the host name of the NetBackup master server. Open the NetBackup Administration Console and choose Help > License Keys. If the NetBackup master server is part of a NetBackup cluster, the license key must be registered on each node. 5. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide. 6. Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point 7. Invoke the install script to load and install the software. For example:./install a. Select the NetBackup Database Agent Software option. The following prompt appears: Do you want to do a local installation? (y/n) [n] b. Answer n. A menu of all database agents available on the CD-ROM displays. c. Select the NetBackup for SAP option. d. Type q to quit selecting options. A prompt appears asking if the list is correct. Chapter 2, Installation 15

28 Installing NetBackup for SAP e. Answer y. The install script identifies the types of client software loaded during the installation of the NetBackup server. By default, any matching NetBackup for SAP software is automatically loaded. If there are more platforms available, the script displays a menu that gives you the opportunity to add more client types to the default list. After the list is complete, the installation script copies database agent version files, tar(1) files compressed with gzip(1), and the install_dbext script to directory /usr/openv/netbackup/dbext. 8. (Conditional) Select another node upon which to install the software. Perform this step under the following circumstances: If you are installing the NetBackup for SAP software on a server that is part of a NetBackup cluster. and If you have nodes that still need to have the software installed. If there are inactive nodes that do not yet have the software installed upon them, select one of these inactive nodes, and repeat step 3 through step 8 for that node. If you have installed the software on all the inactive nodes, select the active node and repeat step 3 through step 8 for that node. If you have installed on all the nodes, proceed to step (Conditional) Unfreeze the active node. Perform this step if you are installing the NetBackup for SAP software on a server that is part of a NetBackup cluster. Unfreezing the active node is the last step in the installation process. Unfreeze the active node only after all the software has been installed on all nodes. For information on how to unfreeze the active node in your specific cluster environment, see the NetBackup High Availability System Administrator s Guide. 10. Decide how you want to distribute the NetBackup for SAP software to the clients. Regardless of whether you are upgrading clients in an existing environment or you are performing a new installation, use one of the following methods: Distribute to all clients currently specified in a SAP policy type. This method distributes the NetBackup for SAP software to all clients that are currently included in a SAP policy type. You can use this method only if you are pushing from a master server. For information on this method, see Pushing the Software to All Clients Currently Specified in an SAP Policy Type on page NetBackup for SAP System Administrator s Guide for UNIX and Linux

29 Installing NetBackup for SAP Distribute to selected clients. This method distributes the NetBackup for SAP software to selected clients only. If you are performing a new installation, and you plan to add clients to a SAP policy type after you install the software, you can install the software on such clients now and configure the policy later. This method also allows you to skip clients that you do not want to upgrade to 6.0 at this time. You can use this method whether you are pushing from a master server or from a media server. For information on this method, see Pushing the Software to New or Selected Clients on page 20. Note Make sure that the NetBackup for SAP version is the same version as the NetBackup client software. Pushing the Software to All Clients Currently Specified in an SAP Policy Type Use the following procedure if you want to install or upgrade the NetBackup for SAP software on all clients currently configured in an SAP policy type. You can use this procedure only from a master server. To push the software to all clients specified in an SAP policy type Note If you are pushing the NetBackup for SAP software from a server that is part of a NetBackup cluster, type all commands in this procedure from the active NetBackup node. 1. Run the update_dbclients command to launch the installation script. Type the following command: /usr/openv/netbackup/bin/update_dbclients SAP ALL ALL 2. Examine the client list that the update_dbclients command returns. a. Locate the client list. The update_dbclients command compiles a list of clients that it detects are included in a SAP policy type. It presents this list to you. If 9 or fewer clients are in the client list, update_dbclients displays all the client names. If 10 or more clients are on the client list, update_dbclients writes the first 9 to standard output and writes the entire list to $TMPDIR/NB_DBCLIENT_LIST.identifier, where identifier is a mix of date, time, and process identifier information. If the TMPDIR environment variable is not set, the default is /tmp. b. Check the client list. Chapter 2, Installation 17

30 Installing NetBackup for SAP The host names of the clients must be the clients individual node names. They cannot be virtual names. The correct value for the individual node names is returned by the hostname(1) and the domainname(1) commands. The format can be either hostname or hostname.domainname. If the client list contains virtual names, you cannot complete this procedure. Do one of the following: To exit this procedure if there are two or more clients, press the Enter key and then type n to stop the upgrade and exit from this installation dialog. To install the software in this situation, use Pushing the Software to New or Selected Clients on page 20. To exit this procedure if there is only one client, type n. To install the software in this situation, use Pushing the Software to New or Selected Clients on page 20. If the client list contains only individual node names, proceed to the following step. c. Check the skipped client list, if any. If update_dbclients detects that it cannot update a particular client, it does not include the name of that client in the client list. Such clients are skipped for one or more of the following reasons: The client is a PC client. You cannot install or upgrade NetBackup for SAP on a PC client from a UNIX server. The database agent does not support the client's platform type. The database agent software for that client type was not loaded onto the server in To load the NetBackup for SAP files on a UNIX server on page 14. The client does not belong to an SAP policy type. The skipped client list is in $TMPDIR/skipped_clients.PID, where PID is the process identifier. If the TMPDIR environment variable is not set, the default is /tmp. If no file is present, no clients were skipped. 3. (Conditional) Specify the number of simultaneous client updates. If you are updating more than one client, the installation software displays the number of updates required to distribute the software to the clients. If the software detects the need to update more than one client, it displays the following prompt: 18 NetBackup for SAP System Administrator s Guide for UNIX and Linux

31 Installing NetBackup for SAP Enter the number of simultaneous updates you wish to take place. [1 - max] (default: dflt) max dflt The maximum number of simultaneous updates that is allowed. The value displayed ranges from 1 to 30. The number the program uses if you press Enter without specifying a number. The value displayed ranges from 1 to 15. If you want the installation software to perform dflt simultaneous updates, press Enter. If you want to specify a different number of simultaneous updates, type a number in the range 1 number max, and then press Enter. For example, if three clients are to be updated, the max and dflt values are 3. If 50 clients are to be updated, the max value is 30, and the dflt value is 15. update_dbclients starts the number of updates that you specify. If this number is less than the total number of client updates to be performed, new updates start as the previous updates finish until all of the updates have been completed. 4. Indicate whether or not you want to upgrade the clients at this time. Based on your answer, the time it will take to update the clients is displayed, followed by this question: Do you want to upgrade the clients now? (y/n) [y] Type y or n for the prompt. If you answer n, update_dbclients quits and leaves the list of clients it would have updated in a file. You can use this file later as the argument to the -ClientList parameter. By default, the installation software writes the client list to $TMPDIR/NB_DBCLIENT_LIST.identifier, where identifier is a mix of date, time, and process identifier information. If the TMPDIR environment variable is not set, the default is /tmp. If you answer y, you continue the installation process. The following actions occur: The update_dbclients command distributes the software to the client. If it is successful, update_dbclients invokes the install_dbext script on the client. The install_dbext script runs on each client. If it is successful, it writes a version file in directory /usr/openv/share that contains the version of NetBackup for SAP that was installed. Chapter 2, Installation 19

32 Installing NetBackup for SAP The update_dbclients command displays a note on whether the update was successful for each client. When the update_dbclients command completes, it displays a file name that contains a complete log of what happened for each client. If the update failed for any client, examine the log file to determine the problem. Pushing the Software to New or Selected Clients Use the following procedure if you want to install or upgrade the NetBackup for SAP software on selected clients. You can use this procedure from either a master server or from a media server. To push the software to new or selected clients Note If you are pushing the NetBackup for SAP software from a server that is part of a NetBackup cluster, type all commands in this procedure from the active NetBackup node. 1. On the master server, type the following command to ensure that the bpdbm daemon is running: /usr/openv/netbackup/bin/bpps If the output shows that the bpdbm daemon is not running, type the following command to start the daemon: /usr/openv/netbackup/bin/initbpdbm 2. Type the following command to change to the NetBackup bin directory: cd /usr/openv/netbackup/bin 3. Use the bpplclients(1m) command to create a file that contains a list of clients currently configured in the NetBackup database. The options to use on this command differ depending on whether you are installing from a master server or from a media server, as follows: If you are performing the install from the master server, type the following command:./admincmd/bpplclients -allunique -noheader > file If you are performing the install from a media server, type the following command: 20 NetBackup for SAP System Administrator s Guide for UNIX and Linux

33 Installing NetBackup for SAP./admincmd/bpplclients -allunique -noheader -M ms_name > file ms_name file Name of the NetBackup master server in this environment. Name of the file to contain the list of unique clients. If no clients have been configured in the NetBackup database, file is empty. Create file using the same format as that generated by bpplclients. bpplclients writes output to file in the following format: hardware op_system client hardware The hardware name. For examples, execute the ls(1) command in directory /usr/openv/netbackup/client. op_system The operating system name. For examples, execute the ls(1) command in directory /usr/openv/netbackup/client/hardware. client The name of the client. For example, file might contain a line like the following: Solaris Solaris8 curry 4. (Optional) Edit file. Perform this step to change the contents of file. Edit file to contain only those clients you want to update with NetBackup for SAP software. The host names of the clients must be the clients individual node names. They cannot be virtual names. The correct value for the individual node names is returned by the hostname(1) and the domainname(1) commands. The format can be either hostname or hostname.domainname. 5. Run the update_dbclients command to install the software. Specify the file you created in step 3 as the argument to update_dbclients. The command installs the software on the clients listed in file. For example:./update_dbclients SAP -ClientList file 6. Answer questions as prompted by the update_dbclients command. Chapter 2, Installation 21

34 Installing NetBackup for SAP The update_dbclients command initiates a dialog with you. It asks you to confirm actions during the update process and presents options to you if there are choices to be made. For information about this dialog, see the instructions starting with step 2 on page 17. Note You do not need to run the cluster_config script after installing NetBackup for SAP on a server that is part of a NetBackup cluster. Local Installation of NetBackup for SAP During a local installation, the NetBackup for SAP files are extracted and installed. The local machine can be a client or a server that also happens to be a NetBackup for SAP client. To install NetBackup for SAP on a local machine 1. Review Verifying the Installation Prerequisites on page 11. If you are installing NetBackup for SAP on a clustered NetBackup server, also see Cluster Software on page (Conditional) Perform this step only if you are installing on a server that is part of a NetBackup cluster. a. Freeze the active NetBackup node. When you install NetBackup for SAP, install the software on all the inactive nodes first, then install on the active node. For information on how to freeze the active node in your specific cluster environment, see the NetBackup High Availability System Administrator s Guide. b. Decide which of the inactive nodes to install the software on first. In the next step, you log in to the first machine and commence the installation process. Because you need to perform the installation on all inactive nodes first, make sure that the first machine you select is an inactive node. 3. Log in as the root user on the machine. If you are already logged in, but are not the root user, run the following command. su - root 4. (Conditional) Log into a media server or the master server. Perform this step if the local machine is a NetBackup client. 22 NetBackup for SAP System Administrator s Guide for UNIX and Linux

35 Installing NetBackup for SAP 5. Verify that a registered and valid license key for NetBackup for SAP resides on the master server. You can obtain master server license information from either the master server or the media server. To view or add license keys, perform one of the following actions: From the master or media server, type the following command: /usr/openv/netbackup/bin/admincmd/get_license_key When the system prompts you, type the host name of the NetBackup master server. Open the NetBackup Administration Console and choose Help > License Keys. If the NetBackup master server is part of a NetBackup cluster, the license key must be registered on each node. 6. (Conditional) Log out of the media server or master server and return to the local client. Perform this step if you logged into a media server or the master server in step 4 to verify the license. 7. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide. 8. Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point 9. Load and install the software by running the install script. Note Make sure that the NetBackup for SAP version is the same version as the NetBackup client software. Type the following command:./install a. Select the NetBackup Database Agent Software option. The following prompt appears: Do you want to do a local installation? (y/n) [n] b. Answer y. Chapter 2, Installation 23

36 Installing NetBackup for SAP A menu of all database agents available on the CD-ROM displays. c. Select the NetBackup for SAP option. d. Type q to quit selecting options. A prompt appears asking if the list is correct. e. Answer y. The following actions occur: The script writes the version file, a tar(1) file compressed with gzip(1), and the install_dbext script to directory /usr/openv/netbackup/dbext. The install script automatically runs the install_dbext script. If install_dbext completes successfully, it writes a version file in directory /usr/openv/share that contains the version of NetBackup for SAP that was installed. f. Type q to quit from the script. Note You do not need to run the cluster_config script after installing NetBackup for SAP on a server that is part of a NetBackup cluster. 10. (Conditional) Select another node upon which to install the software. Perform this step under the following circumstances: If you are installing the NetBackup for SAP software on a server that is part of a NetBackup cluster. and If you have nodes that still need to have the software installed. If there are inactive nodes that do not yet have the software installed upon them, select one of these inactive nodes and repeat step 3 through step 10 for that node. If you have installed the software on all the inactive nodes, select the active node and repeat step 3 through step 10 for that node. If you have installed on all the nodes, proceed to step (Conditional) Unfreeze the active node. Perform this step if you are installing the NetBackup for SAP software on a server that is part of a NetBackup cluster. Unfreezing the active node is the last step in the installation process. Unfreeze the active node only after all the software has been installed on all nodes. 24 NetBackup for SAP System Administrator s Guide for UNIX and Linux

37 Linking NetBackup for SAP with backint (Oracle Databases without RMAN Only) For information on how to unfreeze the active node in your specific cluster environment, see the NetBackup High Availability System Administrator s Guide. Linking NetBackup for SAP with backint (Oracle Databases without RMAN Only) Perform the linking described in this section only if you are using NetBackup for SAP with an Oracle database but without the Oracle recovery manager (RMAN). SAP requires that all SAP tools be located in a predetermined directory. The directory path is as follows: /usr/sap/sid/sys/exe/run SID A unique name for an Oracle database instance. SID is also known as the System ID. The directory should contain the following commands: brarchive brbackup brconnect brrestore brtools sapdba To link the NetBackup for SAP binary file Link backint from the NetBackup install directory to the SAP tools directory. For example, if the Oracle instance name is CER, enter the following command: ln -s /usr/openv/netbackup/bin/backint \ /usr/sap/cer/sys/exe/run/backint Chapter 2, Installation 25

38 Linking the Oracle Database with the SBT Library (Oracle Databases with RMAN Only) Linking the Oracle Database with the SBT Library (Oracle Databases with RMAN Only) Perform the linking described in this section only if you are using NetBackup for SAP with an Oracle database and the Oracle recovery manager (RMAN). The exact linking command to use depends on your operating system platform. To link the NetBackup for SAP binary file on HP-UX Platforms Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.sl \ $ORACLE_HOME/lib/libobk.sl To link the NetBackup for SAP binary file on AIX, Red Hat Linux (Linux X86), Solaris, or Tru64 Platforms Enter the following command to copy the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so \ $ORACLE_HOME/lib/libobk.so 26 NetBackup for SAP System Administrator s Guide for UNIX and Linux

39 Configuration 3 Before attempting to configure NetBackup for SAP, complete the installation procedure as described in the Installation chapter. The configuration procedure consists of the following steps: 1. Configuring the Maximum Jobs Per Client 2. Configuring Backup Policies 3. Creating Scripts 4. Modifying the Configuration Files 5. Testing Configuration Settings 6. Testing Multiple Drives and Files The following sections describe these steps. Note If you are using NetBackup for SAP on an Oracle database, all the information in this chapter applies to you. If you are using NetBackup for SAP on a MaxDB database, this section notes a few differences. In addition, you should also see NetBackup for SAP on MaxDB Databases on page 71 for additional information. User Interface Terminology Notes You can perform many of the configuration steps in this chapter from the NetBackup Administration Console on the master server. Depending on your master server s platform, the console is available in one or two forms. NetBackup supports a Java interface for both Windows and UNIX master servers. In addition, NetBackup supports a Windows interface for Windows master servers. 27

40 Configuring the Maximum Jobs Per Client The Java and Windows interfaces are nearly identical, but when there are interface differences in the configuration procedures, this manual uses the following headings to identify the interface being described: From the Windows interface: From the Java interface: Configuring the Maximum Jobs Per Client To configure the Maximum jobs per client 1. In the left pane of the NetBackup Administration Console, expand Host Properties. 2. Select Master Server. 3. In the right pane, double-click on the server icon. The Master Server Properties dialog box displays. 4. In the Master Server Properties dialog box, click Global Attributes. 5. Change the Maximum jobs per client value to 99. The Maximum jobs per client specifies the maximum number of concurrent backups allowed per client. The default is 1. You can use the following formula to calculate a smaller value: Maximum jobs per client = number_of_drives X number_of_policies number_of_drives number_of_policies The number of concurrent brbackup jobs. The drives parameter in the initsid.utl file defines these jobs. The number of policies of any type that can back up this client at the same time. This number can be greater than one. For example, a client can be in two policies in order to back up two different databases. These backup windows can overlap. 28 NetBackup for SAP System Administrator s Guide for UNIX and Linux

41 Configuring the Maximum Jobs Per Client Tip Enter a large enough value for the Maximum jobs per client attribute to meet the number of jobs executed by SAP. You might need to experiment with different values at your site. Chapter 3, Configuration 29

42 Configuring Backup Policies Configuring Backup Policies A NetBackup policy defines the backup criteria for a specific group of one or more clients. These criteria include: Storage unit and media to use Policy attributes Backup schedules Clients to be backed up The script files to be executed on the clients To use NetBackup for SAP, you need to define at least one SAP policy with the appropriate schedules. A configuration can have a single policy that includes all clients, or there can be many policies, some of which include only one client. Most requirements for SAP policies are the same as for file system backups. In addition to the attributes described here, there are other attributes for a policy to consider. For configuration instructions and information on all the attributes available, see the NetBackup System Administrator s Guide, Volume I. Adding a New Policy To add a new policy 1. Log on to the master server as administrator (Windows) or root (UNIX). 2. Start the NetBackup Administration Console. 3. If your site has more than one master server, choose the one on which you want to add the policy. 4. From the Windows interface: In the left pane, right-click Policies and choose New Policy. From the Java interface: In the left pane, click Policies. In the All Policies pane, right-click the master server, and click New. The Add a New Policy dialog box displays. 5. In the Policy name field, type a unique name for the new policy. 6. Click OK. A dialog box displays in which you can specify the general attributes for the policy. 30 NetBackup for SAP System Administrator s Guide for UNIX and Linux

43 Configuring Backup Policies 7. From the Policy Type box, select the SAP policy type. Note The SAP policy type does not appear in the drop-down list unless your master server has a license key for NetBackup for SAP. 8. Complete the entries on the Attributes tab. For more information, see Description of Attributes, which follows this procedure. 9. Add other policy information. To add schedules, see Adding Schedules on page 32. To add clients, see Adding Clients on page 37. To add scripts to the Backup Selections list, see Adding Backup Selections on page When you have added all the schedules, clients, and Backup Selections you need, click OK. The new policy is created. Description of Attributes With a few exceptions, NetBackup manages a database backup like a file system backup. The following table shows the policy attributes that are different for SAP backups. This information is used when you are adding a new policy. Other policy attributes vary according to your specific backup strategy and system configuration. For more information on policy attributes, see the NetBackup System Administrator s Guide, Volume I. Description of Policy Attributes Attribute Policy type Keyword phrase Description Determines the types of clients that can be in the policy and, in some cases, the types of backups that NetBackup can perform on those clients. To use NetBackup for SAP, you must define at least one policy of type SAP. For NetBackup for SAP, the Keyword phrase entry is ignored. Chapter 3, Configuration 31

44 Configuring Backup Policies Adding Schedules Each policy has its own set of schedules. These schedules initiate automatic backups and specify when a user can initate operations. An SAP backup requires an Application Backup schedule, which is created automatically when you create an SAP policy. The Application Backup schedule manages the backup operation. You also need one or more automatic backup schedules if you plan to have NetBackup perform automatic or scheduled backups. To configure an Application Backup schedule 1. In the Policy dialog, click the Schedules tab. To access the Policy dialog, double-click the policy name in the Policies list in the NetBackup Administration Console. 2. Double-click on the schedule named Default-Application-Backup. A dialog box displays. The title bar shows the name of the policy to which you are adding the schedule. All SAP backup operations are performed through NetBackup for SAP using an Application Backup schedule. This includes backups that start automatically. Configure an Application Backup schedule for each SAP policy you create. If you do not do this, you cannot perform a backup. To help satisfy this requirement, an Application Backup schedule named Default-Application-Backup is automatically created when you configure a new SAP policy. 3. Specify the other properties for the schedule as explained in Schedule Properties. The backup window for an Application Backup schedule must encompass the time period during which all NetBackup for SAP jobs, scheduled and unscheduled, can occur. This is necessary because the Application Backup schedule starts processes that are required for all NetBackup for SAP backups, including those started automatically. For example, assume the following: Users perform SAP backup operations during business hours, 0800 to Automatic backups that use this policy commence between 1800 and NetBackup for SAP System Administrator s Guide for UNIX and Linux

45 Configuring Backup Policies The Application Backup schedule must have a start time of 0800 and a duration of 14 hours. Example Settings for an Application Backup schedule Type of Backup Schedule settings Description Settings Application Backup Retention The length of time the backup images are retained in the NetBackup catalog for restore. 2 weeks Backup Window The time during which a NetBackup operation can be initiated. Sunday through Saturday 00:00:00-24:00:00 Note You can specify the Application Backup schedule name in the initsid.utl file on the client. Tip Set the time period for the Application Backup schedule for 24 hours per day, seven days per week. This ensures that your NetBackup for SAP operations are never locked out due to the Application Backup schedule. To configure an automatic backup schedule 1. On the Policy dialog, click the Schedules tab. 2. Click New. A dialog box displays. The title bar shows the name of the policy to which you are adding the schedules. 3. Specify a unique name for the schedule. 4. Select the Type of backup. For information on the types of backups available for this policy, see Types of Backup Schedules. Chapter 3, Configuration 33

46 Configuring Backup Policies 5. Specify the other properties for the schedule as explained in Schedule Properties, which follows this procedure. The following table shows example settings for an automatic backup schedule: Example Settings for an Automatic Backup Schedule Type of Backup Schedule settings Description Settings Automatic Backup Retention The length of time to store the record of a backup, which NetBackup uses to determine if the schedule needs to be run. 2 weeks Frequency Backup Window Frequency determines how often a backup should be performed The time during which a NetBackup operation can be initiated. every week Sunday, 18:00:00-22:00:00 6. If this is the last schedule, click OK. To add other schedules, repeat step 1 through step 6. Types of Backup Schedules You can perform backups with the following types of schedules: SAP Backup Types Application Backup Automatic Full Backup Automatic Incremental Backup The Application Backup schedule enables user-controlled NetBackup operations from the client, both those initiated from the client and those initiated by an automatic schedule on the master server. NetBackup uses the Application Backup schedule when the SAP user starts a backup manually. Configure at least one Application Backup schedule for each SAP policy. The Default-Application-Backup schedule is configured automatically as an Application Backup schedule. An Automatic Full Backup schedule specifies the dates and times for NetBackup to automatically start backups by running the SAP scripts in the order that they appear in the file list. If there is more than one client in the SAP policy, the SAP scripts are run on each client. An Automatic Incremental Backup is a backup of only those blocks that have changed since the last Automatic Full (baseline) Backup. This kind of backup takes less time and space than a full backup because the Automatic Incremental Backup contains only the changed data. NetBackup for SAP supports this type of backup in MaxDB environments and in Oracle environments with RMAN. 34 NetBackup for SAP System Administrator s Guide for UNIX and Linux

47 Configuring Backup Policies Schedule Properties Some of the schedule properties have a different meaning for database backups than for a regular file system backup. The following table explains the schedule properties: Description of Schedule Properties Property Type of backup Frequency Calendar Description Specifies the type of backup that this schedule controls. The selection list shows only the backup types that apply to the policy you are configuring. For more information, see Types of Backup Schedules. This setting is used only for scheduled backups and not for user-directed backups. Frequency specifies the period of time that can elapse until the next backup or archive operation begins on this schedule. For example, if the frequency is seven days and a successful backup occurs on Wednesday, the next full backup does not occur until the following Wednesday. Typically, incremental backups have a shorter frequency than full backups. This setting is used only for scheduled backups. It is not used for user-directed backups. The Calendar option allows you to schedule backup operations based on specific dates, recurring week days, or recurring days of the month. Chapter 3, Configuration 35

48 Configuring Backup Policies Description of Schedule Properties (continued) Property Retention Multiple copies Description Frequency-based scheduling The retention period for an Application Backup schedule refers to the length of time that NetBackup keeps backup images. The retention period for an Automatic Backup schedule controls how long NetBackup keeps records of when scheduled backups have occurred. Set a retention period that is longer than the frequency setting for the schedule. For example, if the frequency setting is set to one week, set the retention period to be more than one week. The NetBackup scheduler compares the latest record of the Automatic Backup schedule to the frequency of that Automatic Backup schedule to determine whether a backup is due. This means that if you set the retention period to expire the record too early, the scheduled backup frequency is unpredictable. However, if you set the retention period to be longer than necessary, the NetBackup catalog accumulates unnecessary records. Calendar-based scheduling The retention period for an Application Backup schedule refers to the length of time that NetBackup keeps backup images. The retention period for an Automatic Backup schedule controls how long NetBackup keeps records of when scheduled backups have occurred. However, this setting is not significant for calendar-based scheduling. If you want to specify multiple copies for your SAP policy, configure Multiple copies on the Application Backup schedule. Other schedule properties vary according to your specific backup strategy and system configuration. For more information on schedule properties, consult the NetBackup System Administrator s Guide, Volume I. 36 NetBackup for SAP System Administrator s Guide for UNIX and Linux

49 Configuring Backup Policies Adding Clients The client list is the list of clients on which your SAP scripts are run during an automatic backup. A NetBackup client must be in at least one policy but can be in more than one. The following software must be installed on the client: SAP NetBackup client or server NetBackup for SAP The backup or restore script(s) To add clients to a policy 1. In the Policy dialog, click the Clients tab. To access the Policy dialog, double-click the policy name in the Policies list in the NetBackup Administration Console. 2. Click New. 3. Enter the name of the client you want to add. If SAP is installed in a NetBackup cluster, specify the virtual SAP name as the client name. From the Windows interface: Type the name into the client list and press Enter. If NetBackup cannot detect the hardware and operating system, a dialog box displays so you can specify this information. OR Click the Browse for Computer button to choose the client from the network. From the Java interface: a. The Add Client dialog box displays. In the Client name field, type the name of the client you are adding. b. Choose the Hardware and operating system type and click Add. 4. To add another client, repeat step 2 and step If this is the last client, click OK. Chapter 3, Configuration 37

50 Configuring Backup Policies Adding Backup Selections The backup selections list in a database policy has a different meaning than for non-database policies. For example, in a Standard policy, the list contains files and directories to be backed up. In a NetBackup for SAP database policy, you specify scripts to be run. Observe the following when using scripts: Make sure the scripts reside on each client in the client list. Scripts can reside in any location. Make sure that NetBackup can access the location you choose and that NetBackup can run the scripts. NetBackup installs sample scripts when you install the software, and you can modify these scripts for your own use. As part of the modification process, write the scripts to a location outside of the original installation location so future NetBackup installations do not overwrite your site s scripts. If you are using NetBackup for SAP in a NetBackup server cluster, make sure that the scripts reside in a location that is available after a failover. Add scripts only if you are setting up a policy for automatic scheduling. All scripts listed in the backup selections list are run for manual backups and for Automatic Backup schedules as specified under the Schedules tab. NetBackup runs the scripts in the order that the scripts appear in the Backup Selections list. For more information on backup scripts, see Creating Scripts on page 40. To add scripts to the backup selections list The following steps show how to perform this procedure from both the Java interface and from the Windows interface. Caution Be sure to specify the correct script names in the Backup Selections list to prevent an error or possibly a wrong operation. Make sure that the script resides on the client before you try to add it to the Backup Selections list. From the Java interface: 1. Open the Policy dialog. To access the Policy dialog, double-click the policy name in the Policies list in the NetBackup Administration Console. 2. Click the Backup Selections tab. 3. Click New. A dialog box displays. 38 NetBackup for SAP System Administrator s Guide for UNIX and Linux

51 Configuring Backup Policies 4. Specify the names of the scripts that you want NetBackup to use. a. In the Script: box, type the full path name of a script on the client. For example: /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/sap_offline_backup b. Click Add to add the script to the list. c. Repeat step a and step b until all scripts are added. 5. Click OK. From the Windows interface: 1. In the Policy dialog, click the Backup Selections tab. To access the Policy dialog, double-click the policy name in the Policies list in the NetBackup Administration Console. 2. Click New. 3. Specify the names of the scripts you want NetBackup to use. Use one of the following methods: Type the full path name of the script on the client. For example: /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/sap_offline_backup 4. Click OK. Click the Remote Folder button. The Browse window displays the hosts in the client list. Navigate to and select the script file. Click OK. Chapter 3, Configuration 39

52 Creating Scripts Creating Scripts If you configured a policy for automatic scheduling in Adding Backup Selections on page 38, you also need to specify backup scripts to be run automatically. You can either create your own scripts or you can modify one or more of the scripts included in the following locations: /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_maxdb The scripts in the sap_oracle and sap_maxdb directories are as follows: NetBackup for SAP Scripts Script Name Used By (Underlying Database) Comments sap_offline_backup Oracle without RMAN Issues a brbackup command and performs a full offline database backup. Use the export command to make $SAP_SERVER and $SAP_POLICY, which are created by bphdb in root, available to the NetBackup for SAP backint interface process. sap_online_backup Oracle without RMAN Issues the brbackup and brarchive commands and performs a full online database backup. sap_redo_log_backup Oracle without RMAN Issues the brarchive command and backs up the offline redo log files. sap_rman_backup Oracle with RMAN Issues the brbackup command with the RMAN option. sap_maxdb_backup MaxDB Issues a dbmcli command and uses the specified backup medium. If you decide to use these scripts, customize them for your environment Caution Always specify the correct script when configuring automatic backups or when starting operations through NetBackup. NetBackup for SAP does not generate an error if a restore script is used for a backup operation or a backup script is used for a restore operation. 40 NetBackup for SAP System Administrator s Guide for UNIX and Linux

53 Creating Scripts Modifying the Backup Scripts To modify the backup scripts 1. Copy the example script(s) from /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle or /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_maxdb to a different location on your client. The SAP scripts can reside anywhere on the client. Do not store your scripts in the sample directory because your modifications are lost if you upgrade or reinstall. Always relocate your scripts to a safe location. In a NetBackup server cluster, this location must be available after a failover. 2. Enable proper permissions on the script files so NetBackup can run the scripts. Set the access permissions of these scripts to 775. chmod 775 script_name 3. Open the script file with a text editor. For example, you can use the following command if you are modifying the sap_offline_backup script: vi sap_offline_backup 4. Modify the script according to the instructions in the file. In particular, remember to edit lines that starts with su. If you do not include su - user (where user is the SAP administrator account) in your script, the script does not run with the proper account and environment variables. This situation can lead to problems with database backups and restores. For example, the sap_offline_backup script contains the following lines: #!/bin/sh # #NOTE:IF your SAP user (in this script orasap) runs in C shell, environmental #variables can not be exported. In that case, you should modify this script to #work in your environment. For example: # SAP_SERVER=$SAP_SERVER; export SAP_SERVER; (Correct for Bourne and Korn shells) # can change into # setenv SAP_SERVER $SAP_SERVER; (Correct for C shell) # # #This environment variable are created by Netbackup (bphdb) # echo "SAP_SCHEDULED = $SAP_SCHEDULED" Chapter 3, Configuration 41

54 Creating Scripts echo "SAP_USER_INITIATED = $SAP_USER_INITIATED" echo "SAP_SERVER = $SAP_SERVER" echo "SAP_POLICY = $SAP_POLICY" RETURN_STATUS=0 SAP_ENV="" # # If SAP_SERVER exists then export it to make it available to backint # if [ -n "$SAP_SERVER" ] then SAP_ENV="$SAP_ENV SAP_SERVER=$SAP_SERVER; export SAP_SERVER;" #if Oracle DBA account( orasap user) uses C Shell, comment the above line and #uncomment next line # SAP_ENV="$SAP_ENV setenv SAP_SERVER $SAP_SERVER;" fi # # If SAP_POLICY exists then export it to make it available to backint # if [ -n "$SAP_POLICY" ] then SAP_ENV="$SAP_ENV SAP_POLICY=$SAP_POLICY;export SAP_POLICY;" #if Oracle DBA account( orasap user) uses C Shell, comment the above line and #uncomment next line # SAP_ENV="$SAP_ENV setenv SAP_POLICY $SAP_POLICY;" fi # # Full offline backup # CMD_LINE="$SAP_ENV brbackup -c -d util_file -t offline -m all" # # The username on the "su" command needs to be replaced with the correct # user name. # echo "Execute $CMD_LINE" su - orasap -c "$CMD_LINE" RETURN_STATUS=$? exit $RETURN_STATUS 5. Test the scripts you just created. For information on testing, see Testing Configuration Settings on page NetBackup for SAP System Administrator s Guide for UNIX and Linux

55 Creating Scripts Script Parameters The SAP scripts that enable the SAP utilities to perform backups and restores use parameters defined in the following sources: Environment variables Configuration files. For example, initsid.utl, where SID is the instance. For more information on these files, see Modifying the Configuration Files on page 44. NetBackup Configuration File (bp.conf) You can use the different parameter sources to create SAP scripts to perform different database backup and restore tasks. For example, you can define $SAP_POLICY in an SAP script to perform different types of backups. When NetBackup s automatic scheduler executes an SAP script, it creates the following environment variables locally: Environment Variable $SAP_POLICY $SAP_SCHEDULED $SAP_SERVER $SAP_USER_INITIATED Purpose Names the NetBackup for SAP policy. Set to 1 if this is an automatic backup (Scheduled SAP). Names the NetBackup server. Set to 1 if this is a user-initiated backup. That is, if the SAP backup is started from the master server. When an SAP script starts from the Java interface, it creates all of the preceding variables except for the $SAP_POLICY variable. Chapter 3, Configuration 43

56 Modifying the Configuration Files Modifying the Configuration Files The following sections show how to modify the NetBackup for SAP configuration files. The NetBackup for SAP software distribution includes several example configuration files. Files to Configure The files you need to modify depend upon whether your underlying database is an Oracle database or a MaxDB database, as follows: Database Configuration Files File Underlying Database Comments initsid.utl Oracle and MaxDB SAP parameter file. This file specifies policy, schedule, client, and other information to the backint interface. initsid.sap Oracle SAP profile file. This file contains information that the SAP tools use to interact with the backint interface. bsi.env MaxDB MaxDB configuration file. This file contains information that the SAP tools use to interact with the backint interface. Relationships Between Files The SAP tools and NetBackup for SAP pass information in these configuration files to the backint interface. When backint executes, the following occurs: In NetBackup for SAP on Oracle databases, you specify the actual initsid.utl file name as the argument to the util_par_file parameter in the initsid.sap file. In NetBackup for SAP on MaxDB databases, you specify the actual initsid.utl file name as the argument to the PARAMETERFILE parameter in the bsi.env file. The initsid.utl file name becomes the argument to the backint command s -p par_file parameter. 44 NetBackup for SAP System Administrator s Guide for UNIX and Linux

57 Modifying the Configuration Files Modifying the initsid.utl File The initsid.utl file is the SAP parameter file. Edit this file as part of configuring NetBackup for SAP. To modify the initsid.utl file 1. Check for an existing parameter file. If an initsid.utl file already exists in the $ORACLE_HOME/dbs directory, copy it to a backup file. 2. Create a new parameter file. Copy the parameter file included in the NetBackup for SAP software distribution to the $ORACLE_HOME/dbs directory. For example, if the Oracle instance is SAP, copy the NetBackup example.utl file to initsap.utl, as follows: cp /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initsap.utl \ $ORACLE_HOME/dbs/initSAP.utl 3. Modify initsid.utl file with a text editor to set the parameters to values that are appropriate to your site. The following parameters are required: client, switch_list, switch_log, switch_sem. You can set the following additional parameters depending on whether or not you use RMAN: If you use RMAN, set policy, schedule, and server. If you do not use RMAN, set drives, policy, schedule, and server. For example, assume that initsap.utl is your parameter file, and the policy you are configuring is called sap_policy_1. You can use the following procedure to set the policy parameter: a. Use a text editor to open the initsap.utl file. b. Find the following line: policy sap_backup c. Copy and paste this line under the original. policy sap_backup policy sap_backup Chapter 3, Configuration 45

58 Modifying the Configuration Files d. Comment out the original line. #policy sap_backup policy sap_backup e. Change sap_backup to sap_policy_1. #policy sap_backup policy sap_policy_1 f. Repeat the preceding steps for each parameter you want to change. When you are finished changing parameters, save and close the file. The following shows an example initsid.utl file with all the parameters required for NetBackup for SAP on Oracle databases: policy sap_policy_1 schedule Default-Application-Backup client puffin server puffin drives 2 switch_list /oracle/sap/sapbackup/.switch.lis switch_sem /oracle/sap/sapbackup/.switch.sem switch_log /oracle/sap/sapbackup/.switch.log Note The question mark (?) and ampersand (&) Oracle substitution characters and the $ORACLE_HOME environment variable are not allowed in the initsid.utl file. This is because they are not allowed in the par_file that the backint -p parfile option identifies. 46 NetBackup for SAP System Administrator s Guide for UNIX and Linux

59 Modifying the initsid.sap File (NetBackup for SAP on Oracle Databases Only) Modifying the Configuration Files The initsid.sap file is the SAP profile file. This file signals to the SAP tools that you are using the backint interface and conveys information about NetBackup for SAP to the SAP tools. Edit this file as part of configuring NetBackup for SAP when the underlying database is Oracle. To modify the initsid.sap file 1. Check for an existing profile file. If an initsid.sap file already exists in the $ORACLE_HOME/dbs directory, copy it to a backup file. 2. Create a new profile file. Copy the profile file included in the NetBackup for SAP software distribution to the $ORACLE_HOME/dbs directory. For example, if the Oracle instance is SAP, copy the NetBackup example.sap file to initsap.sap, as follows: cp /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initsap.sap \ $ORACLE_HOME/dbs/initSAP.sap 3. Modify the initsid.sap file with a text editor to set the backup_dev_type and util_par_file parameters to values that are appropriate to your site. For example, assume that initsap.sap is your profile file, and initsap.utl is your parameter file. You can use the following procedure to set parameters: a. Use a text editor to open the initsap.sap file. b. Find the following line: backup_dev_type = tape c. Copy and paste this line under the original. backup_dev_type = tape backup_dev_type = tape d. Comment out the original line. #backup_dev_type = tape backup_dev_type = tape e. Change tape to util_file. Chapter 3, Configuration 47

60 Modifying the Configuration Files #backup_dev_type = tape backup_dev_type = util_file f. Find the following line: util_par_file = file_path g. Copy and paste this line under the original. util_par_file = file_path util_par_file = file_path h. Comment out the original line. #util_par_file = file_path util_par_file = file_path i. Change file_path to the path to the initsid.utl parameter file. #util_par_file = file_path util_par_file =?/dbs/[email protected] This example file uses environment variable settings and Oracle substitution characters. When the SAP tools interpret the initsid.sap profile file, they replace the question mark (?) and at sign (@) characters with the values assigned to the $ORACLE_HOME and $ORACLE_SID environment variables, respectively. 4. (Conditional) Specify the rman_parms parameter and set the NB_ORA_SAP environment variable to the value SAP. Perform this step only if you are using NetBackup for SAP on an Oracle database with RMAN. For example: rman_parms = ENV=(NB_ORA_SAP=file) file Specify the full path to the initsid.utl file. Do not use substitution characters in the file specification. For example, this parameter might look like the following: rman_parms = ENV=(NB_ORA_SAP=$ORACLE_HOME/dbs/initCER.utl) Depending on your site practices, you might want to specify the following additional NetBackup environment variables and their values as arguments to the rman_parms parameter: NB_ORA_POLICY, NB_ORA_SCHEDULE, NB_ORA_CLIENT, and NB_ORA_SERV. You can also specify values for these environment variables in the initsid.utl file. If you specify differing values, the ones in initsid.sap override those in initsid.utl. 48 NetBackup for SAP System Administrator s Guide for UNIX and Linux

61 Modifying the Configuration Files For example, if you want to use one policy and schedule for the first part of a backup (data files) and a different policy and schedule for the second part of a backup (the control file backup), you can set the NB_ORA_POLICY and NB_ORA_SCHEDULE variables in initsid.sap to pertain to the first part of the backup. Then, you can set these variables to different values that pertain to the second part of the backup in initsid.utl because NetBackup for SAP checks only initsid.utl when backing up the control files; it does not check initsid.sap. You can include other RMAN parameters in this file. For more information on other parameters, see your SAP documentation. 5. Save and close the initsid.sap file. Chapter 3, Configuration 49

62 Modifying the Configuration Files Modifying the bsi.env File (NetBackup for SAP on MaxDB Databases) The bsi.env file specifies the following: The backint for MaxDB program s location, which is NetBackup for SAP on MaxDB. How to communicate with backint. The database manager uses this information when it performs backups and restores. bsi.env is the default name for this configuration file, but if you want to change this name, you can specify a different name in the BSI_ENV environment variable in the MaxDB user environment. To create a MaxDB configuration file 1. Use a text editor to create the MaxDB configuration file, bsi.env. The following command creates bsi.env in a UNIX environment: vi bsi.env Note You can give the MaxDB configuration file a name other than bsi.env. If you do this, edit the BSI_ENV environment variable and include the full path to this file. 2. Use the parameters to specify backup characteristics. You must include the following parameters in bsi.env: BACKINT, INPUT, OUTPUT, ERROROUTPUT, and PARAMETERFILE. All other parameters are optional. The following is an example of a file with the minimum configuration specified: BACKINT /usr/openv/netbackup/bin/backint INPUT /export/home/sapdb/logs/backint.in OUTPUT /export/home/sapdb/logs/backint.out ERROROUTPUT /export/home/sapdb/logs/backint.err PARAMETERFILE /export/home/sapdb/indep_data/wrk/initsap.utl 50 NetBackup for SAP System Administrator s Guide for UNIX and Linux

63 Modifying the Configuration Files The following list shows the parameters you can include in the bsi.env file: Parameter Description BACKINT absolute_path/file_name Specifies the absolute path and file name of the backint for MaxDB program. INPUT absolute_path/file_name OUTPUT absolute_path/file_name ERROROUTPUT absolute_path/file_name The INPUT parameter specifies the absolute path and file name of the standard input file. The OUTPUT parameter specifies the absolute path and file name of the standard output file. The ERROROUTPUT file specifies the absolute path and file name of the standard error output file. The database manager creates these files temporarily and uses them for standard input, output, and error output for backint for MaxDB. PARAMETERFILE absolute_path/file_name TIMEOUT_SUCCESS seconds TIMEOUT_FAILURE seconds Specifies the absolute path and file name of the configuration file for the backint for MaxDB program, initsap.utl. The number of seconds after which the backup tool exits and after the database kernel has copied all data successfully. Default is 300. This is the period of time after which the database manager terminates the backup tool if all data has been copied to the pipes. Note that the backup tool always exits after this defined period, whether all data copied from the database kernel has been backed up by the backup tool or not. This parameter is effective only if the database kernel has stopped the backup due to an error. In such a case, seconds specifies the number of seconds after which the backup tool exits. Default is 300. Allow enough time for the backup tool to save all data copied by the database kernel because the backup tool always exits when this timeout is reached, even if not all of the copied data has been saved yet. However, do not specify too much time, or you risk a situation in which a backup stopped by the database kernel blocks other backups, such as automatic nightly backups, from being started. ORIGINAL_RUNDIRECTORY absolute_path Chapter 3, Configuration 51

64 Modifying the Configuration Files Parameter Description Specifies the absolute path of the run directory of the source database. The default value is the run directory of the current database instance. This value is case sensitive. Specify this parameter only for a migration. The prerequisite for the migration from one computer to another is that the version of backint for MaxDB that you are using can make backups from the source computer available on the target computer. 52 NetBackup for SAP System Administrator s Guide for UNIX and Linux

65 Testing Configuration Settings Testing Configuration Settings After configuring the master server for NetBackup for SAP, test the configuration settings by performing a manual backup (or backups) using the automatic backup schedules you have created. To test the configuration settings 1. Log onto the master server as administrator (Windows) or root (UNIX). 2. Start the NetBackup Administration Console. 3. In the left pane, click Policies. From the Windows interface: The policy list appears in the right pane. From the Java interface: The right pane splits into an All Policies pane and a details pane. 4. Click the policy you want to test. 5. Choose Actions > Manual Backup. The Manual Backup dialog box appears. The Schedules pane contains the name of an automatic schedule (or schedules) configured for the policy that you are going to test. The Clients pane contains the name of the client(s) listed in the policy that you are going to test. 6. Follow the directions in the Manual Backup dialog box. 7. Click Activity Monitor on the NetBackup Administration Console. If the manual backup does not exit with a successful status, see Troubleshooting on page 77. For a description of status codes and other troubleshooting information, see the NetBackup Troubleshooting Guide. Testing Multiple Drives and Files To test multiple drives, you must have the following in your environment: More than one tablespace to back up Multiple tape drives or multiple disk storage units to write to at the same time Chapter 3, Configuration 53

66 Testing Multiple Drives and Files You can also use the multiplex value to simulate multiple tape and disk drives. To test multiple drives 1. Complete the configuration of NetBackup, NetBackup for SAP, and SAP Tools as described previously in this chapter. 2. Change the number of tape and disk drives specified by the drives parameter in $ORACLE_HOME/dbs/initSAP.utl to equal the number of storage units. For example, the multiplex value multiplied by the number of tape drives = drives. For more information, see the drives parameter in Parameters Used in initsid.utl on page 95. drives 2 When you perform a backup, you should see two or more backups running, depending upon how many drives you have identified in the $ORACLE_HOME/dbs/initSAP.utl parameter file. The number of drives in the utility file should match the number of drives multiplied by the MPX value. The NetBackup for SAP backint interface waits for all backups to complete before reporting success or failure to brbackup. 54 NetBackup for SAP System Administrator s Guide for UNIX and Linux

67 Using NetBackup for SAP 4 When all installation and configuration is complete, you can start SAP backups and restores through NetBackup. This chapter contains the following sections: Performing a backup Performing an archive Performing a restore Caution Always specify the correct SAP script when configuring automatic backups or when starting operations through NetBackup (see Creating Scripts on page 40). NetBackup for SAP does not generate an error if a restore SAP script file is used for a backup operation or a backup SAP script is used for a restore operation. 55

68 Performing a Backup Performing a Backup This section shows how to perform backups using the following methods: Method 1: Using NetBackup for SAP to Perform a Backup Method 2: Using SAP to Perform a Backup (NetBackup for SAP on Oracle Databases Only) Method 1: Using NetBackup for SAP to Perform a Backup Automatic Backup The most convenient way to back up your database is to set up schedules for automatic backups. When the NetBackup scheduler invokes a schedule for an automatic backup, the SAP scripts run as follows: In the same order as they appear in the file list On all clients that have them (that is, matching path names) The SAP scripts start the database backup. The instructions in Configuration on page 27 explain how to create and configure a policy that uses the SAP scripts to back up your database automatically according to the schedules you specify. To add a new schedule or change an existing schedule for automatic backups, follow the guidelines in Adding Schedules on page 32. Manual Backup The administrator can use the NetBackup server software to manually execute an automatic backup schedule for the SAP policy. For information on initiating a manual backup of an Oracle policy, see Testing Configuration Settings on page 53. Method 2: Using SAP to Perform a Backup (NetBackup for SAP on Oracle Databases Only) Note The information in this section applies to NetBackup for SAP on Oracle databases only. If you are using NetBackup for SAP on a MaxDB database, see NetBackup for SAP on MaxDB Databases on page 71. There are two ways to start a backup: Through the SAPDBA utility s menus 56 NetBackup for SAP System Administrator s Guide for UNIX and Linux

69 Performing a Backup Through the brbackup command line When you use the SAPDBA utility or the brbackup command to start a backup, the following events occur: 1. brbackup status messages appear on the console. These messages report when the database server is started or stopped. They also report when the backup mode of the tables is changed. 2. The brbackup command starts the NetBackup for SAP backint interface, and it submits files to be backed up. 3. The NetBackup for SAP backint interface processes input files and calls the XBSA interface. During the file-online mode, each database file is backed up, one at a time. The NetBackup for SAP backint interface coordinates with brbackup using a semaphore file. 4. After all files are backed up, the full file list is displayed in the format required by the NetBackup for SAP backint interface specification as to success or failure. This format includes a Backup ID (BID) to be used for later restores. The SAP tools also maintain a log of the backup session. The standard NetBackup logs keep track of the images created. The NetBackup for SAP backint interface only needs to keep track of the BID date and time. This allows cross-referencing by brrestore. Chapter 4, Using NetBackup for SAP 57

70 Performing a Backup SAPDBA Offline Backup To perform an offline backup using SAPDBA 1. Verify that you have completely configured NetBackup, NetBackup for SAP, and the SAP Tools as described in Configuration on page Verify that you are user sapadm. 3. Run the stopsap R3 command to stop SAP. 4. Start sapdba. The following appears: SAPDBA V SAP Database Administration ORACLE version: ORACLE_SID : CER ORACLE_HOME : /home/orasap/ora920 DATABASE : open SAPR3 : 5, not connected a - Startup/shutdown instance b - Instance information c - Tablespace administration d - Reorganization e - Export/import f - Archive mode h - Backup database i - Backup offline redo logs j - Restore/recovery k - Additional functions l - Show/cleanup m - User and security q - Quit Please select ==> h 58 NetBackup for SAP System Administrator s Guide for UNIX and Linux

71 Performing a Backup 5. Type h to select the Backup database menu item. The following appears: Backup Database a - Backup function b - Parameter file c - Backup device type d - Objects for backup e - Backup type g - Query only h - Special options... i - Standard backup j - Backup from disk backup k - Restart backup l - Make part. backups compl. Current value Normal backup initcer.sap external backup tool (backint) all offline (force) no yes S - Start BRBACKUP (V6.20) q - Return Please select ==> d Chapter 4, Using NetBackup for SAP 59

72 Performing a Backup 6. Type d to select Objects for backup. The following appears: Backup Mode/Backup Objects Current selection: all a - all - whole database backup b - all_data - whole database backup without index tablespaces c - full - full backup (level 0) d - incr - incremental backup (level 1) e - sap_dir - SAP directories backup f - ora_dir - ORACLE directories backup g - - a tablespace name h - - an ORACLE file id <number> or a range of file ids <number>-<number> i - - an absolute or directory name j - - a combination: <item> or <item>,<item>,... q - Return Please select ==>g Enter tablespace name Enter objects for backup (<return> only for no change) ==> PSAPUSER1D 60 NetBackup for SAP System Administrator s Guide for UNIX and Linux

73 Performing a Backup 7. Type g and type the name of the object to back up. For example: PSAPUSER1D. The following appears: Backup Mode/Backup Objects Current selection: PSAPUSER1D a - all - whole database backup b - all_data - whole database backup without index tablespaces c - full - full backup (level 0) d - incr - incremental backup (level 1) e - sap_dir - SAP directories backup f - ora_dir - ORACLE directories backup g - - a tablespace name h - - an ORACLE file id <number> or a range of file ids <number>-<number> i - - an absolute file or directory name j - - a combination: <item> or <item>,<item>,... q - Return Please select ==>q Chapter 4, Using NetBackup for SAP 61

74 Performing a Backup 8. Type q to go back to the previous menu. The information returned indicates the following: The backup device type is external backup tool (backint). The backup type is offline_force. Tablespace is PSAPUSER1D. For example: Backup database a - Backup function b - Parameter file c - Backup device type d - Objects for backup e - Backup type g - Query only h - Special options... i - Standard backup j - Backup from disk backup l - Restart backup m - Make part. backups compl. Current value Normal backup initcer.sap external backup tool (backint) PSAPUSER1D offline (force) no yes S - Start BRBACKUP (V6.20) q - Return Please select ==>S 9. Type S to start the backup. brbackup Online Backup You can use brbackup instead of sapdba to perform database backups. This section shows an online backup. You can change the backup_mode by changing the initsap.sap parameter file or by specifying -t online on the brbackup command. Here is what these changes look like in initsap.sap: backup_type = online_file 62 NetBackup for SAP System Administrator s Guide for UNIX and Linux

75 Performing a Backup This backup mode allows sapdba/brbackup to use a semaphore file with the NetBackup for SAP backint interface. This provides a better online backup for very large files because only the necessary tablespaces are placed in backup mode. When NetBackup is ready to process another file, it notifies brbackup. You can change the backup_mode to online to test this mode. To use brbackup 1. Verify that you have completely configured NetBackup, NetBackup for SAP, and the SAP tools as described in Configuration on page Verify that you are user sapadm. 3. Enter the brbackup command. To initiate an online backup, enter the following command: brbackup -d util_file_online -t online -m all To initate a full backup when you are using RMAN, enter the following command: brbackup -d rman_util -t offline -m full -c To initate an incremental backup when you are using RMAN, enter the following command: brbackup -d rman_util -t online -m incr -c Chapter 4, Using NetBackup for SAP 63

76 Performing an Archive Performing an Archive An archive is performed in a fashion similar to a backup. The brarchive command can create multiple backup copies. NetBackup for SAP is used for each archive run. This section explains how to create two backup copies of an archive log. You can store each copy on separate media and retrieve them. There are two methods to accomplish this task. Depending on how you use NetBackup for SAP, choose the method of creating archive log backup copies that is easiest for you. Method 1: Using the NetBackup Multiple Copies Feature If Multiple Copies is enabled in a backup schedule, NetBackup automatically makes up to four copies of a backup. The brarchive command uses this information and creates the specified number of backup copies of the archive log file. For more information on the Multiple Copies feature, see the NetBackup System Administration Guide, Volume 1. Examples Example 1. When Multiple Copies is enabled, the following command creates the number of backup copies specified and writes each copy to a different tape: brarchive -d util_file -s Example 2. To restore the first available copy of an archive log file, issue the following command: brrestore -d util_file -a log_number log_number The number of the archive log you want to restore. Method 2: Using Two brarchive Commands in Sequence You can also create a backup copy of the archive log by issuing two brarchive commands in sequence. You can write each backup copy to different media. For example, you can write each backup copy to two different tapes, to disk and tape, or to any combination of media. Examples This example assumes that there is only one archive log to be backed up, archive log NetBackup for SAP System Administrator s Guide for UNIX and Linux

77 Performing an Archive To create the backup copies For the first copy, call brarchive with the -s option. For the second copy, call brarchive with the -sc option. Both commands automatically determine that the archive log file needs to be backed up and perform the backup. 1. To create the first backup copy, issue the following command: brarchive -d util_file -s 2. To create the second backup copy, issue the following command: brarchive -d util_file -sc To restore the archived log files 1. To restore the first backup copy, issue the following command: brrestore -a To restore the second backup copy, issue the following command: brrestore -a2 77 Chapter 4, Using NetBackup for SAP 65

78 Performing a Restore Performing a Restore The following sections explain how to perform a restore if you are using NetBackup for SAP on an Oracle database. If you are using NetBackup for SAP on a MaxDB database, see Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores on page 72. Using the SAPDBA Utility (NetBackup for SAP on Oracle Databases Only) To restore a partial or full Oracle database, the sapdba system should be used to maintain the list of valid restores for specific tablespace or complete database restores. Before restoring either individual tablespaces or full databases, the user is prompted prior to deleting an existing copy of the target file. sapdba then invokes the brrestore command. brrestore submits the BID and file name list to the NetBackup for SAP backint interface. The backint interface cross-references the exact date and time to when the backup was made and uses NetBackup to recover the file. The backint interface monitors the progress of the restore and reports status back to brrestore. Upon completion, the backint interface saves a copy of the NetBackup restore logs for auditing purposes. sapdba then provides required database recovery, such as media recovery, and restarts the database server. To use brrestore to restore database files In Oracle-based environments without RMAN, use the command with the following options: brrestore -d util_file -b last -m full -c force In Oracle-based environments with RMAN, use the command with the following options: brrestore -d rman_util -b last -m full -c force Redirecting a Restore to a Different Client (NetBackup for SAP on Oracle Databases Only) You have the option to restore an SAP database to a client other than the one that originally supplied the backup. This process of restoring data to a different client is called a redirected restore. 66 NetBackup for SAP System Administrator s Guide for UNIX and Linux

79 Performing a Restore In order to perform a redirected restore, the following conditions must be present: The source and destination clients must have identical computer system architectures, OS versions, and bit levels. The source and destination clients must have identical Oracle RDBMS levels. Note In some situations, it is possible to restore from lower to higher release levels of Oracle. For more information, see your Oracle documentation. The redirected restore is a 4-part process: 1. Configure the NetBackup server 2. Copy files from the source client to the destination client 3. Configure the NetBackup for SAP destination client 4. Perform the redirected restore The following procedure explains each part of the process. For more information on redirected restores, see the NetBackup System Administrator s Guide. To perform a NetBackup for SAP redirected restore 1. Verify that you are logged in as the NetBackup administrator. 2. Configure the NetBackup server to allow redirected restores. This step differs depending on whether you want to allow restores from any client or from only selected clients. a. To remove restrictions for all clients, create the following file on the Netbackup master server: /usr/openv/netbackup/db/altnames/no.restrictions OR b. To restrict clients to restore only from certain other clients, create the following file: /usr/openv/netbackup/db/altnames/client_name client_name Specify the name of the client allowed to perform the redirected restore. Chapter 4, Using NetBackup for SAP 67

80 Performing a Restore c. If you performed step b, add the name of the NetBackup for SAP source client to the client_name file. 3. On the destination client, back up the existing control files to preserve the original configuration. These files are usually in the $ORACLE_HOME/dbs directory. 4. Copy configuration and control files from the NetBackup for SAP source client to the NetBackup for SAP destination client. For example, you can use ftp(1) to perform the copies. a. Copy the following files from the source client, usually $ORACLE_HOME/dbs, to the same location on the destination client: initsid.sap initsid.utl initsid.ora initsid.dba b. Copy the $SAPDATA_HOME/sapbackup directory from the source client to the same location on the destination client. 5. Configure the NetBackup for SAP destination client. a. Change the client parameter in the initsid.utl file on the destination client to the name of the source client. OR Set the SAP_CLIENT environment variable on the destination client to the name of the source client. For example: SAP_CLIENT=source_client export SAP_CLIENT Note The SAP_CLIENT variable has higher priority than the value in the initsid.utl file. b. (Conditional) Set the restore_filter parameter in the initsid.utl file on the destination client. Perform this step only if you are restoring images created with a NetBackup for SAP version before NetBackup for SAP System Administrator s Guide for UNIX and Linux

81 Performing a Restore For example, if the source client path is set to /home_db/oracle/sap and the input file contains the path /oracle/sap, then the value of restore_filter is a script such as the following: #!\/bin\/sh # this shell is used to change some logically linked files # during a restore sed -e ' s\/oracle\/sap\/home_db\/oracle\/sap\/' $1 > $2 c. Create a symbolic link on the destination client that resembles the actual path of the source client and point it to the directory that points to the SAP files. Note Do not use the -m dest_dir option with brrestore to achieve the same effect. This restores the files to the directory you specify, rather than to the original directories. 6. Perform the redirected restore. a. Log onto the NetBackup for SAP destination client. b. Enter the following command: brrestore -d util_file -b last -m full Redirected Restore Sample Environment This sample environment shows how a redirected restore uses the restore_filter script. This example assumes the following: Source client Actual path is /home_db/oracle/sap Includes soft link /oracle/sap (SAP is the sytem ID), which points to /home_db/oracle/sap. Destination client Actual path is /home2/sap Also has soft link /oracle/sap, which points to /home2/sap. Make soft link /home_db/oracle/sap, which points to /home2/sap In the restore_filter script, substitute the path provided in the input file list of the destination client with the actual path of the source client. The resulting script sample might look like the following: Chapter 4, Using NetBackup for SAP 69

82 Performing a Restore #!/bin/sh # this shell is used to change some logically linked files # during a restore sed -e ' s\/oracle\/sap\/home_db\/oracle\/sap\/' $1 > $2 When the backup starts, the file list contains the file path with the following soft link: /oracle/sap/sapdata1/btabd_1/btabd.data1 However, the file is really backed up with the following actual path: /home_db/oracle/sap/sapdata1/btab_d/btabd.data When the request for a restore is issued, the input file list contains file paths with soft links. These are converted to the actual path of the destination client. Because this path is different from the source client path, the restore would fail in the inquire phase. To prevent this, use the restore_filter script. 70 NetBackup for SAP System Administrator s Guide for UNIX and Linux

83 NetBackup for SAP on MaxDB Databases 5 This chapter describes how to use NetBackup for SAP and describes the differences between using an Oracle versus a MaxDB database with NetBackup for SAP. For more information about MaxDB databsases, see your MaxDB documentation. Note NetBackup documentation uses the terms media or medium to refer to removable media tape and optical disk cartridges in a storage unit. NetBackup writes a backup file to a storage medium. MaxDB database documentation, however, uses the term backup medium to include the named pipes and other entities needed for performing backups. This manual uses the term backup medium when referring to backing up MaxDB database files. Configuration To configure NetBackup for SAP in a MaxDB database environment, follow the directions in Configuration on page 27. No additional steps are required, but because Modifying the Configuration Files on page 44 contains information for both Oracle and MaxDB database environments, follow only the instructions in that section that pertain to MaxDB databases. MaxDB databases require you to create a backup medium. For information on how to do this, see Creating a Backup Medium on page 71. Creating a Backup Medium As part of the configuration process, also create at least one backup medium. Do this before you perform any backups. MaxDB databases require at least one backup medium before a backup or restore can be performed. This section shows how to create a backup medium by entering commands. 71

84 Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores To create a backup medium Use the DBM CLI interface and enter the following commands: OS_prompt% dbmcli -d database_name -u usr,passwd dbmcli> medium_put medium_name medium_path PIPE backup_type database_name Name of the SAP database. usr passwd medium_name medium_path backup_type MaxDB user name. MaxDB password. Name of the backup medium. The first 4 characters must be BACK. The medium_name must be in format BACKname. For example, BACKData. Full path to the named pipe. For example, /export/home/medium1. Specify one of the following: DATA for a full data backup PAGES for an incremental data backup LOG for a log backup Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores The NetBackup for SAP on a MaxDB database does not include the SAP backup and restore tools. You can initiate backup and restore operations through the MaxDB administrative interface when you invoke one of the following interfaces: DBM GUI DBM CLI Web DBM For example, when you issue a backup command using the MaxDB administrative interface through the DBM CLI, the following occurs: 72 NetBackup for SAP System Administrator s Guide for UNIX and Linux

85 Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores 1. The DBM CLI communicates with the MaxDB server, which creates one or more named pipes. 2. The MaxDB server streams the data from the MaxDB instance to the named pipes. 3. The MaxDB server calls NetBackup for SAP with a list of named pipes. 4. NetBackup for SAP reads named pipes and sends data to NetBackup. In the case of a restore, the process is the same except that data goes the other way. Performing a Backup To perform a backup 1. Make sure that you have modified the proper configuration files and created a backup medium. 2. Start a utility session. Type the following command: dbmcli> util_connect 3. Initiate the backup. Type the following command: dbmcli> backup_start medium_name backup_type medium_name backup_type Name of the backup medium. Specify either DATA, PAGES, or LOG. Performing a Query Prior to performing a restore, use the following procedure to query backup information and to obtain a listing of backup information. This information is needed for a restore. To perform a query Enter commands to obtain the backup identifier. Type the following commands: Chapter 5, NetBackup for SAP on MaxDB Databases 73

86 Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores dbmcli> backup_ext_ids_get medium_name database_name server dbmcli> backup_ext_ids_list medium_name Name of the backup medium. database_name Name of the SAP database. server Name of the server that hosts the MaxDB database. Performing a Restore To perform a restore 1. Use the procedure in To perform a query on page 73 to obtain the external backup identification information. 2. Initiate the restore. Type the following command: dbmcli> recover_start medium_nam backup_typ ExternalBackupId "BID" medium_nam backup_typ BID Name of the backup medium. Specify either DATA, PAGES, or LOG. The backup identifier. This information is returned when you perform a query. Performing Backups and Restores Using Parallel Medium Groups Note Parallel backups are optional only for Data Backups. Parallel backups and restores are used to improve backup and restore performance. You can combine individual backup mediums to form parallel mediums. Parallel mediums allow you to implement multiplexing. When parallel mediums are used for backup, the MaxDB database passes two or more named pipes to NetBackup for SAP. 74 NetBackup for SAP System Administrator s Guide for UNIX and Linux

87 Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores NetBackup for SAP starts as many backup streams as there are named pipes. It processes each named pipe independently from the rest of the named pipes in the backup job. Even if a backup is done in parallel, you can perform a restore of that data in either parallel or sequential mode. In other words, parallel backups do not require parallel restores. When the MaxDB database requests a parallel restore by listing multiple named pipes in an input file, NetBackup for SAP processes each pipe independently from the rest of the named pipes. Note that the MaxDB database requires that the number of media in a group of parallel media equal the number of media used during backup. Chapter 5, NetBackup for SAP on MaxDB Databases 75

88 Using NetBackup for SAP on a MaxDB Database to Perform Backups and Restores 76 NetBackup for SAP System Administrator s Guide for UNIX and Linux

89 Troubleshooting 6 This chapter explains the processes and resources that can help you troubleshoot NetBackup for SAP. These resources include the logs and reports that NetBackup, NetBackup for SAP, and the SAP tools provide. These reports are useful for finding errors associated with those applications. This chapter includes the following sections: Setting the Debug Level NetBackup Reports sapdba Logs and Messages Preventing Timeout Failures on Large Database Restores 77

90 Setting the Debug Level Setting the Debug Level You can control the amount of information written to the debugging logs in the /usr/openv/netbackup/logs/ directories by changing the debugging level. The higher the value, the more information is logged. Typically, the default value of 0 is sufficient. However, Technical Support might ask you to set the value higher when a problem is being analyzed. You can set the debugging levels to 0, 1, 2, 3, 4, or 5. A level of 5 provides the most detail. To enable detailed logging Enable detailed logging by entering the following line in the bp.conf file: VERBOSE = 5 NetBackup Reports The NetBackup server and client software allow you to enable detailed debugging logs. The information in these log files can help you troubleshoot problems that occur outside of either NetBackup for SAP or the SAP Tools. Note the following with regard to these logs: These logs do not reveal errors that occur during the execution of the SAP Tools unless those errors also affect NetBackup for SAP. SAP might (or might not) write to the NetBackup for SAP logs for errors in the application. Your best sources for SAP error information are the logs provided by SAP. Generally, each debug log corresponds to a NetBackup process and executable. For information about the debugging log files, see the NetBackup Troubleshooting Guide and the /usr/openv/netbackup/logs/readme.debug file. Enabling Logging To enable the NetBackup for SAP logs 1. Create the following directories on the client: /usr/openv/netbackup/logs/bpbackup /usr/openv/netbackup/logs/bpbkar /usr/openv/netbackup/logs/bphdb /usr/openv/netbackup/logs/bprestore /usr/openv/netbackup/logs/tar /usr/openv/netbackup/logs/backint 78 NetBackup for SAP System Administrator s Guide for UNIX and Linux

91 NetBackup Reports For example: cd /usr/openv/netbackup/logs mkdir bphdb 2. (Conditional) If you are running NetBackup for SAP on Oracle with RMAN, create the following additional directory: /usr/openv/netbackup/logs/dbclient 3. Set the access permissions to 777 on these log directories. For example: chmod 777 bphdb 4. Enable logging for the nbpem, nbjm, and nbrb scheduling processes, which use unified logging. NetBackup writes unified logs to /usr/openv/logs on UNIX and to install_path\netbackup\logs on Windows. You do not need to create log directories for processes that use unified logging. For information on using logs and reports, see the NetBackup Troubleshooting Guide. Accessing the Log Files The following sections describe the logs created when you create the log directories. Use a text editor to view the contents of the logs. bphdb Directory on the Client The /usr/openv/netbackup/logs/bphdb directory contains the following types of logs: sap_stdout.mmddyy Unless redirected elsewhere, NetBackup writes SAP script output to this file. sap_stderr.mmddyy Unless redirected elsewhere, NetBackup writes SAP script errors to this file. mmddyy bphdb is the NetBackup Database Backup binary. This log contains debugging information for the bphdb process. NetBackup for SAP uses this client process for SAP script execution. It is invoked when an automatic backup schedule is run. Chapter 6, Troubleshooting 79

92 sapdba Logs and Messages backint Directory on the Client The /usr/openv/netbackup/logs/backint directory contains the following execution log: mmddyy This log contains debugging information and execution status for the SAP NetBackup client processes linked to the library program provided with NetBackup for SAP. NetBackup Server Reports NetBackup provides other reports that are useful in isolating problems. One such report is All Logs Entries on the server. For information on server reports, see the NetBackup System Administrator s Guide, Volume I. sapdba Logs and Messages The SAP tools log provides information on SAP operations. You can check the log files to determine the ultimate success or failure of database backups and restores. You can view the backup and restore logs in the following ways: Through the following sapdba menu options: Show/Cleanup and Show log files/profiles. In the directories for brbackup/brrestore log information and brarchive log information. Backup and Restore Log Files The following directory contains log files for different types of backups and restores: $SAPDATA_HOME/sapbackup The files in this directory are named according to the following pattern: The summary log file is named backsid.log, where SID is the unique name for the Oracle database instance. The detail log files are named encoded_timestamp.xyz. encoded_timestamp A timestamp used in each detail log name that guarantees a unique file name. 80 NetBackup for SAP System Administrator s Guide for UNIX and Linux

93 sapdba Logs and Messages xyz for backup logs: x y z a represents all. p represents partial. n represents online. f represents offline. f represents utility_file_backup xyz for restore logs: xyz xyz xyz rsb represents restore backup files. rsa represents restore archive files. rsf represents restore individual files. Archive Log Files The following directory contains log files for different types of archive activities: $SAPDATA_HOME/saparch The files in this directory are named according to a pattern. The encoded_timestamp is a timestamp used in each detail log name that guarantees a unique file name. The file suffixes differentiate the different types of archive logs, as follows: File Name encoded_timestamp.sve encoded_timestamp.svd encoded_timestamp.cpy encoded_timestamp.cpd encoded_timestamp.dcp encoded_timestamp.dsv Meaning Original saved. Original saved and deleted. Original copied/saved a second time. Original copied/saved a second time and deleted. Deleted that were saved twice. Deleted that were saved. Chapter 6, Troubleshooting 81

94 Minimizing Timeout Failures on Large Database Restores Minimizing Timeout Failures on Large Database Restores Large database restores sometimes fail when multiple restore sessions compete for resources. In this situation, a restore session can be delayed while waiting for media or device access. If the delay is too long, the restore session times out. Use the following procedures to minimize session timeouts and to allow the restores to complete successfully. To minimize database session timeouts 1. In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Clients 2. Set the Client read timeout property to a large value. The default for the Client read timeout setting is 300 seconds (5 minutes). For database agent clients, increase the value significantly from the value recommended in the NetBackup System Administrator s Guide, Volume 1. For example, change this setting to minutes to minimize timeout errors. 3. Click OK for each client. To minimize loading and unloading of tapes You can minimize excessive unloading and reloading of tapes between multistreamed backups by making changes on the NetBackup media server. In the /usr/openv/netbackup/bp.conf file on the NetBackup media server, add the following options: MEDIA_UNMOUNT_DELAY. MEDIA_REQUEST_DELAY. Use this variable only with nonrobotic drives, such as tape stackers. 82 NetBackup for SAP System Administrator s Guide for UNIX and Linux

95 backint Command Line A The NetBackup for SAP backint interface communicates instructions from the SAP tools to NetBackup. The backint interface implements the SAP system s BC-BRI BACKINT Interface specification. Note VERITAS recommends that you use the backint command only with guidance from a technical support staff member. The backint interface performs the following functions: The backup function. The backup function of the backint interface supports and defines the SAP brbackup and brarchive tools to NetBackup. brbackup and brarchive communicate with the backint interface through an in_file and an out_file parameter. The in_file parameter includes a list of files to be backed up or archived. The out_file parameter reports the status for each file and assigns a Backup ID (BID) to each file. In the event of a partial backup, this function can identify successfully backed up files to the user. The restore function. The restore function of the backint interface supports and defines the brrestore tool to NetBackup. It communicates with the backint interface through the in_file parameter and out_file parameter. The in_file parameter includes a list of files to be restored through NetBackup. It also includes the Backup ID (BID) assigned during the backup function. The out_file parameter contains the status of the restore for each file. When the NetBackup restore operation is complete, the restore function lists successfully restored files. It also lists BIDs used during the operation. The BID is assigned by NetBackup during the backup function. It can identify one or more backup runs, a single file backup, or a group of files. During a backup function, the BID is submitted to the out_file parameter. During the restore and inquiry functions, the BID can only be set in the in_file parameter. If the BID is not set, the restore function uses the BID of the last backup. As an option, this function can also include a list of directories into which files will be restored. 83

96 The inquiry function. The inquiry function supports and defines the sapdba tool to NetBackup. sapdba uses the in_file parameter and the out_file parameter to collect backup information. The in_file parameter contains optional BIDs and file names. If only a #NULL is received on the in_file parameter, a list of BIDs is generated to the out_file parameter. If a BID is received, a list of files belonging to the BID is generated. If a filename is entered along with the #NULL, a list of BIDs containing that file is listed. The backint command line uses the following syntax: backint -u user_id -f function [-t type] -p par_file [-i in_file] [-o out_file] The following list shows the backint command options. As noted in this list, some options are required and others are optional. Option Arguments and Purpose -u user_id Required. UID for backup utility user. No default. -f function Required. It defines a key value that performs different functions between SAP and NetBackup. Specify one of the following arguments: backup - This argument supports and defines brbackup and brarchive to NetBackup. If backup is specified, NetBackup backs up SAP. restore - This argument supports and defines brrestore to NetBackup. If restore is specified, NetBackup restores SAP. inquiry - This argument supports and defines sapdba to NetBackup. sapdba uses this argument when a recovery is performed to get backup information for NetBackup. -t type Optional. It defines the backup type, the backup of individual files, and character special devices. If no type is specified, the default value of file is used. Specify one of the following arguments: file - Defines when to perform a backup, restore, and inquiry function with datafiles and special character devices. Backups from directories are not supported. Default. file_online - Allows brbackup to set tablespace into #BEGIN/#END backup mode when a related file backup takes place. It is used for online backups only. The architecture is based on three control files defined in the -p par_file parameter. 84 NetBackup for SAP System Administrator s Guide for UNIX and Linux

97 Option Arguments and Purpose -p par_file Required. It is a text file that contains comments, parameters (required and optional), and parameter values. These parameters determine the backup and restore procedure between NetBackup and the SAP tools. The following list explains the components of par_file: A pound character (#) in column one denotes a comment. Any other character in column one is considered valid. All required parameters must be specified with a valid value before the NetBackup for SAP backint interface can execute correctly. You can comment out an optional parameter by placing a # in column one. If optional parameters are specified, they must have valid values for the NetBackup for SAP backint interface to execute correctly. If an invalid parameter name is found, the NetBackup for SAP backint interface reports a warning message and continues. The SAP tools parameter file specifies the location of this par_file. For an example file, see the following: /usr/openv/netbackup/ext/db_ext/sap/scripts/initsap.utl For information on on input file contents, see Parameters Used in initsid.utl on page 95. -i in_file Optional. Specifies a text file, the contents of which can vary, depending on the NetBackup for SAP backint interface function initiated. If this option is not specified, the content of this file is data from standard input. For information on input file contents, refer to backint -i in_file Contents on page 87. -o out_file Optional. Specifies a text file that contains process messages for a function. If this option is not specified, the output is written to standard output. For information on output file contents, refer to backint -o out_file Contents on page 89. Appendix A, backint Command Line 85

98 86 NetBackup for SAP System Administrator s Guide for UNIX and Linux

99 backint -i in_file Contents B This appendix explains how to create a backint input file. You specify the name of this input file as the argument to the backint command s -i in_file option. The input file consists of one or more directive lines that specify how to perform a backup, restore, or inquiry. The input file format differs depending on the the function you want backint to initiate and on the underlying database. The following table shows the directives you can include in in_file and indicates the databases that use them: Directive Underlying Database Directives for an input file that requests a backup: file pipe #PIPE special_file size Oracle MaxDB Oracle Directives for an input file that requests a restore: backup_id file [dest_dir] #NULL file [dest_dir] backup_id pipe [dest_name] #NULL pipe [dest_name] Oracle Oracle MaxDB MaxDB Directives for an input file that performs an inquiry: #NULL backup_id Oracle and MaxDB Oracle and MaxDB 87

100 Directive #NULL file #NULL pipe backup_id file backup_id pipe Underlying Database Oracle MaxDB Oracle MaxDB Specify the following for the variables in the in_file: Variable file pipe special_file size backup_id dest_dir dest_name Specification The full path name of the file that you are backing up, restoring, or inquiring about. A named pipe. Specify the keyword #PIPE after the pipe name. The name of a special file, such as a raw device file. The file size as specified to the Oracle database. The BID, or backup identifier, as generated by NetBackup. The name of a directory or folder to which the restore is written. The name of a pipe to which the restore is written. If you use the #NULL keyword, backint uses the most recent version of the file or pipe. 88 NetBackup for SAP System Administrator s Guide for UNIX and Linux

101 backint -o out_file Contents C When the backint command finishes, it writes an output file to the file specified by the -o out_file option on its command line. The contents of the output text file change depending on the function backint performed. This appendix explains the backint output returned from a backup, restore, or inquiry request. Information Returned for a Backup If a backup completes successfully, the output file includes the following: The BID assigned to the backup by NetBackup. The files, pipes, directories, or folders backed up and their sizes. If a backup function fails, the output file lists the files or pipes that it could not back up. Information Returned for a Restore If a restore completes successfully, the output file entry includes the following: The BID. The files or pipes restored. If a restore function fails, the output file lists the files and pipes not found. It also lists the files and pipes that were not successfully restored. Information Returned for an Inquiry If an inquiry completes successfully, the output file entry includes the following: The BID. The files or pipes backed up. 89

102 Information Returned for an Inquiry 90 NetBackup for SAP System Administrator s Guide for UNIX and Linux

103 Environment Variables D The NetBackup for SAP backint interface recognizes the following environment variables: Environment Variable $SAP_SERVER $SAP_CLIENT $SAP_POLICY $SAP_SCHED $SAP_DRIVES Purpose Sets the name of the NetBackup server. It can be used to override the current server and perform a backup to an alternative server. This environment variable is the same as the server parameter in the initsid.utl file and the SERVER option in the NetBackup bp.conf file. Sets the name of the NetBackup client. It can be used to override the current client and perform an alternate restore to a different client. This variable is the same as the client parameter in the initsid.utl file and the CLIENT_NAME option in the NetBackup bp.conf file. Sets the name of the NetBackup policy. You can use this policy to define different types of database backups. You can use one policy type to perform offline database backups and another policy type to perform archive log backups. This environment variable is the same as the policy parameter in the initsid.utl file and the BPBACKUP_POLICY option in the NetBackup bp.conf file. Sets the name of the SAP backup policy schedule. This schedule provides an easy way to switch to a different schedule for each SAP database backup. This environment variable is the same as the schedule parameter in the initsid.utl file and the BPBACKUP_SCHED option in the NetBackup bp.conf file. Sets the number of simultaneous bpbackup/bprestore operations the NetBackup for SAP backint interface can execute. This environment variable is the same as the drives parameter in the initsid.utl file. 91

104 92 NetBackup for SAP System Administrator s Guide for UNIX and Linux

105 bp.conf File E You can specify parameters in several places. In the case of conflicts, the order of precedence is as follows: Setting Environment variables initsid.util file /usr/openv/netbackup/bp.conf file Precedence Highest precedence. Overrides values in initsid.utl and in the bp.conf file. Medium precedence. Values in environment variables override values specified in this file, but values in this file override those in the bp.conf file. Lowest precedence. Values in environment variables and in initsid.utl override values specified in the bp.conf file. The following list shows the variable names and definitions you can use in the bp.conf file: Variable $SERVER $CLIENT_NAME $BPBACKUP_POLICY Meaning Specifies the NetBackup server. This option is the same as the $SAP_SERVER environment variable and the server parameter in the initsid.util file. Specifies the NetBackup client. This option is the same as the $SAP_CLIENT environment variable and the client parameter in the initsid.util file. Specifies the NetBackup policy. This option is the same as the $SAP_POLICY environment variable and the policy parameter in the initsid.util file. 93

106 Variable $BPBACKUP_SCHED Meaning Specifies the NetBackup schedule. This option is the same as the $SAP_SCHED environment variable and the schedule parameter in the initsid.util file. For more information on bp.conf, see the NetBackup System Adminstrator s Guide, Volume II. 94 NetBackup for SAP System Administrator s Guide for UNIX and Linux

107 Parameters Used in initsid.utl F This appendix shows the parameters you can specify in the initsid.utl configuration file. The software passes these parameters to the backint interface through its -p parfile option. Unless otherwise noted, the parameters in this appendix section apply to the following environments: NetBackup for SAP on Oracle databases without RMAN NetBackup for SAP on Oracle databases with RMAN NetBackup for SAP on MaxDB databases Where necessary, the parameter descriptions in this appendix indicate whether they apply to only one or two of these environments. In addition, because not all parameters are useful when restoring NetBackup for SAP 6.0 images, the parameter descriptions indicate this. The following list summarizes the parameters and the database environments that support them: Parameter Name backint_dir backup_stream_buffersize bplist_filter client Underlying Database and Usage Notes Oracle without RMAN MaxDB Oracle without RMAN Oracle with RMAN MaxDB Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. Oracle without RMAN Oracle with RMAN MaxDB 95

108 Parameter Name custom_sort_file drives fail_backup inquire_query_period master_time_offset media_notify_script policy policy2 restore_filter restore_stream_buffersize retry_backup schedule Underlying Database and Usage Notes Oracle without RMAN Oracle without RMAN Oracle without RMAN Oracle with RMAN MaxDB Oracle without RMAN Oracle with RMAN MaxDB Oracle without RMAN Oracle with RMAN MaxDB Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. Oracle without RMAN Oracle with RMAN MaxDB Oracle without RMAN Oracle with RMAN MaxDB Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. MaxDB Oracle without RMAN Oracle with RMAN MaxDB Oracle without RMAN Oracle with RMAN MaxDB 96 NetBackup for SAP System Administrator s Guide for UNIX and Linux

109 backint_dir work_directory Parameter Name schedule2 server sleep sort_backup_type sort_restore_type switch_list switch_log switch_sem Underlying Database and Usage Notes Oracle without RMAN Oracle with RMAN MaxDB Oracle without RMAN Oracle with RMAN MaxDB Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. Oracle without RMAN Oracle without RMAN Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. Oracle without RMAN Oracle without RMAN Oracle without RMAN backint_dir work_directory Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. Set this parameter only if you have old backups performed with NetBackup 3.2. It must be set to a public directory. The NetBackup for SAP backint interface uses this directory for work space. NetBackup for SAP looks for the backint.times file and searches it for previously performed backups (using NetBackup for SAP 3.2). The NetBackup for SAP 4.5 and later releases do not use the backint.times file to store information about new backups. Appendix F, Parameters Used in initsid.utl 97

110 backup_stream_buffersize size backup_stream_buffersize size This parameter specifies the buffer size, in bytes, for stream-based backups. NetBackup receives data from MaxDB through the stream (pipe). When MaxDB passes the data to NetBackup, it uses this buffer size. Also see the restore_stream_buffersize parameter. bplist_filter script_path Note Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter resolves linked file paths on an inquire. Use this parameter only on rare occasions. As with the restore_filter, all of the following cases must exist before this parameter is used: Oracle table spaces use file paths. The directory paths to the Oracle table spaces are linked paths. The linked directory paths do not exist at restore time. The value for this option must be a fully qualified path name to a script with the right file permission. Test the script before implementing. The following is an example of an entry: bplist_filter /usr/openv/netbackup/ext/db_ext/sap/scripts\ /bplist_restore_filter The script must have an input parameter and output parameter and be able to modify the contents of a text file. The script is responsible for converting absolute directory paths into linked directory paths. This is just the opposite of restore_filter. The following is an example of this script: #!/bin/sh # this shell is used to change some logically linked files # during a restore # /oracle/sap/sapdata/sapdata1 to /oracle/product/7.0.16/sapdata1 # /oracle/sap/sapdata/sapdata2 to /oracle/product/7.0.16/sapdata2 # /oracle/sap/sapdata/sapdata3 to /oracle/product/7.0.16/sapdata3 # /oracle/sap/sapdata/sapdata4 to /oracle/product/7.0.16/sapdata4 # /oracle/sap/sapdata/sapdata5 to /oracle/product/7.0.16/sapdata5 # /oracle/sap/sapdata/sapdata6 to /oracle/product/7.0.16/sapdata6 sed -e s/\ oracle\ sap\ sapdata\ sapdata1/\ oracle\ product\ \ sapdata1/ s/\ oracle\ sap\ sapdata\ sapdata2/\ oracle\ product\ NetBackup for SAP System Administrator s Guide for UNIX and Linux

111 client client_machine_name 0.16\ sapdata2/ s/\ oracle\ sap\ sapdata\ sapdata3/\ oracle\ product\ \ sapdata3/ s/\ oracle\ sap\ sapdata\ sapdata4/\ oracle\ product\ \ sapdata4/ s/\ oracle\ sap\ sapdata\ sapdata5/\ oracle\ product\ \ sapdata5/ s/\ oracle\ sap\ sapdata\ sapdata6/\ oracle\ product \ \ sapdata6\/ $1 > $2 client client_machine_name This parameter specifies the machine that contains the NetBackup client software, a database, and an SAP environment. In some cases the server and client machine are the same machine. The following is an example: client saturn If the NetBackup for SAP backint interface finds the $SAP_CLIENT environment variable, the $SAP_CLIENT environment variable value overrides the client parameter value. If the client parameter is not specified, and there is no environment variable, then the client parameter value defaults to the specification for the CLIENT_NAME option in the NetBackup bp.conf file. If the value is not specified in the NetBackup bp.conf file, the NetBackup for SAP backint interface uses the value returned by the gethostname()library function. custom_sort_file file_path Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. Specify this parameter only when the sort_backup_type or the sort_restore_type parameters are set to custom. When custom is specified, set the custom_sort_file parameter to a valid file. The file_path value must be a full path name to a custom sort file that an end user created, and it must have public permissions. The following is an example argument to the custom_sort_file parameter: /usr/openv/dbext/ext/db_ext/sap/scripts/sap_custom_sort_file The custom sort file must include two fields. The first field groups a set of files into a particular bpbackup job. The second field is a file path name that maps the SAP backup file list to a group ID. Appendix F, Parameters Used in initsid.utl 99

112 custom_sort_file file_path Example of a Custom Sort File 1 /oracle/sap/sapdata1/btabd_1/btabd.data1 1 /oracle/sap/sapdata2/btabi_1/btabi.data1 1 /oracle/sap/sapdata2/clud_1/clud.data1 1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 1 /oracle/sap/sapdata5/ddici_1/ddici.data1 1 /oracle/sap/sapdata4/el30cd_1/el30cd.data1 1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 1 /oracle/sap/sapdata2/poold_1/poold.data1 1 /oracle/sap/sapdata1/pooli_1/pooli.data1 1 /oracle/sap/sapdata4/protd_1/protd.data1 1 /dev/rdsk/c0t4d0s6 2 /oracle/sap/sapdata1/roll_1/roll.data1 2 /oracle/sap/sapdata2/sourced_1/sourced.data1 2 /oracle/sap/sapdata3/stabd_1/stabd.data1 2 /oracle/sap/sapdata2/stabi_2/stabi.data2 2 /oracle/sap/sapdata1/temp_1/temp.data1 2 /oracle/sap/sapdata4/user1d_1/user1d.data1 2 /oracle/sap/sapdata2/user1i_1/user1i.data1 2 /oracle/sap/sapdata1/system_1/system.data1 2 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf 2 /oracle/sap/saplog1/log_g2_m1/log2_m1.dbf 2 /oracle/sap/saplog1/log_g3_m1/log3_m1.dbf 2 /oracle/sap/saplog1/log_g4_m1/log4_m1.dbf 2 /oracle/sap/dbs/cntrlsap.dbf Based on the preceding custom sort file, if SAP submits the entire file list to be backed up, there would be two bpbackup jobs running at the same time. The first job includes all the files that have a 1 in the first field. The second job includes all the files that have a 2 in the first field. The following is a list of jobs and associated files: Backup/Restore Job 1 /oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/el30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 100 NetBackup for SAP System Administrator s Guide for UNIX and Linux

113 drives number_of_drives /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 /dev/rdsk/c0t4d0s6 Backup/Restore Job 2 /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf /oracle/sap/saplog1/log_g2_m1/log2_m1.dbf /oracle/sap/saplog1/log_g3_m1/log3_m1.dbf /oracle/sap/saplog1/log_g4_m1/log4_m1.dbf /oracle/sap/dbs/cntrlsap.dbf drives number_of_drives Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies the number of bpbackup/bprestore commands to run. To maximize write performance to a Media Manager or disk storage unit, set the drives value to the number of Media Manager or disk storage units multiplied by the multiplex value per schedule. Based on the number of drives specified, the NetBackup for SAP backint interface simultaneously runs the same number of bpbackup/bprestore commands. If, for example, MPX is set to 4 and there are two available tape drives, set the drives parameter to 8 (4 X 2). The NetBackup for SAP backint interface runs eight bpbackup/bprestore jobs at the same time with four data streams going to each tape. The drives parameter should be set to the following rule: drives = Number_of_drives_per_policy X MPX_value_in_schedule The drives parameter value must not exceed the Set Maximum Jobs per Client global attribute. The following is an example entry: drives 5 Appendix F, Parameters Used in initsid.utl 101

114 fail_backup If the NetBackup for SAP backint interface finds the $SAP_DRIVES environment variable, the $SAP_DRIVES environment variable value overrides the drives parameter value. If the drives parameter is not specified and there is no environment variable, then the NetBackup for SAP backint interface exits with an error. fail_backup This parameter stops the backup process immediately when an error occurs. The standard behavior of backint is to continue processing even in the event of an error and then report the files that failed and the files that were successful. If this parameter is specified, then backint stops processing on the first error and reports failures for all the files that were not backed up. Note fail_backup only pertains to a specific kind of online backup. It is effective only when tablespace is set to #BEGIN/#END backup mode and when a related file backup takes place. This means that backint has to be called with the -t file_online parameter. inquiry_query_period months In the case of #NULL based inquiry queries, NetBackup for SAP restricts the catalog search to the last six months by default. You can use this parameter to specify a different query period. Specify an integer value for months. For example, if you want to set the query to the last 10 months, set this parameter as follows: inquiry_query_period 10 master_time_offset minutes This parameter restores old backups if there was a time difference between the master and client machines. Use this option only in the following circumstances: For restoring files backed up with NetBackup release 3.0 or older software. When the date and times are out of sync between the server and client machines. The parameter value, specified in minutes, is subtracted from the start time and added to the end time for a restore or inquire. The following is an example of an entry: master_time_offset NetBackup for SAP System Administrator s Guide for UNIX and Linux

115 media_notify_script script_path media_notify_script script_path Note Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter calls a script when a Waiting mount is entered in a bpbackup/bprestore log. You can use this parameter to send a message that requests a tape mount to an SAP user. For script_path, specify the full path name to a script. The script must have 755 file permissions. Test the script before implementation. The following is an example entry: media_notify_script /oracle/sap/sapscripts/sap_media_notify If the message is encountered and this parameter is specified, then the following commands are executed from the NetBackup for SAP backint interface: MEDIA_ID=A001;export MEDIA_ID NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER /oracle/sap/sapscripts/sap_media_notify policy policy_name This parameter specifies the name of an SAP policy defined in NetBackup. The SAP policy must have an Application Backup schedule defined in order for the NetBackup for SAP backint interface to work. The following is an example entry: policy sap_nb If the NetBackup for SAP backint interface finds the $SAP_POLICY environment variable, the $SAP_POLICY environment variable value overrides the policy parameter value. If the policy parameter is not specified, and there is no environment variable, then the policy parameter value defaults to the specification for the BPBACKUP_POLICY option in the NetBackup bp.conf file. By default, if BPBACKUP_POLICY is not specified in any NetBackup bp.conf file, NetBackup uses the first active SAP policy type it finds for the client with an Application Backup schedule. policy2 policy_name This parameter specifies the name of a policy to be used for the secondary SAP backup. A secondary backup is performed for each SAP database backup on files that are needed to track SAP backup information. You can use this option to save the backup information on a different media. If policy2 is not specified and schedule2 is specified, then NetBackup uses the value specified for the policy parameter. Appendix F, Parameters Used in initsid.utl 103

116 restore_filter script_path restore_filter script_path Note Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter resolves linked file paths on a restore. Use this parameter only on rare occasions. The following cases must exist before this parameter is used: Oracle table spaces use file paths. The directory paths to the Oracle table spaces are linked paths. The linked directory paths do not exist at restore time. The value for this parameter must be a fully qualified file path name to a script with the right permissions. Test the script before implementation. The following is an example of an entry: restore_filter /usr/openv/netbackup/ext/db_ext/sap/\ scripts/sap_restore_filter The script must have an input parameter and an output parameter. It must be able to modify the contents of a text file. The script converts linked directory paths into absolute directory paths. The following is an example of this script: #!/bin/sh # this shell is used to change some logically linked files # during a restore # /oracle/sap/sapdata/sapdata1 to /oracle/product/7.0.16/sapdata1 # /oracle/sap/sapdata/sapdata2 to /oracle/product/7.0.16/sapdata2 # /oracle/sap/sapdata/sapdata3 to /oracle/product/7.0.16/sapdata3 # /oracle/sap/sapdata/sapdata4 to /oracle/product/7.0.16/sapdata4 # /oracle/sap/sapdata/sapdata5 to /oracle/product/7.0.16/sapdata5 # /oracle/sap/sapdata/sapdata6 to /oracle/product/7.0.16/sapdata6 sed -e s/\ oracle\ sap\ sapdata\ sapdata1/\ oracle\ product\ \ sapdata1/ s/\ oracle\ sap\ sapdata\ sapdata2/\ oracle\ product\ \ sapdata2/ s/\ oracle\ sap\ sapdata\ sapdata3/\ oracle\ product\ \ sapdata3/ s/\ oracle\ sap\ sapdata\ sapdata4/\ oracle\ product\ \ sapdata4/ s/\ oracle\ sap\ sapdata\ sapdata5/\ oracle\ product\ \ sapdata5/ s/\ oracle\ sap\ sapdata\ sapdata6/\ oracle\ product \ \ sapdata6\/ $1 > $2 104 NetBackup for SAP System Administrator s Guide for UNIX and Linux

117 restore_stream_buffersize size restore_stream_buffersize size This parameter specifies the buffer size, in bytes, for stream-based restores. MaxDB receives data from NetBackup through the stream (pipe). When MaxDB receives the data from NetBackup and copies it to the pipe, it uses this buffer size. For more information, see the backup_stream_buffersize parameter. retry_backup number_of_retries This parameter specifies the number of retries for a failed backup. When specified, backint retries a failed bpbackup job the specified number of times. For example: retry_backup 2 schedule schedule_name This parameter specifies the name of an Application Backup schedule associated with an SAP policy type. The schedule can define aspects of the backup such as how long NetBackup retains images, maximum MPX per drive, storage unit, and volume pool. The following is an example entry: schedule sap_full_backup If the NetBackup for SAP backint interface finds the $SAP_SCHED environment variable, the $SAP_SCHED environment variable value overrides the schedule parameter value. If the schedule parameter is not specified and there is no environment variable, then the schedule parameter value defaults to the BPBACKUP_SCHED option in the NetBackup bp.conf file. If BPBACKUP_SCHED is not specified in the NetBackup bp.conf file, NetBackup uses the first Application Backup schedule it finds in the first active SAP policy. schedule2 schedule_name This parameter specifies name of an Application Backup schedule to be used for the secondary SAP backup. If it is not specified, the schedule parameter value is used. For each SAP backup, NetBackup performs two individual backups. The first backup backs up database data. The second backup backs up log files needed to track SAP backup information. You can use this parameter to save SAP log files to a different media. This can make it easier to restore a database. You can also use this option to save the backup information to a different volume pool. The following is an example entry: schedule2 sap_backup_information Appendix F, Parameters Used in initsid.utl 105

118 server server_name server server_name This parameter specifies the name of the NetBackup master server. The NetBackup master server is the name of the machine that provides most of the administration and control for NetBackup operations. It contains the NetBackup database. The following is an example entry: server jupiter If the NetBackup for SAP backint interface finds a $SAP_SERVER environment variable, the $SAP_SERVER environment variable value overrides the server parameter value. If the server parameter is not specified, and there is no environment variable, the server parameter value defaults to the specification for the SERVER option specified in the NetBackup bp.conf file. sleep seconds Note Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter specifies a sleep time to monitor the bpbackup or bprestore logs. If it is not specified, NetBackup uses a default value of five seconds. When the NetBackup for SAP backint interface is called, a number of bpbackup and bprestore commands can be running at the same time. The NetBackup for SAP backint interface monitors each command and writes to the file that is specified on the -o out_file parameter. In some cases, bpbackup and bprestore information is not displayed because of the monitoring cycle. Therefore, this option is used mainly when debugging. The following is an example entry: sleep 3 sort_backup_type value Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies one of four different backup sort parameter values: custom, device, drive, or size (default). The following sections describe each of these parameters. 106 NetBackup for SAP System Administrator s Guide for UNIX and Linux

119 sort_backup_type value sort_backup_type custom Specifies that a customized sort file be used. If sort_backup_type custom is specified, also specify the custom_sort_file parameter with a file path. For more information, see custom_sort_file file_path on page 99. sort_backup_type device Specifies that NetBackup create jobs based on a file s device ID. Because this parameter overrides the drives parameter, the number of Media Manager or disk storage units specified in the intsid.utl file is not used. For example, if there are 12 files requested for backup, and they reside on two different devices (X and Y), then two jobs are forked. The first job contains all the files associated with device X, and the second job contains all the files on device Y. The following example shows how jobs are created when device is specified: Input file list from SAP (brbackup, sapdba) /oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/el30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 /dev/rdsk/c0t4d0s Backup Job 1 (all have the device ID X) /oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/el30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 Appendix F, Parameters Used in initsid.utl 107

120 sort_backup_type value /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 Backup Job 2 (all have the same device ID Y) /dev/rdsk/c0t4d0s Note The implementation is based on the st_dev value from the stat()function. This identifies a file partition. sort_backup_type drive Specifies that NetBackup create jobs based on the number of simultaneous backup jobs specified by the drives parameter in the initsid.utl file. For example, if there are three tape drives and 10 SAP files, the following distribution occurs: Input file list from SAP /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf Backup/Restore Job 1 /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata2/user1i_1/user1i.data1 Backup/Restore Job 2 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata1/system_1/system.data1 108 NetBackup for SAP System Administrator s Guide for UNIX and Linux

121 sort_backup_type value Backup/Restore Job 3 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf sort_backup_type size (Default) This is the default value for the sort_backup_type parameter. If sort_backup_type size is specified, NetBackup creates jobs based upon the number of drives specified in the initsid.utl file. Each file being backed up is associated with a backup job based on size. For example, if three tape drives are specified, the files are divided evenly into three bpbackup jobs based on size. So, if there are 25 input files from SAP and three tape drives, then three bpbackup jobs would be running at the same time with the following files in each job: Input file list from SAP (brbackup, sapdba) /oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/el30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 /dev/rdsk/c0t4d0s /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf /oracle/sap/saplog1/log_g2_m1/log2_m1.dbf /oracle/sap/saplog1/log_g3_m1/log3_m1.dbf /oracle/sap/saplog1/log_g4_m1/log4_m1.dbf /oracle/sap/dbs/cntrlsap.dbf Appendix F, Parameters Used in initsid.utl 109

122 sort_backup_type value Backup Job 1 size= : file /name=/oracle/sap/sapdata1/roll_1/roll.data1 size= : file name=/oracle/sap/sapdata1/temp_1/temp.data1 size= : file name=/oracle/sap/sapdata1/ddicd_1/ddicd.data1 size= : file name=/oracle/sap/sapdata1/el30ci_1/el30ci.data1 size= : file name=/oracle/sap/saplog1/log_g4_m1/log4_m1.dbf Total= Backup Job 2 size= : file name=/oracle/sap/sapdata1/system_1/system.data1 size= : file name=/oracle/sap/sapdata2/btabi_1/btabi.data1 size= : file name=/oracle/sap/sapdata5/ddici_1/ddici.data1 size= : file name=/oracle/sap/sapdata6/es30cd_1/es30cd.data1 size= : file name=/oracle/sap/sapdata2/poold_1/poold.data1 size= : file name=/oracle/sap/sapdata3/stabd_1/stabd.data1 size= : file name=/oracle/sap/sapdata1/pooli_1/pooli.data1 size= : file name=/oracle/sap/sapdata2/user1i_1/user1i.data1 size= : file name=/oracle/sap/saplog1/log_g1_m1/log1_m1.dbf size= : file name=/oracle/sap/dbs/cntrlsap.dbf Total= Backup Job 3 size= : file name=/dev/rdsk/c0t4d0s6 size= : file name=/oracle/sap/sapdata2/clud_1/clud.data size= : file name=/oracle/sap/sapdata4/el30cd_1/el30cd.data1 size= : file name=/oracle/sap/sapdata4/protd_1/protd.data1 size= : file name=/oracle/sap/sapdata2/sourced_1/sourced.data1 size= : file name=/oracle/sap/sapdata2/stabi_2/stabi.data2 size= : file name=/oracle/sap/sapdata4/user1d_1/user1d.data1 size= : file name=/oracle/sap/sapdata1/btabd_1/btabd.data1 size= : file name=/oracle/sap/saplog1/log_g2_m1/log2_m1.dbf size= : file name=/oracle/sap/saplog1/log_g3_m1/log3_m1.dbf Total= The number of drives specified does not have to equal the number of physical Media Manager or disk storage units. The number of drives correlates to the number of simultaneous bpbackup jobs run by the NetBackup for SAP backint interface. For example, if you had 10 SAP files and three tape drives, you can specify 10 drives in the initsid.utl file. This causes 10 bpbackup jobs with one file for each bpbackup job. Netbackup handles all of the job scheduling. Initially, three bpbackup jobs are active and the other seven jobs are queued. You can increase the number of active jobs and data throughput by increasing the multiplex value for the policy. 110 NetBackup for SAP System Administrator s Guide for UNIX and Linux

123 sort_restore_type value sort_restore_type value Note Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies one of three different restore sort options: custom, drive, or image (default). The following sections describe the possible parameter values. sort_restore_type custom Specifies that a customized sort file be used. If sort_restore_type custom is specified, also specify the custom_sort_file parameter with a file path. For more information, see custom_sort_file file_path on page 99. sort_restore_type drive Specifies that NetBackup create jobs based on the number of Media Manager or disk storage units specified in the drives parameter in the initsid.utl file. For example, if there are three tape drives and 10 SAP files, the following distribution occurs: Input file list from SAP /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf Appendix F, Parameters Used in initsid.utl 111

124 sort_restore_type value Backup/Restore Job 1 /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata2/user1i_1/user1i.data1 Backup/Restore Job 2 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata1/system_1/system.data1 Backup/Restore Job 3 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf sort_restore_type image (Default) Specifies that backint create groups of files based on their backup image numbers and fork a bprestore for each group. This is the default behavior used if the sort_restore_type parameter is not set in the intsid.utl file. For example, if nine files were backed up by two bpbackup jobs, each file is associated with one of two backup image IDs. If all nine files are restored, then there are two bprestore jobs forked by the NetBackup for SAP backint interface, one job for each image. The files are grouped the way they were backed up. The following is an example of a restore. Input file list from SAP (brrestore, sapdba): Image 1: /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 112 NetBackup for SAP System Administrator s Guide for UNIX and Linux

125 switch_list control_file_path Image 2: /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf Restore Job 1: /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 Restore Job 2: /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf Note Restore forks another job for raw partition files if they are grouped with regular files. switch_list control_file_path Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies a control file that communicates between the NetBackup for SAP backint interface and brbackup for online backups. A switch list file is created every time brbackup wants to back up a file or when it wants to indicate that a backup is finished. The switch_list parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.lis The following is an example of a valid entry: switch_list /oracle/sap/sapbackup/.switch.lis Appendix F, Parameters Used in initsid.utl 113

126 switch_log control_file_path switch_log control_file_path Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies a control file that communicates between the NetBackup for SAP backint interface and brbackup. After the switch semaphore file has been deleted, the NetBackup for SAP backint interface opens and reads the switch log file, created by brbackup, to determine if the process is successful. The switch_log parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.log The following is an example of a valid entry: switch_list /oracle/sap/sapbackup/.switch.log switch_sem control_file_path Note Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies a control file that communicates between the NetBackup for SAP backint interface and brbackup. After the switch list file has been created and closed, the NetBackup for SAP backint interface creates the switch semaphore file and waits until it is deleted by brbackup. The switch_sem parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.sem The following is an example of a valid entry: switch_list /oracle/sap/sapbackup/.switch.sem 114 NetBackup for SAP System Administrator s Guide for UNIX and Linux

127 Using NetBackup for SAP to Back Up SAPDB G You can use NetBackup for SAP to back up the SAPDB RDBMS. SAPDB relies on an additional adapter program to communicate with NetBackup for SAP. The adapter program is part of the SAPDB distribution. To back up the SAPDB RDBMS, perform the additional configuration tasks that this appendix describes. Follow the NetBackup for SAP directions in Configuration on page 27 to create a policy for SAPDB backups, and then follow the directions in this appendix to perform the following extra configuration steps: Creating the additional configuration files on the SAPDB client Defining a backup medium in SAPDB Note With the release of NetBackup for SAP 6.0, VERITAS does not recommend using the information in this appendix to create backups. Use the newer procedures for backing up and restoring database files that are described in the main sections of this manual. However, if you have backups that were created with a NetBackup for SAP software release prior to 6.0, follow the procedure in Performing a Restore on page 120 to restore those files. Creating Backup Environment Configuration Files In order to configure the backup environment to use NetBackup for SAP to back up SAPDB, you create the following files on the NetBackup for SAP (SAPDB) client: The backint for SAPDB configuration file. The adapter program configuration file. The NetBackup for SAP configuration file, initsid.utl. 115

128 Creating Backup Environment Configuration Files backint for SAPDB Configuration File The backint for SAPDB configuration file provides information about the adapter program to SAPDB. Set the BSI_ENV environment variable to point to the name and location of this file. The configuration file can contain the following parameters: Parameter BACKINT absolute_path/file_name INPUT absolute_path/file_name OUTPUT absolute_path/file_name ERROROUTPUT absolute_path/file_name Description Absolute path and name of the backint program. Absolute path and name of the standard input file. Absolute path and name of the standard output file. Absolute path and name of the standard error output file. PARAMETERFILE absolute_path/file_name Absolute path and name of the configuration file of the backint for SAPDB program. TIMEOUT_SUCCESS number TIMEOUT_FAILURE number ORIGINAL_RUNDIRECTORY absolute_path Time, in seconds, that the database manager waits for the end of a started backint for SAPDB process if the action is successful. Optional. Time, in seconds, that the database manager waits for the end of a started backint for SAPDB process if errors occur. Optional. Absolute path to the run directory of the source database. Optional. For a detailed description of these parameters, see the SAPDB documentation, available on The following is an example of a backint for SAPDB configuration file with the minimum configuration specified: BACKINT /export/home/sapdb/depend/bin/backint INPUT /export/home/sapdb/logs/backint.in OUTPUT /export/home/sapdb/logs/backint.out ERROROUTPUT /export/home/sapdb/logs/backint.err PARAMETERFILE /export/home/sapdb/indep_data/wrk/adapter.config 116 NetBackup for SAP System Administrator s Guide for UNIX and Linux

129 Creating Backup Environment Configuration Files The PARAMETERFILE specifies the name and location of the adapter program configuration file described in Adapter Program Configuration File on page 117. Adapter Program Configuration File The configuration file for the adapter program specifies to the adapter program the location of the NetBackup for SAP (backint for Oracle) software. It also specifies parameters to use when communicating with NetBackup for SAP. Specify the name and location of the adapter program configuration file as the argument to PARAMETERFILE in the backint for SAPDB configuration file. For information on the SAPDB configuration file, see backint for SAPDB Configuration File on page 116. You can include the following parameters in the adapter program file: Parameter Description STAGING AREA: absolute_path/file_name size [KB MB GB] Absolute path and size of a temporary file. FILES PER BACKINT CALL: number BACKINT: absolute_path/file_name PARAMETERFILE OF BACKINT: absolute_path/file_name HISTORY FILE: absolute_path/file_name INPUTFILE FOR BACKINT: absolute_path/file_name OUTPUT FILE FOR BACKINT: absolute_path/file_name Maximum number of temporary files that are to be processed by backint for Oracle concurrently. Optional. Absolute path and name of the backint for Oracle program. Absolute path and name of the configuration file for the backint for Oracle program. Absolute path and name of the backup history file. Absolute path and name of the standard input file. Absolute path and name of the standard output file. Appendix G, Using NetBackup for SAP to Back Up SAPDB 117

130 Creating Backup Environment Configuration Files Parameter ERRORFILE FOR BACKINT: absolute_path/file_name MAXIMAL DELAY OF BACKINT CALL: number OMIT LAST DIRECTORY DELIMITER ON RESTORE: YES NO BI_CALLER_VALUE: value Description Absolute path and name of the standard error output file. Maximum waiting time, in seconds, between creating a temporary file and starting to save it by using backint for Oracle. Optional. Specifies whether the SAPDB adapter program ignores the closing slash (/) of an absolute directory name for backint for Oracle. Optional. Value of the BI_CALLER environment variable. Optional. For a detailed description of these parameters, see the SAPDB documentation, at The following is an example of a file with the minimum configuration specified: BACKINT: /usr/openv/netbackup/bin/backint PARAMETERFILE OF BACKINT: /export/home/sapdb/data/wrk/initsid.utl HISTORY FILE: /export/home/sapdb/logs/backinthistory INPUTFILE FOR BACKINT: /export/home/sapdb/logs/backintoracle.in OUTPUTFILE FOR BACKINT: /export/home/sapdb/logs/backintoracle.out ERRORFILE FOR BACKINT: /export/home/sapdb/logs/backintoracle.err NetBackup for SAP Configuration File, initsid.utl The initsid.utl file includes the NetBackup for SAP parameters. This file is the NetBackup for SAP configuration file, and it is named on the argument to the PARAMETERFILE OF BACKINT parameter, described in Adapter Program Configuration File on page 117. For more information, see Modifying the initsid.utl File on page NetBackup for SAP System Administrator s Guide for UNIX and Linux

131 Defining a Backup Medium in SAPDB Defining a Backup Medium in SAPDB Prior to running a backup, create at least one backup medium per backup type (complete, incremental) in SAPDB. When using backint for Oracle, the name of the backup medium created must begin with BACK. The type of backup medium must be PIPE. To create a backup medium 1. Enter command mode. For example: dbmcli -d MYSAP -u dbm,dbm 2. Create the backup medium. For example: dbmcli on MYSAP>medium_put BACKORA /home/sapdb/medium PIPE DATA 0 8 Performing a Backup When backing up SAPDB, include the backup medium you created. The example in Defining a Backup Medium in SAPDB on page 119 created a backup medium called BACKORA. The example in this section uses that sample backup medium. To run a backup 1. Initiate a utility session. For example: dbmcli on MYSAP>util_connect 2. Inititate the backup. For example: dbmcli on MYSAP>backup_start BACKORA DATA You can also start the backup from the DBM GUI. For more information about the DBM GUI and configuring external backup tools, refer to the SAPDB documentation at Appendix G, Using NetBackup for SAP to Back Up SAPDB 119

132 Performing a Restore Performing a Restore To perform a restore Enter the following commands: dbmcli> backup_ext_ids_get BACK OK dbmcli> backup_ext_ids_list OK END list of EBIDS dbmcli> recover_start BACKORA ExternalBackupId "EBID" EBID The backup identifier. This information is returned in the list of EBIDS when you perform a query. 120 NetBackup for SAP System Administrator s Guide for UNIX and Linux

133 Index A B accessibility features xi alternate client restore see redirected restore Application Backup schedule backup window 33 configuring 32 overview 32, 34 retention 33 archives, creating 64 automatic backup create scripts 40 schedule bphdb log 79 manual backup automatic backup schedules configuring 33 Automatic Full Backup schedule overview 34 Automatic Incremental Backup schedule overview 34 backint interface command line 84 defined 83 input file 87 linking with NetBackup for SAP 25 parameter file 85 restore process 66 role in backup process 57 sequence of operation 6 technical overview 5 theory of operation 83 BACKINT parameter 50, 51 backint_dir parameter 97 Backup ID see BID backup medium configuring 71 defined 71 Backup Selections list adding selections 38 overview 38 backup_dev_type parameter 47 backup_stream_buffersize parameter 98 backups also see automatic backup automatic (configuring scripts) 40 manual 53 offline 58 online 62 output file contents 89 pre scripts for backup operations 41 when using MaxDB 72 BID generation process 57 returned on backup 89 bp.conf administrator 82 repository for script parameters 43, 93 bpdbm daemon 20 bphdb log 78, 79 role in backups and restores 6 role in offline backups 40 bplist_filter parameter 98 bpplclients command 13, 20, 21 brarchive command example script 40 installation directory 25 overview 5, 9 using 64 brbackup command backint parameter file 113 example script

134 C D install directory 25 multiplexing 28 overview 5, 9 sequence of operation 6 use in online backup 62 using to start a backup 57 using without sapdba 62 brconnect command 25 brrestore command installation directory 25 overview 5, 9 using 66 brtools command 25 bsi.env file overview 44 parameters 51 procedure for modifying 50 client list 17 client parameter 45, 99 client read timeout property 82 cluster software prerequisites 13 cluster_config script 13, 22, 24 commands backint 84 bpplclients 13, 20, 21 brarchive 5, 9, 25, 40, 64 brbackup 5, 6, 9, 25, 28, 40, 62 brconnect 25 brrestore 5, 9, 25, 66 brtools 25 export 40 get_license_key 15, 23 initbpdbm 20 install_dbext 19, 24 sapdba 25 stopsap R3 58 su 41 update_dbclients 13, 17, 21 compatibility information 11 configuration database debug level 78 Media Manager 12 custom_sort_file parameter 99 daemons, see processes database software prerequisites for installation 12 E F G I J debug logs description 78 in /usr/openv/netbackup/logs 78 debugging level 78 directory debug log 78 repository for commands 25 drives parameter 28, 45, 54, 101 environment variables 43, 91 ERROROUTPUT parameter 50, 51 export command 40 fail_backup parameter 102 get_license_key command 15, 23 initbpdbm command 20 initsid.sap file Oracle substitution characters 48 procedure for modifying 47 script parameters 43 initsid.utl file effect on Maximum Jobs per Client parameter 28 Oracle substitution characters 46 overview 44 parameter summary 95 procedure for modifying 45 script parameters 43 specifying a schedule name in 33 INPUT parameter 50, 51 inquiry_query_period parameter 102 install script 15, 23 install_dbext command 19, 24 installation database software prerequsites 12 local 22 platform compatibility 11 prerequisites 11 prerequisites in a cluster 13 remote 14 requirements for NetBackup software 12 Java interface NetBackup for SAP System Administrator s Guide for UNIX and Linux

135 L M N O licensing information 15, 23 local installation procedure 22 log files accessing 79 also see debug logs enabling 78 sapdba utility 80 troubleshooting with log files 78 manual backups, see backups master_time_offset parameter 102 MaxDB database administrative interface 5 backup script 40 bsi.env file 44 configuration 71 configuration files 44 SAP parameter file 44 technical overview 4, 10 terminology 1 maximum jobs per client 28 Media Manager configuring backup media 12 media, defined 71 media_notify_script parameter 103 medium, defined 71 multiple copies feature 36 multiplexing overview 2 testing multiple drives 54 with MaxDB 74 multistreamed backups 82 nbjm scheduling process 79 nbpem scheduling process 79 nbrb scheduling process 79 offline backups 58 online backups 62 Oracle database configuration files 44 initsid.sap file 44 SAP parameter file 44 SAP profile file 44 SAP tools support 1 substitution characters 46, 48 P technical overview 4, 6 with RMAN backup script 40 linking with the SBT library 26 technical overview 7 without RMAN backup script 40 linking with backint 25 technical overview 7 ORIGINAL_RUNDIRECTORY parameter 51 OUTPUT parameter 50, 51 parameter file initsid.sap 43 initsid.utl 43 PARAMETERFILE parameter 50, 51 parameters BACKINT 50, 51 backint_dir 97 backup_dev_type 47 backup_stream_buffersize 98 bplist_filter 98 client 45, 99 custom_sort_file 99 drives 28, 45, 54, 101 ERROROUTPUT 50, 51 fail_backup 102 INPUT 50, 51 inquiry_query_period 102 master_time_offset 102 media_notify_script 103 ORIGINAL_RUNDIRECTORY 51 OUTPUT 50, 51 PARAMETERFILE 50, 51 policy 45, 103 policy2 103 restore_filter 104 restore_stream_buffersize 105 retry_backup 105 rman_parms 48 schedule 45, 105 schedule2 105 server 45, 106 sleep 106 sort_backup_type 106 sort_restore_type 111 switch_list 45, 113 Index 123

136 R S switch_log 45, 114 switch_sem 45, 114 TIMEOUT_FAILURE 51 TIMEOUT_SUCCESS 51 util_par_file 44, 47 platform compatibility 11 policy configuration adding clients 37 adding new 30 attributes 31 backup selections list 38 overview 30 schedules 32 testing 53 policy parameter 45, 103 policy2 parameter 103 processes bpdbm 20 bphdb 40 log files for NetBackup processes 79 scheduling (nbpem, nbjm, nbrb) 79 recovery manager, see Oracle database redirected restore 66 remote folder button 39 remote installation procedure 14 reports All Log Entries report 80 also see log files 78 NetBackup server reports 80 restore_filter parameter 104 restore_stream_buffersize parameter 105 restores output file contents 89 pre using sapdba 66 with MaxDB 74 with Oracle 66 retention period for frequency-based schedules 36 retry_backup parameter 105 RMAN see Oracle database rman_parms parameter 48 robust logging 79 SAP DB database backing up and restoring 115 pre-6.0 backups and restores 115 terminology 1 SAP tools, see sapdba SAP_CLIENT environment variable 91 SAP_DRIVES environment variable 91 sap_maxdb_backup script 40 sap_offline_backup script 40 sap_online_backup script 40 SAP_POLICY environment variable 91 sap_redo_log script 40 sap_rman_backup script 40 SAP_SCHED environment variable 91 SAP_SERVER environment variable 91 sapdba backup process 58 command 25 databases that sapdba supports 1 defined 9 examples 58 offline backup 58 restore process 66 technical overview 5 utility log 80 schedule parameter 45, 105 schedule2 parameter 105 schedules adding 32 frequency 35 properties 35 retention 36 types of schedules 32 scripts backup 40 cluster_config 13, 22, 24 examples 40 install 15, 23 restore 40 su command 41 type of operation 40 usage caution 40 server parameter 45, 106 skipped clients 18 sleep parameter 106 sort_backup_type parameter 106 sort_restore_type parameter 111 switch_list parameter 45, 113 switch_log parameter 45, 114 switch_sem parameter 45, NetBackup for SAP System Administrator s Guide for UNIX and Linux

137 T testing policy configuration 53 timeout failures, minimizing 82 TIMEOUT_FAILURE parameter 51 TIMEOUT_SUCCESS parameter 51 troubleshooting logs 78 U unified logging 79 update_dbclients command 13, 17, 21 utl_par_file parameter 44 utl_par_file parameters 47 W Windows interface 28 Index 125

138 126 NetBackup for SAP System Administrator s Guide for UNIX and Linux