Merge pull request #243547 from rdeltcheva/hana-anf-rhel-zone

prmerger-automator[bot] · web-flow · commit 3b0842da5e72 · 2023-06-30T00:39:30.000Z
HANA with ANF - adjust important considerations
diff --git a/articles/sap/workloads/get-started.md b/articles/sap/workloads/get-started.md
@@ -14,7 +14,7 @@ ms.assetid: ad8e5c75-0cf6-4564-ae62-ea1246b4e5f2
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 06/26/2023
+ms.date: 06/29/2023
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 ---
@@ -64,6 +64,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- Jun 29, 2023: Update important considerations and sizing information in [HA for HANA scale-up with ANF on RHEL](./sap-hana-high-availability-netapp-files-red-hat.md), [HANA scale-out with standby node on Azure VMs with ANF on RHEL](./sap-hana-scale-out-standby-netapp-files-rhel.md)
 - Jun 26, 2023: Update important considerations and sizing information in [HA for HANA Scale-up with ANF on SLES](sap-hana-high-availability-netapp-files-suse.md) and [HANA scale-out with standby node with ANF on SLES](./sap-hana-scale-out-standby-netapp-files-suse.md).
 - Jun 23, 2023: Updated Azure scheduled events for SLES in [Pacemaker set up guide](./high-availability-guide-suse-pacemaker.md#configure-pacemaker-for-azure-scheduled-events).
 - June 1, 2023: Included virtual machine scale set with flexible orchestration guidelines in SAP workload [planning guide](./planning-guide.md).
diff --git a/articles/sap/workloads/sap-hana-high-availability-netapp-files-red-hat.md b/articles/sap/workloads/sap-hana-high-availability-netapp-files-red-hat.md
@@ -10,7 +10,7 @@ ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
-ms.date: 04/25/2023
+ms.date: 06/29/2023
 ms.author: radeltch
 ms.custom: ignite-fall-2021
 ---
@@ -157,54 +157,18 @@ The following instructions assume that you've already deployed your [Azure virtu
 
 ### Important considerations
 
-As you are creating your Azure NetApp Files for SAP HANA Scale-up systems, be aware of the following consideration:
-
-- The minimum capacity pool is 4 tebibytes (TiB).
-- The minimum volume size is 100 gibibytes (GiB).
-- Azure NetApp Files and all virtual machines where the Azure NetApp Files volumes will be mounted must be in the same Azure virtual network or in [peered virtual networks](../../virtual-network/virtual-network-peering-overview.md) in the same region.
-- The selected virtual network must have a subnet that is delegated to Azure NetApp Files.
-- The throughput of an Azure NetApp Files volume is a function of the volume quota and service level, as documented in [Service level for Azure NetApp Files](../../azure-netapp-files/azure-netapp-files-service-levels.md). When you are sizing the HANA Azure NetApp volumes, make sure that the resulting throughput meets the HANA system requirements.
-- With the Azure NetApp Files [export policy](../../azure-netapp-files/azure-netapp-files-configure-export-policy.md), you can control the allowed clients, the access type (read-write, read only, and so on).
-- The Azure NetApp Files feature is not zone-aware yet. Currently, the feature is not deployed in all availability zones in an Azure region. Be aware of the potential latency implications in some Azure regions.
-
-> [!IMPORTANT]
-> For SAP HANA workloads, low latency is critical. Work with your Microsoft representative to ensure that the virtual machines and the Azure NetApp Files volumes are deployed in proximity.
+As you are creating your Azure NetApp Files volumes for SAP HANA Scale-up systems, be aware of the important considerations documented in [NFS v4.1 volumes on Azure NetApp Files for SAP HANA](./hana-vm-operations-netapp.md#important-considerations).  
 
 ### Sizing of HANA database on Azure NetApp Files
 
 The throughput of an Azure NetApp Files volume is a function of the volume size and service level, as documented in [Service level for Azure NetApp Files](../../azure-netapp-files/azure-netapp-files-service-levels.md).
 
-As you design the infrastructure for SAP in Azure, be aware of some minimum storage requirements by SAP, which translate into minimum throughput characteristics:
-
-- Read-write on /hana/log of 250 megabytes per second (MB/s) with 1-MB I/O sizes.
-- Read activity of at least 400 MB/s for /hana/data for 16-MB and 64-MB I/O sizes.
-- Write activity of at least 250 MB/s for /hana/data with 16-MB and 64-MB I/O sizes.
-
-The [Azure NetApp Files throughput limits](../../azure-netapp-files/azure-netapp-files-service-levels.md) per 1 TiB of volume quota are:
-
-- Premium Storage tier - 64 MiB/s.
-- Ultra Storage tier - 128 MiB/s.
-
-To meet the SAP minimum throughput requirements for /hana/data and /hana/log, and the guidelines for /hana/shared, the recommended sizes would be:
-
-|    Volume    | Size of Premium Storage Tier | Size of Ultra Storage Tier | Supported NFS Protocol |
-| :----------: | :--------------------------: | :------------------------: | :--------------------: |
-|  /hana/log   |            4 TiB             |           2 TiB            |          v4.1          |
-|  /hana/data  |           6.3 TiB            |          3.2 TiB           |          v4.1          |
-| /hana/shared |           1 x RAM            |          1 x RAM           |          v3 or v4.1    |
-
-
-> [!NOTE]
-> The Azure NetApp Files sizing recommendations stated here are targeted to meet the minimum requirements that SAP recommends for their infrastructure providers. In real customer deployments and workload scenarios, these sizes may not be sufficient. Use these recommendations as a starting point and adapt, based on the requirements of your specific workload.
-
-> [!TIP]
-> You can resize Azure NetApp Files volumes dynamically, without having to *unmount* the volumes, stop the virtual machines, or stop SAP HANA. This approach allows flexibility to meet both the expected and unforeseen throughput demands of your application.
+While designing the infrastructure for SAP HANA on Azure with Azure NetApp Files, be aware of the recommendations in [NFS v4.1 volumes on Azure NetApp Files for SAP HANA](./hana-vm-operations-netapp.md#sizing-for-hana-database-on-azure-netapp-files).   
 
 > [!NOTE]
 > All commands to mount /hana/shared in this article are presented for NFSv4.1 /hana/shared volumes.
 > If you deployed the /hana/shared volumes as NFSv3 volumes, don't forget to adjust the mount commands for /hana/shared for NFSv3.
 
-
 ## Deploy Linux virtual machine via Azure portal 
 
 First you need to create the Azure NetApp Files volumes. Then do the following steps:
diff --git a/articles/sap/workloads/sap-hana-scale-out-standby-netapp-files-rhel.md b/articles/sap/workloads/sap-hana-scale-out-standby-netapp-files-rhel.md
@@ -10,7 +10,7 @@ ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 04/25/2023
+ms.date: 06/29/2023
 ms.author: radeltch
 ---
 
@@ -147,56 +147,13 @@ The following instructions assume that you've already deployed your [Azure virtu
 
 ### Important considerations
 
-As you're creating your Azure NetApp Files for SAP HANA scale-out with stand by nodes scenario, be aware of the following important considerations:
-
-- The minimum capacity pool is 4 tebibytes (TiB).  
-- The minimum volume size is 100 gibibytes (GiB).
-- Azure NetApp Files and all virtual machines where the Azure NetApp Files volumes will be mounted must be in the same Azure virtual network or in [peered virtual networks](../../virtual-network/virtual-network-peering-overview.md) in the same region.  
-- The selected virtual network must have a subnet that's delegated to Azure NetApp Files.
-- The throughput of an Azure NetApp Files volume is a function of the volume quota and service level, as documented in [Service level for Azure NetApp Files](../../azure-netapp-files/azure-netapp-files-service-levels.md). When you're sizing the HANA Azure NetApp volumes, make sure that the resulting throughput meets the HANA system requirements.  
-- With the Azure NetApp Files [export policy](../../azure-netapp-files/azure-netapp-files-configure-export-policy.md), you can control the allowed clients, the access type (read-write, read only, and so on). 
-- The Azure NetApp Files feature isn't zone-aware yet. Currently, the feature isn't deployed in all availability zones in an Azure region. Be aware of the potential latency implications in some Azure regions.  
-
-> [!IMPORTANT]
-> For SAP HANA workloads, low latency is critical. Work with your Microsoft representative to ensure that the virtual machines and the Azure NetApp Files volumes are deployed in close proximity.  
+As you're creating your Azure NetApp Files volumes for SAP HANA scale-out with stand by nodes scenario, be aware of the important considerations documented in [NFS v4.1 volumes on Azure NetApp Files for SAP HANA](./hana-vm-operations-netapp.md#important-considerations).  
 
 ### Sizing for HANA database on Azure NetApp Files
 
 The throughput of an Azure NetApp Files volume is a function of the volume size and service level, as documented in [Service level for Azure NetApp Files](../../azure-netapp-files/azure-netapp-files-service-levels.md). 
 
-As you design the infrastructure for SAP in Azure, be aware of some minimum storage requirements by SAP, which translate into minimum throughput characteristics:
-
-- Read-write on /hana/log of 250 megabytes per second (MB/s) with 1-MB I/O sizes.  
-- Read activity of at least 400 MB/s for /hana/data for 16-MB and 64-MB I/O sizes.  
-- Write activity of at least 250 MB/s for /hana/data with 16-MB and 64-MB I/O sizes. 
-
-The [Azure NetApp Files throughput limits](../../azure-netapp-files/azure-netapp-files-service-levels.md) per 1 TiB of volume quota are:
-- Premium Storage tier - 64 MiB/s  
-- Ultra Storage tier - 128 MiB/s  
-
-To meet the SAP minimum throughput requirements for data and log, and the guidelines for /hana/shared, the recommended sizes would be:
-
-| Volume | Size of<br>Premium Storage tier | Size of<br>Ultra Storage tier | Supported NFS protocol |
-| --- | --- | --- | --- |
-| /hana/log/ | 4 TiB | 2 TiB | v4.1 |
-| /hana/data | 6.3 TiB | 3.2 TiB | v4.1 |
-| /hana/shared | 1xRAM per 4 worker nodes | 1xRAM per 4 worker nodes | v3 or v4.1 |
-
-The SAP HANA configuration for the layout that's presented in this article, using Azure NetApp Files Ultra Storage tier, would be:
-
-| Volume | Size of<br>Ultra Storage tier | Supported NFS protocol |
-| --- | --- | --- |
-| /hana/log/mnt00001 | 2 TiB | v4.1 |
-| /hana/log/mnt00002 | 2 TiB | v4.1 |
-| /hana/data/mnt00001 | 3.2 TiB | v4.1 |
-| /hana/data/mnt00002 | 3.2 TiB | v4.1 |
-| /hana/shared | 2 TiB | v3 or v4.1 |
-
-> [!NOTE]
-> The Azure NetApp Files sizing recommendations stated here are targeted to meet the minimum requirements that SAP recommends for their infrastructure providers. In real customer deployments and workload scenarios, these sizes may not be sufficient. Use these recommendations as a starting point and adapt, based on the requirements of your specific workload.  
-
-> [!TIP]
-> You can resize Azure NetApp Files volumes dynamically, without having to *unmount* the volumes, stop the virtual machines, or stop SAP HANA. This approach allows flexibility to meet both the expected and unforeseen throughput demands of your application.
+While designing the infrastructure for SAP HANA on Azure with Azure NetApp Files, be aware of the recommendations in [NFS v4.1 volumes on Azure NetApp Files for SAP HANA](./hana-vm-operations-netapp.md#sizing-for-hana-database-on-azure-netapp-files).   
 
 ## Deploy Linux virtual machines via the Azure portal
 
