SLES4SAP-hana-angi-perfopt-15.adoc SLES4SAP-hana-angi-scaleout-perfop…

…t-15.adoc SLES4SAP-hana-scaleOut-PerfOpt-15.adoc SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc SLES4SAP-hana-sr-guide-PerfOpt-15.adoc SLES4SAP-hana-sr-guide-costopt-15.adoc: requirements, dos and don´ts

adoc/SLES4SAP-hana-angi-perfopt-15.adoc

@@ -390,6 +390,8 @@ Linux cluster.
 * {HANA} feature Secondary Time Travel is not supported.
 * The {HANA} Fast Restart feature on RAM-tmfps and {HANA} on persistent
 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.
 
 // 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
@@ -2844,7 +2846,8 @@ manually re-registering a site.
 rules mentioned in this setup guide are allowed. For public cloud refer to the
 cloud specific documentation.
 * Using {SAP} tools for attempting start/stop/takeover actions on a database
-while the cluster is in charge of managing that database.
+while the cluster is in charge of managing that database. Same for unregistering/disabling
+system replication.
 
 IMPORTANT: As "migrating" or "moving" resources in crm-shell, HAWK or other
 tools would add client-prefer location rules, support is limited to maintenance
@@ -3557,4 +3560,6 @@ include::common_gfdl1.2_i.adoc[]
 //
 // REVISION 0.1 2024/04
 //   - Initial version
+// REVISION 0.2 2024/09
+//      - updated requirements, dos and don´ts
 //

adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc

@@ -453,6 +453,8 @@ See also manual page susHanaSR.py(7).
   or it can be upgraded as described in respective documentation.
   Not allowed is mixing old and new cluster attributes or hook scripts within
   one cluster.
+* 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.
 
 Find more details in the REQUIREMENTS section of manual pages
 SAPHanaSR-ScaleOut(7), ocf_suse_SAPHanaController(7), ocf_suse_SAPHanaFilesystem(7),
@@ -2958,6 +2960,10 @@ In your project, *avoid* the following:
 * Adding location rules for the clone, multi-state or IP resource. Only
   location rules mentioned in this setup guide are allowed.
 
+* Using {SAP} tools for attempting start/stop/takeover actions on a database
+  while the cluster is in charge of managing that database. Same for unregistering/disabling
+  system replication.
+
 * As "migrating" or "moving" resources in _crm-shell_, HAWK or other tools would
   add client-location rules, these activities are completely forbidden!
 
@@ -3242,4 +3248,6 @@ include::common_gfdl1.2_i.adoc[]
 //
 // REVISION 0.1 (2024-05-27)
 //	- copied from classic scale-out multi-target
+// REVISION 0.2 (2024-09-20)
+//	- updated requirements, dos and don´ts
 //

adoc/SLES4SAP-hana-scaleOut-PerfOpt-15.adoc

@@ -407,6 +407,8 @@ However, all nodes in one Linux cluster have to use the same style.
   or it can be upgraded as described in respective documentation.
   Not allowed is mixing old and new cluster attributes or hook scripts within
   one Linux cluster.
+* 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.
 
 Find more details in the REQUIREMENTS section of manual pages
 SAPHanaSR-ScaleOut(7), ocf_suse_SAPHanaController(7),
@@ -2483,6 +2485,10 @@ In your project, *avoid* the following:
 * Adding location rules for the clone, multi-state or IP resource. Only
   location rules mentioned in this setup guide are allowed.
 
+* Using {SAP} tools for attempting start/stop/takeover actions on a database
+  while the cluster is in charge of managing that database. Same for unregistering/disabling
+  system replication.
+
 * As "migrating" or "moving" resources in _crm-shell_, HAWK or other tools would
   add client-prefer location rules, these activities are completely *forbidden!*.
 
@@ -2766,5 +2772,7 @@ include::common_gfdl1.2_i.adoc[]
 // REVISION 0.3 (2023-04-03)
 //	- SAP native systemd support is default for HANA 2.0 SPS07
 // REVISION 0.3a (2024-02-14)
-//      - HANA 2.0 SPS05 rev.059 Python 3 needed
+//  - HANA 2.0 SPS05 rev.059 Python 3 needed
+// REVISION 0.3b (2024-09-20)
+//  - requirements, dos and don´ts
 //

adoc/SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc

@@ -445,6 +445,8 @@ See also manual page SAPHanaSrMultiTarget.py(7).
   or it can be upgraded as described in respective documentation.
   Not allowed is mixing old and new cluster attributes or hook scripts within
   one cluster.
+* 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.
 
 Find more details in the REQUIREMENTS section of manual pages
 SAPHanaSR-ScaleOut(7), ocf_suse_SAPHanaController(7),
@@ -2847,6 +2849,10 @@ In your project, *avoid* the following:
 * Adding location rules for the clone, multi-state or IP resource. Only
   location rules mentioned in this setup guide are allowed.
 
+* Using {SAP} tools for attempting start/stop/takeover actions on a database
+  while the cluster is in charge of managing that database. Same for unregistering/disabling
+  system replication.
+
 * As "migrating" or "moving" resources in _crm-shell_, HAWK or other tools would
   add client-location rules, these activities are completely *forbidden!*.
 
@@ -3131,4 +3137,6 @@ include::common_gfdl1.2_i.adoc[]
 //	- SAP native systemd support is default for HANA 2.0 SPS07
 // REVISION 0.3a (2024-02-14)
 //	- HANA 2.0 SPS05 rev.059 Python 3 needed
+// REVISION 0.3b (2024-09-20)
+//  - requirements, dos and don´ts
 //

adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc

@@ -418,6 +418,8 @@ Linux cluster.
 * {HANA} feature Secondary Time Travel is not supported.
 * The {HANA} Fast Restart feature on RAM-tmfps and {HANA} on persistent
 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.
 
 // 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
@@ -434,7 +436,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()
@@ -2790,8 +2791,8 @@ In your project, you should:
 * Define STONITH before adding other resources to the cluster.
 * Do intensive testing.
 * Tune the timeouts of operations of SAPHana and SAPHanaTopology.
-* Start with the parameter values PREFER_SITE_TAKEOVER=”true”, AUTOMATED_REGISTER=”false” and
-DUPLICATE_PRIMARY_TIMEOUT=”7200”.
+* Start with the parameter values PREFER_SITE_TAKEOVER=”true”, AUTOMATED_REGISTER=”false”
+and DUPLICATE_PRIMARY_TIMEOUT=”7200”.
 * Always wait for pending cluster actions to finish before doing something.
 * Set up a test cluster for testing configuration changes and administrative
 procedure before applying them on the production cluster.
@@ -2809,7 +2810,8 @@ manually re-registering a site.
 rules mentioned in this setup guide are allowed. For public cloud refer to the
 cloud specific documentation.
 * Using {SAP} tools for attempting start/stop/takeover actions on a database
-while the cluster is in charge of managing that database.
+while the cluster is in charge of managing that database. Same for unregistering/disabling
+system replication.
 
 IMPORTANT: As "migrating" or "moving" resources in crm-shell, HAWK or other
 tools would add client-prefer location rules, support is limited to maintenance
@@ -3537,4 +3539,6 @@ include::common_gfdl1.2_i.adoc[]
 // REVISION 1.6c 2024/03
 //	- updated references
 //	- pointer to SAPHanaSR-angi
+// REVISION 1.6d 2024/09
+//	- updated requirements, dos and don´ts
 //

adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc

@@ -390,6 +390,8 @@ _{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.
+* 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.
 
 The {SLES4SAP} versions are:
 
@@ -3049,7 +3051,8 @@ manually re-registering a site.
 rules mentioned in this setup guide are allowed. For public cloud refer to the
 cloud specific documentation.
 * Using {SAP} tools for attempting start/stop/takeover actions on a database
-while the cluster is in charge of managing that database.
+while the cluster is in charge of managing that database. Same for unregistering/disabling
+system replication.
 
 IMPORTANT: As "migrating" or "moving" resources in crm-shell, HAWK or other
 tools would add client-prefer location rules, support is limited to maintenance
@@ -3978,5 +3981,7 @@ include::common_gfdl1.2_i.adoc[]
 // REVISION 1.6 2023/04
 //   - SAP native systemd support is default for HANA 2.0 SPS07
 // REVISION 1.6b 2024/02
-//      - HANA 2.0 SPS05 rev.059 Python 3 needed
+//   - HANA 2.0 SPS05 rev.059 Python 3 needed
+// REVISION 1.6c 2024/09
+//   - requirements, dos and don´ts
 //