See what's new in SAP HANA SPS10- Scale-Out, High Availability and Disaster Recovery

1. 1© 2014 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA SPS 10 - What’s New?
Scale-Out, High Availability and Disaster Recovery
SAP HANA Product Management June, 2015
(Delta from SPS 09 to SPS 10)

2. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 2Public
Scale-Out, High Availability and Disaster Recovery
What’s New in SPS 10? – Agenda
Scale-Out, Persistence
 Check for existence of vital SAP HANA files
Scale-Out, High Availability (Host Auto-Failover)
 Support for Dynamic Tiering with own failover group
 New Parameters in Host Auto-Failover control
Disaster Recovery, High Availability
 SAP HANA System Replication
• Optimizations in Row store handling for faster take-over times
• Support for SAP HANA Cockpit with tiles for SAP HANA System Replication

3. Scale-Out,
Persistence

4. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 4Public
What’s New in SPS 10: Persistence
Existence check for vital files
Check for existence of Data and Log Volume structures
With every SAP HANA Savepoint execution now
also a check of vital database files is executed
Checked objects:
 Data Volumes directory
 Data Volumes files
 Log Volume directory
 Log Volume segment files
The check is looking for the file/object existence to offer
alerts early enough to start activities to ease the impact
of the accidental file deletion
Recommended activities:
As long as the database is still functional admins can still
create backups and use them for recovery after restart
 With the restart of the SAP HANA finally the locks on the
file bodies are stopped and the file bodies (block chains on disk)
are not existing anymore.
 Before that only the file meta data was deleted in directory structures.
With this alert we want to inform HANA admins early enough to take action!
/ (root)
/usr/sap /hana
data log shared
H36 H36 H36
Linux
mnt00001 mnt00002 mnt00001 mnt00002
hdb00001
hdb00002
hdb00003
hdb00004
hdb00001
hdb00002
hdb00003
hdb00004
hdb00005 hdb00005
10GB 50GB
n x RAM
1 x RAM3 x RAM 1 x RAM3 x RAM

5. Scale-Out
High Availability

6. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 6Public
What’s New in SPS 10: Scale-Out/Host Auto-Failover
Failover Group for Dynamic Tiering
Failover group
A failover group can be defined for each host.
In case of failover the nameserver tries to fail
over to a host within the same group.
Since SPS10 with dynamic tiering a special
failover group for the group of possible
different sized hardware boxes
 Failover group 'default'
 Failover group 'extended_storage'
Technology was now extended to the
different IO schema of Dynamic Tiering
(shared everything) to offer Host Auto-
Failover also with this rather new setup
option
Dynamic Tiering can now operate on NFS
and SAN
No changes necessary to the Storage
Connector API
Warm Data
SAP HANA
Node 5 Node 6
Fail-
Over
Node
Node 7Node 1 Node 2 Node 3
Fail-
over
Node
Node 4
BW
Dynamic Tiering
(Extended Storage)
Data for persistence & recovery
data&
log
Hot data (Loaded) Warm data (Cashed)
Data_es
&
log_es
data&
log
data&
log
data_es
&
log_es
Failover Group
default
Failover Group
extended_storage

7. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 7Public
Warm Data
SAP HANA
Node 5 Node 6
Fail-
Over
Node
Node 7Node 1 Node 2 Node 3
Fail-
over
Node
Node 4
BW
Dynamic Tiering
(Extended Storage)
Data for persistence & recovery
data&
log
Hot data (Loaded) Warm data (Cashed)
Data_es
&
log_es
data&
log
data&
log
data_es
&
log_es
Failover Group
default
Failover Group
extended_storage
What’s New in SPS 10: Scale-Out
Failover Group for Dynamic Tiering
Installation
With SPS10 the installer only supports automatic
failover by setting the same failover group
'extended_storage' for involved hosts
 SAP HANA on any supported storage type
Dynamic Tiering on NFS or SAN
 SAP HANA and Dynamic Tiering on same storage
type
To distinguish Dynamic Tiering on NFS or SAN the
nameserver/fcClient must know if it supposed to
be on SAN
 This will be supported with new INI parameter
 global.ini
[storage]
ha_provider = hdb_ha.fcClient
enable_extended_storage=true
partition_1_data__wwid = <wwid1>
partition_1_log__wwid = <wwid2>
partition_1024_data_es__wwid = <wwid3>
partition_1024_log_es__wwid = <wwid4 >

8. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 8Public
What’s New in SPS 10: Scale-Out
Failover Group for Dynamic Tiering
#HANA
./hdblcm [..] –sid=DT1
--components=server,es
--component_dirs=`pwd`/server,/area51/external_components/ES/latest
--datapath=/hana/data/DT1
--logpath=/hana/log/DT1
--es_datapath=/hana/data_es/DT1
--es_logpath=/hana/log_es/DT1
--storage_cfg=/data/nfs_export/config/lun_es
#DT Worker
./hdblcm --action=add_hosts
--addhosts=<host>:role=extended_storage_worker:group=extended_storage
#DT Standby
./hdblcm --action=add_hosts
--
addhosts=<host+1>:role=extended_storage_standby:group=extended_storage
Landscape setup
Joint failover group
 extended_storage
Host Roles
 extended_storage_worker
 extended_storage_standby
Still possible to use manual failover

9. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 9Public
What’s New in SPS 10: Scale-Out
New Parameter in SPS10: daemon.ini
Daemon.ini – comments on parameters
Number of retries, if a service fails in startup
procedure:
startup_error_restart_retries=4
 Might be important for slow IO systems
Wait time in ms between startup retries set in
parameter:
startup_error_restart_delay=10000
 Waiting period between retries in seconds?
If parameter
startup_error_shutdown_instance in a
service section set to true the daemon will
shutdown all services on the host if this service
cannot start
If startup_error_restart_retries is set the shutdown
will be initiated after all retries failed
startup_error_shutdown_instance=true
 Parameter is set to true in section for [nameserver] by
default
 If nameserver fails to start the daemon will
shutdown all services of this host and the daemon
itself
 Failover
 In earlier version of HANA a still running daemon
prevented the failover

10. High Availability
Disaster Recovery

11. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 11Public
What’s New in SPS 10: SAP HANA System Replication
Improved Take-Over Performance
Improved take-over performance
Optimization in RowStore (RS) handling during take-overs
 Extension of the SPS09 feature keeping the RowStore in main memory on
Secondary during take-over
 With SPS10 the rebuild of the secondary indexes during reactivation of the
RowStore now can be done in a decoupled way
 No necessity to wait for finishing the creation process
 Is done asynchronously in background
 Short-time missing secondary indexes can be coped with primary key accesses
to involved tables until they are created
 ColumnarStore (CS) is preloaded for possible take-over anyway
(if the performance optimized version of System Replication is used)
Primary
HANA
Secondary
HANA
RS
Take-
over
CS
pre-
load
Secondary index
creation
decoupled

12. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 12Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – Main Screen
New support for SAP HANA System Replication in SAP HANA Cockpit
Cockpit accessible via <hostname>:80<sid>/sap/hana/admin/cockpit
 User and Password necessary
 Frontend is highly adaptable to users
or user group tasks

13. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 13Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – Main Tile
Tile on the main screen
 Type of landscape
(2 tier or 3 tier)
 Sums up the status info
underneath
 Presents synchronization
mode for the first
replication in chain
The following states can
be shown:
 Not configured (meaning
system replication is not
configured)
 Active and in sync (green
square)
 All services are active but
not yet in sync yet (yellow
triangle)
 Errors in Replication (red
circle)

14. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 14Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – Details Chain of Systems
Behind the main screen tile
Lists involved systems in
order of their relationships
The upper part sums up the
chain of systems in case of
Multi Tier system replication
 The mentioned avg. write
times are related to log writing
o Values on ASYNC connects
usually are smaller because of
OS buffering
 Avg. Log Buffer Size is the Log
info which is ...
 SY stands for SYNC
 AS stands for ASYNC

15. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 15Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – User settings
Several user settings
changable
Popups
 Columns
 Sort
System related setups

16. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 17Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – Details of replication process per connection
Per SAP HANA replication process
vital data can be shown
IO times history presented graphically
 Shipped [ms]
 Local [ms]
With a click on the diagram columns
related values are presented

17. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 18Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – Even more Details presented
With a click on the host
line more individual
KPIs are presented
Related to the selected
connection and service
following data is
presented
 General Overview
 Log Positions
 Savepoints
 Full Data Replica
 Delta Data Replica
 Backlog

18. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 19Public
What’s New in SPS 10: SAP HANA System Replication
Support for SAP HANA Cockpit – Link to alerts
Crosslinked with
Alerts Tile

19. More Information

20. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 21Public
What’s New in SAP HANA SPS09: HA & DR
More information
SAP HANA documentation
Available on the SAP Help Portal
 SAP HANA Administration Guide,
 SAP HANA Technical Operations Manual
SAP HANA website
 SAP HANA Features: Data Center
SAP HANA in Data Centers – Introduction and
Overview
 http://www.saphana.com/docs/DOC-2010

21. © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Thank you
Contact information
Prasad Illapani
SAP HANA Product Management
prasad.illapani@sap.com
Dr. Ralf Czekalla
SAP HANA Product Management
ralf.czekalla@sap.com

22. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 23Public
© 2015 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 SE’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 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 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.