EMC Backup and Recovery for SAP Oracle and SAP BRTools ...

EMC Confidential - Internal Use Only 

EMC Backup and Recovery for SAP 

Oracle with SAP BR*Tools 

Enabled by EMC Symmetrix DMX-3, EMC Replication Manager, 

EMC Disk Library, and EMC NetWorker 

Integration Guide 

EMC Global Solutions Operations 

EMC Corporation 

Corporate Headquarters 

Hopkinton MA 01748-9103 

1.508.435.1000 

www.EMC.com

Copyright and Trademark Information 


Copyright © 2008 EMC Corporation. All rights reserved. 

Published March 2008 

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

to change without notice. 

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO 

REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN 

THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF 

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 

Use, copying, and distribution of any EMC software described in this publication requires an applicable software 

license. 

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. 

All other trademarks used herein are the property of their respective owners. 

EMC Backup and Recovery for SAP Oracle with SAP BR*Tools Enabled by EMC Symmetrix DMX-3, EMC 

Replication Manager, EMC Disk Library, and EMC NetWorker Integration Guide 

P/N H4256 

2 

EMC Backup and Recovery for SAP Oracle with SAP BR*Tools Integration Guide


Contents 

About this Document 

Purpose .................................................................................................. 5 

Audience................................................................................................ 5 

Scope ..................................................................................................... 6 

Related documents ................................................................................ 6 

Chapter 1 

Chapter 2 

Solution Overview 

The business challenge .......................................................................... 8 

The technology solution ........................................................................ 8 

Solution components ............................................................................. 9 

Physical architecture .............................................................................. 9 

Hardware and software resources ........................................................ 11 

Solution Design 

Process overview ................................................................................. 14 

Process details ..................................................................................... 14 

EMC Backup and Recovery for SAP Oracle with SAP BR*Tools Integration Guide 3

Contents 


Chapter 3 

Chapter 4 

Chapter 5 

Appendix A 

Appendix B 

Installation and Configuration 

Prerequisites and background information .......................................... 18 

Configuring the environment for use with backup software ............... 18 

Oracle environment configuration................................................ 18 

SSH equivalency configuration.................................................... 19 

About the RM CLI replication script............................................ 20 

Configuring EMC NetWorker ............................................................. 21 

Prerequisites ................................................................................. 21 

EMC NetWorker configuration: Part 1 ........................................ 21 

EMC NetWorker configuration: Part 2 ........................................ 28 

Configuring Symantec Veritas NetBackup .......................................... 29 

Prerequisites ................................................................................. 29 

Symantec Veritas NetBackup configuration: Part 1..................... 30 

Symantec Veritas NetBackup configuration: Part 2..................... 33 

Configuring EMC Replication Manager ............................................. 34 

Configuring RM for use with EMC NetWorker........................... 35 

Configuring RM for use with Symantec Veritas NetBackup....... 38 

Validation 

Performing a backup with EMC NetWorker ....................................... 42 

Monitoring the backup process .................................................... 42 

Preparing for restore and recovery with EMC NetWorker .................. 43 

Performing a backup with Symantec Veritas NetBackup ....................44 

Monitoring the backup process .................................................... 45 

Preparing for restore and recovery with Symantec Veritas NetBackup 46 

About archive logs ............................................................................... 47 

Backing up archive logs ............................................................... 47 

Conclusion 

Recovery Example 

Recovering the database ...................................................................... 52 

Restarting SAP .................................................................................... 75 

Manual Backup Example 

4 



About this 

Document 

EMC's commitment to consistently maintain and improve quality is led by 

the Total Customer Experience (TCE) program, which is driven by Six 

Sigma methodologies. As a result, Global Solutions Operations (GSO) has 

built customer integration labs to reflect real-world deployments in which 

TCE use cases are developed and executed. These use cases provide EMC 

with an insight into the challenges currently facing its customers. This 

document was produced as part of the EMC TCE program by the GSO TCE 

Customer Integration Labs working in collaboration with the EMC SAP 

Global Practice and Center for Excellence, EMC Engineering, and EMC 

technical field consultants. 

Purpose 

Audience 

This document describes the split-mirror based EMC Backup and Recovery 

for SAP Oracle with SAP BR*Tools solution. The solution was tested with 

EMC Replication Manager, EMC NetWorker, Symantec Veritas NetBackup, 

and the SAP ECC 6 (ERP2005) ABAP stack with SAP BR*Tools. The 

solution was validated by EMC Global Solutions Operations (GSO). 

This document is intended for EMC field personnel and account teams as a 

guide for designing and building an automated backup and recovery solution 

for an SAP production database by leveraging EMC hardware and software 

in an enterprise environment. 

It is assumed the reader is familiar with the following EMC and SAP 

products: 

• EMC Symmetrix DMX-3 

• EMC Disk Library 

• EMC Replication Manager 

• EMC TimeFinder 


About this Document 


• EMC NetWorker 

• Symantec Veritas NetBackup 

• SAP ECC6 (ERP 2005) 

Scope 

Related 

documents 

The information contained in this document is not intended to replace existing, 

detailed product implementation guides or pre-sale site evaluations. The steps 

outlined during each stage are high level in nature and should be read in 

conjunction with the documentation referenced throughout this guide. The setup 

of this environment simulates an enterprise environment. It is important to note 

that actual customer configurations will be different. 

The following EMC documents provide additional, relevant information: 

• EMC Replication Manager Support Matrix 

• Configuring Oracle for Use with Replication Manager 5.0 Technical Note 

• EMC Replication Manager 5.1.0 Product Guide 

• EMC Replication Manager 5.1.0 Administrator's Guide 

• EMC Replication Manager 5.1.0 Release Notes 

• EMC Replication Manager 5.1.0 Online Help 

• EMC NetWorker Module for SAP with Oracle Release 3.5 Administrator’s 

Guide 

• EMC NetWorker Module for SAP with Oracle Release 3.5 Installation Guide 

• EMC NetWorker Module for SAP with Oracle Release 3.5 Release Notes 

• EMC NetWorker Administration Guide 

• EMC Information Protection Software Compatibility Guide 

The following third-party documents provide additional, relevant information: 

• Veritas Netbackup for SAP Administror's Guide (for UNIX and Linux) 

• Veritas TechNote Document - Advanced Client Support in Netbackup for SAP 

• Symantec Veritas Netbackup - Information that Every SAP R/3 Administrator 

should know 

6 



1 

Solution 

Overview 

This chapter includes the following sections: 

• The business challenge ............................................................................ 8 

• The technology solution........................................................................... 8 

• Solution components................................................................................ 9 

• Physical architecture ................................................................................ 9 

• Hardware and software resources .......................................................... 11 




The business challenge 

The technology solution 

Today SAP customers face many challenges trying to meet backup and recovery 

requirements. Large databases with hundred of gigabytes take an extremely long 

time to back up using traditional backup-to-tape methods. If an online backup 

must run into busy production hours, this affects overall SAP production system 

performance and makes it difficult to choose an appropriate point in time if 

recovery is needed. System maintenance windows are generally too short to 

accommodate a full offline backup, and extending SAP downtime to perform a 

full offline backup is not practical because of the criticality of business uptime. 

The optimal solution for eliminating offline backups and reducing the windows 

for online backups is to make use of a storage system's split-mirror technology to 

make replicas of SAP production volumes. The volumes can then be mounted to 

another server and backed up from there. SAP backup (BR*) tools support 

split-mirror technology but leave the actual management of that technology to the 

storage provider. This can become quite complex and error-prone if manual 

scripting is used to manage the replicas. 

The EMC ® Backup and Recovery for SAP Oracle with SAP BR*Tools solution 

integrates SAP BR* tools with EMC Replication Manager to seamlessly manage 

the online creation and mounting of replica volumes. This eliminates the need to 

develop and maintain custom replica scripts and offloads the backup from the 

production SAP server. The solution also supports industry-leading backup 

products, such as EMC NetWorker ® and Symantec Veritas NetBackup, to further 

automate online backup and recovery of the SAP Oracle database. The solution 

also supports the use of EMC Disk Library virtual tape library to eliminate the 

problems of physical tape backups. 

As an additional benefit, the solution makes the production system available on a 

secondary system if the primary system becomes unavailable. 

8 



Solution components 

Solution components 

Physical architecture 

The EMC Backup and Recovery for SAP Oracle with SAP BR*Tools 

solution includes components from EMC, Symantec Veritas, SAP, HP, and 

Cisco. This section briefly describes the EMC, SAP, and Symantec Veritas 

components. For details on all of the components that make up the solution, 

see “Hardware and software resources” on page 11. 

• EMC Symmetrix ® DMX-3 

• EMC Disk Library 

• EMC Replication Manager 

• EMC TimeFinder ® 

• EMC NetWorker 

• Symantec Veritas NetBackup 

• SAP ECC 6 IDES ABAP stack 

The EMC Backup and Recovery for SAP Oracle with SAP BR*Tools 

solution was validated using both EMC NetWorker and Symantec Veritas 

NetBackup. These backup products are certified by SAP and are typically 

used in enterprise SAP environments. Figure 1 on page 10 illustrates the 

overall physical architecture of the solution. 

EMC Backup and Recovery for SAP Oracle with SAP BR*Tools Integration Guide 

9



EMC Replication Manager (Windows) 

Backup server (Windows) 

SAP 


SAP source (production) 

SAP target (standby) 

EMC Disk Library 

Ethernet 1 GB/s 

Production 2 GB/s FC SAN 

EMC Symmetrix DMX-3 

Figure 1 

Overall physical architecture 

10 



Hardware and software resources 

Hardware and software resources 

The following tables list the hardware and software resources used in the 

validated solution. 

Table 1 

Hardware resources 

Equipment Quantity Configuration 

Storage 1 EMC DMX-3 1500 

146 GB 15k drives 

SAP hosts 2 HP RX4640 

Four Itanium dual-core CPUs 

16 GB RAM 

HP-UX 11i v2 

RM and backup hosts 3 Dell PowerEdge 2650 

Two dual-core CPUs 

4 GB RAM 

Microsoft Windows Server 2003 R2 

Two 72 GB drives 

Virtual tape (disk) library 1 EMC EDL 4200 

Table 2 

Software resources 

Software Version Configuration/comments 

HP-UX 11i v2 HP-UX 11.23/IA64 Installed on SAP servers 

Oracle Database 10G Release 2 10.2.0.1 64-bit Installed on SAP servers 

SAP ECC 6 IDES ABAP stack ERP 2005 Installed on SAP servers 

Microsoft Windows Server 2003 Enterprise R2 32-bit version 

EMC Replication Manager v5.1 

Java JDK v1.4.2.13 Installed on SAP source and target servers and backup 

server 


11



Table 2 

Software resources (continued) 

Software Version Configuration/comments 

SAP BR*Tools v.7.0 Included with SAP kernel installation 

EMC NetWorker Server v.7.4 Installed on backup server 

NetWorker agent for HP-UX installed on SAP source and 

target servers 

SAP agent installed on SAP source and target servers 

NetWorker Storage Node installed on SAP source and target 

servers 

Symantec Veritas NetBackup Server v6.0 Installed on backup server 

NetBackup agent for HP-UX installed on SAP source and 

target servers 

SAP agent installed on SAP source and target servers 

NetBackup Media Server installed on SAP source and target 

servers 

12 



2 



• Process overview ................................................................................... 14 

• Process details........................................................................................ 14 




Process overview 

Process details 

The EMC Backup and Recovery for SAP Oracle with SAP BR*Tools solution 

automates the entire online backup process and allows it to be initiated from the 

backup server. The automated process includes synchronizing and splitting the 

production source mirror, mounting the mirror to the target using RM CLI, and 

backing up the replica to EDL using SAP BR*Tools and BRBACKUP. The 

solution automates the following sequence of events: 

1. The administrator initiates the backup job from the backup server, which 

then calls BRBackup on the SAP target host. 

2. BRBackup integrates with EMC Replication Manager, which automatically 

creates replicas of the production storage volumes while they remain online 

and mounts them on a target host, ready for backup. The replica volumes 

contain a recoverable, point-in-time image of the SAP production volumes 

3. The backup server backs up the replica volumes to the EDL virtual tape 

library. 

The recoverable point-in-time image can be restored from EDL to the target 

system. Only SAP BR*Tools and the backup server are required to perform 

recovery from EDL to the SAP target (standby) system. 

Following the restore operation, the database can be fully recovered to a specific 

point in time on the target system by copying the archive logs from source to 

target and applying them on the target. If a decision is then made to overwrite 

production, replication from target to source can be performed. 

Figure 2 on page 15 illustrates the backup scenario; Figure 3 on page 16 depicts 

the recover/restore scenario. A step-by-step description of each process follows 

each figure. 

14 



Process details 



4 

3 2 

1 4 





4 


Standard 


Data 


Data 

Mirror 




SYM-001454 

Figure 2 

Backup scenario 

The backup steps are as follows: 

1. The backup is initiated by the Backup server, which calls BRBackup on 

the SAP target host. 

2. The target host starts BRBackup, which puts Oracle into Hot Backup 

mode on the source and then calls Replication Manager (RM). 

3. RM synchronizes and splits the source/target mirror, mounts the target 

host, and returns the call to BRBackup. 

4. BRBackup takes Oracle out of Hot Backup mode on the source and 

initiates BACKINT. BACKINT then backs up the SAP database files on 

the target to EMC Disk Library and updates the file catalog on the 

Backup server, creating a record of the files that are being backed up. 


15





Catalogue 

12345 

34256 

Abcde 

3 

2 

3 

Logs 

4 

1 






Data 

3 





SYM-001455 

Figure 3 

Recover/restore scenario 

The recover/restore steps are as follows: 

1. An administrator uses BR*Tools or BRRestore to initiate a restore from the 

target host. 

2. BRRestore locates the backup set that the administrator specified and 

connects to the Backup server to locate the files to be restored. 

3. The Backup server calls the target host to start BACKINT, which initiates the 

restore. EMC Disk Library restores the appropriate files to the target host. 

4. The administrator applies the archive logs from the source to the target, 

resulting in a point-in-time recovery of the database. 

16 



3 

Installation and 

Configuration 


• Prerequisites and background information ............................................ 18 

• Configuring the environment for use with backup software ................. 18 

• Configuring EMC NetWorker................................................................ 21 

• Configuring Symantec Veritas NetBackup ............................................ 29 

• Configuring EMC Replication Manager................................................ 34 




Prerequisites and background information 

Before performing the configuration tasks provided in this chapter, ensure that 

the following components are installed on the appropriate systems. For 

information on software versions and installation locations, refer to “Hardware 

and software resources” on page 11. 

• SAP (which includes BR*Tools) is installed on both the source (production) 

and target (standby) systems. BR*Tools is used only on the target system 

within the context of the solution. 

• A backup server with software such as EMC NetWorker or Symantec Veritas 

NetBackup is installed. 

• A virtual tape library (such as EMC Disk Library) or a tape library is 

installed in conjunction with the backup server. The library must be visible 

from the EMC NetWorker Storage Node or Symantec Veritas NetBackup 

Media Server. 

• The following backup agents are installed on the appropriate systems: 

• NetWorker or NetBackup Agent for HP-UX on both the source and target 

• NetWorker or NetBackup Agent for SAP (NWSAP) on the target only 

• NetWorker Storage Node or Netbackup Media Server on the target only 

Configuring the environment for use with backup software 

Oracle environment configuration 

This section applies to both types of backup software used to validate the 

solution: EMC NetWorker and Symantec Veritas NetBackup. 

Perform the following steps to configure the Oracle environment for use with 

EMC NetWorker or Symantec Veritas NetBackup. 

1. (Optional) Upgrade to the most recent version of SAP DBA Tools 

(BR*Tools). The solution was validated with BR*Tools 7.0 patch 18. 

2. (NetBackup only) Ensure the Oracle pfile.ora and spfile.ora 

exist on the target system. The DBA can verify or create this file if necessary. 

3. Ensure that the Oracle listener is running on both the source and target. 

4. Ensure that the Oracle database is down on the target prior to running a 

backup or replication. 

5. Ensure that the RM client is running on both the source and target. 

18 



Configuring the environment for use with backup software 

6. For all files under /oracle///dbs, set permissions to 

755 and set ownership for owner/group to ora:ora. 

7. Ensure that the Oracle configuration files have the same path location 

and the same format as the archive logs. Consult the DBA. 

8. Ensure that the tnsnames.ora file on the target system includes an entry 

for the source system. This is required to put the source Oracle database 

into hot backup mode prior to replication. 

################ 

# Filename......: tnsnames.ora 

# Created.......: created by SAP AG, R/3 Rel. >= 6.10 

# Name..........: 

# Date..........: 

# @(#) $Id: 

//bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $ 

################ 

.WORLD= 

(DESCRIPTION = 

(ADDRESS_LIST = 

(ADDRESS = 

(COMMUNITY = SAP.WORLD) 

(PROTOCOL = TCP) 

(HOST = saphp09)



About the RM CLI replication script 

2. On the target, execute the following commands: 

$ cd /.ssh 

$ ssh cat /.ssh/id_rsa.pub >> authorized_keys 

$ ssh cat /.ssh/id_dsa.pub >> authorized_keys 

$ ssh cat /.ssh/id_rsa.pub >> authorized_keys 

$ ssh cat /.ssh/id_dsa.pub >> authorized_keys 

$ scp authorized_keys : /.ssh 

3. Ensure that user equivalency works on the target nodes: 

$ ssh 

The custom RM CLI replication script is called splitmirror.sh and it is located in 

the /oracle/SID//dbs directory. 

The script file must have permissions set to 755 and ownership set to 

ora:dba for owner/group. 

Note: The script must not generate any text outputs when running with BRBackup; 

otherwise, BRBackup will consider the text outputs as errors and the backup will fail. If 

the script produces messages to the console, the messsages must be redirected. During 

validation testing, stdin and stderr messages were redirected to two different files. 

The script is as follows: 

#!/bin/sh 

cd /opt/emc/rm/gui/ 

./rmcli /oracle///dbs/rmjob.log 

2>/oracle///dbs/rmjob.err 

connect host= port=65432 

login user= password= 

run-job name=netbackupJob appset=OraApp 

exit 

EOF 

20 



Configuring EMC NetWorker 


This section describes configuration tasks and their prerequisites. 

Configuration instructions are divided into two subsections. The first focuses 

on the modification of configuration files and file properties, while the 

second focuses on configuration tasks performed with the NetWorker 

graphical user interface (GUI). 

Prerequisites 

The following components must be installed prior to configuring EMC 

NetWorker: 

• NetWorker Agent for HP-UX 

• NetWorker Agent for SAP (NWSAP); the installation includes SAP files 

required by the solution 

• NetWorker Storage Node on the SAP target host 

• Tape or disk library (for example, EMC Disk Library) 

Note: Refer to the EMC NetWorker installation documentation for detailed 

installation instructions. 

EMC NetWorker configuration: Part 1 

To prepare configuration files and file properties for use with EMC 

NetWorker: 

1. Copy the BACKINT utility file from /opt/networker/bin/ to 

/usr/sap/SID/SYS/exe/run on the target system. Set permissions to 755 

and set ownership to root:sys for the owner/group. 

2. On the target host, copy the sample file initSID.utl from /etc to 

/oracle/SID//dbs. Adjust the initSID.utl as follows: 

pool = HP10MGroup



Note: If the hostname does not include a full domain name, EMC NetWorker backup 

may fail with an error message similar to the following: 

52858 11/30/07 13:42:54 2 0 0 1 14137 0 saphp10 backint 

Backint exiting at Nov 30 13:42:54 with fatal error 

Parameter Conflict: savegrp "server" is 

sap-2650-02.saptce.com, different from init.utl 

value sap-2650-02 

3. The SAP configuration file initSID.sap file is a key part of this solution. The 

file integrates BRBackup, EMC Replication Manager, and EMC NetWorker. 

On the target host, modify the initSID.sap file so that it corresponds to the 

following example. Pay particular attention to the lines shown in bold in the 

example. 

backup_mode = all 

restore_mode = all 

backup_type = online_split ← specify split mirror backup 

backup_dev_type = util_file ← specify to use the NetWorker util file 

backup_root_dir = /oracle//sapbackup 

stage_root_dir = /oracle//sapbackup 

compress = no 

compress_cmd = "compress -c $ > $" 

uncompress_cmd = "uncompress -c $ > $" 

compress_dir = /oracle//sapreorg 

archive_function = save 

archive_copy_dir = /oracle//sapbackup 

archive_stage_dir = /oracle//sapbackup 

remote_host = saphp09 ← target 

remote_user = ora 

tape_copy_cmd = cpio 

disk_copy_cmd = copy 

stage_copy_cmd = scp 

pipe_copy_cmd = rsh 

cpio_flags = -ovB 

cpio_in_flags = -iuvB 

cpio_disk_flags = -pdcu 

dd_flags = "obs=64k bs=64k" 

dd_in_flags = "ibs=64k bs=64k" 

saveset_members = 1 

copy_out_cmd = "dd ibs=8k obs=64k of=$" 

copy_in_cmd = "dd ibs=64k obs=8k if=$" 

rewind = "mt -f $ rew" 

rewind_offline = "mt -f $ offl" 

tape_pos_cmd = "mt -f $ fsf $" 

split_cmd = /oracle///dbs/splitmirror.sh ← RM Script 

to split mirror 

tape_size = 100G 

exec_parallel = 0 

22 




tape_address = /dev/rmt/0mn 

tape_address_rew = /dev/rmt/0m 

volume_archive = (A01, A02, A03, A04, A05, 

A06, A07, A08, A09, A10, 

A11, A12, A13, A14, A15, 

A16, A17, A18, A19, A20, 

A21, A22, A23, A24, A25, 

A26, A27, A28, A29, A30) 

volume_backup = (B01, B02, B03, B04, B05, 

B06, B07, B08, B09, B10, 

B11, B12, B13, B14, B15, 

B16, B17, B18, B19, B20, 

B21, B22, B23, B24, B25, 

B26, B27, B28, B29, B30) 

expir_period = 30 

tape_use_count = 100 

util_par_file = init.utl 

primary_db = 

4. In /oracle/SID//dbs, set permissions for the splitmirror.sh 

script file to 755 and set ownership for owner/group to root:sys. Note 

that the RM login account and password are defined in this file. 

#!/bin/sh 

cd /opt/emc/rm/gui/ 

./rmcli /oracle///dbs/rmjob.log 2>/oracle///dbs/rmjob.err 

connect host= port=65432 

login user= password= 

run-job name=brbackupJob appset=OraApp 

exit 

EOF 

# 

5. The NetWorker configuration file nsrsapsv.cfg controls the way the 

NetWorker server connects to the SAP system. Since nsrsapsv.cfg uses 

the ora account, the NetWorker configuration file must include all 

of the environment variable settings of that account, including the 

database user ID and password (system). To verify the ora 

environment variable settings, use the env command. NetWorker offers 

a tool to encrypt the database user (system DBA) and the password 

listed in nsrsapsv.cfg. The system DBA user and password are then 

encrypted and put at the end of the nsrsapsv.cfg file. By default, 

nsrsapsv.cfg is located under /nsr/res and is delivered with NWSAP. To 

encrypt the login information, run the nsrsapadm -c /nsr/res/nsrsapsv.cfg 

command and respond to the system prompts. Example output is shown 

below. 

# nsrsapadm -c /nsr/res/nsrsapsv.cfg 

Enter Operating System username: ora 


23



Enter password: 

Confirm password: 

32422:(pid 27719):Parameter OS_USR_PASSWD in configuration file 

/nsr/res/nsrsapsv.cfg is updated 

Is Oracle Database Authentication used? : y 

Enter Oracle Database username: system 

Enter password: 

Confirm password: 

32422:(pid 27719):Parameter ORACLE_USR_PASSWD in configuration file 

/nsr/res/nsrsapsv.cfg is updated 

# 

An example of nsrsapsv.cfg is shown below. Lines shown in bold are 

especially important within the context of the solution. 

# 

# This is the sample nsrsapsv.cfg file. 

# 

# This file contains settings for the NetWorker Module for SAP with 

# Oracle (a.k.a. NMSAP) used during scheduled backups. 

# 

# Note: Comments have a "#" in the first column. 

# 

######################################################################## 

### 

# BR_EXEC specifies the command that nsrsapsv will execute. The BR_EXEC 

# parameter can be any valid brbackup or brarchive command, including 

# any command line options. If a username and password are required to 

# execute the command, they should be encrypted into this file using the 

# nsrsapsv -c command, rather than using the -u option in this parameter. 

# For more information about when the username and password are required, 

# and how to encrypt them into this file, see the EMC NetWorker Module 

# for SAP with Oracle Administrator's Guide. 

# This is a required parameter. 

# 

BR_EXEC=brbackup ← ** BRBackup command is specified here. 

# ORACLE_HOME is a required environment variable. This should be set to 

the 

# value of ORACLE_HOME for the Oracle instance that will be backed up. 


# 

#ORACLE_HOME=/oracle/ 

ORACLE_HOME=/oracle// 

# NLS_LANG is a required environment variable. The format should be 

# LANGUAGE_TERRITORY.CHARACTERSET 

# Refer to your Oracle documentation for more information of this 

variable. 

# 

24 




NLS_LANG = AMERICAN_AMERICA.UTF8 

# SAP_BIN specifies the path to where the BR*Tools executables are 

installed. 

# This should also be where the backint binary resides. This path will 

be 

# added to the PATH environment variable so that the BR*Tools and 

backint 

# executables can be found. 


# 

#SAP_BIN=/usr/sap/SAP/SYS/exe/run 

SAP_BIN=/usr/sap//SYS/exe/run 

# SAPBACKUP specifies the temporary directory for the backup logs 

should go. 

# BR*Tools and backint both use this directory to store their temporary 

log 

# files. On UNIX systems, the default for this is 

$ORACLE_HOME/sapbackup. 

# On Windows, this is a required parameter. On UNIX, this parameter 

is only 

# required if the default is not $ORACLE_HOME/sapbackup. 

# 

SAPBACKUP=/oracle//sapbackup 

# ORACLE_SID specifies the SID of the Oracle instances to be backed 

up. If 

# this parameter is specified here, backint wil use the value of this 

# parameter for the Oracle SID. If this parameter is not specifed 

here, the 

# Oracle SID will be obtained from the save set name you entered when 

this 

# client was configured in the NetWorker software. For example, if you 

# entered backint:SAP:online_backup for the save set name during client 

# configuration and you do not specify a value for ORACLE_SID in this 

file, 

# then SAP will be used for the Oracle SID This parameter is only 

required 

# if you want to override the one specified by the save set name. 

# 

ORACLE_SID= 

DB_SID= 

# If RMAN is used for backing up database files, set 

NSR_SAP_USING_RMAN_OPTION 

# to 'yes' by uncommenting the following line. 

# 

# NSR_SAP_USING_RMAN_OPTION=yes 

# ORACLE_BIN specifies where the Oracle binaries are located. This 

path will 


25



# be appended to the PATH environment variable so that all Oracle binaries 

can 

# be found if needed. The default for this will be $ORACLE_HOME/bin. 

# This parameter is only required if the Oracle binaries are not located in 

# $ORACLE_HOME/bin. 

# 

# ORACLE_BIN=/oracle///bin 

dbs_ora_tnsname= 

dbs_ora_schema=SAPSR3 

dbms_type=ORA 

# SAPARCH, SAPREORG, SAPTRACE, and SAPCHECK are SAP environment variables 

that 

# are normally set in your SAP environment on Windows platforms. These 

# environment variables may be required for brbackup to run properly on 

Windows. 

# If these variables are not set on your Windows system, or if they need 

to be 

# overridden, they should be set here. 

# 

# SAPARCH=/oracle//saparch 

# SAPREORG=/oracle//sapreorg 

# SAPTRACE=/oracle//saptrace 

# SAPCHECK=/oracle//sapcheck 

SAPDATA_HOME=/oracle/ 

SHELL=/usr/bin/sh 

# PATH is used to add more search paths to the environment. Anything 

specified 

# here will be appended to the PATH environment variable. You may specify 

as 

# many PATH variables as you desire. You may specify multiple search 

paths, 

# using either one of the following methods: 

# 

# PATH=/export/home/dir1:/export/home/dir2:/home/dir1/dir2/dir3 

# 

# or 

# 

# PATH=/export/home/dir1 

# PATH=/export/home/dir2 

PATH=/opt/ssh/bin 

PATH=/opt/emc/rm/client/bin 

PATH=PATH=/oracle///bin:/oracle/:/usr/sap//SYS/exe/run:/usr/bin:/usr/ccs/ 

bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/ipf/bin:/opt/hparray/bi 

n:/opt/nettladm/bin:/opt/fcms/bin:/opt/sas/bin:/usr/bin/X11:/opt/resm 

on/bin:/usr/contrib/kwdb/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/graphi 

cs/common/bin:/opt/sfm/bin:/opt/upgrade/bin:/opt/ssh/bin:/opt/mx/bin: 

/opt/sec_mgmt/bastille/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/firefox: 

/opt/gnome/bin:/opt/ignite/bin:/opt/mozilla:/opt/perl/bin:/opt/sec_mg 

mt/spc/bin:/opt/java1.4/jre/bin:/opt/spb/bin:/opt/hpsmh/bin:/opt/thun 

derbird:/opt/gwlm/bin:/usr/contrib/bin/X11:/opt/networker/bin 

26 




# 

# This is an optional parameter. 

# Any _path= pair. This parameter can be used to append 

values 

# to an environment variable named _path (for example, 

LD_LIBRARY_PATH). 

# If an environment variable with this name already exists, then the 

value 

# listed here will be appended to the existing value for this 

environment 

# variable. If an environment variable with this name does not exist, 

it will 

# be created. 

# For example: 

# 

# 

LD_LIBRARY_PATH=/export/home/oracle/product/8.1.5/lib:/usr/openwin 

/lib 

# 


DIR_LIBRARY=/usr/sap//SYS/exe/run 

SHLIB_PATH=/usr/sap//SYS/exe/run:/oracle///lib 

# Any = pair. This parameter can be used to add any 

environment 

# variable named . You may specify any name=value pair. If the 

# environment variable specified by name already exists, then it will 

be 

# overwritten. For example: 

# 

# BR_TRACE=1 

# 

# will set the BR_TRACE environment variable equal to 1 in your 

environment, 

# which will instruct brbackup or brarchive to print out additional 

trace 

# information. This will override any other setting for BR_TRACE. 

# 


OS_USR_PASSWD=gsfcu0-mldgcd48 ← orasid account encrypted 

ORACLE_USR_PASSWD={xtrbd-mldgcd48 ← orasid password encrypted 

# 

** Brbackup command is specified here. 


27



EMC NetWorker configuration: Part 2 

To perform configuration tasks with the EMC NetWorker GUI: 

1. Open NetWorker Administration Console. 

2. At the top of the page select Configuration, expand Groups, right-click the 

appropriate group (or create a new group) and select Properties. 

3. On the Advanced tab, select Manual Restart under Options and change the 

Client Retries setting to 0. Otherwise, if a backup fails, multiple log files will 

be generated. Also, because multiple components are involved, manual 

intervention may be required. Thus, retrying automatically is unlikely to 

work. 

4. In the left pane, select Clients and create an entry for the SAP target client or, 

if the entry already exists, double-click it to view its properties. 

5. On the General tab, ensure that the Save set includes the entry backint: 

and select the appropriate Group. 

6. On the Apps & Modules tab, type the ora userID and password of the 

SAP target host. 

7. In the Backup Command field, type nsrsapsv -f /nsr/res/nsrsapsv.cfg. (This 

command will be executed on the target host.) 

8. On the Globals (1 of 2) tab, Globals (2 of 2) tab, and Info & Licensing tab, 

leave the default values unchanged. 

9. At the top of the page select Monitoring. 

28 



Configuring Symantec Veritas NetBackup 

10. On the Groups tab, ensure that a group appears. 

11. On the Devices tab, ensure that all devices are assigned to the Storage 

Node on the SAP server and that all devices are assigned to the same 

storage pool. 

12. At the top of the page select Media. 

13. Select Volumes and ensure that the appropriate volumes are set up. 

14. At the top of the page select Devices. 

15. On the Devices tab and ensure that the NetWorker devices on the virtual 

disk library are visible from the NetWorker server. 

16. On the Storage Nodes tab, ensure that the Storage Node is connected to 

the SAP target host and that the virtual disk library is visible. 


This section describes configuration tasks and their prerequisites. 

Configuration instructions are divided into two subsections. The first focuses 

on the modification of configuration files and file properties, while the 

second focuses on configuration tasks performed with the NetBackup 

graphical user interface (GUI). 

Prerequisites 

The following components must be installed prior to configuring Symantec 

Veritas NetBackup. 

• NetBackup Agent for HP-UX 

• NetBackup Agent for SAP (NWSAP); the installation includes SAP 

files required by the solution 

• NetBackup Media Server on the SAP target host 

• Tape or disk library (for example, EMC Disk Library) 


29



Note: Refer to the Veritas Netbackup Installation Guide and Veritas Netbackup for SAP 

Administrator's Guide for detailed installation instructions. 

Symantec Veritas NetBackup configuration: Part 1 

To prepare configuration files and file properties for use with Symantec Veritas 

NetBackup: 

1. Copy the BACKINT utility file from /usr/openv/netbackup/bin to 

/usr/sap/SID/SYS/exe/run on the target system. Set permissions to 755 and 

set ownership for owner/group to root:sys. 

2. Copy the NetBackup sample and script files for SAP:Backup the 

/oracle/SID//dbs folder. 

$ cd /usr/openv/netbackup/ext/db_ext/sap/scripts 

$ cp init* /oracle/SID//dbs 

3. Set the ownership and privilege parameters for initSID.sap and initSID.utl. 

$ cd /oracle/SID//dbs 

$ chown orasid:dba initSID.sap initSID.utl 

$ chmod 755 initSID.sap initSID.utl 

4. On the target host, copy the sample file initSID.utl from 

/usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle to 

/oracle/SID//dbs. Adjust the initSID.utl as follows: 

switch_list /oracle//sapbackup/.switch.lis 

switch_sem /oracle//sapbackup/.switch.sem 

switch_log /oracle//sapbackup/.switch.log 

backint_dir /oracle///dbs ← backint file location 

server sap-2650-03.saptce.com ← hostname of the Netbackup server 

client saphp08 ←SAP target host 

drives 4 ← number of drives used for backup 

policy SAPBackup ← policy name to be used on Netbackup 

schedule Default-Application-Backup 

retry_backup 1 

fail_backup 

5. Copy the Symantec Veritas NetBackup script (supplied by Symantec 

Veritas), sap_online_backup, from 

/usr/openv/netbackup/ext/db_ext/scripts/sap_oracle to /oracle/SID//dbs. Change permissions to 755 and change ownership for 

owner/group to ora:dba. 

6. Adjust the sap_online_backup file as indicated by the lines in bold in the 

example below. 

30 




Note: The Oracle database user (system) login information appears in this file. 

#!/bin/sh 

#bcpyrght 

#*************************************************************************** 

#* $VRTScprght: Copyright 1993 - 2005 VERITAS Software Corporation, All Rights 

Reserved $ * 

#*************************************************************************** 

#ecpyrght 

# 

#NOTE:IF your SAP user (in this script orasap) runs in C shell, environmental 

#variables can not be exported. In that case, you should modify this script to 

#work in your environment. For example: 

# SAP_SERVER=$SAP_SERVER; export SAP_SERVER; (Correct for Bourne and Korn 

shells) 

# can change into 

# setenv SAP_SERVER $SAP_SERVER; (Correct for C shell) 

# 

# 

#This environment variable are created by Netbackup (bphdb) 

# 

echo "SAP_SCHEDULED = $SAP_SCHEDULED" 

echo "SAP_USER_INITIATED = $SAP_USER_INITIATED" 

echo "SAP_SERVER = $SAP_SERVER" 

echo "SAP_POLICY = $SAP_POLICY" 

RETURN_STATUS=0 

# SAP_ENV - Holds environmental variables. 

SAP_ENV="" 

# 

# If SAP_SERVER exists then export it to make it available to backint. 

# 

if [ -n "$SAP_SERVER" ] 

then 

SAP_ENV="$SAP_ENV SAP_SERVER=$SAP_SERVER; export SAP_SERVER;" 

#if Oracle DBA acount(orasap user) uses C Shell,comment the above line and 

uncomment the next line 

# SAP_ENV="$SAP_ENV setenv SAP_SERVER $SAP_SERVER;" 

fi 

# 

# If SAP_POLICY exists then export it to make it available to backint. 

# 

if [ -n "$SAP_POLICY" ] 

then 

SAP_ENV="$SAP_ENV SAP_POLICY=$SAP_POLICY; export SAP_POLICY;" 

#if Oracle DBA account(orasap user) uses C Shell, comment the above line and 

uncomment the next line 

# SAP_ENV="$SAP_ENV setenv SAP_POLICY $SAP_POLICY;" 

fi 

# 

# Full online backup with dynamic BEGIN/END BACKUP switch 

# 


31



CMD_LINE="$SAP_ENV brbackup -c -d util_file_online -u system/ -m all" 

# 

# The username on the "su" command needs to be replaced with the correct user 

# name. 

# 

echo "Execute $CMD_LINE" 

su - ora -c "$CMD_LINE"



remote_host = saphp09 

remote_user = ora 

stage_copy_cmd = scp 

pipe_copy_cmd = rsh 

split_cmd = /oracle///dbs/splitmirror.sh ← RM 

script to sync and split 

expir_period = 30 

tape_use_count = 100 

util_par_file = init.utl 

primary_db = 

Symantec Veritas NetBackup configuration: Part 2 

To perform configuration tasks with the Symantec Veritas NetBackup GUI: 

1. Open NetBackup Administration Console. 

2. In the left pane, expand NetBackup Management and Policies. 

3. Right-click the SAP policy and select Properties. 

4. On Attributes tab, select the options shown above. 

5. On the Schedules tab, ensure that schedules are enabled all the time. 

6. On the Clients tab, verify that the SAP server is listed. 


33



7. On the Backup Selections tab, ensure that the full path to the splitmirror.sh 

script is specified. 

Note: For troubleshooting, this script can be run manually from the backup host. 

8. In the left pane, expand Host Properties, select Media Server, and verify that 

the SAP system and the backup server (NetBackup) are listed. 

Configuring EMC Replication Manager 

This section provides condensed procedures for configuring EMC Replication 

Manager (RM) for use with EMC NetWorker and Symantec Veritas NetBackup. 

For detailed information about configuring RM, refer to the following EMC 

documents: 

• Configuring Oracle for Use with Replication Manager 5.0 Technical Note 

• EMC Replication Manager 5.1.0 Product Guide 

• EMC Replication Manager 5.1.0 Administrator's Guide 

• EMC Replication Manager 5.1.0 Release Notes 

34 




Configuring RM for use with EMC NetWorker 

Perform the following steps to configure RM for use with EMC NetWorker. 

1. Install the Oracle HP-UX RM agent on the source and target systems. 

2. Add the SAP hosts to the Hosts section in Replication Manager Console. 

3. Create a storage pool of a suitable size and number of devices, and 

ensure that it is visible to the target host. This is the pool that will 

contain the database replica. 

Note: RM can find suitable devices for the replica, but it is recommended to 

create the pool manually so that you can retain control over which devices are 

used. 

4. Create an application set. Ensure that the entire Oracle database is 

selected for replication. 

Create an RM job 

To define an RM job to perform replication from the source to target system: 

1. Select the application set created previously. 

2. Enter a job name. 

3. Select an appropriate replication technology: either TimeFinder/Mirror 

or TimeFinder/Clone. 

Note: The solution was validated using TimeFinder/Mirror with EMC 

NetWorker and TimeFinder/Clone with Symantec Veritas NetBackup. Either 

technology should work with either backup product. 

4. Specify an appropriate retention period or replica count. 

5. In Advanced Replication Settings, select Use Consistent Split. 

6. Under Consistency Method, select Online Without Hot Backup Mode. 


35



7. Click OK, and click Next. 

8. Select an appropriate storage pool. 

9. On the Mount Options page, select Mount the Replica. 

36 




10. Under Oracle , select Recover the Database. 

11. Ensure that the following values are present under Recover the 

Database: 

• Fail Mount if SID exists: No 

• Recover Type: Prepare only 

• Run recover as OS user: ora 

• OS user password: 

• ORACLE_Home: 

• Database Name: Use original name 

• SID name: Use original name 

12. On the Starting the Job page, select Manually or Using a Third Party 

Scheduler. 

13. On the Users to be Notified page, specify any users to be notified and 

click Next. 

14. On the Completing the Job page, select all settings and click Finish. 


37



Test the RM job 

To test the RM job you just created: 

1. In Replication Manager Console, navigate to Jobs. 

2. Right-click the job and select Run. 

Configuring RM for use with Symantec Veritas NetBackup 

Perform the following steps to configure RM for use with Symantec Veritas 

NetBackup. 

1. Install the Oracle HP-UX RM agent on the source and target systems. 

2. Add the SAP hosts to the Hosts section in Replication Manager Console. 

3. Create a storage pool of a suitable size and number of devices, and ensure 

that it is visible to the target host. This is the pool that will contain the 

database replica. 

Note: RM can find suitable devices for the replica, but it is recommended to create 

the pool manually so that you can retain control over which devices are used. 

4. Create an application set. Ensure that the entire Oracle database is selected 

for replication. 

Create an RM job 

To define an RM job to perform replication from the source to target system: 

1. Select the application set created previously. 

2. Enter a job name. 

3. Select an appropriate replication technology: either TimeFinder/Mirror or 

TimeFinder/Clone. 

Note: The solution was validated using TimeFinder/Mirror with EMC NetWorker and 

TimeFinder/Clone with Symantec Veritas NetBackup. Either technology should work 

with either backup product. 

4. Specify an appropriate retention period or replica count. 

5. In Advanced Replication Settings, select Use Consistent Split. 

6. Under Consistency Method, select Online Without Hot Backup Mode. 

38 




7. Click OK, and click Next. 

8. Select an appropriate storage pool. 

9. On the Mount Options page, select Mount the Replica. 

10. Under the Oracle SID, deselect Recover the Database. 

Note: If Recover the Database is selected, the Oracle SPFile is deleted from the 

Oracle database and the backup fails. This was observed only with Netbackup; 

the issue was not observed with NetWorker. 


39



11. On the Starting the Job page, select Manually or Using a Third Party 

Scheduler. 

12. On the Users to be Notified page, specify any users to be notified and click 

Next. 

13. On the Completing the Job page, select all settings and click Finish. 

Test the RM job 

It is important to verify that the RM job created using the RM graphical user 

interface works before using the custom RM CLI replication script. 

To test the RM job you just created: 

1. In Replication Manager Console, navigate to Jobs. 

2. Right-click the job and select Run. 

40 



4 

Validation 


• Performing a backup with EMC NetWorker ......................................... 42 

• Preparing for restore and recovery with EMC NetWorker .................... 43 

• Performing a backup with Symantec Veritas NetBackup...................... 44 

• Preparing for restore and recovery with Symantec Veritas NetBackup. 46 

• About archive logs ................................................................................. 47 


Validation 


Performing a backup with EMC NetWorker 

Use the instructions provided in this section to verify that the installation and 

configuration of the various solution components has been successful. 

To perform a backup with EMC NetWorker: 

1. Open NetWorker Administration Console. 

2. At the top of the page select Monitoring. 

3. On the Groups tab, right-click the group created for SAP backup and click 

Start. 

Monitoring the backup process 

EMC NetWorker does not provide a GUI-based mechanism for monitoring the 

backup process. To monitor the backup, you can view the following log files: 

• Most recent backup ANF file (BRBackup log) 

• NetWorker log at the OS level 

• BACKINT log 

• Replication Manager (RM) log 

42 



Preparing for restore and recovery with EMC NetWorker 

Viewing the ANF file 

To view the most recent backup ANF file located in the 

/oracle//sapbackup directory: 

1. Connect to the SAP target host with the ora account. 

2. Change directory to /oracle//sapbackup. 

3. Type ls -ltr and locate the most recent ANF file. 

4. Type cat .anf to view the ANF file. 

Note: The ANF file will be empty until the replication completes. 

Viewing the NetWorker log 

To view the NetWorker log at the OS level, navigate to /nsr/applogs on the 

target host and review the most recent file nsrsapsv._. 

Viewing the BACKINT log 

To view the BACKINT log, navigate to /nsr/applogs/backint and locate the 

most recent file backint.log.raw. This raw file is not readable with a text 

editor; it can be rendered only with the command nsr_render_log. The 

command is: 

$ nsr_render_log backint..log.raw > log.txt 

You can then open the file log.txt with a text file viewer/editor. 

Viewing the RM log 

To view the RM log, navigate to /tmp or /opt/emc/rm/logs/client and locate 

the most recent files with names that begin with ERM. You can also view the 

log RM from the Replication Manager Console GUI. 

Preparing for restore and recovery with EMC NetWorker 

Unlike the backup process, restore processes cannot be automated. This is 

not a limitation of the backup software. Restore and recovery operations 

require input from the SAP or database administrator, who must specify 

which backup set to restore and which archive logs to apply for point-in-time 

recovery. 

Note: This section describes how to prepare for manual restore and recovery on the 

SAP target system, not the source system. 

To prepare for manual restore and recovery on the target SAP system: 

1. Ensure that the Oracle listener is running on the target. 


43

Validation 


2. Ensure that the SAP application and the Oracle database are down. 

3. For all files under /oracle///dbs, set permissions to 755 

and set ownership for owner/group to ora:ora. 

4. Ensure that there is no access to file systems /oracle//xxx (where xxx 

is sapdata, orilog, or mirrorlog). Otherwise, the replication process will fail 

because the target system will not be able to unmount the file system. 

5. In the tnsnames.ora file on the target, ensure that there is an entry for the 

target system. 

################ 



# Name..........: 

# Date..........: 

# @(#) $Id: 


################ 

.WORLD= 



(ADDRESS = 



(HOST = saphp10)


Performing a backup with Symantec Veritas NetBackup 

3. Right-click the SAP policy and select Manual Backup. 

Monitoring the backup process 

4. Under Monitoring > Groups, right-click the SAP backup group and click 

Start to start the backup. 

Symantec Veritas NetBackup does not provide a GUI-based mechanism for 

monitoring the backup process. To monitor the backup, you can view the 

following log files: 

• Most recent backup ANF file (BRBackup log) 

• NetWorker log at the OS level 

• BACKINT log 

• Replication Manager (RM) log 

Viewing the ANF file 

To view the most recent backup ANF file located in the 

/oracle//sapbackup directory: 

1. Connect to the SAP target host with the ora account. 

2. Change directory to /oracle//sapbackup. 

3. Type ls -ltr and locate the most recent ANF file. 

4. Type cat .anf to view the ANF file. 


45

Validation 


Note: The ANF file will be empty until the replication completes. 

Viewing the BACKINT log 

To view the BACKINT log, navigate to /usr/openv/netbackup/logs/backint and 

locate the most recent file log.. 

Viewing the RM log 

To view the RM log, navigate to /tmp and locate the most recent files with names 

that begin with ERM. You can also view the RM log from the Replication 

Manager Console GUI. 

Preparing for restore and recovery with Symantec Veritas 

NetBackup 

Unlike the backup process, restore processes cannot be automated. This is not a 

limitation of the backup software. Restore and recovery operations require input 

from the SAP or database administrator, who must specify which backup set to 

restore and which archive logs to apply for point-in-time recovery. 

Note: This section describes how to prepare for manual restore and recovery on the SAP 

target system, not the source system. 

To prepare for manual restore and recovery on the target SAP system: 

1. Ensure that the Oracle listener is running on the target. 

2. Ensure that the SAP application and the Oracle database are down. 

3. For all files under /oracle///dbs, set permissions to 755 

and set ownership for owner/group to ora:ora. 

4. Ensure that there is no access to file systems /oracle/SID/xxx (where xxx is 

sapdata, orilog, or mirrorlog). Otherwise, the replication process will fail 

because the target system will not be able to unmount the file system. 

5. In the tnsnames.ora file on the target, ensure that there is an entry for the 

target system. 

################ 



# Name..........: 

# Date..........: 

# @(#) $Id: 


################ 

.WORLD= 

46 



About archive logs 



(ADDRESS = 



(HOST = saphp10)

Validation 


included in the backup job that backs up the database on the target system. 

Alternative options to back up the archive logs within the context of this solution 

are as follows: 

• Run BRArchive continuously on the source system to back up archive logs 

as they are generated. The backup agent and SAP agent must be installed on 

the source system. During a restore, the the archive logs are redirected from 

the source to the target system. 

• Back up the archive logs on the source system using file system backup. 

Restore the archive logs to the target system using file system restore. A 

backup agent is required only on the source system. 

• Transfer the archive logs from the source to the target. This option was used 

to validate this solution. 

48 



5 

Conclusion 

This integration guide describes a validated SAP ERP production backup 

and recovery solution for Oracle. The solution utilizes SAP BR*Tools with 

split-mirror technology on an EMC Symmetrix DMX-3 storage system in 

conjunction with EMC Replication Manager and EMC NetWorker or 

Symantec Veritas NetBackup. The solution provides the following benefits: 

• Eliminates manual scripting of replica creation and management and 

eliminates the ongoing maintenance of such scripts 

• Eliminates downtime caused by offline backups; increases the 

availability of the production environment; all systems remain online 

during backups 

• Eliminates sluggish system performance associated with conventional 

online backups 

• Eliminates reliability concerns related to tape backups and physical tape 

libraries 

• Reduces manual intervention required by conventional backup methods; 

both backup and restore can be administered by a single BASIS 

administrator 

• Increases the speed of point-in-time recovery, because data retrieval is 

faster from disk than from tape 

EMC can help accelerate assessment, design, implementation, and 

management while lowering the implementation risks and cost of creating a 

backup and recovery solution for SAP and Oracle with SAP BR*Tools. 

To learn more about this and other solutions contact an EMC representative 

or visit www.EMC.com/solutions/sap. 


Conclusion 


50 


A 

Recovery 

Example 

This appendix provides an example of a complete recovery operation using 

the EMC Backup and Recovery for SAP Oracle with SAP BR*Tools 

solution with either EMC NetWorker or Symantec Veritas NetBackup. 

• Recovering the database ........................................................................ 52 

• Restarting SAP....................................................................................... 75 



Recovering the database 

BRRECOVER options for restore and recovery 

To recover the database on the target system: 

1. Use BR*Tools to restore the database to the target system. 

2. Log on to the target system. 

3. Start BR*Tools 

4. Select option 5: Restore and recovery 

5. Select option 2: Database point-in-time recovery 

6. For option 3, specify system/ as shown below. 

1 - BRRECOVER profile (profile) ...... [init.sap] 

2 ~ BACKINT/Mount profile (parfile) .. [init.utl] 

3 - Database user/password (user) .... [system/********] 

4 - Recovery interval (interval) ..... [30] 

5 - Confirmation mode (confirm) ...... [yes] 

6 - Scrolling line count (scroll) .... [20] 

7 - Message language (language) ...... [E] 

8 - BRRECOVER command line (command) . [-p init.sap -r init.utl -t dbpit 

-i 30 -s 20 -l E] 

Standard keys: c - cont, b - back, s - stop, r - refr, h - help 

Press “c” to continue. 

BR0280I BRTOOLS time stamp: 2007-12-12 10.36.54 

BR0663I Your choice: 'c' 

BR0259I Program execution will be continued... 

BR0291I BRRECOVER will be started with options '-p init.sap -r init.utl -t 

dbpit -i 30 -s 20 -l E' 


BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort: 


Database point-in-time recovery main menu 

1 = Set point-in-time for recovery 

2 * Select database backup 

3 * Check the status of database files 

4 * Restore control files 

52 



5 * Restore data files 

6 * Restore split control files 

7 * Restore and apply incremental backup 

8 * Restore and apply archivelog files 

9 * Open database and post-processing 

10 * Exit program 

11 - Reset program status 


------------------------------------------------------------------------------- 

BR0662I Enter your choice: 

Choose option 1 and press enter. 

------------------------------------------------------------------------------- 

Options for point-in-time recovery of database 

1 # Database instance of archivelog thread (instance) . [] 

2 ~ Last archivelog sequence to apply (last_seq) ...... [361] 

3 ~ Last system change number to apply (last_scn) ..... [] 

4 ~ End point-in-time for recovery (end_pit) .......... [] 


------------------------------------------------------------------------------- 


Choose option 2 and specify the last archive log to apply; then press “c” to 

continue. 


1 + Set point-in-time for recovery 

2 = Select database backup 

3 * Check the status of database files 



6 * Restore split control files 

7 * Restore and apply incremental backup 






------------------------------------------------------------------------------- 

BR0662I Enter your choice 

Choose option 2. 


53


BR0280I BRRECOVER time stamp: 2007-12-12 10.43.40 

BR0663I Your choice: '2' 

BR0613I Database instance is shut down 

BR0750I Database instance will be mounted now 





BR0257I Your reply: 'c' 



BR0330I Starting and mounting database instance ... 


BR0331I Start and mount of database instance successful 

BR0773W Archivelog entry for 'SEQ: 361' not found in V$ARCHIVED_LOG - BRRECOVER will 

try to use available redo log files 

BR0668I Warnings or errors occurred - you can continue to ignore them or go back to 

repeat the last action 



Ignore the warning/errors and Press “c” to continue. 

This error was expected since archive log 361 did not exist at the time of the 

backup. This archive log was created after the backup. 




BR0699I Reading log file /oracle//sapbackup/back.log ... 


BR0659I List menu 105 + please select one or more entries 

------------------------------------------------------------------------------- 

Database backups for database point-in-time recovery 

Pos. Log Start Type Mode Device Rc 

1 = bdwtejky.anf 2007-12-05 18.20.16 onl_split all util_file 0 

54 




------------------------------------------------------------------------------- 

BR0662I Enter your selection: 

BR*Tools finds the last good backup set and proposes to use it. In this case it 

is bdwtejky.anf. Press “c”to continue. 


BR0663I Your selection: 'c' 


BR0699I Reading log file /oracle//sapbackup/bdwtejky.anf ... 

BR0772I Checking the availability of archivelog files for database instance 

... 

BR0699I Reading log file /oracle//saparch/arch.log for device type 

DISK... 


DISK... 


STAGE... 


TAPE/BACKINT/RMAN... 


STAGE... 

BR0017W Offline redo log file '/tmp//arch/1_359_340584684.dbf' not found - 

it might be needed for recovery 





BR0668I Warnings or errors occurred - you can continue to ignore them or go back 

to repeat the last action 



The warnings indicate that the archive logs are not in the /tmp//arch 

directory. Since the source system uses a different name format for archive 

logs, BR*Tools indicates that the archive logs cannot be found. Note that the 

archive logs were previously copied from source to target. This is a bug in 

BR*Tools. Ignore these warnings and press “c” to continue. 



55



2 + Select database backup 

3 = Check the status of database files 



6 # Restore split control files 

7 # Restore and apply incremental backup 






------------------------------------------------------------------------------- 


Choose option 3 



BR0614I Database instance is mounted 

BR0750I Database instance will be remounted now with mode 'IMMEDIATE' 








BR0307I Shutting down database instance ... 


BR0308I Shutdown of database instance successful 

BR0370I Directory /oracle//sapbackup/vdwulfax created 

BR0202I Saving /oracle//origlogA/cntrl/cntlr.dbf 

BR0203I to /oracle//sapbackup/vdwulfax/cntlr.dbf ... 





56 



BR0755I Checking the status of database files for instance ... 

BR0428W File /oracle//sapdata1/sr3_1/sr3.data1 will be overwritten 


















































57
















































BR0428W File /oracle//sapdata1/sr3usr_1/sr3usr.data1 will be overwritten 

BR0428W File /oracle//sapdata2/undo_1/undo.data1 will be overwritten 

BR0428W File /oracle//sapdata1/sysaux_1/sysaux.data1 will be overwritten 

BR0428W File /oracle//sapdata4/system_1/system.data1 will be overwritten 

58 



BR0668I Warnings or errors occurred - you can continue to ignore them or go back 

to repeat the last action 







3 + Check the status of database files 

4 = Restore control files 









------------------------------------------------------------------------------- 






BR0064I Database instance will be shut down now with mode 'IMMEDIATE' 



Press 'c' to continue. 








BR0202I Saving /oracle//origlogA/log_g11m1.dbf 

BR0203I to /oracle//sapbackup/vdwulfax/log_g11m1.dbf ... 


59


BR0202I Saving /oracle//origlogB/log_g12m1.dbf 


BR0202I Saving /oracle//origlogA/log_g13m1.dbf 


BR0202I Saving /oracle//origlogB/log_g14m1.dbf 



BR0657I Input menu 111 - please check/enter input values 

------------------------------------------------------------------------------- 

BRRESTORE main options for restore of database files 

1 - BRRESTORE profile (profile) ........ [init.sap] 

2 - BRBACKUP backup run (backup) ....... [bdwtejky.anf] 

3 - Fill-up previous restores (fillup) . [no] 

4 - Restore device type (device) ....... [util_file] 

5 - BACKINT/Mount profile (parfile) .... [/oracle///dbs/init.utl] 

6 # Database user/password (user) ...... [system/********] 

7 - Files for restore (mode) ........... [0] 


------------------------------------------------------------------------------- 




2 - Query mode (query) ............... [no] 

3 # Compression mode (compress) ...... [no] 

4 # Parallel execution (execute) ..... [0] 

5 - Additional output (output) ....... [no] 


7 - BRRESTORE command line (command) . [-p init.sap -b bdwtejky.anf -d util_file 

-r /oracle///dbs/init.utl -m 0 -l E] 


------------------------------------------------------------------------------- 




BR0291I BRRESTORE will be started with options '-p init.sap -b bdwtejky.anf -d 

util_file -r /oracle///dbs/init.utl -m 0 -l E' 


60 








=============================================================================== 

BR0401I BRRESTORE 7.00 (18) 

BR0169I Value 'online_split' of parameter/option 'backup_type/-t' ignored for 

'brrestore' - 'online' assumed 

BR0405I Start of file restore: rdwultfs.rsb 2007-12-12 13.17.28 

BR0428W File /oracle//origlogA/cntrl/cntlr.dbf will be overwritten 

BR0428W File /oracle//origlogB/cntrl/cntrl.dbf will be overwritten 

BR0428W File /oracle//sapdata1/cntrl/cntrl.dbf will be overwritten 

BR0428W File /oracle//origlogA/cntrl/cntlr.dbf will be overwritten 

BR0428W File /oracle//origlogB/cntrl/cntrl.dbf will be overwritten 

BR0428W File /oracle//sapdata1/cntrl/cntrl.dbf will be overwritten 

BR0280I BRRESTORE time stamp: 2007-12-12 13.17.28 

BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRESTORE: 






BR0407I Restore of database: 

BR0408I BRRESTORE action ID: rdwultfs 

BR0409I BRRESTORE function ID: rsb 

BR0449I Restore mode: partial 

BR0411I Database files for restore: 

/oracle//origlogA/cntrl/cntlr.dbf 

/oracle//origlogB/cntrl/cntrl.dbf 

/oracle//sapdata1/cntrl/cntrl.dbf 

/oracle//origlogA/cntrl/cntlr.dbf 

/oracle//origlogB/cntrl/cntrl.dbf 

/oracle//sapdata1/cntrl/cntrl.dbf 

BR0419I Files will be restored from backup: bdwtejky.anf 2007-12-05 18.20.16 

BR0416I 1 file found to restore, size 25.516 MB 

BR0421I Restore device type: util_file 





61






BR0229I Calling backup utility with function 'restore'... 

BR0278I Command output of '/usr/sap//SYS/exe/run/backint -u -f restore -i 

/oracle//sapbackup/.rdwultfs.lst -t file -p /oracle///dbs/init.utl': 


#FILE..... /oracle//sapbackup/cntrl.dbf 

#RESTORED. 1196897169 


BR0374I 1 of 1 file restored by backup utility 

BR0230I Backup utility called successfully 

BR0351I Restoring /oracle//origlogA/cntrl/cntlr.dbf 

BR0355I from /oracle//sapbackup/cntrl.dbf ... 

BR0351I Restoring /oracle//origlogB/cntrl/cntrl.dbf 


BR0351I Restoring /oracle//sapdata1/cntrl/cntrl.dbf 


BR0351I Restoring /oracle//origlogA/cntrl/cntlr.dbf 


BR0351I Restoring /oracle//origlogB/cntrl/cntrl.dbf 


BR0351I Restoring /oracle//sapdata1/cntrl/cntrl.dbf 


BR0406I End of file restore: rdwultfs.rsb 2007-12-12 13.19.44 


BR0403I BRRESTORE completed successfully with warnings 

=============================================================================== 

BR0292I Execution of BRRESTORE finished with return code 1 





62 



You can ignore the warning/errors. Ensure that the control files have been 

restored successfully. Press “c” to continue. 





4 + Restore control files 

5 = Restore data files 








------------------------------------------------------------------------------- 


Choose option 5. 



BR0613I Database instance is shut down 

BR0750I Database instance will be mounted now 













------------------------------------------------------------------------------- 

BRRESTORE main options for restore of database files 


63


1 - BRRESTORE profile (profile) ........ [init.sap] 

2 - BRBACKUP backup run (backup) ....... [bdwtejky.anf] 

3 - Fill-up previous restores (fillup) . [no] 

4 - Restore device type (device) ....... [util_file] 

5 - BACKINT/Mount profile (parfile) .... [/oracle///dbs/init.utl] 

6 # Database user/password (user) ...... [system/********] 

7 - Files for restore (mode) ........... [all] 


------------------------------------------------------------------------------- 








------------------------------------------------------------------------------- 

Additional BRRESTORE options for restore of database files 


2 - Query mode (query) ............... [no] 

3 # Compression mode (compress) ...... [no] 

4 # Parallel execution (execute) ..... [0] 

5 - Additional output (output) ....... [no] 


7 - BRRESTORE command line (command) . [-p init.sap -b bdwtejky.anf -d util_file 

-r /oracle///dbs/init.utl -m all -l E] 


------------------------------------------------------------------------------- 






BR0291I BRRESTORE will be started with options '-p init.sap -b bdwtejky.anf -d 

util_file -r /oracle///dbs/init.utl -m all -l E' 



64 







=============================================================================== 

BR0401I BRRESTORE 7.00 (18) 

BR0169I Value 'online_split' of parameter/option 'backup_type/-t' ignored for 

'brrestore' - 'online' assumed 

BR0405I Start of file restore: rdwuluad.rsb 2007-12-12 13.26.19 








































65





















































66 









BR0428W File /oracle//sapdata1/sr3usr_1/sr3usr.data1 will be overwritten 

BR0428W File /oracle//sapdata2/undo_1/undo.data1 will be overwritten 

BR0428W File /oracle//sapdata1/sysaux_1/sysaux.data1 will be overwritten 

BR0428W File /oracle//sapdata4/system_1/system.data1 will be overwritten 







BR0456I Probably the database must be recovered due to restore from online backup 


BR0407I Restore of database: 

BR0408I BRRESTORE action ID: rdwuluad 

BR0409I BRRESTORE function ID: rsb 

BR0449I Restore mode: ALL 

BR0419I Files will be restored from backup: bdwtejky.anf 2007-12-05 18.20.16 

BR0416I 100 files found to restore, total size 195340.781 MB 

BR0421I Restore device type: util_file 








BR0229I Calling backup utility with function 'restore'... 

BR0278I Command output of '/usr/sap//SYS/exe/run/backint -u -f restore 

-i /oracle//sapbackup/.rdwuluad.lst -t file -p /oracle///dbs/init.utl': 


#FILE..... /oracle//sapdata1/sr3_1/sr3.data1 

#RESTORED. 1196897170 


67




#RESTORED. 1196897170 



#RESTORED. 1196897170 

… 

… 

Section removed for the purpose of this example. 


#FILE..... /oracle//sapdata1/sysaux_1/sysaux.data1 

#RESTORED. 1196899729 



#RESTORED. 1196899729 


BR0374I 100 of 100 files restored by backup utility 

BR0230I Backup utility called successfully 

BR0406I End of file restore: rdwuluad.rsb 2007-12-12 14.03.28 


BR0403I BRRESTORE completed successfully with warnings 

=============================================================================== 

BR0292I Execution of BRRESTORE finished with return code 1 






At this stage, the database is restored and is recoverable. 


68 







5 + Restore data files 



8 = Restore and apply archivelog files 





------------------------------------------------------------------------------- 






BR0750I Database instance will be remounted now with mode 'IMMEDIATE' 















BR0776I First redo log file sequence to apply for database instance : 359 

BR0773W Archivelog entry for 'SEQ: 361' not found in V$ARCHIVED_LOG - BRRECOVER 

will try to use available redo log files 


69


BR0777I Last redo log file sequence to apply for database instance : 361 









BR0699I Reading log file /oracle//saparch/arch.log for device type DISK... 


TAPE/BACKINT/RMAN... 

BR0699I Reading log file /oracle//saparch/arch.log for device type STAGE... 


BR0660I List display 113 - no selection possible 

------------------------------------------------------------------------------- 

Archivelog files to apply of database instance 

Pos. Sequence Status Apply From Disk Tape Util Rman Stage 

1 - 359 in_arch yes arch .... .... .... .... .... 




------------------------------------------------------------------------------- 


BR*Tools automatically selects the archive logs to be applied after the backup is 

taken. The last archive log (361 in this case) is the one selected earlier. Press “c” 

to continue. 






------------------------------------------------------------------------------- 

Applying archivelog files of database instance 

1 - First sequence number (first_seq) .. [359] 

70 



2 - Last sequence number (last_seq) .... [361] 

3 - Use backup control file (back_ctl) . [yes] 

4 ~ Parallel recovery (degree) ......... [] 


------------------------------------------------------------------------------- 






BR0781I All archivelog files to be applied are on disk - no restore required 



------------------------------------------------------------------------------- 

Applying archivelog group of database instance 

1 - Apply unattended (unattend) ....... [no] 

2 - First sequence number (first_seq) . [359] 

3 - Last sequence number (last_seq) ... [361] 

4 - SQLPLUS command (command) ......... [recover from '/tmp//arch' database 

until cancel using backup controlfile] 


------------------------------------------------------------------------------- 






BR0783I Archivelog files with sequence number 359-361 of database instance 

will be applied now 









71


BR0336I Applying offline redo log file /tmp//arch/1_359_638531002.dbf ... 




BR0337I Offline redo log file /tmp//arch/1_359_638531002.dbf applied 

successfully 



successfully 



successfully 


BR0784I Media recovery completed 


BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRECOVER: 

Ensure the media recovery is complete and press “c” to continue. 









8 + Restore and apply archivelog files 

9 = Open database and post-processing 




------------------------------------------------------------------------------- 


Select option 9 




BR0064I Database instance will be shut down now with mode 'IMMEDIATE' 




72 












------------------------------------------------------------------------------- 

Options for opening database instance 

1 ~ Reset logs option (reset_logs) .. [resetlogs] 

2 * Open database command (command) . [alter database open resetlogs] 


------------------------------------------------------------------------------- 







BR0786I Database instance will be opened now in mode 'resetlogs' 

BR0787I No more archivelog files can be applied after database has been opened 

BR0675I Do you want to perform this action? 

BR0676I Enter 'y[es]/c[ont]' to perform the action, 'n[o]' to skip it, 's[top]' 

to abort: 

Press “c” or “y” to continue. 



BR0677I The action will be performed... 



BR0304I Starting and opening database instance ... 


BR0305I Start and open of database instance successful 

BR0795W Tablespace PSAPTEMP has no files defined in database 


73



BR0319I Control file copy created: /oracle//sapbackup/vdwulfax/cntrl.new 

26755072 


BR0595I Selecting indexes with NOLOGGING created during or after the selected backup 

bdwtejky.anf 2007-12-05 18.20.16 ... 

BR0285I This function can take several seconds/minutes - be patient... 


BR0596I No indexes found with NOLOGGING created during or after the selected backup 

bdwtejky.anf 2007-12-05 18.20.16 


BR0716I Database point-in-time recovery completed 


BR0655I Control menu 103 - please decide how to proceed 

------------------------------------------------------------------------------- 









8 + Restore and apply archivelog files 

9 + Open database and post-processing 

10 = Exit program 



------------------------------------------------------------------------------- 


7. Ensure that the Database has opened successfully. 

Note: Note that PSAPTEMP is not backed up or restored. It is the customer’s 

responsibility to re-create the PSAPTEMP tablespace. 

8. Select option 10 to exit BR*Tools. 

74 


Restarting SAP 

Restarting SAP 

Once the recovery is complete, you can restart SAP: 

1. Telnet to the target system using the adm account. 

2. Start SAP with the startsap command. 

> startsap 

Checking Database 

------------------------------ 

ABAP Database is running 

Starting SAP-Collector Daemon 

------------------------------ 

******************************************************************** 

**** 

* This is Saposcol Version COLL 20.90 700 - v2.05 for HP-UX - 28.7.2006 

* Usage: saposcol -l: Start OS Collector 

* saposcol -k: Stop OS Collector 

* saposcol -d: OS Collector Dialog Mode 

* saposcol -s: OS Collector Status 

* Starting collector (create new process) 

******************************************************************** 

**** 

saposcol on host saphp10 started 

Starting SAP Instance DVEBMGS00 

------------------------------ 

Startup-Log is written to /home/adm/startsap_DVEBMGS00.log 

Instance Service on host saphp10 started 

Instance on host saphp10 started 

3. Launch the SAP GUI and ensure that the application is running. 


75


76 


B 

Manual Backup 

Example 

You can validate the backup process itself (without testing the 

synchronization and split of the mirror) by performing a simple online 

backup manually from the target host. 

1. In the init.sap file, change the backup_type value to “online.” 

2. Start BR*Tools and follow the system prompts, as shown below. 

> brtools 

BR0651I BRTOOLS 7.00 (18) 


BR0656I Choice menu 1 - please make a selection 

-------------------------------------------------------------------- 

BR*Tools main menu 

1 = Instance management 

2 - Space management 

3 - Segment management 

4 - Backup and database copy 

5 - Restore and recovery 

6 - Check and verification 

7 - Database statistics 

8 - Additional functions 

9 - Exit program 


-------------------------------------------------------------------- 


4 --> "4" for database backup 


BR0656I Choice menu 9 - please make a selection 

-------------------------------------------------------------------- 

Backup and database copy 

1 = Database backup 

2 - Archivelog backup 

3 - Database copy 

4 - Non-database backup 

5 - Backup of database disk backup 


Manual Backup Example 

6 - Verification of database backup 

7 - Verification of archivelog backup 

8 - Additional functions 



------------------------------------------------------------------------ 


C --> Choose "continue" or "1" for database backup. 

------------------------------------------------------------------------ 

BRBACKUP main options for backup and database copy 

1 - BRBACKUP profile (profile) ....... [initSID.sap] 

2 - Backup device type (device) ...... [util_file] 

3 # Tape volumes for backup (volume) . [] 

4 ~ BACKINT/Mount profile (parfile) .. [/oracle/SID//dbs/initSID.utl] 

5 - Database user/password (user) .... [/] 

6 - Backup type (type) ............... [online] 

7 - Disk backup for backup (backup) .. [no] 

8 # Delete disk backup (delete) ...... [no] 

9 ~ Files for backup (mode) .......... [all] 


------------------------------------------------------------------------ 


c --> ensure all parameters are correct. 

------------------------------------------------------------------------ 

Additional BRBACKUP options for backup and database copy 

1 - Confirmation mode (confirm) ....... [yes] 

2 - Query mode (query) ................ [no] 

3 # Compression mode (compress) ....... [no] 

4 - Verification mode (verify) ........ [no] 

5 - Fill-up previous backups (fillup) . [no] 

6 # Parallel execution (execute) ...... [0] 

7 - Additional output (output) ........ [no] 

8 - Message language (language) ....... [E] 

9 - BRBACKUP command line (command) ... [-p initSID.sap -d util_file -r 

/oracle/SID//dbs/initSID.utl -t online -m all -k no -l E] 


------------------------------------------------------------------------ 


c --> ensure all parameters are correct. 

Make sure backup running well and successfully 

Example Successful backup process : 

BR0051I BRBACKUP 7.00 (18) 

BR0055I Start of database backup: xxxxxx.anf 2007-09-17 09.00.49 

BR0315I 'Alter database begin backup' successful 

BR0280I BRBACKUP time stamp: 2007-09-17 09.00.53 

BR0229I Calling backup utility with function 'backup'... 

78

EMC Backup and Recovery for SAP Oracle and SAP BRTools ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?