Storage limits for Cloud Volumes ONTAP 9.4 Edit on GitHub Request doc changes

Cloud Volumes ONTAP has storage configuration limits to provide reliable operations. For best performance, do not configure your system at the maximum values.

The following sections list limits for aggregates, volumes, LUNs, and related storage objects. Note that the maximum capacity is model specific. Cloud Volumes ONTAP configurations that support a lower raw capacity limit cannot reach some of the size and disk limits. All limits are per Cloud Volumes ONTAP node.

System capacity limit

A system’s capacity limit depends on the Cloud Volumes ONTAP license that you choose for the system:

License Capacity limit

Explore

2 TB

Standard

10 TB

Premium

  • AWS: 368 TB (360 TB for HA)

  • Azure: 252 TB

BYOL

Notes:

  1. If you enable data tiering, a system’s capacity limit stays the same. The capacity limit includes both disks and object storage.

  2. In AWS, an HA pair’s mirrored data does not count against the system capacity limit.

    Data in an HA pair is synchronously mirrored between the nodes so that the data is available in the event of failure. If you purchase an 8 TB disk on node A, Cloud Manager also allocates an 8 TB disk on node B that is used for mirrored data. While 16 TB of capacity was provisioned, only 8 TB counts against the license limit.

Aggregate and disk limits for Cloud Volumes ONTAP in AWS

Physical storage Parameter Limit

Aggregates and disks

Maximum number of aggregates

35 for single-node configurations
18 per node in an HA configuration 1

Maximum aggregate size

96 TB of raw capacity 2, 3

Minimum number of disks per aggregate

1

Maximum number of disks per aggregate

6

Maximum number of data disks across all aggregates 4

35 for single-node configurations
32 per node in an HA configuration

RAID groups

Maximum per aggregate

1

Notes:

  1. It is not possible to create 18 aggregates on both nodes in an HA pair because doing so would exceed the data disk limit.

  2. The maximum usable capacity of a 96 TB aggregate is 85.05 TB.

  3. The aggregate capacity limit is based on the disks that comprise the aggregate. The limit does not include object storage used for data tiering.

  4. The data disk limit is specific to disks that contain user data. The boot disk and root disk for each node are not included in this limit.

Aggregate and disk limits for Cloud Volumes ONTAP in Azure

Physical storage Parameter Limit

Aggregates and disks

Maximum number of aggregates

63

Maximum aggregate size

48 TB of raw capacity 1, 2

Minimum number of disks per aggregate

1

Maximum number of disks per aggregate

12

Maximum number of data disks across all aggregates 3

63

RAID groups

Maximum per aggregate

1

Notes:

  1. The maximum usable capacity of a 48 TB aggregate is 42.52 TB.

  2. The aggregate capacity limit is based on the disks that comprise the aggregate. The limit does not include object storage used for data tiering.

  3. The data disk limit is specific to disks that contain user data. The boot disk and root disk for each node are not included in this limit.

Logical storage limits

Logical storage Parameter Limit

Storage virtual machines (SVMs)

Maximum per node

One data-serving SVM and one or more SVMs used for disaster recovery 1

Files

Maximum size

Volume size dependent

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: 76.55 TB of fully provisioned capacity 3
Azure: 38.27 TB of fully provisioned capacity 3

Qtrees

Maximum per FlexVol volume

4,995

Snapshot copies

Maximum per FlexVol volume

1,023

Notes:

  1. Cloud Manager does not provide any setup or orchestration support for SVM disaster recovery. It also does not support storage-related tasks on any additional SVMs. You must use System Manager or the CLI for SVM disaster recovery.

  2. Hierarchical clone depth is the maximum depth of a nested hierarchy of FlexClone volumes that can be created from a single FlexVol volume.

  3. The specified limit is based on the assumption that you use Cloud Manager to create a volume and that you keep the aggregate free space ratio at 10 percent, which Cloud Manager sets by default.

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

32

Maximum per portset

32

Portsets

Maximum per node

256