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

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.

News

  • Multi SAP HANA VM and NUMA Node Sharing (CPU socket sharing) with VMware vSphere 6 and 6.5 support is available now. This allows the installation and operation of multiple SAP HANA systems deployed on a single SAP HANA certified server virtualized with vSphere 6.0 and 6.5. For details please review SAP note 2315348 and 2393917 and following VMware blog.
  • The new Architecture Guidelines and Best Practices for Deployments of SAP HANA on VMware vSphere Guide, now available! Download it from here.

Support Information

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

Additionally be aware of the following recommendations:

By now we have five 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 May 2017.

SAP HANA on vSphere support notes:

  • 1995460 -        SAP HANA on VMware vSphere 5.5 in production
  • 2024433 -        Multiple SAP HANA VMs on VMware vSphere 5.5 in production
  • 2157587 -        SAP BW, powered by SAP HANA on VMware vSphere 5.5 in scale-out in production
  • 2315348 -        SAP HANA VM on VMware vSphere 6 in production
  • 2393917 -        SAP HANA VM on VMware vSphere 6.5 in production

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. "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 SAP HANA production VM scenario on a single physical server

Availability General Availability - Full SAP Support
Support level production
vSphere releasevSphere 5.5vSphere 6.0vSphere 6.5
SAP note199546023153482393917
SAP HANA start releaseSAP HANA 1.0 SPS 07SAP HANA 1.0 SPS 11SAP HANA 1.0 SPS 12
max RAM VM size1 TB4 TB4 TB [1]
min RAM VM sizesized according to SAP sizing project results
CPU resources (up to ESXi maximum) [2]up to 4-socket VMsup to 8-socket VMsup to 4-sockets
min CPU resources [3]sized according to SAP sizing project results, minimal 8 pCores / 16 vCPUs
Intel Ivy BridgeE7 EX2 and 4-socket2, 4 and 8-socket-
E5 EP2-socket2-socket-
Intel HaswellE7 EX2 and 4-socket2, 4 and 8-socket-
E5 EP2-socket2-socket-
Intel BroadwellE7 EX-2 and 4-socket2 and 4-socket
E5 EP-2-socket2-socket

[1] vSphere 6.5 6 TB SAP HANA VM sizes are in validation. Maximal RAM installed in physical server as specified by SAP, in the Certified SAP HANA Hardware Directory.

[2] A SAP HANA VM configuration should mirror the physical HW. E.g. a SAP HANA VM running as a single VM on a 4-socket server should get configured with 4 virtual CPU sockets and as many as vCPUs per socket as sized, up to the maximum of 128 vCPUs with vSphere 6.x (example: 4 sockets with 32 vCPUs).

[3] SAP requests for a SAP HANA system minimal 8 pCPU cores or 16 threads for production, as of today maximal 2 VMs are allowed for Haswell (18 core CPUs) or Broadwell (22 and 24 core) CPUs. Please use Numa.PreferHT=1 parameter as documented in KB 2003582 when you configure the VMs!

 

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!
 

Multiple SAP HANA production VM scenario on a single physical server

Availability General Availability - Full SAP Support
Support level production
vSphere releasevSphere 5.5vSphere 6.0vSphere 6.5
SAP note202443323153482393917
SAP HANA start releaseSAP HANA 1.0 SPS 07SAP HANA 1.0 SPS 11SAP HANA 1.0 SPS 12
max RAM VM size1 TB4 TB4 TB [1]
min RAM VM sizesized according to SAP sizing project results
CPU resources (up to ESXi maximum) [2]up to 4-sockets2-/8-socket HW:
1- and 2-socket VMs

4-socket HW: 1-,2-,
3- and 4-socket VMs
2-socket HW:
1- and 2-socket VMs

4-socket HW: 1-,2-,
3- and 4-socket VMs
min CPU resources [3]sized according to SAP sizing project results, minimal 8 pCores / 16 vCPUs
Intel Ivy BridgeE7 EX2 and 4-socket-
E5 EP2-socket-
Intel HaswellE7 EX2 and 4-socket2, 4 and 8-socket-
E5 EP2-socket2-socket-
SAP HANA NUMA Node Sharing allowed with this CPU
-Yes, half-socket, no odd multiples of half sockets [4]-
Intel BroadwellE7 EX-2 and 4-socket2 and 4-socket
E5 EP-2-socket2-socket
SAP HANA NUMA Node Sharing allowed with this CPU
-Yes, half-socket, no odd multiples of half sockets [4]

[1] vSphere 6.5 6 TB SAP HANA VM sizes are in validation. Maximal RAM installed in physical server as specified by SAP, in the Certified SAP HANA Hardware Directory.  

[2] A SAP HANA VM configuration should mirror the physical HW. E.g. a SAP HANA VM running as a single VM on a 4-socket server should get configured with 4 virtual CPU sockets and as many as vCPUs per socket as sized, up to the maximum of 128 vCPUs with vSphere 6.x (example: 4 sockets with 32 vCPUs).

[3] SAP requests for a SAP HANA system minimal 8 pCPU cores or 16 threads for production, as of today maximal 2 VMs are allowed for Haswell (18 core CPUs) or Broadwell (22 and 24 core) CPUs. Please use Numa.PreferHT=1 parameter as documented in KB 2003582 when you configure the VMs!

[4] As of today, no odd multiples of half sockets like 1.5 socket VMs, 2.5 socket VMs etc.

 

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

Availability General Availability - Full SAP Support
Support level production
vSphere releasevSphere 5.5vSphere 6.0vSphere 6.5
SAP note2157587  
SAP HANA start releaseSAP HANA 1.0 SPS 09-
max RAM VM size1 TB-
min RAM VM sizesized according to SAP sizing project results-
CPU resources (up to ESXi maximum) [1]up to 4-sockets-
min CPU resources [2]sized according to SAP sizing project results, minimal 8 pCores / 16 vCPUs-
Intel Ivy BridgeE7 EX2 and 4-socket-
E5 EP2-socket-
Intel HaswellE7 EX2 and 4-socket-
E5 EP2-socket-
Intel BroadwellE7 EX-
E5 EP-

[1] A SAP HANA VM configuration should mirror the physical HW. E.g. a SAP HANA VM running as a single VM on a 4-socket server should get configured with 4 virtual CPU sockets and as many as vCPUs per socket as sized (example: 4 sockets with 32 vCPUs).

[2] SAP requests for a SAP HANA system minimal 8 pCPU cores or 16 threads for production, as of today maximal 2 VMs are allowed for Haswell (18 core CPUs) or Broadwell (22 and 24 core) CPUs. Please use Numa.PreferHT=1 parameter as documented in KB 2003582 when you configure the VMs!

 

 

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

SLES 11 and 12 [1] Yes
RHEL 6 and 7 [1] Yes

[1] Both, SUSE Linux Enterprise Server (SLES) 11 and 12 and Red Hat Enterprise Linux (RHEL) 6 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.

 

 

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 (4 vCPus and 64 GB RAM), but can get used to protect for instance the SCS application server instance or a virtualized NFS server to protect in a Scale-Out environment the shared SAP HANA directory.

[5] VMware SRM allows RPO for 15 minutes and may get used for the replication of non-critical systems (RPO = 15 → data loss up to 15 minutes possible).

[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

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

For memory latency sensitive workloads with low processor utilization, such as SAP HANA, or high interthread communication, we recommended using hyperthreads with fewer NUMA nodes instead of full physical cores spread over multiple NUMA nodes. To ensure the usage of hyperthreads and to enforce NUMA node locality, set the Numa.PreferHT=1 parameter as documented in KB 2003582.

In addition please ensure that following configuration parameters are used in addition to achieve optimal performance for SAP HANA:

  • halt_in_monitor = “TRUE”
  • idleLoopSpinBeforeHalt = “TRUE”
  • Lat. Sensitivity – normal

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