SAP extends support for SAP HANA on VMware vSphere 5.5 to include controlled (and also productive) availability of scale-out deployments for SAP BW. Let me share some thoughts and slides with you that I have prepared for this year’s SAPPHIRE in Orlando. I also have some hot of the press figures from my friend at VMware, Erik Rieger.
As you can see in the figure below, you can run your HANA master nodes, HANA worker nodes and other VMs in a vSphere cluster that is connected to TDI storage.
If that’s not enough you can also run HANA over multiple vSphere clusters:
Or, what about having e. g. 2 scale-out HANA systems in 2 vSphere resource pools?
Now, this might be the moment where you ask yourself: “And how many productive VMs can I run on one ESXi server?”. As often the answer is – an I hate it – “… it depends”. So, to give you an idea let me give you an example. Let’s assume you have a 4 socket HANA server, then your TDI storage must be connected in a way that allows you to fulfill the HANA TDI KPIs for 3 parallel running VMs (remember productive HANA VMs must be pinned to a socket). The fourth socket could be used for other VMs.
The following figure shows a virtualized HANA on EMC ScaleIO configuration, that my great VCE colleagues and I were able to validate. We demonstrated that you can run 6 HANA systems on 2 ESXi servers and still fulfill all relevant SAP HANA TDI KPIs for productive use.
For a SAN-based TDI implemention, the SAN storage and network layout for a SAP HANA scale-out on vSphere could look like this:
My final two questions to you are:
- Isn’t that exactly what you want to see in your data center – HANA nodes that can be adjusted to the real needs combined with TDI?
- How many nodes (if any…) do you have beyond 1 TB RAM (vSphere 5.5) and 4 TB RAM (vSphere 6, coming soon)?
For more about virtualized scale-out HANA please see SAP note 1788665.