Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

For any questions regarding the content of this document please send an e-mail to  erieger@vmware.com .

 

By running the SAP HANA platform virtualized on VMware vSphere, SAP customers can leverage an industry standard data center platform, optimized for agility, high availability, cost savings, and easy provisioning.

SAP customers will not only gain the ability to provision instances of SAP HANA in virtual machines much faster, but also benefit from unique capabilities like:

  • Increased security and SLAs, e.g. through NSX or DRS.
  • Live migration of running SAP HANA instances, with VMware vSphere® vMotion®
  • Standardized High Availability, based on VMware vSphere® High Availability (HA)
  • Built-in multi-tenancy support, through system encapsulation in a virtual machine (VM)
  • Abstraction of the hardware layer
  • Higher hardware utilization rates
  • Lower TCO due to SAP HANA instance consolidation

These and other advanced features - to a large extend found exclusively in virtualization - lower the total cost of ownership and ensure the best operational performance and availability.

Support Information

SAP HANA on vSphere is only supported with following three vSphere editions: vSphere Standard, vSphere Enterprise Plus and vSphere Platinum with a Premier Support level contract (min. production). No support for the vSphere Acceleration or Essentials Kits due to missing product features and limited support offerings. Following document provides an overview of the licensing, pricing, and packaging for VMware vSphere. For VMware support offerings review following page, section Premier Support.

For latest SAP released support information please refer to the central VMware on SAP Community WIKI page.

For a collection of recent support issues with VMware vSphere, check  Known Support Issues .

SAP HANA Best Practices and Recommendations:

By now we have several SAP support notes describing the support status of SAP HANA on VMware vSphere. Below tables summarize capabilities, supported deployment options and best practices, like minimal vCPU count or maximal vRAM sizes for production level SAP HANA VMs on VMware vSphere as of September 2018.

SAP HANA on vSphere support notes:

 

2652670SAP HANA on VMware vSphere - Central Note
1995460 and 2024433SAP HANA on VMware vSphere 5.5 in production
2315348SAP HANA VM on VMware vSphere 6 in production
2393917SAP HANA VM on VMware vSphere 6.5 and 6.7 in production
2779240Workload-based sizing for virtualized environments

Note:

For final design and infrastructure buying decisions, please always refer to the listed SAP notes and do not relay on below tables, as they may not have the latest support status. "The single source of trough" are always the related SAP notes!

Disclaimer: For final design and infrastructure buying decisions, please always refer to the listed SAP notes and do not relay on below tables, as they may not have the latest support status!
 

Single and Multiple SAP HANA VM's on a Single Physical Server

Availability General Availability - Full SAP Support
Support Level production
vSphere ReleasevSphere 5.5 (out of support since September 2018)vSphere 6.0vSphere 6.5 / 6.7vSphere 6.7U2
SAP Note

1995460 and 2024433

23153482393917
SAP HANA start Release [1]SAP HANA 1.0 SPS 07SAP HANA 1.0 SPS 11

SAP HANA 1.0 SPS 12 Revision 122.19, SAP HANA 2.0 recommended

max. RAM VM Size1 TB4 TB

4 TB Broadwell [2]

6 TB Skylake and Cascade Lake [2]

max. RAM VM Size Workload Based sizing

 

not available

up to 6 TB Broadwell [2]

6 TB Skylake and Cascade Lake [2]

min. RAM VM Size128 GB RAM
vCPUs per VM [3] up to 64up to 128up to 256
min. CPU Resources [3]
  • Minimal CPU resources, as sized according to SAP sizing project results, minimal 8 pCores per SAP HANA VM.
  • SAP HANA NUMA Node Sharing allowed with Intel Haswell and later CPUs and with vSphere 6.x. As of today, no odd multiples of half sockets VMs like 1.5 socket VMs, 2.5 socket VMs etc. are supported by SAP.
Intel Ivy BridgeE7 EX

Host server up to 4 sockets:

  • VM configuration: 1, 2, 3 and 4-socket VMs
  • maximal 4 SAP HANA VMs per 4 socket server [4]

Only single production level SAP HANA VM support [4]

Host up to 8-sockets. No SAP HANA Multi-VM support with Intel Ivy Bridge CPUs [4]!

 

 

 

 

 

 

 

 

no support

 

E5 EP

Host server up to 2 sockets:

  • VM configuration: 1 and 2-socket VMs
  • maximal 2 SAP HANA VMs per 2 socket server [4]

Only single production level SAP HANA VM support [4]

Host up to 2-sockets. No SAP HANA Multi-VM support with Intel Ivy Bridge CPUs [4]!

Intel HaswellE7 EX

Host server up to 4 sockets:

  • VM configuration: 1, 2, 3 and 4-socket VMs
  • maximal 4 SAP HANA VMs per 4 socket  server or any number of non-production SAP HANA and non-SAP HANA VMs [4]

Host server up to 8 sockets:

  • VM configuration 4 socket server:
    • 0.5, 1, 2, 3 and 4-socket VMs
    • maximal 8 SAP HANA VMs per 4 socket server [4]
  • VM configuration on 2 and 8 socket server:
    • 0.5, 1, and 2-socket VMs
    • maximal 4 SAP HANA VMs per 2 socket and 16 SAP HANA VMs per 8 socket server [4]
E5 EP

Host server up to 2 sockets:

  • VM configuration: 1 and 2-socket VMs
  • maximal 2 SAP HANA VMs per 2 socket  server or any number of non-production SAP HANA and non-SAP HANA VMs [4]

Host server up to 2 sockets:

  • VM configuration: 0.5, 1 and 2-socket VMs
  • maximal 4 SAP HANA VMs per 2 socket server [4]
Intel Broadwell E7 EX

 

 

 

no support

Host server min 2 and maximal 8 sockets:

  • VM configuration 4 and 8 socket server:
    • 0.5, 1, 2, 3 and 4-socket VMs
    • maximal 16 SAP HANA VMs per 8 socket server [4]
  • VM configuration on 2 socket server:
    • 0.5, 1, and 2-socket VMs
    • maximal 4 SAP HANA VMs per 2 socket [4]
E5 EP

 

no support

Host server up to 2 sockets:

  • VM configuration: 0.5, 1 and 2-socket VMs
  • maximal 4 SAP HANA VMs per 2 socket server [4]
Intel Skylake

Platinum

Gold

Silver

 

 

no support

Host server min 2 and maximal 8 sockets:

  • VM configuration 4 and 8 socket server:
    • 0.5, 1, 2, 3 and 4-socket VMs
    • maximal 16 SAP HANA VMs per 8 socket server [4]
  • VM configuration on 2 socket server:
    • 0.5, 1, and 2-socket VMs
    • maximal 4 SAP HANA VMs per 2 socket [4]
Intel Cascade Lake

Platinum

Gold

Silver

 

 

 

 

no support

Host server min 2 and maximal 8 sockets:

  • VM configuration 4 and 8 socket server:
    • 0.5, 1, 2, 3 and 4-socket VMs
    • maximal 16 SAP HANA VMs per 8 socket server [4]
  • VM configuration on 2 socket server:
    • 0.5, 1, and 2-socket VMs
    • maximal 4 SAP HANA VMs per 2 socket [4]
vSphere ReleasevSphere 5.5 (out of support since September 2018)vSphere 6.0

vSphere 6.5 / 6.7

vSphere 6.7U2

[1] The SAP HANA start release defined as "SAP HANA 1.0 SPS xx" includes support for SAP HANA 2.0. SAP HANA 2.0 recommended for Skylake and Cascade Lake platforms!

[2] Maximal SAP HANA VM RAM is 6 TB. vRAM is limited by the maximal supported RAM of a physical SAP HANA supported server configuration as specified by SAP (Broadwell 4 TB, Skylake and Cascade Lake 6 TB) for appliance like configurations. Please refer to the Certified SAP HANA Hardware Directory. Broadwell with workload based sizing up to 6 TB are possible, for details read SAP note 2779240.

[3] A SAP HANA VM configuration can get configured with maximal 256 vCPUs. As of today maximal 4-socket large VMs are supported on 4- or 8-socket systems. 8-socket large VMs are not supported yet. On Broadwell based systems maximal 192 vCPUs and on Skylake and Cascade Lake based systems maximal 224 vCPUs can get configured. This is therefore the limiting factor of a SAP HANA VM for CPU resources (SAPS capacity). SAP requests for a SAP HANA system minimal 8 pCPU cores for production. As of today maximal 2 VMs per CPU socket are allowed with Haswell (18 core CPUs) or or later CPU generation (Half-Socket VM). 

[4] SAP HANA VMs can get co-deployed on a ESXi host server with SAP non-production HANA VMs or any other workload VMs. Co-deployed VMs should not negatively impact production SAP HANA VMs (e.g. overloaded network cards). SAP HANA production VMs have to run on dedicated CPUs (NUMA nodes). Half-Socket SAP HANA VMs can share the CPU socket with other SAP HANA Half-Socket VMs (OLAP and OLTP, prod. and non-prod.). Sharing the CPU socket with non-SAP HANA VMs was not tested and is therefore not supported for SAP HANA production VMs.

[5] For OLAP workload half socket VM’s, customers shall plan an addition of 14% more CPU (SAPS) capacity per half socket VM in the sizing. This will provide additional headroom for high load situations when two SAP HANA OLAP VMs share a CPU socket. Full socket VM’s don’t need this additional CPU buffer, as they don’t share CPU resources with other VM’s.

 

Disclaimer: For final design and infrastructure buying decisions, please always refer to the listed SAP notes and do not relay on below tables, as they may not have the latest support status!
 

SAP HANA Scale-Out Deployment Configurations

NOTE

Please note, SAP general sizing recommendations is to Scale-Up first. Intel E5 based 2-socket servers are not supported in Scale-Out deployments. This SAP recommendations are not specific to virtualization. Minimal and maximal SAP HANA VM and Host sizes as described in the previous table.

Availability General Availability - Full SAP Support
Support Level production
vSphere ReleasevSphere 5.5vSphere 6.0 vSphere 6.5 / 6.7 vSphere 6.7U2
SAP Note2157587

2315348 (non-prod)

2393917
SAP HANA start Release [1]SAP HANA 1.0 SPS 09SAP HANA 1.0 SPS 12 Revision 122.19, SAP HANA 2.0 recommended
Intel Ivy BridgeE7 EX

4 socket Host server

no support

Intel HaswellE7 EX4 socket Host server   

Non-Prod. support as of note 2315348

 

 

no support  
Intel BroadwellE7 EXno support

Host server: 4- and 8-socket server systems

  • VM Size – full socket 
    4 sockets on up to 8 socket hosts (fully and partly QPI meshed),8-socket VMs are yet not supported
    up to 2TB of RAM per Scale-Out node (VM).
Intel Skylake

Platinum

 

no support

 

Intel Cascade Lake

Platinum

 

 

no support

 

Host server: 4- and 8-socket server systems

  • VM Size – full socket 
    4 sockets on up to 8 socket hosts (fully and partly QPI meshed),8-socket VMs are yet not supported
    up to 2TB of RAM per Scale-Out node (VM).

[1] The SAP HANA start release defined as "SAP HANA 1.0 SPS xx" includes support for SAP HANA 2.0.

Support Matrix Summary as of May 2019:

VMware vSphere Support Matrix and Roadmap:

SAP HANA VMware’s HANA certification/support strategy starting with Haswell, is to support a single chipset with 2 versions of the hypervisor and to have a single hypervisor version span 2 chipsets. In the case of Haswell, vSphere 5.5 and 6.0 are both supported. Similarly, with Broadwelll 6.0 and 6.5/6.7 are supported. VMware is following the same strategy with Skylake also. VMware does its best to strike a balance between supporting new customers on the latest hardware and customers who are remaining on older platforms. vSphere 5.5 is by now out of support since September 2018. vSphere 6.0 will remain in General Support from VMware, until March of 2020.

*Scale-Out Non-Prod. support for vSphere 6.0 on Haswell as of note  2315348 . Scale-Out up to 2 TB with 16 nodes, in total 32 TB GA. SAP HANA Workload Based sizing requires vSphere 6.7u2! See SAP Note 2779240

 

VMware vSphere Supported Storage Configurations for virtualized SAP HANA

Supported SAP HANA Storage Systems for virtualisation [1] All SAP HANA TDI certified and VMware [2] supported storage solutions can get used
Storage sizing [3]
As defined by storage vendor and tested regarding the SAP HANA storage KPIs

[1] For details please refer to the Certified SAP HANA Hardware Directory and go to “Certified Enterprise Storage” configurations.

[2] Beside SAP HANA TDI stoarge certification, it has to get ensured, that the storage storage solution is VMware certified. See the VMware HCL for supported storage configurations and select the used storage interface as filter.

[3] The defined KPIs for Data Throughput and Latency for production SAP HANA systems has to be fulfilled for each VM. SAP has released a special tool, the SAP HANA HW Configuration Check Tool, to measure if the used storage is able to deliver the required IO capacity, see SAP Note 1943937.

 

VMware vSphere Supported OS Versions and Vendors for virtualized SAP HANA [1]

  • SUSE Linux Enterprise Server for SAP Applications
  • SUSE Linux Enterprise Server

Yes

  • Red Hat Enterprise Linux for SAP Solutions
  • Red Hat Enterprise Linux for SAP HANA
Yes

[1] Both, SUSE Linux Enterprise Server (SLES) for SAP Applications and SAP HANA and Red Hat Enterprise Linux (RHEL) for SAP Solutions and SAP HANA are supported operating systems when virtualized. However, due to different scope and test coverage during corresponding validation activities, the underlying server must be certified for corresponding operating system. For an updated list of supported releases please refer to SAP Note 2235581

 

VMware vSphere and SAP HANA HA and Operation Features [1]

VMware HA [2]
Yes
In-Guest Cluster [3]
Yes
SAP HANA System ReplicationYes
VMware FT [4]No
VMware SRM [5]Yes
vSphere vMotionYes
VMware DRS [6] Yes
Hot-Add CPU [7]
No
Hot-Add Memory [8] No

[1] Generally all VMware vSphere features, like distributed switches are supported. The listed features got expliciltly tested with the usage with SAP HANA like vMotion to ensure these features work and that the impact is know to SAP HANA (e.g. vMotion of running SAP HANA VMs).

[2] vSphere HA to protect against OS and Host failures. If a higher SLA is needed, then see footnote [3].

[3] SAP HANA supported 3rd party Linux cluster solutions can get used to protect against SAP HANA application failures

[4] VMware FT is not suitable to protect a SAP HANA DB VM due to the resource limitations of VMware FT, but can get used to protect for instance the NetWeaver application servers, SCS application server instance or a virtualized NFS server to protect in a Scale-Out environment the shared SAP HANA directory. Ensure that the SAPS load of the FT protected SAP workload is suitable for the VMware FT limitations.

[5] VMware SRM is an automation tool for disaster recovery and allows a RPO of 5 minutes, if vSphere version 6.5 or above replication gets used for replication (RPO = 5 → data loss up to 5 minutes possible). vSAN also allows a recover point objective of 5 minutes. For any applications or databases that require a RPO < 5 minutes then VMware SRM can get combined with physical synchronous storage replication. For SRM supported storage arrays click on following link.

[6] VMware DRS should get configured in “manual mode” or set to "fully automatic  with conservative". This is the preferred setting as it allows VM host evacuation for instance during a maintenance event.

[7] Please be aware that the use of hot-add CPU feature disables vNUMA and hence may lead to performance degradation. Therefore, as of today we are generally do not support this feature in combination with VMs that run SAP HANA.

[8]  SAP HANA does not support hot-add memory. Because of this, hot-add memory was not validated by SAP and VMware with SAP HANA and is therefore not supported.

SAP HANA on vSphere Best Practices

In a nutshell: SAP HANA follows general published vSphere Best Practices for databases:

  • Set Memory Reservations for SAP HANA Virtual Machines
  • Configuring Paravirtual SCSI Controllers and Network Adapters
  • Right sizing of SAP HANA VMs to ensure local NUMA node memory access and high 2nd level cache hit ratios
  • Enable Hyper Threading on the ESXi host
  • Use dedicated networks for vMotion, management, client and if needed backup and replication network
  • Use vMotion and VMware snapshots during non peak times
  • Configure for SAP HANA latency critical the ESXi scheduler optimisation parameters as documented in below best practices guide
  • Ensure you set following SAP HANA / vSphere specific Linux kernel parameters:
    • transparent_hugepage=never
    • numa_balancing=disabled
    • elevator=noop
    • vmw_pvscsi.cmd_per_lun=254
    • vmw_pvscsi.ring_pages=32

Please read the “Architecture Guidelines and Best Practices for Deployments of SAP HANA on VMware vSphere Guide” for detailed information on the best practices and recomendations. The guide can be downloaded from our central VMware SAP page. Direct link to the document: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/sap_hana_on_vmware_vsphere_best_practices_guide-white-paper.pdf

VMware SAP HANA System Health Check

SAP and VMware are offering joint services to help you design, deploy, and implement your virtual SAP HANA platform. Examples of services which may be offered are:

  • Pre-Call to discuss PoC, goals, timeline and success factors (SAP, HW Partner, Customer and VMware)
  • Architecture review and introduction to the SAP HANA on vSphere Configuration Guidelines and Requirements
  • Introduction to SAP HANA Hardware Check Configuration Tool (HWCCT)
  • Online review session to check prepared environment like:
    • Host including storage and network configuration
    • VM configuration
    • Linux OS configuration

For more information on SAP Consulting and VMware Professional Services, visit vmware.com/consulting or get in contact with your local VMware contact.

  • No labels