sap hana sps08 scale-out, high availability and disaster recovery

Use this title slide only with an image

SAP HANA SPS 08 - What’s New? Scale-Out, High Availability and Disaster Recovery

SAP HANA Product Management May, 2014

(Delta from SPS 07 to SPS 08)

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 2Public

High Availability and Disaster Recovery – What’s New in SPS 08?Agenda

Scale-Out

High Availability

Disaster Recovery SAP HANA Storage Replication

• New offerings by hardware partners SAP HANA System Replication

• System Replication Modes – FullSync mode• Improved support for SAP HANA System Replication in SAP HANA Studio• Hostname management offers a network separation for System Replication

Disaster Recovery


Disaster RecoveryAgenda

Disaster Recovery

SAP HANA Storage Replication• New offerings by hardware partners

SAP HANA System Replication• System Replication Modes – FullSync mode• Improved support for SAP HANA System Replication in SAP HANA Studio• Hostname management offers a network separation for System Replication

SAP HANA Storage Replication


Certified HANA Hardware – May 2014*

(only China)

Scale Out (BW) S - L M M, L M M S - L M M M

High Availability X X X X X X X X X

DR – Storage Repl.: Sync

X X X X X X

DR – Storage Repl.: Async

X X,X X planned

All certified synchronous and asynchronous solutions for SAP HANA Storage Replication are listed in SAP note 1755396.

* For most up to date list please go to the SAP Product Availability Matrix (Westmere) or http://scn.sap.com/docs/DOC-52522 (IvyBridge)

https://service.sap.com/sap/support/notes/1755396

http://service.sap.com/pam

http://scn.sap.com/docs/DOC-52522

http://scn.sap.com/docs/DOC-52522

SAP HANA System Replication


SAP HANA System ReplicationWhat’s New with SPS 08

Replication Modes

Three Replication Modes New Full-Sync option for Synchronous

SAP HANA Studio extensions

Extended system replication configuration Support for Multi-Tier System Replication

Hostname management

Offering a separation of networks and duties System Replication can be supported with an separate network

SAP HANA System ReplicationReplication Modes in SAP HANA System Replication


SAP HANA System Replication - IntroductionPerformance Optimized for HA and DR

Performance optimized option 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

Data Center 1

OS: DNS, hostnames, virt. IPs

Primary(active)

Name Server

Index server

Secondary(active, data pre-loaded)

Name Server

Index server

HA

Sol

utio

n P

artn

er

Clients Application Servers

HA

Sol

utio

n P

artn

er

Transferby

HANAdatabase

kernelInternalDisks

InternalDisks

DataDisks

LogDisks

DataDisks

LogDisks


SAP HANA System Replication - IntroductionCost Optimized for HA and DR

Cost optimized with 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

Data Center 1

OS: DNS, hostnames, virt. IPs

Primary(active)

Name Server

Index server

Secondary

Name Server

Index server

HA

Sol

utio

n P

artn

er

Clients Application Servers

HA

Sol

utio

n P

artn

er

Transferby

HANAdatabase

kernelInternalDisks

DataDisks

LogDisks

InternalDisksData

Disks

LogDisks

DataDisks

LogDisks

PRD

QA/DEV


SAP HANA in Data CentersCluster Manager with direct SAP HANA System Replication Support

HP Serviceguard Directly available from HP and HP drives the implementation process Link for further information: o Reference Guide: HP Serviceguard Extensions for SAP Release Notes, March 2014o User Guide: Managing HP Serviceguard Extensions for SAP for Linux, December 2013

SUSE Cluster Included with “SUSE SLES for SAP Applications” Blog: Fail-Safe Operation of SAP HANA®: SUSE Extends Its High-Availability Solution

SAP Landscape Virtualization Manager (SAP LVM) Consulting package to create a cluster manager with SAP LVM available

Other cluster managers In pipeline or can be adapted with individual consulting packages

Note: Solution certification is not offered for cluster managersSupport is handled by solution partner directly

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/action.process/public/psi/manualsDisplay/?sp4ts.oid=4181640&javax.portlet.action=true&spf_p.tpst=psiContentDisplay&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.prp_psiContentDisplay=wsrp-interactionState=docId=emr_na-c04197457%7CdocLocale=en_US&javax.portlet.endCacheTok=com.vignette.cachetoken






http://scn.sap.com/community/hana-in-memory/blog/2014/04/04/fail-safe-operation-of-sap-hana-suse-extends-its-high-availability-solution


System Replication ModesIntroduction

SAP HANA offers the following replication modes

With HANA SPS 08 SAP introduces a new option for the synchronous mode SYNC named Full Sync option

On the following slides these modes are explained together with the new option.

Log replication Since Short name in system table SR_REGISTER

Synchronous SPS 05 SYNC

Synchronous in Memory SPS 05 SYNCMEM

Asynchronous SPS 06 ASYNC


System Replication ModesSynchronous with Full Sync option

Log Replication “Synchronous with Full Sync Option”

Available since SPS 08

Viewed in system table SR_REGISTER as SYNC (Full Sync is configured via configuration parameter)

Description Log write is successful, when the log buffer has been written to the log volume

of the primary and the secondary instance. In addition, when the secondary system is getting disconnected (e.g. because of network failures), the primary systems suspends transaction processing until the connection to the secondary system is re-established. No data loss occurs in this scenario.

Implementation The replication mode Synchronous can be configured with the full sync option by setting the following configuration parameter on

the primary site:• global.ini/[system_replication]/enable_full_sync = true.• hdbnsutil -sr_fullsync [--enable|--disable]

Replication mode most interesting for financial institutes

Primary Secondary

DataData Log

Transaction

Log

STOP


System Replication ModesSynchronous with Full Sync option - Implementation

The recommended way for setting up full sync is the following: Establish replication between primary and secondary via replication Synchronous first Wait until all services are ACTIVE in replication mode Synchronous Enable Full Sync (via hdbnsutil or configuration parameter change)

Full Sync Status

With the Full Sync Option also the Full Sync Status has been introduced. The Full Sync Status determines, if the Full Sync is currently ACTIVE, that means, when the connection is lost, if transaction processing on the primary will be suspended. Full Sync Status has three possible values: DISABLED

• Full Sync is not configured at all (global.ini/[system_replication]/enable_full_sync = false) ENABLED

• Full Sync configured, but not yet active (global.ini/[system_replication]/enable_full_sync = true) ACTIVE

• Full Sync is configured and active (global.ini/[system_replication]/enable_full_sync = true)

The current value of the Full Sync Status is available via select on M_SERVICE_REPLICATION (column FULL_SYNC) or hdbcons "replication info".

Primary Secondary

DataData Log

Transaction

Log


System Replication ModesSynchronous - SYNC

Log Replication “Synchronous”


Viewed in System Table SR_REGISTER as SYNC

Description Log write is successful, when the log buffer has been written to the log volumes of the primary and the

secondary instance.When the connection to the secondary system is lost (after a timeout period defined with parameter logshipping_timeout=30), the primary system continues transaction processing and is writing the changes only to the local disk. No data loss occurs in this scenario as long as the secondary system is connected. Data loss can occur, when takeover is executed, after the secondary system is disconnected.

Primary Secondary

DataData Log

Transaction

Log


System Replication ModesSynchronous in Memory – SYNCMEM

Log Replication “Synchronous in Memory”


Viewed in System Table SR_REGISTER as SYNCMEM

Description Log write is successful, when the log buffer has been written to the log volumes of the primary and sending the

log has been acknowledged by the secondary instance after copying to memory. When the connection to the secondary system is lost, the primary system continues transaction processing and is writing the changes only to the local disk. Data loss can occur when primary and secondary fail at the same time as long as the secondary system is connected or takeover is executed.

Primary Secondary

DataData Log

Transaction

Log


Log Replication “Asynchronous”


Viewed in System Table SR_REGISTER as ASYNC

Description Log write is successful, when the log buffer has been written to the log volumes of the primary and send to the

secondary via the network channel.In this case data loss can occur.

The change between replication modes SYNC, SYNCMEM and ASYNC is online possible.

System Replication ModesAsynchronous – ASYNC

Primary Secondary

DataData Log

Transaction

Log


System Replication ModesAsynchronous – ASYNC – Improvement

Improvement With SPS 07 the ASYNC mode has been changed in a way that

additionally to the buffering capabilities of the Operating System, an additional memory buffer inside HANA was added and operated with signaling semaphores. This introduces another decoupling with possibly limited resources on OS side when it comes to ASYNC operation.

The size of the intermediate buffer can be changed with the following parameter (here with default size): [system_replication]/logshipping_async_buffer size = 67108864

It is sufficient to set the parameter only for services with high log generation (e.g. in indexserver.ini) to save memory with other services. It is not necessary to set it globally.

Using the following parameter, the behavior in case of buffer full can be change (with default setting): Transactions and their log transfer are waiting for free space in the buffer, if it’s full global.ini/[system_replication]/logshipping_async_wait_on_buffer_full = true

Primary Secondary

DataData Log

Transaction

Log

Buf

fer

SAP HANA System ReplicationSAP HANA Studio extensions for SAP HANA System Replication:Support for Multi Tier System Replication


SAP HANA Studio ExtensionsSupport for Multi-Tier System Replication

Extended system replication configuration To offer higher levels of availability you can link

together multiple systems in a multi-tier system replication landscape.

After setting up a basic system replication scenario you add a third system to provide another level of redundancy.

In a multi-tier setup the primary system is always on tier 1, a tier 2 secondary has a primary system as its replication source and a tier 3 secondary has the tier 2 secondary as its replication source.

The tier 3 secondary can now also be added using SAP HANA studio.

On each node only those actions are provided, which are currently possible – depending on the system status.

Data Center Data Center

SyncAsync

SAP HANA System ReplicationHostname management with SAP HANA System Replication


Hostname management with SAP HANA System ReplicationIntroduction

SAP HANA System Replication started with a shared usage of the public client network for transferring its data and log information between sites

Since SAP HANA SPS 08 its network management offers to separate the networks into Client network Internal Network Network for System Replication

The necessary changes in the parameter files (e.g. global.ini) are described in the following slides. Starting with the case of using a separate network for System Replication And comparing it with the situation before


Network design options for System ReplicationSystem Replication over separate network with single host configuration

Host s1h1

Site 1 Site 2

Separate Replication Network 10.5.*

Public Network 10.0.*

Client Applications

Host s2h110.5.1.* 10.5.2.*

10.0.1.* 10.0.2.*

Host Configuration:

global.ini[communication]listeninterface=.local

[system_replication_hostname_resolution]10.5.2.1=s2h1

Optionally configurable with global.ini:[public_hostname_resulution]

Host Configuration:

global.ini[communication]listeninterface=.local

[system_replication_hostname_resolution]10.5.1.1=s1h1


Network design options for System ReplicationSystem Replication over separate network with Scale-Out configuration

Host s1h1

Host s1h2

Host s1h3

Site 1 Site 2



Client Applications

Host s2h1

Host s2h2

Host s2h310.5.1.* 10.5.2.*

10.0.1.* 10.0.2.*Optionally configurable with global.ini:[public_hostname_resulution]

Host Configuration:

global.ini

[communication]

listeninterface=.global

[ [system_replication_hostname_resolution]

10.5.2.1=s2h1

10.5.2.2=s2h2

10.5.2.3=s2h3

Host Configuration:

global.ini

[communication]

listeninterface=.global

[ [system_replication_hostname_resolution]

10.5.1.1=s2h1

10.5.1.2=s2h2

10.5.1.3=s2h3


Internal Network 192.168.*Internal Network 192.168.*

Network design options for System ReplicationSystem Replication over separate network with Scale-Out and internal network separation

Host s1h1

Host s1h2

Host s1h3

Site 1 Site 2



Client Applications

Host s2h1

Host s2h2

Host s2h310.5.1.* 10.5.2.*

10.0.1.* 10.0.2.*

Host Configuration:

global.ini

[communication]

listeninterface=.internal

[internal_host _resolution]

192.168.1.1=s1h1

192.168.1.2=s1h2

192.168.1.3=s1h3

[system_replication_hostname_resolution]

10.5.2.1=s2h1

10.5.2.2=s2h2

10.5.2.3=s2h3


Host Configuration:

global.ini

[communication]



192.168.1.1=s2h1

192.168.1.2=s2h2

192.168.1.3=s2h3

[system_replication_hostname_resolution]

10.5.1.1=s1h1

10.5.1.2=s1h2

10.5.1.3=s1h3


Internal Network 192.168.*Internal Network 192.168.*

Network design options for System ReplicationSystem Replication over public network with Scale-Out and internal network separation

Host s1h1

Host s1h2

Host s1h3

Site 1 Site 2


Client Applications

Host s2h1

Host s2h2

Host s2h3

10.0.1.* 10.0.2.*

Host Configuration:

global.ini

[communication]



192.168.1.1=s1h1

192.168.1.2=s1h2

192.168.1.3=s1h3


Host Configuration:

global.ini

[communication]



192.168.1.1=s2h1

192.168.1.2=s2h2

192.168.1.3=s2h3


Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP.

SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP’s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.

This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.


How to find SAP HANA documentation on this topic?

SAP HANA Platform SPS What’s New – Release Notes

Installation– SAP HANA Server InstallationGuide

Security

Administration– SAP HANA Administration Guide

Development– SAP HANA Developer Guide

References – SAP HANA SQL Reference

• In addition to this learning material, you find SAP HANA documentation on SAP Help Portal knowledge center at http://help.sap.com/hana_platform.

• The knowledge center is structured according to the product lifecycle: installation, security, administration, development. So you can find e.g. the SAP HANA Server Installation Guide in the Installation section and so forth …

http://help.sap.com/hana_platform



http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf

http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf



http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf


http://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf


http://help.sap.com/hana/SAP_HANA_SQL_and_System_Views_Reference_en.pdf


© 2014 SAP AG or an SAP affiliate company. All rights reserved.

Thank youContact information

Dr. Ralf CzekallaSAP HANA Product [email protected]

To get the best overview of what’s new in SAP HANA SPS 08, read this blog.

mailto:[email protected]

http://www.saphana.com/community/blogs/blog/2014/05/28/what-s-new-in-sap-hana-sps-08


© 2014 SAP AG 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 AG 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 AG (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 AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG 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 AG 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 AG’s 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 AG 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 forward-looking 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.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

sap hana sps08 scale-out, high availability and disaster recovery

Technology

sap affiliate company

sap applicationsblog

image2014 sap ag

sap release notes

separate network2014

public7certified hana

dutiessystem replication

following replication