automating sap hana system replication

Use this title slide only with an image

SAP FORUM İSTANBULDiscover SimpleAutomating SAP HANA System ReplicationSpeaker’s Name : Dirk OppenkowskiDepartment : SAP Alliance Director, SUSE

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2Internal

Agenda

Introduction

SAP HANA System Replication Overview

SAP HANA HA/DR scenarios

Q & A


Introduction


SUSE Linux Enterprise + SAP HANA

SAP HANA was developed on SUSE

7,000+ SAP HANA customers on SUSE

SAP HANA Enterprise Cloud runs on SUSE

SAP IT runs SAP HANA on SUSE

17 out of 17 SAP HANA benchmarks on SUSE


SUSE Linux: Technology Leadership

SAP uses SUSE Linux as development platform for UNIX/LINUX

Co-developed Netweaver 7.30 Cluster certification

#1 provider for SAP HANA Scale-up HA/DR

Currently in Ramp-up for SAP HANA Scale-out HA/DR

20,000+ SAP customers rely on SUSE Linux


SAP HANA System Replication Overview


SAP HANA Business Continutity

HW SAP

Business Continuity

HA per Datacenter

Disaster recovery between Datacenter

SAP HANA Host Auto Failover

(scale out with standby)

SAP HANA System Replication SAP HANA System Replication

SAP HANA Storage Replication

SAP

HW

SAP


Automate SAP HANA System Replication

SAP HANA SystemReplication

“sr_takeover” is a Manual process



SUSE High Availability Solution

Automates the“sr_takeover”




Service Level Agreement

improves


SUSE High Availability Solution


Reliable, Scalable and Secure Operating SystemSUSE Linux Enterprise Server

High AvailabilitySAP Netweaver & SAP HANA

Faster InstallationSAP Installation Wizard

Page Cache Management

AntivirusClamAV

Specific Update Channel

24x7 PRIORITY SUPPORT for SAP

24x7 PRIORITY SUPPORT for SAP

PRIO

RIT

Y SU

PPO

RT

for S

AP

PRIO

RIT

Y SU

PPO

RT

for S

AP

18 Month Grace PeriodLong-Term Service Pack Support

Simplify Linux for SAP WorkloadsSUSE Linux Enterprise Server for SAP Applications 11


SAP HANA System ReplicationPowered by SUSE High Availability Solution

resource failover

active / active

node 1 node 2

N M

A B

N M

A B

HANADatabase

HANAmemory-preload

A B

SystemReplication

HANA PR1primary

HANA PR1secondary

Performance optimized Secondary system completely used for the preparation of a possible take-over Resources used for data pre-load on Secondary Take-overs and Performance Ramp shortened maximally


From Concept to ImplementationSUSE High Availability Solution for SAP HANA

SAP HANAPrimary

SAP HANASecondary

vIP

SAPHana Master/Slave ResourceMaster Slave

SAPHanaTopology Clone ResourceClone Clone

suse01 suse02

Cluster Communication

Fencing


SAP HANA HA/DR scenarios


Allowed Scenarios

• Scale-Up performance-optimized - syncron (=>)A => B

• Scale-Up in a chain or multi tier - asyncron (->)A => B -> C

• Scale-Up in a cost-optimized scenario (+)A => B + Q

• Scale Up in a mixed scenario A => B -> C + Q

• Now all with multi tenancy (%) - here cost optimized%A => %B + %Q


Performance-OptimizedSingle-tier System Replication and memory preload

Pacemaker

System Replication

node 1 node 2

SAP HANAPR1 primary

SAP HANAPR1 secondary

SystemPR1

vIP

SystemPR1

Performance optimized (A → B)

Secondary system completely used for the preparation of a possible take-over Resources used for data pre-load on SecondaryTake-over performance much faster than a cold start


Cost-OptimizedSingle-tier System Replication and DEV / QAS

SystemPR1

SystemDEV

Cost optimized (A → B + Q)

Operating non-prod systems on SecondaryDuring take-over the non-prod operation has to be endedTake-over performance similar to cold start-upNeeds another disk stack for non-prod usage load

Pacemaker

System Replication

node 1 node 2

SAP HANAPR1 primary

SAP HANADEV / PR1 secondary

SystemPR1

vIP


starting with version 0.149 Multi Tier System Replication – Cascading Systems

Datacenter Datacenter

asyncsync

Production Local standbywith data preload

Remote standby systemwith or without preload(mixed usage with non-prod.)

Available since SAP HANA SPS7

(Three cascading systems)


Multi-tier System ReplicationChain Topology ( A → B → C )

asyncsync

ClusterP S

A B C

Default Setup - Chain

Cluster

async

P

A B C

only async now



asyncsync

ClusterPS

A B C

asyncsync

ClusterP S

A B C


Cluster

async

P

A B C

only async now



asyncsync

ClusterPS

A B C

asyncsync

ClusterP S

A B C


Cluster

async

P

A B C

only async now

Not allowed from SAP This would be a star


async

ClusterP

A B C

Only async



async

ClusterP

A B C

ADMIN:Break Replication complete

async

ClusterP

A B C

Only async



asyncsync

PS

A B

C Again a chain

async

ClusterP

A B C

ADMIN:Break Replication complete

async

ClusterP

A B C

Only async

starting with version 0.149 Multi-tier System ReplicationChain Topology ( A → B → C )

ADMIN:Create new SystemReplication


SUSE SAPHanaSR in 3 Facts

Reduces complexity- provides a wizard for easy configuration with just SID, instance number and IP address- automates the sr-takeover and IP failover ("bind")

Reduces risk- includes always a consistent picture of the SAP HANA topology- provides a choice for automatic registrations and site takeover preference

Increases reliability- provides short takeover times in special for table preload scenarios- includes the monitoring of the system replication status to increase data consistency


Outlook: HANA in a SUSE Linux Enterprise High Availability Extension ClusterHANA Multi Node – System Replication / Scale-OUT

SUSE is still scoping and researching this cluster concept.

site 1 site 2

N M

A B

N M

A B

HANADatabase

HANAmemory-preloadA B

SystemReplication

HANA PR1primary

HANA PR1syncmem

resource failover active / active


Q & A