Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 8. Finishing the setup

Ensure that the final setup is complete and the systems and resources are healthy, then you can enable the environment for production workloads.

If you want a previously failed primary site to automatically recover as a fully functional secondary site without manual verification of the data consistency, you can enable the SAPHanaController resource to re-register the site right after a takeover.

This enables the previously failed primary site to continue the HANA system replication and automatically take over again in the event of a new failure of the new primary site.

Your HANA operator must decide if they first require to manually check the health of the previously failed instance and re-register the HANA site afterwards, or if the priority is on a faster automatic recovery of the full high availability.

Procedure

  • Update the SAPHanaController resource and override the default AUTOMATED_REGISTER: 

    [root]# pcs resource update rsc_SAPHanaCon_<SID>_HDB<instance> AUTOMATED_REGISTER=true

Verification

  • Check that AUTOMATED_REGISTER is set to true: 

    [root]# pcs resource config rsc_SAPHanaCon_RH1_HDB02
     
    Resource: rsc_SAPHanaCon_RH1_HDB02 (class=ocf provider=heartbeat type=SAPHanaController)
  Attributes: rsc_SAPHanaCon_RH1_HDB02-instance_attributes
    AUTOMATED_REGISTER=true
    DUPLICATE_PRIMARY_TIMEOUT=7200
    InstanceNumber=02
    PREFER_SITE_TAKEOVER=true
    SID=RH1
...
Warning

Setting AUTOMATED_REGISTER to true can potentially increase the risk of data loss or corruption. If the HA cluster triggers a takeover when the data on the secondary HANA site is not fully in sync, the automatic registration of the old primary HANA site as the new secondary HANA site results in data loss on this site and any data that was not synced before the takeover occurred is lost as well.

For more information, see the article on the SAP Technology Blog for Members: Be Prepared for Using Pacemaker Cluster for SAP HANA – Part 2: Failure of Both Nodes.

8.2. Reviewing the final cluster state
Copy link

After the configuration of a 8-node cluster for a scale-out HANA system replication setup, the status looks like in the below example.

Your cluster state may deviate from the example, depending on your setup of optional or platform dependent resources, like the individual fencing or VIP resources.

Also, you can decide if you want to disable the cluster service, so that it does not start automatically on system boot. This requires manual intervention on every system boot, but allows you more control and supervision for the startup. 

[root]# pcs status --full

+ 

Cluster name: hana-scaleout-cluster
Status of pacemakerd: 'Pacemaker is running' (last updated 2025-12-18 16:27:04Z)
Cluster Summary:
  * Stack: corosync
  * Current DC: dc2hana1 (5) (version 2.1.5-9.el9_2.5-a3f44794f94) - partition with quorum
  * Last updated: Thu Dec 18 16:27:05 2025
  * Last change:  Thu Dec 18 16:26:37 2025 by root via crm_attribute on dc1hana1
  * 9 nodes configured
  * 19 resource instances configured

Node List:
  * Node dc1hana1 (1): online, feature set 3.16.2
  * Node dc1hana2 (2): online, feature set 3.16.2
  * Node dc1hana3 (3): online, feature set 3.16.2
  * Node dc1hana4 (4): online, feature set 3.16.2
  * Node dc2hana1 (5): online, feature set 3.16.2
  * Node dc2hana2 (6): online, feature set 3.16.2
  * Node dc2hana3 (7): online, feature set 3.16.2
  * Node dc2hana4 (8): online, feature set 3.16.2
  * Node dc3mm (9): online, feature set 3.16.2

Full List of Resources:
  * rsc_fence       (stonith:<fence agent>):     Started dc1hana2
  * Clone Set: cln_SAPHanaTop_RH1_HDB02 [rsc_SAPHanaTop_RH1_HDB02]:
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc2hana3
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc1hana1
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc1hana2
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc1hana3
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc2hana1
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc2hana2
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc1hana4
    * rsc_SAPHanaTop_RH1_HDB02  (ocf:heartbeat:SAPHanaTopology):         Started dc2hana4
  * Clone Set: cln_SAPHanaCon_RH1_HDB02 [rsc_SAPHanaCon_RH1_HDB02] (promotable):
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc2hana3
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Promoted dc1hana1
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc1hana2
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc1hana3
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc2hana1
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc2hana2
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc1hana4
    * rsc_SAPHanaCon_RH1_HDB02  (ocf:heartbeat:SAPHanaController):       Unpromoted dc2hana4
  * rsc_vip_RH1_HDB02_primary   (ocf:heartbeat:IPaddr2):         Started dc1hana1
  * rsc_vip_RH1_HDB02_readonly  (ocf:heartbeat:IPaddr2):         Started dc2hana1

Node Attributes:
  * Node: dc1hana1 (1):
    * hana_rh1_clone_state              : PROMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : master1:master:worker:master
    * hana_rh1_site                     : DC1
    * hana_rh1_sra                      : -
    * master-rsc_SAPHanaCon_RH1_HDB02   : 150
  * Node: dc1hana2 (2):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : master2:slave:worker:slave
    * hana_rh1_site                     : DC1
    * master-rsc_SAPHanaCon_RH1_HDB02   : 140
  * Node: dc1hana3 (3):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : slave:slave:worker:slave
    * hana_rh1_site                     : DC1
    * master-rsc_SAPHanaCon_RH1_HDB02   : -10000
  * Node: dc1hana4 (4):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : master3:slave:standby:standby
    * hana_rh1_site                     : DC1
    * master-rsc_SAPHanaCon_RH1_HDB02   : 140
  * Node: dc2hana1 (5):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : master1:master:worker:master
    * hana_rh1_site                     : DC2
    * hana_rh1_sra                      : -
    * master-rsc_SAPHanaCon_RH1_HDB02   : 100
  * Node: dc2hana2 (6):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : master2:slave:worker:slave
    * hana_rh1_site                     : DC2
    * master-rsc_SAPHanaCon_RH1_HDB02   : 80
  * Node: dc2hana3 (7):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : slave:slave:worker:slave
    * hana_rh1_site                     : DC2
    * master-rsc_SAPHanaCon_RH1_HDB02   : -12200
  * Node: dc2hana4 (8):
    * hana_rh1_clone_state              : DEMOTED
    * hana_rh1_gra                      : 2.0
    * hana_rh1_gsh                      : 1.0
    * hana_rh1_roles                    : master3:slave:standby:standby
    * hana_rh1_site                     : DC2
    * master-rsc_SAPHanaCon_RH1_HDB02   : 80

Migration Summary:

Tickets:

PCSD Status:
  dc1hana1: Online
  dc1hana2: Online
  dc1hana3: Online
  dc1hana4: Online
  dc2hana1: Online
  dc2hana2: Online
  dc2hana3: Online
  dc2hana4: Online
  dc3mm: Online

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled


In a healthy setup the additional cluster attributes appear like in this example: 

[root]# SAPHanaSR-showAttr
 
Global cib-time                 prim sec srHook sync_state upd
---------------------------------------------------------------
RH1    Thu Dec 18 16:28:49 2025 DC1  DC2 SOK    SOK        ok

Sites lpt        lss mns      srr
----------------------------------
DC1   1766075329 4   dc1hana1 P
DC2   30         4   dc2hana1 S

Hosts    clone_state gra gsh node_state roles                         score  site sra
--------------------------------------------------------------------------------------
dc1hana1 PROMOTED    2.0 1.0 online     master1:master:worker:master  150    DC1  -
dc1hana2 DEMOTED     2.0 1.0 online     master2:slave:worker:slave    140    DC1
dc1hana3 DEMOTED     2.0 1.0 online     slave:slave:worker:slave      -10000 DC1
dc1hana4 DEMOTED     2.0 1.0 online     master3:slave:standby:standby 140    DC1
dc2hana1 DEMOTED     2.0 1.0 online     master1:master:worker:master  100    DC2  -
dc2hana2 DEMOTED     2.0 1.0 online     master2:slave:worker:slave    80     DC2
dc2hana3 DEMOTED     2.0 1.0 online     slave:slave:worker:slave      -12200 DC2
dc2hana4 DEMOTED     2.0 1.0 online     master3:slave:standby:standby 80     DC2
dc3mm                        online
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Legal Notice

Theme

© 2026 Red HatBack to top