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

Updated -

Red Hat Insights can detect this issue

Proactively detect and remediate issues impacting your systems.
View matching systems and remediation

Contents

Overview

Applicable Environments

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 the 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 and SAP HANA deployments may be dependent upon some input or deliverable from SAP in cases where the issue cannot be adequately solved 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

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's 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
  • IBM Power Virtual Server

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.

Minimum supported releases of resource-agents-sap-hana package for managing SAP HANA Scale-Up System Replication per RHEL release

RHEL7.x (HANA 1.0, HANA 2.0)

  • 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, ppc64le) (HANA 2.0 SPS05 revision 55 and newer): resource-agents-sap-hana-0.154.0-2.el8_4.1
  • RHEL 8.6 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.04 and HANA 2.0 SPS06 revision 63 and newer): resource-agents-sap-hana-0.162.1-0.el8_6.1
  • RHEL 8.8 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.08 and HANA 2.0 SPS06 revision 67.01 and newer): resource-agents-sap-hana-0.162.1-2.el8_8
  • RHEL 8.10 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.08 and HANA 2.0 SPS06 revision 67.01 and newer): resource-agents-sap-hana-0.162.3-1.el8_10

RHEL9.x (HANA 2.0)

  • RHEL 9.0 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.04 and HANA 2.0 SPS06 revision 63 and newer): resource-agents-sap-hana-0.162.1-0.el9_0.1
  • RHEL 9.2 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.04 and HANA 2.0 SPS06 revision 63 and newer): resource-agents-sap-hana-0.162.1-2.el9_2

Minimum supported releases of resource-agents-sap-hana-scaleout package for managing SAP HANA Scale-Out System Replication per RHEL release

RHEL7.x (HANA 1.0, HANA 2.0)

  • 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, ppc64le) (HANA 2.0 SPS05 revision 55 and newer): resource-agents-sap-hana-scaleout-0.180.0-0.el8_4.3
  • RHEL 8.6 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.02 and HANA 2.0 SPS06 revision 63 and newer): resource-agents-sap-hana-scaleout-0.180.0-4.el8
  • RHEL 8.8 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.08 and HANA 2.0 SPS06 revision 67.01 and newer): resource-agents-sap-hana-scaleout-0.180.0-4.el8
  • RHEL 8.10 (x86_64, ppc64le) (HANA 2.0 SPS05 revision 59.08 and HANA 2.0 SPS06 revision 67.01 and newer): resource-agents-sap-hana-scaleout-0.180.0-4.el8

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 the tertiary SAP HANA instance is not managed by the HA cluster. The tertiary HANA instance running outside of the cluster must be registered manually and re-registered after each takeover.

Multitarget System Replication is supported for SAP HANA Scale-Up and SAP HANA Scale-Out System Replication HA setups if the additional secondary sites(one or more) are not managed by the cluster.
For SAP HANA Scale-Up Multitarget System Replication HA setups to work correctly at least version 0.162.1 of the resource-agents-sap-hana package is required.
For SAP HANA Scale-Out Multitarget System Replication HA setups to work correctly at least version 0.185.3-0 of the resource-agents-sap-hana-scaleout package is required.
Please take a look at Configuring SAP HANA Scale-Up Multitarget System Replication for disaster recovery for further details.

Additional technical requirements for SAP HANA System Replication HA deployments

The following conditions apply for Red Hat to provide support:

  • For HANA Scale-Up System Replication environments only 2-Node clusters are supported
  • For HANA Scale-Out System Replication environments a minimum of 5 cluster nodes (4 nodes to manage 2 HANA instances per site plus the majoritymaker cluster node) and Up To 31 cluster nodes (30 cluster nodes managing 15 HANA instances per site plus the majoritymaker node) are supported.
    As mentioned here the RHEL versions where the maximum number of cluster nodes was less then 32 are all out of support.
  • 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)
  • Each cluster node must have a local installation of SAPHostAgent and the version of SAPHostAgent across the cluster must be the same (SAPHostAgent is automatically installed with the HANA installation, if not already installed)

The following additional conditions apply for Red Hat to provide support for Cost-Optimized SAP HANA Scale-Up System Replication environment:

  • The DEV/QA SAP HANA Instance running on the cluster node where the secondary production HANA instance is running must have an SID that is different from the Production Instances

Comments