Professional Documents
Culture Documents
Scale-Out, High Availability and Disaster Recovery: SAP HANA SPS 08 - What's New?
Scale-Out, High Availability and Disaster Recovery: SAP HANA SPS 08 - What's New?
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
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
(only China)
High Availability X X X X X X X X X
DR Storage Repl.:
X X X X X X
Sync
DR Storage Repl.:
X X,X X planned
Async
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)
2014 SAP AG or an SAP affiliate company. All rights reserved. Public 8
SAP HANA System Replication
SAP HANA System Replication
Whats New with SPS 08
Replication Modes
Three Replication Modes
New Full-Sync option for Synchronous
Hostname management
Offering a separation of networks and duties
System Replication can be supported with an separate network
HA Solution Partner
HA Solution Partner
HA Solution Partner
HA Solution Partner
PRD
Name Server Transfer shadow
Name Server During take-over the non-prod
operation
by operation has to be ended
Index server Index server
Take-over performance similar to cold
HANA
database QA/DEV running start-up
Internal kernel Internal
Disks Data Disks
Data
Disks Disks
Data Log PRD QA/DEV
Log Log
Disks Disks
Disks Disks
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 2014
o 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
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.
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.
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.
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.
Improvement
Primary Secondary
Buffer
With SPS 07 the ASYNC mode has been changed in a way that
additionally to the buffering capabilities of the Operating System, Transaction
Sync
Support for Multi-Tier System Replication Async
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
Site 1 Site 2
Site 1 Site 2
Host Host Host Separate Replication Network 10.5.* Host Host Host
s1h1 s1h2 s1h3 10.5.1.* 10.5.2.* s2h1 s2h2 s2h3
Client Applications
Optionally configurable with global.ini:
10.0.1.* Public Network 10.0.* 10.0.2.* [public_hostname_resulution]
Site 1 Site 2
Host Host Host Separate Replication Network 10.5.* Host Host Host
s1h1 s1h2 s1h3 10.5.1.* 10.5.2.* s2h1 s2h2 s2h3
Client Applications
Optionally configurable with global.ini:
10.0.1.* Public Network 10.0.* 10.0.2.* [public_hostname_resulution]
Site 1 Site 2
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
SAPs 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.
To get the best overview of whats new in SAP HANA SPS 08, read this blog.
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.
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 AGs 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.