SAP HANA @ Evonika248.g.akamai.net/n/248/420835/c5ddde3acb66ac7547168012e... · 2016. 12. 22. · November 2016 | SAP TechEd Barcelona SAP LVM and PCA Formerly customer-individual

1

SAP HANA @ Evonik

SAP TechEd Barcelona

November 2016

Sabine Sperzel

Christian Braukmüller

SAP HANA powered by

SAP Landscape Management

2

Sabine SperzelEvonik Industries AG

Team Lead – Special SAP Basis

[email protected]

German User Group (DSAG)

Speaker: Infrastructure & Operations

November 2016 | SAP TechEd Barcelona

Contacts

Twitter: @CBasis SAP Mentor

Christian BraukmüllerIndependent SAP Technology Consultant

[email protected]

3

Agenda

Introduction Evonik

SAP HANA – Project Challenges

Evolution SAP Platform @ Evonik

System Architecture – Keep it Simple

Power of SAP Landscape Management

Outcomes

November 2016 | SAPTechEd Barcelona

4

Introduction Evonik


5 November 2016 | SAP TechEd Barcelona

Evonik in Figures (2015)

Employees (as of December 31, 2015)

33,57618.2 %Profitability (adjusted EBITDA margin)

€2.465 billion Adjusted

EBITDA Return on Capital

Employed (ROCE)

16.6 %

€13.5 billionsales

www.evonik.com

http://corporate.evonik.com/_layouts/Websites/Internet/DownloadCenterFileHandler.ashx?fileid=375


Global SAP Basis Team:“Follow the Sun”

7

BW

SLD

ADS

ERP


SAP System Landscapes @ Evonik

ERP

APO

BW

(HR)

Sol

Man

Portal

CRM

EH&S

GTS

PI

ERP

CPH

GRC

LVM

TM

HRCPS

EWM

Others

History

PPMSEM

Testlab

~ 30 Landscapes

130+ Systems

900+ Instances

200+ Hosts

Prod

QA

DEV

(Sandbox)


Why Migrate all SAP Systems to SAP HANA?

Innovation

9

SAP HANA – Project Challenges



Migration Planning for SAP HANA:Requires an agile roadmap to cover all streams

Roadmap ErstellungFreigabe/Review

Roadmap Implementation

Customer Projects

IT Internal Projects

ERP Consolidation

Project

History Projects

Syncing

with project

“Data Center

2016”

Upgrade Planning

Evonik rule:

every two years

11

Evolution SAP Platform @ Evonik



SAP platform was transformed to a flexible private cloud

Evolution of the SAP Platform @ EvonikPart 1 – from AIX to a Linux-only approach

Once upon a time

• AIX/Tru64based on ORACLE

2010

• Moving application server to physical hosts (SLES Linux)

2013 - 2014

• Main SAP BW landscape migrated toSAP HANA appliancewith scale out and system replication

Yes, SAP HANAbut on TDI

• No TDI available at that time[Tailored Datacenter Integration = (re)use your components]

• Learning curve for infrastructure and initial setup

• Stability phase reached

• Significant performance improvements

• High user acceptance

13

2015 2015 2016 2016 - 2018


Evolution of the SAP Platform @ EvonikPart 2 – Virtualization & In-memory

Once upon a time

• AIX/Tru64based on ORACLE

2010

• Moving application server to physical hosts (SLES Linux)

2013 - 2014

• Main SAP BW landscape migrated toSAP HANA appliancewith scale out and system replication

14

2015

•SAP Application

Cloud

Moving application server to dedicated VMs (SLES Linux)

2015 2016 2016 - 2018



15

2015

•SAP Application

Cloud


2015

•First Migrations

SAP HANA migration of 3 landscapes to TDI

2016 2016 - 2018



• Strategic decision to migrate all databases

• Keep on following the x86 decision

• Simplify the infrastructure stack

• Start with SAP HANA migration for 3 landscapes

• Adapt internal processing and operations

16

2015

•SAP Application

Cloud


2015

•First Migrations


2016

•All new installations on SAP HANA

&more migration projects on TDI

2016 - 2018



• All new landscapes directly on TDI

• Planning a new data center infrastructure (independent decision)

• Evaluating hardware partner and storage provider solution for adaptiveness

17

2015

•SAP Application

Cloud


2015

•First Migrations


2016

•All new installations on SAP HANA

&more migration projects on TDI

2016 - 2018

•New TDI Platform

New Data Center

Full Migration to SAP HANA



Sizing of a DC with two locations: with distributed load

High Availability in one location

DR scenario to other side

Setting up migration plan for all dependencies, such as: Upgrade projects / SAP product availability

Application projects

Migration path options

18

System Architecture

– Keep it Simple


19

VMware - vSphere


Keep it as simple as possible

Efficient use of HW capacity

Expect that current limits today may

not be relevant in near future;

e.g., VMware memory limits and

SAP restrictions (scale out, multi-VM, one server)

Separate SAP systems in dedicated VMs

Enable High Availability via VMware

System Architecture Based on VMware and TDI

VM

VMware HA

Central Services

Appl. Server

SAP HANA

SUSE

Web Dispatcher

20

Power of

SAP Landscape Management



SAP LVM = SAP Java application (based on SAP NW Java)

Operations for multiple SAP systems using APIs

Basic operations (start/stop/relocate)

Extended operations (system copy/refresh/provisioning)

Functionality depends on license model

Standard (start/stop/relocate/custom operations)

Enterprise (all others; e.g., provisioning, post-copy automation)

All releases are/were in use @ Evonik

SAP Adaptive Computing Controller (SAP ACC)

SAP Landscape Virtualization Manager (SAP LVM 1.0 - 2.1) (current)

SAP Landscape Management (SAP LaMa 3.0)

(guided beta and ramp up)

SAP Landscape “Virtualization” Management

SAP NW JAVA

SAP LVM

Central Services

Appl. Server

SAP HANA

OS

Web Dispatcher

Host Agent

API

SAP Solution Manager

RFC

Storage DNS ADvSphere

API /Adapter

23

VMware - vSphere


All virtual hosts are provisioned Linux VMs:

based on template

no SID-specific parts at startup

SAP Landscape Management (LVM/LaMa)

triggers these steps for each instance

(= “Prepare process”)

Binding… IPs (for virtual hostname)

Attaching… Volumes (for block storage)

Mounting… File systems

(/sapmnt/<SID>, /usr/sap/<SID>, /hana/data/SID,…)

Starting… Instance Agent (sapstartsrv)

Adaptive Installation @ Evonik | Explained

VM

VMware HA

Central Services

Appl. Server

SAP HANA

SUSE

Web Dispatcher

Host Agent

LVM

LaMa

24

VMware - vSphere


Relocation of the instances consists of

Stopping instances

Unpreparing

Preparing (on a different host)

(can be either a physical host or virtual VM)

Examples of benefits for operations:

Target VMs can be prepared; e.g., 50 VMs with SLES12

Mass relocation can be scheduled for the weekend

Backout plan in case of issues => relocate back

Adaptive Installation:Showing a Relocate

VM

VMware HA

SUSE

Web Dispatcher

Appl. Server

Central Services

SAP HANA

Host Agent

LVM

LaMa

SUSE

Web Dispatcher

Appl. Server

Central Services

SAP HANA

Host Agent

25

SAP LVM Capabilities in Use @ Evonik



Examples:

Custom Operation: Kernel Patch Web Dispatcher

Custom Hooks: SAPINST (System Refresh)

Custom Instance/Service: SAP Sybase IQ / NLS and Wily

plus:

Custom Validation: Hostagent Configuration (PSE)

Examples of Custom Implementations by Evonik

27

VMware HA

VM

SUSE

Host Agent


High-Availability realized by VMWare + „LVM Autostart“

Issue:

A VM in an adaptive installation starts without mounting filesystems or

binding IPs automaticaly.

An automatic start of an SAP system is therefore not possible.

Solution:

„LVM Autostart“ was realized as customer implementation

We store the last LVM-triggered operation via Hostagent-Hooks

Each Prepare&Start and Stop&Unprepare is registered in a

statusfile

At start of a VM the last status of applications inside a VM is

re-established

via Autostart scripts

replaying the last operations based on the statusfiles

Custom Development for HA Szenario

Central Services

Appl. Server

SAP HANA

Web Dispatcher

LVM

LaMa

Folder:

<hostname>

statusfile

statusfile

statusfile

statusfile

hook

hook

hook

hook

No manual efforts

24/7 automation

Very fast!


Mass operations during maintenance weekends are possible in an efficient and transparent way

Operation logs with details:

What happened when, triggered by whom & took how long?

System status and changes can be attached as a note

URLs to a specific SID for quick LVM access (SAPNote #1646198)

Custom operations / validations / services / links

linked to internal wiki and documentation

Some of Many Benefits for Our Operational Teams

https://launchpad.support.sap.com/#/notes/1646198/E

30

0 3 6 9 12 15 18


SAP LVM and PCA

Formerly customer-individual procedures

now controlled and logged by an SAP standard

framework (LVM + PCA)

transparently handled over several time zones –

consistent status view and clear handover

Standardization of the system refresh (DB-refresh) for

different SAP usage types

Customer tables are handled now via R3trans

(before: Oracle EXP/IMP) triggered by LVM hooks

=> Database-independent procedure ready for HANA

Improved System Refresh Handled by SAP LVM

Optimized

handover

Singapore

Frankfurt

System Refresh


Project Outcomes

32

Outcomes

SAP LVM integration:

Validate or choose your infrastructure to get the best out of the full SAP LVM functionality.

1

Keep it simple:

The adaptive installation of all SAP applications is a key factor in running a highly automatable data

center.

2

Restrictions:

SAP Note for the SAP HANA Data Center Service Point Revision (#2021789).

Schedule two SAP HANA upgrades a year.

Keep the VMware limits in mind with regard to the sockets and productive SAP HANA installations.

3

Migration OrganizationInfrastructure & Architecture

https://launchpad.support.sap.com/#/notes/2021789/E

33

Outcomes

Technical migration:

To ensure a technical migration without any critical problems, recommendation: include SAP services

for the first DMO migrations.

No DMO operation for Java systems: clarify how the data can be migrated (e.g., export/import).

1

Application:

Check the SAP HANA readiness of your add-ons and releases.

SAP HANA custom code checks can be done at an early stage.

2


34

Outcomes

Infrastructure changes:

Be aware that the new architecture of your stack might run best with a restructured OS/DB/SAP-team

organization: Clarify responsibility for the SAP HANA platform.

Cooperation with the infrastructure teams (VMWare, etc.) will be more intensive.

Authorization concept is needed for the SAP HANA platform.

1

Knowledge:

You need SAP HANA certified employees for the SAP HANA installation and migration.

Development team must be prepared for custom code management for SAP HANA adjustments and

new development.

2


35

Sabine SperzelEvonik Industries AG

Team Lead – Special SAP Basis

[email protected]

German User Group (DSAG)

Speaker: Infrastructure & Operations


Contacts

Twitter: @CBasis SAP Mentor

Christian BraukmüllerIndependent SAP Technology Consultant

[email protected]

Documents

SAP HANA @ Evonika248.g.akamai.net/n/248/420835/c5ddde3acb66ac7547168012e... · 2016. 12. 22. · November 2016 | SAP TechEd Barcelona SAP LVM and PCA Formerly customer-individual