Skip to content

Commit 2b0d2f7

Browse files
authored
Changes has been updated as per suggestion
1 parent f271eb6 commit 2b0d2f7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machines/workloads/sap/sap-high-availability-architecture-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ SAP high availability in Azure can be separated into three types:
243243
* Redundant SAP application servers.
244244
* Unique components. An example might be a single point of failure (SPOF) component, such as an SAP ASCS/SCS instance or a database management system (DBMS).
245245

246-
SAP high availability in Azure differs from SAP high availability in an on-premises physical or virtual environment. The following paper [SAP NetWeaver high availability and business continuity in virtual environments with VMware and Hyper-V on Microsoft Windows][sap-ha-bc-virtual-env-hyperv-vmware-white-paper] describes standard SAP high-availability configurations in virtualized environments on Windows.
246+
SAP high availability in Azure differs from SAP high availability in an on-premises physical or virtual environment.
247247

248248
There is no sapinst-integrated SAP high-availability configuration for Linux as there is for Windows. For information about SAP high availability on-premises for Linux, see [High availability partner information][sap-ha-partner-information].
249249

0 commit comments

Comments
 (0)