Professional Documents
Culture Documents
Symptom
You want to install SAP HANA platform in a virtualized environment using VMware vSphere 6.5 or 6.7 virtual
machines
Other Terms
SAP declares support for VMware vSphere 6.5 and 6.7 for virtual deployments in production scenarios of
SAP HANA on either certified appliances or through SAP HANA tailored data center integration verified
hardware configurations. The SAP HANA start release defined as "SAP HANA 1.0 SPS xx" includes support
for SAP HANA 2.0. Certified Hardware can be found in the Certified and Supported SAP HANA® Hardware
directory [1]
Solution
By issuing this SAP Note, SAP extends support for SAP HANA on VMware vSphere 6.5, providing the
following conditions are met:
Single and multiple SAP HANA production virtual machines on a single physical server
The minimum size of a virtual SAP HANA instance is a half socket (represented by at least 8 physical
cores). The minimum is 128GB of RAM.
The maximum size for Broadwell of a virtual SAP HANA instance is limited CPU-wise by the maximum size
of a virtual machine on VMware vSphere 6.5 and 6.7 release, which is 128 vCPUs on 4 Sockets (4 sockets
on up to 8 socket hardware), and 4TB of RAM. Due to the underlying certified hardware OLAP can only used
with maximum 2TB.
The maximum size for Skylake of a virtual SAP HANA instance is limited CPU-wise by the maximum size of
a virtual machine on VMware vSphere 6.5 and 6.7 release, which is 128 vCPUs on 4 Sockets (4 sockets on
up to 8 socket hardware), and 6TB of RAM. Due to the underlying certified hardware OLAP can only used
with maximum 3TB.
Due to the security vulnerability identified in CVE-2018-3646 VMware strongly advices customers
to review and enable the recommendations indicated in VMware KB 55806. In particular, VMWare
recommends that customers must ensure that after enablement, the maximum number of vCPUs
per VM must be less than or equal to the number of total cores available on the system or the VM
will fail to power on. The number of vCPUs on the VM may need to be reduced if it is to run on
existing hardware. The number of vCPUs should be a factor of two. VMware is providing a tool to
assist customers with the analysis of their VM configuration.
SAP HANA production virtual machines as part of a SAP HANA Scale-Out Cluster
Rules for virtualized SAP HANA on VMware vSphere 6.5 and 6.7
• Each SAP HANA instance / virtual machine is sized according to the existing SAP HANA sizing
guidelines and VMware recommendations.
• SAPs general sizing recommendation is to Scale-Up first.
• CPU and Memory over-commitment must not be used.
• The Time Stamp Counter (TSC) must be synchronized between all sockets/cores.
• Certified OS versions (from SUSE and Redhat) and server combinations as listed on the SAP HANA
hardware directory are supported when virtualized.
• VMware vMotion, VMware Distributed Resource Scheduled (DRS), as well as VMware HA
capabilities can be used to achieve operational performance and availability.
• SAP HANA Tailored Datacenter Integration (TDI) [3] delivery methods are supported for SAP HANA on
VMware vSphere. The hardware must be listed on the SAP HANA hardware directory. The SAP HANA
installation must done by an SAP certified engineer, qualified as "SAP Certified Technology Specialist -
Required exam: C_HANATEC_11 (*) - See [4] SAP Training and Certification Shop The SAP HANA
Installation on SAP HANA certified hardware must be successfully verified with the SAP HANA
hardware configuration check tool [5].
• Configuration and overall setup must comply with the latest version of the SAP HANA on VMware
vSphere [6] and the here linked most recent best practice guide. This includes compliance to the SAP
HANA core-to-memory ratio as reflected in the HANA Hardware Directory and virtualization calculus as
described in the best practice guide as well as priority for SAP HANA production workloads over co-
deployed non-production workloads.
• SAP and VMware will jointly support virtual SAP HANA in production adhering to the SLAs defined in
the customer support contract. If a reported problem is a known SAP HANA issue with a validated fix,
SAP support will recommend the appropriate fix directly to the customer. For all other performance
related issues, the customer will be referred within SAP’s OSS system to VMware for support. VMware
will take ownership and work with SAP HANA HW/OS partner, SAP and the customer to identify the
root cause. SAP support may request that additional details be gathered by the customer or the SAP
HANA HW partner to help with troubleshooting issues. In rare cases – SAP may require VMware to re-
produce the issue on SAP HANA running in a bare metal environment.
• SAP and VMware saw degradation compared in performance on bare metal in average of 10%, and
this is to be expected in virtualized environments. Customers are encouraged to size correct and test
performance before going live.
• To allow for an easier distinction to be made between scenarios which can be considered a good fit
against those scenarios which seem to be less suitable for virtualization, more scenario specific
examples are being worked out and described in the VMware Best Practices Guide.
• SAP HANA VMs can get co-deployed with SAP non-production HANA or any other workload VMs, as
long as the production SAP HANA VMs are not negatively impacted by the co-deployed VMs. In case
of negative impact on SAP HANA, SAP may ask to remove any other workload. No Numa node
sharing between SAP HANA and non HANA allowed.
[3] SAP HANA Tailored Data Center Integration - Frequently Asked Questions
[5] SAP Note 1943937 - Hardware Configuration Check Tool - Central Note
[7] SAP HANA on VMware vSphere best practices guide white paper
Software Components
Other Components
Component Description