SAP Solutions on VMware - Deployment Guide

SAP Solutions on VMware Deployment Guide

SAP Solutions on VMware

Deployment Guide


© 2011 VMware, Inc. All rights reserved.

of 110

© 2011 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html.

VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

VMware, Inc. 3401 Hillview Ave Palo Alto, CA 94304 www.vmware.com

http://www.vmware.com/download/patents.html

http://www.vmware.com/



of 110

Contents

1. Introduction ...................................................................................... 5

1.1 SAP Platform Overview ................................................................................................. 5

1.2 vSphere .......................................................................................................................... 6

1.3 HP Hardware Overview ................................................................................................. 7

1.4 SAP Datacenter Benefits ............................................................................................... 8

2. Deployment Approach Summary ................................................... 10

2.1 Install SAP in a Virtual Machine ................................................................................... 10

2.2 Create a Template and Provision a New SAP System from a Template .................... 10

2.3 Snapshots .................................................................................................................... 12

2.4 vMotion – Live Migration .............................................................................................. 12

2.5 vMotion – Cold Migration ............................................................................................. 13

2.6 High Availability ............................................................................................................ 13

2.7 SAP on VMware Deployment Tips and Best Practice Guidelines ............................... 13

3. Infrastructure Environment ............................................................. 14

3.1 Software and Hardware ............................................................................................... 14

3.2 Logical and Physical Architecture ................................................................................ 15

4. Install SAP ECC 6.0 in a Virtual Machine (SID = TEM) .................. 16

4.1 Install VMware Infrastructure 3 .................................................................................... 16

4.2 Create the Virtual Machine .......................................................................................... 17

4.3 Guest Operating System Install ................................................................................... 22

4.4 SAP Install .................................................................................................................... 26

5. Create a Template ......................................................................... 27

5.1 Run the SAP orabrcopy Tool ....................................................................................... 28

5.2 Uninstall the CI Instance .............................................................................................. 30

5.3 Uninstall Oracle Home ................................................................................................. 36

5.4 Create the Template Using the VI Client ..................................................................... 40

6. Provision a New SAP System from a Template (new SID = DEV) . 44

6.1 Background – SAP System ID Rename Based on the SAP System Copy Guide ...... 44

6.2 Clone a New Virtual Machine from a Template ........................................................... 45

6.3 Install Oracle software (SID = DEV) ............................................................................ 57

7. Snapshots ...................................................................................... 69

7.1 Take the First Snapshot and Update from Windows Server 2003 SP1 to SP2 ........... 70

7.2 Take a Second Snapshot and Roll Back to the First ................................................... 73



of 110

8. vMotion – Live Migration ................................................................ 77

8.1 Submit an SAP Batch Workload .................................................................................. 79

8.2 Migrate the Virtual Machine from vega7063 to vega7062 ........................................... 84

8.3 Migrate the Virtual Machine from vega7062 to vega7063 ........................................... 89

9. vMotion – Cold Migration ............................................................... 94

10. vSphere High Availability ........................................................... 98

Appendix A: ESX Host Configuration Screenshots ............................. 102

Appendix B: HP Infrastructure Environment ........................................ 108



of 110

1. Introduction

This guide focuses on the deployment of SAP ERP software on the VMware virtualized platform, and showcases the benefits that VMware solutions provide for the SAP datacenter. Technical procedures, accompanied by screenshots, are provided for using the following VMware features with an SAP ERP ECC 6.0 system installed in a virtual machine:

Template creation and cloning

VMware snapshots

VMware vSphere® vMotion

®

VMware vSphere High Availability (HA)

These features can be used in an SAP environment to achieve server containment, deployment and management flexibility, cost-effective high availability, and rapid provisioning of a new system.

The technical procedures and screen captures in this document are based on lab work conducted on VMware Infrastructure (VMware ESX

® 3.x and VirtualCenter 3). However, all of the procedures are the

same for the newest version of the platform, VMware vSphere®, and the look and feel of the UI for the

VMware vCenter™ client is similar to VirtualCenter.

1.1 SAP Platform Overview

The SAP flagship product is called SAP ERP. In addition to ERP software, other key SAP products and solutions include business intelligence, customer relationship management, supply chain management, supplier relationship management, human resource management, product life cycle management, enterprise portal software, and knowledge warehouse.

SAP Business Suite applications are based on the SAP NetWeaver application and integration platform. SAP enterprise applications can be deployed in a two- or three-tier architecture. The three-tier client/server architecture generally consists of a presentation layer, an application layer, and a database layer. These three layers can run separately on different computers or all together on the same computer, depending on the requirements and size of the SAP solution being deployed. The presentation and application server layers can be distributed over multiple computers. The three-tier architecture scales to support large numbers of users. The two-tier architecture is usually sufficient for many smaller and midsize companies, as well as for sandbox, development, training and test systems.

The SAP application layer can be further broken down into the following components:

Central services, which include messaging (manages client connections and communications) and enqueue (SAP lock management) services.

Application services that process online and batch workloads, which can be further categorized into the following types:

o ABAP: processes workloads based on SAP’s proprietary programming language.

o Java: processes Java-based workloads.

o ABAP + Java: processes both ABAP and Java-based workloads.

The specific SAP product determines the type of application service required (ABAP, Java, or both).



of 110

SAP enables a distributed architecture that allows these services to be centralized or distributed across separate instances or servers, depending on sizing and availability requirements. An instance that includes both central and application services is referred to as the Central Instance (CI). An instance that includes only application services is called a Dialog Instance.

In the steps described in this document, you install the core SAP ERP product. The architecture includes a database and Central Instance (CI) running ABAP-only application services.

1.2 vSphere

vSphere is a virtualization platform that enables datacenters to transform into a simplified cloud infrastructure and enables the next generation of flexible, reliable IT services.

The components of vSphere are classified into:

Infrastructure services – These are components that comprehensively virtualize server, storage and network resources, aggregate them and allocate them precisely on demand to applications based on business priority.

Application services – These are components that provide built in service level controls to all applications running on the Cloud operating system platform, regardless of application type or operating system.

VMware vCenter Server™ provides a central point of control for virtualization management, essential for administering infrastructure and application services, with deep visibility into every aspect of virtual infrastructure, automation of day to day operational tasks and the scalability to manage large datacenter environments.

vSphere holistically manages hardware resources and provides built-in application service level controls, creating dramatically simplified cloud infrastructures. The different VMware products are summarized in the following logical architecture.



of 110

Figure 1. VMware vSphere Logical Architecture

1.3 HP Hardware Overview

As with the ProLiant full-height blade servers, the half-height ProLiant BL460c and BL465c servers are excellent platforms for virtualization, offering an integrated, easily managed infrastructure. To develop this guide, VMware used the ProLiant BL460c half-height blade configured as shown in Appendix B.

The ProLiant BL460c and BL465c servers double the computing capacity in the same space versus full-height blades, while keeping the same flexibility, power management and system control and VMware best practices. The ProLiant BL460c and BL465c offer hot-plug hard drives, large memory capacity, multiple expansion slots and the latest generation processors, making them favorable choices for VMware Infrastructure.

HP BladeSystem servers, storage, and other modular components can be added or removed easily without having to power off. HP BladeSystem c-Class reduces space requirements and can be set up or reconfigured easily. HP provides a common and intuitive interface to monitor and control all HP BladeSystem resources—server, storage, network, power and cooling.



of 110

1.4 SAP Datacenter Benefits

The SAP and vSphere deployment scenarios described in this document demonstrate the following benefits that the vSphere suite brings to enterprise SAP installations:

Server containment

Availability

Rapid provisioning

1.4.1 Server Containment

Traditionally, SAP environments have a one-to-one relationship between the SAP systems and the physical servers they run on. With VMware Infrastructure, it is possible to run multiple SAP systems on the same physical hardware. The instances run in separate operating system environments on isolated virtual machines, providing a high level of server containment and enhanced availability and manageability.

The key benefits of using VMware Infrastructure for server containment are as follows:

Consolidate dedicated and isolated SAP environments to a few physical systems.

Run multiple SAP systems on the same physical system, providing significant reduction in server numbers and lowering total cost of ownership (TCO).

Allow multiple test environments to share the same physical system and eliminate the need for dedicated test systems.

1.4.2 Availability

For customers who run SAP environments on x86 hardware and who can accept lower levels of availability (for example, on non-production systems), VMware HA and vMotion offer a cost-effective alternative to expensive third-party clustering and replication solutions. With VMware HA, failed SAP instances and virtual machines on one ESX host can be restarted on another ESX host within minutes. With vMotion, it is possible to migrate live SAP virtual machines between ESX hosts, and to move SAP instances off failing hardware, with minimal interruption to end users.

The key benefits of using vSphere to achieve high availability are as follows:

Provide a cost-effective failover alternative to expensive third-party clustering and replication solutions. VMware software makes it possible to implement enhanced availability without the cost of identical servers, the complexity of rebuilding clusters when physical hardware is changed, and the difficulty associated with testing the clustering of physical systems.

Employ a time-efficient mechanism to restart an SAP system within minutes on an available ESX host in case of failures.

Cause minimal interruption to end users during live migration of SAP virtual machines from one ESX host to another, and minimize downtime during hardware maintenance.



of 110

1.4.3 Rapid Provisioning

VMware virtualization solutions significantly reduce the time to provision virtual machines to contain a two-tier SAP system. For a new deployment, administrators must ordinarily procure hardware, install the operating systems, and perform necessary configurations before the application can be properly installed. This process consumes significant time, IT resources, and dedicated hardware. Using vSphere, SAP customers can take advantage of virtual machine templates to provision new pre-configured SAP environments in minutes on virtualized infrastructure hardware.

Cloning creates a controlled virtual machine configuration so deployment is less error-prone and time-consuming. Administrators can roll out a robust SAP environment in a very short period of time.

Key benefits of using VMware Infrastructure for provisioning:

Allow rapid provisioning of SAP systems from virtual machine templates.

Pass SAP virtual machine images easily from developers directly to testers.

Pass SAP virtual machine images easily from test back to development for problem replication and resolution.

Reset test images from templates after test completion, cutting down on test setup and reset time.

Instantly provision different versions of SAP software by storing them in virtual machines.



of 110

2. Deployment Approach Summary

This section summarizes the tests and results documented in this guide.

2.1 Install SAP in a Virtual Machine

The lab environment consists of two ESX hosts connected to shared storage. The SAP ECC 6.0 system (database and central instance) is installed onto a single virtual machine with the following properties:

Windows Server 2003 guest operating system

115GB VMFS disk

Two virtual CPUs

3GB RAM

The procedure for installing SAP on a virtual machine is the same as installing it in a physical environment.

2.2 Create a Template and Provision a New SAP System from a Template

This scenario demonstrates rapid deployment of a unique ECC 6.0 system based on VMware template cloning features and the SAP system ID rename procedure (as per the SAP System Copy Guide).

A template is a golden image of a virtual machine that can be used as a master copy to create and provision new virtual machines. It includes the guest operating system and application data. In the tests here, the template consists of a full installation of a base SAP ECC 6.0 (initially installed with System ID, SID = TEM) system on Windows Server 2003. The VMware Infrastructure cloning feature allows creation of a new virtual machine from the template. The subsequent SAP system ID (SID) renaming process creates a new ECC 6.0 system running on the same guest operating system but with different SID and host name. This process is much faster than installing a virtual machine, guest operating system and ECC 6.0 system from scratch.

The SAP SID rename step is required to deploy a unique SAP system into the environment per SAP note 11692 (Renaming the system ID), found in the SAP System Copy Guide from SAP available at http://service.sap.com/instguides. The SAP guide used here is System Copy for SAP Systems Based on SAP NetWeaver 2004s SR2 ABAP, which covers different combinations of databases and operating systems. The part relevant for the tests described here is the Oracle on Windows homogeneous system copy option based on the Oracle backup/restore method.

http://service.sap.com/instguides



of 110

The complete template, cloning, and rename process is shown in the following figures.

Figure 2. Installing SAP on a Virtual Machine

Figure 3. Creating the Golden Image

Figure 4. Deploying a New SAP System from Template

Definitions for SAP tools are as follows:

sapinst: The SAP installation and migration tool that performs the install of SAP software and

database. It also includes features to migrate/rename SAP systems.

orabrcopy: An SAP Java tool that connects to a live Oracle instance and generates control and

parameter files that are used to rename the SID of an Oracle database.

The timings given in the figures are approximate and are based on the tests conducted in the lab. Faster deployment from a template has the following features:

General features:

o Oracle software is uninstalled in the source template so that it can be reinstalled in the new virtual machine to the new SID and host name.

o The SAP CI instance is uninstalled in the source template, as the SAP System Copy process in the new virtual machine reinstalls a new CI for the new SID and host name.



of 110

Advantages:

o Faster than an ECC 6.0 installation from scratch.

o The SAP system rename is based on a documented and supported SAP procedure (the SAP System Copy Guide).

o The SAP System Copy Guide covers other SAP certified databases (not just Oracle).

o The process can be extended for other variations of the SAP application server, ABAP + Java or Java (covered by the SAP System Copy Guide).

Disadvantages:

o Includes manual steps (Oracle software de-install and re-install, sapinst input screens).

o Requires some of the SAP install media CDs or DVDs (Oracle software, Oracle client, SAP kernel).

Potential improvements to this process:

o It might be possible to automate the change of the SID and host name of the Oracle software and database (with Oracle tools or by way of command line) using a script.

o Users who want to try this improvement must check with the database vendor and SAP to determine if such options are supported.

2.3 Snapshots

This test demonstrates software patch testing using the VMware snapshot feature and highlights the benefits of being able to revert back to the state prior to the software update in case of errors or to continue with the current state when tests are successful. This process can be applied to an SAP development or test system for testing patches at the following levels: OS, SAP kernel, and SAP ABAP or Java software.

Users must be aware that any changes made to SAP during the testing phase after a patch or upgrade has been applied are lost in the event of a rollback to a previous snapshot.

2.4 vMotion – Live Migration

Tests demonstrate live migration of a virtual machine running an SAP batch workload between two ESX hosts. The workload is created by running SAP transaction SGEN (which generates and compiles ABAP code and is a standard utility executed after a fresh SAP install). CPU performance charts from VMware Infrastructure (VI) client and SAP monitoring transactions (SM50, SM37, SM21) executed before and after the migration clearly show continuation of the batch job and no disconnections.

The SAP license is not impacted by the migration of the virtual machine between physical servers. The

SAP license utility saplicense –get returns the same hardware key when running on either server.

The hardware key, required for generation of an SAP license, is based on the virtual machine, not on the physical ESX host.



of 110

The tests generated the following results, based on the CPU performance charts from the VI Client:

The batch workload generates approximately 50% CPU utilization on the 4-way ESX host.

The CPU utilization in the virtual machine is near 100%.

The CPU utilization of the ESX host is transferred to the target host after the migration; meanwhile the utilization on the source host drops to zero.

At the time of migration, a CPU spike is observed on the source ESX host machine before falling to zero. This spike is attributed to the copying of the memory state from the source ESX host.

2.5 vMotion – Cold Migration

In this test, the virtual machine is powered off, and the virtual machine and its data are migrated between two different VMFS datastores, from SAN to local storage (on the ESX host) and back again.

This functionality provides a benefit, for example, during the initial setup of an environment where shared storage (SAN, iSCSI, or NAS) might not yet be available but local storage on the ESX host is present with adequate free capacity. SAP software can be installed into a virtual machine on the local datastore and migrated later to shared storage after the SAN is configured.

2.6 High Availability

This test shows how VMware HA provides ESX host-based HA capability with minimum configuration. This feature manages ESX host hardware, not application level failures. The latter require separate third-party application aware cluster software, which is not covered here.

Server failure is simulated using a manual reboot of the ESX host, and the virtual machine is restarted on the remaining server. This feature does not automatically restart the SAP application, which must be manually restarted after the virtual machine is powered up on the failover server.

2.7 SAP on VMware Deployment Tips and Best Practice Guidelines

For the latest information on best practices, see SAP Solutions on VMware vSphere 4 - Best Practice Guidelines (http://www.vmware.com/resources/techresources/10086).

http://www.vmware.com/resources/techresources/10086



of 110

3. Infrastructure Environment

3.1 Software and Hardware

The following software and hardware was used for the environment:

Software:

o VMware Infrastructure 3: ESX 3.0.1; VirtualCenter 2.0; VI Client 2.0

o Guest operating system: Windows Server 2003 SP1

o SAP ECC 6.0 Unicode, NetWeaver 2004s R2, Oracle 10g, ABAP stack

o A single virtual machine running an SAP CI and Oracle Database instance on Windows Server 2003 SP1

Hardware:

o ESX hosts: 2x HP ProLiant BL 460c, 4 CPU x 3GHz each, 16GB RAM

o SAN: HP EVA 6000 2C2D disk array (14x 146GBHDD)

o 2x HP SAN switch

o Network: Gigabit Ethernet



of 110

3.2 Logical and Physical Architecture

The following figures illustrate the logical and physical architecture for implementing SAP software on VMware.

Figure 5. Logical Architecture for SAP Software on VMware

Figure 6. Physical Architecture for SAP Software on VMware



of 110

4. Install SAP ECC 6.0 in a Virtual Machine (SID = TEM)

4.1 Install VMware Infrastructure 3

Installation of VMware Infrastructure is not covered in this document. Consult the VMware Infrastructure 3 Documentation (http://www.vmware.com/support/pubs/vi_pubs.html).

Appendix A shows screenshots of the ESX host configuration. The following table gives an overview of the ESX host setup used for these tests.

ESX Host Datacenter Name HP

Virtual machine (VM) name sap_vm

VM storage size 115GB

VM Windows guest operating system drive C:\

VM memory assigned 3GB

VM CPUs assigned 2

VM Windows guest operating system host name vega7066

SAP instances installed in VM Oracle + CI (ABAP stack)

Datastore name VMFS03 (1x 600GB shared VMFS LUN)

ESX host names vega7062

vega7063

Cloned VM Windows guest operating system host name vega7067

For this test environment I/O performance is not a consideration and the LUN count is limited. As a result the 115GB storage for the virtual machine is assigned to one LUN.

Note A better practice would be to separate the system and application data onto separate LUNs.

http://www.vmware.com/support/pubs/vi_pubs.html



of 110

4.2 Create the Virtual Machine

To create a virtual machine named sap_vm

1. Run the VI Client.

2. Right-click 156.153.117.63 and select New Virtual Machine.

3. Select Typical and click Next.



of 110

4. Enter the Virtual Machine Name as sap_vm, select HP, and click Next.

5. Select shared storage, Datastore = VMFS03. Click Next.



of 110

6. Select Microsoft Windows Server 2003, Enterprise Edition. Click Next.

7. Select 2 from the Number of virtual processors drop-down menu. Click Next.



of 110

8. Enter Memory for this virtual machine = 3000 MB. Click Next.

9. Enter number of NICs = 1, select network = Production. Click Next.

10. Enter Disk Size = 115 GB. Click Next.



of 110

11. Click Finish.



of 110

4.3 Guest Operating System Install

The Windows install ISO image is copied to local storage on the ESX host.

To install the guest operating system

1. Run the VI Client.

2. Right-click sap_vm and select Edit Settings.

3. Select Connect at power on.

4. Click Browse and go to /storage1/iso_images/win2k3sp1.iso to select the datastore ISO

file.



of 110

5. Click OK. At the ESX host level the Windows ISO image is copied to /vmfs/volumes/storage1

(1)/iso_images.

6. Select the Console tab.



of 110

7. Right-click sap_vm and select Power On.

8. Select A (Enterprise Edition) and press Enter.

9. Follow the instructions for a standard Windows Server install. To move the cursor out of the console area, press Ctrl+Alt.



of 110

10. After the Windows install is complete, right-click sap_vm and select Send Ctrl+Alt+Del to log in to Windows.

11. Right-click sap_vm and select Install VMware Tools. Click OK.



of 110

12. After the VMware Tools installation completes successfully, at the prompt set the hardware acceleration to full and restart Windows. VMware Tools optimizes mouse performance, among other things.

4.4 SAP Install

To install SAP on a virtual machine, use the same procedure as for a physical server. A standard SAP Oracle on Windows install is performed with SID = TEM and ORACLE_HOME set to

c:\oracle\TEM\102.

For instructions on the SAP install see the SAP install guide, SAP ERP 2005 SR2 ABAP on Windows: Oracle, which is available at http://service.sap.com/instguides.




of 110

5. Create a Template

The SAP system TEM is running in sap_vm, on ESX host vega7063.

A golden image of the virtual machine is created as a template. This image is used to provision a new SAP system in the next sections.

An SAP Java tool, orabrcopy, is used here. This tool is documented in the System Copy Guide from

SAP, System Copy Guide for SAP Systems Based on SAP NetWeaver 2004s SR2 ABAP. The guide is available at http://service.sap.com/instguides.

At a high level the procedure is as follows:

1. Run the SAP orabrcopy tool to generate the Oracle initTEM.ora and CONTROL.SQL files.

This is required for the Oracle rename to another system ID (SID). The SID contained in these files is TEM. This is changed to the desired target SID (DEV) during the deployment of the new virtual

machine. These files are saved in the virtual machine at C:\oracle\orabrcopy.

2. Uninstall the CI instance using sapinst.

3. Uninstall the Oracle software using the Oracle Universal Installer.

4. The CI instance and the Oracle software are uninstalled as they are not required in the golden image. The SAP rename process reinstalls the Oracle software and CI instance to the new host name and SID after a new virtual machine is deployed from the template.

5. The virtual machine now contains the Oracle data files stored under C:\oracle\TEM. This

corresponds to a database backup.

6. Create a virtual machine template. This is the golden image from which to deploy a new virtual machine and provision a new SAP system.




of 110

5.1 Run the SAP orabrcopy Tool

To run the SAP orabrcopy tool

1. Shut down the CI instance using the SAP Management Console.

2. Double-click the SAP Management Console icon on the desktop.

3. Expand the folders Console Root > SAP Systems > TEM > vega7066 0.

4. Right-click and select Shutdown.

5. In the confirmation window, click Yes.

6. Enter the Administrator password, and click OK.

7. Download the latest version of ORABRCOPY.SAR from SAP Marketplace (see SAP Note 784118 –

System Copy Java Tools) and unpack (using sapcar –xvf) into C:\oracle\orabrcopy.

8. Open a command prompt as user temadm, and execute ora_br_copy.bat as follows:

C:\oracle\orabrcopy\ora_br_copy.bat -generateFiles –forceLogSwitches –targetSid TEM –password vmwaresap7 listenerPort 1527

The following output is generated in the command prompt window:

C:\oracle\orabrcopy>ora_br_copy.bat -generateFiles -forceLogSwitches -targetSid

TEM -password vmwaresap7 listenerPort 1527

Warning: JAVA_HOME environment variable is not set.

C:\oracle\orabrcopy>java.exe -showversion -cp .\.;.\orabrcopy.jar;c:\oracle\T

EM\102\jdbc\lib\classes12.jar com.sap.inst.lib.app.SecureStartup com.sap.ins

t.orabrcopy.OraBRCopy -oracleHome c:\oracle\TEM\102 -sourceSid TEM -generate

Files -forceLogSwitches -targetSid TEM -password vmwaresap7 listenerPort 1527

java version 1.4.2_14

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_14-b05)

Java HotSpot(TM) Client VM (build 1.4.2_14-b05, mixed mode)

SQL*Plus: Release 10.2.0.1.0 - Production on Thu May 31 14:17:31 2007

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected.

Database closed.



of 110

Database dismounted.

ORACLE instance shut down.

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 -

Production

With the Partitioning, OLAP and Data Mining options



Connected to an idle instance.

ORACLE instance started.

Total System Global Area 507510784 bytes

Fixed Size 1249848 bytes

Variable Size 264244680 bytes

Database Buffers 239075328 bytes

Redo Buffers 2940928 bytes

Database mounted.

Database opened.


Production




Connected.

Database closed.

Database dismounted.

ORACLE instance shut down.


Production


C:\oracle\orabrcopy>

The following files are created: CONTROL.SQL and initTEM.ora.

The target SID of TEM will be manually changed in these files later to DEV during the cloning process.



of 110

5.2 Uninstall the CI Instance

To uninstall the CI instance

1. Run the following command:

Z:\51032260_BS_2005_SR2_SAP_Installation_Master_ia32\IM_WINDOWS_I386\sapinst.exe

2. From the menu, select the service you want to install: expand the folders for SAP ERP 2005 Support release 2 > Additional Software Life Cycle Tasks > Uninstall and select Uninstall – System / Standalone Engine. Click Next.



of 110

12. Enter the Profile Directory as C:\usr\sap\TEM\SYS\profile, and click Next.



of 110

3. Select Remove all instances of the SAP system or standalone engine on this host and Remove OS users of SAP system or standalone engine on this host. Click Next.



of 110

4. Deselect Uninstall database and click Next.



of 110

5. Click Start to initiate removal of the CI instance.



of 110

6. After completion (approximately two minutes), click OK.

The CI instance and the SAP user ID have been deleted, but the Oracle database and software still remain.



of 110

5.3 Uninstall Oracle Home

Confirm that the Oracle instance is down after running ora_vr_copy.bat in the previous procedure.

To uninstall Oracle home

1. Copy the sqlplus executable to the desktop as follows: click Start > All programs > ORACLE-

TEM102 > Application Development > Sql Plus.

2. Right-click the Sql Plus icon and select Properties.

3. Change the target to C:\oracle\TEM\102\BIN\sqlplusw.exe /nolog.

4. Double-click the Sql Plus icon. This displays the Oracle SQL*Plus Window.

5. Enter the following commands on the SQL command line:

SQL> set instance tem

Oracle Database 10g Enterprise Edit ion Release 10.2.0.1.0 - Product ion

With the Part it ioning, OLAP and Data Mining options

SQL> connect /as sysdba

Connected to idle instance

SQL>

6. Access Oracle services as follows: click Start > All Programs > Administrative Tools > Services.

7. Stop all Oracle services:

OracleJobSchedulerTEM

OracleServiceTEM

OracleTEM102iSQL*Plus

OracleTEM102TNSListener

8. Run the Oracle Installer as follows: click Start > All programs > Oracle—TEM102 > Oracle Installation Products > Universal Installer.



of 110

9. Click Deinstall Products.

10. Select Oracle Homes > TEM102. Click Remove.



of 110

11. On the Confirmation window, click Yes.



of 110

12. Click Close.

13. Click Cancel.

14. Delete c:\oracle\TEM\102 c:\Program Files\Oracle (a restart of the operating system

might be needed because files in these directories might be still in use). Oracle software has been

removed, but the Oracle data files all remain under c:\oracle\TEM. These are saved as part of the

template.

15. In Windows, select Start > Shutdown to shut down the guest operating system.



of 110

5.4 Create the Template Using the VI Client

To create the template using the VI client

1. Right-click the virtual machine sap3_vm and select Clone to template.

2. Enter Template Name: sap3_vm_golden .

3. Under Datacenters, select HP.

4. Click Next.



of 110

5. Select host 156.153.117.63 and click Next.

6. Select datastore VMFS03 and click Next.



of 110

7. Select Normal, and click Next.

8. Click Finish.



of 110

9. Select the Tasks & Events tab.

10. Select Clone Virtual Machine. The progress of the task is shown (this lasted approximately 70 minutes for a 115GB VM). This creates a template storing the Oracle backup (SID = TEM) of the SAP ECC 6.0 system.



of 110

6. Provision a New SAP System from a Template (new SID = DEV)

The high level procedure for deploying a new SAP ECC 6.0 system from a template is as follows:

1. Extract the Windows Sysprep tools from the Windows install media or the Microsoft Web site.

2. Deploy/clone a new virtual machine from the template using the VMware guest operating system customization feature to set new Run the SAP SID rename process in the cloned virtual machine to create a new SAP ECC 6.0 system with SID = DEV. This is based on the SAP System Copy Guide.

3. A new SAP license is required on the cloned virtual machine.

4. Specify Host name and network parameters.

6.1 Background – SAP System ID Rename Based on the SAP System Copy Guide

SAP Note 11691 – Renaming the system ID requires using the SAP System Copy Guide for renaming the system ID (SID) of an existing system. The SAP guide used here is System Copy for SAP Systems Based on SAP NetWeaver 2004s SR2 ABAP. This is available at http://service.sap.com/instguides.

The SAP System Copy Guide covers the rename procedure for different databases. The Oracle-specific steps followed here are based on having an exact copy of the database files, such as an offline backup or in this case a backup of the database in the template (created in the previous section).

6.1.1 Prepare for Guest OS Customization

Deploying a new virtual machine from a template or clone of an existing virtual machine presents an opportunity to customize the new guest operating system. The Guest Optimization wizard guides the user through the virtual machine cloning process.

The Windows guest operating system environment is customized using Sysprep utility tools. These tools can be obtained either from the Microsoft Web site or from the Windows install CD and must be installed on the Windows system where VirtualCenter is running.

On the Windows Server 2003 CD, perform the following:

1. Locate the DEPLOY.CAB file in the directory \support\tools.

2. Open and expand the DEPLOY.CAB file using a tool such as winzip.exe or another tool capable of

reading Microsoft CAB files.

3. Extract the files to the directory appropriate to your guest operating system, for example, C:\Documents and Settings\All Users\Application Data\VMware\VMware

VirtualCenter\sysprep\svr2003

The extracted files from DEPLOY.CAB are shown in the following screenshot.




of 110

6.2 Clone a New Virtual Machine from a Template

1. Start and log into the VI Client. Select datacenter lab_dc and click the Virtual Machines tab.

2. Right-click sap_vm_golden and select Deploy Virtual machine from Template.



of 110

3. Enter a new virtual machine name, in this example, sap_vm_clone. Select the datacenter HP, and click Next.

4. Select host 156.153.117.63 and click Next.



of 110

5. Select the datastore VMFS03, and click Next.

6. The customize options that appear are based on the Sysprep set up in Section 6.1.1, Prepare for Guest OS Customization. Select Customize using the Customization Wizard and click Next.



of 110

7. Enter the Name and Organization. Click Next.

8. Select Use a specific name and enter vega7067, which is the host name of the new virtual machine.

9. Click Next.



of 110

10. Leave the Product ID field blank. The license key is provided upon system boot after cloning. Click Next.

11. Enter and confirm a Password.

12. Click Next.



of 110

13. Select the appropriate time zone and click Next.

14. Leave the command field blank, and click Next.



of 110

15. In this case Custom settings was already selected. Click Next.

16. Select NIC 1, and click Customize.



of 110

17. Enter the network configuration fields as shown, and click OK.

18. Click Next.



of 110

19. In this case Workgroup was already selected. Click Next.

20. Click Next.



of 110

21. Do not save this customization. Click Next.

22. Click Finish.



of 110

23. Click Finish.

24. View the progress in VI Client under Tasks and Events.



of 110

25. The cloning process took approximately 80 minutes. When it is complete, power on the virtual machine sap_vm_clone.

26. Enter the Product Key and click Next. Windows restarts.



of 110

6.3 Install Oracle software (SID = DEV)

To install the Oracle software (SID = DEV)

1. Change the following environment variables to reflect the new SID = DEV:

ORACLE_HOME = C:\oracle\DEV\102

Add to PATH C:\oracle\DEV\102\bin

2. Set Windows environment variables by clicking Start > My Computer, then right-click and select Properties > Advanced Tab > Environment Variables.

3. Run the Oracle Universal Installer to install the database software for SID = DEV.

4. Run the sapserver.cmd executable from the SAP Oracle install DVD, as documented in Chapter 4

of the SAP install guide SAP ERP 2005 SR2 ABAP on Windows: Oracle.

6.3.1 Run sapinst

Note that the exact flow and sequence might be different in later versions of the sapinst tool.

To run sapinst

1. Execute the sapinst tool located in the master installation CD. In this case it has been copied to a

network drive Z:

Z:\51032260_BS_2005_SR2_SAP_Installat ion_Master_ia32 \ IM_WINDOWS_I386\sapinst .exe

2. Select from the menu SAP ERP 2005 Support Release 2 > Additional Software Life-Cycle Tasks > System Copy > Oracle > Target System > Central System > Based on AS ABAP > Central System Installation.

3. Click Next.



of 110

4. Select Typical. Click Next.

5. Enter DEV for the SAP System ID (SAPSID), select Unicode System (recommended), and click Next.



of 110

6. Enter a password. Click Next.

7. Select Homogeneous System Copy (Backup/Restore), and click Next.



of 110

8. Enter DEV for the Database ID (DBSID), and click Next.

9. Click Cancel to ignore system checks. The error window is displayed.



of 110

10. Click Stop. Apply SAP Note 970518.

11. Edit control.xml in thsapinst install directory C:\Program

Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP.

12. Search for update ORACHECK_PAR and delete the row beneath it, row.createDb = false.

13. Restart sapinst: Z:\51032260_BS_2005_SR2_SAP_Installat ion_Master_ia32 \ IM_WINDOWS_I386\sapinst .exe

14. Select from the menu, SAP ERP 2005 Support Release 2 > Additional Software Life-Cycle Tasks > System Copy > Oracle > Target System > Central System > Based on AS ABAP > Central System Installation.

15. Click Next.



of 110

16. Select Continue old installation and click OK.

17. Click Cancel to ignore system checks.



of 110

18. Enter SAPSR3 in the ABAP Schema field. The other fields use defaults.

19. Click Next.

20. Enter the Password of 'DDIC' in client 000 in the source system as vmwaresap7, and click Next.



of 110

13. Enter the location of the install media:

UC Kernel NW2004sSR2: Z:\51032266_11_NW_2004s_SR2_Kernel_WINDOWS__LNX_X86

Oracle Client: Z: \51031613_CD_ORACLE_10.2_Client_windows_i386

21. Review the input parameters and click Start.



of 110

22. Enter the Solution Manager Key and click Continue.

23. The rename stops with a notification window. Proceed as directed in the following steps.



of 110

24. Update C:\orabrcopy\CONTROL.SQL—change all occurrences of TEM to DEV.

25. Rename C:\orabrcopy\initTEM.ora to initDEV.ora and change all occurrences of TEM to

DEV.

26. Copy CONTROL.SQL to install directory: C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP

27. Copy initDEV.ora to C:\oracle\DEV\102\database.

28. Delete entries in: C:\oracle\TEM\oraarch\, C:\oracle\TEM\saparch;

C:\oracle\TEM\saptrace\background, C:\oracle\TEM\saptrace\usertrace

29. Delete all three TEM control files. See the old initTEM.ora file for the location of the control files.

Note The previous two steps could have been performed before creation of the template. In Windows

Explorer, move all subdirectories in C:\oracle\TEM to C:\oracle\DEV.



of 110

30. Returning to the sapinst window, click OK.

31. Accept the defaults and click Continue.



of 110

32. Click OK.

The creation of a new SAP system from the golden template is now complete. The sapinst utility

creates a temporary license. A new permanent SAP license for the cloned SAP system must be applied.



of 110

7. Snapshots

Snapshots preserve the state of a virtual machine. This feature captures the entire state of a virtual machine at the time of the snapshot is taken, including the memory state, the settings state (virtual machine settings), and the disk state. Reverting to a snapshot returns these items to the state they were in at the time the snapshot was taken. Using this feature allows tests to be run with just one virtual machine. The test here demonstrates using Snapshots to test a guest operating system patch update.

Note The Snapshot tests were carried out on the original virtual machine, sap_vm, before it was used to create the template.

The following two snapshots are taken of sap_vm, with the following different states:

sap_vm snapshot1 sap_vm snapshot2

Windows Server 2003 SP1 Windows Server 2003 SP2

Oracle db up Oracle db up

CI instance down CI instance up

No SAP correction request SAP correction request—TEMK900002

The test sequence is as follows:

1. Initial state: sap_vm is up, CI instance is down, Oracle database is up, the guest operating system is Windows Server 2003 SP1.

2. Take snapshot: name sap_vm snapshot1.

3. Shut down the Oracle database, patch the Windows operating system to SP2, and restart the database and CI instance. In the example here, operating system patch testing is simulated (alternatively it could be an SAP kernel patch update or an SAP software update).

4. Test SAP on Windows Server 2003 SP2. Create a correction in SAP, TEMK900002 (this is an SAP change management request and is created to simulate an online development or testing type of activity).

5. Take a snapshot named sap_vm snapshot2.

6. Assume there are problems with SAP and the SP2 patch, so revert back to the first snapshot sap_vm snapshot1 (Windows Server SP1).

7. Verify the status of the virtual machine, restart the CI instance, and confirm that correction TEMK900002 does not exist.



of 110

7.1 Take the First Snapshot and Update from Windows Server 2003 SP1 to SP2

To take the first snapshot and update Windows

1. Initially, the guest operating system (Windows Server 2003) is at patch level SP1.

2. On the VI Client, right-click sap_vm > Snapshot > Take snapshot.

3. Enter the Name and Description. Click OK.



of 110

4. Observe the progress in the Recent Tasks pane.

5. Right-click sap_vm and select Snapshot > Snapshot Manager.

6. Shut down SAP completely.



of 110

7. Upgrade the guest operating system’s version of Windows Server 2003 to SP2.

8. Restart SAP.



of 110

9. Create a correction request in SAP using transaction SE01 (SAP change management—tickets can be created in SAP to change SAP business configuration and/or SAP programs). This step is implemented here to simulate some activity and create a change in the system.

7.2 Take a Second Snapshot and Roll Back to the First

The status of sap_vm is as follows:

Guest operating system is Windows Server 2003 SP2.

Database up.

CI Instance up.

Correction request TEMK900002 created.



of 110

To take a second snapshot and roll back to the first

1. Take snapshot: Right-click sap_vm and select Snapshot > Take Snapshot.

2. Select sap_vm snapshot1 and click Go to.



of 110

3. Click Yes.



of 110

4. Review the progress in the bottom pane under Recent Tasks (of VI Client).

5. Log in to the guest operating system and verify rollback to the earlier snapshot.

The status of sap_vm is as follows:

The guest operating system is Windows Server 2003 SP1

Database is running.

CI instance down. Note the CI instance was previously running prior to the rollback; snapshots preserve the virtual machine memory state which includes state of the running processes.

Start CI instance—verify that correction TEMK900002 does not exist. This highlights that user changes might be lost during snapshot moves. Procedural steps are required to notify users that during patch testing, changes are lost when, in the event of unsuccessful testing, a rollback to an earlier snapshot is required.



of 110

8. vMotion – Live Migration

The following test sequence is executed to validate vMotion operations.

1. SAP is up and running in a virtual machine (sap_vm) on ESX host vega7063.

Note These tests were carried out on the original virtual machine, sap_vm, before it was used to create the template.

2. Start the SGEN process in SAP. This is the ABAP code generation utility that consumes CPU and database I/O.

3. Check the following monitoring tools to validate load and activity: VI Client CPU charts, SAP transactions SM50 (process monitor), and SM37 (batch job monitor).

4. Migrate sap_vm from ESX host vega7063 to vega7062.

5. Check monitoring tools for load and activity.

6. Perform SAP license check using the saplicense utility.

7. Migrate sap_vm from vega7062 back to vega7063.

8. Check monitoring tools for load and activity.

9. Perform SAP license check using the saplicense utility.

10. Run SAP transaction SM21 (system logs) to verify no disconnections in SAP during the migrations.

vMotion requirements are as follows:

Both ESX hosts have compatible CPUs (same server types).

Both ESX hosts are connected to a virtual switch assigned for vMotion operations (vMotion feature enabled).

Both ESX hosts are connected to a production switch for user access.

sap_vm virtual disk and VMFS configuration files reside on shared storage connected to both ESX hosts.



of 110

To validate vMotion operations

1. The vMotion resource map displays the requirements: log in to VI Client.

2. Click sap_vm and then click the Maps tab.

3. The current status is sap_vm running on ESX host vega7063.



of 110

8.1 Submit an SAP Batch Workload

A batch workload is executed in SAP, and monitoring tools (CPU charts in the VI Client and SAP transactions SM50 and SM37) verify that load/activity has started on ESX host vega7063.

1. Log in to the SAP UI (SAPGUI).

2. Proceed to transaction SGEN.

3. Select Generate All Objects of Selected Software Components, and click Continue.



of 110

4. Select EA-APPL and click Continue.

5. Select vega7066_TEM_00, and click Continue.



of 110

6. Click Start Job Directly.



of 110

7. Proceed to transaction SM37 to verify that the job has started and is active.

8. Wait approximately five minutes and proceed to transaction SM50 to view the SAP processes.



of 110

9. View the CPU utilization on vega7063 (through the VI Client).



of 110

8.2 Migrate the Virtual Machine from vega7063 to vega7062

The virtual machine, sap_vm, is live-migrated to the other ESX host. CPU performance charts in the VI Client show the following:

An initial CPU spike on the source host vega7063 after the migration is started.

The CPU utilization on the source host vega7063 drops to 50% and the CPU utilization on the target host vega7062 rises to 50%.

SAP transactions SM37 and SM50 verify that SAP activity is uninterrupted after the migration.

After migration, when the virtual machine is running on vega7062, an SAP license check is executed verifying that the license is OK.

To migrate the virtual machine

1. On the VI Client right-click sap_vm, then select Migrate.

2. Select 156.153.117.62. Click Next.



of 110

3. Click Next.

4. Click Next.



of 110

5. Click Finish. The progress of the vMotion operation is shown in the Recent Tasks pane.



of 110

6. The CPU utilization on vega7063 spikes and then drops to zero (time 10:57, as seen in the following screenshot).

7. The CPU utilization on vega7062 increases to approximately 50% (at time 10:57, as seen in the following screenshot).



of 110

8. While the virtual machine is running on ESX host vega7062, open an RDP session to the virtual

machine and verify that the SAP license with the SAP license program saplicense.

9. Verify that the SAP job is still running in SM50 and SM37.



of 110

8.3 Migrate the Virtual Machine from vega7062 to vega7063

The virtual machine sap_vm is live migrated back to vega7063. CPU performance charts in the VI Client show the following:

A CPU spike on the source host vega7062 after the migration has started.

The CPU utilization on the source host vega7062 drops from 50% to zeroand the CPU utilization on the target host vega7063 rises to 50%.

The CPU utilization in the virtual machine is near 100% and drops to zero for approximately one minute during the migrations.

SAP transactions SM37 and SM50 verify that SAP activity is uninterrupted after the migration.

After migration, when the virtual machine is running on vega7063, an SAP license check is executed verifying that the license is OK and that the SAP hardware key is the same.

SAP transaction SM21 (displays SAP system log activity) is executed for the period of the migrations and indicates no process interruptions or disconnections (normally any terminations in SAP can be seen in SM21).



of 110

To migrate the virtual machine

1. On the VI Client, right-click sap_vm. Select Migrate and navigate through similar screens as shown in Section 8.2 (the target host is vega7063/156.153.117.63).

2. Wait a few minutes for the migration to complete. The CPU utilization rises to approximately 50% on vega7063 (at time 11:10, as seen in the following screenshot).

3. The CPU utilization on vega7062 spikes and then drops to zero (at time 11:10, as seen in the following screenshot).



of 110

The CPU utilization in the virtual machine sap_vm is near 100%, but drops to zero for approximately one minute during the two live migrations (approximate times 10:56 and 11:09, as in the following screenshot).

4. Open an RDP session to the virtual machine (on vega7063) and verify that there is no change in the SAP license.



of 110

5. Verify that the SAP processes are still running (uninterrupted) by way of transactions SM37 and SM50.



of 110

6. The SAP system log, transaction SM21, shows no disconnections in the timeframe from 10:40—11:20, which is the period of testing vMotion. See the following screenshot.

7. Click Reread system log.



of 110

9. vMotion – Cold Migration

This scenario demonstrates the migration of VMware configuration files and the virtual disk of the virtual machine from one datastore to another. The virtual machine sap_vm is originally installed onto shared storage (datastore VMFS03). The ESX host has local storage of approximately 120GB. The test shows a cold migration of the virtual machine from shared to local storage.

Note The virtual machine is migrated back to shared storage for continuation of the remaining scenarios, but the screenshots are not shown.

To cold migrate the virtual machine from shared to local storage

1. Power off sap_vm.



of 110

2. Right-click sap_vm and select Migrate.

3. Select 156.153.117.63. Click Next.

4. Click Next again.



of 110

5. Select Move virtual machine configuration files and virtual disks.

6. Select datastore storage1—this is local storage on vega7063.

7. Click Next.

8. Click Finish.



of 110

9. View the progress in the Recent Tasks pane.

10. The storage relocation lasted approximately 50 minutes. After the migration, sap_vm is up and running on local datastore, storage1.



of 110

10. vSphere High Availability

The VMware HA test is executed as follows:

1. SAP is up and running in sap_vm on ESX host vega7063.

2. A cluster is created in the VI Client inventory pane and both ESX hosts are assigned to the cluster. This automatically configures the HA feature.

3. Host vega7063 is rebooted to simulate a crash.

4. sap_vm restarts on vega7062.

5. SAP must be manually restarted.

VMware HA requirements are as follows:

Each host in the cluster has access to the virtual machine files (through shared storage).

vMotion requirements (listed in Section 8) should be met.

Each ESX host in the cluster is configured to use DNS, and DNS resolution of the host’s fully qualified domain name is successful (VMware HA relies on this name). Screenshots of the ESX configuration in Appendix A show the DNS configuration.

To validate HA

1. Right-click HP datacenter and select New Cluster.

2. Enter the name HA Cluster, select VMware HA, and click Next.



of 110

3. Accept the defaults and click Next.

4. Click Finish.



of 110

5. Drag and drop the ESX hosts into the HA Cluster (in the left pane). Span HA Cluster and select the Task and Events tab to view the progress of the HA configuration.

The status is that sap_vm is running on vega7063.

6. Reboot vega7063 to simulate a failure: right-click 156.153.117.63 and select Reboot.

7. Click Yes on the warning, type a reason for reboot, and click OK.

8. View the event log during the failure of vega7063. Select HA Cluster in the inventory pane, click the Tasks & Events tab, click Events, click the Show all entries drop-down menu, and select Show Cluster Entries.



of 110

9. sap_vm comes up on vega7062.

10. Manually start up SAP in sap_vm.



of 110

Appendix A: ESX Host Configuration Screenshots

The following screenshots show a summary of the hardware and CPU of the ESX hosts.



of 110



of 110

The following screenshots show the networking characteristics of both ESX host installations.



of 110



of 110

Appendix B: HP Infrastructure Environment

HP c-Class half-height server blades meet all requirements for data center redundancy in a small, easily expandable platform with capacity for large memory and hot-plug hard drives.

Networking requirements: The half-height blades support up to six network interfaces while maintaining dual-port Fibre Channel connectivity to SAN.

SAN connection: A single Fibre Channel host bus adapter (HBA) with two ports is acceptable in most environments, which makes SAN connectivity a minor decision point for choosing a blade. Redundant connections to Fibre Channel are available in every HP c-Class half-height blade server.

Processor: The HP ProLiant c-Class blade servers feature the latest generation processors, including the Intel Xeon 5000 and 5100 series and AMD Opteron 2000 series.

Density: Half-height blades optimize floor space, power efficiency, and cooling. With no loss in functionality versus a full-height blade and the ability to spread infrastructure costs out over more servers, the half-height blades are an excellent choice for dense environments where power and floor space are at a premium.

For information on HP c-class blades and SAP performance go to http://www.hp.com and search for Leadership SAP benchmark on HP BL460c Intel Xeon and DL585 G2 AMD Opteron servers.

Enclosure Configuration

The configuration recommends the NC325m 4-port network adapter for the ProLiant BL460c or BL465c servers. This adapter allows for six individual gigabit network ports. As such, the enclosure should be outfitted with a minimum of three network uplinks and a total of six network uplinks for redundancy. These network uplinks should be placed in switch slots 1, 5, and 7 in a non-redundant configuration, and in slots 1, 2, 5, 6, 7, and 8 for full redundancy.

A channel uplink is required in switch slot 3 for a non-redundant configuration and in slots 3 and 4 for full redundancy. The latter configuration allows for a redundant 4Gb Fibre Channel connection from each blade within the enclosure. When switches are used internally, the need for external Fibre Channel switching is greatly reduced, saving costs and reducing cable failure risks and complexity.

Figure 7 and Figure 8 depict the network switch configuration and enclosure configuration for the servers used in the creation of this deployment guide. Additional HP documentation can be found in the following locations:

HP VMware Server Virtualization http://www.hp.com/go/vmware

http://www.hp.com/

http://www.hp.com/go/vmware



of 110

Figure 7. Network Switch Configuration



of 110

Figure 8. Enclosure Configuration

SAP Solutions on VMware - Deployment Guide

Documents

Transcript of SAP Solutions on VMware - Deployment Guide