Hana On Power For Aix Vug

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
application function library SDK for SAP HANA
1.0
banking services from SAP

SAP Business Planning and Consolidation
9.0
SAP Business Suite, powered by SAP HANA
SAP Business Warehouse, powered by SAP HANA
Comment
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
This includes the add-ons released via Note 1820906 or Note 2167814.
SAP CRM 7.0 EHP3
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
SAP Gateway
SAP Global Trade Services
SAP HANA data warehousing foundation
SAP HANA dynamic tiering
SAP HANA smart data integration
SAP HANA spatial
SAP Hybris Commerce
SAP Hybris Marketing
9.1
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
SAP Operational Process Intelligence
7.5
This includes all add-ons released via Note 2156543 and Note 2156130
SAP Portfolio and Project Management

SAP Risk Management
SAP S/4HANA FINANCE
6.1
SAP S/4HANA ON-PREMISE
1511 FPS 02
SAP SFINANCIALS
1503
SAP Smart Business foundation component
1.0
SAP Solution Manager

SAP Transportation Management
7.2
9.1
SAP Transportation Resource Planning
1.0
2.0
11
SPS 02
SPS 11
1.0 SP02
SPS 11
6.0
1.2
1.0
10.1
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
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.
2016 International Business Machines Corporation
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
Today
Calculation
Future
Application
Layer
Database
Layer
In-Memory Computing Imperative:
Calculation
Avoid movement of detailed data

Calculate first, then move results
4
SAP Business Suite 4 SAP HANA (S/4HANA)
HANA Vora Reference Architecture

Data Sources
EDW
Non-SAP
Analysis
Network
Analytics
Visualization
Customer Analytics
Predictive
Maintenance etc..
ERP
OLAP on Hadoop
Real-Time Analytics
SAP HANA
Spark
Spark
Spark
SAP HANA Vora
SAP HANA Vora
SAP HANA Vora
Files
Files
Files
SAP HANA
Index Server
YARN
Data Processing Engines

SQL Optimizer / Executor
HDFS
In Memory Store
Traditional Row-Oriented vs. Column-Oriented
HANA Data Compression Data Dictionary

Transposing Data into Integers
Dictionaries
Cardinality
Data tuples
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
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: Todays 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
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
SAP ECC
Column Store
Row Store
SAP HANA
R-Z
Table Partitioning
SAP HANA on Power Architecture
HANA
Calculation
Engine
Join
Engine
OLAP
Engine
HW
Engine
x86
Power
Not a separate fork of the HANA code

2010
2011
2012
2013
2014
2015
SAP HANA on IBM POWER
+
Enterprise ready
Mission Critical Reliability
Flexiblility
Virtualized
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
16000000
15,519,000
14000000
12000000
Throughput/hour
Packing more HANA throughput into few cores leaves room for other
requirements, reduces datacenter footprint and environmentals
10,012,000
10000000
8,279,000
8000000
Day
Night
7,429,000
6,664,000
6000000
4,270,000
4000000
2000000
IBM 4-core p6 570
3 to 5x memory bandwidth, 8 threads per core deliver consistent HANA

response time, even during Delta Merge processing
Services
Sun 16-core E6900
HP 16-core rx8620
HANA Appliance
TDI Tailored Datacenter Integration
Fast Implementation
Support fully provided by SAP
Solution validation done by SAP

and partner
Preconfigured hardware set-up
Preinstalled software
More Flexibility
Save IT budget and existing investment
Installation needs to be done by

customer
Customer aligns with the hardware
partner on individual support mode
HANA Appliance
T-Shirt Sizings
Fast Implementation
Support fully provided by SAP
More Flexibility
Save IT budget and existing investment
SUPPORTED
CERTIFIED
TDI Tailored Datacenter Integration
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?
Delivering freedom of choice to the HANA Landscape

Applications
Power Landscape example

SAP HANA
PowerVM
BW HA
HANA
App
, XFS2, NFS, ext3
CRM
DB/App
BW QA
DB/App
CRM QA
DB/App
BW App
VIOS
Monitoring
VIOS
SAP HANA Host Auto-Failover & System

Replication, SUSE HA Ext, RH HA Plugin1,
Symantec HA1, Tivoli SA
Spectrum Scale
HANA
ECC App
High Availability
File System
ECC
App
Backup
Data
Sys Mgmt
PowerVM
OS
ECC HA
HANA
ECC App
App
ECC QA
HANA
POWER7+(non-prod) or POWER8
Standalone or shared/PVM virtualized
ECC HA QA
HANA
Storage Hardware
BW HA QA
Linux Enterprise Server

Priority Support for SAP applications
Server Hardware
App
ECC, BW, SM App Sbx
VIOS
HANA
VIOS
BW
HANA
Customer choice
1)
2)
16
Not currently supported with Linux on Power. Contact RedHat for product plans.
XFS is required for production.
1TB
BW
3TB
BW
4TB
BW
1TB
SoH
6TB
SoH
HANA on POWER Portfolio
E880
E870
E850
S822
S814
S824
Scale-Out
Enterprise
HANA on Power
Solution Editions
IBM fast-start option
Industry best-practice
S824L
Quick configurations
S822L
Aggressively priced
S812L
Linux only Systems
Rapid deployment of SAP

HANA on IBM Power
Systems
DRAM
Chips
POWER8 Memory
Memory
Buffer
10 chips per rank for

extra redundancy
beyond chipkill
DDR Interfaces
16MB
Scheduler &
POWER8
Memory
Management Cache Link
On-the-fly lane isolation/repair
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
This is a very CPU/Memory intensive task (!!!)
19
Power delivers up to 5x memory

bandwidth, 4x CPU threads vs.
x86!
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 v3
POWER8
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
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
Clock rates
Max L4 Cache/socket
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
20
High Availability Disaster Recovery
SAP HANA HA: System Replication

Cost Optimized
Performance Optimized
Performance and
Cost Optimized
with POWER
QA/DEV
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
running
Shared
Shared
Very low RTO

Majority of secondary CPU
resources available to VMs
Perfect fit for strong
production level virtualization
solution such as PowerVM
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
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
Highest Flexibility and Agility with SAP HANA Landscape

POWER8 Server
SAP TDI
certified
Storage
PowerVM
HANA BW PROD DB
(up to 50GB/core)
optional VIOS
(ded.-donating LPARs / IFLs)
LOG 1
Data 1
Suite on HANA
(ERP) PROD DB
Suite on HANA
(ERP) PROD DB
(up to 96GB/core)
Max. of 3 HANA PROD DB
Redundant
8Gb SAN
Data 2
LOG 2
XFS filesystems
Data n
LOGn
HANA DB
Any workload mix

allowed
ERP App-Server
e.g., BW App-Server
HANA BW Non-PROD
HANA Prod MDC
(multi-tenant
)
HANA
ERP Non-PROD
H
N
1
Other workloads
HNn
optional VIOS
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
Shared Processor Pool

BW App-Server
HANA
Analytics
PROD 2-tier
SAP Note 2230704
TDI aligned, Linux,

dedicated donating
Traditional Sizing,
Shared Pool
Free sizing,
Shared Pool
24
SAP HANA Consolidation with VMware

VMware 5.5, 6.0 allowed for
prod with restrictions
x86 Server
VMware Hypervisor
No VM may share a socket

HANA BW PROD DB
Max size 1TB
Up to 28.4GB/core
bare metal
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
Suite on HANA
(ERP) PROD DB
Max size 1TB
Up to 42.7GB/core
bare metal
Non-prod not supported on

same system
HANA Analytics
PROD 2-tier
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
SAN
Connections
SAP TDI
certified
Storage
LOG 1
Data 1
Data 2
LOG 2
HANA DB
XFS filesystems
e.g., BW App-Server
Data 4
HANA Prod MDC

(multi-tenant )
H
N
1
LOG 4
HNn
Power HANA Sample architecture

Based on Best Practices TDI Principles
Production Site
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
Non-prod
Each instance may reside in a

VM and share systems with
prod, HA and/or DR VMs if
enough capacity available
Prod
HA
(optional)
Power System
Power System
<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
DR site
(optional)
DR/Prod
HA
(optional)
Power System
Power System
Dev usually
sized at 25%
or prod
Test
Optional,
sizing variable
Disk subsystem
Optional
QA HA for
testing
purposes
only
Application servers
Each instance may reside on
separate commodity based
servers or on above systems
if enough capacity available
QA usually
sized = prod
RTO criteria for HA
SAPS based sizing,

usually n+1
IBM Storage replication

Or
Async HANA System replication
Disk subsystem
<5 min per TB
IBM FlashSystem V9000

>12 min per TB
IBM Storwize V7000
Log files on SSD
Data files on HDD
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.
6TB HANA SoH Comparison x86 vs. Power

Currently supported
x86
Production
+ HA
8-socket
Haswell EX
6TB
Power
8-socket
Haswell EX
6TB
E870
E870
Data
QA
8-socket
Haswell EX
6TB
Data
8-socket
Haswell EX
6TB
Optional
HA
test
Data
Dev 1TB +
sandbox
.5TB
QA LPAR
on HA node
-add 6TB
Optional
HA test
add 6TB
on prod
node
Dev,
Sandbox on
HA node or
HA test
node - add
1.5TB
2-socket EX
VMware
Data
HA 6TB
LPAR
Layout
App
Servers
2-socket EP
VMware
2-socket EP
VMware
Need 2 for capacity and failover
Prod 6 TB
QA 6TB
HA Test 6 TB
Dev 1TB
Sbx .5TB
S822L
Failover to HA node above

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
If you need to move a lot of dirt, look for track record in that space
Lots of nozzles
Might be able to attach a trailer
Big engines
Huge proven capacity
If you need to run large OLTP systems, 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
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
Benchmarks dont tell the whole story, but they are an

important consideration
SGI UV
HP Superdome
SpecInt_Rate
2006
14,400 @ 192 cores
11,400 @ 288 cores
11,100 @ 288 cores
2-Tier SAPS
436,100 @ 80 cores
5,451 SAPS/core
N/A
545,780 @ 288 cores

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

12/10/08
N/A
4,092,799 tpmC @ 128 Itanium2

cores 08/06/07
N/A
N/A
1,200,011 tpmC @ 8 P7 cores

10/13/10
3-Tier SAPS
1,471,680 @ 64 P7+ cores
NUMA affinity
POWER8
Intel ccNUMA architecture

4-socket/3TB HANA
8-sockets/6TB HANA
Not bad, but limited in size/scale

SGI-uv ccNUMA design up to 32-sockets,

24TB
6 or 7 hops for every

off-motherboard
remote memory
access
HP Superdome X ccNUMA design up to

16-sockets, 24TB
8 hops for every offblade remote

memory access
POWER8 Enterprise SMP Interconnect Topology
Vertical Full Connect
Horizontal Full Connect
4 hops for every off-CEC remote memory access
ccNUMA characteristics, large memory effects on RAS

POWER8
SGI UV
HP Superdome
% of mem
access off
planar
12/16, 75%
28/32, 87.5%
14/16, 87.5%
Off-planar
memory 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

RTO after
failure or
HANA
patching
Data aging
Response time of
on-demand
columns
dependent on
latency,
throughput of
IOPS
Load time
dependent
on
throughput
of IOPS
Client
Part
Order
number date
Shipped
date
Delivery
date
Quantity
Total
price
Item
Item Package
Weight cost weight
Instructions
Status
Conventional DB
Delta Table in HANA
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
Leave on
$42.00 porch
Single Async IOP

abc
123
8/1/2015
9/6/2015
9/15/2015
15
0.56
1.35
In-transit
Delta merge
9.5
$42.00 Leave on porch
In-transit
Async IOPS = number of columns

(at minimum)
abc
9/15/2015
123
8/1/2015
9/6/2015
9.5
15
$42.00
0.56
Leave on porch
1.35
In-transit
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 Backup and Recovery

Data backups
Memory Disk Backup
Contain the current payload of the data
SAP HANA database
Memory
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 backups
Savepoint
Data Area
(disk)
COMMIT
Log Area
(disk)
Contain the content of closed log segments

Automatic (asynchronous) whenever a log
segment is full or the timeout for log backup
has elapsed
Log volume contains log segments
Data Backups
Log Backups
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
studio
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)
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
dpd/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:
hdbsql
Create backup
SAP HANA Database
Backup
Storage,
e.g. NFS
Create backup
SAP HANA Database
o Data backups to Backint can be triggered/ scheduled using SAP HANA

studio, SQL commands, or DBA Cockpit
o Log backups are automatically written to Backint (if configured)
3rd Party
Backup Agent
3rd Party
Backup
Server
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-Shadow
for 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
Available
41
41
Generic PowerLinux Eco-System (1)

not HANA / SAP specific but can be used with
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
42
Generic PowerLinux Eco-System (2)

ISV
Product
Component
Description
Status
Security / Compliance / Inventory

IBM
Endpoint
Manager
For compliance and security management

(agent)
Compliance, security
Available
IBM
TAD
Tivoli Asset Discovery for Distributed
Inventory management
Available
Workload Automation Agent for Linux 11.3

SP1 [formerly AutoSys]
Job scheduling
Beta available
GA 4/2016
VPSX
SAP Output Management
Beta available
Miscellaneous
CA
LRS
Workload
Automation
43
IBM Services for SAP HANA on Power
Technical design and

infrastructure deployment
Operation and optimization
Assess, Upgrade and

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
Overview HANA on POWER Integrated Solution Service
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.
Full SAP HANA on POWER Custom Technical Support
Optimized access
to a
comprehensive
solution support
Integrated
HW and SW1
support
Improve availability
& reduce resolution
time
Avert problems:
proactive services,
preventative support
advice & services
SAP
Individual
SUSE
continuous
customer
interaction
TCO Get the Complete Picture!
TCA
Environments
Components
Time
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!
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

25,0
3,0
11.7%
2,5
2,0
1,5
1,0
0,5
0,0
Power
Infrastructure only
x86 Server
Cost (Million )
Cost (Million )
3,5
1.7%
20,0
15,0
10,0
5,0
0,0
Power
x86 Server
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.
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/cgibin/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
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
Thai
Russian
Traditional Chinese
Hindi
Hebrew
Siyabonga
Dankie
Zulu
Obrigado
Afrikaans
Brazilian Portuguese
Arabic
Danke
German
Gracias
Merci
Spanish
French
Tamil
Korean
Japanese
Grazie
Simplified Chinese
Italian
Blog:
SAPonPower.wordpress.com
51

Hana On Power For Aix Vug

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Hana On Power For Aix Vug

Caricato da

Copyright:

Formati disponibili

SAP HANA on Power

application function library SDK for SAP HANA

banking services from SAP

SAP Business Suite, powered by SAP HANA

SAP Business Warehouse, powered by SAP HANA

Except for SAP Bank Analyzer, which is not yet released.

10.0, version for SAP NetWeaver

Nearline Storage in connection with SAP

Business Intelligence in connection with SAP

SAP BusinessObjects Business Intelligence platform

SAP Cost and Revenue Allocation for Financial Products

SAP Customer Activity Repository retail applications bundle 1.0 SPS 03

SAP Landscape Transformation Replication Server

2.0 DMIS 2011 SP 07

SAP Liquidity Risk Management

SAP Manufacturing Execution

SAP Master Data Governance

SAP Portfolio and Project Management

SAP S/4HANA ON-PREMISE

SAP Smart Business foundation component

SAP Solution Manager

SAP Transportation Resource Planning

2016 International Business Machines Corporation

SAP strategy for HANA

2016 International Business Machines Corporation

In Memory Computing: Re-think Paradigms

Avoid movement of detailed data

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

2016 International Business Machines Corporation

HANA Vora Reference Architecture

SAP HANA Vora

SAP HANA Vora

SAP HANA Vora

Data Processing Engines

2016 International Business Machines Corporation

Traditional Row-Oriented vs. Column-Oriented

2016 International Business Machines Corporation

HANA Data Compression Data Dictionary

Integer representation of data

Example: There are 195 countries in the world.

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

Scale-out vs. Scale-up

2016 International Business Machines Corporation

SAP HANA on Power Architecture

Not a separate fork of the HANA code

2016 International Business Machines Corporation

SAP HANA on IBM POWER

2016 International Business Machines Corporation

SAP HANA on IBM Power Expected Customer Value

IBM 4-core p6 570

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

2016 International Business Machines Corporation

Sun 16-core E6900

TDI Tailored Datacenter Integration

Solution validation done by SAP

Installation needs to be done by

2016 International Business Machines Corporation

TDI Tailored Datacenter Integration