This slide deck was used to present SAP TechEd 2018 session called "Overview of SAP HANA Deployment Options – Including TDI5 Update"

1. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
CNA227: Overview of SAP HANA Deployment
Options – Including TDI5 Update(update 29.8.2018)
Tomas KROJZL
SAP HANA Architect, SAP Mentor, SAP HANA Distinguished Engineer

2. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
2
Disclaimer
This presentation is based on official IBM and SAP information however it is not
representing official position of IBM nor SAP and does not contain statements about
future direction. Content of this presentation is based on personal view and
experience of presenter and cannot be associated with IBM or SAP corporations.
This document is provided without a warranty of any kind, either express or implied,
including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. IBM nor SAP assumes no responsibility for
content of this document.

3. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Agenda
3
• SAP HANA Bare Metal: Appliance Approach
• SAP HANA Tailored Datacenter Integration
• SAP HANA Virtualization
• SAP HANA Stacking Options

4. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
What was SAP HANA “Appliance”
• SAP HANA “Appliance”
• is not really appliance (not serviceable device) – SAP HANA needs to be regularly maintained
• is pre-integrated easy-to-deploy solution with well defined and fixed architecture
4
SAP HANA “Appliance”
=
Fixed Configuration
SAP HANA®
Operating System
SUSE Linux Enterprise Server for SAP
Red Hat Enterprise Linux for SAP HANA
Server HW
Internal
Network
Storage
Subsystem
https://launchpad.support.sap.com/#/notes/2000003 - FAQ: SAP HANA (entry point into SAP HANA related SAP notes)

5. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Basic Deployment Options
5
Using Shared Storage Using Local Disks
Central
Storage
Node
01
Single-node
(Scale-up)
Scale-out
Central
Storage(s)
Inter-node networking
Node
01
Node
02
Node
03
Node
04
Node
05
Node
06
Node
01
Node
02
Node
03
Node
04
Node
05
Node
06
Available only for
Lenovo models.
Inter-node networking
Distributed
“Storage”
(IBM GPFS)
Node
01

6. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA Workload Types
• SAP S/4HANA (with dominant OLAP workload)
• SAP BW/4 HANA
• SAP NetWeaver on HANA
• SAP Business Warehouse (BWoH)
+ add-ons released for SAP HANA
• Standalone SAP HANA as Data Mart (DM)
• Other scenarios unless stated otherwise
• Conservative approach in case that workload
type is not known
6
• SAP S/4HANA (with dominant OLTP workload)
• SAP Business Suite on HANA (SoH)
• SAP ERP, SAP CRM, SAP SRM, SAP SCM
• SAP SFINANCIALS
• Banking services from SAP (including SAP
Bank Analyzer)
• SAP Solution Manager
• SAP Master Data Governance
• SAP Gateway
OLAP or General Workload OLTP Workload

7. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA Workload Types
• Expected dominant analytic workload
(OLAP) that is more CPU intensive
• Conservative approach – more restrictive
CPU:RAM ratio is required
• If relational model can be easily partitioned
then scale-out is available – like for SAP
Business Warehouse on HANA (BWoH),
SAP BW/4 HANA or SAP HANA Data Mart
7
• Dominant transactional workload (OLTP)
that is less CPU intensive then OLAP
• For SAP Business Suite applications
relaxed CPU:RAM ratio can be used
• Typically complex relational model – table
distribution across nodes is not simple –
only SAP S/4HANA is supported as
scale-out deployment
OLAP or General Workload OLTP Workload

8. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
RAM [GB] 2 CPUs 4 CPUs 6 CPUs 8 CPUs 12 CPUs 16 CPUs General SoH/S4H
192 2 CPUs 2 CPUs
384 2 CPUs 2 CPUs
576 2 CPUs 2 CPUs
768 2 CPUs 2 CPUs
1152 2 CPUs 2 CPUs
1536 scale-out 2 CPUs 2 CPUs
1728 - 6 CPUs
2304 4 CPUs 2 CPUs
3072 scale-out scale-out 4 CPUs 2 CPUs
3456 6 CPUs 6 CPUs
4608 6 CPUs 4 CPUs
6144 scale-out 8 CPUs 4 CPUs
6912 - 6 CPUs
9216 scale-out 12 CPUs 6 CPUs
12288 scale-out scale-out 16 CPUs 8 CPUs
Available CPU:RAM configurations
8
• General Purpose models (green area) can
be used for any application (including SAP
Business Suite or SAP S/4HANA)
• SoH / S4H models (orange area) can be
used only for SAP Business Suite
applications on SAP HANA or SAP S/4HANA
• Various HW vendors are offering upgrade
paths to “grow” the models to bigger size by
adding additional HW resources
• Only selected models can scale-out
• Only BWoH, BW4H, DM and S4H are
allowed to run on scale-out environment
Skylake (v5) based models
Note: State as of 20th Aug 2018.
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/appliances.html

9. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Evolution of HW Generations
• There are five SAP HANA model
generations based on different Intel
CPU architectures
• Some CPU: RAM combinations are not
technically possible
• Different vendors support different
CPU: RAM combinations
• More powerful CPUs and SAP HANA
optimizations allow better CPU:RAM
ratios
9
Ivy Bridge (v2) Haswell (v3) Broadwell (v4) Skylake (v5)
RAM [GB] General SoH/S4H General SoH/S4H General SoH/S4H General SoH/S4H
128 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs - -
192 - - - - - - 2 CPUs 2 CPUs
256 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs - -
384 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs
512 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs - -
576 - - - - - - 2 CPUs 2 CPUs
768 4 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs 2 CPUs
1024 4 CPUs 2 CPUs 4 CPUs 2 CPUs 4 CPUs 2 CPUs - -
1152 - - - - - - 2 CPUs 2 CPUs
1536 8 CPUs 2 CPUs 4 CPUs 2 CPUs 4 CPUs 2 CPUs 2 CPUs 2 CPUs
1728 - - - - - - 6 CPUs
2048 8 CPUs 4 CPUs 4 CPUs 4 CPUs 4 CPUs 2 CPUs - -
2304 - - - - - 4 CPUs 2 CPUs
3072 4 CPUs 8 CPUs 4 CPUs 8 CPUs 4 CPUs 4 CPUs 2 CPUs
3456 - - - - - 6 CPUs 6 CPUs
4096 8 CPUs 8 CPUs 8 CPUs 8 CPUs 4 CPUs - -
4608 - 6 CPUs - 6 CPUs 6 CPUs 4 CPUs
6144 8 CPUs 8 CPUs - 6 CPUs 8 CPUs 4 CPUs
6912 - - - - - 6 CPUs
7680 - - - 10 CPUs - -
8192 16 CPUs 16 CPUs 16 CPUs 8 CPUs - -
9216 12 CPUs 12 CPUs - 12 CPUs 12 CPUs 6 CPUs
10240 20 CPUs 20 CPUs 20 CPUs 10 CPUs - -
10752 - - 14 CPUs - -
12288 16 CPUs 16 CPUs 12 CPUs 16 CPUs 8 CPUs
14336 - - 14 CPUs
15360 20 CPUs 20 CPUs 20 CPUs
16384 16 CPUs
20480 20 CPUs
Note:Stateasof20thAug2018.
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/index.html
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/appliances.html

10. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Agenda
10
• SAP HANA Bare Metal: Appliance Approach
• SAP HANA Tailored Datacenter Integration
• SAP HANA Virtualization
• SAP HANA Stacking Options

11. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA®
Operating System
SUSE Linux Enterprise Server for SAP
Red Hat Enterprise Linux for SAP HANA
SAP HANA TDI - Phases
11
https://www.sap.com/documents/2017/09/e6519450-d47c-0010-82c7-eda71af511fa.html
SAP HANA TDI - Phase 1: Storage
Goal: To offer choice which storage to use (storage must be
certified for SAP HANA usage, special KPIs must be met)
1
SAP HANA TDI - Phase 2: Network
Goal: To offer option to build own network design instead having to
use prescribed solution (network throughput KPIs must be met)
2
SAP HANA TDI - Phase 3: Entry Intel Systems
Goal: To offer choice to configure customized systems using
additional CPUs and additional server models (see limitations)
3
SAP HANA TDI - Phase 4: SAP HANA on Power
Goal: To offer additional HW platform – supported only under TDI
program (based on SAP HANA TDI phase 1 and 2).
4
SAP HANA TDI - Phase 5: Workload Driven Sizing
Goal: To relax CPU:RAM fixed sizing rules and allow custom
sizing respecting specific customer usage of database.
5
4
CPU + RAM 5CPU : RAM
Server HW
Internal
Network
Storage
Subsystem
23 1

12. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - Phase 1: Storage
• Only certified storage solutions can be used:
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/enterprise-
storage.html
• Vendor specific configuration guide is helping
customers to understand how to properly implement
their storage solution
• Special considerations are required to enable High
Availability setup for “SAP HANA Host Auto-Failover”
• Local disks can also be used with Intel Xeon E7
models (see https://www.sap.com/documents/2016/05/e8705aae-717c-
0010-82c7-eda71af511fa.html)
12
https://www.sap.com/documents/2015/03/74cdb554-5a7c-0010-82c7-eda71af511fa.html
Storage
Connector
Vendor
Certified
Storages
SAN
Datacore 1
Dell 3
EMC Corporation 6
Fujitsu Technology 6
Hewlett Packard 7
Hitachi 8
Huawei Technologies 7
IBM Corporation 5
INFINIDAT 1
Kaminario 1
Lenovo 2
NEC Corporation 2
NetApp 2
Pure Storage 4
NAS
Cisco Systems 1
Infinidat 1
NetApp 2
GPFS
IBM Corporation 1
Lenovo 1
Total 61
Note: State as of 29th Sep 2018.

13. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - HWCCT tool
• After implementation customer (or its delegate) is responsible to ensure that
mandatory SAP data throughput and latency KPIs are met
• SAP developed HWCCT tool to benchmark existing storage setup – all measured
data throughput and latency values must
meet prescribed SAP KPIs for TDI setup
• HWCCT tool is also used to measure
network throughput between individual
nodes of scale-out configuration
13
https://launchpad.support.sap.com/#/notes/1943937 (including attachments) Note: State as of 29th Sep 2018.
Volume
Block
Sizes
Test
File
Size
Min. throughput in MB/s Max.
Latency
[µs]
Initial
Write
Over-
write
Read
Log
4 KB 5 GB - 30 - 1000
16 KB 16 GB - 120 - 1000
1 MB 16 GB - 250 250 -
Data
4 KB 5 GB - - - -
16 KB 16 GB 40 100 - -
64 KB 16 GB 100 150 250 -
1 MB 16 GB 150 200 300 -
16 MB 16 GB 200 250 400 -
64 MB 16 GB 200 250 400 -

14. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - Phase 2: Network
• No certification for network components – any network setup can be used as long as SAP
requirements including mandatory SAP data throughput KPIs are met (see SAP note
1943937 and “SAP HANA TDI – Network Whitepaper” for more details):
https://www.sap.com/documents/2016/08/1cd2c2fb-807c-0010-82c7-eda71af511fa.html
• Network TDI is “regulating” only network communication between individual SAP HANA
nodes of scale-out system (internode network) – redundant 10Gbit dedicated network is
required (low latency network is important however latency limit is not prescribed)
• Documented best practice recommendations for other networks (client network, replication
network, storage network, backup network, admin network)
• Network throughput is measured by HWCCT benchmarking tool
14
https://launchpad.support.sap.com/#/notes/1943937 (including attachments)
https://www.sap.com/documents/2016/08/1cd2c2fb-807c-0010-82c7-eda71af511fa.html

15. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
• TDI phase 1 and 2 assumes usage of certified server
model as compute component
• Alternatively customer can productively use custom
configured “Entry” Intel Systems (with limitations)
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/intel-
systems.html
• Intel Xeon E5-26xx v2/v3/v4 – 2 socket systems only, min. 8 cores
• Intel Xeon E7 v4 (Broadwell) – min. 8 cores
• Intel Xeon Platinum, Gold, Silver v5 (Skylake) – min. 8 cores
• Intel Xeon Platinum v5 (Skylake) supports scale-out – minimum 4
socket systems for OLAP) or 8 socket systems for OLTP
• All other CPUs support only for single-node
SAP HANA TDI - Phase 3: Supported “Entry” Intel Systems
15
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/index.html
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/intel-systems.html
Supported Systems
Vendor v2 v3 v4 v5 Σ
Cisco Systems 3 5 5 7 20
Dell 5 6 7 9 27
Fujitsu Technology 2 4 4 5 15
Hewlett Packard 3 3 8 8 22
Hitachi 3 5 5 13
Huawei Technologies 1 3 7 11
Lenovo 6 9 14 10 39
NEC Corporation 3 7 9 9 28
Super Micro Computer 1 2 3
VCE 2 2
Grand Total 22 40 56 62 180
Note: State as of 29th Sep 2018.

16. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - Phase 4: SAP HANA on IBM Power Systems
• Based on TDI Phase 1 (Storage) and TDI Phase 2 (Network) principles – not
delivered as an appliance
• Support for very large LPARs
• SAP BWoH / BW4H: up to 16 TB RAM/LPAR with ability to scale-out up to 16 nodes
• SAP SoH / S4H: up to 24 TB RAM/LPAR with ability to scale-out up to 4+1 nodes (S4H only)
• Offers options to consolidate multiple systems on one server
• Non-productive HANA and/or productive non-HANA workloads being located in shared pool
• Additional resiliency (RAS) features of Power platform
• SAP HANA on power is covered in detail later as part of SAP HANA virtualization
16
https://launchpad.support.sap.com/#/notes/2055470 https://launchpad.support.sap.com/#/notes/2230704
https://launchpad.support.sap.com/#/notes/2188482 https://launchpad.support.sap.com/#/notes/2408419

17. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - Phase 5: Workload Driven Sizing
• Started as SAP HANA Appliance Approach
• Available since SAP HANA introduction
• Memory Driven sizing (CPU-to-RAM) – CPU
sizing is derived from RAM sizing as fixed
ratio
• SAP approved Reference Systems
• Infrastructure design opened with TDI
(Tailored Datacenter Integration) phases
17
• SAP Quick Sizer, Sizing Report approach
• Available since end of Q3-2017
• Workload Driven sizing (CPU-and-RAM) –
CPU sizing and RAM sizing is done based
on business utilization
• Custom built systems based on measured
workload requirements
• Available only for Intel Xeon E7 v4
(Broadwell), v5 (Skylake) and IBM Power8
Reference Configurations Workload Driven Sizing
https://blogs.saphana.com/2017/09/20/tdi-phase-5-new-opportunities-for-cost-optimization-of-sap-hana-hardware
https://www.sap.com/documents/2017/09/e6519450-d47c-0010-82c7-eda71af511fa.html
https://www.sap.com/documents/2016/05/e8705aae-717c-0010-82c7-eda71af511fa.html

18. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - Phase 5: Workload Driven Sizing
• Enhanced sizing report for BW/4HANA and
BW on HANA (see SAP notes 2296290 and 2502280)
• Memory sizing report for S/4HANA and Suite
on HANA (see SAP note 1872170) and additional
guidance (see SAP note 1793345)
• These reports are only estimations
• Make sure you understand limitations
18
Migration of Existing System
https://launchpad.support.sap.com/#/notes/2296290 (incl. attachments)
https://launchpad.support.sap.com/#/notes/2502280
https://launchpad.support.sap.com/#/notes/1872170 (incl. attachments)
https://launchpad.support.sap.com/#/notes/1793345
https://help.sap.com/http.svc/rc/f3b94bed4c2343ad8c4d1bf8c48f53b4/SIZING/en-US/HANA_sizing_V3_201612.pdf
https://help.sap.com/viewer/eb3777d5495d46c5b2fa773206bbfb46/2.0.03/en-US/d4a122a7bb57101493e3f5ca08e6b039.html
SAP Note 1793345 - Sizing for SAP Suite on HANA
“To fully support the parallel processing capabilities of HANA
for optimal response times for analytical applications SAP
prefers a factor of 3 more CPU power for HANA than for disk
based databases without parallelization of single statements.”
BW/4HANA and BW on HANA:
S/4HANA and Suite on HANA:

19. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA TDI - Phase 5: Workload Driven Sizing
• Fill in questionnaire describing estimated
business workload
• Size and activity description of different user groups
• Raw table footprint, amount of data loads
• Quantity of various types of business operations
• Push button “Calculate result” to get sizing
• CPU category and reference amount of SAPS
• Memory category and RAM requirements in GB
• Disk capacity category and Data and Log IO category
19
New SAP HANA Implementation
https://www.sap.com/about/benchmark/sizing.quick-sizer.html
https://help.sap.com/viewer/p/SAP_IN-MEMORY_COMPUTING_SIZING
https://help.sap.com/http.svc/rc/f3b94bed4c2343ad8c4d1bf8c48f53b4/SIZING/en-US/HANA_sizing_V3_201612.pdf
https://help.sap.com/viewer/eb3777d5495d46c5b2fa773206bbfb46/2.0.03/en-US/d4a122a7bb57101493e3f5ca08e6b039.html

20. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Cost-Optimized Infrastructure for Non-Production Usage
• Available ONLY for non-productive usage under “special agreement”
• CPU: - Same as for certified SAP HANA appliances
- TDI Phase 3 (Intel E5-26xx v2/v3/v4, Broadwell E7 or Skylake Platinum, Gold, Silver)
- Additional Intel Xeon CPUs – E7-x8xx v1/v2/v3/v4
• RAM: - Maximum memory possible for particular server
• Storage: - Any local or shared storage with RAID 1 (or higher)
- Performance KPIs are NOT relevant
• In general non-production systems do not need to respect CPU:RAM ratio
• Disclaimer: This setup is approved ONLY for non-production usage where performance
does not matter = customer accepts that performance will be degraded
20
https://launchpad.support.sap.com/#/notes/2271345 (including attachments)
https://blogs.saphana.com/2014/08/12/cost-optimized-sap-hana-infrastructure-requirements-for-non-production-usage

21. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Agenda
21
• SAP HANA Bare Metal: Appliance Approach
• SAP HANA Tailored Datacenter Integration
• SAP HANA Virtualization
• SAP HANA Stacking Options

22. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA Virtualization Options
• VMware vSphere see SAP note 2652670
• VMware 5.5 see SAP note 1995460
• Multi-VM support see SAP note 2024433
• SAP BWoH Scale-out see SAP note 2157587
• VMware 6.0 see SAP note 2315348
• VMware 6.5, 6.7 see SAP note 2393917
• SLES KVM see SAP note 2607144
• RedHat KVM see SAP note 2599726
• Nutanix AHV see SAP note 2686722
• XEN (non-production only)
22
• Hypervisors (incl. logical partitions)
• HANA on Power see SAP note 2230704
• Hitachi LPAR 2.0 see SAP note 2063057
• Huawei FusionSphere 6.1 and 6.3 (KVM
based) see SAP note 2659955
• Hardware partitioning
• HP nPartitions see SAP note 2103848
• Fujitsu PPARs see SAP note 2111714
• Lenovo FlexNode see SAP note 2232700
Hardware Vendor Independent Hardware Vendor Specific
https://launchpad.support.sap.com/#/notes/1788665 (including attachments)

23. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
• TDI approach required
• Network TDI KPIs must be met
• Appliance or TDI approach
• Check VMware sizing examples
SAP HANA on VMware – Production Support
• Appliance or TDI approach
23
Single-VM Multi-VM Scale-out
VMware vSphere cluster
Host 01
VM 01
VM 04
App.01
Host 02
VM 02
VM 05
App.02
Host 03
VM 03
VM 06
Central
Storage(s)
vSphere
Host 01
VM 01
VM 02
App.01
Local
Disks
VMware vSphere cluster
Host 01
VM 01
VM 04
App.01
Host 02
VM 02
VM 05
App.02
Host 03
VM 03
VM 06
Central
Storage(s)
vSphere
Host 01
Local
Disks
VM 01
VMware vSphere cluster
Host 01 Host 02 Host 03
Central
Storage(s)
VM 01 VM 02 VM 03
Technically possible - but not really useful

24. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA Virtualization Options – Hypervisor Comparison
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+HANA+on+VMware+vSphere
https://launchpad.support.sap.com/#/notes/2652670 https://launchpad.support.sap.com/#/notes/2607144
https://launchpad.support.sap.com/#/notes/2686722 https://launchpad.support.sap.com/#/notes/2599726
Max VM size Intel Ivy Bridge (v2) Intel Haswell (v3) Intel Broadwell (v4) Intel Skylake (v5)
Virtualization
Option
vCPU
vRAM
[GB]
Single
VM
Multi
VM
Scale-
out
Single
VM
Multi
VM
Scale-
out
Single
VM
Multi
VM
Scale-
out
Single
VM
Multi
VM
Scale-
out
VMware
vSphere 5.5
64 (*1) 1024 yes yes yes yes yes yes - - - - - -
VMware
vSphere 6.0
128 (*1) 4096 yes - - yes yes - yes yes - - - -
VMware
vSphere 6.5, 6.7
128 (*1) 4096 (v4)
6144 (v5)
- - - - - - yes yes yes yes yes
planned
for 6.7
SLES KVM 144 (*2) 2048 - - - yes - - - - - - - -
RedHat KVM 144 (*2) 1536 - - - yes - - - - - - - -
Nutanix 168 (*1) 2300 - - - - - - - - - yes yes -
(*1) Limited by hypervisor capabilities (*2) Limited by supported hardware (Intel Xeon E7-8890v3 18 cores)
24

25. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA on VMware – Best Practices
• Validate latest support statement at
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+HANA+on+VMware+vSphere
• Follow recommended VMware Best Practice documents:
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/sap_hana_on_vmware_vsphere_best_p
ractices_guide-white-paper.pdf
• The underlying host hardware must be listed on the SAP HANA hardware directory
• A SAP HANA VM configuration should mirror the CPU:RAM ratio of physical HW
• CPU and memory over-provisioning must not be used
• All SAP HANA VMs must be able to meet TDI KPIs simultaneously
• In case only non-productive VMs are deployed then TDI KPIs are optional
• Scale-out systems need proper network bandwidth – dedicated 10 GBit for EACH scale-out VM
• SAP HANA Tailored Datacenter Integration (TDI) is best-fit for larger deployments
25
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+HANA+on+VMware+vSphere

26. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
VIOS
(optional)
VIOS
(optional)
SAP TDI
Storage(s)
Dedicated-donating LPARs
SAP HANA on IBM Power Systems
26
• SAP HANA on IBM Power Systems solution is
using SAP TDI certified storage
• Multiple productive SAP HANA LPARs can be
deployed in dedicated mode (four LPARs for
E850, six for E850C and eight for E870/E880)
• Alternative is to use shared processor pool
instead of one productive LPAR; productive
LPARs are running in dedicated-donating
mode giving CPU cycles to shared pool
• Shared pool can host non-productive SAP
HANA workloads or any other productive or
non-productive workloads (for example
application servers)
Single-VM and Multi-VM
Power 8 E850
Productive
HANA 01
Productive
HANA 02
Productive
HANA 03
Productive
HANA 04
Shared Processor Pool
Productive
NW AS 02
Productive
NW AS 01
Productive
NW AS 03
Non-prod.
HANA 04
Non-prod.
HANA 05
Other
workload
Non-prod.
NW AS 04
Non-prod.
NW AS 06
Non-prod.
NW AS 05
Dedicated LPARs

27. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA on IBM Power Systems – Reference Sizing
https://launchpad.support.sap.com/#/notes/2188482/E https://launchpad.support.sap.com/#/notes/2230704/E
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/power-systems.html
27
Cores per
Production LPAR
Maximum Prod.
CPU:RAM ratio
Maximum Prod.
RAM [GB] per LPAR
(*1) Limited by hardware
(*2) Limited by SAP Note 2188482
Power 8
Model
Minimal Maximal General SoH/S4H General SoH/S4H Maximum LPARs (options)
S822 4 20 32 96 640 1024 (*1)
• 4x dedicated prod. LPAR
• 3x dedicated-donating LPAR +
shared pool for non-production
S822L 4 24 32 96 768 1024 (*1)
S824 4 24 32 96 768 2048 (*1)
S824L 4 24 32 96 768 2048 (*1)
E850 4 32 32 96 1024 3072
E850C 4 48 50 96 2400 4096 (*1)
• 6x dedicated prod. LPAR
• 5x dedicated-donating LPAR +
shared pool for non-production
E870 4 80 50 96 4000 (*2) 7680
• 8x dedicated prod. LPAR
• 7x dedicated-donating LPAR +
shared pool for non-production
E870C 4 80 50 96 4000 (*2) 7680
E880 4
192 OLAP
176 OLTP
50
see table
on right
9600
see table
on right
E880C 4
192 OLAP
176 OLTP
50
see table
on right
9600
see table
on right
RAM [GB] per
Production LPAR
SoH/S4H cores per
Production LPAR
Power 8
Model
From To Min. Max.
E880
E880C
128 384 4 4
384 12288 4 128
12288 13312 128 132
13312 14336 132 136
14336 15360 136 140
15360 16384 140 144
16384 17408 144 148
17408 18432 148 152
18432 19456 152 156
19456 20480 156 160
20480 21504 160 164
21504 22528 164 168
22528 23552 168 172
23552 24576 172 176

28. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA on IBM Power Systems – Workload Driven sizing
https://launchpad.support.sap.com/#/notes/2188482/E https://launchpad.support.sap.com/#/notes/2230704/E
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/power-systems.html
28
Cores per
Production LPAR
Maximum Prod.
CPU:RAM ratio
Maximum Prod.
RAM [GB] per LPAR
(*1) Limited by hardware
(*2) Limited by SAP Note 2188482
Power 8
Model
Minimal Maximal General SoH/S4H General SoH/S4H Maximum LPARs (options)
S822 4 20
No ratio No ratio
1024 (*1) 1024 (*1)
• 4x dedicated prod. LPAR
• 3x dedicated-donating LPAR +
shared pool for non-production
S822L 4 24 1024 (*1) 1024 (*1)
S824 4 24 2048 (*1) 2048 (*1)
S824L 4 24 2048 (*1) 2048 (*1)
E850 4 32 4096 (*1) 4096 (*1)
E850C 4 48 4096 (*1) 4096 (*1)
• 6x dedicated prod. LPAR
• 5x dedicated-donating LPAR +
shared pool for non-production
E870 4 80 16384 (*1) 16384 (*1)
• 8x dedicated prod. LPAR
• 7x dedicated-donating LPAR +
shared pool for non-production
E870C 4 80 16384 (*1) 16384 (*1)
E880 4
192 OLAP
176 OLTP
16384 (*2) 24576 (*2)
E880C 4
192 OLAP
176 OLTP
16384 (*2) 24576 (*2)
Single VM Multi VM Scale-out
yes yes
up to 16
nodes

29. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA on IBM Power Systems – Workload Driven sizing
https://launchpad.support.sap.com/#/notes/2188482/E https://launchpad.support.sap.com/#/notes/2230704/E
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/power-systems.html
29
Cores per
Production LPAR
Maximum Prod.
CPU:RAM ratio
Maximum Prod.
RAM [GB] per LPAR (*2) Limited by SAP Note 2188482
Power 9
Model
Minimal Maximal General SoH/S4H General SoH/S4H Maximum LPARs (options)
S922 4 20
No ratio No ratio
1536 (*2) 4096 (*2)
• 4x dedicated prod. LPAR
• 3x dedicated-donating LPAR +
shared pool for non-production
H922 4 20 1536 (*2) 4096 (*2)
S924 4 24 1536 (*2) 4096 (*2)
H924 4 24 1536 (*2) 4096 (*2)
L922 4 24 1536 (*2) 4096 (*2)
Single VM Multi VM Scale-out
yes yes planned

30. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
SAP HANA on IBM Power Systems – Best Practices
• Additional information can be found in Planning Guide and Implementation Guide:
https://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502
• LPARs for productive SAP HANA workloads must run as dedicated or dedicated-donating
• Other workloads (like non-productive SAP HANA or productive non-HANA) can run in Shared
Processor Pool
• Workload Driven sizing is recommended approach
• SAP HANA on Power is not delivered as appliance – SAP HANA Tailored Datacenter
Integration (TDI) certified storage is required
• All productive SAP HANA LPARs must be able to meet TDI KPIs simultaneously
• See SAP notes on minimal requirements for SAP HANA version and SUSE Linux version
30
https://launchpad.support.sap.com/#/notes/2188482/E
https://launchpad.support.sap.com/#/notes/2055470/E https://launchpad.support.sap.com/#/notes/2230704/E

31. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Agenda
31
• SAP HANA Bare Metal: Appliance Approach
• SAP HANA Tailored Datacenter Integration
• SAP HANA Virtualization
• SAP HANA Stacking Options

32. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Multiple Components One System
SAP HANA Stacking Options
Multiple Components One Database
(can be also same schema)
32
Multi-tenant Database Containers
[GA] MCOD [GA] MDC [GA] MCOS
RHEL/SLES
HANA 01
DB 01
HANA 02
DB 02
RHEL/SLES
HANA 01
DB 01
HANA 03
DB 03
App 01 App 02 App 03
Scale-out
Only for
non-Production
RHEL/SLES
HANA 01
DB 01
HANA 02
DB 02
App 01 App 02
Single-node
Production or
non-Production
Single-node or Scale-out
Production or
non-Production
RHEL/SLES
HANA 01
RHEL/SLES
HANA 01
MDC 04
RHEL/SLES
HANA 01
MDC 02
MDC 03
MDC 01 MDC 01
App 01 App 02 App 03 App 04
Single-node
Production or
non-Production
App 01 App 02
RHEL/SLES
HANA 01
DB 01
SCH 01
SCH 02
Scale-out
Production or
non-Production
RHEL/SLES RHEL/SLES
HANA 01 HANA 01
DB 01
SCHEMA 01
SCHEMA 02
App 01 App 02

33. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Multiple Components One System
Production:
Supported only for single-node
installation: see SAP note 1681092
Non-production: No restrictions
Disadvantages:
• Can lead to resource contention
which might impact performance
It is customer responsibility to properly
size infrastructure (TDI) and to activate
resource management parameters.
SAP HANA Stacking Options
Multiple Components One Database
(can be also same schema)
Production:
Supported only for specific
combinations on “white list”:
• General: see SAP note 1661202
• SoH: see SAP note 1826100
• S/4 HANA: see SAP note 2248291
Non-production: No restrictions
Disadvantages:
• Shared binaries (landscape
implications – upgrade, compatibility)
• No backup/restore ability on schema
level (all or nothing decision)
33
Multi-tenant Database Containers
Production:
All combinations are supported.
Additional guidance is in SAP notes
2104291 (FAQ in attachment),
1666670 (BW) and 2121768 (BW) +
MCOD/MCOS notes
Non-production: No restrictions
Disadvantages:
• Shared binaries (landscape
implications – upgrade, compatibility)
• Some limitations as in SAP note
2096000
[GA] MCOD [GA] MDC [GA] MCOS

34. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
Combining SAP HANA Deployment Options
• SAP HANA stacking is always
associated with compromise
• In general it is best to avoid any
stacking unless explicitly
recommended by SAP
• Infrastructure need to be properly
sized to support stacking without
performance degradation (TDI)
• SAP HANA business continuity
options are on infrastructure level
34
MCOD
MDC
MCOS
SAP HANA
TDI
SAP HANA
Appliance
Virtualization
Stacking
Options
Infrastructure
Options

35. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
35

36. © 2018 IBM Corporation
SAP HANA
Distinguished
Engineers
36
Tomas KROJZL
SAP HANA Distinguished
Engineer, SAP Mentor
IBM Delivery Center CE
Technicka 2995/21
616 00 Brno
Czech Republic
Mobile: +420-731-435-817
tomas_krojzl@cz.ibm.com
Thank You!
Feedback
Don’t forget to fill out the Session Evaluation on the Mobile App!