VMware SAP Software Solutions Deployment Guide

VMware White Paper VMware and SAP Software Solutions Deployment Guide
VMware and SAP Software Solutions

Deployment Guide
Vas Mitra
SAP Solutions Engineer
VMware
Note from the Author

The primary audiences for this guide are:
• Customers in the early stages of adopting VMware® Infrastructure solutions.
• Existing SAP customers who are considering or planning to deploy VMware Infrastructure
solutions.
• Existing VMware customers who are considering or planning to deploy new SAP application
environments.
The content in this document is based on tests conducted at the HP Partners Solutions Lab, in
Cupertino, California.
I would like to thank the following for their valuable support for this deployment guide.
HP Solution Alliances Engineering for their time and use of the HP servers and storage in the HP
Partner Solutions Lab.
VMware
Matthias Czwikla, Senior Business Development Manager, SAP
Michael Hesse, Technical Alliance Manager, SAP
Christine Holland, ISV Alliances Marketing Communications Manager
Johanna Holopainen, Senior Manager, ISV Alliances GTM
Raj Ramanujam, ISV Solutions Manager
Christoph Reisbeck, Director, Global SAP Alliances
Table of Contents
1. Introduction..................................................................................................................................................................1
1.1. SAP Platform Overview ....................................................................................................................................... 1
1.2. VMware® Infrastructure 3 Software Suite ....................................................................................................... 2
1.2.1. VMware ESX Server ..................................................................................................................................................................... 2
1.2.2. VMware® VirtualCenter ............................................................................................................................................................. 3
1.3. HP Hardware Overview....................................................................................................................................... 3
1.4. SAP Datacenter Benefits ..................................................................................................................................... 4
1.4.1. Server Containment ................................................................................................................................................................... 4
1.4.2. Availability......................................................................................................................................................................................... 4
1.4.3. Rapid Provisioning....................................................................................................................................................................... 5
2. Deployment Approach Summary...................................................................................................................6
2.1. Install SAP in Virtual Machine ............................................................................................................................ 6
2.2. Create Template & Provision New SAP System from Template ............................................................... 6
2.3. Snapshots ............................................................................................................................................................... 7
2.4. VMotion – Live Migration ................................................................................................................................... 8
2.5. VMotion – Cold Migration.................................................................................................................................. 8
2.6. High Availability .................................................................................................................................................... 8
2.7. SAP on VMware Deployment Tips / Best Practice Guidelines .................................................................. 9
3. Infrastructure Environment.............................................................................................................................. 10
3.1. Software and Hardware ....................................................................................................................................10
3.2. Logical Architecture...........................................................................................................................................10
3.3. Physical Architecture .........................................................................................................................................11
4. Install SAP ECC 6.0 in Virtual Machine (SID = TEM)............................................................................ 12
4.1. Install VMware Infrastructure 3........................................................................................................................12
4.2. Create Virtual Machine......................................................................................................................................13
4.3. Guest OS Install ...................................................................................................................................................17
4.4. SAP Install .............................................................................................................................................................22
5. Create Template...................................................................................................................................................... 23
5.1. Run SAP orabrcopy Tool ...................................................................................................................................23
5.2. Uninstall CI Instance...........................................................................................................................................25
5.3. Uninstall Oracle Home ......................................................................................................................................30
5.4. Create Template Using VI Client.....................................................................................................................34
6. Provision New SAP System from Template (new SID = DEV)...................................................... 38
6.1. Background - SAP System ID Rename based on SAP System Copy Guide .........................................38
6.2. Prepare for Guest OS System Customization..............................................................................................38
6.3. Clone New Virtual Machine from Template ................................................................................................39
6.4. Install Oracle software (SID = “DEV”)..............................................................................................................51
6.5. Run sapinst...........................................................................................................................................................51
7. Snapshots.................................................................................................................................................................... 71
7.1. Take First Snapshot and Upgrade from Windows Server 2003 SP1 to SP2 .........................................71
7.2. Take Second Snapshot and Rollback to First...............................................................................................75
8. VMotion – Live Migration.................................................................................................................................. 78
8.1. Submit SAP Batch Workload............................................................................................................................79
8.2. Migrate Virtual Machine from vega7063 to vega7062 .............................................................................84
8.3. Migrate Virtual Machine from vega7062 to vega7063 .............................................................................89
9. VMotion – Cold Migration ................................................................................................................................ 94
10. High Availability................................................................................................................................................. 98
11. Appendix 1 – ESX Server Configuration Screenshots ............................................................. 102
12. Appendix 2 - SAP on VMware Deployment Tips / Best Practice Guidelines ............. 108
13. Appendix 3 – HP Infrastructure Environment.............................................................................. 109
1. Introduction
This guide demonstrates the deployment of SAP ERP software on the VMware Infrastructure
platform and showcases the benefits that VMware solutions provide for the SAP datacenter.
Users will find the technical steps, accompanied by screenshots, 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® VMotion™; VMware® 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.
For an overview of VMware Infrastructure features and its business benefits in SAP environments,
consult the whitepaper, VMware® Infrastructure for SAP Enterprise Applications: Use Cases, which can
be downloaded from the SAP alliance showcase on VMware.com.
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 number 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.
o The specific SAP product determines the type of application service required (ABAP,
Java or both).
• SAP enables a distributed architecture that allows the above 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 will install the core SAP ERP product. . The
architecture includes a database and Central Instance (CI) running ABAP only application services.
1
1.2. VMware® Infrastructure 3 Software Suite

VMware Infrastructure 3 simplifies IT environments so that customers can leverage their storage,
network, and computing resources to control costs and respond quickly to changing business
needs. The VMware Infrastructure approach to IT management creates virtual services out of the
physical infrastructure, enabling administrators to allocate these virtual resources quickly to the
business units that need them most.
Figure 1-1. VMware Infrastructure
VMware Infrastructure 3 is the next generation of industry-leading infrastructure software that

virtualizes servers, storage, and networking, allowing multiple unmodified operating systems and
their applications to run independently in virtual machines while sharing physical resources. This
document uses the two central VMware Infrastructure software components: VMware® ESX Server
and VMware® VirtualCenter.
1.2.1. VMware ESX Server

VMware ESX Server abstracts processor, memory, storage, and networking resources into multiple
virtual machines, giving IT greater hardware utilization and flexibility.
Figure 1-2. VMware Infrastructure 3 - ESX Server
1.2.2. VMware® VirtualCenter

VirtualCenter enables rapid provisioning of virtual machines and performance monitoring of
physical servers and virtual machines. VirtualCenter intelligently optimizes resources, ensures high
availability to all applications in virtual machines, and makes IT environments more responsive
with virtualization-based distributed services such as VMware® High Availability (HA) and VMware®
VMotionTM.
Figure 1-3. VMware VirtualCenter Management Server
1.3. HP Hardware Overview

To run the procedures outlined in this guide, HP recommends a c-Class BladeSystem
implementation for VMware Infrastructure 3 on half-height ProLiant c-Class blade servers. 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 13.
The ProLiant BL460c and BL465c servers double the amount of computing capacity in the same
space versus full-height blades while keeping the same flexibility, power management and system
control and VI3 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. For more information on using the ProLiant
BL460c and BL465c servers for a VMware Infrastructure, see the HP reference configuration
guide on http://h71028.www7.hp.com/ERC/downloads/4AA0-9717ENW.pdf.
HP BladeSystem servers, storage, and other modular components can be easily added or removed
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.
1.4. SAP Datacenter Benefits

The SAP-VMware Infrastructure deployment scenarios described in this document demonstrate
the following benefits that the VMware Infrastructure 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.
Key benefits of using VMware Infrastructure for server containment:

• 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 Server host can be restarted on another ESX
Server host within minutes. With VMware VMotion, it is possible to migrate live SAP virtual
machines between ESX Server hosts, and to move SAP instances off failing hardware, with minimal
interruption to end users.
Key benefits of using VMware Infrastructure to achieve high availability:

• 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 Server host in case of failures.
• Cause minimal interruption to end users during live migration of SAP virtual machines from one ESX
Server host to another, and minimize downtime during hardware maintenance.
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. By using VMware infrastructure, SAP customers can take advantage of virtual
machine templates to provision new pre-configured SAP environments in minutes on virtualized
infrastructure hardware.
Cloning ensures 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.
2. Deployment Approach Summary

This section summarizes the tests and results documented in this guide.
2.1. Install SAP in Virtual Machine

The lab environment consists of two ESX Server hosts connected to shared storage. SAP ECC 6.0
system (database and central instance) is installed onto a single virtual machine with the following
properties: Windows 2003 Server guest OS; 115 GB VMFS disk; two virtual CPUs; 3GB RAM..
The installation of SAP in a virtual machine is no different from that of a physical environment.
2.2. Create Template & Provision New SAP System from 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 OS 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 OS but with different SID and
host name. This process is much faster than installing a virtual machine, guest OS 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 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 combination of databases and
operating systems. The parts relevant for the tests described here are: Oracle on Windows
homogeneous system copy option based on the Oracle backup/restore method.
The complete template, cloning and rename process is shown in the following diagrams.
Specialized terms used in the diagram are defined here:
• ”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”: a SAP Java tool that connects to a live Oracle instance and generates control and
parameter files which are used to rename the SID of an Oracle database.
Install SAP in Virtual Machine

Create Golden Image
Deploy New SAP system from Template
The timings are approximate and are based on the tests conducted in the lab. Faster deployment
from the template has the following features:
• General:
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 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.
• 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 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 System Copy Guide).
• Disadvantages:
o Includes manual steps (Oracle software deinstall and reinstall, “sapinst” input screens).
o Requires some of the SAP install media CDs/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 need to 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 Infrastructure 3 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; SAP ABAP or Java software.
Users need to be aware that any changes made to SAP during the testing phase after a patch or
upgrade has been applied will be 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 Server hosts. The workload is created by running SAP transaction SGEN (this generates
and compiles ABAP code and is a standard utility executed after a fresh SAP install).
CPU performance charts from 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 Server host.
The tests generated the following results, based on the CPU performance charts from the VI client:
• The batch workload generates about 50% CPU utilization on the 4-way ESX Server host.
• The CPU utilization in the virtual machine is near 100%.
• The CPU utilization of the ESX Server 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 Server host machine
before falling to zero. This spike is attributed to the copying of the memory state from the
source ESX Server 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 Server host) and
back again.
This functionality provides a benefit, for example, during the initial setup of an environment where
shared storage (SAN, iSCSI, NAS) might not yet be available but local storage on the ESX Server
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 High Availability provides ESX Server based HA capability with
minimum configuration. This feature manages ESX Server 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 Server host and the virtual machine is
restarted on the remaining server. This feature does not automatically restart the SAP application,
which needs to be manually restarted after the virtual machine is powered up on the failover
server.
2.7. SAP on VMware Deployment Tips / Best Practice Guidelines

Appendix 2 outlines some best practice guidelines for deploying SAP software on the VMware
platform. The content is not specifically based upon the tests described in this guide but upon
several tests that have been conducted by VMware.
3. Infrastructure Environment
3.1. Software and Hardware
The creators of this guide used the following software and hardware.
Software:
• VMware Infrastructure 3: ESX Server 3.0.1; VirtualCenter 2.0; VMware Infrastructure (VI) Client 2.0
• Guest OS: Windows Server 2003 SP1
• SAP ECC 6.0 Unicode / NetWeaver 2004s R2 / Oracle 10g / ABAP stack
• A single virtual machine running an SAP CI and Oracle Database instance on Windows Server
2003 SP1
Hardware:
• ESX Server hosts: 2 x HP Proliant BL 460c ; 4 CPU x 3 GHz each; 16GB RAM
• SAN: HP EVA 6000 2C2D disk array (14 ea. 146GBHDD)
• 2 ea. HP SAN Switch
• Network: Gigabit Ethernet
3.2. Logical Architecture
Figure 3-1: Logical architecture for SAP software on VMware Infrastructure

3.3. Physical Architecture
Figure 3-2: Physical architecture for SAP software on VMware Infrastructure

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

4.1. Install VMware Infrastructure 3
Installation of VMware Infrastructure is not covered in this document. Consult the following
VMware documentation at http://www.vmware.com/support/pubs/vi_pubs.html.
Appendix 1 shows screenshots of the ESX Server configuration. The following table gives an
overview of the ESX Server setup used for these tests.
ESX Server Datacenter name HP
Virtual Machine (VM) name sap_vm
VM storage size 115 GB
VM Windows guest OS drive C:\
VM memory assigned 3 GB
VM CPUs assigned 2
VM Windows guest OS host name vega7066
SAP instances installed in VM Oracle + CI (ABAP stack)
Datastore name VMFS03 (1 x 600GB shared VMFS

LUN)
ESX server host names vega7062

vega7063
Cloned VM Windows guest OS host name vega7067
For this test environment I/O performance is not a consideration and LUN count is limited; as a
result the 115GBstorage 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.
4.2. Create Virtual Machine

The steps to create a virtual machine called “sap_vm” are shown below.
Select 156.153.117.63. Right click -> New Virtual Machine.
Select Typical, click on Next.

Enter name: sap_vm, select HP, click on Next.
Select shared storage, datastore = VNFS03. Click on Next.

Select Microsoft Windows Server 2003, Enterprise Edition. Click on Next.
Number of virtual processors: 2. Click on Next.

Enter memory = 3000. Click on Next.
Number of NICs = 1, select network = Production. Click on Next.

Enter disk size = 115. Click on Next.
Click on Finish.
4.3. Guest OS Install

The Windows install ISO image is copied to local storage on the ESX Server host.
Select “sap_vm,” right click -> Edit Settings.
Select “Connect at power on.” Select “datastore ISO file.” Select Browse and navigate to
/storage1/iso_images/win2k3sp1.iso. Click on OK.
(At the ESX Server level the Windows iso image is copied to: /vmfs/volumes/storage1
(1)/iso_images.)
Select “Console” tab.
Select “sap_vm,” right click -> Power On.
Select A (Enterprise Edition), <enter>.

Follow instructions for standard Windows Server Install. To navigate cursor out of the console area,
select <Ctrl> + <Alt>. Optimal mouse performance is achieved after the VMware Tools software
package is installed on the Windows guest operating system immediately after the Windows
installation.
After the Windows install is complete, select “sap_vm,” right mouse click -> Send Ctrl+Alt+Del (to
log in to Windows.
Select “sap_vm,” right mouse click -> Install VMware Tools.
Select OK.
Proceed with a typical install of VMware tools. After install, at the prompt, set the hardware
acceleration to full and restart Windows. Mouse navigation will be much easier after this.
4.4. SAP Install

The SAP install process in a virtual machine is the same procedure as on 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 consult the SAP install guide, “SAP ERP 2005 SR2 ABAP on
Windows:Oracle” which is available at http://service.sap.com/instguides.
5. Create Template
Current status: SAP system TEM running in sap_vm, on ESX Server host vega7063.
A golden image of the virtual machine is created as a template. This image will be 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.
The following steps are executed:

• Run SAP “orabrcopy” tool to generate the Oracle initTEM.ora and CONTROL.SQL file. This is
required for the Oracle rename to another system ID (SID). The SID contained in these files is
“TEM” – this will be changed to the desired target SID (“DEV”) during the deployment of the
new VM. These files are saved in the virtual machine at c:\oracle\orabrcopy.
• Uninstall the CI instance using “sapinst.”
• Uninstall Oracle software using the Oracle Universal Installer.
• 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.
• At this point the virtual machine contains the Oracle data files stored under c:\oracle\TEM. This
corresponds to a database backup.
• Create virtual machine template. This will be the golden image from which to deploy a new
virtual machine and provision a new SAP system.
5.1. Run SAP orabrcopy Tool

Shutdown CI instance using SAP Management Console. Double click on SAP Management
Console icon on desktop.
Menu select: Console Root -> SAP Systems -> TEM -> vega7066 0 right mouse click. Select
Shutdown. Confirmation window click on Yes. Enter Administrator password, click on OK.
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.
Open Command prompt as user temadm and execute ora_br_copy.bat:
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.
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.
Connected.
Database closed.
Database dismounted.
ORACLE instance shut down.

C:\oracle\orabrcopy>
The following files are created: CONTROL.SQL and initTEM.ora. The target SID of “TEM” will be
changed manually in these files later to “DEV” during the cloning process.
5.2. Uninstall CI Instance

Execute
Z:\51032260_BS_2005_SR2_SAP_Installation_Master_ia32\IM_WINDOWS_I386\sapinst.exe
Menu: SAP ERP 2005 Support release 2 -> Additional Software Life Cycle Tasks -> Uninstall ->
Uninstall – System / Standalone Engine.
Click on Next.
Enter Profile Directory: C:\usr\sap\TEM\SYS\profile.

Click on Next.
Select “Remove all instance…” and “Remove OS users of SAP …”

Click on Next.
UNSELECT “Unintall database…”

Click on Next.
Click on Start to initiate removal of CI instance.

After completion (about 2 minutes), click on OK.

The CI instance + SAP user id has been deleted, but the Oracle database + software still remain.
5.3. Uninstall Oracle Home

Oracle instance should be down after running ora_vr_copy.bat in the previous step. Confirm this.
Copy sqlplus executable to desktop (Start menu All programs -> ORACLE-TEM102 -> Application
Development -> Sql Plus)
Right click Sql Plus icon, select properties, Change target to: C:\oracle\TEM\102\BIN\sqlplusw.exe
/nolog
Double click on Sql Plus icon - this displays Oracle SQL*Plus Window. Enter following on SQL
command line:
SQL> set instance tem
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 -
Production
SQL> connect / as sysdba
Connected to idle instance
SQL>
Access the Oracle services using Windows menu: Start -> All Programs -> Administrative Tools ->
Services. Stop all the Oracle services: OracleJobSchedulerTEM; OracleServiceTEM;
OracleTEM102iSQL*Plus; OracleTEM102TNSListener.
Run Oracle Installer:

Start -> All programs -> Oracle – TEM102 -> Oracle Installation
Products -> Universal Installer
Click Deinstall Products.

Select Oracle Homes -> TEM102.
Click on Remove.
Click on Yes.
Click on Close.
Click on Cancel.
Delete c:\oracle\TEM\102 c:\Program Files\Oracle (a restart of the OS might be needed as 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
will be saved as part of the template.
On Windows select Start -> Shutdown (shutdown guest OS).
5.4. Create Template Using VI Client

Select virtual machine sap3_vm, right click, -> “clone to template.”
Enter Template Name: sap3_vm_golden.

Select Datacenter HP.
Click on Next.
Select host 156.153.117.63. Click on Next.
Select datastore VMFS03. Click on Next.

Select Normal. Click on Next.
Click on Finish.
Select “Tasks & Events” tab, select “Clone Virtual Machine” – progress of task is shown (this lasted
about 70 minutes for a 115GB VM).
This creates a template storing the Oracle backup (SID = “TEM”) of the SAP ECC 6.0 system.
6. Provision New SAP System from Template (new SID =

DEV)
The sequence to deploy a new SAP ECC 6.0 system from the template is:
• Extract Windows OS “sysprep” tools from Windows OS install media or Microsoft website.
• Deploy / clone new virtual machine from the template using VMware guest OS 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.
• A new SAP license is required on the cloned virtual machine.
• Host name and network parameters.
6.1. Background - SAP System ID Rename based on 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 for download from
http://service.sap.com/instguides.
The 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.2. Prepare for Guest OS System 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 OS environment is customized using “sysprep” utility tools. These tools can be
obtained either from the Microsoft website or from the Windows OS CD and need to be installed
on the windows machine where VirtualCenter is running.
On the Windows 2003 OS CD:

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.
C:\Documents and Settings\All Users\Application Data\VMware\VMware
VirtualCenter\sysprep\svr2003
The extracted files from DEPLOY.CAB are shown below.

6.3. Clone New Virtual Machine from Template

Start and log into the VI client. Select datacenter “lab_dc,” click on “Virtual Machines” tab.
Select sap_vm_golden, right mouse click -> “Deploy Virtual machine from Template.”
Enter new virtual machine name: sap_vm_clone. Select datacenter HP. Click on Next.
Select host 156.153.117.63. Click on Next.

Select datastore VMFS03. Click on Next.
The customize options below will appear based on the “sysprep” set up in section “Prepare for
Guest OS Customization.”
Select “Customize using the Customization Wizard”. Click on Next.

Enter fields Name and Organization. Click on Next.
Select “Use a specific name”; enter “vega7067” – host name of new virtual machine. Click on Next.
Leave blank. License key will be provided upon system boot after cloning. Click on Next.
Enter and confirm password. Click on Next.

Select Pacific Time zone. Click on Next.
Leave blank. Click on Next.

In this case Custom was selected. Click on Next.
Select NIC 1. Click on Customize.

Enter fields as shown above. Click OK.
Click on Next.
In this case Workgroup was selected. Click on Next.
Click on Next.
Do not save customization. Click on Next.
Click on Finish.
Click on Finish.
View progress in VI client under “Tasks and Events.”
The cloning lasted approximately 80 minutes.

Power on the virtual machine sap_vm_clone.
Enter license key. Click on Next.
Windows will restart.

6.4. Install Oracle software (SID = “DEV”)

Change the following environment variables to reflect new SID = DEV: ORACLE_HOME =
C:\oracle\DEV\102; add to PATH C:\oracle\DEV\102\bin
Windows environment variables can be set with: Start -> My Computer, right mouse click, select
Properties -> Advanced Tab -> Environment Variables
Run the Oracle Universal Installer to install the database software for SID = DEV. 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.5. Run sapinst

Note the following:
• The screenshots below are based on the version of “sapinst” in the master installation CD
downloaded from SAP (http://service.sap.com/swdc) in April 2007.
• The exact flow and sequence might be different in later versions of the "sapinst" tool.
Execute the “sapinst” tool located in the master installation CD. In this case it has been copied to a
network drive Z:
Select 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
Click on Next.
Select Typical. Click on Next.

Enter SAPSID = DEV, Select Unicode. Click on Next.

Enter Passwords for system. Click on Next.

Select Homogeneous System Copy. Click on Next.

Enter database ID (DBSID) = DEV. Click on Next.

Click on Cancel to ignore system checks.

Error window will appear.
Click on Stop. Apply SAP note 970518 page 11 approx.

Edit control.xml in sapinst install directory: C:\Program
Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP. Search for “update
ORACHECK_PAR” and delete row beneath it: “row.createDb = false;”
Restart sapinst:
Select 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.
Click on Next.
Select Continue Old Installation. Click on OK.

Click on Cancel to ignore system checks.

Enter field ABAP schema: SAPSR3. The remainder of fields use defaults. Click on Next.
Enter password of DDIC in source system: vmwaresap7. Click on Next.

Enter location of 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
Review Input parameters. Click on Start.

Enter Solution Manager Key. Click on Continue.

The rename stops at the above screen with a notification window. Proceed as follows:
Update c:\orabrcopy\CONTROL.SQL – change all occurrences of TEM to DEV.
Rename c:\orabrcopy\initTEM.ora to initDEV.ora and change all occurrences of TEM to DEV.
Copy CONTROL.SQL to install directory: C:\Program
Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS-ABAP
Copy initDEV.ora to C:\oracle\DEV\102\database.
Delete entries in: c:\oracle\TEM\oraarch\; c:\oracle\TEM\saparch;
c:\oracle\TEM\saptrace\background; c:\oracle\TEM\saptrace\usertrace
Delete all three “TEM” control files: see old initTEM.ora for location of control files.
Note: the previous two steps could have been performed before creation of template.
In Windows Explorer, move all subdirectories in c:\oracle\TEM to c:\oracle\DEV.
Back to sapinst window, click on OK.

Accept defaults, click on Continue.

Click on 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 needs to be
applied.
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 OS
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:

• Initial state: sap_vm is up, CI instance is down, Oracle database is up, guest OS - Windows
Server 2003 SP1.
• Take snapshot – name “sap_vm snapshot1.”
• Shut down the Oracle database, patch OS to SP2, restart database and CI instance. In the
example here OS patch testing is simulated (alternatively it could be an SAP kernel patch
update or a SAP software update).
• 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 online development/testing type
activity).
• Take snapshot – name “sap_vm snapshot2.”
• Assume there are problems with SAP and the SP2 patch, so revert back to first snapshot
“sap_vm snapshot1” (Windows Server SP1).
• Verify status of virtual machine, restart CI instance and check that correction TEMK900002,
does not exist.
7.1. Take First Snapshot and Upgrade from Windows Server 2003 SP1
to SP2
Initially, guest OS is at patch level SP1 – see below.
On the VI client, right click “sap_vm” -> snapshot -> take snapshot.
Enter Name and Description. Click on Ok.
See progress in bottom pane.

Right click “sap_vm” -> Snapshot -> Snapshot Manager.
Shut down SAP completely, upgrade Guest OS Windows 2003 to SP2, restart SAP.
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 Second Snapshot and Rollback to First

Status of sap_vm:
• Windows Server 2003 SP2
• Database up
• CI Instance up
• Correction request, TEMK900002 created
Take snapshot: Right click “sap_vm” -> Snapshot -> Take Snapshot.
Select “sap_vm snapshot1,” click on Go to.

Click on Yes.
Check progress in bottom pane under “Recent Tasks” (of VI client).
Log in to guest OS and verify rollback to earlier snapshot – status of sap_vm:

• 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 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 will be lost when in the event of unsuccessful testing a
rollback is required to an earlier snapshot.
8. VMotion – Live Migration

The following test sequence is executed to validate VMotion:
• SAP is up and running in a virtual machine (sap_vm) on ESX Server host vega7063. Note:
these tests were carried out on the original virtual machine, sap_vm, before it was used
to create the template.
• Start SGEN process in SAP. This is the ABAP code generation utility that consumes CPU and
database I/O.
• Check the following monitoring tools to validate load and activity: VI client CPU charts; SAP
transactions SM50 (process monitor), SM37 (batch job monitor).
• Migrate sap_vm from ESX Server host vega7063 to vega7062.
• Check monitoring tools for load and activity.
• Perform SAP license check using the “saplicense” utility.
• Migrate sap_vm from vega7062 back to vega7063.
• Check monitoring tools for load and activity.
• Perform SAP license check using the “saplicense” utility.”
• Run SAP transaction SM21 (system logs) to verify no disconnections in SAP during the
migrations.
VMotion requirements:
• Both ESX Server hosts have compatible CPUs (same server types).
• Both ESX Server hosts are connected to a virtual switch assigned for VMotion (VMotion feature
enabled).
• Both ESX Server 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 Server hosts.
VMotion resource map displays the requirements: log in to VI client, select “sap_vm” -> tab “Maps.”
Current status: sap_vm running on ESX Server host vega7063.
8.1. Submit SAP Batch Workload

A batch workload is executed in SAP and monitoring tools (CPU charts in VI client and SAP
transactions SM50 and SM37) verify that load/activity has started on ESX Server host vega7063.
Log in to SAP using SAP UI (SAPGUI). Proceed to transaction SGEN.
Select Generate All Objects of Selected…, click on Continue.
Select EA-APPL, click on Continue.
Select "vega7066_TEM_00," click on Continue.

Click on Start Job Immediately.
Proceed to transaction SM37, to see job has started and is active.

Wait about five minutes and proceed to transaction SM50 to view the SAP processes.
View CPU usage on vega7063 (through the VI client).

8.2. Migrate Virtual Machine from vega7063 to vega7062

The virtual machine, sap_vm, is live-migrated to the other ESX Server host:
• CPU performance charts in the VI client show:
o An initial CPU spike on the source host vega7063 after the migration is started.
o CPU utilization on source host vega7063 drops from 50%; CPU on target host
vega7062 rises to 50%.
• SAP transactions SM37 and SM50 verify SAP activity is uninterrupted after the migration.
• After migration, when the virtual machine is running on vega7062, an SAP license check is
executed verifying license is OK.
On the VI client right click “sap_vm,” select Migrate.
Select 156.153.117.62. Click on Next.

Click on Next.
Click on Next.
Click on Finish.
VMotion progress shown in bottom pane – see below.
CPU utilization on vega7063 spikes and then drops to zero (time 10:57, see below).
CPU
CPU utilization on vega7062 increases to about 50% (time 10:57, see below).
While the virtual machine is running on ESX Server host vega7062, execute a remote desktop
session to the virtual machine and verify the SAP license using the SAP license program
“saplicense.”
Verify SAP job still running in SM50 and SM37.

8.3. Migrate 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:
o A CPU spike on the source host vega7062 after the migration has started.
o CPU utilization on source host vega7062 drops from 50% to zero; CPU on target host
vega7063 rises to 50%.
o CPU in the virtual machine is near 100% and drops to zero for about a minute during
the migrations.
• SAP transactions SM37 and SM50 verify SAP activity is uninterrupted after the migration.
• After migration, when the virtual machine is running on vega7063, an SAP license check is
executed verifying 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 indicate no process interruptions or disconnections (normally any
terminations in SAP can be seen in SM21).
On the VI client right click “sap_vm”, select Migrate and follow the same mouse clicks for the
migration as shown in screenshots above (target host is vega7063 / 156.153.117.63). Wait a few
minutes for the migration to complete. CPU utilization rises to about 50% on vega7063 (time
11:10, see below).
CPU utilization on vega7062 spikes and then drops to zero (time 11:10, see below).
CPU utilization in the virtual machine, sap_vm, is near 100%, but drops to zero for about one
minute during the two live migrations (approximate times 10.56 and 11:09, see below).
Execute a remote desktop session to the virtual machine (on vega7063) and verify no change in
the SAP license.
Verify SAP processes are still running (uninterrupted) by way of transactions SM37 and SM50.
SAP system log, transaction SM21, shows no disconnections in the timeframe from 10:40 – 11:20,
period of testing VMotion – see below.
Click on Reread system log.

9. VMotion – Cold Migration

This scenario demonstrates 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 Server host has local storage of about 120 GB.
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.
Power off “sap_vm.”
Right click “sap_vm” -> Migrate.

Select 156.153.117.63, click on Next.
Click on Next.
Select Move virtual machine configuration files and virtual disks.
Select datastore “storage1” – this is local storage on vega7063.
Click on Next.
Click Finish.
View progress in “Recent tasks” pane at bottom - see below.
The storage relocation lasted about 50 minutes. After migration sap_vm is up and running on local
datastore, storage1.
10. High Availability

The HA test is executed as follows:
• SAP is up and running in sap_vm, on ESX Server host vega7063.
• A cluster is created in the VI client inventory pane and both ESX Server hosts are assigned to
the cluster. This automatically configures the HA feature.
• Host vega7063 is rebooted to simulate a crash.
• sap_vm restarts on vega7062.
• SAP needs to be manually restarted.
VMware HA requirements are:

• Each host in the cluster has access to the virtual machine files (through shared storage).
• VMotion requirements (listed in the VMotion section above) should be met.
• Each ESX Server 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 1 show the DNS configuration.
Right click HP datacenter and select New Cluster.
Assign name “HA Cluster”, select VMware HA, click on Next.

Accept defaults, click on Next.
Click on Finish.
Drag and drop the ESX Server hosts into HA Cluster (in the left pane). Select HA Cluster and select
Task and Events tab to view progress of the HA configuration.
sap_vm running on vega7063.

Reboot vega7063 to simulate a failure: right click 156.153.117.63 --> Reboot.
Click Yes on the warning, type a reason for reboot, and click on OK.
View the event log during the “failure” of vega7063: Select “HA Cluster” in the inventory pane, click
on Tasks & Events tab, click Events, click Show all entries drop down list, select Show Cluster
Entries.
sap_vm comes up on vega7062.
Manually start up SAP in sap_vm.

11. Appendix 1 – ESX Server Configuration

Screenshots
The following screenshots show a summary of the hardware and CPU of the ESX Server hosts.
The following screenshots show the networking characteristics of both ESX Server installations.
12. Appendix 2 - SAP on VMware Deployment Tips /

Best Practice Guidelines
This appendix outlines some best practice guidelines for deploying SAP software on the VMware
platform. The content is not specifically based upon the tests described in this guide but upon
several tests that have been conducted within VMware. Also consult SAP note 1056052 – “VMware
ESX Server 3.0 configuration guideline.”
Generally no SAP specific settings exist within ESX Server. For best performance the following best
practices are recommended:
• Use the latest processor generations (Core2duo from Intel Xeon 51xx, 53xx, Rev. E/F AMD), due
to their enhanced support for virtualization.
• It is recommended to start a deployment with the smallest number of vCPUs needed (e.g. one
or two instead of four). This provides more flexibility and better load balancing over the
environment. It is easily possible to add additional vCPUs at a later point in time if needed.
• Follow SAP’s rules for setting up file systems for the database install. Distribute database files
over different disks. Separate log and database files. Use at least two separate VMFS (VMware
Filesystem) volumes to create the Virtual Disks.
• Do not over commit memory! VMware allows more virtual memory to be assigned to virtual
machines than the physical memory available on the host. Overcommitting is not
recommended with SAP as SAP allocates memory permanently and does not release it again.
To enforce this policy, set the “Memory Reservation” to the amount of memory configured for
the virtual machine. This ensures that the virtual machine running SAP will always have the full
amount of memory available. The same applies to the “CPU Reservation,” but this is only
recommended in case of performance problems, because the reserved resources are not
available to other virtual machines.
• Installation of VMware Tools is mandatory to avoid time conflicts. It is also recommended to
use NTP (Network Time Protocol) on the ESX Server host.
• Choose fixed/static memory allocation when using Microsoft SQL Server as the database. This
will avoid the allocation overhead of dynamic memory allocation. SQL Server has two basic
administrative options that control how much memory is used by the program: dynamic and
static allocation. Dynamic allocation allows the administrator to declare a range of memory
sizes; SQL Server can allocate up to the maximum amount of memory allowed for its use, and
(in theory) releases memory when not in use. Static allocation creates a fixed-memory space
for SQL Server to work with, no more, no less.
In regards to all other aspects, a virtual machine can be treated like any other host. Follow the
Installation and tuning guidelines from SAP for best results.
Further documentation can be found in these locations:
o Performance tuning Best Practices for ESX Server
http://www.vmware.com/vmtn/resources/707
o Using VMware Infrastructure for Backup and Restore
o Timekeeping in VMware virtual machines
13. Appendix 3 – 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 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 with HP c-class blades and SAP performance visit 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 6 individual gigabit network ports. As such, the enclosure
should be outfitted with a minimum of 3 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 fibre 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.
Figures 13-1 and 13-2 below depict the network switch configuration and enclosure configuration
for the servers used in the creation of this deployment guide. Further HP documentation can be
found in these locations:
HP VMware Server Virtualization

www.hp.com/go/vmware
HP reference configuration for virtualization: HP ProLiant c-Class half-height servers and VMware
Infrastructure 3
http://h71019.www7.hp.com/ActiveAnswers/cache/421308-0-0-0-121.html
Planning a VMware Virtual Infrastructure with HP ProLiant servers, storage, and management
Deploying a VMware Virtual Infrastructure with HP ProLiant servers, storage, and management
Figure 13-1: Network switch configuration for SAP deployment on VMware Infrastructure
Figure 13-2: Enclosure configuration for SAP deployment on VMware Infrastructure

VMware, Inc3401 Hillview Ave Palo Alto, CA 94304 USA

Tel 650-427-5000 Fax 650-427-5001 www.vmware.com
© 2007 VMware, Inc. All rights reserved. Protected by one or more of U.S. Patent Nos. 6,397,242, 6,496,847,
6,704,925, 6,711,672, 6,725,289, 6,735,601, 6,785,886, 6,789,156, 6,795,966, 6,880,022, 6,961,941, 6,961,806,
6,944,699, 7,069,413; 7,082,598 and 7,089,377; patents pending.

VMware SAP Software Solutions Deployment Guide

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

VMware SAP Software Solutions Deployment Guide

Caricato da

Copyright:

Formati disponibili

VMware White Paper VMware and SAP Software Solutions Deployment Guide

VMware and SAP Software Solutions

Note from the Author

1.1. SAP Platform Overview

1.2. VMware® Infrastructure 3 Software Suite

Figure 1-1. VMware Infrastructure

VMware Infrastructure 3 is the next generation of industry-leading infrastructure software that

1.2.1. VMware ESX Server

Figure 1-2. VMware Infrastructure 3 - ESX Server

1.2.2. VMware® VirtualCenter

Figure 1-3. VMware VirtualCenter Management Server

1.3. HP Hardware Overview

1.4. SAP Datacenter Benefits

1.4.1. Server Containment

Key benefits of using VMware Infrastructure for server containment:

Key benefits of using VMware Infrastructure to achieve high availability:

• Employ a time-efficient mechanism to restart an SAP system within minutes on an available

1.4.3. Rapid Provisioning

Key benefits of using VMware Infrastructure for provisioning:

2. Deployment Approach Summary

2.1. Install SAP in Virtual Machine

Install SAP in Virtual Machine

Create Golden Image

Deploy New SAP system from Template

2.4. VMotion – Live Migration

2.5. VMotion – Cold Migration

2.6. High Availability

2.7. SAP on VMware Deployment Tips / Best Practice Guidelines

3.2. Logical Architecture

Figure 3-1: Logical architecture for SAP software on VMware Infrastructure

3.3. Physical Architecture

Figure 3-2: Physical architecture for SAP software on VMware Infrastructure

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

ESX Server Datacenter name HP

Virtual Machine (VM) name sap_vm

VM storage size 115 GB

VM Windows guest OS drive C:\

VM Windows guest OS host name vega7066

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

Datastore name VMFS03 (1 x 600GB shared VMFS

ESX server host names vega7062

Cloned VM Windows guest OS host name vega7067

4.2. Create Virtual Machine

Select 156.153.117.63. Right click -> New Virtual Machine.

Select Typical, click on Next.

Enter name: sap_vm, select HP, click on Next.

Select shared storage, datastore = VNFS03. Click on Next.

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

Number of virtual processors: 2. Click on Next.

Enter memory = 3000. Click on Next.

Number of NICs = 1, select network = Production. Click on Next.

Enter disk size = 115. Click on Next.

4.3. Guest OS Install

Select “sap_vm,” right click -> Edit Settings.

Select “Console” tab.

Select “sap_vm,” right click -> Power On.

Select A (Enterprise Edition), <enter>.

Select “sap_vm,” right mouse click -> Install VMware Tools.

4.4. SAP Install

The following steps are executed:

5.1. Run SAP orabrcopy Tool

ORACLE instance shut down.

5.2. Uninstall CI Instance