emc management for sap – intelligent cloning - enabled ... · emc management for sap –...

EMC Management for SAP – Intelligent Cloning Enabled by EMC Celerra and

EMC Replication Manager A Detailed Review

Abstract

The white paper demonstrates how EMC® Replication Manager integrates with the EMC Celerra® unified storage platform, EMC Celerra Replicator™, and EMC SnapSure™ technology to give SAP administrators the ability to quickly and easily refresh non-production systems, such as QA and training, from an SAP production system.

November 2009

Copyright © 2009 EMC Corporation. All rights reserved.

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. Part number: H6536

EMC Management for SAP – Intelligent Cloning Enabled by EMC Celerra and EMC Replication Manager A Detailed Review 2

Table of Contents

Executive summary ........................................................................................................................... 4 Introduction ........................................................................................................................................ 5 Key components ............................................................................................................................... 6 Physical architecture ......................................................................................................................... 7 Environment profile ........................................................................................................................... 9 Installation and configuration .......................................................................................................... 10 Design and validation ...................................................................................................................... 15 Conclusion ....................................................................................................................................... 18 References ...................................................................................................................................... 19 Appendix ......................................................................................................................................... 20


Executive summary

Business case Creating non-production environments for testing, training or other non-production

functions without causing production system downtime is important for any business using SAP systems. To meet this challenge, SAP administrators need a simple and reliable solution that takes advantage of advanced storage systems for maximum efficiency.

Product solution

EMC® Replication Manager integrates with the EMC Celerra® unified storage system, EMC Celerra Replicator™, and EMC Celerra SnapSure™ in a NAS environment to allow SAP Administrators to easily create snapshots of their production systems and quickly refresh non-production systems with this data as required without production system downtime or impact. This solution enables SAP project teams to duplicate an SAP production database so that special projects, such as SAP Upgrades, Unicode conversions, and application of Enhancement Packages, can be tested safely and independently in a cost-effective NAS environment. Furthermore, due to the increasing deployment of virtualized servers to further consolidate data center equipment and increase efficiencies, this solution also includes the use of VMware ESX servers and virtual machines for the non-production environment and illustrates performing a system refresh from a physical to a virtual environment. For local replication, EMC Replication Manager creates point-in-time snapshots of production database file systems by integrating with EMC Celerra SnapSure. This enables the production system to remain operational while replicas of the database file systems are mounted and recovered on the target system. The point-in-time snapshots created by EMC Celerra SnapSure provide space savings compared to creating full copies of the production database. In addition to the SnapSure technology, EMC Celerra Replicator is used in this solution for an even higher degree of information protection to create a point-in-time copy of production file systems on a geographically remote Celerra system. The replication can include any specific file system mount points as required. A single replication job can perform all the steps of the cloning process: replication, mount, and recovery of the SAP data on the target system as well as kick-off post-cloning scripts to automate the preparation of the non-production SAP target system. For SAP administrators and DBAs, this results in an easier, faster, and safer system copy process for SAP systems, with increased flexibility and reduced costs.


Key results This white paper demonstrates the following benefits:

• Eliminates the need to create and maintain complex scripts to create data copies

manually. • Simplifies the process to manage system copies and create non-production systems. • Eliminates any production downtime during replications. • Provides an option to create non-production systems on either local or remote

storage array. • Helps automate the execution of post-cloning steps on the target system.

Introduction

Purpose The purpose of the white paper is to demonstrate how EMC Replication Manager

integrates with the EMC Celerra unified storage platform, EMC Celerra Replicator, and EMC SnapSure technology to give SAP administrators the ability to quickly and easily refresh non-production systems, such as QA and training, from an SAP production system.

Audience This white paper is intended for customers, partners, and EMC employees, including

IT planners, storage architects, Basis administrators, and any others involved in evaluating, acquiring, managing, operating, or designing an SAP landscape’s infrastructure.


Key components

Introduction This section briefly describes the key solution components. For details on all of the

components that make up the reference architecture, see the “Environment profile” section in this paper.

EMC Replication Manager

EMC Replication Manager automates and simplifies management of disk-based and NFS-based replication processes. It orchestrates critical business applications, middleware, and underlying EMC replication technologies to create and manage replicas at the application level for a variety of purposes, including operational recovery, backup, restore, development, simulation, and repurposing.

EMC Celerra The EMC Celerra family delivers best-in-class availability, scalability, and

performance. A Celerra unified storage platform (NX4, NS-120, NS-480, or NS-960) is the best choice for customers who want multi-protocol connectivity (NAS, iSCSI, Fibre Channel, and Multi-Path File System) for specific applications, departments, or locations. Advanced, scalable management software makes it easy for customers to access, manage, and optimize an entire IP storage infrastructure from a single console.

VMware ESX VMware ESX is the foundation for a dynamic, self-optimizing IT infrastructure.

VMware ESX is a robust, production-proven virtualization layer that abstracts processor, memory, storage, and networking resources into multiple virtual machines. VMware ESX allows enterprises to dramatically reduce hardware and operating costs by sharing resources across a virtual environment.

SAP ERP 6.0 SAP ERP 6.0 is a world-class, fully integrated solution that fulfills the core business

needs of midsize and large organizations across all industries and market sectors. Together with SAP NetWeaver and a repository of enterprise services, SAP ERP 6.0 can serve as a solid business process platform that supports continued growth, innovation, and operational excellence.

EMC SnapSure EMC SnapSure software creates copies of file systems for backups and quick

recovery of deleted files or file systems. SnapSure permits as many snapshots of file systems as the space allocated for this function allows.

EMC Celerra Replicator

EMC Celerra Replicator provides efficient, snapshot-based, asynchronous data replication over IP networks. With Celerra Replicator, you can create local or remote copies of file systems, or iSCSI LUNs.


Physical architecture

Scenario 1 The following illustration depicts the physical architecture of solution Scenario 1 in

which snapshots are created on the local storage. In this scenario, file systems from the EMC Celerra are mounted on the production SAP ERP server to hold database files. Replication Manager controls EMC Celerra SnapSure to create snapshots of the production database and mount them on a non-production, virtual SAP ERP machine.


Scenario 2 The following illustration depicts the physical architecture of solution Scenario 2 in

which snapshots are created on the remote storage. In this scenario, file systems from the EMC Celerra are mounted on the production SAP ERP server to hold database files. Once the Celerra Replicator session is set up and completed to replicate, Replication Manager creates a replica of the remote copy of the file system(s). The replica is then mounted on a non-production, virtual SAP ERP machine.


Environment profile

Hardware resources

The hardware used in the use case is listed below.

Equipment Quantity Configuration

Storage arrays 2 EMC Celerra NS-480 (DART 5.6.43-8) 30 x 300 GB FC drives 15 x 1 TB SATA drives EMC Celerra NS-120 (DART 5.6.43-8) 30 x 300 GB FC drives 15 x 1 TB SATA drives

SAP servers 2 (1) Production server – 4 CPUs, 16 GB RAM (2) Target server – ESX server VM – 2 CPUs, 16 GB RAM

EMC Replication Manager Server

1 Dell PowerEdge 1950 – 2 CPUs, 4 GB RAM Two 73 GB disks – VMware ESX 3.5 U3

Software resources

The software used in the use case is listed below.

Software Version Configuration

SuSe Linux Enterprise Server 10 SP2 (x86_64) On both source and target hosts

SAP Application ERP 6.0 SR2 ABAP stack only

Oracle Database 10.2.0.2

VMware ESX Server 3.5 U3 Enterprise Edition

EMC Replication Manager 5.2 SP2

EMC Solutions Enabler 7.0.0.4 (Edit Level: 915)

EMC Celerra SnapSure 5.6.43-8

EMC Celerra Replicator 5.6.48-8


Installation and configuration

Introduction This section provides procedures and guidelines for installing and configuring the

components of this solution.

Configuring EMC Celerra NFS

Follow the steps provided in the table below when configuring EMC Celerra NFS for EMC Replication Manager.

Step Action

1 Export all mount points to the production host from the EMC Celerra. Refer to the topic EMC Celerra NFS export considerations in the section Design and Validation for further details.

2 Add all mount points to the /etc/fstab entries. Refer to the topic Mount points considerations in the section Design and Validation for further details.

3 Mount all file systems with the /etc/fstab entries. If you are creating snapshots on the remote storage, make sure to create EMC Celerra replication sessions between source and target systems. Note that in the test performed in Scenario 2 of the solution, the source and target systems reside on separated storage arrays.

SAP system installation considerations

Refer to the relevant SAP Installation manuals for detailed information about installing an SAP system on NFS. To start an SAP system on a mount host, SAP and Oracle binaries are required to be installed on the mount host. In this solution, the SAP and Oracle binaries were installed on the EMC Celerra NFS. However, for the purpose of the replication, it is not necessary for those file systems to be EMC Celerra NFS file systems.

Installing EMC Replication Manager

Installing Replication Manager within the context of this solution involves the following steps:

Step Action

1 Follow the procedures described in the Replication Manager Administrator’s Guide to install Replication Manager on the designated Windows server. Take care to follow the support matrix to install the proper versions of associated software such as Solutions Enabler.

2 Once the RM server is installed, the RM agent software must be installed on the production server as well as the target system. Again, take care to follow the support matrix to install the proper versions of associated software such as Solutions Enabler. See the Software Resources section for specific versions used.


Configuring Oracle for Replication Manager

Follow the steps provided in the table below to configure the Oracle instance on the target host.

Step Action

1 Create OS users and group users that are the same as those on the production host.

2 Create a directory with <SID> name under the directory where the EMC Replication Manager binaries reside. For example: C:\Program Files\EMC\rm\bin\<SID>.

3 Place the Oracle init file into the newly created directory. The init file contains a portion of the actual init file that can be used to change the path and name of the control files. Refer to the Replication Manager Version 5.2 SP2 Product Guide for detailed instructions.

Configuring EMC Replication Manager

Refer to the EMC Replication Manager Administrator’s Guide for detailed information about configuring Replication Manager. In addition, pay attention to the following topics. Adding EMC Celerra Storage For the EMC Celerra storage array to be recognized by EMC Replication Manager, the entry has to be created manually. You can use an IP address or hostname to identify the Celerra storage array but do not mix use of the two. The screenshot below shows the Add Storage Wizard.


Replication Technology As you create a job for EMC Celerra, you are asked to choose the Snap Destination. If you select the same Celerra storage as the Snap Destination, then the snap is created on the same storage with the EMC SnapSure technology. If you select a different Celerra storage as the secondary storage, EMC Celerra Replicator will be used for the remote replication. Note that Celerra Replicator should be configured prior to setting up the Replication Manager job. Once the Celerra Replicator session is set up and started to replicate, EMC Replication Manager creates the remote copy of the file systems on the remote storage. Refer to the EMC Replication Manager Administrator’s Guide for information on how to configure EMC Celerra Replicator. Snap Type EMC Replication Manager supports both read-only and read/write checkpoints of EMC Celerra SnapSure. The read/write checkpoint is created from the read-only checkpoint so that both types of checkpoints should be available if you want to have a read/write checkpoint. This solution uses the writeable checkpoint to allow the snapshot to mount on the non-production host and to create a cloned SAP system.

Snap Destinations For local replication, as you create a job for EMC Celerra, make sure to select Only run job if in-frame replication, so that the job only runs when the source and target file systems reside on the same Celerra.


However, for remote replication, make sure not to select Only run job if in-frame replication because snaps should be created on the secondary storage. This feature is available only if you have configured a Celerra Replicator session between source and remote storage and selected the secondary storage as the Snap Destination, as described earlier in the Replication Technology section.

Consistency Method For an Oracle database, you have two options to ensure the consistency: • Online using hot backup mode • Offline by shutting down the database You are recommended to use the first option, which is also used in this solution.


In addition, a post-clone script is configured to start the SAP system on the target host. This script can be used for automating post-cloning activities on the target SAP system. Refer to the “Appendix” section for more information about the post-clone script.


Design and validation

Introduction This solution integrates EMC Replication Manager with the EMC Celerra unified

storage system, EMC Celerra SnapSure, and EMC Celerra Replicator for NFS to allow SAP administrators to easily create a snapshot of their production systems without affecting the production system. This white paper is a supplement to the existing EMC SAP replication solutions. The primary difference is the replication technology used. In the SAN environment, file systems are created on their servers and the replication is executed on the device level. In this solution, on the other hand, file systems are created within the Celerra array (EMC Celerra NFS) and the replication is performed for each EMC Celerra NFS level.

Replication considerations

For local replication, EMC Replication Manager with EMC Celerra NFS uses EMC Celerra SnapSure technology to create copies of file systems. The snapshots are created on the same storage pool where the production file systems reside. For remote replication, EMC Celerra Replicator is used to copy file systems from the primary to secondary storage array. EMC Replication Manager then uses EMC Celerra SnapSure to create snapshots of the secondary copy on the secondary storage array.

EMC Celerra NFS export considerations

In the EMC Celerra environment, it is common for SAP customers to have several subdirectories under a file system. This is called the “Partitioned NFS” in this paper. If you are replicating a partitioned NFS on the Celerra, make sure to select all the partitions of the file system when selecting an application set.


Mount point considerations

The file systems shown in the following table are the replicated file systems created and exported on the EMC Celerra, and mounted on the SAP production server. Note that the file system /Oracle_data_EN1 has multiple mount points and EMC Celerra exports. File system layout

File system Content Exports name Mount points

/Oracle_data_EN1 Datafiles Oracle_data_EN1_sapdata1 Oracle_data_EN1_sapdata2 Oracle_data_EN1_sapdata3 Oracle_data_EN1_sapdata4

/oracle/EN1/sapdata1 /oracle/EN1/sapdata2 /oracle/EN1/sapdata3 /oracle/EN1/sapdata4

/ARCH_EN1 Archive logs

oraarch_exp /oracle/EN1/oraarch

If your production system is configured with the Partitioned NFS, make sure all partitions are exported to the production host and listed in the /etc/fstab entry in order for Replication Manager to mount the file systems on the target. Important: • If you are running an Oracle database on the partitioned NFS, apply the RM hotfix

HF_URM00065461_R1.

• With version 5.2 SP2 of Replication Manager, ensure that the switch proto=tcp is not used as a NFS mount option in /etc/fstab. Newer versions of Replication manager may remove this restriction, so check the latest support matrix for more information.


Cloning procedure

To execute a replication with EMC Replication Manager, simply run the job. The job automates the following steps:

Step Action

1 Creates a snapshot of the production file systems. You can view the snapshot from the Replication Manager GUI.

The snapshot can also be viewed from the EMC Celerra Manager GUI.

2 Changes the SID name of the directory on the target host.

3 Mounts the file systems to the target host.

4 Changes the SID, recovers, and starts the Oracle database.

5 Executes a post-clone script to start the SAP system on the target host. Refer to the “Appendix” section for more information about the post-clone scripts used in this use case.


Conclusion

Summary Building a replication for SAP systems is often complicated and expensive. This

solution describes how EMC Replication Manager integrates with EMC Celerra to provide a simple and automated replication process.

Benefits This solution provides the following benefits.

• Eliminates the need to create and maintain complex scripts to create data copies

manually. • Simplifies the process to manage system copies and create non-production

systems. • Eliminates any production downtime during replications. • Provides an option to create non-production systems on either local or remote

storage array.

• Helps automate the execution of post-cloning steps on the target system.


References

Technical documentation

For additional information, see the following documents. • Reference Architecture – EMC Management for SAP - Intelligent Cloning for SAP -

Enabled by EMC Symmetrix DMX-3 and EMC CLARiiON CX3 on HP-UX and Oracle

• Reference Architecture – EMC Virtual Infrastructure for SAP Intelligent Cloning in

Virtual Environments, Enabled by EMC Replication Manager, EMC CLARiiON CX4, and VMware ESX

Product documentation

For additional information, see the product documents listed below. • EMC Replication Manager Administrator’s Guide

• EMC Replication Manager Product Guide

• EMC Replication Manager Support Matrix


Appendix

Introduction This appendix describes the sample post-clone scripts used in this use case. The

scripts can be used for automating post-cloning activities on the target SAP system.

startEN2.sh ******************************************************************************

** EMC Corporation –USA ** ** Global Solutions Center ** ** Customer Integration Lab – Hopkinton ** ****************************************************************************** ****************************************************************************** ** File name: startEN2.sh ** ** Description: Log in to sqlplus and execute the script “postEN2.sh” ** ****************************************************************************** su - oraen2 -c 'sqlplus -s "/ as sysdba" @/home/zcscripts/postEN2.sh' su - -c 'chmod +x /usr/sap/EN2/SYS/exe/run/saposcol' su - en2adm -c 'startsap'

postEN2.sh ******************************************************************************

** EMC Corporation –USA ** ** Global Solutions Center ** ** Customer Integration Lab – Hopkinton ** ****************************************************************************** ****************************************************************************** ** File name: postEN2.sh ** ** Description: Perform most of the SAP follow-up activities ** ** necessary to start SAP system with different SID. ** ****************************************************************************** drop table "OPS$EN1ADM".SAPUSER; drop synonym "OPS$SAPSERVICEEN1".SAPUSER; truncate table SAPSR3.DBSTATHORA ; truncate table SAPSR3.DBSTAIHORA ; truncate table SAPSR3.DBSTATIORA ; truncate table SAPSR3.DBSTATTORA ; truncate table SAPSR3.ALCONSEG ; truncate table SAPSR3.ALSYSTEMS ; truncate table SAPSR3.DBSNP ; truncate table SAPSR3.MONI ; truncate table SAPSR3.PAHI ; truncate table SAPSR3.OSMON ; truncate table SAPSR3.SDBAD ; truncate table SAPSR3.SDBAH ; truncate table SAPSR3.SDBAP ; truncate table SAPSR3.SDBAR ; truncate table SAPSR3.DDLOG ; truncate table SAPSR3.TPFET ; truncate table SAPSR3.TPFHT ; truncate table SAPSR3.TLOCK ; commit work; create user "OPS$EN2ADM" default tablespace SYSTEM temporary tablespace PSAPTEMP identified externally; grant connect, resource to "OPS$EN2ADM"; create table "OPS$EN2ADM".SAPUSER (userid varchar2(256), passwd varchar2(256)); Insert into "OPS$EN2ADM".SAPUSER values ('SAPSR3', 'emcadm60'); CREATE USER "OPS$SAPSERVICEEN2" PROFILE "DEFAULT" IDENTIFIED EXTERNALLY DEFAULT TABLESPACE "SYSTEM" TEMPORARY TABLESPACE PSAPTEMP ACCOUNT UNLOCK; GRANT UNLIMITED TABLESPACE TO "OPS$SAPSERVICEEN2";



GRANT "CONNECT" TO "OPS$SAPSERVICEEN2"; GRANT "RESOURCE" TO "OPS$SAPSERVICEEN2"; GRANT "SAPDBA" TO "OPS$SAPSERVICEEN2"; create synonym "OPS$SAPSERVICEEN2".SAPUSER for "OPS$EN2ADM".SAPUSER; grant select, update on "OPS$EN2ADM".SAPUSER to "OPS$SAPSERVICEEN2"; alter user "SAPSR3" identified by "emcadm60"; commit work; exit

emc management for sap – intelligent cloning - enabled ... · emc management for sap –...

Documents