Public SAP HANA Platform boosts customer's digital innovations Forum B… · SAP HANA Platform...

Lou Theunissen, HANA Business Development, SAP Suisse SA

9 March 2016

SAP HANA Platform boosts customer's

digital innovations

Public

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2Public

The size of my ERP Production Data is:

A. > 2,5 TB on AnyDB (ABAP Size Uncompressed)

B. < 2,5 TB on AnyDB (ABAP Size Uncompressed)

C. > 830 GB on HANA

D. < 830 GB on HANA

E. Don’t know

Agenda Current

Session Polls

(Befragung)

Results

https://gameday.doubledutch.me/?sessionToken=aca046b7-3524-4faa-b743-75b61992143a&mod=polls&pollId=49251


Disclaimer

This presentation is not subject to your license agreement or any other service or subscription

agreement with SAP. SAP has no obligation to pursue any course of business outlined in this

document or any related presentation, or to develop or release any functionality mentioned therein.

This document, or any related presentation and SAP's strategy and possible future developments,

products and or platforms directions and functionality are all subject to change and may be changed by

SAP at any time for any reason without notice. The information in this document is not a commitment,

promise or legal obligation to deliver any material, code or functionality. This document is provided

without a warranty of any kind, either express or implied, including but not limited to, the implied

warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for

informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for

errors or omissions in this document, except if such damages were caused by SAP intentionally or

grossly negligent.

All forward-looking statements are subject to various risks and uncertainties that could cause actual

results to differ materially from expectations. Readers are cautioned not to place undue reliance on

these forward-looking statements, which speak only as of their dates, and they should not be relied

upon in making purchasing decisions.


Business Case:

• Customer has ERP, CRM and BW

• Never archived

• Never lean copies

• Starts with HANA

• Starts collecting Sensor Data

• Archiving or not?

• System copies or not?


Agenda

• SAP HANA Platform without Data Temperature Management

• SAP HANA Platform with Data Temperature Management

• Keep TCO low during Digital Transformation

SAP HANA Platform without

Data Temperature Management


Current SAP Landscape

Starting Points:

• Non-Production Clients are copies of PRD

• RPO = RTO 15 Minutes

• PRD Data is not preloaded into PRD’

• Distance Datacenters: 8 KM

ERP

PRD

ERP

QAS

ERP

DEV

ERP

SBX1 ERP

SBX2 ERP

SBX3 ERP

SBX4

CRM

PRD

CRM

QAS

CRM

DEV

CRM

SBX

BW

PRD

BW

QAS

BW

DEV

BW

SBX

Current HANA Note

BW 1,3 TB + 250 GB PY 614 GB 1736976

ERP 2,3 TB + 0 GB PY 832 GB 1872170

CRM 140 GB + 0 GB PY 100 GB 1872170

RPO = Recovery Point Objective (Worst Case Data Loss)

RTO = Recovery Time Objective (Time to Recover from Outage)


Data Center 2Data Center 1

Future Landscape without Data Temperature Management

HW-Investment:

~CHF 660.000

HANA1: 768 GBBW: PRD

HANA2: 768 TBBW: PRD’ & QAS

HANA4: 1,5 TBERP: PRD

CRM: PRD

HANA5: 1,5 TBERP: PRD’& QAS

CRM: PRD’ & QAS

MDC = Multitenant Database Containers

HANA3: 1,5 TBBW: DEV & SBX

HANA6: 6,0 TBERP: DEV & SBX1234

CRM: DEV & SBX

SAP HANA Platform with

Data Temperature Management


Data Temperature Plan

With Data Temperature Management

• Real-Time Analytics Period: 3 years

• Residence Period: 3 years after closing

• Retention Period: 10 years after closing

• Age of oldest records: 10 closed years

• QAS: Exact copy of PRD

• TST, DEV, SBX: 50% of PRD

0 5 1141 2 3 6 987 10

Open Closed Closed Closed

Current Data Historic Data

RT Analytics Period

ERP:

Retention Period

Open Closed Closed Archived

BW:

Residence Period

ColdHot

Frozen

Warm


BW on

HANA

PRD

BW on

old DB

PRD

QAS

DEV

Step 1: Migrate BW to HANA

QAS

DEV

SBX

DEV

SBX

DEV

SBX


Step 2: Activate NLS

ERP on

old DB

PRD

SAP IQ for

NLSPSA = Persistence Staging Area

Any BW-objects

BW on

HANA

PRD

Cold

Hot65% (7/11) can be

offloaded from

memory to NLS


Step 3: Activate Dynamic Tiering

ERP on

old DB

PRD

SAP IQ for

NLS

DT = Dynamic Tiering

wo-DSO = Write-Optimized Data Store Object

PSA = Persistence Staging Area

BW on

HANA

PRDDT Node for

wo-DSOs and PSAs

New: Extended

Server Service for

Dynamic Tiering

Warm

Cold

HotEstimation: 10% can

be offloaded from

memory to DT Node


Result for BW

Data Temperature Plan for BW

0 5 1141 2 3 6 987 10

Open Closed Closed Closed


In Memory

(Hot): 154 GB

Near Line Storage

(Cold): 400 GB

BW:

Dynamic Tiering

(Warm): 60 GBWithout Data

Aging: 614 GB


Step 4: Create Lean ERP Production SystemSAP ILM Retention Management & Data Archiving

ERP on

old DB

PRD

SAP IQ with

ILM Store ILM = Information Lifecycle Management

ADK = Archive Development Kit

Archiving

historical data

in ADK-Files

New

65% (7/11) can

be archived

Frozen


DEV

Step 5: Create Lean & Consistent Non-Production SystemsSAP TDMS / SAP LVM

ERP on

old DB

PRD

QAS

TDMS = Test Data Migration Server

LVM = Landscape Virtualization Manager

Size of DEV and

SBX 50% of PRD

SBX


DEV

Step 6: Migrate CRM to HANA & ERP to S/4HANASQL Monitor / CCLM / DMO of SUM

ERP on

old DB

PRD

QAS

SBX

S/4HANA

PRD

QAS

CCLM = Custom Code Lifecycle Management

DMO = Database Migration Option

SUM = Software Update Manager

DEV

SBX


Step 7: Go-Live

ERP on

old DB

PRD

SAP IQ with

ILM StoreILM = Information Lifecycle Management

S/4HANA

PRD

Hot

Frozen


Step 8: Facilitate Easy Access to Archived Data & DocumentsDefault: ILM Store. Optional: SAP Document Access by OpenText

SAP IQ with

ILM Store

S/4HANA

PRD

Purchase

Order

Customer Information


Step 9: Activate Data Aging

S/4HANA

PRD

Before After

Historic data

remains on disk

Suite on HANA

NetWeaver 7.40 SPS 12

S/4HANA

R1511

S/4HANA

Future Direction

Application Log FI Documents Purchase Orders

IDocs Unified Journal Entries Sales Orders

Change Documents Material Documents Billing Documents

Workflow LE Delivery Documents

Warm

Hot


Result for ERP

Data Temperature Plan for ERP

0 5 1141 2 3 6 987 10

Open Closed Closed Frozen


In Memory

(Hot): 212 GB

ILM Store

(Frozen): 540 GB

ERP:

Data Aging*

(Warm): 80 GB

* For future release of S/4HANA only.

Without Data

Aging: 832 GB


Data Center 2Data Center 1

Future Landscape with Data Temperature Management

HANA1: 256 GBBW: PRD

HANA2: 256 GBBW: PRD’ & QAS

HANA4: 512 GBERP: PRD

CRM: PRD

HANA5: 512 GBERP: PRD’& QAS

CRM: PRD’ & QAS

MDC = Multitenant Database Containers

HANA3: 256 GBBW: DEV & SBX

HANA6: 1,0 TBERP: DEV & SBX1234

CRM: DEV & SBX

DT1:

60GB

DT2:

120GB

IQ2:

1880GB

IQ1:

940GB

DT3:

60GB

HW-Investment:

~CHF 335.000

Without Data Aging:

~CHF 660.000


Conclusions

Data Temperature Management …

1. Expedites migration to HANA

2. Saves substantial HANA memory

3. Automates the management of (unlimited) data growth

4. Does not affect user satisfaction

5. Is unavoidable during Digital Transformation (see next slides)

Keep TCO low during

Digital Transformation


Step 10: Process & Analyze Mass Structured DataFor example: IoT data

S/4HANA

PRD

SAP IQ


Step 11: Process & Analyze Mass Unstructured DataFor example: Social Media Data

S/4HANA

PRD

SAP HANA

Vora


Big Data can no longer be ignored….

As a society, we create .5 quintillion bytes of data on a daily basis.

That is 25.000.000.000.000.000.000 bytes per day!

As the variety and volume of data grows, more and more

companies are facing increased infrastructure costs,

with less budget available for innovation.

The solution: Data Temperature Management(also known as: Data Tiering)


Data Temperature ManagementData Temperature Management (or Data Tiering, not to be confused with

Dynamic Tiering) is the assignment of data to various tiers/storage media

based upon data type, operational usefulness, performance requirements,

frequency of access and security requirements of the data.

Mass

Data?

Data is

current?

HANA

Memory

Data

Source?

Real-Time

Analytics

needed?

Dynamic

Tiering on

DT Node

NLS on IQ

(BW only)

Suite &

S/4HANA

BW or Data

Mart

Yes

No

Data is

current?

No

Past

Residence

period?

Data Aging

HANA Disk

ILM Store on

IQ

Analytics

needed?

Hadoop with

SDA to

HANA

Hadoop with

HANA Vora

IoT, unstructured,

semi-structured and

streaming data

No

Yes

Yes

Yes

Historic

Yes

No

Real-Time

Analytics

Historic


Summary5 Takeaways

1. Start with Data Temperature Management sooner than later

2. BW: Migrate to HANA, then NLS and/or DT

3. Suite: Set Retention Rules and archive, then migrate to HANA

4. S/4HANA: Use Data Aging to free up memory

5. IOT: Use IQ and Hadoop/Vora to keep TCO low

Thank youContact information:

Lou Theunissen

HANA Business Development

[email protected]

SAP Suisse SA

+41798435983

mailto:[email protected]


Which of the following methods optimizes SAP HANA Platform?

A. Data Tiering: Defining which data belongs in which tier (H/W/C/F)

B. Data Aging: Not loading historic S/4HANA data into memory

C. Dynamic Tiering: Not loading historic BW data into memory

D. Data Archiving: Offloading historic data to ILM Store

E. All

Agenda Current

Session Polls

(Befragung)

Results

https://gameday.doubledutch.me/?sessionToken=aca046b7-3524-4faa-b743-75b61992143a&mod=polls&pollId=49251


Give us your feedback!

Give us your feedback after every session and take the

chance to win a Stand-Up Paddle Board.

Vote now – win at the end of the day!

The Event App can be

downloaded for free at the

following shops:

A direct feedback after the

presentation is important

for every speaker.

Also use the chance and

evaluate the entire event.


© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate

company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its

affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and

services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop

or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future

developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time

for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-

looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place

undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

Attachments


Applications to migrate and optimize SAP HANA Platform

Package Explanation Material #

1 NLS Near-Line Storage for SAP BW, offloads historic BW-data to IQ 7018597

2 DT SAP HANA Dynamic Tiering, prevents historic BW-data from being loaded into memory 7018076-80

3 ILM RM SAP Info Lifecycle Mgmt – Retention Mgmt, sets rules for residence and retention period and steers Data

Archiving.

SAP Info Lifecycle Mgmt – Retention Mgmt SAP IQ, creates ILM Store on IQ

701999-2000

701598

4 ILM Decom Rapid System Decommissioning with SAP ILM: Tool to decommission 20 or more production systems 7018007

5 Data Aging Prevents historic S/4HANA data from being loaded into memory. Part of S/4HANA. Incl.

6 Data Archiving Data Archiving in SAP Netweaver. Tool to create ADK-files and delete records from HANA. Incl.

7 OpenText SAP Document Access by OpenText. Tool to get a full view of archived data and documents 7017978-79

8 TDMS SAP Test Data Migration Server: creates stable sandboxes and development clients while reducing size. 7011533

9 LVM SAP Netweaver Landscape Virtualization Mgmt: Manages SAP and non-Sap servers. Creates SBX in

minutes.

7011511-12

10 DMO Tool EhP Upgrade & Migration to HANA. Part of SUM.

11 SUM Software Upgrade Manager.

12 SQL Monitor Custom Code control tool in SAP Netweaver Incl.

13 CCLM Custom Code Lifecycle Manager in SAP Netweaver Incl.


Do Not Oversize HANA Memory

• With ‘Data Aging’ S/4HANA Database Size will shrink

• With S/4HANA Database Size will shrink (This Sizing Report only calculated ERP on HANA,

therefore not considered)

• With Operational Reporting in S/4HANA BW Database Size will shrink

• All Client Needs have been rounded up to above (For example: Needed for PRD ERP: 332

GB, Reserved for ERP: 512 GB.)

• All PRD Clients have 128 GB Reserve

• Reserved room for TST Clients

• Scaling Up is always possible


Comparison MDC versus VirtualizationHANA Multitenant Database Containers (MDC) versus VMWare 5.5

Feature Virtualization MDC

Throughput for OLTP (See next slide) 398,03 - 634,57 DS/sec 9% - 98% Faster (691,87 – 788,85 DS/sec)

DB Update Request Time (OLAP/OLTP) 83,09 – 94,69 ms 19% - 30% Faster (67,39-66,15 ms)

Memory Size Limitation Max 4 virtual 1TB servers No Limitation

Scale Out Supported No Yes

Strong Isolation Always Optional

Performance Management Black Box View White Box View (DB Level)

Additional License needed Yes No

Operation System version Can be different Same for all containers

System Replication Individual All containers simultaneously

DS = Dialog Steps

OLTP = Online Transaction Processing

OLAP = Online Analytics Processing


Maximum Throughput [Dialog Steps/sec] for OLTP scenario for

different virtualization techniques

Alternative Virtualization MDC


HANA MDC Mixed Loads (OLTP/ OLAP Scenario)

Impact on DB Update Request Time


SAP HANA Multitenant Database Containers (MDC)Options - Horizontal View

SAP HANA Instance

App X App Y

HW

OS

Multiple Components,

one Database (MCOD)

See Notes 1661202 + 1826100

Database

SAP HANA InstanceSAP HANA Instance

DatabaseDatabase

Schema X

App X

Schema Y

App Y

Hypervisor (just for Virtualization)

HW

OS OS

Multiple Components / Instances,

one System (MCOS, Virtualization)

See SAP Note 1788665

SAP HANA Instance

Tenant DBTenant DB

Schema X

App X

Schema Y

App Y

HW

OS

Multi-tenant Database Containers,

one HANA Instance (MDC)

See SAP Note 2096000

Schema X Schema Y

https://service.sap.com/sap/support/notes/1661202

https://service.sap.com/sap/support/notes/1826100

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

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

Public SAP HANA Platform boosts customer's digital innovations Forum B… · SAP HANA Platform...

Documents

Transcript of Public SAP HANA Platform boosts customer's digital innovations Forum B… · SAP HANA Platform...