EMC NetWorker Module for SAP 8.2 Administration Guide

EMC® NetWorker® Module for SAPVersion 8.2

Administration GuideP/N 302-000-388

REV 03

Copyright © 2009-2014 EMC Corporation. All rights reserved. Published in USA.

Published November, 2014

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC NetWorker Module for SAP 8.2 Administration Guide

9

11

13

Overview of NMSAP Features 17

Road map for NMSAP operations...................................................................18Terminology used in this guide......................................................................18Importance of backups and the backup lifecycle........................................... 19NMSAP features for all supported applications..............................................20

Scheduled backups......................................................................... 20Manual backups.............................................................................. 20Deduplication backups and restores with EMC Data Domain............ 20Client Direct backups to an AFTD...................................................... 21Backup configuration wizard............................................................ 22Simplified scheduled backup configuration of multiple databases...22

NMSAP features specific to SAP HANA........................................................... 22SAP HANA backups of redo logs....................................................... 23SAP HANA scale-out environments................................................... 24Internationalization with NMSAP HANA............................................ 24

NMSAP features specific to SAP Oracle..........................................................24Restores of Fujitsu NetWorker Module for SAP R/3 backups............. 25Deduplication backups and restores with EMC Avamar.................... 25Probe-based (event-based) backups................................................ 25Snapshot-based backups and restores............................................ 25Restartable backups........................................................................ 26Cluster and Oracle RAC support........................................................26Directory backups and restores........................................................ 26Oracle ASM and Exadata support..................................................... 27Configuration conversion................................................................. 28Internationalization with NMSAP Oracle........................................... 28Secure storage password and role-based secure storage................. 29Virtualization support...................................................................... 30

NMSAP and associated software................................................................... 31NetWorker software..........................................................................31EMC Replication Manager software.................................................. 31SAP server software......................................................................... 31SAP HANA software.......................................................................... 32Oracle server software......................................................................32

NMSAP software components........................................................................32

Configuration for NMSAP HANA Operations 35

Configuration road map for SAP HANA operations......................................... 36Verifying the NMSAP software requirements.................................................. 36Configuring scheduled backups with the wizard............................................ 37Configuring scheduled backups without the wizard.......................................38

Figures

Tables

Preface

Chapter 1

Chapter 2

CONTENTS

EMC NetWorker Module for SAP 8.2 Administration Guide 3

Setting up the NMSAP parameter file and configuration file..............38Enabling the parameter file in SAP HANA Studio...............................47Configuring the scheduled backup resources without the wizard......48

Configuring manual backups.........................................................................50Configuring automatic backups of SAP HANA redo logs................................. 50Configuring Data Domain Boost backups.......................................................51

Requirements for DD Boost backups................................................ 51Best practices for DD Boost backups................................................52Configuring Client Direct with DD Boost backups..............................52Configuring storage node with DD Boost backups............................ 53

Configuring NMSAP backups to AFTD storage................................................ 54Configuring Client Direct backups to AFTD........................................ 54Configuring storage node backups to AFTD.......................................54

NMSAP HANA Operations 57

Performing scheduled backups of SAP HANA data.........................................58Testing scheduled backups..............................................................58Monitoring scheduled backups........................................................ 58Canceling scheduled backups..........................................................59

Performing manual backups and recovery with SAP HANA Studio.................. 59Performing manual backups with SAP HANA Studio..........................59Deleting backups with SAP HANA Studio.......................................... 60Performing restore and recovery with SAP HANA Studio....................61

Performing manual backups and recovery with the SAP HANA CLI..................63Performing manual backups with the SAP HANA CLI......................... 64Canceling manual backups.............................................................. 64Checking NMSAP backups with the SAP HANA CLI............................ 65Performing recovery with the SAP HANA CLI......................................65

Preparing for SAP HANA disaster recovery......................................................66SAP HANA scale-out requirements.................................................................66

Configuration for NMSAP Oracle Operations 69

Configuration road map for NMSAP Oracle operations................................... 70Verifying the NMSAP software requirements.................................................. 70Configuring I18N support.............................................................................. 71

Requirements for I18N support........................................................ 71Configuring I18N support on UNIX.................................................... 72

Choosing either backint or RMAN as the backup and restore utility................72Specifying backint as the backup and restore utility.........................72Specifying RMAN as the backup and restore utility........................... 73

Configuring scheduled backups with the wizard............................................ 74Converting client-side configurations to wizard configurations...................... 75Configuring scheduled backups without the wizard.......................................76

Configuring the NMSAP parameters without the wizard.................... 76Configuring the scheduled backup resources without the wizard......97

Configuring manual backups.......................................................................100Configuring restartable backups..................................................................100

Configuring scheduled restartable backups with the wizard........... 101Configuring scheduled restartable backups without the wizard...... 101Configuring manual restartable backups........................................ 102

Configuring Avamar deduplication backups................................................ 102Requirements for Avamar deduplication backups...........................102Best practices for Avamar deduplication backups.......................... 102

Chapter 3

Chapter 4

CONTENTS


Configuring scheduled Avamar deduplication backups with the wizard...................................................................................................... 103Configuring scheduled Avamar deduplication backups without wizard...................................................................................................... 104Configuring manual Avamar deduplication backups.......................104Configuring deduplication backups with Avamar and Oracle RMAN...................................................................................................... 104

Configuring Data Domain Boost backups.....................................................105Requirements for DD Boost backups.............................................. 105Best practices for DD Boost backups..............................................106Configuring Client Direct with DD Boost backups............................106Configuring storage node with DD Boost backups.......................... 108

Configuring NMSAP backups to AFTD storage.............................................. 108Configuring Client Direct backups to AFTD...................................... 109Configuring storage node backups to AFTD.....................................109

Configuring probe-based backups...............................................................109Configuring a probe-based backup.................................................110User-defined probes...................................................................... 112Example probe-based backup with multiple probes....................... 112

Configuring backup email notifications....................................................... 113

NMSAP Oracle Operations 115

Performing scheduled backups of SAP Oracle data......................................116Testing scheduled backups............................................................116Monitoring scheduled backups...................................................... 116Canceling scheduled backups........................................................117Restarting failed scheduled backups..............................................117

Performing manual backups........................................................................118Running manual backups...............................................................118Monitoring manual backups...........................................................119Canceling manual backups............................................................ 119Restarting failed manual backups.................................................. 119

Reviewing backup and restore session reports............................................ 120Verifying backup information in the NetWorker indexes...............................120

Deletion and expiration of Avamar deduplication backups............. 122Cloning backups......................................................................................... 122

Using the sapclone command and options.....................................122Performing data restore and recovery.......................................................... 124

Restarting a restore for files that failed a restore............................ 126Requirements for disaster recovery............................................................. 127Recovering from a disaster.......................................................................... 127

Restoring the required Oracle and SAP BR*Tools files.....................128Recovering a SAP Oracle database after disaster............................129

SAP Oracle in Cluster and RAC Environments 131

SAP Oracle cluster systems......................................................................... 132Client parameter setting for cluster systems...................................132NSR_PHYSICAL_HOST_LICENSE setting for cluster systems.............132Configuring scheduled backups in a cluster with the wizard...........133Configuring scheduled backups in a cluster without the wizard......133Configuring manual backups in a cluster........................................134Configuring Avamar deduplication backups in a cluster................. 134Configuring Data Domain deduplication backups in a cluster......... 135Configuring probe-based backups in a cluster................................135

Chapter 5

Chapter 6

CONTENTS


Converting client-side configurations to wizard settings in a cluster...................................................................................................... 135Restoring data in a cluster..............................................................135

Oracle RAC systems.....................................................................................135Configuring Oracle RAC backups.................................................... 136Configuring backups with Backint.................................................. 136Configuring backups with RMAN.....................................................136Restoring Oracle RAC data..............................................................138

NMSAP Oracle Snapshot Backups and Restores 139

Snapshot operations with NetWorker Snapshot Management..................... 140Types of NSM backups................................................................................ 141

Snapshot backup (instant backup)................................................ 142Rollover-only backup (immediate live backup)............................... 142Snapshot and rollover backup (deferred live backup).....................142

Types of NSM restores.................................................................................143Snapshot restore (instant restore)..................................................143Restore from rollover (restore from conventional storage)...............143Rollback.........................................................................................143

Backup and restore data flows with NSM.....................................................143Configuring NMSAP snapshot backups with NSM........................................ 144

Configuring Snapshot Pool resources for NSM backups..................146Configuring Device resources for NSM backups..............................146Configuring Snapshot Policy resources for NSM backups............... 146Configuring Group resources for NSM backups...............................146Configuring Client resources for NSM backups............................... 147Configuring the NMSAP parameters for NSM operations................. 147Configuring the NSM parameters....................................................149

Testing NMSAP backups and restores with NSM.......................................... 151Example parameter settings for NSM backups.............................................152Reviewing the NMSAP NSM backup records.................................................153

NMSAP Oracle Split-Mirror Backups and Restores 155

Split-mirror backups and restores............................................................... 156Basic split-mirror backup and restore data flows......................................... 156

Manual split-mirror backup data flow.............................................157Scheduled split-mirror backup data flow........................................ 158Restore of split-mirror backup data flow......................................... 158

Configuring the production host for split-mirror backups............................. 158Configuring Oracle software on the production host....................... 158Configuring BR*Tools on the production host................................. 159Configuring NMSAP on the production host....................................159

Configuring the mount host for split-mirror backups....................................159Configuring Oracle software on the mount host.............................. 160Configuring BR*Tools on the mount host........................................ 160Configuring NMSAP on the mount host...........................................161

Configuring the snapshot software for split-mirror backups......................... 161Configuring the NetWorker server for split-mirror backups........................... 162Configuring a cluster environment for split-mirror backups..........................162Examples of parameters for split-mirror backups.........................................163

Parameter settings on the production host.....................................163Parameter settings on the mount host............................................164

Examples of RM scripts for split-mirror backups.......................................... 164sap_online_split script for RM on UNIX...........................................165

Chapter 7

Chapter 8

CONTENTS


erm_brbackup_online_split.sh script for RM on UNIX..................... 165sap_online_split.cmd script for RM on Windows............................ 165erm_online_split.cmd script for RM on Windows............................ 165

Examples of SAP Oracle Command Options 167

Examples of brbackup and brarchive command syntax and options............ 168Examples of brrestore command syntax and options...................................169Examples of brrecover command syntax and options.................................. 170

Troubleshooting and Error Messages 173

Verifying the release information.................................................................174Generating diagnostic logs..........................................................................174Setting the debugging options for RMAN operations....................................174Backup and restore problems......................................................................175NMSAP error messages............................................................................... 176

181

189

Appendix A

Appendix B

Glossary

Index

CONTENTS


CONTENTS


Software used in the NMSAP environment for NSM snapshot backups and restores.... 141NSM backup and restore data flow with NMSAP...........................................................144

12

FIGURES


FIGURES


Revision history............................................................................................................. 13NMSAP and associated software components............................................................... 32Supported hdbbackint parameters................................................................................ 39Supported nsrsapsv parameters.................................................................................... 45NetWorker Client resource attributes for NMSAP scheduled backups ............................ 48Configuring a Data Domain backup................................................................................53Supported backint parameters...................................................................................... 78Supported nsrsapsv parameters.................................................................................... 89Supported NSR_* parameters for RMAN.........................................................................95NetWorker Client resource attributes for NMSAP scheduled backups ............................ 98Configuring a Data Domain backup..............................................................................107NetWorker Probe resource attributes for NMSAP backups............................................ 110NetWorker Client resource attributes for probe-based NMSAP backups........................111The sapclone command options.................................................................................. 123Typical configuration for NMSAP snapshot operations with NSM..................................140Supported types of NSM backups................................................................................141Supported types of NSM restores.................................................................................143Group resource attributes for NSM backups.................................................................147NMSAP NSM parameters in parameter file initDBSID.utl...............................................147Common parameters in NSM configuration file, nmsapps.cfg...................................... 149Hosts required for split-mirror backups with RM and NMSAP........................................156Options for brbackup and brarchive commands...........................................................168Options for brrestore command................................................................................... 169Options for brrecover command...................................................................................170NMSAP backup or restore problems.............................................................................175NMSAP error messages................................................................................................176

1234567891011121314151617181920212223242526

TABLES


TABLES


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of itssoftware and hardware. Therefore, some functions described in this document might notbe supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properlyor does not function as described in this document.

Note

This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

PurposeThis document describes how to configure and use the EMC NetWorker Module for SAP(NMSAP) release 8.2.

AudienceThis document is intended for system administrators who are responsible for configuringNMSAP and maintaining backup and recovery systems.

Users of this guide must be familiar with the following topics:

l SAP terminology and concepts, especially those related to SAP HANA and Oracledatabase backup and recovery

l Backup and recovery procedures

l Disaster recovery procedures

Revision historyThe following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

03 November 26, 2014 Updated the following information:

l NSR_SNAP_TYPE on page 150 - Deleted theparameter value, emcrp for RecoverPoint, from thevalid values list.

02 August 29, 2014 Updated the following information:

l NMSAP features specific to SAP HANA on page 22 -Updated the information about SAP HANA dataoperations that NMSAP supports.

l NSR_SAVESET_NAME on page 42 - AddedNSR_SAVESET_NAME to the table of supportedhdbbackint parameters.

l Configuring Client Direct with DD Boost backups onpage 52 - Updated the information in step 3 about aClient Direct backup to a DD Boost device over FibreChannel.


https://support.emc.com/

https://support.emc.com/

Table 1 Revision history (continued)

Revision Date Description

l Configuring Client Direct with DD Boost backups onpage 106 - Updated the information in step 3 about aClient Direct backup to a DD Boost device over FibreChannel.

l Performing data restore and recovery on page 124 -Updated the information in step 2 about a restorefrom a DD Boost device over Fibre Channel.

l Configuring NMSAP snapshot backups with NSM onpage 144 - Updated the steps for configuring anNMSAP Oracle snapshot backup with NSM.

01 June 18, 2014 Initial release of NMSAP 8.2.

Related documentationYou can find additional EMC publications for this product release and related NetWorkerproducts at EMC Online Support.

The EMC NetWorker Module for SAP Release 8.2 Release Notes provides details aboutsupported environments and platforms.

Conventions used in this documentEMC uses the following conventions for special notices:

NOTICE

Addresses practices not related to personal injury.

Note

Presents information that is important, but not hazard-related.

Typographical conventionsEMC uses the following type style conventions in this document:

Bold Used for names of interface elements, such as names of windows,dialog boxes, buttons, fields, tab names, key names, and menu paths(what the user specifically selects or clicks)

Italic Used for variables and full titles of publications referenced in text

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, prompts, and syntax

l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means "or"

Preface


{ } Braces enclose content that the user must specify, such as x or y or z

... Ellipses indicate nonessential information omitted from the example

Where to get helpEMC support, product, and licensing information can be obtained as follows.

Product informationFor documentation, release notes, software updates, or information about EMC products,go to EMC Online Support at https://support.emc.com.

Technical supportGo to EMC Online Support and click Service Center. You will see several options forcontacting EMC Technical Support. Note that to open a service request, you must have avalid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Online communitiesVisit EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith customers, partners, and certified professionals for all EMC products.

Your commentsYour suggestions will help to improve the accuracy, organization, and overall quality ofthe user publications. Send your opinions of this document to [email protected].

Preface


https://support.emc.com

https://community.emc.com

mailto:[email protected]

Preface


CHAPTER 1

Overview of NMSAP Features

This chapter includes the following topics:

l Road map for NMSAP operations...........................................................................18l Terminology used in this guide..............................................................................18l Importance of backups and the backup lifecycle................................................... 19l NMSAP features for all supported applications......................................................20l NMSAP features specific to SAP HANA................................................................... 22l NMSAP features specific to SAP Oracle..................................................................24l NMSAP and associated software........................................................................... 31l NMSAP software components................................................................................32

Overview of NMSAP Features 17

Road map for NMSAP operationsUse the following road map to configure the EMC® NetWorker® Module for SAP (NMSAP)software, and perform backups and restores with NMSAP on a SAP HANA host or SAPOracle host.

NOTICE

Before you click a cross-reference, check the page number of your current topic in theguide in case you need to return to the same location from the cross-referenced topic.

1. Review the EMC NetWorker Module for SAP Release Notes for the most up-to-dateinformation about NMSAP.

2. Ensure that you have installed or updated NMSAP according to the instructions in theEMC NetWorker Module for SAP Installation Guide.

3. Review the information in this chapter about the major features of NMSAP.

4. Configure and perform operations in a SAP HANA environment:

l Configure backups according to information in Configuration for NMSAP HANAOperations on page 35.

l Perform backups and restores according to information in NMSAP HANAOperations on page 57.

5. Configure and perform operations in a SAP Oracle environment:

l In a stand-alone SAP Oracle environment:

n Configure regular (nonsnapshot) backups according to information in Configuration for NMSAP Oracle Operations on page 69.

n Perform regular backups and recovery according to information in NMSAPOracle Operations on page 115.

l For SAP Oracle in a cluster or RAC environment, configure and perform backup andrecovery according to information in SAP Oracle in Cluster and RACEnvironments on page 131.

l Configure and perform NMSAP Oracle snapshot backups according to informationin NMSAP Oracle Snapshot Backups and Restores on page 139.

l Configure and perform NMSAP Oracle split-mirror backups according toinformation in NMSAP Oracle Split-Mirror Backups and Restores on page 155.

6. Use the following information to troubleshoot any issues with NMSAP operations:

l Troubleshooting and Error Messages on page 173

l EMC NetWorker Module for SAP Release Notes

Terminology used in this guideThe term "SAP Oracle" used throughout this document refers to a SAP environment withan Oracle database.

The generic sections of this guide use the term “transaction logs” for the logs required torecover data backed up by NMSAP. The different applications that NMSAP supports useapplication-specific terms for the logs, such as archived logs, redo logs, and so on.



In this guide, the UNIX references apply to both UNIX and Linux operating systems, unlessspecified otherwise. The Windows references apply to all the supported MicrosoftWindows operating systems, unless specified otherwise.

Unlike the NetWorker software that uses the term recover for all backup retrievalactivities, NMSAP distinguishes between the restore and recovery of a database:

l Restore means to retrieve datafiles from a backup and store the files on a disk.l Recover means to apply the database transaction logs to update the database to a

specific point-in-time and to make the database consistent.

The glossary provides details about the terms used in this guide.

Importance of backups and the backup lifecycleFor the complete protection of a database system or application system, a viable backupstrategy must include regular backups of the following data:

l Database or application datal Transaction (or archived) logsl Configuration and control files for a database or application

These backups are important for the following reasons:

l Without backups, you cannot restore a database at all.l Without transaction logs, you can restore a database only to the time of its last

consistent backup.l Without the configuration files and control files, you cannot re-create the database

setup or application setup.

The NetWorker server maintains an online client file index and online media database,which together comprise the online indexes. During a backup with NMSAP, the NetWorkerserver makes an entry in the online client file index and records the location of the data inthe online media database. These entries provide recovery information required for allbacked-up data.

During a scheduled backup, the NetWorker server backs up the client index and otherserver configuration information (called the bootstrap), such as the resource database.The client index and bootstrap information is mandatory for performing disaster recoveryof the NetWorker server.

If you do not run scheduled backups with NMSAP, you must back up the bootstrapinformation manually to prepare for a NetWorker server disaster. The NetWorker disasterrecovery documentation describes how to back up the bootstrap information and how toprepare for NetWorker server disaster recovery.

The NetWorker server manages the backup lifecycle of NMSAP data through the browsepolicy and retention policy. You must specify these policies for each file and NetWorkersave set respectively before the backup time. You can specify the policies by setting theNetWorker Client resource browse and retention attributes or the NMSAP parametersNSR_SAVESET_BROWSE and NSR_SAVESET_RETENTION:

l The browse policy determines how long backed-up files are maintained in the clientfile index on the NetWorker server. Set the browse policy to be at least as long as theRecovery Point Objective (RPO).

l The retention policy determines how long save set entries are maintained in themedia database on the NetWorker server. Set the retention policy to be at least aslong as or longer than the browse policy.

When a backup file entry expires from the NetWorker client index, NMSAP is unable torestore the specified file. You can use the NetWorker scanner program to re-create the


Importance of backups and the backup lifecycle 19

missing entry if the volume of the NetWorker save set containing the save file is notrecycled. You cannot recover a backup after a save set's retention policy expires and thevolume that contains the save set is recycled.

The EMC NetWorker Administration Guide describes browse policies and retention policies.

NMSAP features for all supported applicationsNMSAP is an add-on module for the NetWorker server and client software that providesbackup and recovery services for SAP HANA and SAP Oracle data. NMSAP provides abackup and restore interface between the SAP backup and restore interfaces, theNetWorker server, and the NetWorker Management Console (NMC).

The following topics describe the common NMSAP features supported for both SAP HANAand SAP Oracle operations. NMSAP features specific to SAP HANA on page 22 and NMSAP features specific to SAP Oracle on page 24 describe the NMSAP featuressupported only for SAP HANA or SAP Oracle operations.

Scheduled backupsAn NMSAP backup can be a scheduled backup or a manual backup.

You can configure a scheduled backup to use a calendar time or to use probe settingsthat detect when the system meets specific conditions. The NetWorker server initiates thescheduled backup based on the backup configuration settings.

Note

NMSAP does not support probe-based (event-based) scheduled backups of SAP HANAdata.

A scheduled backup automatically backs up the NetWorker bootstrap record, which isessential for disaster recovery.

Manual backupsYou can initiate a manual backup at any time, on demand, by running the required SAPcommand on the NMSAP client host.

A manual backup does not back up the NetWorker bootstrap record, which you must backup separately. The NetWorker disaster recovery documentation provides details.

Deduplication backups and restores with EMC Data DomainNMSAP supports deduplication backups and restores with an EMC Data Domain®

system. You can configure the Data Domain system as NetWorker advanced file typedevices (AFTDs), virtual tape library (VTL) devices, or DD Boost devices.

A Data Domain deduplication backup to an AFTD, VTL, or DD Boost device can be amanual or scheduled backup, including a probe-based backup. NMSAP supportsbackups to DD Boost devices over IP or Fibre Channel (FC).

The first Data Domain backup backs up all the specified data and achieves the leastamount of data deduplication, referred to as compression or global compression in DataDomain documentation. Subsequent Data Domain backups achieve improveddeduplication rates as the backups identify more and more redundant data blocks.

Do not use NMSAP encryption or compression for backups to a Data Domain system. Theencryption or compression decreases the data deduplication ratio.



Backups to VTL or AFTD devices on Data DomainAn NMSAP backup to a Data Domain system configured as a NetWorker VTL or NetWorkerAFTD device sends all the data to the Data Domain system where the deduplicationoccurs. During a restore, the Data Domain system converts the stored data to its originalnondeduplicated format before sending the data over the network.

Backups to DD Boost devicesAn NMSAP backup to a Data Domain system configured as a DD Boost device can takeadvantage of the DD Boost feature, which consists of two components:

l The DD Boost library API enables the NetWorker software to communicate with theData Domain system.

l The distributed segment processing (DSP) component reviews the data that is alreadystored on the Data Domain system and sends only unique data for storage.

DSP enables deduplication of the backup data on the NetWorker storage node or theNMSAP client directly. Deduplication on the NetWorker storage node can be used whenthe NMSAP client does not have direct access to the Data Domain system or when DDBoost does not support the NMSAP client’s operating system. With deduplication on thestorage node, all the data is sent from the NMSAP client to the storage node and only theunique blocks are sent from the storage node to the target device.

To reduce the amount of transferred data, NMSAP can use the DD Boost components todeduplicate the data locally and send only the unique blocks directly to the target devicethrough direct file access (DFA) technology (Client Direct feature). A Client Direct backupuses the storage node only to coordinate the backup and manage the device.

By default, NMSAP tries to perform a Client Direct backup. If the NMSAP client does nothave direct access to the DD Boost device on the Data Domain system, then the backupis automatically routed through the storage node.

During a restore, if the NMSAP client has direct access to the DD Boost device, then theclient restores data directly from the device, regardless of whether the backup was donedirectly from the NMSAP client or through the storage node. If the NMSAP client cannotaccess the data directly, then the restore process uses the traditional method with thestorage node. Regardless of the restore method used, the Data Domain system convertsthe stored data to its original nondeduplicated state before sending the data over thenetwork.

Client Direct backups to an AFTDTraditionally, an NMSAP backup to an AFTD on either a Data Domain system or anothertype of system includes the following steps:

1. The NMSAP client sends all the backup data to the storage node.

2. The storage node sends the data to the attached AFTD device.

The Client Direct feature enables the NMSAP client to bypass the storage node and writethe data directly to the AFTD by using DFA, which can improve the backup performance. AClient Direct backup uses the storage node only to coordinate the backup and managethe device. If an NMSAP backup cannot use the Client Direct method due to thepermissions or accessibility to the AFTD, the backup uses the storage node instead.

The EMC NetWorker Module for SAP Release Notes describes the software requirements ofan NMSAP Client Direct backup to an AFTD.


Client Direct backups to an AFTD 21

Backup configuration wizardNMSAP supports the backup configuration wizard, which is a Java application that yourun from NMC to configure a scheduled backup. If the configuration wizard supports yourenvironment, use the wizard when possible to create a backup configuration.

The wizard provides the option of a typical or custom configuration, depending on theamount of detail needed for a specific backup configuration. The typical workflowenables you to configure a backup with fewer clicks by using default backup settings.

A scheduled backup configuration created with the wizard is not saved as client-sideparameters and configuration files, but as attributes in the Client resource on theNetWorker server. The wizard can use the NMSAP parameters and configuration files usedwith earlier NMSAP releases as input templates to generate a new wizard configuration.

You can optionally save the backup settings created with the wizard to an NMSAPparameter file (initDBSID.utl) and configuration file (nsrsapsv.cfg) on theNMSAP client host. You can use these files for diagnostic or reference purposes.

You must configure some NetWorker resources and settings outside of the wizard withthe NMC program, for example:

l Device resources

l Media Pool resources

l NetWorker user privileges

The wizard does not support the configuration of the following types of NMSAP Oraclebackups:

l RMAN backups

l Split-mirror backups

l Probe-based (event-based) backups

Simplified scheduled backup configuration of multiple databasesNMSAP supports the scheduled backup of multiple databases on the same client host byusing a single NetWorker Client resource.

When you configure a scheduled backup without the wizard, you can specify multipledatabases in the Save Set attribute of a single Client resource. You do not need toconfigure a separate Client resource for each database.

When you use a single Client resource for multiple databases, you also use a singleNMSAP configuration file, nsrsapsv.cfg, and specify unique parameter settings foreach database. You can still use multiple initDBSID.utl files for the backup.

The Parallelism attribute in the NetWorker Client resource or Group resource determineswhether NMSAP backs up the multiple databases simultaneously or sequentially. TheEMC NetWorker Administration Guide provides details about the NetWorker client andsavegrp parallelism.

NMSAP features specific to SAP HANAA SAP HANA database holds most of the data in memory but also uses persistent storageon disk. During normal database operations, the data is automatically saved frommemory to the disk at regular intervals. All the data changes are also captured in the redolog on disk, which is updated after each committed database transaction. The data ondisk must be backed up to ensure protection against a disk failure.



NMSAP is integrated with the SAP HANA BACKINT interface program, hdbbackint, toprovide the backup, deletion, inquiry, and recovery services for SAP HANA database dataand redo logs.

Based on the features that SAP HANA supports, NMSAP supports the following SAP HANAdata operations:

l Manual and scheduled backups

Note

You can configure scheduled backups with the backup configuration wizard.

l Online backups

l Full database backups

l Redo log backups

l Recovery of a database to the most recent state, a specific point-in-time, a specificdata backup, or a log position

l Recovery to the original host or an alternate host

Note

NMSAP supports a redirected recovery of a SAP HANA data backup to an alternatehost only when the same SAP HANA system ID (SID) is used.

l Deduplication backups to and restores from a Data Domain system configured as aNetWorker virtual tape library (VTL), advanced file type device (AFTD), or DD Boostdevice

l Client Direct backups to an AFTD or DD Boost device

Note

For SAP HANA operations, NMSAP does not support probe-based (event-based) backups,integration with Avamar, or restartable backups.

NMSAP works with the following SAP HANA interfaces on the database server to performbackup and restore operations:

l SAP HANA command line interface (CLI) with the hdbsql command

l SAP HANA Studio GUI

l SAP DBA Cockpit in The Computing Center Management System (CCMS) GUI

The following topics describe the NMSAP features supported only for SAP HANA backupand restore operations.

SAP HANA backups of redo logsThe SAP HANA database server automatically performs periodic backups of the redo logsfor a database. You do not run the log backups with any backup commands as is the casefor database backups.

You can use the SAP HANA Studio to configure the frequency of automatic log backupsand whether the BACKINT interface is used for the log backups.


SAP HANA backups of redo logs 23

SAP HANA scale-out environmentsSAP HANA software supports high availability on a SAP HANA scale-out appliance thatcontains multiple nodes.

NMSAP supports backups and restores in a SAP HANA scale-out multinode environment.You must meet specific requirements in the SAP HANA scale-out environment asdescribed in SAP HANA scale-out requirements on page 66.

Internationalization with NMSAP HANASAP HANA only supports UNICODE for internationalization. NMSAP HANA supportsUNICODE for backups and restores. For example, the backup prefix in the NMSAP backupcommand can include Japanese characters.

Note

I18N support is distinguished from localization (L10N) support, in which the softwareuser interface and operational messages are translated into localized languages. ThisNMSAP release does not provide L10N support.

NMSAP features specific to SAP OracleNMSAP interacts with SAP BR*Tools to provide backup and recovery services for Oracledatabase data and logs and other SAP files. NMSAP is integrated with the SAP OracleBACKINT interface program, backint, and also with the BR*Tools Oracle RecoveryManager (RMAN) interface.

NMSAP supports the following SAP Oracle data operations and environments:

l Manual and scheduled backups, including probe-based scheduled backups

l Online and offline backups

l Database, tablespace, and data file backups

l Redo log backups

l Restartable backups

l Recovery to the most recent state or a specific point-in-time

l Recovery to the original host or an alternate host or location

l Restores of Fujitsu NetWorker Module for SAP R/3

l Deduplication backups and restores with an Avamar server or Data Domain system

l Client Direct backups to an AFTD

l Cluster and Oracle RAC environments

l Directory backups and restores

l Snapshot backups and restores

l Split-mirror backups and restores

l Oracle ASM and Exadata

l Configuration with the backup configuration wizard

l Configuration conversion

l Internationalization



l Virtualization

The following topics describe the NMSAP features supported only for NMSAP Oraclebackup and restore operations.

Restores of Fujitsu NetWorker Module for SAP R/3 backupsNMSAP can restore backups performed with Fujitsu NetWorker Module for SAP R/3version 3.0 on an operating system that this NMSAP release supports. The EMC NetWorkerModule for SAP Release 8.2 Release Notes provides details.

If the backup with Fujitsu NetWorker Module for SAP R/3 used advanced backupcompression with GZIP or BZIP2, NMSAP automatically uncompresses the backup duringthe restore.

If you convert from using Fujitsu NetWorker Module for SAP R/3 to using NMSAP, youmust configure backups of SAP Oracle data according to the NMSAP documentation. Forexample, NMSAP operations ignore the following options if they are set:

l Fujitsu-specific compression options GZIP and BZIP2

l Other Fujitsu-specific parameters, such as files_per_save and device_server

Deduplication backups and restores with EMC AvamarA deduplication backup with an Avamar server is an optional feature that deduplicatesbackup data before sending the data to the Avamar server. After an initial backup to asupported Avamar server configured as a deduplication node, backups include onlyunique blocks of data that contain changes.

During a restore, the Avamar server converts the stored data to its originalnondeduplicated format before sending the data over the network.

Deduplication supports manual, scheduled, snapshot, and probe-based backups.

Deduplication does not support the following features:

l Backup of raw devices or volumes

l Use of data compression, checksum, or NSR_AES_ENCRYPTION parameters

Probe-based (event-based) backupsYou can configure NMSAP probe-based (event-based) scheduled backups to be triggeredwhen the system meets specific conditions within a scheduled backup window. You canspecify the conditions by the number of transaction (archived) logs generated, or by thetime elapsed since the previous probe-based backup. NMSAP also supports user-definedprobes.

Snapshot-based backups and restoresSnapshot technology provides enhanced protection and improved availability of data andgreatly reduces the use of resources on the production host to perform backups.

Snapshot backups of Oracle data with NMSAP create point-in-time (PIT) copies ofproduction data on primary storage devices, such as EMC VMAX® (EMC Symmetrix®) orEMC VNX® Block (EMC CLARiiON®).

Snapshot backups can mount the snapshots onto a mount host, and back up thesnapshots to conventional storage, such as a Data Domain device or tape, by usingNMSAP.

NMSAP supports two types of snapshot-based backups and restores:


Restores of Fujitsu NetWorker Module for SAP R/3 backups 25

l Snapshot backups and restores using the EMC NetWorker Snapshot Management(NSM) feature. If you use the NSM feature, you can restore from either a snapshot orconventional storage. NMSAP Oracle Snapshot Backups and Restores on page 139provides details.

l Split-mirror backups and restores using EMC Replication Manager or user-createdscripts working with any other software that supports the BR*Tools split-mirrorbackup interface. If you use the split-mirror feature, you can restore fromconventional storage only. NMSAP Oracle Split-Mirror Backups and Restores on page155 provides details.

Restartable backupsNMSAP supports restartable backups through the NetWorker checkpoint restart featureand SAP brbackup - fillup bkup_log option. This option enables you to restart anNMSAP client backup from a known good point called a checkpoint. During the restartedbackup, NMSAP does not back up files that were successfully backed up during the failedbackup.

For NMSAP restartable backups, the checkpoint granularity is at the save set level. Whenyou restart a backup, a successfully completed save set from the prior failed backup isnot backed up, but a failed save set is backed up.

Note

An NMSAP restarted backup does not generate partial save sets for a prior failed backup.

NMSAP restartable backups support both scheduled backups and manual backups.

Cluster and Oracle RAC supportNMSAP supports backups and restores of Oracle operating system cluster and OracleReal Application Cluster (RAC) systems.

Directory backups and restoresNMSAP supports backups and restores of nondatabase files and directories.

Note

The restore granularity of a directory backup performed with the brbackup command is

the entire directory. You cannot restore a subset of files from a directory backup.

NMSAP supports the following four directory backup modes, provided by the SAPBR*Tools suite:

l sap_dir—This mode backs up SAP-related directories, including the followingdirectories:

n /sapmnt/DBSIDn /usr/sap/DBSIDn /usr/sap/trans

l ora_dir—This mode backs up $ORACLE_HOME with the exception of the followingsubdirectories, if they exist:

n $ORACLE_HOME/sapdatann $ORACLE_HOME/origlog



n $ORACLE_HOME/mirrlogl all_dir—This mode combines the sap_dir and ora_dir modes.

l full_directory_path—This mode backs up the user-specified directory.

You can perform a directory backup as either a manual backup or a scheduled backupconfigured through the nonwizard method.

Note

NMSAP does not support a scheduled directory backup configured with the wizardmethod.

Back up nondatabase files and directories only after a SAP upgrade or Oracle upgrade.Directory backups with NMSAP are not a replacement for file system backups. To fullyprotect the file system environment, use the NetWorker file system interface.

Run backups of nondatabase files and directories separately from database backups.You must create a separate Client resource for the backup of nondatabase files anddirectories.

Oracle ASM and Exadata supportNMSAP supports Oracle Automatic Storage Management (ASM) and Oracle Exadatathrough the BR*Tools RMAN interface only.

NMSAP supports Oracle Exadata in both of the following configurations:

l Exadata Database Machine

l Exadata Storage Server, attached to an external database server

NMSAP supports the same environment for Oracle Exadata (including the Oracledatabase versions, operating system versions, BR*Tools versions, and NetWorkerversions) that NMSAP supports for Oracle RAC, as described in the compatibility matrix inthe EMC NetWorker Module for SAP Release 8.2 Release Notes.

You must install and configure NMSAP on each Exadata database server in the same waythat you install and configure NMSAP for Oracle RAC. The installation and configurationprocedures are described in the EMC NetWorker Module for SAP Installation Guide and inthis administration guide.

To perform backups and restores of Exadata, you must follow the instructions for OracleRAC environments in this administration guide.

If the Oracle Exadata database servers are connected to a NetWorker remote storagenode, then the following requirements apply to the connection:

l The only supported protocol is IP, over InfiniBand or other networks like Ethernet.Native InfiniBand or any protocol other than IP is not supported.

l There could be multiple network interfaces on the Oracle Exadata database servers tothe storage node, such as one for an InfiniBand connection and one for an Ethernetconnection. In such a case, you must configure the network settings and theNetWorker Client resource to send the backup data from the Oracle Exadata server tothe remote storage node over the preferred network, such as InfiniBand. Theconfiguration details are available in the NetWorker documentation.


Oracle ASM and Exadata support 27

Configuration conversionNMSAP supports the conversion of an NMSAP client-side configuration to a wizardconfiguration.

Converting client-side configurations to wizard configurations on page 75 describeshow to use the the nsrsapadm -W command to convert an NMSAP client-sideconfiguration to a wizard configuration.

Internationalization with NMSAP OracleNMSAP Oracle provides internationalization (I18N) support that enables you to monitor,back up, and restore non-ASCII data from NMSAP clients. For example, a NetWorkerserver with an ASCII locale can view and manage backups from an NMSAP client with aChinese locale. Also, a NetWorker server with a Chinese locale can view and managebackups from an NMSAP client with an ASCII locale.

Note

I18N support is distinguished from localization (L10N) support, in which the softwareuser interface and operational messages are translated into localized languages. ThisNMSAP release does not provide L10N support.

I18N support assumes the use of NMSAP with the following I18N products:

l Internationalized operating system

l Unicode version of BR*Tools

l NetWorker server and client that support I18N

Note

NMSAP support of non-ASCII environments is limited by the I18N support provided byOracle, BR*Tools, the NetWorker client, and the underlying operating system.

You must configure I18N support according to Configuring I18N support on page 71.

Support of non-ASCII charactersThe NMSAP client supports non-ASCII characters for the following items:

l Full pathnames of the parameter file and configuration file, for example,initDBSID.utl.

l Full pathnames of the operational log files, for example, SAPBACKUP and SAPTRACE.

l Full pathnames of variables set in the nsrsapsv.cfg file, for example, PATH,SAP_BIN, SAPTRACE, and SAPSWITCH.

l Most strings passed as command line options to the NMSAP programs nsrsapadm,nsrsapsv, sapclone, and backint. Exceptions are the Oracle username andpassword, which is an Oracle limitation, and the full pathname of the NMSAPscheduled backup configuration file (nsrsapsv.cfg), which is a NetWorker serverlimitation. ASCII-only characters on page 29 provides details.

l All NetWorker parameters that the NetWorker software supports.

l Environments configured by the scheduled backup wizard.



Note

The NLS_LANG=AMERICAN.AMERICA.US7ASCII parameter value is an example value ordefault value. This parameter setting occurs in the sample backup configuration file(nsrsapsv.cfg) shipped with the product or generated by the NMSAP wizard. You can

change this setting to another value. The SAP documentation describes how to set theNLS_LANG parameter.

ASCII-only charactersSome Oracle, BR*Tools, and NetWorker software configuration settings that are used withthe NMSAP client do not support I18N and must use ASCII characters. Read theappropriate product documentation for complete details. Examples include:

l Oracle requires ASCII characters for the following items:

n ORACLE_HOME environment variable

n Oracle database instance name DBSID

l BR*Tools requires ASCII characters for the following items:

n Connection strings (database username and password) to the SAP Oracledatabase

n Oracle datafiles, log files, control files, parameter file names

n Oracle tablespace names

n SAPARCH, SAPBACKUP, SAPCHECK, and SAPREORG variable settings in thensrsapsv.cfg file

l NetWorker software and NMSAP require ASCII characters for the following items:

n NetWorker client, server, pool, group, expiration policy, and email notificationparameters, which are set in the NMSAP parameter file (initDBSID.utl)

n NMSAP scheduled backup configuration file (nsrsapsv.cfg) pathname, whichis passed to the Backup Command attribute in the NetWorker Client resource

Secure storage password and role-based secure storageSAP Kernel 7.20 Patch Level 100 introduced a new method for the secure storage of theSAP database user or password to improve the security of database connections. WithBR*Tools Kernel 7.20 Patch 27 or later, you can avoid using the OPS$ database users bystoring the BR*Tools connection data for the database in a BR*Tools specific SecureStorage in File System (SSFS). The SAP Note 1764043 provides details about how toconfigure the storage of the BR*Tools user or password in secure storage.

Note

An NMSAP backup does not save the SSFS data. If the SSFS data becomes unavailable,you can restore the data by using other configured authentication methods, such asdatabase authentication or OS authentication, or you can rerun the procedure to securelystore the database user and password.

You can enable the secure storage password for NMSAP backups by settingNSR_BRTOOLS_SECURE_PASSWORD=TRUE in the nsrsapsv configuration file or in thewizard. This setting causes the BR*Tools binaries brbackup and brarchive to runwith the -u // option.

With BR*Tools Kernel 7.20 Patch 30 or later, you can also use role-based storage of theBR*Tools user and password in the secure storage, which assigns the DBA and OPER


Secure storage password and role-based secure storage 29

roles to OS users without the OS users having to belong to the Oracle OS groups dba andoper.

OS users configured for role-based storage must execute the DBA action only with theBR*Tools. Typically, OS users can call all the BR*Tools programs with the DBA role. OSusers with the OPER role can call only brarchive, brbackup, and brconnect. TheSAP Note 1764043 provides details about how to configure the role-based storage of theBR*Tools user and password in secure storage.

You can enable role-based secure storage for NMSAP backups by settingNSR_BRTOOLS_SECURE_ROLE=OS_group_name in the nsrsapsv configuration file or inthe wizard, where OS_group_name is the name of the OS group configured for securestorage. This setting causes the BR*Tools binaries brbackup and brarchive to runwith the -u //OS_group_name option.

Note

If you enable both the secure storage password and role-based secure storage for NMSAPbackups, then the secure storage password setting takes precedence.

Do not specify database authentication with the nsrsapadm command if you have set

the NSR_BRTOOLS_SECURE_PASSWORD or NSR_BRTOOLS_SECURE_ROLE parameter.Database credentials are ignored if either of these parameters is set.

You can use different authentication methods during backups and restores, provided thatall the authentication methods are configured according to the SAP and Oracledocumentation. For example, you can back up by using the secure role method and thenrestore by using database authentication.

Virtualization supportNMSAP supports several types of virtualization software, such as VMware, Solaris zones,Microsoft Hyper-V, and so on. The EMC NetWorker Module for SAP Release 8.2 ReleaseNotes provides details about supported environments and platforms.

Note

You must install NMSAP in a guest operating system.

VMware supportNMSAP supports regular backups and restores of SAP Oracle databases on a VMwarevirtual machine (VM) on an ESX server.

NMSAP also supports the following advanced features of a VMware ESX server:l VMotion—The VMotion feature enables migration of virtual machines from one ESX

server to another while the servers are on. The migration is seamless to theapplications that run on the virtual machines so users do not experiencedisconnections. The backup or restore remains uninterrupted if a migration occursduring an NMSAP backup or restore. VMware documentation describes the virtualmachine requirements for VMotion.

l Distributed Resource Scheduler (DRS)—The DRS feature enables dynamic balancingand allocation of resources across multiple ESX servers. Depending on the DRSpolicies set by the user, the DRS can migrate a virtual machine or recommend thatusers migrate a virtual machine to a different ESX server by using VMotion. DRS canalso start (at boot-up) a virtual machine on a different ESX server. If a migrationoccurs during an NMSAP backup or restore, the backup or restore remainsuninterrupted because this feature uses VMotion.



l High Availability (HA)—The HA feature enables the restart of VMware on the same ESXserver, on a different ESX server, or on a physical machine, depending on the type ofVMware cluster configured. During a restart, users are disconnected and mustreconnect.If a restart occurs during an NMSAP backup or restore, the backup or restore fails.

n You must manually restart a manual backup or restore when the guest operatingsystem restarts.

n For a scheduled backup, the NetWorker server retries the backup if the ClientRetries attribute in the Group resource is set to a nonzero value.

Solaris zones supportNMSAP supports Solaris global zones, whole root zones, and sparse root zones. The EMCNetWorker Module for SAP Installation Guide provides installation details for sparse rootzone environments.

NMSAP and associated softwareNMSAP works with different types of software in an NMSAP environment: NetWorker, EMCReplication Manager, SAP server, SAP HANA database system, Oracle server.

NetWorker softwareThe NetWorker software provides services to protect an enterprise against data loss. Thebasic NetWorker products include the NetWorker server, client, storage node, and theNetWorker Management Console (NMC).

NetWorker client release 8.1 or later includes the NetWorker Snapshot Management(NSM) feature that integrates and replaces the previous stand-alone EMC NetWorkerPowerSnap™ Modules. NMSAP can use NSM to create a snapshot (point-in-time) copy ofSAP Oracle data on a client host, which serves as a snapshot backup. NMSAP can thenback up the snapshot to conventional storage.

Note

After an upgrade to NetWorker client release 8.1 or later, you can use NMSAP with NSM torecover NMSAP backups of Oracle data performed with a PowerSnap Module.

NMSAP does not support snapshot operations with a SAP HANA database system.

EMC Replication Manager softwareNMSAP can work with EMC Replication Manager (RM) to provide support for BR*Toolssplit-mirror backups. RM creates a replica of production data stored on an EMC storagearray, such as VMAX or VNX Block, which NMSAP can back up to conventional storage.

SAP server softwareThe SAP server software includes the BR*Tools utilities used by NMSAP for the backup,restore, and inquiry of SAP Oracle databases. BR*Tools consist of brbackup,brarchive, brrecover, brrestore, and other utilities.


NMSAP and associated software 31

SAP HANA softwareThe SAP HANA database server software includes the SAP HANA utilities used by NMSAPfor the backup and restore of SAP HANA databases. The SAP HANA utilities include theSAP HANA CLI with the hdbsql command used to run backups. SAP GUIs, such as SAPHANA Studio, are also used for backups and restores.

Oracle server softwareThe Oracle software includes the RMAN utilities for backup, restore, and inquiryoperations. The use of RMAN with NMSAP and BR*Tools software is optional because youcan use the NMSAP backint program as the sole backup and restore software.

If you configure RMAN to back up SAP Oracle databases, the backint program willadditionally back up the SAP configuration files, logs, and other files that RMAN does notback up. Choosing either backint or RMAN as the backup and restore utility on page 72provides details.

NMSAP software componentsThe following table lists the NMSAP software components referenced in this guide. OnMicrosoft Windows systems, most of these files are in the directoryNetWorker_install_directory\nsr\bin.

Table 2 NMSAP and associated software components

Component Description

backint[.exe] NMSAP program interface to SAP BR*Tools, which providesbackup, restore, and inquire functionality.

hdbbackint NMSAP program for SAP HANA operations, which providesbackup and restore functionality.

init_hana_nmsap.utl Configuration file template that specifies the variables usedby the hdbbackint program for manual backups and

restores of SAP HANA data, and for scheduled backups thatare not configured through the wizard.Copy this template file and name it initDBSID.utl, where

DBSID is the name of the SAP HANA database instance to bebacked up.

init_oracle_nmsap.utl Configuration file template that specifies the variables usedby the backint program for manual backups and restores

of SAP Oracle data, and for scheduled backups that are notconfigured through the wizard.Copy this template file and name it initDBSID.utl, where

DBSID is the name of the SAP Oracle database instance to bebacked up.

libnworasap.xx (UNIX)

orasbt.dll,

nsrsbtcnsap.exe (Windows)

RMAN media management utilities.

man pages (UNIX only) Reference for NMSAP commands.



Table 2 NMSAP and associated software components (continued)

Component Description

nsrhanarahanara.jarhanara_res.jar

NMSAP scheduled backup configuration wizard files, usedfor HANA backup configuration.

nsrsapadm[.exe] Binary or executable program that converts an old-styleconfiguration of a scheduled backup to a new-styleconfiguration, which you can modify with the wizard.You can also use this program to encrypt login information inthe nsrsapsv.cfg file for the user who performs a

scheduled backup.

nsrsapprobe[.exe] Program that probes for the number of generated archivedlogs as a condition that triggers a probe-based backup.

nsrsapra[.exe]

nsrsaprachild[.exe]

sapra.jarsapra_res.jar

NMSAP scheduled backup configuration wizard files, usedfor BR*Tools (Oracle) backup configuration.

nsrsapsv[.exe] Scheduled backup program that invokes the appropriateBR*Tools executables.

nsrsapsv.cfg Configuration file template for the nsrsapsv scheduled

backup program for backups that are not configured throughthe wizard.Copy this template file and save the original file with itsdefault settings. On UNIX, this file is in the /etc directory.

nwsldreg.xml SAP Solution Manager registration file.

sapclone[.exe] Save set cloning program that provides an interface to theNetWorker nsrclone program.


NMSAP software components 33



CHAPTER 2

Configuration for NMSAP HANA Operations


l Configuration road map for SAP HANA operations................................................. 36l Verifying the NMSAP software requirements.......................................................... 36l Configuring scheduled backups with the wizard.................................................... 37l Configuring scheduled backups without the wizard...............................................38l Configuring manual backups.................................................................................50l Configuring automatic backups of SAP HANA redo logs......................................... 50l Configuring Data Domain Boost backups...............................................................51l Configuring NMSAP backups to AFTD storage........................................................ 54

Configuration for NMSAP HANA Operations 35

Configuration road map for SAP HANA operationsYou must use the following instructions to configure the NMSAP software for the SAPHANA data operations:

Procedure

1. Verifying the NMSAP software requirements on page 36

2. Use the appropriate instructions to configure either scheduled or manual backups:

l Configuring scheduled backups with the wizard on page 37

l Configuring scheduled backups without the wizard on page 38

l Configuring manual backups on page 50

3. Configuring automatic backups of SAP HANA redo logs on page 50

4. Configuring Data Domain Boost backups on page 51 (only for backups to DD Boostdevices)

5. Configuring NMSAP backups to AFTD storage on page 54 (only for backups to AFTDdevices)

Verifying the NMSAP software requirementsYou must verify that the NMSAP software environment meets the basic requirements.

Procedure

1. You have correctly installed and configured the SAP HANA software before youconfigure the NMSAP environment.

The appropriate SAP documentation provides instructions.

2. You have installed and enabled the NetWorker client software and NMSAP on eachSAP HANA server that requires backup and recovery services.

The platform-specific NetWorker installation guide and the EMC NetWorker Module forSAP Installation Guide provide instructions.

3. You have granted the NetWorker server User Group resource privileges to the SAP userwho performs the SAP HANA operations. You can set the User Group resource withNMC or the nsradmin program. If you use restricted data zones, then you can alsogrant the required privileges by using the Users and Privileges fields of the RestrictedData Zone resource. The EMC NetWorker Administration Guide provides details.

The SAP user requires specific privileges:

l To run backups and restores requires only the following default privileges:

n Monitor NetWorker

n Back Up Local Data

n Recover Local Data

l To review backup information in NetWorker indexes, for example, with thensrinfo and mminfo commands requires the Operate NetWorker privilege.

l To configure a backup requires the Configure NetWorker privilege.

4. You have ensured NMSAP connectivity if you use a firewall. You must configure thecorresponding ports for the NetWorker server as required.



The EMC NetWorker Administration Guide provides details.

Configuring scheduled backups with the wizardYou can create or modify a scheduled backup configuration with the NMSAP wizard.

You must meet the following requirements before you use the configuration wizard:

l You have installed the required NetWorker releases on the NMC server, NetWorkerserver, and NMSAP client hosts as described in the EMC NetWorker Module for SAPRelease Notes.

l On the NetWorker server where the configuration exists, the NMC user that starts thewizard (the wizard user) has the Configure NetWorker privilege and all its prerequisiteprivileges.

l Communication between the NMC server, NetWorker server, and NMSAP client usesNetWorker nsrauth authentication. The NetWorker documentation provides therequirements for nsrauth authentication.

l You have configured the NMSAP software environment as described in Verifying theNMSAP software requirements on page 36.

l If a user store key will be used in the scheduled backup, then the root user hascreated the user store key with the SAP HANA hdbuserstore tool. The credentialsprovided in the user store key are those of a user that has SAP HANA backupprivileges, such as the SYSTEM user. The SAP HANA documentation provides detailsabout the hdbuserstore tool.

Procedure

1. In the NMC Enterprise view, select the NetWorker server name and double-click theNetWorker application to launch the application.

2. In the Configuration view under the NetWorker server name, select Clients:

l To create a NetWorker Client resource for NMSAP, right-click Clients and selectClient Backup Configuration > New.

l To modify a NetWorker Client resource previously created with the wizard forNMSAP, right-click the client name and select Client Backup Configuration >Modify.

3. On each wizard page that appears, specify the options and values required for thebackup configuration. Each wizard page includes an online help button that you canclick to access descriptions of the fields and options on the page.

You can click a link in the wizard steps panel to go directly to the page you want tomodify. The number of steps shown in the steps panel varies according to the chosenconfiguration type.

Note

NMSAP does not support SAP HANA operations with Avamar. You cannot select theAvamar deduplication option in the wizard for a SAP HANA backup configuration.

4. On the last wizard page named Review and Accept the Client Configuration, clickCreate or Modify to create or modify the configuration, and click Finish to exit thewizard.


Configuring scheduled backups with the wizard 37

Configuring scheduled backups without the wizardAs an alternative to the wizard configuration, you can create or modify a scheduledbackup configuration by performing the following tasks:

Procedure

1. Setting up the NMSAP parameter file and configuration file on page 38

2. Enabling the parameter file in SAP HANA Studio on page 47

3. Configuring the scheduled backup resources without the wizard on page 48

Results

The NMC interface provides NetWorker Group, Device, Media Pool, and other resourcesettings that are not available in the wizard.

If a user store key will be used in the scheduled backup, then the root user must createthe user store key with the SAP HANA hdbuserstore tool. The credentials provided inthe user store key must be those of a user that has SAP HANA backup privileges, such asthe SYSTEM user. The SAP HANA documentation provides details about thehdbuserstore tool. You must specify the user store key in the HANA_USR_KEYparameter in the nsrsapsv configuration file, described in the following topic.

Setting up the NMSAP parameter file and configuration fileFor all SAP HANA operations except scheduled backups configured with the wizard, youmust set the required parameters in the hdbbackint parameter file on the NMSAPclient as described in NMSAP hdbbackint parameters on page 38.

For scheduled backups configured without the wizard, you must also set the requiredparameters in the nsrsapsv configuration file on the NMSAP client as described in NMSAP nsrsapsv parameters on page 43.

Note

For scheduled backups configured with the wizard, you do not need to set anyparameters. The configuration wizard sets all the required parameters in the NetWorkerClient resource attributes.

NMSAP hdbbackint parametersThe parameters in the hdbbackint parameter file provide the client, server, pool,deduplication, parallelism, and other values to the NMSAP hdbbackint program.

Make a copy, such as initDBSID.utl, for your own use of the original parameter filetemplate, /etc/init_hana_nmsap.utl, installed with NMSAP. Then you cancustomize the parameters in the copied file for the SAP HANA operations.

Note

When you uninstall NMSAP, the system deletes the original template file and any settingsyou made in the file.

NOTICE

If you use this file for scheduled backups, you do not need to set the server parameter orthe group parameter in the file. However, if you do set the parameters, the parametersettings on the NetWorker server take precedence.



To set parameters in your copy of the hdbbackint parameter file, initDBSID.utl,use the following format and guidelines:

parameter=value

l To use parameters, you must uncomment and modify the parameters as required.

l Parameter names and values are case-sensitive.

l You must set all mandatory parameters.

l If you do not set an optional parameter, the default value of the parameter is used.

The following table describes the hdbbackint parameters that NMSAP supports.

Table 3 Supported hdbbackint parameters

Parameter Description Default and valid values

checksum Specifies whether to perform a cyclic redundancycheck (CRC) on the backup data.Optional for a backup.

Setting this parameter to TRUE excludes the use of thecompress and NSR_AES_ENCRYPTION parameters,which you must set to FALSE. If you set more than oneof these parameters to TRUE, the priority order is:compress, checksum, NSR_AES_ENCRYPTION.

l FALSE (default).

l TRUE.

client Specifies the NetWorker client hostname to use for theclient file index for the current backup or restore.Mandatory for a SAP HANA scale-out environment.Select one node to use for the client file index, such asthe master node.

l Local physical host (default).

l Valid NetWorker client hostname.

compress Specifies whether to compress the data during abackup before the data passes over the network or iswritten to the backup device. The compression canspeed up the backup process. Compression increasesCPU usage on the SAP server, but reduces the amountof data sent to the NetWorker storage node.Optional for a backup.

NMSAP supports only the default NetWorkerencryption algorithm. NMSAP does not support backupcompression with GZIP or BZIP2.

Setting this parameter to TRUE excludes the use of thechecksum and NSR_AES_ENCRYPTION parameters,which you must set to FALSE. If you set more than oneof these parameters to TRUE, the priority order is:compress, checksum, NSR_AES_ENCRYPTION.

l FALSE (default).

l TRUE.

debug_level Specifies the level of debug messages thathdbbackint writes to the debug log file.

Optional for a backup or restore.

l 0 (default, no debugging).

l 0 to 9.

NSR_AES_ENCRYPTION Specifies whether to encrypt backup data with 256-bitAES encryption.Optional for a backup.

l FALSE (default).

l TRUE.


Setting up the NMSAP parameter file and configuration file 39

Table 3 Supported hdbbackint parameters (continued)


Setting this parameter to TRUE excludes the use of thecompress and checksum parameters, which you mustset to FALSE. If you set more than one of theseparameters to TRUE, the priority order is: compress,checksum, NSR_AES_ENCRYPTION.

NOTICE

If the encryption phrase has changed between the timeof the backup and the time when the backup isrestored, NSR_ENCRYPTION_PHRASES must include theoriginal phrase to enable the recovery.

NSR_DATA_DOMAIN_INTERFACE

Specifies the network interface to use to send backupdata to the DD Boost device.Optional for a manual backup only.

Set this parameter if you have a Fibre Channel (FC)connection to the DD Boost device. You must set thisparameter together with NSR_DEVICE_INTERFACE=DATA_DOMAIN. If you do not setNSR_DEVICE_INTERFACE to DATA_DOMAIN, then thisparameter is ignored.

l IP (default) = Backup data is sentover an IP network to the DD Boostdevice.

l Any = Backup data is sent over eitheran IP or FC network to the DD Boostdevice, depending on the availabledevice.

l Fibre Channel = Backup data is sentover an FC network to the DD Boostdevice.

NSR_DEBUG_DIR Specifies the directory of the hdbbackint diagnostic

logs.Optional for a backup or restore.

l /nsr/applogs/ (default on Linux).

l Valid directory pathname.

NSR_DEVICE_INTERFACE

Note

This parameter is deprecated.It is supported in the currentNMSAP release, but will beunsupported in a futurerelease.

Specifies whether the backup is always stored on theData Domain device from the specified pool.Optional for a manual deduplication backup with theData Domain media type only. Set the parameter whenthe backup pool contains a mixture of Data Domaindevices and other types of devices. For example: AFTD,tape, and so on.

Do not set for a scheduled deduplication backup.Instead, set the Data Domain Backup attribute in theNetWorker Client resource when the pool has mixeddevices for a scheduled deduplication backup.

l Undefined (default) = Backup datamight be stored on any device fromthe pool selected by NetWorker.

l DATA_DOMAIN = Backup data isalways stored on the Data Domaindevice.

NSR_DIRECT_ACCESS Specifies the method used to perform a backup to aData Domain device or an AFTD.Optional for a manual backup.

If the target device is on a Data Domain system:

l Data is deduplicated on the NMSAP client whenthe Client Direct feature is enabled.

l Data is deduplicated on the storage node whenthe Client Direct feature is disabled.

l Default (default) = The backup tries touse the Client Direct feature to bypassthe storage node and write datadirectly to the target device. If thebackup cannot use this feature, thenthe backup uses the storage node.

l No = The backup does not try to usethe Client Direct feature. The backupuses the storage node only.

l Yes = The backup tries to use theClient Direct feature. If the backup





This parameter is ignored during scheduled backupswith NetWorker server release 8.0 or later and duringrestores.

For scheduled backups, you can enable the ClientDirect feature with the Client Direct setting in thewizard or the Client resource.

cannot use this feature, then thebackup fails.

Note

The Yes value is deprecated. The value issupported in the current NMSAP release,but will be unsupported in a futurerelease.

NSR_ENCRYPTION_PHRASES Specifies the original phrase to enable the recovery.You can specify multiple phrases to try for therecovery.Mandatory if the NSR_AES_ENCRYPTION phrase haschanged between the time of the backup and the timewhen the backup is restored.

l Encryption phrase from the DatazonePass Phrase attribute in theNetWorker Server resource (default).

l Encryption phrase used at the time ofthe backup.

NSR_GROUP Specifies the name of a NetWorker backup group touse for a manual backup.Optional for a manual backup. Do not set thisparameter for a scheduled backup.

This parameter can be used to enable the followingoperations:

l Test a backup manually on the client side beforestarting scheduled backups.

l Direct a manual backup to a NetWorker devicepool, based on the backup group criteria.

l Default (default).

l Valid name of a NetWorker backupgroup.

NSR_NWPATH Specifies the pathname of the directory that containsthe NetWorker binaries.Recommended for a backup or restore if the NetWorkersoftware is installed in a nondefault location.

l Platform-specific default location ofthe NetWorker client binaries(default).

l Valid pathname of the NetWorkersoftware directory.

NSR_RECOVER_POOL Specifies the name of the NetWorker volume pool touse for a restore. You can use this option to restoredata from a specified volume pool if there are multiplecopies (clones) of the backup in different volumepools.Optional for a restore.

l Pool determined by the NetWorkerserver (default).

l Valid name of a NetWorker volumepool that contains a cloned backup touse for a restore.

NSR_SAVESET_BROWSE Specifies the date when the entry for the backup isremoved from the NetWorker client index and theassociated backup files are no longer readily availablefor browsing.Optional for a backup.

l Browse policy specified in theNetWorker Client resource for theclient, as determined by theNetWorker server (default).

l Valid date in nsr_getdate(3)format.





Note

For a scheduled backup, this parameter overrides theBrowse Policy attribute setting in the NetWorker Clientresource.

NSR_SAVESET_NAME Specifies a customized save set name for a backup.Optional for a backup.

l SAPHANA:SID_data for a data backupand SAPHANA:SID_log for a logbackup (default).

If hdbbackint cannot detect the

backup type, then the default saveset name is SAPHANA:SID.

l Customized save set name in thefollowing format:SAPHANA:user-specified_string

NSR_SAVESET_RETENTION Specifies the date when the save set becomesrecyclable and the associated data on the volume canbe overwritten.Optional for a backup.

Note

For a scheduled backup, this parameter overrides theRetention Policy attribute setting in the NetWorkerClient resource.

l Retention policy specified in theNetWorker Client resource for theclient (default).

l Valid date in nsr_getdate(3)format.

parallelism Specifies the number of concurrent data streams tosend from the NetWorker server during a restore, foreach hdbbackint program that SAP HANA runs for

the restore.Optional for a restore.

Note

A SAP HANA backup always has a parallelism value of1 regardless of this parameter setting because thedatabase server always provides only one pipe foreach hdbbackint program that SAP HANA runs.

l 8 (default).

l Positive integer number.

pool Specifies the NetWorker Media Pool resource, definedon the NetWorker server, which receives backup datafrom the SAP HANA server.Optional for a manual backup. This parameter is usedfor a manual backup and is not recommended for ascheduled backup.

Note

If set for a scheduled backup, this parameter overridesthe NetWorker server setting.

l Most appropriate pool, selected bythe NetWorker server (default).

l Valid name of a NetWorker volumepool.





To use different pools for a database backup and logbackup:

1. Create two separate initDBSID.utl parameter

files, one for the database backup and one for thelog backup.

2. Set this pool parameter to a different NetWorkerMedia Pool resource in each of the two parameterfiles.

3. In the SAP HANA Studio GUI, on the

Configuration tab of the Backup editor:

a. Clear the checkbox beside Use the sameparameter file for data backup and logbackup.

b. Type the corresponding parameter file name in

the Backint Parameter File text box under

both Data Backup and Log Backup.

server Specifies the hostname of the NetWorker server thatNMSAP uses.Mandatory for a manual backup, restore, or inquireoperation.

Note

You do not need to set this parameter for a scheduledbackup, but if you set the parameter, the value mustmatch the server that started the backup or an erroroccurs.

l Local host (default).

l NetWorker server hostname.

NMSAP nsrsapsv parametersThe nsrsapsv parameters provide environmental and other values to the NMSAPscheduled backup program, nsrsapsv.

You can use these parameters to perform the following operations among others:

l Specify the locations of required files and programs, such as hdbsql.

l Specify the SAP HANA database instance to back up.

l Specify the credential information needed to log in to the database server andperform a scheduled backup.

You can set the parameters in the wizard or in the nsrsapsv configuration file fornonwizard configurations.

Make a copy, such as nsrsapsv.cfg, for your own use of the original configuration filetemplate, /etc/nsrsapsv.cfg, installed with NMSAP. Then you can customize theparameters in the copied file for scheduled backups.



Note

When you uninstall NMSAP, the system deletes the original template file and any settingsyou made in the file.

To set parameters in your copy of the nsrsapsv configuration file, use the followingformat and guidelines:

l Use this format for each parameter setting:

parameter_name = parameter_valuel If you back up multiple databases in a single backup configuration, specify the

parameter settings in the configuration file as follows:

n For parameter settings common to all the databases, specify the parametersettings outside of the braces.

n For parameter settings unique to specific databases on the SAP HANA client,group the parameter settings within braces.

The following example shows the correct positions of parameter settings in theconfiguration file:

# Global parameters common to all the databasesparameter1 = valueparameter2 = valueparameter3 = value

DBSID1 {# Parameter settings for DBSID1parameter4 = value1parameter5 = value}

DBSID2 {# Parameter settings for DBSID2parameter4 = value2}

where DBSID1 and DBSID2 are SAP HANA database instances that appear on separatelines in the Save Set attribute of the Client resource for the scheduled backup.

A global parameter appears outside of all the braces. A database-specific parameterappears within the braces after a particular database SID.

l The following precedence rules apply to the parameter settings:

n Global parameter settings apply to all the databases included in the backup.

n If a global parameter is set more than once, the last setting takes precedence overall the previous settings of the global parameter.

n Database-specific parameter settings within braces apply only to the particulardatabase instance and override the corresponding global parameter settings forthe backup of that specific database.

n If a parameter appears more than once within the same braces, the last settingtakes precedence over all the previous settings of the parameter within thebraces.

l To use parameters in a scheduled backup, uncomment and modify the parameters asrequired.


l Use full pathnames for parameters that specify a pathname or a file name.



l Specify the full pathname of the configuration file in the Backup Command attributeof the Client resource for the scheduled backup. Configuring the scheduled backupresources without the wizard on page 48 describes the Client resource attributes.

The following table describes the parameters in the nsrsapsv configuration file thatNMSAP supports.

Table 4 Supported nsrsapsv parameters

Configuration parameter Description Default and valid values

HANA_BACKUP_PREFIX Specifies a prefix to use for the backup name.Optional for a scheduled backup configured withoutthe wizard.

l Undefined (default).

l Valid prefix for the backup name. Forexample:MY_DATA_BACKUP

HANA_BIN Specifies the pathname of the location of the hdbsqlprogram file.Mandatory for a scheduled backup configured withoutthe wizard.

This location is added to the PATH environmentvariable so that the hdbsql program can be found.


l Valid full pathname of the hdbsqlprogram location. For example:/usr/sap/SID/HDBnn/exe/where nn is the database instancenumber

HANA_INSTANCE Specifies the instance number of the SAP HANAdatabase for a backup.Mandatory for a scheduled backup configured withoutthe wizard if the HANA_USR_KEY parameter is not set.


l Valid instance number between 00and 99.

HANA_SID Specifies the system ID (SID) of the SAP HANAdatabase.Mandatory for a scheduled backup configured withoutthe wizard.


l Valid SAP HANA SID.

HANA_USR_KEY Specifies a user store key, which securely stores theSAP HANA database username, password, andinstance number.Optional if the SAP HANA database user credentialsare specified with the HANA_USR_PASSWD setting.


l Valid user store key, created by theroot user with the SAP HANAhdbuserstore tool. The credentials

provided in the user store key mustbe those of a user that has SAP HANAbackup privileges, such as theSYSTEM user. The SAP HANAdocumentation provides detailsabout the hdbuserstore tool.

HANA_USR_PASSWD Specifies an encrypted value that contains theusername and password of the SAP HANA databaseuser.Optional if the SAP HANA database user credentialsare specified with the HANA_USR_KEY setting.


l Uneditable encrypted value set byrunning the nsrsapadm -P hana-z file_name command as the root

user, where file_name is the fullpathname of the nsrsapsvconfiguration file. Follow theinstructions from the nsrsapadmcommand to complete the encryption.



Table 4 Supported nsrsapsv parameters (continued)


PATH Specifies the pathname of the NetWorker client binaryfile and any other required search pathnames.Optional for a scheduled backup configured withoutthe wizard.

The specified value is appended to the PATHenvironment variable. To specify multiple searchpathnames, use one of the following two methods:

l PATH=d:\dir1;d:\dir2;d:\dir1\dir2\dir3

l PATH=d:\dir1PATH=d:\dir2PATH=d:\dir1\dir2\dir3


l Valid pathnames, separated bysemicolons.

POSTCMD Specifies a postprocessing script to run after ascheduled backup:

l The postprocessing script file might needpermissions that enable execution by the rootuser.

l The script must return a zero value when itsucceeds, and a nonzero value when it fails.

l The first line of the script must contain thefollowing interpreter directive:#!/bin/sh

Optional for a scheduled backup configured withoutthe wizard.

Note

If the scheduled backup fails, the postprocessingscript still runs.If the postprocessing script fails, an error messageappears but the scheduled backup succeeds.


l Valid full pathname of apostprocessing script file. Thepathname must not contain anyspaces.

l If the value is undefined or invalid, apostprocessing script does not runafter the scheduled backup.

PRECMD Specifies a preprocessing script to run before ascheduled backup:

l The preprocessing script file might needpermissions that enable execution by the rootuser.

l The script must return a zero value when itsucceeds, and a nonzero value when it fails. Thereturn of a nonzero value causes the scheduledbackup to fail.

l The first line of the script must contain thefollowing interpreter directive:#!/bin/sh

Optional for a scheduled backup configured withoutthe wizard.


l Valid full pathname of apreprocessing script file. Thepathname must not contain anyspaces.

l If the value is undefined or invalid, apreprocessing script does not runbefore the scheduled backup.





Note

If the preprocessing script fails, NMSAP does notperform a scheduled backup, an error messageappears, and any postprocessing script does not run.

Enabling the parameter file in SAP HANA StudioYou must specify the location of the hdbbackint parameter file in SAP HANA Studio. Onthe Configuration tab of the Backup editor, type the complete pathname of the parameterfile in the Backint Parameter File text box.

Note

The same configuration file is used for all the SAP HANA CLI and SAP HANA Studiooperations.

You can specify separate configuration files for the database backup and log backup.

You can also select Use the same parameter file data backup and log backup to use thesame configuration file for both types of backups.

The following figure shows a configuration example in SAP HANA Studio 1.0 SPS 5.


Enabling the parameter file in SAP HANA Studio 47

Configuring the scheduled backup resources without the wizardOn the NetWorker server, you can configure a NetWorker Client resource and otherscheduled backup resources in the NMC program, without using the wizard.

Procedure

1. In the NMC Enterprise view, select the NetWorker server name, and double-click theNetWorker application to launch it.

2. In the Configuration view under the NetWorker server name, select the appropriatebackup resources to configure, such as Groups, Schedules, Clients, and so on.For example:

l To create client, right-click Clients and select New.

l To modify an existing NMSAP client, double-click the client name to open itsProperties window.

On each of the properties tabs, specify the appropriate options and values for thebackup configuration.

3. Configure the NetWorker Group, Schedule, and other NMC resource settings forscheduled NMSAP backups. The EMC NetWorker Administration Guide and online helpprovide details about the NetWorker resources.

l Schedule resource—Create or select a Schedule resource to specify the days of theweek when the scheduled backup runs.

l Group resource—Create or select a Group resource to apply to a group ofNetWorker clients that will start to back up data at a scheduled time. Set Autostartto Enabled. You can apply a Group resource as an attribute to a NetWorker Clientresource and a NetWorker Media Pool resource.

l Device resources—Configure a NetWorker Device resource for each supportedstorage device used for backup and restore operations.

l Media Pool resources—Configure the volumes in each NetWorker Media Poolresource to receive specific types of backup data, such as tablespaces or archivedlogs. When configuring the Media Pool resources, leave the Save Sets attributeblank. The NMSAP program sets the Save Sets during each backup session.

l Client resource—Specify a NetWorker Client resource for each SAP HANA server(NMSAP client) that requires backup, restore, and inquiry services.

The following table describes the Client resource attributes that are applicable toNMSAP operations.

Results

Table 5 NetWorker Client resource attributes for NMSAP scheduled backups

Attribute NMC tab Description

Aliases Globals Specifies all known aliases for the NMSAP host.

BackupCommand

Apps &Modules

Specifies the name of the command to be used for an NMSAP scheduled backup, either:nsrsapsvwhich is configured by the wizard only and cannot be manually set

or

nsrsapsv -f file_pathname



Table 5 NetWorker Client resource attributes for NMSAP scheduled backups (continued)


which uses the settings of the NMSAP configuration file (nsrsapsv.cfg), where

file_pathname is the full pathname of the NMSAP configuration file created on the NMSAP clienthost as described in NMSAP nsrsapsv parameters on page 43. The pathname can contain onlyASCII characters and can be no longer than 64 characters.

Browse Policy General Specifies the length of time that the NetWorker server retains an entry for the backup in theonline client file index.

Checkpointenabled

General This attribute is ignored by SAP HANA operations.

Checkpointgranularity

General This attribute is ignored by SAP HANA operations.

Client Direct General When selected, enables the Client Direct feature for a scheduled backup to a DD Boost deviceor AFTD. If a Client Direct backup is not possible, the backup routes the data through thestorage node instead of sending the data directly from the client to the storage device.

(Avamar)DeduplicationBackup

Apps &Modules

This attribute is ignored by SAP HANA operations.

(Avamar)DeduplicationNode

Apps &Modules


Data DomainBackup

Apps &Modules

When optionally selected, ensures that the deduplication backup is always stored on a DDBoost device when the backup pool contains a mixture of DD Boost devices and other types ofdevices.

Data DomainInterface

Apps &Modules

Specifies the interface over which the backup will occur to a Data Domain device. This option isused only when you enable Data Domain Backup for the client. Select the appropriate settingfor the attribute:

l Fibre Channel—The backup will use a Fibre Channel (FC) interface.

l IP—The backup will use an IP interface.

l Any—The backup will use either an FC or IP interface, depending on the available DataDomain device.

Note

This attribute is only available with NetWorker server release 8.1 or later.To enable a restore from a Data Domain device over an FC interface, you must set this attributeto Fibre Channel.

Directive General Leave blank. NMSAP does not support global directives.

Group General Specifies the NetWorker Group resource to use for an NMSAP scheduled backup.

Name General Specifies the hostname of the SAP server host where the NMSAP software is installed.

Parallelism Globals Specifies the maximum number of concurrent backup and restore sessions to use for a backupoperation. You can use this Client resource attribute instead of the parallelism setting in theparameter file or the wizard configuration.

Pool Globals Specifies the pool to use for a backup. When selected, this attribute overrides the poolassociated with the backup group.


Configuring the scheduled backup resources without the wizard 49



Remote Access Globals Specifies the OS user and fully qualified hostname (IP) of a remote host, used to enablebackups in a SAP HANA scale-out environment and restores of the backups to that remotesystem:

l For a SAP HANA scale-out backup, specifies sap_user@hana_host for each host in thescale-out environment.

l For restore of a backup from this host to a different destination host, specifiessap_user@different_host.

Remote User,Password

Apps &Modules


Retention Policy General Specifies the minimum length of time that must elapse before backed-up data is eligible to beoverwritten on the backup media.

Save Set General Specifies the database to be backed up. Use the following format for the save set name:SAPHANA:DBSID

For a client-side scheduled backup that you configured without the wizard, you can optionallyspecify multiple database instances on separate lines:

SAPHANA:DBSID1

SAPHANA:DBSID2

where DBSID1 and DBSID2 are different database instances on the same SAP HANA client.

You can specify unique parameter settings for each database instance by grouping theparameter settings within braces in the nsrsapsv configuration file as described in NMSAP

nsrsapsv parameters on page 43.

Schedule General Specifies the NetWorker Schedule resource to use for an NMSAP scheduled backup.

Configuring manual backupsYou must complete the required steps to configure an NMSAP manual backup.

Procedure

1. Complete all the steps described in Verifying the NMSAP software requirements onpage 36.

2. Configure the hdbbackint parameter file, initDBSID.utl, with the settings forthe appropriate NetWorker server and the other backup parameters.

NMSAP hdbbackint parameters on page 38 provides details.

Configuring automatic backups of SAP HANA redo logsYou must complete the required steps in SAP HANA Studio to configure the automaticbackups of SAP HANA redo logs. On the Configuration tab of the Backup editor, completethe settings in the Log Backup Settings group box:

l Select Enable Automatic Log Backup.

l For Destination Type, select Backint.



l For Backup Interval, specify the log backup interval. Type the numeric value in thetext box, and select the unit of time, such as Minutes, from the menu.

The following figure shows a configuration example in SAP HANA Studio 1.0 SPS 5.

Configuring Data Domain Boost backupsThis topic provides specific information about using DD Boost with NMSAP. The EMCNetWorker and EMC Data Domain Deduplication Devices Integration Guide providesadditional information about the DD Boost configuration and initial setup.

You must follow the requirements, best practices, and configuration procedures in thistopic for a deduplication backup that uses only DD Boost devices. The content in thistopic does not apply to a deduplication backup that uses AFTD or VTL devices.

The NetWorker documentation describes how to configure a Data Domain backup to AFTDor VTL devices. Configuring NMSAP backups to AFTD storage on page 54 also describeshow to configure a Client Direct backup to AFTD devices.

Requirements for DD Boost backupsBefore you configure a Data Domain deduplication backup with a DD Boost device,ensure that the NetWorker client and server releases support the DD Boost device. TheEMC NetWorker Module for SAP Release Notes provides details.

NMSAP supports three types of configurations for Data Domain deduplication backups:

l Deduplication using Client Direct—This configuration eliminates the sending of dataover the network between the NMSAP client and the storage node. The deduplicateddata is sent directly from the NMSAP client to the DD Boost device.

l Deduplication on a remote storage node—This configuration decreases the amount ofnetwork traffic between the storage node and Data Domain system by sending onlythe unique blocks over the network. However, deduplication requires all the data tobe sent over the network between the NMSAP client and the storage node.


Configuring Data Domain Boost backups 51

l Deduplication on a local storage node (located on the NMSAP client)—Thisconfiguration has similar performance to deduplication using Client Direct. However,this configuration requires a storage node on the NMSAP client and additionalmemory resources.

Best practices for DD Boost backupsDeduplication backups and restores with a Data Domain system are recommended forlarge databases with high data change rates. A daily change rate of more than 5 percentis a high change rate.

During planning and configuration of a deduplication backup, keep in mind the followingbest practices that can improve the backup performance:

l Do not use NMSAP backup encryption because the encryption decreases the datadeduplication ratio.

l Do not use NMSAP backup compression because the compression decreases thedata deduplication ratio.

l Use Client Direct access to a Data Domain device for backups and restores toeliminate data transfer between the NMSAP client and NetWorker storage node.However, using this feature requires an additional 24 MB of memory per data streamon the NMSAP client and also increases the NMSAP CPU usage.

Data Domain and NetWorker documentation describes the requirements fordeduplication backups.

Configuring Client Direct with DD Boost backupsYou can configure a scheduled or manual backup to a DD Boost device that uses theClient Direct feature to deduplicate data on the NMSAP host and pass only unique datablocks directly to the device, bypassing the storage node.

Procedure

1. Review Best practices for DD Boost backups on page 52.

2. Configure the DD Boost device and enable the Data Domain system for NetWorkeroperations. The EMC NetWorker and EMC Data Domain Deduplication Devices IntegrationGuide provides details.

3. For a Client Direct backup to a DD Boost device over Fibre Channel, ensure that theSAP user has the correct device permissions as described in the following EMC article:

Fibre Channel Devices with Products using DD Boost in Linux Environment

(Document ID dd95007)

Use the document ID to search for the article on EMC Online Support.

Note

This step is not required for a backup through the storage node.

4. Associate the backup with a pool that contains the DD Boost device configured in step 2 on page 52:

l For a scheduled backup, associate the required media pool with the NMSAP Groupresource or Client resource by using the NMC program. The EMC NetWorkerAdministration Guide and NMC online help provide details about using the NMCprogram.

l For a manual backup, set the pool parameter to the required pool. Configuringmanual backups on page 50 provides details.



https://my.datadomain.com/download/kb/all/DDBoost-FC-Windows-Generic.html

5. Follow the configuration instructions in the following table, similar to the instructionsfor configuring a nondeduplication backup.

6. For a Client Direct backup, use the default configuration settings. The Client Directfeature is enabled by default.

With Client Direct enabled, NMSAP tries to perform a Client Direct backup. If a ClientDirect backup is not possible, NMSAP performs a backup through the storage node.

Note

If you upgrade from NetWorker server release 7.6.x to 8.0 or later, and you want todisable Client Direct for scheduled backups, you must clear the Client Direct checkboxin the wizard or disable the Client Direct attribute in the Client resource. WithNetWorker server 8.0 or later, the Client Direct setting in the Client resource or wizardfield takes precedence over the NSR_DIRECT_ACCESS setting in the initDBSID.utlparameter file.

Table 6 Configuring a Data Domain backup

Type of Data Domaindeduplication backup

Configuration instructions Additional instructions to use DD Boost over FibreChannel or if the pool contains Data Domain and othertypes of devices

Scheduled backup configuredwith the wizard

Configuring scheduled backupswith the wizard on page 37

On the Client Backup Options wizard page:

l Select the Data Domain backup.

l Select the proper Data Domain interface. Ensure that youselect the Fibre Channel setting if you want to use an FCinterface.

Scheduled backup configuredwithout the wizard

Configuring scheduled backupswithout the wizard on page 38

In the Client resource of the NMSAP client:

l Select the Data Domain Backup attribute.

l Select the proper setting of the Data Domain Interfaceattribute. Ensure that you select the Fibre Channel setting ifyou want to use an FC interface.

Manual backup Configuring manual backups onpage 50

In the initDBSID.utl parameter file:

l Set NSR_DEVICE_INTERFACE=DATA_DOMAIN. NSR_DEVICE_INTERFACE on page 40 provides details.

l Set NSR_DATA_DOMAIN_INTERFACE to the proper interfacevalue. Ensure that you set the Fibre Channel value if youwant to use an FC interface. NSR_DATA_DOMAIN_INTERFACE on page 40 providesdetails.

Configuring storage node with DD Boost backupsYou can configure a scheduled backup or manual backup to a DD Boost device, where thebackup does not try to use the Client Direct method but instead deduplicates data on astorage node.

Procedure

1. Follow step 1 to step 5 in Configuring Client Direct with DD Boost backups on page 52.


Configuring storage node with DD Boost backups 53

2. Ensure that the Client Direct feature is disabled by following the appropriateprocedure:

l For a manual backup, set NSR_DIRECT_ACCESS=No in the initDBSID.utlparameter file. NSR_DIRECT_ACCESS on page 40 provides details.

l For a scheduled backup, clear the Client Direct checkbox in the wizard or disablethe Client Direct attribute in the NetWorker Client resource.

Configuring NMSAP backups to AFTD storageYou can configure an NMSAP scheduled or manual backup to an AFTD as either a ClientDirect backup or a backup that sends data through a storage node.

Configuring Client Direct backups to AFTDYou must complete the required steps to configure a scheduled or manual backup thatuses Client Direct to an AFTD.

Procedure

1. Configure an AFTD by using either the Device Wizard or the NMC device propertieswindow.

The EMC NetWorker Administration Guide provides complete details about AFTDconfigurations, including considerations for Client Direct clients.

2. Ensure that the NMSAP client has the required access to the AFTD through CIFS. TheEMC NetWorker Administration Guide provides details.

3. Associate the backup with a pool that contains the AFTD configured in step 1 on page54.

4. Follow the appropriate configuration instructions:





With Client Direct enabled, NMSAP tries to perform a Client Direct backup. If a ClientDirect backup is not possible, NMSAP performs a traditional backup through thestorage node.

Configuring storage node backups to AFTDYou must complete the required steps to configure a scheduled or manual backup to anAFTD where the backup does not try to use the Client Direct method but instead sendsdata through a storage node.

Procedure

1. Follow step 1 to step 4 in Configuring Client Direct backups to AFTD on page 54.







Configuring storage node backups to AFTD 55



CHAPTER 3

NMSAP HANA Operations


l Performing scheduled backups of SAP HANA data................................................. 58l Performing manual backups and recovery with SAP HANA Studio.......................... 59l Performing manual backups and recovery with the SAP HANA CLI..........................63l Preparing for SAP HANA disaster recovery..............................................................66l SAP HANA scale-out requirements.........................................................................66

NMSAP HANA Operations 57

Performing scheduled backups of SAP HANA dataYou can use the following procedures to test, monitor, and cancel scheduled NMSAPbackups of SAP HANA data.

The EMC NetWorker Administration Guide provides information about restarting checkpointenabled backups.

Testing scheduled backupsYou can configure scheduled NMSAP backups to run automatically according to thebackup schedules. After you configure a scheduled backup, you can manually test thebackup.

Before you test a scheduled backup, ensure that you meet the following requirements:

l You have correctly set up the software environment. You have provided read andwrite access to a common parent directory for all the files associated with thebackup. Verifying the NMSAP software requirements on page 36 provides details.

l You have created the NetWorker Client resource with a correctly configured save setand backup command.

l You have assigned the Client resource to a backup group.

You can test a scheduled backup with the NetWorker Management Console (NMC).

Procedure

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.

Monitoring scheduled backupsThe NMC program provides a centralized view of all the backup and recovery activitythroughout an entire enterprise, the operations related to devices and libraries, and themanaged events that require user intervention.

You can monitor scheduled NMSAP backups with the NMC program.

Procedure

1. Run the NMC program.

2. Select the backup group in the monitor view.

The Details window displays details of backups that are running, successfullycompleted, or failed.

Note

For a deduplication backup, the NMC display shows the total size of the data beforededuplication, not the size of the deduplicated data. The display also does notindicate that the data is for a deduplication backup.



Canceling scheduled backupsYou cannot cancel a scheduled backup by clicking Stop on the ongoing save sets in theAll Sessions or Save Sessions window during the backup process.

The following results occur if you cancel a backup before completion:

l None of the backed-up data might be recoverable.

l The Volume Save Sets are not marked as incomplete in NMC.

You can cancel a scheduled backup in progress from the NMC program.

Procedure



3. Right-click the group to stop and select Stop.

To manually start a canceled backup process from the beginning, right-click the groupto start and select Start. Ensure that the backup successfully completes withoutinterruption.

Performing manual backups and recovery with SAP HANA StudioYou can run the SAP HANA Studio GUI to perform backups, backup deletions, restores,and recovery with NMSAP. The SAP HANA documentation provides details about the SAPHANA Studio procedures.

You can perform operations with SAP HANA Studio after you have completed theconfigurations in Configuration road map for SAP HANA operations on page 36.

NOTICE

The NetWorker server bootstrap and client indexes are not automatically backed up at theend of a manual backup, as they are for a scheduled backup. After running a manualbackup, perform a backup of the NetWorker server bootstrap and client indexes toprepare for disaster recovery of the NetWorker server by following the instructions in theEMC NetWorker Administration Guide.

Performing manual backups with SAP HANA StudioIn SAP HANA Studio, you must specify the database for backup and enable the backup touse the BACKINT interface.

For example, the Specify Backup Settings dialog box appears as follows.


Canceling scheduled backups 59

In the Specify Backup Settings dialog box, you must select Backint for the DestinationType and optionally type a prefix for the backup name in the Backup Prefix text box. If youspecify a prefix, then the backup name will include the prefix, prefix_databackup_#_#.

Deleting backups with SAP HANA StudioIn SAP HANA Studio, you must select the backup catalog option for the required SID andselect a database backup for deletion from the backup catalog list.

For example, the Specify Backup Deletion Settings dialog box appears as follows.



You can select the appropriate type of deletion:

l Select Catalog to delete the backup from the backup catalog only.

Note

This Catalog deletion will not modify any save sets or file information on theNetWorker server.

l Select Catalog and backup location to delete the backup from both the backupcatalog and the NetWorker server.

Performing restore and recovery with SAP HANA StudioIn SAP HANA Studio, you must select the recovery option for the required SID.

For example, the Specify Recovery Type dialog box appears as follows.


Performing restore and recovery with SAP HANA Studio 61

You must select the type of recovery:

l Select Recover the database to its most recent state to recover the database as closeas possible to the current time.

l Select Recover the database to the following point in time to recover the database toa specific point-in-time.

l Select Recover the database to a specific data backup to restore only the specifieddata backup.

l Click Advanced and select Recover the database to the following log position in anexceptional case only when a previous recovery has failed.

For example, the Select Data Backup dialog box appears as follows.



You must select the database backup for the restore or recovery.

You can optionally select to perform an inquire operation that checks the backupavailability by selecting the backup in the list and clicking Check Backup. The Availablecolumn displays a green or red icon, based on the physical availability of the backup.

The recovery progress is displayed for each service, including the name server, indexserver, and statistics server. A confirmation message appears when the backup iscomplete.

Performing manual backups and recovery with the SAP HANA CLIYou can run the SAP HANA CLI to perform manual NMSAP backups of SAP HANA data.

Starting with SAP HANA SPS 07, you can run the SAP HANA CLI to perform recovery ofNMSAP backups, and run specific maintenance commands to check the availability andintegrity of data and log backups.

The SAP HANA documentation provides details about the SAP HANA CLI procedures.

You can perform operations with the SAP HANA CLI after you have completed theconfigurations in Configuration road map for SAP HANA operations on page 36.


Performing manual backups and recovery with the SAP HANA CLI 63

NOTICE


Performing manual backups with the SAP HANA CLIYou can run the appropriate hdbsql command to perform a database backup. Forexample:

hdbsql -U user_key "backup data using backint (‘/usr/sap/SID/SYS/global/hdb/backint/prefix’)"

where:

l user_key is the user key created with the SAP HANA hdbuserstore tool. SAP HANAdocumentation provides details about the tool.

Note

The user key must be created by the same OS user that runs the hdbsql command.

l SID is the system ID of the SAP HANA system. /usr/sap/SID/SYS/global/hdb/backint/ is the backup pathname of the location where the SAP HANA databaseserver creates the pipes. This backup pathname is optional in the hdbsql command.

l prefix is an optional prefix for the backup name. If you specify prefix in the hdbsqlcommand, then the backup name will include the prefix, prefix_databackup_#_#.

Note

You must specify either the backup pathname or the prefix in the hdbsql command.

When you specify one of these items, the other item becomes optional in the command.

The SAP HANA documentation provides details about how to use the hdbsql commandfor backups.

Canceling manual backupsYou can cancel a manual backup by using the appropriate SQL command with the backupID of the running data backup.

Procedure

1. Determine the backup ID of the running data backup by using the monitoring viewM_BACKUP_CATALOG, which provides an overview of information about backup andrecovery activities.

Run the following SQL command to determine the backup ID:

select BACKUP_ID from "M_BACKUP_CATALOG" where entry_type_name = 'complete data backup' and state_name = 'running' order by sys_start_time desc;

2. Run the following SQL command to cancel the running data backup:

backup cancel backup_ID



Checking NMSAP backups with the SAP HANA CLIStarting with SAP HANA SPS 07, you can run the hdbbackupcheck andhdbbackupdiag commands to check the integrity and availability of NMSAP backups.

Using the hdbbackupcheck command to check backup integrityYou can run the hdbbackupcheck command to check the integrity of a data or logbackup. The command reads part of the backup, checks the metadata for correctnessand consistency, and checks the content for any changes.

The following example command checks the integrity of an NMSAP backup:

./hdbbackupcheck -v --backintParamFile /usr/sap/space/space_hana/init.ddp.utl /usr/sap/AAA/SYS/global/hdb/backint/foooo_databackup_0_1 -e 1396019304

In this command, the backup file name is the pipe name provided by SAP HANA duringthe backup. The pathname is the location where the pipes were created. The -e optionprovides the external backup ID of the backup file. You can find all these values in theM_BACKUP_CATALOG_FILES view.

The SAP Note 1869119 provides details about the hdbbackupcheck command.

Using the hdbbackupdiag command to check backup availabilityYou can run the hdbbackupdiag command to check the backup availability.

The following example command checks the availability of an NMSAP backup:

./hdbbackupdiag --check -i 1393886826664 --useBackintForCatalog--backintDataParamFile /nsr/res/initAAA.utl--backintLogParamFile /nsr/res/initAAA-logs.utl

Ensure that you use the --useBackintForCatalog option.

The SAP Note 1873247 provides more details about the hdbbackupdiag command.

Performing recovery with the SAP HANA CLIStarting with SAP HANA SPS 07, you can use an SQL command to perform a recovery ofan NMSAP backup.

Note

The SAP HANA Studio GUI is the recommended method to perform a restore and recovery.

You must be logged in to the SAP HANA system as the OS user sidadm to run the recoverySQL command. In a scale-out multinode environment, you must run the command fromthe master node.

The recovery command must first include the HDBSettings.sh and recoverSys.pyscripts in that order. The HDBSettings.sh script sets the environment for recovery. TherecoverSys.py script processes the recovery SQL command and performs thedatabase recovery.


Checking NMSAP backups with the SAP HANA CLI 65

The following example command performs a recovery of an NMSAP backup:

./HDBSettings.sh recoverSys.py --command="recover database until timestamp '2014-02-28 00:00:00' using data path ('/usr/sap/AAA/SYS/global/hdb/backint/') using log path ('/usr/sap/AAA/SYS/global/hdb/backint/') using BACKUP_ID 1593520382350" --wait

You must include the --wait option for proper completion of the recoverSys.pyscript.

The SPS 07 version of the SAP HANA Administration Guide provides details about the SQLcommand syntax of the recovery command.

Preparing for SAP HANA disaster recoveryFor a comprehensive disaster recovery plan, you must ensure that you can reconstruct thecomputing environment and all the SAP HANA server files associated with maintainingdata on the application host.

Use the following guidelines to prepare for a disaster recovery of the SAP HANA serverhost:

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

n Original operating system media and patches

n Device drivers and device names

n File system configuration

n IP addresses and hostnames

l To ensure the recovery of customer-specific settings of the database, ensure that youback up the SAP HANA configuration files by following the SAP HANA AdministrationGuide. These files are not backed up during database backups.

l Ensure that you have a current full backup of the database and all the redo logs asrequired for a recovery of the database to the current time.

Plan to perform the following tasks during a disaster recovery:

Procedure

1. Set up the SAP HANA database system to the same configuration as when the datawas backed up.

2. Set up the hdbbackint parameter file to be used during the recovery, including theclient parameter setting. The client parameter must be set to the hostname of the hostwhere the data was backed up. Setting up the NMSAP parameter file andconfiguration file on page 38 provides details.

3. Ensure that all the required database and log backup images are available.

4. Run SAP HANA Studio to recover the database and redo logs. Ensure that you selectthe Initialize Log Area option in the SAP HANA Studio database recovery wizard.

SAP HANA scale-out requirementsYou can perform SAP HANA backups in a SAP HANA scale-out multinode environment.

You must meet the following configuration requirements in a SAP HANA scale-outenvironment:



l You have set up the database in the scale-out environment according to theappropriate SAP HANA documentation.

l You have installed the NMSAP software on each node and configured the NMSAPsoftware according to the instructions in the preceding chapter.

l For each node in the system, you have configured a corresponding Client resource inthe NetWorker server.

l For a nonwizard configuration, you have set the client parameter in the hdbbackintparameter file as described in client on page 39. You have enabled the parameter fileas described in Enabling the parameter file in SAP HANA Studio on page 47. Ensurethat each node in the system can access this parameter file. For example, place theparameter file in a shared location.

l For a wizard configuration, you have set the client parameter in the Advanced Optionstable in the wizard.

l Specify the following values in the Remote Access attribute in the Client resource ofthe client where the backup is initiated:

host=node_xhost=node_y...

Specify the host values for all the nodes in the system except the node specified inthe client parameter.


SAP HANA scale-out requirements 67



CHAPTER 4

Configuration for NMSAP Oracle Operations


l Configuration road map for NMSAP Oracle operations........................................... 70l Verifying the NMSAP software requirements.......................................................... 70l Configuring I18N support...................................................................................... 71l Choosing either backint or RMAN as the backup and restore utility........................72l Configuring scheduled backups with the wizard.................................................... 74l Converting client-side configurations to wizard configurations.............................. 75l Configuring scheduled backups without the wizard...............................................76l Configuring manual backups...............................................................................100l Configuring restartable backups..........................................................................100l Configuring Avamar deduplication backups........................................................ 102l Configuring Data Domain Boost backups.............................................................105l Configuring NMSAP backups to AFTD storage...................................................... 108l Configuring probe-based backups.......................................................................109l Configuring backup email notifications............................................................... 113

Configuration for NMSAP Oracle Operations 69

Configuration road map for NMSAP Oracle operationsYou must use the following instructions to configure the NMSAP Oracle operations on asingle host, outside of a cluster or Oracle RAC system:

Procedure

1. Verifying the NMSAP software requirements on page 70

2. Configuring I18N support on page 71

3. Choosing either backint or RMAN as the backup and restore utility on page 72

4. Use the appropriate instructions to configure either scheduled or manual backups:


l Converting client-side configurations to wizard configurations on page 75



Configuring restartable backups on page 100 describes how to configure arestartable scheduled or manual backup.

Configuring probe-based backups on page 109 describes how to configure a probe-based scheduled backup.

5. Configuring Avamar deduplication backups on page 102 (only for backups to anAvamar server)

6. Configuring Data Domain Boost backups on page 105 (only for backups to DD Boostdevices)

7. Configuring NMSAP backups to AFTD storage on page 108 (only for backups to AFTDdevices)

8. Configuring backup email notifications on page 113 (only for setting up emailnotifications)

Verifying the NMSAP software requirementsYou must verify that the NMSAP software environment meets the basic requirements.

Procedure

1. You have correctly installed and configured the Oracle software and SAP softwarebefore you configure the NMSAP environment.

The appropriate Oracle and SAP documentation provides instructions.

Note

You can recover only datafiles for which you had read permission on the operatingsystem when you backed up the datafiles. Grant read access to the datafiles to a DBA operating system group. Granting the readaccess enables the restore of the data by a different user or to a different host.

2. You have installed and enabled the NetWorker client software and NMSAP on eachSAP Oracle server requiring backup and recovery services.

The platform-specific NetWorker installation guide and the EMC NetWorker Module forSAP Installation Guide provide instructions.



3. You have correctly linked the NMSAP RMAN management library/utility if you use theBR*Tools RMAN feature on UNIX.

The EMC NetWorker Module for SAP Installation Guide provides details.

4. The NMSAP backint executable is in the same directory as BR*Tools, or you have setutil_path=full path to directory containing backint in the BR*Tools initialization profileinitDBSID.sap with BR*Tools 7.10 or later.

You have set the owner of backint to root on UNIX.

5. You have set the uid bit for the backint program if you will restore to raw device fileson UNIX. You can set the uid bit for backint by typing the following command:

chmod 4755 backint

Note

In rare cases, you must set the uid bit to enable restores to file systems on UNIX.

6. You have granted the NetWorker server User Group resource privileges to the SAP userwho performs the NMSAP operations. You can set the User Group resource with NMCor the nsradmin program. If you use restricted data zones, then you can also grantthe required privileges by using the Users and Privileges fields of the Restricted DataZone resource. The EMC NetWorker Administration Guide provides details.

The SAP user requires specific privileges:

l To run backups and restores requires only the following default privileges:

n Monitor NetWorker

n Back Up Local Data

n Recover Local Data

l To review backup information in NetWorker indexes, for example, with thensrinfo and mminfo commands requires the Operate NetWorker privilege.

l To configure a backup or to convert a backup configuration with nsrsapadmrequires the Configure NetWorker privilege.

7. You have ensured NMSAP connectivity if you use a firewall. You must configure thecorresponding ports for the NetWorker server as required.


The EMC NetWorker Module for SAP Release 8.2 Release Notes describes thecompatibility of NMSAP with other products.

Configuring I18N supportInternationalization with NMSAP Oracle on page 28 describes the internationalization(I18N) features that NMSAP supports. You must meet the I18N requirements andcomplete any configuration steps to enable NMSAP I18N support.

Requirements for I18N supportNMSAP I18N support requires the following I18N products:

l Internationalized operating system

l Unicode version of BR*Tools


Configuring I18N support 71

l NetWorker server and client that support I18N

The NetWorker documentation describes the NetWorker I18N requirements.

Note

The I18N support provided by Oracle, BR*Tools, the NetWorker client, and the underlyingoperating system limits the NMSAP support of non-ASCII environments.

Internationalization with NMSAP Oracle on page 28 and the EMC NetWorker Module forSAP Release Notes provide more information.

Configuring I18N support on UNIXTo configure I18N support of the NMSAP client host on UNIX only:

Procedure

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 restoreutility

The SAP BR*Tools software coordinates all the backup, restore, and inquiry operations ofSAP Oracle data. You can configure the BR*Tools software to use either the NMSAPbackint program or the Oracle RMAN program with the NMSAP RMAN mediamanagement library to perform these operations. The following examples describe howyou can specify the program to use.

In addition to backing up Oracle data, the brbackup and brarchive programs backup the BR*Tools profiles, log files, and backup catalogs required for disaster recovery.NMSAP operations always use backint to back up and restore these files, regardless ofthe method selected for Oracle data backups and restores. Therefore, even if you useRMAN for an Oracle backup, you must configure the same backup for backintoperations to ensure that the backup succeeds.

Specifying backint as the backup and restore utilityIf you want to use the NMSAP backint program for backup, restore, and inquiryoperations for the Oracle database, you must create a BR*Tools initialization profile withthe required settings.

Procedure

1. With a text editor, open the BR*Tools initialization profile initDBSID.sap, usuallylocated in the following directory:

l On UNIX or Linux: $ORACLE_HOME/dbs



l On Microsoft Windows: %ORACLE_HOME%\DATABASE2. Set the backup device type parameter to use the backint program by specifying one

of the following settings:

backup_dev_type = util_file

or

backup_dev_type = util_file_online

Note

You must set backup_dev_type = util_file_online for online backups to decrease theamount of time each tablespace remains in hot backup mode, resulting in a smallernumber of generated transaction logs.

3. Set the util_par_file parameter to use the NMSAP parameter file, initDBSID.utl:

l On UNIX or Linux:

util_par_file = ?/dbs/initDBSID.utl

where ? is $ORACLE_HOME.

l On Microsoft Windows:

util_par_file = ?\database\initDBSID.utl

where ? is %ORACLE_HOME%.

NMSAP backint parameters on page 77 describes how to configure the parameterfile. The appropriate SAP documentation describes how to use the backint program.

Specifying RMAN as the backup and restore utilityIf you want to use the Oracle RMAN utility with the NMSAP media management library forbackup, restore, and inquiry operations for the Oracle database, you must create aBR*Tools initialization profile with the following settings.

Procedure

1. With a text editor, open the BR*Tools initialization profile initDBSID.sap, usuallylocated in the following directory:

l On UNIX or Linux: $ORACLE_HOME/dbsl On Microsoft Windows: %ORACLE_HOME%\DATABASE

2. Set the backup device type parameter to use the RMAN program:

backup_dev_type = rman_util

The rman_util value ensures that the NMSAP RMAN interface backs up the Oracledatabase data and the NMSAP backint interface backs up the BR*Tools metadata(configuration files, backup catalog, and so on).

Note

Do not use the rman_disk or rman_stage value because these values cause BR*Toolsto back up the metadata without using NMSAP and NetWorker.


Specifying RMAN as the backup and restore utility 73

3. Uncomment the line for the rman_send parameter and set the parameter to includeeach NetWorker (NSR_*) parameter that is appropriate for the backup, restore, andinquiry sessions.

NMSAP parameters for RMAN backups and restores on page 94 describes theseparameters. Use the following syntax:

rman_send="NSR_ENV=(var1=value1, var2=value2, ...)"

For example, the following setting sends the same value to all the allocated channels:

rman_send="NSR_ENV=(NSR_DEBUG_LEVEL=9, NSR_SERVER=bu-libra)"

The following setting sends the channel-specific values:

rman_channels=2rman_send=("channel sbt_1 'NSR_ENV=(NSR_DATA_VOLUME_POOL=pool_name_1)'","channel sbt_2 'NSR_ENV=(NSR_DATA_VOLUME_POOL=pool_name_2)'")

The SAP documentation describes how to use the BR*Tools with RMAN program forbackup and restore operations.

Configuring scheduled backups with the wizardYou can create or modify a scheduled backup configuration with the NMSAP wizard.

You must meet the following requirements before you use the configuration wizard:

l You have installed the required NetWorker releases on the NMC server, NetWorkerserver, and NMSAP client hosts as described in the EMC NetWorker Module for SAPRelease Notes.

l On the NetWorker server where the configuration exists, the NMC user that starts thewizard (the wizard user) has the Configure NetWorker privilege and all its prerequisiteprivileges.

l Communication between the NMC server, NetWorker server, and NMSAP client usesNetWorker nsrauth authentication. The NetWorker documentation provides therequirements for nsrauth authentication.

l You have configured the NMSAP software environment as described in Verifying theNMSAP software requirements on page 70.

Procedure

1. In the NMC Enterprise view, select the NetWorker server name and double-click theNetWorker application to launch the application.

2. In the Configuration view under the NetWorker server name, select Clients:

l To create a NetWorker Client resource for NMSAP, right-click Clients and selectClient Backup Configuration > New.

l To modify a NetWorker Client resource previously created with the wizard forNMSAP, right-click the client name and select Client Backup Configuration >Modify.

3. On each wizard page that appears, specify the options and values required for thebackup configuration.

You can click a link in the wizard steps panel to go directly to the page you want tomodify. The number of steps shown in the steps panel varies according to the chosenconfiguration type.



4. If you use the wizard to modify a configuration and you select to change a databaseuser’s password or OS user’s password, the wizard enables you to apply thatpassword change to other backup configurations with the same credentials. Thefeature facilitates easy password changes across different server-side configurationsas follows:

l If you use database authentication on the client host and you select to change thepassword for a specific database (Net service name) and database username, thepassword change is applied to all the backup configurations that use the samedatabase and username on the host.

Note

If you use the same username for different databases on the same host, you canselect an option to apply the same password change to all the backupconfigurations of all the databases with that username.

l If you select to change the password for a specific OS username, the passwordchange is applied to all the NMSAP backup configurations that use the same OSusername on the host.

5. On the last wizard page named Review and Accept the Client Configuration, clickCreate or Modify to create or modify the configuration, and click Finish to exit thewizard.

Converting client-side configurations to wizard configurationsNMSAP with the supported NetWorker server and client software enables the conversionof scheduled backup settings from NMSAP client-side files, initDBSID.utl andnsrsapsv.cfg, to attributes on the NetWorker server that are used by the NMSAPwizard. After a conversion, you can only modify and update the configuration by using thewizard.

NMSAP can run scheduled backups by using either the wizard configurations or theclient-side parameter file and configuration file.

Note

Manual backups performed with NMSAP require the use of the client-side parameter fileand configuration file.

The conversion method uses the nsrsapadm utility to convert NMSAP 3.0.2 or laterscheduled backup settings to the new wizard settings. This utility reads the backupparameter file and configuration file on the NMSAP client host. The utility then stores theconverted settings on the NetWorker server. The utility changes the scheduled backupcommand specified in the NetWorker Client resource from nsrsapsv -f file_name tonsrsapsv.

To convert a configuration with the nsrsapadm utility, perform the following steps oneach SAP Oracle client to be backed up by the NetWorker server:

Procedure

1. Log in to the SAP Oracle client as the user with the Configure NetWorker privilege onthe NetWorker server.

2. Ensure that you have installed the NetWorker client software and NMSAP on the SAPOracle client, and specified the client as a NetWorker Client resource on theNetWorker server.


Converting client-side configurations to wizard configurations 75

3. On the SAP Oracle client operating system command line (UNIX or Linux) or commandprompt window (Windows), run the following command:

nsrsapadm -W -s server_name [-c client_name] [-g group_name][-N save_set_name]

where:

l -W specifies the conversion mode.

l -s server_name specifies the NetWorker server on which the configuration willbe saved and run.

l -c client_name specifies the NetWorker Client resource that has the backupsettings to be converted. If not specified, the default value is the hostname of thephysical host where the nsrsapadm command runs. You must set this option tothe virtual client name for cluster environments.

l -g group_name specifies the NetWorker Group resource of the client beingconverted. If used, the group must already exist.

l -N save_set_name specifies the save set name used in the Client resource.

For example, the following command converts all the Client resources for the NMSAPphysical host, located on the NetWorker server my.server.com, which have the SaveSet attribute set to backint:SAP1:

nsrsapadm -W -s my.server.com -N backint:SAP1

Configuring scheduled backups without the wizardAs an alternative to the wizard configuration, you can create or modify a scheduledbackup configuration by performing the following tasks:

Procedure

1. Configuring the NMSAP parameters without the wizard on page 76

2. Configuring the scheduled backup resources without the wizard on page 97

The NMC interface provides NetWorker Group, Device, Media Pool, and other resourcesettings that are not available in the wizard.

Configuring the NMSAP parameters without the wizardProcedure

1. Ensure that you have correctly configured the NMSAP software environment asdescribed in Verifying the NMSAP software requirements on page 70.

2. On the NMSAP client, copy the init_oracle_nmsap.utl and nsrsapsv.cfgtemplate files (supplied with the NMSAP installation) with new names for thedatabase instance, and configure the files for the backup.

NMSAP parameters for backups and restores on page 77 provides configurationdetails.

3. Encrypt the SAP operating system username and the password, and if required, theOracle database username and password:

a. On the NMSAP client, log in as the root user or administrator and type thefollowing NMSAP command:

nsrsapadm -P oracle -z config_file_pathname



where config_file_pathname is the full pathname of the NMSAP backupconfiguration 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.

4. On the NMSAP client, configure the BR*Tools initialization profile initDBSID.sapwith the following parameters:

l Backup device type (backup_dev_type)

l Backup utility configuration file (util_par_file)

Choosing either backint or RMAN as the backup and restore utility on page 72provides details.

NMSAP parameters for backups and restores

For all NMSAP Oracle operations except scheduled backups configured with the wizard,you must set the required parameters in the backint parameter file on the NMSAPclient as described in NMSAP backint parameters on page 77. RMAN backups use thebackint program to back up metadata.

In addition, for RMAN backups and restores, you must also set NMSAP parameters in theinitDBSID.sap file with either the rman_send option or the rman_parms option asdescribed in NMSAP parameters for RMAN backups and restores on page 94.

For NMSAP scheduled backups configured without the wizard, you must also set therequired nsrsapsv parameters in the NMSAP configuration file as described in NMSAPnsrsapsv parameters on page 87.

You must also set certain SAP parameters in the initDBSID.sap file, as described inthe relevant sections of this guide.

Note

For scheduled backups configured with the wizard, you do not need to set anyparameters. The configuration wizard sets all the required parameters in the NetWorkerClient resource attributes.

NMSAP backint parametersThe parameters in the backint parameter file provide the client, server, pool,deduplication, parallelism, and other values to the NMSAP backint program.

Make a copy, such as initDBSID.utl, for your own use of the original parameter filetemplate, init_oracle_nmsap.utl, installed with NMSAP.

Note

When you uninstall NMSAP or upgrade NMSAP to a new release, the system deletes theoriginal template file and any settings you made in the file.

The template file is located in the following directory:

l On Linux and UNIX: /etc/init_oracle_nmsap.utll On Windows: NetWorker_install_directory\nsr\bin

\init_oracle_nmsap.utl


Configuring the NMSAP parameters without the wizard 77

NOTICE

If you use this file for scheduled backups, you do not need to set the server parameter orthe group parameter in the file. However, if you do set the parameters, the parametersettings must match the corresponding attributes on the NetWorker server or an erroroccurs. Any other settings specified in this file, such as the pool name, take precedence over thecorresponding setting on the NetWorker server.

To set parameters in your copy of the backint parameter file, initDBSID.utl, usethe following format and guidelines:

parameter=value

l To use parameters, you must uncomment and modify the parameters as required.


l You must set all mandatory parameters.

l If you do not set an optional parameter, the default value of the parameter is used.

The following table describes the backint parameters that NMSAP supports.

Table 7 Supported backint parameters


arch_backint_log Specifies the full pathname of the backint log

file when running the brarchive command.l Default location on UNIX:

/nsr/applogs/arch_backintDBSID.log.raw

l Default location on Windows:NetWorker_install_path\nsr\applogs\arch_backintDBSID.log.raw

l Valid full pathname of the log file. Thedirectory pathname must exist. If the file doesnot exist, the operation creates the file.

backint_log Specifies the full pathname of the backint log

file when running the brbackup command or

brrestore command.

To specify a separate log file to use specifically forrestores, modify this parameter before you runbrrestore. Alternatively, you can specify the

backint_log parameter in an

initDBSID_restore.utl file, which you can

specify as a command line argument to thebrrestore program. For example:

brrestore -r initDBSID_restore.utl

l Default location on UNIX:/nsr/applogs/backintDBSID.log.raw

l Default location on Windows: NetWorker_install_path\nsr\applogs\backintDBSID.log.raw

l Valid full pathname of the log file. Thedirectory pathname must exist. If the file doesnot exist, the operation creates the file.

backint_tmpdir Specifies the directory of the backint temporary

files.l Default location on UNIX:

/nsr/applogs/l Default location on Windows:

NetWorker_install_path\nsr\applogs\



Table 7 Supported backint parameters (continued)


l Valid full pathname. The directory pathnamemust exist.

checksum Specifies whether to perform a cyclic redundancycheck (CRC) on the backup data.Setting this parameter to TRUE excludes the use ofthe compress and NSR_AES_ENCRYPTIONparameters, which you must set to FALSE. If you setmore than one of these parameters to TRUE, thepriority order is: compress, checksum,NSR_AES_ENCRYPTION.

l FALSE (default).

l TRUE.

client Specifies the NetWorker client hostname to use forthe client file index for the current backup orrestore.If you use NMSAP to back up or restore a virtualcluster client, set this value to the virtual nodename.

l Local physical host (default).

l Valid NetWorker client hostname.

compress Specifies whether to compress the data during abackup before the data passes over the network oris written to the backup device. The compressioncan speed up the backup process. Compressionincreases CPU usage on the SAP Oracle server, butreduces the amount of data sent to the NetWorkerstorage node.NMSAP supports only the default NetWorkerencryption algorithm. NMSAP does not supportbackup compression with GZIP or BZIP2.

Setting this parameter to TRUE excludes the use ofthe checksum and NSR_AES_ENCRYPTIONparameters, which you must set to FALSE. If you setmore than one of these parameters to TRUE, thepriority order is: compress, checksum,NSR_AES_ENCRYPTION.

l FALSE (default).

l TRUE.

debug_level Specifies the level of debug messages thatbackint writes to the debug log file.


l 0 to 9.

max_logs Specifies the maximum number of the backintsession logs saved in the backint log file,

specified by the backint_log parameter. If you

set the value to 0, all the backup logs are saved inthe log file.

l 0 (default).

l Any positive integer.

notify_done Alerts when the backint program completes its

activity. Uncomment the option and replace mailxwith the name of the command line email utility tobe used. For example:notify_done = mailx -s ’backint done’ root


l Valid email string.





notify_error Alerts if the backint program encounters any

errors during its activity. Uncomment the optionand replace mailx with the name of the commandline email utility to be used. For example:notify_error = mailx -s ’backint error’ root



notify_start Alerts when the backint program begins its

activity. Uncomment the option and replace mailxwith the name of the command line email utility tobe used. For example:notify_start = mailx -s ’backint start’ root



notify_success Alerts when the backint program successfully

completes its activity. Uncomment the option andreplace mailx with the name of the command lineemail utility to be used. For example:notify_success = mailx -s ’backint success’ root



NSR_AES_ENCRYPTION Specifies whether to encrypt backup data with256-bit AES encryption.Setting this parameter to TRUE excludes the use ofthe compress and checksum parameters, whichyou must set to FALSE. If you set more than one ofthese parameters to TRUE, the priority order is:compress, checksum, NSR_AES_ENCRYPTION.

NOTICE

If the encryption phrase has changed between thetime of the backup and the time the backup isrestored, the NSR_ENCRYPTION_PHRASESparameter must include the original phrase toenable the recovery.

l FALSE (default).

l TRUE.

NSR_ARCH_LOGS_SEQUENTIAL

Specifies whether NMSAP backs up archive logs inalphabetical order to optimize the log removal(cleanup) during an archive log backup.Setting this parameter to TRUE causes thebackint program to back up archive logs in

alphabetical order, which speeds up the logcleanup process during the archive log backup.

Optional for manual and scheduled backups ofarchive logs with brarchive.

l FALSE (default).

l TRUE.

Note

When you use the nondefault value TRUE, the loadbalancing parameters ss_group_by_fs and

ss_size_max are ignored during the

brarchive backup.

NSR_DATA_DOMAIN_INTERFACE

Specifies the network interface to use to sendbackup data to the DD Boost device.Optional for a manual backup only.

Set this parameter if you have a Fibre Channel (FC)connection to the DD Boost device. You must setthis parameter together withNSR_DEVICE_INTERFACE=DATA_DOMAIN. If you do

l IP (default) = Backup data is sent over an IPnetwork to the DD Boost device.

l Any = Backup data is sent over either an IP orFC network to the DD Boost device, dependingon the available device.

l Fibre Channel = Backup data is sent over an FCnetwork to the DD Boost device.





not set NSR_DEVICE_INTERFACE to DATA_DOMAIN,then this parameter is ignored.

NSR_DEBUG_DIR Specifies the directory of the backint diagnostic

logs.l Default location on UNIX:

/nsr/applogs/l Default location on Windows:

C:\Program Files\Legato\nsr\applogs\C:\Program Files\EMC NetWorker\nsr\applogs (after a new installation with

NetWorker client 8.0 or later)

NSR_DEDUP_BACKUP Specifies whether to perform a deduplicationbackup.Mandatory for manual deduplication backups only.Do not set for scheduled backups.

Note

For scheduled deduplication backups, set theDeduplication Backup attribute in the NetWorkerClient resource, instead of setting this parameter.

l FALSE (default) = Deduplication is notperformed during an NMSAP backup. OtherNSR_DEDUP_* parameters are ignored.

l TRUE = Deduplication is performed during anNMSAP backup. If you do not setNSR_DEDUP_NODE, the backup fails.

NSR_DEDUP_CACHE_ENABLED

Specifies whether a cache is used during adeduplication backup.Optional for deduplication backups.

Not using a cache decreases the backupperformance, but also decreases the disk usage inthe /nsr/dedup/cache directory.

Note

When you use the nondefault value FALSE, yourequire knowledge of Avamar operations.

l TRUE (default) = A cache is used to increaseperformance during a deduplication backup.This value is recommended usually.

l FALSE = A cache is not used during adeduplication backup.

NSR_DEDUP_CACHE_TAG

Specifies the name of the cache used by thensravtar process during an NMSAP backup.

Optional for deduplication backups.


l String value of the tag that will generate adeduplication cache name. Do not include theclient name in the value.

NSR_DEDUP_CHUNK_SIZE

Specifies the size in bytes of data chunks that theAvamar server uses in a deduplication backup.Optional for deduplication backups.

Note

When you adjust the data chunk size, you requireexpert knowledge of Avamar operations and thedata to be backed up.

l 0 (default) = Variable sizes are used for thedata chunks, as determined by the Avamarserver. This value is recommended in mostcases.

l Value greater than zero = A fixed data chunksize to use for a deduplication backup. Forexample: 1024, 2048, 5096, 8194, or othervalue as recommended in the Avamardocumentation.





NSR_DEDUP_NODE Specifies the NetWorker De-duplication Noderesource (Avamar server) to be used for thebackup. The name must exactly match theDeduplication Node attribute set in the NetWorkerClient resource.Mandatory for manual deduplication backups only.Do not set for scheduled deduplication backups.


l Name of the NetWorker De-duplication Noderesource.

NSR_DEVICE_INTERFACE

Note

This parameter isdeprecated. It issupported in the currentNMSAP release, but willbe unsupported in afuture release.

Specifies whether the backup is always stored onthe Data Domain device from the specified pool.Optional for manual deduplication backups withthe Data Domain media type only. Set theparameter when the backup pool contains amixture of Data Domain devices and other types ofdevices. For example: AFTD, tape, and so on.

Do not set for scheduled deduplication backups.Instead, set the Data Domain Backup attribute inthe NMSAP Client resource when the pool hasmixed devices for a scheduled deduplicationbackup.

l Undefined (default) = The backup data mightbe stored on any device from the pool selectedby NetWorker.

l DATA_DOMAIN = The backup data is alwaysstored on the Data Domain device.

NSR_DIRECT_ACCESS Specifies the method used to perform a backup toa Data Domain device or an AFTD.Optional for a manual backup with any NetWorkerserver release or a scheduled backup withNetWorker server release earlier than 8.0.

If the target device is on a Data Domain system:

l Data is deduplicated on the NMSAP clientwhen the Client Direct feature is enabled.

l Data is deduplicated on the storage nodewhen the Client Direct feature is disabled

This parameter is ignored during scheduledbackups with NetWorker server release 8.0 or laterand during restores.

For scheduled backups with NetWorker serverrelease 8.0 or later, you can enable the ClientDirect feature with the Client Direct setting in thewizard or the Client resource.

l Default (default) = The backup tries to use theClient Direct feature to bypass the storagenode and write data directly to the targetdevice. If the backup cannot use this feature,the backup uses the storage node.

l No = The backup does not try to use the ClientDirect feature. The backup uses the storagenode only.

l Yes = The backup tries to use the Client Directfeature. If the backup cannot use this feature,the backup fails.

Note

The Yes value is deprecated. The value issupported in the current NMSAP release, but willbe unsupported in a future release.

NSR_ENCRYPTION_PHRASES

Specifies the original phrase to enable therecovery. You can specify multiple phrases to tryfor the recovery.Mandatory if the NSR_AES_ENCRYPTION phrasehas changed between the time of the backup andthe time the backup is restored.

Any valid string. For example:NSR_ENCRYPTION_PHRASES = “phrase 1“ , “phrase2“

Enclose each phrase in double quotes, andseparate phrases with a comma. Do not use acomma after the last phrase.

NSR_GROUP Specifies the name of a NetWorker backup groupto use for a manual backup.

l Default (default).

l Valid name of a NetWorker backup group.





Optional for a manual backup. Do not set thisparameter for a scheduled backup.

This parameter can be used to enable the followingoperations:

l Test a backup manually on the client sidebefore starting scheduled backups.

l Direct a manual backup to a NetWorker devicepool, based on the backup group criteria.

NSR_NWPATH Specifies the pathname of the directory thatcontains the NetWorker binaries or Avamarbinaries.Recommended for deduplication backups orrestores if the NetWorker software is installed in anondefault location.

l Platform-specific default location of theNetWorker client binaries (default).

l Valid directory pathname of the nsravtarbinary.

NSR_PHYSICAL_HOST_LICENSE

Specifies whether NMSAP is licensed per clusternode or per virtual cluster name in an active-passive cluster environment with NetWorker server7.6 SP1 or later.Optional in an active-passive cluster.

l FALSE (default) = NMSAP is licensed pervirtual cluster name in the active-passivecluster.

l TRUE = NMSAP is licensed per cluster node inthe active-passive cluster.

NSR_RAW_DEVICE_SKIP_BYTES

Specifies to omit unwanted data from recovery ona raw device. Specifies the initial amount of data toskip.

Note

When you adjust the amount of data to skip, yourequire expert knowledge of the operating systemand the volume manager specifications.


l Valid device name, followed by an equal signand the amount of data to skip in bytes,kilobytes, megabytes, or gigabytes:NSR_RAW_DEVICE_SKIP_BYTES=/raw/dev1=skip[B|K|M|G]

Specify multiple devices by separating the deviceswith a colon.

For example, the following setting skips 8 KB forthe raw device /dev/rdsk/c2t4d0s5:

NSR_RAW_DEVICE_SKIP_BYTES=/dev/rdsk/c2t4d0s5=8K

NSR_RECOVER_POOL Specifies the name of the NetWorker volume poolto use for a restore. You can use this option torestore data from a specified volume pool if thereare multiple copies (clones) of the backup indifferent volume pools.Optional for restores. Supported for normalrestores only, not for snapshot restores.

l Pool determined by the NetWorker server(default).

l Valid name of a NetWorker volume pool thatcontains a cloned backup to use for a restore.

NSR_RELOCATION_DEST For a relocated restore, specifies a new rootdirectory for SAP datafiles when SAPDATA_HOME ischanged but the structure of subdirectories underSAPDATA_HOME is not modified.


l Same value as the new SAPDATA_HOME value.





NSR_SAVESET_BROWSE Specifies the date when the entry for the backup isremoved from the NetWorker client index and theassociated backup files are no longer readilyavailable for browsing.

Note

For a scheduled backup, this parameter overridesthe Browse Policy attribute setting in theNetWorker Client resource.

l Browse policy specified in the NetWorkerClient resource for the client, as determined bythe NetWorker server (default).

l Valid date in nsr_getdate(3) format.

NSR_SAVESET_RETENTION

Specifies the date when the save set becomesrecyclable and the associated data on the volumecan be overwritten.

Note

For a scheduled backup, this parameter overridesthe Retention Policy attribute setting in theNetWorker Client resource.

l Retention policy specified in the NetWorkerClient resource for the client (default).

l Valid date in nsr_getdate(3) format.

parallelism Specifies the number of save sets or save streamsto send simultaneously to the NetWorker server.Typically, this setting must be equal to the sum ofthe "target sessions" for all the devices dedicatedto the NMSAP backup or restore.You must configure the NetWorker server tosupport this parallelism value or greater. Configuring the scheduled backup resourceswithout the wizard on page 97 provides detailsabout the parallelism setting in the Client resource.

Note

The parallelism value is reduced if the value is

greater than the savesets parameter value.

l 8 (default).


pool Specifies the NetWorker Media Pool resource,defined on the NetWorker server, which receivesbackup data from the SAP Oracle server.This parameter is used for manual backups and isnot recommended for scheduled backups.

Note

If set for scheduled backups, this parameteroverrides the NetWorker server setting.

To use multiple pools to separate data:

1. Create separate initDBSID.utl parameter

files.

l Most appropriate pool, selected by theNetWorker server (default).

l Valid name of a NetWorker volume pool.





2. Use the -r option to specify the parameter file

name to use at the command line withbrbackup or brarchive.

For example, a pool named ARCHData is usedspecifically for archive logs. You can create aseparate parameter file for archive logs, forexample, named archiveC11.utl,and set the poolattribute to ARCHData. To use the pool to back upthe archive logs, type this command at thecommand line:

brarchive -u sys/admin -d util_file-r archiveC11.utl-m all -s save

prev_bk_restore UNIX only. When the query_index parameter is

set to FALSE, the prev_bk_restore parameter

specifies whether to restore the previous backup ifthe required backup cannot be found.

l FALSE (default).

l TRUE.

ps_backup_modeps_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

NMSAP Oracle Snapshot Backups and Restores onpage 139 provides details about the NSMparameters.

query_index UNIX only (Windows is always TRUE). Specifieswhether to query the NetWorker server indexes forvalidation of the requested files and backup IDsbefore a restore begins.

l FALSE (default) = The query does not occurbefore a restore.

l TRUE = The query occurs before a restore.

raw_dir Specifies the directories for raw disk partitions onUNIX only. Any files below these directories areconsidered to be raw disk partitions. Do not setthis parameter to the /dev or /devices


l Directory pathnames of the raw disk partitions,separated by a semicolon (;). For example:raw_dir = /oracle/data;/sap/data





directories, which are already treated as rawdevices.

Note

The listed partitions are pointed to by the symboliclinks under $SAPDATA_HOME/sapraw/TBS_number/.

retry_count Specifies the number of times to retry a failedbackup for each save set.

l 0 (default).


savesets Specifies the number of save sets to divide thefiles on a client and distribute the backup load. Ifthe value is equal to or greater than the number ofdatabase files, then a separate save set is madefor each file. If the value is less than the number ofdatabase files, then a save set might contain morethan one file.This parameter is ignored if thess_group_by_fs parameter is set to TRUE.

l 20 (default).


sem_timeout Specifies the amount of time in minutes thatbackint waits for brbackup or brconnect to

remove the semaphore file. If the semaphore file isnot deleted, backint exits with an error at the

end of this timeout period.

l 30 (default).


server Specifies the hostname of the NetWorker serverthat the NMSAP backint program uses for

backup, restore, and inquiry sessions.

Note

You do not need to set this parameter for ascheduled backup, but if you set the parameter,the value must match the server that started thebackup or an error occurs.


l NetWorker server hostname.

ss_group_by_fs If you set this parameter to TRUE, the operationignores the savesets and ss_size_maxparameters and groups save sets by file systeminstead of file size. This efficient grouping of filescan improve performance of scheduled backups,index searches, and restore times.

l FALSE (default).

l TRUE.

ss_size_max Specifies the maximum save set size inmegabytes. If you do not set this parameter or youset the parameter to zero, the save set size isunrestricted. The value must be equal to or greaterthan the size of the largest datafile.

l 0 (default).


ssNameFormat Specifies the naming convention for save sets: l old (default).





l If you set this parameter to old, then the namefor all the save sets is backint:DBSID.

l If you set this parameter to new, then the saveset name for each session differs according tothe files being backed up. The save set nameuses the format backint:DBSID:full_path of thefirst file name in the save set.If you set each save set to store one file, avalue of new simplifies the process ofbrowsing the media database. The mediadatabase shows each file name as part of thesave set name.

l If you set this parameter to old_pid ornew_pid, then the save set name is generatedaccording to the old or new naming conventionand the process ID is added to the save setname.

l new.

l old_pid.

l new_pid.

NMSAP nsrsapsv parametersThe nsrsapsv parameters provide environmental and other values to the NMSAPscheduled backup program, nsrsapsv.

You can use these parameters to perform the following operations among others:

l Specify nondefault locations of required programs and files.

l Configure system-specific environment variables.

l Identify the specific SAP Oracle database to back up.

l Specify the BR*Tools command and options used for scheduled backups.

You can set the parameters in the wizard or in the nsrsapsv configuration file,nsrsapsv.cfg, for nonwizard configurations. The template file is located in thefollowing directory:

l On Linux and UNIX: /etc/nsrsapsv.cfgl On Windows: NetWorker_install_directory\nsr\bin\nsrsapsv.cfgMake a copy of the configuration file template before you customize the file for backups.You can use any preferred name or location for the customized configuration file.

Note

When you uninstall NMSAP or upgrade NMSAP to a new release, the system deletes theoriginal template file and any settings you made in the file.

To set parameters in your copy of the nsrsapsv configuration file, nsrsapsv.cfg, usethe following format and guidelines:

l Use this format for each parameter setting:

parameter_name = parameter_value



l If you back up multiple databases in a single backup configuration, specify theparameter settings in the configuration file as follows:

n For parameter settings common to all the databases, specify the parametersettings outside of the braces.

n For parameter settings unique to specific databases on the SAP Oracle client,group the parameter settings within braces.

The following example shows the correct positions of parameter settings in theconfiguration file:

# Global parameters common to all the databasesparameter1 = valueparameter2 = valueparameter3 = value

DBSID1 {# Parameter settings for DBSID1parameter4 = value1parameter5 = value}

DBSID2 {# Parameter settings for DBSID2parameter4 = value2}

where DBSID1 and DBSID2 are Oracle database instances that appear on separatelines in the Save Set attribute of the Client resource for the scheduled backup.

A global parameter appears outside of all the braces. A database-specific parameterappears within the braces after a particular database SID.

l The following precedence rules apply to the parameter settings:

n Global parameter settings apply to all the Oracle databases included in thebackup.

n If a global parameter is set more than once, the last setting takes precedence overall the previous settings of the global parameter.

n Database-specific parameter settings within braces apply only to the particularOracle database instance and override the corresponding global parametersettings for the backup of that specific database.

n If a parameter appears more than once within the same braces, the last settingtakes precedence over all the previous settings of the parameter within thebraces.

l To use parameters in a scheduled backup, uncomment and modify the parameters asrequired.


l Use full pathnames for parameters that specify a pathname or a file name. Thefollowing items are not supported in pathnames and file names:

n Special Oracle characters, such as ?

n Environment variables, such as $ORACLE_HOME and %ORACLE_HOME%

l Specify the full pathname of the configuration file in the Backup Command attributeof the Client resource for the scheduled backup. Configuring the scheduled backupresources without the wizard on page 97 describes the Client resource attributes.

The following table describes the parameters in the nsrsapsv configuration file thatNMSAP supports.



Table 8 Supported nsrsapsv parameters


BR_EXEC Specifies the brbackup or brarchivecommand and its options that thensrsapsv scheduled backup program

executes.Mandatory for nonwizard configurationsonly. Do not use for wizard configurations.

Note

Do not use the -u option, which identifies

the username and password of the Oracledatabase administrator. Instead, you mustencrypt the username and password byusing the nsrsapadm -P oracle -zfile_name command. Configuring the NMSAP parameters withoutthe wizard on page 76 provides detailsabout the username and passwordencryption.

Caution: If you save a wizard configurationto a file, such as nsrsapsv.cfg, the file

contains the following parameters that thensrsapsv program uses to generate the

brbackup or brarchive command at

runtime:

l BKUP_TYPE

l BKUP_OBJECTS

l TABLESPACE

l DATAFILE

l LOGS_NUM

l LOGS_DEL

l BRARCHIVE_CLI

l BRBACKUP_CLI

l SAP_CONFIG

You must not use these wizard parametersif you configured the nsrsapsv.cfg file

manually.

l brbackup (default).

l brbackup or brarchive and command line

options.

HOMEDRIVE Specifies the drive name where Windowssystem files reside. Verify this setting bytyping set homedrive on the command

line.Optional. Use on Windows only.


l Valid disk drive. For example: C:

NLS_LANG Specifies the language character set in thefollowing format:LANGUAGE_TERRITORY.CHARACTERSET

l AMERICAN_AMERICA.US7ASCII (default).

l Valid Oracle setting for NLS_LANG variable.





Mandatory parameter.

The Oracle documentation provides details.

NSR_BRTOOLS_SECURE_PASSWORD

Specifies whether to use the secure storagepassword feature, which stores theBR*Tools connection data for the databasein a BR*Tools specific Secure Storage in FileSystem (SSFS).BR*Tools Kernel 7.20 Patch 27 or latersupports this secure storage passwordfeature.

Optional parameter.

l FALSE (default).

l TRUE.

Note

This parameter takes precedence overNSR_BRTOOLS_SECURE_ROLE and any specifieddatabase authentication.

NSR_BRTOOLS_SECURE_ROLE Specifies whether to use the role-basedstorage of the BR*Tools user and passwordin the secure storage, which assigns theDBA and OPER roles to OS users without theOS users having to belong to the Oracle OSgroups dba and oper.BR*Tools Kernel 7.20 Patch 30 or latersupports this role-based secure storagefeature.

Optional parameter.


l Valid OS user group name to use for role-based secure storage.

Note

This parameter takes precedence over anyspecified database authentication.NSR_BRTOOLS_SECURE_PASSWORD takesprecdence over this parameter.

NSR_SAP_SECURE_RUN Hides the Oracle user password passed tothe brbackup -u or brarchive -ucommand from operating systemcommands, such as ps -ef.

Optional. Use on UNIX only.

l FALSE (default).

l TRUE.

NSR_SAP_USING_RMAN_OPTION

If you use RMAN to back up database files,set this parameter to TRUE. For example:NSR_SAP_USING_RMAN_OPTION=TRUE

l FALSE (default).

l TRUE.

NSR_SAP_WAIT_BRTOOLS_DONE_MINS

Specifies how long (after a backup isterminated by the user) the nsrsapsvprogram waits for the brbackup program

to do the following:

l Perform a cleanup routine.

l Remove tablespaces from backupstatus.

l 2 minutes (default).

l Positive number of minutes.

ORACLE_BIN Specifies the pathname of the Oraclebinaries location. The specified pathnameis appended to the PATH environmentvariable so that all the Oracle binaries canbe found.Mandatory only if the Oracle binaries arenot in the default location,$ORACLE_HOME/bin.

l $ORACLE_HOME/bin (default).

l Valid full pathname of the bin directory of the

Oracle server installation.





ORACLE_HOME Specifies the pathname of the homedirectory of the Oracle server installation.Mandatory parameter.


l Valid full pathname of the home directory ofthe Oracle server installation. For example:/db/oracle/product/10.2.0

ORACLE_SID Specifies the system identification (SID) forthe Oracle instance to be backed up.Mandatory. For a nonwizard configuration,must be set either in the configuration fileor in the Save Set field of the Clientresource.

For example, if the save set name in theNetWorker Client resource is backint:SAPand this parameter is not specified in theconfiguration file, then SAP is used for theOracle SID.

l Oracle SID derived from the save set name inthe NetWorker Client resource used for thebackup (default).

l A valid Oracle database SID.

ORACLE_USR_PASSWD Specifies an encrypted value that containsthe SAP user’s Oracle database usernameand password.Optional parameter.

Do not manually add or edit this parameter.Use the nsrsapadm -P oracle -zcommand to set this parameter.

Configuring the NMSAP parameters withoutthe wizard on page 76 provides detailsabout the username and passwordencryption.

Passwords that you enter through thewizard are not stored in the configurationfile but are securely stored in a lockbox.


l Uneditable encrypted value set with thensrsapadm -P oracle -z command.

OS_USR_PASSWD Specifies an encrypted value that containsthe SAP user’s operating system usernameand password.Mandatory parameter.

Do not manually add or edit this parameter.Use the nsrsapadm -P oracle -zcommand to set this parameter.

Configuring the NMSAP parameters withoutthe wizard on page 76 provides detailsabout the username and passwordencryption.

Passwords that you enter through thewizard are not stored in the configurationfile but are securely stored in a lockbox.


l Uneditable encrypted value set with thensrsapadm -P oracle -z command.





PATH Specifies the pathname of the NetWorkerclient binary file and any other requiredsearch pathnames.Optional parameter.

The specified value is appended to thePATH environment variable. To specifymultiple search pathnames, use one of thefollowing two methods:

l PATH=d:\dir1;d:\dir2;d:\dir1\dir2\dir3

l PATH=d:\dir1PATH=d:\dir2PATH=d:\dir1\dir2\dir3


l Valid pathnames, separated by semicolons onUNIX or colons on Windows.

POSTCMD Specifies a postprocessing script to runafter a scheduled backup:

l The postprocessing script file mightneed permissions that allow executionby the root user.

l The script must return a zero valuewhen it succeeds, and a nonzero valuewhen it fails.

l On UNIX, the first line of the script mustcontain the following interpreterdirective:#!/bin/sh

Optional parameter.

Note

If the scheduled backup fails, thepostprocessing script still runs.If the postprocessing script fails, an errormessage appears but the scheduledbackup succeeds.


l Valid full pathname of a postprocessing scriptfile. The pathname must not contain anyspaces.For example, instead of setting POSTCMD to C:\Program Files\Legato\nsr\postcmd.bat, setthe parameter to C:\Progra~1\Legato\nsr\postcmd.bat.Also, instead of setting POSTCMD to C:\Program Files\EMC NetWorker\nsr\postcmd.bat, set the parameter to C:\Progra~1\EMC NetWorker\nsr\postcmd.bat.

l If the value is undefined or invalid, apostprocessing script does not run after thescheduled backup.

PRECMD Specifies a preprocessing script to runbefore a scheduled backup:

l The preprocessing script file mightneed permissions that allow executionby the root user.

l The script must return a zero valuewhen it succeeds, and a nonzero valuewhen it fails. The return of a nonzerovalue causes the scheduled backup tofail.

l On UNIX, the first line of the script mustcontain the following interpreterdirective:


l Valid full pathname of a preprocessing scriptfile. The pathname must not contain anyspaces.For example, instead of setting PRECMD to C:\Program Files\Legato\nsr\precmd.bat, setthe parameter to C:\Progra~1\Legato\nsr\precmd.bat.

Also, instead of setting PRECMD to C:\Program Files\EMC NetWorker\nsr\precmd.bat, set the parameter to C:\Progra~1\EMC NetWorker\nsr\precmd.bat.





#!/bin/sh

Optional parameter.

Note

If the preprocessing script fails, NMSAPdoes not perform a scheduled backup, anerror message appears, and anypostprocessing script does not run.

l If the value is undefined or invalid, apreprocessing script does not run before thescheduled backup.

SAP_BIN Specifies the pathname of the location ofthe BR*Tools binary files.Mandatory parameter.

This location should also be where thebackint (UNIX) or backint.exe(Windows) executable resides, after it ismanually moved to this location followingthe NMSAP installation.

This location is added to the PATHenvironment variable so that the BR*Toolsbinaries and backint can be found.


l Valid full pathname of the BR*Tools location.For example:/usr/sap/SAP/SYS/exe/run

SAPDATA_HOME Specifies the pathname of the root directoryof the SAP Oracle datafiles.Mandatory parameter.

The SAP documentation provides details.

l Undefined.

l Valid full pathname of the root directory of theSAP Oracle datafiles. For example: d:\orant\SAP\

SAP-specific environmentvariables:SAPARCH

SAPBACKUP

SAPCHECK

SAPREORG

SAPTRACE

Mandatory for brbackup to run correctly

on Windows systems. These variables arenormally set in the SAP environment onWindows.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

l UNIX default: $ORACLE_HOME/sapxxxwhere xxx is the appropriate suffix: arch,backup, check, reorg, or trace.

l Windows default: None.

l Valid full pathname of the SAP log directory.

SAPSWITCH Specifies an alternative location of theswitch files during file_online backups.

Optional parameter.

For manual backups, set the parameter inthe environment. For scheduled backups,the parameter supports both client-side andserver-side configuration files. You must notset the parameter in the backintconfiguration file.

l OS-dependent default location:- On Windows: %SAPBACKUP%- On UNIX: $ORACLE_HOME/sapbackup

l Valid directory pathname with no spaces. Forexample: d:\dir1





Requires BR*Tools 7.1 or later. If you do notset the parameter correctly, the backup failsand logs a message in the backint debug

log. For a successful backup, unsetSAPSWITCH and remove the generatedswitch files.

Any name_path=value pair Appends values to any environmentvariable named name_path, such asLD_LIBRARY_PATH, LIBPATH, orSHLIB_PATH.

l If an environment variable with thisname already exists, then the specifiedparameter value is appended to theexisting value for the environmentvariable.

l If an environment variable with thisname does not exist, then the variableis created.

Optional parameter.

Any valid environment variable and pathname. Forexample:LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/dbhome_1/lib

Any name=value pair Adds any environment variable namedname. If the environment variable specifiedby name already exists, then the variable isoverwritten.Optional parameter.

Any valid environment variable and value. Forexample:BR_TRACE=1

BR_TRACE is set to 1 in the environment, whichinstructs brbackup or brarchive to print out

additional trace information.

NMSAP parameters for RMAN backups and restores

If you select RMAN as the backup and restore utility as described in Choosing eitherbackint or RMAN as the backup and restore utility on page 72, then you must set theNMSAP parameters for RMAN backups and restores through BR*Tools parameters. Youmust set the parameters in the BR*Tools initialization profile initDBSID.sap witheither the rman_send option or the rman_parms option.

Note

Set the parameters with the rman_send option unless stated otherwise.

The BR*Tools initialization file is located in the following directory:

l On UNIX or Linux: $ORACLE_HOME/dbsl On Windows: %ORACLE_HOME%\DATABASEThe following table describes the NMSAP parameters to configure the RMAN backups andrestores support.



Table 9 Supported NSR_* parameters for RMAN


NSR_AES_ENCRYPTION Corresponds to the NSR_AES_ENCRYPTIONparameter in Table 7 on page 78.

NSR_CHECKSUM Corresponds to the checksum parameter in Table 7 on page 78.

NSR_CLIENT Corresponds to the client parameter in Table 7 on page 78.

NSR_COMPRESSION Corresponds to the compress parameter in Table 7 on page 78.

NSR_DATA_VOLUME_POOL Corresponds to the pool parameter in Table7 on page 78.

NSR_DEBUG_LEVEL Controls the amount of debug informationthat NMSAP writes to the debug log file,located in the directory specified byNSR_DIAGNOSTIC_DEST or in the defaultdirectory, /nsr/apps/logs (UNIX) orNetWorker_install_path\apps\logs (Windows).

This parameter controls the debug level fordebug messages generated by RMANoperations only.

Optional parameter.

Note

You must set this parameter in therman_parms parameter. Do not set thisparameter in the rman_send parameter.


l 0 to 9.

NSR_DEDUP_BACKUP Corresponds to the NSR_DEDUP_BACKUPparameter in Table 7 on page 78.

NSR_DEDUP_CACHE_ENABLED Corresponds to theNSR_DEDUP_CACHE_ENABLED parameter in Table 7 on page 78.

NSR_DEDUP_CACHE_TAG Corresponds to theNSR_DEDUP_CACHE_TAG parameter in Table 7 on page 78.Set a different value for each channel. If youuse the same tag value for more than onechannel, the deduplication backup fails.

Set this parameter with the rman_sendparameter in the BR*Tools initializationprofile initDBSID.sap. Configuring

deduplication backups with Avamar andOracle RMAN on page 104 gives anexample.

l / (forward slash, default for all RMANchannels).

l Alphanumeric string that will generate adeduplication cache name. Do not include theclient name in the value.

Recommended value is DBSID_channel-ID.

For example: orcl10g_1



Table 9 Supported NSR_* parameters for RMAN (continued)


NSR_DEDUP_CHUNK_SIZE Corresponds to theNSR_DEDUP_CHUNK_SIZE parameter in Table 7 on page 78.

NSR_DEDUP_NODE Corresponds to the NSR_DEDUP_NODEparameter in Table 7 on page 78.

NSR_DEVICE_INTERFACE Corresponds to the NSR_DEVICE_INTERFACEparameter in Table 7 on page 78.

NSR_DIAGNOSTIC_DEST Specifies the directory location of all theNMSAP debug logs generated for an RMANoperation.Optional parameter.

Note

You must set this parameter in therman_parms parameter. Do not set thisparameter in the rman_send parameter.

l /nsr/apps/logs (UNIX) orNetWorker_install_path\apps\logs(Windows) (default).

l Valid pathname of the directory where NMSAPgenerates the debug logs.

NSR_DIRECT_ACCESS Corresponds to the NSR_DIRECT_ACCESSparameter in Table 7 on page 78.

NSR_ENCRYPTION_PHRASES Corresponds to theNSR_ENCRYPTION_PHRASES parameter in Table 7 on page 78.

NSR_GROUP Corresponds to the NSR_GROUP parameterin Table 7 on page 78.

NSR_NO_BUSY_ERRORS Specifies whether a scheduled backup failsimmediately when the NetWorker server isbusy or waits for the NetWorker server toaccept the connection.Optional parameter.

Note

You must always set this parameter toFALSE for proxy Oracle backups.

l FALSE (default) = The scheduled backup waitsfor the NetWorker server to accept theconnection.

l TRUE = The scheduled backup failsimmediately when the NetWorker server isbusy.

NSR_NO_MULTIPLEX When set for a specific RMAN channel,specifies whether multiplexing is disabledduring a backup on the NetWorker devicethat the RMAN channel uses. If you disablemultiplexing, the backup cannot write othersave sets to the device.Optional parameter.

To optimize restore operations, RMANrequires NMSAP backups to not bemultiplexed.

Setting the parameter to TRUE can affect thebackup performance. For example, the

l FALSE (default) = Multiplexing is enabled onthe device that the RMAN channel uses.

l TRUE = Multiplexing is disabled on the devicethat the RMAN channel uses.

Note

If you use a random access NetWorker device,such as an advanced file device, do not set theparameter to TRUE.



Table 9 Supported NSR_* parameters for RMAN (continued)


device can sit idle during part of thebackup. If the performance is adverselyaffected, reset the parameter to FALSE.

NSR_NWPATH Corresponds to the NSR_NWPATHparameter in Table 7 on page 78.

NSR_PHYSICAL_HOST_LICENSE Corresponds to theNSR_PHYSICAL_HOST_LICENSE parameterin Table 7 on page 78.

NSR_RETENTION_DISABLED Specifies whether the NetWorker browsepolicy and retention policy are disabled.Optional parameter.

Set to TRUE to use Oracle policies only (notNetWorker policies) to manage the backupdata lifecycle. Then the RMAN catalog andNetWorker indexes cannot becomeunsynchronized, such as when a NetWorkerindex entry expires but the correspondingRMAN catalog entry is not expired.

l FALSE (default) = NetWorker browse andretention policies are enabled and used tomanage the lifecycle of the Oracle backupdata.

l TRUE = NetWorker browse and retentionpolicies are disabled. You use only Oraclepolicies to manage the lifecycle of the Oraclebackup data.

NSR_SAVESET_BROWSE Corresponds to the NSR_SAVESET_BROWSEparameter in Table 7 on page 78.

NSR_SAVESET_RETENTION Corresponds to theNSR_SAVESET_RETENTION parameter in Table 7 on page 78.

NSR_SERVER Corresponds to the server parameter in Table 7 on page 78.

Configuring the scheduled backup resources without the wizardOn the NetWorker server, you can configure a NetWorker Client resource and otherscheduled backup resources in the NMC program, without using the wizard.

Procedure

1. In the NMC Enterprise view, select the NetWorker server name, and double-click theNetWorker application to launch it.

2. In the Configuration view under the NetWorker server name, select the appropriatebackup resources to configure, such as Groups, Schedules, Clients, and so on.For example:

l To create a client, right-click Clients and select New.

l To modify an existing NMSAP client, double-click the client name to open itsProperties window.

On each of the properties tabs, specify the appropriate options and values for thebackup configuration.

3. Configure the NetWorker Group, Schedule, and other NMC resource settings forscheduled NMSAP backups. The EMC NetWorker Administration Guide and online helpprovide details about the NetWorker resources:



l Schedule resource—Create or select a Schedule resource to specify the days of theweek when the scheduled backup runs.

l Group resource—Create or select a Group resource to apply to a group ofNetWorker clients that will start to back up data at a scheduled time. Set Autostartto Enabled. You can apply a Group resource as an attribute to a NetWorker Clientresource and a NetWorker Media Pool resource.

l Device resources—Configure a NetWorker Device resource for each supportedstorage device used for backup and restore operations.

l Media Pool resources—Configure the volumes in each NetWorker Media Poolresource to receive specific types of backup data, such as tablespaces or archivedlogs. When configuring the Media Pool resources, leave the Save Sets attributeblank. The NMSAP program sets the Save Sets during each backup session.

l Client resource—Specify a NetWorker Client resource for each SAP Oracle server(NMSAP client) that requires backup, restore, and inquiry services.

The following table describes the Client resource attributes that are applicable toNMSAP operations.

Table 10 NetWorker Client resource attributes for NMSAP scheduled backups


Aliases Globals Specifies all known aliases for the NMSAP host.

Backup Command Apps &Modules

Specifies the name of the command to be used for an NMSAP scheduled backup, either:nsrsapsvwhich is configured by the wizard only and cannot be manually set

or

nsrsapsv -f file_pathnamewhich uses the settings of the NMSAP configuration file (nsrsapsv.cfg), where file_pathname is

the full pathname of the NMSAP configuration file created on the NMSAP client host as describedin Configuring the NMSAP parameters without the wizard on page 76. The pathname can containonly ASCII characters and can be no longer than 64 characters.

The default pathname is as follows:

l On Microsoft Windows: NetWorker_install_directory\nsr\res\nsrsapsvDBSID.cfg

l On UNIX: /nsr/res/nsrsapsvDBSID.cfgIf the pathname contains spaces, you might need to add quotes around the pathname and add anextra backslash after each backslash, for example, “C:\\Program Files\\dir\\file”.

Browse Policy General Specifies the length of time that the NetWorker server retains an entry for the backup in the onlineclient file index.

Checkpointenabled

General When selected, enables a restartable backup.

Checkpointgranularity

General This attribute is ignored by all NMSAP operations.

Client Direct General When selected, enables the Client Direct feature for a scheduled backup to a DD Boost device orAFTD. If a Client Direct backup is not possible, the backup routes the data through the storagenode instead of sending the data directly from the client to the storage device.





Note

This attribute is only available with NetWorker server release 8.0 or later.

(Avamar)DeduplicationBackup

Apps &Modules

When selected, enables a deduplication backup to Avamar.

Note

You cannot select this attribute together with the Data Domain Backup attribute.

(Avamar)DeduplicationNode

Apps &Modules

Specifies the hostname of the Avamar server that will store the deduplicated backup.

Data DomainBackup

Apps &Modules

When optionally selected, ensures that the deduplication backup is always stored on a DD Boostdevice when the backup pool contains a mixture of DD Boost devices and other types of devices.

Note

You cannot select this attribute together with the (Avamar) Deduplication Backup attribute.

Data DomainInterface

Apps &Modules

Specifies the interface over which the backup will occur to a Data Domain device. This option isused only when you enable Data Domain Backup for the client. Select the appropriate setting forthe attribute:

l Fibre Channel—The backup will use a Fibre Channel (FC) interface.

l IP—The backup will use an IP interface.

l Any—The backup will use either an FC or IP interface, depending on the available Data Domaindevice.

Note

This attribute is only available with NetWorker server release 8.1 or later.To enable a restore from a Data Domain device over an FC interface, you must set this attribute toFibre Channel.

Directive General Leave blank. NMSAP does not support global directives.

Group General Specifies the NetWorker Group resource to use for an NMSAP scheduled backup.

Name General Specifies the hostname of the SAP server host where the NMSAP software is installed.

Parallelism Globals Specifies the maximum number of concurrent backup and restore sessions to use for a backupoperation. You can use this Client resource attribute instead of the parallelism setting in theparameter file or the wizard configuration.

Pool Globals Specifies the pool to use for a backup. When selected, this attribute overrides the pool associatedwith the backup group.

Remote Access Globals Specifies the SAP user and fully qualified hostname (IP) of a remote host, used to enable backupsin a cluster environment and restores of the backups to that remote system.

l For a cluster backup, specifies sap_user@physical_host for each physical host in the cluster.

l For restore of a backup from this host to a different destination host, specifiessap_user@different_host.





Remote User,Password

Apps &Modules

Recommended for backups on Microsoft Windows systems. Not required on UNIX systems. Theseattributes specify the SAP user’s operating system username and password.

Retention Policy General Specifies the minimum length of time that must elapse before backed-up data is eligible to beoverwritten on the backup media.

Save Set General Specifies the database to be backed up. Use the following format for the save set name:backint:DBSID

For a client-side scheduled backup that you configured without the wizard, you can optionallyspecify multiple database instances on separate lines:

backint:DBSID1

backint:DBSID2

where DBSID1 and DBSID2 are different database instances on the same SAP Oracle client.

You can specify unique parameter settings for each database instance by grouping the parametersettings within braces in the nsrsapsv configuration file as described in NMSAP nsrsapsv

parameters on page 87.

Schedule General Specifies the NetWorker Schedule resource to use for an NMSAP scheduled backup.

Configuring manual backupsYou must complete the required steps to configure an NMSAP manual backup.

Procedure

1. Complete all the steps described in Verifying the NMSAP software requirements onpage 70.

2. Configure the NMSAP parameter file, initDBSID.utl, with the settings for theappropriate NetWorker server and the other backup parameters.

NMSAP backint parameters on page 77 provides details.

3. Set the following parameters in the BR*Tools initialization profile initDBSID.sap:

l Backup device type (backup_dev_type)

l Backup utility configuration file (util_par_file)


Configuring restartable backupsYou can configure a scheduled restartable backup or a manual restartable backup for anNMSAP client.

You can configure a scheduled restartable backup either with the wizard or without thewizard. If you do not use the wizard, you must use individual settings in the NMCprogram.



Configuring scheduled restartable backups with the wizardYou can configure a scheduled restartable backup with the wizard by following theinstructions in Configuring scheduled backups with the wizard on page 74 andperforming the following additional steps.

Procedure

1. On the Specify Backup Type and Data Options page, select the Checkpoint enabledcheckbox.

2. On the Specify Performance and Other Options page:

a. Set the parallelism to the required value for the backup, which should be less thanthe number of files to be backed up.

b. Set the Number of Save Sets field to a value greater than the parallelism.

3. To enable the automatic restart of a failed backup, use the NMC program to set theClient Retries attribute in the Group resource to a value greater than zero.

Note

If you do not enable automatic restart of a failed backup, you must restart the backupmanually through the group restart option.

Configuring scheduled restartable backups without the wizardYou can configure a scheduled restartable backup without the wizard by following theinstructions in Configuring scheduled backups without the wizard on page 76 andperforming the following additional steps.

Procedure

1. On the General tab in the Client resource, select the Checkpoint enabled checkbox.

Note

NMSAP ignores the Checkpoint Granularity attribute during a checkpoint restartablebackup. Changing the attribute setting has no impact on the NMSAP backup.

2. In the backint configuration file, initDBSID.utl, set the following parameters:

l Set parallelism to the required value for the backup, which should be less than thenumber of files to be backed up.

l Set savesets to a value greater than the parallelism.

l Set ss_group_by_fs to FALSE.

NMSAP backint parameters on page 77 describes these backint parameters andhow to set them.

3. To enable the automatic restart of a failed backup, set the Client Retries attribute inthe Group resource to a value greater than zero.

Note

If you do not enable automatic restart of a failed backup, you must restart the backupmanually through the group restart option.


Configuring scheduled restartable backups with the wizard 101

Configuring manual restartable backupsTo configure a manual restartable backup, you must set the required parameters in thebackint configuration file, initDBSID.utl, as described in step 2 of Configuringscheduled restartable backups without the wizard on page 101.

Restarting failed manual backups on page 119 describes how to restart a failed manualbackup.

Configuring Avamar deduplication backupsYou must follow the requirements, best practices, and configuration procedures for adeduplication NMSAP backup with Avamar.

SAP Oracle in Cluster and RAC Environments on page 131 describes additional steps fordeduplication backup configuration in cluster and RAC environments.

Requirements for Avamar deduplication backupsYou must meet the following requirements for an Avamar deduplication backup:

l The NetWorker client and server releases support deduplication. The EMC NetWorkerSoftware Compatibility Guide at EMC Online Support provides details.

l Install and configure the Avamar server as a NetWorker deduplication node. The EMCNetWorker Administration Guide provides details.

l Configure the NetWorker backup device, which receives only the backup metadataduring the NMSAP deduplication backup, as an advanced file type device (AFTD). TheEMC NetWorker Administration Guide and release notes provide details.

Best practices for Avamar deduplication backupsThe benefits of deduplication depend on the environment. Deduplication can bebeneficial in a data warehouse environment where the data does not change frequently.Deduplication can also be beneficial for databases where only a small percentage of datais updated repeatedly, or where new data is added to a database but the old data doesnot change much.

The following practices can improve the deduplication backup performance:

l After you select an Avamar server as the deduplication node for an initial full backupof a client, continue to use that same node for all backups of the client. This practicetakes advantage of the client deduplication information stored on the node.

l Do not use deduplication for RMAN incremental backups. Because only data blocksthat have changed are backed up, incremental backups result in a low rate ofduplication and the benefit is likely to be insignificant.

l Do not include a deduplication client in the same Group resource asnondeduplication clients.

l Depending on computer resources, avoid setting backup parallelism to more thanfour.

l Schedule deduplication backups to avoid the Avamar server read-only periods. AnAvamar server spends periods of time in maintenance mode, where the server mightbe unavailable for backup or have limited bandwidth.



Note

A deduplication NMSAP backup that runs during a maintenance period might becomesuspended until the Avamar server resources become available.

l For RMAN backups only:

n For database full backups, you can improve the deduplication ratio by not usingRMAN multiplexing and by ensuring that the Oracle software does notconcatenate data from different files in the same backup piece. To disablemultiplexing and prevent concatenation, ensure that rman_filesperset is setto 1 in the BR*Tools initialization profile initDBSID.sap. The Oracledocumentation describes RMAN multiplexing and the number of files in eachbackup set.

n If you perform database incremental backups or archived log backups to Avamar,the Oracle software sends only the changed blocks. As a result, the deduplicationratio is typically low. To increase the backup throughput for these backups, setrman_filesperset to a larger value or do not set rman_filesperset. If youdo not set rman_filesperset, then the Oracle software uses the defaultsetting. The Oracle documentation provides more details aboutrman_filesperset.

The Avamar and NetWorker documentation describes the Avamar server and NetWorkerrequirements for deduplication backups.

Configuring scheduled Avamar deduplication backups with the wizardYou can configure a scheduled Avamar deduplication backup either with or without thewizard. The configuration procedure with the wizard requires the following steps.

Procedure

1. Create a NetWorker Deduplication Node resource for the Avamar server.

2. Follow the instructions in Configuring scheduled backups with the wizard on page 74and perform the following additional steps:

a. On the wizard page for deduplication options, select the Avamar deduplicationbackup and the deduplication node (Avamar server).

b. On the Specify Log Files Locations and Additional Options wizard page, in thetable, set the NSR_NWPATH parameter to the location of the NetWorker client.

c. For typical operations, use the default settings for cache usage and chunk size.However, if nondefault settings are required, set the following parameters in thetable on the Specify Log Files Locations and Additional Options wizard page:

l NSR_DEDUP_CACHE_ENABLED

l NSR_DEDUP_CHUNK_SIZE

l NSR_DEDUP_CACHE_TAG

Table 7 on page 78 describes these parameters.


Configuring scheduled Avamar deduplication backups with the wizard 103

Configuring scheduled Avamar deduplication backups without wizardYou can configure a scheduled Avamar deduplication backup either with or without thewizard. The configuration procedure without the wizard uses individual settings in theNMC program.

Procedure


2. Follow the instructions in Configuring scheduled backups without the wizard on page76 and perform the following additional steps:

a. In the Client resource for the NMSAP client host, set the Avamar deduplicationbackup flag and select the deduplication node (Avamar server).

b. In the NMSAP parameter file initDBSID.utl set the NSR_NWPATH parameter tothe location of the NetWorker client.

c. For typical operations, use the default settings for cache usage and chunk size.However, if nondefault settings are required, set the following parameters in theNMSAP parameter file initDBSID.utl:

l NSR_DEDUP_CACHE_ENABLED

l NSR_DEDUP_CHUNK_SIZE

l NSR_DEDUP_CACHE_TAG

Table 7 on page 78 describes these parameters.

Configuring manual Avamar deduplication backupsYou can include deduplication in a manual backup that uses the NMSAP backintprogram.

Procedure


2. Create a NetWorker Client resource for the SAP Oracle host, set the Avamardeduplication backup flag, and select the deduplication node (Avamar server).

3. Edit the NMSAP parameter file initDBSID.utl with the following settings:

l NSR_DEDUP_BACKUP = TRUE

l NSR_DEDUP_NODE = NetWorker_deduplication_nodeThis name must exactly match the Deduplication Node name selected in the Clientresource.

Configuring deduplication backups with Avamar and Oracle RMANYou can include deduplication in a scheduled backup or manual backup that uses theOracle RMAN utility.

Procedure


2. Create a NetWorker Client resource for the SAP Oracle host, set the Avamardeduplication backup flag, and select the deduplication node (Avamar server).

3. On the SAP Oracle server, edit the BR*Tools initialization profile initDBSID.sapand configure the rman_send parameter with the following settings:



l NSR_DEDUP_BACKUP—Mandatory for manual backups only.

l NSR_DEDUP_NODE—Mandatory for manual backups only.

l NSR_DEDUP_CACHE_TAG—Mandatory for backup with more than one RMANchannel. Set this parameter to a different value for each channel.

The following example shows an rman_send parameter configured for a manualdeduplication 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)'")

Table 9 on page 95 describes the parameters.

Configuring Data Domain Boost backupsThis topic provides specific information about using DD Boost with NMSAP. The EMCNetWorker and EMC Data Domain Deduplication Devices Integration Guide providesadditional information about the DD Boost configuration and initial setup.

You must follow the requirements, best practices, and configuration procedures in thissection for a deduplication backup that uses only DD Boost devices. The content in thissection does not apply to a deduplication backup that uses AFTD or VTL devices.

The NetWorker documentation describes how to configure a Data Domain backup to AFTDor VTL devices. Configuring NMSAP backups to AFTD storage on page 108 also describeshow to configure a Client Direct backup to AFTD devices.

Requirements for DD Boost backupsBefore you configure a Data Domain deduplication backup with a DD Boost device,ensure that the NetWorker client and server releases support the DD Boost device. TheEMC NetWorker Module for SAP Release Notes provides details.

NMSAP supports three types of configurations for Data Domain deduplication backups:

l Deduplication using Client Direct—This configuration eliminates the sending of dataover the network between the NMSAP client and the storage node. The deduplicateddata is sent directly from the NMSAP client to the DD Boost device.

l Deduplication on a remote storage node—This configuration decreases the amount ofnetwork traffic between the storage node and Data Domain system by sending onlythe unique blocks over the network. However, deduplication requires all the data tobe sent over the network between the NMSAP client and the storage node.

l Deduplication on a local storage node (located on the NMSAP client)—Thisconfiguration has similar performance to deduplication using Client Direct. However,this configuration requires a storage node on the NMSAP client and additionalmemory resources.


Configuring Data Domain Boost backups 105

Best practices for DD Boost backupsDeduplication backups and restores with a Data Domain system are preferable to thosewith an Avamar server for large databases with high data change rates. A daily changerate of more than 5 percent is a high change rate.

During planning and configuration of a deduplication backup, keep in mind these bestpractices that can improve the backup performance:

l Do not use database backup encryption or NMSAP backup encryption because theencryption decreases the data deduplication ratio.

l Do not use database backup compression or NMSAP backup compression becausethe compression decreases the data deduplication ratio.

l Use Client Direct access to a Data Domain device for backups and restores toeliminate data transfer between the NMSAP client and NetWorker storage node.However, using this feature requires an additional 24 MB of memory per data streamon the NMSAP client and also increases the NMSAP CPU usage.

l For RMAN backups only:

n For database full backups, you can improve the deduplication ratio by not usingRMAN multiplexing and by ensuring that the Oracle software does notconcatenate data from different files in the same backup piece. To disablemultiplexing and prevent concatenation, ensure that rman_filesperset is setto 1 in the BR*Tools initialization profile initDBSID.sap. The Oracledocumentation describes RMAN multiplexing and the number of files in eachbackup set.

n For database incremental backups or archived log backups, the Oracle softwaresends only the changed blocks. As a result, the deduplication ratio is typicallylow. To increase the backup throughput for these backups, setrman_filesperset to a larger value or do not set rman_filesperset. If youdo not set rman_filesperset, then the Oracle software uses the defaultsetting. The Oracle documentation provides more details aboutrman_filesperset.

Data Domain and NetWorker documentation describes the requirements fordeduplication backups.

Configuring Client Direct with DD Boost backupsYou can configure a scheduled backup or manual backup to a DD Boost device that usesthe Client Direct feature to deduplicate data on the NMSAP host and pass only uniquedata blocks directly to the device, bypassing the storage node.

Procedure

1. Review Best practices for DD Boost backups on page 106.

2. Configure the DD Boost device and enable the Data Domain system for NetWorkeroperations. The EMC NetWorker and EMC Data Domain Deduplication Devices IntegrationGuide provides details.

3. For a Client Direct backup to a DD Boost device over Fibre Channel, ensure that theSAP user has the correct device permissions as described in the following EMCarticles:

l Fibre Channel Devices with Products using DD Boost in Linux Environment




l Fibre Channel Devices with Products using DD Boost in Windows Environment


Use the document ID to search for these articles on EMC Online Support.

Note

This step is not required for a backup through the storage node or a snapshot backupwith NSM.

4. Associate the backup with a pool that contains the DD Boost device configured in step 2 on page 106:

l For a scheduled backup, associate the required media pool with the NMSAP Groupresource or Client resource by using the NMC program. The EMC NetWorkerAdministration Guide and NMC online help provide details about using the NMCprogram.

l For a manual backup, set the pool parameter (for backint backups) or theNSR_DATA_VOLUME_POOL parameter (for RMAN backups) to the required pool. Configuring manual backups on page 100 provides details about configuring abackint backup. NSR_DATA_VOLUME_POOL on page 95 provides details aboutthe parameter for RMAN backups.

5. Follow the configuration instructions in the following table, similar to the instructionsfor configuring a nondeduplication backup.


With Client Direct enabled, NMSAP tries to perform a Client Direct backup. If a ClientDirect backup is not possible, NMSAP performs a backup through the storage node.

Note

If you upgrade from NetWorker server release 7.6.x to 8.0 or later, and you want todisable Client Direct for scheduled backups, you must clear the Client Direct checkboxin the wizard or disable the Client Direct attribute in the Client resource. WithNetWorker server 8.0 or later, the Client Direct setting in the Client resource or wizardfield takes precedence over the NSR_DIRECT_ACCESS setting in the initDBSID.utlparameter file.

Table 11 Configuring a Data Domain backup


Configuration instructions Additional instructions to use DD Boost overFibre Channel or if the pool contains Data Domainand other types of devices

Scheduled backup configured withthe wizard

Configuring scheduled backups withthe wizard on page 74

On the Client Backup Options wizard page:

l Select the Data Domain backup.

l Select the proper Data Domain interface. Ensurethat you select the Fibre Channel setting if you wantto use an FC interface.

Scheduled backup configuredwithout the wizard

Configuring scheduled backupswithout the wizard on page 76

In the Client resource of the NMSAP client:

l Select the Data Domain Backup attribute.


Configuring Client Direct with DD Boost backups 107

Table 11 Configuring a Data Domain backup (continued)


Configuration instructions Additional instructions to use DD Boost overFibre Channel or if the pool contains Data Domainand other types of devices

l Select the proper setting of the Data DomainInterface attribute. Ensure that you select the FibreChannel setting if you want to use an FC interface.

Manual backup Configuring manual backups on page100

In the initDBSID.utl parameter file:

l Set NSR_DEVICE_INTERFACE=DATA_DOMAIN. NSR_DEVICE_INTERFACE on page 82 providesdetails.

l Set NSR_DATA_DOMAIN_INTERFACE to the properinterface value. Ensure that you set the FibreChannel value if you want to use an FC interface. NSR_DATA_DOMAIN_INTERFACE on page 80provides details.

Configuring storage node with DD Boost backupsYou can configure a scheduled backup or manual backup to a DD Boost device, where thebackup does not try to use the Client Direct method but instead deduplicates data on astorage node.

Procedure

1. Follow step1 to step 5 in Configuring Client Direct with DD Boost backups on page106.


l For a manual backup with any NetWorker server release or for a scheduled backupwith a NetWorker server release earlier than 8.0, set NSR_DIRECT_ACCESS=No inthe advanced option table in the wizard or in the initDBSID.utl parameter file. NSR_DIRECT_ACCESS on page 82 provides details.

l For a scheduled backup with NetWorker server release 8.0 or later, clear the ClientDirect checkbox in the wizard or disable the Client Direct attribute in theNetWorker Client resource.

Configuring NMSAP backups to AFTD storageYou can configure an NMSAP scheduled or manual backup to an AFTD as either a ClientDirect backup or a backup that sends data through a storage node.



Configuring Client Direct backups to AFTDYou must complete the required steps to configure a scheduled or manual backup thatuses Client Direct to an AFTD.

Procedure

1. Configure an AFTD by using either the Device Wizard or the NMC device propertieswindow.

The EMC NetWorker Administration Guide provides complete details about AFTDconfigurations, including considerations for Client Direct clients.

2. Ensure that the NMSAP client has the required access to the AFTD through CIFS. TheEMC NetWorker Administration Guide provides details.

3. Associate the backup with a pool that contains the AFTD configured in step 1.

4. Follow the appropriate configuration instructions:





With Client Direct enabled, NMSAP tries to perform a Client Direct backup. If a ClientDirect backup is not possible, NMSAP performs a traditional backup through thestorage node.

Configuring storage node backups to AFTDYou must complete the required steps to configure a scheduled or manual backup to anAFTD where the backup does not try to use the Client Direct method but instead sendsdata through a storage node.

Procedure

1. Follow step 1 to step 4 in Configuring Client Direct backups to AFTD on page 109.




Configuring probe-based backupsThe NetWorker Probe resource is an optional feature that triggers backups when thesystem meets user-specified conditions. A probe-based backup is also referred to as anevent-based backup.

Note

Unless the system meets the probe conditions, a scheduled backup group enabled for aprobe will not run.

The system must meet the following conditions for a probe-based backup to be triggered:


Configuring Client Direct backups to AFTD 109

l The current time is within a specified window of time. The backup window is definedby the probe start time and end time in the probe-enabled backup Group resource.

l The system meets one of the following conditions:

n A specified amount of time has elapsed since the previous probe-based backup.

n One probe or all the probes associated with the backup are successful, dependingon the probe success criteria specified in the backup configuration.You can set the probe success criteria in the NetWorker Group resource to thevalue of Any or All.

Configuring a probe-based backupA probe-based NMSAP backup requires settings in three NetWorker resources: Probe,Group, and Client.

Procedure

1. Create a separate NetWorker Probe resource for the supplied NMSAP nsrsapprobeprogram and any other program or script that checks for a user-defined condition. TheProbe resource defines the conditions that trigger the probe-based backup.

NOTICE

Because a NetWorker Probe resource stores information on the state of database redologs, the Probe resource must be associated with a single NetWorker Client resourceonly. Multiple databases configured through multiple Client resources require aseparate Probe resource for each client.

You can associate a script written for a user-defined probe with more than oneNetWorker Client resource.

The following table describes Probe resource attributes for NMSAP backups.

Table 12 NetWorker Probe resource attributes for NMSAP backups

Attribute Description

Name A unique name that identifies the Probe resource.

Probe Command Name of the program or script that triggers a probe-based backup.For example, the nsrsapprobe program supplied with NMSAP 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 theLOG_THRESHOLD parameter.

The Probe Command can be a user-defined program or script. User-defined probes on page 112 provides details.

CommandOptions

Required for the nsrsapprobe program only. A comma-separated list of parameters with their settings as

follows:

l LOG_THRESHOLD—Mandatory. Specifies the number of Oracle transaction (archived redo) logs generated sincethe last probe-based backup, which will trigger a new probe-based backup.

l ORACLE_SERVICE—Mandatory only when database authentication is specified as described in step 4 on page111. 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 theORACLE_SERVICE parameter, then the values for ORACLE_SERVICE must match in both resources.



Table 12 NetWorker Probe resource attributes for NMSAP backups (continued)


l NSR_DEBUG_DIR—Optional. Specifies a valid directory pathname where debug information for probeoperations is recorded in a nsrsapprobe_pid.log file.

Note

When you set NSR_DEBUG_DIR, you enable debugging of probe operations.

l TNS_ADMIN—Mandatory if Oracle Net services files are installed in a nondefault location. Specifies thepathname of the nondefault location of the Oracle Net services files.

For example:

ORACLE_SERVICE=SAP.world,LOG_THRESHOLD=10

2. Create a NetWorker Group resource for the probe-based backup. Configure the Groupresource to enable probe-based backups and set the probe timing options.


3. Associate the NetWorker Probe resource with a Client resource. You must completethis setting with the individual NMC resource settings and not with the wizard. Thefollowing table describes the required Client resource attributes for NMSAP probe-based backups.

Table 13 NetWorker Client resource attributes for probe-based NMSAP backups


Probe ResourceName

Specify the name of the Probe resource from step 1 on page 110.

Note

You can associate a Client resource with only one probe.

Group Specify the name of the probe-enabled Group resource from step 2 onpage 111.


4. Specify either OS authentication or Oracle database authentication for probe-basedbackups by using the wizard or by setting a parameter in the nsrsapsv configurationfile:

l To specify that probe-based backups use OS authentication, set the OS usercredentials without setting the Oracle database user credentials. The OS usercredentials are mandatory. For example, you can run the nsrsapadm -Poracle -z file_pathname command to encrypt the OS user credentials in theOS_USR_PASSWD parameter in the configuration file. OS_USR_PASSWD on page91 provides details.

Note

The OS user password is mandatory on Windows and optional on UNIX. The OSauthentication requires ORACLE_SID to be set in the configuration file. Ensure thatyou have set up the OS authentication according to the Oracle documentation.


Configuring a probe-based backup 111

l To specify that probe-based backups use Oracle database authentication, also setthe Oracle database user credentials. Then the probe-based backups will usedatabase authentication by default. For example, you can run the nsrsapadm -Poracle -z file_pathname command to encrypt the Oracle database usercredentials in the ORACLE_USR_PASSWD parameter in the configuration file. ORACLE_USR_PASSWD on page 91 provides details.

User-defined probesThe user-defined script or program for probe-based backups must meet the followingrequirements:

l Name starts with “nsr” or “save.”

l Location is in the same directory that contains the NetWorker client binaries.

l Permissions of the script or program file include the “execute” permission.

l Returns one of the following code values when the script or program finishes runningits probe:

n 0—Signifies that the backup condition has been met.

n 1—Signifies that the backup condition has not been met.

n Other than 0 or 1—Signifies that an error occurred during the probe.

Example probe-based backup with multiple probesYou can configure a probe-based backup with multiple probes. Depending on the ProbeSuccess Criteria setting in the Group resource, a backup will start when the conditions forany or all of the probes are met.

For example, a probe-based backup is triggered when both of the following conditionsare true:

l 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 suppliednsrsapprobe program.

l More than two tape drives are idle in a tape library attached to a NetWorker storagenode named, for example, libstore_host, where the probe-based backup will be sentfor storage. A second Probe resource for this condition will use a user-defined scriptnamed nsrjukeboxprobe.

To configure an example probe-based backup with these two conditions:

Procedure

1. Create the NetWorker Probe resource for the supplied nsrsapprobe program withthe following attributes:

l Name: myxlogs

l Probe Command: nsrsapprobe

l Command Options: LOG_THRESHOLD=25

2. Create a user-defined script, nsrjukeboxprobe, with “execute” permissions andstore 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, andreturns one of the following values:

l 0—If more than two tape drives are idle in the library.



l 1—If two or fewer tape drives are idle in the library.

l Other than 0 or 1—An error occurred during the probe and no backup will beperformed

3. Create a second NetWorker Probe resource for the user-defined probe with thefollowing attributes:

l Name: myxdrives

l Probe Command: nsrjukeboxprobe

l Command Options: (blank)

4. Create a NetWorker Group resource named, for example, probe_group, and configurethe 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 thefollowing attributes:

l Name: oraprod_host

l Backup Command: nsrsapsv -f

l Group: probe_group

l Probe: myxlogs

l Save Set: backint:DBSID

6. Create a NetWorker Schedule resource named “skip_all” and set the level to skip foreach day in the schedule. This will enable 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:

l Name: libstore_host

l Backup Command: (blank)

l Group: probe_group

l Probe: myxdrives

l Save Set: my_skip_set

l Schedule: skip_all

Configuring backup email notificationsNMSAP enables you to obtain email notifications for when an NMSAP backup starts,ends, completes with errors, or completes successfully. You must specify the email utilitythat NMSAP will run for the email notifications, for example, the mailx utility on UNIX ora supported utility on Windows. This email utility must be installed on the NMSAP client.

To enable the email notifications, you must set the appropriate parameters to thecommand line options of the email utility:

l If you use the wizard to configure a backup, set the following parameters in theAdvanced Options table: notify_done, notify_error, notify_start, notify_success.

l If you use an NMSAP parameter file, initDBSID.utl, for the backup, set thenotify_done, notify_error, notify_start, and notify_success parameters in thatparameter file.

Table 7 on page 78 describes the required settings of these parameters.


Configuring backup email notifications 113



CHAPTER 5

NMSAP Oracle Operations


l Performing scheduled backups of SAP Oracle data..............................................116l Performing manual backups................................................................................118l Reviewing backup and restore session reports.................................................... 120l Verifying backup information in the NetWorker indexes.......................................120l Cloning backups................................................................................................. 122l Performing data restore and recovery.................................................................. 124l Requirements for disaster recovery..................................................................... 127l Recovering from a disaster.................................................................................. 127

NMSAP Oracle Operations 115

Performing scheduled backups of SAP Oracle dataYou can use the following procedures to test, monitor, and cancel scheduled NMSAPbackups of SAP Oracle data, not including snapshot backups.

The EMC NetWorker Administration Guide provides information about restarting checkpointenabled backups.

NMSAP Oracle Snapshot Backups and Restores on page 139 and NMSAP Oracle Split-Mirror Backups and Restores on page 155 describe how to perform NMSAP Oraclesnapshot backups.

Testing scheduled backupsYou can configure scheduled NMSAP backups to run automatically according to thebackup schedules. After you configure a scheduled backup, you can manually test thebackup.

Before you test a scheduled backup, ensure that you meet the following requirements:


l You have created the NetWorker Client resource with a correctly configured save setand backup command.

l You have assigned the Client resource to a backup group.

You can test a scheduled backup with the NetWorker Management Console (NMC).

Procedure

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.

Monitoring scheduled backupsThe NMC program provides a centralized view of all the backup and recovery activitythroughout an entire enterprise, the operations related to devices and libraries, and themanaged events that require user intervention.

You can monitor scheduled NMSAP backups with the NMC program.

Procedure



The Details window displays details of backups that are running, successfullycompleted, or failed.

Note

For a deduplication backup, the NMC display shows the total size of the data beforededuplication, not the size of the deduplicated data. The display also does notindicate that the data is for a deduplication backup.



Troubleshooting and Error Messages on page 173 describes how to review diagnosticmessages and error messages.

Canceling scheduled backupsYou cannot cancel a scheduled backup by clicking Stop on the ongoing save sets in theAll Sessions or Save Sessions window during the backup process.

If you cancel a backup before completion, none of the backed-up data might berecoverable.

You can cancel a scheduled backup in progress from the NMC program.

Procedure



3. Right-click the group to stop and select Stop.

To manually start a canceled backup process from the beginning, right-click the groupto start and select Start. Ensure that the backup successfully completes withoutinterruption.To cancel the scheduled backup from the NMSAP client host, you can use thefollowing command:

brbackup | brarchive -g abort | stop | term | kill

The SAP Note 1129197 provides details.

Restarting failed scheduled backupsIf you set the Client Retries attribute in the Client resource to a value greater than zero,the NetWorker group mechanism retries the backup automatically.

Alternatively, you can manually retry the backup from NMC.

Procedure



3. Right-click the group to rerun and select Restart.

To ensure that only the data that was not backed up in the failed backup is backed upagain, configure the backup to take advantage of the checkpoint restart option, asdescribed in Configuring restartable backups on page 100.

Note

If the restart does not occur within the NetWorker restart window that can be set onthe NMC group properties Advanced tab, the next checkpoint-restart backup backs upall the data.


Canceling scheduled backups 117

Performing manual backupsYou can use the following procedures to perform manual NMSAP backups of SAP Oracledata and NetWorker bootstrap backups, and also monitor and cancel manual NMSAPbackups.

NOTICE


Running manual backupsBefore you run a manual backup, ensure that you meet the following requirements:


l You have set the server parameter in the NMSAP parameter file, initDBSID.utl,for the appropriate NetWorker server. NMSAP backint parameters on page 77provides details.

l You have set the BR*Tools initialization profile initDBSID.sap with parameters forthe following items:

n Backup device type (backup_dev_type)

n Backup the utility configuration file (util_par_file)


You can perform a manual backup as illustrated by the following examples.

Procedure

1. Type the SAP backup command with the appropriate parameters to back up the SAPOracle database or the selected objects to the NetWorker server. For example:

l Offline backup:

brbackup -m all -t offline [-d util_file]l Online backup:

brbackup -m backup_objects -t online [-d util_file_online]

Examples of SAP Oracle Command Options on page 167 describes the availablebrbackup command options.

2. If you perform an online backup, back up the archived redo logs by typing thisadditional command:

brarchive



Note

Without the redo logs, you can recover a database that was backed up online only tothe time of its last full backup.

3. Back up the client file indexes and bootstrap. The EMC NetWorker Administration Guideprovides instructions.

4. Run the following command to back up nondatabase files or directories:

brbackup -m {sap_dir | ora_dir | all_dir | full_directory_path | nondatabase_file_path}

Directory backups and restores on page 26 provides details.

Monitoring manual backupsOperational messages about the status of manual NMSAP backups are displayed at thecommand line or GUI where the backup is started. Also, the NMC program provides acentralized view of the following activity:

l All the NetWorker server backup and restore activity

l Device and library operations and managed events that require user intervention

The EMC NetWorker Administration Guide describes how to review NMC progress andcompletion messages.

Troubleshooting and Error Messages on page 173 describes how to review diagnosticmessages and error messages.

Canceling manual backupsYou can cancel a running manual backup by using one of the following procedures:

l Press Ctrl-c or the equivalent “attention” keyboard shortcut on the system.

l Type the following command:

brbackup | brarchive -g abort | stop | term | kill

The SAP Note 1129197 provides details.

Restarting failed manual backupsWhen a backup session fails, you can restart the backup operation from the beginning byrerunning the brbackup command.

Alternatively, you can restart the backup of only the files that failed to be backed up:

Procedure

1. On the NMSAP host, inspect the backup session log and troubleshoot the errormessages. Reviewing backup and restore session reports on page 120 providesdetails.

2. Complete the backup by running the following command at the command line:

brbackup -f brbackup_log_name1[,brbackup_log_name2,...] | yyyy-mm-ddhh.mi.ss | number_of_days | last

Example 1 Restarting failed backups


Monitoring manual backups 119

Example 1 Restarting failed backups (continued)

l To back up the files that failed to be backed up during the last two backup sessions:

1. Find the backup logs for these two sessions in the SAPBACKUP directory, forexample, beemhgkr.anf and beemhzwi.anf.

2. Run the following command for these logs:

brbackup -f beemhgkr.anf,beemhzwi.anfl To back up the files that were not backed up during the last backup session, run the

following command:

brbackup -f lastl To back up the files that failed to be backed up in all the backup sessions that were

run in the last three days, run the following command:

brbackup -f 3

Reviewing backup and restore session reportsDuring backup sessions or restore sessions, the NMSAP backint program appends areport to a sessions log file on each NMSAP host. The default location for the log is asfollows:

l On Microsoft Windows: NetWorker_install_directory\nsr\applogsl On UNIX or Linux: /nsr/applogsThe default format for the log file name is backintDBSID.log.raw.

You can specify a different location for this backup sessions log by using a different namewith the backint_log and arch_backint_log parameters.

This sessions log is in I18N format. You must run the log through the NetWorkernsr_render_log utility to make the log readable.

Verifying backup information in the NetWorker indexesThe EMC NetWorker Administration Guide provides details about the NetWorker onlineindexes.

You can use the mminfo and nsrinfo commands to review information about NMSAPscheduled backups and manual backups in the NetWorker online indexes.

l Query the backup information in the media database by using the mminfo command.For example:

mminfo -v -s NetWorker_server_hostname -c NMSAP_client_hostname

Note

The deduplication save set size (size field) reported by the mminfo command

includes only the size of the NetWorker save set metadata.

n To view only save sets created as part of an Avamar deduplication backup, usethe mminfo command with the -q dedupe option.



n To view only save sets created as part of a Data Domain deduplication backup,use the mminfo command with the -q DataDomain option.

n To list the extended attributes for the deduplication backups, add the -S option,which provides information about the total size of data protected and the amountof new data passed during backup.The following example shows the result for an Avamar deduplication backup:

# mminfo -S -q dedupe -c oak

ssid=3413300047 savetime=03/23/2013 03:48:22 PM (1282592902) oak:backint:SAP level=full sflags=vF size=3860 files=5 insert=03/23/2013 create=03/23/2013 complete=03/23/2013 browse=04/23/2013 11:59:59 PM retent=03/23/2014 11:59:59 PM clientid=0b211897-00000004-4c72caf4-4c72caf3-00035000-8e6d9956 *ACTUAL_HOST: oak; *Client path: /NetWorker/bu-maple.legato.com/oak; *Data set size: 251666432; *De-Dup session id: 4; *De-Dup snapup time: 2013-03-23; *De-duplication: Yes; *De-duplication host: bu-sonic.lss.emc.com; *Domain: /NetWorker/bu-maple.legato.com; *New data on De-Dup Node: 701967.00; *New files: 1; *Size on De-Dup Node: 251666432.00; group: NMSAP; Clone #1: cloneid=1282592903 time=03/23/2013 03:48:23 PM retent=03/23/2014 flags=F frag@ 0 volid=4268935984 file/rec=3413300047/0 rn=0 last=03/23/2013

Note

For Avamar deduplication backups, the save set size in the size field reported bythe mminfo command includes only the size of the NetWorker save set metadata,

usually stored on the AFTD device. The size field does not include the size of thebacked-up data stored in Avamar. The *Size on De-Dup Node field provides thesize of the backed-up data.

The following example shows the result for a Data Domain deduplication backup:

# mminfo -S -q DataDomain -c oak

ssid=3138980225 savetime=02/11/2013 07:29:31 AM (1360585771) bu-staples:backint:SAP level=full sflags=vF size=52440380 files=8 insert=02/11/2013 create=02/11/2013 complete=02/11/2013 browse=03/11/2013 11:59:59 PM retent=02/11/2014 11:59:59 PM clientid=e78e210a-00000004-511148be-5119091d-00491100-7523d243 *ACTUAL_HOST: bu-staples; *backup start time: 1360585771;*ss data domain backup cloneid: 1360585772;*ss data domain dedup statistics: "v1:1360585772:52648196:52640041:904993"; group: sapdd; Clone #1: cloneid=1360585772 time=02/11/2013 07:29:32 AM retent=02/11/2014 flags=F frag@ 0 volid=3155757360 file/rec= 0/0 rn=0 last=02/11/2013


Verifying backup information in the NetWorker indexes 121

l Query the information about the backed-up files in the client file index by using thensrinfo command. For example:

nsrinfo -s NetWorker_server_hostname NMSAP_client_hostname

The nsrinfo command can produce very verbose output.

Note

For Avamar deduplication backups, the save file size (size field) recorded in theNetWorker index contains only the NetWorker save file metadata. The size field doesnot include the size of the backed-up data.

The EMC NetWorker Command Reference Guide and EMC NetWorker Administration Guidedescribe the nsrinfo command and mminfo command.

Deletion and expiration of Avamar deduplication backupsWhen a user or the NetWorker server deletes a deduplication backup, the backupinformation is deleted immediately from the NetWorker indexes and a request is queuedfor deletion of the backup from the Avamar server.

Once a deduplication save set exceeds the retention time and the data chunks aredeleted from the Avamar server, the save sets are no longer recoverable with the scannerprogram.

The EMC NetWorker Administration Guide describes the deletion of deduplication backups.

Cloning backupsThe NetWorker software can create clone copies of completed backup save sets foradditional protection and recovery options. You can use a special clone command withNMSAP, although the regular nsrclone command is also available.

The NMSAP clone process, which uses the sapclone command, makes an exact copy ofdata in a storage volume and saves the data in a clone volume. You can clone individualsave sets or the entire contents of a storage volume. Because the process clones onlycomplete save sets that can span multiple volumes, the process requests additionalclone volumes when needed.

A clone volume is indistinguishable from the original volume, except that the volumelabels are different. NetWorker software indexes and tracks save set clones in both theclient file index and the media database.

Note

If you clone Avamar deduplication backups, only the metadata stored on the NetWorkerstorage device is cloned, not the data stored by the Avamar server.

Using the sapclone command and optionsYou can clone NMSAP backups of SAP Oracle databases by running the sapclonecommand from the NMSAP host. You can use the sapclone command with the



NetWorker nsrclone command to write the cloned data to the default clone pool or to aspecified clone volume whose pool type is "clone."

Note

The sapclone command can clone only save sets that were generated with the NMSAP

backint program. The names of these save sets start with “backint.” You can clone

RMAN backups with the nsrclone command.

You can also use the sapclone command to create clones of deduplicated NMSAP savesets stored on Data Domain systems by specifying the -b option with a Data Domainclone pool. If you configure both the source device and target device for the clone copy asData Domain devices (not as AFTD or VTL devices), then the clone copy is optimized in thededuplication format, also known as “clone-controlled replication.” If the target device isfor conventional disk or tape storage, then the clone copy uses the nondeduplicatednative format. The EMC NetWorker and EMC Data Domain Deduplication Devices IntegrationGuide describes clone-controlled replication.

Use the following syntax for the sapclone command:

sapclone [-a] [-b pool] [-c client] [-n] [-s server] -u SID

Command options in brackets ([ ]) are optional. Only the -u option is mandatory.

The following table lists the options to use with the sapclone command.

Table 14 The sapclone command options

Option Description

-a Specifies to clone all the save sets of a client. If you do not use this option, the NMSAPprogram clones only the save sets created in the last 24 hours.Example: sapclone -a -u SAP1

-b pool Specifies the pool to which the cloned save sets are sent. If you do not use this option,the save sets are sent to the Default clone pool.Example: sapclone -b SAPClone -u SAP1

-c client Specifies the name of the client whose backed-up data should be cloned. NetWorkersoftware uses the client file index for the specified client to find and clone the clientdata.Use this option for cloning data backed up from a cluster. For example, you can set thisoption to the name of the cluster’s virtual node.

Example: sapclone -c saturn -u SAP1

-n Specifes to test the cloning operation on the save sets for a client. When you use thisoption, 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

-s server Specifies the destination NetWorker server. You must use this option only if one of thefollowing conditions is true:

l You clone to a NetWorker server other than the default server.

l You run the sapclone command on a SAP Oracle server.


Using the sapclone command and options 123

Table 14 The sapclone command options (continued)

Option Description

Example: sapclone -s mars -u SAP1

-u SID Mandatory. Specifies the Oracle database for which the save sets will be cloned.Example: sapclone -u SAP1

Performing data restore and recoveryYou can perform all NMSAP restore and recovery operations on a SAP Oracle host byusing the SAP BrGui interface or the brrestore or brrecover command.

NMSAP can restore and recover only the data that you backed up with NMSAP or with theFujitsu NetWorker Module for SAP R/3 version 3.0.

NOTICE

You can restore only the files for which you have read permission, based on the files’operating system permissions at the time that the files were backed up.

On a UNIX or Linux system, the read permission is associated with the numeric user ID(UID) and group ID (GID), not the username or group name. The UID and GID of the userperforming the restore must match the IDs associated with the files at backup time.

You can use the following procedure to recover an entire database or a subset ofdatabase objects, such as a tablespace or a datafile.

Procedure

1. (Optional) To restore the data to a different SAP Oracle host (destination host) thanthe one that was backed up:

l On a UNIX or Linux system, ensure that the SAP user on the destination host hasread permission to the backed-up files as described in the preceding NOTICE.

l Follow the disaster recovery steps to re-create the environment and restore theconfiguration files and BR*Tools logs.

l Perform the following steps on the destination host.

2. For a restore from a DD Boost device over Fibre Channel, ensure that the SAP user hasthe correct device permissions as described in the following EMC articles:

l Fibre Channel Devices with Products using DD Boost in Linux Environment(Document ID dd95007)

l Fibre Channel Devices with Products using DD Boost in Windows Environment(Document ID dd95005)

Use the document ID to search for these articles on EMC Online Support.

Note

This step is not required for a restore through the storage node or a restore from abackup performed with NSM.

3. Ensure that you have configured the NMSAP environment with all the requirements. Verifying the NMSAP software requirements on page 70 provides details.



4. Ensure that you have configured the BR*Tools initialization profile initDBSID.sapfor either util_file or rman_util as the backup device type. Otherwise, use therequired brrestore options or brrecover options.


5. Ensure that you have configured the NMSAP parameter file, initDBSID.utl, for theappropriate parameters:

l The server parameter specifies the hostname of the NetWorker server thatcontains the backup to be restored.

l The client parameter specifies the hostname of the NMSAP host that wasbacked up if that host is different than the destination host.

l The parallelism setting is the same as used to create the backup. Typically,you set the parallelism to the number of target sessions accepted by the devices,which must be equal to or less than the NetWorker parallelism.

l If you restore the SAP Oracle data to a new location and only the top common datadirectory changes but the subdirectory structure remains the same as it was atbackup time, then NSR_RELOCATION_DEST can specify the new top data directoryto improve the restore performance.

The BR*Tools programs determine the new destination directory, for example,brrestore -m object=new_destination.

If the common directory for files being restored, as determined by brrestore,does not match the path set with NSR_RELOCATION_DEST, then the restore ignoresthe NSR_RELOCATION_DEST setting.

l Optionally, NSR_RECOVER_POOL can specify the pool from which to restore thebackup when multiple backup copies (clones) are available. “NSR_RECOVER_POOL” on page 78 on page 83 provides details.

NMSAP backint parameters on page 77 and Examples of brrestore command syntaxand options on page 169 describe these configurations.

6. Ensure that the backup to be restored exists by using an inquire function before youperform a restore operation. For example, to inquire for the latest backup, type thefollowing command:

brrestore -verify [use_dbv | only_conf]

The files are read from the backup media but are not restored.

7. Prepare for the restore operation:

l For a full restore, shut down the Oracle database instance.

l For the restore of a single database object, take the database object offline.

8. Perform the restore operation by using the BR*Tools interfaces.


Performing data restore and recovery 125

NOTICE

The brrestore program used for a restore operation, whether run directly from the

command line or indirectly from the brrecover command or BrGui interface, first

deletes all the original files to be restored before the program runs backint to

restore the backed-up files. You will lose the original files if brrestore or backintfails.

Perform one of the following actions to prevent these issues:

l Restore the files to a different location that does not include any files by using the-m option and specifying the restore destination, for example:

brrestore -m tablespace_name=restore_directoryl Use the brrestore -NFD option to prevent deletion of the original files by

brrestore.

To restore a restarted backup, specify each BR*Tools log produced by the initialbackup and subsequent restart attempts for the brrestore command orbrrecover command. For example, if you started the NMSAP backup and thebackup required two restart attempts before completion, you must run thebrrestore -b backup_log command three times and use the proper log name eachtime. The list of BR*Tools catalog files is logged in both of the following locations:

l backint logs in the nsr/applogs directory

l BR*Tools SAPBACKUP location

To restore data from a directory (nondatabase) backup, use the brrestore -mnon_db command. When you restore the SAP directory data, prevent deletion of theBR*Tools and backint binaries during the restore by performing a relocated restore.For example, use the following command:

brrestore -m non_db=restore_directory

Examples of SAP Oracle Command Options on page 167 contains examples of thebrrestore and brrecover commands and options. The appropriate SAPdocumentation provides details about these commands and other SAP commands.

9. To apply redo logs to recover a database, refer to the appropriate SAP and Oracledocumentation.

Reviewing backup and restore session reports on page 120 provides details aboutbackup and restore log information.

Restarting a restore for files that failed a restoreDuring a restore operation, NMSAP attempts to restore all the requested files even ifsome files fail to restore. When a restore session is complete, you can use the followingprocedure to restart the restore operation for files that failed to restore.

Procedure

1. On the NMSAP host, inspect the restore session log and troubleshoot the errormessages for files that failed to restore. Reviewing backup and restore sessionreports on page 120 provides details.



2. Complete the restore by applying the brrestore -f command to the appropriatebrrestore logs.

Examples:

l To restore the files that failed to restore during the last two restore sessions:

a. Find the restore logs for these two sessions in the SAPBACKUP directory, forexample, reaxdwie.rsb and reasdwap.rsb.

b. Type the following command for these logs:

brrestore -f reaxdwie.rsb, reasdwap.rsbl To restore the files not restored during the last restore session, type the following

command:

brrestore -f lastl To restore files that failed to restore in all the restore sessions that ran in the last

three days, type the following command:

brrestore -f 3

Requirements for disaster recoveryFor a comprehensive disaster recovery plan, you must fully reconstruct the computingenvironment and all the SAP Oracle server (NMSAP host) files associated withmaintaining data. Importance of backups and the backup lifecycle on page 19 describesthe impacts of incomplete protection.

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

l Original operating system media and patches

l Original NetWorker media

l Device drivers and device names

l File system configuration

l IP addresses and hostnames

l NetWorker bootstrap and client index information

You need the NetWorker server bootstrap and client index information to perform disasterrecovery of the NetWorker server, a separate procedure not covered in this chapter.

NOTICE


The EMC NetWorker Disaster Recovery Guide describes how to recover the NetWorker serverand a NetWorker client or storage node from various types of disasters.

Recovering from a disasterTo recover from a disaster, first restore lost Oracle and SAP configuration files and lostBR*Tools backup log files according to the following instructions. After you restore these


Requirements for disaster recovery 127

files, you can perform a database point-in-time recovery or a whole database resetaccording to the instructions in Performing data restore and recovery on page 124.

Restoring the required Oracle and SAP BR*Tools filesThe following procedure is a concise version of the disaster recovery steps described inthe SAP documentation, modified for the specific requirements of NMSAP. You canperform this procedure on the original host or a new host, both referred to as thedestination host.

NOTICE

You can restore only the files for which you have read permission, based on the files’operating system permissions at the time that the files were backed up.

On a UNIX or Linux system, the read permission is associated with the numeric user ID(UID) and group ID (GID), not the username or group name. The UID or GID of the userperforming the restore must match the ID associated with the files at backup time.

Procedure

1. (Optional) To restore the data to a different SAP Oracle host (destination host) thanthe one backed up:

a. On the NetWorker server that contains the backup to be restored:

l Create a generic Client resource for the destination host if one does not yetexist.

l Set the Remote Access attribute in the Client resource of the backed-up NMSAPhost to sap_user@destination_host.

b. Perform the following steps on the new destination host.

2. If the entire SAP Oracle system is lost:

a. Reinstall all the required software components described in NMSAP andassociated software on page 31.

b. Reconfigure the SAP data layout, such as the SAPDATA_HOME directory and itssubdirectories, to the same state as before the disaster.

3. Load the storage volumes with the required Oracle and SAP configuration files and theBR*Tools backup log files on the NetWorker storage node.

4. Configure the BR*Tools profile file, initDBSID-dr.sap, and NMSAP parameter file,initDBSID-dr.utl, for recovery on the destination host.

Ensure that the NMSAP configuration file contains at least the following parameters:

l The server parameter specifies the hostname of the NetWorker server thatcontains the backup to be restored.

l The client parameter specifies the hostname of the NMSAP host that wasbacked up, if that host is different than the destination host.

5. On the destination host, start BR*Tools or BrGui and follow the onscreen instructionsto perform a disaster recovery of profiles and logs.

For example, the following steps show how to use BR*Tools for disaster recovery ofprofiles and logs:

a. In the brtools menu, select Restore and Recovery and then Disaster recovery.



b. On the page BRRECOVER options for disaster recovery, set the location of theBR*Tools profile file and the NMSAP configuration file for use by brrecover.

Note

If you are restoring the original BR*Tools profile or NMSAP configuration file,ensure that the files used for the disaster recovery have different names or arestored in a different location than the original files to be restored.

c. On the page Device type for restoring profiles and log files from BRBACKUP |BRARCHIVE backup, select Backup utility.

d. On the page Parameters for restoring profiles and log files from BRBACKUPbackup utility, specify the files to restore as they appear in the NetWorker clientindex.

e. On the page Restore of profiles and log files from BRBACKUP backup, select thecomponents that you want to restore.

The SAP documentation provides more details about disaster recovery.

Recovering a SAP Oracle database after disasterAfter you restore the correct SAP BR*Tools profiles and logs on the NMSAP host, followthe normal BR*Tools recovery procedure to perform database point-in-time recovery ordatabase reset.

Performing data restore and recovery on page 124 provides the procedure to recover aSAP Oracle database.

The SAP documentation provides more details about database recovery.


Recovering a SAP Oracle database after disaster 129



CHAPTER 6

SAP Oracle in Cluster and RAC Environments


l SAP Oracle cluster systems................................................................................. 132l Oracle RAC systems.............................................................................................135

SAP Oracle in Cluster and RAC Environments 131

SAP Oracle cluster systemsA cluster environment consists of two or more linked hosts with shared storage, calledcluster nodes, which work together to provide a resilient database processing platform.

In an active-passive cluster, some nodes are active and others are standby, waiting totake over the processing when an active node fails. A user can connect to the cluster byusing a virtual cluster name or IP address, regardless of which nodes are active. Younormally implement active-passive clusters for high availability solutions or to improvecomputer performance.

An Oracle Real Application Cluster (RAC) system provides a single database that can beaccessed by multiple Oracle instances simultaneously as an active-active applicationcluster configuration.

This section describes the procedures for active-passive cluster configurations. OracleRAC systems on page 135 describes the procedures for Oracle RAC configurations.

Client parameter setting for cluster systemsDuring an NMSAP backup, the NetWorker server creates entries about the backed-up datain the online client file index. During an NMSAP restore, you can retrieve the data by firstsearching the client file index.

The client parameter provides the following information to the NetWorker server:

l During a backup, the name of the NetWorker client whose index file is used to recordthe backup information.

l During a restore, the name of the NetWorker client whose index file is used to searchfor the data to be restored.

If you do not set the client parameter, NMSAP uses the name of the local host (clusternode), not the virtual cluster host, for the operations during cluster backups and restores.Because the local host name can change over time and cause confusion and errors, usethe virtual cluster name for the client parameter.

The value of the client parameter (either the default value or an explicitly definedvalue) used for a backup must be the same as the value of the client parameter usedfor the restore of that backup.

Set the client parameter to the virtual cluster hostname in a cluster environment toenable the restore of backup data no matter which cluster node was used during thebackup.

NSR_PHYSICAL_HOST_LICENSE setting for cluster systemsBy default, NMSAP is licensed per virtual cluster host and you require a license for eachvirtual cluster hostname that is backed up.

Set the parameter NSR_PHYSICAL_HOST_LICENSE=TRUE to enforce that NMSAP islicensed per cluster node, not per virtual cluster hostname.

NSR_PHYSICAL_HOST_LICENSE on page 83 describes the parameter.



Configuring scheduled backups in a cluster with the wizardYou can use the wizard or nonwizard method to configure a scheduled backup with theBackint interface in a cluster. This topic describes the configuration procedure with thewizard.

Procedure

1. Ensure that the NetWorker server is remote and not a part of the cluster environment.

2. Ensure that you have installed NMSAP on a local disk on all the physical nodes of thecluster designated to perform a backup.

3. Follow the procedure for Configuring scheduled backups with the wizard on page 74,keeping in mind the following cluster-specific requirements:

l On the Specify the Client Name page, type the name of the virtual host for thecluster and select the Virtual Client checkbox.

l On the Specify Log File Locations and Additional Options page, in the AdvancedOptions table:

n Set the client parameter to the virtual hostname. Client parameter setting forcluster systems on page 132 provides details.

n Set the NSR_PHYSICAL_HOST_LICENSE parameter to specify the correct NMSAPlicensing, if required. NSR_PHYSICAL_HOST_LICENSE setting for clustersystems on page 132 provides details.

l On the Select the NetWorker Client Properties page, add sap_user@physical_hostto the Remote Access field for each physical host in the cluster.

Results

With the previous settings, the wizard performs the following actions:

l Creates a NetWorker Client resource for the virtual host with the usual settings forscheduled backups and the following additional settings:

n The Backup Command attribute contains -c virtual_client_name.

n The Remote Access attribute contains the sap_user@physical_host entries.

l Creates a generic NetWorker Client resource (with the Save Set attribute set to All andnot assigned to a group) for each physical node if the resource does not already exist.

l Grants access (ACL rights) to the Lockbox resource for the virtual host to system/rootuser and sap_user on each physical host.

Note

If additional users need ACL rights to the Lockbox, you can add the users to theLockbox resource directly in NMC.

Configuring scheduled backups in a cluster without the wizardThis topic describes the configuration procedure without the wizard.

Procedure

1. Ensure that the NetWorker server is remote and not a part of the cluster environment.

2. Ensure that you have installed NMSAP on a local disk on all the physical nodes of thecluster designated to perform a backup.


Configuring scheduled backups in a cluster with the wizard 133

3. Ensure that the configuration file and parameter file are stored in the same locationon each physical node or on a shared disk.

4. Follow the procedure for Configuring scheduled backups without the wizard on page76 to create the configuration for the virtual host, keeping in mind the followingcluster-specific requirements:

l Create a generic NetWorker Client resource (with the Save Set attribute set to Alland not assigned to a group) for each physical node if the resource does notalready exist.

l In the Remote Access attribute of the Client resource that you create for the virtualcluster host, add sap_user@physical_host for each node that requires access tothe backup.

Note

You do not need to add -c virtual_client_name to the Backup Command attribute.

l Set the required parameters in the initDBSID.utl file:

n Set the client parameter to the virtual client hostname. Client parametersetting for cluster systems on page 132 provides details.

n Set the NSR_PHYSICAL_HOST_LICENSE parameter to specify the correct NMSAPlicensing, if required. NSR_PHYSICAL_HOST_LICENSE setting for clustersystems on page 132 provides details.

Configuring manual backups in a clusterTo configure an NMSAP manual backup in a cluster, follow the instructions for configuringa scheduled backup without the wizard as described in Configuring scheduled backupsin a cluster without the wizard on page 133.

The only difference in the manual backup configuration procedure is that you mayconfigure a generic NetWorker Client resource for the virtual host.

Configuring Avamar deduplication backups in a clusterProcedure

1. Follow these procedures:

l Configuring scheduled Avamar deduplication backups with the wizard on page103 or Configuring scheduled Avamar deduplication backups without wizard onpage 104 or Configuring manual Avamar deduplication backups on page 104 forthe virtual cluster host

l Configuring scheduled backups in a cluster with the wizard on page 133 or Configuring scheduled backups in a cluster without the wizard on page 133 or Configuring manual backups in a cluster on page 134

2. Ensure that there is at least one NetWorker Client resource enabled for deduplicationbackups, which corresponds to the client host that is set either on the Specify theClient Name wizard page or in the client parameter in the initDBSID.utl file.

3. For scheduled backups, ensure that the NetWorker Client resource for the virtual hostis part of the NetWorker backup group and is enabled for deduplication.



Configuring Data Domain deduplication backups in a clusterFollow these procedures:

l Configuring scheduled backups in a cluster with the wizard on page 133 or Configuring scheduled backups in a cluster without the wizard on page 133 or Configuring manual backups in a cluster on page 134

l Configuring Client Direct with DD Boost backups on page 106 or Configuring storagenode with DD Boost backups on page 108 for the virtual cluster host

Configuring probe-based backups in a clusterFollow these procedures:

l Configure a scheduled backup in the cluster according to Configuring scheduledbackups in a cluster with the wizard on page 133 or Configuring scheduled backupsin a cluster without the wizard on page 133.

l Configure the probe-based backup according to Configuring a probe-basedbackup on page 110. Associate the Probe resource with the Client resource for thevirtual client host.

Converting client-side configurations to wizard settings in a clusterTo convert a scheduled backup configuration that uses configuration files to the wizardconfiguration in a cluster:

Procedure

1. Follow the instructions for Converting client-side configurations to wizardconfigurations on page 75. You can run the nsrsapadm conversion utility from any ofthe physical nodes configured for backup.

2. During the conversion, when nsrsapdm prompts for names of users to add to theLockbox resource, specify the names of SAP operating system users on each physicalnode that will be used for the backup.

Note

If you do not grant the Lockbox ACL rights during the conversion, you can add the userlater by using NMC to edit the Lockbox resource for the cluster virtual host.

Restoring data in a clusterTo restore data backed up from a shared disk of a virtual client:

Procedure

1. Set the client parameter in the NMSAP parameter file, initDBSID.utl, to thevirtual client that holds the NetWorker index entries for the backup to be restored.

2. Follow the instructions for Performing data restore and recovery on page 124.

Oracle RAC systemsAn Oracle Real Application Cluster (RAC) is an active-active application clusterenvironment for parallelism and high availability. A node in an Oracle RAC system is a


Configuring Data Domain deduplication backups in a cluster 135

physical host or virtual host. An Oracle instance is a memory structure and a group ofOracle Server processes running on a node.

An Oracle database comprises datafiles used by the Oracle instances. All the instancesshare the same datafiles and control file. Each instance must have its own redo log filesand its own archived redo logs.

A RAC system enables multiple Oracle instances across multiples nodes to access thesame Oracle database simultaneously. Oracle RAC is based on a cluster softwareinfrastructure that provides concurrent access to the same storage and the samedatafiles from all the nodes in the cluster. All the database files reside on shared disks.

Configuring Oracle RAC backupsThe SAP documentation provides details about RAC setup. Ensure that you meet thefollowing requirements for Oracle RAC backups on a single backup node with BR*Toolsand NMSAP:

l One of the Oracle RAC instances, set as the dedicated database (DDB) instance, isused to perform all the database administration tasks. You must be able toadminister all the RAC instances from the DDB instance.

l You must create the BR*Tools log directories, such as SAPBACKUP and SAPARCH, ona shared file system.

l You must correctly configure Oracle SQL Net.l You must set the required parameters, such as parallel_instances and

db_services, in the SAP initialization file, initDBSID.sap, located on the DDBinstance.

Configuring backups with BackintAll the Oracle RAC backups performed with BR*Tools and NMSAP Backint run on the DDBinstance. You must install BR*Tools and NMSAP on that DDB instance host.

The backup configuration of the DDB instance is the same as for a stand-alone system. Configuration for NMSAP Oracle Operations on page 69 provides details.

The archived redo logs from all the instances are stored in a common shared location.These logs are backed up by the brarchive program, which is started on only one RACinstance, usually the DDB instance.

For a probe-based backup, you must configure a RAC backup as usual. Complete theprobe-based backup configuration according to Configuring a probe-based backup onpage 110. Associate the Probe resource with the Client resource configured for thescheduled backup.

Note

In a RAC environment, the LOG_THRESHOLD parameter setting in the Probe resource mustspecify the total number of logs generated by all the RAC nodes in a cluster since the lastprobe-based backup.

Configuring backups with RMANThe SAP documentation provides details about RAC setup. Ensure that you meet thefollowing requirements for Oracle RAC backups performed as concurrent RMAN backupson multiple nodes:

l You must specify the RMAN utility for the backups and restores as described in Choosing either backint or RMAN as the backup and restore utility on page 72.



l You must install NMSAP on each RAC node host to be used for backups or restores.

l All the nodes included in a backup must use the same type of network connection,for example, a direct connection to a Data Domain device for a Client Direct backup orFibre Channel access for a DFC backup.

l You must select one node as the client that will store all the backup entries for theRAC system in the NetWorker client file index. Select either one of the physical nodesin the RAC system or the virtual RAC host.

l You must create a generic NetWorker Client resource for each RAC node host to beused for backups and restores.

l For scheduled backups, you must create an NMSAP specific Client resource for thehost that will store the backup index entries.

l You must set the required parameters in the BR*Tools initialization profile,initDBSID.sap:

n To distribute the backup load to multiple RAC nodes, set the rman_rac_distparameter:

rman_rac_dist = yesn Set the rman_channels parameter to specify the number of concurrent backup

streams.When rman_rac_dist is set to yes, set rman_channels to a value greaterthan 1, preferably a multiple of the number of RAC nodes. For example, set thefollowing value for a RAC system with two nodes to run two backup streams oneach RAC node:

rman_channels = 4n In the rman_send parameter setting, set the NSR_CLIENT parameter to the

hostname of the client that will store the backup index entries. For example:

rman_send="NSR_ENV=(NSR_CLIENT=vRAChost)"Specifying RMAN as the backup and restore utility on page 73 provides details onsetting parameters in the BR*Tools initialization profile.

l You must set the client parameter in the backint parameter file,initDBSID.utl, to the same value as the NSR_CLIENT parameter in therman_send setting. NMSAP backint parameters on page 77 provides details on thebackint parameter file.

Note

This client parameter setting ensures that the BR*Tools metadata is stored in the

same client index as the backup data. The backint program backs up the metadata

during an RMAN backup.

l For distributed RAC operations (rman_rac_dist = yes), you must connect to thedatabase with a specific database username, for example, by using the -usystem/password option. The database user must have the SAPDBA, SYSDBA, andSYSOPER roles.

l For a probe-based backup, you must configure a RAC backup as usual. Complete theprobe-based backup configuration according to Configuring a probe-basedbackup on page 110. Associate the Probe resource with the Client resourceconfigured for the scheduled backup.


Configuring backups with RMAN 137

Note

In a RAC environment, the LOG_THRESHOLD parameter setting in the Probe resourcemust specify the total number of logs generated by all the RAC nodes in a clustersince the last probe-based backup.

Restoring Oracle RAC dataTo restore Oracle RAC data, run the BR*Tools commands, such as brrestore orbrrecover, on the DDB instance.

You can restore all the required archived redo logs with a single brrestore command.You can specify the instance name and which logs must be restored with thebrrestore -a command.

For example, the following command restores the archived logs with sequence numbersfrom 40 to 50 that belong to the instance ORA2:

brrestore -a 40-50,ORA2



CHAPTER 7

NMSAP Oracle Snapshot Backups and Restores


l Snapshot operations with NetWorker Snapshot Management............................. 140l Types of NSM backups........................................................................................ 141l Types of NSM restores.........................................................................................143l Backup and restore data flows with NSM.............................................................143l Configuring NMSAP snapshot backups with NSM................................................ 144l Testing NMSAP backups and restores with NSM.................................................. 151l Example parameter settings for NSM backups.....................................................152l Reviewing the NMSAP NSM backup records.........................................................153

NMSAP Oracle Snapshot Backups and Restores 139

Snapshot operations with NetWorker Snapshot ManagementNetWorker Snapshot Management (NSM) backups and restores provide snapshot-basedprotection and availability of data on supported types of primary storage, for example,EMC VNX Block (CLARiiON) or EMC VMAX (Symmetrix). NMSAP works with NSM to providethis protection for SAP Oracle data.

Note

With NetWorker release 8.1 or later, the NSM feature integrates and replaces thePowerSnap Modules. NSM is available as part of the NetWorker client software.

The EMC NetWorker Module for SAP Release 8.2 Release Notes describes the supportedsoftware and the primary storage platforms.

NSM supports scheduled backups only, not manual (client-initiated) backups. The NSMdocumentation provides details.

Note

NMSAP snapshot backups with NSM do not use the BR*Tools disk-volume backupinterface introduced in BR*Tools 7.10.

The following table lists the required software components for NMSAP snapshot backupsand restores with NSM.

Table 15 Typical configuration for NMSAP snapshot operations with NSM

Computer or device Required software or configuration

Oracle production server host Oracle server, SAP BR*Tools, NetWorker client, NMSAP

Proxy client host (mount host) NetWorker client, NetWorker storage node

Storage array Storage array that NMSAP supports with NSM, for example, VMAXor VNX Block

NetWorker server host NetWorker server, NetWorker storage node, NetWorker client

The following figure shows the basic NMSAP environment for NSM snapshot backups andrestores.



Figure 1 Software used in the NMSAP environment for NSM snapshot backups and restores

S5

Oracle Server host

Database server

NetWorker client

NMSAP

Primary

storage array

(for example,

VMAX or

VNX Block)

NetWorker

server

LAN

Snapshots

Primary storage

LUNs/volumes S1

S4

S2

S3

SAN

NetWorker storage node

Mount host (proxy client host)

NetWorker client

Conventional

Storage

Types of NSM backupsNMSAP supports the types of NSM backups described in the following table.

Table 16 Supported types of NSM backups

Backup type Snapshotretention

Location of stored data

Snapshot backup (instant backup) onpage 142

Permanent Snapshot on primary storage


Types of NSM backups 141

Table 16 Supported types of NSM backups (continued)

Backup type Snapshotretention

Location of stored data

Rollover-only backup (immediate livebackup) on page 142

Temporary Conventional backup media only

Snapshot and rollover backup (deferredlive backup) on page 142

Permanent Both primary and conventionalstorage

The Snapshot Policy attribute in the NetWorker Group resource specifies the NSM backuptype. Configuring Group resources for NSM backups on page 146 provides details.

Snapshot backup (instant backup)A snapshot backup, formerly known as an instant backup, creates a permanent point-in-time (PIT) copy or snapshot of SAP Oracle data. The snapshot backup stores the snapshoton the primary storage system where it is available to NMSAP for performing snapshotrestores or rollbacks. You can schedule a snapshot backup to occur many times in asingle 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. You mustconfigure the snapshot policy to control the lifecycle of the snap set. This policy specifiesthe frequency of snapshot backups and how long snapshots are retained before beingrecycled. Configuring Snapshot Policy resources for NSM backups on page 146 providesdetails.

Rollover-only backup (immediate live backup)A rollover-only backup, formerly known as an immediate live backup, is also called aserverless snapshot backup. For this type of backup, NSM creates a temporary snapshotand immediately backs up the snapshot to conventional storage. The software thenautomatically deletes the snapshot from the primary storage so that NMSAP cannot usethe snapshot for performing snapshot restores or rollbacks.

NSM can use a proxy client host, also called the mount host, to move the snapshot datato conventional storage. This host is typically separate from the Oracle server host. Theuse of a proxy client as a secondary host reduces the demand on the Oracle server host.The proxy client or mount host is typically a NetWorker storage node.

Snapshot and rollover backup (deferred live backup)A snapshot and rollover backup, formerly known as a deferred live backup, creates apermanent snapshot and uses NSM to back up the snapshot to conventional storage. Thepermanent snapshot is retained on the primary storage and is available to NMSAP forperforming snapshot restores or rollbacks for the period specified by either of thefollowing policies:

l Snapshot expiration policy

l Retain Snapshots attribute of the snapshot policy

Similar to a rollover-only backup, NSM can use a proxy client host, also called the mounthost, to roll over the backup to conventional storage.



Types of NSM restoresNMSAP supports the types of NSM restores described in the following table.

Table 17 Supported types of NSM restores

Restore type Data retrieved from

Snapshot restore (instant restore) on page 143 Mounted snapshot

Restore from rollover (restore from conventionalstorage) on page 143

Conventional storage

Rollback on page 143 Unmounted snapshot, entirely restored tosource location

The RESTORE_TYPE_ORDER parameter in the user-defined NSM configuration filespecifies the type of NSM snapshot restore. Configuring the NSM parameters on page149 provides details.

Snapshot restore (instant restore)A snapshot restore, formerly known as an instant restore, mounts a snapshot that wascreated by a snapshot backup. This process enables NMSAP to retrieve the saved data ora subset of the saved data. This type of restore requires a minimal amount of time.

Restore from rollover (restore from conventional storage)A restore from rollover, formerly known as a restore from conventional storage, restoressnapshot data (saved to the conventional storage system) from the storage system to theSAP Oracle server.

Note

The restore of snapshot data from the conventional storage requires the use of NSM.

RollbackA rollback restores the entire snapshot to the source location by using the hardware’sparticular capabilities. NSM does not support relocation during rollbacks. To determine ifa rollback is supported on a specific type of hardware, refer to the NSM documentation.

NOTICE

Rollbacks are destructive because rollbacks overwrite the entire contents of a snapshotunit, such as a volume or disk.

Backup and restore data flows with NSMDuring an NSM backup, the NMSAP backint process interacts with the NSM processesto create the PIT snapshot and backs up the snapshot to the NetWorker server.

A snapshot backup with NSM includes the following processes.


Types of NSM restores 143

Procedure

1. At the time of a scheduled snapshot backup, the NetWorker server starts the NMSAPnsrsapsv process, which runs the SAP brbackup command.

2. The SAP brbackup program runs the NMSAP backint program, which thencommunicates with NSM.

3. On the SAP Oracle server host, NSM takes a point-in-time snapshot of the Oracle dataon the primary storage, which then becomes available to the NSM mount host.

4. If the backup type has a rollover, NSM on the mount host moves the SAP Oracle datafrom the snapshot on the primary storage to the NetWorker storage node, whichstores the data on conventional storage. If required, NSM deletes the snapshot.

5. At the end of the NSM backup, the NetWorker server updates the online client indexand media database with information about the backup.

Results

The EMC NetWorker Administration Guide describes the NetWorker server and clientservices.

The following figure illustrates the data flow of NSM snapshot backups and restores in anNMSAP environment with NetWorker client release 8.1 or later. The NSM feature providesthe snapshot backup and restore functionality as part of the NetWorker client software.

Figure 2 NSM backup and restore data flow with NMSAP

Configuring NMSAP snapshot backups with NSMYou must configure the required NetWorker resources and parameters for NMSAPsnapshot backups with NSM by using either the configuration wizard or the nonwizardmethod.

The NSM documentation describes the NSM configuration procedures.



Procedure

1. Configure the SAP Oracle database layout to position the datafiles on the primarystorage that NSM supports.

Note

Do not locate the Oracle database control file or any SAP directories, except sapdatan,on the same volume (snapshot unit) as the datafiles that will be backed up throughNSM backups. You cannot back up specific types of Oracle files, such as control files,through an NSM backup. This is an Oracle constraint. The Oracle documentation forthe particular Oracle server version describes the Oracle file types that do not supportsnapshot backups.

2. Ensure that you have installed both NMSAP and the required NetWorker client(including the NSM feature) according to the instructions in the followingdocumentation:

l EMC NetWorker Module for SAP Installation Guide

l NetWorker documentation

3. Ensure that you have installed the required NetWorker client on the mount host.

4. Review Types of NSM backups on page 141 to determine which type of snapshotbackup to perform.

5. Ensure that you have completed the basic database server configuration andNetWorker configuration according to Configuration road map for NMSAP Oracleoperations on page 70. You must configure the required NetWorker Server and otherresources. Configure any required Snapshot Pool resources and Device resources forthe snapshot backups:

l Configuring Snapshot Pool resources for NSM backups on page 146

l Configuring Device resources for NSM backups on page 146

You must configure the Client and Snapshot Policy resources only if you use thenonwizard method. If you use the configuration wizard, then the wizard creates theseparticular resources.

6. For a snapshot backup configuration through the wizard, follow the information in Configuring scheduled backups with the wizard on page 74 except skip any sentencethat includes a cross-reference. The wizard is the recommended method of snapshotbackup configuration.

On the Select the Backup Application Type page in the wizard, select the checkboxthat enables snapshot management for the selected SAP application.

Note

If you specify an NMSAP parameter file, initDBSID.utl, as a template in the

wizard, the file must not include the ps_opaque_pfilename parameter setting.

7. For a snapshot backup configuration through the nonwizard method, complete thefollowing steps:

a. For online database backups, complete one of the following settings:

l In the initDBSID.sap file, set backup_device_type=util_file_online.

l In the nsrsapsv.cfg file, set the BR_EXEC parameter’s CLI option to-d util_file_online.


Configuring NMSAP snapshot backups with NSM 145

Note

If you set backup_device_type to util_file, the database stays in backup mode forthe duration of the backup and generates a larger number of transaction logs.

b. Configure the required NetWorker resources:

l Configuring Snapshot Policy resources for NSM backups on page 146

l Configuring Group resources for NSM backups on page 146

l Configuring Client resources for NSM backups on page 147

c. Configure the required parameters:

l Configuring the NMSAP parameters for NSM operations on page 147

l Configuring the NSM parameters on page 149

8. If you are not using the configuration wizard, complete any additional configurationprocedures:

l For a Client Direct snapshot backup to an AFTD, follow the information in Configuring Client Direct backups to AFTD on page 109 except skip the step aboutconfiguring a scheduled backup.

l For a Client Direct snapshot backup to a DD Boost device, follow the information in Configuring Client Direct with DD Boost backups on page 106 except skip theconfiguration instructions in the second column of Table 11 on page 107.

Configuring Snapshot Pool resources for NSM backupsConfigure a separate NetWorker Snapshot Pool resource to support NMSAP snapshotbackups with NSM. NSM stores the metadata from the snapshot in this pool.

Use the same configuration method as for a regular, nonsnapshot NMSAP backup, exceptthe specified backup device must be a file or advanced file type.

The pool name must be specified in the Snapshot Pool attribute of the NetWorker Groupresource.

Configuring Device resources for NSM backupsConfigure a Device resource for each conventional storage device to be used duringNMSAP Oracle backups to conventional storage. You must mount the devices.

Configuring Snapshot Policy resources for NSM backupsIn the nonwizard method, configure a NetWorker Snapshot Policy resource to performsnapshot backups or backups that include a rollover with NMSAP and NSM. Specify apreconfigured policy or create a policy.

Configuring Group resources for NSM backupsIn the nonwizard method, configure a NetWorker Group resource for NMSAP snapshotbackups with NSM. The following table provides typical settings.

Note

The NetWorker scheduled backup group must start an NSM backup. You cannot schedulean NSM backup through the SAP Computing Center Management System (CCMS).



Table 18 Group resource attributes for NSM backups

Attribute name Attribute setting

Snapshot True.

Snapshot Policy Daily or other customized policy. This attribute setting specifies the NSMbackup type.

Snapshot Pool A Pool resource dedicated to the storage of snapshot operation metadata. Usefile-type volume devices instead of tape.

Start Time Set the start time in relation to the Number of Snapshots attribute for thesnapshot policy: (Interval x Number of Snapshots) must be less than or equal to (24:00 h - StartTime).

Interval Set the interval in relation to the Number of Snapshots attribute for thesnapshot policy.

Configuring Client resources for NSM backupsIn the nonwizard method, configure the NetWorker Client resource for the NMSAPsnapshot operations with NSM as described in Configuring the scheduled backupresources without the wizard on page 97. Associate the Client resource with the snapshotGroup resource.

The snapshot browse policy and retention policy (of the Group resource specified for theClient resource) define the lifecycle of a snapshot.

The Browse Policy attribute in the Client resource applies only to the NetWorker client fileindex entries for NSM backups to conventional storage.

The Retention Policy attribute in the Client resource applies only to the NetWorker mediadatabase entries for NSM backups to conventional storage.

Note

NMSAP appends “:PS:” to the save set name during an NSM backup to identify NSM savesets.

Configuring the NMSAP parameters for NSM operationsThe following table describes the NMSAP parameters set in the parameter fileinitDBSID.utl for NSM backups or restores. The first example in Example parametersettings for NSM backups on page 152 provides a basic example configuration for NSMbackups.

Table 19 NMSAP NSM parameters in parameter file initDBSID.utl

NMSAP NSM parameter Description Default and valid values

ps_backup_modeps_archive_mode

ps_restore_mode

ps_inquire_mode

Each of these NSM functional modes is enabled if set to TRUE.Normally, all the modes are set together to either all TRUE orall FALSE, except ps_archive_mode=FALSE and all others=TRUE. Do not use any other settings except for diagnosticpurposes.

l FALSE (default)

l TRUE


Configuring Client resources for NSM backups 147

Table 19 NMSAP NSM parameters in parameter file initDBSID.utl (continued)


ps_opaque_pfilename Full pathname of a configuration file that contains NSMspecific parameters. Configuring the NSM parameters on page149 describes how to set the parameters.

l Undefined (default)

l Full pathname of theNSM configuration file

ps_exclude_backup_bi_run_numsps_exclude_archive_bi_run_nums

Specifies which backint runs to exclude from NSM

processing, typically run number 2. Each brbackup or

brarchive session invokes the backint process to run

twice in sequence.

l Run 1 backs up the Oracle data.

l Run 2 backs up the Oracle database initialization fileinitDBSID.ora, and the BR*Tools initialization profile

initDBSID.sap and catalog files.

Files backed up during run 2 do not require NSM processingand can be backed up by conventional processing withoutNSM, thereby saving valuable snapshot disk resources.

Use the following starting values:ps_exclude_backup_bi_run_nums=2ps_exclude_archive_bi_run_nums=1;2


l Numeric value of one ormore valid backint run

numbers to exclude, eachseparated by a semicolon(;)

ps_exclude_backup_pathsps_exclude_archive_paths

Specifies individual NSM files to exclude from NSMprocessing and back up with conventional nonsnapshotprocessing instead. NSM files are those on a snapshot-capable file system that NetWorker is aware of.Whenever possible, set the ps_exclude_xxx_bi_run_numsparameters instead of the ps_exclude_xxx_paths parameters.

Note

l On Microsoft Windows systems, support of wildcardcharacters is limited, and a single trailing * denotessimple case-insensitive prefix matching. If you set theparameter to a value of: X:\*, or X:\db*, or X:\DB01\*, then X:\DB01\FOO.DBF is excluded from

NSM backups.

l On UNIX systems, wildcard support follows the standardshell support for full file pathnames. For example, if youset the parameter to a value of: /db01/foo.*, or /db??/*.dbf, the file /db01/foo.dbf is excluded.

However, if you set the parameter to /db*, the file is not

excluded.


l Full pathnames of thefiles to be excluded, eachseparated by a semicolon(;). You can use wildcardcharacters as describedin the Note. Use valuesbased on the actual filename that BR*Toolspasses to backint.

ps_ps_before_nonps Specifies whether to perform all NSM processing beforeconventional processing without NSM. This helps preventpotential resource conflicts.Setting this parameter to FALSE enables concurrentprocessing of all files set for backup, archive, or restore.

l TRUE (default)

l FALSE



Table 19 NMSAP NSM parameters in parameter file initDBSID.utl (continued)


Note

Use the FALSE value at your discretion.

ps_group_objs Specifies whether to group all session files for each NSMoperation, such as prepare or sync, snapshot or split, save orrestore, or cleanup.Setting this parameter to TRUE improves NMSAP performancefor certain database disk or file system configurations,particularly if large numbers of files are processed byBR*Tools and NSM with util_file_online.

However, grouping files also reduces the potential parallelismfor certain backup and restore suboperations, which in turncan reduce performance.

l TRUE (default)

l FALSE

Configuring the NSM parametersYou can set the NSM parameters in the NSM configuration file for backups or restores, orin the Application Info attribute of the NetWorker Client resource for backups only.

You must specify the NSM configuration file by its complete file pathname, forexample, /nsr/res/nmsapps.cfg, in the ps_opaque_pfilename parameter in theNMSAP parameter file, initDBSID.utl.

Some parameters in the NSM configuration file have corresponding parameters in theNMSAP parameter file, initDBSID.utl, from which they inherit their values. Normally,you should not specify values for these parameters in the NSM configuration file. If youset a corresponding parameter in the NSM configuration file, it overrides the equivalentparameter in the NMSAP parameter file. Table 7 on page 78 lists the parameters in theNMSAP parameter file.

You must list each parameter in the configuration file or the Application Info attribute ona separate line, in the following format:

parameter_name=parameter_value

where:

l parameter_name is the parameter name, such as NSR_SNAP_TYPE.

l parameter_value is the parameter value, such as emcclar.

The following table lists some common NSM parameters. The NSM documentationprovides a complete list of NSM parameters.

Table 20 Common parameters in NSM configuration file, nmsapps.cfg

NSM parameter Description Default and valid values

NSR_CHECKSUM Corresponds to the checksum parameter in Table 7 onpage 78.

Setting of NMSAP checksumparameter (default).


Configuring the NSM parameters 149

Table 20 Common parameters in NSM configuration file, nmsapps.cfg (continued)


NSR_CLIENT Corresponds to the client parameter in Table 7 on page78.

Note

If set, the NSR_CLIENT parameter value must match theclient parameter value.

Setting of NMSAP clientparameter (default).

NSR_COMPRESSION Corresponds to the compress parameter in Table 7 onpage 78.

Setting of NMSAP compressparameter (default).

NSR_DATA_MOVER Mandatory if the NSM backup uses a mount host that isdifferent from the NSM client host (NSR_CLIENT).Specifies the hostname or IP address of the NSM mounthost.


l Valid hostname or IPaddress.

NSR_DATA_VOLUME_POOL Corresponds to the pool parameter in Table 7 on page78.

Setting of NMSAP poolparameter (default).

NSR_MAX_STREAMS Optional. Specifies the maximum number of restorestreams.

l Setting of the NMSAPpallelism parameter(default).

l An integer value.

NSR_PS_DEBUG_LEVEL Optional. Specifies the NSM debug level. l 0 (default, no debugging).

l 0 to 9.

NSR_PS_SAVE_PARALLELISM Optional. Specifies the maximum number of concurrentbackup save streams on the NSM client host.

l Setting of the NMSAPpallelism parameter(default).

l An integer value.

NSR_SAVESET_BROWSE Corresponds to NSR_SAVESET_BROWSE in Table 7 onpage 78.

Note

Applies only to data stored on conventional storage asdescribed in Configuring Client resources for NSMbackups on page 147.

Setting of NMSAPNSR_SAVESET_BROWSEparameter (default).

NSR_SAVESET_RETENTION Corresponds to NSR_SAVESET_RETENTION in Table 7 onpage 78.

Note

Applies only to data stored on conventional storage asdescribed in Configuring Client resources for NSMbackups on page 147.

Setting of NMSAPNSR_SAVESET_RETENTIONparameter (default).

NSR_SNAP_TYPE Optional. Specifies snapshot platforms.If the value is unspecified, NSM inquires the BRC serviceto choose the most appropriate value.

The value must be lowercase,for example:

l symm-dmx for VMAX



Table 20 Common parameters in NSM configuration file, nmsapps.cfg (continued)


l emcclar for VNX Block

RESTORE_TYPE_ORDER Optional. Specifies the type of restore to perform.If you specify multiple values, the system attempts eachtype of restore in the order specified until a restoreoperation is successful.

Note

For NMSAP, a rollback operation terminates if one of thefollowing conditions is true:

l You have specified brrestore file relocation.

l Nonrequested files exist in the brrestore-

requested file systems. These files could becomecorrupted after a rollback.

l pit:conventional (default)

One or more of the followingvalues is supported, with eachvalue delimited from the othersby a colon (:):

l pit—Specifies a snapshot(PIT) restore.

l conventional—Specifies arestore from conventionalstorage media.

l rollback—Specifies arollback restore from a PITcopy.

Testing NMSAP backups and restores with NSMYou can test NMSAP backups and restores with NSM by running the appropriatecommands.

Before you test NMSAP backups and restores with NSM, ensure that you have configuredthe required NetWorker resources and NMSAP configuration files as described in Configuring NMSAP snapshot backups with NSM on page 144.

Procedure

1. Test the NMSAP NSM backups by running the savegrp command either from theNMC GUI program or from the command line on the NetWorker server host:

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 an NSM disk.

If you encounter a problem, check the NMSAP backint log and NSM log. Thefollowing problems are common:

l NSM does not manage the target file.

l The NSM daemon or service, nsrpsd, is not running.

l The NSM configuration file, symm.res, needs to be modified. The file is used onlyin VMAX storage configurations.

l The ps_xxx_mode or ps_exclude_xxx parameter is set to exclude a file from NSMprocessing, where xxx is described in Table 19 on page 147.

l The ps_opaque_pfilename file needs to be modified.


Testing NMSAP backups and restores with NSM 151

For additional troubleshooting, set the following parameters in the initDBSID.utlfile to generate diagnostic logs for EMC Customer Support:

debug_level = 9nsr_debug_msg = TRUE

To obtain NSM debug logs, set the following parameter in the ps_opaque_pfilenamefile:

NSR_PS_DEBUG_LEVEL=92. Run a pre-restore inquiry with the following command:

brrestore -verify3. 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 that NSMsupports.

Example parameter settings for NSM backupsThe following examples include settings in the NMSAP parameter file, initDBSID.utl,and the NSM configuration file, nmsapps.cfg, for NMSAP backups and restores withNSM.

The following example provides typical settings in the backint parameter fileinitDBSID.utl:

ps_backup_mode = TRUEps_archive_mode = FALSEps_restore_mode = TRUEps_inquire_mode = TRUEps_exclude_backup_bi_run_nums = 2ps_exclude_archive_bi_run_nums = 1;2ps_exclude_backup_paths = (left blank)ps_exclude_archive_paths = (left blank)ps_ps_before_nonps = TRUEps_group_objs = TRUEps_opaque_pfilename = /nsr/res/nmsapps_backup.cfg

The following examples provide typical settings in the NSM configuration file. The NSMparameters for specific primary storage are set in the /nsr/res/nmsapps_backup.cfg file, which is specified with the ps_opaque_pfilenameparameter in the NMSAP parameter file:

l For VNX Block:

NSR_DATA_MOVER=datamover.emc.comNSR_SNAP_TYPE=emcclarEMCCLAR_SNAP_SUBTYPE=CloneFRAME_IP=10.5.167.17:10.5.167.18

l For VMAX:

NSR_DATA_MOVER=datamover.emc.comNSR_SNAP_TYPE=symm_dmx



Reviewing the NMSAP NSM backup recordsThe NetWorker server records information about each NMSAP NSM backup in the onlineclient file index and media database. The NetWorker client file index for NMSAP NSMbackups is stored under the "saporacle" namespace. The “backup” namespace is usedfor regular, nonsnapshot NMSAP backups.

Use the nsrinfo and mminfo commands to query the online NetWorker indexes:

l To query the NetWorker client file index, type the nsrinfo command. For example:

nsrinfo [-v] -n saporacle -s NetWorker_server client

where client is the SAP Oracle server hostname.

l 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 the SAP Oracle server hostname.

The EMC NetWorker Command Reference Guide and the UNIX man pages describe theseNetWorker commands.


Reviewing the NMSAP NSM backup records 153



CHAPTER 8

NMSAP Oracle Split-Mirror Backups and Restores


l Split-mirror backups and restores....................................................................... 156l Basic split-mirror backup and restore data flows................................................. 156l Configuring the production host for split-mirror backups..................................... 158l Configuring the mount host for split-mirror backups............................................159l Configuring the snapshot software for split-mirror backups................................. 161l Configuring the NetWorker server for split-mirror backups................................... 162l Configuring a cluster environment for split-mirror backups..................................162l Examples of parameters for split-mirror backups.................................................163l Examples of RM scripts for split-mirror backups.................................................. 164

NMSAP Oracle Split-Mirror Backups and Restores 155

Split-mirror backups and restoresNMSAP in cooperation with EMC Replication Manager (RM) software or any othersnapshot technology software supports BR*Tools split-mirror backups with a split-command interface.

NMSAP supports split-mirror backups of SAP Oracle data stored on an EMC storage array,such as EMC VMAX (Symmetrix) or EMC VNX Block (CLARiiON), through the use of RMsoftware on all NMSAP platforms (UNIX, Linux, Windows).

NMSAP also supports other types of storage arrays, such as EMC, HP, Hitachi, and IBM,without the use of RM software. This support is available on the UNIX and Linux platformsthat NMSAP supports.

Note

The NMSAP split-mirror backup implementation does not support the SAP splitintinterface.

Split-mirror backups created with NMSAP, BR*Tools, and RM require the softwarecomponents described in the following table. If you do not use RM software, you mustinstall the snapshot technology software components that are required.

Table 21 Hosts required for split-mirror backups with RM and NMSAP

Computer or device Required software or configuration

Oracle production server host Oracle server, SAP BR*Tools, RM agent. Optionally,NetWorker client, NMSAP.

Mount host

Note

Mount host is also known as the datamover, mirror host, or backup host.

At least Oracle client software and SQL Plus, SAPBR*Tools, RM agent, NetWorker client, and NMSAP.

Replication Manager server host RM server.

NetWorker server host NetWorker client and NetWorker server.

Basic split-mirror backup and restore data flowsA split-mirror backup involves the following basic processes:

l Snapshot technology software “splits” the disks on the primary storage array, whichcreates a snapshot copy or replica of the database.

l Snapshot technology mounts the replica onto the backup host or mount host,enabling the NMSAP backint program to access the files to be backed up. Thesoftware can optionally synchronize the disks at a later time, if required.

l The NMSAP backint program backs up the snapshot data from the mount host toconventional storage.



Note

The SAP split-mirror backup framework does not support the backup of archived redologs. To fully protect the SAP environment, configure NMSAP on the production host toback up the archived logs at least once a day.

Manual split-mirror backup data flowYou start a manual split-mirror backup on the mount host by running the SAP brbackupcommand.

During a manual split-mirror backup, the following process occurs:

Procedure

1. The brbackup program contacts the production database to determine the locationof objects to be backed up. For an online backup, the program also creates a copy ofthe control file on the mount host.

2. The brbackup program prepares the production database for the backup:

l For an online backup, the program puts the required tablespaces into backupmode.

l For an offline backup, the program shuts down the database, if required.

3. The brbackup program runs the script specified by the split_cmd parameter in theinitDBSID.sap file.

4. The split script runs the proper command for the specified snapshot technologysoftware, for example, an RM job that creates a database replica and mounts thereplica on the mount host.

5. The script returns control to brbackup.

6. The brbackup program completes the operations with the production database:

l For an online backup, the program takes the tablespaces out of backup mode.

l For an offline backup, the program restarts the database, if required.

7. The brbackup program runs the NMSAP backint program on the mount host.

8. The backint program establishes a connection with the NetWorker server, backs upthe data to conventional storage, and records the backups in the NetWorker servercatalog.

9. The brbackup program records the backup in its own catalog on the mount host andmakes a copy of the catalog on the production host.

10.Optionally, the brbackup program runs the script specified by the resync_cmdparameter in the initDBSID.sap file to resynchronize the mirror disks.

Results

By default, NMSAP stores backup entries in the NetWorker client file index under thename of the client that NMSAP backs up, in this case the mount host. The backup entriescan be recorded under the Oracle production host by setting the NMSAP client parameterto the production host.


Manual split-mirror backup data flow 157

Note

To simplify the restore, store the data backed up through the split-mirror framework andthe archived logs backed up outside of the framework under the same NetWorker clientname, either the production host or the mount host.

Scheduled split-mirror backup data flowScheduled split-mirror backups are scheduled through the NetWorker server.

At the scheduled backup start time, the following process occurs:

Procedure

1. The NetWorker server contacts the NetWorker client on the mount host.

2. The NetWorker client calls the NMSAP nsrsapsv scheduled backup program.

3. The nsrsapsv program sets the environment required to run the brbackup programand runs the brbackup program, as configured in the NMSAP nsrsapsv.cfgconfiguration file.

4. The backup then follows the same steps as a manual split-mirror backup.

Restore of split-mirror backup data flowThe restore and recover operations for split-mirror backups are the same as for normalNMSAP backups and do not use the snapshot technology software.

You can restore the backup data to either the mount host or the production host byrunning the brrestore command on the destination host.

Configuring the production host for split-mirror backupsTable 21 on page 156 lists the required and optional software components to beinstalled on the production host.

Configuration of the production host for split-mirror backups requires the configuration ofthe Oracle, BR*Tools, and NMSAP software on the production host.

Configuring Oracle software on the production hostFollow the SAP documentation for details about how to create an Oracle database on theproduction host.

The following configurations apply specifically to split-mirror backups.

Procedure

1. Preferably, use the same ORACLE_HOME and user operating system account on boththe 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:

l Database files

l Control file

l Parameter file (initDBSID.ora)

l Redo log files



l Archived logs

l Dump files

4. Configure and start the Oracle Net services. This step enables the mount host toconnect to the production database.

5. Grant sysoper and sysdba privileges to the SAP database user for BR*Toolsoperations.

Configuring BR*Tools on the production hostFollow the SAP documentation for details about how to configure BR*Tools on theproduction host.


Procedure

1. Preferably, use the same paths and values for SAP-specific parameters, such asSAPBACKUP and SAPARCH, on both the production host and mount host.

2. On Windows, use NFS to share the %SAPBACKUP% directory located on the productionhost with the mount host.

Ensure that the Oracle and SAP user and services on the mount host have read andwrite permissions on the %SAPBACKUP% directory. The permissions are required tocopy the control file to the %SAPBACKUP% directory during a split-mirror backup.

Note

On Windows, the brrestore command might fail to restore the Oracle database

control file, generated during an online split-mirror backup, and the BR*Tools backupcatalogs. Split-mirror backups on Windows use NFS sharing, which enables these filesto be backed up from their location in the %SAPBACKUP% directory. However, the NFS

sharing does not enable NMSAP to find the expected request file in the NetWorkerindex. Restore these files by using NetWorker file system tools, such as the recovercommand or the client graphical user interface.

Configuring NMSAP on the production hostOptionally, install NMSAP on the production host. This installation enables the followingoperations:

l Backup of Oracle archived logs, which must be performed outside of the split-mirrorbackup framework.

l Recovery of the backups directly to the production host instead of the mount host.

Configuring the mount host for split-mirror backupsTable 21 on page 156 lists the required software components to be installed on themount host.

Configuration of the mount host for split-mirror backups requires the configuration of theOracle, BR*Tools, and NMSAP software on the mount host.


Configuring BR*Tools on the production host 159

Configuring Oracle software on the mount hostFollow the Oracle documentation for details about how to configure the Oracle softwareon the mount host.


Procedure

1. Preferably, use the same ORACLE_HOME and user operating system account on boththe production host and mount host.

2. Configure and start the Oracle Net services. This step enables the mount host toconnect to the production database.

3. Either copy the initDBSID.ora parameter file from the production host to themount host, or create a dummy initDBSID.ora file that contains the followingparameters:

l db_name=SID of the production database

l control_files=(location of the control file on the production host, location2)

Configuring BR*Tools on the mount hostFollow the SAP documentation for details about how to configure BR*Tools on the mount.

You must complete the following configurations specifically for split-mirror backups.

Procedure

1. Preferably use the same paths and values for SAP-specific parameters, such asSAPBACKUP and SAPARCH, on both the production host and mount host.

2. Create the split command script by following the appropriate RM documentation.

3. Set the following parameters in the initDBSID.sap initialization profile:

l split_cmd = location of the snapshot technology software split command script

l primary_db = SID of the production database

Note

For a single-host configuration where the mount host is the same as theproduction host, you must set this parameter to the LOCAL keyword:primary_db = LOCAL

l orig_db_home = $SAPDATA_HOME on the production host

Note

This parameter is required when the replica is mounted onto a different directorythan the production database, for example, in a single-host environment.

4. In a two-host UNIX environment, set the following parameters in theinitDBSID.sap file:

l remote_host = production database host

l stage_copy_cmd = rcp | ftp | scpSet only one of these values.



Note

Ensure that the SAP user on the mount host is allowed to perform the specifiedcommand on the production host.

5. In a Windows environment, mount the shared %SAPBACKUP% directory under thesame 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 initDBSID.sap file, or specify them ascommand line options of the brbackup command:

Note

The command line options take precedence over the corresponding parameters set inthe initDBSID.sap file.

l backup_type = online_split | offline_split

l backup_dev_type = util_file

l util_par_file = location of the NMSAP config utl file

7. Set the required SAP environment variables:

l $SAPDATA_HOME = location of the replica

l Set other required variables, for example, $SAPBACKUP, as described in theBR*Tools documentation.

Configuring NMSAP on the mount hostConfiguration for NMSAP Oracle Operations on page 69 describes how to configureNMSAP.

For scheduled backups, ensure that the nsrsapsv.cfg file on the mount host containsthe following setting:

PATH = location of the snapshot technology software binaries to be run as part of the splitcommand

Note

The NMSAP wizard does not support the configuration of split-mirror backups. You mustmanually configure scheduled backups.

Configuring the snapshot software for split-mirror backupsFollow the proper software documentation for details about how to configure the softwareto perform a consistent split and mount the replica on a mount host so that the replica isaccessible to the NMSAP backint program.

When you use the RM software, follow the documentation for that software. The followingrequirements apply specifically to split-mirror backups:

1. Add the array devices to the RM storage pool. The devices must be visible to both theproduction host and mount host.


Configuring NMSAP on the mount host 161

2. Create an application set and an RM job for the SAP Oracle database instance. In theRM job properties, select the Consistent split replication option.

3. In the RM job properties, unselect Unmount the replica on job completion. Thereplica must remain mounted after the RM job completes. Also, the job must fail if thereplica mount attempt fails.

Configuring the NetWorker server for split-mirror backupsTable 21 on page 156 lists the required software components to be installed on theNetWorker server host.

Configuration for NMSAP Oracle Operations on page 69 describes how to configure theNetWorker server for NMSAP manual backups and scheduled backups.

The following requirements apply specifically to split-mirror backups:

1. Configure the NetWorker Client resource for the production host with the followingsettings:

l Scheduled backup group: None, unless this resource is configured for archivedlog backups

l Remote access: SAP_user@mount_host

2. Configure the NetWorker Client resource for the mount host with the followingsettings:

l Save set: backint:DBSID

l Group: NMSAP group

l Backup command: nsrsapsv -f location of nsrsapsv.cfg file

l Remote access: SAP_user@production_host

Configuring a cluster environment for split-mirror backupsSAP Oracle in Cluster and RAC Environments on page 131 describes how to configure acluster 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 ofthe cluster.

Note

Only a production host can be in a cluster environment. The mount host must be astand-alone host.

3. Store the parameter file, initDBSID.utl, and the configuration file,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 foreach physical node with the following settings:

l Generic NetWorker resource (not specific to NMSAP)

l Group: None



6. On the NetWorker server, create, and configure the NetWorker Client resource for thevirtual node with the following settings:

l Group: None, unless this resource is configured for archived log backups

l Remote access:

n SAP user@physical node #1

n SAP user@physical node #2

n SAP user@mount host

7. Configure the NetWorker Client resource for the mount host with the followingsettings:

l Save set: backint:DBSID

l Group: NMSAP group

l Backup command: nsrsapsv -f location of nsrsapsv.cfg file

l Remote access: SAP_user@virtual_node

Examples of parameters for split-mirror backupsThe following examples show parameters that must be set in the Oracle, BR*Tools, andNMSAP configuration files on the production host and mount host for split-mirrorbackups and restores.

Parameter settings on the production hostYou must modify the following Oracle configuration files on the production hostaccording to the requirements of the environment. In these examples, the productionhost is named bu-erie.

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\backgrounduser_dump_dest = H:\oradata\SAP\saptrace\usertracelog_archive_dest = H:\oradata\SAP\saparchlog_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 163

Parameter settings on the mount hostYou must modify the following Oracle and BR*Tools configuration files on the mount hostaccording to the requirements of the environment. In these examples, the productionhost is named bu-erie.

initSAP.ora

db_name=SAPcontrol_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) ) )

initSAP.sap

split_cmd = F:\oracle\product\brtools\7.00\online_split.cmdbackup_type = online_splitprimary_db = SAPbackup_dev_type = util_fileutil_par_file = initSAP.utlorig_db_home = H:\oradata\SAP

Note

If the mount host is the same as the production host, then set primary_db = LOCAL.

nsrsapsv.cfg

BR_EXEC=brbackup -m all -d util_file -rF:\oracle\product\10.2.0\db_1\database\initSAP.utl -pF:\oracle\product\10.2.0\db_1\database\initSAP.sapORACLE_HOME=F:\oracle\product\10.2.0\db_1DBSID=SAPNLS_LANG = AMERICAN_AMERICA.US7ASCIISAPBACKUP=\\bu-erie\I\oradata\SAP\sapbackupSAPDATA_HOME=H:\oradata\SAPSAP_BIN=F:\oracle\product\brtools\7.00Path=C:\Program Files\EMC\rm\client\bin

Examples of RM scripts for split-mirror backupsThe following examples show RM scripts that you can modify as required for specificenvironments and configurations. Different scripts are used on UNIX and Windowssystems.

Note

The following scripts have no error handling and do not consider possible use caseswhere the operations might fail.



sap_online_split script for RM on UNIX

# SAP_ONLINE_SPLIT# File to launch into ermcli and read the commands to executeWDIR=/space10/home/ora101/nmsap/nasRMDIR=/opt/emc/rm/guiLOG=/opt/emc/rm/logs/cliDATE=`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>&1TIME=`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_split$DATE$TIME.log 2 >&1echo "End of the RM split command" >> /db/app/oracle/product/10.1.0/db_1/SAP/sapbackup/echo.log 2>&1

erm_brbackup_online_split.sh script for RM on UNIX

login user=Administrator password=emcrun-activity name=sap_brbk_j infoset=sap_brbkexit

sap_online_split.cmd script for RM on Windows

@echo offREM EMC_SAP_ONLINE_SPLITREM File to launch into ermcli and read the commands to executeset WDIR=C:\oracle\product\brtools\7.00set RMDIR=C:\Program Files\EMC\rm\guiset 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 Windows

connect host=cdendobread1c port=65432if-not login user=Administrator password=emc then exit 1if-not run-job name=sap_buhuron appset=clar_buerie then exit 1


sap_online_split script for RM on UNIX 165



APPENDIX A

Examples of SAP Oracle Command Options

This appendix includes the following topics:

l Examples of brbackup and brarchive command syntax and options.................... 168l Examples of brrestore command syntax and options........................................... 169l Examples of brrecover command syntax and options.......................................... 170

Examples of SAP Oracle Command Options 167

Examples of brbackup and brarchive command syntax andoptions

You can use the SAP brbackup and brarchive commands with the NMSAP programfrom any command prompt. Examples of the syntax and options for these commands areas 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 | online_split | offline_split}] [-u user/password] [-w [use_dbv | only_config]]

brarchive [-c force] [-d {util_file | rman_util}] [-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 useat least one of the enclosed options. Variables are in italics. Keywords are in bold text.The following table lists examples of the command options.

The SAP documentation provides complete details about the command syntax andoptions for the brbackup and brarchive commands.

Note

The command line options overwrite the corresponding parameters set in theinitialization profile initDBSID.sap.

Table 22 Options for brbackup and brarchive commands

Option Description

-c force Suppresses most of the confirmation messages that interrupt thebackup process.

-d {util_file | util_file_online |rman_util}

Specifies to use NMSAP with backint or RMAN for the backup or

archive.

-f stop Instructs brarchive to wait for the next offline redo log file

written by Oracle, and then send the file to backint for

archiving.

-m database_objects_to_back_up

Specifies the database objects to back up, for example, the wholedatabase, selected tablespaces or datafiles, incremental RMANbackup, and so on. The brbackup program uses this option.

-m delay_time Specifies the delay time between Oracle creating the offline redolog file and sending datafiles to the database in standby mode.The brarchive program uses this option.

-m nondatabase_objects_to_back_up

Specifies what nondatabase files or folders to back up. Use one ofthe following keywords: sap_dir, ora_dir, all_dir,full_directory_path. The brbackup program uses this option.



Table 22 Options for brbackup and brarchive commands (continued)

Option Description

-p profile Specifies a BR*Tools intialization profile if the file does not havethe default name or is not stored in the default location.

-r parameter_file Specifies the parameter file, initDBSID.utl, that NMSAP

backint uses during the backup or archive process.

-t backup_type Instructs brbackup and NMSAP backint what type of backup

to perform. During an online backup, to reduce the number of redologs that Oracle generates, use this option with the -dutil_file_online option.

-u user/password Specifies the username and password of the Oracle databaseadministrator.

-w use_dbv | only_config Verifies the backup after the files are backed up. Helps detectpossible hardware problems.The use_dbv option performs the backup, followed by a restore

of the backup to a temporary location. This option approximatelydoubles the backup time.

Examples of brrestore command syntax and optionsYou can use the SAP brrestore command with the NMSAP backint program from anycommand 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 | number_of_days][-m {all | all_data | full | incr | tablespace_list | file_ID | file_ID1_range | file_list | non_db}] [-p profile] [-q check][-r parameter_file]

Options in brackets ([ ]) are optional. Options in braces ({ }) must use at least one of theenclosed options. The following table lists examples of the command options.

The SAP documentation provides complete details about the command syntax andoptions for the brrestore command.

Table 23 Options for brrestore command

Option Description

-c force Suppresses most of the confirmation messages that interrupt the restoreprocess.

-d {util_file | rman_util} Specifies to use NMSAP with backint or RMAN for the restore.

-f restore_to_complete Specifies which restores to restart to restore missing files.

-m objects_to_restore Specifies the database objects to restore, for example, the wholedatabase, selected tablespaces or datafiles, and incremental RMANbackup.

-m non_db Specifies the restore of data from a directory (nondatabase) backup.


Examples of brrestore command syntax and options 169

Table 23 Options for brrestore command (continued)

Option Description

-p profile Specifies a BR*Tools initialization profile if the file does not have thedefault name or is not stored in the default location.

-r parameter_file Specifies the parameter file, initDBSID.utl, that NMSAP backintuses during the restore process.

Examples of brrecover command syntax and optionsYou can use the SAP brrecover command with the NMSAP program from any commandprompt. 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

The following table lists examples of the command options.

The SAP documentation describes these commands.

Table 24 Options for brrecover command

Option Description

-c force Suppresses most of the confirmation messages thatinterrupt the recovery process.

-d {util_file | rman_util} Recovers NMSAP backups performed with backint(util_file) or RMAN (rman_util).

-p profile Specifies a BR*Tools initialization profile if the file does nothave the default name or is not stored in the defaultlocation.

-pit yyyy-mo-dd hh.mi.ss Recovers the database or tablespaces for a specific point-in-time.

-r parameter_file Specifies the parameter file, initDBSID.utl, which

NMSAP backint uses during the backup or archive

process.

-scn scn Recovers the database to the specified Oracle systemchange number.

-t complete | dbpit | tspit | reset |restore | apply | disaster

Specifies the type of recovery:

l complete: complete database recovery

l dbpit: database point-in-time recovery

l tspit: tablespace point-in-time recovery



Table 24 Options for brrecover command (continued)

Option Description

l reset: whole database reset

l restore: restore of individual backup files

l apply: apply offline redo log files (archive logs)

l disaster: disaster recovery

-tsp tablespace_name |tablespace_name_list

Recovers a single specified tablespace or the tablespaceslisted in the specified file.

-u user/password Specifies the username and password of the Oracledatabase administrator.


Examples of brrecover command syntax and options 171



APPENDIX B

Troubleshooting and Error Messages

This appendix includes the following topics:

l Verifying the release information.........................................................................174l Generating diagnostic logs..................................................................................174l Setting the debugging options for RMAN operations............................................174l Backup and restore problems..............................................................................175l NMSAP error messages....................................................................................... 176

Troubleshooting and Error Messages 173

Verifying the release informationWhen making queries or requests to an EMC Customer Support Representative, providespecific information about the NMSAP software that you are using.

To verify the release information for the installation, use the appropriate command orprocedure:

l On UNIX, type the following command as the root user:

what file_name | more

where file_name is the name of an NMSAP binary file, for example, backint ornsrsapsv.

l On Linux, type the following command as the root user:

strings file_name | grep "@(#)"

where file_name is the name of an NMSAP binary file, for example, backint,hdbbackint, or nsrsapsv.

l On Windows:

1. Locate the NMSAP binary file, for example, backint.exe or nsrsapsv.exe.

2. Right-click the file, and select Properties.

3. In the Properties window, click the Version tab to display the version information.

Generating diagnostic logsTo generate diagnostic logs, set the following parameters:

l Set NSR_DEBUG_DIR if you do not want to use the default location for the backintor hdbbackint diagnostic logs, which is /nsr/applogs (UNIX) orNetWorker_installation_path\nsr\applogs (Windows).

l To debug a failed scheduled backup only, set NSR_DEBUG_LEVEL = 9 in the NMSAPconfiguration file or in the Advanced Options table in the wizard.

l Set debug_level = 9 in the initDBSID.utl file or in the Advanced Options table inthe wizard.

l Set nsr_debug_msg = TRUE in the initDBSID.utl file or in the Advanced Optionstable in the wizard.

Note

The recommended debug level is 9. Use this debug level for testing and EMC CustomerSupport diagnostics only. Do not leave the debug settings in place for an extended time because the log files canquickly increase in size.

Setting the debugging options for RMAN operationsTo debug an NMSAP backup or restore that uses RMAN, you must set theNSR_DEBUG_LEVEL parameter in the BR*Tools initialization profile initDBSID.sap.



To specify a nondefault location for the NMSAP debug logs generated for the RMANoperation, you must also set the NSR_DIAGNOSTIC_DEST parameter.

Note

You must set the NSR_DEBUG_LEVEL and NSR_DIAGNOSTIC_DEST parameters by usingthe rman_parms parameter in the initDBSID.sap file, not the rman_send parameter.For example:

rman_parms=”ENV=(NSR_DEBUG_LEVEL=9)”

On a Windows system, when you use rman_parms to set a parameter, the parametervalue remains in effect for all subsequent allocated channels and for all RMAN sessionsuntil one of the following events occurs:

l You shut down the Oracle database.

l You set the parameter to a different value by using the rman_parms option forsubsequent allocated channels.

l You unset the parameter for the channel by using the rman_parms option, as in thefollowing example:

rman_parms="ENV=(NSR_DEBUG_LEVEL=,NSR_DIAGNOSTIC_DEST=)"

Backup and restore problemsThe following table provides guidelines for solving problems that might occur during anNMSAP backup or restore.

Table 25 NMSAP backup or restore problems

Problem Possible reason or solution

The data is not backed up by using the settingsin the Client resource on the NetWorker server.

NMSAP uses the Client resource settings only for scheduled backups. Formanual backups, you must specify the settings in the initDBSID.utl file.

You must specify the client settings in the initDBSID.utl file on the SAP

Oracle server. NMSAP backint parameters on page 77 provides details.

The bootstrap notification report was not printedto the printer specified in the Group resource onthe NMSAP server.

Bootstrap notification reports are not generated after a manual NMSAP backup. Monitoring manual backups on page 119 describes the generation of abootstrap notification report.

An online backup of an Oracle tablespace istaking a long time.

Oracle software creates more online redo logs during an online backup thanduring an offline backup. This occurrence might prolong the online backup.

After a backup, the parallelism setting in theNMSAP operation log,backintDBSID.log.raw, is different from

the configuration setting.

The backint program adjusts the parallelism setting during the backup

session depending on other parameters, such as when the number of fileswithin the backup session is lower than the server parallelism setting.

A specified backup of an Oracle directory failed. NMSAP does not support the backup of directories. Specify each databaseobject within the directory to back up and then perform the backup.

You are unable to view the files backed up to theNetWorker server from the BrGui program on theSAP Oracle server.

Ensure that the SAP user has proper privileges to view the information, forexample, the Operate NetWorker privilege.


Backup and restore problems 175

Table 25 NMSAP backup or restore problems (continued)

Problem Possible reason or solution

You are unable to view backup information inNetWorker online indexes.

When you start a restore within a certain timeframe that expired or otherwise isnot available, brrestore restores files from previous backups, depending on

whether the prev_bk_restore parameter is set to Yes. The prev_bk_restore in NMSAP backint parameters on page 77 provides details.Ensure that the SAP user’s operating system authorization has the appropriatepermission to access the NetWorker server.

NMSAP error messagesThe following table lists possible error messages that might appear in thebackintDBSID.log.raw file.

Table 26 NMSAP error messages

Error message Description Solution

BACKUP: Bad input line: lineINQUIRE: Bad input line:line

RESTORE: Bad input line:line

One of the lines in the input file had a bad format.There must be only one or two specifications oneach input line (file name and size, if it is a specialfile).

Check the input file that the BR*Tools binarygenerated to ensure that the file has the correctformat. If not and this error recurs, contact SAPcustomer support.

Cannot connect to server:error

The backint program was unable to connect to

the NetWorker server to start reading the mediadatabase.

Ensure that you specify the correct NetWorkerserver. Check the log file to see if any othermessages refer to this problem.

Cannot reopen file_name asstderr

The backint program was unable to open a log

file for writing.

Check the permissions on the file listed in themessage and the permissions on the directory.

Cannot start session withserver: error

The backint program was unable to start reading

the media database on the NetWorker server.

Ensure that you specify the correct NetWorkerserver. Check the log file to see if any othermessages refer to this problem.

Checking for deletion ofsemaphore file: error

The system could not confirm the existence of thesemaphore file due to a system error.

Check to see if the .switch.sem file is still in

the SAPBACKUP directory. If so, delete the file

before running the SAP backup again.

Creating directive file: error The system cannot create the directive file for useby the NetWorker server. This directive file iscreated so that the NetWorker software canprocess files with the correct attributes.

Check the directory where the directive file isbeing created, specified by the backint_tmpdirparameter in the NMSAP parameter file, toensure that files can write to the directory.

Empty input file The input file that contains the list of files thatrequire backup or restore is empty.

Ensure that you have selected database objectsfor backup or restore.

Error opening input file:error

The operation could not open the input file thatlists all the files to be backed up or restored. Thefile might not exist, or the file might not have readpermissions.

Ensure that the input file exists and is readable.



Table 26 NMSAP error messages (continued)


Error opening output file:error

The operation could not open the output file forthe reason specified.

Check the permissions on the output file anddirectory, and check for sufficient disk space tocreate a file.

Error: file_name isn’t aregular file, raw partition, ordirectory.

The backint program does not support the file

type, such as a symbolic link or a named pipe.

Check the file name to see what type of file isbeing backed up. If brbackup requests a

backup of special files, contact SAP customersupport.

Error: Too many symlinks There are too many (more than 100) symbolic linksto save.

Consider restructuring the directories toeliminate the extra symbolic links if the list ofdatabase files to be backed up contains morethan 100 symbolic links.

Error: unexpected inquirecase.

The files requested in the input file do not matchthe SAP backint specification. Valid file

specifications include:

l #NULL is specified for a backup ID, with orwithout a file name.

l A file name is specified with a backup ID.

l A backup ID is specified without a file name.

Check the backup input file generated bybrbackup. If the input file appears to be the

wrong format, contact SAP customer support.

File file_name not found inindex, no attempt to recoverwill be made

The NetWorker software did not save the file namespecified for recovery. The file name does notappear in the client file index.

Check the specified file name to ensure that thename is correct. Check previous backups todetermine whether the file was saved in aprevious backup.

File was file_name, lstaterror

NMSAP tried to obtain information for a symboliclink that does not exist or NMSAP cannot accessbecause permission is denied.

Check the file to ensure that the file exists andis a valid symbolic link.

Improperly formattedbackup id: backup ID

The backup ID is incorrect. The backup ID mustspecify either a number or the word #NULL.

Check the input file brrestore generated to

ensure that the file has the correct format. If notand this error keeps occurring, contact SAPcustomer support.

Lookup failed on file_name(backup_ID)

The backint program was trying to look up a file

name or backup ID in the client file index, but theindex query failed. The next message must explainwhy the index query failed.

Check the next error message to determine whythe index query failed.

Non-recursive directorybackup is not supported atthis time

You have tried to back up a directory. NMSAP doessupport the backup of directories.

Select specific database objects to back upfrom the BrGui program and restart the backup.

Not enough savesetsconfigured. Increase"savesets" setting.

The number or size of the save sets to be backedup exceeds the current settings for the number ofsave sets allowed or the maximum save set size.

Increase the number of save sets or themaximum save set size:

l The savesets parameter specifies thenumber of save sets.

l The ss_size_max parameter specifies themaximum save set size.

Table 7 on page 78 provides details.


NMSAP error messages 177



Open param file: file_name,error: error_message

Unable to open the backint parameter file,

initDBSID.utl.

Try to open the parameter file for backint in

any text editor. If you are unable to open theparameter file, replace the file with the originalfile from the NMSAP installation package.

Opening switch list file foronline backup: error

When performing an online backup, backinttried to open a file to communicate withbrbackup. This file could not be opened for the

specified reason.

Check if the .switch.lis file exists in the

SAPBACKUP directory. If so, check the

permissions on this file. Normally, NMSAPdeletes and re-creates this file for everytablespace to be switched into backup mode.

Opening switch log file foronline backup: error

When performing an online backup, backintexpects brbackup to provide a log file of the

tablespaces that were switched into or out ofbackup mode.

Check if the .switch.log file is still in the

SAPBACKUP directory. If so, delete the file

before running the SAP backup again.

Opening switch semaphorefile for online backup: error

When performing an online backup, backinttries to open a file to communicate withbrbackup. You cannot open this file for the

reason specified.

Check if the .switch.sem file exists in the

SAPBACKUP directory. If so, check this file’s

permissions. Normally, NMSAP deletes and re-creates this file for every tablespace to beswitched into backup mode.

Semaphore file not deletedin time seconds.

When performing an online backup, the SAPmodule waited for the switch semaphore file to bedeleted. After waiting for the number of seconds,the switch semaphore file was not deleted.

If brbackup appears to be running correctly

but slowly, you can increase the sem_timeoutsetting for backint.

Switch log file indicates anerror.

The brconnect program indicated in the switch

log file that there was an error switching one of thetablespaces into or out of backup status. Thiserror is a fatal error in the backint specification.

Investigate the error messages in the switch logfile to determine the problem. Check the SAPinstallation or the SAP documentation todetermine the problem.

Unable to allocate memory:error

The backint program was unable to allocate

memory.

Check the memory usage on the computer.

Unable to execute childbackint process.

The backint process could not run a subprocess

to backup an individual save set.

Ensure that the backint binary is in the

directory from which brbackup or brrestoreruns. Check the log file for any other messagesthat might help pinpoint the problem.

Unable to find pid processID in list of files

The backint program checked the status of a

subprocess created to save individual files.However, the subprocess ID did not match any ofthe expected process IDs.

Ensure that all the files were saved by checkingthe rest of the messages from the backupprocess. In particular, check for the message “xof y files saved at time.” Retry the backup if allthe files were not saved.

Unable to open output file:error

The output file could not be opened due to thespecified error.

Check the permissions on the output file anddirectory, and check for sufficient disk space tocreate a file.

Unable to query withsavetime and filename bothabsent

The backint program tried to find a file in the

client file index, but neither the save time nor thefile name were provided.

Check the input file for any incorrect fileinformation.





Use absolute path namefor: file_name

The file name specified in the input file was not anabsolute pathname. Without a full pathname, thefile could not be restored or inquired.

Check the input file brrestore generated to

ensure that the file has the correct format. If notand this error recurs, contact SAP customersupport.


NMSAP error messages 179



GLOSSARY

This glossary contains the definitions of terms found in this manual. Most of the termsare specific to the NMSAP software. For terms specific to the NetWorker software, refer tothe latest EMC NetWorker Administration Guide.

A

active-active applicationcluster

Type of cluster configuration where a group of linked virtual or physical hosts with sharedstorage, called cluster nodes, can access the database data from multiple nodesconcurrently.

active-passive cluster Type of cluster configuration where the data server runs on the active physical node, andother nodes are passive nodes that maintain data updates and wait to take over if theactive node fails.

administrator Person who normally installs, configures, and maintains software on network computers,and who adds users and defines user privileges.

archive Process by which NetWorker software backs up directories or files to an archive volume tofree disk space. Archived data can be deleted but is not recyclable.

attribute Feature of a NetWorker resource. A setting or information that the resource provides.

autochanger See library.

B

backup 1. Duplicate of database or application data or an entire computer system storedseparately from the original, which can be used to recover the original if it is destroyedor damaged.

2. Operation that saves data to a volume for use during a recovery.

backup level See level.

backup volume See volume.

bootstrap Save set that is essential for disaster recovery procedures with the NetWorker server. Thebootstrap consists of three components that reside on the NetWorker server: the mediadatabase, the resource database, and a server index.

BR*Tools SAP backup utilities, specifically the brbackup, brrestore, brarchive, andbrrecover programs.

browse policy NetWorker policy that specifies the period of time during which backup entries are retainedin the client file index. The index makes the associated backed-up data readily accessiblefor recovery. See retention policy .


C

client Computer, workstation, or file server whose data can be backed up and restored withNetWorker software.

Client Direct Feature that enables clients to deduplicate backup data and send the deduplicated datadirectly to AFTD or DD Boost storage devices, bypassing the NetWorker storage node. Thestorage node manages the backup devices but does not handle the backup data.

client file index Database maintained by the NetWorker server that tracks every database object, file, or filesystem backed up. The NetWorker server maintains a single index file for each clientcomputer. The tracking information for each backup is deleted from the index when thebrowse time of the backup expires.

client-initiated backup See manual backup.

client-side configuration NetWorker module backup configuration, made without the configuration wizard, that isperformed through the NetWorker Management Console and configuration files orparameters stored on the client host, as compared to server-side configuration. See server-side configuration .

clone Duplicate copy of backed-up data, which is indexed and tracked by the NetWorker server.Single save sets or entire volumes can be cloned.

clone volume Exact duplicate of a backup or archive volume. NetWorker software can track four types ofvolumes (backup, archive, backup clone, and archive clone). Save sets of these differenttypes may not be intermixed on one volume. Clone volumes may be used in exactly thesame way as the original backup or archive volume.

cluster nodes A group of linked virtual or physical hosts with shared storage in a cluster, which worktogether and represent themselves as a single host called a virtual cluster host.

conventional storage Storage library attached to the NetWorker server or storage node, used to storeconventional backups or snapshot backups. See primary storage .

D

daemon Process on UNIX systems that runs in the background and performs a specified operationat predefined times or in response to certain events.

database 1. A collection of data arranged for ease and speed of update, search, and retrieval bycomputer software.

2. An instance of a database management system (DBMS), which in a simple case mightbe a single file containing many records, each of which contains the same set of fields.

Data Domain device Logical storage device created on a Data Domain system, used to store deduplicatedNetWorker backups. Each device appears as a folder on the Data Domain system andappears with a storage volume name in NMC. A Data Domain device is also known as aDD Boost device.

DBA (databaseadministrator)

Person who is typically responsible for installing, configuring, and maintaining databasesystems.

Glossary


DBSID Variable representing the name of the SAP Oracle database instance.

DD Boost An optimized library and communication framework with a special Data Domain API thatallows the NetWorker software to define and interact with storage devices on the DataDomain system.

deduplication backup Type of backup in which redundant data blocks are identified and only unique blocks ofdata are stored. When the deduplicated data is restored, the data is returned to its originalnative format.

device 1. Storage unit that can contain a backup volume. A storage unit can be a tape device,optical drive, autochanger, or disk connected to the server or storage node.

2. General term that refers to storage hardware.

3. Access path to the physical drive, when dynamic drive sharing (DDS) is enabled.

direct file access (DFA) See Client Direct.

directive Instruction that directs NetWorker software to take special actions on a given set of files fora specified client during a backup or recovery operation. Directives are ignored in manual(unscheduled) backups.

disaster recovery Restore and recovery of business operations and data in the event of hardware failure orsoftware corruption.

distributed segmentprocessing (DSP)

Part of the DD Boost interface, which enables data deduplication to be performed on ahost before the data is sent to the Data Domain system for storage.

drive Hardware device through which media can be read or written to. See device.

E

event-based backup See probe-based backup.

expiration date Date when a volume changes from read/write to read-only.

expired save set Save set that has exceeded its browse time and has been removed from the NetWorkerclient file index. Expired save sets can no longer be browsed.

F

firewall A system designed to prevent unauthorized access to or from a private network.

full backup See level.

G

group Client computer or group of clients that are configured to back up files during a NetWorkerscheduled backup, according to a single designated schedule or set of conditions.

Glossary


H

high-availability system System of multiple computers configured as cluster nodes on a network that ensures theapplication services continue despite a hardware or software failure.

host Computer on a network.

I

incremental backup See level.

instance Combination of processes that runs each time a database starts up.

Internationalization(I18N)

Process of adapting software to accept input and output of data in various languages andlocales.

J

jukebox See library.

L

label Electronic header on a volume used for identification by NetWorker or other data moverapplication.

level Backup configuration option that specifies how much data is saved during a scheduled ormanual backup:

l A full backup backs up all data objects, regardless of when they last changed.

l An incremental backup backs up only data objects that have changed since theprevious backup.

library Hardware device containing one or more removable media drives, as well as slots forpieces of media, media access ports, and a robotic mechanism for moving pieces of mediabetween these components. Libraries automate media loading and mounting functionsduring backup and recovery. The term library is synonymous with autochanger, autoloader,carousel, datawheel, jukebox, and near-line storage.

M

manual backup Backup that a user performs from the client, also known as an unscheduled, on-demand,or ad hoc backup.

media Physical storage, such as magnetic tape, optical disk, or file system, to which backup datais written. See volume.

media index Database that contains indexed entries of storage volume location and the life cycle statusof all data and volumes managed by the NetWorker server. Also known as media database.

media pool See pool.

Glossary


mount host Host used in NSM backups that is separate from the database server host, with access tothe primary storage unit. During a backup to conventional storage, either the databaseserver host or mount host backs up a point-in-time copy (snapshot) from the primarystorage to conventional storage.

multiplex To simultaneously write data from more than one save set to the same storage device.

N

NetWorker ManagementConsole (NMC)

Software program that is used to manage NetWorker servers and clients. The NMC serveralso provides reporting and monitoring capabilities for all NetWorker processes.

NetWorker server Computer on a network that runs the NetWorker server software, contains the onlineindexes, and provides backup and restore services to the clients and storage nodes on thesame network.

NetWorker SnapshotManagement (NSM)

EMC NetWorker software integrated into the NetWorker client with NetWorker release 8.1,which provides point-in-time snapshots of data to be backed up. Applications that arerunning on the host system continue to write data during the snapshot operation. Thesnapshots include data from open files.

NMSAP NetWorker Module for SAP software.

NMSAP wizard NetWorker client backup configuration wizard that incorporates NMSAP features andfunctionality for both regular (nonsnapshot) backups and snapshot backups. A userlaunches the wizard from the NetWorker Management Console.

notification Message sent to the NetWorker administrator about important NetWorker events.

O

offline backup Backup of database objects performed while the corresponding database or instance isshut down and unavailable to users.

online backup Backup of database objects performed while the corresponding database or instance isrunning and available to users.

online indexes Databases located on the NetWorker server that contain all the information pertaining tothe client backups (client file index) and backup volumes (media index).

operator Person who performs day-to-day data storage tasks such as loading backup volumes intostorage devices, managing libraries, monitoring volume locations and server status,verifying backups, and labeling volumes.

Oracle Recovery Manager(RMAN)

Oracle utility that acts as an intelligent interface to Oracle databases for the backup andrestore of Oracle database objects.

P

parallelism Method that backs up or recovers data for multiple clients, or multiple save sets for oneclient, at the same time.

Glossary


pathname Instructions to the operating system for accessing a file:

l An absolute pathname indicates how to find a file starting from the root directory andworking down the directory tree.

l A relative pathname indicates how to find a file starting from the current location.

physical host Node or host that forms part of a cluster.

point-in-time copy (PITcopy)

Fully usable copy of a defined collection of data, such as a consistent file system,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.

policy Defined rules for client backups that can be named and applied to multiple groups. Groupshave dataset, schedule, browse, and retention policies.

pool 1. NetWorker sorting feature that assigns specific backup data to be stored on selectedmedia volumes.

2. Collection of NetWorker backup volumes to which specific data has been backed up.

primary storage Server storage subsystem that contains application data and any persistent snapshotbackups of data. See conventional storage .

probe-based backup Type of scheduled backup, also known as an event-based backup, where the NetWorkerserver initiates the backup only when specified conditions are met, as determined by oneor more probes.

proxy client host Host used in NSM snapshot backups that is separate from the database server host, withaccess to the primary storage unit. During an NSM backup to conventional storage, eitherthe database server host or proxy client host backs up a point-in-time copy (snapshot)from the primary storage to conventional storage.

R

recover To apply transaction (redo) logs to make data consistent with a given point-in-time.

recyclable save set Save set whose browse and retention policies have expired in the NetWorker indexes.Recyclable save sets are removed from the media database.

recyclable volume NetWorker volume whose data has exceeded both its browse and retention policies and isnow available to be relabeled and reused.

redo log Oracle transaction log file that records a history of all the transactions made to a database.Archived redo logs are backed up and used to recover a database to a specific point-in-time.

remote device Storage device that is attached to a storage node that is separate from the NetWorkerserver.

resource NetWorker software component that describes details of the NetWorker server or itsclients. Clients, devices, schedules, groups, and policies are all NetWorker resources. Eachresource has configurable attributes that define its properties.

resource database NetWorker database of information about each configured resource.

Glossary


restore To retrieve individual datafiles from backup media and copy the files to disk, withoutapplying transaction logs. See recover.

restore from conventionalstorage

Type of restore that restores a proxy backup from a conventional storage medium, such asa tape or disk.

retention policy NetWorker setting that determines the minimum period of time that backup data isretained on a volume available for recovery. After this time is exceeded, the data is eligibleto be overwritten. See browse policy .

retrieve To locate and recover archived files and directories.

RMAN See Oracle Recovery Manager (RMAN).

rollback restore NSM process by which a specific point-in-time copy (snapshot) of data is restored to thesource location by using the hardware's particular capabilities. A rollback restore is adestructive save set restore.

rollover-only backup Type of backup in which an existing point-in-time copy (snapshot) of data, which wascreated on the primary storage during a snapshot backup, is immediately backed up toconventional storage. The snapshot is automatically deleted from the primary storage.

S

save NetWorker command that backs up client files to backup media volumes and makes dataentries in the online index.

save set Collection of data from a single client computer, which is backed up on storage media.

save set ID (ssid) Internal identification number assigned to a save set.

save stream Data and save set information that is written to a storage volume during a backup. A savestream originates from a single save set.

scanner NetWorker command used to read a backup volume when the online indexes are notavailable.

scheduled backup Type of backup that is configured to start automatically at a specified time for a group ofone or more NetWorker clients. A scheduled backup generates a bootstrap save set.

server index See client file index.

server-side configuration NetWorker module backup configuration that is performed through the configurationwizard, with settings saved on the NetWorker server, as compared to client-sideconfiguration. See client-side configuration .

shared disk Storage disk that is connected to multiple nodes in the cluster.

snap set Group of files, volumes, or file systems from a single client that describes the collection ofdata for which a point-in-time copy is created on an external disk subsystem, such as astorage array.

snapshot Point-in-time, read-only copy of data created on a primary storage system during asnapshot backup.

Glossary


snapshot and rolloverbackup

Type of backup in which an existing point-in-time copy (snapshot) of data, which wascreated on the primary storage unit by a snapshot backup, is backed up to conventionalstorage. The snapshot is retained on the primary storage.

snapshot backup Type of backup that creates a point-in-time copy or snapshot of data on the primarystorage unit, which may be immediately recovered as a backup copy.

snapshot policy Rules that control the lifecycle of a snap set. The snapshot policy specifies the frequency ofsnapshots and how long snapshots are retained before recycling.

Snapshot restore Type of restore that copies data created during a snapshot backup to its original locationor to an alternate location.

ssid See save set ID (ssid).

stand-alone device Storage device that contains a single drive for backing up data. Stand-alone devicescannot store or automatically load backup volumes.

storage device See device.

storage node Storage device physically attached to a computer other than the NetWorker server, whosebackup operations are administered from the controlling NetWorker server.

T

tablespace Database structure that consists of one or more data files.

target database Database that the NetWorker server backs up as a safeguard against data loss.

transaction log Record of named database transactions or list of changed files in a database, stored in alog file to execute quick restore and rollback transactions.

U

unscheduled backup See manual backup.

V

volume 1. Unit of physical storage medium, such as a magnetic tape, optical disk, or file systemused to store data. Backup data must be stored on a backup volume and cannot bestored on an archive volume or a clone volume.

2. Identifiable unit of data storage that may reside on one or more computer disks.

volume name Name that you assign to a backup volume when it is labeled. See label.

Glossary


INDEX

Aactive-passive cluster configurations 132advanced file type device (AFTD) 102archived redo logs 118, 156audience 13Avamar deduplication backup

cluster 134Avamar server 102, 122

Bbackint

command 32location 70

backint parameter file 77backup

archived redo logs 118cloning 122manual 118probe-based 109Replication Manager 156session log 120split-mirror 156

Backup Command client attribute 48, 97backup notifications, email 113backup types

DD Boost 51, 105deduplication 20

bootstrap backup 19bootstrap file 127BR_EXEC configuration parameter 87BR*Tools 31, 72brarchive command 168brbackup command 168BrGui interface 72brrecover command 124, 170brrestore command 124, 169

Ccancel manual backup 64, 119cancel scheduled backup 59, 117choosing the backup and restore utility 72Client Direct method 52, 106client file index 19client indexs 127Client resource attributes 48, 97cloning backups 122cluster

Avamar deduplication backup 134backups 132cloning backups 122Data Domain deduplication backup 135manual backups 134probe-based backup 135restoring backups 135

split-mirror backup 162command

backint 32brarchive 168brbackup 168brrecover 124, 170brrestore 124, 169hdbbackint 32mminfo 120, 153nsrinfo 120nsrsapsv 32sapclone 122

comments 13component software used with NMSAP 32configuration file

conversion 75init_hana_nmsap.utl file 32init_oracle_nmsap.utl file 32init(DBSID).utl file 149initDBSID.utl 77nsrsapsv.cfg 87

conventions for publication 13convert backup settings from earlier releases 75, 135

DData Domain deduplication backup

cluster 135data flow with NSM 143data mover 156DBSID 87DD Boost backup 51, 105debug level 174deduplication

backup 20restore 20

deduplication backupdeletion and expiry 122manual 104requirements 102scheduled 103, 104with Oracle RMAN 104with the wizard 103without the wizard 104

deferred live backup 142deletion of deduplication backups 122destination host 124diagnostic logs 174direct file access (DFA) 21directory backup and restore 26disaster recovery 66, 127distributed segment processing (DSP) 21

Eemail backup notifications 113


encryption, SAP user for OS and Oracle 76environment, NMSAP software 31error messages 176event-based backup 109

Ffirewall 36, 70

Ggeneric Client resource 133

Hhdbbackint

command 32

II18N support 28, 71immediate live backup 142init_hana_nmsap.utl file 32init_oracle_nmsap.utl file 32init.utl file 76init(DBSID).sap file 160init(DBSID).utl file 149initDBSID.utl file 77instant backup 142instant restore 143internationalization support 28

Llive backup 142Lockbox resource, in cluster 133logs

archived redo 118backup session reports 120

Mmanual backup

cancelling 64, 119cluster 134commands 168configuration 50, 100deduplication 104monitoring 119performing 118

media database 19, 120mirror host 156mminfo command 120, 153mount host 140, 156multiple probes 112

NNetWorker

client file index 19media database 19

NMSAPcomponents 32environment 36, 70

NMSAP parameters for NSM operations 147

nmsapps.cfg file 149non-ASCII (I18N) characters 28NSM

backup configuration 144backup records 153backup types 141configuration file 149data flow descriptions 143examples 152parameters 149PIT copy 142ps_opaque_pfilename file 151requirements 140restore types 143testing 151

NSM snapshot operations 140nsrinfo command 120nsrsapadm command 76nsrsapadm utility 32, 75nsrsapprobe program 110nsrsapsv command 32nsrsapsv.cfg file 32, 76, 87

Oonline indexes 120online NetWorker indexes 19Oracle Real Application Cluster (RAC) 135

Pparameter file

initDBSID.utl 77nsrsapsv.cfg 87

password, SAP user 76point-in-time (PIT) copy 142preface 13privileges for NMSAP operations 36, 70probe-based backup

cluster 135description 109example 112multiple probes 112

problems, backup or restore 175Proxy client host 140ps_opaque_pfilename file 151ps_opaque_pfilename parameter 149

Qquery the client file index 120

RRAC data

backups 135restoring 138

recoverbrrecover 170parameter file 170

related documentation 13Replication Manager

See also split-mirror backups 156restart a restore 126

Index


restartable backup 26, 100restore

brrestore 169cluster data 135deduplication 20restart for missing files 126to a different host 124to a new location 124

restore and recover data 18reviewing backups 120RMAN

enabling 73parameters 73

rollover-only backup 142

SSAP HANA interfaces 32sapclone command 32, 122save

archived redo logs 118save sets, cloning 122scheduled backup

canceling 59, 117configuration file 87configuration with wizard 37, 74configuration without the wizard 76deduplication 103, 104monitoring 58, 116performing 116probe-based 109snapshot 156testing 58, 116

snap set 142

snapshot and rollover backup 142snapshot backup 140, 142snapshot restore 143software used with NMSAP 36, 70split-mirror backups

cluster configuration 162example parameters 163example scripts 164mount host configuration 159

splitint interface 156support information 13

Ttemplate files 76testing scheduled backups 174

Uuid bit 70user privileges for NMSAP 36, 70username of SAP user 76

Vversion information, verifying 174virtual host 133VMware support 30

Wwizard

description 22limitations 22requirements 37, 74

Index


Index


Documents

EMC NetWorker Module for SAP 8.2 Administration Guide