Merge pull request #269233 from b-ahibbard/lg-vol-50

new minimum large volume size: 50 TiB

Author: PMEds28

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

@@ -60,7 +60,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
         The **Available quota** field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.  
 
     * **Large Volume**
-        If the quota of your volume is less than 100 TiB, select **No**. If the quota of your volume is greater than 100 TiB, select **Yes**.
+        For volumes between 50 TiB and 500 TiB, select **Yes**. If the volume does not require more than 100 TiB, select **No**. 
         [!INCLUDE [Large volumes warning](includes/large-volumes-notice.md)]
 
     * **Throughput (MiB/S)**   

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -101,14 +101,14 @@ For volumes 100 TiB or under, if you've allocated at least 5 TiB of quota for a
 For volumes 100 TiB or under, you can increase the `maxfiles` limit up to 531,278,150 if your volume quota is at least 25 TiB.
 
 >[!IMPORTANT]
-> When files or folders are allocated to an Azure NetApp Files volume, they count against the `maxfiles` limit. If a file or folder is deleted, the internal data structures for `maxfiles` allocation remain the same. For instance, if the files used in a volume increase to 63,753,378 and 100,000 files are deleted, the `maxfiles` allocation will remain at 63,753,378. 
+> When files or folders are allocated to an Azure NetApp Files volume, they count against the `maxfiles` limit. If a file or folder is deleted, the internal data structures for `maxfiles` allocation remain the same. For instance, if the files used in a volume increase to 63,753,378 and 100,000 files are deleted, the `maxfiles` allocation remains at 63,753,378. 
 > Once a volume has exceeded a `maxfiles` limit, you cannot reduce volume size below the quota corresponding to that `maxfiles` limit even if you have reduced the actual used file count. For example, the `maxfiles` limit for a 2 TiB volume is 63,753,378. If you create more than 63,753,378 files in that volume, the volume quota cannot be reduced below its corresponding index of 2 TiB.
 
 **For [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes):**
 
 | Volume size (quota) | Automatic readjustment of the `maxfiles` limit |
 | - | - |
-|   > 100 TiB    | 2,550,135,120                  |
+|   > 50 TiB    | 2,550,135,120                  | 
              
 You can increase the `maxfiles` limit beyond 2,550,135,120 using a support request. For every 2,550,135,120 files you increase (or a fraction thereof), you need to increase the corresponding volume quota by 120 TiB. For example, if you increase `maxfiles` limit from 2,550,135,120 to 5,100,270,240 files (or any number in between), you need to increase the volume quota to at least 240 TiB.
 

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -77,7 +77,7 @@ When you use a manual QoS capacity pool with, for example, an SAP HANA system, a
 
 ## Large volumes
 
-Azure NetApp Files allows you to create volumes up to 500 TiB in size, exceeding the previous 100-TiB limit. Large volumes begin at a capacity of 102,401 GiB and scale up to 500 TiB. Regular Azure NetApp Files volumes are offered between 100 GiB and 102,400 GiB. 
+Azure NetApp Files allows you to create volumes up to 500 TiB in size, exceeding the previous 100-TiB limit. Large volumes begin at a capacity of 50 TiB and scale up to 500 TiB. Regular Azure NetApp Files volumes are offered between 100 GiB and 102,400 GiB. 
 
 For more information, see [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md).
 

articles/azure-netapp-files/create-volumes-dual-protocol.md

@@ -99,7 +99,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
         The **Available quota** field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.  
 
     * **Large Volume**
-        If the quota of your volume is less than 100 TiB, select **No**. If the quota of your volume is greater than 100 TiB, select **Yes**.
+        For volumes between 50 TiB and 500 TiB, select **Yes**. If the volume does not require more than 100 TiB, select **No**. 
         [!INCLUDE [Large volumes warning](includes/large-volumes-notice.md)]
 
     * **Throughput (MiB/S)**   

articles/azure-netapp-files/includes/large-volumes-notice.md

@@ -16,4 +16,4 @@ ms.custom: include file
 >[!IMPORTANT]
 > Large volumes are currently in preview. If this is your first time using large volumes, you must first [register the feature](../azure-netapp-files-understand-storage-hierarchy.md#large-volumes) and request [an increase in regional capacity quota](../azure-netapp-files-resource-limits.md#request-limit-increase).
 >
->Volumes are considered large if they are between 100 TiB and 500 TiB in size. Once created, volumes less than 100 TiB in size cannot be resized to large volumes. Large volumes cannot be resized to less than 100 TiB and can only be resized up to 30% of lowest provisioned size. To understand the requirements and considerations of large volumes, refer to for using [Requirements and considerations for large volumes](../large-volumes-requirements-considerations.md).
+>Volumes are considered large if they are between 50 TiB and 500 TiB in size. Regular volumes cannot be converted to large volumes. Large volumes cannot be resized to less than 50 TiB. To understand the requirements and considerations of large volumes, refer to for using [Requirements and considerations for large volumes](../large-volumes-requirements-considerations.md).

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -25,9 +25,9 @@ The following requirements and considerations apply to large volumes. For perfor
 
 * Existing regular volumes can't be resized over 100 TiB.
 * You can't convert regular Azure NetApp Files volumes to large volumes.
-* You must create a large volume at a size greater than 100 TiB. A single volume can't exceed 500 TiB.  
-* You can't resize a large volume to less than 100 TiB.
-* You can only resize a large to be volume up to 30%, of lowest provisioned size. 
+* You must create a large volume at a size of 50 TiB or larger. A single volume can't exceed 500 TiB.  
+* You can't resize a large volume to less than 50 TiB.
+    A large volume cannot be resized to less than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
 * Large volumes are currently not supported with Azure NetApp Files backup.
 * Large volumes aren't currently supported with cross-region replication.
 * You can't create a large volume with application volume groups.
@@ -37,9 +37,9 @@ The following requirements and considerations apply to large volumes. For perfor
 
     | Capacity tier | Volume size (TiB) | Throughput (MiB/s) |
     | --- | --- | --- |
-    | Standard | 100 to 500 | 1,600 |
-    | Premium | 100 to 500 | 6,400 | 
-    | Ultra | 100 to 500 | 10,240 | 
+    | Standard | 50 to 500 | 1,600 |
+    | Premium | 50 to 500 | 6,400 | 
+    | Ultra | 50 to 500 | 10,240 | 
 
 * Large volumes aren't currently supported with standard storage with cool access.
 

articles/azure-netapp-files/media/azure-netapp-files-understand-storage-hierarchy/azure-netapp-files-storage-hierarchy.png

@@ -14,6 +14,10 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+* [Large volumes (Preview) improvement:](large-volumes-requirements-considerations.md) new minimum size of 50 TiB
+
+    Large volumes support a minimum size of 50 TiB. Large volumes still support a maximum quota of 500 TiB. 
+
 ## March 2024
 
 * [Availability zone volume placement](manage-availability-zone-volume-placement.md) is now generally available (GA).