Support Policies for RHEL High Availability Clusters - Management of SAP HANA in a Cluster

Updated -

Contents

Overview

Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On

Useful References and Guides

Introduction

This guide offers Red Hat's policies and requirements around managing an SAP HANA deployment with a RHEL High Availability (HA) cluster. Users of RHEL High Availability clusters should adhere to these policies in order to be eligible for support from Red Hat with the appropriate product support subscriptions.

Policies

Scope of Red Hat support with SAP software resources managed by a cluster: Refer to Red Hat's policy on Management of applications that Red Hat does not ship for further details on Red Hat's scope of support applicable to SAP software deployments in a RHEL High Availability cluster.

The focus of Red Hat's assistance may be limited to functionality of the High Availability software and the SAP resource-agent(s). In some cases SAP's input may be necessary to diagnose the nature of a problem - even if the problem originates in the resource-agent Red Hat ships. Solutions to problems with RHEL High Availability + SAP HANA deployments may be dependent upon some input or deliverable from SAP in cases where the issue can not be solved adequately through RHEL High Availability without SAP's assistance.


Red Hat subscriptions for SAP HANA support: Red Hat provides support for RHEL High Availability resource-agents managing SAP HANA deployments through the following subscriptions:

  • RHEL for SAP Solutions
  • RHEL for SAP HANA (no longer sold)

One of these subscriptions for each cluster node is required in order for Red Hat to assist with RHEL High Availability management of SAP HANA.


Supported platforms for SAP HANA on RHEL High Availability

Red Hat support for its software supporting the SAP HANA solution stack for Scale-Up/Scale-Out System Replication environments including RHEL High Availability and its resource-agents for SAP software - largely follows the policies laid out for RHEL High Availability and RHEL:

See SAP Note 2235581 for certified/supported combinations of RHEL and SAP HANA releases.

For the list of x86_64 and IBM POWER servers, storage systems and cloud instance types that are certified for running SAP HANA Scale-Up and Scale-Out installations, see Certified and Supported SAP HANA® Hardware Directory.

Note that in public-cloud deployments, Red Hat's support for this SAP HANA solution stack is limited to only the following cloud platforms:

  • Amazon Web Services Elastic Cloud (AWS EC2)
  • Microsoft Azure
  • Google Cloud Platform

Other cloud provider platforms are currently not supported by Red Hat. Please contact Red Hat Support if you are interested in running SAP HANA on another cloud platform. For general information on using SAP on RHEL in cloud environments see SAP Offerings on Certified Cloud Providers.


Supported releases of resource-agents-sap-hana and versions of SAP HANA for Scale-Up systems

Note: See also SAP Note 2235581 - SAP HANA: Supported Operating Systems for SAP's list of supported OS versions for each version of HANA, along with any required HANA service pack numbers or revision numbers.

Red Hat provides support for RHEL High Availability management of the following HANA major versions:

Minimum supported version of the resource-agents-sap-hana package for each OS minor release:

RHEL6.x (HANA 1.0)

  • RHEL 6.7 (x86_64) (HANA 1.0 SPS11 and newer): resource-agents-sap-hana-3.9.5-24.el6_7.2
  • RHEL 6.10 (x86_64) (HANA 1.0 SPS12 revision 122.23 and newer): resource-agents-sap-hana-3.9.5-46.el6

RHEL7.x (HANA 1.0, HANA 2.0)

  • RHEL 7.2 (x86_64) (HANA 1.0 SPS12; up to HANA 2.0 SPS03): resource-agents-sap-hana-3.9.5-54.el7_2.22
  • RHEL 7.3 (x86_64) (HANA 1.0 SPS12; HANA 2.0 SPS02 revision 21 and newer, up to HANA 2.0 SPS03): resource-agents-sap-hana-3.9.5-82.el7_3.12
  • RHEL 7.4 (x86_64, ppc64le) (HANA 1.0 SPS12 revision 122.14 and newer; HANA 2.0 SPS02 revision 23 and newer, up to HANA 2.0 SPS04): resource-agents-sap-hana-3.9.5-105.el7_4.6
  • RHEL 7.5 (x86_64, ppc64le) (HANA 1.0 SPS12 revision 122.19 and newer; HANA 2.0 SPS03 only, starting with revision 32): resource-agents-sap-hana-3.9.5-124.el7
  • RHEL 7.6 (x86_64, ppc64le) (HANA 1.0 SPS12 revision 122.23 and newer; HANA 2.0 SPS03 revision 36 and newer): resource-agents-sap-hana-4.1.1-12.el7_6.26
  • RHEL 7.7 (x86_64, ppc64le) (HANA 1.0 SPS12 revision 122.30 and newer; HANA 2.0 SPS04 revision 48 and newer): resource-agents-sap-hana-4.1.1-30.el7_7.7
  • RHEL 7.9 (x86_64, ppc64le) (HANA 1.0 SPS12 revision 122.33 and newer; HANA 2.0 SPS05 revision 54 and newer): resource-agents-sap-hana-4.1.1-61.el7_9.4

RHEL8.x (HANA 2.0)

  • RHEL 8.0 (x86_64, ppc64le) (HANA 2.0 SPS04 only, starting with revision 40): resource-agents-sap-hana-4.1.1-17.el8_0.6
  • RHEL 8.1 (x86_64, ppc64le) (HANA 2.0 SPS04 revision 45 and newer): resource-agents-sap-hana-0.154.0-1.el8_1.1
  • RHEL 8.2 (x86_64, ppc64le) (HANA 2.0 SPS04 revision 48.02 and HANA 2.0 SPS05 revision 52 and newer): resource-agents-sap-hana-0.154.0-2
  • RHEL 8.4 (x86_64) (HANA 2.0 SPS05 revision 55 and newer): resource-agents-sap-hana-0.154.0-2.el8_4.1

Support for RHEL 8.4 on ppc64le architecture is expected to be added later, according to a support matrix on an SAP wiki.

Supported releases of resource-agents-sap-hana-scaleout and versions of SAP HANA for Scale-Out Systems

RHEL7.x (HANA 1.0, HANA 2.0)

  • RHEL 7.6 (x86_64, ppc64le) (SAP HANA 1.0 SPS12 revision 122.23 and newer; SAP HANA 2.0 SPS03 revision 36 and newer): resource-agents-sap-hana-scaleout-0.163.2-1.el7_6.5
  • RHEL 7.7 (x86_64, ppc64le) (SAP HANA 1.0 SPS12 revision 122.30 and newer; SAP HANA 2.0 SPS04 revision 48 and newer): resource-agents-sap-hana-scaleout-0.163.2-7.el7
  • RHEL 7.9 (x86_64, ppc64le) (SAP HANA 1.0 SPS12 revision 122.33 and newer; SAP HANA 2.0 SPS05 revision 54 and newer): resource-agents-sap-hana-scaleout-0.163.2-7.el7

RHEL8.x (HANA 2.0 SPS04 and newer)

  • RHEL 8.0 (x86_64, ppc64le) (HANA 2.0 SPS04 only, starting with revision 40): resource-agents-sap-hana-scaleout-0.163.2-6.el8
  • RHEL 8.1 (x86_64, ppc64le) (HANA 2.0 SPS04 revision 45 and newer): resource-agents-sap-hana-scaleout-0.164.0-0.el8_1.1
  • RHEL 8.2 (x86_64, ppc64le) (HANA 2.0 SPS04 revision 48.02 and newer, HANA 2.0 SPS05 revision 52 and newer): resource-agents-sap-hana-scaleout-0.164.0-0.el8_2.2
  • RHEL 8.4 (x86_64) (HANA 2.0 SPS05 revision 55 and newer): resource-agents-sap-hana-scaleout-0.180.0-0.el8_4.3

Supported SAP HANA deployment types

  • Single database deployments
  • MCOD (Multiple Components One Database)
  • MDC (Multiple Database containers),
  • MCOS (Multiple Components One System) is only supported if all databases running on the hosts are replicated and the replication is always to the same secondary node (for Scale-Up only)

Active/Active (Read Enabled) SAP HANA System Replication setups are possible with SAP HANA 2.0 using version 0.152.17 or later of the SAPHana, SAPHanaTopology and SAPHanaController resource agents. To enable these setups, the additional secondary IPs as well as the appropriate co-location constraint(s) will need to be added in order to manage the other IP address(es) for the requirement (Scale-Up or Scale-Out).

Multitier System Replication is supported for SAP HANA Scale-Up and SAP HANA Scale-Out System Replication HA setups, and is only possible if additional SAP HANA instances are not managed by an HA cluster. The HANA instances running outside of the cluster must be registered manually and re-registered after each takeover.

Multi-Target System Replication is supported for SAP HANA Scale-Out System Replication HA Setups. For SAP HANA Scale-Up System Replication HA setups it is only possible if additional SAP HANA instances are not managed by an HA cluster. Then the HANA instances running outside of the cluster must be registered manually and re-registered after each takeover.


Additional technical requirements for SAP HANA System Replication HA deployments

The following conditions apply for Red Hat to provide support:

  • 2-Node clusters are supported for SAP HANA Scale-Up System Replication environments.
  • Up To 16/32 node (depending on pacemaker version) clusters are supported for SAP HANA Scale-Out System Replication environments.
  • Users and groups used by SAP HANA must be identically defined on all nodes (use the same UIDs/GIDs, home directories, ...).
  • The SAP HANA instances on all nodes must be configured with the same SID..
  • Using Full Sync Replication is possible, but due to the way Full Sync Replication works some functionality of the cluster will be restricted (for example the automatic start of the HANA instances on both nodes when the cluster is started will not work and the HANA instance on the secondary node will have to be started manually for the cluster to be able to resume operation if Full Sync Replication is enabled.). To check Full Sync Replication state you can run command hdbcons -e hdbindexserver "replication info"|egrep "(ReplicationFullSync|enable_full_sync)" as SAP HANA administrative user.
  • If the cluster nodes are installed in different data centers or data center areas, the environment must match both
  • Time on all cluster nodes must be in sync (using NTP) or some other time synchronization method) - resource agents require the time to be the same on all nodes for proper operation.
  • Each cluster node must have a local installation of SAPHostAgent and the version of SAPHostAgent across the cluster must be the same. SAPHostAgent is installed with the HANA installation, if not already installed.

In Addition to the above, following conditions apply for Red Hat to provide support for Cost-Optimized SAP HANA environments.

  • 2-Node clusters only.
  • Both the production SAP HANA instances must have the same SAP Identifier (SID) and Instance-Number between which the system replication will be established. The DEV/QA SAP HANA Instance must have an SID that is different from the Production Instances.
  • hostname resolution of the cluster node names and IP addresses must be possible locally on all cluster nodes
  • The network configuration must be done according to the Red Hat guidelines for cluster setups and the SAP guidelines for SAP HANA deployments. For example, if the cluster nodes are installed in different data centers or data center areas, the environment must match both the requirements defined by SAP for HANA System Replication (see chapter "4.2 Distance between data centers" in the SAP "How to Perform System Replication for SAP HANA" guide) and also the RHEL HA add-on stretch cluster requirements (see Support for Red Hat Enterprise Linux High Availability Cluster Stretch and Multi-Site Architectures), specifically the network latencies between the nodes and the recommended maximum distance.
  • Access to the SAP Service Marketplace to be able to download SAP installation media, installation guides etc
  • Current set of SAP HANA installation media (see SAP HANA Installation Guides for the correct list of installation media)
  • The latest and the same version of SAP HOSTAGENT must be installed on all nodes (see SAP Note 1031096 - Installing Package SAPHOSTAGENT)

1 Comments

Hi , MY Redhat SAP Cluster(Rhel 8.2 , hana2sp05) configured with Scale up System between two nodes .Sync replication enabled . I have maintenance Plan on Monthly Basis. System A is Primary and System B is acting as Secondary nodes in Cluster . I dont want switch over so put cluster in Maintenance mode. Restart the primary server after Maintained of Hardware . After reboot completed i bring out the Cluster from Maintained mode . After that i have observed my system switch over and Primary is showing demoted and secondary is prompted in the cluster . is this the common behavior after system come out of maintenance mode which trigger the switch over.