update zu sap hana auf ibm power systemen · sap hana 1.0 sps10+ sap hana 2.0 sles4sap 11sp4...

Welcome to the waitless world

Carsten Dieterle [email protected]

Update zu SAP HANAauf IBM POWER Systemen

Infrastruktur:Status-News-Update, TDI5

Kundenbeispiele• Freudenberg IT (FIT)• Adolf Würth GmbH

AIX User Group Meeting, 07. Februar 2018

© 2018 IBM Corporation


Agenda:

2

• HANA on POWER: Status-News-Update• SAP TDI5 Sizing – Core reduction, I/O• PoC: SAP BW workload in shared processor pool• IBM Storage and Backup solutions for SAP HANA• Customer examples

• Freudenberg IT (FIT)• Würth – SAP HANA 2.0 Migration



3

FlexibilitySuperior virtualization and management features to afford flexibility and maximum utilization

ResiliencyUnsurpassed RAS (reliability, availability, serviceability) characteristics to support mission critical SAP applications

PerformanceHighest throughput per core and core/memory bandwidth to deliver faster business results, up to 2x Intel-based alternatives

Competitive CostFlexibility + Performance + RAS= better TCO

ü Best infrastructure to achieve scalability, response time and throughput requirements

– Additional headroom for peak workload due to virtualization capabilities

ü Reliable infrastructure for enterprise applications

ü Risk-free sizing and implementation

– Dynamically adjust sizing to changing requirements

– Grow number of systems and sizes on demand while project advances

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

Thro

ughp

ut/ho

ur

DayNight

ü TCA: similar to x86

ü TCO: better than x86

What makes IBM Power Systems the best platform for clients’ mission critical SAP HANA deployments?



4

HANA DB- scale-up- scale-out

Application Tier- SAP NetWeaver - SAP NetWeaver BW- SAP Business Suite - SAP S/4HANA- SAP BW/4HANA others

SAP HANA on IBM POWER Platform Support

SAP HANA Client SW

V1.0 V2.0

SLES 11 SLES 12RHEL 7.3/7.4

Big vs. LittleEndian

(SLES 11 for SAP (SLES 12 for SAP, RHEL for SAP Solutions

recommended) mandatory)

SAP HANASAP HANA



POWER8 Product Line – current available models -for SAP HANA on IBM POWER Production

Power E870C

Power E880C

Power E850C

Power S822

Power S824

PowerS824LPower

S822L

Scale-out server2 sockets

Number of cores & memory

E870C: 4-8 Sockets

32-64 Cores

up to 16 TB

E880C: 4-16 Sockets

32-192 Cores

up to 32 TB

E850C: 2-4 Sockets

16-48 Cores

up to 4TB

S-models: 2 Sockets

8-24 Cores, up to 4TB

Enterprise server2 - 16 sockets

32-128 Cores4,35 GHz



32-64 Cores4,02 GHz



6

SAP HANA on IBM POWER Systems Memory Limits:

Quelle: 2188482 - SAP HANA on IBM Power Systems: Allowed Hardware V45 – 19.12.2017

BW on HANA and BW/4HANA:ScaleUp: 10 TBScaleOut: 16x 10 TB = 160 TBSuite on HANA and S/4HANA:ScaleUp: 16 TB (24 TB with SLES4SAP 12 SP3 soon)

ScaleOut (S/4HANA only): 4x 16 TB = 64 TB(4x 24 TB = 96 TB with SLES4SAP 12 SP3 soon)



7

• The new rules are valid for all Suite / S/4 and BW / BW/4 Sizing cases(L = 100% CTM, M = 50% CTM, S = 25% CTM)

• Running on certified IBM Power 8 (and also Intel HANA Nodes).

• The primary sizing factor of a HANA DB is still the memory requirement, this remains unchanged

• New is the CPU and I/O Capacity sizing.

SAP HANA Migration Sizing – TDI Phase 5



8

IBM Optimization example of HANA on POWER core usage, based on best practises HANA DB Server



9

IBM Optimization example of HANA on POWER core usage, based on best practises, HANA DB Server + SAP APP Server


Welcome to the waitless worldSAP SEM PRD on Oracle

10



SAP SEM PRD on HANA – shared pool cappedw/ red. entitlement - Summary

11

• The (11-days-)average maximum physical CPU on Oracle: 1,9

• The (5-days-)average maximum physical CPU on HoP (dd): 1,3• The (7-days-)average maximum physical CPU on HoP (dd): 0,7

• The (3-days-)average maximum physical CPU on HoP (spu): 4,0

• The (4-days-)average maximum physical CPU on HoP (spc): 3,6

• The (n-days-)average maximum physical CPU on HoP (spc - reduced): Does not make sense!



Conclusion from PoC with SPP

12

From a practical standpoint, we proved that:

• the given HANA BW systems can be moved to shared pool cores w/o loosing the performance advantage vs. former Oracle implementation

• even if the number of available cores in the shared pool drastically decreases, the HANA BW still runs and a correlation in-between a poor(er) performance and the stressed shared pool has not be seen so far

• anyhow, SAP and IBM labs are right: Turning off NUMA affinity increases the number of cores (by factor 3) consumed!



Some Thoughts on ‚Right-Sizing‘

13



14

IBM SW defined Storage & IBM Cloud Object Storage

IBM storage Non-IBM storage

All-Flash Hybrid Tape / Virtual Tape

VirtualizedBlock

Scale-OutBlock

Scale-OutFile

Scale-OutObject

Infrastructure

ArchiveBackup

Monitoring & ControlManagement

Copy Data Management

Backup & Archive

Cloud

Snapshot and Replication Automation for heterogeneous storage environments.

Optimized hybrid cloud data protection to reduce backup costs by 53%

Scalable, simple to manage storage technology that provides the ideal object based storage platform for hybrid cloud.

Virtualization of heterogeneous storage environment – stores up to 5x more data.



15

IBM Spectrum Storage

SVCV9000

Storwize V7000V5000

Software

FlashCore

FS900A9000V9000

DS8880

Classical

IBM Spectrum Copy Data Management – Infrastructure view

© Copyright IBM Corporation 2018 16

IBM Spectrum CDM

LEVE

RAG

E

Use Cases Your IBM Infrastructure

Protection and Disaster Recovery

Automate Dev-Test

DevOps: Infrastructure as Code

Leverage Hybrid Cloud Compute

Automated CopyManagement by SLA

• Cloud integrated• DevOps enabledTransform

Catalog • Discover• Search

Automate • SLA compliance• Policy-based

IBM FlashSystem A9000IBM FlashSystem V9000

IBM Storwize FamilyVersaStack


IBM Spectrum CDM

LEVE

RAG

E

Use Cases Your IBM Apps

Protection and Disaster Recovery

Automate Dev-Test

DevOps: Infrastructure as Code

Leverage Hybrid Cloud Compute

Automated CopyManagement by SLA

• Cloud integrated• DevOps enabledTransform

Catalog • Discover• Search

Automate • SLA compliance• Policy-based

Your IBM Infrastructure

IBM: A9000, V9000SVC, StorwizeVersaStackEMC VNX, UnityNetAPPPureStorage

IBM Spectrum Copy Data Management – Application view

Generic Database Workflow Management


QUIEISCE DATABASE(S)Low impact

1

3

2

SPACE-EFFICIENT ARRAY SNAPSHOTS

1,000s with zero overhead

SPACE-EFFICIENT REMOTE REPLICATION W SNAPSHOTS

Replication with low RPO

INSTANT RECOVERY ANYWHERE

Instant Access with low RTO

4

AUTOMATION VIA POLICYSelf-service, variable retention

5

API

API

Instant Clones

GlobalMirrorChange Volumes



Selected IBM SAP HANA References and examples usingIBM Enterprise POWER technology

In case of interest to contact mentioned on other Power HANA customers, contacts to be provided by IBM sales team per request.

Italian US-americanAutomotive CompanyPower Enterprise Server E880

Power Enterprise Server E850

Technische UniversitätMünchen

Power ScaleOut Server S822 for HANA

Power ScaleOut Server S824Reno Youtube Video:

http://ibm.biz/HRHoPRefVideo

USPower Enterprise Server E870

Argentina Power Enterprise Server E870


German Automotive CompanyPower Enterprise Server E880

Power Enterprise Server E870 (BW)

Power Enterprise Server E880 (CAR, BW, CRM)

United Breweries Ltd IndiaPower ScaleOut Server S824

Australia Power Server

Bosch Youtube Video: http://ibm.biz/BoschHoPRefVideo

Foodstuffs NZ

US Pharma Company Power Enterprise Server E880

MSPs / IT Service Providers

Power Enterprise Server E880 and E870

COOP Youtube Video: http://ibm.biz/COOPHoPVideo201705

Chuangmei Medicine, China, Pharmaceutical

PT. Diamond Cold Storage, Indonesia, Consumer Products

Pakistan, Automotive<

South Shore Furniture, Canada

CSN (Companhia Siderurgica Nacional), Brazil

YPE (Química Amparo)

Brazil


Power Enterprise Server E850C




Power Enterprise Server E880C

19

E880CE850CS824

Danish DefencePower Enterprise Server

E880C



Freudenberg IT (FIT) – IT Serviceprovider / MSP:

HANA on POWER Flexibilität = „HANAFlex“ „wie am Fliessband installiert“ ...

„HANA on Power a la Cloud“ für den Mittelstand

Adolf Würth GmbH:

x86 HANA Scale Out Lösung migriert mit Backup / Restorenach HANA on POWER als Scale Upzusätzlich Migration HANA 1.0 nach HANA 2.0alles in einem Rutsch und ohne RISIKO

20

Kundenbeispiele



Freudenberg IT – HANA on POWER Flexibilität = „HANAFlex“ „wie am Fliessband installiert“ ...

21

Freudenberg IT – HANA on POWER Flexibilität



22




23




24


Memory in TB

12 TB(3 CECs)

8 TB(2 CECs)

4 TB(1 CEC)



25




26




WÜRTH: EINE starke FAMILIE

27

WELTMARKTFÜHRERim Handel mit Montage- und Befestigungsmaterial71.391 Mitarbeiterinnen/Mitarbeiter weltweit Motor unseres Erfolgs: DIREKTVERTRIEBrund 31.500 Außendienstmitarbeiter kontaktieren jeden Tag 300.000 Kunden

Produkte umfasst unser Kernsortiment125.000Jahresumsatz 201611,8 Mrd. EUR

Über 400 selbstständige Einzelgesellschaftenin mehr als 80 Ländern

27

Würth – Migration x86 HANA nach HANA on POWER



SAP HANA Historie bei der Adolf Würth GmbH

• Dezember 2013: Würth entscheidet seine SAP BW Landschaft auf SAP HANA 1.0 zu migrieren• SAP HANA DB Größe: 3,5 TB (scale out) für Produktion SAP BW System• HA-Szenario mit Standby Node war gewünscht / keine DR Lösung notwendig• 2 System Landschaft (Development und Produktion)• Applikationserver und CI bleiben weiterhin auf der IBM Power (AIX) Platform• IBM gewann die SAP HANA Ausschreibung gegen HP mit der IBM SAP HANA Appliance• Implementierung im January / February 2014 durchgeführt (IBM und IBM BP SVA)• SAP BW 7.4 powered by SAP HANA 1.0 und SLES4SAP 11 SP4• Dezember 2016 SAP CRM on HANA mit IBM Power Systems (HANA 1.0 with SLES11 SP4 (BE))

28




Initiale Situation vor der HoP Migration

GPFS-Filesystem

Indexserver 1

HANA Node 1

Indexserver 2

HANA Node 2

Indexserver 3

HANA Node 3

Indexserver 4

HANA Node 4

Indexserver 5

HANA Node 5

Indexserver 6

HANA Node 6

Indexserver n

HANA Standby

SAP HANA Produktivumgebung

IBM x3950 X5, 8 Sockets (80 Cores), 1 TB RAM

• Produktives HANA Cluster wuchs zu einem 6+1 Node Cluster, Dev. System Cluster blieb 4+1• Kein Support für “Blue” und “Red” SAP HANA Knoten in einem Cluster• Kauf von “used” IBM SAP HANA Appliance Knoten im November 2015• Leasingende der SAP HANA Appliance Infrastruktur im February 2017• Power8 Refresh im Juni 2016 (2x E880 + 16x E870 (Deutschland), 1x E880 + 2x E870 (Schweiz)

29




SAP Heterogeneous System Copy

SAP HANA 2.0 x86

Little Endian

Any Database

LE / BE

SAP HANA 1.0 POWER Big Endian

SAP HANA 2

Linux on

SAP NetWeaver(supported apps: 2460699)

Target EnvironmentSource Environment

Migration Methods

Export/Import (ASCII)

“HANAtize” code

Little Endian

SAP HANA 1.0 x86

Little Endian

NetWeaver based systems only

SAP HANA Migration Tool

Backup/Restore

HANA System Replication

Preferred (fastest and most completemethods if appropriate) and if possible!

Transition / Migration Methoden für SAP HANA 2.0 LE auf IBM POWER

30



31

SAP HANA 2.0: Easy Migration from x86 to IBM Power

New Installation on IBM POWER withSLES4SAP 12 and SAP HANA 2.0

Existing x86 HANA Installation withA) SLES11 SP4 SPS10+ and HANA 1.0

orB) SLES 12 and SAP HANA 2.0

SAP HANA 1.0 SPS10+

SAP HANA 2.0SLES4SAP

11SP4SLES4SAP 12

SAP NetWeaver 7.5 / 7.51

x86

Backup / Restore(HANA 1.0 SPS10+

/ HANA 2.0) or

SAP HANA System Replication(HANA 2.0)

No Endian Conversion

SAP HANA 2.0

SLES4SAP 12

SAP NetWeaver 7.5 / 7.51

IBM POWER



SAP HANA auf IBM Power Systems Lösung Übersicht

Indexserver

HANA Prod

EMC VMax

Indexserver

HANA Dev

App Server

App Server

Indexserver

HANA Prod

Indexserver

HANA Dev

App Server

App Server

SAP HANA System Replication

PowerHA

IBM E880, 8 CPUs (96 Cores), 16 TB RAM

EMC VMax

32




Gemessene Laufzeiten bei den verschiedenen Migrationsoptionen

• Heterogene Migration• Export der Datenbank: ungefähr 9 Stunden• Datenbank Import: ca. 12 Stunden

• Backup und Restore• Backup: ungefähr 4 Stunden• Restore: ca. 5 Stunden• Reduktion der Anzahl der Indexservers: ungefähr 3-4 Stunden (online, nach Migration)

33




Zusammenfassung / ErgebnisseMigration von SAP HANA Systeme von Intel nach IBM Power mit derBackup / Restore Option oder mit SAP HANA System Replication bedeutet:

kein zusätzlicher

Optimierungsaufwandkürzere Migrationen / Laufzeiten

Einfachheit der Lösung

(SO to SU)

Risiko

Minimierungweniger Downtime

34




SAP / IBM Referenz Video auf Youtube

https://www.youtube.com/watch?v=1mza951g6to36




37



38

Carsten DieterleLeading SOLAR(SAP Infrastructure SOLution ARchitect)

IBM Deutschland GmbH IBM-Allee 171139 EhningenGermany

Phone/Mobile +49 7034 274 [email protected]

Member of the IBM Technical Expert Council (TEC)

update zu sap hana auf ibm power systemen · sap hana 1.0 sps10+ sap hana 2.0 sles4sap 11sp4...

Documents