Review the product documentation for SUSE Linux Enterprise High Availability Extension regarding those recommendations.Īutomated registration of a failed primary after takeover is available. Of particular concern is the network latency and recommended maximum distance between the nodes. The environment must match the requirements of the SLE HAE cluster product. If the cluster nodes are installed in different AWS Availability Zones,
Time synchronization between the cluster nodes like NTP is required.īoth SAP HANA instances (primary and secondary) have the same SAP Identifier (SID) and instance number. Name resolution of the cluster nodes and the virtual IP address must be done locally on all cluster nodes. Technical users and groups, such as adm, are defined locally in the Linux system. The Overlay IP address must be an IP outside the Virtual Private Cloud (VPC) CIDR. The AWS EC2 STONITH mechanism supported by SUSE Linux Enterprise High Availability Extension 12 is supported with SAPHanaSR.Įach cluster node is in a different Availability Zone (AZ) within the same AWS Region. Will also automatically register a former failed primary to get the new If automated registration is activated, the cluster You can set up the level of automation by setting the parameterĪUTOMATED_REGISTER. The cluster continues to poll the system replication status on a regular basis. If the SAP HANA system replication breaks. SAP HANA hook described in this document allows to inform the cluster immediately To include such SAP HANA hooks to optimize the cluster interface. Implementing SAP HANA hooks written in python. These call outs are also called HA/DR providers. These improvements also include the implementation of SAP HANAĬall outs in case of special events such as status changes for services or system replicationĬhannels.
SAP did improve the interfaces between SAP HANA and external software such asĬluster frameworks. This ensures that the last commits processed on the primary site are System replication was in sync until the point when the service of the primary The cluster only allows a takeover to the secondary site if the SAP HANA Productive database is automated with SAPHana and SAPHanaTopology. SAP HANA resource agents included in SAPHanaSR. To achieve an automation of this resource handling process, use the Use the already loaded data at the secondary site. Instance), the cluster first tries to start the takeover process.
In case of failure of the primary SAP HANA on node 1 (node or database SUSE LLC, its affiliates, the authors, and the translators may not be held liable for possible errorsġ.1.4 The Concept of the Performance Optimized Scenario # In these documents do what is claimed or whether actions described have unintended consequences. SUSE cannot verify that actions described However, this does not guarantee complete accuracy. They have been compiled with utmost attention to detail. They are meant to serve as examples of how particularĪctions can be performed.
This document is based on SUSE Linux Enterprise Serverĭocuments published as part of the SUSE Best Practices series have been contributed voluntarilyīy SUSE employees and third parties. Installed and working SAP HANA with system replication. The document focuses on the steps to integrate an already Linux Enterprise Server for SAP Applications for SAP HANA system replication in the performance This guide provides detailed information about installing and customizing SUSE SUSE® Linux Enterprise Server for SAP Applications is optimized in various ways for SAP*Īpplications.