Merge pull request #105579 from rdeltcheva/chg-meta5

Change metadata for improved searchability and add update HA links

Author: PRMerger7

articles/virtual-machines/workloads/sap/get-started.md

@@ -116,6 +116,7 @@ For information on integration of Azure services into SAP components, see:
 
 
 ## Change Log
+- 02/25/2020: Change in [High availability architecture and scenarios for SAP](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-high-availability-architecture-scenarios) to add links to newer HA articles
 - 02/25/2020: Change in [High availability of IBM Db2 LUW on Azure VMs on SUSE Linux Enterprise Server with Pacemaker](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/dbms-guide-ha-ibm) to point to document that describes access to public endpoint with Standard Azure Load balancer
 - 02/21/2020: Complete revision of the article [SAP ASE Azure Virtual Machines DBMS deployment for SAP workload](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/dbms_guide_sapase)
 - 02/21/2020: Change in [SAP HANA Azure virtual machine storage configuration](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-vm-operations-storage) to represent new recommendation in stripe size for /hana/data and adding setting of I/O scheduler

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

@@ -1,5 +1,5 @@
 ---
-title: Azure Virtual Machines high-availability architecture and scenarios for SAP NetWeaver | Microsoft Docs
+title: Azure VMs HA architecture and scenarios for SAP NetWeaver | Microsoft Docs
 description: High-availability architecture and scenarios for SAP NetWeaver on Azure Virtual Machines
 services: virtual-machines-windows,virtual-network,storage
 documentationcenter: saponazure
@@ -15,7 +15,7 @@ ms.service: virtual-machines-windows
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 01/21/2019
+ms.date: 02/25/2020
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017
 
@@ -389,6 +389,8 @@ You can use a WSFC solution to protect the SAP ASCS/SCS instance. The solution h
 
 * **Cluster the SAP ASCS/SCS instance by using file share**: For more information about this architecture, see [Cluster an SAP ASCS/SCS instance on a Windows failover cluster by using file share][sap-high-availability-guide-wsfc-file-share].
 
+* **Cluster the SAP ASCS/SCS instance by using ANF SMB share**: For more information about this architecture, see Cluster [Cluster an SAP ASCS/SCS instance on a Windows failover cluster by using ANF SMB file share](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-windows-netapp-files-smb).
+
 ### High-availability architecture for an SAP ASCS/SCS instance on Linux
 
 > ![Linux][Logo_Linux] Linux
@@ -402,14 +404,21 @@ For more information about clustering the SAP ASCS/SCS instance by using the Red
 
 > ![Windows][Logo_Windows] Windows
 > 
-> Currently, multi-SID is supported only with WSFC. Multi-SID is supported using file share and shared disk.
+> Multi-SID is supported with WSFC, using file share and shared disk.
 > 
-> For more information about multi-SID high-availability architecture, see:
+> For more information about multi-SID high-availability architecture on Windows, see:
 
 * [SAP ASCS/SCS instance multi-SID high availability for Windows Server Failover Clustering and file share][sap-ascs-ha-multi-sid-wsfc-file-share]
 
 * [SAP ASCS/SCS instance multi-SID high availability for Windows Server Failover Clustering and shared disk][sap-ascs-ha-multi-sid-wsfc-shared-disk]
 
+> ![Linux][Logo_Linux] Linux
+> 
+> Multi-SID clustering is supported on Linux Pacemaker clusters for SAP ASCS/ERS, limited to **five** SAP SIDs on the same cluster.
+> For more information about multi-SID high-availability architecture on Linux, see:
+
+* [HA for SAP NW on Azure VMs on SLES for SAP applications multi-SID guide](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-multi-sid)
+
 ### High-availability DBMS instance
 
 The DBMS also is a single point of contact in an SAP system. You need to protect it by using a high-availability solution. The following figure shows a SQL Server AlwaysOn high-availability solution in Azure, with Windows Server Failover Clustering and the Azure internal load balancer. SQL Server AlwaysOn replicates DBMS data and log files by using its own DBMS replication. In this case, you don't need cluster shared disk, which simplifies the entire setup.

articles/virtual-machines/workloads/sap/sap-high-availability-guide-start.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Virtual Machines high availability for SAP NetWeaver | Microsoft Docs
+title: Azure VMs high availability for SAP NetWeaver | Microsoft Docs
 description: High-availability guide for SAP NetWeaver on Azure Virtual Machines
 services: virtual-machines-windows,virtual-network,storage
 documentationcenter: saponazure

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

@@ -1,5 +1,5 @@
 ---
-title: Utilize Azure infrastructure VM restart to achieve “higher availability” of an SAP system | Microsoft Docs
+title: Utilize Azure VMs restart for “higher availability” of an SAP system | Microsoft Docs
 description: Utilize Azure infrastructure VM restart to achieve “higher availability” of SAP applications
 services: virtual-machines-windows,virtual-network,storage
 documentationcenter: saponazure