Skip to content

Commit dc287e2

Browse files
Update articles/virtual-machines/workloads/sap/disaster-recovery-sap-guide.md
Co-authored-by: Ralitza Deltcheva <[email protected]>
1 parent b110f04 commit dc287e2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ For SAP system, the redundancy of SPOF component in the primary region is achiev
9999

100100
##### SAP system configured with File share
101101

102-
If you've configured your SAP system using file share on primary region, you need to make sure all the component along with the data in the file share (SMB on Azure Files, SMB on ANF) is available in disaster recovery region if there is failover. With SAP system configured with File share, you can use Azure Site Recovery to replicate cluster and other application server VMs to disaster recovery region. But there are some additional considerations that you need to keep in mind.
102+
If you've configured your SAP system using file share on primary region, you need to make sure all components and the data in the file share (SMB on Azure Files, SMB on ANF) are replicated to the disaster recovery region if there is failover. You can use Azure Site Recovery to replicate the cluster VMs and other application server VMs to the disaster recovery region. There are some additional considerations that are outlined below.
103103

104104
###### Load balancer
105105

0 commit comments

Comments
 (0)