SUSE Cluster Support for SAP HANA System Replication Active / Active Read Enabled Feature
This document (7023884) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension
Situation
With the release of SAP HANA version 2.0, there is a new option in HANA System Replication ( HSR in the following) to free up CPU resources by using a secondary SAP HANA node with a 'read enabled' feature.
SAP HANA allows SAP Applications to read data not only from the primary SAP HANA node, but also from a secondary SAP HANA node, which is usually part of your system landscape as part of the high-availability scenario.
The question often arises about how to manage this feature in an SUSE High Availability Cluster, often used to manage the HA and business continuity requirements.
SAP HANA allows SAP Applications to read data not only from the primary SAP HANA node, but also from a secondary SAP HANA node, which is usually part of your system landscape as part of the high-availability scenario.
The question often arises about how to manage this feature in an SUSE High Availability Cluster, often used to manage the HA and business continuity requirements.
Resolution
Firstly, this is a supported configuration within a SUSE HAE cluster. However, in order to take advantage of this capability within the Cluster, some minor reconfiguration will be needed.
Assumptions to proceed with this description:
- Having a fully configured SUSE HAE Cluster Managing the SAP HANA DATABASE and the HSR.
- Having configured the Read Enable Feature in HSR
Additional Cluster Resources:
The introduction of an additional resource IP address is required. There is also the need for a constraint to bind the IP address to the slave/secondary instance of HANA within the cluster.
The following is an example that has to be changed according to the resource naming in the cluster:
crm configure primitive rsc_ip_hanasecondary_ip2 IPaddr2 \
op monitor interval=10s timeout=20s \
params ip=x.x.x.x
colocation col_sap_secondary 4000: rsc_ip_hanasecondary_ip2:Started msl_SAPHana_HDB00:Slave
Assumptions to proceed with this description:
- Having a fully configured SUSE HAE Cluster Managing the SAP HANA DATABASE and the HSR.
- Having configured the Read Enable Feature in HSR
Additional Cluster Resources:
The introduction of an additional resource IP address is required. There is also the need for a constraint to bind the IP address to the slave/secondary instance of HANA within the cluster.
The following is an example that has to be changed according to the resource naming in the cluster:
crm configure primitive rsc_ip_hanasecondary_ip2 IPaddr2 \
op monitor interval=10s timeout=20s \
params ip=x.x.x.x
colocation col_sap_secondary 4000: rsc_ip_hanasecondary_ip2:Started msl_SAPHana_HDB00:Slave
Additional Information
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7023884
- Creation Date: 15-May-2019
- Modified Date:03-Mar-2020
-
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
