Update links

msftrobiro · msftrobiro · commit 8c137aa84ef9 · 2025-05-28T10:01:54.000+02:00
diff --git a/articles/sap/workloads/disaster-recovery-sap-hana.md b/articles/sap/workloads/disaster-recovery-sap-hana.md
@@ -41,7 +41,7 @@ Requirements for additional HSR sites are different for HANA scale-up and HANA s
 - **Both scale-up and scale-out**: Maximum of one SAP HANA system replication connected from outside the Linux cluster.
 - **HANA scale-out only**: SLES 15 SP1 or higher.
 - **HANA scale-out only**: Operating system (OS) package SAPHanaSR-ScaleOut version 0.180 or higher.
-- **HANA scale-out only**: SAP HANA high-availability (HA) hook [SAPHanaSrMultiTarget](./sap-hana-high-availability-scale-out-hsr-suse.md#implement-hana-ha-hooks-saphanasrmultitarget-and-suschksrv) in use. Preview HANA HA hook `SAPHanaSR` isn't multitarget aware for scale-out.
+- **HANA scale-out only**: SAP HANA high-availability (HA) hooks [susHanaSR or SAPHanaSrMultiTarget](./sap-hana-high-availability-scale-out-hsr-suse.md#implement-hana-resource-agents) in use. Older HANA HA hook `SAPHanaSR` isn't multitarget aware for scale-out.
 
 ## Prerequisites for RHEL
 
@@ -120,7 +120,7 @@ The following example shows a multitarget system replication system. For more in
 
 ## HANA scale-out: Add HANA multitarget system replication for DR purposes
 
-With the SAP HANA HA provider [SAPHanaSrMultiTarget](./sap-hana-high-availability-scale-out-hsr-suse.md#implement-hana-ha-hooks-saphanasrmultitarget-and-suschksrv), you can add a third HANA scale-out site. This third site is often used for DR in another Azure region. The Pacemaker environment is aware of a HANA multitarget DR setup. This section applies to systems running Pacemaker on SUSE only. See the "Prerequisites" section in this document for details.
+With the SAP HANA HA providers  [susHanaSR or SAPHanaSrMultiTarget](./sap-hana-high-availability-scale-out-hsr-suse.md#implement-hana-resource-agents), you can add a third HANA scale-out site. This third site is often used for DR in another Azure region. The Pacemaker environment is aware of a HANA multitarget DR setup. This section applies to systems running Pacemaker on SUSE only. See the "Prerequisites" section in this document for details.
 
 Failure of the third node doesn't trigger any cluster action. The cluster detects the replication status of connected sites and the monitored attribute for the third site can change between the `SOK` and `SFAIL` states. Any takeover tests to the third/DR site or executing your DR exercise process should first place the cluster resources into maintenance mode to prevent any undesired cluster action.
 
diff --git a/articles/sap/workloads/sap-hana-high-availability-scale-out-hsr-suse.md b/articles/sap/workloads/sap-hana-high-availability-scale-out-hsr-suse.md
@@ -1209,121 +1209,6 @@ sudo /usr/sbin/SAPHanaSR-showAttr
 > [!NOTE]
 > The timeouts in the above configuration are just examples and may need to be adapted to the specific HANA setup. For instance, you may need to increase the start timeout, if it takes longer to start the SAP HANA database.
 
-
-
-
-
-
-
-
-
-## Create SAP HANA cluster resources
-
-1. **[1]** Create the HANA cluster resources. Execute the following commands as `root`.
-
-   1. Make sure the cluster is already maintenance mode.  
-
-   2. Next, create the HANA Topology resource.
-
-      ```bash
-      sudo crm configure primitive rsc_SAPHanaTopology_HN1_HDB03 ocf:suse:SAPHanaTopology \
-        op monitor interval="10" timeout="600" \
-        op start interval="0" timeout="600" \
-        op stop interval="0" timeout="300" \
-        params SID="HN1" InstanceNumber="03"
-      
-      sudo crm configure clone cln_SAPHanaTopology_HN1_HDB03 rsc_SAPHanaTopology_HN1_HDB03 \
-       meta clone-node-max="1" target-role="Started" interleave="true"
-      ```
-
-   3. Next, create the HANA instance resource.
-
-      > [!NOTE]
-      > This article contains references to terms that Microsoft no longer uses. When these terms are removed from the software, we'll remove them from this article.
-
-      ```bash
-      sudo crm configure primitive rsc_SAPHana_HN1_HDB03 ocf:suse:SAPHanaController \
-        op start interval="0" timeout="3600" \
-        op stop interval="0" timeout="3600" \
-        op promote interval="0" timeout="3600" \
-        op monitor interval="60" role="Master" timeout="700" \
-        op monitor interval="61" role="Slave" timeout="700" \
-        params SID="HN1" InstanceNumber="03" PREFER_SITE_TAKEOVER="true" \
-        DUPLICATE_PRIMARY_TIMEOUT="7200" AUTOMATED_REGISTER="false"
-      
-      sudo crm configure ms msl_SAPHana_HN1_HDB03 rsc_SAPHana_HN1_HDB03 \
-        meta clone-node-max="1" master-max="1" interleave="true"
-      ```
-
-      > [!IMPORTANT]
-      > We recommend as a best practice that you only set AUTOMATED_REGISTER to **no**, while performing thorough fail-over tests, to prevent failed primary instance to automatically register as secondary. Once the fail-over tests have completed successfully, set AUTOMATED_REGISTER to **yes**, so that after takeover system replication can resume automatically.
-
-   4. Create Virtual IP and associated resources.
-
-      ```bash
-      sudo crm configure primitive rsc_ip_HN1_HDB03 ocf:heartbeat:IPaddr2 \
-        op start timeout=60s on-fail=fence \
-        op monitor interval="10s" timeout="20s" \
-        params ip="10.23.0.27"
-      
-      sudo crm configure primitive rsc_nc_HN1_HDB03 azure-lb port=62503 \
-        op monitor timeout=20s interval=10 \
-        meta resource-stickiness=0
-      
-      sudo crm configure group g_ip_HN1_HDB03 rsc_ip_HN1_HDB03 rsc_nc_HN1_HDB03
-      ```
-
-   5. Create the cluster constraints
-
-      ```bash
-      # Colocate the IP with HANA master
-      sudo crm configure colocation col_saphana_ip_HN1_HDB03 4000: g_ip_HN1_HDB03:Started \
-        msl_SAPHana_HN1_HDB03:Master  
-      
-      # Start HANA Topology before HANA  instance
-      sudo crm configure order ord_SAPHana_HN1_HDB03 Optional: cln_SAPHanaTopology_HN1_HDB03 \
-        msl_SAPHana_HN1_HDB03
-      
-      # HANA resources don't run on the majority maker node
-      sudo crm configure location loc_SAPHanaCon_not_on_majority_maker msl_SAPHana_HN1_HDB03 -inf: hana-s-mm
-      sudo crm configure location loc_SAPHanaTop_not_on_majority_maker cln_SAPHanaTopology_HN1_HDB03 -inf: hana-s-mm
-      ```
-
-2. **[1]** Configure additional cluster properties
-
-    ```bash
-    sudo crm configure rsc_defaults resource-stickiness=1000
-    sudo crm configure rsc_defaults migration-threshold=50
-    ```
-
-3. **[1]** Place the cluster out of maintenance mode. Make sure that the cluster status is ok and that all of the resources are started.
-
-    ```bash
-    # Cleanup any failed resources - the following command is example 
-    crm resource cleanup rsc_SAPHana_HN1_HDB03
-    
-    # Place the cluster out of maintenance mode
-    sudo crm configure property maintenance-mode=false
-    ```
-
-4. **[1]** Verify the communication between the HANA HA hook and the cluster, showing status SOK for SID and both replication sites with status P(rimary) or S(econdary).
-
-    ```bash
-    sudo /usr/sbin/SAPHanaSR-showAttr
-    # Expected result
-    # Global cib-time                 maintenance prim  sec sync_state upd
-    # ---------------------------------------------------------------------
-    # HN1    Fri Jan 27 10:38:46 2023 false       HANA_S1 -   SOK        ok
-    # 
-    # Sites     lpt        lss mns        srHook srr
-    # -----------------------------------------------
-    # HANA_S1     1674815869 4   hana-s1-db1 PRIM   P
-    # HANA_S2     30         4   hana-s2-db1 SWAIT  S
-    ```
-  
-   > [!NOTE]
-   > The timeouts in the above configuration are just examples and may need to be adapted to the specific HANA setup. For instance, you may need to increase the start timeout, if it takes longer to start the SAP HANA database.
-
 ## Test SAP HANA failover
 
 > [!NOTE]
