| title | FAQs About Azure NetApp Files | |
|---|---|---|
| description | Answers frequently asked questions (FAQs) about Azure NetApp Files capacity management. | |
| ms.service | azure-netapp-files | |
| ms.topic | concept-article | |
| author | b-hchen | |
| ms.author | anfdocs | |
| ms.date | 03/01/2025 | |
| ms.custom |
|
This article answers frequently asked questions (FAQs) about Azure NetApp Files capacity management.
Azure NetApp Files provides capacity pool and volume usage metrics. You can also use Azure Monitor to monitor usage for Azure NetApp Files. See Metrics for Azure NetApp Files for details.
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).
See Understand directory sizes in Azure NetApp Files for the limit and calculation.
Yes, the consumed snapshot capacity counts towards the provisioned space in the volume. In case the volume runs full, consider taking the following actions:
- Resize the volume.
- Remove older snapshots to free up space in the hosting volume.
No, Azure NetApp Files volumes and capacity pools don't auto-grow upon filling up. See Cost model for Azure NetApp Files.
You can use the community supported ANFCapacityManager tool to manage capacity-based alert rules. The tool can automatically increase volume sizes to prevent your volumes from running out of space.
No, the destination volume of a replication doesn't count towards hard volume quota.
No. Azure NetApp Files isn't supported by Azure Storage Explorer.
When deleting a very large amount of data in a volume (which can include snapshots), the space reclamation process can take time. Wait a few minutes for Azure NetApp Files to reclaim the space in the volume.