willkommen - profi-ag.de sap hana –neue ... sizing guidelines can be significantlyrelaxed. −...

WILLKOMMEN

SAP HANA – NEUE ENTWICKLUNGEN

Arne Tornieporth, PROFI

Leiter Kompetenzteam SAP HANA

Solution Architekt

SAP HANA in Data Centers Ι Arne Tornieporth2

AGENDA

1 SAP Produkte mit SAP HANA DB

2 HANA on Power Update

• Neue Funktionen in HANA 1.0 SPS12 und HANA 2

• Neue Applikationen S/4HANA, BW/4HANA

• Supported Topologies

• Big Endian/Little Endian

3

DSAG 2017 Mannheim

4 SAP HANA neue Entwicklungen | PROFI Webcast

HANA on POWER Entscheidungsfindung

Infrastruktur

https://www.youtube.com/watch?v=2ox71S6RgpA

SAP S/4HANA

Six Years of SAP HANA Evolution

5

SAP HANA neue Entwicklungen | PROFI Webcast

- On-premise market is split between appliance and TDI model

while TDI is getting momentum- 13 vendors selling SAP HANA pre-built appliances

- 10 server & 17 storage vendors participating in TDI (tailored datacenter

integration) that offers flexibility to choose SAP HANAinfrastructure

- IBM HANA on POWER is exclusively supported via TDI model

- ~10% of HANA deployments is on Cloud and 90% is on-premise(June ‘16)

- SAP offers fully managed offering in their cloudinfrastructure named as SAP HEC (HANA EnterpriseCloud)

- 4 Cloud (IaaS) providers offer SAP HANA as a service

(Amazon, Huawei, Azure, IBM Bluemix)

- IBM IaaS Cloud offering via Softlayer under SAP certification

- IBM CMS offerings for HANA areavailable

Source: Considerations When Selecting a SAP Hana Platform Vendor – Gartner June 2016

HANA Infrastructure Players

4


HANA Dynamic Workload Mapping (SPS11)

• Dynamic Workload Mapping can:

− classify workloads based on user and application

context information

− apply configured resource limitations to:

memory limit, maximum tx parallelization, priority

− allow to influence dynamic resource consumption

on the session or statement level.

• Enables dynamic mapping of system resources

to DB-clients with different workload profiles

− on session and statement granularity

− avoid resource abuse by single statements

• Pre-defined workload classes can be mapped

to end-user or application session context

according to mapping policies

• No changes in the application code of theDB-clients

− end-user / session variables identify various workload qualities

− non-tagged context is processed with default class and priority.

Desktop Datamart

Mobile Dashboard

db-connect

Workload Class

“DATAMART”

db-connect

Session Context Workload Class

BW”

Workload Class

“CRM”Ma

pp

ing

Rule

s

Session Layer

Workload Class

“MOBILE”

Session Context

➢ Results in more consistent response time behaviour

even with changing HANA DB utilization.

➢ Avoids resource consumption by single transactions

and query steps.


HANA Workload Capture and Replay (SPS12)

• Assess impact of landscape changes with recorded

customer workload instead of

artificial scripts and scenarios

• Use Cases like evaluation of:

− new software revisions of HANA, OS etc.

− impact of changed information/data model

− system landscape topology changes

− …

• Allows for similar concurrency, memory allocation

and CPU usage than the captured real DB-

workload

− Not for XS based workloads now

• Records and replays SQLstatements

− Platform independent and transportable

• (Replayed) DB-workload can be analysed in great

detail and with high time-based resolution

© 2017 IBM Corporation


HANA Scale-Out

• Valid for OLAP (BW) use cases

– No support for OLTP-like applications (e.g., Suite on HANA orS/4HANA)

• Database resiliency can be providedby

– Host Auto-Failover n active and m standby nodes

– System Replication with 2 * n nodes

• File system layout:

– Shared nothing architecture, separate file system for each HANAnode

– Binaries and configuration files in /HANA/shared are shared, e.g. via NFS

Update SAP HANA 2

• Scale-out for S/4HANA release February,28th

• Only for system sizes which are not yet supported with single HANA

scale-up instances

• Limited to maximum of 4 worker nodes + optional standby

• Minimum 64 cores and 6TB per node

• SAP-Note 2408419 “SAP S/4HANA Multi-NodeSupport”

Host Auto-Failover

Standby

Name

Server

Index

Server

Workern

Name

Server

Index

Server

Worker1

Name

Server

Index

Server

Data

Disks

Log

Disks

Data

Disks

Log

Disks

Data

Disks

Log

Disks

Master

Name

Server

Index

Server

Standby

Name

Server

Index

Server

Pers

iste

nce

SA

N/N

AS

Storage Connector


BW-on-HANA Extension Nodes

• Use for SAP HANA OLAP workloadsonly

• Extension nodes of same physical size as worker nodes

− Require own spare node(s)

− Single HANA DB, one SID

• HANA sizing targets a RAM occupation of 50% by in-memory

business data.

− Remaining RAM as space for intermediate result sets and data processing

area.

• By placing less frequently used data onto the Extension Node(s),

sizing guidelines can be significantly relaxed.

− Allows significantly more business data to reside in Ext. Node RAM

• Limited memory gain with initial architecture, but:

• Consistent HANA cluster incl. Ext. Nodes (no SybaseIQ)

Update SAP HANA 2

• Extension Nodes can be of different (larger) size than

Worker Nodes

• extension node class can be defined amongworker

groups


External Data Access

Update SAP HANA 2

SDI

• Virtual Procedures

• RESTAPI

• New and enhancedAdapters

• Extended Table Support

SDA

• Sync of virtual table metadata

• virtual tables result caching in HANA

• Integration of virtual tables with result caching in HANA

• SAP HANA to Hadoop native connectivity

• SAP HANA SDI (smart data integration) and SDQ (smart data quality) load

data, in batch or real-time, into HANA from a variety of sources usingadapters

− Combination of Data Provisioning Agent instance with the adapters

connected to the Data Provisioning server, housed in the HANA system

• SAP HANA SDA (smart data access) enables remote data to

be accessed as if they were local tables in SAPHANA−

−

−

no data are copied/moved into SAP HANA DB

virtual HANA tables map to an existing object at the remote data source

HANA functionality without moving all data to HANA DB

SDA

SDI


HANA External Data Access with IBM POWER

• Data ProvisioningAgent

−

−

−

−

With HoP V1 BE it needs to be hosted on an Intel machine

It an be connected to a HANA on POWER DB for a full SDI landscape

With HoP V2 LE it can be co-hosted on POWER

Is used by SAP Migration Tool

HANA SDA (Smart Data Access)

• For IBM Power Systems the following data sources are supported

with SAP HANA2:− SAP HANA

− SAP IQ

− SAP Adaptive Service Enterprise

− Oracle Database 12C

− (DB2 LUW on Intel only)

• Landscape setup can be POWER only, or cross platform (source

systems / HANA DB)

x86 with

POWERBE

HANA SDI (Smart Data Integration)

• SAP HANA with the data provisioning server is supported with IBM

POWERany

OS

Heterogeneous data

sources on POWERor

other platforms

© 2017 IBM Corporation


S/4 HANA - the Next Generation Business Suite (announced Feb. 2015)

• S/4 HANA: S= Simple, 4= forth

generation

• “New” SAP Business Suite fully

built on the SAP HANAplatform• only supports SAP HANA asunique

database

• Contains core business functions

from CRM, SCM, ERM, BW…

• SAP Fiori user experience• Fewer transactions, drill-in

• Role based views

• Mobile support

• Can coexist with traditional

SAP Business Suite

• SAP Netweaver 7.50 for on-premise

• SAP NW 7.60 for cloud deployments

20


Transition to SAP S/4HANA

Three basic scenarios:

Source: SAP SE

• System Conversion of an existing SAP Business Suite system to SAP S/4HANA• Adaption to S/4 data model = profiling, cleansing and de-duplication of existing Business Suite data

• Is technically based on Software Update Manager (SUM) with Database Migration Option (DMO) in case

the customer is not yet on SAP HANA as the underlying database.


SAP BW/4HANA - the Next Generation BW (announced in September 2016)

• is a new data warehouse solution highly optimized

for HANA

– Provides the required eco-system and management

capabilities around HANA as an OLAP-DB

• Transition from SAP BW to BW/ 4HANA can be

compared with the transition of the SAP Business

Suite to S/4HANA.

• customers have “one version of the truth”

– Significant reduction of the numberof

data objects to be stored and maintained

• Supports / Integrates variety of data sources

– HANA native DataStore object

– Big Data source system type for Hadoop Spark SQL

adapter

• accelerates solution development

• Supports cloud (HEC, AWS) and on-premise use

case- Both share identical code base and functionality.

…“The SAP HANA platform on its own is an amazing

database, but it doesn't contain the rich functionality of data

warehouses for data harmonization, batch loading of legacy

data, and long term storage. That's where SAP BW/4HANA

comes in.”…Source: The SAP BW/4HANA FAQ by bluefin

23


http://www.bluefinsolutions.com/blogs/john-appleby/august-2016/the-sap-bw-4hana-faq

SAP HANA in Data Centers Ι Arne Tornieporth16

AGENDA

1 SAP Produkte mit SAP HANA DB

2 HANA on Power Update

• Neue Funktionen in HANA 1.0 SPS12 und HANA 2

• Neue Applikationen S/4HANA, BW/4HANA

• Supported Topologies

• Big Endian/Little Endian

Allowed Hardware for HANA on IBM Power ServerPOWER8

Model

Minimal

cores per

LPAR

(128GB)

Maximalcores

per LPAR

Max. memory

per LPAR BW

or BW/4HANA

Max. Memoryper

LPAR

SoH or S/4HANAAllowed PowerVM

LPARs

Maximum

Core-To-Memory

Ratio (CTM)

SAP-Note2188482 - SAP HANA on IBM Power Systems: Allowed Hardware

2230704 2188482

S822 4 20 640 GB 1024 (1920) GB • 4 dedicated(-donating)

PROD

• 3 dedicated(-donating)

PROD +

1 shared pool for other

workload

• optional 2 VIOs

• 1:32 BW

• 1:96 SoH & S/4

S822L 4 24 768 GB 1024 (2304) GB

S824 4 24 768 GB 2048 (2304)GB

S824L 4 24 768 GB 2048 (2304)GB

E850 4 32 (!) 1024 GB 3072 GB

E850C 4 48 2400 GB 4096 (4608) GB• 6 ded. or 5+1

• 1:50 BW

• 1:96 SoH & S/4

E870, E870C 4 80 4000 GB 7680 GB• 8 ded.(-don.) PROD

• 7 ded.(-don.) PROD +

1 shared pool for other

workload

• optional 2 VIOs

• 1:50 BW

• 1:96 SoH & S/4

E880, E880C 4 96+ 4800 GB see separate table

• 1:50 BW

• 1:114(1) SoH & S/4

Scale-Out

(Multi-Host)

max.

cores per

node *max. 16max. memory per

node *max. 16n/a as with single node as with single node

26(1) 16TB LPAR, see details here

Allowed Hardware for HANA on IBM Power Server


http://service.sap.com/sap/support/notes/2188482



• The rules for BW on HANA and BW/4HANA stayunaffected.• CTM 1:50 yielding a max. LPAR size of 4.800GB

• Beyond this limit make use of scale-out (in a box)

• Consider HANA mechanisms like extension nodes, data tiering.

Memory Support for E880 and E880C to 16TB for SoH

27

2188482 - SAP HANA on IBM Power Systems:Allowed Hardware• For the E880 models up to 16TB per LPAR are supported for OLTP-type of workloads,namely:

Products from SAP Business Suite, powered by SAPHANA

SAP S/4HANA ON-PREMISE

SAP S/4HANA FINANCE, SAP SFINANCIALS

Banking services from SAP (including SAP BankAnalyzer)

SAP Solution Manager

SAP Master Data Governance

SAP Gateway

• Below 9TB memory size the constant Suite on HANA core to memory ratio of 1:96 applies

• Above 9TB memory size the following ratios are supported according to absolute LPAR size:

min LPAR size/GB max. LPAR size/GB

Minimum numberof

cores per LPAR

maximum number of

cores per LPAR

maximum

GB/core

9.217 10.240 108 132 95

10.241 11.264 120 132 94

11.265 12.288 128 144 96

12.289 13.312 132 144 101

13.313 14.336 136 144 105

14.337 15.360 140 144 110

15.361 16.384 144 144 114

Mandatory:

run LPAR in

SMT4 mode

In these cases



SLES for SAP 12 LE Support for HANA 2 and SAP Applications

• SAP HANA 2 has been announced in November2016

• S/4HANA, BW/4HANAand SAP NetWeaver 7.5 (including BW) are supported as of February

2017

• see SAP-Note 2460699 for details:

• Support for SAP Business Suite (ERP) on HANA 2 or SAP NetWeaver 7.4 only during

upgrade phase

• does not depend on platform or endianness


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

SAP HANA 2.0 – Current Application Support Summary

*** IBM and IBM Business Partners only ***


HANA DB

- scale-up

- scale-out

Application Tier

- SAP NetWeaver BW

- SAP Business Suite (H1 only)

-SAP S/4HANA

-BW/4HANAothers

SAP HANA on POWER Platform Support

HANA

Client SW

V1.0 SAP HANA2

SLES 11

Big vs.

(SLES for SAP 11

recommended)

SLES 12

Little Endian

(SLES for SAP 12

mandatory)


SLES 11 BE to SLES 12 LE Transition

• IBM and SAP have decided to provide SAP HANA2 only in Little Endian format• SUSE SLES (for SAP) 12 on POWER is LE only

• SAP NetWeaver 7.5ff stack has been released as LE version

• Existing BE App-Servers can connect to LE-HANA 2 DBtoo

• Existing HoP 1.0 and supported applications will stay BE only, supporteduntil

03/19 per SUSE mainstream support, plus optional Support extension(LTSS)• LE NetWeaver can connect to BE-HANA V1.0 DBtoo

• The switch to LE has some advantages:• Easier eco-system adaption on PowerLinux (3rd party applications)

• Data compatibility with x86 platforms

• Existing HANA on Intel systems can easily migrate to HoP LE

• Better integration into SAP SE development and sw-logistics chain

• Internal FAQ available on HANA on POWER Community and IBM Conversations


SLES 11 BE to SLES 12 LE

Consequences for SAP HANA Users

• Existing BE HANA 1.0 customers switching to SAP HANA 2 LE haveto:• transform their existing SLES 11 environments to SLES 12

• migrate their existing HANA databases to LE presentation

• HANA data migrationoptions• Traditional SAP heterogeneous datamigration..

• SAP SW Provisioning Mgr. tools for an export in parallel with the import using SOCKETS

• HANAASCII export and import

• HANA Smart Data Access (SDA) and Create Table as Select (CTAS)

to transfer selected tables from BE source system.

• SAP HANA Migration Tool based on HANA SDI for offline migration

• Online migration options are in development with the goal of minimized DB downtime.

• Existing HANA2.0 on Intel customers can just copy their data to POWER• HANA System Replication across both platforms possible (not active/active)

• Backup/Restore


PROFI Engineering Systems AG

Zentrale

Otto-Röhm-Straße 18

64293 Darmstadt

Telefon +49 6151 8290-0

Telefax +49 6151 8290-7610

mailto:[email protected]

http://www.profi-ag.de

VIELEN DANK!

Arne Tornieporth

Leiter Kompetenzteam SAP HANA

Solution Architekt

Telefon +49 40 636699-2214

Telefax +49 40 636699-2229



http://www.profi-ag.de/


willkommen - profi-ag.de sap hana –neue ... sizing guidelines can be significantlyrelaxed. −...

Documents