Storage limits in Google Cloud
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 capacity limit by using disks alone. You can reach the capacity limit by tiering inactive data to object storage. Refer to the disk limits below for more details.
| License | Maximum system capacity (disks + object storage) |
|---|---|
Freemium |
500 GB |
PAYGO Explore |
2 TB (data tiering is not supported with Explore) |
PAYGO Standard |
10 TB |
PAYGO Premium |
368 TB |
Node-based license |
2 PiB (requires multiple licenses) |
Capacity-based license |
2 PiB |
Disk and tiering limits
The table below shows the maximum system capacity with disks alone, and with disks and cold data tiering to object storage. The disk limits are specific to disks that contain user data. The limits do not include the boot disk and root disk.
| Parameter | Limit |
|---|---|
Maximum disks per system |
124 |
Maximum disk size |
16 TB |
Maximum system capacity with disks alone |
256 TB |
Maximum system capacity with disks and cold data tiering to a Google Cloud Storage bucket |
Depends on the license. See the table above. |
Aggregate limits
Cloud Volumes ONTAP groups Google Cloud disks into aggregates. Aggregates provide storage to volumes.
| Parameter | Limit |
|---|---|
Maximum number of data aggregates |
99 1 |
Maximum aggregate size |
96 TB of raw capacity 2 |
Disks per aggregate |
1-6 3 |
Maximum number of RAID groups per aggregate |
1 |
Notes:
-
The maximum number of data aggregates doesn't include the root aggregate.
-
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 TB |
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 |
100 TB |
|
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.
iSCSI storage limits
| iSCSI storage | Parameter | Limit |
|---|---|---|
LUNs |
Maximum per node |
1,024 |
Maximum number of LUN maps |
1,024 |
|
Maximum size |
16 TB |
|
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 |
1 |
Maximum per portset |
32 |
|
Portsets |
Maximum per node |
256 |