Hop - Sizing and Hardware Planning Mar2017

SAP HANA on Power Technical Sales Roadmap – Module 7
Sizing and Hardware Planning

IBM Client Center – Montpellier
Sylvie Lemariey
Thomas Mariën
Cesar Beltran
IBM SAP International Competency Center
Kent Wang
BP Technical Enablement, IBM Systems
March 2017
SAP HANA on IBM POWER
Agenda
• SAP HANA Building Blocks

• SAP HANA Sizing and Hardware Planning
• SAP HANA Storage Sizing
Note that the following presentation does not cover HANA 2.0 sizing and hardware planning.
Refer to HoP - SAP HANA 2.0 Presentation Module
2 © 2017 IBM Corporation

IBM Internal and Business Partner Use Only
HANA on POWER Solution Stack
Business Applications
HANA
Middleware
OS
IBM POWER8
Virtualization SYSTEM SOLUTIONS
Server for HANA

LAN / SAN Connectivity
Storage Virtualization
Storage
3 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
UPDATED 07/03/2016
HANA on POWER Building Blocks OSS 2133369 / 2227464 / 2218464
Application Stack: Business Warehouse
Business Warehouse
HANA SPS
(Support Package SPS09 SPS10 SPS11
Stack)
HDB Rev. 94 102.02 110

• SAP BW 7.3 EHP1 powered by SAP HANA
• SAP BW 7.4 powered by SAP HANA
Supported •
•
SAP BW 7.5
BI Java 7.40 for SAP HANA
Applications • Tools (not for BW 7.5):
• Nearline Storage
• Business Intelligence
CLIENT LINUX / AIX

MDC
(Multitenant Database - Supported
Container)
Scaling Single Node Up to 16 nodes
Note: SPS 10 is available as part of an early adopter care

program
UPDATED 07/03/2016
HANA on POWER Building Blocks OSS 2133369 / 2227464 / 2218464
Application Stack: Business Suite

Business Suite
HANA SPS SPS10 SPS11

HDB Rev. 102.02 110
• Business Planning and Consolidation 10.1
• SAP ERP 6.0 EHP7
• SAP SRM 7.0 EHP3
• SAP CRM 7.0 EHP3
• Trigger-Based Replication (SAP Landscape Transformation Replication Server 2.0). DMIS (DATA Migration server) 2011 SP07 / SP08 / SP09
• Application function library SDK for SAP HANA v1.0

• Banking services from SAP v9.0
• SAP Business Planning and Consolidation 10.1
• SAP SCM 7.0 EHP4
• SAP BusinessObjects Business Intelligence platform 4.1 SP 03
•
Supported •
SAP Cost and Revenue Allocation for Financial Products 1.0 SP 02
SAP Customer Activity Repository 1.0 SPS03
Applications •
•
SAP Gateway 2.0
SAP Global Trade Services 11
- • SAP HANA data warehousing foundation SPS02
• SAP HANA dynamic tiering SPS11
• SAP HANA smart data integration 1.0 SP02
• SAP HANA spatial SPS11
• SAP Master Data Governance 7.0
• SAP LT Replication Server 2.0 DMIS 2011 SP 07
• SAP Liquidity Risk Management 1.1 SP 09
• SAP Smart Business Foundation Component 1.0
• SAP Solution Manager 7.2
• SAP Transportation Resource Planning 1.0
CLIENT LINUX / AIX

MDC - Supported
Scaling Single Node
Note: SPS 10 is available as part of an early adopter care
program
UPDATED 07/03/2016
HANA on POWER Building Blocks OSS 2055470
Technical Stack
Production Non Production
Middleware HANA Ready Enterprise Applications (Backup, monitoring, ...)

OS SLES 11 SP4
No Core/RAM Ratio
Server Model Dependent
Min 2 Cores / 64GB RAM
Dedicated / Dedicated Donating. Full
Shared Processor Pool (w/ performance degradation)
system partition or LPAR.
PowerVM (Support for LPM and COD. No support for AME / AMS.)
Server Supported POWER8 Systems. Any POWER7+ and POWER8 Systems
VIO or Direct Attachment
DIMMs must be equally populated across CPU/nodes
1GB (Rec. Admin) / 10GB (Rec. App to DB) / 10GB (Req.
Standard Network components
Scale-out) Connectivity
4 x 8GB FC Ports
Storage Xfs w/ multipath NPIV (TDI or internal disk) Xfs, NFS, GPFS and ext3
HANA 2.0 release, supports only SLES V12 little Endian

Refer to SAP Note 2235581 - SAP HANA Supported Operating Systems.pdf
UPDATED 07/03/2016
Production Systems: Memory & CPU / LPAR

SCM (Single Chip Module) DCM (Dual Chip Module)
Be sure to Server
verify Min-Max E880 E870 E850 S824L S824 S822L S822
Model
configurations
Min Cores 4
based on
latest testing Max Cores 96 80 32 24 24 24 20
Min RAM 128 GB
Application SAP Business Warehouse

SPS SPS09 SPS10 SPS11 Any
Max RAM 3.0 TB 4.8 TB 1 TB (Server Capacity Dependent)
GB / Core 50GB /
32GB / Core 32GB / Core
Ratio Core
Application SAP Business Suite

SPS Any
Max RAM 9.0 TB (Server Capacity Dependent)
GB / Core
96GB / Core
Ratio
Note: Certified and Supported SAP HANA® Hardware Directory
UPDATED 07/03/2016
Production Systems: Memory & CPU Limitations / LPAR
Memory & CPU / LPAR (PRD)

9216 96
Be sure to 8192
verify Min-Max 80
7168
configurations
RAM
based on 6144 64
latest testing – 5120
CORES
48
this is an older 4096
chart and
3072 32
shows 8 vs 4
min cores per 2048
16
LPAR. 1024
0 0
E880 E870 E850 S824L S824 S822L S822
Min Cores 8 8 8 8 8 8 8
Max Cores 96 80 32 24 24 24 20
MIN Ram 128 128 128 128 128 128 128
BW SPS09 Max RAM 3072 2560 1024 768 768 768 640
BW SPS10 Max RAM 3072 2560 1024 768 768 768 640
BW SPS11 Max RAM 4800 4000 1024 768 768 768 640
BS Max RAM 9216 7680 3072 2304 2304 2304 1920
SERVER MODEL
UPDATED 07/03/2016
Production Systems: Multiple LPARS per physical host – with at least one production system.
SCM (Single Chip Module) DCM (Dual Chip Module)
Server Model E880 E870 E850 S824L S824 S822 S822L
PRD Mode 8 Concurrent production LPARS 4 Concurrent production LPARS
7 Concurrent PRD LPARs + 1 Shared 3 Concurrent PRD LPARs + 1 Shared

Mixed Mode
Processor Pool for n-PRD Processor Pool for nPRD.
N-PRD mode No imposed limitation
Virtualization PowerVM. Dedicated or Dedicated Donating for PRD. Shared Processor Pools for n-PRD.
Pre-Req. (DPO) Dynamic Platform Optimizer > Uniform Topology
VIO Optional and excluded from the above lpar count (Recomended: Dedicated Donating).

HANA Sizing and Hardware Planning

The disruptive nature of SAP HANA
Changes
No Changes
Frontends  New infrastructure
 At frontends mandatory to run SAP
 At application server HANA
infrastructure  Different sizing for
Application Servers
=> HANA infrastructure
Any OS
 Re-use of available  Migration of database
APP APP APP APP
application servers to SAP HANA required
 Sizing of application
servers remains Partly necessary
valid  Data model adoptions
Any DB / HANA migration HANA /  Custom extensions
Any OS Linux

The Disruptive Nature of SAP HANA

Application Workload

Hardware Planning Sizing
Overview
Hardware Design
SW Setup
Compliance Verification

Four Major HANA Sizing Scenarios
 Business Warehouse on HANA

 Suite on HANA
 S/4HANA
 BW/4HANA (new since October 2016)
© 2017 IBM Corporation
Sizing Overview
 Sizing Factors:
– Memory (Dominant factor)
– CPU (No of cores is dependent on the Memory Size of HANA Node/LPAR)
 Sizing Approach
– For Migration Sizing, SAP provides two different Sizing Reports (BW or SoH).
• For both reports an ABAP runs on the existing SAP System and creates a
sizing document.
• The content of both sizing documents provides a detailed description of
HANA DB memory requirements.
– Each Initial Sizing should be done using the HANA version of the SAP
Quicksizer (mandatory)
– Rule of thumb.
• HANA needs about 50% the size of an existing classic DB for its memory
Example: DB = 1TB, HANA Node/LPAR size = 500 GB
Sizing Process and Workflow
HANA Sizing is a so-called Black Box Approach.

Sizing Input (by SAP Sizing Report or SAP Quicksizer) will be used by SAP Algorithm to calculate HANA
requirements. The result is documented by Sizing Report or Quicksizer. Based on this result, each HW
Vendor is able to do sizing and HWIBM Internal. and Business Partner Use Only
Mapping
Migration Sizing - HANA DB
Optional
 Memory sizing Consists of:

– Data and Working Memory
• Depending on the amount of Data, this usually is the
largest share on total Hana Memory. It will be analysed
and estimated by running the Sizing Reports.
– Operating System Sizing Report
• Memory for Operating System depends on the size of
the Node/LPAR.
• It is not determined at the Sizing report, and is reducing
the available memory of a Node/LPAR.
– Caches & Services
• Is always calculated with a fix amount of 50GB and is
already included at the sizing reports.
– Growth
• Grow is an option that can be activated when starting
the sizing report.
• We recommend include at least a small share of
Memory for Grow at your sizing.
OS Not considered in Report
Migration Sizing
HANA Sizing Components Overview
This table shows where to get sizing estimates, depending on the Sizing Scenario. © 2017 IBM Corporation
18
CPU Sizing by Core to Memory Ratios
• The primary sizing factor for HANA is the Memory (RAM).
• Of course the HANA DB Node needs CPU capacity as well.
• At the current HANA DB CPU sizing the CPU requirement is related to the DB Mem size.
• As larger the Database as lager the RAM as more CPU is need.
• The calculation method used is the so called “Core to Memory” ratio (CtM).
For production: Power8 servers with at least 2 Sockets

For development and testing: Power7+ servers, min 2 cores per HANA LPAR, no CtM mandatory
Migration Sizing
HANA LPAR Sizing Limits
Example of Initial HANA

LPAR Solution Design
This simplified example is to demonstrate

virtualization, distribution of memory and
cores, Vios and donating cores.
(Remaining Capacity is an unused LPAR

that can be used as App Server or other
SAP Systems)

Migration Sizing
List Eligible Power Servers – BW Production Systems

Migration Sizing
List Eligible Power Servers – SoH Production Systems

Migration Sizing - OS Estimated HANA DB Size (GB)
 Memory requirement of the OS depends on the Reserved for OS (GB)

Estimated LPAR Size (GB)
Size of Node/LPAR.
 HANA cannot allocate the complete physical 244 12 256
memory of each node. Some space must be 492 20 512
740 28 768
reserved for the operating system and other 989 35 1024
services. 1485 51 1536
1982 66 2048
 As a rule, 10% of the first 64 GB and another 3% 2975 97 3072
of the remaining memory will be reserved 3969 127 4096
exclusively for OS purposes. 4962 158 5120
5955 189 6144
 To determine required LPAR size take the row 6948 220 7168
7942 250 8192
closest to your estimated HANA DB size. 8935 281 9216
– example: for HANA DB of 900GB = 1024 9928 312 10240
LPAR size 10922 342 11264
11915 373 12288
 You do not need to include additional OS 12908 404 13312
memory if you are only requested to propose a 13901 435 14336
14895 465 15360
HANA Node (vs the size of the HANA DB) with a 15888 496 16384
fixed amount of memory
Migration Sizing
Power Sizing/Mapping Tool
https://www.ibm.com/partnerworld/wps/sizing/protect/sizingguide/ViewSG?guide_id=sgq84752020041706102
Planning and Implementation Guides

http://www.ibm.com/support/techdocs/atsmastr.nsf/webindex/wp102502
Migration Sizing - Business Warehouse Example
 Estimated HANA DB Size:

= HANA DB Memory estimate + Cache + Room to Grow
= 800 + 50 + 139 = 989GB
 Additional to the Estimated HANA DB size you need to calculate memory
for the Operating System. Estimated LPAR Size:
= HANA DB Memory estimate + Cache+ Room to Grow + Size of OS
= 800 + 50 + 139 + 35 = 1024GB
 CPU Sizing is based on a Core to Memory Ratio
. Assuming S824 w/ 32GB/Core for production system.
= Max 1TB at 24 Cores
 BW Application Server Sizing
– HANA migration has only a low impact on the Application Server Tier.
– From a sizing point, the Application servers remains unchanged.
Migration Sizing:
Business Warehouse Example w/ Report
OSS Note: 1736976 - Sizing Report for BW on HANA
 In the example shown: the estimated HANA DB

Size after migration is 202 GB (Includes 50GB for
Cache).
 Assuming you setup a node or LPAR of 256GB the
OS would consume 12GB from the total LPAR
Memory.
– Node/LPAR Size = 256 GB
– Operating System = 12 GB
– HANA DB = 202 GB
 Free Memory
Memory Sizing
= 256 – 12 – 202 = 42 GB
 Following the core to memory ratio of 1:32 you
need 256GB/32 = 8 Cores.
 For E870 or E880 server - CtM is 1:50 = 5 Cores
Migration Sizing
Sizing Report for Business Warehouse on HANA (Multi Node)
OSS Note: 1736976 - Sizing Report for BW on HANA
 POWER8: Each node has a maximum RAM size below or equal to the maximum RAM allowed per LPAR.
Please refer to SAP note 2188482 for details.
 POWER8: The sum of total RAM of the nodes participating is equal or bigger than the value of 'Memory
Requirement (Minimum Total)' from the sizing report.
 About the size …
– Calculated in ABAP
– Based on Sample Data
– Omits indexes, temporary
space, …
Memory Sizing Selected Node Size
Rule of Thumb sizing for Business Warehouse
RAW DATA
[2.5TB]
COMPRESSED
MEMORY
OLAP DATA 0.5:1
[1TB]
[512 GB]
 As a rule of thumb, physical HANA memory requirements are approximately 0.5*Raw DB Size
Points to Note on Sizing Reports
• Scale Up and Scale Out
– Scale Up: HANA DB fits into one Node/LPAR
– Scale Out: HANA DB does not fit in one Node/LPAR must be distributed over
several LPARs / also if the memory requirement is higher than the preselected
memory size
– To avoid Scale Out sizing report, choose the largest possible Node size (saves
50GB of cache per server)
– The BW sizing report allows analyzing of existing HANA systems, verifies sizing
estimates pre- and after migration and helps migration to other Nodes or LPARs
– Initial Sizing = Sizing from scratch (also called Greenfeld sizing)
– Initial Sizing of HANA DB can be done by SAP or experienced IBMer usually with
the HANA version of the SAP Quicksizer (QS)… https: //service.sap.com/quicksizer
– For SAP HANA server memory sizing you need input on the Quicksizer tables 5 + 6
(InfoCubes (Cube) and DataStore Objects (DSO) )
BW/4 HANA Migration
• BW/4 HANA Initial Sizing
– Have information on the largest InfoProviders of the planned systems (record
structures, line counts)
– Create a SAP Quicksizer project, HANA version – select “SAP NetWeaver BW
Powered by SAP HANA” and enter values into the Quicksizer form
– Use only table 6 for DSO objects to enter information on InfoProviders
– Do not use table 5 (InfoCubes).
– The Quicksizer result can be used as an estimate for the BW/4 HANA system
• BW/4 HANA Migration Sizing
– Refer to note 2296290 and derive sizing requirements for the current BW system
running on BW on HANA sizing report /SDF/HANA_BW_SIZING
– Sizing results can be used to estimate the resource requirements for the BW/4
HANA system as well
Migration Sizing - Suite on HANA Example w/ Report
OSS Note: 1872170 - Suite on HANA - S/4 sizing report
 The estimated HANA DB Size after

migration is 765 GB (Includes 50 GB
for Services).
 Estimated LPAR size:
HDB size + OS Size
= 765 + 35 = 800GB
 Assuming you anticipate for growth,
you may want to recommend a total
size of 1024GB.
 Using a Ratio of 1:96 for SoH
1024 / 96 ~ 11 Cores
Memory Sizing
Migration Sizing - Suite on HANA Detailed Report
OSS Note: 1872170 - Suite on HANA - S/4 sizing report
 Hybrid LOB: Large Object (LOB) is a data type used to store large records (Typically texts,
images, audio, …) and is often not well compressed. By default, columns of data type LOB are
no longer fully loaded to memory on first access. Consequently only LOB data which is needed,
is loaded to memory. For sizing, the assumption is made, by the report that 20% of the Data
stored on disk can be loaded to memory at the same time.
 Anticipated requirement
after clean up shows the
memory consumption that
can be achieved if some
data volume management
projects are implemented
on the system. (Data
Aging, …)
 Example does not include
growth or OS
HANA Storage Sizing

Storage Sizing
 SAP HANA uses storage for several purposes:
– The SAP HANA installation. This directory tree contains the run-time binaries, installation scripts and other
support scripts. In addition, this directory tree contains the SAP HANA configuration files, and is also the default
location for storing trace files and profiles. On distributed systems, it is created on each of the hosts.
• 𝑆𝑖𝑧𝑒𝑖𝑛𝑠𝑡𝑟𝑎𝑙𝑙𝑎𝑡𝑖𝑜𝑛(𝑠𝑖𝑛𝑔𝑙𝑒 𝑛𝑜𝑑𝑒) = 𝑀𝐼𝑁 1 ∗ 𝑅𝐴𝑀; 1𝑇𝐵
• 𝑆𝑖𝑧𝑒𝑖𝑛𝑠𝑡𝑟𝑎𝑙𝑙𝑎𝑡𝑖𝑜𝑛(𝑠𝑐𝑎𝑙𝑒−𝑜𝑢𝑡) = 1 ∗ 𝑅𝐴𝑀 𝑜𝑓 𝑊𝑜𝑟𝑘𝑒𝑟 (𝑝𝑒𝑟 4 𝑤𝑜𝑟𝑘𝑒𝑟 𝑁𝑜𝑑𝑒𝑠)
– Backups. Regularly scheduled backups are written to storage in configurable block sizes up to 64 MB.
• 𝑆𝑖𝑧𝑒𝑏𝑎𝑐𝑘𝑢𝑝𝑠 ≥ 𝑆𝑖𝑧𝑒𝑑𝑎𝑡𝑎 + 𝑆𝑖𝑧𝑒𝑟𝑒𝑑𝑜𝑙𝑜𝑔
– Data. SAP HANA persists a copy of the in-memory data, by writing changed data in the form of so-called savepoint
blocks to free file positions, using I/O operations from 4 KB to 16 MB (up to 64 MB when considering super blocks)
depending on the data usage type and number of free blocks. Each SAP HANA service (process) separately writes to
its own savepoint files, every five minutes by default.
• 𝑆𝑖𝑧𝑒𝑑𝑎𝑡𝑎 = 1.2 ∗ 𝑛𝑒𝑡 𝑑𝑖𝑠𝑘 𝑠𝑝𝑎𝑐𝑒 𝑓𝑜𝑟 𝑑𝑎𝑡𝑎 Use Sizing Reports
– Redo Log. To ensure the recovery of the database with zero data loss in case of faults, SAP HANA records each
transaction in the form of a so-called redo log entry. Each SAP HANA service separately writes its own redo-log files.
Typical block-write sizes range from 4KB to 1MB.
• 𝑆𝑌𝑆𝑇𝐸𝑀 ≤ 512𝐺𝐵 𝑆𝑖𝑧𝑒𝑟𝑒𝑑𝑜𝑙𝑜𝑔 = 1.2 ∗ 𝑅𝐴𝑀
 As a rule of thumb, disk size = ~2 x RAM (assuming 1 copy of Backup)
• 𝑆𝑌𝑆𝑇𝐸𝑀 > 512𝐺𝐵 𝑆𝑖𝑧𝑒𝑟𝑒𝑑𝑜𝑙𝑜𝑔(𝑚𝑖𝑛) = 512𝐺𝐵
Storage Configuration Guidelines
 Storage and SAN-Adapters have to be configured to comply with SAP Tailored Data Center Integration
(TDI) performance KPIs. (Min 8GB SAN Adapters).
 Disk sizing / layout as HANA-DB persistency is not volume, but I/O driven.
 Overall disk capacity is dominated by the number of DB-backups kept on disk.
 A mix of HDD for DATA and SSD for LOG is used, see:
– SAPmagic Tool
– Storage Architecture and Configuration Guide for SAP HANA TDI
 Non-Production and less performance critical systems can be built using internal disks.
 Recommended IBM Storage System Combinations (Production):
Storage
Virtualization SAP HANA data SAP HANA log SAP HANA data SAP HANA log
System
FlashSystem /
SVC Storwize Storwize HDD SSD
(Storwize)
FlashSystem / DS8000 HDD SSD
SVC XIV
(XIV)
DS8800 / XIV Module Module
SVC DS8800
(FlashSystem)
SVC FlashSystem FlashSystem Flash
Flash Card Flash Card
System
© 2017 IBM Corporation

SAPmagic supports HANA TDI
This tab configures IBM Storage Systems for one SAP HANA TDI systems.
In column C please specify your landscape: Chose load performance with care. Use default "Standard"
The HANA performance does not depend on the DATA storage system (and limited on the LOG storage system).
The DATA storage type just effects boot up (load) performance.
Select the types of storage systems, SVC usage, number of HANA nodes and RAM per HANA node,
as well as disk types in case DS8000 or Storwize are used.
If SVC is not used, DS8000 is configured for DATA and Log.
IF SVC stretched cluster is used the configured storage systems (and capacity) will be doubled due to mirroring.
SAP requires DATA capacity = 3 * RAM capacity, and LOG capacity = 1 * RAM capacity
All HDD and SSD need to be configured as RAID 5 (7+1)
Field "Use same system for DATA and LOG" is only valid for DS8870 (as of today)
SAP HANA Load performance (KPI) Standard
Storage Type for DATA Storwize V7000 Storwize V7000 Number of SVC nodes (pairs) 4 (2)
Storage Type for LOG FlashSystem 820 20TB FlashSystem 820 20TB Number of Storage Systems for DATA 4
Use same system for DATA and LOG No FALSE Number of disks per Storage System for DATA 64
Use SVC Stretched-Cluster
Number of HANA nodes 8 Number of Storage Systems for LOG 2
RAM per HANA node [in GB] 1024 Number of disk per Storage System for Log n/a
Type of Disk for DATA HDD 10K, 900GB, 2.5"
Type of Disk for LOG n/a
SAP HANA Sizing and Hardware Planning Guides - Summary
The following are useful guides to assist in sizing your SAP HANA Solution on IBM Systems:
• SAP HANA on IBM Power Systems and IBM System Storage – Guides
– Techdocs: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502
• IBM System Storage Architecture and Configuration Guide for SAP HANA TDI (tailored
datacenter integration) V2.10
– Techdocs: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102347
• IBM System Storage sizing guideline for SAP HANA TDI, V3.1
– Techdocs: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10859
• SLES 11.x for SAP Applications Configuration Guide for SAP HANA (x86 and POWER)
– Attached to SAP Note 1944799 –
“SAP HANA Guidelines for SLES Operating System Installation”

HANA / POWER OSS Notes
• 1736976 - Sizing Report for BW on HANA

• 1872170 - Suite on HANA - S/4 sizing report
• 1900823 - SAP HANA Storage Connector API
• 1903576 - SAN HANA DB: additional main memory in exceptional cases
• 1943937 - Hardware Configuration Check Tool - Central Note
• 1953429 - SAP HANA and SAP NetWeaver AS ABAP on one Server
• 2055470 - HANA on POWER Planning and Installation specifics
• 2130682 - SAP HANA on IBM Power Systems: Documentation
• 2133369 - SAP HANA on IBM Power Systems: Central Release Note for SPS 09 and SPS 10
• 2188482 - SAP HANA on IBM Power Systems: Allowed Hardware
• 2218464 - Supported products when running SAP HANA on IBM Power Systems
• 2227464 - SAP HANA Platform SPS 11 Release Note
• 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host
• 2240716 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP4
• Also look for the latest SAP HANA Notes on the SAP Site.

Sizing and Hardware Planning - Summary
• Sizing and hardware planning for SAP HANA is a moving target as specifications continually
change with product announcements and testing results
• Follow the Sizing process to ensure accurate results
• Understand the process guidelines and specific scenarios
• It is essential that any sizing be checked with the latest test results, sizing tools and SAP
Notes
• Get help from SAP or an experienced IBM professional

End of Module 7
Thank You
41 41 © 2017 IBM Corporation

IBM System Storage sizing guideline for SAP HANA TDI

Reasonable storage configs …
Storage Virtualization SAP HANA data SAP HANA log
Storwize FlashSystem
Spectrum Virtualize XIV FlashSystem
(SVC) DS8800 FlashSystem
FlashSystem FlashSystem
Storage System SAP HANA data SAP HANA log

Storwize HDD SSD
XIV Module Module
DS8800 HDD SSD (HDD)
FlashSystem Module Module


Hop - Sizing and Hardware Planning Mar2017

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Hop - Sizing and Hardware Planning Mar2017

Hochgeladen von

Copyright:

Verfügbare Formate

SAP HANA on Power Technical Sales Roadmap – Module 7

Sizing and Hardware Planning

IBM SAP International Competency Center

• SAP HANA Building Blocks

2 © 2017 IBM Corporation

Server for HANA

Application Stack: Business Warehouse

HDB Rev. 94 102.02 110

CLIENT LINUX / AIX

Scaling Single Node Up to 16 nodes

Note: SPS 10 is available as part of an early adopter care

Application Stack: Business Suite

HANA SPS SPS10 SPS11

• Application function library SDK for SAP HANA v1.0

CLIENT LINUX / AIX

HANA on POWER Building Blocks OSS 2055470

Middleware HANA Ready Enterprise Applications (Backup, monitoring, ...)

HANA 2.0 release, supports only SLES V12 little Endian

Production Systems: Memory & CPU / LPAR

Min RAM 128 GB

Application SAP Business Warehouse

Application SAP Business Suite

Production Systems: Memory & CPU Limitations / LPAR

Memory & CPU / LPAR (PRD)

latest testing – 5120

SCM (Single Chip Module) DCM (Dual Chip Module)

Server Model E880 E870 E850 S824L S824 S822 S822L

PRD Mode 8 Concurrent production LPARS 4 Concurrent production LPARS

7 Concurrent PRD LPARs + 1 Shared 3 Concurrent PRD LPARs + 1 Shared

N-PRD mode No imposed limitation

Pre-Req. (DPO) Dynamic Platform Optimizer > Uniform Topology

9 © 2017 IBM Corporation

10 © 2017 IBM Corporation

The disruptive nature of SAP HANA

11 © 2017 IBM Corporation

The Disruptive Nature of SAP HANA

12 © 2017 IBM Corporation

13 © 2017 IBM Corporation

 Business Warehouse on HANA

HANA Sizing is a so-called Black Box Approach.

 Memory sizing Consists of:

For production: Power8 servers with at least 2 Sockets

Example of Initial HANA

This simplified example is to demonstrate

(Remaining Capacity is an unused LPAR

20 © 2017 IBM Corporation

21 © 2017 IBM Corporation

22 © 2017 IBM Corporation

 Memory requirement of the OS depends on the Reserved for OS (GB)

Planning and Implementation Guides

 Estimated HANA DB Size:

 In the example shown: the estimated HANA DB

 The estimated HANA DB Size after

33 © 2017 IBM Corporation

© 2017 IBM Corporation

SAP HANA Load performance (KPI) Standard

SAP HANA Sizing and Hardware Planning Guides - Summary

38 © 2017 IBM Corporation

• 1736976 - Sizing Report for BW on HANA

39 © 2017 IBM Corporation

• Follow the Sizing process to ensure accurate results

• Understand the process guidelines and specific scenarios

• Get help from SAP or an experienced IBM professional

40 © 2017 IBM Corporation