sap hana on ibm power systems and ibm system …...production and less critical non-production sap...

SAP HANA on IBM Power Systems

and IBM System Storage

Planning Guide

IBM Deutschland Research amp Development GmbH Created on July 8 2014 ndash Version 00

Last modified on July 08th 2019 ndash Version 473 copy Copyright IBM Corporation 2020

2

IBM Systems Solution for SAP HANA on POWER and IBM System Storage copy Copyright IBM Corporation 2019

Edition Notice and Version Information copy Copyright IBM Corporation 2020 All Rights Reserved US Government Users Restricted Rights ndash Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp All trademarks or registered trademarks mentioned herein are the property of their respective holders IBM Corporation Systems and Technology Group Route 100 Somers NY 10589 Edition Notice this is version 473 of this document Focus SAP HANA Scale-up and Scale-out solutions Target

bull SAP HANA 2

bull SAP HANA Platform Edition ndash SPS11 and above

bull SAP HANA version for IBM Power Systems architecture SPS 09 or SPS 10

Doc Version Changes 12 ndash 18 Changes documented up to version 21

19 ndash 25 Changes documented up to version 31

30 ndash 33 Changes documented up to version 4 40 ndash 42 Changes documented up to version 43


46 (Nov062019

Add additional Information about Migration (SAP Note updates) Re-emphasize relaxations based on SAPrsquos TDI 5 approach LPM Mand SPLPAR Full SMT 8 support for all core counts

47 (July142020

Adding ldquoServiceReportrdquo to Support chapter (RAS setting validation + correction in Linux) New Sizing and Mapping chapter Easier TDI5 planning workflow First updates for SPLPAR vPMEM vNIC exploitation

Note Before using this information and the product it supports be sure to read the general information under rdquoCopyrights and Trademarksrdquo on page 52 as well as ldquoDisclaimer and Special Noticesrdquo on page 52

3


Preface

Running SAP HANA on IBM Power Systems offers customers a consistent platform for their HANA-based and traditional applications best-in-class performance resilience for critical workloads and most flexible infrastructure Existing IT assets - servers storage as well as skills and operation procedures - can easily be (re-)used leveraging the SAP HANA Tailored Data Center (TDI) concept to its maximum

About This Document

This document is intended for architects and specialists planning a SAP HANAreg on POWERreg deployment It describes the design considerations for hardware networking and software components of the SAP HANA on POWER solution stack This guide does not replace existing SAP HANA documentation and sizing guides It serves as a supplement to the existing SAP HANA documentation and SAP Sizing methods to provide specific guidance on how to meet all SAP requirements when running SAP HANA on IBM Power Systemstrade IBM System Storagereg IBM PowerVMreg and Linux Operating System It describes the requirements for LAN and external SAN topologies For special topics own documentation is maintained and referenced at the end IBM processes and contacts are introduced which help to obtain a valid hardware mapping based on SAP sizing for SAP HANA IBM employees can access the ISICC SAP HANA on Power Systems Community (IBM only) for up-to-date materials complementary to this guide The most recent document version can be downloaded from IBM TechDocs httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102502 Feel free to provide feedback and change requests for this document via email to enableSAPdeibmcom

4


Table of Contents

Introduction 7

The Planning Process 8

SAP Sizing for SAP HANA on POWER 9

Introduction 9

HANA Memory Sizing 10

HANA CPU Sizing 10

SAP HANA Sizing Types Brownfield or Greenfield 10

SAP HANA Sizing Cases OLAP vs OLTP 11

Summary SAP Sizing options 11

SAP References and Notes for Sizing 12

Sizing Report Best Practices 12

Growth and Timeline of your Database 12

Brownfield OLAP Sizing (BW) 12

Brownfield S4 or Suite on HANA Sizing (with Sizing Report) 15

Greenfield S4 or Suite on HANA Sizing (with HANA Quicksizer) 17

Greenfield BW Sizing with the SAP Quickiszer 20

Sizing related technologies 21

SAP HANA Data Temperatures reduce the sizing result of CPU and Memory 21

Native Storage Extension (NSE) Warm Store Configuration Rules 21

Quick Reference Get SAP HANA Sizing from SAP 23

Links References and Tools 23

Decide on Power and SAP features implemented to reduce Hardware or accelerate your workload 24

SAP HANA startup acceleration 24

SAP HANA in Shared CPU Pools 24

Introduction into Shared Processor Pools 25

SAP HANA Performance Observations 26

Get to the right PowerVM SPLPAR settings for an SAP HANA LPAR 26

Monitoring SAP HANA in Shared Pools 27

Eco System and Landscape aspects 27

Mapping SAP Sizing Output to IBM Power Systems Configurations 27

SAP HANA deployment options and IBM Power Server 28

Quick Reference Find valid IBM Power Systems options 31


Mapping SAP IO KPIs to a SAN Storage Design 32

Planning Considerations for a valid Storage Type 32

Background SAP HANA filesystems and SAN storage33

Additional Storage Sizing Considerations for Backup DR and HA 34

Additional Planning Considerations for SAP HANA scale-out installations 34

Quick Reference Find valid Storage Subsystem 35


5


SAP HANA Connectivity 35

Operating System 39

Software and Operating System 39

HWCCT validation (deprecated) 39

SLES 11 considerations 39

SLES 12 and SLES 15 considerations 40

RHEL considerations 40

Quick Reference OS Planning 40


File System 40

Planning Considerations for XFS with Multi-pathing 41

Planning Considerations for IBM Spectrum Scale 41

Quick Reference File System Definition 41


Additional Considerations for Large OLTP Installations 42

SAP HANA Software 42

SAP HANA tuning 42

How to check the PAM 42

Scale-out deployments 42

Quick Reference SAP HANA Software 42


Verification42

Support and Services 43

Getting help and information from the World Wide Web for IBM products 43

Getting help and information for IBM Server and Storage mapping 43

Standard Support Flow 43

IBM Services Support and Operation offerings for SAP HANA on POWER 44

Migration Support and Services 44

Planning and Installation 45

IBM Total Solution Support 45

Referenced documents 47

Copyrights and Trademarks 52

Disclaimer and Special Notices 52

Figures

Figure 1 SAP HANA on IBM Power Servers Planning Process 8

6


Figure 2 Brownfield HANA Memory Sizing 10

Figure 3 Start the sizing report 12

Figure 4 general input parameters BW Sizing Report 13

Figure 5 BW Sizing report precision 13

Figure 6 Customized Memory Configuration 13

Figure 7 Sample BW sizing report output 14

Figure 8 CPU requirement Class M caused by Data load peaks 14

Figure 9 Start the S4Business Suite Sizing Report 15

Figure 10 Sample ERP Sizing Report output 16

Figure 11 CPU consumption classic DB vs HANA for S4 16

Figure 12 SAP HANA Quicksizer Versions 17

Figure 13 Create Quicksizer Project17

Figure 14 Quicksizer Protfolio - Select SAP Solution(s) 18

Figure 15 Sample sizing Sales and Services 19

Figure 16 Sample Quicksizer input for Sales and Services 19

Figure 17 Sample Sales and Service SAPS 19

Figure 18Sample Sales and Service Memory 19

Figure 19 Sample Sales and Service Growth output 19

Figure 20 Select the solution to be sized 20

Figure 21 Size the Appserver Tier by number of users 20

Figure 22 Impact of objects upload 21

Figure 23 Advanced Data Store 21

Figure 24 Quick Reference Get SAP HANA Sizing from SAP 23

Figure 25 Typical Example of Workload behavior in Shared Processor LPAR vs Dedicated LPAR 25

Figure 26 NMON LPAR utilization profiles (CPU user + system) of independent26

Figure 27 PowerVM LPAR types 28

Figure 28 SAP HANA Category and Features in eConfig 30

Figure 29 Quick Reference Mapping SAP Sizing Output to IBM Power Systems 31

Figure 30 Quick Reference Find valid Storage Subsystem 35

Figure 31 Standard Support ownership of SAP HANA and Hardware Stack 43

Figure 32 Support Flow for HANA on Power Solution Stack 44

Figure 33 IBM Services for SAP HANA on POWER environments 46

Tables

Table 1 Minimum Single-Host SAP HANA IO connectivity for production (floor configuration as

required by SAP) 37

Table 2 Minimum Multi-Host SAP HANA IO connectivity per Server (floor configuration as required

by SAP) 38

7


Introduction SAP HANA comprises several functional modules whose core is the SAP in-memory database These are deployed on top of a hardware and software stack which should be planned according to this Planning Guide Initially SAP supported only the appliance delivery method for HANA in which certified hardware partners offer a HANA appliance SAP HANA TDI (Tailored Data Center) opened the appliance deployment model to provide customers with more flexibility and choices Customers can choose the matching IBM Power Server model - along with the best matching storage components from a large selection of suitable TDI-certified hardware They may reuse existing hardware while keeping the operational processes for these This possibility ndash or alternatively purchase of incremental special priced HANA Power Systems - significantly lowers the costs and allows for easier integration of SAP HANA based solutions in a customer data center During introduction of SAP HANA or the transition of older solutions to eg S4HANA the available POWER capacity can be easily be re-allocated to the growing HANA-driven workloads or installed on a partition using available capacity or Capacity Upgrade on Demand resources The same applies if customers transition AIXIBM I environments to new Linux on Power platforms SAP HANA on IBM Power Server has been introduced with TDI Phase 4 in 2015 Since then the SAP solution portfolio of new (S4HANA BWHANA) as well as many traditional Business Suite applications have become available IBM Power Systems have been integral part of the SAP HANA 20 announcement in 2016 including all the new technology features coming with this new DB version In September 2017 SAP SE announced TDI Phase 5 The most significant impact on platforms is the switch from rigid Core to Memory ratios (still documented as ldquoreference configurationrdquo by SAP) to a SAPS based sizing derived from the data footprint of HANA and targeted workload Basically this allows Power Systems to become more efficiently from a TCO aspect the more intensively sharing ad virtualization technologies are used In 2019 SAP SE in collaboration with IBM supports now also the exploitation of Shared Pool LPARs Virtual Persistent Memory and other acceleration and sharing technologies outlined later

8


The Planning Process To give an overview of this documentation Figure 1 describes the structure of this paper

Figure 1 SAP HANA on IBM Power Servers Planning Process

The orange part represents the initial SAP owned sizing process as described in chapter ldquoError Reference source not foundrdquo which delivers information on the SAP HANA sizing methodologies and tools including Best Practices on creating reports in an iterative process matching best the actual business needs Further it helps to identify the appropriate planning resources provided by SAP

Eco-System and SAP Landscape planning

Identify and Layout Storage and Server System(s) configurations

Validate Configuration

Execute the SAP workload sizing (TDIv5)

Complete SAP HANA Quicksizer process

Apply SAP tools versus existing DB

Apply recommended Best Practices to optimize the Server utilization

OS System deployment

Start with the SAPS and Data-Footprint the Storage and Server mapping

HANA Installation

Refine your business needs based on available technologies of IBM and SAP

Determine Connectivity requirements and derive adapter requirements

SAP Sizing

Hardware and LPAR Mapping

Determine HANA LPAR size and IBM Power server model

9


Since 2018 the black and white steps became important to ensure to meet the level of resiliency and performance while reducing the SAP HANA LPAR footprint The blue parts refer to the IBM specific SAP HANA on POWER and IBM System Storage hardware mapping and layout steps The green parts represent the Operating System (OS) and SAP HANA software setup described in chapter ldquoSoftware and Operating Systemrdquo The grey box describes the validation While before TDI5 there was a mandatory verification step this is now optional Warnings and errors thrown by HWCCT and HCoT are indicators but not necessarily issues In the meantime the field has advanced validation tools to ensure a good start experience Support channels IBM service offering details and contacts are summarized in chapter ldquoSupport and Servicesrdquo IBM provides additional guides such as an Advanced Operation Guide High Availability IO Configurations and acceleration options etc on SAP HANA on IBM Power Systems and IBM System Storage - Guides

SAP Sizing for SAP HANA on POWER SAP Sizing is a building block to translate SAP business requirements into physical andor logical hardware As a result of the sizing process the HANA ldquosizing estimaterdquo specifies vendor and platform independent SAP HANA system requirements The SAP Sizing is an iterative process Iterative means that after getting the first sizing result more iterations of sizing with corrected sizing input will improve the accuracy to the benefit of resource savings What a SAP HANA sizing includes

bull The HANA DB Sizing process covers only the HANA database

bull A HANA DB sizing result includes the memory SAPS and disk capacity for a fully dedicated deployment

bull Platform in depended methodology What a SAP HANA sizing does not include

bull It neither includes landscape (app-servers pre-PROD stages) nor resiliency nor sharing or virtualization aspects This will be covered later

bull The mapping to an LPAR andor Server

bull IBM Power and Spectrum Storage specific

Introduction

The following chapters provide an entry point to get a basic understanding of SAP Memory and CPU sizing in conjunction with different sizing types and workloads

10


HANA Memory Sizing

System sizing for SAP HANA and its configuration is dominated by the physical memory demand of the HANA instance respectively the amount of ldquohotrdquo business data to be maintained in memory versus warm or cold data which remain on disk or other sources Putting an iterative sizing approach followed by a customer specific landscape hardware mapping can hence reduce the HANA footprint dramatically As a first very rough starting point (followed by an iterative sizing approach) the compressed HANA data in-memory footprint is 14th of the uncompressed source business data For internal processing and temporary work area a HANA system requires the same amount of physical memory resulting in an estimated physical memory amount of frac12 of uncompressed source SAP database size With recent SAP and IBM innovations in special Native Storage Extensions and the TDIv5 Workload sizing and the experiences resulting in Best Practices SAP and IBM provide as a Service the memory footprint must be reduced to the actual needs what is relevant for IaaS as well as on Premise deployments to save cost

Figure 2 Brownfield HANA Memory Sizing

HANA CPU Sizing

Before the Tailored Data Integration Phase 5 a workload independent ratio between Cores and Memory was used anticipating constant worst case workloads With the introduction of TDI Phase 5 HANA CPU sizing is customer workload-driven To further reduce the footprint Shared Pool LPARs NSE and Services are highly recommended to reduce cost

SAP HANA Sizing Types Brownfield or Greenfield

The first step in a sizing is to determine the right sizing methodology ndash Greenfield or Brownfield In general a Brownfield sizing is done based on an existing SAP installation on HANA or any DB (eg DB2 Oracle hellip) A Brownfield sizing is always preferred as the sizing result is more accurate based on analyzing the existing system This method applies to the following scenarios

bull plan a hardware upgrade

bull change or migration of an existing HANA Instance

bull migration from ANY DB to SAP HANA

Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11


A Greenfield sizing is only to be used when having no SAP instance based on Any DB or HANA to collect data from The sizing input is a quantity structure based on a bundle of assumptions or workload statistics

Attention Re-sizing any existing SAP System by a Greenfield approach is not allowed

SAP HANA Sizing Cases OLAP vs OLTP

Due to the different characteristics between OLAP and OLTP SAP has different sizing toolls Typical OLTP Solutions are ERP SRM CRM SCM EWM Banking Services S4 Solution Manager SAP Gateway Typical OLAP Solutions are BW CAR BW4 BO

Summary SAP Sizing options

Combining Green-Brownfield and OLAPOLTP one of the following four scenarios apply

Greenfield Sizing (former named Initial Sizing)

bull New SAP workload andor customer

Tools

bull SAP Quicksizer bull SAP Sizing Guidelines bull Sizing by ConsultantsCustomerRFP

Brownfield Sizing (former named Migration or Upgrade Sizing)

1 Workload already on SAP using Any DB 2 Migrate from Any DB to HANA DB 3 Upgrade an existing HANA System

Tools bull BW4 Sizing Report bull S4 Sizing Report bull Rules of thumb

Rule of Thumbs

Brownfield OLAP BW Sizing with Sizing Report (see SAP Note 2296290)

Greenfield OLAP BW Sizing with HANA Quicksizer

Brownfield OLTP ABAP on HANA Sizing Report S4 SoH (see SAP Note 1872170)

Greenfield OLTP Solution Sizing with HANA Quicksizer

12


SAP References and Notes for Sizing

The Sizing decision Tree provided by SAP is a perfect starting point to get started on SAP HANA Sizing httpswwwsapcomaboutbenchmarksizingdecision-treehtmlpdf-asset=aaa93b78-8f7c-0010-82c7-eda71af511faamppage=1

Sizing Report Best Practices

The next chapters will focus on how to feed the sizing tools correctly to retrieve a valid result At the end mandatory SAP Notes and how to retrieve assistance are listed

Growth and Timeline of your Database

Independ of the sizing type a data timeline and growth per year factor must be determined as input to the Sizing Repots and the Quicksizer

Note IBM recommends using a timeline of 3 years and a minimum growth rate of 10 per year

Brownfield OLAP Sizing (BW)

Customers with existing SAP Business Warehouse implementations now migrating to SAP HANA or having a SAP HANA to be upgraded must run the SAP provided report within their existing system SAP makes this step mandatory for customers running SAP solutions on traditional databases This is accomplished by analyzing the existing SAP systems in terms of data sizes characteristics and distribution of data objects as well as the transaction history for these data sets

The ABAP reports attached SAP-Note SAP Note 2296290 New BW Sizing Report must be installed and executed (The current report Version is 80 February 2020) At minimum BW-Sizing Report V259 or higher is strongly recommended SAP and IBM recommend to always use the latest version

Brownfield OLAP sample

Start the sizing report ABAP code in the background

Note It is mandatory to run the report under a typical load period

Figure 3 Start the sizing report

The BW-Sizing Report (V259 and higher) has been extended to include a CPU capacity requirement estimation The estimated CPU demand is reported in SAPS in addition to a memory calculation For more details about BW CPU sizing SAP Note 2502280 - Adding CPU requirements analysis to BW4HANA sizing report

13


Major Input Parameters of the BW Sizing Report

Figure 4 general input parameters BW Sizing Report

Note Customers need to comply with the conditions outlined in SAP-Note 2502280 to activate the CPU analysis Four parallel procs is the default Higher numbers will result in higher CPU sizings

Figure 5 BW Sizing report precision

In most cases a ldquoMediumrdquo Precision level is good enough In samples taken there had been hardly differences between High and medium

Figure 6 Customized Memory Configuration

Memory Configuration custom is the default for Power Server sizing as it allows to define this value to the actual need The ldquopredefinedrdquo match the appliance model sizes and are typically not used on Power In order to start the iterative sizing process on possible starting point is to use frac12 of uncompressed source SAP database size and then review the output and re-adjust if possible

Note SAP and IBM recommend to prefer scale-up over scale-out deployments in both cases ndash OLTP and OLAP The maximum memory footprint for scale-up is documented in SAP Note 2188482 - SAP HANA on IBM Power Systems Allowed Hardware

In this example a node with a size of 800GB is defined Depending on the DB Size the program runs between 10 minutes up to hours Please forward the complete report to your IBM representative for review and hardware mapping assistance

Result of the BW Sizing Report

The report is provided in rtf or html file format inside the SAP system

14


The first page of the TDIv5 BW sizing report starts with the 2Minimum Memory Sizing Resultsrdquo section

Figure 7 Sample BW sizing report output

On the following pages of the BW Sizing Report the RSDDSTAT Analysis Details can be found Two values are highlighted Data Load Peak vol In below sample the CPU requirement is caused by a high Data load peak at February 17th If this is an exceptional situation where a lower performance is acceptable re-taking the Sizing Report is the way to address this CPU requirements The CPU requirement class reflects the number of Queries Dataload CPU Utilization and the Quality of sizing relevant statistical Data There are three classes S M and L This class is put into the calculation of the physical cores As a rule of thumb going from an L class to an S class requirement the core count is reduced by frac14 Hence the selection of sizing report runtime is so important

Figure 8 CPU requirement Class M caused by Data load peaks

The next step is to translate the SAPS value and the CPU requirement Class to physical cores IBM can help you to analyze your Workload and the impact on the CPU requirement IBM recommends to forward the complete sizing report to the IBM representative to determine based

15


on the targeted Power Server Model the right CPU sizing which then has to undergo a mapping to the right LPAR configuration eg when using Spared pool LPARs

Note The entitlement of an LPAR in a shared processor pool is typically in the range of double-digit range below to a dedicted(-donating) LPAR configuration

For more details about the BW Sizing Report please read the documentation attached to SAP Note 2296290 New BW Sizing Report

Brownfield S4 or Suite on HANA Sizing (with Sizing Report)

Customers with existing SAP Business Suite implementations must run the SAP provided report within their existing system This is accomplished by analyzing the existing SAP systems in terms of data sizes characteristics and distribution of data objects as well as the transaction history for these data sets For long running Business SuiteS4 applications data clean-up is an option that must be decided on project level depending on local regulations that will save memory and core values

Customers must execute the ABAP report attached this SAP-Note SAP Note 1872170 - Business Suite on HANA and S4HANA sizing report (The current report Version is 80 February 2020) Start the sizing report ABAP code in the background


Figure 9 Start the S4Business Suite Sizing Report

Depending on the size of the database and computing resources the report runs between minutes and hours and does NOT provide SAPS but the Memory requirements IBM recommends as a default to include a growth factor for 3 years with a growth rate of 10 unless there are other indications Use as with the BW Sizing Report the custom option to define the memory size of the LPAR to fit the actual needs

Memory Sizing of S4BS Systems

As a starting point the ldquomemory requirement for the initial installationrdquo value must be used In addition the ldquoupgrade shadow instancerdquo has to be added to the LPAR mapping In the given Sample the LPAR Memory footprint is 16697 GB what easily fits into a scale-up deployment

16


Figure 10 Sample ERP Sizing Report output

CPU Sizing of S4 HANA Systems

The S4 Sizing Report does not include CPU Sizing by default By SAP Note 1793345 Sizing for SAP Suite on HANA SAP recommends to expect Factor 3 more of CPU requirement for the database tier than on Any DB The Appserver CPU consumption remains stable for same workload

Figure 11 CPU consumption classic DB vs HANA for S4

The database tier on traditional Business Suite systems consumes 20 of the total CPU consumption roughly A HANA DB needs 3x the CPU resources than a traditional DB The CPU sizing can be reduced by NSE and Data Clean-up The server utilization can be further optimized during the Hardware Mapping by using SPLPARs

CPU Upgrade Sizing of S4 HANA App Servers

Before migrating to HANA the Application Server should be upgraded to EHP 8 as per SAP recommendations (as of 72020) Requirement of additional CPU resources should be taken into account IBMrsquos recommendations for CPU capacity upgrade factors () can be found in the ISICC Sizing Community (IBM or Business Partner accessible) Also the actual current usage of CPU capacity on the application servers should be looked at first and optimized

17


Greenfield S4 or Suite on HANA Sizing (with HANA Quicksizer)

The SAP Quicksizer method is dedicated for initialgreen-field HANA sizing only It is a tool owned by SAP and available on the SAP Webpages httpswwwsapcomaboutbenchmarksizingquick-sizerhtml (a valid S-User ID is required)

Figure 12 SAP HANA Quicksizer Versions

Sap provides three versions depending on where the Instance is going to be deployed

bull Hana Version on-premise or IaaS deployments

bull Classic Version none HANA DBs on premise or IaaS bull S4HANA Cloud Version SAP HEC

The Quicksizer allows to create a Sizing Project and share the access with others by sending Customer No and Project Name

Figure 13 Create Quicksizer Project

In this Picture the sample the Quicksizer Project ldquoHOP-PLANNING-GUIDE-1rdquo has been created The Quicksizer covers all common Business Application Solutions Hence the more are included the more complex the sizing input will be In order to accomplish the task successfully the following is needed

bull A basic understanding of the application bull Identify all SAP Solutions used bull Define the Quantity Structure of the Workload (selected transactions parallel users) bull Team with SAP Solution Consultants and customer subject matter experts

12345

18


Figure 14 Quicksizer Protfolio - Select SAP Solution(s)

User based vs Throughput based sizing

The Quicksizer works with two major sizing inputs 1 User based The Number of users working concurrent active on the System at peek

workload time (example 1000 User working on ERP System) 2 Throughput based The highest number of Transactions being processed within a defined

timeframe (example Creating 1 Mio Billing documents between 10-11 orsquoclock) Throughput and Transaction Based means the same

If throughput and user based information is available for example if large batch workload runs in parallel to active users IBM recommends to create two reports one user based and one throughputtransactions based The sizing is at minimum the highest of both In case the two workloads run in parallel the Sizing estimate will be above

Data TieringResidence time in Memory

The longer data is kept in memory the more memory will be needed over time By default the Quicksizer calculates a Residence time in Memory of 24 months The Quicksizer allows to set residence times for each sizing position individually to get to a right memory sizing

19


Sample sizing for 1000 Users in Sales and Service

Figure 15 Sample sizing Sales and Services

The yellow bulb shows your current input region

Figure 16 Sample Quicksizer input for Sales and Services

The sample sizing input is a total of 1000 Users keeping the data 36 months in memory and 48 months on disk (Aging) After pressing the ldquoCheck Inputrdquo and ldquoCalculate resultrdquo buttons the sizing result is displayed

Figure 17 Sample Sales and Service SAPS

The sample HANA DB needs 10000 SAPS

Figure 18Sample Sales and Service Memory

The sample HANA DB needs 362GB of Memory

Figure 19 Sample Sales and Service Growth output

The sample HANA DB Memory requirement growths from 200 GB up to 360 GB after 3 years

20


Learn more about the Quicksizer at the SAP HANA Academy

httpswwwyoutubecomwatchv=9zWuNlwQGM4

More SAP Sizing Guidelines

Even the SAP Quicksizer does not cover every SAP Solution Find more or detailed sizing guidelines at the SAP Sizing Homepage httpswwwsapcomaboutbenchmarksizinghtml

Greenfield BW Sizing with the SAP Quickiszer

To do a BW4 Greenfield Sizing the SAP HANA Quicksizer is to be used httpswwwsapcomaboutbenchmarksizingquick-sizerhtmlquick-sizer

Figure 20 Select the solution to be sized

Select the chapter Technology Platform and find SAP BW4 HANA Sizing Below you see the most common Sizing Questionnaire Tables for a BW Sizing shown in Figure 21 Size the Appserver Tier by number of users Figure 22 Impact of objects upload and Figure 23 Advanced Data Store ldquoTable 2rdquo is to size the App Server Tier by the number of users

21


Figure 21 Size the Appserver Tier by number of users

ldquoTable 3rdquo is to size the Impact of the Objects Upload on the HANA DB Tier

Figure 22 Impact of objects upload

Table 5 defines the Advanced DataStore and has Impact on the HANA DB Size and CPU

Figure 23 Advanced Data Store

After pressing the ldquoCheck Inputrdquo and ldquoCalculate Resultrdquo Buttons the sizing output is generated The next step is to choose the result level for the Software Components in the ldquoAllrdquo tab

The Quicksizer input above leads to an estimated HANA DB node size with a total Memory of 1754112 MB (17TB) The estimate for the CPU capacity of the HANA DB is 230000 SAPS (The CPU Sizing result at this Demo is caused by a extreme Workload entered for demo reason only In reality most of the systems performs perfect with half of the CPU capacity)

Sizing related technologies

SAP HANA Data Temperatures reduce the sizing result of CPU and Memory

In order to reduce the (expensive) in-memory footprint of business data using the principle of data temperatures (hotwarmcold) and sharing of resources In many cases data temperatures refer to the concurrency of data for ongoing business transactions versus historical ie report only data The latter are no more contained in the HANA core memory but in different repositories depending on the implemented solution which can be

- Native Storage Extension (NSE) leaving data on disk It works for Aging as well replacing

Extension Nodes

- Data Aging (retention periods of data can be specified in Quick Sizer see S4 Greenfield )

- Dynamic Tiering

- SAP HANA BW Extension nodes

The more data are offloaded from the ldquohotrdquo data segment the less resources are required for the

HANA nodes - at cost of higher access time for the warm and cold data sets

22


Native Storage Extension (NSE) Warm Store Configuration Rules

NSE is an intelligent HANA Native feature exploited today by selected business applications such as

S4 and BW The candidates for NSE are per se all data which is aged or that can be put on a BW

Extension node

It is the preferred warm store option for those SAP Applications supporting it as it gives highest

savings and the easiest way of operation by simply leaving data on disk that is iot used

SAP today provides no sizing for NSE but a set of configuration rules and tooling

bull SAP Note 2771956 - SAP HANA Native Storage Extension 20 SPS 04 Functional Restrictions


bull SAP HANA NSE Documentation July2020

httpswwwsapcomdocuments2019094475a0dd-637d-0010-87a3-c30de2ffd8ffhtml

23


Quick Reference Get SAP HANA Sizing from SAP

Figure 24 Quick Reference Get SAP HANA Sizing from SAP

Links References and Tools

bull Learn more about the Quicksizer at the SAP HANA Academy httpswwwyoutubecomwatchv=9zWuNlwQGM4

NSE

bull SAP Note 2771956 - SAP HANA Native Storage Extension 20 SPS 04 Functional Restrictions bull SAP Note 2927591 - SAP HANA Native Storage Extension 20 SPS 05 Functional Restrictions

bull SAP HANA NSE Documentation July2020 httpswwwsapcomdocuments2019094475a0dd-637d-0010-87a3-c30de2ffd8ffhtml


bull SAP Sizing Homepage httpswwwsapcomaboutbenchmarksizinghtml

bull SAP Sizing Service Marketplace bull SAP HANA Sizing Decision Tree

bull SAP Note 2296290 New BW Sizing Report

bull SAP Note 1872170 - Business Suite on HANA and S4HANA sizing report bull SAP Quicksizer

bull SAP HANA Hardware Directory

bull SAP HANA Tailored Data Center Integration Sizing Support

bull IBM Techline (IBM internal)

bull IBM Techline (Partnerworld) IBM Only Material

bull IBM employees can find additional guidance at IBM SAP Sizing Community the IBM HANA on Power Community IBM SAPS Capacity Tables (IBM internal)

Make yourself familiar with SAP HANA Sizing Decision Tree(see bdquoLinks References and Toolsldquo subchapter)

Complete SAP Quicksizer for Greenfield deployments or use the Sizing Report for Brown Filed sizings as per SAP Note for OLAPOLTP

Need support

contact your respective TechLine FTSS andor ATS team (see bdquoLinks References and Toolsldquo subchapter)

Quantified system requirements without server consolidation PowerVM sharing benefits or desired Memory or Core savings

yes

24


Decide on Power and SAP features implemented to reduce Hardware or

accelerate your workload In 2019 IBM release a set of innovations allowing for up to 18 times faster SAP HANA restart times while maintaining virtualization and LPM capabilities reducing the Core consumption by combining Shared Pools with SAP HANA NSE up to more than 30 and cut the memory footprint up to 50 by combining Services and SAP HANA features These options added another dimension to the planning process helping to reduce the LPAR footprint What was formerly a

Sizing -gt LPAR mapping became an equation of

(SAP Sizing ndash benefits of new technologies) -gt LPAR mapping Important is that many technologies can or even should coexist A collection of related documentation describing the innovations compare options can be found here httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102502 and in SAP Notes listed later

SAP HANA startup acceleration

IBM provides a portfolio of different acceleration options and provided in 2019 a full documentation refresh on httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102502 Start with the document ldquoComparison of available Fast-Restart-Solutions on IBM Power for SAP HANAldquo to be able to determine the differences Assuming as a baseline a SVC backed by an older SSD based Storage subsystem connected to 48Gbs Fiberchannel the following Info gives a thought about options and ranges discussed in the above technical guides Highlevel Options Faster Storage

IBM NVMe based SAN attached Storage Subsystems can accelerate a HANA Startup by a factor of 3x and more compared to older SSD based Storage backends

Internal NVMe PCIe Cards Internal NVMe cards as used for H922 models accelerate up to 45x read (link)

Rapid Cold Start Accelerates slow SAN by an NVMe cache up to 45x (link)

SAP HANA Native Storage Extension HANA 2 SPS4 With SAP HANA NSE not only the memory footprint can be reduced but also startup time is accelerated by intentionally leave data on disk

Temp-fs HANA 2 SPS4 Accelerates HANA restarts by gt18x (link)

Virtual Persistent Memory HANA 2 SPS4 Accelerates HANA and OS restarts by gt17x (link)

SAP HANA in Shared CPU Pools

SAP HANA on POWER system configurations must not only focus on the SAP HANA database instance itself but also consider resources for SAP application servers and other systems running in the customerrsquos datacenters Aggregating instance capacities and consolidating those with PowerVM

25


will establish a more efficient usage of IBM Power Systems and at the same time it can provide a performance improvement by co-location in regard to communication and SPLPAR values covering CPU peaks better in a reasonably consolidated system The SAP Note defining the allowed configurations is 2055470 - HANA on POWER Planning and Installation Specifics - Central Note

Introduction into Shared Processor Pools Shared processor pools define virtual CPUs as the entity where the hypervisor can schedule a physical processor Entitlement is a setting that defines how many cycles of a physical CPU are guaranteed to be made available to a virtual processor by the hypervisor For example an entitlement of 05 guarantees that a virtual CPU is getting scheduled to a physical CPU at least 50 within a given time window As long as not all CPUs in the shared pool are used the virtual processor may even get 100 of a given time window scheduled to a physical CPU The total amount of configured entitlements can never exceed the physical CPUs available in a system This allows the hypervisor to assign physical CPUs to the virtual processors for the configured entitlement always on the same NUMA nodes Those NUMA nodes are also known as the home nodes of a Virtual CPU For assignments of physical CPUs above the entitlement the hypervisor tries to schedule to the home nodes as well but this canrsquot be guaranteed

Shared Processor Pool and SAP HANA

If a client is running shared processor pools with a proper sizing of the entitlement for SAP HANA the database can make use of the internal NUMA optimizations In most cases performance is at least identical to a comparable setup with dedicated CPUs Performance could be even better if more virtual CPUs are configured than in the dedicated case and overall system utilization isnrsquot too high (see Figure 25 below) Throughput performance in the shared pool with SAP HANA matches the performance expectation (red line) based on the entitlementmdashand often exceeds it

Figure 25 Typical Example of Workload behavior in Shared Processor LPAR vs Dedicated LPAR

26


The definition of more virtual CPUs in the shared LPAR compared to the dedicated LPAR allows it to make use of unused capacity in the shared pool for improved performance

SAP HANA Performance Observations

SAP HANA workloads are rather spikey with short periods (seconds and less) of very high CPU utilization while processing parallelized queries followed by longer periods of low utilization The SAP HANA sizing targets best performance even at the workload peaks As a result many SAP HANA servers show a 10 to 20 CPU utilization as daily average This characteristic pretty much accommodates the mechanism of a PowerVM shared processor pool with its highly dynamic resource management In a shared pool the PowerVM hypervisor can switch CPU resources from an idle HANA system to another loaded system within milli-seconds This means that shared pool LPARs can save compute resources by over-commitment Performance impacts by a variable core-memory affinity between HANA in-memory data and processing cores are avoided by keeping the HANA CPUs and DIMMS on the identical socket which is easy to accomplish by the PowerVM Home node concept ensuring locality

Get to the right PowerVM SPLPAR settings for an SAP

HANA LPAR

The combination of multiple LPARs with various workload types in a shared pool allows for capacity synergies though by dynamic load compensation among the applications This is accomplished by parameterization of each LPAR per its application requirements Following are few guidelines for production HANA DBs more aggressive configurations should be chosen for none productive instances having a lower weight factor

bull The virtual processor count (vCPUs) should be the same as the sized physical CPU-capacity (SAPS cores) allowing for the same degree of parallelism

bull For highest elasticity across LPARs in the shared pool all production HANA LPARs should run in uncapped mode

bull Customers can balance resource savings against tolerable performance impacts for their important transactions and jobs As starting points we see

o At the time of initial setup the entitlement of CPU resources should be in the range of 75 for workload with critical SLAs

o From that starting point customers can gradually fine tune CPU characteristics (entitlement) while observing response time behavior This can be performed iteratively without disrupting the affected applications

bull Lower entitlements ~50 are possible for SAP HANA LPARs o Customers should individually balance the importance and constancy of response

and job run times with resource savings when reducing LPAR entitlements bull Higher weighting factors are recommended for production systems over less performance

critical systems

bull SAP HANA TDI5 workload categories for OLAP (large medium small) do not necessarily correspond to higher or lower LPAR entitlements

Figure 26 NMON LPAR utilization profiles (CPU user + system) of independent

27


o Means also ldquosmallrdquo workloads can comprise of performance critical customer transactions while there might be less critical response time SLAs for class ldquolargerdquo HANA workloads

bull Non-performance critical LPARs eg running test or development systems can have small entitlements and lower weighting factors

bull The memory per shared HANA LPAR is static and sized identical to dedicated environments bull Newer versions of Linux are reporting the home nodes of virtual CPUs in Shared Processor

Pools and HANA is able to use this information for its internal performance optimization A user can check with the command ldquonumactl ndashhardwarerdquo the NUMA topology based on the home nodes If all CPUs are listed only on NUMA node 0 the following minimum kernels have to be used SLES 12 SP3 with kernel =gt 44120-9417-default SLES 15 or RedHat

768 bull Regularly validate the CPU utilization (see next chapter)

bull Assuming a reasonable workload mix the entitled CPU capacity of the pool will be significantly less than the CPUs allocated for the identical mix to dedicated LPARs This gives room for additional LPARs on this system thereby increasing overall CPU utilization and lowering TCO

o For example an average pool entitlement across all LPARs of 67 provides spare resources of 33 which can host additional workloads thus increasing overall server utilization and reducing TCO

Monitoring SAP HANA in Shared Pools

On SAP HANA DB and application level the resource monitoring in shared processor LPARs uses the default SAP monitoring tools like saposcol and HANA Cockpit Same is true for CIM-based external tools No adaptions had to be made to the SAP tools and their interfaces On LPAR level the physical consumption (physc) refers to the core processing capacity currently used The additional metric entitlement consumption (entc) represents the processing capacity being used compared to the LPARrsquos entitlement Uncapped shared partitions can show an entitled capacity gt100 if they access idle pool processors from other shared LPARs Often the entitlement can be adjusted mentionable The most common way to determine the best setting is to use nmon with a sampling interval of 5 seconds for a period of one week during a typical workload on ALL LPARS on the serverrsquos shared pool

Eco System and Landscape aspects For TDI deployments there is a rich set of options The corresponding IBM documents can be found on IBM Techdocs httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102502

Mapping SAP Sizing Output to IBM Power Systems Configurations The server decision has to be made to fit the memory CPU and IO adapter requirements including the additional workload running on the same server SAP HANA server planning comprises of three parts

1) The size of the SAP HANA partition(s) =

SAP HANA Sizing (memory + SAPS) ndash ldquoSPLPAR NSE NVMe helliprdquo + SLA requirements

2) Adapterstorage planning =

28


SAP TDIEthernet sizing + VIOS + SLA requirements 3) The size of the IBM Power Server running multiple partitions next to HANA

= workload consolidation + VIOS

Note There is no linkage between SAP HANA scale-upscale-out and the IBM Power E- and S-class models Both ndash E- and S-class models ndash can be used for SAP HANA scale-up and scale-out installations

SAP HANA deployment options and IBM Power Server

For SAP HANA scale-up (single SAP HANA node) all resources must fit into a single POWER server or an LPAR running on it Multiple single-node HANA databases and other workloads can be consolidated on a single server A shared pool should be used for all LPARs including SAP HANA production instances where possible SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host documents supported LPAR configurations

Figure 27 PowerVM LPAR types

For production HANA partitions there is a window defined by a minimum (SAP Note 2055470) and maximum LPAR configuration (SAP Note 2188482 - 24TB as of 72020) Within this window any Partition size can be chosen In scale-out multiple of these LPARs are used which can reside in a single or spread across multiple IBM Power Servers each with the maximum size of a scale-up HANA LPAR For SAP HANA scale-out (multi-node) the inter-node network communication and the host auto failover architecture (shared disk vs shared filesystem) must be considered when planning the servers On IBM Power Systems SAP HANA scale-out setups can comprise of multiple LPARs residing on a single server or spanning multiple servers Power Systems hosting HANA scale-out partitions can also run additional LPARs with other HANA or non-HANA workloads

Note

Power Server Hardware

PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR

Shared Processor Pool

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Virtual Shared Processor Pool n

Virtual Shared Processor Pool 1

HANA productionnone production systems ApplicationServers optimizer HANA Production

(1)1025(40)Gbs Ethernet adapters

SR-IOV capable (8)1632Gbs FC adapters

29


SAP HANA scale-up should be preferred over scale-out since it is less complex plus more resource efficient and typically provides better performance

Planning for SAP HANA System Replication IBM published a two Redbooks describing the pro and cons of the large variety of HANA System Replication modes Also consider for which option the targeted Cluster Manager has the predefined scripting as this provides best integration robustness and support For in depth information please contact your cluster Vendor what typically is SLES HAE and RHEL Pacemaker To optimize TCO according to SLA criteria you must differentiate between mission critical production and less critical non-production SAP HANA database servers (SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note) Selecting the best suited Power System materials

bull SAP HANA Hardware Directory listing the supported Power Systems and their allowed core

counts only models showing up here can be used for production HANA databases

bull The Power Systems Facts and Features on Sales Support Information (IBM only) (SSI) or

similar documents provide detailed IBM Power Systems specifications(for example POWER8

Facts and Features or POWER9 Facts and Features(IBM only)

bull Linux only server models are available and can be an alternative at a compelling price The

same applies to Integrated Facility for Linux (IFL) specialty processors which are dedicated to

run Linux operating systems only in the E-Class models For the E-class models these allow

tailoring IFL memory to host a SAP HANA DB

bull Within IBM eConfig a server category for ldquoHANA modelsrdquo is available These differ from the

general Power Systems in the way that they include on HANA tracking feature code and

preselect the ldquoLinux for SAPrdquo distributions as default OS These are mandatory for both SLES

12 and RHEL 7 running production HANA instances since they include the technical and

support extensions required for mission critical HANA systems

Also special priced HANA servers become available in this eConfig server category

30


Figure 28 SAP HANA Category and Features in eConfig

Planning Considerations for Power Systems Memory Capacity

The memory size for the SAP HANA production partition is defined by the SAP sizing output In exceptional cases customers can request individual adaptions of the common limits at SAP SE This is a post-sales effort (ie cannot be applied to initial sizing) since it requires an operational HANA on POWER systems to be analyzed first SAP Note 1903576 - SAP HANA DB additional main memory in exceptional cases describes the details for this process PowerVM AME (Advanced Memory Expansion) and AMS (Advanced Memory Sharing) are NOT supported for SAP HANA database partitions In the overall context such as considering the Application servers on AIX a good memory saving can be achieved on those LPARs using AME The rules of thumb given by SAP can be found in the attachment in SAP Note 2296290

Planning Considerations for Power Systems CPU Capacity

Starting with TDI Phase 5 the required core count is defined based on SAPS compared to earlier CTM (Core to Memory) ratios The tools and process has been described above in the ldquoHANA Sizingrdquo chapter With the introduction of SAP HANA 20 the default deployment mode has changed to MDC (multi-tenant database containers) A single or multiple HANA databases reside within a single HANA system One implication is that the tenants can dynamically share memory and CPU resources more efficiently compared to LPAR or VM boundaries Details are described the PDFs attached to

- SAP Note 2104291 FAQ - SAP HANA multitenant database containers

- SAP Note 2096000 SAP HANA multitenant database containers - Additional Information

SMT8 is the recommended multi-threading mode It changes for HANA OLTP-type workloads if the systemLPAR holds many cores spanning 8 times of threads SAP Note 2188482 documents the threshold and target SMT level

Virtualization LPARs performance related considerations

SAP HANA is highly optimized for the underlying hardware in order to achieve its superior performance Those optimizations include sophisticated algorithms using specific processor features (like vector facilities) as well as exploiting the underlying cache and memory structures Hence the partitions on IBM Power Systems should be created in a specific manner to allow for the best performance The following is a set of recommendations to achieve a good partition layout for SAP HANA

bull SAP HANA benefits especially on larger systems from an even distribution of compute power

across the LPAR PowerVM will automatically achieve this when the number of processors is

the same for each socket

bull The LPAR layout can be verified with the command numactl --hardware (OS command) and

should show the same number of processors for each NUMA node along with an even

distribution of memory

bull When dynamic operations are planned (such as CoD or LPM) the NUMA layout has to be

ensured at the target if the HANA instance needs to provide the same performance as

before

bull Servers with multiple partitions which have been created and deleted over time PowerVM

might not be able to achieve the best partition layout immediately In this case you can use

DPO (Dynamic Platform Optimizer) to change the partition placements This can be done on-

line without down-time of the SAP HANA system

31


bull To provide the best performance experience the higher frequency core option of a server

model should be preferred

Relaxed conditions for all none-production LPARs apply as of SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note

Planning Considerations for Power Systems IO Adapter Capacity

Please see chapter ldquoSAP HANA Connectivityrdquo to ensure the server provides sufficient adapter slots When using VIOS ensure an appropriate resource planning for these LPARs as a minimum of 10Gb Ethernet cards is required More details on VIOS is provided in chapter ldquoSAP HANA Connectivityrdquo

Quick Reference Find valid IBM Power Systems options

Figure 29 Quick Reference Mapping SAP Sizing Output to IBM Power Systems


ISICC SAPS Capacity Tables for Power Systems (IBM only) Use the table to identify systems and number of cores The SAPS tables are maintained as an Excel-sheet and are valid for all OSs running on Power Systems They are only accessible for IBM employees BPs should contact IBM TechLine for support This is identical to sizing systems for other SAP workloads Refer to the IBM Power Systems Facts and Features for detailed system specifications (IBM only)

bull POWER8 Facts and Features POWER9 Facts and Features (IBM only)

bull Sales Support Information (IBM only) bull Certified and Supported SAP HANA Hardware Directory ndash IBM Power Server

Please check SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note for relaxations for non-production systems

Quantified system requirements

available from SAP HANA Sizing

Indentify IBM Power Server options providing enough memory as sized by SAP

(see POWER Systems Facts amp Features or SSI for Server details

Verify that only SAP HANA approved Power Hardware as of SAP Note 2133369 is used)

Verify SAPS requirements can be met

(see ISICC SAPS Capacity Tables for Power

Systems for LINUX)

Ensure later the Server can also

fulfill all IO Adapter Requirements

List of valid IBM Power Servers available

Add additional requirements for

additional workload

(eg VIOS Appserver )

FOR PRODUCTION partition is sized accordingly

to SAP Note 2188482

corememory ratio available

SAPS available

yes

yes

Will the LPAR be used for SAP HANA production LPARs

yes

For none-production partitions

relaxed Storage Server core and

memory requirements apply

No (all non-prod HANA LPARs)

no

no

32


Note Additional processors and memory are required for Virtual IO server partitions (VIOS) and PHYP Power Hypervisor (PHYP) also uses memory ndash at a max of 8 of total server memory Do not under estimate VIOS sizing as it can hurt SAP HANA performance when requiring high Ethernet throughput

Mapping SAP IO KPIs to a SAN Storage Design

External and internal disks can be used External disk subsystems must be SAP HANA TDI certified The sizing output of the Quick Sizer is not specific enough The SAP HANA Server Installation Guide the SAP HANA TDI ndash Storage Requirements Guide along with the result of the SAP HANA Quick Sizer gives a good understanding of the volume requirements of storage SAP HANA database performance depends on processing everything in memory Hence the ongoing load and store operation are reduced to initial loads from disk at first access of data and writes of log files and save-points To improve cold start additional NVMe cards can be used to speed-up the start by factors Technical white paper--Optimizing Quality of Service with SAP HANA on Power Rapid Cold Start The requirements introduced by the SAP HANA IO characteristics for the file system and the underlying storage have four planning objectives

bull Start-up time

Starting an SAP HANA Database from the stored content on disk requires read performance

during startup Also consider other cases such as failovers to a standby node using SAP

HANA auto-host-failover or SAP HANA System replication

bull Database Persistency

To provide persistency data and log content is written regularly to disk This requires low

latency for log volumes SAP also offers to hold multiple versions of the data area multiply

the storage requirements if used

bull Backup

SAP HANA provides different options to backup data Check with your Backup Vendor for

options provided

bull Data Protection

This can be achieved using SAP HANA or Storage mechanisms (see page 34)

To optimize TCO according to SLA criteria one must differentiate between mission critical production and less critical non-production SAP HANA database servers

Planning Considerations for a valid Storage Type

Storage selection and deployment options

1 Storage systems having passed the TDI certification (SAP Certified Enterprise Storage

Hardware for SAP HANA web-site for IBM)

2 Ensure appropriate multipath drivers are installed in the targeted Linux Operating system

supporting the desired technology (eg NPIV)

3 The end-to-end setup up to the server comprising of filesystem operating system server

network and storage needs to be tested with the SAP HANA Hardware Configuration Check

Tool ldquoHWCCTrdquo before installing SAP HANA

4 Storage subsystems can be attached either natively or via a storage virtualization layer like

IBM Spectrum Virtualize (formerly known as IBM SAN Volume Controller SVC)

33


5 Redundant SAN attachments via virtual (VIOS) or dedicated Fibre Channel (FC) adapters are

possible The usage of vSCSI technology is not recommended as SAP HANA auto host-failover

will not work on such disk attachments

6 To accellerate startup times internal NVMe drives can be used as described in the ldquoRapid

Cold Startrdquo Documentation httpswwwibmcomcommonssicgi-

binssialiashtmlfid=POS03155USEN

Use the following SAP documents as a starting point SAP HANA TDI ndash Storage Requirements and SAP HANA Server Installation Guide IBM developed the SAPmagic - Storage Sizing Tool for SAP landscapes (IBM only) which can be used to verify or outline options complementing the SAP HANA Quick Sizer across IBM storage technologies for the SAP HANA data log and shared filesystems It includes a special method for optimizing SAP HANA file placement and IO bandwidth leveraging a balanced blend of HDDs and SSDsFlash See the IBM System Storage Architecture and Configuration Guide for SAP HANA TDI on TechDocs for a detailed description of SAPmagic methods

Note Be aware that the mapping of the SAP sizing output and the following planning steps identify a larger disk space requirement than the sizing provided by the SAP HANA Quick Sizer and the SAP HANA TDI ndash Storage Requirements paper based on the desired backup advanced performance and resiliency capabilities However the baseline requirements are identical to all vendors as they are provided by SAP Note Attempting to compress data at the storage level that is already compressed at the application level does not save any space and can have a significant performance impact

Background SAP HANA filesystems and SAN storage

The SAP HANA storage capacity requirements consist of several elements with different characteristics

bull SAP HANA install directory and usrsap

local directory

bull SAP HANA shared

A shared filesystem spanning all SAP HANA nodes belonging to the same system It holds the

SAP HANA executables configuration files and work directories It can reside on NFS or IBM

spectrum Scale which can be served by SAN or a FILER option

bull SAP HANA data

Performance relevant for RTO on startup (mainly read) Needs to fulfill the minimum Storage

KPIs validated by HWCCT Runs a supported Filesystem for SAP HANA as documented by SAP

Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note

Compared to SAP HANA shared filesystems SAP is more restrictive FILERS must be TDI

certified and the combination of Filesystem and Storage Backend must be verified

accordingly to SAP Note 2055470 - HANA on POWER Planning and Installation Specifics -

Central Note

bull SAP HANA log

Benefits from low latency IO characteristics (mainly write) Needs to fulfill the minimum

Storage KPIs validated by HWCCT Runs a supported Filesystem for SAP HANA as documented

by SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note



34



Central Note

bull The Operating System

Additional Storage Sizing Considerations for Backup DR and HA

An SAP HANA database landscape also requires space and functionality for bull Disaster recovery data protection

o Storage replication A storage subsystem can provide functionality to duplicate data

to a second location This can be a storage mirror IBM Spectrum Virtualize (SVC)

stretched cluster mdisk mirroring Hyperswap or similar storage methods to

duplicate data to a second location

o Backup

bull High availability data protection

o Eg IBM Spectrum Virtualize (formerly SVC) stretched clusters

bull SAP HANA data protection

SAP HANA backups consist of an individual strategy for SAP HANA data log and

configuration files The SAP HANA Administration Guide provides all required information

to determine the space and setup requirements and the different options for creating the

backup Some of the SAP Solutions do rely on storage subsystem features such as FlashCopy

To protect the data in case of a disaster the SAP HANA database content can be replicated

on database level using SAP HANA System Replication or a storage subsystem mirror to a

secondary site The mirroring technology must guarantee a logical order in sense of IO

requests Details can be found in the Introduction to High Availability for SAP HANA

document from SAP

Additional Planning Considerations for SAP HANA scale-out installations

The two objectives for scale-out in addition to scale-up are bull The SAP HWCCT tool needs to be run on all HANA production partition belonging to one

System in parallel and fulfill all SAP given KPIs

bull SAP HANA Host Auto-Failover

This SAP HANA feature requires enabling the hosts to access the data volumes of another

host in case of a failover This can be done either by

o a shared filesystem such as IBM Spectrum Scale on ESS (details in SAP Note 2055470

- HANA on POWER Planning and Installation Specifics - Central Note)

o shared disks with XFS Please read the SAP HANA Server Installation Guide and the

referenced documents for LUN requirements and required host attachments The

client partitions must not use vSCSI adapters As an intermediate Solution until the

SAP Server Installation guide documents all required steps IBM provides a quick

guide on IBM Techdocs

35


Quick Reference Find valid Storage Subsystem

Figure 30 Quick Reference Find valid Storage Subsystem


SAP Documentation SAP HANA TDI ndash Storage Requirements SAP Certified Enterprise Storage Hardware for SAP HANA SAP HANA Administration Guide 2407186 - How-To Guides amp Whitepapers For SAP HANA High Availability SAP Note 1943937 - Hardware Configuration Check Tool - Central Note (defines also the SAP KPIs) SAP Active Global Support offers the SAP HANA Going-Live Check which ndash among other tests ndash conducts a data throughput test using the ldquoSAP HANA Hardware Configuration Check Toolrdquo IBM Documentation IBM System Storage Architecture and Configuration Guide for SAP HANA TDI A Best Practices Guide on how to configure SAP HANA TDI certified IBM Storage Systems can be found at httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102347 A Best Practices Guide on how to configure SAP HANA TDI certified NetApp Storage Systems with NFS can be found at httpwwwnetappcomusmediatr-4435pdf A Best Practices Guide on how to configure the IBM Elastic Storage Server (ESS) for the IBM Spectrum Scale (GPFS) case can be found at httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102644 Tools Quick Sizer Tool The IBM provided ldquoHANAmagic - Storage Sizing Tool for SAP HANA TDIrdquo figures to address not only volume oriented requirements but also RTO ndash ie the time to restore a HANA database from disk to server memory ndash impact of various IBM storage technologies incl FlashSystems (BP and IBM only)

SAP HANA Connectivity

The IO adapter specifications and zones are identical to those of Intel based SAP HANA systems with external storage However for SAP HANA on POWER landscapes these adapters can either be installed dedicated or shared (eg using dual VIOS) With PowerVM additional workload can be put on the same server this must be reflected in the overall planning

SAP minimum requirements

SAP HANA Storage KPIs for TDI

SAP volume requirement based on the SAP

HANA sizing effort

Calculate overall disk capacity requirement for HANA by SLA quality (SSDFlash vs HDD)

Identify required Storage features (OS multipath drivers HA DR redundency and backup)

Ensure later the IO Adapter

Requirements are met

List of valid storage subsystems for the SAP HANA workload available

Customer SLAs

Max startup time of HANA

Backup HA and DR requirements

Requirements from other workload

(Appserver VIOS )

For IBM storage subsystems Identify valid storage options based on capacity and IO performance

using the SAPmagic tool for HANA

Add additional requirements (eg

VIOS SAP Appserver )

36


SAP HANA connectivity planning needs to consider bandwidth requirements for the following communication paths

bull Communication - LAN

o SAP HANA database tier to SAP application server tier

o SAP HANA inter-node communication (scale-out only)

o SAP HANA System Replication Communication

o SAP HANA share (for CTS+ andor scale-out)

o Administrator network

bull Storage ndash SAN

Planning Considerations for Virtual IPs

Similar to SAP NetWeaver systems a SAP HANA database can be installed using a virtual IP address Beside the standard of using virtual IPs for SAP applications there are two cases where a virtual IP for the SAP HANA Database becomes mandatory

bull SAP management tools such as SAP Landscape Virtualization Management (LVM) rely on

virtual IPs to operate on the SAP instances

bull Most cluster solutions require having a virtual IP to failover a SAP HANA System Replication

SAP HANA itself provides such capabilities too

SAP Note 962955 - Use of virtual or logical TCPIP host names and SAP Note 1900823 - SAP HANA Storage Connector API provide additional information

Planning Considerations for VIOS IO virtualization

All IO adapters have to be configured redundantly in order to meet resiliency requirements of a production enterprise database For shared adapters using VIOS this always implies a dual-VIO server setup VIOS is a standard component for most customers deploying partitions on IBM Power Systems VIOS based deployments are mandatory for consolidation Live Partition Mobility (LPM1) and other features For Fibre Channel in multipath environments

bull Each LUN for SAP HANA data and log filesystems should be accessible through a minimum of

4 pathsmaximum of 16 paths to utilize multi-pathing for IO workload

bull For Fibre Channel virtualization NPIV capable adapters should to be chosen to take

advantage of functionality in the larger eco-system and ease of use

For SAP HANA scale-out installations nPIV is mandatory

For Ethernet bull SAP only defines a minimum throughput for the HANA internode communication in scale-

out Besides that there are no HANA specifics

bull SR-IOV capable adapters should be considered for Ethernet connectivity but should be

implemented traditionally using SEA Failover or native SR-IOV (check support by Power

Server when selecting above 25Gbs)

bull For traditional Ethernet virtualization plan for appropriate CPU sizing and dedicated

donating cores for the VIOS and HANA partitions

1 Considering the large memory footprint LPM can only be done under load conditions allowing the memory to be transferred in a reasonable amount of time

37


bull Large_send Large_receive as well as Jumbo frames with a MTU size of 9000 are required for

native and VIOS attached 10Gb Ethernet adapters to achieve the throughput KPIs demanded

by the SAP HANA HWCCT tool for the internode communication Detailed setup and

planning instructions can be found on Network Configuration for HANA Workloads on IBM

Power Servers

bull VIOS in a mixed environment using AIX iOS and Linux require the above settings when using

the same VIOS For using large_receive in a Linux environment

o The minimum VIOS level is 22410

o The kernel module ldquoibmvethrdquo of your Linux must be version 105 or higher

Planning Considerations Single-Host SAP HANA (scale-up)

SAP documents the required connectivity in SAP HANA ndash Network Requirements This applies directly to all dedicated adapter deployments not using VIOS technology Using VIOS sharing these resources becomes a desirable option

bull LPM (live partition mobility) is only possible in VIOS environments

bull In multi LPAR deployments ports can be shared and by that redundancy requires less

physical adapters and sharing can be applied

bull Additional adapters should be considered when planning for a later multi-host landscape

for growth or resiliency reasons or additional workload (see subsequent chapter)

Minimum IO adapter requirements for a production SAP HANA system on SAN with XFS using dual-VIOS are2 Table 1 Minimum Single-Host SAP HANA IO connectivity for production (floor configuration as required by SAP)

Function For EACH VIOS

LAN Ethernet Zones as defined by SAP

SAP HANA to app server The connectivity to all appservers can be shared and is to be sized as done traditionally for DB2 Growth can be achieved transparently to the application

Backup Network (optional) SAP wants to separate Backup IO from Business application IO The 10Gbits adapters to transfer a backup as recommended by SAP can be shared by all HANA and none HANA partitions Growth can be achieved transparently to the application Also verify the requirement documented by the backup tool vendor

SAP HANA System Replication (optional)

Min 10Gbits between data centers is recommended by SAP3 Growth can be achieved transparently to the application

SAN FC Attachment to data and log persistency

Min 8Gb connectivity for at least 4 paths multipathing

2When using dedicated adapters each HANA node requires the same amount of adapters as a dual VIOS setup would require However if a HANA node uses the entire server native attachment is a reasonable option if no VIOS features (eg Live Partition Migration (LPM)) are used 3 The peak load of 24Gbs is the highest known load for SAP HANA System replication Campus solutions where both sides are synchronously replicated to avoid data loss in a HA fail-over scenario have to deal with the individual peak loads DR setups between sides typically have an intentional delay between tiers and by that the need to cover peak loads is lower

38


The network throughputs in Table 1 are a starting point and need adaptation for the specific installation The pattern can be mapped into any supported Power System which fulfills previous sizing criteria and has sufficient free adapter slots It makes no difference whether this is applied to a dedicated SAP HANA on POWER server or to a partition in a larger consolidation system

Planning Considerations Multi-Host SAP HANA (scale-out)

The members in a scale-out setup need to coordinate their workload during a query This requires additional dedicated LAN segments as per SAP SE design guideline SAP documents the required connectivity in SAP HANA ndash Network Requirements This applies directly to all dedicated adapter deployments not using VIOS technology Using VIOS sharing these resources becomes a desirable an option






Minimum requirements for a production SAP HANA system on SAN with XFS using dual-VIOS are Table 2 Minimum Multi-Host SAP HANA IO connectivity per Server (floor configuration as required by SAP)




SAP HANA shared network should be 10GbE connectivity

SAP HANA inter-node connects

SAP documents a minimum of 10 Gbs connectivity Growth can be achieved transparently to the application later in case the minimum is insufficient




SAN FC Attachment to data and log persistency (SAN)


Note Your Linux must be configured as described in the IBM Implementation guide to guarantee 10

Gb Ethernet connectivity

4 The peak load of 24Gbs is the highest known load for SAP HANA System replication Campus solutions where both sides are synchronously replicated to avoid data loss in a HA fail-over scenario have to deal with the individual peak loads DR setups between sides typically have an intentional delay between tiers and by that the need to cover peak loads is lower

39


Note When planning to use the IBM Elastic Storage Server as a filer for IBM Spectrum Scale Filesystems additional Ethernet or InfiniBand requirements apply They are documented in ldquoIBM ESS (Spectrum Scale) Architecture and Configuration Guide for SAP HANA TDIrdquo

Quick Reference IO Adapter Definition

bull A Minimum of 2 cards is required for redundancy for FC and Ethernet (one per VIOS)

bull Ethernet

o Multi part cards are available also with mixed speed ports

bull Fibre Channel

o Calculate the Fibre Channel throughput to meet the desired start time to load the

data into memory

o Ensure the calculated FC adapters can cope with the SAP HANA Filesystem

Throughput KPIs in HWCCT


IBM System Storage Architecture and Configuration Guide for SAP HANA TDI SAP HANA ndash Network Requirements SAP Note 2382421 - Optimizing the Network Configuration on HANA-and OS-Level for SPS10 and Higher Network Configuration for HANA Workloads on IBM Power Servers

Operating System The basis is the same as for all other SAP supported Linux distributions Ensure appropriate licensing versions distributions and configurations as documented in SAP Notes listed in the ldquoLinks References and Toolsrdquo section in this chapter Keep to the limits the OS vendor has supported by the used distribution Be aware that the SAP specific packages often have extended support and higher limits

Software and Operating System

The Linux setup of SAP HANA on POWER does not differ from any Intel SAP HANA deployment The central SAP document is retrievable through SAP Note 2235581 - SAP HANA Supported Operating Systems It provides the match between OS and HANA version and links the appropriate installation and tuning resources for Linux

HWCCT validation (deprecated)

The HWCCT tool has been sunset but is still available through the Market Place There is no mandatory run of any tool requested by SAP The successor of HWCCT is cloud based and can be found through HCoT (Hardware Configuration Check Tool)

SLES 11 considerations

SAP recommends on Power BE the usage of the SLES bigmem kernel variant and makes it mandatory for systems with more than 4TB RAM (as seen on the HMC as max memory) IBM recommends going to a minimum kernel of kernel-bigmem-30101-10871ppc64rpm The latest kernel is recommended It is available for download via the usual SUSE support channels (maintenance web) There is no specific documentation on the SUSE web site except for the usual change log for a maintenance kernel update which in this case is here httpsdownloadsusecomDownloadbuildid=HDdQHihdFrk~

40


HWCCT

bull Warns if a plain SLES 11 SP4 is found on the reason that the bigmem kernel is recommended and that SUSE supports this only with SLES 11 SP4 for SAP

bull Warns if SLES 11 SP4 for SAP is found but the bigmem kernel is not used as the bigmem kernel is recommended

Reports an error if 4 TB or more physical RAM is used without the bigmem kernel variant as a needed bugfix for such systems on Power is only implemented in the bigmem kernel variant

SLES 12 and SLES 15 considerations

Preferably start with a minimum of SLES 12 SP3 For configuration use the auto tuning tool of SLES as described in SAP Note 1275776 - Linux Preparing SLES for SAP environments The saptunev2 has been dramatically improved for Power clients and is absolutely recommended to be used for all SAP related Partitions ndash NetWever and HANA

RHEL considerations

The entry SAP Note for documentation is 2235581 - SAP HANA Supported Operating Systems SAP references from there the already published material Architecture relevant materials

bull httpsaccessredhatcomarticlesrhel-limits

Quick Reference OS Planning

Select any documented Linux distribution as documented by SAP in SAP Note 2235581 - SAP HANA Supported Operating Systems From here the OS installation and configuration guides and tuning notes will be referenced


Installation Guides SAP HANA Server Installation Guide SUSE LINUX Enterprise Server Deployment Guide SUSE Knowledge Base SUSE Linux Enterprise Server for SAP httpswwwsusecomdocumentationsuse-best-practices SAP HANA on IBM Power Systems and IBM System Storage (Supplemental IBM Installation Guide to the SAP HANA Master Implementation and Administration Guides) SAP Notes SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System Installation SAP Note 2235581 - SAP HANA Supported Operating Systems SAP Note 1275776 - Linux Preparing SLES for SAP environments

File System Beside the root file system optional SAP HANA backup file systems usrsap and file systems for other applications a special thought must be given to hanadata hanashared and hanalog

41


The hanashared is a shared file system for CTS+ to exchange data between nodes and the location for the SAP HANA executables of a scale-out solution Typical options are IBM Spectrum Scale (GPFS) or NFS Decisions made for hanadata and hanalog will have a direct effect on storage network HA and DR solutions as well as backups Valid filesystem options are listed in SAP Note 2055470 - HANA on POWER planning and installation specifics - central note The options differ between production and none-production The size of the SAP HANA file systems is determined during the sizing effort documented in the ldquoThe

Planning Processrdquo chapter

Planning Considerations for XFS with Multi-pathing

Using XFS with multi-pathing and LVM striping provides desirable options to optimize the IO characteristics This chapter will explain how Fibre Channel connectivity zoning and multi-pathing influence the LUN layout planning

Note

The minimum number of paths volumes and disks determined in the sizing process is the absolute

minimum even if in the following planning process less might be sufficient

To optimize the implementation on Linux the following considerations should be taken into account for the data and log file systems

bull When increasing the number of ports the minimum number of LUNs should be equal to the number of active Fibre Channel ports (size adjusted accordingly)

bull When increasing the number of LUNs they should be a multiple of the number of active FC ports This will later ensure to optimize the LVM striping

bull The number of logical volume stripes should match the number of LUNs

Planning Considerations for IBM Spectrum Scale

Please download the ESS TDI deployment guide from IBM Techdocs IBM ESS (Spectrum Scale) Architecture and Configuration Guide for SAP HANA TDI

Quick Reference File System Definition

bull Follow the SAP HANA on IBM Power Systems and IBM System Storage (Supplemental IBM Installation Guide to the SAP HANA Master Implementation and Administration Guides) when using XFS or use appropriate file system documentation

bull Follow the IBM ESS (Spectrum Scale) Architecture and Configuration Guide for SAP HANA TDI

when using a Spectrum Scale clients (GPFS) setup with IBM Elastic Storage Server (ESS)

bull Download the SAP HANA SUSE installation guide SAP Note 2235581 - SAP HANA Supported

Operating Systems will provide the right link based on the HANA Version

bull Run the verification prior to the installation of SAP HANA as described in chapter

ldquoVerificationrdquo


See above

42


Additional Considerations for Large OLTP Installations Highly utilized OLTP systems with a large memory footprint need to cope with a vast amount of threads and network IO of small packages To ensure the optimal performance of these installations the following documents and SAP Notes should be reviewed

bull SAP Note 2188482 - SAP HANA on IBM Power Systems Allowed Hardware This SAP Note documents the current maximum of memory installed HANA minimum version and the SMT mode requirements

bull SAP Note 2519670 ndash Lock contention in ptimeQueryPlanHandlevalidate()

ptimeQueryPlanHandlereset() on a large scale IBM Power machine

bull Optional Verify the Network Configuration based on ldquoNetwork Configuration for HANA

Workloads on IBM Power Serversrdquo

bull Optional SAP Note 2081591 ndash FAQ SAP HANA Table Distribution

bull Optional SAP Note 2470289 ndash FAQ SAP HANA Non-Uniform Memory Access (NUMA)

SAP HANA Software The SAP HANA database should be installed according to the SAP HANA Installation Guides

SAP HANA tuning

There are various SAP HANA tuning notes Please apply all settings required for IBM Power Server SAP Note 2600030 - Parameter Recommendations in SAP HANA Environments

How to check the PAM

There is a short Guide (IBM only) with detailed instructions how to verify the Application availability in the PAM

Scale-out deployments

The recommendation from SAP and IBM is to first scale-up to the maximum before starting to scale out See SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host for the number of LPARs which can share a physical server Fitting all the LPARs in a physical server using VIOS benefits from advanced network throughput over the internal VLAN

Quick Reference SAP HANA Software

Please follow the below referenced SAP HANA Installation Guide and the SAP HANA on IBM Power Systems and IBM System Storage Supplemental IBM Installation Guide


bull See the release note for your specific HANA release (links provided in the reference section)

Verification Before installing the HANA software the setup should be verified Formerly the HWCCT was used Today IBM LBS and the Solution Support (see next chapter) provides advanced solutions Additionally the OS vendors provide auto tuning configuration and validation scripts described in the chapter before

43


Support and Services

Getting help and information from the World Wide Web for IBM products

On the World Wide Web the IBM website has up-to-date information about IBM systems optional devices services and support You can find service information for IBM systems and optional devices at Support Portal

Getting help and information for IBM Server and Storage mapping

People responsible for SAP HANA sizing who are not familiar with the SAP process and have not received quantified system requirements (memory GB cores or SAPS) for the SAP HANA project can contact their responsible IBM TechLine FTSS or ATS team for guidance through the official SAP sizing process

Standard Support Flow

Not using the centralized IBM service support and operation offerings for SAP HANA it must be

verified the product owner provides sufficient support Figure 32 Support Flow for HANA on Power Solution Stack outlines the standard support ownership of SAP HANA the operating system

and the hardware stack Stack brings the typical responsibilities into the context of SAP Support

Figure 31 Standard Support ownership of SAP HANA and Hardware Stack

Note To collect OS and HANA system configuration information use the sapsysinfo and HWCCT tool available through following SAP Notes SAP Note 618104 - sapsysinfo - Compiling system information on Linux SAP Note 1943937 - Hardware Configuration Check Tool - Central Note

(IBM) Storage

Server

IBM Power Server and PowerVM

SAN

Linux Operating System

HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support

providerSAP IBM Vendor

IB

GPFS

Filesystem used for SAP HANA Data and Log

44


Figure 32 Support Flow for HANA on Power Solution Stack

The above flow chart shows the support flow without the IBM Total Solution Support (TSS) capability which will be introduced in the following chapters as an optional solution for single point of contact incident management

IBM Services Support and Operation offerings for SAP HANA on POWER

Besides the SAP support and standard IBM support for the infrastructure components IBM intends to provide at GA a more comprehensive set of services to best support customers for SAP HANA on Power systems The following areas will be addressed by the services

Migration Support and Services The IBM Systems Lab Services Migration Factory is an experienced group of migration consultants with proven expertise to help clients design build and deliver successful migrations to IBM platforms This helps clients reduce the costs and risks of migration with proven processes specialized tools and many years of migration experience The Migration Factory has performed SAP and Database migrations from any competitive platform or database onto Power servers including SAP HANA on Power using a variety of native proprietary and third party tools to achieve our customers downtime requirements In 2017 the migration factory extended their offerings to address HANA migrations from big endian (HANA 10) to little endian (Hana 20) Details can be found on httpwwwibmcomsystemsserviceslabservicesmigrationfactoryindexhtml The SAP entry points for documentation are SAP Notes

httpslaunchpadsupportsapcomnotes2551355 httpslaunchpadsupportsapcomnotes2537080 httpslaunchpadsupportsapcomnotes2554012

Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a

problem record at the

vendor

Customer faces an issue with HANA on

Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified

Resolution remains in

regular SAP Support

Process

rootcause in

SAP code

configOS

Customer opens a problem

record at SAP referencing

the PMRIncident number


regular partner support

process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45


The following document outlines a sample migration httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102761

Planning and Installation

The planning process introduced in this paper which is based on a SAP sizing and an IBM mapping supported by the IBM TechLine Enablement SAP Sizing Questionnaire for Suite and BW (IBM only) can be enriched by the IBM Systems Lab Services These services will offer clients services for on-site SAP HANA Installations

IBM Total Solution Support

IBMreg Total Solution Support for SAP HANA on Power Systems trade provides an array of flexible support options for the full lifecycle of your SAP HANA on Power Systems infrastructure The offering helps you ease management and improve uptime with a single source of integrated break-fix how-to and proactive support for hardware and software It includes ongoing recommendations to help you prevent problems optimize system performance and reduce total cost of ownership for your SAP HANA on Power Systems infrastructure with a Single Point of Contact Since SAP HANA on Power Systems infrastructure includes a combination of different vendorsrsquo hardware and software systems proactive support from a vendor with multivendor and multiplatform expertise can be helpful By offering a variety of proactive services that are designed to optimize systems availability and stability our solution helps prevent costly outages that might have otherwise occurred without regularly scheduled maintenance support In addition through a highly skilled support team trained to deliver centralized and integrated support our offerings help provide a faster easier and more cost-effective way to expedite the resolution of virtually any problems To ensure the best possible problem resolution time for severity 1 issues the IBM SAP Center of excellence has a short linkage to the SAP Mission Control Center to ensure a joint problem determination team This link does only exist for customers with a IBM Total Solution Support contract

46


Figure 33 IBM Services for SAP HANA on POWER environments

The following Proactive Services are available bull Hardware Health Check for SAP HANA on Power (remote) bull Onsite Health Check for SAP HANA on Power (onsite) 5 days bull Microcode and Release Management for SAP HANA on Power This service is implemented in the e-configurator in the service section in Europe MEA and US In all other GEOS the seller has to contact TSS

Planning for IBM Total Solution Support

SAP and TSS require for production support to use SLES for SAP Applications In special this covers - ESPOS Expanded Service Pack Overlap Support - SAP Specific Update Channel for HANA and NetWeaver - SUSE HAE Cluster automation for SAP applications including SAP HANA - SAP-SUSE-Cluster Connector In combination with the IBM Total Solution Support for SAP HANA on Power the customer can benefit from the SLES for SAP Application L3 only subscription as TSS includes L1 and L2 automatically This will be the best price point for the customer

ServiceReport Tool

ServiceReport is a tool to validate repair and configure the system for specific purposes Initially envisaged to help setup systems for First Failure Data Capture (FFDC) it has now morphed into a plugin based framework which can do more than just FFDC validation ServiceReport is designed to run in two modes - validate and repair In the validate phase it runs a set of configured plugins to validate if the requisite checks (package install daemon config etc) pass and flags errors found to syslog In the repair phase if the system is configured correctly to contact the appropriate repos ServiceReport fixes the issues found in the validate phase The initial Open Source release of ServiceReport caters to all manners of Power platforms running Linux It validates the FFDC setup for the particular instance of Linux on Power (whether running on a PowerVM LPAR or Baremetal or as a KVM guest) For instance when run on a PowerVM based LPAR ServiceReport knows to check if the requisite RTAS services are installed and configured to run on boot (rtas_errd) ServiceReport also validates the dump configuration (kdumpfadump) and flags errors as found The repair action fixes all errors found in the validate phase including any crashkernel memory reservation issues for dumping updating the bootloader config regenerating initramfs files etc A further feature of ServiceReport is that it can trigger a dummy crash dump to validate the setup for dumping The plugin nature of ServiceReport lends itself to be useful for any platform on any architecture running Linux Anything scriptable can be a plugin - a workload specific setup can be a workload-plugin ServiceReport is Open Source and can be downloaded from

httpsgithubibmcomlinuxrasServiceReport Bugs and feature enhancements can be communicated through

httpsgithubibmcomlinuxrasServiceReportissues

47


New plugins enhancements bug fixes can be contributed by way of github pull requests


SUSE Linux Enterprise Server 11 on POWER Ordering Guide for SAP Application Environment (BP only) SLES on POWER Ordering Guide for SAP Environments V20 (SLES 12) These guides provide advanced details on offering details and ordering options Latest update New SLES on POWER Ordering Guide for SAP Environments for BPIBM on IBM Partner world published

Referenced documents This is a full list of documents used to write this planning Guide Some of these require special permissions Collaborating with IBM SAP or your Business Partner will provide access to all of them SAP Notes Due to the large amount of grown SAP HANA notes not all do reflect a 100 status for SAP HANA on Power To assist the following color coding is used

bull Work in progress

bull Not current

So if you see content not looking reasonable please contact your SAP representative to verify the status In cases where an SAP Note documents more current information than this Planning Guide the SAP Note supersedes this guide First color coding January 27th 2016 Last update June 5th 2018 SAP HANA Release Notes relevant for IBM Power

bull SAP Note 2133369 - SAP HANA on Power Central Release Note (Valid for SPS9 and SPS10) bull SAP Note 2227464 - SAP HANA Platform SPS 11 Release Note bull SAP Note 2380257 - SAP HANA Platform 20 SPS 00 Release Note bull SAP Note 2404375 - SAP HANA Platform 20 SPS 01 Release Note bull SAP Note 2460914 - SAP HANA Platform 20 SPS 02 Release Note bull SAP Note 2551355 - SAP HANA Platform 20 SPS 03 Release Note bull

SAP HANA Operating System Server and Storage Deployment

bull SAP Note 2161344 - HWCCT patch note bull SAP Note 1943937 - Hardware Configuration Check Tool - Central Note bull SAP Note 2501817 - HWCCT 10 (ge220) bull SAP Note 2382421 - Optimizing the Network Configuration on HANA-and OS-Level for SPS10

and Higher

bull SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note

bull SAP Note 1900823 ndash Storage Connector API (to make use of the connector API nPIV based

disc setup is required when using VIOS The mount points to configure when using share

disks are different to the ones when using a shared filesystem)

bull SAP Note 2130682 - SAP HANA on IBM Power Systems Documentation (HANA 1 SPS9 only) bull SAP Note 2235581 - SAP HANA Supported Operating Systems (the only entry point for all OS

Settings)

48


bull SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System Installation bull SAP Note 2205917 - SAP HANA DB Recommended OS settings for SLES 12 SLES for SAP

Applications 12 bull SAP Note 2240716 - SAP HANA DB Recommended OS settings for SLES 11 SLES for SAP

Applications 11 SP4 Is mostly covered in pdf attached to SAP Note 1944799

bull SAP Note 1275776 - Linux Preparing SLES for SAP environments bull SAP Note 2600030 - Parameter Recommendations in SAP HANA Environments

SAP HANA Sizing and Planning

bull SAP Note 2188482 - SAP HANA on IBM Power Systems Allowed Hardware bull SAP Note 2696290 - SAP HANA on IBM Power 8 Reference configuration bull SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host

(Extending SAP note 1788665 by Power Specifics)

bull SAP Note 1736976 - Sizing Report for BW on HANA (replaces SAP Note 1637145)

bull SAP Note 1514966 - SAP HANA 10 Sizing SAP In-Memory Database

bull SAP Note 1702409 - HANA DB Optimal number of scale out nodes for BW on HANA

bull SAP Note 1872170 - Suite on HANA sizing report (replaces SAP Note 1793345 )

bull SAP Note 1953429 - SAP HANA and SAP NetWeaver AS ABAP on one Server bull SAP Note 2396942 - hdbfilterserver for SAP HANA 2 Text Analysis on Little Endian IBM Power

Systems (obsolete SAP Note All available on Power LE) bull SAP Note 2367899 - BW-IP Planungsevents (sizing)

SAP HANA Migration

bull SAP Note 1813548 - Database Migration Option (DMO) of SUM

bull SAP Note 2537080 - Migrate SAP HANA 10 on IBM Power Systems Big-Endian to SAP HANA

20 on IBM Power Systems Little-Endian bull SAP Note 2551355 - SAP HANA Platform 20 SPS 03 Release Note (Migrating HANA1 to

HANA2 section)

bull SAP Note 2537080

bull The following document outlines a sample migration

httpwwwibmcomsupporttechdocsatsmastrnsfWebIndexWP102761

IBM Power Virtual Persistent Memory

bull There are no virtual Persistent SAP Notes available as of April222020 In the following the

SAP Notes reflect limitations of Optane (Intel) based solutions not allowing for the same

granularity and flexibility compared to virtual Persistent Memory

o 2700084 - FAQ SAP HANA Persistent Memory

o 2813454 - Recommendations for Persistent Memory Configuration with BW4HANA

Support bull SAP Note 618104 - sapsysinfo - Compiling system information on Linux

bull SAP Note 784391 - SAP support terms and 3rd-party Linux kernel drivers

bull SAP Note 1056161 - SUSE Priority Support for SAP applications

Other bull SAP Note 1514967 - SAP HANA Central Note (wording)

bull SAP Note 1599888 - SAP HANA Operational Concept (incomplete)

49


bull SAP Note 1642148 - FAQ SAP HANA Database Backup amp Recovery (links outdated) bull SAP Note 1999997 FAQ SAP HANA Memory

bull SAP Note 2000003 FAQ SAP HANA (outdated links)

bull SAP Note 2031547 - Overview of SAP-certified 3rd party backup tools and associated support

process (list not complete)

bull SAP Note 2039883 - FAQ SAP HANA database and storage snapshots bull SAP Note 2140959 ndash Dynamic Tiering bull SAP Note 218464 - Supported products when running SAP HANA on IBM Power Systems bull HANA 2 FAQ httpgosapcomdocuments20161182bad2f8-937c-0010-82c7-

eda71af511fahtml bull SAP Note 218464

bull The SAP HANA release documentation

httpshelpsapcomviewerpSAP_HANA_PLATFORM

bull SAP HANA in Data Centers

Although this is not always aligned with the latest HANA SPS capabilities it gives a summary

and good introduction in pretested deployment options

bull SAP Note 1825774 - SAP Business Suite Powered by SAP HANA - Multi-Node Support

Be careful with following SAP Notes as they only partially apply to Power deployments

bull SAP Note 1557506 ndash Page Cache Limits (applying these setting can cause hangs in HANA)

bull SAP Note 171356 - SAP Software on Linux General information

bull SAP Note 1730928 - Using external software in a HANA appliance

bull SAP Note 1730929 - Using external tools in an SAP HANA appliance

bull SAP Note 1730930 - Using antivirus software in an SAP HANA appliance

bull SAP Note 1730932 - Using backup tools with Backint for HANA

bull SAP Note 1730996 - Unrecommended external software and software versions

bull SAP Note 1730998 - Unrecommended versions of backup tools

bull SAP Note 1730999 - Configuration changes to SAP HANA system

bull SAP Note 1731000 - Configuration changes that are not recommended bull SAP Note 1954788 - SAP HANA DB Recommended OS settings for SLES 11 SLES for SAP

Applications 11 SP3 Is covered in pdf attached to SAP Note 1944799

bull SAP Note 2001528 - Linux SAP HANA Database SPS 08 SPS 09 and SPS 10 on RHEL 6 or SLES

11 Is verified by HWCCCT Not relevant for Power

bull SAP Note 2228351 - Linux SAP HANA Database SPS 11 revision 110 (or higher) on RHEL 6 or

SLES 11 Is verified by HWCCCT Not relevant for Power

bull SAP Note 2246163 - Indexserver crashes in the onLoad method (references not current)

bull SAP Note 1310037 - SUSE LINUX Enterprise Server 11 Installation notes

bull SAP Note 1855805 - Recommended SLES 11 packages for HANA support on OS level


SAP Documents

bull Sizing

o SAP HANA sizing (SAP Community Network Registered S-Users)

50


o Sizing Approaches for SAP HANA ndash Lessons Learned (current as of Oct2015

Some things have changed in the meantime)

o How to size SAP BW on SAP HANA

o Sizing for SAP S4HANA o Quick Sizer Tool (ensure to use the HANA Quick Sizer)

bull Storage and High Availability

o SAP Note 2407186 - How-To Guides amp Whitepapers For SAP HANA High

Availability

o SAP HANA TDI ndash Storage Requirements

o SAP Certified Enterprise Storage Hardware for SAP HANA

o SAP HANA ndash Network Requirements

o Introduction to High Availability for SAP HANA

bull Architecture o Certified and Supported SAP HANA Hardware Directory ndash IBM Power Server o SAP Certified Enterprise Storage Hardware for SAP HANA web-site for IBM

o SAP HANA Platform (all HANA related documents as in scope accordingly to SAP

Note 2130682 - SAP HANA on IBM Power Systems Documentation)

SAP HANA Server Installation Guide

SAP HANA Administration Guide

SAP HANA Master Guide

SAP HANA Security Guide

hellip

o SAP HANA core documentation sets SAP HANA Platform (Core) 20

o SAP HANA in Data Centers

o IT Planning Documents

o SUSE LINUX Enterprise Server Deployment Guide

o SUSE Knowledge Base

o SAP HANA TDI FAQ

IBM Documents bull Assistance

o IBM TechLine support

o SAP Sizing Questionnaire for Suite and BW

o ISICC SAP HANA on Power Systems (IBM only)

o SUSE Linux Enterprise Server 11 on POWER Ordering Guide for SAP Application

Environment (BP only)

bull SAP HANA and Hortonworks Data Platform (HDP) integration with SAP HANA Spark Controller running

on IBM Power Systems httpswwwibmcomdeveloperworkslibraryl-sap-hana-spark-controller-

integration-hdp

bull Storage

o IBM System Storage Architecture and Configuration Guide for SAP HANA TDI

o HANAmagic - Storage Sizing Tool for SAP HANA TDI (IBM and BP only)

o IBM FlashCopy backup solution for SAP HANA TDI

51


o IBM ESS (Spectrum Scale) Architecture and Configuration Guide for SAP HANA TDI

o SAP HANA on NetApp All Flash FAS Systems with NFS

o Optimizing Quality of Service with SAP HANA on Power Rapid Cold Start

o Best Practices Guide on how to configure SAP HANA TDI certified NetApp Storage

Systems with NFS

bull Hardware mapping

o ISICC SAPS Capacity Tables for Power Systems (IBM only BPs and customers

should contact the IBM TechLine for support)

o POWER8 Facts and features POWER9 Facts and Features

o Sales Support Information (SSI) (IBM only)

bull Deployment

o SAP HANA on IBM Power Systems and IBM System Storage (Supplemental IBM

Installation Guide to the SAP HANA Master Implementation and Administration

Guides) o SUSE Linux Enterprise Server for SAP httpswwwsusecomdocumentationsuse-

best-practices o Implementing High Availability and Disaster Recovery Solutions with SAP HANA on

IBM Power Systems

52


Copyrights and Trademarks copy Copyright 2020 IBM Corporation All Rights Reserved IBM Corporation Systems and Technology Group Route 100 Somers NY 10589 Neither this documentation nor any part of it may be copied or reproduced in any form or by any means or translated into another language without the prior consent of the IBM Corporation IBM makes no warranties or representations with respect to the content hereof and specifically disclaim any implied warranties of merchantability or fitness for any particular purpose IBM assumes no responsibility for any errors that may appear in this document The information contained in this document is subject to change without any notice IBM reserves the right to make any such changes without obligation to notify any person of such revision or changes IBM makes no commitment to keep the information contained herein up to date Edition Notice 2020 This is version 473 of this document IBM the IBM logo and ibmcom are trademarks or registered trademarks of International Business Machines Corp registered in many jurisdictions worldwide A current list of IBM trademarks is available on the web at Copyright and trademark information Adobe and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States andor other countries Intel Intel Xeon Itanium and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems Inc in the United States other countries or both UNIX is a registered trademark of The Open Group in the United States and other countries Linux is the registered trademark of Linus Torvalds in the United States and other countries Microsoft Windows Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both SAP HANA SAP NetWeaver are trademarks or registered trademarks of SAP Corporation in the United States other countries or both Oracle is a registered trademark of Oracle Corporation andor its affiliates Other company product or service names may be trademarks or service marks of others Information is provided AS IS without warranty of any kind Information concerning non-IBM products was obtained from a supplier of these products published announcement material or other publicly available sources and does not constitute an endorsement of such products by IBM Sources for non-IBM list prices and performance numbers are taken from publicly available information including vendor announcements and vendor worldwide home pages IBM has not tested these products and cannot confirm the accuracy of performance capability or any other claims related to non-IBM products Questions on the capability of non-IBM products should be addressed to the supplier of those products

Disclaimer and Special Notices This information could include technical inaccuracies or typographical errors Changes are periodically made to the information herein these changes will be incorporated in new editions of

53


the publication IBM may make improvements andor changes in the product(s) andor the program(s) described in this publication at any time without notice Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk Any performance data contained herein was determined in a controlled environment Therefore the results obtained in other operating environments may vary significantly Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems Furthermore some measurement may have been estimated through extrapolation Actual results may vary Users of this document should verify the applicable data for their specific environment Information concerning non-IBM products was obtained from the suppliers of those products their published announcements or other publicly available sources IBM has not tested those products and cannot confirm the accuracy of performance compatibility or any other claims related to non-IBM products Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products This information contains examples of data and reports used in daily business operations To illustrate them as completely as possible the examples include the names of individuals companies brands and products All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental COPYRIGHT LICENSE This information contains sample application programs in source language which illustrate programming techniques on various operating platforms You may copy modify and distribute these sample programs in any form without payment to IBM for the purposes of developing using marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written These examples have not been thoroughly tested under all conditions IBM therefore cannot guarantee or imply reliability serviceability or function of these programs

ANY INFORMATION HEREIN IS PROVIDED ldquoAS ISrdquo WITHOUT WARRANTY OR INDEMNIFICATION OF ANY KIND BY IBM AND DO NOT ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY FITNESS OR USAGE FOR PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT

Preface

About This Document

Figures

Tables

Introduction

The Planning Process

SAP Sizing for SAP HANA on POWER

Introduction

HANA Memory Sizing

HANA CPU Sizing


























Decide on Power and SAP features implemented to reduce Hardware or accelerate your workload



Introduction into Shared Processor Pools



Get to the right PowerVM SPLPAR settings for an SAP HANA LPAR


Eco System and Landscape aspects

Mapping SAP Sizing Output to IBM Power Systems Configurations






















Operating System





RHEL considerations



File System





Additional Considerations for Large OLTP Installations

SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool


Referenced documents

Copyrights and Trademarks

Disclaimer and Special Notices

2


Edition Notice and Version Information copy Copyright IBM Corporation 2020 All Rights Reserved US Government Users Restricted Rights ndash Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp All trademarks or registered trademarks mentioned herein are the property of their respective holders IBM Corporation Systems and Technology Group Route 100 Somers NY 10589 Edition Notice this is version 473 of this document Focus SAP HANA Scale-up and Scale-out solutions Target

bull SAP HANA 2

bull SAP HANA Platform Edition ndash SPS11 and above

bull SAP HANA version for IBM Power Systems architecture SPS 09 or SPS 10

Doc Version Changes 12 ndash 18 Changes documented up to version 21


30 ndash 33 Changes documented up to version 4 40 ndash 42 Changes documented up to version 43


46 (Nov062019

Add additional Information about Migration (SAP Note updates) Re-emphasize relaxations based on SAPrsquos TDI 5 approach LPM Mand SPLPAR Full SMT 8 support for all core counts

47 (July142020

Adding ldquoServiceReportrdquo to Support chapter (RAS setting validation + correction in Linux) New Sizing and Mapping chapter Easier TDI5 planning workflow First updates for SPLPAR vPMEM vNIC exploitation

Note Before using this information and the product it supports be sure to read the general information under rdquoCopyrights and Trademarksrdquo on page 52 as well as ldquoDisclaimer and Special Noticesrdquo on page 52

3


Preface


About This Document


4


Table of Contents

Introduction 7



Introduction 9


HANA CPU Sizing 10



































5



Operating System 39








File System 40







SAP HANA tuning 42





Verification42












Figures


6


































Tables


required by SAP) 37


by SAP) 38

7



8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





3


Preface


About This Document


4


Table of Contents

Introduction 7



Introduction 9


HANA CPU Sizing 10



































5



Operating System 39








File System 40







SAP HANA tuning 42





Verification42












Figures


6


































Tables


required by SAP) 37


by SAP) 38

7



8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





4


Table of Contents

Introduction 7



Introduction 9


HANA CPU Sizing 10



































5



Operating System 39








File System 40







SAP HANA tuning 42





Verification42












Figures


6


































Tables


required by SAP) 37


by SAP) 38

7



8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





5



Operating System 39








File System 40







SAP HANA tuning 42





Verification42












Figures


6


































Tables


required by SAP) 37


by SAP) 38

7



8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





6


































Tables


required by SAP) 37


by SAP) 38

7



8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





7



8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





8














HANA Installation



SAP Sizing



9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





9










Introduction


10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





10


HANA Memory Sizing



HANA CPU Sizing







Source DB

LPAR

Work Area

Main Area

hanadata hanalog

11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





11










Tools





Rule of Thumbs





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





12

















13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





13













14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





14







15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





15













16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





16









17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





17












12345

18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





18










19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





19













20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





20










21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





21













Extension Nodes


- Dynamic Tiering




22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





22





Extension node








23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





23






NSE















Need support



yes

24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





24
















25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





25







26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





26






HANA LPAR









critical systems



27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





27
















28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





28









Note


PowerVM Hypervisor

DedicatedDonating

LPAR

SharedPool LPAR

SharedPoolLPAR


Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR

Shared Pool LPAR






29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





29



















30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





30




















before





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





31





















Systems for LINUX)





additional workload



to SAP Note 2188482


SAPS available

yes

yes


yes





no

no

32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





32





bull Start-up time








bull Backup


options provided















33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





33













local directory





bull SAP HANA data







Central Note

bull SAP HANA log






34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





34



Central Note








o Backup












document from SAP














35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





35











HANA sizing effort






Customer SLAs




(Appserver VIOS )





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





36
































37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





37






Power Servers






















38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





38

























39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





39





bull Ethernet


bull Fibre Channel


data into memory












40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





40


HWCCT






RHEL considerations








41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





41






Note


















See above

42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





42











SAP HANA tuning











43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





43













(IBM) Storage

Server


SAN


HWCCT - TOOL

SAP HANA

Ethernet

SVC (optional)

Component owner

SAP AG

SAP AG

FS Distributor

OS Vendor

IBM

Product Vendor

IBM

Product Vendor

Component support


IB

GPFS


44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





44








Customer can

identify the origin

area of the problem

Open SAP OSS

Ticket on HAN-

yes

Customer opens an

IBM PMR

Customer opens a


vendor


Power Servers

no

Server

related

yes

Storage

Infrastructure

related

yes

Issue within

SAP

responsibility

yes

no Origin area

identified


regular SAP Support

Process

rootcause in

SAP code

configOS






process

noyes

no

Open SAP OSS

Ticket on HAN-

no

SAP code OS

configurationOS

related

Open SAP OSS

Ticket on HAN-

BC-OP-PLNX

BC-OP-LNXhellip

yes

45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





45







46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





46






ServiceReport Tool




47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





47







bull Not current





and Higher






Settings)

48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





48















SAP HANA Migration




HANA2 section)















49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





49


































SAP Documents

bull Sizing


50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





50








Availability












hellip






o SAP HANA TDI FAQ









integration-hdp

bull Storage




51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





51






Systems with NFS






bull Deployment





IBM Power Systems

52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





52




53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool





53




Preface

About This Document

Figures

Tables

Introduction



Introduction

HANA Memory Sizing

HANA CPU Sizing

























































Operating System





RHEL considerations



File System






SAP HANA Software

SAP HANA tuning





Verification









ServiceReport Tool



