Red Hat SummitAppendix A. Component options
A.1. HA/DR provider options for SAPHanaSR
Parameters that are available for the configuration of the SAPHanaSR HA/DR provider are shown below:
| Provider options | Required | Default | Description |
|---|---|---|---|
|
| yes |
The provider parameter must be set to the hook script name without the | |
|
| yes | The full path to the location of the hook script. | |
|
| yes |
Set to |
A.2. HA/DR provider options for ChkSrv
Parameters that are available for the configuration of the ChkSrv HA/DR provider are shown below:
| Provider options | Required | Default | Description |
|---|---|---|---|
|
| yes |
The provider parameter must be set to the hook script name without the | |
|
| yes | The full path to the location of the hook script. | |
|
| yes |
Set to | |
|
| no | ignore | Action to be triggered when a lost indexserver is identified.
|
|
| no | 9 |
The signal that is used with the |
|
| no | 20s |
How many seconds to wait for the |
A.3. SAPHanaTopology resource parameters
Parameters that are available for the configuration of SAPHanaTopology resources are shown below:
| Resource options | Required | Default | Description |
|---|---|---|---|
|
| yes | SAP system identifier. | |
|
| yes | Number of the SAP HANA instance. | |
|
| no | 120 |
Defines the timeout - how long a call to HANA to receive information can take, for example, when the resource agent executes If you increase the timeout for HANA calls of this resource you must also consider increasing the operation timeout values of the same resource. |
A.4. SAPHanaController resource parameters
Parameters that are available for the configuration of SAPHanaController resources are shown below:
| Resource options | Required | Default | Description |
|---|---|---|---|
|
| yes | SAP system identifier. | |
|
| yes | Number of the SAP HANA instance. | |
|
| no |
The fully qualified path to binaries such as SAP standard paths are searched by default. | |
|
| no | The fully qualified path to the SAP START profile. Specify this parameter if you have changed the SAP profile directory location after the default SAP installation. SAP standard paths are searched by default. | |
|
| no | 120 |
Defines the timeout - how long a call to HANA to receive information can take, for example, when the resource agent runs If you increase the timeout for HANA calls of this resource you must also consider increasing the operation timeout values of the same resource. |
|
| no | The name of the SAP HANA instance profile. Specify this parameter if you have changed the name of the SAP HANA instance profile after the default SAP installation. SAP standard paths are searched by default. | |
|
| no | false |
Defines whether the resource agent should prefer to trigger takeover to the secondary site instead of restarting the primary site locally. However, a takeover is only triggered if the SAP HANA landscape status is on
|
|
| no | false |
Defines whether the resource agent automatically registers a former primary instance as a secondary during cluster resource start and if the
|
|
| no | 7200 |
The time difference required between two primary time stamps (LPTs), in case a dual-primary situation occurs. If the difference between both nodes' last primary time stamps is less than
How the recovery proceeds after the |
We recommend that you set PREFER_SITE_TAKEOVER to true. This allows the HA cluster to trigger a takeover when a failure of the primary HANA instance is detected. In most cases it takes less time for the new HANA primary instance to become fully active after a takeover, than it takes for the original primary instance to restart and reload all data back from disk into memory.
Leave AUTOMATED_REGISTER set to false to give the operator the option to first verify the health and data consistency of the previously failed primary instance, before you manually register it as the new secondary instance to re-establish the HANA system replication between both instances and manually start the instance.
Set AUTOMATED_REGISTER to true to enable the automatic registration of the former primary instance as the new secondary after a takeover occurs. This increases the availability of the HANA system replication setup and prevents so-called dual-primary situations in the SAP HANA system replication environment.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}