EMC Backup and Recovery for SAP with IBM DB2 on IBM AIX ...

<strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> 

<strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX 

Enabled by <strong>EMC</strong> Symmetrix DMX-4, <strong>EMC</strong> CLARiiON CX4, 

<strong>EMC</strong> Replication Manager, <strong>IBM</strong> Tivoli Storage Manager, <strong>and</strong> <strong>EMC</strong> NetWorker 

Integration Guide 

<strong>EMC</strong> Global Solutions 

42 South Street 

Hopkinton MA 01748-9103 

1.508.435.1000 

www.<strong>EMC</strong>.com

Copyright <strong>and</strong> Trademark In<strong>for</strong>mation 

Copyright © 2009 <strong>EMC</strong> Corporation. All rights reserved. 

Published March 2009 

<strong>EMC</strong> believes the in<strong>for</strong>mation in this publication is accurate as of its publication date. The in<strong>for</strong>mation is subject 

to change <strong>with</strong>out notice. 

Benchmark results are highly dependent upon workload, specific application requirements, <strong>and</strong> system design 

<strong>and</strong> implementation. Relative system per<strong>for</strong>mance will vary as a result of these <strong>and</strong> other factors. There<strong>for</strong>e, this 

workload should not be used as a substitute <strong>for</strong> a specific customer application benchmark when critical capacity 

planning <strong>and</strong>/or product evaluation decisions are contemplated. 

All per<strong>for</strong>mance data contained in this report was obtained in a rigorously controlled environment. Results 

obtained in other operating environments may vary significantly. 

<strong>EMC</strong> Corporation does not warrant or represent that a user can or will achieve similar per<strong>for</strong>mance expressed in 

transactions per minute. 

No warranty of system per<strong>for</strong>mance or price/per<strong>for</strong>mance is expressed or implied in this document. Use, 

copying, <strong>and</strong> distribution of any <strong>EMC</strong> software described in this publication requires an applicable software 

license. 

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

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

<strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX Enabled by <strong>EMC</strong> Symmetrix DMX-4, <strong>EMC</strong> 

CLARiiON CX4, <strong>EMC</strong> Replication Manager, <strong>IBM</strong> Tivoli Storage Manager, <strong>and</strong> <strong>EMC</strong> NetWorker Integration 

Guide 

P/N H5994 

2 

<strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX Integration Guide

Contents 

About this Document 

Purpose................................................................................................... 7 

Audience ................................................................................................ 7 

Scope...................................................................................................... 8 

Related documents................................................................................. 8 

Chapter 1 

Chapter 2 

Solution Overview 

The business challenge ........................................................................10 

The technology solution .......................................................................10 

Solution components ............................................................................11 

Physical architecture ............................................................................12 

Hardware <strong>and</strong> software resources ........................................................14 

Solution Design 

Process overview .................................................................................18 

Storage design ......................................................................................18 

<strong>Backup</strong> process design .........................................................................19 

<strong>Recovery</strong> process design ......................................................................20 

Design considerations ..........................................................................21 

Filesystem backup vs. database-specific backup.......................... 21 

Split-mirror backup....................................................................... 21 

<strong>SAP</strong> operational recovery ............................................................. 21 

Archive logs.................................................................................. 22 

Source <strong>and</strong> backup host storage on same storage array................ 22 

Multiplexing <strong>and</strong> physical vs. virtual tape libraries...................... 23 

<strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX Integration Guide 

3


Chapter 3 

Chapter 4 

Chapter 5 

Appendix A 

Installation <strong>and</strong> Configuration 

Prerequisites <strong>and</strong> background in<strong>for</strong>mation .......................................... 26 

Configuring Replication Manager ....................................................... 27 

Creating an application set ........................................................... 28 

Creating a Replication Manager job............................................. 29 

Configuring <strong>EMC</strong> NetWorker ............................................................. 31 

Prerequisites ................................................................................. 31 

Configuration through the NetWorker Administration Console.. 32 

Pre-comm<strong>and</strong> script configuration ............................................... 43 

Installing <strong>and</strong> configuring <strong>IBM</strong> TSM ERP module ............................. 44 

Prerequisites ................................................................................. 44 

Configuring the Tivoli Storage Manager server........................... 44 

Configuring the Tivoli Storage Manager clients.......................... 47 

Installing DP <strong>for</strong> <strong>SAP</strong>................................................................... 48 

Post-installation steps ................................................................... 49 

Scheduling a backup job............................................................... 50 

Pre-comm<strong>and</strong> script configuration ............................................... 55 

<strong>Backup</strong> script configuration ......................................................... 55 

Validation 

Per<strong>for</strong>ming a backup <strong>with</strong> <strong>EMC</strong> NetWorker ....................................... 58 

Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>EMC</strong> NetWorker .................. 59 

Restore the backup image from EDL to the backup host............. 59 

Recover the database <strong>and</strong> apply archive logs at the backup......... 59 

Restore validated <strong>SAP</strong> database from the backup to the source .. 60 

Per<strong>for</strong>ming a backup <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager ....................62 

Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager 64 

Restore the backup image from EDL to the backup host............. 64 

Recover the database <strong>and</strong> apply archive logs at the backup......... 65 

Restore validated <strong>SAP</strong> database from the backup to the source .. 66 

Conclusion 

Reference Documentation 

<strong>SAP</strong> Notes .................................................................................... 73 

<strong>IBM</strong> Redbook ............................................................................... 73 

4 

<strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIXIntegration Guide


Appendix B 

Appendix C 

Monitoring the <strong>Backup</strong> Process 

Configuration Files 

vendor.env .................................................................................... 81 

initae2.utl ...................................................................................... 81 


5


6 

<strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIXIntegration Guide

About this 

Document 

<strong>EMC</strong>'s commitment to consistently maintain <strong>and</strong> improve quality is led by the 

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

methodologies. As a result, <strong>EMC</strong> has built Customer Integration Labs in its 

Global Solutions Centers to reflect real-world deployments in which TCE use 

cases are developed <strong>and</strong> executed. These use cases provide <strong>EMC</strong> <strong>with</strong> an insight 

into the challenges currently facing its customers. 

This document was produced as part of the <strong>EMC</strong> TCE program by the GSC TCE 

Customer Integration Labs working in collaboration <strong>with</strong> the <strong>EMC</strong> <strong>SAP</strong> Global 

Solutions Practice, <strong>EMC</strong> Engineering, <strong>and</strong> <strong>EMC</strong> technical field consultants. 

Purpose 

Audience 

This integration guide describes the <strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> 

<strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX solution. The solution was validated <strong>with</strong> <strong>EMC</strong> 

Symmetrix DMX-4, <strong>EMC</strong> CLARiiON CX4, <strong>EMC</strong> Replication Manager, the 

<strong>SAP</strong> ERP 6.0 ABAP stack, <strong>EMC</strong> NetWorker, <strong>and</strong> <strong>IBM</strong> Tivoli Storage Manager. 

The solution was validated by <strong>EMC</strong> Global Solutions Centers (GSC). 

The document is intended to be used by both pre- <strong>and</strong> post-sales technical 

consultants to assist <strong>with</strong> the design <strong>and</strong> configuration of a customer 

environment. It is assumed the reader is familiar <strong>with</strong> the following <strong>EMC</strong>, <strong>IBM</strong>, 

<strong>and</strong> <strong>SAP</strong> products: 

• <strong>EMC</strong> CLARiiON CX4 UltraScale series 

• <strong>EMC</strong> Symmetrix DMX-4 

• <strong>EMC</strong> Replication Manager 

• <strong>EMC</strong> Disk Library 

• <strong>EMC</strong> NetWorker 

• <strong>IBM</strong> Tivoli Storage Manager 


7

About this Document 

• <strong>SAP</strong> ERP 6.0 ABAP Stack 

• <strong>IBM</strong> <strong>DB2</strong> 

Scope 

Related 

documents 

The in<strong>for</strong>mation 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 <strong>and</strong> should be read in 

conjunction <strong>with</strong> 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 <strong>EMC</strong> documents provide additional, relevant in<strong>for</strong>mation: 

• <strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX Enabled by 

<strong>EMC</strong> Symmetrix DMX-4, <strong>EMC</strong> CLARiiON CX4, <strong>EMC</strong> Replication Manager, 

<strong>IBM</strong> Tivoli Storage Manager, <strong>and</strong> <strong>EMC</strong> NetWorker Reference Architecture 

• <strong>EMC</strong> Replication Manager Support Matrix 

• <strong>EMC</strong> Replication Manager 5.1.3 Product Guide 

• <strong>EMC</strong> Replication Manager 5.13 Administrator's Guide 

• <strong>EMC</strong> NetWorker Release 7.4 Service Pack 2 Administration Guide 

• <strong>EMC</strong> NetWorker Version 7.4 Service Pack 2 Comm<strong>and</strong> Reference Guide 

• <strong>EMC</strong> NetWorker Module <strong>for</strong> <strong>DB2</strong> Release 2.1 Administration Guide 

• Backing up <strong>DB2</strong> With <strong>IBM</strong> Tivoli Storage Management 

• Tivoli Storage Manager For Enterprise Resource Planning Data Protection 

<strong>for</strong> <strong>SAP</strong> Installation <strong>and</strong> User's Guide <strong>for</strong> <strong>DB2</strong> 

• <strong>IBM</strong> Tivoli Storage Manager Implementation Guide 

• <strong>IBM</strong> Tivoli Storage Manager <strong>for</strong> Unix <strong>and</strong> Linux <strong>Backup</strong> -Archive Client 

Installation <strong>and</strong> User Guide 

• <strong>SAP</strong> Best Practice: <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> my<strong>SAP</strong> Business Suite 

8 


1 

Solution 

Overview 

This chapter includes the following sections: 

• The business challenge...........................................................................10 

• The technology solution .........................................................................10 

• Solution components ..............................................................................11 

• Physical architecture...............................................................................12 

• Hardware <strong>and</strong> software resources...........................................................14 


9


The business challenge 

The technology solution 

In today's world, <strong>SAP</strong> customers face many challenges trying to meet their 

backup <strong>and</strong> recovery requirements: 

1. Large databases <strong>with</strong> thous<strong>and</strong>s of gigabytes take an extremely long time to 

back up using traditional backup-to-tape methods. 

2. Online backups that run into busy production hours affect overall <strong>SAP</strong> 

production system per<strong>for</strong>mance <strong>and</strong> make it difficult to choose an 

appropriate point in time if recovery is needed. 

3. System maintenance windows are too short to accommodate a full offline 

backup, while longer <strong>SAP</strong> downtime to per<strong>for</strong>m an offline backup is not 

practical because of the criticality of business uptime. 

There<strong>for</strong>e, a solution is required to provide a highly reliable, cost-effective, data 

protection strategy <strong>for</strong> the mission critical <strong>SAP</strong> business applications. 

One of the most efficient ways to eliminate the need <strong>for</strong> production downtime 

<strong>and</strong> to reduce the time required to per<strong>for</strong>m full <strong>SAP</strong> backups is to leverage the 

replication technologies available in storage systems. <strong>EMC</strong>'s split-mirror 

replication technology can be used to make replicas of <strong>SAP</strong> production volumes 

that can then be mounted to another server (a backup host) <strong>for</strong> backup <strong>with</strong>out 

affecting the production system. 

Not only does this approach minimize the effect of the backup process on the 

production system, but it also provides an additional level of protection <strong>and</strong> the 

ability to execute a faster operational recovery from the backup host. This host 

can be used as a secondary system if the primary system becomes unavailable. 

The backup management software can still be used to manage backups while 

taking advantage of these replication technologies at the storage level. 

The <strong>EMC</strong> ® <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX solution 

uses <strong>EMC</strong> Replication Manager to seamlessly manage the online creation <strong>and</strong> 

mounting of replica volumes. This eliminates the need to develop <strong>and</strong> maintain 

custom replication scripts, <strong>and</strong> offloads the backup from the production <strong>SAP</strong> 

server. The solution also supports industry-leading backup products, such as 

<strong>EMC</strong> NetWorker ® <strong>and</strong> <strong>IBM</strong> Tivoli Storage Manager (TSM), <strong>for</strong> integration <strong>with</strong> 

existing backup systems <strong>and</strong> processes <strong>and</strong> uses the <strong>EMC</strong> Disk Library virtual 

tape library to eliminate the problems of physical tape backups. 

10 


Solution components 

Solution components 

The <strong>EMC</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX solution 

includes components from <strong>EMC</strong>, <strong>IBM</strong>, <strong>SAP</strong>, <strong>and</strong> Cisco. For details on all of the 

components that make up the solution, see “Hardware <strong>and</strong> software resources” 

on page 14. 

• <strong>EMC</strong> Symmetrix ® DMX-4 

• <strong>EMC</strong> CLARiiON ® CX4 UltraScale series 

• <strong>EMC</strong> Disk Library 

• <strong>EMC</strong> Replication Manager 

• <strong>EMC</strong> SnapView 

• <strong>EMC</strong> TimeFinder ® 

• <strong>EMC</strong> NetWorker 

• <strong>IBM</strong> Tivoli Storage Manager 

• <strong>SAP</strong> ERP 6.0 IDES 


11


Physical architecture 


was validated using both <strong>EMC</strong> NetWorker <strong>and</strong> <strong>IBM</strong> Tivoli Storage Manager. 

These backup products are certified by <strong>SAP</strong> <strong>and</strong> are typically used in enterprise 

<strong>SAP</strong> environments. 

Figure 1 illustrates the physical architecture of the solution as validated in the 

<strong>EMC</strong> NetWorker environment. 

Replication Manager 

(Windows) 

Source <strong>SAP</strong> 

Database Server 

<strong>Backup</strong> <strong>SAP</strong> 


<strong>EMC</strong> NetWorker Server 

(Windows) 

<strong>SAP</strong> 


Production 1GBps Ethernet 

Production 2GBps FC SAN 

<strong>EMC</strong> CLARiiON CX4 UltraScale Series 

EDL 

GEN-001029 

Figure 1 

Physical architecture as validated in the <strong>EMC</strong> NetWorker environment 

12 


Physical architecture 

Figure 2 illustrates the physical architecture of the solution as validated in the 

<strong>IBM</strong> TSM environment. 

Source <strong>SAP</strong> 


<strong>Backup</strong> <strong>SAP</strong> 


TSM Server 


(Windows) 




Production 1GBps Ethernet 

Production 2GBps FC SAN 

<strong>EMC</strong> Symmetrix DMX-4 

EDL 

GEN-001028 

Figure 2 

Physical architecture as validated in the <strong>IBM</strong> TSM environment 

Note: The <strong>EMC</strong> storage, DMX-4 <strong>and</strong> CX4, is interchangeable in the two validated 

environments. 


13


Hardware <strong>and</strong> software resources 

Table 1 <strong>and</strong> Table 2 list the hardware <strong>and</strong> software resources used in the validated 

solution. 

Table 1 

Hardware resources 

Equipment Quantity Configuration 

Storage array 1 <strong>EMC</strong> Symmetrix DMX-4 

146 GB 15k drives 

ucode: 5773 (123.83) 

Storage array 1 <strong>EMC</strong> CLARiiON CX4 UltraScale series 

146 GB 15k drives 

FLARE ® : 04.28.000.5.003 

Fibre Channel switch 1 Cisco MDS 9509 

64 ports 

Network switch 1 Cisco 3560G 

64 ports 

<strong>SAP</strong> server TSM environment: 2 

NetWorker environment: 2 

<strong>IBM</strong> p570 

Four CPUs 

8 GB RAM 

<strong>IBM</strong> AIX 5.3 ML06 64-bit 

Two Emulex LP11002-E HBAs 

<strong>EMC</strong> Replication Manager 

server 

1 Dell 1950 

Two dual-core 3.0 GHz Intel Pentium 4 processors 

6 GB memory 

Two 73 GB 10k internal SCSi disks 

Two on-board 10/100/1000 MB Ethernet NICs 

<strong>EMC</strong> NetWorker server 1 Dell PowerEdge 2650 

2 CPUs 

4 GB RAM 

TSM server 1 <strong>IBM</strong> p570 

Four CPUs 

8 GB RAM 

<strong>IBM</strong> AIX 5.3 ML06 64-bit 

Two Emulex LP11002-E HBAs 

<strong>EMC</strong> EDL Storage 1 DL-4206 

14 


Hardware <strong>and</strong> software resources 

Table 2 

Software resources 

Software Version Configuration/comments 

<strong>IBM</strong> AIX 5.3 <strong>IBM</strong> AIX 5.3 ML06 64-bit Installed on <strong>SAP</strong> source <strong>and</strong> backup 

<strong>IBM</strong> <strong>DB2</strong> 9.1 <strong>IBM</strong> <strong>DB2</strong> 9.1 Fix Pack 2 Installed on <strong>SAP</strong> source <strong>and</strong> backup 

<strong>SAP</strong> Applications ERP 6.0 Installed on <strong>SAP</strong> source <strong>and</strong> backup, ABAP Stack only 

<strong>EMC</strong> PowerPath ® 5.1.0 Installed on <strong>SAP</strong> source <strong>and</strong> backup 

Microsoft Windows 2003 Enterprise Edition 32-bit R2 SP2 Installed on RM <strong>and</strong> NetWorker servers 

<strong>EMC</strong> NetWorker 7.4.2 Installed on backup server 

AIX Agent installed on <strong>SAP</strong> backup server 

<strong>DB2</strong> Agent installed on <strong>SAP</strong> backup server 

Note: AIX Agent <strong>and</strong> <strong>DB2</strong> Agent must also be installed on 

the <strong>SAP</strong> source host if a user wants to restore to the 

source host directly. 

NetWorker Storage Node installed on <strong>SAP</strong> backup server 

<strong>EMC</strong> Solutions Enabler 6.5.0.12 or later Installed on <strong>SAP</strong> source <strong>and</strong> backup 

<strong>EMC</strong> Replication 

Manager 

5.1 SP3 Storage management software 

RM Agent installed on <strong>SAP</strong> source <strong>and</strong> backup servers 

<strong>EMC</strong> ADMSnap 2.9.0.0.7 Installed on <strong>SAP</strong> source <strong>and</strong> backup servers 

For NetWorker environment only 

<strong>EMC</strong> Navisphere ® CLI 6.28.0.4.25 Installed on <strong>SAP</strong> source <strong>and</strong> backup servers 


<strong>EMC</strong> Navisphere Agent 6.28.0.4.25 Installed on <strong>SAP</strong> source <strong>and</strong> backup servers 


Java JDK 1.4.2 64-bit Installed on <strong>SAP</strong> source <strong>and</strong> backup servers 

<strong>IBM</strong> Tivoli Storage 

Manager 

5.5 64-bit Server installed on TSM server; Client/ERP modules 

installed on <strong>SAP</strong> backup server 


15


16 


2 



• Process overview....................................................................................18 

• Storage design ........................................................................................18 

• <strong>Backup</strong> process design ...........................................................................19 

• <strong>Recovery</strong> process design ........................................................................20 

• Design considerations.............................................................................21 


17


Process overview 

Storage design 


automates the entire online backup <strong>and</strong> recovery process using the backup 

management software (<strong>EMC</strong> NetWorker <strong>and</strong> <strong>IBM</strong> TSM) <strong>and</strong> <strong>EMC</strong> Replication 

Manager. The automated process includes initiating the backup job, replicating 

the production source image to the backup host, <strong>and</strong> backing up the replica to 

EDL. The solution automates the following sequence of events: 

1. The administrator-scheduled backup job is initiated by the backup 

management software (<strong>EMC</strong> NetWorker or <strong>IBM</strong> TSM), which is the central 

point of backup <strong>and</strong> recovery operations. 

2. The backup management software utilizes <strong>EMC</strong> Replication Manager to 

create replicas of the production database image while the production 

database remains online <strong>and</strong> mounts the replicas on the backup host. 

3. The backup management software backs up the replica to the EDL virtual 

tape library. 

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

host by an administrator. Following the restore operation, the database can be 

fully recovered to a specific point in time on the backup system by copying the 

transaction logs from the source host to the backup host <strong>and</strong> applying them on the 

backup host. If a decision is then made to overwrite production, the administrator 

may choose to per<strong>for</strong>m a restoration from the backup host to the source using 

<strong>EMC</strong> Replication Manager. 

For the <strong>DB2</strong> replication, <strong>SAP</strong> systems are installed on both source <strong>and</strong> backup 

hosts. The database directory, primary <strong>and</strong> secondary logs, data files, <strong>and</strong> 

temporary tablespace are hosted on the <strong>EMC</strong> Symmetrix/CLARiiON array <strong>and</strong> 

are replicated from the source to the backup host. The rest of the volumes can be 

hosted on either the <strong>EMC</strong> Symmetrix/CLARiiON array or on local disks. They 

are not replicated to the backup system. 

It is important to note that the offline logs generated by the database during 

normal operations should be backed up independently by traditional means (tape) 

<strong>and</strong> kept available to be applied to the replica if necessary. 

Both the production host <strong>and</strong> the backup host are connected to the <strong>EMC</strong> 

Symmetrix/CLARiiON array. The <strong>EMC</strong> Disk Library (EDL) is visible only to 

the backup host since the backup operation is per<strong>for</strong>med on the host only. 

EDL is configured to emulate a specific tape library <strong>with</strong> four tape drives. Virtual 

tapes are created <strong>with</strong>in the tape library <strong>and</strong> managed by a volume pool by the 

18 


<strong>Backup</strong> process design 

<strong>Backup</strong> process design 

backup management software. The backup process is configured to take 

advantage of multiple streams <strong>with</strong>in each tape drive <strong>and</strong> the multiplexing of 

backup sessions on all available drives. 

Figure 3 illustrates the backup process. 

1 


(Windows) 

<strong>Backup</strong> 

Management Server 

Ethernet 1 Gbps 

Production 2 Gbps FC SAN 

2 3 

4 


<strong>SAP</strong> Source host 


<strong>SAP</strong> <strong>Backup</strong> host 

EDL 

CX/DMX 

GEN-001034 

Figure 3 

<strong>Backup</strong> process 

1. The backup management software calls <strong>EMC</strong> Replication Manager as a 

pre-backup call to start the clone process. 

2. <strong>EMC</strong> Replication Manager synchronizes the mirror volume to the 

production volume, splits the mirror, <strong>and</strong> mounts it to the backup host. 

3. The backup management software initiates a database backup on the backup 

host. 

4. The backup management software backs up the replica to <strong>EMC</strong> Disk 

Library. After the backup, the environment is ready <strong>for</strong> the next backup 

cycle. 


19


<strong>Recovery</strong> process design 

Figure 4 illustrates the restore/recovery process. 


(Windows) 

Ethernet 1 Gbps 

Production 2 Gbps FC SAN 

1 


Management Server 


3 

5 


4 

2 

<strong>SAP</strong> Source host 

<strong>SAP</strong> <strong>Backup</strong> host 

EDL 

CX/DMX 

GEN-001035 

Figure 4 

<strong>Recovery</strong> process 

1. The backup host runs the <strong>DB2</strong> restore comm<strong>and</strong> to call the backup 

management server to start the restore process. 

2. The backup management software restores the backup from EDL to the 

backup host. 

3. An administrator copies the archive logs from the <strong>SAP</strong> source to the backup. 

4. The administrator applies the archive logs to the backup host, resulting in a 

point-in-time recovery of the database. 

5. <strong>EMC</strong> Replication Manager restores the copy of the database back to the 

source host. 

20 


Design considerations 


There are considerations <strong>and</strong> implications during any design decisions. This 

section describes a few topics that must be considered when architecting a 

backup <strong>and</strong> recovery infrastructure <strong>for</strong> <strong>SAP</strong> on AIX/<strong>DB2</strong>. One of the objectives 

of this section is to address potential customer questions regarding this backup 

<strong>and</strong> recovery solution. 

Filesystem backup vs. database-specific backup 

A database-specific backup refers to a job that backs up a database by interacting 

<strong>with</strong> the database management software (i.e., <strong>DB2</strong> server). On the other h<strong>and</strong>, a 

filesystem backup is per<strong>for</strong>med by backing up the files that make up the database 

<strong>with</strong>out interacting <strong>with</strong> the database management software (<strong>and</strong> <strong>with</strong> no regards 

to the files' internal structure). 

A database backup is required <strong>for</strong> the following scenarios: 

• To back up while the database is online. 

• To apply transaction log records to recover changes made after the backup 

image was created. 

A database backup is per<strong>for</strong>med in this use case. 

Split-mirror backup 

The <strong>IBM</strong> <strong>DB2</strong> database can be initialized as a clone of the production database 

<strong>and</strong> placed in a roll <strong>for</strong>ward pending state or used as a backup image to restore 

the production database in a split-mirror environment. <strong>EMC</strong> storage supports the 

split-mirror backup <strong>for</strong> <strong>DB2</strong> database through db2inidb: 

• As a st<strong>and</strong>by database 

• As a mirror backup image 

• As a clone database 

The mirror backup image is validated in this solution. For detailed in<strong>for</strong>mation 

about split-mirror backup, refer to the <strong>IBM</strong> <strong>DB2</strong> split-mirror backup 

documentation. 

<strong>SAP</strong> operational recovery 

The term "operational recovery" is used in this document to refer to the use of a 

replica of a production <strong>SAP</strong> system <strong>for</strong> the purpose of bringing the system's data 

to a specific desired state after a disaster/corruption either through technical 


21


backup/recovery methods or by additionally per<strong>for</strong>ming recovery steps from 

<strong>with</strong>in the application. 

The architecture described in this solution allows the use of the dedicated backup 

host <strong>for</strong> this type of operational recovery. It is possible to start the <strong>SAP</strong> 

application <strong>with</strong> the recovered database on the backup host. In this case 

additional steps are needed to ensure the operational recovery system does not 

interface <strong>with</strong> external production systems. These steps are outlined in the 

documentation of other <strong>EMC</strong> solutions related to system copies (<strong>EMC</strong> Intelligent 

Cloning <strong>for</strong> <strong>SAP</strong>) <strong>and</strong> are out of the scope of this solution. 

As an example, a hardware-specific <strong>SAP</strong> license needs to be applied in the 

backup host, background jobs need to be suspended, printers need to be 

remapped or disabled, <strong>and</strong> RFC destinations need to be reconfigured or disabled. 

However, keep in mind that the existence of a dedicated backup host <strong>with</strong> a 

mounted replica of the production database files makes it possible to per<strong>for</strong>m a 

database recovery to the latest replicated point in time <strong>with</strong>out having to restore 

any backups from tape (or from a VTL). 

Archive logs 

The availability of archive logs is an important requirement to recover a <strong>DB2</strong> 

server database to the most recent point in time. There<strong>for</strong>e, it is important to 

consider backing up these logs frequently so they can be made available in the 

backup host when needed. Either the <strong>DB2</strong> server or the backup management 

software (NetWorker, <strong>IBM</strong> TSM) can be configured to keep track <strong>and</strong> protect 

archive logs as they are generated in the production database. 

Source <strong>and</strong> backup host storage on same storage array 

To configure the replication of <strong>SAP</strong> production data as described in this use case, 

both the production database <strong>and</strong> the replication backup backup host storage 

devices must exist <strong>with</strong>in the same storage array. If there are any factors that 

preclude this condition in a customer environment, special considerations need to 

be made to configure the backup process. 

Cross-array technologies to create replicas across the SAN can be used if the 

related front-end traffic requirements are considered. One of the principles <strong>for</strong> 

the design of this solution was to isolate the backup process so that production 

per<strong>for</strong>mance is not affected when per<strong>for</strong>ming a full <strong>SAP</strong> database backup. 

22 



Multiplexing <strong>and</strong> physical vs. virtual tape libraries 

Several parameters in the configuration of different <strong>EMC</strong> NetWorker or <strong>IBM</strong> 

TSM elements affect how many backup jobs/streams can be processed at a time 

in a client <strong>and</strong> how many jobs can be written to tape at the same time. These 

parameters can affect the per<strong>for</strong>mance of the backup process <strong>and</strong> might be worth 

reviewing to ensure the backup requirements are being met. 

Ideally, since the backup host in the proposed solution is used only <strong>for</strong> 

per<strong>for</strong>ming backups, these settings should be set to maximize the utilization of 

the host <strong>and</strong> the attached tape drives <strong>with</strong>in the library. Since the <strong>SAP</strong> database is 

usually spread out over different volumes, it makes sense to back these up in 

parallel. For the same reason, these save sets should be written to tape in parallel 

utilizing all available tape drives. 


23


24 


3 

Installation <strong>and</strong> 

Configuration 


• Prerequisites <strong>and</strong> background in<strong>for</strong>mation.............................................26 

• Configuring Replication Manager..........................................................27 

• Configuring <strong>EMC</strong> NetWorker ................................................................31 

• Installing <strong>and</strong> configuring <strong>IBM</strong> TSM ERP module ...............................44 


25


The installation <strong>and</strong> configuration instructions presented in this chapter apply to 

the specific revision levels of components used during the development of this 

solution. It is important to review the installation <strong>and</strong> configuration 

documentation <strong>for</strong> the hardware <strong>and</strong> software components involved <strong>with</strong> the 

solution. Version-specific release notes are especially important. 

Prerequisites <strong>and</strong> background in<strong>for</strong>mation 

Be<strong>for</strong>e per<strong>for</strong>ming the configuration tasks provided in this chapter, ensure that 

the following components are installed on the appropriate systems. For 

in<strong>for</strong>mation on software versions <strong>and</strong> installation locations, refer to “Hardware 

<strong>and</strong> software resources” on page 14. 

• <strong>SAP</strong> is installed on both the source (production) <strong>and</strong> backup host (replication 

backup). The System ID (SID) <strong>and</strong> <strong>SAP</strong> profile configuration <strong>for</strong> both hosts 

should be the same. The backup host installation is only used to validate the 

recovery process <strong>and</strong> <strong>for</strong> operational recovery activities. 

Note: If the customer does not require a fully operational <strong>SAP</strong> installation in the 

backup host (no operational recovery outside of production), the installation of <strong>SAP</strong> 

software on this host can be omitted. However, the <strong>DB2</strong> software must be installed on 

the backup host to be able to restore <strong>and</strong> recover the database be<strong>for</strong>e restoring the 

recovered replica back to the production. 

• A virtual tape library (such as <strong>EMC</strong> Disk Library) or a physical tape library 

is installed in conjunction <strong>with</strong> the backup server. The library must be visible 

from the <strong>EMC</strong> NetWorker storage node or <strong>IBM</strong> TSM client node. 

• A NetWorker agent or TSM <strong>for</strong> ERP agent is installed on the backup host. 

• An appropriate number of volumes are created <strong>for</strong> the EDL. 

• <strong>EMC</strong> Replication Manager server <strong>and</strong> agents are installed on both source <strong>and</strong> 

backup hosts. 

• <strong>EMC</strong> Solutions Enabler <strong>with</strong> the TimeFinder license is installed on both 

source <strong>and</strong> backup hosts <strong>for</strong> the TSM scenario. 

• A SnapView license (enabler) is applied on CX4. 

• <strong>EMC</strong> Navisphere Agent/CLI <strong>and</strong> <strong>EMC</strong> ADMSnap are installed on both 

source <strong>and</strong> backup hosts <strong>for</strong> the NetWorker scenario. 

26 


Configuring Replication Manager 


This section provides condensed procedures <strong>for</strong> configuring <strong>EMC</strong> Replication 

Manager (RM) <strong>for</strong> use <strong>with</strong> <strong>EMC</strong> NetWorker or <strong>IBM</strong> TSM. Be<strong>for</strong>e configuring 

<strong>EMC</strong> Replication Manager, do the following: 

• Refer to the section “Configuring the UDB environment (UNIX)” in the 

<strong>EMC</strong> Replication Manager 5.1.2 Product Guide <strong>for</strong> detailed in<strong>for</strong>mation 

about the check list. 

• Ensure that a <strong>DB2</strong> instance has been running on the backup host <strong>for</strong> the 

replica to mount on. 

• Create a storage pool of a suitable size <strong>and</strong> number of devices, <strong>and</strong> ensure 

that it is visible to the backup host. This pool will be used to contain the 

database replica. 

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

the pool manually so that control can be retained over which devices are used. 


27


Creating an application set 

This use case was completed using Replication Manager version 5.1. Refer to the 

current Replication Manager Product Guide <strong>for</strong> your version <strong>for</strong> more 

in<strong>for</strong>mation about creating an application set. Make sure to include the entire 

<strong>SAP</strong> <strong>DB2</strong> database <strong>and</strong> archive log files into the application set. 

Note: To unmount the entire /db2/ filesystem successfully on the backup host, the 

filesystem /db2//log_archive must be selected. 

28 



Creating a Replication Manager job 

A Replication Manager job automates the creation of the split-mirror copy of a 

production <strong>DB2</strong> database <strong>and</strong> mounts/unmounts it to the backup host. The job 

can be called through RMCLI (Replication Manager Comm<strong>and</strong> Line Interface) 

by the backup management software as a pre-comm<strong>and</strong> to the backup job. 

1. In the RM Console, right-click the previously created application set <strong>and</strong> 

select Create Job to start the Job Wizard. 

2. Enter the job name. 

3. Select an appropriate Replication Technology. 

Note: The solution was validated using CLARiiON's SnapView/Clone <strong>for</strong> the 

NetWorker scenario <strong>and</strong> DMX's TimeFinder/Clone <strong>for</strong> the TSM scenario. It is 

recommended to use TimeFinder/Clone or TimeFinder/Mirror or SnapView/Clone 

<strong>for</strong> the backup purpose. 

4. Specify an appropriate retention period or replica count. 


29


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

database in a consistent state when splitting a mirror. Under Consistency 

Method, select by database. 

6. On the Replication Storage screen, select an appropriate storage pool 

(created previously). 

30 


Configuring <strong>EMC</strong> NetWorker 

7. On the Mount Options screen, select Mount the Replica, select the backup 

host (e.g., sapaix06) as the mount host, <strong>and</strong> select Original path as the path 

option. Note that by database must be selected <strong>for</strong> UDB. 

Note: Do not select Recover the database <strong>for</strong> backup purposes; otherwise, roll 

<strong>for</strong>ward logs cannot be applied later to bring the database to the latest state. In 

addition, RM cannot recover a database that was created using ASM. 


Prerequisites 

The following components must be installed on the backup host prior to 

configuring <strong>EMC</strong> NetWorker: 

• NetWorker module (NW<strong>DB2</strong>) <strong>for</strong> AIX <strong>DB2</strong>. 

• Tape or disk library (e.g., EDL), which should be visible to the backup host. 

• Replication Manager agent. 

The NetWorker module (NW<strong>DB2</strong>) <strong>for</strong> <strong>SAP</strong> <strong>DB2</strong> must be installed because the 

backup process done at the backup host is based on the <strong>DB2</strong> database. 


31


After installing NetWorker, you must run the following comm<strong>and</strong> on the backup 

host, otherwise the backup job fails: 

# ln -s /opt/<strong>IBM</strong>/db2/V9.1/lib64 /usr/opt/db2_08_01/lib64 

Refer to the <strong>EMC</strong> NetWorker installation documentation <strong>for</strong> detailed installation 

instructions. 

Configuration through the NetWorker Administration Console 

This section explains how to per<strong>for</strong>m the following steps to configure <strong>EMC</strong> 

NetWorker to per<strong>for</strong>m the <strong>SAP</strong> backup: 

1. “Configure the NM<strong>DB2</strong> configuration file” 

2. “Configure the NetWorker Server resource” 

3. “Create a new <strong>Backup</strong> Group” 

4. “Configure a Client resource” 

5. “Add storage node, verify the library, <strong>and</strong> configure devices” 

6. “Configure volume pools” 

7. “Configure a label template <strong>and</strong> media pool” 

Configure the NM<strong>DB2</strong> configuration file 

1. Create a NM<strong>DB2</strong> configuration file that contains all required environment 

settings. For example, the file can be named <strong>DB2</strong>_CFG. 

2. Ensure that the NM<strong>DB2</strong> configuration file has the following structure, <strong>with</strong> 

the environment variable name followed by an equal sign (=) <strong>and</strong> then the 

variable setting value. For example: 

Environment Variable=Setting 

Ensure that the correct syntax is followed in the NM<strong>DB2</strong> configuration file, 

otherwise the backup or restore will not run correctly. 

Below is an example of a NM<strong>DB2</strong> configuration file. For detailed 

in<strong>for</strong>mation about configuring a NB<strong>DB2</strong> file, refer to the <strong>EMC</strong> NetWorker 

Module <strong>for</strong> <strong>DB2</strong> Release 2.1 Administration Guide. 

<strong>DB2</strong>_ALIAS=AE9 

<strong>DB2</strong>_NODE_NAME=db2ae9 

<strong>DB2</strong>_USR=db2ae9 

<strong>DB2</strong>_VENDOR_LIB_PATH=/usr/lib/libnsrdb2.o 

<strong>DB2</strong>_OPTIONS=<strong>DB2</strong>BACKUP_OFFLINE 

INSTHOME=/db2/db2ae9 

NSR_<strong>DB2</strong>_BACKUP_INFO=yes 

32 



NSR_SERVER=sap-2650-02 

NSR_DATA_VOLUME_POOL=sapaix10 

NSR_LOG_VOLUME_POOL=sapaix10 

NSR_DEBUG_LEVEL=9 

NSR_DEBUG_FILE=/nsr/applogs/db2.log 

NSR_LIBNSR<strong>DB2</strong>_DEBUG_LEVEL=9 

NSR_LIBNSR<strong>DB2</strong>_DEBUG_FILE=/nsr/applogs/db2sql.log 

NSR_LOG_VOLUME_POOL=sapaixlog 

PRECMD=/db2/db2ae9/splitmirror.sh 

<strong>DB2</strong>_PSWD=xxxxxx 

Note: The password is generated by the system automatically. 

Note: Do not include spaces when listing a path. 

Configure the NetWorker Server resource 

The following table describes the main NetWorker Server resource attributes <strong>and</strong> 

gives the sample values used in this use case. Verify that the attribute settings in 

your server resource are valid <strong>for</strong> the <strong>DB2</strong> backup environment, <strong>and</strong> modify the 

settings as required. 

Attribute Description Value 

Name Specifies the hostname of the networker server sap-2650-02.saptce.com 

Parallelism 

Administrator 

Specifies the maximum number of backup save 

streams that the NetWorker software allows to arrive 

concurrently at the server. The NetWorker server 

edition determines the maximum parallelism value. 

When multiple data streams are backed up at the same 

time, the efficiency of the storage devices is increased. 

Specifies users <strong>with</strong> NetWorker Administrator 

privileges. The default setting of the attribute is 

root@hostname on UNIX <strong>and</strong> 

Administrators@hostname on Windows, where 

hostname is the NetWorker server hostname. 

1 

group=Administrators,host=sap-2650-02.saptce.com 

user=administrator,host=sap-2650-02.saptce.com 

user=system,host=sap-2650-02.saptce.com 

Create a new <strong>Backup</strong> Group 

A <strong>Backup</strong> Group is used to specify the starting time <strong>for</strong> a client's scheduled 

backup. It is recommended to create a group to manage all clients related <strong>with</strong> 

the same backup strategy (i.e., <strong>SAP</strong> servers). 

1. From the Administration window, click Configuration. 

2. In the exp<strong>and</strong>ed left pane, right-click Groups <strong>and</strong> select New. 


33


3. Enter the name <strong>for</strong> the group <strong>and</strong> scheduling options if necessary. If the 

backup job needs to run automatically, set Autostart to Enabled. 

4. Click the Advanced tab <strong>and</strong> review the advanced settings <strong>for</strong> the group. It is 

recommended to set the Savegrp parallelism setting to be more than or at 

least equal to the number of drives the library has configured. 

34 



Configure a Client resource 

The NetWorker Client resource is a set of attributes assigned to the <strong>DB2</strong> server 

host <strong>and</strong> stored on the NetWorker server. Be<strong>for</strong>e the NM<strong>DB2</strong> software can be 

used <strong>for</strong> <strong>DB2</strong> backup <strong>and</strong> restore operations, a Client resource must be 

configured <strong>for</strong> the <strong>DB2</strong> server host. 

To configure the NetWorker Client resource <strong>for</strong> a <strong>DB2</strong> server, per<strong>for</strong>m the 

following steps: 

1. Log in on the NetWorker console, from the Administration window, click 

Configuration, right-click the NetWorker server <strong>and</strong> click Properties. For 

the <strong>DB2</strong> backup in offline mode, set Parallelism to 1 in the Properties 

window. For detailed in<strong>for</strong>mation about configuring a Client resource, refer 

to the <strong>EMC</strong> NetWorker Module <strong>for</strong> <strong>DB2</strong> Release 2.1 Administration Guide. 


35


2. Log in on the NetWorker console, from the Administration window, click 

Configuration. In the left-h<strong>and</strong> pane, right-click Clients <strong>and</strong> create a new 

client. A Properties window will be displayed. Enter the basic in<strong>for</strong>mation 

on the General tab. 

3. On the Apps & Modules tab, enter the <strong>Backup</strong> comm<strong>and</strong>. 

36 



Refer to the following table <strong>for</strong> the in<strong>for</strong>mation required in each attribute of the 

Client resource. 


Name Specifies the hostname of the <strong>DB2</strong> server host. Sapaix10 


Comm<strong>and</strong> 

Browse Policy 

For scheduled backup only. Specifies the name of the comm<strong>and</strong> to be used <strong>for</strong> a scheduled 

<strong>DB2</strong> backup. For example: 

nsrdb2sv -f <strong>DB2</strong>_CFG 

where <strong>DB2</strong>_CFG is the NM<strong>DB2</strong> configuration file. 

For scheduled backup only. Specifies the length of time that the NetWorker server retains an 

entry <strong>for</strong> a <strong>DB2</strong> backup in the online client file index. To set a specific browse policy <strong>for</strong> a 

manual <strong>DB2</strong> backup, use the parameter NSR_SAVESET_BROWSE. 

Note: If you do not select a value <strong>for</strong> the Browse policy attribute, the NetWorker server uses 

the default value of one month. The value <strong>for</strong> the Browse policy attribute cannot exceed the 

value <strong>for</strong> the Retention policy attribute. 

nsrdb2sv -f 

/db2/db2ae9/<strong>DB2</strong>_ 

CFG 

Month 

Group 

Parallelism 

Password 

Remote Access 

Remote Use 

Retention Policy 

For scheduled backup only. Specifies the NetWorker backup group to be used <strong>for</strong> a 

scheduled <strong>DB2</strong> backup. 

Specifies the maximum number of concurrent backup or restore tasks to use <strong>for</strong> a backup or 

restore operation. For a backup, this attribute can be used instead of the 

NSR_PARALLELISM parameter. 

For backups, used only if the Remote User is specified. Enter the password of the user 

specified by the Remote User attribute. 

Specifies the fully qualified IP name of a remote system, to enable restores of the <strong>DB2</strong> Server 

backups to that remote system. 

Optional <strong>for</strong> backups on Windows. Specifies the user that is allowed to run remote comm<strong>and</strong>s 

on the client or access specific application data on the client. 

For scheduled backup only. Specifies the minimum length of time that the NetWorker server 

maintains in<strong>for</strong>mation about <strong>DB2</strong> backup data in the online media database. This attribute 

applies only to scheduled <strong>DB2</strong> backups. To set a specific retention policy <strong>for</strong> a manual <strong>DB2</strong> 

backup, use the parameter NSR_SAVESET_RETENTION. 

Note: If you do not select a value <strong>for</strong> the Retention policy attribute, the NetWorker server 

uses the default value of one year. The Retention policy attribute must be greater than or 

equal to the value Browse policy attribute 

Sapaix10 

1 

*@* 

year 


37



Save Set 

Schedule 

Specifies the database <strong>and</strong> node to be backed up. For example: 

<strong>DB2</strong>:/database_name/node_name 

For scheduled backup only. Specifies the NetWorker backup schedule to be used <strong>for</strong> a 

scheduled <strong>DB2</strong> backup. 

<strong>DB2</strong>:/AE9/NODE00 

00 

Full every day 

Add storage node, verify the library, <strong>and</strong> configure devices 

Make sure you have emulated the tape library (<strong>IBM</strong> 3584 tape library was used 

in this use case) from the EDL console <strong>and</strong> the tape drivers have been recognized 

by the operating system be<strong>for</strong>e you run the jbconfig comm<strong>and</strong> on the backup 

host (i.e., NetWorker storage node) to configure the library <strong>for</strong> use <strong>with</strong> 

NetWorker. 

1. Run the jbconfig comm<strong>and</strong> under the bin subdirectory of the NetWorker 

installation directory on the backup host. 

2. Open the NetWorker Administration Console. 

3. Under the Devices section, right-click Storage Nodes in the navigation tree, 

<strong>and</strong> select New. 

38 



4. Enter the fully-qualified name of the storage node (backup host), select the 

type of storage <strong>and</strong> select Yes <strong>for</strong> Search all luns. Click OK to create the 

storage node. 

5. To verify that the EDL attached to the server is detected, right-click the 

newly created node <strong>and</strong> select Scan <strong>for</strong> Devices. 

Upon the completion of the process, the library will appear under the storage 

node <strong>with</strong> its drives. 

Configure volume pools 

For detailed in<strong>for</strong>mation on configuring volume pools, refer to the <strong>EMC</strong> 

NetWorker Module <strong>for</strong> <strong>DB2</strong> Release 2.1 Administration Guide. 


39


Configure a label template <strong>and</strong> media pool 

A label template needs to be created to identify <strong>and</strong> organize volumes (i.e., tapes) 

<strong>with</strong>in a media pool. 

1. In the Server Administration Interface, click the Media button. 

2. In the exp<strong>and</strong>ed left pane, right-click Label Templates <strong>and</strong> select New. 

3. Enter the name, fields, separator, <strong>and</strong> comments as required <strong>for</strong> the label 

template. Click OK to create the template. 

40 



4. In the exp<strong>and</strong>ed left pane, right-click Media Pools <strong>and</strong> select New. 

5. Enter basic in<strong>for</strong>mation <strong>for</strong> the Media Pool. Select <strong>Backup</strong> under Pool type, 

associate this pool <strong>with</strong> the label template created previously <strong>and</strong> select the 

previously created Group under the Data Source section. 


41


6. On the Selection Criteria tab, add the backup host name to the Clients list, 

<strong>and</strong> select the appropriate tape drives from the configured library under the 

backup Device section. 

7. On the Configuration tab, review the Max parallelism setting. 

42 



Pre-comm<strong>and</strong> script configuration 

This section describes how to configure the NetWorker pre-comm<strong>and</strong> script that 

calls RMCLI to execute the RM replication job be<strong>for</strong>e the actual backup job is 

executed. The pre-comm<strong>and</strong> script is defined by the parameter PRECMD located in 

<strong>DB2</strong>_CFG. Refer to the <strong>EMC</strong> NetWorker Module <strong>for</strong> <strong>DB2</strong> Release 2.1 

Administration Guide <strong>for</strong> detailed in<strong>for</strong>mation about the pre-comm<strong>and</strong> script. 

The pre-comm<strong>and</strong> script per<strong>for</strong>ms the following two actions: 

1. Run the clone job. (RM can automatically unmount <strong>and</strong> delete a replica 

be<strong>for</strong>e running the clone job). 

2. Initiate the replica as a st<strong>and</strong>by or mirror database. 

Example 

#!/bin/sh 

#Call RM to run a clone job 

cd /opt/emc/rm/gui/ 

./rmcli /db2/db2ae9/rm/rmjob.log 

2>/db2/db2ae9/rm/rmjob.err 

connect host=sap-2650-01 port=65432 

login user=Administrator password=hsc1 

run-job name=sapaix09 appset=sapaix09 

exit 

EOF 

#Register source database on backup host db2 instance <strong>and</strong> initiate 

the database as mirror or st<strong>and</strong>by 

su - db2ae9 -c "db2 catalog db ae9 as ae9 " 

su - db2ae9 -c "db2start" 

su - db2ae9 -c "db2inidb ae9 as mirror" 

# su - db2ae9 -c "db2inidb ae9 as st<strong>and</strong>by" 


43


Installing <strong>and</strong> configuring <strong>IBM</strong> TSM ERP module 

This section explains the procedures needed to install <strong>and</strong> customize Data 

Protection <strong>for</strong> <strong>SAP</strong>, the interface between <strong>SAP</strong> <strong>and</strong> the Tivoli Storage Manager. 

In this documentation, the <strong>IBM</strong> TSM ERP module is usually referred to as “Data 

Protection <strong>for</strong> <strong>SAP</strong>” or as “DP <strong>for</strong> <strong>SAP</strong>”. <strong>IBM</strong> Tivoli Storage Manager is usually 

referred to as “Tivoli Storage Manager” or “TSM”. 

Prerequisites 

The following components must be installed prior to configuring the <strong>IBM</strong> TSM 

ERP module (Data Protection <strong>for</strong> <strong>SAP</strong>): 

• TSM server 

• TSM ERP module 

• Tape or disk library (<strong>for</strong> example, <strong>EMC</strong> Disk Library), which should be 

visible to the backup host. 

Refer to the Planning Data Protection <strong>for</strong> <strong>SAP</strong> Installation <strong>and</strong> User's Guide <strong>for</strong> 

<strong>DB2</strong> <strong>for</strong> detailed installation instructions. 

Configuring the Tivoli Storage Manager server 

In order to adjust the installed TSM <strong>for</strong> DP <strong>for</strong> <strong>SAP</strong>, the following activities must 

be per<strong>for</strong>med on TSM server: 

1. “Storage device setup” 

2. “Storage pool definition” 

3. “Policy definition” 

4. “Node definition” 

Storage device setup 

A storage device defines a device class, which will h<strong>and</strong>le one type of media, <strong>for</strong> 

example, tape libraries or jukeboxes. TSM has a default device class called Disk, 

which is used <strong>for</strong> disk storage. 

Storage device setup includes the following steps: 

• Library definition 

• Drivers definition 

• Device class definition 

44 



Storage pool definition 

Policy definition 

Node definition 

Example: 

A storage pool is a named collection of storage volumes that are associated <strong>with</strong> 

one device class. Each storage pool represents a collection of volumes that are of 

the same media type. The storage pool setup defines the storage hierarchy <strong>for</strong> the 

appropriate environment. 

Tivoli Storage Manager policies are used to specify how files are backed up, 

archived, migrated from client node storage, <strong>and</strong> managed in server storage. 

A policy definition includes the definition of a policy domain, a policy set, 

management classes, <strong>and</strong> copy groups. After the definition phase, you need to 

assign a default policy set <strong>and</strong> validate <strong>and</strong> activate it. For the policy definition, 

log on as a Tivoli Storage Manager Administrator using the Admin Comm<strong>and</strong> 

Line or the Web Admin. 

The policy definition includes the following steps: 

• Policy domain <strong>and</strong> policy set definition. 

• Management class definition <strong>for</strong> file system backups, data files, offline log 

files, <strong>and</strong> copies of offline log files. 

• Copy Group definition. 

• Assigning the default management class. 

• Validating <strong>and</strong> activating the policy set. 

The Tivoli Storage Manager server views its registered clients, application 

clients, host servers, <strong>and</strong> source servers as nodes that require services <strong>and</strong> 

resources from the server. To register a node <strong>with</strong> Tivoli Storage Manager, log in 

on the Tivoli Storage Manager console using the Admin comm<strong>and</strong> line or the 

Web Admin. 

Define Server 

Define server TSMSERVER serverpassword=yourpassword 

hladdress= lladdress=1500 validateprotocol=all 

Define library 

def libr 3584lib libt=scsi 

define path TSMSERVER 3584lib srctype=server desttype=library 

device=/dev/smc0 

Define drive 

define drive 3584lib 3584dr1 online=yes 

define path TSMSERVER 3584dr1 srctype=server desttype=drive 

library=3584lib device=/dev/rmt4 online=yes 


45











Define devclass 

def devclass 3584class devt=LTO libr=3584lib 

Define storage pool 

define stgpool db2pool 3584class maxscratch=100 

define stgpool logpool 3584class maxscratch=100 

Label tape 

label libvolume 3584lib checkin=scratch search=yes 

labelsource=barcode overwrite=yes 

Define Domain 

Copy domain st<strong>and</strong>ard db2domain 

Define mgmtclass 

define mgmtclass db2domain st<strong>and</strong>ard db2mgmta 

define mgmtclass db2domain st<strong>and</strong>ard db2mgmtb 

Define copygroup 

define copygroup db2domain st<strong>and</strong>ard db2mgmta type=backup 

destination=db2pool vere=4 rete=28 verd=1 reto=28 

define copygroup db2domain st<strong>and</strong>ard db2mgmta type=archive 

destination=logpool retv=28 

define copygroup db2domain st<strong>and</strong>ard db2mgmtb type=backup 

destination=db2pool vere=4 rete=28 verd=1 reto=28 

define copygroup db2domain st<strong>and</strong>ard db2mgmtb type=archive 

destination=logpool retv=28 

Register node 

reg node sapaix06 sapaix06 domain=db2domain passexp=9999 

backdelete=yes 

Validating <strong>and</strong> activating the policy set 

validate policyset db2domain st<strong>and</strong>ard 

activate policyset db2domain st<strong>and</strong>ard 

46 



Configuring the Tivoli Storage Manager clients 

After the server configuration, you must then configure the clients that will use 

the Tivoli Storage Manager server. These include the backup-archive client <strong>for</strong> 

the filesystem backups <strong>and</strong> the Application Programming Interface (API) <strong>for</strong> 

interface programs. The Tivoli Storage Manager backup-archive client will be 

used <strong>for</strong> filesystem backups. The API client allows users to enhance existing 

applications <strong>with</strong> backup, archive, restore, <strong>and</strong> retrieve services. An installed <strong>and</strong> 

confirmed API client is a prerequisite <strong>for</strong> the Tivoli ERP module. 

A Tivoli Storage Manager installer or administrator must per<strong>for</strong>m the following 

typical steps to prepare the Tivoli Storage Manager to operate in an <strong>SAP</strong> 

environment. 

1. Install the Tivoli Storage Manager client software on the <strong>SAP</strong> database 

server machine. 

2. Edit the Application Programming Interface(API) client system file dsm.sys 

located in /usr/Tivoli/tsm/client/ api/bin64, <strong>and</strong> set the following values as 

appropriate to your installation. 

Servername 

COMMMethod 

TSMSERVER 

TCPip 

TCPPort 1500 

TCPServeraddress 

NODename 

TCPCLIENTAddress 

PASSWORDAccess 

 

sapaix06 

sapaix06 

Generate 

3. Edit the Application Programming Interface (API) client options file 

dsm.opt located in /usr/Tivoli/tsm/client/api/bin64 <strong>and</strong> set the following 

value. 

Servername 

TSMSERVER 


47


4. Edit the backup-archive(BA) client system file dsm.sys located in 

/usr/Tivoli/tsm/client/ ba/bin, <strong>and</strong> set the following values as appropriate to 

your installation. 

Servername 

COMMMethod 

TSMSERVER 

TCPip 

TCPPort 1500 

TCPServeraddress 

NODename 

TCPCLIENTAddress 

PASSWORDAccess 

PRESCHEDULECMD 

 

sapix06 

sapaix06 

Generate 

/db2/db2ae2/splitmirror.sh 

Note: The PRESCHEDULECMD parameter specifies a comm<strong>and</strong> that the client 

processes be<strong>for</strong>e it runs a scheduled job. TSM uses this parameter to call RM to do a 

clone be<strong>for</strong>e backing up the backup system. For the detailed in<strong>for</strong>mation about 

splitmirror.sh, refer to “Pre-comm<strong>and</strong> script configuration” on page 55. 

5. Edit the backup-archive(BA) client options file dsm.opt located in 

/usr/Tivoli/tsm/client/ba/bin <strong>and</strong> set the following values: 

Servername 

TSMSERVER 

Installing DP <strong>for</strong> <strong>SAP</strong> 

Refer to the Data Protection <strong>for</strong> <strong>SAP</strong> Installation <strong>and</strong> User's Guide <strong>for</strong> <strong>DB2</strong> 

(Version 5.5) <strong>for</strong> detailed in<strong>for</strong>mation about the Data Protection <strong>for</strong> <strong>SAP</strong> 

installation. 

Note: When installing DP <strong>for</strong> <strong>SAP</strong>, it is recommended to change the DP installation 

directory from /db2/SID/tdp_r3 to /tdp_r3 to ensure that DP <strong>for</strong> <strong>SAP</strong> can work properly. 

48 



Post-installation steps 

After successfully completing the installation dialog <strong>for</strong> DP <strong>for</strong> <strong>SAP</strong>, you need to 

per<strong>for</strong>m the following steps in order to get a properly running system. 

1. “Review/edit the TSM option files” 

2. “Set the initial password” 

Review/edit the TSM option files 

Check the TSM client option files to make sure that they contain the correct 

server name as specified in the server statement of the init.utl file, <strong>and</strong> 

that the parameters are set correctly. 

After the DP installation, the <strong>DB2</strong> parameter VENDOROPT is automatically set <strong>with</strong> 

the following convention: 

/DP configuration directory/vendor.env. 

For example, /tdp_r3/vendor.env: 

XINT_PROFILE=/tdp_r3/initAE2.utl 

TDP_DIR=/tdp_r3/tdplog 

BACKOM_LOCATION=/usr/tivoli/tsm/tdp_r3/db264/backom 

To edit the file /tdp_r3/initAE2.utl, change the value of the following 

parameters as appropriate. 

SERVER 

SESSIONS 

PASSWORDREQUIRED 

ADSMNODE 

BRBACKUPMGTCLASS 

BRARCHIVEMGTCLASS 

TSMSERVER 

2 (Maximum number of sessions) 

YES (Use a password) 

sapaix06 

db2mgmta 

db2mgmta 

For detailed in<strong>for</strong>mation about the initAE2 file, refer to Appendix C, page 81. 

Set the initial password 

Log in on TSM server <strong>with</strong> the db2 administrator, run the comm<strong>and</strong>: 

Db2#> /usr/Tivoli/tsm/tdp_r3/db264/backom -c password 

If the comm<strong>and</strong> runs successfully, another file 

/tdp_r3/NODE0000/init.bki, will be created automatically. 


49


Scheduling a backup job 

A backup job can be scheduled <strong>with</strong> comm<strong>and</strong> lines, <strong>for</strong> example: 

#Define a schedule 

Define schedule db2domain backupdb2 type=client Description 

='backup db2 database everyday" action=comm<strong>and</strong> 

objects="/usr/tivoli/tsm/tdp_r3/db264/backup.ksh" 

startdate=today starttime=03:03:00 

#Associate a client node <strong>with</strong> the schedule 

define association db2domain backupdb2 sapaix06 

Or by logging in to the TSM server console from the following sample web link, 

where will be replaced by the TSM server name or IP address: 

http://:8421/ibm/console 

1. Enter the User ID <strong>and</strong> Password to log in. 

2. Select Policy Domains <strong>and</strong> Client Nodes <strong>and</strong> click TSMSERVER. 

50 



3. Click <strong>DB2</strong>DOMAIN. 

4. Select Client Node Schedules, <strong>and</strong> select Create a Schedule. 


51


5. Specify the Schedule name, <strong>and</strong> select Comm<strong>and</strong> - run a comm<strong>and</strong> on a 

client node machine. 

6. Specify the Comm<strong>and</strong> to run. 

52 



7. Select a repetition option. 

8. Specify the Schedule priority <strong>and</strong> Schedule Expiration. 


53


9. Select client nodes to associate <strong>with</strong> the schedule. 

10. Review the Summary <strong>and</strong> click Finish to complete the schedule. 

54 



Pre-comm<strong>and</strong> script configuration 

<strong>Backup</strong> script configuration 

This section describes how to configure the TSM pre-comm<strong>and</strong> script that will 

call RMCLI to execute the RM replication job be<strong>for</strong>e the actual backup job is 

executed. 

1. Execute /db2/db2/splitmirror.sh: 

#!/bin/sh 

sudo su - -c /db2/db2/call_rm_job.sh 

2. The RM script, /db2/db2/call_rm_job.sh, is being called: 

#!/bin/sh 

#Call RM to run a clone job 

echo "Start of call_rm_job.sh" 

cd /opt/emc/rm/gui/ 

./rmcli /db2/db2/rm/rmjob.log 

2>/db2/db2/rm/rmjob.err 

connect host=sap-2650-01 port=65432 

login user=Administrator password=XXXX 

run-job name=db2tsm appset=db2tsm 

exit 

EOF 

echo "Finished RM job of call_rm_job.sh" 

#Register the source database to the backup host db2 instance <strong>and</strong> 

initiate it as mirror or st<strong>and</strong>by 

su - db2 -c "db2 catalog db as " 

su - db2 -c "db2start" 

su - db2 -c "db2inidb as mirror " 

echo "End of call_rm_job.sh" 

~ 

The sample <strong>DB2</strong> backup shell script that invokes a <strong>DB2</strong> backup to per<strong>for</strong>m a full 

offline backup of all <strong>DB2</strong> tablespaces is listed below: 

/usr/tivoli/tsm/tdp_r3/db264/backup.ksh 

#!/bin/ksh 

# ---------------------------------------------------------------- 

# backup.ksh: 

# Sample <strong>DB2</strong> backup shell script <strong>for</strong> 32bit environments 

# ---------------------------------------------------------------- 

# Task: 

# Invokes a <strong>DB2</strong> backup in order to per<strong>for</strong>m a full offline backup of 

# all <strong>DB2</strong> tablespaces 

# ---------------------------------------------------------------- 

# ***** NOTE ***** NOTE ***** NOTE ***** 

# 

# This script is intended only as a model <strong>and</strong> should be 

# carefully tailored to the needs of the specific site. 

# 

# ***** NOTE ***** NOTE ***** NOTE ***** 

# ---------------------------------------------------------------- 

# 


55


# For the following examples, the system id (alias) of the <strong>DB2</strong> 

database is 

# assumed to be 'AE2'. 

# 

# --------------------------------COMMAND------------------------- 

su - db2 -c "db2 backup db load 

/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a" 

56 


4 



• Per<strong>for</strong>ming a backup <strong>with</strong> <strong>EMC</strong> NetWorker..........................................58 

• Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>EMC</strong> NetWorker.....................59 

• Per<strong>for</strong>ming a backup <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager.......................62 

• Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager..64 


57


Use the instructions provided in this chapter to verify that the installation <strong>and</strong> 

configuration of the various solution components have been done successfully. 

Per<strong>for</strong>ming a backup <strong>with</strong> <strong>EMC</strong> NetWorker 

To per<strong>for</strong>m a backup <strong>with</strong> <strong>EMC</strong> NetWorker, do the following: 

1. Open NetWorker Administration Console. 

2. At the top of the page, select Monitoring. 

3. On the Groups tab, right-click the group created <strong>for</strong> <strong>SAP</strong> backup <strong>and</strong> select 

Start. 

58 


Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>EMC</strong> NetWorker 


This section describes the process to per<strong>for</strong>m a full <strong>SAP</strong> database recovery from 

an EDL (or other tape library) back to the backup host <strong>for</strong> an <strong>SAP</strong> system using 

<strong>EMC</strong> NetWorker. 

The recovery process includes the following steps: 

1. “Restore the backup image from EDL to the backup host” 

2. “Recover the database <strong>and</strong> apply archive logs at the backup” 

3. “Restore validated <strong>SAP</strong> database from the backup to the source” 

Restore the backup image from EDL to the backup host 

To recover the latest available backup done through the process outlined in this 

document, you will not need to restore the backup from tape to the backup host. 

In that case, the latest replica of the production database is already available on 

the backup host <strong>and</strong> you can initiate the recovery on that host (step 2) <strong>with</strong>out 

having to restore the backup from tape. 

For database backup <strong>and</strong> recovery, NetWorker does not support running the 

restore process on NetWorker console. The db2 comm<strong>and</strong> must be used to restore 

the backup image to the backup system <strong>with</strong> the <strong>DB2</strong> administrator user. 

db2 restore db load /usr/lib/libnsrdb2.o options 

/db2/db2/<strong>DB2</strong>_CFG taken at timestamp 

Note: The NetWorker backup log file /nsr/applog/nsrdb2sv.log that records all 

backup timestamps must be checked. 

Recover the database <strong>and</strong> apply archive logs at the backup 

Once the database backup image has been restored to the backup host, you can 

initiate the database recovery process, which includes applying the most recent 

archive logs from the source host. The following steps assume the latest archive 

logs are available in the backup host. 

The production transaction logs need to be backed up from the production host 

through a separate (<strong>and</strong> more frequent) backup process so they can be made 

available in the event of a catastrophic loss of the whole production system. You 

can use <strong>EMC</strong> NetWorker to manage transaction log backups. 

1. Log in <strong>with</strong> the db2 user on the backup host. 


59


2. Run the comm<strong>and</strong>: 

db2> db2 roll<strong>for</strong>ward db to end of logs 

To validate that the <strong>SAP</strong> system can be started on the database be<strong>for</strong>e restoring 

the replica to the production system, run the comm<strong>and</strong> “db2 roll<strong>for</strong>ward db 

stop” <strong>with</strong> the db2 user be<strong>for</strong>e starting up <strong>SAP</strong>. 

Note: At this point, some customers might choose to use the backup host as a temporary 

“operational recovery” system to which some selected users will have access to per<strong>for</strong>m 

functional checks or recovery operations on the application. If this is the case, you will 

need to take into account certain considerations similar to those taken when creating a 

system copy to ensure the backup host does not interface <strong>with</strong> other production systems or 

otherwise behaves like the production system. 

Restore validated <strong>SAP</strong> database from the backup to the source 

1. Shut down <strong>SAP</strong> on both source <strong>and</strong> backup hosts prior to the restore. 

2. Unmount the replica that will be restored to the source host manually through 

RM console. 

60 



3. Restore the replica. 

4. The Restore Wizard displays. 


61


5. Select the objects to be restored. 

Note: If /db2//log_archive is selected, the /db2//log_archive filesystem in the 

source system will be replaced by that of the backup host. If the /db2//log_archive 

is not selected, /db2//log_archive must be umounted in the source system; 

otherwise, the /db2/ filesystem cannot be umounted, which leads to a restore action 

failure. 

6. After the restore, log in <strong>with</strong> the user adm on the source system <strong>and</strong> run 

the comm<strong>and</strong> “startsap” to start the <strong>SAP</strong> system. 

7. Log in on the <strong>SAP</strong> system <strong>with</strong> <strong>SAP</strong>GUI to check whether <strong>SAP</strong> is running. 

Per<strong>for</strong>ming a backup <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager 

To per<strong>for</strong>m a backup <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager manually, do the 

following steps: 

1. Log in <strong>with</strong> the root user on the backup system (sapaix06). 

2. Run the dsmadm comm<strong>and</strong> to log in to the TSM server. 

62 


Per<strong>for</strong>ming a backup <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager 

3. Run q schedule to check the schedule status. 

4. Update the schedule <strong>with</strong> the following comm<strong>and</strong>: 

update schedule db2domain db2backup starttime= 

Note: You can also change the schedule through the TSM server console: 


63


Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>IBM</strong> Tivoli Storage Manager 

This section describes the process to per<strong>for</strong>m a full <strong>SAP</strong> database recovery from 

an EDL (or other tape library) back to the source <strong>SAP</strong> system using <strong>IBM</strong> Tivoli 

Storage Manager. 

To per<strong>for</strong>m a restore <strong>and</strong> recovery <strong>with</strong> TSM, do the following steps: 

1. “Restore the backup image from EDL to the backup host” 

2. “Recover the database <strong>and</strong> apply archive logs at the backup” 

3. “Restore validated <strong>SAP</strong> database from the backup to the source” 

Restore the backup image from EDL to the backup host 

To restore the backup image from EDL to the backup host, per<strong>for</strong>m the 

following: 

1. Ensure that the <strong>DB2</strong> database manager is started on the backup host. 


3. Run either of the following two comm<strong>and</strong>s to per<strong>for</strong>m the restore. 

db2> db2 restore db load /usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a 

taken at timestamp 

db2> /usr/Tivoli/tsm/tdp_r3/db264/backom -c r_db -a -t imestamp 

The file /tdp_r3/tdp_log/tdprlf..NODE0000.log that records all 

backup <strong>and</strong> restore in<strong>for</strong>mation can be checked to get the detailed in<strong>for</strong>mation of 

the database backup image timestamps. 

Note: The backup <strong>and</strong> archive log file 

/db2//db2/NODE0000/SQL00001/db2rhist.asc has been refreshed 

during the backup process, so the comm<strong>and</strong> line “db2 list history backup all <strong>for</strong> 

” only gets the latest backup image timestamp. 

Note: To recover the latest available backup done through the process outlined in this 

document, you will not need to restore the backup from tape to the backup host. In that 

case, the latest replica of the production database is already available on the backup host 

<strong>and</strong> you can initiate the recovery on that host (step 2) <strong>with</strong>out having to restore the backup 

from tape. 

64 


Per<strong>for</strong>ming a restore <strong>and</strong> recovery <strong>with</strong> <strong>IBM</strong> Tivoli Storage 

Recover the database <strong>and</strong> apply archive logs at the backup 

Once the database backup image has been restored to the backup host, you can 

initiate the database recovery process, which includes applying the most recent 

archive logs from the source host. The following steps assume the latest archive 

logs are available in the backup host. 

The production archive logs need to be backed up from the production host 

through a separate (<strong>and</strong> more frequent) backup process so they can be made 

available in the event of a catastrophic loss of the whole production system. You 

can use TSM to manage archive log backups. 


2. Run the comm<strong>and</strong>: 

db2> db2 roll<strong>for</strong>ward db to end of logs 

To validate that the <strong>SAP</strong> system can be started on the database be<strong>for</strong>e restoring 

the replica to the production system, run the comm<strong>and</strong> “db2 roll<strong>for</strong>ward db 

stop” <strong>with</strong> the db2 user be<strong>for</strong>e starting up <strong>SAP</strong>. 

Note: At this point, some customers might choose to use the backup host as a temporary 

“operational recovery” system to which some selected users will have access to per<strong>for</strong>m 

functional checks or recovery operations on the application. If this is the case, you will 

need to take into account certain considerations similar to those taken when creating a 

system copy to ensure the backup host does not interface <strong>with</strong> other production systems. 


65


Restore validated <strong>SAP</strong> database from the backup to the source 

1. Shut down <strong>SAP</strong> on both source <strong>and</strong> backup hosts. 

2. Open the Replication Manager server, <strong>and</strong> select the application set under 

Application Sets in the left-h<strong>and</strong> pane to display the replicas. Right-click the 

mounted replica, <strong>and</strong> select Unmount. 

3. Click Yes to confirm. 

4. The replica status changes to “Successful” after the unmount. 

66 



5. Right-click the replica <strong>and</strong> select Restore. 

6. The Restore Wizard displays. 


67


7. Select the objects to be restored. 

Note: If /db2//log_archive is selected, the /db2//log_archive filesystem 

in the source system will be replaced by that of the backup host. If the 

/db2//log_archive is not selected, /db2//log_archive must be umounted 

in the source system; otherwise, the /db2/ filesystem cannot be umounted, 

which leads to a restore action failure. 

8. Click Yes to confirm. 

68 



9. Restore in progress. 

10. Restore completed. 

11. After the restore, log in <strong>with</strong> the user adm on the source system <strong>and</strong> run 

the comm<strong>and</strong> startsap to start the <strong>SAP</strong> system. 

12. Log in on the <strong>SAP</strong> system <strong>with</strong> <strong>SAP</strong>GUI to check whether <strong>SAP</strong> is running. 


69


70 


5 


Building an <strong>SAP</strong> environment that enables an efficient <strong>and</strong> non-disruptive 

backup <strong>and</strong> recovery strategy can be a complicated endeavor. This integration 

guide depicts a validated design using an <strong>EMC</strong> CLARiiON CX4 or Symmetrix 

DMX-4 storage system, an <strong>EMC</strong> Disk Library DL-4206, <strong>EMC</strong> Replication 

Manager, <strong>and</strong> <strong>EMC</strong> NetWorker or <strong>IBM</strong> TSM. This solution provides the 

following benefits: 

• Reduces the impact of backup processes on production systems compared to 

backup strategies run directly on production hosts. 

• Utilizes a centralized user interface <strong>with</strong> <strong>EMC</strong>'s most powerful replication 

technologies to provide st<strong>and</strong>ard operational procedures <strong>for</strong> <strong>SAP</strong> backups as 

well as backups <strong>for</strong> other applications. 

• Eliminates downtime caused by offline backups; increasing the availability 

of the production environment during backups. 

• Eliminates reliability <strong>and</strong> security concerns associated <strong>with</strong> tape backups <strong>and</strong> 

physical tape libraries. 

• Increases the speed of point-in-time recovery. Data retrieval is faster from 

disk than from tape. The production replica mounted on a backup host 

provides a first line of protection <strong>for</strong> fast operational recoveries. 

<strong>EMC</strong> can help accelerate assessment, design, implementation, <strong>and</strong> management 

while lowering the implementation risks <strong>and</strong> cost of creating a backup <strong>and</strong> 

recovery environment <strong>for</strong> <strong>SAP</strong> <strong>with</strong> <strong>IBM</strong> <strong>DB2</strong> on <strong>IBM</strong> AIX. 

To learn more about this <strong>and</strong> other solutions contact an <strong>EMC</strong> representative or 

visit www.<strong>EMC</strong>.com/solutions/sap. 


71


72 


A 

Reference 

Documentation 

This appendix lists some important documentation related to this use case. 

<strong>SAP</strong> Notes • Note 82029 - DB6: TSM installation in <strong>DB2</strong> environment 

• Note 930487 - DB6: Using <strong>DB2</strong> 9.1 <strong>with</strong> <strong>SAP</strong> software 

• Note 899322- <strong>DB2</strong> V9.1 St<strong>and</strong>ard Parameter settings 

• Note 913481- DB6: Archiving log files <strong>with</strong> <strong>DB2</strong> log file management 

• Note 101809 - DB6: Supported FixPaks <strong>for</strong> <strong>DB2</strong> UDB <strong>for</strong> UNIX <strong>and</strong> 

Windows 

<strong>IBM</strong> Redbook 

<strong>SAP</strong> Solutions on <strong>IBM</strong> <strong>DB2</strong> UDB V8.2.2 H<strong>and</strong>book - October/2005 on <strong>SAP</strong> 

SDN, <strong>SAP</strong> on <strong>DB2</strong> <strong>for</strong> Linux, UNIX, <strong>and</strong> Windows 

https://www.sdn.sap.com/irj/sdn/db6 


73

Reference Documentation 

74 


B 

Monitoring the 

<strong>Backup</strong> Process 

This appendix describes the following general steps you can per<strong>for</strong>m to monitor 

the backup process <strong>for</strong> both NetWorker <strong>and</strong> TSM backup scenarios. 

1. “Monitor unmounting a replica on the backup host” 

2. “Monitor deleting a replica” 

3. “Monitor running a clone job” 

4. “Monitor backing up a replica to EDL” 

Note: The screenshots used in this appendix are <strong>for</strong> the TSM backup scenario, but the 

monitoring steps described can be applied to the NetWorker backup scenario also. 

Monitor unmounting a replica on the backup host 

Open the RM server <strong>and</strong> select Active Tasks in the left-h<strong>and</strong> pane. 


75


Monitor deleting a replica 

1. Open the Replication Manager server, click Application Sets, <strong>and</strong> select the 

application set used <strong>for</strong> the backup. 

2. The replica is deleted automatically. 

76 


3. Click Storage Pools, <strong>and</strong> select the storage pool used <strong>for</strong> the backup in the 

left-h<strong>and</strong> pane, you will find the devices in the storage pool are not in use, 

which means that the clone can be done again. 

Monitor running a clone job 

1. Open the Replication Manager server, <strong>and</strong> select Active Tasks in the 

left-h<strong>and</strong> pane. A clone job is started automatically. 


77


2. The clone job is finished. 

3. After the clone, the replica status “Mounted” indicates that the clone is 

finished <strong>and</strong> the replica has been mounted on the backup system. 

78 


4. Log in to the backup system, <strong>and</strong> run the comm<strong>and</strong> df. You can see that the 

filesystems have been mounted on the backup system. 

Monitor backing up a replica to EDL 

1. Run the following comm<strong>and</strong> <strong>with</strong> the db2 user to check the backup 

status. 

db2> db2 list utilities show detail 

The comm<strong>and</strong> line produces the following sample output: 

2. After the backup, you can check the backup logs <strong>with</strong> the following 

comm<strong>and</strong>: 

db2> db2 list history backup all <strong>for</strong> 


79


The comm<strong>and</strong> produces the following sample output: 

80 


C 

Configuration 

Files 

This appendix lists the sample configuration files used in this use case. 

vendor.env 

Location 

Function 

/tdp_r3/vendor.env 

Interface between <strong>DB2</strong> <strong>and</strong> TSM ERP module. 

vendor.env 

XINT_PROFILE=/tdp_r3/initAE2.utl 

TDP_DIR=/tdp_r3/tdplog 

BACKOM_LOCATION=/usr/tivoli/tsm/tdp_r3/db264/backom 

initae2.utl 

Location 

Function 

/tdp_r3/initAE2.utl 

TSM ERP module configuration file. 

Initae2.utl 

#-------------------------------------------------------------------------- 

# 

# Data Protection <strong>for</strong> <strong>SAP</strong> (R) interface <strong>for</strong> <strong>DB2</strong> UDB 

# 

# Sample profile <strong>for</strong> Data Protection <strong>for</strong> <strong>SAP</strong> (R) Version 5.4 

# 

#-------------------------------------------------------------------------- 

# 

# See the 'Data Protection <strong>for</strong> <strong>SAP</strong> (R) Installation & 

# User's Guide' <strong>for</strong> a full description. 

# 


81


# For a comment symbol the character '#' can be used. 

# Everything following this character will be interpreted as comment. 

# 

# Data Protection <strong>for</strong> <strong>SAP</strong> (R) accesses its profile 

# in "read only" mode. All variable parameters like passwords, date of 

# last password change, current version number will be written into the file 

# specified <strong>with</strong> the CONFIG_FILE parameter. The passwords will be encrypted. 

#-------------------------------------------------------------------------- 

# Prefix of the '<strong>Backup</strong> ID' which is used <strong>for</strong> communication <strong>with</strong> 

# the <strong>SAP</strong>-<strong>DB2</strong> Administration Tools <strong>and</strong> stored in the description field of 

# the Tivoli Storage Manager archive function. 

# Maximum 6 characters. 

# Default: none. 

#-------------------------------------------------------------------------- 

BACKUPIDPREFIX AE2___ 

#-------------------------------------------------------------------------- 

# Number of parallel sessions to be established. 

# Note: This number must not exceed the number of tape drives simultaneously 

# available to the node on the Tivoli Storage Manager servers to be accessed. 

# The valid range of MAX_SESSIONS is from 1 <strong>and</strong> 32. 


#-------------------------------------------------------------------------- 

MAX_SESSIONS 

1 # Tivoli Storage Manager client sessions 

#-------------------------------------------------------------------------- 

# Number of backup copies of the <strong>DB2</strong> log files. 

# The valid range of REDOLOG_COPIES is from 1 to 9. 

# Default: 1. 

#-------------------------------------------------------------------------- 

#REDOLOG_COPIES 2 

#-------------------------------------------------------------------------- 

# Specifies the block size <strong>for</strong> disk I/O (in bytes). 

# The default values have been chosen from our per<strong>for</strong>mance experiments in 

# st<strong>and</strong>ard hardware environments. 

# The valid range of BUFFSIZE is from 4KB to 32MB. 

# Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows. 

#-------------------------------------------------------------------------- 

BUFFSIZE 131072 # block size in bytes 

#-------------------------------------------------------------------------- 

# This optional parameter controls how Data Protection <strong>for</strong> <strong>SAP</strong>(R) uses 

# the internal buffers <strong>for</strong> transferring data during a backup. 

# Valid values: SIMPLE | PREVENT | AUTO 

82 


# Default: SIMPLE 

#-------------------------------------------------------------------------- 

#BUFFCOPY 

AUTO 

#-------------------------------------------------------------------------- 

# Name of a program to be called be<strong>for</strong>e the backup task is started. 


#-------------------------------------------------------------------------- 

# FRONTEND pgmname parameterlist 

#FRONTEND 

/db2/db2ae2/call_rm_job.sh 

#FRONTEND /db2/db2ae2/splitmirror.sh 

#-------------------------------------------------------------------------- 

# Name of a program to be called after the backup task is completed. 


#-------------------------------------------------------------------------- 

#BACKEND 

pgmname parameterlist 

#-------------------------------------------------------------------------- 

# Maximum number of data base backup versions to be kept. 

# Note: Version control by Data Protection <strong>for</strong> <strong>SAP</strong> (R) is only activated 

# only activated if the parameter MAX_VERSION is not 0. 

# The valid range of MAX_VERSIONS is from 0 to 9999. 

# A value of 0 means no versioning. 

# Default: 0, no versioning. 

#-------------------------------------------------------------------------- 

#MAX_VERSIONS 4 

#-------------------------------------------------------------------------- 

# Specifies whether a null block compression of the data is to be per<strong>for</strong>med 

# be<strong>for</strong>e transmission to Tivoli Storage Manager. 

# Although RL compression introduces additional CPU load, throughput can be 

# improved when the network is the bottleneck. RL compression in Data 

# Protection <strong>for</strong> <strong>SAP</strong>(R) should not be used together <strong>with</strong> 

# Tivoli Storage Manager API compression. 

# Default: NO 

#-------------------------------------------------------------------------- 

#RL_COMPRESSION YES # NO is default 

#-------------------------------------------------------------------------- 

# Controls generation of a trace file. 

# Note: We recommend using the trace function only in cooperation <strong>with</strong> 

# Data Protection <strong>for</strong> <strong>SAP</strong> (R) support. 

# Default: OFF. 

#-------------------------------------------------------------------------- 

TRACE 

ON 

TRACEFILE 

/db2/db2ae2/sqllib/db2dump/tdpr3.trace 


83


#-------------------------------------------------------------------------- 

# Denotes the maximum size of the trace file in KB. 

# If not specified, the trace file size is unlimited. 

#-------------------------------------------------------------------------- 

#TRACEMAX # trace file size in KB 

#-------------------------------------------------------------------------- 

# Specify the full path of the configuration file. 


#-------------------------------------------------------------------------- 

#CONFIG_FILE 

/db2/C21/sqllib/%<strong>DB2</strong>NODE/initSID.bki 

CONFIG_FILE /tdp_r3/%<strong>DB2</strong>NODE/initAE2.bki 

#-------------------------------------------------------------------------- 

# Denotes if Data Protection <strong>for</strong> <strong>SAP</strong> (R) shall send error/status 

# in<strong>for</strong>mation to a Tivoli Storage Manager server. 

# The servername must match one of the servers listed in a SERVER statement. 

# Valid values <strong>for</strong> verbosity are ERROR | WARNING | DETAIL. 


#-------------------------------------------------------------------------- 

#LOG_SERVER servername [verbosity] 

#LOG_SERVER server_a ERROR 

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

# Statement <strong>for</strong> servers <strong>and</strong> paths. 

# Multiple servers may be defined. 

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

SERVER 

TSMSERVER 

SESSIONS 2 # Maximum number of sessions 

# to server_a 

PASSWORDREQUIRED YES # Use a password 

ADSMNODE 

sapaix06 

BRBACKUPMGTCLASS db2mgmta 

BRARCHIVEMGTCLASS db2mgmta 

# TCP_ADDRESS 192.168.1.1 # IP address of network interface 

# on server_a 

# Overrides IP address of dsm.sys 

# USE_AT 0 1 2 3 4 5 6 # Days when server_a is used <strong>for</strong> 

# backup 

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

# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa 

# The valid range of USE_AT is from 0 to 6. 

# Default: all days 

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

#SERVER server_b # Servername, as defined in dsm.sys 

84 


# SESSIONS 2 # Maximum number of sessions 

# to server_b 

# PASSWORDREQUIRED YES # Use a password 

# ADSMNODE NODE # Tivoli Storage Manager Nodename 

# BRBACKUPMGTCLASS MDB # Mgmt-Classes <strong>for</strong> database backup 

# BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes <strong>for</strong> redo log backup 

# TCP_ADDRESS 192.168.1.1 # IP address of network interface 

# on server_b 

# Overrides IP address of dsm.sys 

# USE_AT 0 1 2 3 4 5 6 # Days when server_b is used <strong>for</strong> 

# backup 

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

# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa 

# Default: all days 

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

#-------------------------------------------------------------------------- 

# End of profile 


85


86

EMC Backup and Recovery for SAP with IBM DB2 on IBM AIX ...

Create successful ePaper yourself

Delete template?

Save as template?