Storage limits
Suggest changes
PDFs
Cloud Volumes ONTAP has storage configuration limits to provide reliable operations. For best performance, do not configure your system at the maximum values.
Maximum system capacity by license
The maximum system capacity for a Cloud Volumes ONTAP system is determined by its license. The maximum system capacity includes disk-based storage plus object storage used for data tiering. NetApp doesn't support exceeding this limit.
For some configurations, disk limits prevent you from reaching the 368 TiB capacity limit by using disks alone. In those cases, you can reach the 368 TiB capacity limit by tiering inactive data to object storage. Refer to capacity and disk limits below for more details.
| License | Maximum system capacity (disks + object storage) |
|---|---|
Explore |
2 TiB (data tiering is not supported with Explore) |
Standard |
10 TiB |
Premium |
368 TiB |
BYOL |
368 TiB per license |
The capacity limit is for the entire HA pair. It is not per node. For example, if you use the Premium license, you can have up to 368 TiB of capacity between both nodes.
No, it doesn't. Data in an AWS HA pair is synchronously mirrored between the nodes so that the data is available in the event of failure. For example, if you purchase an 8 TiB disk on node A, Cloud Manager also allocates an 8 TiB disk on node B that is used for mirrored data. While 16 TiB of capacity was provisioned, only 8 TiB counts against the license limit.
Capacity and disk limits by AWS EC2 instance
Cloud Volumes ONTAP uses EBS volumes as disks. The disk limits below are specific to disks that contain user data. The limits do not include the boot disk and root disk.
The maximum EBS disk size is 16 TiB. The number of supported disks varies by instance type.
The tables below shows the maximum capacity by instance type with just EBS disks, and with disks and tiering to object storage.
Single node with a Premium license
| Instance type | Max disks per node | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
c4.4xlarge |
34 |
368 TiB |
368 TiB |
c4.8xlarge |
34 |
368 TiB |
368 TiB |
c5d.4xlarge |
23 |
368 TiB |
368 TiB |
c5d.9xlarge |
23 |
368 TiB |
368 TiB |
m4.4xlarge |
34 |
368 TiB |
368 TiB |
m5.4xlarge |
23 |
368 TiB |
368 TiB |
r4.2xlarge |
34 |
368 TiB |
368 TiB |
r5.2xlarge |
23 |
368 TiB |
368 TiB |
r5d.2xlarge |
23 |
368 TiB |
368 TiB |
Single node with one or more BYOL licenses
| Instance type | Max disks per node | Max system capacity with one license | Max system capacity with multiple licenses | ||
|---|---|---|---|---|---|
Disks alone |
Disks + data tiering |
Disks alone |
Disks + data tiering |
||
c4.4xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
c4.8xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
c5d.4xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
c5d.9xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
m4.xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
m4.2xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
m4.4xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
m5.xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
m5.2xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
m5.4xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
r4.xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
r4.2xlarge |
34 |
368 TiB |
368 TiB |
544 TiB |
368 TiB x each license |
r5.xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
r5.2xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
r5d.2xlarge |
23 |
368 TiB |
368 TiB |
368 TiB |
368 TiB x each license |
HA pairs with a Premium license
| Instance type | Max disks per node | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
c4.4xlarge |
31 |
368 TiB |
368 TiB |
c4.8xlarge |
31 |
368 TiB |
368 TiB |
c5d.4xlarge |
20 |
320 TiB |
368 TiB |
c5d.9xlarge |
20 |
320 TiB |
368 TiB |
m4.4xlarge |
31 |
368 TiB |
368 TiB |
m5.4xlarge |
20 |
320 TiB |
368 TiB |
r4.2xlarge |
31 |
368 TiB |
368 TiB |
r5.2xlarge |
20 |
320 TiB |
368 TiB |
r5d.2xlarge |
20 |
320 TiB |
368 TiB |
HA pairs with one or more BYOL licenses
| Instance type | Max disks per node | Max system capacity with one license | Max system capacity with multiple licenses | ||
|---|---|---|---|---|---|
Disks alone |
Disks + data tiering |
Disks alone |
Disks + data tiering |
||
c4.4xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
c4.8xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
c5d.4xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
c5d.9xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
m4.xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
m4.2xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
m4.4xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
m5.xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
m5.2xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
m5.4xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
r4.xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
r4.2xlarge |
31 |
368 TiB |
368 TiB |
496 TiB |
368 TiB x each license |
r5.xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
r5.2xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
r5d.2xlarge |
20 |
320 TiB |
368 TiB |
320 TiB |
368 TiB x each license |
Disk and tiering limits by Azure VM size
The disk limits below are specific to disks that contain user data. The limits do not include the boot disk and root disk. The tables below show the maximum system capacity by VM size with managed disks alone, and with disks and cold data tiering to object storage.
Disk limits are shown by VM size for Premium and BYOL licenses only because disk limits can’t be reached with Explore or Standard licenses due to system capacity limits.
-
Single node systems can use Standard HDD Managed Disks, Standard SSD Managed Disks, and Premium SSD Managed Disks, with up to 32 TiB per disk. The number of supported disks varies by VM size.
-
HA systems use Premium page blobs as disks, with up to 8 TiB per page blob. The number of supported disks varies by VM size.
Single node with a Premium license
| VM size | Max disks per node | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
DS3_v2 |
15 |
368 TiB |
Tiering not supported |
DS4_v2 |
31 |
368 TiB |
368 TiB |
DS5_v2 |
63 |
368 TiB |
368 TiB |
DS13_v2 |
31 |
368 TiB |
368 TiB |
DS14_v2 |
63 |
368 TiB |
368 TiB |
Single node with one or more BYOL licenses
|
For some VM types, you'll need several BYOL licenses to reach the max system capacity listed below. For example, you'd need 6 BYOL licenses to reach 2 PiB with DS5_v2. |
| VM size | Max disks per node | Max system capacity with one license | Max system capacity with multiple licenses | ||
|---|---|---|---|---|---|
Disks alone |
Disks + data tiering |
Disks alone |
Disks + data tiering |
||
DS3_v2 |
15 |
368 TiB |
Tiering not supported |
480 TiB |
Tiering not supported |
DS4_v2 |
31 |
368 TiB |
368 TiB |
896 TiB |
368 TiB x each license |
DS5_v2 |
63 |
368 TiB |
368 TiB |
896 TiB |
368 TiB x each license |
DS13_v2 |
31 |
368 TiB |
368 TiB |
896 TiB |
368 TiB x each license |
DS14_v2 |
63 |
368 TiB |
368 TiB |
896 TiB |
368 TiB x each license |
HA pairs with a Premium license
| VM size | Max data disks for an HA pair | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
DS4_v2 |
31 |
368 TiB |
Tiering not supported |
DS5_v2 |
63 |
368 TiB |
Tiering not supported |
DS13_v2 |
31 |
368 TiB |
Tiering not supported |
DS14_v2 |
63 |
368 TiB |
Tiering not supported |
DS15_v2 |
63 |
368 TiB |
Tiering not supported |
HA pairs with one or more BYOL licenses
|
|
For some VM types, you'll need several BYOL licenses to reach the max system capacity listed below. For example, you'd need 3 BYOL licenses to reach 1 PiB with DS5_v2. |
| VM size | Max data disks for an HA pair | Max system capacity with one license | Max system capacity with multiple licenses | ||
|---|---|---|---|---|---|
Disks alone |
Disks + data tiering |
Disks alone |
Disks + data tiering |
||
DS4_v2 |
31 |
368 TiB |
Tiering not supported |
248 TiB |
Tiering not supported |
DS5_v2 |
63 |
368 TiB |
Tiering not supported |
504 TiB |
Tiering not supported |
DS13_v2 |
31 |
368 TiB |
Tiering not supported |
248 TiB |
Tiering not supported |
DS14_v2 |
63 |
368 TiB |
Tiering not supported |
504 TiB |
Tiering not supported |
DS15_v2 |
63 |
368 TiB |
Tiering not supported |
504 TiB |
Tiering not supported |
Aggregate limits in AWS
Cloud Volumes ONTAP uses AWS volumes as disks and groups them into aggregates. Aggregates provide storage to volumes.
| Parameter | Limit |
|---|---|
Maximum number of aggregates |
Single node: Same as the disk limit |
Maximum aggregate size |
96 TiB of raw capacity 2 |
Disks per aggregate |
1-6 3 |
Maximum number of RAID groups per aggregate |
1 |
Notes:
-
It is not possible to create 18 aggregates on both nodes in an HA pair because doing so would exceed the data disk limit.
-
The aggregate capacity limit is based on the disks that comprise the aggregate. The limit does not include object storage used for data tiering.
-
All disks in an aggregate must be the same size.
Aggregate limits in Azure
Cloud Volumes ONTAP uses Azure storage as disks and groups them into aggregates. Aggregates provide storage to volumes.
| Parameter | Limit |
|---|---|
Maximum number of aggregates |
Same as the disk limit |
Maximum aggregate size |
200 TiB of raw capacity for single node 1 |
Disks per aggregate |
1-12 2 |
Maximum number of RAID groups per aggregate |
Single node: 1 |
Notes:
-
The aggregate capacity limit is based on the disks that comprise the aggregate. The limit does not include object storage used for data tiering.
-
All disks in an aggregate must be the same size.
Logical storage limits
| Logical storage | Parameter | Limit |
|---|---|---|
Storage virtual machines (SVMs) |
Maximum number for Cloud Volumes ONTAP |
One data-serving SVM and one destination SVM used for disaster recovery. You can activate the destination SVM for data access if there’s an outage on the source SVM. 1 |
Files |
Maximum size |
16 TiB |
Maximum per volume |
Volume size dependent, up to 2 billion |
|
FlexClone volumes |
Hierarchical clone depth 2 |
499 |
FlexVol volumes |
Maximum per node |
500 |
Minimum size |
20 MB |
|
Maximum size |
AWS: Dependent on the size of the aggregate 3 |
|
Qtrees |
Maximum per FlexVol volume |
4,995 |
Snapshot copies |
Maximum per FlexVol volume |
1,023 |
Notes:
-
Cloud Manager does not provide any setup or orchestration support for SVM disaster recovery. It also does not support storage-related tasks on an additional SVM. You must use System Manager or the CLI for SVM disaster recovery.
-
Hierarchical clone depth is the maximum depth of a nested hierarchy of FlexClone volumes that can be created from a single FlexVol volume.
-
Less than 100 TiB is supported because aggregates for this configuration are limited to 96 TiB of raw capacity.
iSCSI storage limits
| iSCSI storage | Parameter | Limit |
|---|---|---|
LUNs |
Maximum per node |
1,024 |
Maximum number of LUN maps |
1,024 |
|
Maximum size |
16 TiB |
|
Maximum per volume |
512 |
|
igroups |
Maximum per node |
256 |
Initiators |
Maximum per node |
512 |
Maximum per igroup |
128 |
|
iSCSI sessions |
Maximum per node |
1,024 |
LIFs |
Maximum per port |
32 |
Maximum per portset |
32 |
|
Portsets |
Maximum per node |
256 |