SLES4SAP-hana-angi-perfopt-15.adoc SLES4SAP-hana-sr-guide-PerfOpt-15.…

…adoc SLES4SAP-hana-sr-guide-costopt-15.adoc: aligned string <multi-state-resource> in examples
SUSE · Mar 26, 2024 · b201af0 · b201af0
1 parent 433e237
commit b201af0
Show file tree

Hide file tree

Showing 3 changed files with 21 additions and 27 deletions.
diff --git a/adoc/SLES4SAP-hana-angi-perfopt-15.adoc b/adoc/SLES4SAP-hana-angi-perfopt-15.adoc
@@ -2884,7 +2884,7 @@ format script you can define effective queries:
 
 [subs="attributes,quotes"]
 ----
-{sapnode1}:~ # SAPHanaSR-showAttr --format=script | grep remote
+{sapnode1}:~ # SAPHanaSR-showAttr --format=script | grep "/remoteHost="
 Thu Feb  6 12:28:10 2020; Hosts/{sapnode1}/remoteHost={sapnode2}
 Thu Feb  6 12:28:10 2020; Hosts/{sapnode2}/remoteHost={sapnode1}
 ----
@@ -2895,16 +2895,14 @@ Thu Feb  6 12:28:10 2020; Hosts/{sapnode2}/remoteHost={sapnode1}
 In our example, the administrator killed the primary {HANA} instance using the command
 `HDB kill-9`. This happened around 9:10 pm.
 
-// TODO PRIO1: replace SAPHanaSR-filter
 [subs="attributes,quotes"]
 ----
 {sapnode1}:~ # hb_report -f 19:00
 INFO: {sapnode1}# The report is saved in ./hb_report-1-11-11-2019.tar.bz2
 INFO: {sapnode1}# Report timespan: 11/11/19 19:00:00 - 11/11/19 21:05:33
 INFO: {sapnode1}# Thank you for taking time to create this report.
 {sapnode1}:~ # SAPHanaSR-replay-archive --format=script \
-    ./hb_report-1-11-11-2019.tar.bz2 | \
-    SAPHanaSR-filter --search='roles' --filterDouble
+    ./hb_report-1-11-11-2019.tar.bz2 | grep "/roles="
 Mon Nov 11 20:38:01 2019; Hosts/{sapnode1}/roles=4:P:master1:master:worker:master
 Mon Nov 11 20:38:01 2019; Hosts/{sapnode2}/roles=4:S:master1:master:worker:master
 Mon Nov 11 21:11:37 2019; Hosts/{sapnode1}/roles=1:P:master1::worker:
@@ -3051,7 +3049,7 @@ cluster node.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource maintenance <multi-state-resource-name>
+# crm resource maintenance <multi-state-resource>
 ----
 
 // TODO PRIO2: Check -sr_takeover with 'handshake'
@@ -3103,15 +3101,15 @@ cluster node as user root.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource refresh <multi-state-resource-name>
+# crm resource refresh <multi-state-resource>
 ----
 +
 * Set the multi-state resource to the status managed again. The command
 can be submitted on any cluster node as user root.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource maintenance <multi-state-resource-name> off
+# crm resource maintenance <multi-state-resource> off
 ----
 ==============================
 
@@ -3124,7 +3122,7 @@ migration.
 +
 [subs="attributes,specialchars,quotes"]
 ----
-# crm resource move <multi-state-resource-name> *force*
+# crm resource move <multi-state-resource> *force*
 ----
 +
 Because of the "move away" (*force*) rule, the cluster will *stop* the
@@ -3139,11 +3137,9 @@ former primary to be stopped. Only the migration with *force* option is supporte
   see this using the command line tool `SAPHanaSR-showAttr`. Now check for the
   attributes "roles" for the new primary. It must start with "*4:P*".
 +
-// TODO PRIO1: replace SAPHanaSR-filter
 [subs="specialchars,attributes,quotes"]
 ----
-{sapnode1}:~ # SAPHanaSR-showAttr --format=script | \
-   SAPHanaSR-filter --search='roles'
+{sapnode1}:~ # SAPHanaSR-showAttr --format=script | grep "/roles="
 Mon Jun 21 19:38:50 2021; Hosts/{sapnode1}/roles=*1:P*:master1::worker:
 Mon Jun 21 19:38:50 2021; Hosts/{sapnode2}/roles=*4:P*:master1:master:worker:master
 ----
@@ -3163,19 +3159,17 @@ in our example on node1 as user _{refsidadm}_.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource clear <multi-state-resource-name>
+# crm resource clear <multi-state-resource>
 ----
 +
 
 * Wait until the new secondary has started. You
   see this using the command line tool `SAPHanaSR-showAttr` and check for the
   attributes "roles" for the new primary. It must start with "*4:S*".
 +
-// TODO PRIO1: replace SAPHanaSR-filter
 [subs="specialchars,attributes,quotes"]
 ----
-{sapnode1}:~ # SAPHanaSR-showAttr --format=script | \
-   SAPHanaSR-filter --search='roles'
+{sapnode1}:~ # SAPHanaSR-showAttr --format=script | grep "/roles="
 Mon Jun 21 19:38:50 2021; Hosts/{sapnode1}/roles=*4:S*:master1::worker:
 Mon Jun 21 19:38:50 2021; Hosts/{sapnode2}/roles=*4:P*:master1:master:worker:master
 ----

diff --git a/adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc b/adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc
@@ -3061,7 +3061,7 @@ cluster node.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource maintenance <multi-state-resource-name>
+# crm resource maintenance <multi-state-resource>
 ----
 
 // TODO PRIO2: Check -sr_takeover with 'handshake'
@@ -3113,15 +3113,15 @@ cluster node as user root.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource refresh multi-state-resource-name
+# crm resource refresh <multi-state-resource>
 ----
 +
 * Set the multi-state resource to the status managed again. The command
 can be submitted on any cluster node as user root.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource maintenance <multi-state-resource-name> off
+# crm resource maintenance <multi-state-resource> off
 ----
 ==============================
 
@@ -3135,7 +3135,7 @@ migration. For the described attribute query using `SAPHanaSR-showAttr` and
 +
 [subs="attributes,specialchars,quotes"]
 ----
-# crm resource move <multi-state-resource-name> *force*
+# crm resource move <multi-state-resource> *force*
 ----
 +
 Because of the "move away" (*force*) rule, the cluster will *stop* the
@@ -3176,7 +3176,7 @@ in our example on node1 as user _{refsidadm}_.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource clear <multi-state-resource-name>
+# crm resource clear <multi-state-resource>
 ----
 +
 NOTE: The crm resource command *clear* was previously named *unmigrate*. The *unmigrate*

diff --git a/adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc b/adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc
@@ -3337,7 +3337,7 @@ cluster node.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource maintenance <multi-state-resource-name>
+# crm resource maintenance <multi-state-resource>
 ----
 
 // TODO PRIO2: Check -sr_takeover with 'handshake'
@@ -3389,15 +3389,15 @@ cluster node as user root.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource refresh <multi-state-resource-name>
+# crm resource refresh <multi-state-resource>
 ----
 +
 * Set the multi-state resource to the status managed again. The command
 can be submitted on any cluster node as user root.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource maintenance <multi-state-resource-name> off
+# crm resource maintenance <multi-state-resource> off
 ----
 ==============================
 
@@ -3411,7 +3411,7 @@ migration. For the described attribute query using `SAPHanaSR-showAttr` and
 +
 [subs="attributes,specialchars,quotes"]
 ----
-# crm resource move <multi-state-resource-name> *force*
+# crm resource move <multi-state-resource> *force*
 ----
 +
 Because of the "move away" (*force*) rule, the cluster will *stop* the
@@ -3452,7 +3452,7 @@ in our example on node1 as user _{refsidadm}_.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource clear <multi-state-resource-name>
+# crm resource clear <multi-state-resource>
 ----
 +
 NOTE: The crm resource command *clear* was previously named *unmigrate*. The *unmigrate*
@@ -3518,15 +3518,15 @@ preload_column_tables = false
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource move <multi-state-resource-name> force
+# crm resource move <multi-state-resource> force
 ----
 
 * Wait until the cluster has finished the transition and is idle.
 Then remove the migration constraint from CIB.
 +
 [subs="specialchars,attributes,quotes"]
 ----
-# crm resource clear <multi-state-resource-name>
+# crm resource clear <multi-state-resource>
 ----
 ==============================