Merge pull request #209963 from b-ahibbard/anf-large-volumes-2022.09

Large volumes preview

Author: v-ccolin

articles/azure-netapp-files/TOC.yml

@@ -13,7 +13,7 @@
   items:
   - name: Set up Azure NetApp Files and create an NFS volume
     href: azure-netapp-files-quickstart-set-up-account-create-volumes.md
-# - name: Tutorials
+# - name: Tutorials 
 # - name: Samples
 - name: Concepts
   items:
@@ -45,6 +45,8 @@
       href: volume-hard-quota-guidelines.md
     - name: Regional capacity quota
       href: regional-capacity-quota.md
+    - name: Requirements and considerations for large volumes
+      href: large-volumes-requirements-considerations.md
   - name: Performance
     items:
     - name: Performance considerations for Azure NetApp Files

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 02/02/2023
+ms.date: 02/21/2023
 ms.author: anfdocs
 ---
 # Create an SMB volume for Azure NetApp Files
@@ -32,14 +32,14 @@ Before creating an SMB volume, you need to create an Active Directory connection
 
 ## Add an SMB volume
 
-1. Click the **Volumes** blade from the Capacity Pools blade. 
+1. Select the **Volumes** blade from the Capacity Pools blade. 
 
     ![Navigate to Volumes](../media/azure-netapp-files/azure-netapp-files-navigate-to-volumes.png)
 
-2. Click **+ Add volume** to create a volume.  
+2. Select **+ Add volume** to create a volume.  
     The Create a Volume window appears.
 
-3. In the Create a Volume window, click **Create** and provide information for the following fields under the Basics tab:   
+3. In the Create a Volume window, select **Create** and provide information for the following fields under the Basics tab:   
     * **Volume name**      
         Specify the name for the volume that you are creating.   
 
@@ -53,6 +53,10 @@ Before creating an SMB volume, you need to create an Active Directory connection
 
         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**.  
+        [!INCLUDE [Large volumes warning](includes/large-volumes-notice.md)]
+
     * **Throughput (MiB/S)**   
         If the volume is created in a manual QoS capacity pool, specify the throughput you want for the volume.   
 
@@ -67,7 +71,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
         Specify the subnet that you want to use for the volume.  
         The subnet you specify must be delegated to Azure NetApp Files. 
 
-        If you haven't delegated a subnet, you can click **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.   
+        If you haven't delegated a subnet, you can select **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.   
 
         ![Create a volume](../media/azure-netapp-files/azure-netapp-files-new-volume.png)
 
@@ -79,13 +83,13 @@ Before creating an SMB volume, you need to create an Active Directory connection
     * **Availability zone**   
         This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
 
-    * If you want to apply an existing snapshot policy to the volume, click **Show advanced section** to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu. 
+    * If you want to apply an existing snapshot policy to the volume, select **Show advanced section** to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu. 
 
         For information about creating a snapshot policy, see [Manage snapshot policies](snapshots-manage-policy.md).
 
         ![Show advanced selection](../media/azure-netapp-files/volume-create-advanced-selection.png)
 
-4. Click **Protocol** and complete the following information:  
+4. Select **Protocol** and complete the following information:  
     * Select **SMB** as the protocol type for the volume.  
 
     * Select your **Active Directory** connection from the drop-down list.  
@@ -130,7 +134,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
 
     ![Screenshot that describes the Protocol tab of creating an SMB volume.](../media/azure-netapp-files/azure-netapp-files-protocol-smb.png)
 
-5. Click **Review + Create** to review the volume details.  Then click **Create** to create the SMB volume.
+5. Select **Review + Create** to review the volume details. Then select **Create** to create the SMB volume.
 
     The volume you created appears in the Volumes page. 
 
@@ -163,9 +167,10 @@ You can modify SMB share permissions using Microsoft Management Console (MMC).
 ## Next steps  
 
 * [Manage availability zone volume placement for Azure NetApp Files](manage-availability-zone-volume-placement.md)
+* [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)
 * [Mount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)
-* [Enable Active Directory Domain Services (ADDS) LDAP authentication for NFS volumes](configure-ldap-over-tls.md) 
+* [Enable Active Directory Domain Services (AD DS) LDAP authentication for NFS volumes](configure-ldap-over-tls.md) 
 * [Enable Continuous Availability on existing SMB volumes](enable-continuous-availability-existing-SMB.md)
 * [SMB encryption](azure-netapp-files-smb-performance.md#smb-encryption)
 * [Troubleshoot volume errors for Azure NetApp Files](troubleshoot-volumes.md)

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 11/08/2022
+ms.date: 02/23/2023
 ms.author: anfdocs
 ---
 # Create an NFS volume for Azure NetApp Files
@@ -66,6 +66,10 @@ 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**.
+        [!INCLUDE [Large volumes warning](includes/large-volumes-notice.md)]
+
     * **Throughput (MiB/S)**   
         If the volume is created in a manual QoS capacity pool, specify the throughput you want for the volume.   
 
@@ -145,3 +149,4 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
 * [Learn about virtual network integration for Azure services](../virtual-network/virtual-network-for-azure-services.md)
 * [Configure access control lists on NFSv4.1 with Azure NetApp Files](configure-access-control-lists.md)
 * [Application resilience FAQs for Azure NetApp Files](faq-application-resilience.md)
+* [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 02/21/2023
+ms.date: 02/23/2023
 ms.author: anfdocs
 ---
 # Resource limits for Azure NetApp Files
@@ -31,15 +31,17 @@ The following table describes resource limits for Azure NetApp Files:
 |  Number of volumes per subscription   |    500     |   Yes   |
 |  Number of volumes per capacity pool     |    500   |    Yes     |
 |  Number of snapshots per volume       |    255     |    No        |
-|  Number of IPs in a VNet (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |   <ul><li>**Basic**: 1000</li><li>**Standard**: [Same standard limits as VMs](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)</li></ul>  |    No    |
+|  Number of IPs in a virtual network (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |   <ul><li>**Basic**: 1000</li><li>**Standard**: [Same standard limits as VMs](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)</li></ul>  |    No    |
 |  Minimum size of a single capacity pool   |  2 TiB*     |    No  |
-|  Maximum size of a single capacity pool    |  500 TiB   |   No   |
-|  Minimum size of a single volume    |    100 GiB    |    No    |
-|  Maximum size of a single volume     |    100 TiB    |    No    |
+|  Maximum size of a single capacity pool    |  500 TiB   |   Yes   |
+|  Minimum size of a single regular volume    |    100 GiB    |    No    |
+|  Maximum size of a single regular volume     |    100 TiB    |    No    |
+|  Minimum size of a single [large volume](large-volumes-requirements-considerations.md) |     102,401 GiB |     No |
+|  Maximum size of a single large volume     |    500 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    |   
-|  Maximum number of files ([`maxfiles`](#maxfiles)) per volume     |    106,255,630    |    Yes    |    
+|  Maximum number of files [`maxfiles`](#maxfiles) per volume     |    106,255,630    |    Yes    |    
 |  Maximum number of export policy rules per volume     |    5  |    No    | 
 |  Minimum assigned throughput for a manual QoS volume     |    1 MiB/s   |    No    |    
 |  Maximum assigned throughput for a manual QoS volume     |    4,500 MiB/s    |    No    |    
@@ -84,13 +86,15 @@ Azure NetApp Files volumes have a limit called *`maxfiles`*. The `maxfiles` limi
 
 The service dynamically adjusts the `maxfiles` limit for a volume based on its provisioned size. For example, a volume configured initially with a size of 1 TiB would have a `maxfiles` limit of 21,251,126. Subsequent changes to the size of the volume would result in an automatic readjustment of the `maxfiles` limit based on the following rules: 
 
+**For volumes up to 100 TiB in size:**
+
 |    Volume size (quota)     |  Automatic readjustment of the `maxfiles` limit    |
 |----------------------------|-------------------|
-|    <= 1 TiB                |     21,251,126    |
+|    <= 1 TiB                |    21,251,126     |
 |    > 1 TiB but <= 2 TiB    |    42,502,252     |
 |    > 2 TiB but <= 3 TiB    |    63,753,378     |
 |    > 3 TiB but <= 4 TiB    |    85,004,504     |
-|    > 4 TiB                 |     106,255,630   |
+|    > 4 TiB but <= 100 TiB  |    106,255,630    |
 
 >[!IMPORTANT]
 > If your volume has a volume size (quota) of more than 4 TiB and you want to increase the `maxfiles` limit, you must initiate [a support request](#request-limit-increase).
@@ -102,6 +106,16 @@ You can increase the `maxfiles` limit to 531,278,150 if your volume quota is at
 >[!IMPORTANT]
 > 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, if you have crossed the 63,753,378 `maxfiles` limit, 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 |
+             
+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.
+ 
+The maximum `maxfiles` value for a 500 TiB volume is 10,625,563,000 files.
+
 You cannot set `maxfiles` limits for data protection volumes via a quota request.  Azure NetApp Files automatically increases the `maxfiles` limit of a data protection volume to accommodate the number of files replicated to the volume.  When a failover happens to a data protection volume, the `maxfiles` limit remains the last value before the failover.  In this situation, you can submit a `maxfiles` [quota request](#request-limit-increase) for the volume.
 
 ## Request limit increase
@@ -143,6 +157,7 @@ You can create an Azure support request to increase the adjustable limits from t
 ## Next steps  
 
 - [Understand the storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
+- [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)
 - [Cost model for Azure NetApp Files](azure-netapp-files-cost-model.md)
 - [Regional capacity quota for Azure NetApp Files](regional-capacity-quota.md)
 - [Request region access for Azure NetApp Files](request-region-access.md)

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 02/21/2023
+ms.date: 02/23/2023
 ms.author: anfdocs
 ---
 # Storage hierarchy of Azure NetApp Files
@@ -41,7 +41,7 @@ Understanding how capacity pools work helps you select the right capacity pool t
 ### General rules of capacity pools
 
 - A capacity pool is measured by its provisioned capacity.   
-    For more information, see [QoS types](#qos_types).
+    For more information, see [QoS types](#qos_types).  
 - The capacity is provisioned by the fixed SKUs that you purchased (for example, a 4-TiB capacity).
 - A capacity pool can have only one service level.  
 - Each capacity pool can belong to only one NetApp account. However, you can have multiple capacity pools within a NetApp account.  
@@ -51,7 +51,7 @@ Understanding how capacity pools work helps you select the right capacity pool t
 
 ### <a name="qos_types"></a>Quality of Service (QoS) types for capacity pools
 
-The QoS type is an attribute of a capacity pool. Azure NetApp Files provides two QoS types of capacity pools--*auto (default)* and *manual*. 
+The QoS type is an attribute of a capacity pool. Azure NetApp Files provides two QoS types of capacity pools: *auto (default)* and *manual*. 
 
 #### *Automatic (or auto)* QoS type  
 
@@ -71,14 +71,21 @@ In a manual QoS capacity pool, you can assign the capacity and throughput for a
 
 ##### Example of using manual QoS
 
-When you use a manual QoS capacity pool with, for example, an SAP HANA system, an Oracle database, or other workloads requiring multiple volumes, the capacity pool can be used to create these application volumes.  Each volume can provide the individual size and throughput to meet the application requirements.  See [Throughput limit examples of volumes in a manual QoS capacity pool](azure-netapp-files-service-levels.md#throughput-limit-examples-of-volumes-in-a-manual-qos-capacity-pool) for details about the benefits.  
+When you use a manual QoS capacity pool with, for example, an SAP HANA system, an Oracle database, or other workloads requiring multiple volumes, the capacity pool can be used to create these application volumes.  Each volume can provide the individual size and throughput to meet the application requirements. See [Throughput limit examples of volumes in a manual QoS capacity pool](azure-netapp-files-service-levels.md#throughput-limit-examples-of-volumes-in-a-manual-qos-capacity-pool) for details about the benefits.  
 
 ## <a name="volumes"></a>Volumes
 
 - A volume is measured by logical capacity consumption and is scalable. 
 - 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 4 TiB and 100 TiB. You can create a [large volume](#large-volumes) with a size of between 100 TiB and 500 TiB.
+
+## 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, whereas regular Azure NetApp Files volumes, which are offered between 100 GiB and 102,400 GiB. 
+
+For more information, see [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md).
 
 ## Next steps
 
@@ -87,3 +94,4 @@ When you use a manual QoS capacity pool with, for example, an SAP HANA system, a
 - [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md)
 - [Create a capacity pool](azure-netapp-files-set-up-capacity-pool.md)
 - [Manage a manual QoS capacity pool](manage-manual-qos-capacity-pool.md)
+- [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)