Resource limits for Azure NetApp Files

Understanding resource limits for Azure NetApp Files helps you manage your volumes.

Resource limits

The following table describes resource limits for Azure NetApp Files:

Resource Default limit Adjustable via support request
Regional capacity quota per subscription 25 TiB Yes
Number of NetApp accounts per Azure region per subscription 10 Yes
Number of capacity pools per NetApp account 25 Yes
Number of volumes per subscription 500 Yes
Number of volumes per capacity pool 500 Yes
Number of snapshots per volume 255 No
Number of subnets delegated to Azure NetApp Files (Microsoft.NetApp/volumes) per Azure Virtual Network 1 No
Number of used IPs in a VNet (including immediately peered VNets) with Azure NetApp Files 1000 No
Minimum size of a single capacity pool 4 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 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.
See Determine if a directory is approaching the limit size.
No
Maximum number of files (maxfiles) per volume 100 million 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
Number of cross-region replication data protection volumes (destination volumes) 10 Yes
Maximum numbers of policy-based (scheduled) backups per volume
  • Daily retention count: 1 (minimum) to 1019 (maximum)
  • Weekly retention count: 1 (minimum) to 1019 (maximum)
  • Monthly retention count: 1 (minimum) to 1019 (maximum)

  • The maximum daily, weekly, and monthly backup retention counts combined is 1019.
N
Maximum size of protected volume 100 TiB N
Maximum number of volumes that can be backed up per subscription 5 Y
Maximum number of manual backups per volume per day 5 Y

For more information, see Capacity management FAQs.

Determine if a directory is approaching the limit size

You can use the stat command from a client to see whether a directory is approaching the maximum size limit for directory metadata (320 MB).

For a 320-MB directory, the number of blocks is 655360, with each block size being 512 bytes. (That is, 320x1024x1024/512.) This number translates to approximately 4 million files maximum for a 320-MB directory. However, the actual number of maximum files might be lower, depending on factors such as the number of files containing non-ASCII characters in the directory. As such, you should use the stat command as follows to determine whether your directory is approaching its limit.

Examples:

[makam@cycrh6rtp07 ~]$ stat bin
File: 'bin'
Size: 4096            Blocks: 8          IO Block: 65536  directory

[makam@cycrh6rtp07 ~]$ stat tmp
File: 'tmp'
Size: 12288           Blocks: 24         IO Block: 65536  directory
 
[makam@cycrh6rtp07 ~]$ stat tmp1
File: 'tmp1'
Size: 4096            Blocks: 8          IO Block: 65536  directory

Maxfiles limits

Azure NetApp Files volumes have a limit called maxfiles. The maxfiles limit is the number of files a volume can contain. Linux file systems refer to the limit as inodes. The maxfiles limit for an Azure NetApp Files volume is indexed based on the size (quota) of the volume. The maxfiles limit for a volume increases or decreases at the rate of 20 million files per TiB of provisioned volume size.

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 20 million. Subsequent changes to the size of the volume would result in an automatic readjustment of the maxfiles limit based on the following rules:

Volume size (quota) Automatic readjustment of the maxfiles limit
<= 1 TiB 20 million
> 1 TiB but <= 2 TiB 40 million
> 2 TiB but <= 3 TiB 60 million
> 3 TiB but <= 4 TiB 80 million
> 4 TiB 100 million

If you have already allocated at least 4 TiB of quota for a volume, you can initiate a support request to increase the maxfiles (inodes) limit beyond 100 million. For every 100 million files you increase (or a fraction thereof), you need to increase the corresponding volume quota by 4 TiB. For example, if you increase the maxfiles limit from 100 million files to 200 million files (or any number in between), you need to increase the volume quota from 4 TiB to 8 TiB.

You can increase the maxfiles limit to 500 million if your volume quota is at least 20 TiB.

Request limit increase

You can create an Azure support request to increase the adjustable limits from the Resource Limits table.

  1. Go to New Support Request under Support + troubleshooting.

  2. Under the Problem description tab, provide the required information:

    1. For Issue Type, select Service and Subscription Limits (Quotas).
    2. For Subscription, select your subscription.
    3. For Quota Type, select Storage: Azure NetApp Files limits.

    Screenshot that shows the Problem Description tab.

  3. Under the Additional details tab, click Enter details in the Request Details field.

    Screenshot that shows the Details tab and the Enter Details field.

  4. To request limit increase, provide the following information in the Quota Details window that appears:

    1. In Quota Type, select the type of resource you want to increase.
      For example:

      • Regional Capacity Quota per Subscription (TiB)
      • Number of NetApp accounts per Azure region per subscription
      • Number of volumes per subscription
    2. In Region Requested, select your region.
      The current and default sizes are displayed under Quota State.

    3. Enter a value to request an increase for the quota type you specified.

    Screenshot that shows how to display and request increase for regional quota.

  5. Click Save and continue. Click Review + create to create the request.

Next steps