High Availability for SAP HANA: Cost-optimized scenario

First Published on SUSE Blog 




SAP HANA contains a feature called System Replication: it replicates all data to a secondary SAP HANA system, and the data is then constantly pre-loaded into memory on the secondary system to minimize recovery time objective (RTO). More information on SAP HANA System Replication see here. While System Replication is running, the secondary system, which is configured identically to the primary, is on standby until a takeover takes place. The secondary server can normally not be used for anything else.


How the failover between 2 HANA instances in the cost-optimized scenario is automated leveraging SUSE HA technology is explained in this new Whitepaper.

Whats Covered in this White paper?
1 About This Guide 1
1.1 Introduction 1
Scale-Up vs. Scale-Out 1 • Scale-Up scenarios and resource
agents 2 • The concept of the Cost Optimized Scenario 3 • Customers
Receive Complete Package 4
1.2 Additional Documentation and Resources 5
1.3 Feedback 5
1.4 Documentation Conventions 6

2 Supported Scenarios and Prerequisites 7

3 Scope of this Documentation 9

4 Installing the SAP HANA Databases on both cluster
nodes 11
4.1 SAP HANA Installation 11
4.2 Postinstallation configuration 12
Back Up the Primary Database 12 • HDB System Replication 13 • Reducing
memory resources of the productive SAP HANA system on node2 15 • Implementing
the srTakeover-Hook 16 • Manual SAP HANA takeover
test 19 • Manual re-establish SAP HANA SR to original state 19 • Install
the non-productive SAP HANA database (QAS) 20 • Shutdown all SAP HANA
databases 21

5 Configuration of the Cluster and SAP HANA Database
Integration 22
5.1 Installation 22
iv SAP HANA SR Cost Optimized Scenario
5.2 Basic Cluster Configuration 22
Initial cluster setup using ha-cluster-init 23 • Adapting the Corosync
and sbd Configuration 23 • Cluster configuration on the second
node 27 • Check the Cluster for the first Time 27
5.3 Configure Cluster Properties and Resources 28
Cluster bootstrap and more 28 • STONITH device 28 • Using
IPMI as fencing mechanism 29 • Using other fencing mechanisms
29 • SAPHanaTopology 29 • SAPHana 30 • The virtual IP address
32 • Constraints 32 • Add the cluster resource for the non-productive
SAP HANA database 33 • Adding the cluster rules for the automatic shutdown
of SAP HANA QAS 33

6 Testing the Cluster 35

7 Administration 37
7.1 Do and Don't 37
7.2 Monitoring and Tools 37
HAWK – Cluster Status and more 37 • SAP HANA Studio 38 • Cluster
Command-Line Tools 38 • SAP HANA LandscapeHostConfiguration 39
7.3 Maintenance 40

Updating the OS and Cluster 41 • Updating SAP HANA 41 • Migrating a
HANA primary 42
A Useful Links, Manuals, and SAP Notes 44
A.1 SUSE Best Practices and More 44
A.2 SUSE Product Documentation 44
A.3 SAP Product Documentation 45
A.4 SAP Notes 45

B Examples 47
B.1 Example ha-cluster-init Configuration 47
B.2 Example Cluster Configuration in Format 48
v SAP HANA SR Cost Optimized Scenario
B.3 Example for /etc/corosync/corosync.conf 49
B.4 Example for the IPMI STONITH Method 51




#SPS12 #S4HANA #SLES #HA #HIGHAVAILABILITY 
Share this article :

Post a Comment

 
Copyright © 2011. SAP HANA TUTORIALS FREE - S/4 HANA - All Rights Reserved