Merge pull request #281228 from b-ahibbard/lg-vol

new large volume limits

Author: JamesJBarnett

articles/azure-netapp-files/azure-netapp-files-cost-model.md

@@ -18,7 +18,7 @@ For cost model specific to cross-region replication, see [Cost model for cross-r
 
 Azure NetApp Files is billed on provisioned storage capacity, which is allocated by creating capacity pools. Capacity pools are billed monthly based on a set cost per allocated GiB per hour. Capacity pool allocation is measured hourly.  
 
-Capacity pools must be at least 1 TiB and can be increased or decreased in 1-TiB intervals. Capacity pools contain volumes that range in size from a minimum of 100 GiB to a maximum of 100 TiB for regular volumes and up to 500 TiB for [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes). Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [How Azure NetApp Files snapshots work](snapshots-introduction.md) for details. 
+Capacity pools must be at least 1 TiB and can be increased or decreased in 1-TiB intervals. Capacity pools contain volumes that range in size from a minimum of 100 GiB to a maximum of 100 TiB for regular volumes and up to 1 PiB for [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes). Volumes are assigned quotas that are subtracted from the capacity pool’s provisioned size. For an active volume, capacity consumption against the quota is based on logical (effective) capacity, being active filesystem data or snapshot data. See [How Azure NetApp Files snapshots work](snapshots-introduction.md) for details. 
 
 ### Pricing examples
 

articles/azure-netapp-files/azure-netapp-files-introduction.md

@@ -40,7 +40,7 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | Small-to-large volumes | Easily resize file volumes from 100 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.
 | 1-TiB minimum capacity pool size | 1-TiB capacity pool is a reduced-size storage pool compared to the initial 4-TiB minimum. | Save money by starting with a smaller storage footprint and lower entry point, without sacrificing performance or availability. Scale storage based on growth without high upfront costs.
 | 2,048-TiB maximum capacity pool | 2048-TiB capacity pool is an increased storage pool compared to the initial 500-TiB maximum. | Reduce waste by creating larger, pooled capacity and performance budget, and share and distribute across volumes.
-| 50-500 TiB large volumes | Store large volumes of data up to 500 TiB in a single volume. | Manage large datasets and high-performance workloads with ease.
+| 50-1,024 TiB large volumes | Store large volumes of data up to 1,024 TiB in a single volume. | Manage large datasets and high-performance workloads with ease.
 | User and group quotas | Set quotas on storage usage for individual users and groups. | Control storage usage and optimize resource allocation.
 | Virtual machine (VM) networked storage performance | Higher VM network throughput compared to disk IO limits enable more demanding workloads on smaller Azure VMs. | Improve application performance at a smaller VM footprint, improving overall efficiency and lowering application license cost.
 | Deep workload readiness | Seamless deployment and migration of any-size workload with well-documented deployment guides. | Easily migrate any workload of any size to the platform. Enjoy a seamless, cost-effective deployment and migration experience.

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

@@ -31,7 +31,8 @@ The following table describes resource limits for Azure NetApp Files:
 |  Maximum size of a single regular volume     |    100 TiB    |    No    |
 |  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) | 50 TiB |     No |
 | Large volume size increase | 30% of lowest provisioned size | Yes |
-|  Maximum size of a single [large volume](large-volumes-requirements-considerations.md)    |    500 TiB    |    No    |
+|  Maximum size of a single [large volume](large-volumes-requirements-considerations.md)    | 1,024 TiB |    No    |
+| Maximum size of a single large volume on dedicated capacity (preview) | 2,048 TiB | No |
 |  Maximum size of a single file     |    16 TiB    |    No    |    
 |  Maximum size of directory metadata in a single directory      |    320 MB    |    No    |    
 |  Maximum number of files in a single directory  | *Approximately* 4 million. <br> See [Determine if a directory is approaching the limit size](#directory-limit).  |    No    |   

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

@@ -73,11 +73,11 @@ When you use a manual QoS capacity pool with, for example, an SAP HANA system, a
 - A volume's capacity consumption counts against its pool's provisioned capacity.
 - A volume’s throughput consumption counts against its pool’s available throughput. See [Manual QoS type](#manual-qos-type).
 - Each volume belongs to only one pool, but a pool can contain multiple volumes. 
-- Volumes contain a capacity of between 100 GiB and 100 TiB. You can create a [large volume](#large-volumes) with a size of between 50 TiB and 500 TiB.
+- Volumes contain a capacity of between 100 GiB and 100 TiB. You can create a [large volume](#large-volumes) with a size of between 50 and 1 PiB.
 
 ## Large volumes
 
-Azure NetApp Files allows you to create volumes up to 500 TiB in size. 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. 
+Azure NetApp Files allows you to create large volumes up to 1 PiB in size. Large volumes begin at a capacity of 50 TiB and scale up to 1 PiB. 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/includes/large-volumes-notice.md

@@ -11,7 +11,7 @@ ms.custom: include file
 # azure-netapp-files-create-volumes
 ---
 
-Regular volumes quotas are between 100 GiB and 100 TiB. Large volume quotas range from 50 TiB to 500 TiB in size. If you intend for the volume quota to fall in the large volume range, select **Yes**. 
+Regular volumes quotas are between 100 GiB and 100 TiB. Large volume quotas range from 50 TiB to 1 PiB in size. If you intend for the volume quota to fall in the large volume range, select **Yes**. Volume quotas are entered in GiB.
 
 >[!IMPORTANT]
 > If this is your first time using large volumes, you must first [register the feature](../large-volumes-requirements-considerations.md#register-the-feature) and request [an increase in regional capacity quota](../azure-netapp-files-resource-limits.md#request-limit-increase).

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

@@ -18,19 +18,46 @@ This article describes the requirements and considerations you need to be aware
 The following requirements and considerations apply to large volumes. For performance considerations of *regular volumes*, see [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md).
 
 * A regular volume can’t be converted to a large volume.
-* You must create a large volume at a size of 50 TiB or larger. A single volume can't exceed 500 TiB.  
+* You must create a large volume at a size of 50 TiB or larger. A single volume can't exceed 1 PiB.  
 * 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.
 * You can't create a large volume with application volume groups.
 * Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes. To optimize multiple volume deployments for databases, use [application volume groups](application-volume-group-concept.md).
-* Throughput ceilings for the three performance tiers (Standard, Premium, and Ultra) of large volumes are based on the existing 100-TiB maximum capacity targets. You're able to grow to 500 TiB with the throughput ceiling per the following table:  
+* Throughput ceilings for the three performance tiers (Standard, Premium, and Ultra) of large volumes are based on the existing 100-TiB maximum capacity targets. You're able to grow to 1 PiB with the throughput ceiling per the following table:  
 
-    | Capacity tier | Volume size (TiB) | Throughput (MiB/s) |
-    | --- | --- | --- |
-    | Standard | 50 to 500 | 1,600 |
-    | Premium | 50 to 500 | 6,400 | 
-    | Ultra | 50 to 500 | 10,240 | 
+    <table><thead>
+      <tr>
+        <th></th>
+        <th colspan="2">Capacity</th>
+        <th colspan="2">Linear performance scaling per TiB up to maximum throughput </th>
+      </tr></thead>
+    <tbody>
+      <tr>
+        <td>Capacity tier</td>
+        <td>Minimum volume size<br>(TiB)</td>
+        <td>Maximum volume size (TiB)</td>
+        <td>Minimum throughput (MiB/s)</td>
+        <td>Maximum throughput (MiB/s)</td>
+      </tr>
+      <tr>
+        <td>Standard (16 MiB/s per TiB)</td>
+        <td>50</td>
+        <td>1,024</td>
+        <td>800</td>
+        <td>12,800</td>
+      </tr>
+      <tr>
+        <td>Premium (64 MiB/s per TiB)</td>
+        <td>50</td>
+        <td>1,024</td>
+        <td>3,200</td>
+        <td>12</td>
+      </tr>
+    </tbody>
+    </table>
+
+    \* 2-PiB large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team. 
 
 * Large volumes aren't currently supported with standard storage with cool access.
 
@@ -73,7 +100,7 @@ Support for Azure NetApp Files large volumes is available in the following regio
 >[!IMPORTANT]
 >Before you can use large volumes, you must first request [an increase in regional capacity quota](azure-netapp-files-resource-limits.md#request-limit-increase).
 
-Once your [regional capacity quota](regional-capacity-quota.md) has increased, you can create volumes that are up to 500 TiB in size. When creating a volume, after you designate the volume quota, you must select **Yes** for the **Large volume** field. Once created, you can manage your large volumes in the same manner as regular volumes. 
+Once your [regional capacity quota](regional-capacity-quota.md) has increased, you can create volumes that are up to 1 PiB in size. When creating a volume, after you designate the volume quota, you must select **Yes** for the **Large volume** field. Once created, you can manage your large volumes in the same manner as regular volumes. 
 
 ### Register the feature