always onvirtualizedsapsystemwithhpandvmware

8/6/2019 Always OnVirtualizedSAPSystemwithHPandVMware

1/17

Always-on virtualized SAP systems with HPStorageWorks P4000 G2 storage systemsfor VMware vSphere 4

Technical white paper

Table of contents

Executive summary ............................................................................................................................... 2Introduction ......................................................................................................................................... 2

Storage overview ............................................................................................................................. 3High availability for SAP systems ........................................................................................................... 4

Solution objectives ........................................................................................................................... 4Multi-site cluster with FT and HA ........................................................................................................ 5FT overview ..................................................................................................................................... 6Selecting an appropriate solution ....................................................................................................... 6

Validating an Always-on solution ........................................................................................................... 7Solution options ............................................................................................................................... 7

Always-on failover testing.................................................................................................................. 8FT performance considerations ............................................................................................................ 10

Optimizing FT-protected VM performance ......................................................................................... 10Conclusion ........................................................................................................................................ 11

Appendix: Setting up the solution ........................................................................................................ 12Qualified hardware and software .................................................................................................... 12Configuring storage resources ......................................................................................................... 13Configuring vSphere resources ........................................................................................................ 14Configuring SAP systems ................................................................................................................. 15

For more information .......................................................................................................................... 16


2/17

2

Executive summary

This white paper, one in a series on the virtualization of an SAP environment through a combinationof HP storage systems, HP ProLiant servers, and VMware virtualization technology, focuses ondeploying advanced VMware vSphere functionality High Availability (HA) and Fault Tolerance (FT) so that virtualized SAP systems can take full advantage of the disaster-tolerance delivered by HPStorageWorks P4000 G2 SAN storage.

HP has developed and validated a disaster-tolerant SAP solution featuring HA and FT, in conjunctionwith automatic, synchronous SAN storage replication. This solution was based on best practices forHP Converged Infrastructure and published maximum configurations for a vSphere environment.

The combination of P4000 G2 SAN storage and HP ProLiant servers allows a disaster-tolerant SAPsystem to scale1 from an entry-level P4000 Virtual SAN Appliance Software (VSA) to P4300 G2 SASStarter SAN and enterprise-class P4500 G2 SAN, and from a single HP ProLiant DL server to a multi-blade HP BladeSystem configuration, until the resource limits of FT-protected virtual machines (VMs)are reached.

Target audience:This paper is intended for SAP administrators wishing to learn more aboutvirtualizing and protecting SAP systems using vSphere software in conjunction with an HP hardwareplatform. In general, however, the reader does not require experience with SAP software.

Testing performed in September 2010 is described.

Introduction

The combination of HP storage systems, HP servers, and SAP software in a VMware virtualizedenvironment has been described in the following series of HP white papers:

SAP system virtualization with HP ProLiant servers an introductionThis paper highlights virtualization as a business enabler and provides detailed information on howto use HP offerings (such as HP ProLiant servers, shared HP StorageWorks SAN storage, and HP

Virtual Connect FlexFabric networking) to virtualize an SAP landscape with vSphere 4. In addition,guidelines for sizing a virtualized SAP landscape are presented.

SAP system virtualization with HP ProLiant servers total cost of ownership and return oninvestment with VMware vSphere

This paper outlines the business case for virtualization, describing economic, environmental, andtechnological drivers. It also reviews a total cost of ownership (TCO) study concerning thevirtualization of a legacy environment and outlines projected cost savings for the first three years ofoperation.

HP LeftHand P4000 iSCSI SAN for SAP landscapes with HP BladeSystem and HP ProCurve configuration and performance

This paper in conjunction with the VMware paper, SAP Solutions on VMware vSphere 4 - Best

Practice Guidelines outlines the capabilities and benefits of a P4000 G2 iSCSI SAN andprovides sample configurations for environments featuring bare-metal and virtualized SAP servers.Performance testing validated that the I/O performance delivered by these configurations satisfiesSAP system requirements.

The solution described in this paper was designed to enhance the availability of an SAP systemprotected by HA and FT by deploying a P4000 G2 SAN to provide multi-site storage. This solution issuitable for larger installations where many virtualized SAP systems can be deployed.

1 Following HP sizing guidelines for virtualized SAP systems
http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8267ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8267ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8267ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8267ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8267ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8309ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-8267ENW&cc=us&lc=en%20


3/17

3

HP validated a disaster-tolerant SAP NetWeaver 7.0 system with Microsoft SQL Server 2008 onMicrosoft Windows Server 2008.

Storage overview

Most SAP production systems need a high level of availability along with reasonable levels ofperformance. Thus, a suitable storage system is required whether there are thousands of interactiveusers connecting to a terabyte-sized SAP database or fewer than a hundred users connecting to adatabase that only contains several hundred gigabytes.

Figure 1 outlines three sample configurations ranging from entry level software-only P4000 VSA to asolution featuring P4300 G2 Starter SAN with ProLiant DL model servers and one featuring a P4500G2 Multi-site SAN with HP BladeSystem. Here the server blades can scale to accommodate a largenumber of virtualized SAP systems.

Figure 1 HP StorageWorks P4000 G2 sample configurations for SAP landscapes

Attached to an HP BladeSystem, the HP StorageWorks P4500 G2 SAN is optimized to deliverscalability to a multi-blade environment supporting a predominantly Enterprise Resource Planning(ERP) random-access I/O workload. Features include:

Highly-dense storage that can dynamically scale performance and capacity as the infrastructureexpands

Clustered architecture that promotes high availability with no single point of failure (SPOF). Simplicity and performance are enhanced by high-speed storage paths, dense disk spindle counts,

and no external storage switching

All P4000 G2 SANs are driven by built-in SAN/iQ software with features that include storageclustering, thin provisioning, snapshots, remote copy, and Network RAID for high availability.


4/17

4

High availability for SAP systems

SAP provides a range of enterprise software applications and business solutions that can manage andrun your business. To help provide the continuous availability these mission-critical system needs, SAPhas developed a scalable, multi-tier architecture that can be protected either by scaling out (byadding NetWeaver application servers, for example) or by clustering and failover solutions thatsafeguard SPOFs within the architecture.

The VMware papers SAP Solutions on VMware vSphere 4 - Best Practice Guidelines and SAPSolutions on VMware vSphere High Availability" outline the following options to optimize SAP systemavailability:

Windows clustering and monitoring at the application-level, which enhances the visibility ofapplication status but is complex to set up and maintain

High-availability at the VM-level, which is simpler to implement but does not provide high-levelapplication monitoring

Solution objectives

The objective of the high-availability solution described in this paper is to provide high availably for

an SAP system at the VM level by eliminating the following SPOFs that have been identified in theSAP architecture:

SAP databaseWhen each SAP work process starts, it makes a private connection to the database. If thisconnection is interrupted due the failure of the database instance, the work process attempts to setup a new connection and changes to "database reconnect" state until the instance is restored.

User sessions engaged in database activity receive SQL error messages; however, logged-onsessions are preserved on the application server.

SAP Message ServiceMessage Service is used to exchange and regulate messages between SAP instances. For example,it schedules batch jobs and determines to which instance a user will log on.

SAP Enqueue ServiceEnqueue Service manages the locking of business objects at the SAP transaction level.

Locks are set in a lock table that is stored in the shared memory of the host on which EnqueueService is running.

Failure of this service would have a considerable effect on the system because all transactionscontaining locks would have to be rolled back; in addition, any SAP updates being processedwould fail and, depending on business requirements, may have to be manually applied via SAPtransaction SM13 once Enqueue Service has been restored.

You can protect the database by allowing the instance to failover to another physical machine in theevent of a failure.

In addition, isolating Message and Enqueue Services from the SAP Central Instance (CI) helps addressthe high-availability requirements of these particular SPOFs. The SAP Central Services (SCS)component is less cumbersome than the CI and, if necessary, can be restarted much more quicklyafter a failure.
http://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdf


5/17


6/17

6

HA continuously monitors all vSphere hosts in the cluster and, in the event of a host failure, migratesaffected VMs and restarts them on surviving hosts.

FT gives you the ability to run two VMs (primary and secondary) simultaneously, in lockstep3. If theprimary VM were to fail, the secondary VM would immediately take over, becoming the new primary

VM and continuing processing at the point the original VM stopped. A new secondary VM is thencreated on the next available vSphere host.

In the solution shown in Figure 2, FT enables the transparent failover of an SCS instance.

NoteThe combination of HA and FT can be used to address SPOFs in avirtualized SAP environment. For more information, refer to the VMwarewhite paper, SAP Solutions on VMware vSphere: High Availability.

An HP P4000 G2 multi-site SAN cluster extends the protection delivered by HA (vSphere host-level)and FT (VM-level) to the storage-level. By combining the three components HA, FT, and a P4000 G2multi-site SAN cluster an entire installation at one site can be protected by a second site and viceversa.

FT overviewFT establishes and maintains an active secondary VM that runs in lockstep with the primary VM.

Although the secondary VM resides on a different vSphere host, it executes exactly the samesequence of instructions as the primary and receives the same inputs; their states are identical. Shouldthe primary fail, the secondary is ready to take over at any time, without data loss or interruption ofservice. To summarize, both VMs are managed as a single unit but run on different physical hosts.

Currently, FT only supports single-vCPU VMs, making this feature a viable solution for lightercomponents of the SAP architecture, such as SCS.

Selecting an appropriate solution

While HA and FT can provide protection for hardware SPOFs, they cannot monitor the health of theSCS and database instances. If you need application-level monitoring and automatic failover, thenyou should consider using third-party clustering software.

Given that you have a range of design options for creating a highly available SAP installation onVMware virtual infrastructure, your final choice should depend on your specific business and sizingrequirements and service level agreements (SLAs).

For example, if the size of your SAP system is such that all locking and messaging activities can besatisfied by a single x86 processor core, then you can use FT to provide zero-downtime protection forSCS against hardware failure4. This solution would not require a complex clustered environmentfeaturing Enqueue Service replication. For larger systems, an in-house performance test may be

required in order to characterize suitability.

3 Using what VMware refers to as vLockstep technology4 Assuming SCS is installed in a VM wi th a single vCPU
http://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdf


7/17

7

Validating an Always-on solution

As described earlier, there are multiple options for eliminating the SPOFs from an SAP system runningon vSphere. This section describes two such options and then details how HP validated a multi-site,multiple VM solution that has no SPOF.

Solution options

HP focused on Always-on solutions configured with HA and FT. The options described below are

designed to balance complexity, cost, and SAP application availability.

Single VM

A two-tier SAP environment with the CI and database server deployed on a single VM is the simplestway to virtualize an SAP system. According toVMware, this single-VM solution can scale to as manyas eight vCPUs (as shown in Table 1) and, thus, is able to support a reasonable number of SAPtransactions.

Table 1. Configuration maximums

Item Maximum

VM

vCPUs per VM 8

RAM per VM 255 GB

FT

vCPUs per FT VM 1

RAM per FT VM 64 GB

vDisks per FT VM 16

The single-VM approach allows an SAP system to be protected by HA. However, using FT to protectEnqueue and Message Services would impose a limit of a single vCPU on the VM, which would, inturn, restrict the number of transactions supported. Thus, for larger workloads, a differentconfiguration is required.

Multiple VMs

To enhance scalability, you can use a three-tier SAP environment, separating the database from theCI. Moreover, since NetWeaver architecture would then allow you to separate Enqueue and MessageServices from the CI via a lightweight SCS server, you can protect this SPOF by enabling FT, asshown inFigure 2 Simplified view of a multi-site, replicated SAP system protected by HA and FT.

The FT-protected VM is configured with a single vCPU and a theoretical maximum of 64 GB ofmemory.

The database server is protected by HA, allowing it to be configured with up to eight vCPUs and atheoretical maximum of 255 GB of memory.
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf


8/17

8

Always-on failover testing

HP validated the multi-site, multiple VM configuration in the following scenarios, which effectivelyculminated in the loss of the entire Site A:

Loss of the SCS VM at Site A Loss of the vSphere host at Site A Loss of storage at Site A

Figure 3 Overview of the tested configuration, showing the loss of an entire site with minimal interruption to SAP transactionprocessing

Losing the FT-protected VM

While SAP transactions were being processed, HP manually powered off the primary SCS VM, which

had been running at Site A. However, there was a secondary SCS VM running at Site B; both SCSVMs had access to the same iSCSI storage, which was protected by the P4000 G2 multi -site SANdescribed inAppendix: Setting up the solution.

As a result of the simulated VM failure, the SCS VM at Site B became the primary. Since there hadbeen no disruption to the database VM, FT protection allowed SAP transactions to continue runningseamlessly.


9/17

9

Losing the vSphere host

Figure 4 shows what happened when the vSphere host at Site A (172.16.2.18) was powered off.

SAP dialog and SCS instances are both running on the host at Site B (172.16.2.19); however, theSCS VM is showing an alert because it cannot be protected by FT until you provide a secondary VMat some other site.

The database VM, which is protected by HA, is in the process of failing over to Site B.

Figure 4 The SCS VM is running at Site B; following the failure of the host at Site A, the DB VM is in the process of failing5over

After the HA failover, the database VM automatically re-started at Site B, as shown in Figure 5.

Because they were protected by FT, Enqueue and Message Services remained active despite thefailure of the SCS VM at Site A. As a result, SAP transactions that had been halted by the failure ofthe database VM at Site A were able to continue processing when it re-started at Site B.

Figure 5 SAP transaction processing continued after the database VM failed over to the surviving host at Site B6

5 Refer toAppendix: Setting up the solutionfor details on vSphere resources6 Once the second VMware cluster member is back online the FT protected SCS secondary is spawned and the alert status from figure 4 gets

cleared.


10/17

10

Losing storage

When power to the P4000 G2 SAN storage nodes at Site A was abruptly cut, all VMs now at SiteB were able to continue running, thanks to synchronous storage replication between the sites.

After noting that storage at Site A was no longer available, SAN/iQ Failover Manager functionalitywas able to maintain quorum7. Storage at Site B was still operational and was able to process I/Osfor the VMs; however, the loss of a pair of storage nodes led to some degradation of storageperformance.

NoteSince the failed vSphere host at Site A had also been running a Windowsdomain controller (SAP-FT-DC) and Domain Name System (DNS) services,the failure of storage at this site constituted a failure of the entire site.For convenience, the domain controller and DNS services in the testedenvironment were protected by HA.

The P4000 SAN/iQ central management console (CMC) reported that Site As storage was offline,as shown in Figure 6.

Figure 6 Due to the protection provided by Network RAID, a storage failure at Site A caused no interruption to storageservices

After completing these three test cases, when HP restored power to the affected VM, vSphere host, orstorage nodes, Site A came back online with minimal effort.

FT performance considerations

Protecting a lightweight SCS instance with FT allows a production SAP system to scale to supporthigher transaction loads until the resource limits of the FT-protected VM are reached.

Optimizing FT-protected VM performance

NoteTo supplement the information provided in this section, refer to the VMwarewhite paper, Performance Best Practices for VMware vSphere 4.0.

7 In the tested environment there was one Failover Manager (vote) for each of the four storage nodes. A Virtual Manager, the fifth vote, wasdeployed at Site B.
http://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdf


11/17

11

Inherent resource requirements

Enabling FT inherently requires additional resources because the secondary VM uses as much CPUand memory as the primary.

If the secondary VM lags too far behind the primary, which may happen, for example, if the primaryVM is CPU-bound and the secondary VM is not receiving enough CPU cycles, the hypervisor mayslow the primary to allow the secondary to catch up.

Optimizing network traffic

When FT is first enabled, the live migration required to spawn a secondary instance may temporarilysaturate the associated VMware vMotion network link. If this link is also being used for otheroperations, such as FT logging, the performance of those operations can be impacted. Thus, youshould use separate, dedicated network interface cards (NICs) for FT logging and vMotion traffic.

FT-protected VMs that receive large amounts of network traffic or perform lots of disk reads can createa significant load on the NIC specified for logging traffic. In this case, you should implement adedicated SCS VM that is separate from the database server.

To avoid saturating the network link used for FT logging traffic, limit the number of FT -protected VMson each host or limit the disk-read and network-receive bandwidths of those VMs. Make sure thatlogging traffic is carried by at least a Gigabit-rated NIC.

Multiple FT-protected instances

If you are implementing multiple FT-protected SCS instances, distribute the primary VMs acrossavailable vSphere hosts. By spreading out the FT logging traffic, which is asymmetric (that is, themajority flowing from the primary VM to the secondary), you avoid saturating the logging NIC.

Conclusion

If you are running an SAP system on VMware software, you can successfully utilize HA to help satisfythe high-availability requirements of mission-critical SAP environments. FT can further enhanceavailability by protecting SPOFs such as the SCS instance.

Combining FT-protection for the SCS with HA-protection for the SAP database helps create an SAPsystem with no SPOFs. Adding a P4000 G2 SAN to provide disaster-tolerant, replicated storage canfurther enhance data and application availability without introducing excessive levels of complexity.

Since it is critical to understand how to set up and configure the underlying infrastructure, theappendix to this white paper outlines the setup of a VMware-protected SAP system that incorporates aP4000 G2 SAN multi-site architecture.


12/17

12

Appendix: Setting up the solution

This appendix provides information on installing and setting up the HP hardware and softwarerequired to deploy a disaster-tolerant SAP system protected by VMware HA and FT, and synchronousSAN replication.

For the tested NetWeaver 7.0 installation, HP used two HP ProLiant BL460c G6 blades with an HPStorageWorks P4000 G2 SAN solution providing back-end storage.

Qualified hardware and software

Table 2 lists hardware and software components that have been used by HP to verify the solution. Thesolution is expected to work on every SAP certified HP server model in combination with any P4000storage system.

HP configured these components over two sites, as shown inFigure 2 Simplified view of a multi-site,replicated SAP system protected by HA and FT.

Table 2 Hardware and software components

Server-side /Network Shared storage

Hardware

vSphere hosts

Two HP ProLiant BL460c G6 server blades, eachconfigured with:

72 GB RAM Two 15,000 rpm SAS hard drives One NC373m Dual Port Multifunction 1Gb NIC)Two Ethernet switches

Four HP StorageWorks P4300 storage nodes, eachconfigured with:

2 GB cache Eight SAS hard drives (450 GB, 15,000 rpm)

Software

vSphere hosts

On each BL460c G6 server blade:

VMware ESXi 4.0.0VMs

Windows Server 2008 NetWeaver 7.0

HP StorageWorks P4000 SAN/iQ 8.5


13/17

13

Configuring storage resources

The P4300 G2 SAN cluster was set up for usage with SAP as described in the HP white paper, HPLeftHand P4000 iSCSI SAN for SAP landscapes with HP BladeSystem and HP ProCurve configuration and performance.

The SAN was configured over two sites, with two storage nodes at each, as shown in layout consistsof having the P4300 storage nodes stretched across two sites as shown inFigure 2 Simplified viewof a multi-site, replicated SAP system protected by HA and FT. Highlights of this implementation were

as follows: NICs in the P4300 storage nodes were teamed to support advanced load balancing SAN traffic ran on a dedicated network The CMC and Failover Manager were given access to the network switches, enhancing stability

and allowing the environment to be better managed

Equal numbers (two) of storage nodes were configured at each site, allowing SAN/iQ to supportthe automatic, synchronous mirroring of data between these sites

Best practices

As a best practice for a storage cluster that spans multiple sites, you should run the same number of

Failover Managers (quorum votes) at each site. To provide an odd number of votes in a cluster thatspans two sites, run a Failover Manager at a third site, on a physical or logical server that is not partof the cluster.

Since a third site was not used to test this disaster-tolerant SAP solution, a Virtual Manager wasdeployed at Site B (as shown in Figure 7).

Figure 7 P4300 G2 multi-site SAN configuration viewed in the CMC

The tested P4300 G2 SAN complied with best practices presented in the HP white paper, RunningVMware vSphere 4 on HP P4000 SAN Solutions.
http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-4478ENW&cc=us&lc=en


14/17

14

Configuring vSphere resources

In this example, HP has set up a two-node vSphere 4 cluster, as shown in 8.

Figure 8 Tested cluster, shown in a vSphere client

While the SAP database server (SAP-FT-DB) and application dialog servers (SAP-FT-DI-1 and SAP-FT-DI-2,) have been configured for HA, the characteristics of the SAP SCS instance like single vCPU andFT protection (dark blue icon) are marked with red circles in Figure 9.

Figure 9 FT-protected SCS instance

To protect a VM with FT, simply right-click its icon in the vSphere client, which allows you to enablethe FT feature and spawn a secondary instance on a different vSphere cluster member.


15/17

15

Configuring SAP systems

Figure 10 shows the SAP systems deployed in this disaster-tolerant solution.

Figure 10 SAP Management Console (sapmmc) showing the SAP system configuration

For more information on how the tested SAP systems were installed, refer to the SAP document, SAPInstallation Guide: NetWeaver 7.0 ABAP on Windows: MS SQL Server, available athttp://service.sap.com/instguides.
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguides


16/17

For more information

HP

Best practices for deploying VMwarevSphere 4 with VMware High Availabilityand Fault Tolerance on HP P4500 Multi-Site SAN cluster

http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA0-4385ENW&cc=us&lc=en

Running VMware vSphere 4 on HPP4000 SAN Solutions

http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=en

Other solution white papers, forums, andwebinars

www.hp.com/solutions/activeanswers

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

HP StorageWorks P4000 G2 SANsolutions

HP StorageWorks P4000 Virtual SAN

Appliance Software

www.hp.com/go/p4000

http://h18006.www1.hp.com/products/storage/softw

are/vsa/index.html?jumpid=reg_R1002_USEN

VMware

VMware Fault ToleranceRecommendations and Considerations on

VMware vSphere 4

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

SAP Solutions on VMware vSphere 4 -Best Practice Guidelines

http://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdf

Configuration maximums for VMware

vSphere 4.1

http://www.vmware.com/pdf/vsphere4/r41/vsp_41_c

onfig_max.pdf

SAP Solutions on VMware vSphere HighAvailability

http://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdf

Performance Best Practices for VMwarevSphere 4.0

http://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdf
http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA0-4385ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA0-4385ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=en%20http://www.hp.com/solutions/activeanswershttp://www.hp.com/solutions/activeanswershttp://www.hp.com/go/hpcfthttp://www.hp.com/go/hpcfthttp://www.hp.com/go/p4000http://www.hp.com/go/p4000http://h18006.www1.hp.com/products/storage/software/vsa/index.html?jumpid=reg_R1002_USENhttp://h18006.www1.hp.com/products/storage/software/vsa/index.html?jumpid=reg_R1002_USENhttp://h18006.www1.hp.com/products/storage/software/vsa/index.html?jumpid=reg_R1002_USENhttp://www.vmware.com/resources/techresources/10040http://www.vmware.com/resources/techresources/10040http://www.vmware.com/resources/techresources/10040http://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/files/pdf/SAP_vsphere_high_availability.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://vmware.com/files/pdf/SAP-Best-Practices-White-Paper-2009.pdfhttp://www.vmware.com/resources/techresources/10040http://www.vmware.com/resources/techresources/10040http://h18006.www1.hp.com/products/storage/software/vsa/index.html?jumpid=reg_R1002_USENhttp://h18006.www1.hp.com/products/storage/software/vsa/index.html?jumpid=reg_R1002_USENhttp://www.hp.com/go/p4000http://www.hp.com/go/hpcfthttp://www.hp.com/solutions/activeanswershttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-0261ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA0-4385ENW&cc=us&lc=en%20http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA0-4385ENW&cc=us&lc=en%20


17/17

SAP

SAP S- or C-user account required for thefollowing:

SAP Note 1409608 Virtualization onWindows

http://service.sap.com

Installation Guide: NetWeaver 7.0 ABAPon Windows: MS SQL Server

http://service.sap.com/instguides

To help us improve our documents, please provide feedback athttp://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.html.

Copyright 2010 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice.The only warranties for HP products and services are set forth in theexpress warranty statements accompanying such products and services.Nothing herein should be construed as constituting an additionalwarranty HP shall not be liable for technical or editorial errors oromissions contained herein.

Microsoft and Windows are U.S. registered trademarks of MicrosoftC ti
http://service.sap.com/http://service.sap.com/http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.htmlhttp://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.htmlhttp://www.hp.com/go/getconnectedhttp://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.htmlhttp://service.sap.com/instguideshttp://service.sap.com/

always onvirtualizedsapsystemwithhpandvmware

Documents