Week 1 Unit 1: Introduction

Introduction
Course overview High Availability and Disaster Recovery with SAP HANA Platform
Course Content:
Week 1: HA/DR Introduction, Overview, Setup Options
Week 2: HA/DR Support
Week 3: Backup & Recovery Support
Week 4: Final Exam

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

Public

Introduction
Impact of downtime on enterprise business

On average, enterprises lose between $84,000 and

$108,000 for every hour of downtime*

* Source: http://www.dataxstream.com/sap-virtualization-solutions/disaster-recovery/costs-of-downtime/
2016 SAP SE or an SAP affiliate company. All rights reserved.

Public

Introduction
Examples for business downtime

ABAP

Planned

Unplanned

Upgrades to new releases of SAP

application components

Front-end and middleware services for

connection to the Web

Maintenance events

SAP system services of the individual

application components

Customer transports

SAP
HANA

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

Planned outages

Underlying hardware and software

services

SAP HANA revisions & SPSs

Malfunction including networks

Patches for Data Services and SLT

Security threat

Maintenance events for OS &

hardware

Natural disasters

Custom development & enhancements

Unplanned outages

Failure of compliance & operation

Public

Introduction
SAP HANA continuous availability
Customer Expectation: Planned & Unplanned Downtimes

SAP HANA revisions & SPSs

Patches for Data Services and SLT
Maintenance events for OS & hardware
Custom development & enhancements
Planned outages

Continuous
availability

Unplanned downtime

Planned downtime

Data center
readiness
Hardware failure / malfunction
including networks
Software malfunction / security
threat / update
Natural / man-made disasters
Failure of compliance & operation
Unplanned outages

SAP HANA consumption

Extended SAP back-end deployments

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

Public

Introduction
What is high availability?

Availability is defined as a measure of a

systems operational continuity, which is
expressed as a percentage of time,
inversely proportional to downtime.

Fault Recovery is the process of

recovery and resuming system operations
after an outage in the data center due to a
fault.

Downtime is the consequence of

outages, which may be planned
(e.g. system upgrades) or unplanned
(e.g. power failures, natural disasters),
and brings down the data center
operations.

Disaster Recovery is the process of

recovering operations after an outage due
to a prolonged data center or site failure,
which requires preparations to back up
data over long distances.

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

Public

Introduction
Recovery key performance indicators
Recovery Period Objective (RPO) is the maximum tolerable period of time during which operational
data is lost without the ability to recover
Recovery Time Objective (RTO) is the maximum permissible time it takes to recover the system
after an outage for operations to resume

system operational

operation resumed

backups

time
RPO

RTO

RPO and RTO

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

Public

Introduction
Single points of failure (1)
The key to achieving fault tolerance is to eliminate single
points of failure by introducing redundancy. SAP HANA
appliance vendors deliver several levels of redundancy
to avoid outages due to component failures.

1. Hardware Redundancy: These include:

Redundant and hot-swappable power supply units
(PSUs), fans, network interface cards
Enterprise-grade, error-correcting protected
memories

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

Public

Introduction
Single points of failure (2)
2. Network Redundancy:

Redundant networks, network equipment, and

network connectivity is required to avoid network
failures from affecting system availability. This is
typically accomplished by deploying a completely
redundant switch topology, using the Spanning Tree
Protocol to avoid loops.
Routers can be configured with the Hot Standby
Router Protocol (HSRP) for automatic failover.

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

Public

Introduction
Single points of failure (3)
3. Data Center Redundancy: Data centers that host
SAP HANA solutions are equipped with:

Uninterrupted power supply (UPS) and backup

power generators
Redundant cooling systems and multi-sourced
providers of network connectivity and electricity

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

Public

10

Introduction
Single points of failure (4)
SAP HANA platform provides additional levels of defense
against failure-related outages.

a) Software: SAP HANA provides security

preconfigurations, a watchdog function, which
automatically restarts configured services in case of
detected stoppages
b) Persistence: SAP HANA persists transaction logs,
savepoints, and snapshots to support system restart
and recovery from host failures
c) Standby and Failover: Separate, dedicated standby
hosts are used for failover in case of failure of the
primary active hosts

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

Public

11

Thank you

Contact information:
open@sap.com

 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 SEs 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 forwardlooking 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.

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

Public

13

Week 1 Unit 2: Overview

Overview
High availability Support (1)
As an in-memory database platform:
SAP HANA maintains the reliability of its data in the event of failures
It resumes operations with most of the data loaded back in memory as quickly as possible in order to meet
the RTO objectives
fault or
disaster
primary

system operational
RPO

RTO

operation resumed

backup
prepare

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

detect recover performance failback

ramp

time

Public

Overview
High availability Support (2)
Mission-critical application systems are expected to operate with an RPO of zero data loss in the case of local
faults or disasters etc.
In order to achieve zero RPO and low RTO, data must be replicated synchronously over longer distances,
which impacts regular system performance and may require more expensive standby and failover solutions.
All of this leads to tradeoff decisions around the attributes of fault recovery functionality, cost, and complexity.

Solution
Backup & Recovery
SAP HANA Host Auto-Failover
SAP HANA Storage Replication w/ QA, Dev.
SAP HANA System Replication
SAP HANA System Replication w/ QA, Dev.

Used for
HA & DR
HA
DR
HA & DR
HA & DR

RPO
high
0
0*
0*
0*

RTO
high
med
med
low
med

Perf. ramp
med
long
long
short
long
*synchronous solution

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

Public

Overview
High availability Support (3)
SAP HANA platform supports the following high availability measures:

System availability support:

Host auto-failover:
Automatic failover from crashed host to standby host in the same system
Storage replication:
Continuous replication (mirroring) between primary storage and backup storage over a network
(may be synchronous)
System replication:
Continuous update of secondary systems by primary system, including in-memory table loading

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

Public

Overview
Fault recovery Support
SAP HANA platform supports the following fault recovery measures from failures:

Fault recovery support:

Service auto-restart:
Automatic restart of stopped services on host (watchdog)
Host auto-failover:
Automatic failover from crashed host to standby host in the same system

System replication:
Continuous update of secondary systems by primary system, including in-memory table loading

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

Public

Overview
Disaster recovery Support
SAP HANA platform supports the following recovery measures from failures:

Disaster recovery support:

Storage replication:
Continuous replication (mirroring) between primary storage and backup storage over a network (may be
synchronous)
System replication:
Continuous update of secondary systems by primary system, including in-memory table loading
Backups:
Periodic saving of database copies in safe place

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

Public

Overview
Data center readiness
SAP HANA
Data Center Readiness
Backup & Recovery
Data & log backup
Point-in-time
recovery
rd
3 -party backup
tool support
Netbackup,
Tivoli, Simpana,
DataProtector,
Networker,
Sesam
Storage snapshots
Point-in-time
recovery

Fault Recovery
In case of hardware
or system failure
the standby system
takes over in the
same data center
Several options:
Storage-based
Shadow
databases
Internal or
external cluster
manager

Disaster Recovery
Failover to a
different SAP
HANA instance in
another, even far
distant data center
Automatic and
manual procedures
possible
Several options:
Storage-based
Shadow
databases
External cluster
manager

Design & Setup

Several deployment
options
Multi-tenant
database container
SAP NetWeaver
central instance on
SAP HANA server
Virtualization
for production usage
Tailored data center
integration
Dynamic tiering

Security & Auditing

Comprehensive
security framework
Fine-granular
authorizations
Encryption
Compliance (SoD,
audit logging, ...)
Secure hardware /
software setup
IDM and GRC
integration
3rd party via standard /
documented interfaces

Continuous Improvement of Simplification & Flexibility

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

Public

Thank you

Contact information:
open@sap.com

 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 SEs 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 forwardlooking 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.

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

Public

Week 1 Unit 3: High Availability, Backup,

and Disaster Recovery Setup Options

High Availability, Backup, and Disaster Recovery Setup Options

High availability and disaster recovery Setup options
Storage Replication

Cluster-like solution

Similar to classical shadow

database solutions

Often already used by several

customers

One data pool

Includes solution for HA with
internal cluster manager
Uses Storage Connector APIs for
communication with environment

Ambivalent solution for HA & DR

Automation possible with external
cluster manager

Usually used for DR

Automation possible with external
cluster manager

Name
Server

Server 3
Standby Server

Covers HW problems with

additional host(s)
2016 SAP SE or an SAP affiliate company. All rights reserved.

Clients

Secondary

(active)

(active, data pre-loaded)

Name Server

Index Server

Index Server

SAP HANA
Database
Kernel

Internal
Disks
Data
Disks

Transfer
by

Name Server

Log
Disks

Internal
Disks
Data
Disks

Log
Disks

Covers HW and data integrity

problems with an additional set
of individually-driven data pools

Secondary

Primary

(inactive)
Name
Server

Name
Server

Name
Server

Name
Server

Name
Server

Name
Server

Index
Server

Index
Server

Index
Server

Index
Server

Index
Server

Index
Server

OS: Mounts
Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

HA Solution
Partner

Primary

Data Center 2
Data Center 1
OS: DNS, hostnames

HA Solution
Partner

Data Center
OS: DNS, virt. hostnames, virt. IPs

Application Servers

Storage
Mirroring

Name
Server

Server 2

Application Servers

HA Solution Partner

Name
Server

Server 1

Clients

HA Solution Partner

Name
Server

SAN Storage

System Replication

Storage
Connector API

Host Auto-Failover

Covers HW (data center)

failures on a broader scale
Public

High Availability, Backup, and Disaster Recovery Setup Options

Name
Server

Server 1

Standby node, data is not preloaded

Name
Server

Server 2

Automatic failover from crashed host to

standby host in the same system

Name
Server

Server 3

Cluster-like solution in a single data center

One (or more) standby hosts are added to an

SAP HANA system and configured to work in
standby mode

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

Name
Server

Standby Server

SAN Storage

1. Host Auto-Failover:

Storage Connector API

High availability and disaster recovery Capabilities (1)

Data Center

Public

High Availability, Backup, and Disaster Recovery Setup Options

High availability and disaster recovery Capabilities (2)
Clients
Data Center
OS: DNS, virt. hostnames, virt. IPs

Data is preloaded in secondary sites

Single or multiple data center support
Secondary standby system with the same
number of active nodes as the active primary
system

HA Solution Partner

Classical shadow database solution

Primary
(active)
Name Server
Index Server

Transfer
by

Name Server
Index Server

SAP HANA
Database
Kernel

Internal
Disks
Data
Disks

Secondary
(active, data preloaded)

Log
Disks

HA Solution Partner

2. System Replication:

Application Servers

Internal
Disks
Data
Disks

Data Center

Log
Disks

Data Center

Async
Sync

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

Public

High Availability, Backup, and Disaster Recovery Setup Options

High availability and disaster recovery Capabilities (3)
Clients

Single or multiple data center support

Often supported by storage partners

OS: DNS, hostnames

Secondary
(inactive)

Primary
Name
Server

Name
Server

Name
Server

Name
Server

Name
Server

Name
Server

Index
Server

Index
Server

Index
Server

Index
Server

Index
Server

Index
Server

OS: Mounts
Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

Data Center

Storage
Mirroring

Data is not preloaded in secondary sites

HA Solution Partner

Continuous replication (mirroring) between

primary storage and backup storage over a
network

Data Center 2

Data Center 1

Data
Volumes

Data
Volumes

Log
Volume

Log
Volume

HA Solution Partner

3. Storage Replication:

Application Servers

Data Center

Data Center

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

Public

High Availability, Backup, and Disaster Recovery Setup Options

Backup and recovery Setup options
B&R to file system

B&R to 3rd party backup tool

B&R using storage snapshots

Point-in-time recovery

Point-in-time recovery

Point-in-time recovery

Check of physical consistency

with header/trailer check sums

Check of physical consistency

with header/trailer check sums

No check of physical consistency

with header/trailer check sums

SAP HANA
Studio

SAP HANA
Studio

hdbsql

SAP HANA
Studio

Storage
Tool

hdbsql
hdbsql

Create backup

SAP HANA
Database

Prepare database

Create backup

Backup
Storage,
e.g. NFS

Early option often with local or remote

disk pools
Follow-up work necessary to transport
backup files to Save location
2016 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA
Database

SAP HANA
Database
3rd Party
Backup Agent

Confirm storage
snapshot

3rd Party
Backup
Server

Most comfortable solution

SAP HANA has full control of B&R
management

Create storage
snapshot
Data Snapshot

External
Storage

Data Area (Disk)

Very useful to create fast and ad-hoc

backups in seconds to minutes
Better combined with the other
options to get check data for free
Public

High Availability, Backup, and Disaster Recovery Setup Options

Backup and recovery Capabilities (1)
1. Backups File System:
SAP HANA platform persists two types of data
to storage: transaction redo logs and data
changes in the form of savepoints
File system is the common method to back up
data to a local or remote file system and
protect the database against any disk failures

SAP HANA
Studio

Create backup

SAP HANA
Database

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

hdbsql

Backup
Storage,
e.g. NFS

Public

High Availability, Backup, and Disaster Recovery Setup Options

Backup and recovery Capabilities (2)
2. Backups 3rd Party Backup Tools:
SAP HANA platform provides 3rd party backup agent
via the BACKINT API to back up data to a backup
server selected by the vendor
SAP also provides certifications for different backup
vendors for the BACKINT API

SAP HANA
Studio

hdbsql

Create backup

SAP HANA
Database

3rd

Party
Backup Agent

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

3rd Party
Backup
Server

Public

High Availability, Backup, and Disaster Recovery Setup Options

Backup and recovery Capabilities (3)
3. Backups Storage Snapshots:
A snapshot is a set of reference pointers to
data stored on a disk
SAP HANA platform provides backup
capabilities with split-mirror snapshots via
plugins

Storage vendor tools provide the capabilities

to perform the backup operations

SAP HANA
Studio
hdbsql

Storage
Tool

Create backup
Confirm storage
snapshot

SAP HANA Database

Create storage
snapshot
Data Snapshot

External
Storage

Data Area (Disk)

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

Public

Thank you

Contact information:
open@sap.com

 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 SEs 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 forwardlooking 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.

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

Public

11