High Availability and Disaster Recovery for SAP HANA

with SUSE Linux Enterprise Server for SAP

Applications

Uwe Heinz

Fabian Herschel

Product Manager
SAP

Senior Architect SAP LinuxLab

SUSE SAP Global Alliance

Uwe.Heinz@sap.com

Fabian.Herschel@suse.com

Agenda
SAP HANA typical implementations
Outlook for the next 12 18 months
Disaster Recovery Capabilities of SAP HANA
Automate SAP HANA System Replication
SAPHanaSR - Setup and Implementation
SAPHanaSR - Roadmap
Our Community

Introduction & Overview (SAP and LINUX)

15
years
Linux
develpoment
plattform

SAP
Netweaver

SoH and
BWonH

SAP BWA and

SAP HANA

Foundation
of Linuxlab

and growing ...

CeBit
99

1999

2000

2001

2002

2003

2004

2005

SAP supports only :

2014 SAP SE or an SAP affiliate company. All rights reserved.

2006

2007

2008

2009

2010

2011

2012

2013

2014

SLES, RHEL and Oracle Linux

Public

Joined activities
NUMA
optimiz
ation

Gcc
optimization

NFS
local
loopback

Joined
support
> 15
years

SUSE
HA

harde
ning

bench
marks

SLES4SAP

HANA for
Linux on
Power

KVM/
XEN

Teched
Berlin/Las
Vegas

Development

>50
customer
WS

Priority
support
Maintenance

SuseLabs
conference

Events
DSAG/
ASUG

4 Developer
in
SAPLinuxlab

2014 SAP SE or an SAP affiliate company. All rights reserved.

SuseCon

Public

Joined activities

High Availability & Disaster Recovery

Customer

http://www.saphana.com/docs/DOC-2010

High Availability Disaster Recovery

Overview
Business Continuity

High Availability

Disaster recovery

per Data Center

between Data Centers

SAP HANA Host Auto-Failover

(Scale-Out with Standby)

SAP HANA Storage Replication

SAP HANA System Replication

SAP HANA System Replication

Performance Optimized

Performance Optimized

Cost Optimized

Cost Optimized

2014 SAP SE or an SAP affiliate company. All rights reserved.

Public

High Availability Options

1 Scale-Out or Host Auto-Failover

SAP HANA High Availability: Host Auto-Failover

Services
Name and index server on all nodes
Statistics server (only on one active server)
Name server active on Standby

Server 3
Server 4
Server 5

Failover
Server X fails
Server N+1 reads indexes from shared storage and connects to logical
connection of server X
Storage Connector API ensures remount of necessary disk areas
(Note 1900823 - Storage Connector API Attachments)

2014 SAP SE or an SAP affiliate company. All rights reserved.

Server 6

SAN Storage

Server 2

Shared Storage

Server 1
Storage Connector API

High Availability configuration

N active servers in one cluster
M standby server(s) in one cluster
Shared file system for all servers

Standby Server

Public

HANA High Availability

Host Auto-Failover (standby)
Different implementation of High Availability by HW partners

Using storage solution inside

NFS/cluster fs / reallocating block devices

2014 SAP SE or an SAP affiliate company. All rights reserved.

Using internal disk

Standby

Name
Server

Name
Server

Index
Server

Index
Server

Index
Server

Data
Disks

Data
Disks

Data
Disks

GPFS

Log
Disks

Log
Disks

Log
Disks

GPFS

Name
Server

Public

High Availability Options

2

SAP HANA System Replication

SAP HANA High Availability: System Replication

Performance Optimized
Clients

Application Servers

Performance optimized option

Data Center 1

Primary

Secondary

(active)

(active, data pre-loaded)

Name Server

Transfer
by

Index server

Index server

HANA
database
kernel

Internal
Disks
Data
Disks

Name Server

Log
Disks

2014 SAP SE or an SAP affiliate company. All rights reserved.

Internal
Disks
Data
Disks

Log
Disks

HA Solution Partner

HA Solution Partner

OS: DNS, hostnames, virt. IPs

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

Public

10

SAP HANA High Availability: System Replication

Cost Optimized
Clients

Application Servers

Cost optimized with

Data Center 1

OS: DNS, hostnames, virt. IPs

Secondary

(active)
Name Server

Transfer
by

Index server

Data
Disks

Index
server
QA/DEV

HANA
database
kernel

Internal
Disks

PRD
shadow
Name Server
operation

running

Data
Disks

Log
Disks

2014 SAP SE or an SAP affiliate company. All rights reserved.

PRD

Log
Disks

Internal
Disks
Data
Disks

QA/DEV
Log
Disks

HA Solution Partner

HA Solution Partner

Primary

Operating non-prod systems on

Secondary
Resources freed (no data pre-load) to
be offered to one or more non-prod
installations
During take-over the non-prod
operation has to be ended
Take-over performance similar to cold
start-up

Public

11

Disaster Recovery Options

3

SAP HANA Storage Replication

SAP HANA Disaster Recovery: Storage Replication

Cluster across Data Centers with non-prod on 2nd site
Clients

Application Servers

Arrangement usually offered with a

strong part of hardware partners
involvement

Data Center 2

Data Center 1

Primary

Secondary
Prod. (inactive), QA&DEV (active)

Name
Server

Name
Server

Name
Server

Name
Server

Name
Server

Name
Server

Index
server

Index
server

Index
server

Index
server

Index
server

Index
server

HA Solution Partner

HA Solution Partner

OS: DNS, hostnames

Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

Storage
Mirroring

OS: Mounts

2014 SAP SE or an SAP affiliate company. All rights reserved.

Data
Volumes

Data
Volumes

Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

Log
Volume

Log
Volume

Support issues handled by/routed

to HW partners
TCO reduction by combined
operation with non-prod on
Secondary

Needs another disk stack for nonprod usage load

Cluster management often included
and delivered as a whole package

Public

13

Disaster Recovery Options

4

SAP HANA System Replication

SAP HANA Disaster Recovery: System Replication

Cluster across Data Centers with DB controlled transfer
Clients

Application Servers

Performance optimized option

Data Center 2

Data Center 1

Primary

Secondary

(active)
Name
Server

Name
Server

Name
Server

Index
server

Index
server

Index
server

Transfer
by

HANA
database
kernel

(active, data pre-loaded)

Name
Server

Name
Server

Name
Server

Index
server

Index
server

Index
server

HA Solution Partner

HA Solution Partner

OS: DNS, hostnames, virt. IPs

Faster Take-Over
Shortened Performance Ramp
(seconds to less minutes)
SYNC & ASYNC possible
Several cluster options

Some HW Partners offer prepackaged options

OS: Mounts
Data
Volumes

Data
Volumes

Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

Log
Volume

Log
Volume

2014 SAP SE or an SAP affiliate company. All rights reserved.

Step-by-Step Implementation Guide

(updated recently to SPS8):

https://scn.sap.com/docs/DOC47702
Public

15

How to configure
HANA system replication

SAP HANA in Data Centers

Video about SAP HANA System Replication

http://www.saphana.com/docs/DOC-4152
https://www.youtube.com/watch?v=oBUiWMjARpc
2014 SAP SE or an SAP affiliate company. All rights reserved.

Public

17

System replication using SAP HANA studio

Same SID

Same
Systemnumber
Same number of
services
(index,name,)

2014 SAP SE or an SAP affiliate company. All rights reserved.

Public

18

System replication using SAP HANA studio

Complete data backup

2014 SAP SE or an SAP affiliate company. All rights reserved.

Public

19

System replication using SAP HANA studio

Apply a logical
systemname e.g. location

2014 SAP SE or an SAP affiliate company. All rights reserved.

Public

20

System replication using SAP HANA studio

First stop the

secondary site

Apply a logical name

e.g. location

2014 SAP SE or an SAP affiliate company. All rights reserved.

Public

21

System replication using SAP HANA studio

2014 SAP SE or an SAP affiliate company. All rights reserved.

1.

Start the secondary site

2.

replication starts using backup

and logs

3.

Takeover done using SAP

HANA Studio (admin)

Public

22

High Availability for SAP with SUSE

Around 10 years of experience with High Availability for SAP NetWeaver
Systems

Starting around 1 year ago to implement the HANA SR Automation

Solutions are jointly developed between SUSE, SAP, customers and

partners in the SAP Linux Lab in Walldorf

SAP HANA System Replication and

SLES for SAP Applications
node 1

node 2
resource failover
active / active

N M
A

HANA PR1
primary

N M

HANA PR1
secondary

System
Replication

HANA
Database

HANA
memory-preload

Automate SAP HANA System Replication

Service Level Agreement

SAP HANA System

Replication

SUSE High Availability

Solution

SUSE Linux Enterprise High Availability Extension Cluster for SAP

HANA System Replication

node 1

Pacemaker

node 2

vIP
System Replication

SAP HANA
PR1
primary
System
PR1

SAP HANA
PR1
secondary
System
PR1

SUSE Linux Enterprise High Availability Extension Cluster for SAP

HANA System Replication

node 1

Pacemaker

node 2

System Replication

SAP HANA
PR1
primary
System
PR1

SAP HANA
PR1
secondary
System
PR1

SUSE Linux Enterprise High Availability Extension Cluster for SAP

HANA System Replication

node 1

Pacemaker

node 2

vIP
System Replication

SAP HANA
PR1
[primary]
System
PR1

SAP HANA
PR1
primary
System
PR1

SUSE Linux Enterprise High Availability Extension Cluster for SAP

HANA System Replication

node 1

Pacemaker

node 2

vIP
System Replication

SAP HANA
PR1
secondary
System
PR1

SAP HANA
PR1
primary
System
PR1

Direction of the system replication will only be changed if the

parameter AUTOMATED_REGISTER is been changed to true

From Concept to Implementation

suse01

suse02

vIP

SAP HANA
Primary

SAP HANA
Secondary
Cluster Communication

Master

SAPHana
Master/SlaveResource

Slave

Clone

SAPHanaTopology
CloneResource

Clone

Fencing

HANA System Replication in HAWK

SAPHanaSR Delivery
Package SAPHanaSR with two resource agents: SAPHanaTopology and
SAPHana
SAPHanaSR HAWK Wizard

Setup Guide

and

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

SAPHanaSR HAWK Wizard

Technical preview included in the
shipping.

Outlook: SAPHanaSR-monitor

Internal Testing: Test-Driver with >25K Tests

The Five Interfaces

HANA Startframework: sapstartsrv/sapcontrol/ HDB
(calls, output format GetProcessList)
HANA-Topology: landscapeHostConfiguration.py
(rc, output format)
SR-Topology: hdbnsutil
(calls, output format -sr_state--sapcontrol=1)
SAPHostagent: saphostctrl
(call, output format ListInstances)
SR-Status: hdbsql(now) / systemReplicationStatus.py (SPS09)
(rc, calls, output format)

Allowed Scenarios (yet)

Two-node clusters
Scale-up (single-box to single-box) HANA system replication
Single-tier System Replication ( A B ), no multi-tier
Preferred site takeover active - there is no other SAP HANA system (like
DEV, TST, QAS) on the replicating node that needs to be stopped during
takeover (not a technical limit, but requires additional testing)
Both physical and virtual SAP host names

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

Roadmap / Next Steps

Scale-Out ( @A @B )
- Currently under development
- PoC Tests expected in Q1/2015
Multi-tier System Replication Chain Topology ( A B C )
- Currently under testing
- Partner Tests expected in Q4/2014
Single-tier System Replication and DEV / TST ( A [B] + DEV )
- Cluster configuration already available
- Partner Tests expected in Q4/2014

Outlook: HANA in a SUSE Linux Enterprise High

Availability Extension Cluster
HANA Multi Node System Replication / Scale-OUT

swarm 1

swarm 2
resource failover
active / active

N M
A

HANA PR1
primary

N M

HANA PR1
secondary

System
Replication

HANA
Database
This scenario is currently in development

HANA
memory-preload

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 join

our community :-)
Visit our booth or contact us via
sapalliance@suse.com or saphana@suse.com

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

Find our Best Practices at:

www.suse.com/products/sles-for-sap/resource-library/

Thank you.

Corporate Headquarters

+49 911 740 53 0 (Worldwide)

Join us on:

Maxfeldstrasse 5

www.suse.com

www.opensuse.org

90409 Nuremberg
Germany

Unpublished Work of SUSE. All Rights Reserved.

This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE.
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 Disclaimer
This 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.