Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 6. Maintenance procedures

The following sections describe the recommended procedures to perform maintenance on HA cluster setups used for managing HANA Scale-Out System Replication. You must use these procedures independently from each other.

Note

It is not necessary to put the cluster in maintenance-mode when using these procedures. For more information, refer to When to use "maintenance-mode" in RHEL High Availability Add-on for pacemaker based cluster?.

6.1. Updating the OS and HA cluster components
Copy link

Please refer to Recommended Practices for Applying Software Updates to a RHEL High Availability or Resilient Storage Cluster, for more information.

6.2. Updating the SAP HANA instances
Copy link

Procedure

If the HA cluster configuration described in this document manages the SAP HANA System Replication setup, then you need to execute some additional steps apart from the actual process of updating the SAP HANA instances before and after the update. Execute the following steps:

  1. Put the SAPHana resource in unmanaged mode: 

    [root]# pcs resource unmanage SAPHana_RH1_HDB10-clone
    Copy to Clipboard Toggle word wrap
  2. Update the SAP HANA instances using the procedure that SAP provides.

  3. Refresh the status of the SAPHana resource to make sure the cluster is aware of the current state of the SAP HANA System Replication setup when the update of the SAP HANA instances has been completed and it has been verified that SAP HANA System Replication is working again: 

    [root]# pcs resource refresh SAPHana_RH1_HDB10-clone
    Copy to Clipboard Toggle word wrap

  4. Put the SAPHana resource back into managed mode so that the HA cluster will be able to react to any issues in the SAP HANA System Replication setup again when the HA cluster correctly picks up the current status of the SAP HANA System Replication setup: 

    [root]# pcs resource manage SAPHana_RH1_HDB10-clone
    Copy to Clipboard Toggle word wrap

A manual takeover of SAP HANA System Replication can be triggered by moving the promotable clone resource: 

[root]# pcs resource move SAPHana_RH1_HDB10-clone
Copy to Clipboard Toggle word wrap

See Moving a resource from its current node in the Configuring and managing high availability clusters document for more information. In RHEL 9, you no longer have to remove the location constraint created with the pcs resource move command because it is automatically removed when the resource move is finished.

Note

What happens to the former SAP HANA primary instance after the takeover has been completed and the constraint has been removed depends on the setting of the AUTOMATED_REGISTER parameter of the SAPHana resource:

  • If Automated_REGISTER=true, then the former SAP HANA primary instance is registered as the new secondary, and SAP HANA System Replication becomes active again.
  • If AUTOMATED_REGISTER=false, then it is up to the operator to decide what should happen with the former SAP HANA primary instance after the takeover.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

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.

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

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

Theme

© 2026 Red Hat