Skip navigation

SAP HANA tailored datacenter integration (TDI) offers great flexibility for SAP business solutions in production and non-production environments. This can be deployed in a bare metal or virtualized environment. Our solution, SAP HANA on VMware vSphere 6.5 and 6.7, follows the SAP HANA TDI guidelines. It offers the power of SAP HANA while benefitting from the flexibility of a virtualized environment.

VMware has certified VMware vSphere 6.5 and vSphere 6.7 on Intel Skylake SP processors for virtualized SAP HANA deployments. See SAP Note 2393917.

SAP HANA Tailored Datacenter Integration

SAP increases flexibility and provides an alternative to SAP HANA appliances with a SAP HANA TDI solution in 5 phases currently. This includes many kinds of virtualization technology. Understanding the possibilities and requirements of an SAP HANA TDI environment is crucial. One of these requirements by SAP is to consider all virtualized environments for SAP HANA as SAP HANA TDI.

SAP provides the following documentation around SAP HANA TDI environments that explain the 5 phases of SAP HANA TDI, as well as the hardware and software requirements for the whole stack:

Hardware Elements

Currently Hitachi Vantara Engineering has tested and validated SAP HANA on VMware vSphere on the certified appliances and on Intel supported system servers with external storage only. The installer created for use by Hitachi Vantara service personnel and a raw template deployment were tested on Hitachi Advanced Server DS7000 as described in the reference architecture guide.

Also, the following servers have been tested and validated for use with external storage:

  • Hitachi Advanced Server DS220
  • Hitachi Advanced Server DS240

Running SAP HANA on VMware is allowed also inside partitions of Hitachi Advanced Server DS7000, following the same rules and guidelines as non-partitioned systems.

While Hitachi Virtual Storage Platform G700 is mentioned in the reference architecture guide, all SAP HANA-certified Hitachi enterprise storage systems are supported to run SAP HANA on VMware. This enables consolidated landscapes that guarantee equal performance and reliability as in bare metal appliances when following the sizing guidelines according to SAP, where each virtual machine counts as one HANA node.

SAP HANA Tailored Data Center Integration on Hitachi Virtual Storage Platform G Series and VSP F Series with Hitachi Storage Virtualization Operating System Reference Architecture Guide provides insight in best practices for Hitachi storage in SAP HANA TDI environments.

VMware vSphere

In the SAP Community Wiki, VMware hosts a page with up to date information about SAP HANA on VMware vSphere. This includes the following:

  • A supportability matrix for the different vSphere releases
  • SAP HANA service pack stacks
  • CPU generations
  • References and best practices for SAP HANA on VMware

Find more information around SAP and SAP HANA on VMware vSphere is available on VMware’s SAP and VMware page.

The latest Architecture Guidelines and Best Practices for deployments of SAP HANA on VMware vSphere are implemented in our solutions.

VMware vSphere Configuration

The Speculative Execution Side Channel vulnerability on Intel processors affects microprocessors, operating systems, system management mode, and virtualization software. VMware provides a patch that affects the sizing of the virtual machines. When activated, it can successfully mitigate this vulnerability. However, this is at the cost of not using hyperthreads and thus impacting performance. VMware has summarized the performance impact of enabling the patches in KB55767.

For the SAP HANA workload in the virtual machines, SAP does not allow overcommitting CPU resources. Take this into account when sizing virtual machines and determining the required compute hardware resources.

Multiple Virtual Machine Configurations

When running this solution in a single-virtual machine configuration, one Hitachi Advanced Server DS7000 with 4 CPUs provides enough resources to run a virtual machine with the maximum possible 128 vCPUs.

A setup with multiple virtual machines may soon require a server with more CPU and memory resources, like Hitachi Advanced Server DS7000, with either 6 CPUs or 8 CPUs.

Depending on the number of virtual machines as well as the requirements of the SAP HANA installation inside these virtual machines, further storage resources can become necessary. Contact your Hitachi Vantara account team to size storage for all SAP HANA-certified enterprise storage units.

Sizing is available for SAS drives, SSD drives, and Hitachi Accelerated Flash devices for the maximum number of SAP HANA nodes in the SAP HANA Certified Hardware Directory. For virtualized environments, one virtual machine counts as one SAP HANA node, according to SAP requirements.

In a single server environment, the maximum number of virtual machines is 16 when using only 0.5-socket virtual machines on an 8-socket server. However, this sizing is also valid for running multiple VMware ESXi servers connected to one Hitachi storage system.

According to SAP Note 2393917, SAP and VMware support a co-deployment of production and non-production virtual machines on the same server. It is also possible to separate the production and non-production SAP HANA virtual machines on different servers but connect both servers to the same storage array.

Non-production virtual machines do not have the same performance requirements as production virtual machines. SAP gives no performance guarantee for non-production SAP HANA installations.

However, in both cases, you must ensure that the production SAP HANA instances and virtual machines are not negatively impacted by the non-production systems running in parallel.

Installer Media and Documentation from SAP Solution Engineering Team

As mentioned before, we have tested our installer for VMware vSphere and the deployment of the raw template on the above-listed servers. The vInstaller, available to Hitachi Vantara service personnel, makes sure that VMware and Hitachi Vantara best practices are configured on VMware ESXi and virtual machine level.