|
| 1 | +--- |
| 2 | +title: Understand resizing guidelines for cache volumes in Azure NetApp Files |
| 3 | +description: Describes the resizing guidelines you must be aware of before resizing a cache volume. |
| 4 | +services: azure-netapp-files |
| 5 | +author: netapp-manishc |
| 6 | +ms.service: azure-netapp-files |
| 7 | +ms.topic: concept-article |
| 8 | +ms.date: 12/18/2025 |
| 9 | +ms.author: anfdocs |
| 10 | +ms.custom: references_regions |
| 11 | +# Customer intent: As a data administrator, I want to understand the guidelines to resize a cache volume. |
| 12 | +--- |
| 13 | + |
| 14 | +# Understand resizing guidelines for cache volumes in Azure NetApp Files |
| 15 | + |
| 16 | +This article describes the guidelines you need to be aware of before resizing an Azure NetApp Files cache volume. |
| 17 | + |
| 18 | +When a cache volume is created, one or more constituent volumes (CVs) are provisioned based on the size and the service level. The resize range of a cache volume is based on the number of CVs provisioned at creation time and the CV count cannot be changed. |
| 19 | + |
| 20 | +The following table shows CV count, minimum and maximum cache volume size and resize ranges per service level: |
| 21 | + |
| 22 | +| Service Level | CV count | Cache Size at Creation (Minimum GiB) | Cache Size at Creation (Maximum GiB) | Resize Range (Minimum GiB) | Resize Range (Maximum GiB) | |
| 23 | +|:---: |:---:|:---: |:---: |:---: |:---: | |
| 24 | +| Standard | 1 | 50 | 99 | 50 | 307,200 | |
| 25 | +| | 2 | 100 | 1,023 | 100 | 614,400 | |
| 26 | +| | 4 | 1,024 | 10,239 | 200 | 1,048,576 | |
| 27 | +| | 8 | 10,240 | 25,843 | 800 | 1,048,576 | |
| 28 | +| | 12 | 25,844 | 65,226 | 1,800 | 1,048,576 | |
| 29 | +| | 16 | 65,227 | 164,622 | 3,200 | 1,048,576 | |
| 30 | +| | 20 | 164,623 | 415,483 | 5,000 | 1,048,576 | |
| 31 | +| | 24 | 415,484 | 1,048,576 | 7,200 | 1,048,576 | |
| 32 | +| Service Level | CV count | Cache Size at Creation (Minimum GiB) | Cache Size at Creation (Maximum GiB) | Resize Range (Minimum GiB) | Resize Range (Maximum GiB) | |
| 33 | +| Premium | 1 | 50 | 99 | 50 | 307,200 | |
| 34 | +| | 2 | 100 | 1,023 | 100 | 614,400 | |
| 35 | +| | 4 | 1,024 | 10,239 | 200 | 1,048,576 | |
| 36 | +| | 8 | 10,240 | 22,148 | 400 | 1,048,576 | |
| 37 | +| | 16 | 22,149 | 47,905 | 1,600 | 1,048,576 | |
| 38 | +| | 24 | 47,906 | 103,618 | 3,600 | 1,048,576 | |
| 39 | +| | 32 | 103,619 | 224,122 | 6,400 | 1,048,576 | |
| 40 | +| | 40 | 224,123 | 484,765 | 10,000 | 1,048,576 | |
| 41 | +| | 48 | 484,766 | 1,048,576 | 14,400 | 1,048,576 | |
| 42 | +| Service Level | CV count | Cache Size at Creation (Minimum GiB) | Cache Size at Creation (Maximum GiB) | Resize Range (Minimum GiB) | Resize Range (Maximum GiB) | |
| 43 | +| Ultra, Flexible | 1 | 50 | 99 | 50 | 307,200 | |
| 44 | +| | 2 | 100 | 1,023 | 100 | 614,400 | |
| 45 | +| | 4 | 1,024 | 10,239 | 200 | 1,048,576 | |
| 46 | +| | 8 | 10,240 | 19,836 | 400 | 1,048,576 | |
| 47 | +| | 16 | 19,837 | 38,429 | 800 | 1,048,576 | |
| 48 | +| | 32 | 38,430 | 74,448 | 3,200 | 1,048,576 | |
| 49 | +| | 48 | 74,449 | 144,225 | 7,200 | 1,048,576 | |
| 50 | +| | 64 | 144,226 | 279,400 | 12,800 | 1,048,576 | |
| 51 | +| | 80 | 279,401 | 541,269 | 20,000 | 1,048,576 | |
| 52 | +| | 96 | 541,270 | 1,048,576 | 28,800 | 1,048,576 | |
| 53 | + |
| 54 | + |
| 55 | +**Example:** |
| 56 | + |
| 57 | +* Cache volume size at creation = 12,288 GiB |
| 58 | +* CV Count = 8 |
| 59 | +* Service level = Premium |
| 60 | +* Cache volume size can be decreased to 400 GiB |
| 61 | +* Cache volume size can be increased to 1,048,576 GiB |
| 62 | + |
| 63 | +If the desired size is larger or smaller than the resize range for that cache volume, then a new cache volume needs to be created with the desired size. |
| 64 | + |
| 65 | + |
| 66 | + |
0 commit comments