Storage limits for ONTAP Cloud 9.3 Edit on GitHub Request doc changes

ONTAP Cloud 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 for an ONTAP Cloud system is model specific. ONTAP Cloud configurations that support a lower raw capacity limit cannot reach some of the size and disk limits. All limits are per ONTAP Cloud node.

Physical storage limits for ONTAP Cloud 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

Minimum number of disks per aggregate

1

Maximum number of disks per aggregate

6

Maximum number of data disks across all aggregates 3

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 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.

Physical storage limits for ONTAP Cloud in Azure

Physical storage Parameter Limit

Aggregates and disks

Maximum number of aggregates

63

Maximum aggregate size

48 TB of raw capacity 1

Minimum number of disks per aggregate

1

Maximum number of disks per aggregate

12

Maximum number of data disks across all aggregates 2

63

RAID groups

Maximum per aggregate

1

Notes:

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

  2. 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

255

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