SAP HANA System Replication simplified

SAP HANA SystemreplicationSimplified

Peter Schinagl

[email protected]

Senior Technical Architect

SUSE SAP Global Alliance

2

Simplify Linux for SAPSUSE Linux Enterprise Server for SAP Applications

Page Cache Management

Antivirus ClamAV

Extended Service Pack Support18 Month Grace Period

Faster InstallationSAP Installation Wizard

High AvailabilitySAP HANA & SAP NetWeaver

Reliable, Scalable, and Secure Operating SystemSUSE Linux Enterprise Server

SAP specific update channel

24x7 Priority Support for SAP

24x7 Priority Support for SAP

Automate SAP HANA System Replication

4

SAP HANA Scenarios

Source: SAP HANA in Data Centers

HWSAP

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

5

Automate SAP HANA System Replication

Service Level Agreement

SAP HANA SystemReplication

SUSE High Availability Solution

6

SAP HANA System ReplicationPowered by SUSE High Availability Solution

resource failover

node 1 node 2

HANADatabase

HANAmemory-preloadmemory-preload

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

N M

A B

N M

A B

A B

7

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

8

Four Steps to Install and Configure

Install SAP HANA

Configure SAP HANA System Replication

Install and initialize SUSE Cluster

Configure SR Automation using HAWK wizard

9

Allowed Scenarios (initial version)

Two-node clusters

Scale-up (single-box to single-box) HANA system replication

Only Single-tier System Replication ( A → B )no multi-tier

no other SAP HANA system (like DEV, TST, QAS) on the replicating node that needs to be stopped during takeover

Both physical and “virtual” SAP host names

10

Requirements

Both SAP HANA instances have the same SAP Identifier (SID) and Instance Number

Both cluster nodes in-time sync (ntp)

Both nodes are in the same network segment (layer2)

Technical users and host names resolved locally

Distance / Latencies

11

SAPHanaSR HAWK Wizard

Technical preview included in the shipping.

12

SAPHanaSR in HAWK

13

What is the Delivery?SUSE Linux Enterprise Server for SAP Applications

The package SAPHanaSR the two resource agents

SAPHanaTopologySAPHana

HAWK setup Wizard (as technical preview)

The package SAPHanaSR-docthe important SetupGuide

New Use Cases

15

starting with version 0.149

Single-tier System Replication and DEV / QAS( A → [B] + DEV )

Pacemaker

System Replication

node 1 node 2

SAP HANAPR1primary

SAP HANADEV / PR1 secondary

SystemPR1

vIP

SystemPR1

SystemDEV

Cost optimizedOperating non-prod systems on SecondaryResources freed (no data pre-load) to be offered to one or more non-prod installationsDuring 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

Requirements

Needs to be implemented as a project, because this is not a simple pre-build solution.

HW Partner needed because of different HANA systems (disks and general sizing)

Fencing is HW specific

Cluster-rules needs to be adopted to the customer specific implementation

17


Multi Tier System Replication – Cascading Systems

Datacenter Datacenter

asyncronsyncron

Production Local standbywith data preload

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

Available since SAP HANA SPS7

(Three cascading systems)

Requirements

Needs to be implemented as a project, because this is not a simple pre-build solution.

Side C is not in the cluster, therefore the administrator need to do many tasks manually after an switchover.

19


Multi-tier System Replication (cascading systems)Chain Topology ( A → B → C )

asyncsync

ClusterPP S

A B C

Default Setup - ChainChain

20



asyncsync

ClusterPP S

A B C


Cluster

async

PP

A B C

only async now

21



asyncsync

ClusterPPS

A B C

asyncsync

ClusterPP S

A B C


Cluster

async

PP

A B C

only async now

22



asyncsync

ClusterPPS

A B C

asyncsync

ClusterPP S

A B C


Cluster

async

PP

A B C

only async now

Not allowed from SAPNot allowed from SAP This would be a starstar

23

async

ClusterPP

A B C

Only async


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

24

async

ClusterPP

A B C

ADMIN:Break Replication complete

async

ClusterPP

A B C

Only async



25

asyncsync

PPS

A B

C Again a chain

async

ClusterPP

A B C

ADMIN:Break Replication complete

async

ClusterPP

A B C

Only async



ADMIN:Create new SystemReplication

26

Our Community

Developed jointly in the SAP Linux Lab in Walldorf

Integration of the solution in partner products

Upstream open-source project

Scoping, discussing and implementing Scale-Out

You are invited to joinour community :-)

Visit our booth or contact us via

[email protected] or [email protected]

27

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

28

More Informationhttp://www.suse.com/products/sles-for-sap

Thank you.

29

Visit us online to learn more about the SUSE and SAP partnership at

http://www.suse.com/saphttp://www.suse.com/products/sles-for-sap

http://www.suse.com/sap

http://www.suse.com/products/sles-for-sap

Corporate HeadquartersMaxfeldstrasse 590409 NurembergGermany

+49 911 740 53 0 (Worldwide)www.suse.com

Join us on:www.opensuse.org

30

http://www.opensuse.org/

Unpublished Work of SUSE LLC. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE LLC. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

Software

SAP HANA System Replication simplified