sap hana on ibm power systems and ibm system …file/sap_hana_on_power-planning_4.4.pdf · sap hana...

SAP HANA on IBM Power Systems

and IBM System Storage

Planning Guide

IBM Deutschland Research & Development GmbH Created on July 8, 2014 – Version 0.0

Last modified on August 14th, 2018 – Version 4.4 © Copyright IBM Corporation, 2018

2

IBM Systems Solution for SAP HANA on POWER and IBM System Storage © Copyright IBM Corporation, 2018

Edition Notice and Version Information © Copyright IBM Corporation 2018. All Rights Reserved. US Government Users Restricted Rights – 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 4.4 of this document. Focus: SAP HANA Scale-up and Scale-out solutions Target:

• SAP HANA 2

• SAP HANA Platform Edition – SPS11 and above

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

Doc Version Changes 1.2 – 1.8 Changes documented up to version 2.1

1.9 – 2.5 Changes documented up to version 3.1

3.0 – 3.3 Changes documented up to version 4

4.0 – 4.2 Changes documented up to version 4.3

4.3 (July/5/2018)

Using the SLES auto config tool is recommended as per SAP note 1275776 - Linux: Preparing SLES for SAP environments. Consolidated HANA Tuning Note available: 2600030 - Parameter Recommendations in SAP HANA Environments. Removed Planning Sheets Two SAP HWCCT Notes. 1) up to HANA2 SPS1 and one starting from HANA2 SPS2 they have different OSS notes and needs to be called differently.

4.4 (August/14/2018)

New SLES on POWER Ordering Guide for SAP Environments for BP/IBM on IBM Partner world published. For SAP HANA 1.0 to SAP HANA 2.0 migrations the following two SAP Notes have been updated: SAP Note 2551355 and SAP Note 2537080 Power9 Support for SAP HANA on Power launched. See SAP Note 2188482: “… Power 9: The maximum of 24 cores & 4TB used by single HANA 2.0 (scale-up) must not be exceeded. For analytic workload (e.g. BW) up to 1.5 TB can be used. …“

Note: Before using this information and the product it supports, be sure to read the general information under ”Copyrights and Trademarks” on page 38 as well as “Disclaimer and Special Notices” on page 39.

https://www.ibm.com/partnerworld/wps/servlet/mem/ContentHandler/tech_WP102617

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, instead of enforcing additional investment into dedicated SAP HANA only appliances.

About This Document

This document is intended for architects and specialists planning an SAP HANA® on POWER® 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 Systems™, IBM System Storage®, IBM PowerVM®, 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 configuration 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: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502 Feel free to provide feedback and change requests for this document via email to one of the named authors.

https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=e4d11bf2-8632-4a00-ba19-d767a98a2cf3

http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502

4


Table of Contents

Introduction ............................................................................................................................................. 7

Hardware Planning .................................................................................................................................. 8

SAP Sizing for SAP HANA on POWER ................................................................................................... 9

SAP HANA Quick Sizer Method ......................................................................................................10

Migration sizing based on an existing system ...............................................................................11

SAPS Reference Tables for Hardware Mapping.............................................................................12

SAP HANA Data Temperatures ......................................................................................................13

Quick Reference: Get SAP HANA Sizing from SAP .............................................................................13

Links, References and Tools ...........................................................................................................13

Mapping SAP Sizing Output to IBM Power Systems Configurations .................................................14

SAP HANA deployment options and IBM Power Server ................................................................14

SMT8 is the recommended multi-threading mode. It changes for HANA OLTP-type workloads, if the

system/LPAR holds many cores, spanning 8 times of threads. SAP Note 2188482 ..............................17

Quick Reference: Find valid IBM Power Systems options .............................................................18


Mapping SAP I/O KPIs to a SAN Storage Design ................................................................................19

Planning Considerations for a valid Storage Type .........................................................................19

Background: SAP HANA filesystems and SAN storage...................................................................20

Additional Storage Sizing Considerations for Backup, DR and HA ................................................21

Additional Planning Considerations for SAP HANA scale-out installations ...................................21

Quick Reference: Find valid Storage Subsystem ...........................................................................22


SAP HANA Connectivity .....................................................................................................................22

Planning Considerations for Virtual IPs .........................................................................................23

Planning Considerations for VIOS I/O virtualization ......................................................................23

Planning Considerations: Single-Host SAP HANA (scale-up) .........................................................24

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

Quick Reference: I/O Adapter Definition ......................................................................................26


Operating System ..................................................................................................................................26

Software and Operating System ....................................................................................................26

HWCCT validation ..............................................................................................................................26

Power 9 SLES considerations .............................................................................................................27

SLES 11 considerations ......................................................................................................................27

SLES 12 considerations ......................................................................................................................27

RHEL considerations ..........................................................................................................................27

Quick Reference: OS Planning ...........................................................................................................27

Links, References and Tools ...............................................................................................................28

File System .............................................................................................................................................28

Planning Considerations for XFS with Multi-pathing .........................................................................28

5


Planning Considerations for IBM Spectrum Scale .............................................................................28

Quick Reference: File System Definition ...........................................................................................29

Links, References and Tools ...............................................................................................................29

Additional Considerations for Large OLTP Installations ........................................................................29

SAP HANA Software ...............................................................................................................................29

SAP HANA tuning ...............................................................................................................................29

How to check the PAM ......................................................................................................................29

Scale-out deployments ......................................................................................................................29

Quick Reference: SAP HANA Software. .............................................................................................30

Links, References, and Tools ..............................................................................................................30

Verification.............................................................................................................................................30

Support and Services .............................................................................................................................30

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

Getting help and information for IBM Server and Storage mapping ................................................30

Standard Support Flow ......................................................................................................................30

IBM Services, Support and Operation offerings for SAP HANA on POWER ......................................32

Migration Support and Services ........................................................................................................32

Planning and Installation ...................................................................................................................32

IBM Total Solution Support ..............................................................................................................32

Planning for IBM Total Solution Support .......................................................................................33

Links, References and Tools: ..........................................................................................................33

Referenced documents ..........................................................................................................................34

Copyrights and Trademarks ...................................................................................................................38

Disclaimer and Special Notices ..............................................................................................................39

Figures

Figure 1 SAP HANA on IBM Power Servers Planning Process.................................................................. 8

Figure 2 SAP HANA QuickSizer input panel ...........................................................................................10

Figure 3 HANA Quick Sizer S/4HANA results example ..........................................................................11

Figure 4 Sample get_size report output ................................................................................................12

Figure 5 TDI5 BW Utilization categories ................................................................................................12

Figure 6 Quick Reference: "Get SAP HANA Sizing from SAP" ................................................................13

Figure 7 PowerVM LPAR types ..............................................................................................................15

Figure 8 SAP HANA Category and Features in eConfig ..........................................................................16

Figure 9 Quick Reference: Mapping SAP Sizing Output to IBM Power Systems ...................................18

Figure 10 Quick Reference: Find valid Storage Subsystem ...................................................................22

Figure 11 Standard Support ownership of SAP HANA and Hardware Stack .........................................31

Figure 12 Support Flow for HANA on Power Solution Stack .................................................................31

Figure 13 IBM Services for SAP HANA on POWER environments .........................................................33

6


Tables

Table 1. Minimum Single-Host SAP HANA I/O connectivity for production (floor configuration as

required by SAP) ....................................................................................................................................24

Table 2. Minimum Multi-Host SAP HANA I/O connectivity per Server (floor configuration as required

by SAP) ...................................................................................................................................................25

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 – 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 e.g. S4/HANA the available POWER8 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 AIX/IBM 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 (S/4HANA, BW/HANA), as well as many traditional Business Suite applications have become available. IBM Power Systems have been integral part of the SAP HANA 2.0 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 “reference configuration” by SAP) to a SAPS based CPU sizing derived from the required HANA memory and targeted workload. Basically, this allows Power Systems to become more efficiently sized, while better exploiting PowerVM virtualization mechanisms. Meanwhile more than 850 customer deployments provide evidence that IBM Power Systems are very well suited to provide excellent SAP HANA database performance and reliability. SAP HANA on POWER exploits excellent memory bandwidth, SIMD parallelization, and Simultaneous Multi-Threading (SMT), which contribute to large throughput gains, in particular when customers migrate from a scale-out to a scale-up HANA topology.

8


Hardware Planning The following sections describe the hardware selection criteria and validation process based on an SAP sizing along the workflow outlined in Error! Reference source not found.:

Figure 1 SAP HANA on IBM Power Servers Planning Process

The orange part represents the initial SAP owned sizing process as described in chapter SAP Sizing for SAP HANA on POWER, which delivers some background information on the SAP HANA sizing methodologies and tools. Further, it helps to identify the appropriate planning resources provided by SAP and IBM. The blue parts refer to the IBM specific SAP HANA on POWER hardware design and layout steps which are described in three chapters:

• Mapping SAP Sizing Output to IBM Power Systems Configurations Describes, how to select the right server model and how to leverage PowerVM virtualization capabilities for scale-up and scale-out deployments of SAP HANA.

• Mapping SAP I/O KPIs to a SAN Storage Design Besides designing the I/O infrastructure to comply with the SAP TDI performance characteristics for the persistent data and log files, the requirements to achieve a suitable startup time of SAP HANA is also included.

Identify Power System with sufficient DIMM and

adapter capacity

Identify and Layout Storage System(s)

Map LAN & SAN I/O adapters into

selected system

Verify SAP KPI-compliance of the

deployed system

Obtain required hardware capacity

requirements from SAP

Complete SAP HANA

Quicksizer process

Apply SAP tools versus

existing DB

Calculate socket/core count

Enforced by # of DIMMs Match sizing output with SAPS capacity

table for cross check

Meet RTO and RPO

objective

Match sizing output with

storage space

OS System deployment

SAP defined HANA Memory and Disk

configuration, SAPS

HANA System deployment

9


External and internal disks can be used. External disk subsystems must be TDI vendor certified and listed in the SAP HANA Hardware Directory. In all cases the selected storage configuration must achieve the performance KPIs set by the HWCCT tool (See SAP Note 2501817). Specific ESS Storage design documentation is available on IBM Techdocs: “IBM ESS (Spectrum Scale) Architecture and Configuration Guide for SAP HANA TDI”.

• SAP HANA Connectivity Provides details on selecting the appropriate Fibre-Channel and Ethernet cards and their configuration to accommodate the SAP requirements.

These chapters explain the background and provide the related IBM and SAP materials to select and configure the hardware. It is important to consider these planning items as a whole in the context of the individual SAP system landscape. The green parts represent the Operating System (OS) and SAP HANA software setup described in chapter “Software and Operating System”. Finally, the red box explains the verification of the deployed hardware and software stack. It is a mandatory task to ensure production readiness of each individual customer installation. Details and how to ensure datacenter readiness using the SAP HWCCT (Hardware Configuration Check Tool) tool is documented in the chapter “

Verification”. Support channels, IBM service offering details and contacts are summarized in chapter “Support and Services”. IBM provides additional guides such as installation handbooks, planning spreadsheets etc. on SAP HANA on IBM Power Systems and IBM System Storage - Guides. Redbooks about implementing best practices for SAP HANA HA/DR and Backup/Restore are available via the public IBM Redbooks site.

SAP Sizing for SAP HANA on POWER

IBM Power Systems are not sold as an SAP HANA appliance. Instead, SAP requirements can be mapped to any Power System listed on the SAP HANA Hardware Directory, as long as it provides the resources defined by the design considerations discussed in this document. Sizing for SAP HANA (on POWER) is based on methodologies and tools provided by SAP SE. Their output will specify vendor and platform independent SAP HANA system requirements in regards to compute, memory and disk requirements. These values only cover the HANA database portion of a whole solution landscape. They neither include landscape (app-servers, pre-PROD stages), nor resiliency aspects. However, SAP HANA on POWER system configurations should not only focus on the SAP HANA database instance itself, but also consider resources for SAP application servers and other systems running in the customer’s datacenters. Aggregating instance capacities and consolidating those with PowerVM will establish a more efficient usage of IBM Power Systems and at the same time can provide a performance improvement by co-location. Therefore always consider end-to-end solutions throughout the design process also looking at other requirements as for example SAP HANA Database resiliency and other (SAP) applications around the HANA database layer. System sizing for SAP HANA and its configuration is dominated by the physical memory demand of the HANA instance, respectively the amount of “hot” business data to be maintained in memory. As a first, rough estimate you can expect the compressed HANA data in-memory footprint to be 1/4th of the uncompressed source business data. For internal processing and temporary work space a HANA

https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/enterprise-storage.html





https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/power-systems.html

10


system requires the same amount of physical memory, resulting in an estimated physical memory amount of ½ of uncompressed source SAP database size. Two official SAP HANA sizing methods are available to get more exact results:

SAP HANA Quick Sizer Method

This method should only be used for initial/green-field HANA sizing. Whenever possible the Migration-Sizing method described below should be used, as it provides more accurate results. Since SAP introduced a special HANA-variant of the Quick Sizer in 2014, it has been enriched to cover various application scenarios.

Figure 2 SAP HANA QuickSizer input panel

The HANA Quick Sizer supports business components and modules which are running on top of a SAP HANA database. They have to be pre-selected before entering their specific user or quantity workload. Most sizings are user based, and thus less accurate. However, only few customers are able to provide comprehensive volume based input data at the beginning of a SAP (HANA) project. If available though, volume data should always be the preferred Quick Sizer input. The HANA Quick Sizer will provide a memory, SAPS and I/O result. The SAPS result should then be translated to the appropriate number of processor cores.

11


Figure 3 HANA Quick Sizer S/4HANA results example

Before the announcement of TDI 5, the core count was determined by a fixed Core-To-Memory (CTM) ratio for OLTP- and OLAP-workloads. This has now been replaced by the SAPS output of the SAP tools. SAP Note 2188482 - SAP HANA on IBM Power Systems: Allowed Hardware defines the current max memory configurations to be applied. This SAP Note still outlines the old core to memory ratio for P8 Servers titled as “reference configuration”. The resulting SAPS need to be matched to vendor provided server SAPS capacity tables - see the section below for IBM Power Systems.

Migration sizing based on an existing system

Customers with existing SAP Business Warehouse and Business Suite implementations now migrating to SAP HANA must run a SAP provided report within their existing system. SAP SE makes this step mandatory for customers running SAP solutions on traditional databases, as it provides more accurate and detailed sizing results than the HANA Quick Sizer approach. 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. According to their application customers must execute the ABAP reports attached to one of these SAP-Notes:

• SAP Note 2296290 New BW Sizing Report

• SAP Note 1872170 - Business Suite on HANA and S/4HANA sizing report

With TDI 5 the BW-Report has been extended to include CPU capacity requirements reported in SAPS in addition to a memory calculation. Customers need to comply with the conditions outlined in this SAP-Note to activate the CPU analysis:

• SAP Note 2502280 - Adding CPU requirements analysis to BW/4HANA sizing report

o This will output the CPU (SAPS) requirement, if pre-requisites are confirmed.

At the time of writing this function is only available for BW environments, not yet for ERP or S/4HANA systems.

https://launchpad.support.sap.com/#/notes/2188482/E

https://launchpad.support.sap.com/#/notes/2296290



12


The result section of the TDI 5 BW-report looks like in this example, including CPU sizing. It is calculated on the individual analysis of the customer’s source system and the resulting physical memory size:

Figure 4 Sample get_size report output

Note: Two things can lower the overall memory footprint of a HANA. 1. For HANA nodes bigger than 2GB the sizing rules can make better utilization of the master node. 2. For each node a Memory Footprint of at least 100Gb is introduced to to overall sizing by OS and HANA requirements.

If a sufficient number of query statistics could be analyzed, another result is the classification of this workload into a workload class L / M / S, see bottom line in the example:

Figure 5 TDI5 BW Utilization categories

The workload or CPU classes reflect the characteristic of transactions and queries. With the introduction of TDI 5, Class M and S provide relief in terms of required CPU capacity compared to the previous CTM based sizing.

SAPS Reference Tables for Hardware Mapping

Independent from the defining method the SAPS results can be mapped to the SAPS capacity of the Power Systems, which are listed in the ISICC SAPS Capacity Tables for Power Systems (IBM only). Here all systems that provide sufficient SAPS and maximum memory capacity can be selected as a valid base system. Larger systems can be used to host multiple HANA or further SAP systems in LPARs. SAPS can be linearly interpolated per core count in order to determine LPAR sub-capacities. IBM employees can

https://w3-connections.ibm.com/blogs/db4b6082-e758-423f-acae-becdec160371/entry/Migration_of_Power_Systems_Capacity_Tables_from_Lotus_Notes_DB_to_Community?lang=en_us

13


find additional guidance in the paper Sizing-Info-SAP-HANA-Database-on-IBM-Power-Server and the ISICC Sizing Community(IBM only). Sizing support can be requested from the IBM Digital TechLine Center (DTC) using the SAP specific TechLine Support Request Generator (IBM only) link.

SAP HANA Data Temperatures

In order to reduce the (expensive) in-memory footprint of business data, SAP has introduced various technologies. All use the principle of data temperatures (hot/warm/cold), which in many cases refer to the concurrency of data for ongoing business transactions versus historical, i.e. 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:

- Data aging (retention periods of data can be specified in Quick Sizer)

- Dynamic Tiering

- SAP HANA BW Extension nodes

The more data are offloaded from the “hot” data segment, the less resources are required for the

HANA nodes - obviously at cost of worse access time for the warm and cold data sets.

Quick Reference: Get SAP HANA Sizing from SAP

Figure 6 Quick Reference: "Get SAP HANA Sizing from SAP"

Links, References and Tools

• Background information on memory and CPU capacity:

SAP publishes a document Sizing Approaches for SAP HANA – Lessons Learned (This

document was current as of October 2015. Some content is outdated in the meantime).

• The ISICC SAPS Capacity Tables for Power Systems (IBM only) contain a “Maximum

Memory” column to identify maximum possible system memory in GB, dependent on

number of sockets.

• How to size SAP BW on SAP HANA

Make yourself familiar with HANA Sizing basics to be able to complete the

„SAP Sizing Questionnaire for Techline or the SAP HANA Quicksizer Tool

(see: „Links, References and Tools“ subchapter)

Complete SAP Quicksizer process or use the SAP Sizing

Questionnaire from Techline (www.ibm.com/erp/sizing)

Apply SAP tools versus existing DB

(Use provied SAP Notes)

Need

support ?

contact your respective TechLine, FTSS

and/or ATS team

Quantified system requirements (memory GB, cores, SAPS, volume)

available from SAP.

Business

Warehouse

yes

yes

https://w3-connections.ibm.com/files/app/file/040d4a0a-3801-4607-9fd5-f64d5f39f681

https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=4d96dfe7-b689-465c-896a-d7c6cad1621b

https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W7035da1c75b4_493d_8e8c_76839416c7cc/page/--SAP

https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W7035da1c75b4_493d_8e8c_76839416c7cc/page/--SAP

https://websmp108.sap-ag.de/~sapidb/011000358700000050632013E

notes://d06dbl044/m_dir/me018116.nsf

https://scn.sap.com/docs/DOC-61091

14


• Sizing for SAP S/4HANA

• IT Planning Documents (SAP Wiki)

• SAP Sizing Questionnaires by DTC

• Quick Sizer Tool

• SAP Note 2367899 - BW-IP: Planungsevents (sizing)

Read more about SAP HANA sizing on SAP Community Network (registered S-Users only) • Guide to Effective Sizing of SAP HANA

• Sizing Approaches for SAP HANA

and these central SAP Notes about SAP HANA sizing:

• SAP Note 2502280 - Adding CPU requirements analysis to BW/4HANA sizing report (TDI 5)

• SAP Note 2296290 - New Sizing Report for BW on HANA (replaces SAP Note 1736976)

• SAP Note 1872170 - Business Suite on HANA and S/4HANA sizing report

• SAP Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database (includes Sidecar)

• SAP Note 1599888 - SAP HANA: Operational Concept

Mapping SAP Sizing Output to IBM Power Systems Configurations

The server decision has to be made to fit the memory, CPU and I/O 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) + SLA requirements 2) Adapter/storage planning

= SAP TDI/Ethernet sizing + VIOS + SLA requirements

3) The size of the IBM Power Server running multiple partitions next to HANA =

workload consolidation + VIOS

SAPS and maximum memory specifications of Power Systems are maintained in the POWER SAPS Capacity tables. It can be accessed by IBMers after an initial registration.

Note: There is no linkage between SAP HANA scale-up/scale-out and the IBM Power E- and S-class models. Both – E- and S-class models – 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 a dedicated(-donating) LPAR running on it. Multiple single-node HANA databases and other workloads can be consolidated on a single server. A shared pool can be used for all LPARs not running a SAP HANA production instance. SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host documents supported LPAR configurations.

http://scn.sap.com/docs/DOC-59920

http://wiki.scn.sap.com/wiki/display/ITP/List+of+IT+Planning+Documents

https://ibm.box.com/v/questionnaireSAP

http://service.sap.com/quicksizer


http://scn.sap.com/community/hana-in-memory/blog/2013/01/17/sap-hana-sizing

https://blogs.sap.com/2017/03/07/the-ultimate-guide-to-effective-sizing-of-sap-hana/







https://w3-connections.ibm.com/communities/service/html/communityoverview?communityUuid=e8e3b159-92d8-48f8-a070-955264abefc3#fullpageWidgetId=W0a495369baff_48f5_a614_852c0d13219e


https://launchpad.support.sap.com/#/notes/ 2230704/E

15


Figure 7 PowerVM LPAR types

For production HANA partitions, there is a range of available partition sizes in any IBM Power Server with POWER8 processor architecture. The partition must be between the floor (defined by the size of the smallest possible HANA LPAR, typical 4 cores) and ceiling (defined by the size of the largest possible HANA LPAR. 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: 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 should include that the standby server can host additional non-production workloads on the HANA LPAR when running in the “cost optimized” mode. Depending on the system replication operation mode (delta_datashipping versus logreplay), around 10-50% of resources are used by the standby instance. The remaining resources can be used for temporary workload on the HANA LPAR. For more details, read the SAP HANA documentation or contact your cluster vendor automating the SAP HANA SR (Some cluster vendors do automate also the handling of “cost optimized” deployments). 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:

• 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

• 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 (IBM only).

• 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

Power Server Hardware

PowerVM Hypervisor

Dedicated/Donating

LPAR

Dedicated/Donating

LPAR

Dedicated/Donating

LPAR

Shared Processor Pool

Shared Pool

LPAR

Shared Pool

LPAR

Shared Pool

LPAR

Shared Pool

LPARShared

Pool LPAR

Shared Pool

LPAR

Virtual Shared Processor Pool n

Virtual Shared Processor Pool 1

Application Servers, non-production HANA

instances, optimizer, ...HANA Production



https://w3-03.sso.ibm.com/sales/support/index_en_US.html

https://w3-03.sso.ibm.com/sales/support/ShowDoc.wss?docid=POB03046USEN&node=&ftext=Power8%20Facts%20and%20Features&sort=date&sno=rating&showDetails=show&hitsize=25&offset=0&fromdate=&todate=&filtermessage=&option=&searchin=entiredoc&isw=&sw=&swv=&l=&s=desc&campaign=


16


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.

• Within IBM eConfig a server category for “HANA models” is available. These differ from the

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

preselect the “Linux for SAP” 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.

Figure 8 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 (i.e., 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 “HANA Sizing” chapter. With the introduction of SAP HANA 2.0, the default deployment mode has changed to MDC (multi-tenant database containers). A single or multiple HANA databases reside within a single HANA




17


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

system/LPAR holds many cores, spanning 8 times of threads. SAP Note 2188482

documents the threshold and target SMT level.

Virtualization / LPARs performance related considerations

In order to minimize Hypervisor dispatching latency and to provide best memory affinity, only dedicated or dedicated donating LPARs are supported for SAP HANA production partitions. Partitions with dedicated donating processor configurations combine the performance benefits of dedicated CPU resources – in particular minimized dispatching latency - with efficient re-use of surplus CPU cycles by other partitions running in a shared processor pool. The dedicated partitions receive absolute priority for dedicated CPU cycles, and sharing will only occur when the dedicated partition does not consume its resources. 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:

• 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.

• 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.

• 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.

• 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.

• 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 I/O Adapter Capacity

Please see chapter “SAP HANA Connectivity” 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 “SAP HANA Connectivity”.





18


Quick Reference: Find valid IBM Power Systems options

Figure 9 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):

• POWER8 Facts and Features (IBM only)

• Sales Support Information (IBM only)

• Certified and Supported SAP HANA Hardware Directory – IBM Power Server

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

Note: Additional processors and memory are required for Virtual I/O server partitions (VIOS) and PHYP. Power Hypervisor (PHYP) also uses memory – 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.

Quantified system requirements

available from SAP HANA Sizing

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

(see POWER Systems Facts & 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 I/O Adapter Requirements

List of valid IBM Power Servers available.

Add additional requirements for

additional workload

(e.g. VIOS, Appserver, ...)

FOR PRODUCTION: partition is sized accordingly

to SAP Note 2188482

core/memory 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


http://repository.techline.ibm.com/systemx/contact/contact/



http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/power-systems.html


19


Mapping SAP I/O KPIs to a SAN Storage Design

External and internal disks can be used. External disk subsystems must be SAP HANA TDI certified. In all cases, the selected storage configuration must achieve the performance KPIs set by the HWCCT tool. See SAP Note 1943937 - Hardware Configuration Check Tool - Central Note for details. The sizing output of the Quick Sizer is not specific enough. The SAP HANA Server Installation Guide, the SAP HANA TDI – 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 HANAon Power Rapid Cold Start The requirements introduced by the SAP HANA I/O characteristics for the file system and the underlying storage have four planning objectives:

• 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.

• 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.

• Backup:

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

options provided.

• Data Protection:

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

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 (e.g. 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 “HWCCT” 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).

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.


http://help.sap.com/hana_platform#section2


https://www.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=POW03190USEN&


http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html#categories=certified%2CInternational%20Business%20Machines%20Corporation



20


Use the following SAP documents as a starting point: SAP HANA TDI – 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 I/O bandwidth leveraging a balanced blend of HDDs and SSDs/Flash. 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 – 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:

• SAP HANA install directory and /usr/sap

local directory

• 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.

• 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.

• SAP HANA log

Benefits from low latency I/O 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.

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.

• The Operating System



http://w3.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS4555










21


Additional Storage Sizing Considerations for Backup, DR and HA

An SAP HANA database landscape also requires space and functionality for:

• 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

• High availability data protection.

o E.g. IBM Spectrum Virtualize (formerly SVC) stretched clusters

• 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 I/O

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:

• 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

• 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.







22


Quick Reference: Find valid Storage Subsystem

Figure 10 Quick Reference: Find valid Storage Subsystem


SAP Documentation: SAP HANA TDI – Storage Requirements SAP Certified Enterprise Storage Hardware for SAP HANA SAP HANA Administration Guide 2407186 - How-To Guides & 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 – among other tests – conducts a data throughput test using the “SAP HANA Hardware Configuration Check Tool”. 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: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102347 A Best Practices Guide on how to configure SAP HANA TDI certified NetApp Storage Systems with NFS can be found at: http://www.netapp.com/us/media/tr-4435.pdf 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: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102644 Tools: Quick Sizer Tool The IBM provided “HANAmagic - Storage Sizing Tool for SAP HANA TDI” figures to address not only volume oriented requirements, but also RTO – i.e. the time to restore a HANA database from disk to server memory – impact of various IBM storage technologies incl. FlashSystems. (BP and IBM only)

SAP HANA Connectivity

The I/O 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

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 (SSD/Flash vs. HDD)

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

Ensure later the I/O 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 I/O performance

using the SAPmagic tool for HANA

Add additional requirements (e.g.

VIOS, SAP Appserver, ...)



http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html





http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102347

http://www.netapp.com/us/media/tr-4435.pdf



https://www.ibm.com/partnerworld/wps/servlet/ContentHandler/tech_PRS5340

23


installed dedicated or shared (e.g. using dual VIOS). With PowerVM, additional workload can be put on the same server, this must be reflected in the overall planning. SAP HANA connectivity planning needs to consider bandwidth requirements for the following communication paths:

• 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+ and/or scale-out)

o Administrator network

• Storage – 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:

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

virtual IPs to operate on the SAP instances.

• 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 TCP/IP host names and SAP Note 1900823 - SAP HANA Storage Connector API provide additional information

Planning Considerations for VIOS I/O virtualization

All I/O 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:

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

4 paths to utilize multi-pathing for I/O workload.

• 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:

• I/O sensitive internode communication does not exist for scale-up. Using the full bandwidth

of a 10Gb Ethernet port is no functional requirement for scale-up HANA installations (except

for HA scenarios based on HANA System Replication).

• SR-IOV and RoCE capable adapters should be considered for Ethernet connectivity, but

should be implemented traditionally using SEA Failover.

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.




24


• For traditional Ethernet virtualization, plan for appropriate CPU sizing and dedicated

donating cores for the VIOS partitions.

• 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. Detailed setup and planning instructions can be found on

Network Configuration for HANA Workloads on IBM Power Servers

• 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 recommended VIOS level is 2.2.4.10.

o The kernel module “ibmveth” of your Linux must be version 1.05 or higher

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

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

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

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

physical adapters and sharing can be applied.

• 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 I/O adapter requirements for a production SAP HANA system on SAN with XFS using dual-VIOS are2: Table 1. Minimum Single-Host SAP HANA I/O 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 I/O from Business application I/O. The 10Gbit/s 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. 10Gbit/s between data centers is recommended by SAP.3 Growth can be achieved transparently to the application.

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 (e.g. Live Partition Migration (LPM)) are used. 3 The peak load of 2.4Gb/s 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.




25


SAN / FC Attachment to data and log persistency

Min. 8Gb connectivity for at least 4 paths multipathing.

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 – Network Requirements . This applies directly to all dedicated adapter deployments not using VIOS technology. Using VIOS sharing these resources becomes a desirable an option:

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

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

physical adapters and sharing can be applied.

• 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 requirements for a production SAP HANA system on SAN with XFS using dual-VIOS are: Table 2. Minimum Multi-Host SAP HANA I/O connectivity per Server (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.

SAP HANA shared network should be 10GbE connectivity

SAP HANA inter-node connects

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

Backup Network (optional) SAP wants to separate Backup I/O from Business application I/O. The 10Gbit/s 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. 10Gbit/s between data centers is recommended by SAP.4 Growth can be achieved transparently to the application.

SAN / FC Attachment to data and log persistency (SAN)

Min. 8Gb connectivity for at least 4 paths multipathing.

4 The peak load of 2.4Gb/s 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.



26


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

Gb Ethernet connectivity.

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 “IBM ESS (Spectrum Scale) Architecture and Configuration Guide for SAP HANA TDI”.

Quick Reference: I/O Adapter Definition

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

• Ethernet:

o Multi part cards are available also with mixed speed ports.

• 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 – 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 “Links, References and Tools” 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. How to best leverage the Power capabilities in conjunction with the SUSE operating system is documented in the IBM Installation Guide for SAP HANA.

HWCCT validation

The HWCCT test is often not current with the latest SAP HANA Notes. In case The Landscape test fails this is no inhibitor to continue. In case of a failure please verify you have applied the SAP Notes referenced in this section (including the relevant links in the SAP Note) and open a SAP Incident. In case the I/O tests do not operate for a given setup (e.g. scale-out) download an old version based on HANA 2 SPS1 (Python scripts). The results will not vary from the latest ones.









http://www.ibm.com/support/docview.wss?uid=isg3T1024094




27


Power 9 SLES considerations

With GA we recommend to start with a minimum kernel of 4.4.140-94.42-default (rpm: kernel-default-4.4.140-94.42.1.ppc64le) for SLES 12 SP3

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-3.0.101-108.7.1.ppc64.rpm". 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: https://download.suse.com/Download?buildid=HDdQHihdFrk~

HWCCT:

• 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.

• 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 considerations

Preferably start with SLES 12 SP3. For configuration use the auto tuning tool of SLES as described in SAP Note 1275776 - Linux: Preparing SLES for SAP environments.

RHEL considerations

Since October 6th 2017 SAP supports also Red Hat as an Operating System for SAP HANA on Power. The first release supported is RHEL 7.3. The entry SAP Note for documentation is 2235581 - SAP HANA: Supported Operating Systems. SAP references from there the already published material. The following minimum packages/kernel are:

• RHEL 7.3 kernel-3.10.0-514.28.1.el7

• RHEL 7.3 kexec-tools-2.0.7-50.el7_3.2

• RHEL 7.3 glibc-2.17-157.el7_3.5

Architecture relevant materials:

• https://access.redhat.com/articles/rhel-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.

https://download.suse.com/Download?buildid=HDdQHihdFrk%7E


https://access.redhat.com/articles/rhel-limits



28



Installation Guides: SAP HANA Server Installation Guide SUSE LINUX Enterprise Server Deployment Guide SUSE Knowledge Base SUSE Linux Enterprise Server for SAP: https://www.suse.com/documentation/suse-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, /usr/sap, and file systems for other applications, a special thought must be given to /hana/data, /hana/shared, and /hana/log. The /hana/shared 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 /hana/data and /hana/log 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 “Hardware Planning” chapter.

Planning Considerations for XFS with Multi-pathing

Using XFS with multi-pathing and LVM striping provides desirable options to optimize the I/O 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:

• 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).

• 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.

• 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


https://www.suse.com/documentation/sles11/book_sle_deployment/?page=/documentation/sles11/book_sle_deployment/data/book_sle_deployment.html

https://www.suse.com/support/kb

https://www.suse.com/documentation/suse-best-practices/











29


Quick Reference: File System Definition

• 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.

• 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).

• 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.

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

“Verification”.


See above.

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 I/O of small packages. To ensure the optimal performance of these installations, the following documents and SAP Notes should be reviewed:

• 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

• SAP Note 2519670 – Lock contention in ptime::Query::PlanHandle::validate()/

ptime::Query::PlanHandle::reset() on a large scale IBM Power machine

• Optional: Verify the Network Configuration based on “Network Configuration for HANA

Workloads on IBM Power Servers”

• Optional: SAP Note 2081591 – FAQ: SAP HANA Table Distribution

• Optional: SAP Note 2470289 – 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.














https://w3-connections.ibm.com/communities/service/html/communityview?communityUuid=e4d11bf2-8632-4a00-ba19-d767a98a2cf3

30


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.

Links, References, and Tools

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

Verification Before installing the HANA software, the setup must be verified with the SAP HANA Hardware Configuration Check Tool (HWCCT). It provides several modules to verify the configuration, but cannot guarantee a 100% perfect setup. For SAP HANA on POWER in a scale-up deployment, only the Landscape- and the Filesystem-Test are relevant to validate the environment before going life or after configuration changes. Ensure to keep ongoing records of the HWCCT output containing the KPIs for the file-system test and the HWCCT version used. This is useful in case of support situations and for regular health checks. The HWCCT tool:

• MUST be used before go life

• SHOULD be used after each change in the landscape

• Is RECOMMENDED for regular health checks

The minimum KPI figures and instructions up to HANA 2 SPS1 on how to run and configure HWCCT can be found in SAP Note 1943937 - Hardware Configuration Check Tool - Central Note. Starting with HANA2 SPS2 please use SAP Note 2501817 - HWCCT 1.0 (≥220).

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 12 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.




https://www.ibm.com/support/entry/portal/support.

https://repository.techline.ibm.com/powersystems/ISVsoln/ISVSAP/

31


Figure 11 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

Figure 12 Support Flow for HANA on Power Solution Stack

(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

provider:SAP IBM Vendor

IB

GPFS

Filesystem used for SAP HANA Data and Log

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/

config/OS

Customer opens a problem

record at SAP referencing

the PMR/Incident number.

Resolution remains in

regular partner support

process

noyes

no

Open SAP OSS

Ticket on HAN-*

no

SAP code/ OS

configuration/OS

related

Open SAP OSS

Ticket on HAN-*/

BC-OP-PLNX/

BC-OP-LNX/…

yes



32


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 customer's downtime requirements. In 2017, the migration factory extended their offerings to address HANA migrations from big endian (HANA 1.0) to little endian (Hana 2.0). Details can be found on http://www.ibm.com/systems/services/labservices/migrationfactory/index.html The SAP entry point for documentation is SAP Note 2537080 - Migrate SAP HANA 1.0 on IBM Power Systems Big-Endian to SAP HANA 2.0 on IBM Power Systems Little-Endian.

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

IBM® Total Solution Support for SAP HANA on Power Systems ™ 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 vendors’ 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

http://www-03.ibm.com/systems/services/labservices/migrationfactory/index.html


33


determination team. This link does only exist for customers with a IBM Total Solution Support contract.

Figure 13 IBM Services for SAP HANA on POWER environments

The following Proactive Services are available: • Hardware Health Check for SAP HANA on Power (remote) • Onsite Health Check for SAP HANA on Power (onsite) 5 days • 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.

Links, References and Tools:

SUSE Linux Enterprise Server 11 on POWER Ordering Guide for SAP Application Environment (BP only) SLES on POWER Ordering Guide for SAP Environments V2.0 (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 BP/IBM on IBM Partner world published.

https://www-304.ibm.com/partnerworld/wps/servlet/mem/ContentHandler/tech_WP102617/lc=en_ALL_ZZ


https://www.ibm.com/partnerworld/wps/servlet/mem/ContentHandler/tech_WP102617

34


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:

• Work in progress

• 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:

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

SAP HANA Operating System, Server and Storage Deployment:

• SAP Note 2161344 - HWCCT patch note • SAP Note 1943937 - Hardware Configuration Check Tool - Central Note

• SAP Note 2501817 - HWCCT 1.0 (≥220) • SAP Note 2382421 - Optimizing the Network Configuration on HANA-and OS-Level for SPS10

and Higher

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

• SAP Note 1900823 – 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.)

• SAP Note 2130682 - SAP HANA on IBM Power Systems: Documentation (HANA 1 SPS9 only)

• SAP Note 2235581 - SAP HANA: Supported Operating Systems (the only entry point for all OS Settings)

• SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System Installation

• SAP Note 2205917 - SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12

• 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

• SAP Note 1275776 - Linux: Preparing SLES for SAP environments

• SAP Note 2600030 - Parameter Recommendations in SAP HANA Environments SAP HANA Sizing and Planning:

• SAP Note 2188482 - SAP HANA on IBM Power Systems: Allowed Hardware • SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host





https://launchpad.support.sap.com/#/solutions/r/?type=note&route=notes&pos=0&p=%7B%22note%22%3A%222460914%22%7D



















35


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

• SAP Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database

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

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

• SAP Note 1953429 - SAP HANA and SAP NetWeaver AS ABAP on one Server

• SAP Note 2396942 - hdbfilterserver for SAP HANA 2 Text Analysis on Little Endian IBM Power Systems (obsolete SAP Note! All available on Power LE)

• SAP Note 2367899 - BW-IP: Planungsevents (sizing) SAP HANA Migration:

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

• SAP Note 2537080 - Migrate SAP HANA 1.0 on IBM Power Systems Big-Endian to SAP HANA

2.0 on IBM Power Systems Little-Endian

• SAP Note 2551355 - SAP HANA Platform 2.0 SPS 03 Release Note (Migrating HANA1 to HANA2 section!)

Support:

• SAP Note 618104 - "sapsysinfo" - Compiling system information on Linux

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

• SAP Note 1056161 - SUSE Priority Support for SAP applications

Other:

• SAP Note 1514967 - SAP HANA: Central Note (wording)

• SAP Note 1599888 - SAP HANA: Operational Concept (incomplete)

• SAP Note 1642148 - FAQ: SAP HANA Database Backup & Recovery (links outdated)

• SAP Note 1999997 FAQ: SAP HANA Memory

• SAP Note 2000003 FAQ: SAP HANA (outdated links)

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

process (list not complete)

• SAP Note 2039883 - FAQ: SAP HANA database and storage snapshots

• SAP Note 2140959 – Dynamic Tiering

• SAP Note 218464 - Supported products when running SAP HANA on IBM Power Systems

• HANA 2 FAQ: http://go.sap.com/documents/2016/11/82bad2f8-937c-0010-82c7-eda71af511fa.html

• SAP Note 218464

• The SAP HANA release documentation:

https://help.sap.com/viewer/p/SAP_HANA_PLATFORM

• 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.

• 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:

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

• SAP Note 171356 - SAP Software on Linux: General information

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

























http://go.sap.com/documents/2016/11/82bad2f8-937c-0010-82c7-eda71af511fa.html

http://go.sap.com/documents/2016/11/82bad2f8-937c-0010-82c7-eda71af511fa.html


https://help.sap.com/viewer/p/SAP_HANA_PLATFORM


https://launchpad.support.sap.com/#/solutions/r/?type=note&route=notes&pos=0&p=%7B%22note%22%3A%221825774%22%2C%22lang%22%3A%22E%22%7D




36


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

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

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

• SAP Note 1730996 - Unrecommended external software and software versions

• SAP Note 1730998 - Unrecommended versions of backup tools

• SAP Note 1730999 - Configuration changes to SAP HANA system

• SAP Note 1731000 - Configuration changes that are not recommended

• 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

• 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

• 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

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

• SAP Note 1310037 - SUSE LINUX Enterprise Server 11: Installation notes

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

• SAP Note 1984787 - SUSE LINUX Enterprise Server 12: Installation notes

SAP Documents:

• Sizing:

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

o Sizing Approaches for SAP HANA – Lessons Learned (current as of Oct/2015.

Some things have changed in the meantime)

o How to size SAP BW on SAP HANA

o Sizing for SAP S/4HANA

o Quick Sizer Tool (ensure to use the HANA Quick Sizer)

• Storage and High Availability

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

Availability

o SAP HANA TDI – Storage Requirements

o SAP Certified Enterprise Storage Hardware for SAP HANA

o SAP HANA – Network Requirements

o Introduction to High Availability for SAP HANA

• Architecture

o Certified and Supported SAP HANA Hardware Directory – 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

▪ …


















http://scn.sap.com/community/hana-in-memory/blog/2013/01/17/sap-hana-sizing







https://www.sap.com/documents/2015/03/74cdb554-5a7c-0010-82c7-eda71af511fa.html

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html




http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/power-systems.html



http://help.sap.com/hana_platform






37


o SAP HANA core documentation sets: SAP HANA Platform (Core) 2.0

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:

• 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)

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

on IBM Power Systems: https://www.ibm.com/developerworks/library/l-sap-hana-spark-controller-

integration-hdp/

• 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

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

• 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

o Sales Support Information (SSI) (IBM only)

• 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: https://www.suse.com/documentation/suse-best-practices/

http://help.sap.com/hana_on_power/


http://wiki.scn.sap.com/wiki/display/ITP/List+of+IT+Planning+Documents

https://www.suse.com/documentation/sles11/book_sle_deployment/?page=/documentation/sles11/book_sle_deployment/data/book_sle_deployment.html

https://www.suse.com/support/kb


http://repository.techline.ibm.com/systemx/contact/contact/


https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=e4d11bf2-8632-4a00-ba19-d767a98a2cf3



https://www.ibm.com/developerworks/library/l-sap-hana-spark-controller-integration-hdp/

https://www.ibm.com/developerworks/library/l-sap-hana-spark-controller-integration-hdp/


https://www.ibm.com/partnerworld/wps/servlet/ContentHandler/tech_PRS5340







notes://d06dbl044/m_dir/me018116.nsf








38


Copyrights and Trademarks © Copyright 2018 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: 2018 This is version 4.4 of this document. IBM, the IBM logo, and ibm.com 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 and/or 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 and/or 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.

http://www.ibm.com/legal/copytrade.shtml

39


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 the publication. IBM may make improvements and/or changes in the product(s) and/or 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 “AS IS” 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.