Remove one order constraint in RHEL document for ENSA2 configuration

Author: dennispadia

articles/sap/workloads/disaster-recovery-overview-guide.md

@@ -8,7 +8,7 @@ ms.author: depadia
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: conceptual
-ms.date: 05/08/2024
+ms.date: 04/29/2025
 ---
 
 # Disaster recovery overview and infrastructure guidelines for SAP workload
@@ -107,7 +107,7 @@ An SAP workload running on Azure uses different infrastructure components to run
 
 - On enabling Azure Site Recovery for a VM to set up DR, the local managed disks attached to the VMs are replicated to the DR region. During replication, the VM disk writes are sent to a cache storage account in the source region. Data is sent from there to the target region, and recovery points are generated from the data. When you fail over a VM during DR, a recovery point is used to restore the VM in the target region. But Azure Site Recovery doesn’t support all storages types that are available in Azure. For more information, see [Azure Site Recovery support matrix for storages](../../site-recovery/azure-to-azure-support-matrix.md#replicated-machines---storage).
 
-- For SAP system running on Windows with Azure shared disk, you could use [Azure Site Recovery with Azure Shared Disk (preview)](https://azure.microsoft.com/updates/public-preview-dr-for-shared-disks-azure-site-recovery/). As the feature is in public preview, we don't recommend implementing the scenario for most critical SAP production workloads. For more information on supported scenarios for Azure Shared Disk, see [Support matrix for shared disks in Azure VM disaster recovery (preview)](../../site-recovery/shared-disk-support-matrix.md)
+- For SAP system running on Windows with Azure shared disk, you could use [Azure Site Recovery with Azure Shared Disk](../../site-recovery/tutorial-shared-disk.md). For more information on supported scenarios for Azure Shared Disk, see [Support matrix for shared disks in Azure VM disaster recovery](../../site-recovery/shared-disk-support-matrix.md)
 
 - In addition to Azure managed data disks attached to VMs, different Azure native storage solutions are used to run SAP application on Azure. The DR approach for each Azure storage solution might differ, as not all storage services available in Azure are supported with Azure Site Recovery. Below are the list of storage type that is typically used for SAP workload.
 
@@ -116,7 +116,7 @@ An SAP workload running on Azure uses different infrastructure components to run
   | Managed disk                    | Azure Site Recovery                                          |
   | NFS on Azure files (LRS or ZRS) | Custom script to replicate data between two sites (for example, rsync) |
   | NFS on Azure NetApp Files       | Use [Cross-region replication of Azure NetApp Files volumes](../../azure-netapp-files/cross-region-replication-introduction.md) |
-  | Azure Shared Disk (LRS or ZRS)  | [Azure Site Recovery with Azure Shared Disk (in preview)](../../site-recovery/tutorial-shared-disk.md) |
+  | Azure Shared Disk (LRS or ZRS)  | [Azure Site Recovery with Azure Shared Disk](../../site-recovery/tutorial-shared-disk.md) |
   | SMB on Azure files (LRS or ZRS) | Use [RoboCopy](../../storage/files/storage-files-migration-robocopy.md) to copy files between two sites |
   | SMB on Azure NetApp Files       | Use [Cross-region replication of Azure NetApp Files volumes](../../azure-netapp-files/cross-region-replication-introduction.md) |
 

articles/sap/workloads/disaster-recovery-sap-guide.md

@@ -8,7 +8,7 @@ ms.author: depadia
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: conceptual
-ms.date: 05/08/2024
+ms.date: 04/29/2025
 ---
 
 # Disaster recovery guidelines for SAP application
@@ -121,11 +121,7 @@ On Windows, the high availability configuration of SAP central services (ASCS an
 | ------------------------- | ------------------------------------------------------------ |
 | SMB on Azure Files        | [Robocopy](../../storage/files/storage-files-migration-robocopy.md) |
 | SMB on Azure NetApp Files | [Cross Region Replication](../../azure-netapp-files/cross-region-replication-introduction.md) |
-| Azure Shared Disk         | [Azure Site Recovery with Shared Disks (preview)](../../site-recovery/shared-disk-support-matrix.md) |
-
-> [!NOTE]
->
-> Azure Site Recovery with shared disk is currently in public preview. So, we don't recommend implementing the scenario for most critical SAP production workloads
+| Azure Shared Disk         | [Azure Site Recovery with Shared Disks](../../site-recovery/shared-disk-support-matrix.md) |
 
 ---
 

articles/sap/workloads/high-availability-guide-rhel-multi-sid.md

@@ -8,7 +8,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.custom: linux-related-content
 ms.topic: how-to
-ms.date: 11/19/2024
+ms.date: 04/29/2025
 ms.author: radeltch
 ---
 
@@ -440,7 +440,6 @@ This article assumes that:
     sudo pcs resource meta rsc_sap_NW2_ERS12  resource-stickiness=3000
 
     sudo pcs constraint colocation add g-NW2_AERS with g-NW2_ASCS -5000
-    sudo pcs constraint order start g-NW2_ASCS then start g-NW2_AERS kind=Optional symmetrical=false
     sudo pcs constraint order start g-NW2_ASCS then stop g-NW2_AERS kind=Optional symmetrical=false
 
     sudo pcs resource create rsc_sap_NW3_ASCS20 SAPInstance \
@@ -462,7 +461,6 @@ This article assumes that:
     sudo pcs resource meta rsc_sap_NW3_ERS22  resource-stickiness=3000
 
     sudo pcs constraint colocation add g-NW3_AERS with g-NW3_ASCS -5000
-    sudo pcs constraint order start g-NW3_ASCS then start g-NW3_AERS kind=Optional symmetrical=false
     sudo pcs constraint order start g-NW3_ASCS then stop g-NW3_AERS kind=Optional symmetrical=false
 
     sudo pcs property set maintenance-mode=false

articles/sap/workloads/high-availability-guide-rhel-netapp-files.md

@@ -7,7 +7,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-conten
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
-ms.date: 11/19/2024
+ms.date: 04/29/2025
 ms.author: radeltch
 ---
 
@@ -662,7 +662,6 @@ The following items are prefixed with either:
     sudo pcs resource meta rsc_sap_QAS_ERS01  resource-stickiness=3000
    
     sudo pcs constraint colocation add g-QAS_AERS with g-QAS_ASCS -5000
-    sudo pcs constraint order start g-QAS_ASCS then start g-QAS_AERS kind=Optional symmetrical=false
     sudo pcs constraint order start g-QAS_ASCS then stop g-QAS_AERS kind=Optional symmetrical=false
    
     sudo pcs node unstandby anftstsapcl1

articles/sap/workloads/high-availability-guide-rhel-nfs-azure-files.md

@@ -7,7 +7,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-conten
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: tutorial
-ms.date: 11/19/2024
+ms.date: 04/29/2025
 ms.author: radeltch
 ---
 
@@ -568,7 +568,6 @@ The following items are prefixed with:
     sudo pcs resource meta rsc_sap_NW1_ERS01  resource-stickiness=3000
 
     sudo pcs constraint colocation add g-NW1_AERS with g-NW1_ASCS -5000
-    sudo pcs constraint order start g-NW1_ASCS then start g-NW1_AERS kind=Optional symmetrical=false
     sudo pcs constraint order start g-NW1_ASCS then stop g-NW1_AERS kind=Optional symmetrical=false
    
     sudo pcs node unstandby sap-cl1

articles/sap/workloads/high-availability-guide-rhel.md

@@ -7,7 +7,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-conten
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
-ms.date: 11/20/2024
+ms.date: 04/29/2025
 ms.author: radeltch
 ---
 
@@ -481,7 +481,6 @@ The following items are prefixed with:
     sudo pcs resource meta rsc_sap_NW1_ERS02 resource-stickiness=3000
    
     sudo pcs constraint colocation add g-NW1_AERS with g-NW1_ASCS -5000
-    sudo pcs constraint order start g-NW1_ASCS then start g-NW1_AERS kind=Optional symmetrical=false
     sudo pcs constraint order start g-NW1_ASCS then stop g-NW1_AERS kind=Optional symmetrical=false
    
     sudo pcs node unstandby nw1-cl-0