Resize a capacity pool or a volume
You can change the size of a capacity pool or a volume as necessary, for example, when a volume or capacity pool fills up.
For information about monitoring a volume’s capacity, see Monitor the capacity of a volume.
Resize the capacity pool using the Azure portal
You can change the capacity pool size in 1-TiB increments or decrements. However, the capacity pool size cannot be smaller than the sum of the capacity of the volumes hosted in the pool, with a minimum of 4TiB. Resizing the capacity pool changes the purchased Azure NetApp Files capacity.
From the NetApp Account view, go to Capacity pools, and click the capacity pool that you want to resize.
Right-click the capacity pool name or click the "…" icon at the end of the capacity pool row to display the context menu. Click Resize.
In the Resize pool window, specify the pool size. Click OK.
Resize a volume using the Azure portal
You can change the size of a volume as necessary. A volume's capacity consumption counts against its pool's provisioned capacity.
From the NetApp Account view, go to Volumes, and click the volume that you want to resize.
Right-click the volume name or click the "…" icon at the end of the volume's row to display the context menu. Click Resize.
In the Update volume quota window, specify the quota for the volume. Click OK.
Resizing the capacity pool or a volume using Azure CLI
You can use the following commands of the Azure command line (CLI) tools to resize a capacity pool or a volume:
Resizing the capacity pool or a volume using REST API
You can build automation to handle the capacity pool and volume size change.
The REST API specification and example code for Azure NetApp Files are available through the resource-manager GitHub directory.
Resize a cross-region replication destination volume
In a cross-region replication relationship, a destination volume is automatically resized based on the size of the source volume. As such, you don’t need to resize the destination volume separately. This automatic resizing behavior is applicable when the volumes are in an active replication relationship, or when replication peering is broken with the resync operation.
The following table describes the destination volume resizing behavior based on the Mirror state:
|Mirror state||Destination volume resizing behavior|
|Mirrored||When the destination volume has been initialized and is ready to receive mirroring updates, resizing the source volume automatically resizes the destination volumes.|
|Broken||When you resize the source volume and the Mirror state is broken, the destination volume is automatically resized with the resync operation.|
|Uninitialized||When you resize the source volume and the Mirror state is still uninitialized, resizing the destination volume needs to be done manually. As such, it's recommended that you wait for the initialization to complete (that is, when the Mirror state becomes mirrored) to resize the source volume.|
Ensure that you have enough headroom in the capacity pools for both the source and the destination volumes of cross-region replication. When you resize the source volume, the destination volume is automatically resized. But if the capacity pool hosting the destination volume doesn’t have enough headroom, the resizing of both the source and the destination volumes will fail.
Submit and view feedback for