NSR-R/3 V3.0 (Solaris, Linux)

Transcription

1 Target group The information in this guide is intended for system administrators who are responsible for installing software and maintaining the servers and clients on a network. Operators who monitor the daily backups may also find this manual useful. Contents This guide provides information on how to configure and manage the NSR-R/3 software. Edition: September 2004 Product Number: File: nsr-r3.pdf Base of NSR-R/3 V3.0 / this guide: Legato NetWorker Module for SAP R/3 with Oracle, Release 3.0, Multiplatform Version, Copyright 2003, LEGATO Software, a division of EMC Copyright Fujitsu Siemens Computers GmbH All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. This manual was produced by cognitas. Gesellschaft für Technik-Dokumentation mbh

2

3 Contents Preface Audience Product Documentation Conventions Information and Services Customer Service Technical Support Chapter 1: Introduction Importance of Backing Up Mission-Critical Data Naming Conventions Used in This Guide Basic Network Configuration Summary of Features NetWorker Server Software Features NSR-R/3 Software Features New or Enhanced Features Improved Administrator s Security Expiration Parameter Replaces Browse and Retention Policy Settings Added Support for SAP BRRECOVER Improved Manageability and Performance of Backups and Restores Improved Logging and Placement of Log/Temporary Files More Flexible Query and Restore More Flexible Backup and Restore User Selection New Data Compression Algorithms BRTools Software Features Oracle RMAN Software Features NetWorker PowerSnap Features

4 Contents Types of PowerSnap Backups Supported Types of PowerSnap Restores Supported Summary of Components and Settings NetWorker Server Components NSR-R/3 Components NetWorker Client Settings SAP Components Oracle Components PowerSnap Components Summary of Processes Backup with SAPDBA or brbackup Backup with RMAN Restore with SAPDBA or brrestore Restore with RMAN Related Documentation Chapter 2: Basic Software Configuration Task 1: Configure the Environment Task 2: Configure the NetWorker Resources Task 3: Configure the NSR-R/3 Parameters Task 4: Configure the Backup and Restore Utility Example: Configuring backint as the Backup and Restore Utility Example: Configuring RMAN as the Backup and Restore Utility Task 5: Configure a Backup of Cluster Data Chapter 3: Installation Installation Requirements Supported Operating Systems Software Requirements Files Installed Upgrading from Release 2.x of NSR-R/

5 Contents Install Procedures Installing the NSR-R/3 Software Task 1: Access the Installation Files From a Local CD-ROM From the Fujitsu Siemens Computers Web Site Task 2: Install the NSR-R/3 Software Installing the NSR-R/3 Software in a Nondefault Location Installing the NSR-R/3 Software on Solaris with Installer Installing RMAN Components (NSR-DBM-ORA, Optional) Installing Licenses Managing Your Fujitsu Siemens Computers Licenses Uninstall Procedures Uninstalling the RMAN Components (NSR-DBM-ORA) Chapter 4: Manual Backups About Manual Backups Performing an Offline Manual Backup How to Perform an Offline Backup Performing an Online Manual Backup How to Perform an Online Backup Backing Up the Client File Indexes and Bootstrap Reviewing Backup Session Reports Chapter 5: Scheduled Backups Task 1: Test Basic Settings Task 2: Configure the Client Resource Task 3: Configure the Scheduled Backup Configuration File Reviewing Backup Session Reports Chapter 6: Cloning Save Sets Clone Command Syntax and Options

6 Contents Monitoring the Cloning Process Chapter 7: Restoring Data Reviewing Save Sets Expiration of Save Sets Performing Restores How to Restore a Database or Database Object Restoring SAP R/3 with Oracle Cluster Data Reviewing Restore Session Reports Chapter 8: PowerSnap Backups and Restores Requirements Supported Environments Required Software Components Types of PowerSnap Backups Instant Backup Live Backup Immediate Live Backup Deferred Live Backup Types of PowerSnap Restores Instant Restore Rollback Restore from Secondary Storage PowerSnap Backup and Restore Data Flows Quick Start PowerSnap Software Configuration Roadmap Configuring NetWorker Resources for PowerSnap Configuring the NetWorker Snapshot Pool Resource Configuring the NetWorker Snapshot Policy Resource Configuring the NetWorker Group Resource Configuring the NetWorker Client Resource

7 Contents Setting PowerSnap Parameters in the NSR-R/3 configuration file Setting Variables in the PowerSnap Configuration File PowerSnap Use of Equivalent NSR-R/3 Parameters Invoking PowerSnap Backup Processes Instant Backup Processes Immediate Live Backup Processes Deferred Live Backup Processes Querying PowerSnap Backup Records Invoking PowerSnap Restore Processes Instant Restore and Rollback Processes Restore from Secondary Storage Processes Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore Syntax and Options for brbackup and brarchive Commands Syntax and Options for brrecover Command Syntax and Options for brrestore Command Appendix B: Environment Variables for RMAN Setting the Environment Variables Environment Variable Definitions Appendix C: Troubleshooting Verifying the Release Information Generating Diagnostic Logs Backup and Restore Problems Regular Session Error Messages Fatal Error Messages Glossary Index

8 Contents 8

9 Preface This guide provides information on how to configure and manage the NSR-R/3 software. Install this multiplatform NSR-R/3 software on the supported Solaris, or Linux server and clients before using the information presented in this guide. For installation instructions, refer to "Chapter 3: Installation" on page 47. Audience The information in this guide is intended for system administrators who are responsible for installing software and maintaining the servers and clients on a network. Operators who monitor the daily backups may also find this manual useful. Product Documentation Fujitsu Siemens Computers offers an extensive archive of product documentation at its web site The NetWorker Module documentation can be found following the links NetWorker Modules / NSR-R/3 and then Support / manuals. Most of the documents are in Adobe Acrobat Portable Document Format (PDF), and can be viewed by downloading and installing the Adobe Acrobat Reader as of V4.05. The Reader is available from Adobe at To install and use the Reader on the platform of your choice, refer to the instructions at the Adobe web site. 9

10 Conventions Conventions This document uses the following typographic conventions and symbols to make information easier to access and understand. Convention Indicates Example boldface italic in text italic in command line fixed-width fixed-width, boldface Important: Names of line commands, daemons, options, programs, or scripts Pathnames, filenames, computer names, new terms defined in the Glossary or within the chapter, or emphasized words A variable that must be provided in the command line Examples and information displayed on the screen Commands and options that must be entered exactly as shown Information that must be read and followed to ensure successful backup and recovery of data Ensure the backint executable binary file is in the same directory as BRTools. Most NSR-R/3 logs can be found by searching for /nsr/applogs/*backint*. brrestore -m tablespace_name media waiting: recover waiting for 8mm 5GB tape volume name brrestore -verify Important: Use the no_verify option with extreme caution. 10

11 Preface Information and Services Fujitsu Siemens Computers offers a variety of methods for you to obtain company, product, and technical information. Customer Service Technical Support Service Latest news about NetWorker and software patches Address Support phone Support fax Customer Interaction Center Fujitsu Siemens Computers workshop center Technical Support The Support section of the Fujitsu Siemens Computers web site at provides links with contact information, software patches, technical documentation, and information about available support programs. If you have an active support agreement, you may contact your service provider. If you do not have an active support agreement, contact your Fujitsu Siemens Computers sales representative to purchase a service contract or updates. 11

12 Technical Support 12

13 Chapter 1: Introduction This chapter describes the main features and components of NSR-R/3, and the associated NetWorker, SAP, and Oracle systems. It also describes the NetWorker PowerSnap module, which is required for snapshot backups. This chapter contains the following sections: "Importance of Backing Up Mission-Critical Data" on page 13 "Naming Conventions Used in This Guide" on page 14 "Basic Network Configuration" on page 14 "Summary of Features" on page 15 "Summary of Components and Settings" on page 21 "Summary of Processes" on page 25 "Related Documentation" on page 28 Importance of Backing Up Mission-Critical Data It is important to back up computer systems to protect them from the loss of valuable data. In a network environment, where users depend on shared data and the amount of data continuously grows, the need to manage data becomes crucial. A viable backup strategy includes regular backups of databases and archive logs. Without archive logs, you can recover a database only to the time of its last full backup. 13

14 Naming Conventions Used in This Guide Naming Conventions Used in This Guide 1 Table 1 on page 14 lists special terms that are used in this guide. Table 1. Naming Conventions Used in This Guide Term BRTools NSR-R/3 software <ORACLE_SID> restore and recover Description or Usage SAP R/3 backup utilities, specifically the brbackup, brrestore, brrecover, and brarchive programs. The shortened form, used throughout this guide, for the complete name, NetWorker Module for SAP R/3 with Oracle, release 3.0 software. The name of the Oracle database instance that you want to back up, usually the argument for the -u option of brbackup or brarchive. This guide follows Oracle terminology, which distinguishes between restoring and recovering a database. Restore means to retrieve individual datafiles from backup media and store the files on disk. Recover means to apply the redo log to make the database consistent. This usage is unlike NetWorker terminology, which uses recover for all data retrieval activities (as distinguished from the restore command). Basic Network Configuration This section describes a network configuration for regular backup and recovery services when using the NSR-R/3 software. Note: For information on snapshot backup and restore with PowerSnap, see "Chapter 8: PowerSnap Backups and Restores" on page 85 A basic backup and recovery network can be configured as follows: The NetWorker storage management server has NetWorker server software installed. A backup storage device is either attached to the NetWorker server or on a separate NetWorker storage node server. 14

15 Chapter 1: Introduction Each database server has NetWorker client software, NetWorker Module software, SAP software, and Oracle database software installed. Each Networker client, including each database server, has Networker client software installed. Figure 1 on page 15 shows a sample configuration with the NetWorker server software and the database server software on separate computers. Figure 1. NetWorker Server and the Database Server on Separate Systems 1 NetWorker Server Database Server SAP R/3 Server Oracle database NetWorker Module NetWorker Client UNIX Client without database UNIX NetWorker Client Summary of Features This section describes the features of the related NetWorker server and client software, NSR-R/3 software, SAP R/3 software, and optional Oracle RMAN software that work together to provide storage management services. For a summary of software components, see "Summary of Components and Settings" on page

16 NetWorker Server Software Features NetWorker Server Software Features 1 The NetWorker software provides data storage management services that protect and help manage data across an entire network. The main NetWorker server software features that work in conjunction with the NetWorker Module software include: Save group, pool, and client configuration Backup scheduling Authorization Online index maintenance (client file index and media database) NSR-R/3 Software Features The NSR-R/3 software is an add-on module for NetWorker client software that provides a backup and restore interface between the SAP BRTools program and the NetWorker server. The main component of NSR-R/3 is the backint program, which provides backup, inquiry, and restore processes for all Oracle and SAP R/3 files. The NSR-R/3 software enables you to perform the following operations for SAP R/3 data on Oracle databases: Manual backups Scheduled backups Inquiry of backed up data Restores of backed up data Automated media management Snapshot backup and recovery Sapclone New or Enhanced Features NSR-R/3 provides several new or enhanced features that are described in the following sections. Improved Administrator s Security The requirement to add the SAP database administrator's user ID and host name to the NetWorker server's Administrator's list was removed. 16

17 Chapter 1: Introduction Expiration Parameter Replaces Browse and Retention Policy Settings For all backups, the expiration parameter, which is configured in the NSR-R/3 configuration file, init<oracle_sid>.utl, sets both the browse and retention periods for the stored data. Note: If using NetWorker version 7.x, the behavior of the expiration parameter is different than it is for NetWorker version 6.x. For NetWorker 7.x, this parameter overrides the NetWorker server-side Client resource settings. For NetWorker 6.x this parameter does not override the NetWorker server-side Client resource settings unless it specifies a longer period of time. 1 Added Support for SAP BRRECOVER Support has been added for BRRECOVER functionality, included in SAP BRTools version SAP documentation states the following recommendation concerning BRRECOVER: We strongly recommend you to use BRRECOVER functions rather than the equivalent SAPDBA ones. The reason is that we will in future no longer develop the SAPDBA functions, whereas BRRECOVER functions will always be fully up-to-date. Note: If up-front errors are encountered while using BRRECOVER in disaster recovery mode, check the backint logs. You may be instructed to set the following operating system environment variable at your shell/command prompt and then retry BRRECOVER, for example using the Bourne shell: NSR_SAP_BRRECOVER=yes export NSR_SAP_BRRECOVER Improved Manageability and Performance of Backups and Restores New parameters simplify backup configuration and improve backup and restore performance. The ss_group_by_fs parameter allows more efficient grouping of files into save sets by file system instead of by file size. Setting this parameter to yes potentially improves performance of backups, index lookups, and restore times. 17

18 NSR-R/3 Software Features 1 The ss_size_max parameter lets you limit the maximum save set size. This has the effect of breaking up many large files that reside on the same file system into multiple save sets, which thereby potentially improves backup and restore manageability and performance. The device_server parameter lets you define the device server to use during backup, improving therefore the backup manageability. If not defined, the NetWorker server will determine it according to the client ressource definition. New operating system environment variables allow automatic internal retries of a restore when there is a heavy NetWorker server load: NSR_SAP_RESTORE_RETRY_COUNT NSR_SAP_RESTORE_RETRY_DELAY_SECS For more details see Table 18 on page 70. Improved Logging and Placement of Log/Temporary Files New parameters have been added to allow more streamlined, organized, and flexible placement of logs and temporary files, and log file names are now more user-friendly. The backint_log parameter specifies the full pathname of the backint log file for running the brbackup and brrestore commands. You can modify this parameter before running restores, or you can specify this parameter in a customized init<oracle_sid>_restore.utl file, which can be referenced from the util_par_file parameter in your init<oracle_sid>_restore.sap file, for example: brrestore -p init<oracle_sid>_restore.sap The arch_backint_log parameter specifies the full pathname of the log file for running the brarchive command. The backint_tmpdir parameter specifies the directory of the backint temporary files. The max_logs parameter specifies the maximum number of backint session logs to be saved in the backint_log file. More Flexible Query and Restore A new parameter provides more flexible query processing and restores. The prev_bk_restore parameter allows you to automatically restore the previous earlier version of a file if the specified version does not exist. The default condition is to not allow this. 18

19 Chapter 1: Introduction More Flexible Backup and Restore User Selection New operating system environment variables have been introduced to specify the user and group to run the BRTools NSR_SAP_ADMIN_USER NSR_SAP_ADMIN_GROUP For more details see Table 18 on page New Data Compression Algorithms The compress_type parameter specifies the directive to use while compressing the data. You may define here the new options of the compressasm directive to determine the compress algorithm. BRTools Software Features Backup, restore, and inquiry of SAP R/3 databases on Oracle is provided through the following SAP R/3 features: BRTools (comprised of the brbackup, brrestore, brarchive, and other utilities). SAP database administration (SAPDBA) utility, a menu-driven interface to BRTools. Invoking the brbackup command directly or from the SAPDBA Backup Database screen passes the following data to backint for backup: Oracle datafiles Control files Any existing profiles or specified files SAP internal catalogs for backup sessions Invoking the brarchive command directly or from the SAPDBA Backup Archive Logs screen passes the offline redo logs to backint for backup. Oracle RMAN Software Features The NSR-R/3 software supports the use of Oracle s Recovery Manager (RMAN) backup and restore utility, which is available with Oracle8 or later databases. Use of RMAN with NSR-R/3 is optional, and you can continue to use NSR-R/3 s backint program as the sole backup and restore tool. If you 19

20 NetWorker PowerSnap Features 1 want to use RMAN to back up Oracle databases, you must still use backint to back up SAP R/3 configuration files, logs, and other files. For a description of RMAN features, refer to Oracle documentation. NetWorker PowerSnap Features NetWorker backups use the PowerSnap functionality to create a snapshot (point-in-time copy) of a group of files or filesystems that belong to a client. The snapshot serves as an instant backup, which can then optionally be backed up immediately to a traditional storage medium, such as tape. Many instant backups can be performed in a single day, thus reducing the exposure to data loss. Instant backups protect only against logical failures. To protect against physical failures, the snapshot must be backed up to a traditional storage medium. Whether or not a backup uses the PowerSnap features is determined by Client, Group, and Policy resource configurations. To use the PowerSnap features, NSR-R/3 must be used with the NetWorker PowerSnap Module. The PowerSnap Module creates the snapshots, and NSR-R/3 stores the snapshot data. Note: PowerSnap release 1.0 modules support scheduled backups only. Manual (client-initiated) backups are not supported. Types of PowerSnap Backups Supported NSR-R/3, with the appropriate PowerSnap Module, supports the following types of snapshot-backups: Instant backup, which creates a permanent PIT copy (snapshot) of SAP R/3 with Oracle data. This copy is then stored on the primary storage system where it is available to NSR-R/3 for performing instant restores or rollbacks. Instant backups can be scheduled to occur many times in a single day, with little impact to the SAP R/3 with Oracle Server or network. Immediate live backup (also known as "serverless snapshot backup" or "snapshot-based backup"), which creates a temporary snapshot that is immediately backed up to secondary storage such as tape. The snapshot is then automatically deleted from the primary storage (and is not available for performing instant restores or rollbacks). 20

21 Chapter 1: Introduction Deferred live backup, which creates a permanent snapshot on the primary storage system by an instant backup, and backs up the snapshot to secondary storage, such as tape. The permanent snapshot is retained on the primary storage (and is available for performing instant restores or rollbacks) for a specified period. 1 Types of PowerSnap Restores Supported NSR-R/3, with the appropriate PowerSnap Module, supports the following types of snapshot-based restores: Instant restore, which is the process of mounting a snapshot that was created by an instant backup. This enables the snapshot s saved data to be retrieved. A minimal amount of time is required for this type of restore. Rollback, which restores the entire snapshot to the source location by using the hardware s particular capabilities. Relocation during rollbacks is not currently supported by PowerSnap. To determine if a rollback is supported on a specific type of hardware, refer to the appropriate NetWorker PowerSnap Module Installation and. Restore from secondary storage, which is the process of restoring from a snapshot that was saved to the secondary storage system. The PowerSnap Module software effectively uses the NetWorker recover program, to retrieve the data. Summary of Components and Settings This section summarizes the user-configurable components and basic settings of the various products used with NSR-R/3, and how they work with their associated binary executable files to provide storage management services. These components are described in the following topics: "NetWorker Server Components" on page 22 "NSR-R/3 Components" on page 22 "NetWorker Client Settings" on page 23 "SAP Components" on page 23 "Oracle Components" on page 24 "PowerSnap Components" on page 24 21

22 NetWorker Server Components NetWorker Server Components 1 The NetWorker Administrator program is a graphical user interface. This NetWorker Server component is used to configure NetWorker resources, such as Client, Group, and Pool. For details, refer to the Fujitsu Siemens Computers NetWorker NSR-R/3 Components Table 2 on page 22 lists the NSR-R/3 components. Table 2. NSR-R/3 Components Component Type Description backint init.utl backint* nsrsapsv* NSRSAP* nsrsapsv nsrsapsv.cfg sapclone Binary executable Configuration file log files Binary executable Configuration file Binary executable This backup, restore, and inquiry program provides an interface to SAP BRTools. It uses configurations from the init<oracle_sid>.utl file. This is the sample configuration file for the backint program and is to be used as a template. Its location is /opt/nsr/nsr_r3. Copy this file and name it init<oracle_sid>.utl, where <ORACLE_SID> is the name of the Oracle database instance that is to be backed up. Use the copy and save the original. Log files used for the NSR-R/3 software. The default location by operating system is as follows: /nsr/applogs The scheduled backup program, which invokes the appropriate BRTools executables. It uses configurations from the renamed copy of the nsrsapsv.cfg template file. Specify this file as the backup command in the NetWorker Client resource. The sample configuration file for the nsrsapsv program. Its location is /opt/nsr/nsr_r3. Copy the sample template file and save the original. The save set cloning program. Provides an interface to the NetWorker nsrclone program. 22

23 Chapter 1: Introduction NetWorker Client Settings Table 3 on page 23 lists the main NetWorker Client resource attributes used with the NSR-R/3 software. For a complete description of NetWorker Client resource attributes, refer to the Fujitsu Siemens Computers NetWorker. 1 Table 3. NetWorker Client Resource Settings Used by the NSR-R/3 Software Attribute Backup command Save Set Description Specifies the command used for scheduled backups, including parameters and configuration file. For example: nsrsapsv -f /nsr/res/nsrsapsv.cfg Normally specified as backint:<oracle_sid>. For PowerSnap usage, this attribute must be specified. For all other usage, this attribute is only informational, because the nsrsapsv.cfg file determines the ORACLE_SID parameter. SAP Components Table 4 on page 23 lists the SAP software components used with the NSR-R/3 software. Table 4. SAP Components Used by the NSR-R/3 Software Component Type Description BRTools SAPDBA init<oracle_sid>.sap Binary executables Binary executable Configuration file SAP R/3 backup utilities, specifically the brbackup, brrestore, and brarchive programs (equivalent to NetWorker client save, recover, nsrinfo, and mminfo programs). Invoked by nsrsapsv, SAPDBA, or command line. As of SAP version 6.20 brrecover is also part of BRTools. Menu-driven interface to BRTools for backup, restore, and inquiry-related operations. The SAP configuration file. Relevant parameters specify whether to use the backint program or RMAN for backup, inquire, and restore sessions. 23

24 Oracle Components Oracle Components 1 Table 5 on page 24 lists the Oracle software components used with the NSR-R/3 software. Table 5. Oracle Components Used by the NSR-R/3 Software Component Type Description RMAN Binary executable Oracle utility for performing backups and restores of the Oracle database, using the rman_parms parameter. To enable RMAN, set the backup_dev_type parameter in the init<oracle_sid>.sap file to rman_utl. rman_parms Parameter Optional parameter in the init<oracle_sid>.sap file. Used to specify environment variables for an RMAN backup or restore with NSR-R/3. PowerSnap Components The NetWorker Module software components that are used specifically to enable and configure PowerSnap features are listed in Table 6 on page 24. Table 6. PowerSnap Components Used by the NSR-R/3 Software Component Type Description init.utl nsrsapps.cfg (example name) Configuration File Configuration File The init<oracle_sid>.utl configuration file for the backint program. The parameters within this file that are specific to PowerSnap are those with the ps_ prefix. User-defined PowerSnap configuration file, in which the PowerSnap parameters are set. ps_opaque_pfilename Parameter Parameter in the init<oracle_sid>.utl file that specifies the complete file pathname for the user-defined PowerSnap configuration file, for example /nsr/res/nsrsapps.cfg 24

25 Chapter 1: Introduction Summary of Processes The NSR-R/3 software provides storage management services that connect NetWorker functionality to SAP R/3 servers running Oracle databases. The backup and restore processes can be initiated from the following interfaces: 1 SAPDBA menu-driven interface BRTools: brbackup, brarchive, brrestore, or brrecover commands NSR-R/3 s nsrsapsv command, used for scheduled backups Additionally, Oracle s RMAN can be invoked through these interfaces to back up and restore Oracle databases. Note: PowerSnap backups must be initiated through the nsrsapsv scheduled backup program, and are not supported for manual backups. Backup with SAPDBA or brbackup When a backup is initiated from SAPDBA or the brbackup program on the SAP R/3 server running Oracle, brbackup sends a request to the backint program. The backint program runs two or more times, as required, to back up the requested Oracle datafiles, control files, online redo logs, and profiles. It sends all the data and process information in parallel streams to the NetWorker server. The data stream is backed up on storage media or a NetWorker storage node, and NetWorker software creates entries in the client file index and media database. The final results of the backup are recorded in a log file, backint<oracle_sid>.log, on the SAP R/3 server running Oracle. Figure 2 on page 26 shows how the NetWorker services, processes, and programs interact during a backup. 25

26 Backup with RMAN Figure 2. NetWorker and Database Interaction during a Backup 1 NetWorker Client NetWorker Server Storage SAP R/3 on Oracle Server Client File Media Medium Index Database brbackup (SAPDBA) backint backint (save) nsrindexd nsrmmdbd nsrmmd data nsrd inter-process communication Backup with RMAN When the Oracle RMAN utility (available with Oracle8 or later) is used to back up an Oracle database, the process is similar to backup that uses SAPDBA, except brbackup sends requests to both RMAN and backint. The following occurs as a result: 1. RMAN backs up the Oracle datafiles. 2. The backint backs up the configuration files, logs, and other flat files that are specific to SAP. 26

27 Chapter 1: Introduction Restore with SAPDBA or brrestore When a restore is initiated from SAPDBA or the brrestore program on the SAP R/3 server running Oracle, brrestore sends a restore request to the backint program. The backint program browses the NetWorker server s client file index and restores the specified files in a parallel stream from the NetWorker server to the SAP R/3 server running Oracle. Figure 3 on page 27 shows how NetWorker services, processes, and programs interact during a restore. Figure 3. NetWorker and Database Interaction during a Restore 1 NetWorker Client NetWorker Server Storage SAP R/3 on Oracle Server Client File Media Medium Index Database brrestore (SAPDBA) backint nsrindexd nsrmmdbd nsrmmd data backint (recover) nsrd inter-process communication Restore with RMAN If RMAN is used to restore the Oracle database, RMAN restores the Oracle database datafiles only. If you also want to restore the configuration files, logs, and other flat files that are specific to SAP R/3, you must manually restore them by using any of the following: The backint program The NetWorker recover program 27

28 Related Documentation BRTools with appropriate command line parameters. 1 Related Documentation For further information on the NSR-R/3 software, refer to the following related documentation: NetWorker PowerSnap Module Installation and appropriate for your primary storage system NetWorker V7.1 (UNIX) Online man pages (for NetWorker commands) NetWorker Command Reference Guide 28

29 Chapter 2: Basic Software Configuration This chapter provides basic configuration instructions for NSR-R/3 and other supporting software required for backup, recovery, and inquiry of SAP R/3 with Oracle data and other files. Unless otherwise noted, the configurations described in this chapter apply to both manual and scheduled backups. This chapter describes the following tasks that need to be performed, although not necessarily in this order: "Task 1: Configure the Environment" on page 30 "Task 2: Configure the NetWorker Resources" on page 31 "Task 3: Configure the NSR-R/3 Parameters" on page 33 "Task 4: Configure the Backup and Restore Utility" on page 42 "Task 5: Configure a Backup of Cluster Data" on page 46 More specific configurations are covered in later chapters: "Chapter 4: Manual Backups" on page 57 "Chapter 5: Scheduled Backups" on page 65 "Chapter 6: Cloning Save Sets" on page 75 "Chapter 7: Restoring Data" on page 79 "Chapter 8: PowerSnap Backups and Restores" on page 85 29

30 Task 1: Configure the Environment Task 1: Configure the Environment Use the following steps to configure the environment for the NSR-R/3 software: 1. Install and enable NSR-R/3 on each Oracle database server with SAP R/3 that requires backup and recovery services. For instructions, refer to "Chapter 3: Installation" on page Set the PATH environment variable for the Oracle user to point to the location of the NetWorker client executables, which is typically /opt/nsr. 3. Ensure the backint executable binary file is in the same directory as BRTools. Usually you only have to make a symbolic link to /opt/nsr/backint. Set the owner of backint to root. 4. If you need to restore to raw device files, set the uid bit on for the backint program by entering the following command: chmod 4755 backint 5. For NetWorker 7.x, ensure that the SAP backup user is listed in the User Groups, and has the following privileges: Monitor NetWorker processes Back up local data Recover local data To verify these settings, run NetWorker Administrator (nwadmin) on the server and select User Groups from the Customize menu. 30

31 Chapter 2: Basic Software Configuration Task 2: Configure the NetWorker Resources The NetWorker resources reside on the NetWorker server and are configured using the NetWorker Administrator program. Table 7 provides resource configuration details that are specific to the NSR-R/3 software. Resource Client Group Pool Schedule Table 7. NetWorker Resources (Part 1 of 2) Comments Specifies the NetWorker Client resources for each SAP R/3 server running Oracle that requires backup, restore, and inquiry operations. Browse and Retention settings in the Client resource are ignored. Instead, a value must be set in the "expiration" parameter in NSR-R/3 s parameter file, init<oracle_sid>.utl. See the listing for "expiration" on page 36. For details on setting the Save Set and Backup Command attributes, which are specific for scheduled backups, see Table 17 on page 66. Specifies a set of clients to start backing up data at a specified time. Note: The group name must be the same as defined in NSR-R/3 s parameter file, init<oracle_sid>.utl, see the listing for "group" on page 36. Specifies the medium volumes in each pool to receive specific backup data. When configuring the Pool resource, complete the following: Leave the Save Sets attribute blank; the NSR-R/3 program sets this attribute during each backup session. Once a pool is created, specify its name in NSR-R/3 s parameter file, init<oracle_sid>.utl. Specifies the days of the week or month when scheduled backups runs. 2 31

32 Task 2: Configure the NetWorker Resources Table 7. NetWorker Resources (Part 2 of 2) 2 Resource Server Device Comments Defines the NetWorker server to be used for backup, restore, and inquiry operations. When configuring the Server resource, check for the following: Ensure that the Parallelism attribute is equal to or greater than the number of save streams being sent to the NetWorker server by the Oracle server or cluster client. The value should match or be greater than the parallelism setting found in NSR-R/3 s parameter file, init<oracle_sid>.utl, see "parallelism" on page 38. When performing manual backups, ensure the Manual Saves attribute is set to Enabled. It is not necessary to specify the SAP backup user in the Administrator attribute. Specifies the NetWorker storage device used for backup the data. Ensure that a Device resource is configured for each storage device used for backup and restore operations. Each device must contain a labeled and mounted volume. For more information on configuring the NetWorker resources, refer to the NetWorker Online Help or the NetWorker. 32

33 Chapter 2: Basic Software Configuration Task 3: Configure the NSR-R/3 Parameters During backup, restore, or inquire sessions, the NSR-R/3 program uses the parameter settings specified (or the default values if not specified) from the init<oracle_sid>.utl parameter file. These parameter settings provide client, server, pool, group, expiration and other values to the backint program. Important: The names for the server, group, client, and pool specified in the parameter file must match the corresponding resource settings defined on the NetWorker server. An error results if there is a mismatch. 2 To set a parameter in the init<oracle_sid>.utl parameter file, use the following format: parameter=value Refer to the following rules when setting parameters: Uncomment and modify as necessary all parameters to be used in backup, restore, or inquire operations. Use lowercase parameter names and values. For descriptions and default values for NSR-R/3 parameters, see Table 8 on page

34 Task 3: Configure the NSR-R/3 Parameters For specific instructions on configuring data clusters, see "Task 5: Configure a Backup of Cluster Data" on page 46. Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 1 of 8) Parameter Default Description 2 arch_backint_log See Description Specifies the full pathname of the log file for running the brarchive command. Default location: /nsr/applogs/arch_backint<oracle_sid>.log backint_log See Description Specifies the full pathname of the backint log file for running the brbackup, brrestore or brrecover commands. Default location: /nsr/applogs/backint<oracle_sid>.log Note: To specify a separate log file to use specifically for restores, modify this parameter before running brrestore. Alternatively, the "backint_log" parameter can be specified in an init<oracle_sid>_restore.utl file, which can be referenced from the "util_par_file" parameter in the init<oracle_sid>_restore.sap file, for example: brrestore -p init<oracle_sid>_restore.sap backint_tmpdir /nsr/applogs Specifies the directory name of the backint temporary files. client Local host Specifies the NetWorker client hostname to use for the client file index for the current backup. If you are using NSR-R/3 to back up a virtual cluster client, set this value to the virtual node name. During cluster restores, this parameter specifies the name of the client with the client file index for the backup to be restored. For example, to restore data to a host named saturn using the backup from a host named mars, set this parameter to mars so that the client file indexes for mars are used. 34

35 Chapter 2: Basic Software Configuration Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 2 of 8) Parameter Default Description compress No Compresses data during a backup before the data is passed over the network or written to tape, which can speed up the backup process. If set to Yes, you can choose the compression algorithm by providing the corresponding directive in the "compress_type" parameter below. Compression increases CPU usage on the SAP R/3 server running Oracle, but reduces the amount of data sent to the NetWorker server. 2 compress_type compressasm Determines the directive to use while compressing the data. You can specify any valid option for the ASM to determine the algorithm to be used during the compression (e.g. compressasm -gzip -level 9). The "compress_type" parameter is ignored if the "compress" parameter is set to No. Valid Values: compressasm or compressasm -bzip2 [-<level>] or compressasm -gzip [-<level>] The value for <level> depends on the specific compress algorithm: bzip2: (default: 0) gzip: 0-9 (default: 6) device_server Not specified Defines the Storage Node to use during backup. If not specified, the NetWorker Server will determine it according to the "Storage Node" attribute in the client resource. This parameter will be passed to any save command initiated by backint as parameter for option -J. Valid Values: Name of the NetWorker Server or any NetWorker Storage Node 35

36 Task 3: Configure the NSR-R/3 Parameters Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 3 of 8) Parameter Default Description 2 expiration 2 Weeks For all backups, the "expiration" parameter sets both the browse and retention periods. For NetWorker 7.x, this parameter overrides the NetWorker server-side Client resource settings. For NetWorker 6.x this parameter does not override the NetWorker server-side Client resource settings unless it specifies a longer period of time. The value must use nsr_getdate format, for example: expiration = 2 Weeks files_per_save 10 Determines the maximum number of files to be included in a saveset.it should be set to prevent the creation of single save sessions in case of small files. If not set, or set to zero, then the allowed number of files in a saveset is unrestricted. Valid Values: > 1 integer (limited by the command buffer size) The "files_per_save" parameter is ignored if the "ss_group_by_fs" parameter is set to Yes. group Default Specifies the backup Group resource that is used by the NetWorker save program. If not specified, the Default group is used. To assign a value, set the parameter, for example: group = SAPBackup Note: The group name must match the corresponding group attribute in the NetWorker Client resource, see "Group" on page 31. level_full Yes Specifies that a full backup is always performed. For SAP data, do not change this setting from Yes. 36

37 Chapter 2: Basic Software Configuration Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 4 of 8) Parameter Default Description max_logs 0 Specifies the maximum number of backint session logs to be saved in the backint log file. If the value is set to 0, all backup logs will be saved in the log file. See also the "backint_log" parameter on page 34. notify_done Not specified Executed at the completion of a backup or restore session. Uncomment the option and replace mailx with the name of the command line utility to be used as an alert when the backint program has completed its activity, for example: notify_done = mailx -s backint done root 2 notify_error Not specified Executed at the completion of a failed backup or restore session. Uncomment the option and replace mailx with the name of the command line utility to be used as an alert if the backint program encounters any errors during its activity, for example: notify_error = mailx -s backint error root notify_start Not specified Executed at the beginning of a backup or restore session. Uncomment the option and replace mailx with the name of the command line utility to be used as an alert when the backint program begins its activity, for example: notify_start = mailx -s backint start root 37

38 Task 3: Configure the NSR-R/3 Parameters Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 5 of 8) Parameter Default Description 2 notify_success Not specified Executed at the completion of a successful backup or restore session. Uncomment the option and replace mailx with the name of the command line utility to be used as an alert when the backint program has successfully completed its activity, for example: notify_success = mailx -s backint success root parallelism 8 Specifies the number of save sets or save streams to send simultaneously to the NetWorker server. Typically, this setting should be equal to the sum of the "target sessions" for all of the devices dedicated to NSR-R/3. Ensure that the NetWorker server is configured to support this parallelism value or greater, see the listing for "Server" on page 32. Note: The Parallelism value will be reduced if it is greater than the value of the "savesets" parameter, provided the "ss_group_by_fs" parameter is set to No or not set. 38

39 Chapter 2: Basic Software Configuration Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 6 of 8) Parameter Default Description pool Default Specifies the NetWorker media Pool resource, (defined in the NetWorker server), that receives backup data from the SAP R/3 server that is running Oracle. If not specified, the Default pool is used. To use a pool other than the Default, uncomment this parameter and set it equal to the name of the pool, for example: pool = SAPData To use multiple pools to separate data: 1. Create separate init<oracle_sid>.utl parameter files. 2. Use the -r option to specify the parameter "filename" to use at the command line when using brbackup or brarchive. For example, a pool named ARCHData is used specifically for archive logs. You can create a separate parameter file for archive logs, named for example archivec11.utl, and set the pool attribute equal to ARCHData. To use this pool to back up the archive logs, you would enter the following command at the command line: brarchive -u sys/admin -d util_file -r archivec11.utl -m all -s save 2 prev_bk_restore No Specifies whether to restore the previous backup if the required backup cannot be found, when the "query_index" parameter is set to No. query_index No Specifies whether to query the NetWorker server indexes for validation of the requested files and backup IDs before a restore begins. If set to No, the query does not occur. 39

40 Task 3: Configure the NSR-R/3 Parameters Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 7 of 8) Parameter Default Description 2 raw_dir Not specified Specifies the directory for raw disk partitions. Any files below these directories are considered to be raw disk partitions. Do not set the /dev or /devices directories for raw partitions. They are already treated as raw devices. To specify the directory, uncomment this option, and use a semicolon (;) to separate the directory paths, for example: raw_dir = /oracle/data;/sap/data retry_count 0 Specifies the number of times that a retry of a failed backup is attempted for each save set. Any integer greater than 0 is allowed. savesets 20 To distribute the backup load, a client s files can be divided among several save sets, as specified by this value. If the value is equal to or greater than the number of database files, then a separate save set is made for each file. If the value is smaller than the number of database files, then a save set may contain more than one file, according to the parameter "files_per_save". This value is ignored if the "ss_group_by_fs" parameter is set to Yes. sem_timeout 30 Sets the amount of time, in minutes, that backint waits for brbackup or brconnect to remove the semaphore file. If the semaphore file is not deleted, backint exits with an error at the end of this timeout period. server Local Host The hostname of the NetWorker server that NSR-R/3 uses for backup, restore, and inquiry sessions, for example: server = jupiter Note: The server name must match the server attribute specified in the NetWorker Server resource. If the "server" parameter is not specified, then NSR-R/3 backs up data to the local host. 40

41 Chapter 2: Basic Software Configuration Table 8. Parameters for the NSR-R/3 init<oracle_sid>.utl File (Part 8 of 8) Parameter Default Description ss_group_by_fs No If set to Yes, the "savesets" and "files_per_save" parameters are ignored and save sets are grouped by filesystem instead of file size. This more efficient grouping of files can improve performance of scheduled backups, index lookups, and restore times. 2 ss_size_max 0 Specifies maximum save set size in megabytes. If not set, or set to zero, then size is unrestricted. ssnameformat Old Sets the naming convention for save sets without PowerSnap. If set to Old, then the name for all save sets is backint:<oracle_sid>. If set to New, then the save set name for each session differs according to the files being backed up. It uses the format backint:<oracle_sid>:<full path of the first filename in the save set>. If you set each save set to store one file, then a value of New simplifies the process of browsing the media database. The media database will shows each filename as part of the save set name. Note: If set to New, the NetWorker recover -S command cannot be used to restore the database, however the brrestore command can be used. Note: For PowerSnap savesets the saveset name will be always generated as backint:<oracle_sid>:ps:. verbose No Provides more detailed information in the log file from save and recover operations. 41

42 Task 4: Configure the Backup and Restore Utility Task 4: Configure the Backup and Restore Utility Depending on your configuration needs and preferences, you can perform backups, restores, and inquiries of SAP R/3 data using the SAP BRTools with or without use of Oracle s RMAN utility. The following examples describe a simple configuration of each of the cases of use with NSR-R/3. 2 For the SAP BRTools, see "Example: Configuring backint as the Backup and Restore Utility" on page 44. For the Oracle RMAN utility, see "Example: Configuring RMAN as the Backup and Restore Utility" on page 44. You will have to set the "backup_dev_type" parameter accordingly to the description on Table 9 on page 43, to be able to use NSR-R/3 as your Backup and Restore Utility. 42

43 Chapter 2: Basic Software Configuration Table 9. SAP parameters for the use of NSR-R/3 backup_dev_type = backup_type = online backup_type = offline util_file The database will be brought online, all tablespaces to be backed up will be set in backup mode and in addition the list of files will be provided to backint for the needed operation. After completion of all tablespaces, the backup mode will be ended. The database will be brought offline and in addition the list of files will be provided to backint for the needed operation. 2 util_file_online The database will be brought online, the list of files will be provided to backint for the needed operation and with use of semaphore files, each tablespace will be set in backup mode as soon as their files turn arrives. After completion of each tablespace, its backup mode will be ended. This combination is accepted as of SAP The database will be brought offline, the list of files will be provided to backint for the needed operation. The semaphore files generated by backint are non-relevant for the operation. rman_util Only the database files will be backed up online using the RMAN-Utility provided by Oracle. The additional SAP files will be still backed up with backint. Only the database files will be backed up offline using the RMAN-Utility provided by Oracle. The additional SAP files will be still backed up with backint. You may use command line options to override these parameters from your init@.sap: -t [online offline] will override the backup_type parameter -d [util_file util_file_online rman_util] will override the backup_dev_type parameter 43

44 Task 4: Configure the Backup and Restore Utility Example: Configuring backint as the Backup and Restore Utility 2 The following example describes a simple configuration of BRTools (specifically the SAPDBA interface and the brbackup, brarchive, brrestore, and brrecover commands) to use the backint program for backup, restore, and inquiry operations. For complete instructions, refer to the appropriate SAP documentation. 1. With a text editor, open the SAP initialization file, init<oracle_sid>.sap, which is typically located in the directory $ORACLE_HOME/dbs 2. Set the backup_dev_type parameter to use the backint program by entering one of the following: # backup device type backup_dev_type = util_file backup_dev_type = util_file_online 3. Set the util_par_file parameter to point to the NSR-R/3 s parameter file, init<oracle_sid>.utl, as follows: # backup utility parameter file util_par_file =?/dbs/init<oracle_sid>.utl where? = $ORACLE_HOME For details on the NSR-R/3 parameter file, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. Example: Configuring RMAN as the Backup and Restore Utility The following example describes a simple configuration of Oracle s RMAN utility (available with Oracle8 or later databases), which works with the BRTools utilities, for backup, restore, and inquiry operations. For complete instructions, refer to the appropriate SAP documentation. 1. With a text editor, open the SAP initialization file, init<oracle_sid>.sap, which is typically located in the directory $ORACLE_HOME/dbs 2. Set the backup_dev_type parameter to use the RMAN utility by entering the following: # backup device type 44

45 Chapter 2: Basic Software Configuration backup_dev_type = rman_util 3. Uncomment the line for the rman_parms parameter and set it to include each NetWorker software-specific (NSR_*) environment variable that is appropriate for your backup, restore, and inquiry sessions. For a list of these environment variables, see Table 29 on page 130. The environment variable names must be uppercase and use the following syntax: rman_parms="env=(<var1>=<value>, <var2>=<value>,...)" For example: rman_parms="env=(nsr_server=server_name, NSR_DATA_VOLUME_POOL=pool_name)" 2 45

46 Task 5: Configure a Backup of Cluster Data Task 5: Configure a Backup of Cluster Data Note: If you are not using a cluster configuration, ignore this task. NSR-R/3 backs up all Oracle data residing on private disks in a cluster, or only shared Oracle data residing on a virtual client in a cluster. To configure a backup of cluster data on SAP R/3 with Oracle systems: 2 1. Ensure that NSR-R/3 is installed on both physical nodes of the cluster, but only on the private disks of the nodes. For details on installing NSR-R/3, refer to "Chapter 3: Installation" on page Ensure that a NetWorker Client resource is created for each physical node and for the virtual node. 3. Configure the NSR-R/3 parameter file (init<oracle_sid>.utl) with the appropriate client parameter setting for the type of backup you want: To back up Oracle data located on a private disk, use the physical node name as the client name. To back up Oracle data located on a shared disk that belongs to a virtual system, use the network name associated with the virtual system as the client name. For details on NSR-R/3 s client parameter settings, see "client" on page

47 Chapter 3: Installation This chapter describes how to install, enable, and uninstall NSR-R/3 on a supported operating system. This chapter includes the following main sections: "Installation Requirements" on page 47 "Supported Operating Systems" on page 48 "Software Requirements" on page 48 "Files Installed" on page 49 "Upgrading from Release 2.x of NSR-R/3" on page 49 "Install Procedures" on page 50 "Installing Licenses" on page 53 "Managing Your Fujitsu Siemens Computers Licenses" on page 54 "Uninstall Procedures" on page 54 Installation Requirements This section discusses the requirements necessary for installing the NSR-R/3 software. 47

48 Supported Operating Systems Supported Operating Systems Table 10 on page 48 lists the operating systems on which this release of the NSR-R/3 software operates. Versions in bold text have been added in this release. Table 10. Supported Operating Systems Operating System Supported versions Red Hat Linux Advanced Server 2.1, Enterprise Edition 3 SuSE SLES7, SLES8 3 Sun Solaris 7, 8, 9 For the latest NetWorker software compatibility information, refer to the Release Notes. For details on patches required for a particular system, refer to the Support section of the Fujitsu Siemens Computers web site. Software Requirements Table 11 on page 48 lists the software that may be used to properly configure this release of the NSR-R/3 software. Support for software and versions in bold text have been added in this release. Table 11. Supported Software Software Supported Versions Comments BRTools 4.0B to 6.10B, 6.20 Required for all operating sytems newly supported by NSR-R/3, release 3.0. NetWorker client software 7.1 or later 48

49 Chapter 3: Installation Table 11. Supported Software Software Supported Versions Comments NetWorker server software NetWorker PowerSnap Module 7.1 or later 1.0 Required for serverless backup and snapshot management on Solaris; supports concurrent multiple PowerSnap modules to enable parallel backup and recovery services. For the latest NetWorker software compatibility information, refer to the Release Notes. 3 Files Installed The following files are installed with the NSR-R/3 software: backint Backup, restore, and inquire program sapclone Save set cloning program nsrsapsv Scheduled backup program init.utl Example parameter file that specifies the variables backint uses nsrsapsv.cfg Example configuration file for the nsrsapsv program Upgrading from Release 2.x of NSR-R/3 Note: If removing the NSR-R/3 software from a cluster, you must perform this procedure on each cluster node. To upgrade from release 2.x of NSR-R/3: 1. Verify that no SAP R/3 with Oracle database backups or restores are currently running on the SAP R/3 Server host. 2. Log in as root. # su root 49

50 Install Procedures 3. If uninstalling on an Oracle system earlier than Oracle 9i, shut down all Oracle instances that use this ORACLE_HOME. If uninstalling on a system using Oracle 9i or later, this step is not required. 4. Enter the appropriate command for your operating system. Table 14 on page 54 lists the uninstall commands by operating system. 5. Install and enable the license for release 3.0 of NSR-R/3 on the SAP R/3 Server host, see "Install Procedures" on page 50. Install Procedures 3 This section describes how to install NSR-R/3 on a supported operating system. Installing the NSR-R/3 Software To install the NSR-R/3 software, complete the following tasks: "Task 1: Access the Installation Files" on page 50 "Task 2: Install the NSR-R/3 Software" on page 51 Task 1: Access the Installation Files Access NSR-R/3 files from any of these sources: "From a Local CD-ROM" on page 50 "From the Fujitsu Siemens Computers Web Site" on page 51 From a Local CD-ROM To access the NSR-R/3 installation software from a local CD-ROM drive: 1. Log on as root on the server running SAP R/3 with the Oracle database. 2. Insert and mount the NSR-R/3 CD-ROM in the CD-ROM drive: # mount /dev/cd_drivename /mount_point 50

51 Chapter 3: Installation 3. Go to the correct directory on the CD-ROM, as described in Table 12 on page 51. Table 12. Accessing the Correct Directory on the Local CD-ROM On this system: Linux Solaris Enter the following command: # cd /mount_point/rpms # cd /mount_point/products/nsr-r3_<version>/sparc 4. Continue with "Task 2: Install the NSR-R/3 Software" on page 51. From the Fujitsu Siemens Computers Web Site Visit the Fujitsu Siemens Computers web site at and follow the links NetWorker Modules and then NetWorker SW. Select the appropriate operating system (Linux or Solaris) and note the information provided before downloading NSR-R/3 V3.0. After downloading, gunzip the package, if necessary, and continue with "Task 2: Install the NSR-R/3 Software" on page Task 2: Install the NSR-R/3 Software To install the NSR-R/3 software on a computer running SAP R/3 with Oracle software: 1. Log on as root on the SAP R/3 with Oracle database server and change to the directory containing the installation files. 2. Depending on the operating system, at a command prompt enter the appropriate installation command with the appropriate package name, as listed in Table 13 on page 51. Table 13. Commands for Installing NSR-R/3 Operating System Linux Solaris Install Package Command # rpm -i nsrbckint.rpm # pkgadd -d installation_path SMAWnwr3 51

52 Task 2: Install the NSR-R/3 Software 3. Link the backint program to the directory where the SAP BRTools reside, for example on Solaris: # ln -s /opt/nsr/backint /usr/sap/<oracle_sid>/sys/exe/run/backint 4. Copy the init.utl file to the $ORACLE_HOME/dbs directory and rename this file to init<oracle_sid>.utl, where <ORACLE_SID> is the name of the Oracle system ID (defined in the environment variable $ORACLE_SID), for example on Solaris: # cp /opt/nsr/nsr_r3/init.utl $ORACLE_HOME/dbs/init<ORACLE_SID>.utl 3 5. Set the $PATH environment variable to include the location of the NetWorker client executables, typically /opt/nsr. 6. Enable and register NSR-R/3. For instructions, see "Installing Licenses" on page 53. Installing the NSR-R/3 Software in a Nondefault Location If the NetWorker software is installed in a nondefault location, you can either: Install the NSR-R/3 software into the same nondefault location using the appropriate options for your operating system s installation program. Copy the nsrsapsv and sapclone executables from their default installation location into the directory where nsrexecd is located. For example, the default installation directory for nsrsapsv is /opt/nsr. Installing the NSR-R/3 Software on Solaris with Installer If you perform the installation at the console, the installation program appears automatically after inserting the CD. If you are not at the system's console, please perform the following steps: Insert the NetWorker CD into the CD ROM drive. Solaris automatically performs the mount operation. Log in as the root user. Set the variable DISPLAY # DISPLAY=<myhost>:0 Enter the following command, to change to the product directory on the CD # cd /cdrom/<cd name> 52

53 Chapter 3: Installation Execute the following command #./installer Select the package SMAWnwr3. SMAWnwr3 is then installed automatically using the Solaris pkgadd command (see pkgadd(8)). Installing RMAN Components (NSR-DBM-ORA, Optional) Installing Licenses Oracle version 8 or later can use Oracle RMAN software in conjunction with the NSR-R/3 software as an optional method of backing up and restoring data files. To use RMAN, you must install NSR-DBM-ORA (Solaris, Linux) from the NetWorker CD-ROM or downloaded files. For further information refer to the NSR-DBM-ORA. 3 Licenses are delivered in a license file. This license file can contain one or more license strings. You can use the keylic command to install the licenses from your license file. 1. Log on to the NetWorker server as root. 2. When you see the shell prompt, enter the following command to install the license: # keylic -f license file The following messages are then displayed: license name enabled license name authorized This two messages are displayed for each license string contained in the license file. Option -s server can be used to load a license into a remote NetWorker server. This can be used to load a license from a Fujitsu Siemens Computers NetWorker client into a Legato NetWorker server. Note that option -s is not allowed for all types of licenses. 53

54 Managing Your Fujitsu Siemens Computers Licenses Managing Your Fujitsu Siemens Computers Licenses The Fujitsu Siemens Computers License Manager provides a central place for managing the licenses of all your NetWorker clients and servers. Instead of managing licenses separately, you can maintain all your NetWorker licenses from a single computer. Installation of the License Manager is an option when installing the NetWorker software. Using the Fujitsu Siemens Computers License Manager software, you can move the NetWorker software from one computer to another or use a new IP address on an existing NetWorker server without having to reauthorize the software. 3 Uninstall Procedures To uninstall the NSR-R/3 software: 1. Ensure that no Oracle database backups or restores are running. 2. Log in as root. # su root 3. If uninstalling on an Oracle system earlier than Oracle 9i, shut down all Oracle instances that use this ORACLE_HOME. If uninstalling on a system using Oracle 9i or later, this step is not required. 4. Enter the appropriate command for your operating system. Table 14 on page 54 lists the uninstall commands by operating system: Table 14. NSR-R/3 Uninstall Commands Operating System Linux Solaris Uninstall Command # rpm -e nsrbckint # pkgrm SMAWnwr3 54

55 Chapter 3: Installation Uninstalling the RMAN Components (NSR-DBM-ORA) To uninstall RMAN components of the NSR-R/3 software, run the command that is appropriate for your operating system. Table 15 on page 55 lists the NSR-DBM-ORA uninstall commands by operating system: Table 15. NSR-DBM-ORA Uninstall Commands Operating System Linux Solaris NSR-DBM-ORA Uninstall Command # rpm -e nsrdnmo # pkgrm SMAWnwnmo For further information on the uninstallation refer to the NSR-DBM-ORA. 3 55

56 Uninstalling the RMAN Components (NSR-DBM-ORA) 3 56

57 Chapter 4: Manual Backups This chapter describes how to configure and perform manual backups of either online or offline Oracle database instances residing on a SAP R/3 server running Oracle. It assumes that you have properly configured the basic settings for manual backups, described in "Chapter 2: Basic Software Configuration" on page 29. This chapter includes the following sections: "About Manual Backups" on page 57 "Performing an Offline Manual Backup" on page 58 "Performing an Online Manual Backup" on page 59 "Backing Up the Client File Indexes and Bootstrap" on page 61 "Reviewing Backup Session Reports" on page 62 About Manual Backups You can use the following to perform manual backups: The SAPDBA menu interface The brbackup or brarchive command Oracle s RMAN utility can be invoked through either SAPDBA or the brbackup or brarchive command Each of these methods uses NSR-R/3 s backint program. Note: PowerSnap operations are not supported for manual backups, and must be initiated through the nsrsapsv scheduled backup program. For details, see "Chapter 8: PowerSnap Backups and Restores" on page

58 Performing an Offline Manual Backup Important: Manual backups do not automatically back up the NetWorker server s client file index database and the bootstrap save set. Regular backups of these components are needed to ensure adequate protection for disaster recovery. For details, see "Backing Up the Client File Indexes and Bootstrap" on page 61 Performing an Offline Manual Backup Perform offline backups when network traffic is low, typically in the evenings or on weekends, because the SAP R/3 services and the Oracle database instance are not available to users during the backups. Before you begin an offline backup, ensure the following: 4 The backup parameters are set in NSR-R/3 s init<oracle_sid>.utl file. For details on configuring backup parameters, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. The parameters for the backup device type (backup_dev_type) and backup utility parameter file (util_par_file) are set in the SAP utilities profile, init<oracle_sid>.sap. For details on configuring the utilities profile, see "Task 4: Configure the Backup and Restore Utility" on page 42. The NetWorker server, the SAP R/3 server running Oracle, and the NetWorker Remote Exec services are all running. How to Perform an Offline Backup For complete instructions on how to perform an offline backup, refer to the following: To perform an offline backup using the SAPDBA menu interface or the brbackup or brarchive command, refer to the appropriate SAP documentation. To perform an offline backup using the RMAN utility, refer to the appropriate Oracle documentation. 58

59 Chapter 4: Manual Backups The following is an example of an offline backup using the brbackup command: 1. Enter the following command: brbackup -m all -t offline [-d util_file] The -m all option specifies that the backup mode is to back up the entire Oracle database instance. The -t offline option specifies that the backup type is offline. The (optional)-d util_file option specifies that NSR-R/3 is to be used for the backup. For more information on the available brbackup command options, see "Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore" on page 119. With this brbackup command, the Oracle database instance is backed up to the NetWorker server. 2. Back up the client file indexes and bootstrap. For instructions, see "Backing Up the Client File Indexes and Bootstrap" on page 61. Performing an Online Manual Backup 4 An online backup allows users to continue using SAP R/3 services and Oracle database instances while the Oracle tablespaces on the SAP R/3 server are being backed up. Before you begin an online backup, ensure the following: The backup parameters are set in NSR-R/3 s init<oracle_sid>.utl file. For details on configuring the backup parameters, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. The parameters for the backup device type (backup_dev_type) and backup utility parameter file (util_par_file) are set in the SAP utilities profile, init<oracle_sid>.sap. For details on configuring the utilities profile, see "Task 4: Configure the Backup and Restore Utility" on page 42. The NetWorker server, the SAP R/3 server running Oracle, and the NetWorker Remote Exec services are all running. The Oracle database instance is in ARCHIVELOG mode. To set an Oracle database instance to ARCHIVELOG mode, refer to the appropriate Oracle manual. 59

60 Performing an Online Manual Backup How to Perform an Online Backup For complete instructions on how to perform an online backup, refer to the following: 4 To perform an online backup using the SAPDBA menu interface or the brbackup or brarchive command, refer to the appropriate SAP documentation. To perform an online backup using the RMAN utility, refer to the appropriate Oracle documentation. The following is a simple example of an online backup using the brbackup command: 1. Enter the following command: brbackup -m backup_objects -t online [-d util_file_online] The -m backup_objects option specifies the objects to be backed up, where backup_objects is a tablespace, file ID, file ID range, or object list. The -t online option specifies that the backup type is online. The (optional) -d util_file_online option specifies that NSR-R/3 is to be used for the online backup. For more information on the available brbackup command options, see "Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore" on page 119. With this brbackup command, the selected objects are backed up to the NetWorker server. 2. Enter the following command to back up the archive redo logs: brarchive For more information on the available brarchive command options, see "Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore" on page 119. Note: Archive redo logs are required for an online backup. Without redo logs, you can recover a database only to the time of its last full backup. 3. Back up the client file indexes and bootstrap. For instructions, see "Backing Up the Client File Indexes and Bootstrap" on page

61 Chapter 4: Manual Backups Backing Up the Client File Indexes and Bootstrap Unlike scheduled backups, manual backups do not automatically back up the client file indexes and the NetWorker server s bootstrap file. If you do not perform regular scheduled backups, you need to protect this vital information following a manual backup. Important: The client file indexes and bootstrap record are required for restoring the data to a database system in the event of a disaster, such as a disk failure. To back up the client file indexes and NetWorker server bootstrap file, and to apply browse and retention policies to the client file indexes: 1. Include the client in a Group resource, which you must define in both the NetWorker Administrator program and the init<oracle_sid>.utl file. (A Group resource can be created even for a single client.) This ensures that browse and retention policies are applied to the client file indexes when the savegrp command is entered in step 2. For more information on how to configure a Group resource with the NetWorker Administrator program, refer to the NetWorker Administrator s Guide. Note: If the client is not included in a Group resource, you must perform step 3 as an additional step to manually run the nsrim command. 2. On the NetWorker server, log in as the root user (Solaris, Linux) or administrator (Windows), and enter the following savegrp command: savegrp -O -c client_name where: -O saves the client s index files and the associated NetWorker server s bootstrap without backing up the client s database files. -c client_name specifies the hostname of the SAP R/3 server running Oracle whose index files are to be backed up. For more information on the savegrp command, refer to the NetWorker Command Reference Guide. 4 61

62 Reviewing Backup Session Reports 3. If the client is not included in a Group resource (see step 1), apply browse and retention policies to the client index files by entering the following nsrim command: nsrim -c client_name where -c client_name specifies the hostname of the SAP R/3 server running Oracle whose index is to be backed up. For more information on the nsrim command, refer to the NetWorker Command Reference Guide. Important: Applying browse and retention policies to SAP R/3 backups avoids the problems of client file indexes using large amounts of hard drive space and slow index queries. Reviewing Backup Session Reports 4 During backup, NSR-R/3 appends a backup session report to a log file on each SAP R/3 server running Oracle where NSR-R/3 resides. This file can be viewed with any text editor. The default location for all logs is the directory /nsr/applogs Logs can be written to a different location, using a different name, as specified in the backint_log, arch_backint_log, or backint_tmpdir parameters. Logs can be made verbose by setting the verbose parameter. See "verbose" on page 41. Most NSR-R/3 logs can be found by searching for nsr/applogs/*backint*, nsr/applogs/*sap*, or nsr/applogs/*sap*. The default format for the backup report s log filename is as follows: backint<oracle_sid>.log At the end of each operation in the report, there is a statement of the number of successfully completed files out of the total number of files. 62

63 Chapter 4: Manual Backups Table 16 on page 63 lists the attributes recorded in a backup, restore, or inquire session report. Table 16. Report Attributes for Backup and Restore Sessions (Part 1 of 2) Attribute #BACKUP <backup_id> <file> #ERROR <file> or #NOTFOUND <file> #RESTORED <backup_id> <file> #SAVED <backup_id> <file> Files Input File Local Host n of m files saved n of m files restored n of m files reported Number of Symlinks Description Indicates the ID and filename from a successful inquiry function. Indicates an unsuccessful backup, restore, or inquire function and the intended file. Indicates the ID and filename for each successful restore function. Indicates the ID and file name for each successful backup function. Indicates the number of files to be backed up or restored in this backup or restore session. Indicates the name of the input file containing all files that backint is requested to back up or restore. Each requested file is listed under the message, "Reading input file." Indicates the SAP R/3 server running Oracle that is associated with the report. Indicates the number of files (n) successfully saved, restored, or reported by the NetWorker program out of the total number of files (m, see "Files" attribute) intended for the backup or restore operation. Backups list two records, one for data and one for profiles. Indicates the total number of symbolic links found in the files listed in the Input File. 4 63

64 Reviewing Backup Session Reports Table 16. Report Attributes for Backup and Restore Sessions (Part 2 of 2) 4 Attribute Parallelism Params File Processing Parameter File Savesets/Sessions Starting Symlink User Description Indicates the parallelism setting that backint uses when either passing save sets to the NetWorker server for backup or receiving save sets for restore. Indicates the init<oracle_sid>.utl parameter file that backint uses for backup, restore, or inquiry of the SAP R/3 with Oracle data. Indicates the parameter that backint uses during the backup, restore, or inquire process. For details on the NSR-R/3 parameters, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. Indicates the number of save sets that backint sends to the NetWorker server. Indicates the backup or restore command, which is followed by a list of the files that were or were not successfully backed up or recovered in each session. Specifies the location of a symbolic link associated with the file backed up or restored. The most common symbolic link is between the /oracle and /mnt/oracle directories. During backup, this link is backed up so that upon recovery the link is resolved. Indicates the database ID (ORACLE_SID) associated with the database instance. BRTools passes this value to backint. 64

65 Chapter 5: Scheduled Backups This chapter describes how to configure scheduled backups of SAP R/3 servers running Oracle. It includes the following sections, which describe tasks that should be performed in sequence: "Task 1: Test Basic Settings" on page 65 "Task 2: Configure the Client Resource" on page 66 "Task 3: Configure the Scheduled Backup Configuration File" on page 68 "Reviewing Backup Session Reports" on page 73 Task 1: Test Basic Settings Before configuring scheduled backups, test the network connections and basic software settings by performing a successful manual SAP R/3 with Oracle backup. For basic settings, see "Chapter 2: Basic Software Configuration" on page 29. For manual backup instructions, see "Chapter 4: Manual Backups" on page

66 Task 2: Configure the Client Resource Task 2: Configure the Client Resource Use the NetWorker Administrator program on the NetWorker server to configure the Client resource for each SAP R/3 server running Oracle to be scheduled for backup. For general Client resource settings for NSR-R/3, review the listings for "Client" on page 31. For Client resource settings that are specific to scheduled backups, see Table 17 on page 66. All other settings for scheduled backups must be specified in NSR-R/3 s parameter file and the scheduled backup configuration file. For more information, see the following: "Task 3: Configure the NSR-R/3 Parameters" on page 33 "Task 3: Configure the Scheduled Backup Configuration File" on page 68. Important: Settings in NSR-R/3 s parameter file override any corresponding settings (including default settings) in the NetWorker Client resource. For a complete description of Client resource settings, refer to the NetWorker Administrators Guide. 5 Table 17. Client Resource Settings for Scheduled Backups (Part 1 of 2) Attribute Description Save Set Ensure that the save set name includes the backint command and is defined in the following format: backint:<oracle_sid> For non-powersnap usage, this attribute is only informational, because the nsrsapsv.cfg file determines the ORACLE_SID parameter. For PowerSnap usage, this attribute must be set to backint:<oracle_sid>. 66

67 Chapter 5: Scheduled Backups Table 17. Client Resource Settings for Scheduled Backups (Part 2 of 2) Attribute Backup Command Description Enter the nsrsapsv command in this attribute, with the -f option and the configuration filename: nsrsapsv -f filename where filename is the full pathname of the scheduled backup configuration file (for example, /nsr/res/nsrsapsv.cfg). For information on the scheduled backup configuration file, see "Task 3: Configure the Scheduled Backup Configuration File" on page 68. Note: Because the Backup Command attribute is limited to 64 characters, store scheduled backup configuration files in the default path /nsr/res/nsrsapsv.cfg Figure 4 on page 68 provides an example showing part of a Client resource configuration in the NetWorker Administrator program on a Solaris or Linux system. Note the sample values in the Save Set and Backup Command fields. 5 67

68 Task 3: Configure the Scheduled Backup Configuration File Figure 4. Example Client Resource 5 Task 3: Configure the Scheduled Backup Configuration File NSR-R/3 s scheduled backup configuration file, named nsrsapsv.cfg (included with the installation), is a text file that contains parameters required by the NetWorker nsrsapsv scheduled backup program. Note: Use a copy of the /opt/nsr/nsr_r3/nsrsapsv.cfg file, and preserve the original file. Among other things, the nsrsapsv.cfg configuration file is used to: Identify the SAP Oracle database to be backed up. Specify the BRTools command used for the scheduled backups. Configure system specific environment variables. 68

69 Chapter 5: Scheduled Backups To use this configuration file, its full pathname must be specified in the Backup Command attribute of the Client resource (see "Backup Command" on page 67). Uncomment any parameters in the configuration file that you want to use in the backup. To set a parameter, use the following format: parameter = value Important: Use full pathnames for parameters that specify a path or filename. Oracle special characters such as? are not supported. Also environment variables such as $ORACLE_HOME are not supported. 5 69

70 Task 3: Configure the Scheduled Backup Configuration File Table 18 on page 70 lists the parameters and values for the scheduled backup configuration file, nsrsapsv.cfg, or a copy of this file. Table 18. Parameters for the NSR-R/3 Scheduled Backup Configuration File (Part 1 of 4) 5 Parameter Any name_path=value pair Any name=value pair BR_EXEC Value This parameter is used to append values to any environment variable named name_path (for example, LD_LIBRARY_PATH). If an environment variable with this name already exists, then the parameter value listed here is appended to the existing value for the environment variable. If an environment variable with this name does not exist, then it is created. For example: LD_LIBRARY_PATH=/export/home/oracle/product/8.1.5/ lib:/usr/openwin/lib This parameter is optional. This parameter is used to add any environment variable named name. If the environment variable specified by name already exists, then it is overwritten. For example: BR_TRACE=1 BR_TRACE is set to 1 in the environment, which instructs brbackup or brarchive to print out additional trace information. This parameter is optional. This parameter specifies the brbackup or brarchive command, with any options that nsrsapsv uses. Note: Do not use the -u option, which identifies the user name and password of the Oracle database administrator. For example: BR_EXEC=brbackup This is a required parameter. 70

71 Chapter 5: Scheduled Backups Table 18. Parameters for the NSR-R/3 Scheduled Backup Configuration File (Part 2 of 4) Parameter NLS_LANG NSR_SAP_ADMIN_ USER NSR_SAP_ADMIN_ GROUP NSR_SAP_RESTORE_ RETRY_COUNT NSR_SAP_RESTORE_ RETRY_DELAY_SECS ORACLE_BIN Value Format the value of this parameter as follows: LANGUAGE_TERRITORY.CHARACTERSET For example: NLS_LANG=AMERICAN_AMERICA.US7ASCII For more information about this parameter, refer to the Oracle documentation. This is a required parameter. This parameter specifies the user name as which BR_EXEC tool will run. If no name is specified, or the name is not valid, the '<OracleSID>adm' user will be used. This parameter is optional. This parameter specifies the group name as wich BR_EXEC tool will run. If no name is specified, or the specified name is not a valid group for the admin user, the default group for this user will be used. This parameter is optional. This parameter specifies the number of times a failed restore will retry. If no value is set, retry is not attempted. This parameter specifies the wait time in seconds before attempting retries of failed restores. If no value is set, retry is immediately attempted. This parameter specifies the location of the Oracle binaries. The specified path is appended to the PATH environment variable so that all Oracle binaries can be found, if needed. This parameter is required only if the Oracle binaries are not in the default location, $ORACLE_HOME/bin. 5 71

72 Task 3: Configure the Scheduled Backup Configuration File Table 18. Parameters for the NSR-R/3 Scheduled Backup Configuration File (Part 3 of 4) 5 Parameter ORACLE_HOME ORACLE_SID PATH Value Set this parameter to the installation path for the Oracle server software for ORACLE_SID. Use the full pathname. For example: ORACLE_HOME=/export/home/oracle/product/8.1.5 This is a required parameter. This parameter identifies the system identification (SID) for the Oracle instance to be backed up. If this parameter is specified, then its value is used for the Oracle SID. If the parameter is not specified, then the Oracle SID is derived from the save set name in the NetWorker Administrator s Client resource for this client. For example, if the save set name is backint:sap and you do not specify ORACLE_SID in the scheduled backup configuration file, then SAP is used for the Oracle SID. For example: ORACLE_SID=SAP This parameter is optional. This parameter is used to add more search paths to the PATH environment variable. The specified value is appended to the PATH environment variable. You may specify multiple search paths, using either one of the following methods: PATH=/dir1:/dir2:/dir3/dir4/dir5 PATH=/dir1 PATH=/dir2 PATH=/dir3/dir4/dir5 This parameter is optional. 72

73 Chapter 5: Scheduled Backups Table 18. Parameters for the NSR-R/3 Scheduled Backup Configuration File (Part 4 of 4) Parameter SAP_BIN SAPBACKUP SAPDATA_HOME Value This parameter specifies the path to the location of the BRTools binary files. This should also be where the backint executable resides, after it is manually moved to this location following installation of NSR-R/3. This path is added to the PATH environment variable so that the BRTools binaries and backint can be found. For example in case of ORACLE_SID = "SAP": SAP_BIN=/usr/sap/SAP/SYS/exe/run This is a required parameter. This parameter indicates the directory to store backup logs. BRTools uses this directory to store temporary or log files. The default value is $ORACLE_HOME/sapbackup. This parameter specifies the root directory for SAP datafiles. For details, refer to the SAP documentation. Reviewing Backup Session Reports During a backup session, several reports are written to log files on each SAP R/3 server running Oracle where NSR-R/3 resides. Each time the nsrsapsv program is called, a log file is created with the name nsrsapsv.<process_id>_<oracle_sid>, for example, nsrsapsv.359_sap. The backint program saves a backup report in the backint log file. The default log filename is backint <ORACLE_SID>.log. These log files can be viewed with any text editor. The default location for all logs is the directory /nsr/applogs The default format for the backint log filename is as follows: backint <ORACLE_SID>.log 5 73

74 Reviewing Backup Session Reports Logs can be written to a different location, using different names, as specified in the backint_log, arch_backint_log, or backint_tmpdir parameters. For information on these parameters, see Table 8 on page 34. Logs can be made verbose by setting the verbose parameter. See "verbose" on page 41. For a list of backup and restore session report attributes, see Table 16 on page

75 Chapter 6: Cloning Save Sets Cloning is the NetWorker process used to make an exact copy of saved data (save sets) from a storage volume to a clone volume. NetWorker software indexes and tracks clones in both the client file index and the media database. The NSR-R/3 software uses the sapclone command to clone save sets. This chapter includes the following sections: "Clone Command Syntax and Options" on page 75 "Monitoring the Cloning Process" on page 77 Clone Command Syntax and Options Save sets generated for the Oracle database ID, ORACLE_SID, using NSR-R/3 can be cloned by running the sapclone command from either the NetWorker server or the SAP R/3 server running Oracle. The sapclone command works with nsrclone to write the cloned data to the default clone pool, or to a specified clone volume whose pool type is "clone." Use the following syntax for the sapclone command: sapclone [-a] [-b pool] [-c client] [-n] [-s server] -u user Command options in brackets ([ ]) are optional; only the -u option is mandatory and user specifies the ORACLE_SID of the database. Table 19 on page 76 lists the options to use with the sapclone command. 75

76 Clone Command Syntax and Options Table 19. The sapclone Options (Part 1 of 2) Option Description Example -a Clones all of a client s save sets. If this option is not specified, NSR-R/3 only clones save sets created in the last 24 hours. -b pool Specifies the pool to which the cloned save sets are sent. If this option is not specified, the save sets are sent to the Default clone pool. -c client Identifies the name of the client whose backed up data should be cloned. NetWorker software uses the client file index for the specified client to find and clone the client s data. Use this option for cloning data backed up from a cluster. For example, you may want to set this option to the name of the cluster s virtual node. sapclone -a -u SAP sapclone -b SAPClone -u SAP sapclone -c saturn -u SAP 6 -n Tests the cloning operation on a client s save sets. When this option is specified, the cloning operation is not initiated. The example performs a trial cloning process on the save sets created by backint in the last 24 hours, with none of the data being stored onto volumes of a clone pool. sapclone -n -u SAP 76

77 Chapter 6: Cloning Save Sets Table 19. The sapclone Options (Part 2 of 2) Option Description Example -s server Specifies the NetWorker server to which to clone. You need this option only if one of the following conditions is true: You want to clone to a NetWorker server other than the default server You enter the sapclone command on a SAP R/3 server running Oracle. -u user Mandatory option. Specifies the ID of the Oracle database, whose save sets are to be cloned. sapclone -s mars -u SAP sapclone -u SAP Monitoring the Cloning Process To enable monitoring of the cloning process, the NetWorker server displays messages in the NetWorker Administrator program for each save set that is cloned. Because the cloning process only clones complete save sets, additional volumes are requested if a save set spans multiple volumes. Messages generated during the cloning process appear on screen and are recorded in the NetWorker messages log file in the location /nsr/logs For more information on NSR-R/3 and NetWorker error messages, see "Appendix C: Troubleshooting" on page

78 Monitoring the Cloning Process 6 78

79 Chapter 7: Restoring Data This chapter describes how to restore data that was backed up by NSR-R/3. It includes the following sections: "Reviewing Save Sets" on page 79 "Performing Restores" on page 80 "Restoring SAP R/3 with Oracle Cluster Data" on page 82 "Reviewing Restore Session Reports" on page 82 Note: In the event of a disaster, such as disk failure, refer also to the NetWorker Disaster Recovery Guide. Reviewing Save Sets To review NetWorker save sets in the NetWorker Administrator program, select Indexes from the Client menu to open the Indexes window. Select an entry to review. Each entry displays the ID assigned to the save set, the number and size of the file, and the date and level of the backup session. 79

80 Expiration of Save Sets Expiration of Save Sets For every client save set backed up, the NetWorker server stores two sets of records: One or more records are written to the online client file index for the client computer and its save set. These records are maintained until the browse policy for the save set expires. One record is written to the online media database for the location of the save set s data on a specific storage media. This record is maintained until the retention policy for the save set expires. The expiration for the browse and retention policies must be set in NSR-R/3 s parameter file. For details, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. Once the browse and retention policies expire, the backup media is eligible for recycling and can be overwritten. Until the media is actually overwritten (relabeled), the data from the media can be restored by using the scanner command on the NetWorker server. For a complete description of how NetWorker software uses browse and retention policies to track data, refer to the NetWorker. Performing Restores If a SAP R/3 server running Oracle was backed up by using the NSR-R/3 software, then you can restore data to the server by using either the SAPDBA interface or BRTools (the brrecover or brrestore command) directly. If a backup was done with RMAN, then the restore should also be done with RMAN. For information on restoring with RMAN, refer to the appropriate Oracle documentation. 7 A full restore of an entire Oracle database instance restores database files, redo logs, and control files. A restore of a single database object, such as a tablespace or datafile, restores the object you specify, and does not restore redo logs and control files. Note: Restore options used with either SAPDBA or BRTools overwrite any corresponding settings in the SAP R/3 initialization file, init<oracle_sid>.sap. For information on using the initialization file, see "Task 4: Configure the Backup and Restore Utility" on page

81 Chapter 7: Restoring Data Important: The brrestore program, whether invoked directly from the command line or from the SAPDBA interface, first deletes all the original files to be restored before calling backint to restore the files. If brrestore is unable to invoke backint for any reason, the original files are lost. Perform an inquiry of the backup first, before performing a restore. An alternative is to restore the files to another location, and preserve the original files. Use the -m parameter, and specify the restore destination, as follows: brrestore -m tablespace_name=restore_directory For more information on restoring to a different location, refer to the appropriate SAP documentation. How to Restore a Database or Database Object To restore an entire database instance or a single database object using either the SAPDBA interface or the brrestore command: 1. Ensure that the NetWorker server, the SAP R/3 server running Oracle, and the NetWorker Remote Exec services are running. 2. Shut down the Oracle database instance (for a full restore), or take the database objects you are restoring offline (for restore of a single database object). 3. Ensure that either utl_file or rman_utl is configured as the backup device type in the SAP initialization file, init<oracle_sid>.sap. For details, see "Task 4: Configure the Backup and Restore Utility" on page Ensure that the appropriate NetWorker server, client, and parallelism settings are configured in NSR-R/3 s init<oracle_sid>.utl file. For details, see "Task 3: Configure the NSR-R/3 Parameters" on page Ensure that the backup you want to restore exists using either SAPDBA or the brrestore inquire function as follows: brrestore -verify 7 81

82 Restoring SAP R/3 with Oracle Cluster Data 6. Depending on the type of restore you are performing and your restore method, do one of the following: To restore an entire database instance: If using the SAPDBA interface, in the Restore/Recovery window, select Full Restore. If using the command line, enter the brrestore command with the -m full option. See "Syntax and Options for brrestore Command" on page 126. To restore a single database object: If using the SAPDBA interface, in the Restore/Recovery window, select Restore One Tablespace or Restore Individual Files. If using the command line, enter the brrestore command with the -m option to specify a tablespace, file ID, or file ID range. See "Syntax and Options for brrestore Command" on page For details on applying the applicable redo logs to recover the database, refer to the related SAP R/3 and Oracle documentation. 8. To recover the database after a disaster occurence please use the brrecover command if available. See "Syntax and Options for brrecover Command" on page 123. For more details on using the SAPDBA interface or the BRTools, refer to the appropriate SAP documentation. Restoring SAP R/3 with Oracle Cluster Data Restoring data backed up from private disks in a cluster node is similar to restoring data on a system that is not part of a cluster. To restore data from a shared disk of a virtual client, set NSR-R/3 s client parameter to restore files to the virtual client, where the files originated during the backup. For more information on this parameter, see "client" on page 34. Reviewing Restore Session Reports 7 During restore, NSR-R/3 appends a restore session report to a log file on each SAP R/3 server running Oracle where NSR-R/3 resides. This file can be viewed with any text editor. The default location for all logs is the directory /nsr/applogs 82

83 Chapter 7: Restoring Data The default format for the restore report s log filename is as follows: backint <ORACLE_SID>.log Logs can be written to a different location using different names, as specified in the backint_log, arch_backint_log, or backint_tmpdir parameters. For information on these parameters, see Table 8 on page 34. For a list of restore session report attributes, see Table 16 on page

84 Reviewing Restore Session Reports 7 84

85 Chapter 8: PowerSnap Backups and Restores This chapter describes how to configure and run PowerSnap backups and restores of SAP R/3 with Oracle data on supported primary storage devices. This chapter includes the following sections: "Requirements" on page 86 "Types of PowerSnap Backups" on page 87 "Types of PowerSnap Restores" on page 89 "PowerSnap Backup and Restore Data Flows" on page 90 "Quick Start" on page 92 "PowerSnap Software Configuration Roadmap" on page 94 "Configuring NetWorker Resources for PowerSnap" on page 96 "Setting PowerSnap Parameters in the NSR-R/3 configuration file" on page 98 "Setting Variables in the PowerSnap Configuration File" on page 102 "Invoking PowerSnap Backup Processes" on page 106 "Querying PowerSnap Backup Records" on page 114 "Invoking PowerSnap Restore Processes" on page

86 Requirements Requirements 8 This section describes the types of environments and software required to use the PowerSnap features of the NSR-R/3 software. Supported Environments PowerSnap provides continuous point-in-time (PIT), snapshot-based (immediate live backup) protection and availability of SAP R/3 with Oracle data on supported primary storage platforms. To use the PowerSnap features, NSR-R/3 must be used in conjunction with the NetWorker PowerSnap Module. The PowerSnap Module creates the snapshots, and NSR-R/3 stores the snapshot data. PowerSnap backups must use servers, clients, or storage nodes on Solaris platforms only. The supported types of primary storage platforms include, but are not limited to EMC CLARiiON. The Oracle control file and all SAP directories, except sapdata<n>, should not be located on a snap volume. Refer to your snapshot vendor and corresponding NetWorker PowerSnap documentation for details. Note: A PowerSnap backup can only be invoked by a NetWorker savegroup run. The savegroup may be started manually or automatically. A PowerSnap backup must not be started by directly invoking the BRTools commands or SAPDBA. Required Software Components PowerSnap backup and restore of SAP R/3 with Oracle data and files require the following software components: On the application server (Oracle Server): SAP R/3, which contains the BRTools and SAPDBA At least NetWorker Client NSR-R/3 for SAP R/3 NetWorker PowerSnap Module On the PowerSnap proxy client: NetWorker PowerSnap Module At least NetWorker Client. If the secondary storage is on this host, NetWorker Storage Node is required 86

87 Chapter 8: PowerSnap Backups and Restores For details on the installation requirements, refer to the appropriate NetWorker PowerSnap Module Installation and. Types of PowerSnap Backups 8 This NSR-R/3, in conjunction with the PowerSnap Module, supports the types of PowerSnap for SAP R/3 with Oracle backups summarized in Table 20 on page 87: Table 20. Summary of Supported PowerSnap Backup Types Backup Type Snapshot Retention Location of Stored Data "Instant Backup" see page 87 Permanent Snapshot only "Immediate Live Backup" see page 88 Temporary Secondary storage (tape) only "Deferred Live Backup" see page 88 Permanent Both snapshot and secondary storage The PowerSnap backup type is configured by the Snapshot Policy attribute in the NetWorker Backup Group, see "Configuring the NetWorker Group Resource" on page 96. Instant Backup An instant backup creates a permanent point-in-time (PIT) copy, or snapshot, of SAP R/3 with Oracle data. This copy is then stored on the primary storage system where it is available to NSR-R/3 for performing instant restores or rollbacks. Instant backups can be scheduled to occur many times in a single day, with little impact to the SAP R/3 with Oracle Server or network. A group of SAP R/3 with Oracle datafiles in the snapshot is referred to as a snap set. The snapshot policy must be configured to control the lifecycle of the snap set. This policy specifies the frequency of instant backups and how long snapshots are retained before being recycled. For more information, see "Configuring the NetWorker Snapshot Policy Resource" on page

88 Live Backup 8 Important: Instant backups protect against logical failures only. To protect against physical media failures, the snapshot must be backed up to secondary storage, such as tape. For functional details of an instant backup, see "Instant Backup Processes" on page 106. Live Backup A live backup (also known as "snapshot rollover" or "rollover to tape" backup) is a tape backup of a previously-created snapshot. NSR-R/3 supports two types of live backup: immediate live backup, and deferred live backup. Immediate Live Backup Immediate live backup (also known as "serverless snapshot backup" or "snapshot-based backup") is a process by which a temporary snapshot is created, and immediately backed up to secondary storage such as tape. The snapshot is then automatically deleted from the primary storage (and not available to NSR-R/3 for performing instant restores or rollbacks). Deferred Live Backup Deferred live backup is a process by which a permanent snapshot, created on the primary storage system by an instant backup, is backed up to secondary (conventional) storage, such as tape. The permanent snapshot is retained on the primary storage (and available to NSR-R/3 for performing instant restores or rollbacks) for the period specified by either of the following: Snapshot expiration policy Retain SnapShots attribute of the SnapShot Policy for the client s Group resource. The Group Snapshot Policy must be configured to enable live backups. For more information, see "Configuring the NetWorker Snapshot Policy Resource" on page 96. Note: A PowerSnap client host that is separate from the SAP R/3 host can be used to move the snapshot to the conventional storage medium such as tape. The use of a PowerSnap client as a secondary host reduces the demand on the SAP R/3 host. The PowerSnap client can be a NetWorker storage node. 88

89 Chapter 8: PowerSnap Backups and Restores For functional details on live backups, see the following: "Immediate Live Backup Processes" on page 109 "Deferred Live Backup Processes" on page Types of PowerSnap Restores NSR-R/3, in conjunction with the PowerSnap Module, supports the types of PowerSnap for SAP R/3 with Oracle restores described in Table 21 on page 89. Table 21. Summary of Supported PowerSnap Restore Types Restore Type "Instant Restore" see page 89 "Rollback" see page 89 "Restore from Secondary Storage" see page 90 Data Retrieved From: Mounted snapshot Unmounted snapshot, entirely restored to source location Secondary storage (no snapshot available) The restore type is specified in the RESTORE_TYPE_ORDER variable in the user-defined PowerSnap configuration file. See "Setting Variables in the PowerSnap Configuration File" on page 102. Instant Restore An instant restore is the process by which a snapshot that was created by an instant backup is mounted. This enables its saved data to be retrieved. A minimal amount of time is required for this type of restore. For functional details of instant restores, see "Instant Restore and Rollback Processes" on page 115. Rollback A rollback restores the entire snapshot to the source location by using the hardware s particular capabilities. Relocation during rollbacks is not currently supported by PowerSnap. To determine if a rollback is supported on a specific type of hardware, refer to the appropriate NetWorker PowerSnap Module Installation and. 89

90 Restore from Secondary Storage 8 Important: Rollbacks are potentially destructive because they overwrite the entire contents of a snapshot unit, such as a volume or disk. For functional details of rollbacks, see "Instant Restore and Rollback Processes" on page 115. Restore from Secondary Storage A restore from secondary storage is the process by which a snapshot that was saved to the secondary storage system is restored from the secondary storage. The PowerSnap Module software essentially uses the NetWorker recover program, to retrieve the data. For functional details on restores from secondary storage, see "Restore from Secondary Storage Processes" on page 117. PowerSnap Backup and Restore Data Flows The backup and restore strategy requires knowledge of how the Oracle and Fujitsu Siemens Computers NetWorker software components all work together, see "Required Software Components" on page 86. During a PowerSnap backup of SAP R/3 with Oracle data, the SAP R/3 with Oracle Server processes interact indirectly with the NetWorker server through the NSR-R/3 and PowerSnap Module software. 1. The SAP brbackup program invokes the NSR-R/3 software, which then communicates with the PowerSnap Module. 2. On the SAP R/3 with Oracle server host, the PowerSnap Module takes a point-in-time snapshot of the Oracle data on the primary storage. 3. If a live backup is performed, the PowerSnap Module moves the SAP R/3 with Oracle data from the snapshot on the primary storage to the NetWorker server or storage node. 4. The NetWorker server or storage node then stores the Oracle data on the secondary storage, such as a tape. 5. At the end of the PowerSnap backup, the NetWorker server updates the online client and media indexes with information about the backup. 90

91 Chapter 8: PowerSnap Backups and Restores For more information about NetWorker server and NetWorker client programs and services, refer to the NetWorker. Data flow and intraprocess communication for SAP R/3 with Oracle PowerSnap backup and restore is illustrated in Figure 5 on page 91. For functional details on backup and restore process, see the following topics: "Invoking PowerSnap Backup Processes" on page 106 "Invoking PowerSnap Restore Processes" on page 115 Figure 5. NSR-R/3 PowerSnap Backup and Restore Data Flow 8 SAP R/3 with Oracle Server Host NetWorker Client BRTools/ SAP R/3 with Oracle process PowerSnap Client (NetWorker Storage Node) data NetWorker Server NSR-R3 NetWorker Client PowerSnap Module PowerSnap Module NetWorker Server SAP R/3 with Oracle Datafiles Primary Storage Point-in-Time Copy of SAP R/3 with Oracle Datafiles Storage Medium 91

92 Quick Start 8 Quick Start The following steps describe typical settings to enable and use NSR-R/3 s PowerSnap features for backup and restore. To customize your configuration, use this information in conjunction with more specialized information described in "PowerSnap Software Configuration Roadmap" on page 94. Note: Before running the test included in this procedure, back up the test database. Test on a nonproduction database. To configure and test the PowerSnap features for a typical configuration: 1. Ensure that the NetWorker Group used by NSR-R/3 has the proper PowerSnap attribute settings, as listed in Table 22 on page 92. Table 22. Backup Group s PowerSnap Attributes Attribute Snapshot Snapshot Policy Snapshot Pool Start Time Interval Setting To enable PowerSnap functionality: True Serverless is recommended for this testing. If needed, daily or other customized policies can be used later. Selecting a "Pool" resource dedicated to storing snapshot operation metadata is recommended. File type volume devices are strongly recommended over tape. Must be set in relation to the Number of Snapshots attribute for the snapshot policy: (Interval x Number of Snapshots) must be less than or equal to (24:00 h - Start Time). Must be set in relation to the "Start Time" and the "Number of Snapshots" attribute for the snapshot policy. 92

93 Chapter 8: PowerSnap Backups and Restores 2. Modify NSR-R/3 s init<oracle_sid>.utl file to enable the PowerSnap parameters and variables. A typical and recommended configuration is as follows: ps_backup_mode = yes ps_archive_mode = no ps_restore_mode = yes ps_inquire_mode = yes ps_exclude_backup_bi_run_nums = 2 ps_exclude_archive_bi_run_nums = 1;2 ps_exclude_backup_paths = (leave blank) ps_exclude_archive_paths = (leave blank) ps_ps_before_nonps = yes ps_group_objs = yes ps_opaque_pfilename = /nsr/res/nsrsapps.cfg Descriptions of these parameters are listed in Table 23 on page Create and edit the PowerSnap configuration file by using an appropriate filepath and name, for example /nsr/res/nsrsapps.cfg Include any parameters required or intended for use with the PowerSnap Module, for example: NSR_SNAP_TYPE = emcclar NSR_PS_DEBUG_LEVEL = 5 NSR_VERBOSE = true NSR_DATA_MOVER = jupiter Debug level is intended for technical support diagnostics only. For more information on the nsrsapps.cfg file s contents, refer to Table 24 on page 102 or to the NetWorker PowerSnap Module Installation and Administrator s Guide. 4. Test the client s group snapshot settings by invoking the savegrp command. a. From the NetWorker server nwadmin program, open the Group resource. b. In the Autostart attribute, select Enabled. c. In the Start Time attribute, enter a time that is one or two minutes later than the current time. d. Click Apply, or invoke the savegrp command from the command prompt as follows: savegrp -c clientname grpname 8 93

94 PowerSnap Software Configuration Roadmap 8 The backup test is successful if the backint log reports the following message: n of n PS files reported where n is the number of files requested that reside on a PowerSnap disk. Note: If you encounter a problem, check NSR-R/3 s backint log file for PowerSnap related messages. Some common problems include: The target file is not managed by the PowerSnap Module. The PowerSnap Module daemon or service, nsrpsd, is not running. The PowerSnap powersnap.res configuration file needs to be modified. The ps_xxx_mode or ps_exclude_xxx parameter (where xxx is specified as described in Table 23 on page 98) is set to exclude a file from PowerSnap processing. The ps_opaque_pfilename file needs to be modified. For further troubleshooting, refer to "Generating Diagnostic Logs" on page Run a pre-restore inquiry with the following command: brrestore -verify 6. Test a restore with the following command: brrestore The restore test is successful if a backint log reports the following message: n of n PS files reported where n is the number of files requested that reside on a PowerSnap disk. PowerSnap Software Configuration Roadmap Before you configure the PowerSnap features, ensure that both NSR-R/3 for SAP R/3 with Oracle and the required PowerSnap Module software are installed according to the instructions in the following documentation: "Chapter 3: Installation" on page 47 NetWorker PowerSnap Module Installation and (Refer to the PowerSnap Module version for the primary storage system.) 94

95 Chapter 8: PowerSnap Backups and Restores To configure the PowerSnap features, complete the following sets of procedures: 1. Use the instructions in "Chapter 2: Basic Software Configuration" to configure the NetWorker Server, Client, Device, and other resources. 2. For live SAP R/3 with Oracle backups, configure a Device resource for each secondary storage device (such as a tape) to be used during backups. The devices must be mounted. 3. Configure the SAP R/3 with Oracle database layout to position the datafiles on the primary storage supported by the specific PowerSnap Module. 4. Use the instructions in "Chapter 5: Scheduled Backups" to configure the basic scheduled backup. 5. Complete the procedure: "Configuring NetWorker Resources for PowerSnap" on page Complete the procedure: "Setting PowerSnap Parameters in the NSR-R/3 configuration file" on page Complete the procedure: "Setting Variables in the PowerSnap Configuration File" on page

96 Configuring NetWorker Resources for PowerSnap Configuring NetWorker Resources for PowerSnap 8 Configure the following NetWorker resources as described in this section: SnapShot Pool resource SnapShot Policy resource Group resource Client resource Configuring the NetWorker Snapshot Pool Resource Configure a separate snapshot pool to support PowerSnap for SAP R/3 with Oracle backups. The PowerSnap Module stores the metadata from the snapshot in this pool. Use the same configuration method as for a regular NSR-R/3 for SAP R/3 with Oracle backup. However, the specified backup device should be a file or advanced file type. Specify the pool name in the Snapshot Pool attribute of the NetWorker Group resource as described in "Configuring the NetWorker Group Resource" on page 96. For more information on configuring this extra pool, refer to the appropriate NetWorker PowerSnap Module Installation and. Configuring the NetWorker Snapshot Policy Resource A NetWorker snapshot policy must be configured to perform either instant or live PowerSnap for SAP R/3 with Oracle backups. You can either specify a preconfigured policy, or create a new one. Configure a NetWorker Snapshot Policy resource by using the instructions in the appropriate NetWorker PowerSnap Module Installation and Administrator s Guide. Configuring the NetWorker Group Resource For PowerSnap for SAP R/3 with Oracle backups, configure a NetWorker Group resource by using the instructions in the appropriate NetWorker PowerSnap Module Installation and. 96

97 Chapter 8: PowerSnap Backups and Restores Configuring the NetWorker Client Resource The basic NetWorker Client resource for NSR-R/3 is configured according to the settings described in "Task 2: Configure the Client Resource" on page 66. Only members of a NetWorker user group with the Change Security Settings privilege can set the Remote Access attribute in the Client resource. The Browse Policy attribute in the Client resource, which is superseded by the init<oracle_sid>.utl expiration parameter, applies only to the NetWorker client file index entries for these types of backups: Backups that reside on secondary storage (live backups). Backups not performed by the PowerSnap Module. The Retention Policy attribute in the Client resource, which is superseded by the init<oracle_sid>.utl expiration parameter, applies only to the NetWorker media database entries for these types of backups: Live backups. Backups not performed by the PowerSnap Module. The life cycle of a snapshot (instant backup) is governed by the snapshot policy specified in the client s Group resource. 8 97

98 Setting PowerSnap Parameters in the NSR-R/3 configuration file 8 Setting PowerSnap Parameters in the NSR-R/3 configuration file PowerSnap parameters are set in the init<oracle_sid>.utl file. These settings assume that the PowerSnap Module is installed and licensed. Descriptions of the PowerSnap parameters for NSR-R/3 are listed in Table 23 on page 98. Table 23. PowerSnap Parameters in init<oracle_sid>.utl File (Part 1 of 4) PowerSnap Parameter ps_backup_mode ps_archive_mode ps_restore_mode ps_inquire_mode Default Value No Description Each of these PowerSnap functional modes is enabled if set to Yes. Normally, all the modes are set together to either all Yes or all No, except ps_archive_mode=no and all others =yes. Do not use any other settings except for diagnostic purposes. ps_opaque_pfilename Null Absolute pathname of the PowerSnap parameter file. For details, refer to the appropriate PowerSnap module documentation. This setting is mandatory if the PowerSnap functional mode parameters are enabled. For example: /nsr/res/nsrsapps.cfg. See Table 24 on page

99 Chapter 8: PowerSnap Backups and Restores Table 23. PowerSnap Parameters in init<oracle_sid>.utl File (Part 2 of 4) PowerSnap Parameter Default Value Description 8 ps_exclude_backup_bi_run_nums ps_exclude_archive_bi_run_nums Null Specifies which backint runs are to be excluded from PowerSnap processing (typically run number 2). Parameter files, SAP backup catalog files, and other files that do not benefit from PowerSnap processing can be backed up by conventional processing without PowerSnap, thereby saving valuable snapshot disk resources. Specify a value of one or more valid backint run numbers to exclude, each separated by a semicolon (;). Important! The following starting values are strongly recommended: ps_exclude_backup_bi_run_nums=2 ps_exclude_archive_bi_run_nums=1;2 Each brbackup or brarchive session invokes multiple backint processes sequentially, for example run number 1 followed by run number 2. If run 2 is excluded, then run 1 backs up the database datafiles exclusively by using PowerSnap, and run 2 forces files that do not benefit from PowerSnap processing, to be backed up by conventional processing without PowerSnap. 99

100 Setting PowerSnap Parameters in the NSR-R/3 configuration file Table 23. PowerSnap Parameters in init<oracle_sid>.utl File (Part 3 of 4) 8 PowerSnap Parameter Default Value Description ps_exclude_backup_paths ps_exclude_archive_paths Null Specifies individual PowerSnap files to exclude from PowerSnap processing, but to back up with conventional non-snapshot processing instead. PowerSnap files are those on a snapshot-capable file system that NetWorker is aware of. Valid values are any full path string, including standard wildcard characters. Use values that are based on the actual filenames that BRTools passes to backint. Note: Wildcard support follows standard shell support for full file pathnames. For example the file /db01/foo.dbf is excluded if the parameter is set to a value of: /db01/foo.*, or /db??/*.dbf, but not excluded if set to /db*. Specify one or more valid, full pathnames, each separated by a semicolon (;). Whenever possible, preference should be given to setting the ps_exclude_xxx_bi_run_nums parameters instead of using these parameters. 100

101 Chapter 8: PowerSnap Backups and Restores Table 23. PowerSnap Parameters in init<oracle_sid>.utl File (Part 4 of 4) PowerSnap Parameter Default Value Description 8 ps_ps_before_nonps Yes Specifies whether to perform all PowerSnap processing before conventional processing without PowerSnap. This helps prevent potential resource conflicts. Setting this value to No enables concurrent processing of all files set for backup, archive, or restore. Note: The No value is not recommended and is done at the user s own discretion. ps_group_objs Yes Specifies whether to group all session files for each PowerSnap operation, such as prepare or sync, snapshot or split, save or restore, or postpare. Setting this value to Yes will group all files from a certain LUN to one session, thus improving the NSR-R/3 performance for certain database disk or filesystem configurations, particularly if large numbers of files are processed by BRTools and PowerSnap with util_file_online. However, grouping files also reduces the potential parallelism for certain backup and restore suboperations, which in turn can reduce performance. Setting this value to Yes is also intended for use with BRTools 6.10 and later, offline and util_file_online, for example: brbackup -t offline -d util_file_online 101

102 Setting Variables in the PowerSnap Configuration File Setting Variables in the PowerSnap Configuration File 8 The PowerSnap parameters that do not directly belong to NSR-R/3 for SAP R/3 with Oracle must be set as variables in the attribute application information, in the client resource or in a user-defined PowerSnap configuration file, for example: nsrsapps.cfg. This file must be specified by its complete file pathname in the ps_opaque_pfilename parameter in the init<oracle_sid>.utl file. The configuration file must list a separate line for each variable setting by using the following format: var_name=var_value where: var_name is the variable name, such as RESTORE_TYPE_ORDER. var_value is the variable value, such as pit. Commonly-used PowerSnap environment variables are listed in Table 24 on page 102. For a complete list, refer to the appropriate NetWorker PowerSnap Module Installation and. PowerSnap variables that have settings equivalent to NSR-R/3 parameters are listed separately in Table 25 on page 104. Table 24. Commonly-Used PowerSnap Module Environment Variables (Part 1 of 3) PowerSnap Variables Description Default and Valid Values FRAME_IP Both IP addresses for the EMC CLARiiON Storage Processor nodes, separated by colons; for example, : If only one IP address is specified for the Storage Processor, PowerSnap operations fail. none 102

103 Chapter 8: PowerSnap Backups and Restores Table 24. Commonly-Used PowerSnap Module Environment Variables (Part 2 of 3) PowerSnap Variables Description Default and Valid Values NSR_DATA_MOVER NSR_MAX_STREAMS Mandatory if the PowerSnap backup uses a live backup host different from the PowerSnap client host (NSR_CLIENT). Specifies the hostname of the PowerSnap backup host. Optional. Specifies the maximum number of restore streams. Local host (default). The valid hostname of the secondary live backup host. Note: The NSR_CLIENT PowerSnap variable must always be set to the original brbackup or brarchive host, init<oracle_sid>.utl client value. Defaults to the parallelism value set in the init<oracle_sid>.utl file, or its default value of 8. An integer value. 8 NSR_PS_DEBUG_LEVEL Optional. PowerSnap debug level. NSR_PS_SAVE_ PARALLELISM Optional. Specifies the maximum number of concurrent save streams on the PowerSnap client host. Valid values are 0 to 9. Default value is 1. Defaults to the parallelism value set in the init<oracle_sid>.utl file, or its default value of 8. An integer value. NSR_SNAP_TYPE Optional. Specifies snapshot platforms and releases, when multiple snapshot platforms are used. Value should be a concatenated string, delimited by a colon (:). Default: emcclar 103

104 PowerSnap Use of Equivalent NSR-R/3 Parameters Table 24. Commonly-Used PowerSnap Module Environment Variables (Part 3 of 3) 8 PowerSnap Variables Description Default and Valid Values RESTORE_TYPE_ORDER Optional. Specifies the type of restore to be performed. Note: If multiple values are specified, each type of restore is attempted, in the order specified, until a restore operation is successful. One or more of the following values, with each value delimited from the others by a colon(:): pit - Specifies an instant (point-in-time) restore. conventional - Specifies a restore from secondary storage media. rollback - Specifies a rollback restore from a PIT copy. The default value is pit:conventional Note: For NSR-R/3, a rollback operation aborts if one of the following occurs: If brrestore file relocation is specified. If nonrequested files exist in the brrestore-requested filesystems. (These files could become corrupted after a rollback.) PowerSnap Use of Equivalent NSR-R/3 Parameters Some parameters used by PowerSnap are the same as those used in conventional backup and restore operations and are inherited from the init<oracle_sid>.utl file. Normally, these equivalent parameters should not be specified as variables in the PowerSnap configuration file. See Table 25 on page 104. Table 25. PowerSnap Use of Equivalent NSR-R/3 Parameters (Part 1 of 2) PowerSnap variables in the ps_opaque_pfilename parameter NSR_CLIENT NSR_SERVER Equivalent parameter in the init<oracle_sid>.utl file client (must match if NSR_CLIENT is used) server (must match if NSR_SERVER is used) 104

105 Chapter 8: PowerSnap Backups and Restores Table 25. PowerSnap Use of Equivalent NSR-R/3 Parameters (Part 2 of 2) PowerSnap variables in the ps_opaque_pfilename parameter NSR_GROUP NSR_SAVESET_EXPIRATION NSR_COMPRESSION NSR_PS_SAVE_PARALLELISM NSR_MAX_STREAMS NSR_DATA_VOLUME_POOL Equivalent parameter in the init<oracle_sid>.utl file group (must match if NSR_GROUP is used) expiration compress parallelism parallelism pool 8 105

106 Invoking PowerSnap Backup Processes Invoking PowerSnap Backup Processes 8 A PowerSnap for SAP R/3 with Oracle backup is started by automatically or manually invoking the scheduled NetWorker backup group on the NetWorker server. For information on how to invoke a scheduled backup, refer to the NetWorker PowerSnap Module Installation and. Note: A PowerSnap backup must not be started by directly invoking the client-side BRTools commands or SAPDBA. There are three types of scheduled PowerSnap backup processes, which are summarized in the following sections: "Instant Backup Processes" on page 106 "Immediate Live Backup Processes" on page 109 "Deferred Live Backup Processes" on page 112 Instant Backup Processes An instant backup creates a permanent snapshot copy of SAP R/3 with Oracle data that is retained on the primary storage system, where it is available to NSR-R/3 for performing instant restores or rollbacks. An instant backup is performed as follows: 1. At the backup start time, the main NetWorker service, nsrd, invokes the savegrp program to start the group s backup. 2. The savegrp program requests that the NetWorker client-side service, nsrexecd, on the SAP R/3 with Oracle Server host run the savefs program to validate the client. 3. If the savefs program succeeds, the savegrp program starts the PowerSnap program, nsrsnap, on the SAP R/3 with Oracle Server host. Otherwise, the backup fails. 4. If an existing snapshot needs to be removed (for example, it is due to be recycled according to the snapshot policy), the nsrsnap program invokes the nsrsnapck program, which removes both the snapshot from the storage system and the corresponding NetWorker file and media index entries. File and media index entries are removed only if the snapshot was not backed up to tape. Note: If the existing snapshot was not backed up to tape, there will be invalid records in the BRTools sapbackup catalog that do not correspond to any file index entries for the snapshots, because they were deleted by nsrsnapck processing. A subsequent brrestore attempt, without prior 106

107 Chapter 8: PowerSnap Backups and Restores verification, results in an expected "#NOT FOUND" message for all requested files. Run the brrestore -verify command after running Snapshot Policies that do not back up to tape. This message does not appear if you run brrestore for either of the following: The most recent backup. An earlier backup that had its snapshot backed up to the tape. 5. The nsrsnap program contacts the nsrexecd service, which starts the nsrsapsv program for the scheduled backup. 6. The nsrsapsv program sets the required environment variables and invokes the brbackup or brarchive program. 7. The brbackup or brarchive program starts NSR-R/3 s backint program for the SAP R/3 with Oracle backup. 8. The backint program contacts the PowerSnap master program, nsrpsd, to perform the instant backup. PowerSnap processes create the snapshot that comprises the backup. The nsrmmd service stores metadata (used only by the PowerSnap Module) about the snapshot on the media configured for the snapshot pool, typically on a file or disk type device. The nsrmmd service records tracking information about the point-in-time metadata in the NetWorker media database by using the nsrmmdbd service. The nsrindexd service records tracking information about each file name in the NetWorker client file index. The client index contains one entry per datafile. brbackup resp. brarchive records the backup entry in its sapbackup catalog. 9. The brbackup or brarchive program calls backint a second time to invoke backup processes for non-databasefiles, for example init<oracle_sid>.sap, that do not benefit from PowerSnap processing. This extra backup is configured to be a conventional backup without PowerSnap by the following setting in the init<oracle_sid>.utl parameter file: ps_exclude_xxx_bi_run_nums = 2 where xxx is backup or archive. For configuration details, see Table 23 on page

108 Instant Backup Processes If the Snapshot Policy resource specifies that the snapshot must be copied to secondary storage, the nsrsnap program performs the steps in "Deferred Live Backup Processes" on page 112. Note: The snapshot is not deleted from the primary storage. 11. The savegrp program backs up the NetWorker server bootstrap and SAP R/3 with Oracle client file indexes. Figure 6 on page 108 shows how the Oracle Server and NetWorker processes interact during a scheduled instant backup. Figure 6. Scheduled Instant Backup Processes SAP R/3 with Oracle Server (NetWorker Client) SAP R/3 with Oracle Datafiles Primary Storage PowerSnap Client (NetWorker Storage Node) Point-in-Time Copy of SAP R/3 with Oracle Datafiles NetWorker Server Client File Index data green fill indicates NSR-R3 elements PowerSnap processes PowerSnap processes tracking information nsrindexd Media Database backint nsrpsd nsrexecd nsrmmd brbackup or brarchive nsrsapsv nsrsnap violet fill indicates PowerSnap elements white fill indicates NetWorker and Oracle elements Snapshot Pool Media nsrmmdbd nsrd nsrsnapck nsrexecd interprocess communication savegrp savefs Start Here 108

109 Chapter 8: PowerSnap Backups and Restores Immediate Live Backup Processes An immediate live backup creates a temporary snapshot copy of the SAP R/3 with Oracle data on the primary storage, which is then immediately backed up to secondary storage, such as tape. The snapshot is then automatically deleted from the primary storage, and is not available for instant restores or rollbacks. This process involves the following sequence: 8 Note: The first seven steps are the same as those in "Instant Backup Processes" on page At the backup start time, the main NetWorker service, nsrd, invokes the savegrp program to start the group s backup. 2. The savegrp program requests that the NetWorker client-side service, nsrexecd, on the SAP R/3 with Oracle Server host run the savefs program to validate the client. 3. If the savefs program succeeds, the savegrp program starts the PowerSnap program, nsrsnap, on the SAP R/3 with Oracle Server host. Otherwise, the backup fails. 4. If an existing snapshot needs to be removed (for example, it is due to be recycled according to the snapshot policy), the nsrsnap program invokes the nsrsnapck program, which removes both the snapshot from the storage system and the corresponding NetWorker file and media index entries. File and media index entries are removed only if the snapshot was not backed up to tape. Note: If the existing snapshot was not backed up to tape, there will be invalid records in the BRTools sapbackup catalog that do not correspond to any file index entries for the snapshots, because they were deleted by nsrsnapck processing. A subsequent brrestore attempt, without prior verification, results in an expected "#NOT FOUND" message for all requested files. Run the brrestore -verify command after running Snapshot Policies that do not back up to tape. This message does not appear if you run brrestore for either of the following: The most recent backup. An earlier backup that had its snapshot backed up to the tape. 5. The nsrsnap program contacts the nsrexecd service, which starts the nsrsapsv program for the scheduled backup. 6. The nsrsapsv program sets the required environment variables and invokes the brbackup or brarchive program. 109

110 Immediate Live Backup Processes 8 7. The brbackup or brarchive program starts NSR-R/3 s backint program for the SAP R/3 with Oracle backup. 8. The backint program contacts the PowerSnap master program, nsrpsd, to perform the immediate live backup. PowerSnap processes create the snapshot, move the data to secondary storage, and then delete the snapshot from the primary storage. The nsrmmd service records tracking information about the secondary storage save sets in the NetWorker media database by using the nsrmmdbd service. The nsrindexd service records tracking information for each backup piece name and for each stored operating system datafile in the NetWorker client file index. The client index contains two entries per datafile. brbackup resp. brarchive records the backup entry in its sapbackup catalog. 9. The brbackup or brarchive program calls backint a second time to back up backup processes for non-databasefiles, for example init<oracle_sid>.sap, that do not benefit from PowerSnap processing. This extra backup is configured to be a conventional backup without PowerSnap by the following setting in the init<oracle_sid>.utl parameter file: ps_exclude_xxx_bi_run_nums = 2 where xxx is backup or archive. For configuration details, see Table 23 on page The savegrp program backs up the NetWorker server bootstrap and Oracle client file indexes. Figure 7 on page 111 shows how the Oracle server and NetWorker processes interact during a scheduled immediate live backup. 110

111 Chapter 8: PowerSnap Backups and Restores Figure 7. Scheduled Immediate Live Backup SAP R/3 with Oracle Server (NetWorker Client) SAP R/3 with Oracle Datafiles Primary Storage PowerSnap Client (NetWorker Storage Node) Point-in-Time Copy of SAP R/3 with Oracle Datafiles NetWorker Server Client File Index 8 data green fill indicates NSR-R3 elements PowerSnap processes PowerSnap processes tracking information nsrindexd Media Database backint nsrpsd nsrexecd nsrmmd brbackup or brarchive nsrsapsv nsrsnap violet fill indicates PowerSnap elements white fill indicates NetWorker and Oracle elements Secondary Storage Meduim nsrmmdbd nsrd nsrsnapck nsrexecd savegrp savefs interprocess communication Start Here 111

112 Deferred Live Backup Processes Deferred Live Backup Processes 8 A deferred live backup creates a permanent snapshot copy of the SAP R/3 with Oracle data on the primary storage system, which is then backed up to secondary storage system, such as tape. The snapshot is retained on the primary storage for the period specified by either of these snapshot policy attributes for the client s Group resource: SnapShot Expiration Policy Retain Snapshots A deferred live backup will run only automatically as part of a scheduled NSR-R/3 backup. For more information, refer to the appropriate NetWorker PowerSnap Module Installation and. A scheduled deferred live backup uses the following process: 1. The nsrsnap program invokes the PowerSnap processes to copy the snapshot to secondary storage. Note: The snapshot is not deleted from the primary storage. 2. The nsrmmd service records tracking information about the deferred live backup in the NetWorker media database by using the nsrmmdbd service. 3. The nsrindexd service records tracking information for each stored operating system datafile in the NetWorker client file index. Figure 8 on page 113 shows how the Oracle Server and NetWorker processes interact during a scheduled deferred live backup. 112

113 Chapter 8: PowerSnap Backups and Restores Figure 8. Scheduled Deferred Live Backup SAP R/3 with Oracle Server (NetWorker Client) SAP R/3 with Oracle Datafiles Primary Storage PowerSnap Client (NetWorker Storage Node) Point-in-Time Copy of SAP R/3 with Oracle Datafiles NetWorker Server Client File Index 8 Start Here interprocess communication PowerSnap processes tracking information data nsrindexd Media Database nsrsnap (at end of savegrp) nsrexecd nsrmmd violet fill indicates PowerSnap elements white fill indicates NetWorker elements Secondary Storage Medium nsrmmdbd 113

114 Querying PowerSnap Backup Records Querying PowerSnap Backup Records 8 The NetWorker server records information about each backup in its online indexes. The index entry for NSR-R/3 for SAP R/3 with Oracle PowerSnap backup is stored in the NetWorker client file index for the SAP R/3 with Oracle Server host, under the new "saporacle" namespace (instead of the "backup" namespace, which is used for regular NSR-R/3 for SAP R/3 with Oracle backups). For NetWorker release 7.1 or later, you can query the online NetWorker indexes by using the NetWorker commands, nsrinfo and mminfo. To query the NetWorker client file index, enter the nsrinfo command. This displays BRTools file BIDs, for example: nsrinfo [-v] -n saporacle -s NetWorker_server client where client is your SAP R/3 with Oracle server hostname. To query the NetWorker media database, enter the mminfo command. For example: mminfo [-v] [-N backint:<oracle_sid>:ps:] -s NetWorker_server -c client where client is your SAP R/3 with Oracle server hostname. NSR-R/3 for SAP R/3 with Oracle PowerSnap save sets all have the following save set format: backint:<oracle_sid>:ps: For more information on these NetWorker commands, refer to the NetWorker Command Reference Guide and the online man pages. 114

115 Chapter 8: PowerSnap Backups and Restores Invoking PowerSnap Restore Processes NSR-R/3 for SAP R/3 with Oracle restores are performed with either the brrecover command, the brrestore command or the SAPDBA interface, each of which ultimately calls NSR-R/3 s backint program. For PowerSnap restores, the backint program interacts with both the PowerSnap and NetWorker software. 8 For descriptions of the processes involved, see the following: "Instant Restore and Rollback Processes" on page 115 "Restore from Secondary Storage Processes" on page 117 Instant Restore and Rollback Processes Both instant restores and rollbacks use the permanent snapshot created by an instant backup or as part of a deferred live backup. For an instant restore, the snapshot copy is mounted and the files are copied as needed. For a rollback, the entire snapshot is moved to the source destination by using the appropriate commands for the specific platform, if supported by the NetWorker PowerSnap Module. Instant restores and rollbacks use the following process: 1. NSR-R/3 s backint program verifies the existence of the requested files versions through the nsrindexd service. 2. The backint program contacts the PowerSnap master program, nsrpsd, on the Oracle Server host. 3. The nsrpsd program works with other PowerSnap and NetWorker programs to access the instant backup copy on the primary storage, and to perform the restore operation. PowerSnap processes retrieve the snapshot metadata saveset by using the nsrmmd and nsrmmdbd processes. PowerSnap processes do one of the following, depending on the RESTORE_TYPE_ORDER setting, see Table 24 on page 102: For an instant restore, mount the snapshot and copy the files into a destination requested by NSR-R/3. For a rollback, execute the command (specific to the primary storage system) to move the entire snapshot unit into the source destination. 115

116 Instant Restore and Rollback Processes 8 Once the required SAP R/3 with Oracle files are restored, a database administrator can complete the standard SAP R/3 with Oracle database recovery. Figure 9 on page 116 shows how the Oracle server and NetWorker processes interact during an instant restore or rollback. Figure 9. Instant Restore or Rollback SAP R/3 with Oracle Server (NetWorker Client) SAP R/3 with Oracle Datafiles Primary Storage PowerSnap Client (NetWorker Storage Node) Point-in-Time Copy of SAP R/3 with Oracle Datafiles NetWorker Server Start Here data (for details on data flow, see description) Client File Index tracking information brrestore/ brrecover PowerSnap module PowerSnap module nsrindexd backint nsrpsd nsrexecd nsrmmd Media Database nsrexecd green fill indicates NSR-R3 elements violet fill indicates PowerSnap elements white fill indicates NetWorker and Oracle elements SnapShot Pool Media nsrmmdbd interprocess communication nsrd 116

117 Chapter 8: PowerSnap Backups and Restores Restore from Secondary Storage Processes A restore of a PowerSnap backup from secondary storage uses the following process: 1. NSR-R/3 s backint program verifies the existence of the requested files versions through the nsrindexd service. 2. The backint program contacts the PowerSnap master program, nsrpsd, on the Oracle Server host. 3. The nsrpsd program works with other PowerSnap and NetWorker programs to retrieve the data from secondary storage, and perform the restore operation. PowerSnap processes restore the files (save sets) into a destination requested by NSR-R/3. The processes use the nsrmmd and nsrmmdbd programs to do the following: Determine which media contain the requested save sets. Read the backup volumes. 4. Once the required SAP R/3 with Oracle files are restored from the backup volumes, a database administrator can complete the standard SAP R/3 with Oracle database recovery. Figure 10 on page 118 shows how the Oracle Server and NetWorker processes interact during a restore from secondary storage

118 Restore from Secondary Storage Processes Figure 10. Restore from Secondary Storage 8 SAP R/3 with Oracle Server (NetWorker Client) Start Here Primary Storage Oracle Datafiles data PowerSnap Client (NetWorker Storage Node) NetWorker Server Client File Index brrestore/ brrecover PowerSnap module tracking information nsrindexd backint nsrexecd green fill indicates NSR-R/3 elements nsrpsd violet fill indicates PowerSnap elements white fill indicates NetWorker and Oracle elements nsrmmd Secondary Storage Media Database nsrmmdbd interprocess communication nsrd 118

119 Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore This appendix provides sample syntax and options for the SAP R/3 Release 4.6B brbackup, brarchive, brrecover and brrestore commands, which are commonly used for NSR-R/3 operations. For a complete listing of the syntax and options used with the brbackup, brarchive, brrecover and brrestore commands, refer to the appropriate SAP documentation. Note: The commands can be used from any command prompt. This appendix includes the following sections: "Syntax and Options for brbackup and brarchive Commands" on page 120 "Syntax and Options for brrecover Command" on page 123 "Syntax and Options for brrestore Command" on page

120 Syntax and Options for brbackup and brarchive Commands Syntax and Options for brbackup and brarchive Commands A NSR-R/3 uses the following brbackup command syntax and options: brbackup [-c force][-d {util_file util_file_online rman_util}] [-m {all tablespace_name file_id file_id_range}] [-p profile][-r parameter_file] [-t {online offline offline_force offline_standby}] [-u user/password][-w -verify] Command options in brackets ([ ]) are optional. At least one of the command options in braces ({ }) must be included in the command. NSR-R/3 uses the following brarchive syntax and options: brarchive [-c force][-d {util_file util_file_online rman_util}] [-f stop][-m delay_time][-p profile][-r parameter_file][-s save] [-u user/password][-w -verify] Table 26 on page 120 lists the options available with the brbackup and brarchive commands. Table 26. The brbackup and brarchive Command Options (Part 1 of 3) Option Description -c force Suppresses most of the confirmation messages that interrupt the backup process. -d util_file util_file_online rman_util Specifies that NSR-R/3 is used for the backup or archive process. This option is not required because it is set during configuration (see "Task 4: Configure the Backup and Restore Utility" on page 42.) -f stop Instructs brarchive to wait for the next offline redo log file written by Oracle, and then send it to backint for archiving. -m all Sends the entire database to backint for backup. -m tablespace_name Sends a single tablespace to backint for backup. 120

121 Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore Table 26. The brbackup and brarchive Command Options (Part 2 of 3) Option Description -m file_id Sends a datafile with an associated Oracle file ID to backint for backup. The following file ID formats are acceptable: Specify control files as ID 0. Specify online redo log files as the following ID: 0 group_number where group_number is the group number associated with the redo log files. Specify all online redo log files as ID 00. A -m file_id_range Sends datafiles within a specified Oracle file ID range to backint for backup. -m delay_time Specifies the delay time between Oracle creating the offline redo log file and sending datafiles to the database in standby mode. -p profile Specifies a profile other than the default, init<oracle_sid>.sap. The nondefault profile used for BRTools must specify the settings outlined in "Task 4: Configure the Backup and Restore Utility" on page 42. -r parameter_file Specifies the parameter file that NSR-R/3 uses during the backup or archive process. This option is required only if you have created additional parameter files. Otherwise, this option is not required, because init<oracle_sid>.utl is set as the default parameter file during configuration. For details on setting the default parameters, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. -s saveset Specifies the number of members in save sets (1, 2, 3, 4, tablespace, or all). -t online Instructs brbackup and NSR-R/3 to perform an online backup of the Oracle database. To reduce the number of redo logs that Oracle generates, use this option with the -d util_file_online option. 121

122 Syntax and Options for brbackup and brarchive Commands Table 26. The brbackup and brarchive Command Options (Part 3 of 3) Option Description -t offline Specifies to brbackup and NSR-R/3 that the Oracle database is shut down. A -t offline_force Instructs the SAP R/3 system to shut down the Oracle database immediately and tell brbackup to send data to backint for backup. -t offline_standby Instructs the SAP R/3 system that the database in standby mode is ready for backup. -u user/password Specifies the Oracle database administrator s user name and password. -w -verify Instructs brbackup or brarchive to perform a verification after a successful backup of the data. So backint has to be called again with the option -f inquire. 122

123 Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore Syntax and Options for brrecover Command NSR-R/3 uses the following brrecover syntax and options: brrecover [-b [log_name last]][-c [force]][-i days] [-own own_name own_name_list][-p profile][-pit yyyy-mo-dd hh.mi.ss] [-r parfile][-scn scn][-seq seq_nr][-seq1 seq_nr] [-t complete dbpit tspit reset restore apply disaster] [-tsp tsp_name tsp_name_list][-u [user[/password]] /] Command options in brackets ([ ]) are optional. Table 28 on page 126 lists the options available with the brrecover command. A Table 27. The brrecover Command Line Options (Part 1 of 3) Option Description -b log_name last Specifies a brbackup run from which to restore the database files. log_name: brrecover restores database files from the brbackup backup with the log name entered in log_name as "bencoded_timestamp.function_id". last (default): brrecover restores the files from the last successful database backup. -c [force] Specifies whether the recovery is attended (default) or unattended. In unattended mode, brrecover only stops at menus. At other prompts, it continues processing with the default value. force: all confirmation messages are suppressed. In addition, brrecover automatically selects default choices and accepts default input values in menus. Note: Do not use the option -c force when recovering a production database. In this case, follow the brrecover prompts and menus, and carefully check the default choices and input values suggested by brrecover. -i days Specifies the interval in which brrecover searches for backups. 123

124 Syntax and Options for brrecover Command Table 27. The brrecover Command Line Options (Part 2 of 3) Option -own own_name own_name_list Description Specifies the SAP owner for a tablespace point-in-time (PIT) recovery. A -p profile Defines the profile name. Default: init<oracle_sid>.sap -pit yyyy-mo-dd hh.mi.ss Specifies the point in time to which brrecover recovers the database or tablespaces for a point-in-time (PIT) recovery. -r parfile Defines the backint parameter file. Default: no parameter file. -scn scn -seq seq_nr -seq1 seq_nr -t complete dbpit tspit reset restore apply disaster Specifies the last Oracle system change number for a point-in-time (PIT) recovery. Specifies the sequence number of the last redo log file for a point-in-time (PIT) recovery. Specifies the sequence number of the first redo log file for applying offline redo log files using the command option -t apply. Specifies the type of recovery. complete: complete database recovery dbpit: database point-in-time recovery tspit: tablespace point-in-time recovery reset: whole database reset restore: restore of individual backup files apply: apply offline redo log files (that is, archivelogs) disaster: disaster recovery 124

125 Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore Table 27. The brrecover Command Line Options (Part 3 of 3) Option -tsp tsp_name tsp_name_list Description Specifies the tablespaces to be recovered in a tablespace point-in-time (PIT) recovery. -u user/password / Defines the user name and password with which brrecover connects to the database. The user must have SYSDBA privileges. Default: system/default_password A 125

126 Syntax and Options for brrestore Command Syntax and Options for brrestore Command A NSR-R/3 uses the following brrestore syntax and options: brrestore [[-c [force]][-d {util_file util_file_online rman_util}] [-m {all full table_space_name file_id file_id_range generic_path}] [-p profile][-r parameter_file][-w -verify] Command options in brackets ([ ]) are optional. At least one of the command options in braces ({ }) must be included in the command. Table 28 on page 126 lists the options available with the brrestore command. Table 28. The brrestore Command Line Options (Part 1 of 2) Option Description -c [force] Suppresses most of the confirmation messages that interrupt the restore process. -d util_file util_file_online rman_util Specifies that NSR-R/3 is used for the restore process. This option is not required because it is set during configuration (see "Task 4: Configure the Backup and Restore Utility" on page 42). -m all Requests the backint program to restore all tablespaces and associated files. -m full Requests the backint program to restore the entire database instance. -m table_space_name Requests the backint program to restore a single tablespace. -m file_id Requests the backint program to restore a datafile with an associated Oracle file ID. The following file ID formats are acceptable: Specify control files as ID 0. Specify online redo log files as the following ID: 0 group_number where group_number is the group number associated with the redo log files. Specify all online redo log files as ID

127 Appendix A: Commonly Used Command Options for brbackup, brarchive, brrecover, and brrestore Table 28. The brrestore Command Line Options (Part 2 of 2) Option Description -m file_id_range Requests the backint program to restore datafiles within a specified Oracle file ID range. -m generic_path Requests the backint program to restore all the datafiles whose names start with that full path. The path must contain at least the SAPDATA_HOME directory and an additional generic specification (for example, sapdata<n> ). If the generic path is a directory, you can also restore one or more files from this directory by additionally specifying one or more filenames. A -p profile Specifies a profile other than the default init<oracle_sid>.sap profile. A nondefault profile must specify the settings outlined in "Task 4: Configure the Backup and Restore Utility" on page 42. -r parameter_file Specifies the parameter file that NSR-R/3 uses during the restore process. This option is required only if you have created additional parameter files. Otherwise, this option is not required, because init<oracle_sid>.utl is set as the default parameter file during configuration. For details on setting the default parameters, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. -w -verify Instructs brrestore to perform only a verification of the data. So backint will be called with the option -f inquire. 127

128 Syntax and Options for brrestore Command A 128

129 Appendix B: Environment Variables for RMAN To configure the RMAN utility for backup and restore, NetWorker software uses specific NSR_* environment variables that are described in this appendix. This appendix contains the following sections: "Setting the Environment Variables" on page 129 "Environment Variable Definitions" on page 130 Setting the Environment Variables The environment variables are set with the rman_parms parameter in the SAP initialization file (also called the utilities profile), init<oracle_sid>.sap, which is typically located in the directory $ORACLE_HOME/dbs For instructions on configuring the RMAN utility for NSR-R/3, see "Configuring RMAN as the Backup and Restore Utility" on page

130 Environment Variable Definitions Environment Variable Definitions Table 29 on page 130 lists all the NSR_* environment variables that can be used with NSR-R/3. Table 29. NSR_* Environment Variables (Part 1 of 6) Variable Description Default and Valid Values B NSR_CLIENT NSR_COMPRESSION Recommended for a backup of Oracle running on a cluster, Oracle Parallel Server (OPS), or Real Application cluster (RAC) system. Recommended for all restores. Specifies the NetWorker Client resource to use for a backup or restore session. Might be needed for disaster recovery. Optional. Specifies whether or not the NetWorker software performs compression on the backup data. The physical host on which the session runs (default). A valid NetWorker client hostname. FALSE (default) = The NetWorker software performs no compression. TRUE = The NetWorker software performs compression. 130

131 Appendix B: Environment Variables for RMAN Table 29. NSR_* Environment Variables (Part 2 of 6) Variable Description Default and Valid Values NSR_DATA_VOLUME_ POOL NSR_DATA_VOLUME_ POOL1 NSR_DATA_VOLUME_ POOL2 NSR_DATA_VOLUME_ POOL3 Mandatory if using set duplex command (set to 1, 2, 3, or 4). Specifies the name of the volume pool to use for the Oracle backup, including a duplexed Oracle backup. In the case of proxy backups, specifies the volume pool for live backups only (backups to secondary storage only). Note: For a scheduled backup, the NSR_DATA_VOLUME_POOL setting takes precedence over any pool associated with the scheduled backup group. Mandatory if using set duplex command (set to 2, 3, or 4). Specifies the name of the volume pool to use for a duplexed Oracle backup. Mandatory if using set duplex command (set to 3 or 4). Specifies the name of the volume pool to use for a duplexed Oracle backup. Mandatory if using set duplex command (set to 4). Specifies the name of the volume pool to use for a duplexed Oracle backup. The most appropriate pool, selected by the NetWorker server (default). A valid NetWorker pool name. The name must be different from the name used by another NSR_DATA_ VOLUME_POOL* variable. Undefined (default). A valid NetWorker pool name. The name must be different from the name used by another NSR_DATA_ VOLUME_POOL* variable. Undefined (default). A valid NetWorker pool name. The name must be different from the name used by another NSR_DATA_ VOLUME_POOL* variable. Undefined (default). A valid NetWorker pool name. The name must be different from the name used by another NSR_DATA_ VOLUME_POOL* variable. B 131

132 Environment Variable Definitions Table 29. NSR_* Environment Variables (Part 3 of 6) Variable Description Default and Valid Values B NSR_DEBUG_FILE NSR_DEBUG_LEVEL NSR_GROUP Optional. Enables debugging by specifying the complete pathname of the log file on the Oracle Server that receives debugging information during a proxy or nonproxy backup or restore. Only used for debugging the NSR-R/3 for Oracle media management library (MML). Optional. Controls the amount of debugging information that NSR-R/3 for Oracle writes to the debug log file, which is specified by NSR_DEBUG_FILE. The debug level limits only the amount of debug information generated by the three functions sbtread(), sbtwrite(), and sbtpcstatus() that are called most often during backups and restores. All the debug messages for other functions are always written to the log file, regardless of the debug level. Optional. Use for a manual backup only. Specifies the NetWorker group to use for a backup session. Used by the NetWorker server to select the volume pool for the manual backup. Note: Do not set this variable for a scheduled backup. Undefined (default). The valid pathname of the debug file to use on the Oracle Server. Note: If undefined, no debugging information is generated. If a file with the specified pathname cannot be created, debugging information is either directed to the default location or not generated. 0 (default) = Only operational messages are written for the sbtread(), sbtwrite(), and sbtpcstatus() functions. No entry or exit messages are written for the functions. 1 = Only entry and exit messages are written for the sbtread(), sbtwrite(), and sbtpcstatus() functions. No operational messages are written for the functions. 3 = All debug messages for all the functions are written to the log file. Default group (default). A valid NetWorker backup group name. Note: A NetWorker Group resource must be configured for the specified backup group. 132

133 Appendix B: Environment Variables for RMAN Table 29. NSR_* Environment Variables (Part 4 of 6) Variable Description Default and Valid Values NSR_NO_BUSY_ ERRORS NSR_NWPATH NSR_PROXY_PFILE Optional. Specifies whether a scheduled backup fails immediately when the NetWorker server is busy or waits for the NetWorker server to accept the connection. Note: For proxy Oracle backups, this variable is always set to FALSE. Mandatory when removing a backup from the NetWorker server if both: The nsrmm binary is in a nondefault location; and The /nsr/res/nwora.res file does not contain the correct location of the NetWorker client binaries. a Specifies the complete pathname of the directory containing the nsrmm binary. Supported only for a proxy Oracle backup or restore. Mandatory if setting PowerSnap variables in a configuration file. Specifies the complete pathname of a configuration file that contains PowerSnap variable settings for a proxy Oracle backup or restore. FALSE (default) = The scheduled backup waits for the NetWorker server to accept the connection. TRUE = The scheduled backup fails immediately when the NetWorker server is busy. The platform-specific default location of the NetWorker client binaries (default). A valid pathname of the nsrmm binary directory, for example, /usr/local/bin. Undefined (default). A valid pathname of the configuration file. Note: If undefined or an invalid pathname, variable settings in the preferred configuration file are ignored. B 133

134 Environment Variable Definitions Table 29. NSR_* Environment Variables (Part 5 of 6) Variable Description Default and Valid Values B NSR_SAVESET_ BROWSE NSR_SAVESET_ EXPIRATION NSR_SAVESET_ RETENTION Mandatory if setting a nondefault browse policy for a manual Oracle backup with NetWorker server 6.x or later. Specifies the date when the entry for the backup is to be removed from the NetWorker client file index. Note: This variable has an effect only for an Oracle backup with NetWorker server 6.x or later. For a scheduled Oracle backup with NetWorker server 6.x or later, this variable overrides the Browse Policy attribute setting in the NetWorker Client resource. Not recommended. This variable from release 3.5 of NSR-R/3 for Oracle has been replaced by the NSR_SAVESET_RETENTION variable. Mandatory if setting a nondefault retention policy for a manual Oracle backup with NetWorker server 6.x or later. Specifies the date when the save set becomes recyclable. Note: This variable has an effect only for an Oracle backup with NetWorker server 6.x or later. For a scheduled Oracle backup with NetWorker server 6.x or later, this variable overrides the Retention Policy attribute setting in the NetWorker Client resource. The most appropriate policy for the client, as selected by the NetWorker server (default). A valid date in nsr_getdate(3) format. If this variable is used, its value is assigned to the NSR_SAVESET_RETENTION variable. The most appropriate policy for the client, as selected by the NetWorker server (default). A valid date in nsr_getdate(3) format. 134

135 Appendix B: Environment Variables for RMAN Table 29. NSR_* Environment Variables (Part 6 of 6) Variable Description Default and Valid Values NSR_SERVER Mandatory for a manual backup if the NetWorker server host is different from the Oracle Server host. Recommended for a local manual backup. Specifies the hostname of the NetWorker server to perform the Oracle backup. The local physical host (default). A valid NetWorker server name. a. Instead of setting the NSR_NWPATH variable in the RMAN script, a line containing NSR_NWPATH=nsrmm_dirpath can be added to the /nsr/res/nwora.res file, where nsrmm_dirpath is the complete pathname of the directory containing the NetWorker nsrmm program. For example: NSR_NWPATH=/opt/nsr B 135

136 Environment Variable Definitions B 136

137 Appendix C: Troubleshooting This appendix contains troubleshooting tips and NSR-R/3 error messages. It also provides suggestions to help diagnose and fix problems with NSR-R/3 during backup and restore sessions. This appendix includes the following sections: "Verifying the Release Information" on page 137 "Generating Diagnostic Logs" on page 138 "Backup and Restore Problems" on page 138 "Regular Session Error Messages" on page 140 "Fatal Error Messages" on page 143 Verifying the Release Information When making queries or requests to Customer Support, provide specific information for the NSR-R/3 software you are using. To verify the release information for your NSR-R/3 installation, use the appropriate command or procedure as follows: On Solaris, enter the following commands as the root user: pkginfo -l SMAWnwr3 pkgparam -v SMAWnwr3 mcs -p filename sort -u 137

138 Generating Diagnostic Logs On Linux, enter the following commands as the root user: ident filename sort -u rpm -q -i nsrr3 where filename is the name of a NSR-R/3 binary file, for example backint or nsrsapsv. Generating Diagnostic Logs To generate backint diagnostic logs, set the following values in your init<oracle_sid>.utl file: debug_level = 5 nsr_debug_msg = yes verbose = yes Note: Debug level is intended for testing and technical support diagnostics only. C Backup and Restore Problems Table 30 on page 138 provides guidelines for solving problems that may occur during a NSR-R/3 backup or restore process. Table 30. NSR-R/3 Backup or Restore Problems (Part 1 of 2) Problem Data is not being backed up to the NetWorker server. Data is not being backed up using the settings in the Client resource on the NetWorker server. Possible Reason or Solution Ensure that the SAP initialization file, init<oracle_sid>.sap, is configured to use NSR-R/3. For information, see "Task 4: Configure the Backup and Restore Utility" on page 42. During a backup, NSR-R/3 does not use most of the settings in the Client resource, except for the save set name and backup schedule. The client settings must be specified in the init<oracle_sid>.utl file on the SAP R/3 server running Oracle. For information, see "Task 3: Configure the NSR-R/3 Parameters" on page

139 Appendix C: Troubleshooting Table 30. NSR-R/3 Backup or Restore Problems (Part 2 of 2) Problem Possible Reason or Solution The bootstrap notification report was not printed to the printer specified in the Group resource on the NSR-R/3 server. Bootstrap notification reports are not generated after a manual NSR-R/3 backup. To generate a bootstrap notification report, see "Backing Up the Client File Indexes and Bootstrap" on page 61. Online backup of an Oracle tablespace is taking a long time. Following a backup, the parallelism setting in the backint<oracle_sid>.log is different from the setting in the parameter file init<oracle_sid>.utl. A specified backup of an Oracle directory failed. Oracle creates more online redo logs during an online backup than during an offline backup. This might prolong the online backup. The parallelism setting is adjusted by backint during the backup session depending on other parameters, for example, when the number of files within the backup session is lower than the server parallelism setting. NSR-R/3 does not support backing up directories. Specify each database object within the directory to back up and then perform the backup. C You are unable to view the files backed up to the NetWorker server from the SAPDBA program on the SAP R/3 server running Oracle. Ensure that the SAP user s operating system authorization has the appropriate permission to access the NetWorker server. You are unable to restore the most recent version of the file that was backed up. When a restore is initiated within a certain time frame that expired or otherwise is not available, brrestore restores files from previous backups, depending on whether the prev_bk_restore parameter is set to Yes. For more information, see "prev_bk_restore" on page 39. Ensure that the SAP user s operating system authorization has the appropriate permission to access the NetWorker server. 139

140 Regular Session Error Messages Regular Session Error Messages This section discusses error messages that may occur during a backup, restore, or inquire session, but which do not prevent the session from continuing. Table 31 on page 140 indicates possible error messages that might appear in the backint<oracle_sid>.log file. Table 31. NSR-R/3 Regular Session Error Messages (Part 1 of 3) Error Message Description Solution C Error when sending out Error: filename is not a regular file, raw partition, or directory. Error: save symlinks had errors Error: unexpected inquire case. NSR-R/3 could not write a notification to the command line mail utility specified in the error message. The backint program does not support the file type (such as a symbolic link or a named pipe). During the process of saving symbolic links, backint ran out of memory and could no longer add symbolic links to its list. The files requested in the input file do not match the SAP R/3 backint specification. Valid file specifications include: #NULL is specified for a backup ID, with or without a filename A filename is specified with a backup ID. A backup ID is specified without a filename Check the usage of the notify parameters in the init<oracle_sid>.utl file. See "Task 3: Configure the NSR-R/3 Parameters" on page 33. Check the filename to see what type of file is being backed up. If brbackup is requesting backup of special files, contact SAP support. This situation is unlikely to occur. The computer may be low on memory, or the program may contain a logic error. If this situation recurs, contact Fujitsu Siemens Computers Technical Support. Check the backup input file generated by brbackup. If the input file generated appears to be the wrong format, contact SAP support. 140

141 Appendix C: Troubleshooting Table 31. NSR-R/3 Regular Session Error Messages (Part 2 of 3) Error Message Description Solution Ignoring, use format param=value Uncommented text in the init<oracle_sid>.utl parameter file does not conform to param = value and is ignored. For information on setting the parameters in the init<oracle_sid>.utl file, see "Task 3: Configure the NSR-R/3 Parameters" on page 33. Lookup failed on filename (backup_id) The backint program was trying to look up a filename and/or backup ID in the client file index, but the attempt to query the index failed. The next message should explain why the index query failed. Check the error message to determine why the attempt to query the index failed. If this message does not explain the problem, and future inquire or restore requests fail, contact Fujitsu Siemens Computers Technical Support. Pathname nothing found in index The specified file was not found in the NetWorker client file index. Ensure that the file was actually backed up in a previous run of backint. If brbackup specifies filenames that were never backed up, check the SAP R/3 installation. C Process_ID File filename not found in index, no attempt to recover will be made The NetWorker software did not save the filename specified for recovery and the filename does not appear in the client file index. Check the filename specified to see if the name is correct. Check previous backups to determine whether the file was actually saved in a previous backup. Unable to build command line. The backint command was unable to build a command line for a subprocess because the program ran out of memory. This situation is unlikely to occur. The computer may be low on memory, or the program may contain a logic error. If this situation recurs, contact Fujitsu Siemens Computers Technical Support. 141

142 Regular Session Error Messages Table 31. NSR-R/3 Regular Session Error Messages (Part 3 of 3) Error Message Description Solution Unable to find pid process ID in list of files The backint program is checking the status of a subprocess that was created to save individual files. However, the subprocess ID does not match any of the expected process IDs. Check the rest of the messages from the backup process to ensure that everything was saved. In particular, check for the message x of y files saved at time. If all of the files were not saved, retry the backup. Unable to query with savetime and filename both absent The backint program was trying to find a file in the client file index, but neither the save time nor the filename were provided. Check the input file to see if any file information is specified incorrectly. If this situation persists, contact Legato Technical Support. C Warning: Unknown parameter, parameter_name The parameter indicated is not a valid NSR-R/3 parameter. For valid parameters, see "Task 3: Configure the NSR-R/3 Parameters" on page

143 Appendix C: Troubleshooting Fatal Error Messages This section discusses fatal error messages and provides information as to why a particular backup, restore, or inquire session fails. Table 32 on page 143 indicates any fatal error messages that begin with the following line: Backint exiting at time_stamp with fatal error Table 32. NSR-R/3 Fatal Error Messages (Part 1 of 6) Error Message Description Solution BACKUP: Bad input line: line One of the lines in the input file had a bad format. There should be only one or two specifications on each input line (filename and size, if it is a special file). Check the input file brbackup generated to make sure it has the correct format. If not, and this error keeps occurring, contact SAP technical support. Bad function on input line, function The function indicated cannot be performed as it is either an invalid function or you are attempting to use unsupported options. NSR-R/3 can only be invoked through the SAPDBA program or associated commands. For information on supported functions refer to the -f option in SAP s BC-BRI BACKINT Interface for Oracle documentation. C Can not reopen filename as stderr The backint program was unable to open a log file for writing. Check the permissions on the file listed in the message, as well as the permissions on the directory. Cannot connect to server: error The backint program was unable to connect to the NetWorker server to start reading the media database. Ensure that the correct NetWorker server is specified. Check the log file to see if any other messages refer to this problem. Cannot start session with server: error The backint program was unable to start reading the media database on the NetWorker server. Ensure that the correct NetWorker server is specified. Check the log file to see if any other messages refer to this problem. 143

144 Fatal Error Messages Table 32. NSR-R/3 Fatal Error Messages (Part 2 of 6) Error Message Description Solution Checking for deletion of semaphore file: error The existence of the semaphore file could not be confirmed because of a system error. Check to see if the.switch.sem file is still in the SAPBACKUP directory. If so, delete it before running the SAP R/3 backup again. Creating directive file: error The directive file for NetWorker software to use cannot be created. This directive file is created so the NetWorker software can process files with the correct attributes. Check the directory where the directive file is being created, specified by the backint_tmpdir parameter in NSR-R/3 s parameter file, to ensure files can write to it. C Error: Too many symlinks There are too many symbolic links to save (more than 100). If the list of database files to be backed up contains more than 100 symbolic links, consider restructuring the directories to eliminate the extra symbolic links. File was filename, lstat error NSR-R/3 tried to get information for a symbolic link that does not exist or NSR-R/3 cannot access because permission is denied. Check the file to see that it exists and is a valid symbolic link. Improperly formatted backup id: backup ID The backup ID is incorrect. It should specify either a number or the word #NULL. Check the input file brrestore generated to ensure that it has the correct format. If not, and this error keeps occurring, contact SAP technical support. INQUIRE: Bad input line: line One of the lines in the input file had a bad format. There should be only one or two specifications on each input line (backup ID or #NULL an optional filename). Check the input file brrestore generated to ensure that it has the correct format. If not, and this error keeps occurring, contact SAP technical support. Interrupted... backint exiting The NSR-R/3 backint program was interrupted during a backup, restore, or inquire session. This error usually occurs due to a keyboard error. 144

145 Appendix C: Troubleshooting Table 32. NSR-R/3 Fatal Error Messages (Part 3 of 6) Error Message Description Solution Non-recursive directory backup is not supported at this time You have attempted to back up a directory. The backup of directories is not supported. Select specific database objects to back up from the SAPDBA program and restart the backup process. Not enough save sets, please increase savesets setting in.utl file The number or size of the save sets to be backed up exceeds the current settings for the number of save sets allowed or the maximum save set size allowed. Increase the number of save sets. or the maximum save set size. To configure the parameter for the number of save sets, see "savesets" on page 40. To configure the parameter for maximum save set size, see "ss_size_max" on page 41. Opening input file: error Opening output file: error The input file, which lists all files to be backed up or restored, could not be opened. It may not exist, or it may not have read permissions. The output file could not be opened for the reason specified. Ensure that the input file exists and is readable. Check the permissions on the output file and directory, and check for sufficient disk space to create a new file. C Opening parameter file Unable to open the backint parameter file, init<oracle_sid>.utl. Attempt to open the parameter file for backint in any text editor. If you are unable to open the parameter file, replace it with the original file from the NSR-R/3 CD. Opening switch list file for online backup: error When performing an online backup, backint tries to open a file to communicate with brbackup. This file could not be opened for the reason given. Check to see if the.switch.lis file exists in the SAPBACKUP directory. If so, check the permissions on this file. Normally, NSR-R/3 deletes and re-creates this file for every tablespace to be switched into backup mode. 145

146 Fatal Error Messages Table 32. NSR-R/3 Fatal Error Messages (Part 4 of 6) Error Message Description Solution Opening switch log file for online backup: error Opening switch semaphore file for online backup: error When performing an online backup, backint expects brbackup to provide a log file of the tablespaces that were switched into or out of backup mode. When performing an online backup, backint tries to open a file to communicate with brbackup. This file could not be opened for the reason given. Check to see if the.switch.log file is still in the SAPBACKUP directory. If so, delete it before running the SAP R/3 backup again. Check to see if the.switch.sem file exists in the SAPBACKUP directory. If so, check this file s permissions. Normally, NSR-R/3 deletes and re-creates this file for every tablespace to be switched into backup mode. C ORACLE_HOME not set. recover_start: cannot connect to server server_name The ORACLE_HOME environment variable must be set. The backint program was unable to connect to the NetWorker server to start the recovery process. Set the ORACLE_HOME environment variable to the correct directory. Ensure that the correct NetWorker server is specified. Check the log file to see if any other messages refer to this problem. RESTORE: Bad input line: line One of the lines in the input file had a bad format. There should be only two or three specifications on each input line (backup ID or #NULL, a filename, and an optional destination directory). Check the input file brrestore generated to make sure it has the correct format. If not, and this error keeps occurring, contact SAP technical support. Semaphore file not deleted in time seconds When performing an online backup, the SAP R/3 module was waiting for the switch semaphore file to be deleted. After waiting some number of seconds, the switch semaphore file still was not deleted. If brbackup appears to be running properly but just slowly, you can increase the sem_timeout setting in init<oracle_sid>.utl. stat ing file: error The filename given in the input file does not exist, or it may be inaccessible. Check the file to see if it exists and has read permissions. 146

147 Appendix C: Troubleshooting Table 32. NSR-R/3 Fatal Error Messages (Part 5 of 6) Error Message Description Solution Switch log file indicates an error. The brconnect program indicated in the switch log file that there was an error switching one of the tablespaces into or out of backup status. This is considered a fatal error in the backint specification. Investigate the error messages in the switch log file to determine the problem. Check the SAP R/3 installation or the SAP R/3 documentation to determine the problem. Unable to allocate memory for struct fileinfo The backint program ran out of space when it tried to allocate memory for a block of file information. Check the memory usage on the computer. You may need to reboot the computer if it is running low on memory. If the input file is excessively large, check to make sure SAPDBA is providing a valid list of files. Unable to allocate memory: error The backint program was unable to allocate memory. Check the memory usage on the computer. You may need to reboot the computer if it is running low on memory. C Unable to change to root: error In a cluster environment the program was unable to change its real and effective user IDs to root. Ensure the user has proper permission to log on as root. Unable to execute child backint process. The backint process could not execute a subprocess to back up an individual save set. Ensure that the backint binary is installed in the directory from which SAPDBA, brbackup, or brrestore is run. Check the log file for any other messages which may help pinpoint the problem. Unable to open output file: error The output file could not be opened because of the error specified. Check the permissions on the output file and directory, and check for sufficient disk space to create a new file. Usage error An unsupported option was included in the backint command. For parameters accepted by backint, refer to SAP s BC-BRI BACKINT Interface for Oracle documentation. 147

148 Fatal Error Messages Table 32. NSR-R/3 Fatal Error Messages (Part 6 of 6) Error Message Description Solution Use absolute path name for: filename The filename given in the input file was not an absolute pathname. The file cannot be restored or inquired without having the full pathname. Check the input file brrestore generated to ensure that it has the correct format. If not, and this error keeps occurring, contact SAP technical support. waitchild (name) failed: error Warning, empty input file The program could not properly receive the exit code from a subprocess. It is possible that the subprocess did not start correctly. The input file that contains the list of files to be backed up or restored is empty. Check any prior error messages to determine whether a subprocess failed, and if so, why. Ensure that you have selected database objects for backup or restore. C 148

149 Glossary This glossary contains terms and definitions found in this manual. Most of the terms are specific to NSR-R/3 products.? The Oracle placeholder for the main directory of the Oracle database instance identified as $ORACLE_HOME. See init<oracle_sid>.utl. archive archived redo log ARCHIVELOG mode The process by which NetWorker software backs up directories or files to an archive volume and then grooms them to free disk space. When data is archived, it is written to one or more storage volumes and then marked so that it is never subject to automatic recycling. You can delete the archived files from the client, thus freeing disk space. An archived copy of a filled online Oracle redo log. You can optionally configure an Oracle database to archive copies of the online redo logs after they fill. An archived redo log preserves older redo log data for recovery operations while the preallocated online redo log files are reused to store the most current database changes. See redo log. Setting the Oracle database to this mode enables archiving of the online redo logs. 149

150 authentication method backint backup device type A security method that enables high confidence in the identity of users, clients, and servers in distributed environments. The NSR-R/3 software allows two methods of authenticating identity: Database authentication uses the SAP R/3 or Oracle system user name, as designated by the database administrator for the client s Oracle database. External or enterprise authentication applies a user name that is derived from either the save set name entered in the Client resource or the ORACLE_SID parameter set in the scheduled backup configuration file. The interface the NSR-R/3 software uses to connect the NetWorker software with the SAP BRTools. The backint program enables backups, restores, or inquiries on the associated Oracle databases. The backup device type to which the SAP BRTools program sends data. When this attribute is set to util_file util_file_online, BRTools use NSR-R/3 for backup and recover. When this attribute is set to rman_util BRTools use RMAN for DB files backup/restore and NSR-R/3 for all other files. Glossary BID bootstrap Backup ID is the savetime of the backup. A save set that is essential for the NetWorker disaster recovery procedures. It is composed of three components that reside on the NetWorker server: the media database, the resource database, and the server index. brarchive brbackup browse policy brrecover The SAP BRTools program that sends requests to NSR-R/3 to back up Oracle database archive logs. The SAP BRTools program that sends requests to NSR-R/3 to back up Oracle data files, control files, redo logs, and tablespaces. A policy that determines how long entries for backup data remain in the client file index. The SAP BRTools program of newer SAP Versions used to interactively recover the database from disaster. This utility should be preferred to SAPDBA for recovery. 150

151 Glossary brrestore The SAP BRTools program that sends requests to NSR-R/3 to restore Oracle data to the Oracle server. BRTools A set of SAP tools used to back up and recover SAP R/3 data in an Oracle database. The tools are: brbackup, brarchive, brrecover, and brrestore. client file index clone clone volume A database of information the NetWorker server maintains that tracks every database object, file, or filesystem backed up. The NetWorker server maintains a single client file index for each client computer. The NetWorker process used to make an exact copy of saved data (save sets). NetWorker software indexes and tracks clones in both the client file index and the media database. The NSR-R/3 software uses the sapclone command to clone save sets. A duplicated volume belonging to a clone pool. NetWorker software can track four types of volumes: backup, archive, backup clone, and archive clone. Save sets of different types may not be intermixed on one volume. cluster cold Oracle backup Two or more nodes that are connected and appear to network users as a single highly available system. A highly available system allows the application services to continue despite most hardware or software failures. See offline backup. Glossary database authentication DATA_MOVER DBA deferred live backup See authentication method. Hostname of the PowerSnap proxy client An abbreviation for database administrator. The person normally responsible for installing, configuring, and maintaining Oracle database systems. See live backup. 151

152 device directed recovery directive external or enterprise authentication file index filesystem hot Oracle backup A storage unit that reads from and writes to storage volumes. A storage unit can be a tape device, optical drive, autochanger, or file connected to the server or storage node. A recovery method used to recover data that originated on one computer and re-create it on another computer. An instruction that directs NetWorker software to take special actions on a given set of files for a specified client during a backup. See authentication method. See client file index. 1. A file tree located on a specific disk partition or other mount point. 2. The entire set of all files. 3. A method of storing files. See online backup. Glossary immediate live backup init<oracle_sid>.sap See live backup. The SAP initialization file used to set the parameters the SAP BRTools program uses during backup, restore, and archive sessions. init<oracle_sid>.utl instance The NSR-R/3 parameter file that specifies the parameters the backint command uses during backup, restore, and archive sessions. See Oracle instance. instant backup A permanent point-in-time copy, or snapshot, of SAP R/3 with Oracle data that is stored as a backup on the primary storage system. instant restore The process by which the snapshot that was created on the primary storage system with an instant backup is mounted and its saved data is retrieved as needed. 152

153 Glossary license enabler live backup manual backup The license code that enables you to run a feature or product. A live backup (also known as a "PIT rollover" or "rollover to tape" backup) is a tape backup of a previously-created snapshot. NSR-R/3 for SAP R/3 with Oracle supports the following two types of live backup: Immediate live backup (also known as "serverless snapshot backup" or "snapshot-based backup") is a process by which a temporary snapshot is created, and immediately backed up to secondary storage such as tape. The snapshot is then automatically deleted from the primary storage. Deferred live backup is a process by which a permanent snapshot, created on the primary storage system, is backed up to secondary storage such as tape. The snapshot is retained on the primary storage for a specified period of time. An unscheduled backup that a user requests from the NetWorker client side. A manual backup does not generate a bootstrap save set. media database NSR-R/3 offline backup A database that contains indexed entries about the storage volume location and the life cycle status of all data and volumes the NetWorker server manages. NetWorker Service Release for SAP R/3 with Oracle A backup of Oracle database objects performed while the corresponding Oracle instance is shut down and unavailable to users. Glossary online backup online indexes Oracle instance A backup of Oracle database objects performed while the corresponding Oracle instance is running and available to users. The databases located on the NetWorker server that contain all the information pertaining to the client backups (client file index) and backup volumes (media database). The combination of Oracle processes and shared memory that is created each time a database starts up. 153

154 Oracle user ORACLE_SID parameter pathname PIT copy PowerSnap proxy client The user of an Oracle database. The system ID of the Oracle database instance. A variable used to identify the specific values or options to be used by associated commands. A set of instructions to the operating system for accessing a file. An absolute pathname indicates how to find a file starting from the root directory and working down the directory tree. A relative pathname indicates how to find the file starting from where you are now. Point-in-time copy, which generally means a permanently retained snapshot of data created with a PowerSnap Module. A snapshot results in one or more PITs being created nearly simultaneously with the option to back these up to tape. Surrogate client that performs the NetWorker save operation for client that requested the backup. Glossary RDBMS recover An abbreviation for Relational Database Management System, which refers to the primary architecture that the Oracle database uses. NetWorker software: The command used to browse the server index and to recover files from a backup volume to a client s disk (a process in Oracle known as "restore"). Oracle: The datafile recovery method that uses Oracle commands to apply archived redo logs and online redo logs to make the database consistent. Recovery Manager redo log resource database See RMAN. The online log of an Oracle database, consisting of at least two redo log files (separate from the datafiles) that record all changes made in the database. See also archived redo log. A database that contains information about each of the configured backup server s resources. 154

155 Glossary restore RMAN rollback restore rollover to tape root sapclone The process of retrieving individual files from backup media and storing the files on disk. An abbreviation for Recovery Manager, the Oracle utility that acts as an intelligent interface to Oracle databases and works with third-party media management products, such as NetWorker, to back up and restore Oracle database objects. The process by which the entire snapshot, created on the primary storage system by an instant backup, is restored to the source location by using the hardware s particular capabilities. See live backup. The superuser account (with user name root and user ID). By extension, the privileged system-maintenance login on any operating system. The NSR-R/3 command used to create a duplicate copy of the data (save sets) backed up using the NSR-R/3 software. SAPDBA save set The SAP R/3 database administration utility that simplifies the administrative tasks related to Oracle databases, including backup and restore operations. This utility can be used to call brbackup, brrestore, and brarchive programs. A group of files or a filesystem from a single client computer backed up to storage media. Glossary save set ID save set status secondary storage restore A unique identification number that NetWorker software assigns to a save set. The NetWorker attribute that indicates whether a given save set is restorable, recoverable, or recyclable. The save set status also indicates whether the save set has been successfully backed up. The process by which a snapshot that was backed up to secondary storage by a live backup is restored by using the traditional NetWorker recover program. 155

156 server index SID snap set snapshot ssid tablespace A database containing information about the NetWorker server's files that have been backed up during scheduled backups. Also known as the NetWorker server s client file index. An Oracle abbreviation for system identifier, a unique name for an Oracle database instance. This value is typically set in an ORACLE_SID environment variable. The group of datafiles included in any given snapshot copy, the lifecycle of which is specified in the Snapshot Policy. A point-in-time copy of a filesystem or partition. See save set ID. An Oracle database structure comprising one or more datafiles. Glossary 156

157 Index <ORACLE_SID>, description 14 A alert, backup completion 37 arch_backint_log parameter 34 archive logs 39 archive redo logs 60 ARCHIVELOG mode 59 attempts, retry backup 40 B backint backup process 25 command 22, 57 description 16, 22 parameter file 33 restore process 27 setting ownership of 30 backint_log parameter 34 backint_tmpdir parameter 34 backup archive redo logs 60 bootstrap file 61 client file index 61 client settings 66 command 67 command attribute 23 completion notification 38 deferred live 88, 112 diagram 26 group 36 immediate live 88, 109 instant 87, 106 live 88, 109 manual 57 offline manual 58 online manual PowerSnap records 114 PowerSnap types of 87 processes 25, 106 with RMAN 26 with SAPDBA 25 rollover 88, 109 save sets grouped by filesystem 41 scheduled 65 serverless snapshot 88 session log 62, 73 session report 62, 73 snapshot-based 88 backup_dev_type parameter 44 bootstrap file, backing up 61 bootstrap, NetWorker 108, 110 BR_EXEC 70 brarchive 107, 109 command 23, 119 description 23 difference from brbackup 19 manual backup 119 supported options 119 syntax 119 brbackup 107, 109, 119 command 23, 119 description 23 difference from brarchive 19 offline backup 59 online backup 60 supported options 119 syntax 119 browse naming format 41 browse policy 80 expiration 36 for manual backup 61 BRRECOVER added support 17 brrecover 123 command 123 options, syntax 123 brrestore 27, 115 command 23, 115 description 23 supported options 123,

158 Index C - D Index usage 123, 126 BRTools 23 configuring 44 See also SAPDBA C client configuring 31, 66 expiration parameter 36 NetWorker, configuring 66 parameter 34 resource 31 save set location 80 settings in parameter file 66 client file index backup 61 database 61 Client resource 66 configuration 66 parameter 34 client resource PowerSnap 97 cloning messages 77 monitoring 77 save sets 75 syntax of sapclone 75 cluster client file index 34 data, cloning 76 data, restoring 82 command backint 22, 57 backup 67 brarchive 23, 119 brbackup 23, 119 brrecover 123 brrestore 23, 115 mminfo 114 nsrim 62 nsrinfo 114 nsrsapsv 22, 67 sapclone 75 savefs 106, 109 savegrp 61, 106, 109 scanner 80 components description 21 NetWorker client 23 NSR-R/3 22 Oracle 24 PowerSnap 24 SAP R/3 23 user-configurable 21 compress parameter 35 configuration BRTools 44 NetWorker client 66 NetWorker for PowerSnap 96 NetWorker Module environment 30 PowerSnap 94 SAPDBA 44 configuration file init<oracle_sid>.sap 23, 44 init<oracle_sid>.utl 22, 24, 33, 93, 102 init<oracle_sid>.utl for PowerSnap 98 nmsapps.cfg 24, 93, 102 nsrsapsv.cfg 22, customer service 11 D data backing up 25 26, 57, 65 expiration 80 recovering 14 restoring 27, 79 data flow description backup 25 PowerSnap 90 restore 27 database instance, restoring 80, 126 server, description 15 datafile, restoring by ID 126 debug level 138 deferred live backup 88, 112 description backup and restore processes 25 components 21 features 15 NetWorker server

159 Index E - I NSR-R/3 16 RMAN 19 SAP R/3 19 SAPDBA 19, 23 device_server 35 diagnose problems 137 diagnostic logs 138 disaster recovery files 61 disk failure 61 distributing backup load 40 documentation conventions 10 electronic access to Fujitsu Siemens information 11 environment variables mandatory 131, NSR_CLIENT 104, 130 NSR_COMPRESSION 105, 130 NSR_DATA_MOVER 103 NSR_DATA_VOLUME_POOL 105, 131 NSR_DEBUG_FILE 132 NSR_DEBUG_LEVEL 132 NSR_GROUP 105, 132 NSR_MAX_STREAMS 103, 105 NSR_NO_BUSY_ERRORS 133 NSR_NWPATH 133 NSR_PROXY_PFILE 133 NSR_PS_DEBUG_LEVEL 103 NSR_PS_SAVE_PARALLELISM 103, 105 NSR_SAVESET_BROWSE 134 NSR_SAVESET_EXPIRATION 105, 134 NSR_SAVESET_RETENTION 134 NSR_SERVER 104, 135 NSR_SNAP_TYPE 103 RESTORE_TYPE_ORDER 104 used with RMAN 45, 129 error messages 137 fatal 143 nonfatal 140 errors notification, enabling 37 expiration of data 80 expiration parameter 31, 36 feature 17 E failure notification 37 features description 15 expiration parameter 17 improved administrator s security 16 NetWorker server 16 new or enhanced features 16 NSR-R/3 16 Oracle, with 19 PowerSnap 20 RMAN, with 19 SAP BRRECOVER 17 SAP R/3, with 19 SAPDBA, with 19 files backed up, number of 63 files requested for backup 63 filesystem group save sets by 41 Fujitsu Siemens customer service 11 support 11 workshop center 11 full restore 80 F G group parameter 36 group resource for PowerSnap 96 group save sets by filesystem 41 H hostname, NetWorker server 40 ID range, restoring by 127 ID, restore by 126 immediate live backup 88, 109 index entries, query parameter 39 init<oracle_sid>.sap file description 23 enabling SAPDBA or brbackup 44 I Index 159

160 Index L - N enabling SAPDBA or RMAN 44 specifying different profile 127 init<oracle_sid>.utl file 22, 102 equivalent parameters for PowerSnap 104 parameters 33 parameters for PowerSnap 24, 93, 98 input file report 63 installation files installed 49 licenses 53 instant backup 87, 106 instant restore 89, 115 L media database records 80 messages cloning 77 notify_done 37 notify_error 37 notify_start 37 notify_success 38 mminfo 114 monitoring backups 62, 73 cloning 77 restores 82 N Index level_full parameter 36 license file installing 53 live backup 88, 109 location of save set data 80 logs arch_backint_log parameter 34 archive redo 60 backint_log parameter 34 backint_tmpdir parameter 34 backup session reports 62, 73 restore 82 verbose setting 41 M mailx utility 38 mandatory environment variables 131, manual backup 57 backup session reports 62, 73 bootstrap 58, 61 client file indexes 61 command line options 119 offline 58 online 59 using brarchive command 58, 60 using brbackup command 58, 60 with SAPDBA 58, 60 max_logs parameter 37 maximum size of save sets 41 naming conventions 14 save set format 41 save sets 41 NetWorker bootstrap backup 108, 110 client components 23 configuration 66 name 34 media database service, nsrmmdbd 107, 110, 112 save set records 80 server components 22 features 16 hostname 40 NLS_LANG 71 nmsapps.cfg file 24, 93, 102 notify_done message 37 notify_error message 37 notify_start message 37 notify_success message 38 NSR_CLIENT 104, 130 NSR_COMPRESSION 105, 130 NSR_DATA_MOVER 103 NSR_DATA_VOLUME_POOL 105, 131 NSR_DEBUG_FILE 132 NSR_DEBUG_LEVEL 132 NSR_GROUP 105, 132 NSR_MAX_STREAMS 103, 105 NSR_NO_BUSY_ERRORS

161 Index O - P NSR_NWPATH 133 NSR_PROXY_PFILE 133 NSR_PS_DEBUG_LEVEL 103 NSR_PS_SAVE_PARALLELISM 103, 105 NSR_SAP_ADMIN_ GROUP 71 NSR_SAP_ADMIN_ USER 71 NSR_SAP_RESTORE_ RETRY_COUNT 71 NSR_SAP_RESTORE_ RETRY_DELAY_SECS 71 NSR_SAVESET_BROWSE 134 NSR_SAVESET_EXPIRATION 105, 134 NSR_SAVESET_RETENTION 134 NSR_SERVER 104, 135 NSR_SNAP_TYPE 103 nsrexecd service 106, 109 nsrim command 62 nsrindexd service 107, 110, 112, 117 nsrinfo command 114 nsrmmdbd service 107, 110, 112 nsrpsd program 94, 117 NSR-R/3 153 components 22 environment 30 example network 14 features 16 features summary 15 parameter file 93 restoring with 126 nsrsapsv command 22, 67 configuration file 68 description 22 program 107, 109 nsrsapsv.cfg file configuration 68 description 22 enabling 67 O offline manual backup 58 online manual backup options brarchive 119 brbackup 119 brrecover 123 brrestore 126 sapclone command 75 Oracle components used 24 features used 19 user 30 ORACLE_BIN 71 ORACLE_HOME 72 ORACLE_SID 72 P parallelism, setting 38 parameter arch_backint_log 34 backint_log 34 backint_tmpdir 34 backup_dev_type 44 BR_EXEC 70 Client resource 34 compress 35 device_server 35 equivalents to PowerSnap variables 104 expiration 36 group 36 level_full 36 max_logs 37 NLS_LANG 71 notify_done 37 notify_error 37 notify_start 37 notify_success 38 NSR_SAP_ADMIN_ GROUP 71 NSR_SAP_ADMIN_ USER 71 NSR_SAP_RESTORE_ RETRY_COUNT 71 NSR_SAP_RESTORE_ RETRY_DELAY_SECS 71 ORACLE_BIN 71 ORACLE_HOME 72 ORACLE_SID 72 parallelism 38 PATH 72 pool 39 PowerSnap 98 prev_bk_restore 39 ps_archive_mode 98 ps_backup_mode 98 ps_exclude_backup_bi_run_nums Index 161

162 Index P - P Index ps_group_objs 101 ps_opaque_pfilename 24, 102 query_index 39 raw_dir 40 retry_count 40 rman_parms 45 SAP_BIN 73 SAPBACKUP 73 SAPDATA_HOME 73 savesets 40 sem_timeout 40 server resource 40 ss_group_by_fs 41 ss_size_max 41 ssnameformat 41 verbose logs 41 parameter file changing 127 parameters for brarchive 119 for brbackup 119 NetWorker Module 33 PATH 72 PATH variable, setting 30 physical media failures 88 PIT copy 87 point-in-time copy 87 policies, expiration 36, 80 pool multiple 39 parameter 39 selection 36 settings 39 PowerSnap attribute settings 92 backup processes 106 backup records 114 backups and restores 85 client resource 97 components 24 configuration 94 configuration file 24, 93, 102 data flow descriptions 90 features 20 getting started 92 group resource 96 instant backup 87, 106 instant restore 89, 115 invoking a restore 115 invoking backups 106 live backup 88, 109 Module 86 nsrpsd daemon 94 parameter file 24 parameter settings 98 ps_opaque_pfilename file 94 requirements 86 restore from secondary storage 90, 117 restore processes 115 rollback restore 89, 115 rollover backup 88, 109 Snapshot Policy resource 96 Snapshot Pool resource 96 types of backups 87 types of restore 89 variables 24 PowerSnap Module 93 prev_bk_restore parameter 39 problems, backup or restore 138 processes, NetWorker Module 25 profile, using different for restore 127 program brarchive 107, 109 brbackup 107, 109 nsrd 106, 109 nsrexecd 106, 109 nsrindexd 107, 110, 112 nsrmmdbd 107, 110, 112 nsrsapsv 107, 109 savefs 106, 109 savegrp 106, 109 ps_archive_mode 98 ps_backup_mode 98 ps_exclude_archive_bi_run_nums 99 ps_exclude_archive_paths 100 ps_exclude_backup_bi_run_nums 99 ps_exclude_backup_paths 100 ps_group_objs 101 ps_inquire_mode 98 ps_opaque_pfilename 98 ps_opaque_pfilename file 94 ps_opaque_pfilename parameter 24, 102 ps_ps_before_nonps 101 ps_restore_mode

163 Index Q - S Q query PowerSnap backup records 114 query_index parameter 39 R raw directories 40 raw_dir parameter 40 recover command line options 123 recover, description 14 Recovery Manager 19 See also RMAN related documentation 28 release information, verifying 137 Remote Exec services report, backup session 62, 73 requirements PowerSnap 86 resources, NetWorker 31, 36 client 66 configuring 31 group 31 pool and pool parameter 31, 39 configuring 31 schedule 31 server 32 restore a single tablespace 126 all tablespaces 126 brrestore, syntax 123, 126 by datafile ID 126 by ID range 127 cluster data 82 command line options 126 data 79 description 14 diagram 27 entire database instance 80, 126 from secondary storage 90, 117 full 80 instant 89, 115 monitoring 82 options, syntax 126 parameter file used for setting 127 PowerSnap 89 previous backup if not found 39 process described 25 processes 115 reviewing report log 82 rollback 89, 115 single database object 80 using a different profile 127 using NSR-R/3 126 restore messages, suppress 126 restore process with RMAN 27 with SAPDBA 27 RESTORE_TYPE_ORDER 104 retention policy expiration 80 manual backup 61 retry_count, setting 40 reviewing backups 62, 73 restore logs 82 RMAN 24 backup process 26 enabling 44 environment variables 45, 129 features with 19 restore process 27 rman_parms parameter 24, 45 rollback restore 89, 115 rollover backup 88, 109 root, setting owner to 30 S SAP R/3 components 23 features 19 initialization file 44 SAP_BIN 73 SAPBACKUP 73 sapclone command 75 description 22 options 76 syntax 75 Index 163

164 Index T - V Index SAPDATA_HOME 73 SAPDBA 25 backup process 25 components 23 configuring 44 description 23 features 19 restore process 27 utilities 19 save archive redo logs 60 bootstrap file 61 client file index 61 command 40 save sets description 66 expiry 80 maximum size parameter 41 naming 41 parameter 40 setting 23 viewing 79 save streams, setting 38 savefs command 106, 109 savegrp command 61, 106, 109 savesets parameter 40 scanner command 80 scheduled backup configuration file tasks 65 sem_timeout parameter 40 semaphore file 40 server resource parameter 40 serverless snapshot backup 88 service nsrd 106, 109 nsrexecd 106, 109 nsrindexd 107, 110, 112 nsrmmdbd 107, 110, 112 service for customers 11 setting backint ownership 30 single database object, restoring 80 single tablespace, restoring 126 snap set 87 snapshot 87, 106 Snapshot Policy resource 96 Snapshot Pool resource 96 snapshot-based backup 88 special terms 14 ss_group_by_fs parameter 41 ss_size_max parameter 41 ssnameformat parameter 41 starting attribute 64 support 11 suppress restore messages 126 symbols 10 symlink attribute 64 tablespaces, restoring 126 temporary files directory 34 testing 138 timeout period 40 troubleshooting tips 137 typographic conventions and symbols 10 T U uid bit 30 Upgrading NSR-R/3 49 user, SAP 64 user-configurable components 21 validation of server indexes 39 variables mandatory 131, NSR_CLIENT 104, 130 NSR_COMPRESSION 105, 130 NSR_DATA_MOVER 103 NSR_DATA_VOLUME_POOL 105, 131 NSR_DEBUG_FILE 132 NSR_DEBUG_LEVEL 132 NSR_GROUP 105, 132 NSR_MAX_STREAMS 103, 105 NSR_NO_BUSY_ERRORS 133 NSR_NWPATH 133 NSR_PROXY_PFILE 133 NSR_PS_DEBUG_LEVEL 103 NSR_PS_SAVE_PARALLELISM 103, 105 NSR_SAVESET_BROWSE 134 V 164

165 Index W - W NSR_SAVESET_EXPIRATION 105, 134 NSR_SAVESET_RETENTION 134 NSR_SERVER 104, 135 NSR_SNAP_TYPE 103 PowerSnap 24, 102 RESTORE_TYPE_ORDER 104 verbose logs parameter 41 viewing save sets 79 virtual node 34 web address 11 workshop center 11 W Index 165

166 Index W - W Index 166

167 Fujitsu Siemens Computers GmbH User Documentation Munich Germany Fax: (+49) 700 / Comments Suggestions Corrections manuals@fujitsu-siemens.com Submitted by Comments on

168 168 NSR-R/3 V3.0

169 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009