sap hana on power - ibm.com

SAP HANA on Power

Alfred Freudenberger

IBM North America Power Systems SAP Sales Leader

[email protected]

512-659-8059

Blog: saponpower.wordpress.com

© 2016 International Business Machines Corporation

SAP Note 2218464 - Supported products when running SAP HANA on IBM Power SystemsProduct / Software Components / Addon Minimum Release Comment

application function library SDK for SAP HANA 1.0

banking services from SAP 9.0 Except for SAP Bank Analyzer, which is not yet released.

SAP Business Planning and Consolidation 10.0, version for SAP NetWeaver

SAP Business Suite, powered by SAP HANA

•SAP ERP 6.0 EHP7•SAP SRM 7.0 EHP3•SAP CRM 7.0 EHP3•SAP SCM 7.0 EHP4

This includes the add-ons released via Note 1820906 or Note 2167814.

SAP Business Warehouse, powered by SAP HANA

•SAP EHP1 for SAP NetWeaver Business Warehouse 7.3, powered by SAP HANA•SAP Business Warehouse 7.4, powered by SAP HANA•BI Java 7.40 for SAP HANA•The following SAP tools released for SAP EHP1 for SAP NetWeaver Business Warehouse 7.3, SAP Business Warehouse 7.4, powered by SAP HANA, and BI Java 7.40:

• Nearline Storage in connection with SAP Business Warehouse and BI Java

• Business Intelligence in connection with SAP Business Warehouse and BI Java

This includes SAP Business Warehouse 7.5, edition for SAP HANA.

SAP BusinessObjects Business Intelligence platform 4.1 SP 03

SAP Cost and Revenue Allocation for Financial Products 1.0 SP 02

SAP Customer Activity Repository retail applications bundle 1.0 SPS 03

SAP Extended Warehouse Management 9.1

SAP Gateway 2.0

SAP Global Trade Services 11

SAP HANA data warehousing foundation SPS 02

SAP HANA dynamic tiering SPS 11

SAP HANA smart data integration 1.0 SP02

SAP HANA spatial SPS 11

SAP Hybris Commerce 6.0

SAP Hybris Marketing 1.2

SAP Landscape Transformation Replication Server 2.0 DMIS 2011 SP 07

SAP Liquidity Risk Management 1.1 SP 09

SAP Manufacturing Execution 15.1

SAP Master Data Governance 7.0 Please see documentation for SAP Master Data Governance for additional requirements with respect to versions of other applications.

SAP NetWeaver 7.5 This includes all add-ons released via Note 2156543 and Note 2156130

SAP Operational Process Intelligence 1.0

SAP Portfolio and Project Management 6.1

SAP Risk Management 10.1

SAP S/4HANA FINANCE 1605

SAP S/4HANA ON-PREMISE 1511 FPS 02

This includes SAP S/4HANA ON-PREMISE 1511 SR1.Please note, that SAP S/4HANA ON-PREMISE 1511 FPS 02 does not allow new installations and direct migrations to FPS 02. That means it can only be used with a SAP HANA database running on IBM Power, by migrating an existing FPS 02 system with the SAP HANA database running on Intel towards IBM Power by applying the SAP guide for heterogeneous system copies.Please note, that SAP S/4HANA ON-PREMISE 1511 SR1 currently only allows new installations.

SAP SFINANCIALS 1503

SAP Smart Business foundation component 1.0

SAP Solution Manager 7.2

SAP Transportation Management 9.1

SAP Transportation Resource Planning 1.0

As of 6/27/2016


SAP strategy for HANA

From:• One DB per application• Point-to-point integration • Long running queries, e.g. in

batch mode

To:• One DB per landscape• No integration necessary• Real time execution


In Memory Computing: Re-think Paradigms

In-Memory Computing Imperative: Avoid movement of detailed data Calculate first, then move results

ApplicationLayer

DatabaseLayer

Calculation

Calculation

Today Future

4


SAP Business Suite 4 SAP HANA (S/4HANA)


HANA Vora Reference Architecture

Non-SAP

Data SourcesData Sources

EDW

ERP

AnalysisAnalysis VisualizationVisualization

Network Analytics

Customer Analytics

Spark

SAP HANA Vora

Files

Spark

SAP HANA Vora

Files

Spark

SAP HANA Vora

Files

SAP HANA

Data Processing Engines

SQL Optimizer / Executor

Index Server

In Memory Store

SAP HANA

OLAP on Hadoop

Real-Time Analytics

Predictive Maintenance etc..

YARN

HDFS


Traditional Row-Oriented vs. Column-Oriented

7


HANA Data Compression Data Dictionary Transposing Data into Integers

8

Data tuplesDictionaries

Integer representation of data

Example: There are 195 countries in the world.

�� can be represented by a single Byte column- need log2(n) Bits to represent n distinct entries in dictionary

- can be further condensed by bitwise compression, e.g. Huffman algorithms

Ca

rdin

alit

y


9

• Modern ERP systems are challenged by mixed workloads, including OLAP--‐style queries. For example:

• OLTP--‐style: create sales order, invoice, accounting documents, display customer master data or

sales order

• OLAP--‐style: dunning, available--‐to--‐promise, cross selling, operational reporting (list open sales

orders)

• But: Today’s data management systems are optimized either for daily transactional or analytical

workloads storing their data along rows or columns

• Drawbacks of the OLTP and OLAP separation:

• OLAP system does not have the latest data

• OLAP system does only have a predefined subset of the data

• Cost--‐‐‐‐intensive ETL process has to synch both systems

• There is a lot of redundancy,

• aggregates and materialized views required for performance

• Different data schemas introduce complexity for applications that combine sources

OLTP vs OLAP


SAP HANA

Column Store

Row Store

Scale-out vs. Scale-up

SAP BW

SAP HANA

Column Store

Row Store

SAP ECC

SAP HANA

Column Store

Row Store

SAP HANA

Column Store

Row Store

SAP HANA

Column Store

Row Store

A - F G - K L - Q R - Z Table Partitioning

Parallel Queries


SAP HANA on Power Architecture

2010 2011 2012 2013 2014 2015

Not a separate fork of the HANA code

HANA

Powerx86

OLAP Engine

Join Engine

Calculation Engine

HW Engine


SAP HANA on IBM POWER

+

Enterprise ready

Mission Critical Reliability

Flexiblility

Virtualized


SAP HANA on IBM Power – Expected Customer Value

15,519,000

10,012,000

8,279,000

7,429,000

6,664,000

4,270,000

0

2000000

4000000

6000000

8000000

10000000

12000000

14000000

16000000

IBM 4-core p6 570 Sun 16-core E6900 HP 16-core rx8620

Th

rou

gh

pu

t/h

ou

r

Day

Night

• Delivering the reliability required by mission critical systems

– HANA needs 30 to 40x memory of conventional DBs – Power delivers comprehensive memory protection by default , not as an option

– Historic fault resilience, dynamic component deallocation, on the fly repair and fault isolation are unmatched in open systems

• Flexibility

– Industry leading, low overhead virtualization included by default, not an option with high overhead and artificial constraints unsuitable for production workloads

– Capacity on Demand

– Partition isolation allowing prod, non-prod and HA to be intermixed

• Performance

– Packing more HANA throughput into few cores leaves room for other requirements, reduces datacenter footprint and environmentals

– 3 to 5x memory bandwidth, 8 threads per core deliver consistent HANA response time, even during Delta Merge processing

Services


TDI – Tailored Datacenter Integration

• Solution validation done by SAP and partner

• Preconfigured hardware set-up• Preinstalled software

• Installation needs to be done by customer

• Customer aligns with the hardware partner on individual support mode

Fast ImplementationSupport fully provided by SAP

More FlexibilitySave IT budget and existing investment

HANA Appliance


TDI – Tailored Datacenter Integration

Fast ImplementationSupport fully provided by SAP

More FlexibilitySave IT budget and existing investment

HANA Appliance

CE

RT

IFIE

D

SU

PP

OR

TE

D

• Want support from SAP if you have a problem?• Utilize network or storage vendor subsystem compliant with existing standards?• Want flexibility with resource assignment, e.g. server consolidation?• Need to change configuration, e.g. add new types of disks, external storage, etc.?• Desire lower TCO through effective virtualization of cpu and I/O?

T-Shirt Sizings


Delivering freedom of choice to the HANA Landscape

16

SAP HANA®

OSLinux Enterprise Server

Priority Support for SAP applications

File System Monitoring

Backup

Sys MgmtSpectrum Scale, XFS2, NFS, ext3

Server HardwarePOWER7+(non-prod) or POWER8

Standalone or shared/PVM virtualized

Applications

Storage Hardware

Customer choice

High AvailabilitySAP HANA Host Auto-Failover & System

Replication, SUSE HA Ext, RH HA Plugin1, Symantec HA1, Tivoli SA

ECC

BW HA

PowerVM

ECC App

Power Landscape example

CRM

ECC HA

BW

PowerVM

Data

ECC, BW, SM App Sbx

ECC QA

BW QA

CRM QA

ECC App

VIO

S

VIO

S

ECC HA QA

HANA

HANA

App

DB/App

DB/App

DB/App

App

HANA

HANA

App

HANA

HANA

App

HANABW HA QA

BW App

VIO

S

VIO

S

1) Not currently supported with Linux on Power. Contact RedHat for product plans.

2) XFS is required for production.

1TB SoH

6TB SoH

1TB BW

3TB BW

4TB BW


HANA on POWER Portfolio

S812L

S822L

Linux only Systems

S822

S824

Scale-Out

S824L

E870

Enterprise

E880

E850

HANA on Power

Solution Editions

S814

� IBM fast-start option

� Industry best-practice

� Quick configurations

� Aggressively priced

� Rapid deployment of SAP

HANA on IBM Power

Systems


MemoryBuffer

DRAMChips

DDR Interfaces

POWER8

Link

Scheduler &

Management

16MB

Memory

Cache

“On-the-fly” lane isolation/repair

POWER8 Memory10 chips per rank for

extra redundancy

beyond chipkill


SAP HANA Delta-Merge Process

19

• Column store table - comprised of a Main storage and a Delta storage all located in RAM

• Delta storage optimized for write operations• Main storage is optimized for reads

• Use of Delta tables addresses performance issues of loading directly to compressed columns.

• Merge process takes the data out of the Delta structures and puts it into the Main structure

• This is a very CPU/Memory intensive task (!!!)Power delivers up to 5x memory

bandwidth, 4x CPU threads vs.

x86!

© 2016 International Business Machines Corporation 20

POWER8 processor is Purpose Built – resulting in premium performance over Intel Xeon

Haswell EP

E5-26xx v3

Ivy Bridge EX

E7-88xx v2

Haswell EX

E7-88xx v3POWER8

Clock rates 1.7-3.7GHz 1.9-3.4 GHz 2.0-3.0 GHz 3.0-4.15 GHz

SMT options 1, 2 1, 2 1, 2 1, 2, 4, 8

Cores per socket 18 15 18 12

Max Threads / socket 36 30 36 96

L1 Cache/core 32KB I + 32KB D3 32KB I + 32KB D3 32KB I + 32KB D3 32KB I + 64KB D

L2 Cache/core 256 KB 256 KB 256 KB 512 KB

L3 Cache/socket 45 MB 37.5 MB 45 MB 96 MB

Max L4 Cache/socket 0 0 0 128 MB

Performance Mode Memory Bandwidth

50-66.6 GB/s1 66.2-83.3 GB/s1 100 GB/s1 N/A

RAS Mode Memory Bandwidth

N/A 41.65-50GB/s1 41.652-58.3GB/s1 190-230 GB/sec

1) Depending on DIMM Rank and # of DIMMS/Channel

2) Lenovo supports a minimum of 50GB in RAS mode with Haswell-EX

3) L1 data cache with parity protection – 32KB, ECC – 16KB


High Availability – Disaster Recovery


SAP HANA HA: System Replication

Performance Optimized Cost Optimized

• Very low RTO• High cost for 100% standby

resources• Ideal for non-virtualized

systems and/or expectation of frequent outages

• With SPS10, secondary available Read Only

• Much lower cost – 10% reserved

• Works best with virtualized infrastructure

• If using VMware, may not be compatible with production (1 VM only, size restrictions)

• RTO from disk much slower• Memory must be reassigned

upon HA incident, very slow

Dedicated Shared

Performance and

Cost Optimized

with POWER

• Very low RTO• Majority of secondary CPU

resources available to VMs• Perfect fit for strong

production level virtualization solution such as PowerVM

Shared

QA/DEVrunning


HANA HA/DR Options

23

Storage subsystem replicationSync or AsyncWrite order dependentAsymmetric

HANA System ReplicationSync or AsyncWrite order independentHardware and vendor agnosticSymmetricSupport NZDT upgrades

Filesystem replicationSyncWrite order dependentSymmetric


SAP TDI

certified

Storage

LOG 2

LOG 1

Data 1

Data 2

24

POWER8 Server

PowerVM(ded.-donating LPARs / IFLs)

op

tion

al V

IOS

HANA BW PROD DB

Suite on HANA(ERP) PROD DB

Data n

LOGn

Redundant

8Gb SAN

XFS filesystems

TDI aligned, Linux,

dedicated donating

“Free” sizing, Shared Pool

Traditional Sizing,Shared Pool

Shared Processor Pool

op

tion

al V

IOS

BW App-Server

ERP App-Server

HANA BW Non-PROD

HANA ERP Non-PROD

Other workloads

Highest Flexibility and Agility with SAP HANA Landscape

An

y w

ork

loa

d m

ix

allo

we

d

Max. of 3 HANA PROD DB

HANA Prod MDC (multi-tenant )

H

N

1

HNn

HANA BW PROD DB(up to 50GB/core)


(up to 96GB/core)

HANA AnalyticsPROD 2-tier

HANA DB

e.g., BW App-Server

SAP Note 2230704

• Up to 4

concurrent

SAP HANA

Production

LPARs for

E870 and E880

or 3 prod + 1

shared pool

• < E870

Systems, n-1

of the above


SAP HANA Consolidation with VMware

SAP TDI

certified

Storage

LOG 2

LOG 1

Data 1

• VMware 5.5, 6.0 allowed for

prod with restrictions

• No VM may share a socket

• With 6.0, only one prod VM

supported, nothing else on

same system

• VMs may use more than one

socket up to limits of

memory and vps

• Non-prod not supported on

same system

• Max VM size, 64vp, 1TB with

5.5, 128vp, 4TB with 6.0

• Way too little CPU

resource compared to

bare-metal sizing

• Minimum performance

penalty vs. bare metal – 12%

• Approximately 100 low level

tests performed worse with

VMware

Data 2

x86 Server

VMware Hypervisor

Data 4

LOG 4

SAN

Connections

XFS filesystems

HANA Prod MDC (multi-tenant )

H

N

1

HNn

HANA BW PROD DBMax size 1TB

Up to 28.4GB/core bare metal


Max size 1TBUp to 42.7GB/core

bare metal

HANA AnalyticsPROD 2-tier

HANA DB

e.g., BW App-Server


Power HANA Sample architectureBased on Best Practices TDI Principles

Power SystemPower System

Prod

Dev – usually sized at 25% or prod

Test –Optional, sizing variable

QA – usually sized = prod

Optional QA HA for testing purposes only

HA

(optional)

• <5 min per TB • Performance optimized

HANA system replication• >15 min per TB

• Host-auto failover• >25 min per TB

• Cost optimized HANA system replication

RTO criteria for HA

Non-prod• Each instance may reside in a

VM and share systems with prod, HA and/or DR VMs if enough capacity available

Application servers• Each instance may reside on

separate commodity based servers or on above systems if enough capacity available

SAPS based sizing, usually n+1

Production• BW (up to 4.7TB/node)• Scale out to 16 nodes• SOH - ERP, CRM, CAR, SCM,

SRM•+ more SAP supported apps

added almost every day

• <5 min per TB • IBM FlashSystem V9000

• >12 min per TB• IBM Storwize V7000

• Log files on SSD• Data files on HDD

Disk subsystem

Power SystemPower System

DR/ProdHA

(optional)

DR site(optional)

IBM Power Systems for HANA Solution Editions offer competitive price points, full virtualization, flexibility to react seamlessly to environment changes, e.g. move from SoH to S4, addition of dynamic data tiering, Hadoop, etc. Up to 4 prod VMs may be hosted on large systems, or up to 3 prod VMs + multiple VMs with anything except prod HANA DB.

Disk subsystem

IBM Storage replicationOr

Async HANA System replication

Production Site


6TB HANA SoH Comparison x86 vs. Power

8-socket Haswell EX

6TB

Data

8-socket Haswell EX

6TBE870

Data

E870

x86 Power

Production + HA

QA

Data

8-socket Haswell EX

6TB

8-socket Haswell EX

6TB

Data

2-socket EXVMwareDev 1TB +

sandbox .5TB

QA LPAR on HA node

-add 6TB

OptionalHAtest

Optional HA test –add 6TB on prod

node

2-socket EPVMware

2-socket EPVMware

S822LApp

ServersNeed 2 for capacity and failover Failover to HA node above

HA – 6TB

Prod – 6 TB QA – 6TB

Dev – 1TB

Sbx – .5TB

LPAR Layout

Dev, Sandbox on HA node or

HA test node - add

1.5TB

Currently supported

HA Test – 6 TB


How to pick a system for a large scale-up transactional system

• Lacking a direct, head-to-head benchmark using your data and transactions or even an audited third party benchmark

– Flip a coin?

– Believe the vendor claims?

• The ability to physically place a certain number of components in a system does not imply its ability to utilize them much less keep them running.

Howard Hughes’ Spruce Goose8-engines, 6 times the size of any aircraft at the time

Flown only once

• A better way, look at

– History

– Benchmarks

– Architecture


If you need to move a lot of dirt, look for track record in that space

IBM Power Systems

– Transactional DB systems for• One of largest online marketplaces• Supply chain, parts mgmt for 7 of top 10 auto• Financials for many top world-wide banks• ERP for many of largest manufacturing, pharma

retail, distribution, oil & gas, cell phone companies

• Customer care and/or facilities management for most of top US & Canadian Utilities

HP Superdome X

- Transactional DB systems for- ?

SGI UV

- High performance computing

Big enginesHuge proven capacity

Lots of nozzlesMight be able to attach a trailer

If you need to run large OLTP systems, look for track record in that space


The challenge with large scale-up HANA systems

• Physical capacity does not necessarily correlate to ability to utilize capacity for HANA

– SGI and HP claim systems can support 288 cores/24TB memory– SAP systems matrix shows support for

• HP Superdome X @ 16TB• SGI 300H UV @ 20TB

HANA Columnar structure is optimized for analytics

and scales well with ccNUMA

Transaction processing often accesses all columns in a row resulting in accesses across all sockets where columns are stored.


POWER8 SGI UV HP Superdome

SpecInt_Rate2006

14,400 @ 192 cores 11,400 @ 288 cores 11,100 @ 288 cores

2-Tier SAPS 436,100 @ 80 cores5,451 SAPS/core

N/A 545,780 @ 288 cores1,895 SAPS/core

BW-EML 192,750 @ 40 cores, 2M rows N/A N/A

TPC-C 6,085,166 tpmC @ 64 P6 cores 12/10/08

N/A 4,092,799 tpmC @ 128 Itanium2 cores 08/06/07

1,200,011 tpmC @ 8 P7 cores 10/13/10

3-Tier SAPS 1,471,680 @ 64 P7+ cores N/A N/A

NU

MA

affin

ity

Benchmarks don’t tell the whole story, but they are an important consideration


Intel ccNUMA architecture

4-socket/3TB HANA 8-sockets/6TB HANA

Not bad, but limited in size/scale


6 or 7 hops for every off-motherboard remote memory access

SGI-uv ccNUMA design up to 32-sockets, 24TB


HP Superdome X ccNUMA design up to 16-sockets, 24TB

8 hops for every off-blade remote memory access


POWER8 Enterprise SMP Interconnect Topology

Horizontal Full Connect

Ve

rtic

al F

ull

Co

nnect

4 hops for every off-CEC remote memory access


ccNUMA characteristics, large memory effects on RAS

POWER8 SGI UV HP Superdome

% of mem access offplanar

12/16, 75% 28/32, 87.5% 14/16, 87.5%

Off-planarmemory access

4-hop return trip 6 or 7 hop return trip 8 hop return trip

Cache line size 128B 64B 64B

System NUMA optimization

DPO, cache line prefetch N/A N/A

Memory protection

ChipKill + spare chips, i.e. DDDC+1+1

SDDC DDDC+1

Memory deallocation

Firmware directed DIMMS to spare and/or on-demand memory

SGI MemLog Utility page deallocation resulting in loss of capacity

N/A

“This technology delivers up to a

17x improvement in the number

of DIMM replacements versus

those systems that use only

Single-Chip Sparing technologies.

Furthermore, DDDC +1

significantly reduces the chances

of memory related crashes

compared to systems that only

have Single-Chip Sparing

capabilities” HP Superdome RAS


When faster I/O may make a difference

Load time dependent on throughput of IOPS

Response time of on-demand columns dependent on latency, throughput of IOPS

Conventional DB

ClientPart number

Order date

Shipped date

Delivery date

QuantityItem Weight

Item cost

Package weight

Total price

Instructions Status

abc 123 8/1/2015 9/6/2015 9/15/2015 15 0.56 1.35 9.5 $42.00 Leave on porch In-transit

Delta Table in HANA

Single Async IOP

abc

123

8/1/2015

9/6/2015

9/15/2015

15

0.56

1.35

9.5

$42.00

Leave on porch

In-transit

Async IOPS = number of columns(at minimum)

Delta merge

To log file and in-memory row

abc 123 8/1/2015 9/6/2015 9/15/2015 15 0.56 1.35 9.5 $42.00 Leave on porch In-transit

RTO after

failure or

HANA

patching

Data aging


HWCCT – Hardware configuration check tool

Determine if system meets KPI requirements

• Landscape test• OS config validity• Consistency of

landscape based on reference architecture

• File system throughput/latency

• Network throughput for multinode configurations

• 9.5 GBits for single stream

• 9.0 GBits for duplex stream


SAP HANA database

SAP HANA Backup and Recovery

Memory �� Disk �� Backup– Data backups

Contain the current payload of the data volumes (data and undo)

Any pages that are changed during the data backup written to different locations in the data volumes (shadow page concept)

Manual (SAP HANA studio, SQL commands), or scheduled (DBA Cockpit)

– Log backupsContain the content of closed log segments

Automatic (asynchronous) whenever a log segment is full or the timeout for log backup has elapsed

Log Area

(disk)

Data Area

(disk)

Memory

Savepoint COMMIT

Data Backups Log Backups

− Log volume contains log segments� Number of pre-formatted log segments is

configurable� Log segments are closed when they are

full, or the log backup timeout has elapsed� After a log segment has been successfully

backed up, it is released for overwriting


SAP HANA Backup Destinations

Backups to the file system

� For both data and log backups,

e.g., to an NFS share

� For information on file systems: SAP Note 1820529

� Data backups triggered/scheduled using SAP HANA studio, SQL commands, or DBA Cockpit, log backups written automatically (unless disabled)

SAP HANA Database

Backup

Storage,

e.g. NFS

Create backup

hdbsql

SAP HANA

studio

SAP HANA Database

3rd Party

Backup

Server

3rd Party

Backup Agent

Create backup

Backups to 3rd party backup server

� “Backint for SAP HANA” API can be implemented by a 3rd party backup agent. Check for certified products: http://global.sap.com/community/ebook/2013_09_adpd/enEN/search.html#search=HANA-brint

� Provides functions for backup, recovery, query, delete

� 3rd party backup agent runs on the SAP HANA server, communicates with 3rd party backup server

� Backups are transferred via pipe

� Direct integration with SAP HANA:o Data backups to Backint can be triggered/ scheduled using SAP HANA

studio, SQL commands, or DBA Cockpito Log backups are automatically written to Backint (if configured)


The HANA on POWER Eco-Systems Continuously Grows

ISV Product Component Description Status

Backup solutions for HANA

IBM TSM for ERP • Data Protection for HANA SAP HANA BACKINT � Available� SAP Certified

EMC NetWorker • NetWorker Module for SAP HANA• NetWorker Client• NetWorker Storage Node

SAP HANA BACKINT � HANA agent not yet available (requests per RPQ)

Veritas NetBackup • NetBackup Client• NetBackup for HANA agent

SAP HANA BACKINT � Client available� Agent planned for

4/2016, certification 5/2016

SEP sesam • SEP sesam for SAP HANA SAP HANA BACKINT �� Available

Libelle Business-Shadowfor SAP

• BusinessShadow BackupServer via BRINT SAP HANA BACKINT �� Available

Simpana Commvault • SAP HANA iDataAgent SAP HANA BACKINT � Available [to be verified]

High-Availability / Disaster Recovery Solutions for HANA

IBM System Automation MP

• SAP HANA policy HANA failover solution �� Available

SUSE Linux HA • SAPHanaSR scale-up and scale-out HANA failover solution �� Available, included in SLES for SAP

Libelle Business-Shadow for SAP

• BusinessShadow managing SAP HANA Replication

HANA replication and failover control

�� Available41


Generic PowerLinux Eco-System (1)

Storage Backup Solutions

Storix Storix Backup Administrator

• Backup File system backup solution �� Available

Monitoring

Open Source Nagios Monitoring, alerting �� Available

Open Source Ganglia Monitoring �� Available

IBM ITCAM Tivoli Composite Application Manager•Tivoli Monitoring – available•SAP Agent – remote access to SAP Solution Manager

SAP Monitoring �� All required agents available

BMC PATROL TrueSight Operations Management Knowledge Module:•PATROL for Unix and Linux

Monitoring agent � Planned 5/16

CA Service Assurance

• Systems Performance for Infrastructure Managers – Linux SystemEDGE Agent 5.6.0

Performance monitoring � Planned 5/16

HP Business Service Mgmt

• SiteScope [formerly OpenView] Agentless monitoring �� Available (To be tested)

Splunk Splunk Enterprise • Universal Forwarder [agent] Operational monitoring �� Available

� not HANA / SAP specific but can be used with


Generic PowerLinux Eco-System (2)

ISV Product Component Description Status

Security / Compliance / Inventory

IBM EndpointManager

• For compliance and security management (agent)

Compliance, security �� Available

IBM TAD • Tivoli Asset Discovery for Distributed Inventory management �� Available

Miscellaneous

CA Workload Automation

• Workload Automation Agent for Linux 11.3 SP1 [formerly AutoSys]

Job scheduling �� Beta availableGA 4/2016

LRS • VPSX SAP Output Management �� Beta available


Technical design and

infrastructure deployment

� Planning and configuration

� Installation and verification

� Coordinate with SAP

� Validation and testing

� Recovery/availability plan

� Coaching and skills transfer

Operation and optimization

� Proactive services

� Solution support

� Optimization

� Service management

� Operating model

Assess, Upgrade and

Migrate

� Project services

� Health check assessment

� Platform upgrade

� Deploy scale-out hardware1

Life cycle management

1 Scale our solution with General Parallel File System (GFPS)

IBM Services for SAP HANA on Power

44


Full SAP HANA on POWER Custom Technical Support

Overview HANA on POWER Integrated Solution Service

Individual

continuous customer interaction

Integrated HW and SW1

supportImprove availability & reduce resolution

time

Optimized access to a

comprehensive solution support

Avert problems:

proactive services, preventative support

advice & services

• This Service Component is a key differentiator for our POWER Platform• Close Linkage with SAP (Electronic Retain Ticket Interface with SAP )• With single-source and central responsibility, Customer Technical Services are

designed to simplify support and accelerate problem resolution for mission critical HANA on POWER environments.

• SUSE License can be included in the service package. This combination is a huge added value for our customers from an pricing and content perspective.

• For offering support and individual pricing contact your local CTS representative listed below.

SAP

SUSE


TCO – Get the Complete Picture!

Total Cost of Ownership is much more than Total Cost of Acquisition!

ComponentsEnvironments

Time

Hardware $$$$ $$$$ $$$$ $$$$ $$$$ Planning

Software $$$$ $$$$ $$$$ $$$$ $$$$ Upgrades

People $$$$ $$$$ $$$$ $$$$ $$$$ Migration

Network $$$$ $$$$ $$$$ $$$$ $$$$ Growth

Storage $$$$ $$$$ $$$$ $$$$ $$$$ Parallel Costs

Facilities $$$$ $$$$ $$$$ $$$$ $$$$ Net Present Value

QoS – Availability, Reliability, Security and Scalability

TCATCATCATCA


Look at the complete picture

Usually the percentage of the infrastructure cost for an SAP environment is in the range of 10% of

the total cost, which also includes the SAP Licence fees, and manpower for administration.

Spending an additional few percent of your overall cost on IBM Power Systems for the infrastructure

part gives a much better performance, service level and more flexibility compared to x86.

0,0

0,5

1,0

1,5

2,0

2,5

3,0

3,5

Power x86 Server

Co

st

(Millio

n €

)

5 year TCO comparison

0,0

5,0

10,0

15,0

20,0

25,0

Power x86 Server

Co

st

(Millio

n €

)

5 year TCO comparison

11.7%11.7%11.7%11.7% 1.7%1.7%1.7%1.7%

Infrastructure onlyInfrastructure onlyInfrastructure onlyInfrastructure only Infrastructure plus SAP ApplicationInfrastructure plus SAP ApplicationInfrastructure plus SAP ApplicationInfrastructure plus SAP Application


Get more information from these key resources

• IBM Systems & Services for HANA on Power

� https://www.ibm.com/solutions/sap/us/en/landing/hana.html

� http://www-03.ibm.com/systems/power/solutions/bigdata-analytics/sap-hana/

� http://www-01.ibm.com/common/ssi/cgi-

bin/ssialias?subtype=WH&infotype=SA&htmlfid=POW03161USEN&attachment=POW03161USEN.PDF

• Key contacts

– NA HANA on Power Sales:

o SAP Sales Leader, Rich Rommel, [email protected]

o Alfred Freudenberger, [email protected],

https://saponpower.wordpress.com/author/afreude/

o Bob Wolf, [email protected]

– Offering Manager: Anna Coffey, [email protected]

– SAP BUE: Vicente Moranta, [email protected]


Get more information from these key resources

• IBM Techdocs

� SAP HANA on IBM Power,

� https://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502

� SAP HANA on IBM Storage,

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

• SAP Notes:

� 2133369 - SAP HANA on IBM Power Systems: Central Release Note

� 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host

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

� 2000003 - FAQ: SAP HANA

• SAP Help Documentation:

� SAP HANA Platform Core: http://help.sap.com/hana_platform


SAP HANA on IBM Power Summary

• Analytics enable decision making, Suite on HANA runs the business

– Power Systems delivers the non-stop operations required of these mission critical systems

• Performance - HANA demands extreme memory and thread throughput

– Power Systems delivers 4x threads, over 3x memory throughput compared to x86

• Flexibility– Power Virtualization built in, not a poorly supported afterthought

• Competitive TCA, Lower Total Cost of HANA Landscape


Merci

Grazie

Gracias

Obrigado

Danke

Japanese

French

Russian

German

Italian

Spanish

Brazilian PortugueseArabic

Traditional Chinese

Simplified Chinese

Thai

Korean

Hindi

DankieAfrikaans

SiyabongaZulu

Tamil

תודהHebrew

Blog: SAPonPower.wordpress.com

sap hana on power - ibm.com

Documents