SAP HANA on Power

Alfred Freudenberger
IBM North America Power Systems
SAP Sales Leader
afreude@us.ibm.com
512-659-8059

Blog: saponpower.wordpress.com
 SAP Note 2218464 - Supported products when running SAP HANA on IBM Power Systems
Product / Software Components / Addon Minimum Release Comment

application function library SDK for SAP HANA 1.0

banking services from SAP
SAP Business Planning and Consolidation
SAP Business Suite, powered by SAP HANA
SAP Business Warehouse, powered by SAP HANA
9.0 Except for SAP Bank Analyzer, which is not yet released.
10.0, version for SAP NetWeaver
•SAP ERP 6.0 EHP7
•SAP SRM 7.0 EHP3
•SAP CRM 7.0 EHP3
This includes the add-ons released via Note 1820906 or Note 2167814.
•SAP SCM 7.0 EHP4
•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 This includes SAP Business Warehouse 7.5, edition for SAP HANA.
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

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
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
SAP S/4HANA ON-PREMISE 1511 FPS 02 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

© 2016 International Business Machines Corporation

As of 6/27/2016
SAP strategy for HANA
From: To:
• One DB per application • One DB per landscape
• Point-to-point integration • No integration necessary
• Long running queries, e.g. in • Real time execution
batch mode

© 2016 International Business Machines Corporation

 In Memory Computing: Re-think Paradigms

Today Future
Calculation Application
Layer

Database
Layer
Calculation

In-Memory Computing Imperative: Avoid movement of detailed data

Calculate first, then move results

4
© 2016 International Business Machines Corporation
SAP Business Suite 4 SAP HANA (S/4HANA)

© 2016 International Business Machines Corporation

HANA Vora Reference Architecture

Data Sources Analysis Visualization

Network Customer Analytics

Predictive
Non-SAP Analytics Maintenance etc..
EDW
ERP

OLAP on Hadoop
Real-Time Analytics
SAP HANA Spark Spark Spark
SAP HANA
SAP HANA Vora SAP HANA Vora SAP HANA Vora

Index Server
YARN
Data Processing Engines

SQL Optimizer / Executor

HDFS
Files Files Files

In Memory Store

© 2016 International Business Machines Corporation

Traditional Row-Oriented vs. Column-Oriented

© 2016 International Business Machines Corporation 7

HANA Data Compression Data Dictionary
Transposing Data into Integers
Data tuples
Dictionaries

Cardinality
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
© 2016 International Business Machines Corporation 8
 OLTP vs OLAP
• 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

9
© 2016 International Business Machines Corporation
Scale-out vs. Scale-up
SAP BW
Parallel Queries

Column Store Column Store Column Store Column Store

Row Store Row Store Row Store Row Store

SAP HANA SAP HANA SAP HANA SAP HANA

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

SAP ECC

Column Store

Row Store

SAP HANA

© 2016 International Business Machines Corporation

SAP HANA on Power Architecture

HANA

Calculation Join OLAP HW

Engine Engine Engine Engine
x86 Power

Not a separate fork of the HANA code

2010 2011 2012 2013 2014 2015

© 2016 International Business Machines Corporation

SAP HANA on IBM POWER

Enterprise ready
Mission Critical Reliability
Flexiblility
Virtualized

© 2016 International Business Machines Corporation

SAP HANA on IBM Power – Expected Customer Value
• 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
16000000 15,519,000

14000000

12000000

10,012,000

Throughput/hour
10000000

8,279,000

8000000
Day

requirements, reduces datacenter footprint and environmentals

7,429,000
6,664,000
Night

6000000

4,270,000
4000000

2000000

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

– 3 to 5x memory bandwidth, 8 threads per core deliver consistent HANA

response time, even during Delta Merge processing

Services © 2016 International Business Machines Corporation

 HANA Appliance TDI – Tailored Datacenter Integration
Fast Implementation More Flexibility
Support fully provided by SAP Save IT budget and existing investment

• Solution validation done by SAP • Installation needs to be done by

and partner customer
• Preconfigured hardware set-up • Customer aligns with the hardware
• Preinstalled software partner on individual support mode

© 2016 International Business Machines Corporation

HANA Appliance TDI – Tailored Datacenter Integration
T-Shirt Sizings
Fast Implementation More Flexibility
Support fully provided by SAP Save IT budget and existing investment

SUPPORTED
CERTIFIED

• 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?
© 2016 International Business Machines Corporation
Delivering freedom of choice to the HANA Landscape
Applications

Power Landscape example

SAP HANA® PowerVM

ECC HANA

VIOS
BW HA HANA

ECC App App

High Availability
CRM DB/App
SAP HANA Host Auto-Failover & System
Replication, SUSE HA Ext, RH HA Plugin1, BW QA DB/App
Symantec HA1, Tivoli SA

VIOS
CRM QA DB/App
File System Monitoring
BW App App
Backup
Spectrum Scale , XFS2, NFS, ext3 Data
Sys Mgmt
PowerVM
OS BW HANA
Linux Enterprise Server

VIOS
ECC HA HANA
Priority Support for SAP applications
ECC App App

Server Hardware ECC QA HANA

POWER7+(non-prod) or POWER8 ECC HA QA HANA

VIOS
Standalone or shared/PVM virtualized ECC, BW, SM App Sbx App

BW HA QA HANA
Storage Hardware
Customer choice
1TB 3TB 4TB 1TB 6TB
1) Not currently supported with Linux on Power. Contact RedHat for product plans. BW BW BW SoH SoH
2) XFS is required for production.

16
© 2016 International Business Machines Corporation
HANA on POWER Portfolio
E880

E870

E850

S824
S814 Enterprise
S822
HANA on Power
Scale-Out Solution Editions
 IBM fast-start option

 Industry best-practice
S824L
 Quick configurations
S822L  Aggressively priced

S812L  Rapid deployment of SAP

HANA on IBM Power
Linux only Systems Systems

© 2016 International Business Machines Corporation

 DRAM Memory
Chips Buffer
POWER8 Memory
10 chips per rank for
extra redundancy
beyond chipkill

DDR Interfaces

16MB
Scheduler & POWER8
Memory
Management Cache Link

“On-the-fly” lane isolation/repair

© 2016 International Business Machines Corporation

SAP HANA Delta-Merge Process

• 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 Power delivers up to 5x memory
• This is a very CPU/Memory intensive task (!!!)
bandwidth, 4x CPU threads vs.
19
x86!
© 2016 International Business Machines Corporation
 POWER8 processor is Purpose Built – resulting in premium
performance over Intel Xeon

Haswell EP Ivy Bridge EX Haswell EX

POWER8
E5-26xx v3 E7-88xx v2 E7-88xx v3

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
50-66.6 GB/s1 66.2-83.3 GB/s1 100 GB/s1 N/A
Memory Bandwidth
RAS Mode Memory
N/A 41.65-50GB/s1 41.652-58.3GB/s1 190-230 GB/sec
Bandwidth

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

© 2016 International Business Machines Corporation 20

High Availability – Disaster Recovery

© 2016 International Business Machines Corporation

SAP HANA HA: System Replication
Performance Optimized
Dedicated
• 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
© 2016 International Business Machines Corporation
Cost Optimized
Performance and
Cost Optimized
with POWER
QA/DEV
running
Shared
• Much lower cost – 10%
reserved
Shared • Works best with virtualized
infrastructure
• Very low RTO • If using VMware, may not
• Majority of secondary CPU be compatible with
resources available to VMs production (1 VM only,
• Perfect fit for strong size restrictions)
production level virtualization • RTO from disk much slower
solution such as PowerVM • Memory must be reassigned
upon HA incident, very slow
HANA HA/DR Options

Storage subsystem replication

Sync or Async
Write order dependent
Asymmetric

Filesystem replication
Sync
Write order dependent
Symmetric

HANA System Replication

Sync or Async
Write order independent
Hardware and vendor agnostic
Symmetric
Support NZDT upgrades

23
© 2016 International Business Machines Corporation
 Highest Flexibility and Agility with SAP HANA Landscape

POWER8 Server SAP TDI

PowerVM certified

optional VIOS
(ded.-donating LPARs / IFLs)
Storage
HANA BW PROD DB LOG 1
(up to 50GB/core)

Data 1
Suite on HANA
(ERP) PROD DB
Suite on HANA
(ERP) PROD DB Redundant Data 2
(up to 96GB/core) 8Gb SAN LOG 2
Max. of 3 HANA PROD DB
XFS filesystems
Shared Processor Pool
BW App-Server
HANA Analytics
• Up to 4 PROD 2-tier Data n
concurrent
SAP HANA HANA DB LOGn
ERP App-Server
Production e.g., BW App-Server
LPARs for
Any workload mix

optional VIOS
E870 and E880 HANA BW Non-PROD
or 3 prod + 1 HANA Prod MDC
shared pool (multi-tenant
HANA )
ERP Non-PROD TDI aligned, Linux,
• < E870 dedicated donating
allowed

H
Systems, n-1 N HNn
of the above 1 Other workloads
Traditional Sizing,
Shared Pool

SAP Note 2230704 “Free” sizing,

Shared Pool
© 2016 International Business Machines Corporation 24
 SAP HANA Consolidation with VMware

• VMware 5.5, 6.0 allowed for x86 Server

prod with restrictions
VMware Hypervisor

• No VM may share a socket

SAN
HANA BW PROD DB
• With 6.0, only one prod VM Max size 1TB Connections
supported, nothing else on Up to 28.4GB/core SAP TDI
same system bare metal certified
Storage
• VMs may use more than one
socket up to limits of Suite on HANA LOG 1
(ERP) PROD DB
memory and vps Max size 1TB
Up to 42.7GB/core
bare metal Data 1
• Non-prod not supported on
same system
HANA Analytics Data 2
• Max VM size, 64vp, 1TB with PROD 2-tier LOG 2
5.5, 128vp, 4TB with 6.0
• Way too little CPU HANA DB
XFS filesystems
resource compared to e.g., BW App-Server
bare-metal sizing
HANA Prod MDC Data 4
• Minimum performance (multi-tenant ) LOG 4
penalty vs. bare metal – 12%
H
N HNn
1
• Approximately 100 low level
tests performed worse with
VMware

© 2016 International Business Machines Corporation

 Power HANA Sample architecture
Based on Best Practices TDI Principles
Production Site
RTO criteria for HA DR site
Production HA • <5 min per TB (optional)
• BW (up to 4.7TB/node) Prod • Performance optimized
(optional) HANA system replication
• Scale out to 16 nodes
• >15 min per TB HA
• SOH - ERP, CRM, CAR, SCM, Power System Power System
• Host-auto failover DR/Prod
SRM (optional)
• >25 min per TB
•+ more SAP supported apps • Cost optimized HANA Power System Power System
system replication
added almost every day

Dev – usually
Non-prod sized at 25%
• Each instance may reside in a or prod
VM and share systems with IBM Storage replication
prod, HA and/or DR VMs if Test – Disk subsystem Or Disk subsystem
Optional, Async HANA System replication
enough capacity available sizing variable
Optional
QA HA for
testing
QA – usually • <5 min per TB
purposes
sized = prod • IBM FlashSystem V9000
only
• >12 min per TB
• IBM Storwize V7000
Application servers • Log files on SSD
• Each instance may reside on • Data files on HDD
SAPS based sizing,
separate commodity based usually n+1
servers or on above systems
if enough capacity available

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.

© 2016 International Business Machines Corporation

 6TB HANA SoH Comparison x86 vs. Power
Currently supported
x86 Power
8-socket 8-socket
Production Haswell EX
6TB
Haswell EX
6TB
E870 E870
+ HA

Data Data

8-socket 8-socket
Optional
QA LPAR
Haswell EX Haswell EX
QA 6TB 6TB HA on HA node
Optional
test HA test –
-add 6TB
add 6TB
Data on prod
node

Dev,
2-socket EX
Dev 1TB + VMware Sandbox on
sandbox HA node or
.5TB HA test
Data node - add
1.5TB
HA – 6TB
LPAR Prod – 6 TB QA – 6TB
Layout Dev – 1TB
HA Test – 6 TB Sbx – .5TB

App 2-socket EP 2-socket EP

S822L
VMware VMware
Servers
Need 2 for capacity and failover Failover to HA node above

© 2016 International Business Machines Corporation

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.

• A better way, look at

– History
– Benchmarks
– Architecture Howard Hughes’ Spruce Goose
8-engines, 6 times the size of any aircraft at the time
Flown only once

© 2016 International Business Machines Corporation

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

Lots of nozzles
Big engines Might be able to attach a trailer
Huge proven capacity

If you need to run large OLTP systems, look for track record in that space
IBM Power Systems HP Superdome X
– Transactional DB systems for - 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 SGI UV
retail, distribution, oil & gas, cell phone - High performance computing
companies
• Customer care and/or facilities management for
most of top US & Canadian Utilities
© 2016 International Business Machines Corporation
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

Transaction processing often accesses all

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

and scales well with ccNUMA

© 2016 International Business Machines Corporation

 Benchmarks don’t tell the whole story, but they are an
important consideration
POWER8 SGI UV HP Superdome
SpecInt_Rate 14,400 @ 192 cores 11,400 @ 288 cores 11,100 @ 288 cores
2006

NUMA affinity
2-Tier SAPS 436,100 @ 80 cores N/A 545,780 @ 288 cores
5,451 SAPS/core 1,895 SAPS/core
BW-EML 192,750 @ 40 cores, 2M rows N/A N/A

TPC-C 6,085,166 tpmC @ 64 P6 cores N/A 4,092,799 tpmC @ 128 Itanium2

12/10/08 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

© 2016 International Business Machines Corporation

Intel ccNUMA architecture
4-socket/3TB HANA 8-sockets/6TB HANA

Not bad, but limited in size/scale

© 2016 International Business Machines Corporation

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

6 or 7 hops for every

off-motherboard
remote memory
access

© 2016 International Business Machines Corporation

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

8 hops for every off-

blade remote
memory access

© 2016 International Business Machines Corporation

 POWER8 Enterprise SMP Interconnect Topology
Horizontal Full Connect
Vertical Full Connect

4 hops for every off-CEC remote memory access

© 2016 International Business Machines Corporation

ccNUMA characteristics, large memory effects on RAS
POWER8 SGI UV HP Superdome
% of mem 12/16, 75% 28/32, 87.5% 14/16, 87.5%
access off
planar
Off-planar 4-hop return trip 6 or 7 hop return trip 8 hop return trip
memory access
Cache line size 128B 64B 64B
“This technology delivers up to a
System NUMA DPO, cache line prefetch N/A N/A 17x improvement in the number
optimization of DIMM replacements versus
Memory ChipKill + spare chips, i.e. SDDC DDDC+1 those systems that use only
Single-Chip Sparing technologies.
protection DDDC+1+1
Furthermore, DDDC +1
Memory Firmware directed DIMMS to SGI MemLog Utility page N/A significantly reduces the chances
deallocation spare and/or on-demand deallocation resulting in loss of of memory related crashes
compared to systems that only
memory capacity
have Single-Chip Sparing
capabilities” HP Superdome RAS

© 2016 International Business Machines Corporation

When faster I/O may make a difference

RTO after
failure or Data aging
HANA
patching

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

Part Order Shipped Delivery Item Item Package Total

Client Quantity Instructions Status
number date date date Weight cost weight price

Conventional DB Delta Table in HANA

To log file and in-memory row
Leave on
abc 123 8/1/2015 9/6/2015 9/15/2015 15 0.56 1.35 9.5 $42.00 porch In-transit

Single Async IOP Delta merge

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)
abc 9/15/2015 9.5
123 15 $42.00
8/1/2015 0.56 Leave on porch

9/6/2015 1.35 In-transit

© 2016 International Business Machines Corporation

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

© 2016 International Business Machines Corporation

SAP HANA Backup and Recovery
– Data backups
Memory
Disk
Backup Contain the current payload of the data
volumes (data and undo)
SAP HANA database Any pages that are changed during the data
backup written to different locations in the
data volumes (shadow page concept)
Memory
Manual (SAP HANA studio, SQL commands),
or scheduled (DBA Cockpit)
– Log backups
Savepoint COMMIT Contain the content of closed log segments
Automatic (asynchronous) whenever a log
segment is full or the timeout for log backup
Data Area has elapsed
Log Area
(disk) (disk)
− Log volume contains log segments
 Number of pre-formatted log segments is
Data Backups Log Backups 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

© 2016 International Business Machines Corporation

 SAP HANA
SAP HANA Backup Destinations studio
hdbsql
Backups to the file system
 For both data and log backups, Create backup
e.g., to an NFS share
 For information on file systems: SAP Note 1820529
Backup
 Data backups triggered/scheduled using SAP HANA
Storage,
studio, SQL commands, or DBA Cockpit, log backups e.g. NFS
SAP HANA Database
written automatically (unless disabled)
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_a Create backup
dpd/enEN/search.html#search=HANA-brint
 Provides functions for backup, recovery, query,
delete
 3rd party backup agent runs on the SAP HANA SAP HANA Database
server, communicates with 3rd party backup server
 Backups are transferred via pipe
3rd Party
 Direct integration with SAP HANA: 3rd Party Backup
o Data backups to Backint can be triggered/ scheduled using SAP HANA Backup Agent Server
studio, SQL commands, or DBA Cockpit
o Log backups are automatically written to Backint (if configured)
© 2016 International Business Machines Corporation
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 SAP HANA BACKINT  HANA agent not yet
• NetWorker Client available (requests per
• NetWorker Storage Node RPQ)
Veritas NetBackup • NetBackup Client SAP HANA BACKINT  Client available
• NetBackup for HANA agent  Agent planned for
4/2016, certification
5/2016
SEP sesam • SEP sesam for SAP HANA SAP HANA BACKINT  Available
Libelle Business-Shadow • BusinessShadow BackupServer via BRINT SAP HANA BACKINT  Available
for SAP
Simpana Commvault • SAP HANA iDataAgent SAP HANA BACKINT  Available [to be verified]

High-Availability / Disaster Recovery Solutions for HANA

IBM System Automation • SAP HANA policy HANA failover solution  Available
MP
SUSE Linux HA • SAPHanaSR scale-up and scale-out HANA failover solution  Available, included in
SLES for SAP
Libelle Business-Shadow • BusinessShadow managing SAP HANA HANA replication and  Available
41
for SAP Replication failover control

© 2016 International Business Machines Corporation 41

Generic PowerLinux Eco-System (1)

not HANA / SAP specific but can be used with
Storage Backup Solutions
Storix Storix Backup • Backup File system backup solution  Available
Administrator
Monitoring
Open Source Nagios Monitoring, alerting  Available

Open Source Ganglia Monitoring  Available

IBM ITCAM Tivoli Composite Application Manager SAP Monitoring  All required agents
•Tivoli Monitoring – available available
•SAP Agent – remote access to SAP Solution
Manager
BMC PATROL TrueSight Operations Management Monitoring agent  Planned 5/16
Knowledge Module:
•PATROL for Unix and Linux
CA Service • Systems Performance for Infrastructure Performance monitoring  Planned 5/16
Assurance Managers – Linux SystemEDGE Agent
5.6.0
HP Business Service • SiteScope [formerly OpenView] Agentless monitoring  Available
Mgmt (To be tested)
Splunk Splunk Enterprise • Universal Forwarder [agent] Operational monitoring  Available

© 2016 International Business Machines Corporation 42

Generic PowerLinux Eco-System (2)
ISV Product Component Description Status
Security / Compliance / Inventory
IBM Endpoint • For compliance and security management Compliance, security  Available
Manager (agent)
IBM TAD • Tivoli Asset Discovery for Distributed Inventory management  Available

Miscellaneous
CA Workload • Workload Automation Agent for Linux 11.3 Job scheduling  Beta available
Automation SP1 [formerly AutoSys] GA 4/2016
LRS • VPSX SAP Output Management  Beta available

© 2016 International Business Machines Corporation 43

IBM Services for SAP HANA on Power

Technical design and Assess, Upgrade and

Operation and optimization
infrastructure deployment Migrate

 Planning and configuration  Proactive services  Project services

 Installation and verification  Solution support  Health check assessment
 Coordinate with SAP  Optimization  Platform upgrade
 Validation and testing  Service management  Deploy scale-out hardware1
 Recovery/availability plan  Operating model
 Coaching and skills transfer

Life cycle management

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

44

© 2016 International Business Machines Corporation

Overview HANA on POWER Integrated Solution Service
• This Service Component is a key differentiator for our POWER Platform Optimized access
• Close Linkage with SAP (Electronic Retain Ticket Interface with SAP ) to a
• With single-source and central responsibility, Customer Technical Services are comprehensive
designed to simplify support and accelerate problem resolution for mission solution support
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. Integrated
• For offering support and individual pricing contact your local CTS HW and SW1
representative listed below. support
Improve availability
Full SAP HANA on POWER Custom Technical Support & reduce resolution
time

Avert problems:

proactive services,
preventative support
advice & services
SAP

Individual
SUSE
continuous
customer
interaction

© 2016 International Business Machines Corporation

TCO – Get the Complete Picture!

Environments
Components Time
TCA
Hardware $ $ $ $ $ Planning
Software $ $ $ $ $ Upgrades
People $ $ $ $ $ Migration
Network $ $ $ $ $ Growth
Storage $ $ $ $ $ Parallel Costs
Facilities $ $ $ $ $ Net Present Value

QoS – Availability, Reliability, Security and Scalability

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

© 2016 International Business Machines Corporation

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.
5 year TCO comparison 5 year TCO comparison
3,5 25,0
3,0
Cost (Million €)

Cost (Million €)
2,5
11.7% 20,0
1.7%
2,0 15,0

1,5
10,0
1,0

0,5 5,0

0,0
0,0
Power x86 Server
Power x86 Server

Infrastructure only Infrastructure plus SAP Application

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.

© 2016 International Business Machines Corporation

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, rrommel@us.ibm.com

o Alfred Freudenberger, afreude@us.ibm.com,

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

o Bob Wolf, rewolf@us.ibm.com

– Offering Manager: Anna Coffey, amcoffey@us.ibm.com

– SAP BUE: Vicente Moranta, vmorant@us.ibm.com

© 2016 International Business Machines Corporation

 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

© 2016 International Business Machines Corporation

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

© 2016 International Business Machines Corporation

 Thai

Russian
Traditional Chinese

‫תודה‬
Hindi

Hebrew

Siyabonga
Zulu
Dankie
Obrigado Afrikaans

Brazilian Portuguese
Arabic

Danke
German

Gracias Spanish
Merci
French

Tamil
Korean
Japanese

Grazie
Italian Simplified Chinese

Blog:
SAPonPower.wordpress.com
© 2016 International Business Machines Corporation 51