Merge pull request #180078 from rdeltcheva/sapha-nfsafs-gs

Add SAP ASCS/ERS HA guides with NFS on Azure Files to change log, add…

Author: PRMerger16

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

@@ -13,7 +13,7 @@ ms.assetid: ad8e5c75-0cf6-4564-ae62-ea1246b4e5f2
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 11/02/2021
+ms.date: 11/16/2021
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 
@@ -77,7 +77,7 @@ In this section, you can find information in how to configure SSO with most of t
 In this section, you find documents about Microsoft Power BI integration into SAP data sources as well as Azure Data Factory integration into SAP BW.
 
 ## Change Log
-- 
+- November 16, 2021: Release of high availability guides for SAP ASCS/ERS with NFS on Azure files [HA for SAP NW on SLES with NFS on Azure Files](./high-availability-guide-suse-nfs-azure-files.md) and [HA for SAP NW on RHEL with NFS on Azure Files](./high-availability-guide-rhel-nfs-azure-files.md). 
 - November 02, 2021: Changed [Azure Storage types for SAP workload](./planning-guide-storage.md) and [SAP ASE Azure Virtual Machines DBMS deployment for SAP workload](./dbms_guide_sapase.md) to declare SAP ASE support for NFS on Azure NetApp Files.
 - November 02, 2021: Changed [SAP workload configurations with Azure Availability Zones](./sap-ha-availability-zones.md) to move Singapore SouthEast to regions for active/active configurations
 - November 02, 2021: Change in [High availability of SAP HANA on Azure VMs on Red Hat Enterprise Linux](./sap-hana-high-availability-rhel.md)  to update instructions for HANA scale-up Active/Active (Read Enabled) configuration.

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

@@ -10,7 +10,7 @@ ms.service: virtual-machines-sap
 ms.topic: tutorial
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 11/15/2021
+ms.date: 11/16/2021
 ms.author: radeltch
 
 ---
@@ -203,7 +203,7 @@ When you plan your deployment with NFS on Azure Files, consider the following im
 - Avoid consolidating the shares for too many SAP systems in a single storage account. There are also [Storage account performance scale targets](../../../storage/files/storage-files-scale-targets.md#storage-account-scale-targets). Be careful to not exceed the limits for the storage account, too.
 - In general,  don't consolidate the shares for more than 5 SAP systems in a single storage account. This guideline helps avoid exceeding the storage account limits and simplifies performance analysis.   
 - In general, avoid mixing shares for non-production and production SAP systems in the same storage account.
-- Deploy on RHEL8 or higher to benefit from NFS client improvements.    
+- We recommend to deploy on RHEL 8.4 or higher to benefit from [NFS client improvements](../../../storage/files/storage-troubleshooting-files-nfs.md#ls-hangs-for-large-directory-enumeration-on-some-kernels).   
 - Use a private endpoint. In the unlikely event of a zonal failure, your NFS sessions automatically redirect to a healthy zone. You don't have to remount the NFS shares on your VMs.
 - If you're deploying your VMs across Availability Zones, use [Storage account with ZRS](../../../storage/common/storage-redundancy.md#zone-redundant-storage) in the Azure regions that supports ZRS. 
 - Azure Files doesn't currently support automatic cross-region replication for disaster recovery scenarios.

articles/virtual-machines/workloads/sap/high-availability-guide-suse-nfs-azure-files.md

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: tutorial
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 11/15/2021
+ms.date: 11/16/2021
 ms.author: radeltch
 
 ---
@@ -205,7 +205,7 @@ When you plan your deployment with NFS on Azure Files, consider the following im
 - Avoid consolidating the shares for too many SAP systems in a single storage account. There are also [Storage account performance scale targets](../../../storage/files/storage-files-scale-targets.md#storage-account-scale-targets). Be careful to not exceed the limits for the storage account, too.
 - In general,  don't consolidate the shares for more than 5 SAP systems in a single storage account. This guideline helps avoid exceeding the storage account limits and simplifies performance analysis.   
 - In general, avoid mixing shares for non-production and production SAP systems in the same storage account.
-- Deploy on RHEL8 or higher to benefit from NFS client improvements.    
+- We recommend to deploy on SLES 15 SP2 or higher to benefit from [NFS client improvements](../../../storage/files/storage-troubleshooting-files-nfs.md#ls-hangs-for-large-directory-enumeration-on-some-kernels).     
 - Use a private endpoint. In the unlikely event of a zonal failure, your NFS sessions automatically redirect to a healthy zone. You don't have to remount the NFS shares on your VMs.
 - If you're deploying your VMs across Availability Zones, use [Storage account with ZRS](../../../storage/common/storage-redundancy.md#zone-redundant-storage) in the Azure regions that supports ZRS. 
 - Azure Files doesn't currently support automatic cross-region replication for disaster recovery scenarios.