acrolinx

Author: b-ahibbard

articles/azure-netapp-files/application-volume-group-considerations.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 03/13/2025
+ms.date: 04/15/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for application volume group for SAP HANA 
@@ -31,7 +31,7 @@ This article describes the requirements and considerations you need to be aware
     * Determine whether you want to use HANA System Replication (HSR).
         HSR enables SAP HANA databases to synchronously or asynchronously replicate from a primary SAP HANA system to a secondary SAP HANA system. 
     * The expected change rate for the data volume (in case you're using snapshots for backup purposes)
-* You must create a VNet and delegated subnet to map the Azure NetApp Files IP addresses.
+* You must create a virtual network (VNet) and delegated subnet to map the Azure NetApp Files IP addresses.
 
     It's recommended that you lay out the VNet and delegated subnet at design time. 
 
@@ -45,12 +45,12 @@ This article describes the requirements and considerations you need to be aware
 To deploy SAP HANA volumes using the application volume group, you need to ensure that your HANA database VMs and the Azure NetApp Files resources are in close proximity to ensure lowest possible latency. You can achieve close proximity using either of the following deployment methods: 
 
 * **Availability zone volume placement (preferred)**
-        Select the availability zone for the volumes and select Standard network features for the deployment. Neither a proximity placement group nor VM pinning are required for this method. 
+    Select the availability zone for the volumes and select Standard network features for the deployment. You don't need a proximity placement group or VM pinning with availability zone volume placement. 
 * **Proximity placement group with VM pinning**
     The application volume group uses a proximity placement group linked (or anchored) to the database VMs. When passed to the application volume group, the PPG is used to find all Azure NetApp Files resources in close proximity to the database servers. Volumes are deployed using Basic network features.
 
 > [!IMPORTANT]
-> A PPG is only anchored and can therefore identify the location of the VMs if at least one VM is started and kept running for the duration of all AVG deployments. If all VMs are stopped, the PPG loses its anchor, and at the next restart, the VMs may move to a different location. This situation could lead to increased latency as Azure NetApp Files volumes are not moved after initial creation. 
+> A PPG is only anchored and can therefore identify the location of the VMs if at least one VM is started and kept running for the duration of all AVG deployments. If all VMs are stopped, the PPG loses its anchor. At the next restart, the VMs can move to a different location. This situation could lead to increased latency as Azure NetApp Files volumes are not moved after initial creation. 
 
 To avoid this situation, you should create an availability set per database and use the **[SAP HANA VM pinning request form](https://aka.ms/HANAPINNING)** to pin the availability set to a dedicated compute cluster. After pinning, you need to add a PPG to the availability set, and then deploy all hosts of an SAP HANA database using that availability set. Doing so ensures that all virtual machines are at the same location. As long as one of the virtual machines is started, the PPG retains its anchor to deploy the AVG volumes. 
 
@@ -61,7 +61,7 @@ To avoid this situation, you should create an availability set per database and
 
 A PPG needs to have at least one VM assigned to it, either directly or via an availability set. The purpose of the PPG is to extract the exact location of a VM and pass this information to AVG to search for Azure NetApp Files resources in the same location for volume creation. This approach works only when at least ONE VM in the PPG is started and kept running. Typically, you should add your database servers to this PPG.
 
-PPGs have the side effect that, if all VMs are shut down, a following restart of VMs does NOT guarantee that they would start in the same location as before. To prevent this situation from happening, it is strongly recommended to use an availability set that has all VMs and the PPG associated to it, and use the [HANA pinning workflow](https://aka.ms/HANAPINNING). The workflow not only ensures that the VMs are not moving if restarted, it also ensures that locations are selected where enough compute and Azure NetApp Files resources are available.
+PPGs have the side effect that, if all VMs are shut down, a following restart of VMs does NOT guarantee that they would start in the same location as before. To prevent this situation from happening, it's strongly recommended to use an availability set that has all VMs and the PPG associated to it, and use the [HANA pinning workflow](https://aka.ms/HANAPINNING). The workflow not only ensures that the VMs are not moving if restarted, it also ensures that locations are selected where enough compute and Azure NetApp Files resources are available.
 
 When using a PPG without a pinned availability set, a PPG would lose its anchor if all virtual machines in that PPG are stopped. When the virtual machines are restarted, they might be started in a different location, which can result in a latency increase because the volumes created with the application volume group won't be moved.
 
@@ -72,7 +72,7 @@ This situation leads to two possible scenarios:
 * Stable long-term setup:   
     Using an availability set in combination with a PPG where the availability set is manually pinned.
 
-    With the pinning, it is always assured that the placement of the virtual machine won't be changed even if all machines in the availability set are stopped.
+    With pinning, it's always assured that the placement of the virtual machine won't be changed even if all machines in the availability set are stopped.
 
 * Temporary setup:   
     Using a PPG or an availability set in combination with a PPG without any pinning.