Merge pull request #296131 from b-ahibbard/avg-sap-oracle

JillGrant615 · web-flow · commit 0a6b93001085 · 2025-03-13T09:21:19.000-06:00
GA: AVG SAP HANA ext. 1 &amp; Oracle
diff --git a/articles/azure-netapp-files/application-volume-group-considerations.md b/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: 01/29/2025
+ms.date: 03/13/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for application volume group for SAP HANA 
@@ -37,9 +37,9 @@ This article describes the requirements and considerations you need to be aware
 >[!IMPORTANT]
 >The use of application volume group for SAP HANA for applications other than SAP HANA is not supported. Reach out to your Azure NetApp Files specialist for guidance on using Azure NetApp Files multi-volume layouts with other database applications.
 
-### <a name="extension-1-requirements-considerations"></a> Extension 1 requirements and considerations (preview)
+### <a name="extension-1-requirements-considerations"></a> Extension 1 requirements and considerations
 
-* Extension 1 is currently in preview and requires that you [register for the feature](application-volume-group-deploy-first-host.md#register-for-extension-1).
+* You must be [registered for extension 1](application-volume-group-deploy-first-host.md#register-for-extension-1).
 * Application volume group supports Basic network features. If you're registered for extension 1, application volume group also supports [Standard network features](azure-netapp-files-network-topologies.md).
 * Extension 1 supports [availability zone volume placement](use-availability-zones.md) as the new default method for placement. This upgrade mitigates the need for AVset pinning and eliminates the need for proximity placement groups. With support for availability zone volume placement, you only need to select the same availability zone as the database servers. Using availability zone volume placement aligns with the Microsoft recommendation on how to deploy SAP HANA infrastructures to achieve best performance with high-availability, maximum flexibility, and simplified deployment. 
     If regions do not support availability zones, you can select a regional deployment or choose proximity placement groups.
diff --git a/articles/azure-netapp-files/application-volume-group-deploy-first-host.md b/articles/azure-netapp-files/application-volume-group-deploy-first-host.md
@@ -23,7 +23,7 @@ This article describes how to deploy the first SAP HANA host using Azure NetApp
 
 ### Register for extension 1 
 
-Azure NetApp Files application volume group for SAP HANA Extension 1 is currently in preview. You need to register the feature before using it for the first time. Feature registration may take up to 60 minutes to complete.
+You need to register for Azure NetApp Files application volume group for SAP HANA Extension 1 before using it for the first time. Feature registration may take up to 60 minutes to complete.
 
 1. Register the feature
 
diff --git a/articles/azure-netapp-files/application-volume-group-introduction.md b/articles/azure-netapp-files/application-volume-group-introduction.md
@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 02/24/2025
+ms.date: 03/13/2025
 ms.author: anfdocs
 ---
 # Understand Azure NetApp Files application volume group for SAP HANA 
@@ -46,7 +46,7 @@ Application volume group for SAP HANA helps you simplify the deployment process
 * Creation of separate storage endpoints (with different IP addresses) for data and log volumes.
     * This deployment method provides better performance and throughput for the SAP HANA database.
 
-### <a name="extension-1-features"></a> Extension 1 features (preview)
+### <a name="extension-1-features"></a> Extension 1 features
 
 Application volume group for SAP HANA extension one offers support for:
 
diff --git a/articles/azure-netapp-files/application-volume-group-oracle-deploy-volumes.md b/articles/azure-netapp-files/application-volume-group-oracle-deploy-volumes.md
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 01/29/2025
+ms.date: 03/13/2025
 ms.author: anfdocs
 ---
 # Deploy application volume group for Oracle
@@ -25,7 +25,7 @@ You should understand the [requirements and considerations for application volum
 
 ## Register the feature  
 
-Azure NetApp Files application volume group for Oracle is currently in preview. Before using this feature for the first time, you need to register it. 
+Before using Azure NetApp Files application volume group for Oracle for the first time, you need to register it. 
 
 1. Register the feature: 
 
@@ -54,17 +54,17 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 3. In the **ORACLE** tab, provide Oracle-specific information:   
 
     * **Unique System ID (SID)**:    
-        Choose a unique identifier that will be used in the naming proposals for all your storage objects and helps to uniquely identify the volumes for this database.
+        Use the unique Oracle identifier that will be used to identify the volumes for this database in the naming proposals for all your storage objects.
     * **Group name / Group description**:  
         Provide the volume group name and description.
     * **Number of Oracle data volumes (1-8)**:  
-        Depending on your sizing and performance requirements of the database you can create a minimum of 1 and up to 8 data volumes. 
+        Depending on your sizing and performance requirements of the database, you can create a minimum of 1 and up to 8 data volumes. 
     * **Oracle database size in (TiB)**:   
-        Specify the total capacity required for your database. If you select more than one database volume, the capacity is distributed evenly among all volumes. You may change each individual volume once the proposals have been created. See Step 8 in this article.
+        Specify the total capacity required for your database. If you select more than one database volume, the capacity is distributed evenly among all volumes. You can change each individual volume once the proposals have been created. See Step 8 in this article.
     * **Additional capacity for snapshots (%)**:   
-        If you use snapshots for data protection, you need to plan for extra capacity. This field will add an additional size (%) for the data volume.
+        If you use snapshots for data protection, you need to plan for extra capacity. This field adds an additional size (%) for the data volume.
     * **Oracle database storage throughput (MiB/s)**:   
-        Specify the total throughput required for your database. If you select more than one database volume, the throughput is distributed evenly among all volumes. You may change each individual volume once the proposals have been created. See Step in this article.
+        Specify the total throughput required for your database. If you select more than one database volume, the throughput is distributed evenly among all volumes. You can change each individual volume once the proposals have been created. See Step in this article.
 
     Select **Next: Volume Group**.
 
@@ -73,28 +73,28 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 4. In the **Volume group** tab, provide information for creating the volume group:
 
     * **Availability options**:  
-        There are two **Availability** options. This screenshot is for a volume placement using **Availability Zone**.  
+        There are 2 **Availability** options. The following screenshot illustrates volume placement using **Availability Zone**.  
     * **Availability Zone**:  
-        Select the zone where Azure NetApp Files is available. In regions without zones, you can select **none**.
+        Select the zone where Azure NetApp Files is available. In regions without zones, select **none**.
     * **Network features**:  
-        Select either **Basic** or **Standard** network features. All volumes should use the same network feature. This selection is set for each individual volume.
+        Select either **Basic** or **Standard** network features. All volumes should use the same network feature setting. This selection is set for each individual volume.
     * **Capacity pool**:  
-        All volumes will be placed in a single manual QoS capacity pool.
+        Design that manual QoS capacity where all volumes are placed. 
     * **Virtual network**:  
-        Specify an existing VNet where the VMs are placed. 
+        Specify an existing VNet where the Oracle VMs are located.
     * **Subnet**:  
-        Specify the delegated subnet where the IP addresses for the NFS exports will be created. Ensure that you have a delegated subnet with enough free IP addresses.
+        Specify the delegated subnet where the IP addresses for the NFS exports will be created. Ensure you have a delegated subnet with enough free IP addresses.
     * **Encryption key source**:
         Select [Customer Managed Key](configure-customer-managed-keys.md) or Microsoft Managed Key. If you choose Customer Managed Key, provide the key vault private endpoint.
 
     Select **Next: Tags**. Continue with Step 6. 
 
     [ ![Screenshot that shows the Volume Group tag for Oracle.](./media/volume-hard-quota-guidelines/application-volume-group-tag-oracle.png) ](./media/volume-hard-quota-guidelines/application-volume-group-tag-oracle.png#lightbox)
 
-5. If you select **Proximity placement group**, then specify the following information in the **Volume group** tab: 
+5. If you select **Proximity placement group**, specify the following information in the **Volume group** tab: 
 
     * **Availability options**:   
-        This screenshot is for a volume placement using **Proximity placement group**.
+        This screenshot shows a volume placement using **Proximity placement group**.
     * **Proximity placement group**:
         Specify the proximity placement group for all volumes.
 
@@ -112,10 +112,10 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
     [ ![Screenshot that shows how to add tags for Oracle.](./media/volume-hard-quota-guidelines/application-add-tags-oracle.png) ](./media/volume-hard-quota-guidelines/application-add-tags-oracle.png#lightbox)
 
 
-7. In the **Protocols** section of the Volume Group tab, you can select the NFS version, modify the Export Policy, and select [LDAP-enabled volumes](configure-ldap-extended-groups.md). These settings need to be common to all volumes. 
+7. In the **Protocols** section of the Volume Group tab, you can select the NFS version, modify the Export Policy, and select [LDAP-enabled volumes](configure-ldap-extended-groups.md). These settings need to be common across all volumes in this volume group. 
 
     > [!NOTE]
-    > For optimal performance, use Oracle dNFS to mount the volumes at the database server. We recommend using NFSv3 as a base for dNFS, but NFSv4.1 is also supported. Check the support documentation of your Azure VM operating system for guidance about which NFS protocol version to use in combination with dNFS and your operating system. 
+    > For optimal performance, use Oracle dNFS to mount the volumes at the database server. It's recommended you use NFSv3 as a base for dNFS. NFSv4.1 is also supported. Check the support documentation of your Azure VM operating system for guidance about which NFS protocol version to use in combination with dNFS and your operating system. 
 
     Select **Next: Volumes**. 
 
@@ -160,14 +160,13 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
 12. The **Volumes Tab** enables you to remove optional volumes. 
 
-    <!-- check -->
     Provide an **Encryption key source**. Select [Customer Managed Key](configure-customer-managed-keys.md) or Microsoft Managed Key. If you choose Customer Managed Key, provide the key vault private endpoint.
 
     On the Volumes tab, optional volumes are marked with an asterisk (`*`) in front of the name.   
     If you want to remove the optional volumes such as `ORA1-ora-data4` volume or `ORA1-ora-binary` volume from the volume group, select the volume then **Remove volume**. Confirm the removal in the dialog box that appears.
 
     > [!IMPORTANT]    
-    > You cannot add a removed volume back to the volume group again.
+    > You can't add a removed volume back to the volume group again without canceling and restarting the application volume group workflow.
 
     Select **Volumes** after completing the changes of volumes.
 
@@ -178,7 +177,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
     [ ![Screenshot that shows confirmation about removing an optional volume for Oracle.](./media/volume-hard-quota-guidelines/application-volume-remove-confirm-oracle.png) ](./media/volume-hard-quota-guidelines/application-volume-remove-confirm-oracle.png#lightbox)
 
 
-13.	The **Review + Create** tab lists all the volumes that will be created. The process also validates the creation.  
+13.	The **Review + Create** tab lists all the volumes to be created. The process also validates the creation.  
 
     Select **Create Volume Group** to start the volume group creation. 
 
@@ -189,12 +188,12 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
     [ ![Screenshot that shows the Deployment in Progress window for Oracle.](./media/volume-hard-quota-guidelines/application-deployment-in-progress-oracle.png) ](./media/volume-hard-quota-guidelines/application-deployment-in-progress-oracle.png#lightbox)
 
-    Creating a volume group is an "all-or-none" operation. If one volume can't be created, the operation is canceled, and all remaining volumes will be removed also.
+    Creating a volume group is an "all-or-none" operation. If one volume can't be created, the operation is canceled, and all remaining volumes are also removed.
 
     [ ![Screenshot that shows the new volume group for Oracle.](./media/volume-hard-quota-guidelines/application-new-volume-group-oracle.png) ](./media/volume-hard-quota-guidelines/application-new-volume-group-oracle.png#lightbox)
 
 
-15. Following completion, in **Volumes** you can display the list of volume groups to see the new volume group. You can select the new volume group to see the details and status of each of the volumes being created.
+15. Following completion, in **Volumes** you can display the list of volume groups to see the new volume group. Select the new volume group to see the details and status of each of the volumes being created.
 
 ## Next steps
 
diff --git a/articles/azure-netapp-files/application-volume-group-oracle-introduction.md b/articles/azure-netapp-files/application-volume-group-oracle-introduction.md
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 01/29/2025
+ms.date: 03/13/2025
 ms.author: anfdocs
 ---
 # Understand Azure NetApp Files application volume group for Oracle 
diff --git a/articles/azure-netapp-files/includes/application-volume-group-layout.md b/articles/azure-netapp-files/includes/application-volume-group-layout.md
@@ -2,15 +2,15 @@
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
-ms.date: 01/31/2024
+ms.date: 03/13/2025
 ms.author: anfdocs
 ms.custom: include file
 
 # application-volume-group-concepts.md
 # application-volume-group-oracle-introduction.md
 ---
 
-* AVG can deploy 1 to 8 data, log (and optionally, log-mirror), backup, and binary volumes in the selected zone using the same network features setting (Standard or Basic) and the same NFS version (NFSv4.1 or NFSv3).
+* Application volume group can deploy 1 to 8 data, log (and optionally, log-mirror), backup, and binary volumes in the selected zone using the same network features setting (Standard or Basic) and the same NFS version (NFSv4.1 or NFSv3).
 * The hosting capacity pool needs to be configured with [Manual QoS](../azure-netapp-files-performance-considerations.md#manual-qos-volume-quota-and-throughput).
 * Data volumes are deployed following anti-affinity rules to ensure they're spread over as many Azure NetApp Files storage endpoints as possible in the selected zone. The volumes are also assigned direct storage-endpoints for the best possible latency. 
 * Up to three data volumes can be deployed on the same storage-endpoint in resource-constrained zones if capacity and throughput requirements permit. 
diff --git a/articles/azure-netapp-files/includes/application-volume-group.md b/articles/azure-netapp-files/includes/application-volume-group.md
@@ -1,10 +1,8 @@
 ---
-title: include file
-description: include file
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
-ms.date: 07/03/2023
+ms.date: 03/13/2025
 ms.author: anfdocs
 ms.custom: include file
 
@@ -14,4 +12,4 @@ ms.custom: include file
 ---
 
 >[!IMPORTANT]
->For SAP HANA production workloads make sure to use [Azure NetApp Files application volume group for SAP HANA](../application-volume-group-introduction.md) to deploy your HANA volumes.
+>For SAP HANA production workloads, use [Azure NetApp Files application volume group for SAP HANA](../application-volume-group-introduction.md) to deploy your HANA volumes.
diff --git a/articles/azure-netapp-files/includes/extension-one.md b/articles/azure-netapp-files/includes/extension-one.md
@@ -1,9 +1,8 @@
 ---
-title: include file
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
-ms.date: 03/08/2024
+ms.date: 03/13/2025
 ms.author: anfdocs
 ms.custom: include file
 
@@ -14,4 +13,4 @@ ms.custom: include file
 ---
 
 >[!IMPORTANT]
->The options for this procedure differ if you've registered for the [Application volume group for SAP HANA extension 1 preview](../application-volume-group-considerations.md#extension-1-requirements-considerations). Select the correct tab for your configuration. To take advantage of the feature, you must [register for extension 1](../application-volume-group-deploy-first-host.md#register-for-extension-1).
+>The options for this procedure differ if you're using [Application volume group for SAP HANA extension 1](../application-volume-group-considerations.md#extension-1-requirements-considerations). Select the correct tab for your configuration. To take advantage of the feature, you must [register for extension 1](../application-volume-group-deploy-first-host.md#register-for-extension-1).
diff --git a/articles/azure-netapp-files/whats-new.md b/articles/azure-netapp-files/whats-new.md
@@ -6,7 +6,7 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.custom: linux-related-content
 ms.topic: overview
-ms.date: 03/06/2025
+ms.date: 03/13/2025
 ms.author: anfdocs
 ---
 
@@ -16,6 +16,15 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## March 2025
 
+* [Application volume group for Oracle](application-volume-group-oracle-introduction.md) is now generally available (GA)
+
+* [Application volume group for SAP HANA extension one](application-volume-group-introduction.md) is now generally available (GA)
+
+    Application volume group for SAP HANA extension one enables you to improve your volume group deployment experience for SAP HANA. Key improvements include: 
+
+    - Support for availability zone volume placement, avoiding the manual AVset pining requirement (when using PPG) 
+    - Support for Standard network features for SAP HANA volumes 
+
 * [Storage with cool access enhancement:](manage-cool-access.md) snapshot-only tiering policy
 
     Azure NetApp Files storage with cool access now supports a snapshots-only policy. With this policy enabled, only snapshots are moved to the cool tier. 
