diff --git a/adoc/SLES4SAP-hana-angi-perfopt-15.adoc b/adoc/SLES4SAP-hana-angi-perfopt-15.adoc index 6e36daeb..669c66b0 100644 --- a/adoc/SLES4SAP-hana-angi-perfopt-15.adoc +++ b/adoc/SLES4SAP-hana-angi-perfopt-15.adoc @@ -392,6 +392,10 @@ Linux cluster. memory can be used, as long as they are transparent to Linux HA. * No manual actions must be performed on the {HANA} database while it is controlled by the Linux cluster. All administrative actions need to be aligned with the cluster. +* No firewall rules must block any needed port. +* No SELinux rules must block any needed action. +* Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-up +scenarios require both sites prepared for running the primary {HANA} database. // TODO PRIO3: align with manual pages SAPHanaSR(7) and susHanaSR.py(7) For the HA/DR provider hook scripts _susHanaSR.py_ and _susTkOver.py_, the following @@ -407,7 +411,6 @@ _crm_attribute_. * The hook provider needs to be added to the {HANA} global configuration, in memory and on disk (in persistence). - For the HA/DR provider hook script _susChkSrv.py_, the following requirements apply: * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged() diff --git a/adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc b/adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc index da50902a..5fd49cc1 100644 --- a/adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc +++ b/adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc @@ -413,11 +413,15 @@ However, all nodes in one Linux cluster need to use the same style. *off*. * The replication mode should be either 'sync' or 'syncmem'. 'async' is supported outside the Linux cluster. +* No firewall rules must block any needed port. +* No SELinux rules must block any needed action. +* Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-out + scenarios require both sites prepared for running the primary {HANA} database. * {HANA} 2.0 SPS05 rev.059.04 and later provides Python 3 and the HA/DR provider hook method srConnectionChanged() with needed parameters for _susHanaSR.py_. * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged() with needed parameters for susChkSrv.py. -* {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with +* {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with multi-target aware parameters and separate return code for Linux HA clusters. * No other HA/DR provider hook script should be configured for the above mentioned methods. Hook scripts for other methods, provided in SAPHanaSR-angi, can be used in parallel, diff --git a/adoc/SLES4SAP-hana-scaleOut-PerfOpt-15.adoc b/adoc/SLES4SAP-hana-scaleOut-PerfOpt-15.adoc index 5ca2428b..99d89051 100644 --- a/adoc/SLES4SAP-hana-scaleOut-PerfOpt-15.adoc +++ b/adoc/SLES4SAP-hana-scaleOut-PerfOpt-15.adoc @@ -393,11 +393,15 @@ However, all nodes in one Linux cluster have to use the same style. _sapinit_ auto-start. * The replication mode should be either 'sync' or 'syncmem'. But 'async' is not supported. +* No firewall rules must block any needed port. +* No SELinux rules must block any needed action. +* Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-out + scenarios require both sites prepared for running the primary {HANA} database. * {HANA} 2.0 SPS05 rev.059 and later provides Python 3 as well as the HA/DR provider hook method srConnectionChanged() with needed parameters for SAPHanaSrMultiTarget.py. * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged() with needed parameters for susChkSrv.py. -* {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with +* {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with multi-target aware parameters and separate return code for Linux HA clusters. * No other HA/DR provider hook script should be configured for the above mentioned methods. Hook scripts for other methods, provided in SAPHanaSR-ScaleOut, can be used in parallel, diff --git a/adoc/SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc b/adoc/SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc index a323c101..95e2e0c4 100644 --- a/adoc/SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc +++ b/adoc/SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc @@ -408,11 +408,15 @@ However, all nodes in one Linux cluster have to use the same style. *off*. * The replication mode should be either 'sync' or 'syncmem'. 'async' is supported outside the Linux cluster. +* No firewall rules must block any needed port. +* No SELinux rules must block any needed action. +* Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-out + scenarios require both sites prepared for running the primary {HANA} database. * {HANA} 2.0 SPS05 rev.059 and later provides Python 3 as well as the HA/DR provider hook method srConnectionChanged() with needed parameters for SAPHanaSrMultiTarget.py. * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged() with needed parameters for susChkSrv.py. -* {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with +* {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with multi-target aware parameters and separate return code for Linux HA clusters. * No other HA/DR provider hook script should be configured for the above mentioned methods. Hook scripts for other methods, provided in SAPHanaSR-ScaleOut, can be used in parallel, @@ -424,6 +428,7 @@ However, all nodes in one Linux cluster have to use the same style. _SAPHanaSR-hookHelper_. * For optimal automation, _AUTOMATED_REGISTER="true"_ is recommended. + [IMPORTANT] ==== As good starting configuration for projects, it is recommended to *switch off* diff --git a/adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc b/adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc index ccfb0123..6787c75c 100644 --- a/adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc +++ b/adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc @@ -423,6 +423,10 @@ Linux cluster. memory can be used, as long as they are transparent to Linux HA. * No manual actions must be performed on the {HANA} database while it is controlled by the Linux cluster. All administrative actions need to be aligned with the cluster. +* No firewall rules must block any needed port. +* No SELinux rules must block any needed action. +* Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-up +scenarios require both sites prepared for running the primary {HANA} database. // TODO PRIO3: align with manual pages SAPHanaSR(7) and SAPHanaSR.py(7) For the HA/DR provider hook scripts SAPHanaSR.py and susTkOver.py, the following diff --git a/adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc b/adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc index be7d851a..bdd083fb 100644 --- a/adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc +++ b/adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc @@ -393,8 +393,23 @@ _{refsidadm}_ is not allowed to terminate the processes of the other tenant user scenario. Hence, only one replicating database pair and one non-replicating database in the same cluster as described in this guide are supported for the cost-optimized scenario. +* RA and srHook runtime almost completely depends on call-outs to controlled +resources, OS and Linux cluster. The infrastructure needs to allow these call-outs +to return in time. +* Colocation constraints between the SAPHanaController or SAPHana RA and other +resources are allowed only if they do not affect the RA's scoring. The location +scoring finally depends on system replication status and must not be overruled by +additional constraints. Thus it is not allowed to define rules forcing an SAPHanaController +or SAPHana master to follow another resource. +* Reliable access to the /hana/shared/ file system is crucial for {HANA} and the +Linux cluster. +* {HANA} feature Secondary Time Travel is not supported. * No manual actions must be performed on the {HANA} database while it is controlled by the Linux cluster. All administrative actions need to be aligned with the cluster. +* No firewall rules must block any needed port. +* No SELinux rules must block any needed action. +* Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-up +scenarios require both sites prepared for running the primary {HANA} database. The {SLES4SAP} versions are: