SAPHanaSR-angi - SAP HANA System Replication
A Next Generation Interface
A Next Generation Interface
The SUSE resource agents to control the SAP HANA database in system replication setups
Introduction
SAPHanaSR-angi is "SAP HANA SR - An Next Generation Interface" for SUSE high availabilty clusters to manage SAP HANA databases with system replication. It provides an automatic failover between SAP HANA nodes with configured System Replication in HANA. The current version of SAPHanaSR-angi is targeting SAP HANA SR scale-up and scale-out setups.
CIB attributes are not backward compatible between SAPHanaSR-angi and the classic SAPHanaSR. Nevertheless, SAPHanaSR and SAPHanaSR-ScaleOut can be upgraded to SAPHanaSR-angi by following the documented procedure.
This technology is included in the SUSE Linux Enterprise Server for SAP Applications 15, via the RPM package with the same name.
System replication will help to replicate the database data from one node to another node in order to compensate for database failures. With this mode of operation, internal SAP HANA high-availability (HA) mechanisms and the Linux cluster have to work together.
The SAPHanaController resource agent performs the actual check of the SAP HANA database instances and is configured as a promotable multi-state resource. Managing the two SAP HANA instances means that the resource agent controls the start/stop of the instances. In addition the resource agent is able to monitor the SAP HANA databases on landscape host configuration level.
For this monitoring the resource agent relies on interfaces provided by SAP.
As long as the HANA landscape status is not "ERROR" the Linux cluster will not act. The main purpose of the Linux cluster is to handle the takeover to the other site.
Only if the HANA landscape status indicates that HANA can not recover from the failure and the replication is in sync, then Linux will act.
An important task of the resource agent is to check the synchronisation status of the two SAP HANA databases. If the synchronisation is not "SOK", then the cluster avoids to take over to the secondary side, if the primary fails. This is to improve the data consistency.
For more information, refer to the "Supported High Availability Solutions by SLES for SAP Applications" and all the manual pages shipped with the package.
For SAP HANA Databases in System Replication only the listed scenarios at "Supported High Availability Solutions by SLES for SAP Applications" are supported. For any scenario not matching the scenarios named or referenced in our setup guides please contact SUSE services.
The following SUSE blog series gives a good overview about running SAP HANA in System Replication in the SUSE cluster: "towardszerodowntime"
File structure of installed package
/usr/share/SAPHanaSR-angi/doccontains readme and license;/usr/share/manand it's subdirectories contains manual pages;/usr/lib/ocf/resource.d/susecontains the actual resource agents,SAPHanaControllerandSAPHanaTopology;/usr/lib/SAPHanaSR-angicontains the libraries for the resource agents;/usr/share/SAPHanaSR-angicontains SAP HA/DR provider hook scripts;/usr/share/SAPHanaSR-angi/samplescontains examples for global ini configuration and various additional stuff;/usr/bincontains tools;
License
See the LICENSE file for license rights and limitations.
Contributing
If you are interested in contributing to this project, read the CONTRIBUTING.md for more information.
Feedback
Do you have suggestions for improvement? Let us know!
Go to Issues, create a new issue and describe what you think could be improved.
Feedback is always welcome!
Development and Branches
Please read development.md for more information.