EMC Intelligent Cloning for SAP Automated Replication for IBM DB2 ...

EMC Confidential - Internal Use Only 

EMC Intelligent Cloning for SAP 

Automated Replication for IBM DB2 on IBM AIX 

Enabled by EMC Symmetrix DMX-3, EMC CLARiiON CX3, 

and EMC Replication Manager 

Integration Guide 

EMC Global Solutions 

42 South Street 

Hopkinton MA 01748-9103 

1.508.435.1000 

www.EMC.com

Copyright and Trademark Information 

Copyright © 2008 EMC Corporation. All rights reserved. 

Published October 2008 

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

to change without notice. 

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

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

THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF 

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 

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

license. 

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

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

EMC Intelligent Cloning for SAP Automated Replication for IBM DB2 on IBM AIX Enabled by EMC 

Symmetrix DMX-3, EMC CLARiiON CX3, and EMC Replication Manager Integration Guide 

P/N H5564 

2 

EMC Intelligent Cloning for SAP Automated Replication for IBM DB2 on IBM AIX Enabled by EMC Symmetrix 

DMX-3, EMC CLARiiON CX3, and EMC Replication Manager Integration Guide


Contents 

About this Document 

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

Audience................................................................................................ 6 

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

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

Chapter 1 

Chapter 2 

Solution Overview 

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

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

Solution components ............................................................................. 8 

Validated environments ......................................................................... 9 

Physical architecture ............................................................................ 10 

Hardware and software resources ........................................................ 14 

Solution Design 

Introduction ......................................................................................... 18 

Standalone source to standalone target replication on EMC CLARiiON 

storage systems .................................................................................... 19 

Multi-partitioned local replication on EMC Symmetrix DMX storage 

systems ................................................................................................ 19 

Cluster source to cluster target replication on EMC Symmetrix DMX 

storage systems .................................................................................... 21 

Cluster source to standalone target replication on EMC Symmetrix 

DMX storage systems ......................................................................... 22 


DMX-3, EMC CLARiiON CX3, and EMC Replication Manager Integration Guide 

3

Contents 


Chapter 3 

Chapter 4 

Appendix A 

Appendix B 

Appendix C 

Installation and Configuration 

Preparation ........................................................................................... 26 

EMC Replication Manager and Consistent Split technology....... 26 

Preparing to install EMC Replication Manager ........................... 26 

Software installation ............................................................................ 27 

Installing EMC Solutions Enabler................................................ 27 

Installing EMC PowerPath........................................................... 27 

Installing EMC Navisphere Agent and CLI ................................. 27 

Installing EMC Admsnap............................................................. 28 

Installing EMC Replication Manager........................................... 28 

Obtaining Replication Manager Client licenses........................... 28 

Assigning Replication Manager Client licenses to hosts ............. 28 

Component configuration ....................................................................29 

Configuring SAP DB2 for Replication Manager ......................... 29 

Configuring DB2 for mount and recover operations.................... 29 

Configuring RM for mount and recover operations..................... 30 

Configuring Replication Manager callout scripts......................... 35 

Conclusion 

Example Scripts 

Replication Manager callout scripts .................................................... 39 

Post-clone cleanup script ..................................................................... 39 

SAP post-clone cleanup script ............................................................. 42 

Unmount script .................................................................................... 43 

Relocation configuration file ............................................................... 43 

Cluster configuration scripts ................................................................ 44 

Troubleshooting 

Database Layout and Mount Points 

4 




About this 

Document 

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

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

Sigma methodologies. As a result, EMC’s Global Solutions organization has 

built Customer Integration Labs in its Solutions Centers to reflect real-world 

deployments in which TCE solutions are developed and validated. These 

validation exercises provide EMC with an insight into the challenges 

currently facing its customers. 

This document was produced as part of the EMC TCE program by the GSC 

TCE Customer Integration Labs working in collaboration with the EMC 

SAP Global Practice, EMC Engineering, and EMC technical field 

consultants. 

Purpose 

This integration guide describes the SAP Automated Replication for IBM 

DB2 and IBM AIX on Symmetrix DMX and CLARiiON CX3 UltraScale 

Series solution. 

In the solution, SAP ERP 2005 and NetWeaver BI are installed on IBM-AIX 

servers. An EMC Symmetrix DMX-3 1500 and an EMC CLARiiON 

CX3-40 are used for storage, and EMC Replication Manager (RM) is used 

for local CX/Symmetrix DMX replications. RM also enables the 

coordination of post-clone cleanup processes run with customized callout 

scripts. 

This document is intended to be used by EMC field personnel and account 

teams as a guide for designing and building a solution for cloning an SAP 

production database locally, for repurposing such as testing and reporting, by 

leveraging EMC hardware and software in an enterprise SAP environment. 


DMX-3, EMC CLARiiON CX3, and EMC Replication Manager Integration Guide 5

About this Document 


Audience 

Scope 

Related 

documents 

The EMC internal document is intended to be used by both pre- and post-sales 

technical consultants to assist with the design and configuration of a customer 

environment. It is assumed the reader is familiar with the following EMC and 

SAP products: 

• EMC Symmetrix DMX 

• EMC CLARiiON CX 

• EMC Navisphere 

• EMC PowerPath 

• EMC Replication Manager 

• EMC SnapView 

• EMC TimeFinder 

• SAP ERP 2005 

• SAP NetWeaver BI 

Before implementing a solution, consider the size and complexity of the 

environment. 

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

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

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

conjunction with the documentation referenced throughout this guide. The 

solution environment simulates an enterprise environment. The solution tests 

were done using standard SAP configurations and SAP best practices. It is 

important to note that actual customer configurations might be different. 

The following document provides additional, relevant information. 

• EMC Replication Manager Version 5.1 Release Notes 

• EMC Replication Manager Version 5.1 Administrator's Guide 

• EMC Replication Manager Version 5.1 Product Guide 

• EMC Replication Manager Support Matrix 

6 




1 

Solution 

Overview 

This chapter includes the following sections: 

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

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

• Solution components................................................................................ 8 

• Validated environments............................................................................ 9 

• Physical architecture .............................................................................. 10 

• Hardware and software resources .......................................................... 14 





The business challenge 

The technology solution 

Solution components 

Copying an SAP system is required under the following situations: 

• Copying a production system to produce a representative testing 

environment. 

• Copying a development system to support a trial upgrade to test the applying 

of SAP support packs. 

The challenges with SAP data replication include: 

• Taking a non-disruptive copy: Copy the database without shutting down the 

source system. 

• Copying a federated environment: Copy combined or collective systems, 

such as ECC and BI/CRM/APO. The databases must be kept synchronized in 

order to preserve data integrity. 

• Simplifying the process: Minimize the manual steps to avoid potential 

human errors. 

• Speeding up the process: Reduce the overall time required to copy the source 

database to the target location and have a usable SAP system. 

The overall objective is to move to an easily reproduceable, automated, and 

efficient process that will benefit the SAP application team, the data center, and 

storage administration teams. 

The EMC ® Intelligent Cloning for SAP Automated Replication for IBM DB2 

and IBM AIX on Symmetrix DMX and CLARiiON ® CX3 UltraScale Series 

solution uses EMC Replication Manager (RM) in conjunction with EMC storage 

arrays to help an SAP project team duplicate an SAP database environment to 

perform various test scenarios, such as applying patches, planning and testing the 

next phase of added functionality for SAP, and Unicode conversion, without 

affecting the production environment. It provides automated SAP storage 

replication processes to enable on-demand replicas to be executed within the 

SAP environment. For BASIS administrators and DBAs, this results in a 

streamlined, faster, and safer SAP database copy process. 

The EMC Intelligent Cloning for SAP Automated Replication for IBM AIX and 

IBM DB2 on Symmetrix DMX-3 and CLARiiON CX3 UltraScale Series 

solution includes components from EMC, SAP, and IBM. This section only lists 

8 




Validated environments 

Validated environments 

the EMC and SAP components. For details on all of the components that 

make up the solution, see “Hardware and software resources” on page 14. 

• EMC Symmetrix DMX-3 1500 

• EMC CLARiiON CX3-40 

• EMC Navisphere ® 

• EMC PowerPath ® 

• EMC Replication Manager 

• EMC SnapView 

• EMC TimeFinder ® 

• SAP ECC6 

• SAP NetWeaver 

The EMC Intelligent Cloning for SAP Automated Replication for IBM DB2 

on IBM AIX solution encompasses four replication scenarios. With this 

document, one or more of these scenarios can be implemented in any 

combination: 

• Standalone (AKA: single instance) source to standalone target 

replication on EMC CLARiiON storage systems 

• Multi-partitioned source to multi-partitioned target replication on EMC 

Symmetrix DMX storage systems 

• Cluster source to cluster target replication on EMC Symmetrix DMX 

storage systems 

• Cluster source to standalone target replication on EMC Symmetrix 

DMX storage systems 

Note: All scenarios are local to the storage system. 



9



Physical architecture 

Figure 1 illustrates the physical architecture of the standalone source to 

standalone target replication on EMC CLARiiON storage systems. 

Standalone clone 

SAP ECC6 

IBM AIX 5.3 

IBM DB2 9.1 




Replication Manager 

Window Server 2003 SR2 SP2 

SAP 


RM Server 

CX3 

Figure 1 



10 





Figure 2 illustrates the physical architecture of the multi-partitioned source 

to multi-partitioned target replication on EMC Symmetrix DMX storage 

systems. 

Partition clone 

Partition 

Partition 

SAP BI 7 



SAP central system and database logical partition 




Database logical partition 




SAP central system and database logical partition 




Database logical partition 



SAP SAP SAP 


RM Server 

DMX 

Figure 2 

Multi-partitioned source to multi-partitioned target replication on EMC 

Symmetrix DMX storage systems 



11



Figure 3 illustrates the physical architecture of the cluster source to cluster target 

replication on EMC Symmetrix DMX storage systems. 

Cluster clone 

IBM HACMP 
















Cluster 

Cluster 

SAP SAP SAP SAP 

RM Server 

DMX 

Figure 3 

Cluster source to cluster target replication on EMC Symmetrix DMX storage 

systems 

12 





Figure 4 illustrates the physical architecture of the cluster source to 

standalone target replication on EMC Symmetrix DMX storage systems. 


SAP System 1 




Clone 

Cluster 













RM Server 

DMX 

Figure 4 

Cluster source to standalone target replication on EMC Symmetrix DMX 




13



Hardware and software resources 

Table 1 and Table 2 present the hardware and software resources used to validate 

the solution. 

Table 1 

Hardware resources 

Equipment Quantity Configuration 

Storage array 1 EMC Symmetrix DMX-3 24 

146 GB 15K drives 

ucode: 5771 (168B0000) 

Storage array 1 EMC CLARiiON CX3-40 UltraScale Series 

146 GB 15k drives 

FLARE ® : 03.24.040.5.016 

Fibre Channel switch 1 Cisco MDS 9509s 

64 ports 

Network switch 1 Cisco 3560G 

64 ports 

SAP server Standalone source to standalone target on CLARiiON: 2 

Multi-partition standalone source to multi-partition 

standalone target on Symmetrix DMX: 4 

Cluster source to cluster target on Symmetrix DMX: 4 

Cluster source to standalone target on Symmetrix DMX: 3 

IBM p570 

Four CPUs 

8 GB RAM 

IBM AIX 5.3.0.60 64-bit 

Two Emulex LP11002-E HBAs 


server 

1 Dell 1950 

Two dual-core 3.0 GHz Intel Pentium 4 

processors 

6 GB memory 

Two 73GB 10K internal SCSI disks 

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

Table 2 

Software resources 

Software Version Configuration/comments 

IBM AIX 5.3 IBM AIX 5.3.0.60 (11.23/IA64) 64-bit Installed on SAP source and target 

IBM DB2 9.1 IBM DB2 9.1 Fix Pack 2 Installed on SAP source and target 

IBM HACMP IBM HACMP 5.4.x Installed on clustered servers 

14 




Hardware and software resources 

Table 2 

Software resources (continued) 

Software Version Configuration/comments 

SAP Applications ECC6 (ERP 2005) 

Solution Manager 7.0 

NetWeaver 2004s 

NW BI 7.0 

Installed on SAP source and target 

Solution Manager generates SAP 

installation keys 

EMC PowerPath 5.1.1 Installed on SAP source and target 

EMC Solutions Enabler 6.4.2.20 Installed on SAP source and target 

EMC Replication Manager 5.1 Storage management software 

EMC ADMSnap 2.24.0.0.0 33 

EMC Navisphere CLI 6.24.2.5 3 

EMC Navisphere Agent 6.24.2.5 

Java JDK 1.4.2 J9 Hybrid Special version; available only from SAP 

website 



15



16 




2 



• Introduction............................................................................................ 18 

• Standalone source to standalone target replication on EMC CLARiiON 

storage systems ...................................................................................... 19 

• Multi-partitioned local replication on EMC Symmetrix DMX storage 

systems................................................................................................... 19 

• Cluster source to cluster target replication on EMC Symmetrix DMX 


• Cluster source to standalone target replication on EMC Symmetrix DMX 






Introduction 

For all replication scenarios, SAP and DB2 binaries can be installed on either 

IBM AIX local disks or EMC standard SAN storage disks on both source and 

target. SAP DB2 data and log files reside on EMC standard SAN storage disks at 

the source and are replicated to the target. 

All scenarios have been validated using EMC Consistent Split replication 

technology, available with Replication Manager. This technology produces a 

restartable image, which is necessary for creating a mountable replica of a 

production SAP DB2 database for repurposing activities such as testing and 

offline reporting. 

For all scenarios, the source and target systems are set up with the same operating 

system, database configuration, and patch levels. 

For all scenarios, the target system SID is different from the source system SID. 

The remainder of this chapter provides additional details about each of the 

validated scenarios. 

18 




Standalone source to standalone target replication on EMC 

Standalone source to standalone target replication on EMC 

CLARiiON storage systems 

For standalone source to standalone target replication on EMC CLARiiON 

storage systems, the LUNs for SAP DB2 logs, data files, and DB directory 

are configured. 

Replication Manager creates a replica of a production SAP DB2 database, 

using the SnapView storage array replication along with EMC Consistent 

Split technology for EMC CLARiiON. 

Figure 5 illustrates standalone source to standalone target replication on 

EMC CLARiiON storage systems. 

Log , data files, 

temporary tablespace, 

DB directory 

Log, data files, 


DB directory 


Cloning controlled by 






Source 

Target 




CX 

Figure 5 



Multi-partitioned local replication on EMC Symmetrix DMX 


SAP uses the DB2 feature of multi-partitioning to distribute the database 

across multiple partitions. This feature can mitigate the performance 

problems that can be associated with extremely large SAP data warehouse 

applications. Also, this feature provides the scalability for potential future 

expansions. 

For this scenario, SAP NetWeaver BI 7.0 is installed on two source IBM 

AIX servers and two target IBM AIX servers. An SAP central system and a 

logical database partition reside on one pair of source and target servers, 



19



while two logical database partitions reside on the other pair of source and target 

servers. Two logical partitions are created on each of the four servers. 

When cloning the multi-partitioned BI systems, Replication Manager uses EMC 

Consistent Split technology to ensure application consistency. Replication 

Manager currently requires the data source to be selected as the filesystem, 

because RM currently does not recognize UDB multi-partitioned databases. The 

filesystems that contain data, active logs, temporary tablespace, and DB directory 

of the database must be selected for the replication. 

RM eliminates the need to create and maintain complex scripts to maintain 

consistency groups or synchronize them manually. This helps to reduce errors 

and speed up the creation of clones. 

The callout scripts or post-mount scripts for federated replication run in parallel 

across all servers. To maintain consistency across the nodes, scripts are used to 

check the replication status of the primary node and wait to complete until other 

nodes are completed. 

Figure 6 illustrates a multi-partitioned standalone source to multi-partitioned 

standalone target replication on EMC Symmetrix storage systems scenario. 

Source 

Target 



DB directory 



DB directory 



DB directory 



DB directory 

Partition 0 

Partition 2 

Partition 0 

Partition 2 



DB directory 



DB directory 





DB directory 



DB directory 

Partition 1 

Partition 3 

Partition 1 

Partition 3 


SAP IBM AIX 5.3 


SAP central system and 

database logical partition 





Database logical partitions 




SAP central system and 

database logical partition 




Database logical partitions 

DMX 

Figure 6 

Multi-partitioned local replication on EMC Symmetrix DMX storage systems 

20 




Cluster source to cluster target replication on EMC Symmetrix 

Cluster source to cluster target replication on EMC Symmetrix 


For cluster source to cluster target replication on EMC Symmetrix DMX 

storage systems, the LUNs for SAP DB2 data, active logs, temporary 

tablespace, and DB directory are configured in separate Volume Groups. 

Replication Manager creates a replica of a production SAP DB2 database, 

using the TimeFinder storage array replication along with EMC Consistent 

Split technology. Note that the DB2 Volume Group (VG) name created by 

the replica will be changed automatically, because the VG in target cluster is 

different from the one created by the replica. The target system environment 

must be reconfigured after a successful cloning. 

The replica is not under the control of the cluster even if it is mounted. To 

place the mounted replica under the control of the cluster, follow the 

following steps: 

1. Shut down the SAP system and database. 

2. Unmount corresponding filesystems. 

3. Deactivate (varyoffvg) the VGs created by the replica. 

4. Add relevant DB instance VGs created by the replica to the cluster 

environment. 

5. Synchronize the cluster environment. 

EMC provides two cluster configuration scripts, cladd.sh and 

clrem.sh, to run these steps automatically. For detailed information about 

the two scripts, refer to “Cluster configuration scripts” on page 44. 

Please refer to Table 3 on page 47 for detailed information about the SAP 

DB2 database layout and mount points configured for this solution. 

Please also refer to the Replication Manager user manuals for more detailed 

information. 



21



Figure 7 illustrates a cluster source to cluster target replication on EMC 

Symmetrix DMX storage systems scenario. 










DB directory 





DB directory 








Source 

Target 





DMX 

Figure 7 

Cluster source to cluster target replication on EMC Symmetrix DMX storage 

systems 

Cluster source to standalone target replication on EMC Symmetrix 


For cluster source to standalone target replication on EMC Symmetrix DMX 

storage systems, all the DB resources on the first server are clustered resources. 

The second server, however, contains both clustered and non-clustered resources. 

The DB resource group on the first server constitutes the replication source, 

while the non-clustered resources on the second server constitute the replication 

target. Replication, therefore, can be said to occur from a “cluster source” (the 

clustered resources on the first and second servers) to a “standalone target” (the 

non-clustered resources on the second server). It can be cost-effective to share 

the target server with both clustered and non-clustered resources. 

22 




Cluster source to standalone target replication on EMC 

For this scenario, devices for DB2 data, logs, temporary tablespace, and DB 

directory are configured for replication. Replication Manager creates a 

replica of a production DB2 database, using the TimeFinder storage array 

replication along with EMC Consistent Split technology for EMC 

Symmetrix. 

Figure 8 illustrates a cluster source to standalone target replication on EMC 

Symmetrix storage systems scenario. 







SAP System 1 SAP System 2 

SAP ECC6 SAP ECC6 

IBM AIX 5.3 IBM AIX 5.3 

IBM DB2 9.1 IBM DB2 9.1 



DB directory 




DB directory 

Source 



Target 

DMX 

Figure 8 

Cluster source to standalone target replication on EMC Symmetrix DMX 




23



24 




3 

Installation and 

Configuration 


• Preparation ............................................................................................. 26 

• Software installation .............................................................................. 27 

• Component configuration ...................................................................... 29 





Preparation 

EMC Replication Manager and Consistent Split technology 

RM with Symmetrix 

RM with CLARiiON 

Consistent Split 

technology 

Replication Manager supports the following replication technologies for 

Symmetrix arrays, among which the TimeFinder/Clone replication along with 

EMC Consistent Split technology were used in this solution: 

• TimeFinder/Clone 

• TimeFinder/Mirror 

• TimeFinder/Snap 

• TimeFinder/Mirror of R2 

Replication Manager supports the following replication technologies for 

CLARiiON arrays, among which the SnapView Clone replication along with 

EMC Consistent Split technology were used in this solution: 

• SnapView Clone 

• SnapView Snapshot 

• SAN Copy for Symmetrix to CLARiiON 

The technology that is used is determined by customer requirements. 

Replication Manager can utilize Consistent Split technology provided by 

Symmetrix and CLARiiON storage arrays to create consistent copies of 

application data. Consistency is assured not by the application, but by the EMC 

storage arrays and enabling software: TimeFinder for Symmetrix, and 

Navisphere and SnapView for CLARiiON. 

Preparing to install EMC Replication Manager 

Refer to the EMC Replication Manager Support Matrix for prerequisites and 

compatibility information on EMC Powerlink ® : 

Support > Interoperability and Product Lifecycle Information > E-Lab 

Interoperability Navigator 

or go directly to this URL: 

https://elabnavigator.emc.com/do/navigator.jsp 

26 




Software installation 

Note: Replication Manager Server currently supports Windows 2000 Server, 

Windows 2000 Advanced Server, and Windows Server 2003. In addition, the system 

must meet the operating system patch levels specified in the EMC Replication 

Manager Support Matrix. 

Software installation 

Installing EMC Solutions Enabler 

Installing EMC PowerPath 

Installing EMC Navisphere Agent and CLI 

Replication Manager uses EMC Solutions Enabler software to communicate 

with the Symmetrix or CLARiiON array's native software to create replicas 

of data and to discover storage arrays, their configurations, and the layout of 

application data. 

EMC Solutions Enabler must be installed on both source and target hosts for 

replication, regardless of the storage array type being used. 

Refer to the EMC Solutions Enabler product documentation for detailed 

installation instructions. 

EMC strongly recommends using PowerPath with Replication Manager 

whenever possible, especially with CLARiiON storage where the 

trespassing of LUNs from one SP to another occurs. If PowerPath is installed 

on a production host, it also must be installed on all mount hosts; otherwise 

the mounts will fail. 

Refer to the Replication Manager Support Matrix for compatibility 

information. 

Refer to the EMC PowerPath product documentation for installation 

instructions. 

Refer to the Navisphere product documentation for installation instructions. 

There are no special considerations for installing the product within this 

environment. 



27



Installing EMC Admsnap 

Installing EMC Replication Manager 

Refer to the Navisphere product documentation for installation instructions. 

There are no special considerations for installing the product within this 

environment. 

Installing Replication Manager within the context of this solution involves: 

• Installing Replication Manager Server on a Windows server 

• Installing Replication Manager Agent on each IBM-AIX host 

• Installing Replication Manager Console on Windows 

Refer to the Replication Manager Administrator's Guide for detailed installation 

instructions. 

Obtaining Replication Manager Client licenses 

Replication Manager is license-controlled and licensed per each host that uses 

Replication Manager Agent. Refer to the Replication Manager Administrator's 

Guide for information on obtaining a license. All hosts participating in the 

replication need to be licensed. 

Assigning Replication Manager Client licenses to hosts 

Once you have obtained the appropriate number of Replication Manager Client 

licenses, you can assign them to the hosts to be used for replication. 

To assign a Replication Manager Client license to a host, do the following in 

Replication Manager: 

1. Right-click the Replication Manager host or server to which you want to 

assign a license 

2. Choose Properties 

3. Select the Licenses tab 

4. Click the link at the bottom of the dialog box 

5. Specify the license information 

28 




Component configuration 


Configuring SAP DB2 for Replication Manager 

To configure the SAP DB2 database for Replication Manager, follow the 

instructions in the "UDB Procedures" chapter of the EMC Replication 

Manager Version 5.1 Product Guide. 

1. Ensure that data files, active logs, temporary tablespace, DB directory, 

and all containers in each tablespace are located in an EMC supported 

storage array, since all of these files must be replicated. 

2. Ensure that appropriate SYSADM privileges are assigned to OS users 

for SAP and the database on the target in order to facilitate the 

administration of the target database. 

3. Ensure that an OS user for SAP application (e.g. , SAP) is created 

on target, which is identical to the source host. For Symmetrix DMX 

multi-partitioned local replication scenario, an identical OS user for 

database (e.g., DB2) is also required on target hosts. 

4. Verify that an instance directory on target is created as below: 

db2//db2 

OR 

db2//db2 

5. For Symmetrix DMX multi-partitioned local replication, verify the 

sapdata1... n directories on the second node regardless of the 

usage. The subdirectories that contain the SYSCATALOG tablespace 

have to exist on all DB2 nodes, so that they must be created even if they 

are empty on nodes where they are not being used. 

6. Verify that the target database log archive parameter value is the log 

archive directory. 

Configuring DB2 for mount and recover operations 

The following steps need to be done either for the first time after the 

replication, or when the database name is changed on the target server. 

1. Verify that the user ID (UID) and the group ID (GID) of DB2 database 

instance owner are the same on both the production host and mount host. 

Otherwise, permission issues when performing mount-related operations 



29



can occur. In the cluster to standalone replication, the UID is different 

between source and target. You can use RM callout scripts to handle file 

permission changes. 

2. Modify the environment variable with the following command: 

setenv dbs_db6_schema sap 

3. Update the password file on the target host. 

a. Verify the database connection: 

dscdb6up adm 

b. Run the following command if an error occurs: 

dscdb6up -create 

c. Run the following command to overwrite the existing password file: 

dscdb6up -rewrite 

d. Verify the database connection: 

dscdb6up adm 

The file dscdb6.conf is now updated. 

Configuring RM for mount and recover operations 

Mounting and unmounting procedures 

Replication Manager executes the steps from mapping appropriate devices for 

replication to mounting to target hosts. With the callout scripts, Replication 

Manager brings up the database with the target SID, and starts the SAP 

application. Optionally, a script to initialize SAP system (e.g., Job, Transport 

route) can be run manually. 

The steps can be divided into 3 kinds of actions: 

1. Steps executed by Replication Manager 

2. Steps executed by callout scripts 

3. Steps executed by scripts manually 

Steps 1 and 2 are run with a Replication Manager job. Step 3 is run manually, but 

can be implemented with a Replication Manager job as a post-mount script or 

callout script based on the your requirement. 

30 





Figure 9 and 10 illustrate the mounting and unmounting procedures of 

Replication Manager. 

Figure 9 

Mounting procedure 

Note: DB2 instance and DAS must run on both source and target mount hosts. 

Figure 10 

Unmounting procedure 



31



Configuring Replication Manager 

Application set 

settings 

Advanced replication 

settings 

For the multi-partitioned replication, multiple source servers are selected. Select 

appropriate directories from the servers you want to replicate. 

For the cluster-to-cluster replication, please select the DB2 virtual host source 

server. 

For all replication scenarios, make sure Use consistent split, Online by 

suspending the database,and by database are selected. 

32 





For the multi-partitioned replication, multiple source servers are selected. 

Add pre- and post-scripts to the host that is running the primary DB2 node.. 

Mount option 

Make sure Alternate Path is selected and specified for cluster-to-standalone 

replication. 



33



For multi-partitioned replication, make sure the multiple paths are selected. In the 

following table, the first row indicates the locations of the DB directory. The 

second row indicates the locations of the rest of the database. 

For cluster-to-cluster replication, make sure Clustered volume group import is 

selected. 

34 





Configuring Replication Manager callout scripts 

Replication Manager callout scripts can be used for triggering customized 

actions at several points in the replication, mounting, and restore processes. 

The EMC Intelligent Cloning for SAP Automated Replication for IBM DB2 

on IBM AIX solution utilized pairs of callout scripts. The first script in each 

pair performs a pre-clone action; the second script performs some post-clone 

cleanups. 

You must adhere to the following callout naming convention when creating 

callout scripts: 

IR_CALLOUT___ 

where 

is the name of the application set that 

contains the job that will run the script. 

is the name of the job that will run the script (within the 

application set defined above). 

When = 600, the callout script is used to relocate database and start 

SAP system during the solution testing. The script is called “post-clone 

cleanup script” throughout this document. 

When = 1300, the callout script is used to stop SAP system and drop the 

database on target during the solution testing. 

Examples of the post-clone cleanup scripts are provided in Appendix A. 

For detailed information on creating callout scripts, including all possible 

entry points and entry point numbers, refer to “Using application callout 

scripts” in the EMC Replication Manager Version 5.1 Product Guide. 



35



36 




4 

Conclusion 

Building an enterprise SAP landscape that encompasses local replication, 

multi-partitioned replication, and cluster replication is a complicated 

endeavor. This integration guide depicts solutions that are reproduceable and 

a validated design using EMC Symmetrix DMX-3 1500 and CLARiiON 

CX3-40 storage systems, EMC Replication Manager, and storage 

consistency technology. This solution provides effective cloning of SAP 

ERP and BI production data for IBM-AIX on a DB2 platform for quality 

assurance, reporting, and upgrading purposes. The solution offers the 

following benefits: 

• Eliminates manual errors and custom script maintenance 

• Empowers SAP administrators and DBAs to create a second SAP 

system where needed and when needed 

• Lowers TCO and provides greater flexibility with tiered storage 

replication 

• Accelerates "time to value" for new SAP modules 

• Improves productivity of IT resources 

• Enables consistent copies of multi-partitioning system 

• Provides customized automation of major post-cloning processes 

EMC can help accelerate assessment, design, implementation, and 

management while lowering the implementation risks and cost of creating a 

cloning environment for SAP on IBM-AIX with DB2 on EMC Symmetrix 

DMX or CLARiiON CX storage. 

Please contact the EMC SAP Solution Practice in Hopkinton, MA, for 

assistance and guidance. To learn more about this and other solutions, 

contact an EMC representative or visit www.EMC.com/solutions/sap. 



Conclusion 


38 




A 


Replication Manager callout scripts 

Post-clone cleanup script 

Replication Manager Application callout scripts are available for triggering 

customized actions at several points in the replication, mounting, and restore 

processes. 

This solution utilized pairs of callout scripts. The first script in each pair 

performed a pre-clone action; the second script performed some post-clone 

cleanups. 

You must adhere to the following callout naming convention when creating 

callout scripts; otherwise the scripts will not work: 

IR_CALLOUT___ 

This section presents an outline of the post-clone cleanup script used during 

solution testing. The script was called automatically from a Replication 

Manager callout script named IR_CALLOUT___600. 

For example: 

su - db2ae5 -c "/db2/db2ae5/relocatedb.sh" 

su - ae5adm -c "startsap" 

This callout script starts an SAP application on the target host. 





The post-clone cleanup script performed the following tasks: 

• Relocate database on the target host 

• Start database and SAP application 

Example: 

CLARiiON standalone source to standalone target replication: 

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

#File Name: IR_CALLOUT_test_test_600 

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

su - db2ae0 -c "/db2/db2ae0/relocatedb.sh 

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

#File Name: relocatedb.sh 

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

#!/bin/csh -fXV 

source $HOME/.dbenv_sapaix10.csh 

if ($status != 0) goto error 

set TSID=AE0 

set SSID=AE9 

set SH_NAME=relocatedb.sh 

set DBSSID=db2ae9 

set DBTSID=db2ae0 

set RELOCATEFILE=relocatedb.cfg_AE0 

set DBSHOST=sapaix09 

set DBSPWD=emcadm60 

cd $HOME 


rm $HOME/*.scr 

if ($status > 2) goto error 

rm $HOME/*.brp 


rm $HOME/$RELOCATEFILE 


# db2start 

# if ($status > 1) goto error 

db2 CATALOG TCPIP NODE $DBSSID REMOTE $DBSHOST SERVER 5912 

REMOTE_INSTANCE $DBSSID 

SYSTEM $DBSHOST OSTYPE AIX64 

db2 CATALOG DATABASE $SSID AS $SSID AT NODE $DBSSID 

/sapmnt/$TSID/exe/brdb6brt -s $SSID -user $DBSSID -using 

$DBSPWD -bm RETRIEVE_RELOCATE 

40 




Post-clone cleanup script 

-ip $HOME -replace $SSID/=$TSID/ -es 

if ($status != 0) then 

mv ${RELOCATEFILE}.save $RELOCATEFILE 


endif 

# awk -F, '{if (/INSTANCE=$DBTSID,$DBTSID/) {printf 

"INSTANCE=$DBSSID,$DBTSID\n"}else 

if (/DB_NAME=$SSID,$SSID/){ printf 

"DB_NAME=$SSID,$TSID\n"}else if (/DB_PATH=,/) 

{printf "DB_PATH=/db2/$SSID,/db2/$TSID\n"}else{print 

$0}}' $HOME/$SSID_NODE0000.scr > 

$HOME/$RELOCATEFILE 

awk -F, '{if (/INSTANCE='$DBTSID','$DBTSID'/) {print 

"INSTANCE='$DBSSID','$DBTSID'"}else if 

(/DB_NAME='$SSID','$SSID'/){ print 

"DB_NAME='$SSID','$TSID'"}else if (/DB_PATH=,/) {print 

"DB_PATH=/db2/'$SSID',/db2/'$TSID'"}else{print $0}}' 

$HOME/${SSID}_NODE0000.scr > 

$HOME/$RELOCATEFILE 


cp $RELOCATEFILE ${RELOCATEFILE}.save 


cd /db2/$TSID/sapdata1 


mv $DBSSID $DBTSID 














db2 list applications 


db2start 


endif 



41



db2inidb $TSID as standby relocate using $HOME/$RELOCATEFILE 


db2 list db directory on /db2/$TSID 


endif 

# db2 -tvf $HOME/post_clone.sql -z $HOME/post_clone.log 


done: 

exit 0 

SAP post-clone cleanup script 

error: 

exit 1 

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

This section presents an outline of the SAP post-clone cleanup script used during 

solution testing. During the solution testing, the script was called manually to be 

distinguished from the post-clone cleanup script that actually starts an SAP 

application. 

The SAP post-clone cleanup script performed the following tasks: 

1. Adjust required RFC destinations. 

2. Delete a single RFC connection. 

3. Update operation modes. 

4. Remove system copy message. 

5. Adjust and change job status. 

6. Initiate and reset transport system. 

7. Delete entries from SAP tables. 

8. Delete all entries from tables TPFET and TPFHT. These contain information 

about changes made to the profile of the source system. 

9. Clean up DDLOG. 

10. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, 

DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP, SDBAR. 

11. Delete all entries from table TLOCK, which holds the repair requests from 

the source system. 

12. Delete all print jobs (transaction SP01, or ABAP program RSPO0041). 

42 




Unmount script 

13. Disable printers, except selected printers. 

14. Deactivate all user events (transactions SM62,SM64). 

15. Reset password expiration times and invalid login counters for all users. 

Unmount script 

This section presents an outline of the unmount script used during solution 

testing. The script is called automatically from a Replication Manager 

callout script named IR_CALLOUT___1300. For 

example: 

su - ae5adm -c "/home/ae5adm/stopallsap.sh" 

su - db2ae5 -c "db2 -tvf /db2/db2ae5/dropdb.sql" 

Relocation configuration file 

/usr/es/sbin/cluster/utilities/claddres -g 'rg_NodeA' 

SERVICE_LABEL='dbae5' APPLICATIONS='db' 

VG_AUTO_IMPORT='false' VOLUME_GROUP='db2binvg' 

/usr/es/sbin/cluster/utilities/cldare -rt -V 'normal' 

The unmount script performed the following tasks: 

1. Stop the SAP application 

2. Stop the DB connection, if any 

3. Drop the database 

The relocation configuration file consists of the location of filesystem paths, 

instance name, database name, log directory, and container paths. To bring 

up the database on target, create and modify the relocation configuration file 

follow the steps below: 

1. Log in as an adm user and generate a configuration file on the 

source host using the following command: 

brdb6brt -bm RETRIEVE_RELOCATE -replace = 

The command generates a configuration file (_NODE0000.scr) 

and a comment file (_NODE0000.brp). 



43



2. Modify the generated configuration file and move the file to the target host. 

a. Modify the name of the configuration file: 

cp _NODE0000.brp relocatedb.cfg_ 

b. Modify the content of the configuration file: 

Example: 

From: 

INSTANCE=db2ae1,db2ae1 

CONT_PATH=/db2/AE1/sapdata1/NODE0000/AE1#DBD.container000 

,/db2/AE5/sapdata1/NODE0000/AE5#DBD.container000 

... 

**AE1 is source SID while AE5 is target SID. 

To: 

INSTANCE=db2ae1,db2ae5 

CONT_PATH=/db2/AE1/sapdata1/NODE0000/AE1#DBD.container000 

,/db2/AE5/sapdata1/NODE0000/AE1#DBD.container000 

... 

**AE1 is source SID while AE5 is target SID. 

Cluster configuration scripts 

Use these scripts to manipulate the target cluster to add/remove Volume Groups 

carried over by the replication. 

cladd.sh 

x=`lsvg | awk '/^ERM/ {printf "%s ",$0}'` 

echo "claddres -g 'rg_NodeA' SERVICE_LABEL='dbae5' 

APPLICATIONS='db' VG_AUTO_IMPORT='false' 

VOLUME_GROUP='db2binvg $x'" 

echo "claddres -g 'rg_NodeA' SERVICE_LABEL='dbae5' 


VOLUME_GROUP='db2binvg $x'" | sh 

cldare -rt -V 'normal' 

clrem.sh 

claddres -g 'rg_NodeA' SERVICE_LABEL='dbae5' 


VOLUME_GROUP='db2binvg' 

cldare -rt -V 'normal' 

44 




B 


This appendix lists potential issues and their corresponding solutions. 

CLARiiON local replication: SAP is not able to add partitions to the DB2 nodes 

In the case of multi-partitioned database only, the subdirectories that contain 

the SYSCATALOG tablespace must exist on all DB2 nodes. The 

subdirectories must be created even if they are empty on nodes where they 

are not being used. 

CLARiiON local replication: Replication terminates with an error that db directory is not on 

a supported array even if they are on CLARiiON storage 

Check the trace file. If the trace file indicates that the db_dir was a separate 

mount point that was not replicated by Replication Manager, manually 

create the subdirectory of db_dir. However, creating the mount point is not 

necessary. The filesystem that contains the DB directory should be present 

on CLARiiON/DMX storage. This location can be found by the db2 

user using the following command: 

db2 list db directory 

CLARiiON local replication: Unable to save Job Setting in Replication Manager 

Contact Replication Manager customer support to obtain the hotfix 

URM00049436. 

Symmetrix DMX cluster-to-cluster replication: Mounting replica terminates with an error 

Modify the node name of the cluster to its physical host name, or contact 

Replication Manager customer support to obtain the hotfix URM00049676. 





Symmetrix DMX cluster-to-standalone replication and Symmetrix DMX cluster-to-cluster 

replication: Umounting replica hangs with Callout script 1300 

Set the environment variable EMC_ERM_NOXMLFILE to 1 and start IRCCD. 

CLARiiON local replication: Recover DB option fails 

If you are using the DB2 Automatic Storage feature for any tablespace, use RM's 

"Callout script" instead of the Recover DB option. 

46 




C 

Database Layout 

and Mount Points 

Table 3 presents the SAP DB2 database layout and mount points configured 

for this solution. 

Table 3 


VG Name LV Name Mount Point Usage Size (GB) 

db2binvg db2binvg_lv03 /db2/db2/V9 DB2 software 32 

db2binvg_lv04 /db2/db2 Home directory of db user and contains 

the DB2 instance data for 

db2binvg_lv05 

/db2/db2as 

db2logvg lvdb2logs /db2//log_dir DB Logs 32 

lvdb2archive /db2//log_archive Log archiving directory 

db2datavg lvsapdata /db2//sapdata1.. sap datafiles 64* 

lvdb2dump /db2//db2dump Contains DB2 diagnostic log files, DB2 

dump files 

lvae1saptemp /db2//saptemp Contains the temporary tablespace 

divg lvusrsapd /usr/sap//D Dialog Instance 68 





Table 3 

Database Layout and Mount Points (continued) 

VG Name LV Name Mount Point Usage Size (GB) 

sapvg lvusrsap /usr/sap/ SAP instance files 68 

lvusrsaptrans /usr/sap/trans SAP transport file 

lvsapmnt /sapmnt/ SAP base directory 

(link to /usr/sap/) 

lvscs /usr/sap//CSC Central services instance 

lvsap

EMC Intelligent Cloning for SAP Automated Replication for IBM DB2 ...

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

Delete template?

Save as template?