alarmbta.blogg.se

This article does NOT cover preparation of a RHEL system for SAP HANA installation nor the SAP HANA installation procedure. This article describes how to configure Automated HANA System Replication in Scale-Up in a Pacemaker cluster on supported RHEL releases. Testing the manual move of SAPHana resource to another node (SAP Hana takeover by cluster) 4.8.2 Creating location constraints to ensure that the secondary virtual IP address is placed on the right cluster node.Creating the resource for managing the secondary virtual IP address Adding a secondary virtual IP address for an Active/Active (Read-Enabled) HANA System Replication setup constraint - colocate the IPaddr2 resource with Master of SAPHana resource

constraint - start SAPHanaTopology before SAPHana

Activate the srConnectionChanged() hook on all SAP HANA instances Verify that a version of the resource-agents-sap-hana package is installed that provides the components to enable the srConnectionChanged() hook Enable the SAP HANA srConnectionChanged() hook Install resource agents and other components required for managing SAP HANA Scale-Up System Replication using the RHEL HA Add-On Configuring SAP HANA in a pacemaker cluster Store monitoring user credentials on all nodes Configuring monitoring account in SAP HANA for cluster resource agents (SAP HANA 1.0 SPS12 and earlier) Checking SAP HANA System Replication state On-Premise or Bring Your Own Subscription through Cloud Access