SAP Ora 4 Admin

EMC NetWorker Module for SAP with Oracle
Release 4.0
Administration Guide
P/N 300-009-525 REV A01
EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103

1-508-435-1000 www.EMC.com
Copyright 1998 - 2009 EMC Corporation. All rights reserved. Published November, 2009 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.
EMC NetWorker Module for SAP with Oracle Release 4.0 Administration Guide
Contents
Preface Chapter 1 Introduction

Naming conventions .............................................................................................. Complete backup protection................................................................................. NetWorker Module for SAP with Oracle Software features ............................ Internationalization ................................................................................................ Support of Non-English characters................................................................ English-only characters.................................................................................... NMSAP and associated software ......................................................................... NMSAP software .............................................................................................. NetWorker software......................................................................................... NetWorker PowerSnap software ................................................................... EMC Replication Manager software.............................................................. SAP server software ......................................................................................... Oracle server software ..................................................................................... NMSAP software components.............................................................................. 12 12 13 15 15 16 16 16 16 16 17 17 17 17
Chapter 2
Software Configuration
Verifying the NMSAP software requirements.................................................... Configuring I18N support..................................................................................... Requirements for I18N support...................................................................... Configure I18N support (UNIX only) ........................................................... Choosing either backint or RMAN as the backup and restore utility............. Set backint as the backup and restore utility................................................ Set RMAN as the backup and restore utility................................................ Configuring a scheduled backup with the wizard ............................................ Wizard workflows............................................................................................ Wizard limitations............................................................................................ Wizard requirements ....................................................................................... Configure a scheduled backup with the wizard.......................................... Converting client-side configurations to wizard configurations..................... Configuring a scheduled backup without the wizard ...................................... Configure the NMSAP parameters without the wizard............................. Configure the scheduled backup resources without the wizard............... Configuring a manual backup .............................................................................. Configuring a deduplication backup................................................................... Requirements for a deduplication backup.................................................... 20 21 21 21 21 22 22 23 23 23 24 24 25 26 26 27 29 29 29
Contents
Best practices for a deduplication backup..................................................... 29 Configure deduplication for a scheduled backup........................................ 30 Configure deduplication for a manual backup ............................................ 31 Configure deduplication for Oracle RMAN backup ................................... 32 Configuring a probe-based backup ...................................................................... 32 Configure a probe-based backup.................................................................... 33 User-defined probes ......................................................................................... 34 Example probe-based backup with multiple probes................................... 34 Configuring backup email notifications .............................................................. 35
Chapter 3
Backup Procedures
Performing scheduled backups............................................................................. 38 Test a scheduled backup .................................................................................. 38 Monitor a scheduled backup........................................................................... 38 Cancel a scheduled backup ............................................................................. 39 Performing a manual backup ................................................................................ 39 Requirements..................................................................................................... 39 Run a manual backup....................................................................................... 39 Back up the NetWorker bootstrap and online indexes ............................... 40 Monitor a manual backup................................................................................ 41 Cancel a manual backup .................................................................................. 41 Reviewing backup and restore session reports................................................... 41 Verifying the backup information in the NetWorker indexes .......................... 41 Verify backup information in the NetWorker indexes................................ 41 Cloning backups...................................................................................................... 42 The sapclone command syntax and options ................................................. 43
Chapter 4
Data Restore and Recovery

Restoring and recovering data .............................................................................. 46 Restore and recover .......................................................................................... 46 The backup lifecycle ......................................................................................... 46 Performing a restore and recovery ....................................................................... 46 Restart a restore for files that failed to be restored ...................................... 48
Chapter 5
Disaster Recovery
Requirements for disaster recovery...................................................................... 50 Protect the computing environment .............................................................. 50 Recovering from a disaster .................................................................................... 50 Restore the required Oracle and SAP BRTools files .................................... 50 Recover a SAP Oracle database after disaster .............................................. 51
Chapter 6
Cluster and Oracle RAC Configurations

Cluster systems........................................................................................................ 54 Configuring a scheduled backup in a cluster ............................................... 54 Configuring a manual backup in a cluster .................................................... 55 Configuring a deduplication backup in a cluster......................................... 55 Converting client-side configurations to wizard settings in a cluster....... 55 Restoring in a cluster ........................................................................................ 56 Oracle RAC systems ............................................................................................... 56 Configuring Oracle RAC backups.................................................................. 56 Restoring Oracle RAC data ............................................................................. 56
Contents
Chapter 7
Snapshot Backup with PowerSnap

PowerSnap snapshot backups and restores........................................................ 58 Supported environments................................................................................. 58 Required software components...................................................................... 58 Types of PowerSnap backup ................................................................................. 59 Instant backup................................................................................................... 60 Live backup ....................................................................................................... 60 Types of PowerSnap restore .................................................................................. 61 Instant restore.................................................................................................... 61 Rollback.............................................................................................................. 61 Restore from conventional storage ................................................................ 61 Basic PowerSnap backup and restore data flows............................................... 61 Configuring NMSAP snapshot backups and restores....................................... 63 Configure the NetWorker resources for NMSAP snapshot backups ....... 63 Configure NMSAP and PowerSnap parameters for snapshot operations 65 Testing NMSAP snapshot backups and restores................................................ 68 Example parameter settings for NMSAP snapshot backup ............................. 69 Reviewing NMSAP snapshot backup records.................................................... 70
Chapter 8
Split-Mirror Backup with Replication Manager

Split-mirror backups and restores ........................................................................ Supported environments................................................................................. Required software components...................................................................... Basic split-mirror backup and restore data flows .............................................. Manual split-mirror backup data flow.......................................................... Scheduled split-mirror backup data flow ..................................................... Restore of split-mirror backups data flow .................................................... Configuring the production host for split-mirror backups .............................. Configure Oracle on the production host ..................................................... Configure BRTools on the production host .................................................. Configure NMSAP on the production host .................................................. Configuring the mount host for split-mirror backups ...................................... Configure Oracle software on the mount host............................................. Configure BRTools on the mount host .......................................................... Configure NMSAP on the mount host .......................................................... Configuring the RM server for split-mirror backups ........................................ Configuring the NetWorker server for split-mirror backups ........................... Configuring a cluster environment for split-mirror backups .......................... Examples of RM scripts for split-mirror backups .............................................. sap_online_split script for RM on UNIX systems........................................ erm_brbackup_online_split.sh script for RM on UNIX systems............... sap_online_split.cmd script for RM on Microsoft Windows systems ...... erm_online_split.cmd script for RM on Microsoft Windows systems ..... Examples of parameters for split-mirror backups ............................................. Parameters to set on the production host ..................................................... Parameters to set on the mount host ............................................................. 72 72 72 72 73 73 73 74 74 74 75 75 75 75 76 77 77 77 78 78 79 79 79 79 79 80
Appendix A
NMSAP Parameter and Configuration Files

NMSAP backint parameters.................................................................................. Configure the NMSAP parameter file ........................................................... Supported backint parameters ....................................................................... NMSAP nsrsapsv parameters ............................................................................... Configure the NMSAP configuration file .....................................................
82 82 82 88 88
5
Contents
Supported nsrsapsv parameters ..................................................................... 89 NMSAP parameters for RMAN backups and restores...................................... 92 Configure the RMAN parameters .................................................................. 92 Supported NMSAP RMAN parameters ........................................................ 92
Appendix B
Examples of SAP Command Options

Examples of brbackup and brarchive command syntax and options ............. 98 Examples of brrestore command syntax and options........................................ 99 Examples of brrecover command syntax and options....................................... 99
Appendix C
Troubleshooting
Verifying the release information........................................................................ 102 Generating diagnostic logs .................................................................................. 102 Backup and restore problems .............................................................................. 102 NMSAP Error messages ....................................................................................... 103
Glossary Index
Preface
As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information about product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Audience This document is part of the EMC NetWorker Module for SAP with Oracle (NMSAP) documentation set, and is intended for use by system administrators during the configuration of the NMSAP software. Readers of this document are expected to be familiar with the following topics:

SAP terminology and concepts, especially those related to Oracle database backup and recovery Backup and recovery procedures Disaster recovery procedures
Related documentation
Documentation related to the use of this product can be found at the EMC Powerlink website, Powerlink.EMC.com, including:
The NetWorker Module for SAP with Oracle release 4.0 documentation set: Administration guide Installation guide Release notes Command reference guide The NetWorker documentation set: Administration guide Installation guide Release notes Command reference guide NetWorker Licensing Process Guide Disaster recovery guide Other EMC documentation: NetWorker PowerSnap Module documentation Software compatibility guide UNIX man pages
Preface
Conventions used in this document
EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.
CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment.
IMPORTANT An important notice contains information essential to software or hardware operation. Typographical conventions EMC uses the following type style conventions in this document: Normal
Used in running (nonprocedural) text for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications Used in running (nonprocedural) text for: Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) What user specifically selects, clicks, presses, or types
Bold
Italic
Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis (for example a new term) Variables Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Used for: Specific user input (such as commands) Used in procedures for: Variables on command line User input variables Angle brackets enclose parameter or variable values supplied by the user Square brackets enclose optional values Vertical bar indicates alternate selections - the bar means or Braces indicate content that you must specify (that is, x or y or z) Ellipses indicate nonessential information omitted from the example
Courier
Courier bold
Courier italic
<> [] | {} ...
Preface
Where to get help
EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:
Powerlink.EMC.com
Technical support For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:
techpubcomments@EMC.com
If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.
Preface
10
1
Introduction
This chapter includes the following sections:

Naming conventions..................................................................................................... Complete backup protection ....................................................................................... NetWorker Module for SAP with Oracle Software features ................................... Internationalization....................................................................................................... NMSAP and associated software................................................................................ NMSAP software components ....................................................................................
12 12 13 15 16 17
Introduction
11
Introduction
Naming conventions
Table 1 on page 12 lists some special terms that are are frequently used in this EMC NetWorker guide.
Table 1
Descriptions of frequently used terms Term BRTools NMC NMSAP Description The SAP backup utilities, specifically the brbackup, brrestore, brarchive, and brrecover programs. NetWorker Management Console. NetWorker Module for SAP with Oracle software. Variable representing the name of the SAP Oracle database instance that you want to back up. Oracle transaction log file, which records a history of all transactions made to a database. Archived redo logs are backed up and used to recover a database to a specific point in time. 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. Note: This usage is unlike NetWorker terminology, which uses recover for all data retrieval activities. wizard, NMSAP Wizard NetWorker client backup configuration wizard, which incorporates NMSAP features and functionality and is launched from NetWorker Management Console.
DBSID
redo log
restore and recover
The Glossary provides a complete list of terms used in this guide.
Complete backup protection

When protection of a computer system is complete, it protects not only against the loss of data, but also against catastrophic disaster, such as a system or hardware failure. For complete protection, a viable backup strategy includes regular backups of:

Data Transaction (archived) redo logs NetWorker bootstrap records (media database, resource database, and server index, which reside on the NetWorker server) Without data backups, data content cannot be recovered. Without transaction log backups, a database can be restored only to the time of its last full backup. Without the bootstrap backup records, it may not be possible to recover essential file and configuration data after a disaster, such as a disk crash or NetWorker server failure.
These backups are important for the following reasons:

12
Introduction
NetWorker Module for SAP with Oracle Software features

The EMC NetWorker Module for SAP with Oracle (NMSAP) software is an add-on module for EMC NetWorker client software that provides a backup and restore interface between SAP BRTools, the NetWorker server, and the NetWorker Management Console (NMC). The NMSAP software provides or supports the features described in this section. Scheduled backup Scheduled backups may be configured for either calendar time or probe settings that detect when specific conditions are met. Scheduled backups include backup of the NetWorker bootstrap record, which is essential for disaster recovery. Manual backup Manual backups may be performed at any time, on demand. They are initiated from the NMSAP client host. Manual backups do not include backup of the NetWorker bootstrap record, which is required for disaster recovery. Backup of these items should be done separately. RMAN backup and restore The Oracle RMAN program is integrated with the NMSAP software and may be used for backup, restore, and inquiry operations. RMAN does not back up configuration files, logs, and other files, which are backed up by the NMSAP backint program. The BRTools documentation provides details on RMAN. Deduplication backup and restore Deduplication backup and restore is an optional feature that removes duplicate data from backups before it is sent to the backup server. After an initial backup to a supported EMC Avamar server, configured as a deduplication node, backups include only unique blocks of data that contain change. Deduplication supports manual, scheduled, snapshot, and probe-based backups. Deduplication does not support the following:

Backup of raw devices or volumes Use of data compression, checksum, or NSR_AES_ENCRYPTION parameters
Probe-based backup NMSAP probe-based (event-based) backups may be configured to be triggered when specific conditions are met within a scheduled backup window. The conditions may be specified by the number of transaction (archived) logs generated, or the time elapsed since the previous probe-based backup. User-defined probes are also supported. Snapshot backup and restore Snapshot technology provides continuous protection and availability of data and nearly eliminates the use of resources on the production host to perform backups. A snapshot is a point-in-time (PIT), read-only copy of production data located on a primary storage platform, such as EMC Symmetrix or EMC CLARiiON. The snapshots may be restored back to the production host or they may be mounted onto a data mover host, where they may be backed up to conventional storage with NMSAP software.
NetWorker Module for SAP with Oracle Software features
13
Introduction
The NMSAP software supports both NetWorker PowerSnap software and EMC Replication Manager software for snapshot backups. Cluster and Oracle RAC backup and restore The NMSAP software supports backups and restores of operating system cluster and Oracle Real Application Cluster (RAC) systems. Wizard NMSAP 4.0 software supports the new NetWorker scheduled backup configuration wizard that is integrated with the NetWorker Management Console (NMC). This new wizard replaces the configuration wizard used in NMSAP release 3.5. Unlike earlier releases of NMSAP, configurations made with the wizard are not saved as a client-side parameter and configuration files, but are saved as client attributes on the NetWorker serer. The NMSAP parameter and configuration files that were used with earlier releases of NMSAP may be used by the wizard as input templates to generate a new wizard configuration. Backup settings created with the wizard may optionally be saved to an NMSAP parameter file (init<DBSID>.utl) and configuration file (nsrsapsv.cfg) on the NMSAP client host. These files are used for special purposes, such as the following:

Manual backups (init<DBSID>.utl only) Restore operations (init<DBSID>.utl only) Diagnostic or reference purposes
VMware support NMSAP software provides VMware support for backup and restore of SAP Oracle databases installed on a Virtual Machine (VM) on an ESX server, including the following advanced features:
VMotion This feature enables migration of virtual machines from one ESX server to another while the servers are on, without disruption to the applications they are running, including NMSAP backup or restore operations. Distributed Resource Scheduler (DRS) This feature enables dynamic balancing and allocation of resources across multiple ESX servers. Depending on the DRS policies set by the user, the DRS can migrate or recommend that users migrate a virtual machine to a different ESX server by using VMotion. DRS can also start (at boot-up time) a virtual machine on a different ESX server. Because this feature uses VMotion, if a migration occurs during an NMSAP backup or restore, the backup or restore is not interrupted. High Availability (HA) The HA feature enables VMware to be restarted on the same ESX server, on a different ESX server, or on a physical machine, depending on the type of VMware cluster configured. During a restart, users are disconnected, and must reconnect. If a restart occurs during an NMSAP backup or restore, the backup or restore fails. For a failed manual backup or restore, the backup or restore must be manually restarted when the guest operating system is restarted. For a failed scheduled backup, the NetWorker server retries the backup if the Client Retries attribute in the Group resource is set to a nonzero value. The EMC NetWorker Administration Guide and EMC NetWorker Release Notes provide information on VMware HA functionality and limitations.
14
Introduction
Internationalization
The NMSAP software provides internationalization (I18N) support. Non-English data from NMSAP clients may be monitored, backed up, and restored. For example, a NetWorker server with an English locale can view and manage backups from an NMSAP client with a Chinese locale and the other way around, a NetWorker server with a Chinese locale can view and manage backups from an NMSAP client with an English locale.
Note: I18N support should be distinguished from localization (L10N) support, in which the software user interface and operational messages are translated into localized languages. This NMSAP software release does not provide L10N support.
I18N support assumes the use of NMSAP software with the following I18N products:

Internationalized operating system Unicode version of BRTools NetWorker server and client that supports I18N
Note: NMSAP support of non-English environments is limited by the I18N support provided by Oracle, BRTools, NetWorker client, and the underlying operating system.
Support of Non-English characters

The NMSAP client supports non-English characters for the following:
Full pathnames of parameter and configuration files, for example, init<DBSID>. utl. Full pathnames of operational log files, for example, SAPBACKUP and SAPTRACE. Full pathnames of variables that are set in the nsrsapsv.cfg file, for example, PATH, SAP_BIN, SAPBACKUP, SAPARCH, SAPCHECK, SAPREORG, and SAPTRACE. Most strings that are passed as command-line options to the NMSAP programs nsrsapadm, nsrsapsv, sapclone, and backint. Exceptions are the Oracle username and password, which is an Oracle limitation, and the full pathname of the NMSAP scheduled backup configuration file (nsrsapsv.cfg), which is a NetWorker server limitation. English-only characters on page 16 gives details. All NetWorker parameters that are supported by NetWorker software. Environments configured by the scheduled backup wizard.
Note: The NLS_LANG=AMERICAN.AMERICA.US7ASCII parameter value, which is used in the sample backup configuration file (nsrsapsv.cfg) that is shipped with the product or generated by the NMSAP wizard, is an example or default value. This value can, and in some cases should, be set to another value. Refer to the SAP documentation on how to set the NLS_LANG parameter.
Internationalization
15
Introduction
English-only characters
Some Oracle, BRTools, and NetWorker software configuration settings, that are used with the NMSAP client, do not support I18N and must use ASCII characters. Read the appropriate product documentation for complete details. Examples include:
Oracle requires ASCII characters for the following: ORACLE_HOME environment variable Oracle instance name <DBSID>
BRTools requires English characters for the following: Connection strings (database username and password) to the SAP Oracle database Oracle datafiles, log files, control files, parameter filenames Oracle tablespace names
NetWorker and NMSAP software require ASCII characters for the following: NetWorker client, server, pool, group, expiration policy, and email notification parameters, which are set in the NMSAP parameter file (init<DBSID>.utl) NMSAP scheduled backup configuration file (nsrsapsv.cfg) pathname, which is passed to the Backup Command attribute in the NetWorker Client resource
NMSAP and associated software

This section describes the NMSAP software and other software that are used in an NMSAP environment, and which are referred to in this guide.
NMSAP software
The NMSAP software is an add-on module for NetWorker client software and provides a backup and restore interface between the SAP BRTools program and the NetWorker server. The main component of the NMSAP software is the backint program, which provides backup, inquiry, and restore processes for all Oracle and SAP files.
NetWorker software
The NetWorker software provides data storage management services that protect, move, and manage data across a network. The basic NetWorker products include the NetWorker server, client, storage node, and the NetWorker Management Console (NMC).
NetWorker PowerSnap software

NMSAP can work with the add-on NetWorker Module for PowerSnap software to provide a high-availability storage environment. The PowerSnap software creates a snapshot (point-in-time) copy of a group of files or filesystems on a client host, which serves as an instant backup. NMSAP can then back up the snapshot to a conventional storage medium.
16
Introduction
EMC Replication Manager software

NMSAP software can work with EMC Replication Manager (RM) software to provide support for BRTools split-mirror backups. RM creates a replica of production data stored on an EMC storage array, such as Symmetrix or CLARiiON, which NMSAP can back up to conventional storage.
SAP server software

The SAP server software includes the BRTools utilities, which are used by the NMSAP software for the backup, restore, and inquiry of the SAP Oracle databases. BRTools consist of brbackup, brarchive, brrecover, brrestore, and other utilities.
Oracle server software

The Oracle software includes the Recovery Manager (RMAN) utilities for backup, restore, and inquiry operations. The use of RMAN with NMSAP and BRTools software is optional because the NMSAP backint program may be used as the sole backup and restore software. If RMAN is configured to back up SAP Oracle databases, the backint program will additionally back up the SAP configuration files, logs, and other files that RMAN does not back up. Choosing either backint or RMAN as the backup and restore utility on page 21 provides details.
NMSAP software components

Table 2 on page 17 lists the NMSAP software components that are referred to in this guide. On Microsoft Windows systems, most of these files are located in the NetWorker_install_directory\nsr\bin.
Table 2
NMSAP and associated software components (page 1 of 2) Component backint[.exe] init.utl Description The NMSAP program interface to SAP BRTools, which provides backup, restore, and inquire functionality. Configuration file template that specifies the variables used by the backint program for manual backups and restores, and for scheduled backups that are not configured through the wizard. Copy this template file and name it init<DBSID>.utl, where DBSID is the name of the SAP Oracle database instance that is to be backed up. RMAN Media Management utility.
libnworasap.xx (UNIX) orasbt.dll, nsrsbtcnsap.exe (Windows) nsrsapsv[.exe] nsrsapsv.cfg
The scheduled backup program, which invokes the appropriate BRTools executables. Configuration file template for the nsrsapsv scheduled backup program for backups that are not configured through the wizard. Copy this template file and save the original file with its default settings. On UNIX systems, this file is located in the /etc directory.
NMSAP software components
17
Introduction
Table 2
NMSAP and associated software components (page 2 of 2) (continued) Component nsrsapadm[.exe] Description This binary or executable file is used to convert old-style configurations of scheduled backup to a new-style configuration that can be modified through the wizard. It is also used to encrypt logon information in the nsrsapsv.cfg file for the user who performs a scheduled backup. Program that probes for the number of generated archived logs as a condition that triggers a probe-based backup. The save set cloning program. Provides an interface to the NetWorker nsrclone program. NMSAP scheduled backup configuration wizard.
nsrsapprobe[.exe] sapclone[.exe] nsrsapra[.exe] nsrsaprachild[.exe] sapra.jar sapra_res.jar nwsldreg.xml man pages (UNIX only)
SAP Solution Manager registration file. Reference for NMSAP commands.
18
2

Verifying the NMSAP software requirements .......................................................... Configuring I18N support ........................................................................................... Choosing either backint or RMAN as the backup and restore utility ................... Configuring a scheduled backup with the wizard................................................... Converting client-side configurations to wizard configurations ........................... Configuring a scheduled backup without the wizard............................................. Configuring a manual backup .................................................................................... Configuring a deduplication backup ......................................................................... Configuring a probe-based backup ............................................................................ Configuring backup email notifications ....................................................................
20 21 21 23 25 26 29 29 32 35
19
Verifying the NMSAP software requirements

Verify that the NMSAP software environment meets the following basic requirements: 1. Ensure the Oracle and SAP software is properly installed and configured before the NMSAP environment is configured. The appropriate Oracle and SAP documentation provides instructions.
Note: You may recover only data files for which you had operating system read permission when they were backed up. It is recommended to grant read access to the data files to a DBA operating system group. This will allow the data to be restored by a different user or to a different host.
2. Ensure that NetWorker client software and NMSAP software are installed and enabled on each SAP Oracle server that requires backup and recovery services. The platform-specific NetWorker installation guide and the EMC NetWorker Module for SAP with Oracle Installation Guide provide instructions. 3. If using the BRTools RMAN feature on UNIX systems, ensure that the NMSAP RMAN management library/utility is properly linked. The EMC NetWorker Module for SAP with Oracle Installation Guide provides details. 4. Ensure that the NMSAP backint executable is located in the same directory as BRTools. On UNIX, ensure that the owner of backint is set to root. 5. If restores will be made to raw device files on UNIX, ensure that the uid bit is set for the backint program by typing the following command:
chmod 4755 backint Note: In rare cases, the uid bit must be set in order to restore to file systems on UNIX.
6. Ensure that the NetWorker server User Group resource privileges are granted to the SAP user who performs the NMSAP operations. The User Group resource may be set with NMC or the nsradmin program. The SAP user requires the following privileges: To run backups and restores requires only the default privileges, which are: Monitor NetWorker Back Up Local Data Recover Local Data To review backup information in NetWorker indexes, for example through the nsrinfo and mminfo commands: Operate NetWorker privilege To configure a backup or to convert a backup configuration with nsrsapadm: Configure NetWorker privilege 7. If a firewall is used, ensure NMSAP connectivity, which requires the corresponding ports to be configured for the NetWorker server. The EMC NetWorker Administration Guide provides details. The EMC Information Protection Software Compatibility Guide provides details on the compatibility of the NMSAP software with other products.
20
Configuring I18N support

Internationalization on page 15 describes the internationalization (I18N) features that NMSAP supports.
Requirements for I18N support

NMSAP I18N support requires the following I18N products:

Internationalized operating system Unicode version of BRTools NetWorker server and client that supports I18N
The NetWorker documentation provides specific details on NetWorker I18N requirements.

Note: NMSAP support of non-English environments is limited by the I18N support provided by Oracle, BRTools, NetWorker client, and the underlying operating system.
Internationalization on page 15 and the EMC NetWorker Module for SAP with Oracle Release Notes provides more information.
Configure I18N support (UNIX only)

To configure I18N support of the NMSAP client host on UNIX only: 1. Log in as the root user. 2. Shut down the NetWorker services. 3. Set the LC_ALL environment variable to the appropriate locale. For example, in a Japanese locale on Solaris, set LC_ALL as follows:
# nsr_shutdown # export LC_ALL=ja_JP.eucJP # /etc/init.d/networker start
4. Restart the NetWorker services.
Choosing either backint or RMAN as the backup and restore utility

All backup, restore, and inquiry operations of SAP Oracle data are interfaced through the SAP BRTools software. The BRTools software may be configured to use either the NMSAP backint program or the Oracle RMAN program to perform the actual operations. Which of these programs to use must be specified in the BRTools initialization file (init<DBSID>.sap, also known as the BRTools utility profile) or the BRTools command. The following examples describe how either may be specified.
Note: If RMAN is specified as the backup utility for the SAP Oracle databases, the NMSAP backint program will additionally back up the SAP configuration files, logs, and other files, which RMAN does not back up.
Configuring I18N support
21
Set backint as the backup and restore utility

If you want to use the NMSAP backint program for backup, restore, and inquiry operations, create a BRTools initialization profile with settings similar to the following example. 1. With a text editor, open the BRTools initialization file (utilities profile), init<DBSID>.sap, which is typically located in the following directory: On UNIX systems: $ORACLE_HOME/dbs On Microsoft Windows systems: %ORACLE_HOME%\DATABASE 2. Set the backup device type parameter to use the backint program by specifying one of the following:
backup_dev_type = util_file
or
backup_dev_type = util_file_online
3. Set the util_par_file parameter to use the NMSAP parameter file (init<DBSID>.utl) as follows: On UNIX or Linux systems:
util_par_file = ?/dbs/init<DBSID>.utl
where ? is $ORACLE_HOME On Microsoft Windows systems:

util_par_file = ?\database\init<DBSID>.utl
where ? is %ORACLE_HOME% Configure the NMSAP parameter file on page 82 describes how to configure the parameter file. The appropriate SAP documentation provides further instructions on the use of the backint program.
Set RMAN as the backup and restore utility

If you want to use the Oracle RMAN utility and NMSAP RMAN management library for backup, restore, and inquiry operations, create a BRTools initialization profile with settings similar to the following example. 1. With a text editor, open the BRTools initialization file, init<DBSID>.sap, which is typically located in the following directory: On Microsoft Windows systems: %ORACLE_HOME%\DATABASE On UNIX systems: $ORACLE_HOME/dbs 2. Set the backup device type parameter to use the RMAN utility by specifying the following:
backup_dev_type = rman_util
3. Uncomment the line for the rman_send parameter and set it to include each NetWorker-specific (NSR_*) parameter that is appropriate for your backup, restore, and inquiry sessions. NMSAP parameters for RMAN backups and restores on page 92 lists these parameters. The parameter names are case-sensitive and use the following syntax:
rman_send="NSR_ENV=(var1=value, var2=value, ...)"
22
Examples:
rman_parms="ENV=(NSR_DEBUG_LEVEL=9, NSR_SERVER=bu-libra)"
or
rman_channels=2 rman_send=("channel sbt_1 'NSR_ENV= NSR_DATA_VOLUME_POOL=pool_name)'", "channel sbt_2 'NSR_ENV=(NSR_NSR_DATA_VOLUME_POOL=pool_name)'")
The SAP documentation provides information on the use of the BRTools with RMAN program for backup and restore operations.
Configuring a scheduled backup with the wizard

The wizard is a Java application that runs from the NetWorker Management Console (NMC). The configurations for scheduled backups created with the wizard are stored on the NetWorker server. Configuring a scheduled backup without the wizard on page 26 describes the non-wizard method of configuring a scheduled backup.
Wizard workflows
The wizard provides the option of a typical or custom configuration, which depends on the amount of detail needed for specific scheduled backup configurations. The typical workflow allows you to configure a backup with fewer clicks by using default backup settings. The typical configuration configures a full offline backup of the whole database. The custom configuration allows you to:
Use existing NMSAP parameter, init<DBSID>.utl, and configuration, nsrsapsv.cfg, files as an initial input to the wizard configuration. Customize backup options, for example to configure: Number of NMSAP backup sessions to use Specific database objects to back up Online backup to run Backup level Additional backup parameters
Extract the created wizard configuration to a client-side parameter file (init<DBSID>.utl) and configuration file (nsrsapsv.cfg).
Wizard limitations
The wizard has the following limitations:
Some NetWorker resources and settings must be configured outside of the wizard with the NMC program, for example: Device resources Media Pool resources Deduplication Node resource NetWorker user privileges
Configuring a scheduled backup without the wizard on page 26 gives details.
Configuring a scheduled backup with the wizard
23
The wizard does not support the configuration of: RMAN backups snapshot backups (with NetWorker PowerSnap software) split-mirror backups (with EMC Replication Manager software) probe-based (event-based) backups
Wizard requirements
Before you use the wizard, ensure that all of the following requirements are met:
The required NetWorker releases are installed on the NMC server, NetWorker server, and NMSAP client hosts, as described in the EMC NetWorker Module for SAP with Oracle Release Notes and the EMC Information Protection Software Compatibility Guide. The NMC user that starts the wizard (the wizard user) must have Configure NetWorker privilege, and all its prerequisite privileges, on the NetWorker server where the configuration is created. Communication between the NMC server, NetWorker server, and NMSAP client must use nsrauth authentication. The NetWorker documentation provides the requirements for nsrauth authentication.
Configure a scheduled backup with the wizard

To create or modify a scheduled backup configuration with the wizard: 1. Ensure that the NMSAP software environment is properly configured. Verifying the NMSAP software requirements on page 20 provides details. 2. In the NetWorker Management Console (NMC) Enterprise view, select the NetWorker server name, and double-click the NetWorker application to launch it. 3. In the Configuration view, under the NetWorker server name, select Clients. To create a new NetWorker Client resource for NMSAP, right-click Clients and select Client Backup Configuration > New. To modify a NetWorker Client resource that was previously created with the wizard for NMSAP, right-click the client name and select Client Backup Configuration > Modify. 4. On each wizard page that appears, specify the options and values required for the backup configuration. You may click a link in the wizard steps panel to go directly to the page you want to modify. The number of steps shown in the steps panel may vary according to the chosen configuration type. 5. On the last wizard page named Review and Accept the Client Configuration, click Create or Modify to create or modify the configuration, and click Finish to exit the wizard. Configuring a deduplication backup on page 29 provides details on wizard settings for a deduplication backup. Chapter 6, Cluster and Oracle RAC Configurations, provides details on wizard settings for a cluster environment.
24
Converting client-side configurations to wizard configurations

The NMSAP 4.0 software, with supported NetWorker server and client software, allows for the conversion of scheduled backup settings from NMSAP client-side files (init<DBSID>.utl and nsrsapsv.cfg), to attributes on the NetWorker server that are used by the NMSAP wizard. After conversion, the configuration may be modified and updated only through the wizard. The NMSAP 4.0 software may run scheduled backups by using either wizard configurations or client-side parameter and configuration files.
Note: Manual backups performed with NMSAP 4.0 software require the use of client-side parameter and configuration files.
The conversion method uses the nsrsapadm utility to convert NMSAP 3.0.2 and later scheduled backup settings to the new wizard settings. This utility reads the backup parameter and configuration files found on the NMSAP client host and stores its converted settings on the NetWorker server. It changes the scheduled backup command, specified in the NetWorker Client resource, from: nsrsapsv -f filename to nsrsapsv. To convert with the nsrsapadm utility, perform the following steps on each SAP Oracle client to be backed up by the NetWorker server: 1. Log in to the SAP Oracle client as the user with Configure NetWorker privilege on the NetWorker server. 2. Ensure NetWorker client software and NMSAP software are installed on the SAP Oracle client and the client is specified as a NetWorker Client resource on the NetWorker server. 3. On the SAP Oracle client operating system command line (UNIX) or command prompt window (Windows), run the following command:
$ nsrsapadm -W -s server_name [query] query: [-c client_name] [-g group_name] [-N save_set_name]
where: -W specifies the conversion mode. -s server_name is the NetWorker server on which the configuration will be saved and run. query: -c client_name is the NetWorker Client resource whose backup settings are to be converted. If not specified, the default value is the hostname of the physical host where the nsrsapadm command runs. For cluster environments, this option must be set to the virtual client name. -g group_name is the NetWorker Group resource of the client being converted. If used, the group must already exist. -N save_set_name is the save set name used in the Client resource. For example:
nsrsapadm -W -s my.server.com -N backint:SAP1
The EMC NetWorker Module for SAP with Oracle Command Reference Guide provides details on the nsrsapadm command.
Converting client-side configurations to wizard configurations
25
Configuring a scheduled backup without the wizard

As an alternative to the wizard configuration, you may create and modify a scheduled backup by:

Manually creating the NMSAP parameter and configuration files Setting the NetWorker Client resources directly in the NMC program
The NMC interface also provides NetWorker Group, Device, Media Pool, and other resource settings that are not available in the wizard.
Configure the NMSAP parameters without the wizard

To configure NMSAP for a scheduled backup without using the wizard: 1. Ensure that the NMSAP software environment is properly configured. Verifying the NMSAP software requirements on page 20 provides details. 2. On the NMSAP client, copy the init.utl and nsrsapsv.cfg template files (supplied with the NMSAP installation) with new names suitable for your database instance, and configure them for the backup. Appendix A, NMSAP Parameter and Configuration Files, provides configuration details. 3. Encrypt the SAP operating system username and password, and if required, the Oracle database username and password, as follows: a. On the NMSAP client, log in as root or administrator and type the following NMSAP command:
nsrsapadm -P -z filename
where filename is the full pathname of the NMSAP backup configuration file (nsrsapsv.cfg) used for the backup. b. Follow the prompt instructions for the encryption. The configuration file is updated with the encrypted password authorizations.
Note: The Oracle database username and password must be set for probe-based backups. Configure a probe-based backup on page 33 gives details.
4. On the NMSAP client, configure the BRTools initialization file (init<DBSID>.sap) with the following parameters: Backup device type (backup_dev_type) Backup utility configuration file (util_par_file) Choosing either backint or RMAN as the backup and restore utility on page 21 provides more information.
26
Configure the scheduled backup resources without the wizard

On the NetWorker server, configure a NetWorker Client resource and other scheduled backup resources in NMC without the wizard as follows: 1. In the NMC Enterprise view, select the NetWorker server name, and double-click the NetWorker application to launch it. 2. In the Configuration view, under the NetWorker server name, select the appropriate backup resources to configure, such as Groups, Schedules, Clients, and so forth. For example: To create a new client, right-click Clients and select New. To modify an existing NMSAP client, double-click the client name to open its Properties window. On each of the properties tabs, specify the appropriate options and values for the backup configuration. 3. Configure the Group, Schedule and other NMC resource settings for scheduled NMSAP backups. The following sections highlight information that is specific to NMSAP. The EMC NetWorker Administration Guide and online help provide further details. Set the Schedule resource Create or select a Schedule resource to specify the days of the week when the scheduled backup runs. Set the Group resource Create or select a NetWorker backup Group resource to apply to a set of NetWorker clients, all of which will start to back up data at a scheduled time. Ensure that Autostart is set to Enabled. A Group resource may be applied as an attribute to a NetWorker Client resource and a NetWorker Media Pool resource. Set the Device resources Ensure that a NetWorker Device resource is configured for each supported storage device used for backup and restore operations.
Note: When creating Device resources, ensure that each physical device contains a labeled and mounted storage media volume.
Set the Media Pool resource Configure the volumes in each NetWorker Media Pool resource to receive specific types of backup data, such as tablespaces or archived logs. When configuring the Media Pool resources, leave the Save Sets attribute blank. The NMSAP program sets the Save Sets during each backup session. Set the Client resource Specify a NetWorker Client resource for each SAP Oracle server (NMSAP client) that requires backup, restore, and inquiry services. Table 3 on page 28 describes NMC Client resource attributes that are applicable to NMSAP operations.
Configuring a scheduled backup without the wizard
27
Table 3
NetWorker Client resource attributes for NMSAP scheduled backups Attribute Aliases Backup Command Description Specifies all known aliases for the host where the NMSAP software is installed. Specifies the name of the command to be used for a scheduled NMSAP backup, either: nsrsapsv which is configured by the wizard only and cannot be manually set, or nsrsapsv -f filename which uses the settings of the NMSAP configuration file (nsrsapsv.cfg). where filename is the full pathname of the NMSAP configuration file created as described in Configure the NMSAP parameters without the wizard on page 26, which resides on the NMSAP client host. The pathname may contain only ASCII characters. Because the Backup Command attribute is limited to 64 characters, the following default path is recommended: On Microsoft Windows systems: NetWorker_install_directory\nsr\res\nsrsapsv<DBSID>.cfg On UNIX systems: /nsr/res/nsrsapsv<DBSID>.cfg Specifies the length of time that the NetWorker server retains an entry for the backup in the online client file index. When selected, enables deduplication backup and restore. Specifies the hostname of the Avamar server that will store the deduplicated backup. Identifies a set of NetWorker Group resource to be used for a scheduled NMSAP backup. Specifies the hostname of the SAP server host where the NMSAP software is installed. Specifies the maximum number of concurrent backup and restore sessions to use for a backup operation. This Client resource attribute may be used instead of the parallelism setting in the parameter file or wizard configuration. Specifies the password for the Remote User attribute. Specifies the SAP user and fully qualified hostname (IP) of a remote host, used to enable backups in a cluster environment, and restores of the backups to that remote system. For a cluster backup, specifies sap_user@physical_host for each physical host in the cluster. For restore of a backup from this host to a different destination host, specifies sap_user@different_host. Recommended for backups on Microsoft Windows systems. Not needed on UNIX systems. Specifies the SAP users operating system username. Specifies the minimum length of time that must elapse before backed-up data is eligible to be overwritten on the backup media. Specifies the database to be backed up. The save set name must be specified in the following format: backint:<DBSID> Specifies the NetWorker backup Schedule resource to use for a scheduled backup.
Browse Policy Deduplication Backup Deduplication Node Group Name Parallelism
Password Remote Access
Remote User Retention Policy Save Set
Schedule
28
Configuring a manual backup

To configure a manual NMSAP backup: 1. Ensure that all the steps described in Verifying the NMSAP software requirements on page 20 are done. 2. Configure the NMSAP parameter file, init<DBSID>.utl, with the settings for the appropriate NetWorker server and other backup parameters. Configure the NMSAP parameter file on page 82 provides details. 3. Set the BRTools initialization file, init<DBSID>.sap, with parameters for Backup device type (backup_dev_type) Backup utility configuration file (util_par_file) Choosing either backint or RMAN as the backup and restore utility on page 21 provides details.
Configuring a deduplication backup

This section describes requirements, best practices, and configuration details for deduplication NMSAP backup. Chapter 6, Cluster and Oracle RAC Configurations, gives information on additional steps for deduplication backup configuration in cluster and RAC environments.
Requirements for a deduplication backup

Ensure that the following requirements for deduplication backup are met:
The NetWorker client and server releases support deduplication. The EMC Information Protection Software Compatibility Guide on the Powerlink website provides details. The Avamar server is installed and configured as a NetWorker deduplication node. The EMC NetWorker Administration Guide provides details. The NetWorker backup device, which receives only the backup metadata during the NMSAP deduplication backup, is configured as an advanced file type device (AFTD). The EMC NetWorker Administration Guide and release notes provide details.
Best practices for a deduplication backup

This section provides recommendations on when to use NMSAP deduplication, and configuration tips to improve deduplication backup performance. Benefits The benefits of deduplication depend on the environment. Deduplication can be beneficial in a data warehouse environment where the data does not change frequently. It can also be beneficial for databases where only a small percentage of data is updated repeatedly, or where new data is added to a database but the old data does not change much.
Configuring a manual backup
29
Performance
The following practices can improve deduplication backup performance:
Once an Avamar server is chosen as the deduplication node for an initial full backup of a client, continue to use that same node for all backups of the client, to take advantage of the client deduplication information stored on the node. Deduplication is not recommended for RMAN incremental backups. Because only data blocks that have changed are backed up, incremental backups result in a low rate of duplication and the benefit is likely to be insignificant. Do not include a deduplication client in the same Group resource as non-deduplication clients. Depending on computer resources, avoid setting backup parallelism to more than four. Schedule deduplication backups to avoid Avamar server read-only periods. An Avamar server spends periods of time in maintenance mode, where it may be unavailable for backup or have limited bandwidth.
Note: A deduplication NMSAP backup that runs during a maintenance period may be suspended until the Avamar server resources become available.
The Avamar and NetWorker documentation provide more information on Avamar server and NetWorker requirements for deduplication backups.
Configure deduplication for a scheduled backup

A scheduled deduplication backup may be configured with either the wizard or with individual settings in the NMC program. Wizard method Configure a scheduled deduplication backup with the wizard as follows: 1. Ensure a NetWorker Deduplication Node resource is created for the Avamar server. 2. Follow the instructions in Configuring a scheduled backup without the wizard on page 26. 3. On the Specify the Deduplication Options wizard page, apply these additional settings: Select the Deduplication Backup attribute to enable deduplication. Select the deduplication node (Avamar server) that will store the deduplicated backup data. 4. On the Specify Log Files Locations and Additional Options wizard page, in the table, set NSR_NWPATH parameter to the location of NetWorker client. 5. For typical operations, use the default settings for cache usage and chunk size. However, if nondefault settings are required, set the following parameters in the table on the Specify Log Files Locations and Additional Options wizard page: NSR_DEDUP_CACHE_ENABLED NSR_DEDUP_CHUNK_SIZE NSR_DEDUP_CACHE_TAG Appendix A, NMSAP Parameter and Configuration Files, provides details on these parameters.
30
Non-wizard method
Configure a scheduled deduplication backup with specific settings in the NMC program, instead of the wizard, as follows: 1. Ensure that a NetWorker Deduplication Node resource is created for the Avamar server. 2. Follow the instructions in Configuring a scheduled backup without the wizard on page 26. 3. In the Client resource for the NMSAP client host, set the following attributes: Select the Deduplication Backup attribute to enable deduplication. Select the deduplication node (Avamar server) that will store the deduplicated backup data. 4. In the NMSAP parameter file, init<DBSID>.utl, set the NSR_NWPATH parameter to the location of NetWorker client. 5. For typical operations, use the default settings for cache usage and chunk size. However, if nondefault settings are required, the following parameters may be set in the NMSAP parameter file (init<DBSID>.utl: NSR_DEDUP_CACHE_ENABLED NSR_DEDUP_CHUNK_SIZE NSR_DEDUP_CACHE_TAG Appendix A, NMSAP Parameter and Configuration Files, provides details on these parameters.
Configure deduplication for a manual backup

To include deduplication in a manual backup that uses the NMSAP backint program: 1. Ensure a NetWorker Deduplication Node resource is created for the Avamar server. 2. Create a NetWorker Client resource for the SAP Oracle host and set the following attributes: Select the Deduplication Backup attribute to enable deduplication. Select the deduplication node (Avamar server) that will store the deduplicated backup data. 3. Edit the NMSAP parameter file (init<DBSID>.utl) with the following settings: NSR_DEDUP_BACKUP = TRUE. NSR_DEDUP_NODE = NetWorker_deduplication_node This name must exactly match the Deduplication Node name selected in the Client resource.
Configuring a deduplication backup
31
Configure deduplication for Oracle RMAN backup

To include deduplication in a scheduled or manual backup that uses the Oracle RMAN utility: 1. Ensure a NetWorker Deduplication Node resource is created for the Avamar server. 2. Create a NetWorker Client resource for the SAP Oracle host and set the following attributes: Select the Deduplication Backup attribute to enable deduplication. Select the deduplication node (Avamar server) that will store the deduplicated backup data. 3. On the SAP Oracle server, edit the BRTools parameter file (init<DBSID>.sap) and configure the rman_send parameter with the following settings. NSR_DEDUP_BACKUP. Mandatory for manual backups only. NSR_DEDUP_NODE. Mandatory for manual backups only. NSR_DEDUP_CACHE_TAG. Mandatory for backup with more than one RMAN channel. Set this parameter to a different value for each channel. The following example shows an rman_send parameter configured for a manual deduplication backup:
rman_channels=2 rman_send=( "'NSR_ENV=(NSR_DEDUP_BACKUP=TRUE, NSR_DEDUP_NODE=test.emc.com)'", "channel sbt_1 'NSR_ENV=(NSR_DEDUP_CACHE_TAG=orcl10g_1)'", "channel sbt_2 'NSR_ENV=(NSR_DEDUP_CACHE_TAG=orcl10g_2)'")
Appendix A, NMSAP Parameter and Configuration Files, gives details on the parameters.
Configuring a probe-based backup

The NetWorker Probe resource is an optional feature that triggers backups when user-specified conditions are met. A probe-based backup is also known as an event-based backup.
Note: A scheduled backup group that is enabled for a probe will not run unless the probe conditions are met.
The probe-based backup is triggered when both of the following conditions are met:
The current time is within a specified window of time. The backup window is defined by the probe start and end times in the probe-enabled backup Group resource. One of the following conditions is met: A specified amount of time has elapsed since the previous probe-based backup. One or all of the probes associated with the backup are successful, depending on the probe success criteria specified in the backup configuration. The probe success criteria can be set in the NetWorker Group resource to the value of Any or All.
32
Configure a probe-based backup

A probe-based NMSAP backup requires settings in three NetWorker resources: Probe, Group, and Client. To configure a probe-based NMSAP backup: 1. Create a separate NetWorker Probe resource for the supplied NMSAP nsrsapprobe program and any other program or script that checks for a user-defined condition. The Probe resource defines the conditions that trigger the probe-based backup.
IMPORTANT Because a NetWorker Probe resource stores information on the state of database redo logs, it must be associated with a single NetWorker Client resource only. Multiple databases configured through multiple Client resources require a separate Probe resource for each client. A script written for a user-defined probe may be associated with more than one NetWorker Client. Table 4 on page 33 describes Probe resource attributes for NMSAP backups.
Table 4
NetWorker Probe resource attributes for NMSAP backups Attribute Name Probe Command Description A unique name that identifies the Probe resource. Name of the program or script that triggers a probe-based backup. For example, the nsrsapprobe program, which is supplied with NMSAP software, triggers a backup when the number of Oracle transaction (archived redo) logs generated since the last probe-based backup meets or exceeds the value of the LOG_THRESHOLD parameter. The Probe Command may be a user-defined program or script. User-defined probes on page 34 provides details. Required for the nsrsapprobe program only. A comma-separated list of parameters with their settings as follows: LOG_THRESHOLDMandatory. Specifies the number of Oracle transaction (archived redo) logs generated since the last probe-based backup, which will trigger a new probe-based backup. ORACLE_SERVICEMandatory. Specifies the Net service name for the Oracle database that is to be probed. Note: If this Probe resource is associated with a Client resource that is configured with the wizard and contains the ORACLE_SERVICE parameter, then the values for ORACLE_SERVICE must match in both resources. NSR_DEBUG_DIROptional. Specifies a valid directory path where debug information for probe operations is recorded in a nsrsapprobe_pid.log file. For example: ORACLE_SERVICE=SAP.world,LOG_THRESHOLD=10
Command Options
2. Create a NetWorker Group resource for the probe-based backup. Configure the Group resource to enable probe-based backups and set the probe timing options. The EMC NetWorker Administration Guide provides details. 3. Associate the NetWorker Probe resource with a Client resource. This setting cannot be done with the wizard, but must be done with the individual NMC
Configuring a probe-based backup
33
resource settings. Table 5 on page 34 describes the required Client resource attributes for NMSAP probe-based backups.
IMPORTANT Probe-based backups use Oracle database authentication. The Oracle database username and password must be set in the backup configuration, either through the wizard or encrypted in the nsrsapsv.cfg file.
Table 5
NetWorker Client resource attributes for probe-based NMSAP backups Attribute Description
Probe Resource Name Specify the name of the Probe resource from step 1 . Note: A Client resource can be associated with only one probe. Group Specify the name of the probe-enabled Group resource from step 2 .
The EMC NetWorker Administration Guide provides further details.
User-defined probes
The user-defined script or program for probe-based backups must meet the following requirements:

Name starts with nsr or save. Location is in the same directory that contains the NetWorker client binaries. Permissions of the script or program file include the execute permission. Returns one of the following code values when it finishes running its probe: 0 Signifies that the backup condition has been met. 1 Signifies that the backup condition has not been met. Other than 0 or 1 Signifies that an error occurred during the probe.
Example probe-based backup with multiple probes

A probe-based backup may be configured with multiple probes. Depending on the Probe Success Criteria setting in the Group resource, a backup will start when the conditions for any or all of the probes are met. For example, a probe-based backup could be triggered when both of the following conditions are true:
At least 25 Oracle transaction log files are generated on an SAP Oracle client named, for example, oraprod_host. A Probe resource for this condition will use the supplied nsrsapprobe program. More than two tape drives are idle in a tape library attached to a NetWorker storage node, named for example libstore_host, where the probe-based backup will be sent for storage. A second Probe resource for this condition will use a user-defined script named nsrjukeboxprobe.
34
To configure an example probe-based backup with these two conditions: 1. Create the NetWorker Probe resource for the supplied nsrsapprobe program with the following attributes: Name: myxlogs Probe Command: nsrsapprobe Command Options: LOG_THRESHOLD=25 2. Create a user-defined script, nsrjukeboxprobe, with execute permissions and store the script in the same directory as the NetWorker binaries on libstore_host. When the script runs, it checks for the number of idle tape drives in the library, and returns one of the following values: 0 If more than two tape drives are idle in the library. 1 If two or fewer tape drives are idle in the library. Other than 0 or 1 An error occurred during the probe and no backup will be performed. 3. Create a second NetWorker Probe resource for the user-defined probe with the following attributes: Name: myxdrives Probe Command: nsrjukeboxprobe Command Options: (blank) 4. Create a NetWorker Group resource, named for example probe_group, and configure the required probe attributes, with the Probe Success Criteria attribute set to All. 5. Create a NetWorker Client resource for the NMSAP backup of oraprod_host with the following attributes: Name oraprod_host Backup Command nsrsapsv -f Group probe_group Probe myxlogs Save Set backint:<DBSID>
6. Create a NetWorker Schedule resource named skip_all and set the level to skip for each day in the schedule. This will allow a probe to run without running a backup. 7. Create a dummy Client resource for the libstore_host storage node with the skip-all schedule and the following attributes: Name libstore_host Backup Command (blank) Group probe_group Probe myxdrives Save Set my_skip_set Schedule skip_all
Configuring backup email notifications

Email notifications of NMSAP backup results are available on all supported platforms, provided a command line utility is used to convey the email.

On UNIX systems, the mailx utility is supplied. On Microsoft Windows systems, any of various supported e-mail utilities, available on the Internet, may be used.
Configuring backup email notifications
35
If the wizard is used to configure a backup, set the following parameters in the Advanced Options table: notify_done, notify_error, notify_start, and notify_success. If an NMSAP parameter file (init<DBSID>.utl) is used for the backup, set the notify_done, notify_error, notify_start, and notify_success parameters in that parameter file.
36
3
Backup Procedures

Performing scheduled backups................................................................................... Performing a manual backup ...................................................................................... Reviewing backup and restore session reports......................................................... Verifying the backup information in the NetWorker indexes ................................ Cloning backups............................................................................................................
38 39 41 41 42
Backup Procedures
37
Backup Procedures
Performing scheduled backups

This section describes how to test, monitor, and cancel scheduled NMSAP backups. This section does not describe how to perform snapshot backups, which are described separately other chapters: Chapter 7, Snapshot Backup with PowerSnap, and Chapter 8, Split-Mirror Backup with Replication Manager.
Test a scheduled backup

Backups that are scheduled with NetWorker programs are configured to run automatically according to their schedules. However, after a scheduled backup has been configured, it may be manually tested. Requirements Before testing a scheduled backup, ensure the following requirements:
The software environment is properly set up, including the requirement for read and write access to a common parent directory for all files associated with the backup. Verifying the NMSAP software requirements on page 20 provides details. The NetWorker Client resource has been created with a properly configured save set and backup command The Client resource has been assigned to a backup group Any pre- and post-processing scripts are in defined (optional).
Test a scheduled backup
To test a scheduled backup with the NetWorker Management Console (NMC): 1. Start the NMC program. 2. Select the appropriate NetWorker server to perform the backup. 3. Select the group to monitor for the test. 4. Start the scheduled backup for the specified group.
Monitor a scheduled backup

The NMC program provides a centralized view of all backup and recovery activity throughout an entire enterprise, as well as operations related to devices and libraries, and managed events that require user intervention. To monitor a scheduled backup: 1. Run the NMC program. 2. Select the backup group in the monitor view. The Details window displays details of backups that are currently running, successfully completed, or failed.
Note: For a deduplication backup, the NMC display shows the total size of the data prior to deduplication, not the size of the deduplicated data. The display also does not indicate that the data is for a deduplication backup.
Appendix C, Troubleshooting, provides information on how to review diagnostic and error messages.
38
Backup Procedures
Cancel a scheduled backup

To cancel a scheduled backup in progress: 1. Run the NMC program. 2. Select the backup group in the monitor view. 3. Right-click the group to stop and select Stop.
Note: If a backup is canceled before completion, none of the backed-up data may be recoverable. To manually start a canceled backup process from the beginning, right-click the group to start, and select Start. Ensure that the backup successfully completes without interruption.
Performing a manual backup

This section describes how to perform a manual NMSAP backup and NetWorker bootstrap backup, and also how to monitor and cancel a manual NMSAP backup.
Requirements
Before running a manual backup, ensure the following requirements are met:
The software environment is properly set up, including the requirement for read and write access to a common parent directory for all files associated with the backup. Verifying the NMSAP software requirements on page 20 provides details. The server parameter in the NMSAP parameter file, init<DBSID>.utl, is set for the appropriate NetWorker server. Configure the NMSAP parameter file on page 82 provides details. The BRTools initialization file, init<DBSID>.sap, is set with parameters for: Backup device type (backup_dev_type) Backup utility configuration file (util_par_file) Choosing either backint or RMAN as the backup and restore utility on page 21 provides details.
Run a manual backup
Perform a manual backup as illustrated by the following example: 1. Type the SAP backup command with the appropriate parameters to back up the SAP Oracle database instance or the selected objects to the NetWorker server, for example: Offline backup:
brbackup -m all -t offline [-d util_file]
Online backup:
brbackup -m backup_objects -t online [-d util_file_online]
Appendix B, Examples of SAP Command Options, provides information on available brbackup command options. 2. If an online backup is performed, back up the archived redo logs by the typing the additional command:
brarchive
Performing a manual backup
39
Backup Procedures
Note: Without the redo logs, a database that was backed up online can be recovered only to the time of its last full backup.
3. Back up the client file indexes and bootstrap. Back up the NetWorker bootstrap and online indexes on page 40 provides instructions.
Back up the NetWorker bootstrap and online indexes

The bootstrap is a special save set that the NetWorker server software creates in preparation for disaster recovery. The bootstrap save set contains the information needed to restore the online NetWorker indexes and resource configuration files to the state just before the bootstrap was created. The NetWorker server automatically performs a backup of the bootstrap and client indexes of the database or application host at the end of a scheduled backup. Manual backups do not back up the bootstrap and client indexes.
Note: If only manual backups are run, and the bootstrap and client indexes are not backed up manually, then no backups of the bootstrap and client indexes will be available for use in the event of a disaster recovery on the NetWorker server.
To back up the NetWorker server bootstrap and client file indexes: 1. On the NetWorker server, log in as the root user (UNIX) or administrator (Microsoft Windows), and at the operating system command line enter the following command:
savegrp -O -l full -c NW_client_name -s NW_server_name [-P printer_name]
where: -O saves only the bootstrap file and index files for the client on the associated NetWorker server without backing up the client database files. NW_client_name is the hostname of the NMSAP client host. NW_server_name is the hostname of the NetWorker server. printer_name is the name of the printer where the bootstrap information is printed at the end of the bootstrap backup, instead of being sent through email notification. Confirmation of the savegrp completion appears in the NMC program. 2. Store the bootstrap printout in a safe place. The EMC NetWorker Command Reference Guide and the UNIX man pages provide more information on the savegrp command. The EMC NetWorker Administration Guide has more information on bootstrap backups.
40
Backup Procedures
Monitor a manual backup

Operational messages on the status of manual NMSAP backups are displayed at the command line or GUI where the backup is started. Also, the NMC program provides a centralized view of all NetWorker server backup and restore activity, as well as device and library operations and managed events that require user intervention. The EMC NetWorker Administration Guide provides information on reviewing NMC progress and completion messages. Appendix C, Troubleshooting, provides information on how to review diagnostic and error messages.
Cancel a manual backup

To cancel a running manual backup, press either Ctrl+C, or the equivalent attention key combination on the system.
Reviewing backup and restore session reports

During backup or restore sessions, the NMSAP backint program appends a report to a sessions log file on each NMSAP host. The default location for the log is:

On Microsoft Windows systems: NetWorker_install_directory\nsr\applogs On UNIX or Linux systems: /nsr/applogs
The default format for the log filename is backint<DBSID>.log.raw. This backup sessions log can be written to a different location by using a different name, as specified in the backint_log, arch_backint_log parameters. This sessions log is in I18N format, and must be run through the NetWorker nsr_render_log utility to be readable.
Verifying the backup information in the NetWorker indexes

The following sections describe how to verify the backup information that is stored in the NetWorker online indexes for NMSAP backups. The EMC NetWorker Administration Guide the NetWorker online indexes in detail.
Verify backup information in the NetWorker indexes

To review information about NMSAP scheduled and manual backups in the NetWorker online indexes, use the following commands:
To query the client file index, use the nsrinfo command. For example:
nsrinfo -s networker_server_hostname nmsap_client_hostname Note: The deduplication backup size (size field) recorded in the NetWorker index contains only the NetWorker save file metadata and does not include the size of the data backed up during the deduplication backup.
To query the media database, use the mminfo command. For example:
mminfo -v -s networker_server_hostname -c nmsap_client_hostname
Reviewing backup and restore session reports
41
Backup Procedures
Note: The deduplication save set size (size field) reported by the mminfo command includes only the size of the NetWorker save set metadata.
To view only save sets created as part of a deduplication backup, use the mminfo command with the -q dedupe option. To list the extended attributes for the deduplication backups, add the -S option, which provides information on the total size of data protected as well as the amount of new data passed to the Avamar server during backup. For example:
# mminfo -S -q dedupe ssid=1968946304 savetime=12/31/08 13:39:59 (1230748799) molecule.lss.emc.com:backint:CER_12330 level=full sflags=vF size=24828 files=18 insert=12/31/08 create=12/31/08 complete=12/31/08 browse=01/31/09 23:59:59 retent=12/31/09 23:59:59 clientid=b24d1144-00000004-49468a5a-49468a56-00040003-bab08c2d *ACTUAL_HOST: molecule.lss.emc.com; *Client path: \ /NetWorker/molecule.lss.emc.com/molecule.lss.emc.com; *Data set size: 19333120; *De-Dup session id: 388; *De-Dup snapup time: 2008-12-31; *De-duplication: Yes; *De-duplication host: bu-doppelganger.lss.emc.com; *Domain: /NetWorker/molecule.lss.emc.com; *New data on De-Dup Node: 18596.00; *New files: 4; *Size on De-Dup Node: 19333120.00; Clone #1: cloneid=1230748800 time=12/31/08 13:40:00 retent=12/31/09 flags=F frag@ 0 volid=2002500679 file/rec=1968946304/0 rn=0 last=12/31/08
The EMC NetWorker Command Reference Guide, and EMC NetWorker Administration Guide provide more information on the nsrinfo and mminfo commands. Deletion and expiry of deduplication backups When a deduplication backup is deleted (for example, by a user or the NetWorker server), the backup information is deleted immediately from the NetWorker indexes, and a request is queued for deletion of the backup from the Avamar server. Once a deduplication save set exceeds its retention time and its data chunks are deleted from the Avamar server, the save sets are no longer recoverable with the scanner program. The EMC NetWorker Administration Guide provide more information on the deletion of deduplication backups.
Cloning backups
Cloning is an NMSAP process that makes an exact copy of saved data from a storage volume to a clone volume. Individual save sets or the entire contents of a storage volume may be cloned. Because the process clones only complete save sets, additional clone volumes are requested if a save set spans multiple volumes. The clone volumes are indistinguishable from the original, except that the volume labels are different. NetWorker software indexes and tracks clones in both the client file index and the media database.
42
Backup Procedures
Note: Cloning deduplication backups will clone only the metadata stored on the NetWorker storage device and not the data stored by the Avamar server.
The sapclone command syntax and options

NMSAP backups of SAP Oracle databases can be cloned by running the NMSAP sapclone command from the NMSAP host. 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. Table 6 on page 43 lists the options to use with the sapclone command.
Table 6
The sapclone options Option -a Description Clones all the save sets of a client. If this option is not specified, the NMSAP program clones only save sets created in the last 24 hours. Example: sapclone -a -u SAP1 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. Example: sapclone -b SAPClone -u SAP1 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 data. Use this option for cloning data backed up from a cluster. For example, you can set this option to the name of the clusters virtual node. Example: sapclone -c saturn -u SAP1 Tests the cloning operation on the save sets for a client. 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 stored onto volumes of a clone pool. Example: sapclone -n -u SAP1 Specifies the destination NetWorker server. You need this option only if one of the following conditions is true: You clone to a NetWorker server other than the default server. You enter the sapclone command on a SAP Oracle server. Example: sapclone -s mars -u SAP1 Mandatory. Specifies the Oracle database with the save sets to be cloned. Example: sapclone -u SAP1
-b pool
-c client
-n
-s server
-u user
Cloning backups
43
Backup Procedures
44
4

Restoring and recovering data .................................................................................... 46 Performing a restore and recovery ............................................................................. 46
45
Restoring and recovering data

This chapter describes how to configure and perform SAP Oracle data restore operations, including how to redirect a restore to a different client hostname, and how to recover a database to a consistent state.
Restore and recover
Unlike the NetWorker software, which uses the term recover for all backup retrieval activities, this NetWorker Module software distinguishes between the restore and recovery of a database:
Restore means to retrieve individual datafiles from backup and store the files on disk. Recover means to apply the database transaction logs to update the database to a specific point in time and to make it consistent..
The backup lifecycle
NetWorker software manages the backup lifecycle of data through browse and retention policies. These are set for each file and NetWorker save set respectively at backup time through the NetWorker Client resource browse and retention attributes or the NMSAP NSR_SAVESET_BROWSE and NSR_SAVESET_RETENTION parameters.
The browse policy determines how long backed-up files are maintained in the clients file index on the NetWorker server. The retention policy determines how long save set entries are maintained in the NetWorker servers media database.
When a file entry expires from the NetWorker client index, the NMSAP software is not able to restore the specified file. You may use the NetWorker scanner program to re-create the missing entry as long as the volume of the NetWorker saveset containing the save file is not recycled. After a save set's retention policy expires and the volume that contains the save set is recycled, the backup cannot be recovered.
Set the browse policy to be at least as long as your Recovery Point Objective (RPO). Set the retention policy to be at least as long as or longer than the browse policy.
The EMC NetWorker Administration Guide provides details on browse and retention policies.
Performing a restore and recovery

All NMSAP recovery operations are performed manually on an SAP Oracle host by using, for example, the SAP BrGui interface or the brrestore or brrecover commands. The NMSAP software can recover only data that was backed up with NMSAP software. To recover an entire database or a subset of database objects, such as a tablespace or datafile: 1. Ensure the NMSAP environment is configured with all necessary requirements. Verifying the NMSAP software requirements on page 20 provides details. 2. Ensure that the NetWorker server and the NetWorker client services are running.
46
3. (Optional) To restore the data to a different SAP Oracle host (destination host) than the one that was backed up: a. Ensure that the NMSAP software is installed and configured on the new destination host. b. On the NetWorker server that contains the backup to be restored, set the Remote Access attribute in the Client resource of the backed up NMSAP host to sap_user@destination_host.
Note: Users may recover only files for which they have read permission, based on file operating system permissions at the time that the files were backed up.
c. Perform steps 4 through 9 on the new destination host. 4. Ensure that the BRTools initialization file (init<DBSID>.sap) is configured for either utl_file or rman_util as the backup device type, or use the proper brrestore or brrecover options. Choosing either backint or RMAN as the backup and restore utility on page 21 provides details. 5. Ensure that the NMSAP parameter file (init<DBSID>.utl) is configured for the appropriate parameters. The server parameter must be set to the hostname of the NetWorker server that contains the backup to be restored. The client parameter must be set to the hostname of the NMSAP host that was backed up, if it is different than the destination host. The parallelism setting should be the same that was used to make the backup. Typically, it is set to the number of target sessions accepted by the devices, which should be equal to or less than the NetWorker parallelism setting. If you restore the SAP Oracle data to a new location and only the top common data directory changes, but the subdirectory structure remains the same as it was at backup time, then you may set the NSR_RELOCATION_DEST parameter to the new top data directory to improve the restore performance. The new destination directory is determined by BRTool programs. For example, brrestore -m object=new_destination. If the common directory for the files being restored, as determined by brrestore, does not match the path set in the NSR_RELOCATION_DEST, then the NSR_RELOCATION_DEST setting is ignored. Configure the NMSAP parameter file on page 82 and Examples of brrestore command syntax and options on page 99 provide details on these configurations. 6. Ensure that the backup to be restored exists by using an inquire function before performing a restore operation. For example, to inquire for the latest backup, type the following command:
brrestore -verify [use_dbv|only_conf]
The files are read from backup media but are not restored. 7. Prepare for the restore operation as follows: For a full restore, shut down the Oracle database instance. For the restore of a single database object, take that database object offline. 8. Perform the restore operation by using BRTools interfaces.
Performing a restore and recovery
47
CAUTION The brrestore program, when used for a restore operation, whether invoked directly from the command line or indirectly from the brrecover command or the BrGui interface, first deletes all the original files to be restored before it invokes backint to restore the backed up files. If brrestore or backint fails, then the original files are lost. An alternative method is to restore the files to a different location. Use the -m parameter, and specify the restore destination, for example:
brrestore -m tablespace_name=restore_directory
Appendix B, Examples of SAP Command Options, contains examples of brrestore and brrecover commands and options. Details of these and other SAP commands can be found in the appropriate SAP documentation. 9. To apply redo logs to recover a database, refer to the appropriate SAP and Oracle documentation. Reviewing backup and restore session reports on page 41 gives details on backup and restore log information.
Restart a restore for files that failed to be restored

During a restore operation, NMSAP attempts to restore all requested files even if some files fail to be restored. When a restore session is complete, you can restart the restore operation for the files that failed as follows: 1. On the NMSAP host, inspect the restore session log and troubleshoot the error messages for files that failed to be restored. Reviewing backup and restore session reports on page 41 gives details. 2. On a command line, complete the restore by applying the brrestore -f command to the appropriate brrestore logs. Examples: To restore the files that failed to be restored during the last two restore sessions: a. Find the restore logs for these two sessions in the SAPBACKUP directory, for example, reaxdwie.rsb and reasdwap.rsb. b. Enter the following command for these logs:
brrestore -f reaxdwie.rsb, reasdwap.rsb
To restore the files that were not restored during the last restore session, enter:
brrestore -f last
To restore files that failed to be restored in all the restore sessions that were run in the last 3 days, enter:
brrestore -f 3
48
5
Disaster Recovery

Requirements for disaster recovery............................................................................ 50 Recovering from a disaster .......................................................................................... 50
Disaster Recovery
49
Disaster Recovery
Requirements for disaster recovery

For a comprehensive disaster recovery plan, it is necessary to fully reconstruct the computing environment and all the SAP Oracle server (NMSAP host) files that are associated with maintaining data. Complete backup protection on page 12 describes the impacts of incomplete protection.
Protect the computing environment

Maintain accurate and complete records of the network and system configurations. Keep all the original software media in a safe location. Include the following:

Original operating system media and patches Original NetWorker media Device drivers and device names File system configuration IP addresses and hostnames NetWorker bootstrap and client index information The NetWorker bootstrap and client index information is required to perform disaster recovery of the NetWorker server, a separate procedure that is not covered in this chapter. Back up the NetWorker bootstrap and online indexes on page 40 provides information.
The EMC NetWorker Disaster Recovery Guide provides information on how to recover the NetWorker server, and a NetWorker client or storage node, from various types of disasters.
Recovering from a disaster

To recover from a disaster, first restore lost Oracle and SAP configuration files and lost BRTools backup log files. After these files are restored, you can perform a database point-in-time recovery or a whole database reset.
Restore the required Oracle and SAP BRTools files

The following procedure is a concise version of the disaster recovery steps described in the SAP documentation, modified for the specific requirements of NMSAP. The procedure can be performed on the original host or a new host, either of which is called the destination host. 1. If the entire SAP Oracle system has been lost: a. Reinstall all the required software components described in NMSAP and associated software on page 16. b. Reconfigure the SAP data layout (such as the SAPDATA_HOME directory and its subdirectories) to the same state as before the disaster.
50
Disaster Recovery
2. (Optional) If restoring to a different destination host, on the NetWorker server that contains the backup to be restored, set the Remote Access attribute in the original Client resource to sap_user@destination_host.
Note: Users may recover only files for which they have read permission, based on file operating system permissions at the time that the files were backed up.
3. Ensure that the storage volumes with the required Oracle and SAP configuration files and the BRTools backup log files are loaded on the NetWorker server or storage node. 4. Configure the NMSAP parameter file (init<DBSID>.utl) for recovery in the default location on the destination host: UNIX or Linux systems: $ORACLE_HOME/dbs Microsoft Windows systems: %ORACLE_HOME%\database 5. On the destination host, start BRTools or BrGui and follow the on-screen instructions to perform a disaster recovery of profiles and logs. The SAP documentation provides provides more details on disaster recovery.
Recover a SAP Oracle database after disaster

After the correct SAP BRTools profiles and logs are restored on the NMSAP host, follow the regular BRTools recovery procedure to perform database point-in-time recovery or database reset. Performing a restore and recovery on page 46 gives the procedure to recover an SAP Oracle database. The SAP documentation provides provides further details on database recovery.
Recovering from a disaster
51
Disaster Recovery
52
6

Cluster systems.............................................................................................................. 54 Oracle RAC systems ..................................................................................................... 56
53
Cluster systems
A cluster environment consists of two or more linked nodes that provide redundant database processing. The NMSAP software backs up the data from the client nodes in the cluster and stores it under a single hostname. The NMSAP software supports active-passive cluster configurations with the procedures described in this section. Oracle RAC systems on page 56 describes active-active application cluster configurations.
Configuring a scheduled backup in a cluster

To configure NMSAP scheduled backups in a cluster: 1. Ensure that the NetWorker server is remote and not a part of the cluster environment. 2. Ensure that the NMSAP software is installed on a local disk on all physical nodes of the cluster designated to perform a backup. 3. If configuration and parameter files are to be used (instead of the wizard) to configure a backup on the cluster, ensure that these files are stored in the same location on each physical node, or on a shared disk. 4. Configure a scheduled backup for the cluster by using one of the following methods: Wizard method on page 54 Non-wizard method on page 55 Wizard method Follow the procedure for Configure a scheduled backup with the wizard on page 24, keeping in mind the following cluster-specific requirements. 1. On the Specify the Client Name page, type the name of the virtual host for the cluster and select the Virtual Client check box. 2. On the Specify Log File Locations and Additional Options page, in the Advanced Options table, ensure the client parameter is set to the virtual hostname. 3. On the Select the NetWorker Client Properties page, add sap_user@physical_host to the Remote Access field for each physical host in the cluster. Using these settings, the wizard will do the following:
Create a NetWorker Client resource for the virtual host with the usual settings for scheduled backups and the following additional settings: The Backup Command attribute will contain -c virtual_clientname. The Remote Access attribute will contain the sap_user@physical_host entries.
Create a generic NetWorker Client resource (with the saveset attribute set to All and not assigned to any group) for each physical node, if they do not already exist. Grant access (ACL rights) to the Lockbox resource for the virtual host to system/root user and sap_user on each physical host.
Note: If additional users need ACL rights to the Lockbox, you can add them to the Lockbox resource directly in NMC.
54
Non-wizard method
Follow the procedure for Configuring a scheduled backup without the wizard on page 26 to create the configuration for the virtual host, keeping in mind the following cluster-specific requirements. 1. Create a generic NetWorker Client resource (with the saveset attribute set to All and not assigned to any group) for each physical node, if they do not already exist. 2. In the Remote Access attribute of the Client resource that you create for the virtual cluster host, add sap_user@physical_host for each node that requires access to the backup.
Note: You do not need to add -c virtual_clientname to the backup command.
3. In the init<DBSID>.util file, set the client parameter to the virtual client hostname.
Configuring a manual backup in a cluster

To configure NMSAP manual backups in a cluster: Follow the same instructions as for a scheduled backup without the wizard. Configuring a scheduled backup in a cluster on page 54 gives details. The only difference is that you may configure a generic NetWorker Client resource for the virtual host.
Configuring a deduplication backup in a cluster

To configure NMSAP deduplication backups in cluster environment: 1. Follow the instructions for the following procedures: Configure deduplication for a scheduled backup on page 30. Configuring a scheduled backup in a cluster on page 54 or Configuring a manual backup in a cluster on page 55. 2. Ensure that there is at least one NetWorker Client resource enabled for deduplication backups, which corresponds to the client host that is set either on the Specify the Client Name wizard page, or in the client parameter in the init<DBSID>.utl file. 3. For scheduled backups, ensure that the NetWorker Client resource for the virtual host is part of the NetWorker backup group, and is enabled for deduplication.
Converting client-side configurations to wizard settings in a cluster

To convert a scheduled backup configuration that uses configuration files to the wizard configuration in a cluster: 1. Follow the instructions for Converting client-side configurations to wizard configurations on page 25. You can run the nsrsapadm conversion utility from any of the physical nodes configured for backup. 2. During the conversion, when nsrsapdm prompts for names of users to add to the Lockbox resource, specify the names of SAP operating system users on each physical node that will be used for the backup.
Cluster systems
55
Note: If you do not grant the Lockbox ACL rights during the conversion, you can add the user later by using NMC to edit the Lockbox resource for the cluster virtual host.
Restoring in a cluster
To restore data backed up from a shared disk of a virtual client: 1. Set the client parameter in the NMSAP parameter file, init<DBSID>.utl, to the virtual client that holds the NetWorker index entries for the backup to be restored. 2. Follow the instructions for Performing a restore and recovery on page 46.
Oracle RAC systems

An Oracle Real Application Cluster (RAC) system provides a single database that can be accessed by multiple Oracle instances at the same time. Each Oracle instance is located on a separate host.
Configuring Oracle RAC backups

The SAP documentation provides details on RAC setup. Specific requirements for Oracle RAC backups with BRTools and NMSAP are as follows:
One of the Oracle RAC instances, set as the dedicated database (DDB) instance, is used to perform all database administration tasks. You must be able to administer all RAC instances from the DDB instance. BRTools and NMSAP software must be installed on the DDB instance host. The BRTools log directories, such as SAPBACKUP, SAPARCH, and so on, must be created on a shared file system. Oracle SQL Net must be properly configured. The required parameters, such as parallel_instances and db_services, must be set in the SAP initialization file, init<DBSID>.sap, located on the DDB instance.
All Oracle RAC backups performed with BRTools and NMSAP run on the DDB instance. The backup configuration of the DDB instance is the same as for a stand-alone systems. Chapter 2, Software Configuration, provides details. The archived redo logs from all instances are usually stored in a common shared location. These logs are backed up by the brarchive program, which is started on only one RAC instance, usually the DDB instance.
Restoring Oracle RAC data

To restore Oracle RAC data, run the BRTools comands, such as brrestore or brrecover, on the DDB instance. You can restore all the required archived redo logs in a single brrestore command. The brrestore -a command allows you to enter the instance name and which logs should be restored. For example:
brrestore -a 40-50,ORA2
restores the archived logs with sequence numbers from 40 to 50 that belong to instance ORA2.
56
7

PowerSnap snapshot backups and restores .............................................................. Types of PowerSnap backup........................................................................................ Types of PowerSnap restore......................................................................................... Basic PowerSnap backup and restore data flows ..................................................... Configuring NMSAP snapshot backups and restores ............................................. Testing NMSAP snapshot backups and restores ...................................................... Example parameter settings for NMSAP snapshot backup.................................... Reviewing NMSAP snapshot backup records ..........................................................
58 59 61 61 63 68 69 70
57
PowerSnap snapshot backups and restores

PowerSnap snapshot backups and restores provide continuous snapshot-based protection and availability of data on supported types of primary storage. NMSAP works with the NetWorker PowerSnap Module to provide this protection for SAP Oracle data. PowerSnap modules support scheduled backups only. Manual (client-initiated) backups are not supported. The PowerSnap documentation provides details.
Supported environments
The types of primary storage platforms supported by PowerSnap include:

EMC CLARiiON EMC Symmetrix EMC Celerra (NAS Filer)
The EMC Powerlink website (registration required) at Powerlink.EMC.com provides a complete list of supported PowerSnap modules.
Required software components

Figure 1 on page 59 shows the basic NMSAP environment for PowerSnap snapshot backup and restore. Table 7 on page 58 lists the requires software components:
Table 7
Typical configuration for PowerSnap snapshot operations with NMSAP Computer or device Oracle production server host Proxy client host (Data Mover host) Storage array NetWorker server host Required software or configuration Oracle server, SAP BRTools, NetWorker client, NMSAP, PowerSnap Module NetWorker client, NetWorker storage node (optional), PowerSnap Module Storage array supported by PowerSnap, for example, Symmetrix, CLARiiON, or Celerra (NAS devices) NetWorker server, NetWorker client
58
NetWorker Server
NetWorker Stotrage Node
Conventional Storage
LAN
Oracle Server Host Database Server NetWorker Client NMSAP PowerSnap Module
SAN
Data Mover (proxy client host) NetWorker Client PowerSnap Module
Primary Storage Array (For example, Symmetrix, CLARiiON, or Celerra)
S4 S5
Primary Storage LUNs/Volumes
S3
S1
S2
Snapshots
GEN-001253
Figure 1
Software used in the NMSAP environment for PowerSnap backups and restores
Types of PowerSnap backup

The NMSAP software, with the appropriate PowerSnap Module, supports the types of backups summarized in Table 8 on page 59
Table 8
Summary of supported PowerSnap backup types Backup type Instant backup on page 60 Immediate live backup on page 60 Deferred live backup on page 60 Snapshot retention Permanent Temporary Permanent Location of stored data Snapshot only Conventional storage only Both snapshot and conventional storage
Types of PowerSnap backup
59
The PowerSnap backup type is configured by the Snapshot Policy attribute in the NetWorker Backup Group. Group resource on page 64 gives details.
Instant backup
An instant backup creates a permanent point-in-time (PIT) copy, or snapshot, of SAP Oracle data. This copy is stored on the primary storage system where it is available to the NMSAP program for performing instant restores or rollbacks. Instant backups can be scheduled to occur many times in a single day, with minimal impact to the SAP Oracle server or network. A group of SAP 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. Snapshot Policy resource on page 64 gives more information.
IMPORTANT Instant backups protect against logical failures only. To protect against physical media failures, the snapshot must be backed up to conventional storage.
Live backup
A live backup (also known as snapshot rollover or rollover to conventional storage) is a backup of a snapshot to conventional (secondary) storage. A proxy client host (also called the data mover host) is separate from the Oracle server host and is used by the PowerSnap module to move the snapshot data to conventional storage. The use of a proxy client as a secondary host reduces the demand on the Oracle server host. The proxy client may be a NetWorker storage node.
Note: The group snapshot policy must be configured to enable live backups. Snapshot Policy resource on page 64 provides more information.
The NMSAP program 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 by the PowerSnap module to conventional storage. The snapshot is then automatically deleted from the primary storage (and is not available to the NMSAP program for performing instant restores or rollbacks). Deferred live backup Deferred live backup is a process by which a permanent snapshot is created and is backed up by the PowerSnap module to conventional storage. The permanent snapshot is retained on the primary storage and is available to the NMSAP program for performing instant restores or rollbacks for the period specified by either of the following policies:

The snapshot expiration policy The Retain Snapshots attribute of the snapshot policy
60
Types of PowerSnap restore

The NMSAP software, with the appropriate PowerSnap Module, supports the types of restore described in Table 9 on page 61.
Table 9
Supported restore types Restore type Instant restore on page 61 Rollback on page 61 Restore from conventional storage on page 61 Data retrieved from: Mounted snapshot Unmounted snapshot, entirely restored to source location Conventional storage
The restore type is specified in the RESTORE_TYPE_ORDER parameter in the user-defined PowerSnap configuration file. PowerSnap parameters on page 66 provides details.
Instant restore
An instant restore is the process by which a snapshot that was created by an instant backup is mounted. This enables NMSAP to retrieve its saved data, or subset of the saved data. A minimal amount of time is required for this type of restore.
Rollback
A rollback restores the entire snapshot to the source location by using the hardwares particular capabilities. Relocation during rollbacks is not supported by PowerSnap software. To determine if a rollback is supported on a specific type of hardware, refer to the appropriate NetWorker PowerSnap Module Installation and Administration Guide.
CAUTION Rollbacks are potentially destructive because they overwrite the entire contents of a snapshot unit, such as a volume or disk.
Restore from conventional storage

A restore from conventional storage is the process by which a snapshot data that was saved to the conventional storage system is restored from that storage system to the SAP Oracle Server.
Note: The restore of snapshot data from the conventional storage requires the use of PowerSnap software.
Basic PowerSnap backup and restore data flows

During a PowerSnap backup the NMSAP backint process interacts with the PowerSnap Module processes to create the point-in-time (PIT) snapshot and backs it up to NetWorker server.
Types of PowerSnap restore
61
A PowerSnap snapshot backup involves the following processes: 1. At the time of a scheduled snapshot backup, the NetWorker server starts the NMSAP nsrsapsv process, which invokes the SAP brbackup command. 2. The SAP brbackup program invokes the NMSAP backint program which then communicates with the PowerSnap Module. 3. On the SAP Oracle server host, the PowerSnap Module takes a point-in-time snapshot of the Oracle data on the primary storage, which then becomes available to the PowerSnap data mover host. 4. If a live backup is performed, the PowerSnap Module on the data mover host moves the SAP Oracle data from the snapshot on the primary storage to the NetWorker storage node, which stores the data to conventional storage. If required, PowerSnap deletes the snapshot. 5. At the end of the PowerSnap backup, the NetWorker server updates the online client and media indexes with information about the backup. The NetWorker Administration Guide provides more information on NetWorker server and client services. Figure 2 on page 62 illustrates the architecture of the NMSAP backup and recovery system, and shows the functional relationship between SAP and NetWorker software components.
SAP Oracle Server Host NetWorker Client
Control
PowerSnap Data Mover Host
NetWorker Server Host
BRTools
NMSAP
NetWorker Client
PowerSnap Module
PowerSnap Module
Data
NetWorker Server
SAP with Oracle Datafiles
Point-in-Time Copy of SAP with Oracle Datafiles
Storage Medium
Primary Storage
GEN-000436
Figure 2
PowerSnap backup and restore data flow with NMSAP
62
Configuring NMSAP snapshot backups and restores

To configure NMSAP snapshot backups: 1. Configure the SAP Oracle database layout to position the datafiles on the primary storage that is supported by the specific PowerSnap Module.
Note: Do not locate the Oracle database control file or any SAP directories, except sapdata<n>, on the same volume (snapshot unit) as the datafiles that will be backed up through PowerSnap backups. Specific types of Oracle files, such as control files, cannot be backed up through a PowerSnap backup. This is an Oracle constraint. The Oracle documentation for the particular Oracle Server version provides more information on the Oracle file types that do not support snapshot backups.
2. Ensure that both the NMSAP software and the required PowerSnap Module software are installed according to the instructions in the following documentation: NetWorker Module for SAP with Oracle Installation Guide NetWorker Module for PowerSnap Installation and Administration Guide (Refer to the PowerSnap Module release for the primary storage system.) 3. For online database backups, do one of the following: In the init<DBSID>.sap file, set backup_device_type=util_file_online In the nsrsapsv.cfg file, set the BR_EXEC parameters CLI option to -d util_file_online.
Note: If backup_device_type is set to util_file, the database stays in backup mode for the entire duration of the backup and generates a larger number of transaction logs.
4. Complete the procedure: Configure the NetWorker resources for NMSAP snapshot backups on page 63. 5. Complete the procedure: Configure NMSAP and PowerSnap parameters for snapshot operations on page 65.
Configure the NetWorker resources for NMSAP snapshot backups

The following sections describe how to configure the NetWorker resources for NMSAP backups with PowerSnap. The NetWorker Module for PowerSnap Installation and Administration Guide also provides more details on PowerSnap configuration. Snapshot Pool resource Configure a separate NetWorker snapshot Pool resource to support NMSAP PowerSnap backups. The PowerSnap Module stores the metadata from the snapshot in this pool.
Use the same configuration method as for a regular NMSAP backup, except the specified backup device should be a file or advanced file type. Specify this pool name in the Snapshot Pool attribute of the NetWorker Group resource as described in Group resource on page 64.
63
Snapshot Policy resource A NetWorker snapshot policy must be configured to perform either instant or live NMSAP PowerSnap backups. Specify either a preconfigured policy, or create a new one. Group resource Configure a NetWorker Group resource for NMSAP PowerSnap backups. Table 10 on page 64 gives typical settings.
Note: A PowerSnap backup must be started by the NetWorker scheduled backup group. It cannot be scheduled, for example, by SAP Computing Center Management System (CCMS).
Table 10
Backup Group resource attributes for PowerSnap backups Attribute Snapshot Snapshot Policy Snapshot Pool Start Time Interval Setting True Daily or other customized policy. A Pool resource dedicated to the storage of 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 Number of Snapshots attribute for the snapshot policy.
Device resource For live SAP Oracle backups, configure a Device resource for each conventional storage device to be used during backups. The devices must be mounted. Client resource The NetWorker Client resource for the NMSAP PowerSnap operations should be configured as described in Set the Client resource on page 27. The Client resource should be associated with the snapshot Group resource.
Note: During a backup, the NMSAP software appends :PS: to the saveset name to identify PowerSnap save sets.
The lifecycle of a snapshot is defined by the snapshot browse and retention policies of the Group resource that is specified for the NetWorker Client resource. The Browse Policy attribute in the Client resource applies only to the NetWorker client file index entries for PowerSnap backups that reside on conventional storage (live backups). The Retention Policy attribute in the Client resource applies only to the NetWorker media database entries for live backups. Client resources for NAS devices For PowerSnap operations with a network-attached storage (NAS) device, specify two NetWorker Client resources as follows.
NetWorker Client resource for the NAS device Do not associate the Client resource with any group. Set the Save Set to none.
64
Enable NDMP. Set the remote username and password to the root username and password of the NAS device.
Note: Only members of a NetWorker user group with the Change Security Settings privilege can set the Remote Access attribute in the Client resource.
NetWorker Client resource for the NMSAP host Configure the Client resource and associate it with the snapshot Group resource, as described in Client resource on page 64 Specify the following parameter in the Application Info attribute: NSR_SNAP_NAS_CLIENT = NASFilerHostName where NASFilerHostName is the name of the NAS device.
Configure NMSAP and PowerSnap parameters for snapshot operations

NMSAP PowerSnap backups and restores use the parameter settings described in the following sections:

NMSAP parameters for PowerSnap operations on page 65 PowerSnap parameters on page 66
NMSAP parameters for PowerSnap operations Table 11 on page 65 lists detailed descriptions of the NMSAP parameters that are set in the parameter file, init<DBSID>.utl for PowerSnap backups or restores. Example 1 on page 69 provides a basic configuration for NMSAP snapshot backups with PowerSnap.
Table 11
PowerSnap parameters in the NMSAP parameter file, init<DBSID>.utl file (page 1 of 2) Description / Default value Each of these PowerSnap functional modes is enabled if set to TRUE. Normally, all the modes are set together to either all TRUE or all FALSE, except ps_archive_mode=FALSE and all others =TRUE. Do not use any other settings except for diagnostic purposes. Full pathname of a configuration file that contains PowerSnap specific parameters. PowerSnap parameters on page 66 describes how to set the parameters. Specifies which backint runs are to be excluded from PowerSnap processing (typically run number 2). Each brbackup or brarchive session invokes the backint process to run twice in sequence. Run 1 backs up the Oracle data. Run 2 backs up the Oracle database initialization file (init<DBSID>.ora), and the BRTools parameter file (init<DBSID>.sap) and catalog files. Files backed up during Run 2 do not require PowerSnap processing and can be backed up by conventional processing without PowerSnap, thereby saving valuable snapshot disk resources. Note: The following starting values are strongly recommended: ps_exclude_backup_bi_run_nums=2 ps_exclude_archive_bi_run_nums=1;2 Default and valid values FALSE (default) TRUE
PowerSnap parameter ps_backup_mode ps_archive_mode ps_restore_mode ps_inquire_mode ps_opaque_pfilename
Undefined (default) A valid full pathname of the PowerSnap configuration file Undefined (default) Numeric value of one or more valid backint run numbers to exclude, each separated by a semicolon (;)
ps_exclude_backup_bi_run_nums ps_exclude_archive_bi_run_nums
65
Table 11
PowerSnap parameters in the NMSAP parameter file, init<DBSID>.utl file (page 2 of 2) Description / Default value Specifies individual PowerSnap files to exclude from PowerSnap processing and back up with conventional non-snapshot processing instead. PowerSnap files are those on a snapshot-capable file system that NetWorker is aware of. Whenever possible, set the ps_exclude_xxx_bi_run_nums parameters instead of ps_exclude_xxx_paths parameters. Note: - On Microsoft Windows systems, support of wildcard characters is limited, and a single trailing * denotes simple case-insensitive prefix matching. Thus X:\DB01\FOO.DBF will be excluded from PowerSnap backups if the parameter is set to a value of: X:\*, or X:\db*, or X:\DB01\* - On UNIX systems, 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*. Default and valid values Undefined (default) Full path of the files to be excluded, each separated by a semicolon (;). Wildcard characters can be used as described in the Note. Use values that are based on the actual filename that BRTools passes to backint.
PowerSnap parameter ps_exclude_backup_paths ps_exclude_archive_paths
ps_ps_before_nonps
Specifies whether to perform all PowerSnap processing before conventional processing without PowerSnap. This helps prevent potential resource conflicts. Setting this value to FALSE enables concurrent processing of all files set for backup, archive, or restore. Note: The FALSE value is not recommended and is used at the users own discretion.
TRUE (default) FALSE
ps_group_objs
Specifies whether to group all session files for each PowerSnap operation, such as prepare or sync, snapshot or split, save or restore, or cleanup. Setting this value to TRUE improves NMSAP 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.
TRUE (default) FALSE
PowerSnap parameters PowerSnap parameters can be set in the PowerSnap configuration file for backups or restores, or in the Application Info attribute of the NetWorker Client resource for backups only. The PowerSnap configuration file must be specified by its complete file pathname, for example, /nsr/res/nmsapps.cfg, in the ps_opaque_pfilename parameter in the NMSAP parameter file, init<DBSID>.utl. Example 2 on page 69 provides a simple PowerSnap with Celerra NAS devices example. Some parameters in the PowerSnap configuration file have corresponding parameters in the NMSAP parameter file, init<DBSID>.utl, from which they inherit their values. Normally, values for these parameters should not be specified in the PowerSnap configuration file. If a corresponding parameter is set in the PowerSnap configuration file, it overrides the equivalent parameter in the NMSAP parameter file. Table 14 on page 82 lists the parameters in the NMSAP parameter file.
66
Each parameter in the configuration file or in the Application Info attribute must be listed on a separate line, in the following format:
parm_name=parm_value
where:

parm_name is the variable name, such as NSR_SNAP_TYPE. parm_value is the variable value, such as nas.
Table 12 on page 67 lists some common PowerSnap parameters. The appropriate NetWorker Module for PowerSnap Installation and Administration Guide provides a complete list of PowerSnap parameters.
Table 12
Common parameters in the PowerSnap configuration file, nmsapps.cfg (page 1 of 2) Description Corresponds to the checksum parameter in Table 14 on page 82. Corresponds to the client parameter in Table 14 on page 82. Note: If set, the value of NSR_CLIENT parameter must match the value of client parameter. Default and valid values Setting of NMSAP checksum parameter (default). Setting of NMSAP client parameter (default).
PowerSnap variables NSR_CHECKSUM NSR_CLIENT
NSR_COMPRESSION NSR_DATA_MOVER
Corresponds to the compress parameter in Table 14 on page 82. Mandatory. if the PowerSnap backup uses a data mover host different from the PowerSnap client host (NSR_CLIENT). Specifies the hostname or IP of the of the PowerSnap data mover host. Corresponds to the pool parameter in Table 14 on page 82. Optional. Specifies the maximum number of restore streams.
Setting of NMSAP compress parameter (default). Local host (default). Valid hostname or IP address.
NSR_DATA_VOLUME_POOL NSR_MAX_STREAMS
Setting of NMSAP pool parameter (default). Setting of the NMSAP pallelism parameter (default). An integer value. 0 (default, no debugging). 0 9. Setting of the NMSAP pallelism parameter (default). An integer value. Setting of NMSAP NSR_SAVESET_BROWSE parameter (default).
NSR_PS_DEBUG_LEVEL
Optional. PowerSnap debug level.
NSR_PS_SAVE_PARALLELISM
Optional. Specifies the maximum number of concurrent backup save streams on the PowerSnap client host.
NSR_SAVESET_BROWSE
Corresponds to NSR_SAVESET_BROWSE in Table 14 on page 82. Note: Applies only to data stored on conventional storage as described in Client resource on page 64.
NSR_SAVESET_RETENTION
Corresponds to NSR_SAVESET_RETENTION in Table 14 on page 82. Note: Applies only to data stored on conventional storage as described in Client resource on page 64.
Setting of NMSAP NSR_SAVESET_RETENTION parameter (default).
NSR_SNAP_NAS_CEL_CS_HOST
Mandatory for NAS devices. Specifies the hostname or IP of the Celerra control station.
Local host (default). Valid hostname or IP address.
67
Table 12
Common parameters in the PowerSnap configuration file, nmsapps.cfg (page 2 of 2) Description Mandatory for NAS devices. Specifies the hostname or IP of the NAS filer with NFS server for the specified mount point. Mandatory for NAS devices. Specifies the NAS SCM subtype to use for snapshot management. Mandatory for NAS devices. Optional for other platforms. Specifies snapshot platforms. If the value is unspecified, PowerSnap inquires the BRC service to choose the most appropriate value. Default and valid values Local host (default). Valid hostname or IP address. Must be defined as CEL_SNAPSURE (default). The value must be lowercase, for example: nas for NAS devices symm-dmx for Symmetrix DMX emcclar for CLARiiON emcrp for RecoverPoint pit:conventional (default) One or more of the following values is supported, with each value delimited from the others by a colon (:) pit - Specifies an instant (point-in-time) restore. conventional - Specifies a restore from conventional storage media. rollback - Specifies a rollback restore from a PiT copy.
PowerSnap variables NSR_SNAP_NAS_CLIENT
NSR_SNAP_SUBTYPE NSR_SNAP_TYPE
RESTORE_TYPE_ORDER
Optional. Specifies the type of restore to be performed. If multiple values are specified, each type of restore is attempted, in the order specified, until a restore operation is successful. Note: For NMSAP, a rollback operation aborts if one of the following occurs: - If brrestore file relocation is specified. - If nonrequested files exist in the brrestore-requested file systems. These files could become corrupted after a rollback.
Testing NMSAP snapshot backups and restores

To test NMSAP backups and restores with PowerSnap: 1. Configure the NetWorker resources and NMSAP configuration files as described in Configuring NMSAP snapshot backups and restores on page 63. 2. Test the NMSAP PowerSnap backups by invoking the savegrp command either from the NMC GUI program or from the command line on the NetWorker server host as follows:
savegrp -c client_name group_name
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. If you encounter a problem, check the NMSAP backint and PowerSnap logs. 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 11 on page 65, is set to exclude a file from PowerSnap processing. The ps_opaque_pfilename file needs to be modified.
68
For further troubleshooting, enable the following parameters in the init<DBSID>.utl file to generate diagnostic logs for EMC Customer Support:
debug_level = 9 nsr_debug_msg = TRUE
To obtain PowerSnap debug logs, also specify the following in the ps_opaque_pfilename file:
NSR_PS_DEBUG_LEVEL=9
3. Run a pre-restore inquiry with the following command:

brrestore -verify
4. 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 the primary storage supported by PowerSnap.
Example parameter settings for NMSAP snapshot backup

The following are examples of settings in the NMSAP parameter file, init<DBSID>.utl, and the PowerSnap configuration file (for example, nmsapps.cfg) for snapshot backups and restores with PowerSnap software.
Example 1
Typical settings in the backint parameter file, init<DBSID>.utl ps_backup_mode = TRUE ps_archive_mode = FALSE ps_restore_mode = TRUE ps_inquire_mode = TRUE 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 = TRUE ps_group_objs = TRUE ps_opaque_pfilename = /nsr/res/nmsapps_backup.cfg
Example 2
Typical settings for NAS device in the PowerSnap configuration file
This example of a backup with Celerra NAS devices uses the following PowerSnap parameter settings in the /nsr/res/nmsapps_backup.cfg file, which is specified with the ps_opaque_pfilename parameter in the NMSAP parameter file.
NSR_SNAP_TYPE=nas NSR_DATA_MOVER=mover_computer NSR_SNAP_NAS_CEL_CS_HOST=controlstn NAS_SNAP_SUBTYPE=CEL_SNAPSURE NSR_SNAP_NAS_CLIENT=11.222.333.44
Example parameter settings for NMSAP snapshot backup
69
Reviewing NMSAP snapshot backup records

The NetWorker server records information about each NMSAP PowerSnap backup in its online indexes, client file index, and media database. The NetWorker client file index for NMSAP PowerSnap backups is stored under the "saporacle" namespace. The backup namespace is used for regular (non-PowerSnap) NMSAP backups. Use the nsrinfo and mminfo commands to query the online NetWorker indexes.
To query the NetWorker client file index, type the nsrinfo command, for example:
nsrinfo [-v] -n saporacle -s NetWorker_server client
where client is your SAP Oracle server hostname.
To query the NetWorker media database, type the mminfo command. For example:
mminfo [-v] [-N backint:DBSID:PS:] -s NetWorker_server -c client
where client is your SAP Oracle server hostname. The NetWorker Command Reference Guide and the UNIX man pages provide more information on these NetWorker commands.
70
8

Split-mirror backups and restores .............................................................................. Basic split-mirror backup and restore data flows..................................................... Configuring the production host for split-mirror backups..................................... Configuring the mount host for split-mirror backups............................................. Configuring the RM server for split-mirror backups............................................... Configuring the NetWorker server for split-mirror backups ................................. Configuring a cluster environment for split-mirror backups................................. Examples of RM scripts for split-mirror backups .................................................... Examples of parameters for split-mirror backups....................................................
72 72 74 75 77 77 77 78 79
71
Split-mirror backups and restores

NMSAP in cooperation with EMC Replication Manager (RM) software supports BRTools split-mirror backups with split-command interface.
Note: The SAP splitint interface is not supported by the NMSAP with RM split-mirror backup implementation.
Supported environments
The types of primary storage array platforms supported by RM include:

EMC CLARiiON EMC Symmetrix
The EMC Powerlink website (registration required) at Powerlink.EMC.com provides a complete list of supported RM modules.
Required software components

Split-mirror backups created with NMSAP, BRTools, and RM require the software components described in Table 13 on page 72.
Table 13
Hosts required for split-mirror backups with RM and NMSAP Computer or device Oracle production server host Mount host Note: Mount host is also also known as the data mover, mirror host, or backup host Replication Manager server host NetWorker server host RM server NetWorker client and NetWorker server Required software or configuration Oracle server, SAP BRTools, RM agent. Optionally: NW client, NMSAP At least Oracle client software and SQL Plus, SAP BRTools, RM agent, NetWorker client, and NMSAP
Basic split-mirror backup and restore data flows

A split-mirror backup involves the following basic processes:
RM software splits the disks on the primary storage array, which creates a snapshot copy (replica) of the database. RM mounts the replica onto the backup host (data mover), and later synchronizes the disks if necessary. The NMSAP backint program backs up the snapshot data from the mount host to conventional storage.
Note: The SAP split-mirror backup framework does not support the backup of archived redo logs. To fully protect the SAP environment, NMSAP should be configured on the production host to back up archived logs.
72
Manual split-mirror backup data flow

A manual split-mirror backup is started on the mount host by running the SAP brbackup command, as described in the following process. 1. The brbackup program contacts the production database to determine the location of objects to be backed up. For an online backup, it also creates a copy of the control file on the mount host. 2. brbackup prepares the production database for the backup. For an online backup, it puts the required tablespaces into backup mode. For an offline backup, it shuts down the database if necessary. 3. brbackup executes the script specified by the split_cmd parameter in the init<DBSID>.sap file. 4. The split script runs an RM job that creates a database replica and mounts it on the mount host. 5. The script ends executions and returns control to brbackup. 6. brbackup completes its interaction with the production database. For an online backup, it takes the tablespaces out of backup mode. For a offline backup, it restarts the database if necessary. 7. brbackup runs the NMSAP backint binary on the mount host. 8. backint establishes connection with the NetWorker server, backs up the data to conventional storage, and records the backups in the NetWorker server catalog. 9. brbackup records the backup in its own catalog on the mount host and makes a copy of the catalog on the production host. By default, NMSAP stores backup entries in the NetWorker client file index under the name of the client that it backs up, in this case the mount host. The backup entries can be recorded under the Oracle production host by setting the NMSAP client parameter to the production host.
Scheduled split-mirror backup data flow

Scheduled split-mirror backups are scheduled through the NetWorker server. At the scheduled backup start time, the following process occurs: 1. The NetWorker server contacts the NetWorker client on the mount host. 2. The NetWorker client calls the NMSAP nsrsapsv scheduled backup program. 3. nsrsapsv sets the environment needed to run the brbackup program, and runs the brbackup program, as configured in the NMSAP nsrsapsv.cfg configuration file. 4. The backup then follows the same processes as a manual backup.
Restore of split-mirror backups data flow

Restore and recovery operations are the same as for regular NMSAP backups and do not involve RM. The backup data can be restored to either the mount host or the production host by running the brrestore command on the destination host.
Basic split-mirror backup and restore data flows
73
Configuring the production host for split-mirror backups

Table 13 on page 72 lists required and optional software components to be installed on the production host.
Configure Oracle on the production host

Follow the SAP documentation for details on how to create an Oracle database on the production host. The following configurations apply specifically to split-mirror backups: 1. Preferably, use the same ORACLE_HOME and user operating system account on both the production host and mount host. 2. Ensure that the database is in archived log mode. 3. Ensure that the following database files are located on the storage array: Database files Control file Parameter file (init<SID>.ora) Redo log files Archived logs Dump files 4. Configure and start the Oracle Net services. This enables the mount host to connect to the production database. 5. Grant sysoper and sysdba privileges to the SAP database user for BRTools operations.
Configure BRTools on the production host

Follow the SAP documentation for details on how to configure BRTools on the production host. The following configurations apply specifically to split-mirror backups: 1. Preferably, use the same paths and values for SAP specific parameters, such as SAPBACKUP and SAPARCH, on both the production and mount hosts. 2. On Microsoft Windows systems, use NFS to share the %SAPBACKUP% directory, which is located on the production host, with the mount host. Ensure the Oracle and SAP user and services on the mount host have read and write permissions on the %SAPBACKUP% directory. This is required to copy the control file to the %SAPBACKUP% directory during a split-mirror backup.
Note: On Microsoft Windows, the brrestore command may fail to restore the Oracle database control file, generated during an online split-mirror backup, and the BRTools backup catalogs. Split-mirror backups on Windows systems use NFS sharing. This enables these files to be backed up from their location in the %SAPBACKUP% directory, but it does not enable NMSAP to find the expected request file in the NetWorker index. Restore these files by using NetWorker file system tools, such as the recover command or the client graphical user interface.
74
Configure NMSAP on the production host

Optionally, install NMSAP on the production host. This enables the following activities:
Backup of Oracle archived logs, which must be performed outside of the split-mirror backup framework. Recovery of the backups directly to the production host instead of the mount host.
Configuring the mount host for split-mirror backups

Table 13 on page 72 lists required software components to be installed on the mount host. Review the following sections for important details about the mount host configuration.
Configure Oracle software on the mount host

Follow the Oracle documentation for details on how to configure the Oracle software on the mount host. The following configurations apply specifically to split-mirror backups: 1. Preferably, use the same ORACLE_HOME and user operating system account on both the production host and mount host. 2. Configure and start the Oracle Net services. This enables the mount host to connect to the production database. 3. Either copy the init<SID>.ora parameter file from the production host to the mount host, or create a dummy init<SID>.ora file that contains the following parameters: db_name=SID of the production database control_files=(location of the control file on the production host, location2)
Configure BRTools on the mount host

Follow the SAP documentation for details on how to configure BRTools on the mount host. The following configurations apply specifically to split-mirror backups: 1. Preferably, use the same paths and values for SAP specific parameters, such as SAPBACKUP and SAPARCH, on both the production and mount hosts. 2. Create the split command script by following the appropriate RM documentation. 3. Set the following parameters in the init<DBSID>.sap initialization file: split_cmd = location of the RM split command script primary_db = SID of the production database
Configuring the mount host for split-mirror backups
75
Note: For a single-host configuration, where the mount host is the same as the production host, this parameter must be set to the following keyword: primary_db = LOCAL
orig_db_home = $SAPDATA_HOME on the production host

Note: This parameter is required when the replica is mounted onto a different directory than the production database, for example in a single-host environment.
4. For a two-host UNIX environment, set the following parameters in the init<DBSID>.sap file: remote_host = production database host stage_copy_cmd = rcp | ftp | scp Set only one of these values.
Note: Ensure that the SAP user on the mount host is allowed to perform the specified command on the production host.
5. In a Microsoft Windows environment, mount the shared %SAPBACKUP% directory under the same path as on the production host.
Note: The %SAPBACKUP% directory must be shared because SAP split-mirror backups do not support FTP or RCP on Windows.
6. Set the following parameters in the init<DBSID>.sap file, or specify them as command line options to the brbackup command.
Note: The command line options take precedence over the corresponding parameters set in the init<DBSID>.sap file.
backup_type = online_split | offline_split backup_dev_type = util_file util_par_file = location of the NMSAP config utl.file 7. Set the SAP environment variables as follows: $SAPDATA_HOME = location of the replica Set other required variables, for example $SAPBACKUP, as described in the BRTools documentation.
Configure NMSAP on the mount host

Chapter 2, Software Configuration, provides instructions on how to configure the NMSAP software. For scheduled backups, ensure that the nsrsapsv.cfg file on the mount host contains the following setting: PATH = location of the RM agent binaries
Note: The NMSAP wizard does not support the configuration of split-mirror backups. Scheduled backups must be manually configured.
76
Configuring the RM server for split-mirror backups

Follow the Replication Manager documentation for details on how to configure the RM server for SAP split-mirror replication. The following requirements apply specifically to split-mirror backups: 1. Add the array devices to the RM storage pool. The devices must be visible to both the production host and mount host. 2. Create an application set and a RM job for the SAP Oracle database instance. In the RM job properties, select the Consistent split replication option. 3. In the RM job properties, unselect Unmount the replica on job completion. The replica should stay mounted after the RM job completes. Also, the job should fail if the replica mount attempt fails.
Configuring the NetWorker server for split-mirror backups

Table 13 on page 72 lists required software components to be installed on the NetWorker server host. Chapter 2, Software Configuration, provides instructions on how to configure the NetWorker server for NMSAP manual and scheduled backups. The following requirements apply specifically to split-mirror backups: 1. Configure the NetWorker Client resource for the production host with the following settings: Scheduled backup group: None, unless this resource is configured for archived log backups. Remote access: SAP_user@mount_host 2. Configure the NetWorker Client resource for the mount host with the following settings: Save set: backint:<DBSID> Group: NMSAP group Backup command: nsrsapsv -f location of nsrsapsv.cfg file Remote access: SAP_user@production_host
Configuring a cluster environment for split-mirror backups

Chapter 6, Cluster and Oracle RAC Configurations, provides instructions on how to configure a cluster environment for scheduled backups. The following requirements apply specifically to split-mirror backups: 1. Configure the required production host software on each physical node of the cluster. 2. Configure the required mount host software on a computer that is located outside of the cluster.
Note: Only a production host can be in a cluster environment. The mount host must be a stand-alone host.
Configuring the RM server for split-mirror backups
77
3. Store the parameter and configuration files, init<DBSID>.utl and nsrsapsv.cfg, in the same location on each physical node or on a shared drive. 4. Use the virtual node name for the production hostname. 5. On the NetWorker server, create and configure the NetWorker Client resource for each physical node with the following settings: Generic NetWorker resource (not NMSAP-specific) Group: none 6. On the NetWorker server, create and configure the NetWorker Client resource for the virtual node with the following settings: Group: none, unless this resource is configured for archived log backups. Remote access: SAP user@physical node #1 SAP user@physical node #2 SAP user@mount host 7. Configure the NetWorker Client resource for the mount host with the following settings: Save set: backint:<DBSID> Group: NMSAP group Backup command: nsrsapsv -f location of nsrsapsv.cfg file Remote access: SAP_user@virtual_node
Examples of RM scripts for split-mirror backups

This section shows examples of Replication Manager scripts that can be modified as needed for specific environments and configurations. Different scripts are used on UNIX and Microsoft Windows platforms.
Note: The following scripts have no error handling and do not consider possible use cases where the operations might fail.
sap_online_split script for RM on UNIX systems

# SAP_ONLINE_SPLIT # File to launch into ermcli and read the commands to execute WDIR=/space10/home/ora101/nmsap/nas RMDIR=/opt/emc/rm/gui LOG=/opt/emc/rm/logs/cli DATE=`date '+DATE %m_%d_%y_'|awk '{print $2}'` echo "Date $DATE" >> /db/app/oracle/product/10.1.0/db_1/SAP/sapbackup/echo.log 2>&1 TIME=`date '+TIME %H:%M'|awk '{print $2}'` echo "Time $TIME" >> /db/app/oracle/product/10.1.0/db_1/SAP/sapbackup/echo.log 2>&1 $RMDIR/rmcli host=cdendobread1c port=65432 file=$WDIR/erm_brbackup_online_split.sh >> $LOG/brbackup_online_spl it$DATE$TIME.log 2 >&1 echo "End of the RM split command" >> /db/app/oracle/product/10.1.0/db_1/SAP/sapbackup/echo.log 2>&1
78
erm_brbackup_online_split.sh script for RM on UNIX systems

login user=Administrator password=emc run-activity name=sap_brbk_j infoset=sap_brbk exit
sap_online_split.cmd script for RM on Microsoft Windows systems

@echo off REM EMC_SAP_ONLINE_SPLIT REM File to launch into ermcli and read the commands to execute set WDIR=C:\oracle\product\brtools\7.00 set RMDIR=C:\Program Files\EMC\rm\gui set LOG=C:\Program Files\EMC\rm\logs\client "%RMDIR%/\rmcli.bat" file=%WDIR%\erm_online_split.cmd >> %LOG%\rmjob_output.txt echo #INFO Success
erm_online_split.cmd script for RM on Microsoft Windows systems

connect host=cdendobread1c port=65432 if-not login user=Administrator password=emc then exit 1 if-not run-job name=sap_buhuron appset=clar_buerie then exit 1
Examples of parameters for split-mirror backups

This section provides examples of parameters that must be set in Oracle, BRTools, and NMSAP configuration files on the production host and mount host for split-mirror backup and restore.
Parameters to set on the production host

The following configuration files on the production host should be modified according to the requirements of the environment. In these examples, the production host is named "bu-erie." Oracle initSAP .ora
control_files = (H:\oradata\SAP\sapdata1\cntrl\ctrlSAP.ctl, H:\oradata\SAP\sapdata2\cntrl\ctrlSAP.ctl, H:\oradata\SAP\saparch\cntrl\ctrlSAP.ctl) background_dump_dest = H:\oradata\SAP\saptrace\background user_dump_dest = H:\oradata\SAP\saptrace\usertrace log_archive_dest = H:\oradata\SAP\saparch log_archive_format = SAParch%t_%s_%r
listener.ora
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = SAP) (ORACLE_HOME = C:\oracle\product\10.2.0\db_1) ) )
Examples of parameters for split-mirror backups
79
Parameters to set on the mount host

The following configuration files on the mount host should be modified according to the requirements of the environment. In these examples, the production host is named "bu-erie." Oracle initSAP.ora
db_name=SAP control_files = (H:\oradata\SAP\sapdata1\cntrl\ctrlSAP.ctl, H:\oradata\SAP\sapdata2\cntrl\ctrlSAP.ctl, H:\oradata\SAP\saparch\cntrl\ctrlSAP.ctl)
tnsnames.ora
SAP = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = bu-erie)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = SAP) ) )
BRTools initSAP.sap
split_cmd = F:\oracle\product\brtools\7.00\online_split.cmd backup_type = online_split primary_db = SAP backup_dev_type = util_file util_par_file = initSAP.utl orig_db_home = H:\oradata\SAP Note: If mount host is the same as production host, then set primary_db = LOCAL.
nsrsapsv.cfg
BR_EXEC=brbackup -m all -d util_file -r F:\oracle\product\10.2.0\db_1\database\initSAP.utl -p F:\oracle\product\10.2.0\db_1\database\initSAP.sap ORACLE_HOME=F:\oracle\product\10.2.0\db_1 DBSID=SAP NLS_LANG = AMERICAN_AMERICA.US7ASCII SAPBACKUP=\\bu-erie\I\oradata\SAP\sapbackup SAPDATA_HOME=H:\oradata\SAP SAP_BIN=F:\oracle\product\brtools\7.00 Path=C:\Program Files\EMC\rm\client\bin
80
A
This appendix includes the following sections:

NMSAP backint parameters ........................................................................................ Configure the NMSAP parameter file........................................................................ NMSAP nsrsapsv parameters ..................................................................................... NMSAP parameters for RMAN backups and restores............................................
82 82 88 92
81
NMSAP backint parameters

The backint parameters provide client, server, pool, deduplication, parallelism, and other values to the NMSAP backint program.
For manual backups, restores, and inquiries, these parameters must be set in the NMSAP parameter file (init<DBSID>.utl). For scheduled backups, these parameters can be set through the wizard, or in the parameter file for non-wizard configurations.
Configure the NMSAP parameter file

Use a copy (init<DBSID>.utl) of the original parameter file template (init.utl) supplied with the NMSAP software. The original template is removed, along with any settings you may have made in it, when the NMSAP software is uninstalled, for example when you upgrade NMSAP releases. The template file is located at:

Linux and UNIX: /etc/init.utl Windows: NetWorker_install_directory\nsr\bin\init.utl
IMPORTANT The server and group parameters do not need to be specified in this file if used for scheduled backups. However, if they are specified, then they must match the corresponding attributes on the NetWorker server or an error occurs. Any other settings specified in this file, such as pool name, take precedence over a corresponding setting on the NetWorker server. To set parameters in the NMSAP init<DBSID>.utl file, use the following format:
parameter=value
Keep the following rules in mind:
Uncomment and modify as necessary all parameters to be used in backup, restore, or inquire operations. Parameter names and values are case-sensitive.
Supported backint parameters

Table 14 on page 82 lists descriptions and default values for NMSAP parameters supported by the backint program.
Table 14
Supported backint parameters (page 1 of 7) Description Specifies the full pathname of the backint log file when running the brarchive command. Default and valid values Default location on UNIX: /nsr/applogs/arch_backint<DBSID>.lo g.raw Default location on Microsoft Windows: <NetWorker_install_path>\Legato\nsr\ applogs\arch_backint<DBSID>.log. Valid full pathname for the log file. The directory path must exist. The file will be created if it does not exist.
Parameter arch_backint_log
82
Table 14
Supported backint parameters (page 2 of 7) Description Specifies the full pathname of the backint log file when running the brbackup and brrestore commands. To specify a separate log file to use specifically for restores, modify this parameter before you run brrestore. Alternatively, the backint_log parameter can be specified in an init<DBSID>_restore.utl file, which can be passed as command line argument to brrestore program, for example: brrestore -r init<DBSID>_restore.utl Default and valid values Default location on UNIX systems: /nsr/applogs/backint<DBSID>.log.raw Default location on Microsoft Windows systems: <NetWorker_install_path>\Legato\nsr\ applogs\backint<DBSID>.log. Valid full pathname for the log file. The directory path must exist. The file will be created if it does not exist. Default location on UNIX systems: /nsr/applogs/ Default location on Microsoft Windows systems: <NetWorker_install_path>\Legato\nsr\ applogs\ Valid full pathname. The directory path must exist. The file will be created if it does not exist. FALSE (default) TRUE
Parameter backint_log
backint_tmpdir
Specifies the directory name of the backint temporary files.
checksum
Specifies whether to perform cyclic redundancy checking (CRC) on the backup data. Setting this parameter to TRUE excludes the use of the compress and NSR_AES_ENCRYPTION parameters, which should be set to FALSE. If more than one of these parameters is set to TRUE, the priority order is: compress, checksum, and NSR_AES_ENCRYPTION. Specifies the NetWorker client hostname to use for the client file index for the current backup or restore operation. If you are using the NMSAP software to back up or restore a virtual cluster client, set this value to the virtual node name. Compresses data during a backup before the data is passed over the network or written to the backup device, which can speed up the backup process. Compression increases CPU usage on the SAP Oracle server, but reduces the amount of data sent to the NetWorker storage node. Setting this parameter to TRUE excludes the use of the checksum and NSR_AES_ENCRYPTION parameters, which should be set to FALSE. If more than one of these parameters is set to TRUE, the priority order is: compress, checksum, and NSR_AES_ENCRYPTION. Specifies the level of debug messages that backint writes to the debug log file. Specifies the maximum number of backint session logs to be saved in the backint log file, specified by the backint_log parameter. If the value is set to 0, all backup logs will be saved in the log file. Alerts when the backint program has completed its activity. Uncomment the option and replace mailx with the name of the command line e-mail utility to be used, for example: notify_done = mailx -s backint done root
client
Local physical host (default) Valid NetWorker client hostname
compress
FALSE (default) TRUE
debug_level
0 (default, no debugging) 09 0 (default) Any positive integer
max_logs
notify_done
Undefined (default) Valid e-mail string
83
Table 14
Supported backint parameters (page 3 of 7) Description Alerts if the backint program encounters any errors during its activity. Uncomment the option and replace mailx with the name of the command line e-mail utility to be used, for example: notify_error = mailx -s backint error root Alerts when the backint program begins its activity. Uncomment the option and replace mailx with the name of the command line e-mail utility to be used, for example: notify_start = mailx -s backint start root Alerts when the backint program has successfully completed its activity. Uncomment the option and replace mailx with the name of the command line e-mail utility to be used, for example: notify_success = mailx -s backint success root Specifies whether to encrypt backup data with 256-bit AES encryption. Setting this parameter to TRUE excludes the use of the compress and checksum parameters, which should be set to FALSE. If more than one of these parameters is set to TRUE, then the priority order is: compress, checksum, and NSR_AES_ENCRYPTION. Note: If the encryption phrase has changed between the time of the backup and the time the backup is restored, then the NSR_ENCRYPTION_PHRASES parameter must include the original phrase to enable the recovery. Default and valid values Undefined (default) Valid e-mail string
Parameter notify_error
notify_start
notify_success
NRS_AES_ENCRYPTION
NSR_DEBUG_DIR
Specifies the directory for the backint diagnostic logs.
Default location on UNIX systems: /nsr/applogs/ Default location on Microsoft Windows systems: C:\Program Files\Legato\nsr\applogs\ FALSE (default). Deduplication is not performed during an NMSAP backup. Other NSR_DEDUP_* parameters are ignored. TRUE. Deduplication is performed during an NMSAP backup. If NSR_DEDUP_NODE is not set, the backup fails. TRUE (default). A cache is used to increase performance during a deduplication backup. This value is recommended in most cases. FALSE. A cache is not used during a deduplication backup.
NSR_DEDUP_BACKUP
Mandatory for manual deduplication backups only. Do not set for scheduled backups. Specifies whether to perform a deduplication backup. Note: For scheduled deduplication backups, set the Deduplication Backup attribute in the NetWorker Client resource, instead of setting this parameter.
NSR_DEDUP_CACHE_ENABLED
Optional for deduplication backups. Specifies whether a cache is used during a deduplication backup. Not using a cache decreases the backup performance, but also decreases the disk usage in the /nsr/dedup/cache directory. Note: Use of the nondefault value (FALSE) requires knowledge of Avamar operations.
NSR_DEDUP_CACHE_TAG
Optional for deduplication backups. Specifies the name of the cache to be used by the nsravtar process during NMSAP backup.
Undefined (default). String value of the tag that will generate a deduplication cache name. Do not include the client name in the value.
84
Table 14
Supported backint parameters (page 4 of 7) Description Optional for deduplication backups. Specifies the size, in bytes, of data chunks that the Avamar server uses in a deduplication backup. Note: Adjusting the data chunk size requires expert knowledge of Avamar operations and the data that will be backed up. Default and valid values 0 (default). Signifies that variable sizes are used for the data chunks, as determined by the Avamar server. This value is recommended in most cases. (Value greater than zero). A fixed data chunk size to use for deduplication backup. For example, 1024, 2048, 5096, 8194, or other value as recommended in the Avamar documentation. Undefined (default). Name of the NetWorker Deduplication Node resource.
Parameter NSR_DEDUP_CHUNK SIZE
NSR_DEDUP_NODE
Mandatory for manual deduplication backups only. Do not set for a scheduled deduplication backup. Specifies the NetWorker De-duplication Node resource (Avamar server) to be used for the backup. The name must exactly match the Deduplication Node attribute set in the NetWorker Client resource. Mandatory if the NSR_AES_ENCRYPTION phrase has changed between the time of the backup and the time the backup is restored. Specifies the original phrase to enable the recovery. Multiple phrases are permitted. For example: NSR_ENCRYPTION_PHRASES = phrase 1, phrase 2 Each attempted phrase must be enclosed in double quotes and separated by a comma. Do not put a comma after the last phrase. Specifies the pathname of the directory that contains the NetWorker or Avamar binaries. Recommended for deduplication backup or restore if the NetWorker software is installed in a nondefault location.
NSR_ENCRYPTION_PHRASES
Any valid string
NSR_NWPATH
Platform-specific default location of the NetWorker client binaries (default). Valid directory pathname of the nsravtar binary.
NSR_RAW_DEVICE_SKIP_BYTES
Undefined (default). Used to omit unwanted data from recovery on a raw device. Specifies the initial amount of data to skip. This parameter has Valid device name and amount of data the following syntax: to skip. NSR_RAW_DEVICE_SKIP_BYTES=/raw/dev1=skip[B|K|M|G] The device name is followed by an equal sign and the amount of data to skip, specified in bytes, kilobytes, megabytes, or gigabytes. The parameter can specify multiple devices by separating the entries with a colon. For example, to skip 8 KB for the raw device /dev/rdsk/c2t4d0s5, set: NSR_RAW_DEVICE_SKIP_BYTES=/dev/rdsk/c2t4d0s5=8K Note: Adjusting the amount of data to skip requires expert knowledge of the operating system and volume manager specifications.
NSR_RELOCATION_DEST
For a relocated restore, specifies the new root directory for SAP datafiles when SAPDATA_HOME is changed, but the structure of subdirectories under SAPDATA_HOME are not modified.
Undefined (default) Same value as the new SAPDATA_HOME value
85
Table 14
Supported backint parameters (page 5 of 7) Description Specifies the date when the entry for the backup is to be removed from the NetWorker client index and the associated backup files are no longer readily available for browsing. Note: For a scheduled backup, this parameter overrides the Browse Policy attribute setting in the NetWorker Client resource. Default and valid values Browse policy specified in the NetWorker Client resource for the client, as determined by the NetWorker server (default). Valid date in nsr_getdate(3) format.
Parameter NSR_SAVESET_BROWSE
NSR_SAVESET_RETENTION
Specifies the date when the save set becomes recyclable and the associated data on the volume can be overwritten. Note: For a scheduled backup, this parameter overrides the Retention Policy attribute setting in the NetWorker Client resource.
Retention policy specified in the NetWorker Client resource for the client (default). Valid date in nsr_getdate(3) format.
parallelism
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 the NMSAP backup or restore. Ensure that the NetWorker server is configured to support this parallelism value or greater. Set the Client resource on page 27 provides more information. Note: The parallelism value will be reduced if it is greater than the value of the savesets parameter.
8 (default) Any positive integer.
pool
Specifies the NetWorkerMedia Pool resource, defined on the NetWorker server, that receives backup data from the SAP Oracle server. This parameter is used for manual backups and is not recommended for scheduled backups. Note: If set for scheduled backups, this parameter overrides the NetWorker server setting. To use multiple pools to separate data: 1. Create separate init<DBSID>.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 type the following command at the command line: brarchive -u sys/admin -d util_file -r archiveC11.utl -m all -s save
Most appropriate pool, selected by the NetWorker server (default). Valid name of a NetWorker volume pool.
prev_bk_restore
UNIX only. When the query_index parameter is set to FALSE, parameter specifies whether to restore the previous backup if the required backup cannot be found.
86
Table 14
Supported backint parameters (page 6 of 7) Description Chapter 7, Snapshot Backup with PowerSnap, provides details on PowerSnap parameters and their values. Default and valid values
Parameter ps_backup_mode ps_archive_mode ps_restore_mode ps_inquire_mode ps_opaque_pfilename ps_exclude_backup_bi_run_nums ps_exclude_archive_bi_run_nums ps_exclude_backup_paths ps_exclude_archive_paths ps_ps_before_nonps ps_group_objs query_index
UNIX only (Microsoft Windows is always TRUE). Specifies whether to query the NetWorker server indexes for validation of the requested files and backup IDs before a restore begins. If set to FALSE, the query does not occur. 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;/lotus/data Specifies the number of times that a failed backup is attempted for each save set. Specifies the number of save sets to divide the files on a client and distribute the backup load. 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. This value is ignored if the ss_group_by_fs parameter is set to TRUE. 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 time-out period. Specifies the hostname of the NetWorker server that the NMSAP backint program uses for backup, restore, and inquiry sessions. Note: This parameter does not need to be set for scheduled backups, but if it is, it must match the server that started the backup, or an error occurs.
raw_dir
Undefined (default) The directory names of the raw disk partitions
retry_count
0 (default) Any positive integer 20 (default) Any positive integer
savesets
sem_timeout
30 (default) Any positive integer
server
The local host (default) The NetWorker server hostname
ss_group_by_fs
If set to TRUE, ignores the savesets and ss_size_max parameters and groups save sets by file system instead of file size. This more efficient grouping of files can improve performance of scheduled backups, index searches, and restore times.
87
Table 14
Supported backint parameters (page 7 of 7) Description Specifies maximum save set size in megabytes. If not set, or set to zero, then size is unrestricted. The value must be equal to or greater than the size of the largest datafile. Sets the naming convention for save sets. If set to old, then the name for all save sets is backint:<DBSID>. 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:<DBSID>: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 show each filename as part of the save set name. If set to old_pid or new_pid, then the save set name is generated according to the old or new naming convention and the process id is added to the saveset name. Default and valid values 0 (default) Any positive integer old (default) new old_pid new_pid
Parameter ss_size_max
ssNameFormat
NMSAP nsrsapsv parameters

The nsrsapsv parameters provide environmental and other values to the NMSAP scheduled backup program, nsrsapsv. Among other functions, these parameters may be used to:

Specify nondefault locations of required programs and files. Configure system-specific environment variables. Identify the specific SAP Oracle database instance to back up. Specify the BRTools command and options to be used for the scheduled backups.
These parameters can be set in the wizard or in the configuration file, nsrsapsv.cfg, for non-wizard configurations.
Configure the NMSAP configuration file

Make a copy for your own use of the original configuration file template (nsrsapsv.cfg) supplied with the NMSAP software.
Note: When NMSAP software is uninstalled or upgraded to new releases, the original template file is deleted, along with any settings you may have made in it.
The template file is located at:

Linux and UNIX: /etc/nsrsapsv.cfg Windows: NetWorker_install_directory\nsr\bin\nsrsapsv.cfg
To set the parameters in the NMSAP backup configuration file (nsrsapsv.cfg), use the following format and the guidelines:
parameter = value
Uncomment and modify as necessary all parameters to be used in the scheduled backups.
88
Parameter names and values are case-sensitive. Use full pathnames for parameters that specify a path or filename. Special Oracle characters, such as ?, are not supported. Also, environment variables, such as $ORACLE_HOME and %ORACLE_HOME%, are not supported. The full pathname of the configuration file is specified in the Backup Command attribute of the Client resource configured for the scheduled backup, Set the Client resource on page 27 provides details.
Supported nsrsapsv parameters

Table 15 on page 89 lists the parameters and valid values for the NMSAP backup configuration file (nsrsapsv.cfg), used by the nsrsapsv program.
Table 15
Supported nsrsapsv parameters (page 1 of 3) Description Mandatory for non-wizard configurations only. Do not use for wizard configurations. Specifies the brbackup or brarchive command and its options that the nsrsapsv scheduled backup program will execute. Note: Do not use the -u option, which identifies the username and password of the Oracle database administrator. Instead, the username and password should be encrypted by using the nsrsapadmn -P -z filename command. Configure the scheduled backup resources without the wizard on page 27 provides further details on username and password encryption. Caution! If a wizard configuration is saved to a file, for example, nsrsapsv.cfg, the file will contain the following parameters that the nsrsapsv program uses to generate the brbackup or brarchive command at run time: BKUP_TYPE BKUP_OBJECTS TABLESPACE DATAFILE LOGS_NUM LOGS_DEL BRACHIVE_CLI BRBACKUP_CLI SAP_CONFIG Ensure these wizard parameters are not used if the nsrsapsv.cfg file is manually configured. Default and valid values brbackup (default) brbackup, brarchive (and command line options for either)
Configuration parameter BR_EXEC
HOMEDRIVE
Optional, use for Microsoft Windows systems only. Specifies the drive name where Windows system files reside. Verify this setting by typing set homedrive in a command line. For example: HOMEDRIVE=C: Mandatory. Specifies the language character set. Format the value of this parameter as follows: LANGUAGE_TERRITORY.CHARACTERSET For example: NLS_LANG=AMERICAN_AMERICA.US7ASCII The Oracle documentation provides more information.
Undefined (default) Valid disk drive
NLS_LANG
AMERICAN_AMERICA.US7ASCII (default) Valid Oracle setting for NLS_LANG variable.
89
Table 15
Supported nsrsapsv parameters (page 2 of 3) Description Optional, use for UNIX systems. Hides the Oracle user password that is passed to the brbackup -u or brarchive -u command from operating system commands, such as ps -ef. If RMAN is used to back up database files, set this parameter to yes by uncommenting its line in the file. For example: NSR_SAP_USING_RMAN_OPTION=yes Specifies how long after a backup is aborted by the user the nsrsapsv program waits for the brbackup program to do the following: Perform a cleanup routine Remove tablespaces from backup status. Mandatory only if the Oracle binaries are not in the default location, $ORACLE_HOME/bin. Specifies the location of the Oracle binaries. The specified path is appended to the PATH environment variable so that all Oracle binaries may be found. Mandatory. Specifies the home directory pathname of the Oracle Server installation. Use the full pathname. For example: ORACLE_HOME=/db/oracle/product/10.2.0 Default and valid values FALSE (default) TRUE FALSE (default) TRUE
Configuration parameter NSR_SAP_SECURE_RUN
NSR_SAP_USING_RMAN_OPTION
NSR_SAP_WAIT_BRTOOLS_DONE_MINS
2 minutes (default) Positive number of minutes
ORACLE_BIN
$ORACLE_HOME/bin (default). Valid path of bin directory of the Oracle server installation.
ORACLE_HOME
Undefined (default). Valid pathname of the home directory of the Oracle server installation.
ORACLE_SID
Mandatory. For non-wizard configuration, must be set either in Oracle SID derived from the the configuration file or in the saveset field of the Client resource. save set name in the NetWorker Client resource used for the Specifies the system identification (SID) for the Oracle instance backup (default). to be backed up. A valid Oracle database SID. For example, if the save set name in the NetWorker Client resource is backint:SAP and this parameter is not specified in the configuration file, then SAP is used for the Oracle SID. Optional. Contains the SAP users encrypted Oracle username and password. Do not manually add or edit this parameter. Use the nsrsapadm -P -z command instead. Configure the scheduled backup resources without the wizard on page 27 provides details on username and password encryption. Passwords entered through the wizard are not stored in the configuration file but are securely stored in a lockbox. Mandatory. Contains the SAP users operating system username and password. Do not manually add or edit this parameter. Use the nsrsapadm -P -z command instead. Configure the scheduled backup resources without the wizard on page 27 provides further details on username and password encryption. Passwords entered through the wizard are not stored in the configuration file but are securely stored in a lockbox. Uneditable value (set with the nsrsapadm -P -z command).
ORACLE_USR_PASSWD
OS_USR_PASSWD
Uneditable value (set with the nsrsapadm -P -z command).
90
Table 15
Supported nsrsapsv parameters (page 3 of 3) Description Optional. Specifies the required path of the NetWorker client binary file, and any other required search paths. The specified value is appended to the PATH environment variable. To specify multiple search paths, use one of the following two methods: PATH=d:\dir1;d:\dir2;d:\dir1\dir2\dir3 or PATH=d:\dir1 PATH=d:\dir2 PATH=d:\dir1\dir2\dir3 Mandatory. Specifies the path to the location of the BRTools binary files. This should also be where the backint (UNIX) or backint.exe (Microsoft Windows) executable resides, after it is manually moved to this location following installation of the NMSAP software. This location is added to the PATH environment variable so that the BRTools binaries and backint can be found. For example: SAP_BIN=/usr/sap/SAP/SYS/exe/run Mandatory. Specifies the root directory for SAP datafiles. For example: SPDATA_HOME=d:\orant\SAP\ The SAP documentation provides details. Mandatory for brbackup to run properly on Windows systems. They are normally set in the SAP environment on Windows. Examples: SAPARCH=d:\orant\SAP\saparch SAPBACKUP=d:\orant\SAP\sapbackup SAPCHECK=d:\orant\SAP\sapcheck SAPREORG=d:\orant\SAP\sapreorg SAPTRACE=d:\orant\SAP\saptrace Optional. Appends values to any environment variable named name_path (for example, LD_LIBRARY_PATH, LIBPATH, SHLIB_PATH). If an environment variable with this name already exists, then the parameter value specified 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 Optional. Adds 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. Default and valid values Undefined (default). Valid paths separated by semicolons on UNIX or colons on Windows.
Configuration parameter PATH
SAP_BIN
Undefined (default). Valid full path of BRTools location.
SAPDATA_HOME
Undefined Valid full path of root directory of SAP Oracle datafiles.
SAP-specific environment variables: SAPARCH SAPBACKUP SAPCHECK SAPREORG SAPTRACE
UNIX default: $ORACLE_HOME/sapxxx where xxx is the appropriate suffix: arch, backup, check reorg, or trace. Windows default: none. Valid full path of the SAP log directory. Any valid environment variable and pathname.
Any name_path=value pair
Any name=value pair
Any valid environment variable and value.
91
NMSAP parameters for RMAN backups and restores

If RMAN is chosen as the backup and restore utility as described in Choosing either backint or RMAN as the backup and restore utility on page 21, then the NMSAP parameters for RMAN backups and restores must be set through BRTools parameters as described in the following sections.
Configure the RMAN parameters

The NMSAP parameters for RMAN backups and restores must be set in the BRTools initialization file, init<DBSID>.sap, with either the rman_send or the rman_parms option.
Note: Set the parameters with the rman_send option unless stated otherwise.
The BRTools initialization file is normally located in the following directory:

On Microsoft Windows systems: %ORACLE_HOME%\DATABASE On UNIX or Linux systems: $ORACLE_HOME/dbs
Supported NMSAP RMAN parameters

Table 16 on page 92 lists the NMSAP parameters to configure the RMAN backups and restores.
Table 16
Supported NSR_* parameters for RMAN (page 1 of 3) Description Corresponds to the NSR_AES_ENCRYPTION parameter in Table 14 on page 82. Corresponds to the checksum parameter in Table 14 on page 82. Corresponds to the client parameter in Table 14 on page 82. Corresponds to the compress parameter in Table 14 on page 82. Corresponds to the pool parameter in Table 14 on page 82. Optional. Controls the amount of debug information that NMSAP writes to the debug log file, which is specified by NSR_DIAGNOSTIC_DEST. 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. Note: This parameter must be set in the rman_parms parameter. Do not set it in the rman_send parameter. 0 (default, no debugging). 09 Default and valid values
Parameter NSR_AES_ENCRYPTION NSR_CHECKSUM NSR_CLIENT NSR_COMPRESSION NSR_DATA_VOLUME_POOL NSR_DEBUG_LEVEL
NSR_DEDUP_BACKUP
Corresponds to the NSR_DEDUP_BACKUP parameter in Table 14 on page 82.
92
Table 16
Supported NSR_* parameters for RMAN (page 2 of 3) Description Corresponds to the NSR_DEDUP_CACHE_ENABLED parameter in Table 14 on page 82. Corresponds to the NSR_DEDUP_CACHE_TAG parameter in Table 14 on page 82. Set a different value for each channel. If the same tag value is used for more than one channel, the deduplication backup fails. Set this parameter in the rman_send parameter in the BRTools parameter file (init<DBSID>.sap). Configure deduplication for Oracle RMAN backup on page 32 gives an example. Corresponds to the NSR_DEDUP_CHUNK SIZE parameter in Table 14 on page 82. Corresponds to the NSR_DEDUP_NODE parameter in Table 14 on page 82. Corresponds to the NSR_ENCRYPTION_PHRASES parameter in Table 14 on page 82. Corresponds to the NSR_NWPATH parameter in Table 14 on page 82. 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 parameter is always set to FALSE. 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. / (forward slash all RMAN channels) (default). Alphanumeric string that will generate a deduplication cache name. Do not include the client name in the value. Recommended value is: <DBSID>_<channel-ID> for example: orcl10g_1. Default and valid values
Parameter NSR_DEDUP_CACHE_ENABLED
NSR_DEDUP_CACHE_TAG
NSR_DEDUP_CHUNK SIZE NSR_DEDUP_NODE NSR_ENCRYPTION_PHRASES NSR_NWPATH NSR_NO_BUSY_ERRORS
NSR_NO_MULTIPLEX
Optional. When set for a specific RMAN channel, specifies whether multiplexing is disabled during a backup on the NetWorker device that the RMAN channel is using. If multiplexing is disabled, no other save sets can be written to the device. To optimize restore operations, RMAN requires NMSAP backups to not be multiplexed. Setting the parameter to TRUE may affect the backup performance. For example, the device may sit idle during part of the backup. If the performance is adversely affected, reset the parameter to FALSE. Optional. Specifies whether the NetWorker browse and retention policies are disabled. Set to TRUE to use Oracle policies only (not NetWorker policies) to manage the backup data lifecycle. Then the RMAN catalog and NetWorker indexes cannot become unsynchronized, fsuch as when a NetWorker index entry is expired but the corresponding RMAN catalog entry is not expired.
FALSE (default). Multiplexing is enabled on the device that the RMAN channel is using. TRUE. Multiplexing is disabled on the device that the RMAN channel is using. Note: If a random access NetWorker device such as an advanced file device is used, do not set the parameter to TRUE.
NSR_RETENTION_DISABLED
FALSE (default). NetWorker browse and retention policies are enabled, and used to manage the lifecycle of the Oracle backup data. TRUE. NetWorker browse and retention policies are disabled. Only Oracle policies are used to manage the lifecycle of the Oracle backup data.
93
Table 16
Supported NSR_* parameters for RMAN (page 2 of 3) Description Corresponds to the NSR_DEDUP_CACHE_ENABLED parameter in Table 14 on page 82. Corresponds to the NSR_DEDUP_CACHE_TAG parameter in Table 14 on page 82. Set a different value for each channel. If the same tag value is used for more than one channel, the deduplication backup fails. Set this parameter in the rman_send parameter in the BRTools parameter file (init<DBSID>.sap). Configure deduplication for Oracle RMAN backup on page 32 gives an example. Corresponds to the NSR_DEDUP_CHUNK SIZE parameter in Table 14 on page 82. Corresponds to the NSR_DEDUP_NODE parameter in Table 14 on page 82. Corresponds to the NSR_ENCRYPTION_PHRASES parameter in Table 14 on page 82. Corresponds to the NSR_NWPATH parameter in Table 14 on page 82. 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 parameter is always set to FALSE. 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. / (forward slash all RMAN channels) (default). Alphanumeric string that will generate a deduplication cache name. Do not include the client name in the value. Recommended value is: <DBSID>_<channel-ID> for example: orcl10g_1. Default and valid values
Parameter NSR_DEDUP_CACHE_ENABLED
NSR_DEDUP_CACHE_TAG
NSR_DEDUP_CHUNK SIZE NSR_DEDUP_NODE NSR_ENCRYPTION_PHRASES NSR_NWPATH NSR_NO_BUSY_ERRORS
NSR_NO_MULTIPLEX
Optional. When set for a specific RMAN channel, specifies whether multiplexing is disabled during a backup on the NetWorker device that the RMAN channel is using. If multiplexing is disabled, no other save sets can be written to the device. To optimize restore operations, RMAN requires NMSAP backups to not be multiplexed. Setting the parameter to TRUE may affect the backup performance. For example, the device may sit idle during part of the backup. If the performance is adversely affected, reset the parameter to FALSE. Optional. Specifies whether the NetWorker browse and retention policies are disabled. Set to TRUE to use Oracle policies only (not NetWorker policies) to manage the backup data lifecycle. Then the RMAN catalog and NetWorker indexes cannot become unsynchronized, fsuch as when a NetWorker index entry is expired but the corresponding RMAN catalog entry is not expired.
FALSE (default). Multiplexing is enabled on the device that the RMAN channel is using. TRUE. Multiplexing is disabled on the device that the RMAN channel is using. Note: If a random access NetWorker device such as an advanced file device is used, do not set the parameter to TRUE.
NSR_RETENTION_DISABLED
FALSE (default). NetWorker browse and retention policies are enabled, and used to manage the lifecycle of the Oracle backup data. TRUE. NetWorker browse and retention policies are disabled. Only Oracle policies are used to manage the lifecycle of the Oracle backup data.
94
Table 16
Supported NSR_* parameters for RMAN (page 3 of 3) Description Corresponds to the NSR_SAVESET_BROWSE parameter in Table 14 on page 82. Corresponds to the NSR_SAVESET_RETENTION parameter in Table 14 on page 82. Corresponds to the server parameter in Table 14 on page 82. Default and valid values
Parameter NSR_SAVESET_BROWSE NSR_SAVESET_RETENTION NSR_SERVER
95
96
B

Examples of brbackup and brarchive command syntax and options ................... 98 Examples of brrestore command syntax and options.............................................. 99 Examples of brrecover command syntax and options............................................. 99
97
Examples of brbackup and brarchive command syntax and options

The SAP brbackup and brarchive commands can be used with the NMSAP program from any command prompt. Examples of the syntax and options for these commands are as follows:
brbackup [-c force][-d {util_file|util_file_online|rman_util}] [-m {all|all_data|full|incr|tablespace_list|file_ID|file_ID1_range|file_list}] [-p profile] [-q check] [-r parameter_file] [-t {online|offline|offline_force|offline_standby|online_split|offline_split}] [-u user/password][-w [use_dbv|only_config]] brarchive [-c force][-d {util_file|rman_utl}][-f stop] [-m delay_time][-p profile][-q check][-r parameter_file] [-u user/password]
Options enclosed in brackets ([ ]) are optional. Options enclosed in braces ({ }) must use at least one of the enclosed options. Variables are in italics. Key words are in plain text. Table 17 on page 98 lists example options for these commands. The SAP documentation provides complete details of these commands.
Note: The command line options overwrite the corresponding parameters set in the SAP parameter file init<DBSID>.sap.
Table 17
Options for brbackup and brarchive command Option -c force -d util_file | util_file_online | rman_util -f stop -m <objects_to_back_up> Description Suppresses most of the confirmation messages that interrupt the backup process. Specifies that NMSAP with backint or RMAN is used for the backup or archive process. Instructs brarchive to wait for the next offline redo log file written by Oracle, and then send it to backint for archiving. Specifies what database objects to back up, for examples whole database, selected tablespaces or datafiles, incremental RMAN backup, and so forth. This option is used by brbackup. Specifies the delay time between Oracle creating the offline redo log file and sending datafiles to the database in standby mode. This option is used by brarchive. Specifies an initialization BRTools parameter file if the file does not have the default name or is not stored in the default location. Specifies the parameter file, init<DBSID>.util, that NMSAP backint uses during the backup or archive process. Instructs brbackup and NMSAP backint what type of backup to perform. During an online backup, to reduce the number of redo logs that Oracle generates, use this option with the -d util_file_online option. Specifies the Oracle database administrators username and password. Verifies the backup after the files have been backed up. Helps detect possible hardware problems. The use_dbv option performs the backup followed by a restore of the backup to a temporary location. This option approximately doubles backup time.
-m delay_time
-p profile -r parameter_file -t <backup_type>
-u user/password -w use_dbv | only_config
98
Examples of brrestore command syntax and options

The SAP brrestore command can be used with the NMSAP backint program from any command prompt. An example of the syntax and options for this command is as follows:
brrestore [-c force][-d {util_file|rman_util}] [-f last|brtools_log1, <brtools_log2>,..|<yyyy-mm-dd hh-mmss>|<numofdays>] [-m {all|all_data|full|incr|tablespace_list|file_ID|file_ID1_range|file_list}] [-p profile][-q check][-r parameter_file]
Options enclosed in brackets ([ ]) are optional. Options enclosed in braces ({ }) must use at least one of the enclosed options. Table 18 on page 99 lists example options for this command. The SAP documentation provides complete details of this command..
Table 18
Options for brrestore command Option -c force -d util_file | rman_utl -f <restore to complete> -m <objects_to_restore> -p profile -r parameter_file Description Suppresses most of the confirmation messages that interrupt the restore process. Specifies that NMSAP with backint or RMAN is used for the restore. Specifies which restores to re-start to restore missing files. Specifies what database objects to restore, such as whole database, selected tablespaces or datafiles, and incremental RMAN backup. Specifies an initialization BRTools parameter file if the file does not have the default name or is not stored in the default location. Specifies the parameter file, init<DBSID>.util, that NMSAP backint uses during the restore process.
Examples of brrecover command syntax and options

The SAP brrecover command can be used with the NMSAP program from any command prompt. An example of the syntax and options for this command is as follows:
brrecover [-c force][-d {util_file|rman_util}][-p profile] [-pit yyyy-mo-dd hh.mi.ss][-r parameter_file][-scn scn] [-t complete|dbpit|tspit|reset|restore|apply|disaster] [-tsp tablespace_name|tablespace_name_list][-u user/password]
For example:
brrecover -t complete -p initGC2.sap
Table 19 on page 100 lists examples of options for this command. The SAP documentation provides complete details of these commands.
Examples of brrestore command syntax and options
99
Table 19
Options for brrecover command Option -c force -d util_file | rman_util -p profile -pit yyyy-mo-dd hh.mi.ss -r parameter_file -scn scn -t complete | dbpit | tspit | reset | restore | apply | disaster Description Suppresses most of the confirmation messages that interrupt the recovery process. Recovers NMSAP backups performed with backint (util_file) or RMAN (rman_file). Specifies an initialization BRTools parameter file if the file does not have the default name or is not stored in the default location. Recovers the database or tablespaces for a specific point in time. Specifies the parameter file, init<DBSID>.util, that NMSAP backint uses during the backup or archive process. Recovers the database to the specified Oracle system change number. 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 Recovers a single specified tablespace or the tablespaces listed in the specified file. Specifies the Oracle database administrators username and password.
-tsp tablespace_name | tablespace_name_list -u user/password
100
C
Troubleshooting

Verifying the release information.............................................................................. Generating diagnostic logs ........................................................................................ Backup and restore problems .................................................................................... NMSAP Error messages .............................................................................................
102 102 102 103
Troubleshooting
101
Troubleshooting
Verifying the release information

When making queries or requests to an EMC Customer Support Representative, provide specific information about the NMSAP software you are using. To verify the release information for your installation, use the appropriate command or procedure:
On UNIX systems, type the following command as the root user:

what filename | more
where filename is the name of an NMSAP binary file, for example, backint or nsrsapsv.
On Linux systems, type the following command as the root user:

strings filename | grep "@(#)"
where filename is the name of an NMSAP binary file, for example, backint or nsrsapsv.
On Microsoft Windows systems: a. Locate the NMSAP binary file, for example, backint.exe or nsrsapsv.exe. b. Right-click the file, and select Properties. c. In the Properties window, click the Version tab to display the version information.
Generating diagnostic logs

To generate backint diagnostic logs, set the following parameters:
NSR_DEBUG_DIR (if not using the default location nsr/applogs) debug_level = 9 Note: Debug level is intended for testing and EMC Customer Support diagnostics only.
Backup and restore problems

Table 20 on page 102 provides guidelines for solving problems that may occur during an NMSAP backup or restore.
Table 20
NMSAP backup or restore problems (page 1 of 2) Possible reason or solution NMSAP uses the Client resource settings only for scheduled backups. For manual backups, the settings must be specified in the init<DBSID>.utl.The client settings must be specified in the init<DBSID>.utl file on the SAP Oracle server. Configure the NMSAP parameter file on page 82 provides more information. Bootstrap notification reports are not generated after a manual NMSAP backup. Back up the NetWorker bootstrap and online indexes on page 40 provides information on the generation of a bootstrap notification report. Oracle creates more online redo logs during an online backup than during an offline backup. This might prolong the online backup.
Problem Data is not being backed up by using the settings in the Client resource on the NetWorker server.
The bootstrap notification report was not printed to the printer specified in the Group resource on the NMSAP server. Online backup of an Oracle tablespace is taking a long time.
102
Troubleshooting
Table 20
NMSAP backup or restore problems (page 2 of 2) Possible reason or solution The parallelism setting is adjusted by backint during the backup session depending on other parameters, such as when the number of files within the backup session is lower than the server parallelism setting. NMSAP does not support the backup of directories. Specify each database object within the directory to back up and then perform the backup. Ensure that the SAP user has proper privileges to view the information, for example, the Operate NetWorker privilege. 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. The prev_bk_restore in Configure the NMSAP parameter file on page 82 provides more information. Ensure that the SAP users operating system authorization has the appropriate permission to access the NetWorker server.
Problem Following a backup, the parallelism setting in the NMSAP operation log, backint<DBSID>.log.raw, is different from the configuration setting. A specified backup of an Oracle directory failed. You are unable to view the files backed up to the NetWorker server from the BrGui program on the SAP Oracle server. You are unable to view backup information in NetWorker online indexes.
NMSAP Error messages

Table 21 on page 103 lists possible error messages that might appear in the backint<DBSID>.log.raw file.
Table 21
NMSAP error messages (page 1 of 3) Description 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). The backint program was unable to connect to the NetWorker server to start reading the media database. The backint program was unable to open a log file for writing. The backint program was unable to start reading the media database on the NetWorker server. The existence of the semaphore file could not be confirmed because of a system 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. The input file that contains the list of files to be backed up or restored is empty. 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. Solution Check the input file BRTool binary generated to make sure it has the correct format. If not, and this error recurs, contact SAP customer support. Ensure that the correct NetWorker server is specified. Check the log file to see if any other messages refer to this problem. Check the permissions on the file listed in the message, as well as the permissions on the directory. Ensure that the correct NetWorker server is specified. Check the log file to see if any other messages refer to this problem. Check to see if the .switch.sem file is still in the SAPBACKUP directory. If so, delete it before running the SAP backup again. Check the directory where the directive file is being created, specified by the backint_tmpdir parameter in the NMSAP parameter file, to ensure files can write to it. Ensure that you have selected database objects for backup or restore. Ensure that the input file exists and is readable.
Error message BACKUP: Bad input line: line INQUIRE: Bad input line: line RESTORE: Bad input line: line Cannot connect to server: error
Cannot reopen filename as stderr Cannot start session with server: error Checking for deletion of semaphore file: error Creating directive file: error
Empty input file Error opening input file: error
Error opening output file: error
Check the permissions on the output file and directory, and check for sufficient disk space to create a new file.
103
Troubleshooting
Table 21
NMSAP error messages (page 2 of 3) Description The backint program does not support the file type (such as a symbolic link or a named pipe). There are too many symbolic links to save (more than 100). The files requested in the input file do not match the SAP 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. The NetWorker software did not save the filename specified for recovery. The filename does not appear in the client file index. NMSAP tried to get information for a symbolic link that does not exist, or NMSAP cannot access because permission is denied. The backup ID is incorrect. It should specify either a number or the word #NULL. 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. You have attempted to back up a directory. The backup of directories is not supported. 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. Solution Check the filename to see what type of file is being backed up. If brbackup requests a backup of special files, contact SAP support. 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. Check the backup input file generated by brbackup. If the input file generated appears to be the wrong format, contact SAP support.
Error message Error: filename isnt a regular file, raw partition, or directory. Error: Too many symlinks
Error: unexpected inquire case.
File filename not found in index, no attempt to recover will be made File was filename, lstat error
Check the specified filename to see if the name is correct. Check previous backups to determine whether the file was actually saved in a previous backup. Check the file to see that it exists and is a valid symbolic link. Check the input file brrestore generated to ensure that it has the correct format. If not, and this error keeps occurring, contact SAP customer support. Check the next error message to determine why the attempt to query the index failed.
Improperly formatted backup id: backup ID Lookup failed on filename (backup_ID)
Non-recursive directory backup is not supported at this time Not enough savesets configured. Increase "savesets" setting.
Select specific database objects to back up from the BrGui program and restart the backup process. Increase the number of save sets or the maximum save set size. The savesets parameter in specifies the number of save sets. The ss_size_max parameter in specifies the maximum save set size. Table 14 on page 82 provides details. 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 NMSAP installation package. Check to see if the .switch.lis file exists in the SAPBACKUP directory. If so, check the permissions on this file. Normally, NMSAP deletes and re-creates this file for every tablespace to be switched into backup mode. Check to see if the .switch.log file is still in the SAPBACKUP directory. If so, delete it before running the SAP backup again.
Open param file: <filename>, error: <error msg>
Unable to open the backint parameter file, init<DBSID>.utl.
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.
Opening switch log 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.
104
Troubleshooting
Table 21
NMSAP error messages (page 3 of 3) Description 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. Solution Check to see if the .switch.sem file exists in the SAPBACKUP directory. If so, check this files permissions. Normally, NMSAP deletes and re-creates this file for every tablespace to be switched into backup mode. If brbackup appears to be running properly but just slowly, you can increase the sem_timeout setting for backint. Investigate the error messages in the switch log file to determine the problem. Check the SAP installation or the SAP documentation to determine the problem. Check the memory usage on the computer. Ensure that the backint binary is installed in the directory from which brbackup or brrestore is run. Check the log file for any other messages which may help pinpoint the problem. 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. Check the permissions on the output file and directory, and check for sufficient disk space to create a new file. Check the input file to see if any file information is specified incorrectly. Check the input file brrestore generated to ensure that it has the correct format. If not, and this error recurs, contact SAP customer support.
Error message Opening switch semaphore file for online backup: error
Semaphore file not deleted in time seconds.
When performing an online backup, the SAP module was waiting for the switch semaphore file to be deleted. After waiting seconds, the switch semaphore file still was not deleted. 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. The backint program was unable to allocate memory. The backint process could not execute a subprocess to back up an individual save set.
Switch log file indicates an error.
Unable to allocate memory: error Unable to execute child backint process.
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. The output file could not be opened because of the error specified. The backint program was trying to find a file in the client file index, but neither the save time nor the filename were provided. The filename given in the input file was not an absolute pathname. The file cannot be restored or inquired without having the full pathname.
Unable to open output file: error Unable to query with savetime and filename both absent Use absolute path name for: filename
105
Troubleshooting
106
Glossary
This glossary contains terms and definitions found in this manual. Most of the terms are specific to NetWorker Module for SAP with Oracle (NMSAP) software.
A
ad hoc backup administrator See manual backup. The person who normally installs, configures, and maintains software on network computers, and who adds users and defines user privileges. A Microsoft Windows user group whose members have the rights and privileges of users in other groups, plus the ability to create, modify, and manage the users and groups in the domain. The process by which NetWorker software backs up directories or files to an archive volume to free disk space. Archived data can be deleted but is not recyclable. See redo log. A security method that enables high confidence in the identity of users, clients, and servers in distributed environments. See library.
Administrator group
archive
archived redo log authentication
autochanger
B
backup backup cycle backup volume An operation that saves data to a volume. The period of time from one level full backup to the next level full backup. A volume used to store backup data. Backup data cannot be stored on an archive volume or a clone volume. A save set that is essential for the NetWorker disaster recovery procedures. The bootstrap consists of three components that reside on the NetWorker server: the media database, the resource database, and the server index. A NetWorker policy that specifies the time period during which backup entries are stored in a client file index and the associated backup files are readily accessible to desktop users.
bootstrap
browse policy
107
Glossary
C
carousel client client file index See library. A computer, workstation, or fileserver whose data can be backed up and recovered. A database maintained by the NetWorker server that tracks every database object, file, or file system backed up. The NetWorker server maintains a single index file for each client computer. The tracking information is purged from the index after the browse time of each backup expires. See manual backup.
client-initiated backup clone
A reliable copy of backed up data, which is indexed and tracked. Unlike volumes created with a simple copy command, clone volumes can be used in exactly the same way as the original backup volume. Single save sets or entire volumes can be cloned. An exact duplicate of a backup volume. One of four types of volumes that NetWorker software can track (backup, archive, backup clone, and archive clone). Save sets of these different types may not be intermixed on one volume. 1. Two or more independent network servers that operate and appear to clients as if they were a single unit. The cluster configuration enables work to be shifted from one server to another, thereby providing "high availability," which allows application services to continue despite most hardware or software failures. Also known as an agent (Sun), logical server (HP TruCluster), package (HP-UX), and virtual server (Microsoft). 2. A group of disk sectors. The operating system assigns a unique number to each cluster and keeps track of files according to which clusters they use. The line on a display screen, also known as a command prompt or shell prompt, where you enter software commands. The software program that is used to manage NetWorker servers and clients. The Console server also provides reporting and monitoring capabilities for all NetWorker processes.
clone volume
cluster
command line
Console server
D
datawheel datazone device See library. A group of computers administered by a NetWorker server. 1. A storage unit that reads from and writes to backup volumes. A storage unit can be a tape device, optical drive, library, or file connected to the server or storage node. 2. When dynamic drive sharing (DDS) is enabled, refers to the access path to the physical drive. A method of recovery that recovers data that originated on one client computer and re-creates it on another client computer. An instruction that directs NetWorker software to take special actions on a given set of files for a specified client during a backup or recover operation. Directives are ignored in manual (unscheduled) backups. A hardware device through which media can be read or written to.
directed recovery
directive
drive
108
Glossary
Dynamic Drive Sharing (DDS)
A feature that allows NetWorker software to recognize shared drives and when they are available.
E
enabler code A special code that activates the software. The enabler code that unlocks the base features for software is called a base enabler. Enabler codes for additional features or products (for example, library support) are called add-on enablers.
F
file index file system See client file index. 1. The software interface used to save, retrieve, and manage files on storage media by providing directory structures, data transfer methods, and file association. 2. The entire set of all files. See level.
full backup
G
group A client or group of client computers that are configured to back up files at a designated time of day.
H
high availability system A system of multiple computers configured as cluster nodes on a network that ensures that application services continue despite a hardware or software failure. Each cluster node has its own IP address with private resources or disks that are available only to that computer. A computer on a network. A serial number that uniquely identifies a host computer.
host host ID
I
instant backup The process of creating a point-in-time copy (snapshot) of data from a single client and saving it on a primary storage volume, which can be immediately recovered as a backup copy. The process of copying data created during an instant backup to its original location, or to an alternate location, during a recover operation.
instant restore
L
label An electronic header on a volume used for identification by NetWorker or other data move application. A backup configuration option that specifies how much data is saved during a scheduled or manual backup. A full (f) backup backs up all files, regardless of whether they have changed. Levels one through nine [1-9] backup files that have changed since the last lower numbered backup level. An incremental (incr) backup backs up only files that have changed since the last backup.
level
109
Glossary
library
A hardware device containing one or more removable media drives, as well as slots for pieces of media, media access ports, and a robotic mechanism for moving pieces of media between these components. Libraries automate media loading and mounting functions during backup and recovery. The term library is synonymous with autochanger, autoloader, carousel, silo, datawheel, jukebox, and near-line storage. Also known as a "PIT rollover" or "rollover to tape" backup. A backup to media of a previously created snapshot. The two types of live backup are immediate live backup and deferred live backup.
live backup
M
manual backup A backup that a user performs from the client, also known as an unscheduled backup or an ad hoc backup. The user specifies the files, file systems, and directories to back up. A manual backup does not generate a bootstrap save set. The physical storage, such as magnetic tape, optical disk, or file system, to which backup data is written. A database that contains indexed entries of storage volume location and the life cycle status of all data and volumes managed by the NetWorker server. See media database. The NetWorker database that tracks save sets stored on backup volumes. See pool. To make a database available for use or to place a removable tape or disk volume into a drive for reading or writing.
media
media database
media index Media Manager media pool mount
N
NAS NDMP data server NDMP host NDMP save set NDMP server See Network attached storage (NAS). An NDMP service that either reads from or writes to disk. The host computer that executes the NDMP server application. A save set of an NDMP client that is backed up to an NDMP device. An instance of one or more NDMP services controlled by a single NDMP control connection. Thus a data/tape/SCSI server is an NDMP server providing data, tape, and SCSI services. The virtual state machine on an NDMP host that is controlled by the DMA. Examples of NDMP services include: a general server with direct attached storage (storage appliance), a system with one or more tape drives, or a software process that reads two data streams and multiplexes them into one stream. A host or any open system having NDMP services installed such as Netapp Filer and EMC Filer. See library.
NDMP service
NDMP storage node
near-line storage
110
Glossary
Network attached storage (NAS)
A disk array or storage device (NAS filer) with multiple file systems that connects directly to the messaging network or LAN interfaces and uses common communication protocols (TCP/IP or NDMP). A TCP/IP-based protocol that specifies how heterogeneous network components communicate for the purpose of backup and recovery.
Network Data Management Protocol (NDMP) Network File System (NFS) NetWorker NetWorker Management Console NetWorker resource NetWorker server
A client/server application that allows users to access shared files stored on networked computers of different types. A network-based EMC software product that backs up and recovers file systems. See Console server.
See resource. The computer on a network that runs the NetWorker server software, which contains the online indexes and provides backup and recovery services to the clients on the same network. See Network File System (NFS). A computer that contains exported file systems that NFS clients can access. The master NetWorker server process. The logical hostname of the computer that is the NetWorker server.
NFS NFS server nsrd nsrhost
O
online indexes The records of backup details, consisting of the client file index and the media database, maintained on the NetWorker server. A different backup level that is used in place of the regularly scheduled backup.
override
P
parallelism A method that backs up or recovers data for several clients, or several save sets for one client, at the same time. 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 a file starting from the current location. A NetWorker client that is bound to a physical host in the cluster and can have its own resources (private or local). A node or host that forms part of a cluster. A fully usable copy of a defined collection of data, such as a consistent filesystem, database, or volume, which contains an image of the data as it appeared at a single point in time. A PIT copy is also called a shadow copy or a snapshot.
pathname
physical cluster host
physical host point-in-time (PIT) copy
111
Glossary
policy
A set of constraints that specify how long the save sets for a client are available for recovery. Each client has a browse policy and a retention policy. When the retention policy expires, the save sets associated with that policy are marked recyclable. A feature to sort backup data to selected storage volumes. A surrogate client that performs the NetWorker save operation for the client that requested the backup. A proxy client is required to perform a serverless backup. Removing file data from the extended drive (after the file has been moved to media), while leaving a file tag behind. The file appears as if it is still on the drive. A list of files that have qualified for purge rules but have not yet been purged from the extended drive. Files on the purge list are purged either when a background scan occurs or when extended drive used space reaches a certain level, depending on the configuration.
pool proxy-client
purge
purge list
R
recover To apply transactional logs to a database to make it consistent with a given point in time. A save set whose browse and retention policies have expired. Recyclable save sets are removed from the media database. A volume whose data has exceeded both its browse and retention policies and is now available to be relabeled and reused. The online log (also known as archived redo log) of an Oracle database, consisting of at least two redo log files (separate from the datafiles) that records all changes made in the database instance. A storage device that is attached to a storage node. The protocol that the NetWorker server uses to perform client requests over a network. A component that describes the NetWorker server or its clients. Clients, devices, schedules, groups, and policies are all NetWorker resources. Each resource has attributes that define its properties. A database of information about each resource. The process of retrieving individual files from backup storage and copying the files to disk. A setting that determines the length of time that backup data is retained on a volume available for recovery, though not necessarily immediate recovery. To locate and recover archived files and directories. The process by which a specific point-in-time copy (snapshot) of data is restored to the source location by using the hardware's particular capabilities. A rollback restore is a destructive save set restore. A save set that is backed up to tape from a snapshot. Whether this snapshot is retained or not depends on a snapshot policy. When a snapshot is rolled over to tape,
recyclable save set
recyclable volume
redo log
remote device Remote Procedure Call (RPC) resource
resource database restore
retention policy
retrieve rollback restore
rollover save set
112
Glossary
entries are made in the client file index and media database, which enable the save set to be browsed for recovery. root 1. (UNIX only) The UNIX superuser account. 2. (Microsoft Windows and UNIX) The highest level of the system directory structure. See Remote Procedure Call (RPC).
RPC
S
save The NetWorker command that backs up client files to backup volumes and makes data entries in the online index. A group of files or a file system from a single client computer, which is backed up on storage media. A process that performs a level 1 backup and merges it with the last full backup of a save set to create a new full backup. A internal identification number assigned to a save set. To recover data by specifying save sets rather than by browsing and selecting files or directories. A NetWorker attribute that indicates whether a save set is browsable, recoverable, or recyclable. The save set status also indicates whether the save set was successfully backed up. The data and save set information that is written to a storage volume during a backup. A save stream originates from a single save set. The NetWorker command used to read a backup volume when the online indexes are not available. A type of backup that is configured to start automatically at a specified time for a group of one or more NetWorker clients. A scheduled backup generates a bootstrap save set. A storage library attached to the NetWorker server or storage node, used to store traditional or snapshot backups. A NetWorker server Device resource must be configured for each conventional storage device. See client file index. The storage disk that is connected to multiple nodes in the cluster. System identifier for an Oracle database instance. See library. An EMC software application that manages media resources within a distributed environment. The group of files, volumes, or file systems from a single client that describes the collection of data for which a point-in-time copy is created on an external disk subsystem, such as a storage array.
save set
save set consolidation
save set ID save set recover
save set status
save stream
scanner
scheduled backup
conventional storage
server index shared disk SID silo SmartMedia
snap set
113
Glossary
snapshot snapshot policy
A point-in-time, read-only copy of data created during an instant backup. A set of rules that control the lifecycle of a snap set. The snapshot policy specifies the frequency of snapshots, and how long snapshots are retained before recycling. A protocol used to send messages to the administrator about NetWorker events.
SNMP (Simple Network Management Protocol) ssid staging
See save set ID. Moving data from one storage medium to a less-costly medium, and later removing the data from its original location. A storage device that contains a single drive for backing up data. Stand-alone devices cannot store or automatically load backup volumes. A storage device physically attached to a computer other than the NetWorker server, whose backup operations are administered from the controlling NetWorker server. The person normally responsible for installing, configuring, and maintaining NetWorker software.
stand-alone device
storage node
system administrator
T
tablespace tape service An Oracle database structure that consists of one or more datafiles. An NDMP DSP service that controls access to tape storage. A system can simultaneously host multiple tape services corresponding to multiple backup streams. The number of backup sessions accepted by a backup device. A code that allows operation of the software for an additional 45 days beyond the evaluation period. Unsolicited notification sent from the SNMP agent to the network managers SNMP event manager.
target sessions temporary enabler
trap
U
unscheduled backup update enabler See manual backup. A code that updates software from a previous version. Like other temporary enabler codes, it expires after 45 days.
V
versions virtual cluster client The date-stamped collection of available backups for any single file. A NetWorker client that is not permanently bound to one physical host but is managed by a cluster manager. It can have its own data disks. It is also referred to as a logical cluster client or a virtual client.
114
Glossary
volume
1. A unit of physical storage medium, such as a magnetic tape, optical disk, or file system to which backup data is written. 2. An identifiable unit of data storage that may reside on one or more computer disks. An internal identification that NetWorker software assigns to a backup volume. A disk volume that is grafted into the namespace of a host disk volume. This allows multiple disk volumes to be linked into a single directory tree, and a single disk or partition to be linked to more than one directory tree. The name assigned to a backup volume when it is labeled.
volume ID volume mount point
volume name
115
Glossary
116
Index
A
active-active cluster configurations 54 active-passive cluster configurations 54 advanced file type device (AFTD) 29 archived redo logs 40, 72 Avamar server 29, 42
B
backint command 17 location 20 backint parameter file 82 backup archived redo logs 40 bootstrap file 40 client file index 40 cloning 42 manual 39 PowerSnap 58 probe-based 32 Replication Manager 72 session log 41 snapshot 58 split-mirror 72 Backup Command client attribute 28 backup notifications, email 35 bootstrap file 12, 40, 50 BR_EXEC configuration parameter 89 brarchive command 98 brbackup command 98 BrGui interface 22 brrecover command 46, 99 brrestore command 46, 99 BRTools 17, 21, 22
cluster backups 54 cloning backups 43 deduplication backup 55 manual backups 55 restoring backups 56 split-mirror backup 77 command backint 17 brarchive 98 brbackup 98 brrecover 46, 99 brrestore 46, 99 mminfo 41, 70 nsrinfo 41 nsrsapsv 17 sapclone 43 savegrp 40 component software used with NMSAP 17 configuration file conversion 25 created by wizard 23 init(DBSID).sap file 21 init(DBSID).utl file 17, 66 nsrsapsv.cfg 88 convert backup settings from earlier releases 25, 55
D
data flow PowerSnap 61 data mover 58, 72 DBSID 12, 90 debug level 102 deduplication backup cluster 55 deletion and expiry 42 manual 31 requirements 29 scheduled 30 with Oracle RMAN 32 with the wizard 30 without the wizard 31 deletion of deduplication backups 42
117
C
cancel manual backup 41 cancel scheduled backup 39 choosing the backup and restore utility 21 client indexs 50 Client resource attributes 27, 28 cloning backups 42
Index
destination host 47, 51 diagnostic logs 102 disaster recovery 12, 50
E
email backup notifications 35 encryption, SAP user for OS and Oracle 26 environment, NMSAP software 16 error messages 103 event-based backup 32
nsrsapadm command 26 nsrsapadm utility 18, 25 nsrsapprobe program 33 nsrsapsv command 17 nsrsapsv.cfg file 17, 26, 88
O
online indexes 41 Oracle Real Application Cluster (RAC) 56
F
firewall 20
P
parameter file created by wizard 23 init(DBSID).utl 82 password, SAP user 26 point-in-time (PIT) copy 60 PowerSnap backup configuration 63 backup records 70 backup types 59 configuration file 66 data flow descriptions 61 description 58 examples 69 NAS devices 69 parameters 65, 66 PIT copy 60 ps_opaque_pfilename file 68 requirements 58 restore types 61 testing 68 privileges for NMSAP operations 20 probe-based backup description 32 example 34 multiple probes 34 problems, backup or restore 102 Proxy client host 58 ps_opaque_pfilename file 68 ps_opaque_pfilename parameter 66
G
generic Client resource 54
I
I18N support 15, 21 init(DBSID).sap file 21, 76 init(DBSID).utl file 17, 66, 82 init.utl file 26 internationalization support 15
L
Lockbox resource, in cluster 54 logs archived redo 40 backup session reports 41
M
manual backup bootstrap 40 cancelling 41 client file indexes 40 cluster 55 commands 98 configuration 29 deduplication 31 monitoring 41 performing 39 media database 41 mirror host 72 mminfo command 41, 70 mount host 72 multiple probes 34
Q
query the client file index 41
R
RAC data backups 56 restoring 56 recover brrecover 99 defined 12 description 46 parameter file 100 Replication Manager 72 See also split-mirror backups restart a restore 48 restore brrestore 99
N
NAS devices 64 NMC program 23, 26 NMSAP components 17 environment 20 features 13 nmsapps.cfg file 66 non-ASCII (I18N) characters 15 nsrinfo command 41
118
Index
cluster data 56 defined 12 description 46 restart for missing files 48 to a different host 47, 51 to a new location 47 restore and recover data 46 reviewing backups 41 RMAN 21 enabling 22 parameters 22 rollover to conventional storage 60
W
wizard description 14, 23 limitations 23 requirements 24
S
sapclone command 18, 43 save archived redo logs 40 client file index 40 save sets, cloning 42 savegrp command 40 scheduled backup canceling 39 cluster environment 54 configuration file 88 configuration with wizard 23, 24 configuration without the wizard 26 deduplication 30 monitoring 38 performing 38 PowerSnap 72 probe-based 32 snapshot 72 testing 38 snap set 60 snapshot backup 58 See also PowerSnap snapshot rollover 60 software used with NMSAP 20 splitint interface 72 split-mirror backups 72 cluster configuration 77 example parameters 79 example scripts 78 mount host configuration 75
T
template files 26 testing scheduled backups 102
U
uid bit 20 user privileges for NMSAP 20 username of SAP user 26
V
version information, verifying 102 virtual host 54 VMware support 14
119
Index
120

SAP Ora 4 Admin

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Ora 4 Admin

Uploaded by

Copyright:

Available Formats

EMC NetWorker Module for SAP with Oracle

EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103

Preface Chapter 1 Introduction

Data Restore and Recovery

Cluster and Oracle RAC Configurations

Snapshot Backup with PowerSnap

Split-Mirror Backup with Replication Manager

NMSAP Parameter and Configuration Files

Examples of SAP Command Options

Conventions used in this document

EMC uses the following conventions for special notices.

Where to get help

This chapter includes the following sections:

restore and recover

The Glossary provides a complete list of terms used in this guide.

Complete backup protection

These backups are important for the following reasons:

NetWorker Module for SAP with Oracle Software features

Support of Non-English characters

NMSAP and associated software

NetWorker PowerSnap software

EMC Replication Manager software

SAP server software

Oracle server software

NMSAP software components

libnworasap.xx (UNIX) orasbt.dll, nsrsbtcnsap.exe (Windows) nsrsapsv[.exe] nsrsapsv.cfg

NMSAP software components

SAP Solution Manager registration file. Reference for NMSAP commands.

This chapter includes the following sections:

Verifying the NMSAP software requirements

Configuring I18N support

Requirements for I18N support

The NetWorker documentation provides specific details on NetWorker I18N requirements.

Configure I18N support (UNIX only)

4. Restart the NetWorker services.

Choosing either backint or RMAN as the backup and restore utility

Configuring I18N support

Set backint as the backup and restore utility

where ? is $ORACLE_HOME On Microsoft Windows systems:

Set RMAN as the backup and restore utility

Configuring a scheduled backup with the wizard

Configuring a scheduled backup without the wizard on page 26 gives details.

Configuring a scheduled backup with the wizard

Configure a scheduled backup with the wizard

Converting client-side configurations to wizard configurations

Converting client-side configurations to wizard configurations

Configuring a scheduled backup without the wizard

Configure the NMSAP parameters without the wizard

Configure the scheduled backup resources without the wizard

Configuring a scheduled backup without the wizard

Browse Policy Deduplication Backup Deduplication Node Group Name Parallelism

Password Remote Access

Remote User Retention Policy Save Set

Configuring a manual backup

Configuring a deduplication backup

Requirements for a deduplication backup

Best practices for a deduplication backup

Configuring a manual backup

The following practices can improve deduplication backup performance:

Configure deduplication for a scheduled backup

Configure deduplication for a manual backup

Configuring a deduplication backup

Configure deduplication for Oracle RMAN backup