9. microsoft private cloud solution for sap landscape ... · web viewalthough many sap systems...

Further. Forward. Faster.

9. Microsoft Private Cloud Solution for SAP: Landscape DesignAuthorsCameron Gardiner, Microsoft Senior Program Manager – SAP

Technical ReviewersJuergen Thomas, Principal Lead Program ManagerHermann Daeubler, Microsoft Senior Program Manager – SAP

SummaryThis document provides guidance for customers and partners to deploy SAP on a Microsoft Private Cloud Solution for SAP. This chapter discusses Landscape Design

Landscape Design

Table of Contents

Table of Contents..........................................................................1 Summary..................................................................................2 Server Building Blocks..............................................................

2.1 MANDATORY HARDWARE CONFIGURATION...............................................................2.2 SAP 2 TIER CONFIGURATION................................................................................2.3 SAP 3 TIER CONFIGURATION................................................................................

3 Permitted VM Sizes...................................................................3.1 SMALL..............................................................................................................3.1.1 Target Use.........................................................................................63.1.2 VM Properties....................................................................................63.1.3 Database Sizing Guide (per SQL Server Instance).............................63.1.4 SAP Application Server Sizing Guide..................................................63.2 MEDIUM............................................................................................................3.2.1 Target Use.........................................................................................63.2.2 VM Properties....................................................................................63.2.3 Database Sizing Guide (per SQL Server Instance).............................63.2.4 SAP Application Server Sizing Guide..................................................63.3 LARGE..............................................................................................................3.3.1 Target Use.........................................................................................73.3.2 VM Properties....................................................................................73.3.3 Database Sizing Guide (per SQL Server Instance).............................73.3.4 SAP Application Server Sizing Guide..................................................73.4 EXTRA LARGE (SQL SERVER ONLY).......................................................................3.4.1 Target Use.........................................................................................73.4.2 VM Properties....................................................................................73.4.3 Database Sizing Guide (per SQL Server Instance).............................73.4.4 SAP Application Server Sizing Guide..................................................7

4 Sizing Calculations....................................................................4.1 SAP QUICKSIZER................................................................................................4.2 SIZING PROCESS.................................................................................................4.3 RAM BASED SIZING............................................................................................4.4 MICROSOFT PRIVATE CLOUD SOLUTION VM CALCULATOR.........................................

5 Network Configuration............................................................6 Storage Configuration.............................................................

6.1 ISCSI.............................................................................................................6.2 FIBRE CHANNEL (VHBA)....................................................................................6.3 FCOE.............................................................................................................6.4 SMB 3.0........................................................................................................

7 Appendix 1 – 4 Socket Configurations......................................

SAP on Microsoft Private Cloud Page of Created:

Landscape Design

8 Appendix 2 – Tested Network Cards.........................................9 Appendix 3 – Sample Bill of Materials.......................................


Landscape Design

1 Summary

Chapter 9 details Landscape Design – the process of mapping SAP Components and SAPS values onto the Microsoft Private Cloud Solution for SAP.

Smaller customers are encouraged to adopt simple 2 Tier SAP solutions. These are very simple to setup and install. If systems outgrow 2 Tier configuration in terms of user workload or HA/DR required they can be changed to 3 Tier via the SAP homogeneous system copy process.

The process of consolidating SAP Application servers onto a single VM and consolidating smaller Database Named Instances onto a single VM requires tuning and adjustment. Customers and Partners are encouraged to review the sample landscape diagram in this document. This can be adapted and modified. The VM calculator Excel spreadsheet allows a customer to quickly and easily check if too many or too few system resources are allocated.

This reference architecture is designed and tested as a solution to consolidate an entire SAP landscape including all components such ECC, BW, SRM, CRM, Solution Manager etc. The recommendations and restrictions in these documents are developed to deliver stable high performance solutions for consolidated landscapes. The guidance in this whitepaper may also be useful for customers wishing to run only one SAP component on Hyper-V, though this document does not specifically cover such a scenario. Hyper-V 3.0 is an excellent consolidation platform for an entire SAP landscape.

The high level process is detailed below:

1. SAP Business Solution Architect prepares a list SAP Components require to meet business requirements

2. Complete the SAP Quicksizer to calculation SAPS values 3. Determine which SAP Components require Development, QAS, Production

landscapes4. Fully review Note 1612283 - Hardware Configuration Standards and Guidance5. Determine how many Development, QAS and Production Virtual Machines are

required6. Determine the size of each VM: Small, Medium, Large or Extra Large7. Determine which Deployment Scenario is required (Scenario 1, 2, 3 or 4)8. Use the Virtual Machine Calculator to add up the total memory of all VMs and

automatically determine the number of cluster nodes required9. Round up this number to the nearest whole number and add one or two cluster

nodes as sizing buffer


https://service.sap.com/sap/support/notes/1612283

Landscape Design

2 Server Building BlocksSAP on Microsoft Private Cloud reference deployment is based on an exact hardware specification. Customers and Partners must follow the minimum hardware guidance.

2.1 Mandatory Hardware ConfigurationThe hardware configurations in this document have been prototyped in the lab and tested at customer sites. Customers and Partners are strongly advised to completely follow the guidance in these documents. The two most critical components that have been identified are (1) 10 Gigabit networking infrastructure (2) the requirement that each cluster node has 384GB. Deviating from these requirements does not save any significant amount of money and is extremely likely to lead to performance and stability problems. No testing has been performed on lower memory specifications and 1 Gigabit Ethernet is not tested.

Customers are advised not to deploy this consolidation solution on servers with less than 384GB or without 10 Gigabit Ethernet.

2.2 SAP 2 Tier Configuration When the Database and the SAP Application server are running on the same operating system image. Communication between the SAP application and the Database occurs via shared memory. 2 Tier systems are suitable for Development, Solution Manager or other small systems. SAP systems are vastly more scalable when running in 3 tier configurations.

2.3 SAP 3 Tier Configuration When the Database and one or more SAP Application server(s) are running on separate operating system images. Communication between the SAP application and the Database occurs via Network. Network is therefore critical for 3 Tier Configurations.10 Gigabit network with modern offload features eliminates latencies that previously existed in older generation Ethernet technologies. SAP 3 Tier systems running on Microsoft Private Cloud can scale up to >200,000 SAPS with >60,000 SAPS for SQL Server and 140,000 SAPS on the SAP application server layer


Landscape Design

3 Permitted VM SizesThe SAP on Microsoft Private Cloud Solution is build out of four defined VM configurations. The configurations, testing and guidance in this document are based on the four different VM sizes described below. It is strongly advised not to alter the VM sizes.

3.1 Small3.1.1 Target UseDevelopment systems, Solution Manager and very small test and production systems. Small config can also be used for ASCS clusters. This VM can be used for small production systems in 2 tier configuration (DB + SAP application server on the same operating system image). DB size up to 320GB with full PAGE compression. Small size VM can be used as a SAP application server

3.1.2 VM PropertiesSingle 10G network, 32GB RAM, 4 vCPU

3.1.3 Database Sizing Guide (per SQL Server Instance)SAP DB Layout: 4 datafiles, 1 x 5GB Log Tempdb Layout: 4 x 1GB datafiles, 1 x 1GB Log LUN: 5 x 20 to 100 GB LUN

3.1.4 SAP Application Server Sizing Guide SAP application server only storage is 1 x 120GB LUN for OS + SAP. This VM is capable of running 2 ABAP instances for small systems or non-production systems. Target PHYS_MEMSIZE = 16000

3.2 Medium3.2.1 Target UseMedium test and production systems. Medium VM can be used for both SQL Server and SAP application servers. Small to Medium size Production systems in 2 tier configurations. DB size up to 640GB with full PAGE compression

3.2.2 VM PropertiesDual 10G network, 128GB RAM, 8 vCPU

3.2.3 Database Sizing Guide (per SQL Server Instance)SAP DB Layout: 8 datafiles, 1x 80GB Log Tempdb Layout: 4x 1GB datafiles, 1x 1GB Log LUN: 5 x 50-200GB LUN

3.2.4 SAP Application Server Sizing Guide


Landscape Design

SAP application server only storage is 1 x 120GB LUN for OS + SAP. This VM is capable of running 4-6 ABAP instances. Target PHYS_MEMSIZE = 24000 - 32000

3.3 Large 3.3.1 Target UseLarge production SQL Server databases and consolidation of many SAP application servers. Medium size customers can deploy Production systems in 3 Tier configuration on this VM size. DB size up to 1TB with full PAGE compression in 3 Tier configuration

3.3.2 VM PropertiesDual 10G network, 192GB RAM, 16vCPU

3.3.3 Database Sizing Guide (per SQL Server Instance)SAP DB Layout: 16 datafiles, 1x 200GB Log Tempdb Layout: 4 x 1GB datafiles, 1x 1GB Log LUN: 5 x 100-400GB LUN

3.3.4 SAP Application Server Sizing Guide This VM configuration should not be used for SAP application servers

3.4 Extra Large (SQL Server Only)3.4.1 Target UseExtra large SQL Server use only. Not for SAP application servers. DB size up to >3TB 1 with full PAGE compression

3.4.2 VM PropertiesDual 10G network, HW max GB RAM (1TB max), HW max vCPU (64v CPU max)

3.4.3 Database Sizing Guide (per SQL Server Instance)SAP DB Layout: 16 datafiles, 1x 600GB Log Tempdb Layout: 4 x 1GB datafiles, 1x 1GB Log LUN: 8 x 100-1000GB LUN. Log LUN should be 1TB for very large and busy systems

3.4.4 SAP Application Server Sizing Guide This VM configuration should not be used for SAP application servers

1 Maxium DB size is determined by the amount of vRAM and the IO subsystem


Landscape Design

4 Sizing CalculationsModern SAP solutions consolidate many SAP components (ECC, BW, CRM etc) onto one single infrastructure. This concept is illustrated in the PDF file attached to SAP Note 1612283 - Hardware Configuration Standards and Guidance. Many SAP systems such as ECC, BW, CRM can be running on a shared server infrastructure either with or without virtualization.

Cloud deployments further consolidate the scope and number of SAP systems running on a hardware infrastructure. This creates some difficulty in sizing SAP systems on cloud deployments. Fortunately unlike with traditional hardware infrastructures it is relatively easy to change the Processor and Memory components with Hyper-V 3.0 and therefore increase or decrease the processing power of a VM.

The approach that has been successfully prototyped in the lab and tested at customer sites is to follow some basic assumptions about the hardware capacity and to size based on memory.

Using the 2 processor commodity servers available today the performance envelope is:

1. Based on E5 2680 (or AMD equivalent) processor with SD 2 Tier Benchmark = ~40,000 SAPS

2. 2 processor with 8 cores and Hyperthreading = 32 threads3. SAPS per thread is approximately 1250 (with Hyperthreading on)4. Overhead of Hyper-V 3.0 is minimal on modern Hardware 5. SQL Server Database Compression and large SQL Cache sizes lead to dramatic

reductions in the amount of physical read IO, in many cases eliminating physical read IO

6. Although many SAP systems such as ECC, BW, CRM, SCM and other workload intensive applications may be consolidated on a single Private Cloud Infrastructure, it is exceedingly unlikely that all of them are extremely busy at a single point in time2

4.1 SAP QuicksizerNew customer deployments should follow the SAP standard process and complete the SAP Quicksizer. In many cases the output of the Quicksizer even for 1000-1500 user systems are SAPS values in the range of 15,000 to 30,000. This value is far less than a 2 processor commodity Intel server running in 2 tier configuration. Running in 3 tier configuration a 2 processor commodity Intel server can deliver 150,000 to 200,000 SAPS. These values are higher than almost all SAP systems in production currently. The PDF file attached to SAP Note 1612283 - Hardware Configuration Standards and Guidance has more guidance in this area

2 In fact during customer testing it has been proved that the resource requirements between SAP systems has extremely low covariance, meaning there is a very weak relationship between the peaks on ECC and any other system






Landscape Design

Calculation of the SAPS value of a SAP solution is always the responsibility of the Hardware Partner.

4.2 Sizing ProcessThe following steps are required to determine how many physical cluster nodes are required:

1. List SAP Components2. Determine which SAP Components require Development, QAS, Production

environments3. Complete SAP Quicksizer 4. Fully review SAP Note 1612283 - Hardware Configuration Standards and

Guidance5. Determine how many Development, QAS and Production Virtual Machines are

required6. Determine the size of each VM: Small, Medium, Large or Extra Large7. Determine which Deployment Scenario is required (Scenario 1, 2, 3 or 4)8. Use the Virtual Machine Calculator to add up the total memory of all VMs and

automatically determine the minimum number of cluster nodes required (it would be normal to add one or two nodes more)

9. Round up this number to the nearest whole number and add one or two3 cluster nodes as sizing buffer. Example: 1800GB RAM requires 6 physical nodes

Additional capacity of 1-2 cluster nodes provides customers with additional capacity that may be useful for operational or HA/DR purposes. SAP do not allow over-committ4 of RAM and it is therefore important never to overload an individual physical cluster node during maintenance operations such as updating the BIOS/Firmware on a server.

4.3 RAM Based SizingIn order to determine how many Hyper-V cluster servers are required it is necessary to calculate the total RAM requirement.The example below illustrates a typical scenario A customer has a Development, Test and Production landscapeComponent Develo

pQAS Production Notes

ECC 6.0 EHP 6

DB+CI DB+CI

HA DB + ASCS + 8 App

BW 7.31 DB+CI DB+CI


BW Java DB+CI DB+CI


EP DB+CI DB+CI


PI DB+CI DB+ HA DB + ASCS + 2

3 This document takes a conservative approach to sizing. Due to the high density of systems it is recommended to add one or two (for larger systems) cluster nodes as a buffer for peak loads and future growth4 Over-committ is allocating more vRAM than the physical RAM present in a server – see Note 1409608 - Virtualization on Windows




Landscape Design

CI AppSCM DB+CI DB+

CIHA DB + ASCS + 2 App

+LiveCache5

GRC DB+CI DB+CI


SolMan DB+CI DB+CI


Business Obj DB+App

- HA DB + 2 App

5 Note 1142243 - SAP MaxDB release for virtual systems


Landscape Design

4.4 Microsoft Private Cloud Solution VM CalculatorThe Excel spreadsheet below is very useful to “balance” the VMs over the required number of physical cluster nodes.The original Excel spreadsheet is embedded in this document and can be modified to increase the number of cluster nodes or other changes.

The VM Calculator allows customers to enter in the amount of RAM in a physical server (min 384GB, max 2TB), the number of logical processors (min 32, max 144) and to add or remove cluster nodes (min 4, max 64). The virtual machine sizes (Small = 32GB, Medium 128GB, Large 196GB and Extra Large 384GB) are fixed and cannot be changed. The Calculator will warn on overcommit of vCPU and will give an error on overcommit of vRAM.

It is recommended to test different landscape configurations with different degrees of consolidation of Database and Application servers to obtain the optimal solution specific to each customer requirement. The VM Calculator will automatically re-calculate the per node and total vRAM and vCPU.

Some customers may have a preference for a higher degree of consolidation of both DB and Application servers within a single VM. Other customers may prefer to have only one SQL Server named instance or SAP application server per single VM. Customers and Partners should consider Sizing and Operational factors when determining the degree of consolidation.

The illustration on page 12 shows a rather high degree of consolidation on the SAP application layer. A larger number of smaller VMs with fewer SAP application servers per VM is also a valid configuration.

Value Units

Number of Cluster Nodes Required

5


Landscape Design

Physical RAM (384GB to 2TB)

384 GB

Physical threads 32

Cluster Node 1 Cluster Node 2 Cluster Node 3 Cluster Node 4 Cluster Node 5 Cluster Node 6Cluster Totals

Environment

#VMs(1-32) VM Size

#VMs(1-32) VM Size

#VMs(1-32) VM Size

#VMs(1-32) VM Size

#VMs(1-32) VM Size

#VMs(1-32) VM Size

Total

vCPU

Total

vRAM

Development 3Small 32 GB / 4 vCPU 3

Small 32 GB / 4 vCPU 3

Small 32 GB / 4 vCPU 36 288

Development Total 3 3 3 36 288

QAS 2Small 32 GB / 4 vCPU 2




QAS Total 2 2 2 1 28 224

Prod DB 1Medium 128 GB / 8 vCPU 1

Large 192 GB / 16 vCPU 2


Medium 128 GB / 8 vCPU 1

Large 192 GB / 16 vCPU 64 832

Prod DB Total 2 2 1 64 832

Prod ASCS 1Small 32 GB / 4 vCPU 1


Prod App Server 1Medium 128 GB / 8 vCPU 2

Medium 128 GB / 8 vCPU 1

Medium 128 GB / 8 vCPU 32 512

Prod App Server Total 1 2 1 32 512 Total vCPU 28 32 32 24 28 24 168

Total vRAM (GB) 288 384 256 320 352 320 192

0


Landscape Design


Landscape Design

5 Network Configuration

Review Chapter 1 Hardware and Network for more details on Network Configuration.

It is strongly recommend to use 10 Gigabit network for SAP on Microsoft Private Cloud Solution. The use of 1Gigabit Ethernet for Live Migration, the network between the SAP application server and the DB server and for iSCSI is strongly advised against. 10 Gigabit network cards have performance, virtualization and “balancing” features that most 1 Gigabit network cards do not have. No testing has been performed on 1 Gigabit cards. No pilot deployments have been validated on 1 Gigabit cards. 10 Gigabit is the defacto data center standard and 1 Gigabit infrastructure should be considered obsolete. See Networking chapter for more information.

Rack based systems support multiple dual port 10 Gigabit network cards. It is exceeding unlikely that many customers can saturate multiple 10 Gigabit network cards.

Blade based systems sometimes offer converged network interfaces that aggregate the network load from an entire chassis of blades into multiple 10 Gigabit interfaces. Sometimes these 10 Gigabit interfaces are also shared with FCoE devices, thereby reducing the available bandwidth by either 4 Gigabits/sec or 8 Gigabits/sec. In such cases it is possible that a fully populated Blade Chassis would overload the network interfaces. Blade based technologies that re-route network communication within the Blade Chassis itself can reduce the amount of external network communication and improve performance.

Very large SAP systems running on Blade based servers need very careful network design in order to avoid network becoming a bottleneck.


Landscape Design

6 Storage Configuration

Microsoft Private Cloud Solution for SAP supports the following storage protocolsIn many cases iSCSI has proved to be a high performance, reliable and cost effective solution.

6.1 iSCSIiSCSI performance has improved dramatically in recent years due the 10 Gigabit network and offload features on the network cards. iSCSI performance in most cases is similar to conventional SAN with Fibre Channel interface. The cost of iSCSI is comparatively less than alternatives and has therefore become increasingly popular.

Two 10 Gigabit iSCSI interfaces per physical server are always required as a minimum for HA reasons. Two iSCSI would be sufficient for very large SAP systems. Rather than adding additional iSCSI interfaces it is recommended to scale out the solution onto more physical cluster nodes. This distributes the IO over additional servers and 10 Gigabit network interfaces.

6.2 Fibre Channel (vHBA)At least one dual port HBA per physical server are required giving a total of two active ports. Two 4 Gigabit/sec or 8 Gigabit/sec Fibre Channel connections are sufficient for most systems. Multipath software must be configured to evenly distribute IO across all ports.

If a particular cluster node has excessive IO or is experiencing IO latencies then it is recommended to scale out the solution by adding additional cluster nodes to run the Database components. Optionally additional HBA can be added if required.

6.3 FCoEFCoE presents to Windows in the same manner as Fibre Channel. The requirements are therefore the same. The bandwidth allocated to each FCoE connection should be no less than 4 Gigabits/sec

6.4 SMB 3.0SMB 3.0 configurations will be covered in a later document after successful customer pilot deployments of this technology. Correct network configuration and high performance network cards and drivers become critical for SMB 3.0.


Landscape Design

7 Appendix 1 – 4 Socket ConfigurationsBuilding Microsoft Private Cloud solutions for SAP is only tested in the lab and piloted at customer sites on 2 socket systems. 4 socket systems have not been tested or deployed so far. Before deploying on 4 socket systems fully review SAP Note 1612283

4 socket systems need to have at least 800GB RAM in order to achieve the same local NUMA memory as 2 socket systems. Customers who wish to deploy on larger scale up servers are recommended to:

1. Utilize 4 socket systems with 1-2TB RAM2. Utilize 8 socket systems with 2-4TB RAM3. Ensure VM sizing does not exceed 1 NUMA node4. Engage Microsoft Consulting or expert assistance5. Monitor per NUMA node performance closely

32GB DIMMs will be required on most systemboards to reach these memory densities.

4 socket or 8 socket scale up platforms may have additional RAS features that make them especially useful for virtualizing data database workloads. Due to the reasons explain in SAP Note 1612283 SAP application servers will almost always perform better on 2 socket servers with high clock speed.

Examples of the enhanced RAS features are detailed in the links below:With Hyper-V: http://h20324.www2.hp.com/SDP/Content/ContentDetails.aspx?ID=3432Native OS: http://h20324.www2.hp.com/SDP/Content/ContentDetails.aspx?ID=3397


http://h20324.www2.hp.com/SDP/Content/ContentDetails.aspx?ID=3397




Landscape Design

8 Appendix 2 – Tested Network Cards HPHP NC552 – EmulexHP NC560 – Intel

DellIntel based 10 Gigabit add in cards or LOM

CiscoAll tested NICs are ok

IBMIntel x520 and x540 based NIC


Landscape Design

9 Appendix 3 – Sample Bill of Materials A small SAP customer has ECC 6.6, BW 7.31, PI 7.31, EP 7.31, Solution Manager 7.1, GRC and Business Objects. The customer has a simple Development, QAS and Production Landscape with no DR. The ECC system has 1,000 medium users of which 700 are active at one time

Servers = 6 units of:2 x Intel E5 2680 Processors24 x 16GB DDR-3 RAM = 384GB per Server2 x Dual Port Intel 10 Gigabit Network Card with SRIOv, VMQ, RSS 2 x Dual Port Intel 10 Gigabit Network Card with SRIOv, VMQ, RSS 1 x onboard 1 Gigabit Dual Port Network Card for Heartbeat and Management network interfacesOptional: 1 x 785GB FusionIO card for accelerating transaction log3 year standard service and supportWindows 2012 Data Center Edition x64SQL Server 2012 Enterprise Edition x64

Storage & Network1 x 48 Port 10 Gigabit Network Switch (with support for Jumbo Frames and LACP Port Trunking)1 x iSCSI Device with 48 x 600GB SAS disksCAT6a/CAT7 Twinax Network Cabling


9. microsoft private cloud solution for sap landscape ... · web viewalthough many sap systems...

Documents