- docs.netapp.com
- Cloud Docs
- BlueXP
- CloudVolumesONTAP9.12.1releasenotes
Contributors 
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 the system capacity limit. If you reach the licensed capacity limit, BlueXP displays an action required message and no longer allows you to add additional disks.
| License | Maximum system capacity (disks + object storage) |
|---|---|
Freemium | 500 GiB |
PAYGO Explore | 2 TiB (data tiering is not supported with Explore) |
PAYGO Standard | 10 TiB |
PAYGO Premium | 368 TiB |
Node-based license | 368 TiB per license |
Capacity-based license | 2 PiB |
For HA, is the license capacity limit per node or for the entire HA pair?
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.
Aggregate limits
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 1 | 384 TiB of raw capacity for single node 2 |
Disks per aggregate | 1-12 3 |
Maximum number of RAID groups per aggregate | 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.
If using node-based licensing, two BYOL licenses are required to reach 384 TiB.
All disks in an aggregate must be the same size.
Disk and tiering limits by VM size
Capacity limits are different depending on the VM size that you use and whether you’re using a single node system or an HA pair.
The following notes provide details about the numbers that you’ll see in the tables below:
The disk limits are specific to disks that contain user data.
(Video) Implement and manage storage in AzureThe limits do not include the root disk, core disk, and VNVRAM.
A maximum system capacity is listed when using disks alone and when using disks and cold data tiering to object storage.
Single node and HA systems which use managed disks have a maximum of 32 TiB per disk. The number of supported disks varies by VM size.
HA systems which use page blobs have a maximum of 8 TiB per page blob. The number of supported disks varies by VM size.
The 896 TiB disk-based limit that’s listed for single node systems with certain VM sizes is the tested limit.
Limits for capacity-based licensing
The following disk limits apply to Cloud Volumes ONTAP systems that use a capacity-based licensing package. Learn about Cloud Volumes ONTAP licensing options
Single node
| VM size | Max data disks per node | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
DS4_v2 | 29 | 896 TiB | 2 PiB |
DS5_v2 | 61 | 896 TiB | 2 PiB |
DS13_v2 | 29 | 896 TiB | 2 PiB |
DS14_v2 | 61 | 896 TiB | 2 PiB |
DS15_v2 | 61 | 896 TiB | 2 PiB |
E4s_v3 | 5 | 160 TiB | 2 PiB |
E8s_v3 | 13 | 416 TiB | 2 PiB |
E32s_v3 | 29 | 896 TiB | 2 PiB |
E48s_v3 | 29 | 896 TiB | 2 PiB |
E64is_v3 | 29 | 896 TiB | 2 PiB |
E4ds_v4 | 5 | 160 TiB | 2 PiB |
E8ds_v4 | 13 | 416 TiB | 2 PiB |
E32ds_v4 | 29 | 896 TiB | 2 PiB |
E48ds_v4 | 29 | 896 TiB | 2 PiB |
E80ids_v4 | 61 | 896 TiB | 2 PiB |
L8s_v3 | 12 | 384 TiB | 2 PiB |
L16s_v3 | 28 | 896 TiB | 2 PiB |
L32s_v3 | 28 | 896 TiB | 2 PiB |
HA pairs in a single availability zone with page blobs
| 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 | 29 | 232 TiB | 2 PiB |
DS5_v2 | 61 | 488 TiB | 2 PiB |
DS13_v2 | 29 | 232 TiB | 2 PiB |
DS14_v2 | 61 | 488 TiB | 2 PiB |
DS15_v2 | 61 | 488 TiB | 2 PiB |
E8s_v3 | 13 | 104 TiB | 2 PiB |
E48s_v3 | 29 | 232 TiB | 2 PiB |
E8ds_v4 | 13 | 104 TiB | 2 PiB |
E32ds_v4 | 29 | 232 TiB | 2 PiB |
E48ds_v4 | 29 | 232 TiB | 2 PiB |
E80ids_v4 | 61 | 488 TiB | 2 PiB |
| VM size | Max data disks for an HA pair | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
E8ds_v4 | 12 | 384 TiB | 2 PiB |
E32ds_v4 | 28 | 896 TiB | 2 PiB |
E48ds_v4 | 28 | 896 TiB | 2 PiB |
E80ids_v4 | 28 | 896 TiB | 2 PiB |
L16s_v3 | 28 | 896 TiB | 2 PiB |
L32s_v3 | 28 | 896 TiB | 2 PiB |
| VM size | Max data disks for an HA pair | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
E8ds_v4 | 12 | 384 TiB | 2 PiB |
E32ds_v4 | 28 | 896 TiB | 2 PiB |
E48ds_v4 | 28 | 896 TiB | 2 PiB |
E80ids_v4 | 28 | 896 TiB | 2 PiB |
Limits for node-based licensing
The following disk limits apply to Cloud Volumes ONTAP systems that use node-based licensing, which is the previous generation licensing model that enabled you to license Cloud Volumes ONTAP by node. Node-based licensing is still available for existing customers.
If you use node-based licensing, you can purchase multiple node-based licenses for a Cloud Volumes ONTAP BYOL system to allocate more than 368 TiB of capacity.
The number of licenses that you can purchase for a single node system or HA pair is unlimited. Be aware that disk limits can prevent you from reaching the capacity limit by using disks alone. You can go beyond the disk limit by tiering inactive data to object storage. Learn how to add additional system licenses to Cloud Volumes ONTAP.
Single node
Single node has two node-based licensing options: PAYGO Premium and BYOL.
Single node with PAYGO Premium
| VM size | Max data disks per node | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
DS5_v2 | 61 | 368 TiB | 368 TiB |
DS14_v2 | 61 | 368 TiB | 368 TiB |
DS15_v2 | 61 | 368 TiB | 368 TiB |
E32s_v3 | 29 | 368 TiB | 368 TiB |
E48s_v3 | 29 | 368 TiB | 368 TiB |
E64is_v3 | 29 | 368 TiB | 368 TiB |
E32ds_v4 | 29 | 368 TiB | 368 TiB |
E48ds_v4 | 29 | 368 TiB | 368 TiB |
E80ids_v4 | 61 | 368 TiB | 368 TiB |
Single node with BYOL
| VM size | Max data 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 | ||
DS4_v2 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
DS5_v2 | 61 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
DS13_v2 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
DS14_v2 | 61 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
DS15_v2 | 61 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
L8s_v2 | 13 | 368 TiB | 368 TiB | 416 TiB | 368 TiB x each license |
E4s_v3 | 5 | 160 TiB | 368 TiB | 160 TiB | 368 TiB x each license |
E8s_v3 | 13 | 368 TiB | 368 TiB | 416 TiB | 368 TiB x each license |
E32s_v3 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
E48s_v3 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
E64is_v3 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
E4ds_v4 | 5 | 160 TiB | 368 TiB | 160 TiB | 368 TiB x each license |
E8ds_v4 | 13 | 368 TiB | 368 TiB | 416 TiB | 368 TiB x each license |
E32ds_v4 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
E48ds_v4 | 29 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
E80ids_v4 | 61 | 368 TiB | 368 TiB | 896 TiB | 368 TiB x each license |
HA pairs
HA pairs have two configuration types: page blob and multiple availability zone. Each configuration has two node-based licensing options: PAYGO Premium and BYOL.
PAYGO Premium: HA pairs in single availability zone with page blobs
| VM size | Max data disks for an HA pair | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
DS5_v2 | 61 | 368 TiB | 368 TiB |
DS14_v2 | 61 | 368 TiB | 368 TiB |
DS15_v2 | 61 | 368 TiB | 368 TiB |
E8s_v3 | 13 | 104 TiB | 368 TiB |
E48s_v3 | 29 | 232 TiB | 368 TiB |
E32ds_v4 | 29 | 232 TiB | 368 TiB |
E48ds_v4 | 29 | 232 TiB | 368 TiB |
E80ids_v4 | 61 | 368 TiB | 368 TiB |
PAYGO Premium: HA pairs in a multiple availability zone configuration with shared managed disks
| VM size | Max data disks for an HA pair | Max system capacity with disks alone | Max system capacity with disks and data tiering |
|---|---|---|---|
E32ds_v4 | 28 | 368 TiB | 368 TiB |
E48ds_v4 | 28 | 368 TiB | 368 TiB |
E80ids_v4 | 28 | 368 TiB | 368 TiB |
BYOL: HA pairs in single availability zone with page blobs
| 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 | 29 | 232 TiB | 368 TiB | 232 TiB | 368 TiB x each license |
DS5_v2 | 61 | 368 TiB | 368 TiB | 488 TiB | 368 TiB x each license |
DS13_v2 | 29 | 232 TiB | 368 TiB | 232 TiB | 368 TiB x each license |
DS14_v2 | 61 | 368 TiB | 368 TiB | 488 TiB | 368 TiB x each license |
DS15_v2 | 61 | 368 TiB | 368 TiB | 488 TiB | 368 TiB x each license |
E8s_v3 | 13 | 104 TiB | 368 TiB | 104 TiB | 368 TiB x each license |
E48s_v3 | 29 | 232 TiB | 368 TiB | 232 TiB | 368 TiB x each license |
E8ds_v4 | 13 | 104 TiB | 368 TiB | 104 TiB | 368 TiB x each license |
E32ds_v4 | 29 | 232 TiB | 368 TiB | 232 TiB | 368 TiB x each license |
E48ds_v4 | 29 | 232 TiB | 368 TiB | 232 TiB | 368 TiB x each license |
E80ids_v4 | 61 | 368 TiB | 368 TiB | 488 TiB | 368 TiB x each license |
BYOL: HA pairs in a multiple availability zone configuration with shared managed disks
| 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 | ||
E8ds_v4 | 12 | 368 TiB | 368 TiB | 368 TiB | 368 TiB x each license |
E32ds_v4 | 28 | 368 TiB | 368 TiB | 368 TiB | 368 TiB x each license |
E48ds_v4 | 28 | 368 TiB | 368 TiB | 368 TiB | 368 TiB x each license |
E80ids_v4 | 28 | 368 TiB | 368 TiB | 368 TiB | 368 TiB x each license |
Storage VM limits
Some configurations enable you to create additional storage VMs (SVMs) for Cloud Volumes ONTAP.
These are the tested limits. While it is theoretically possible to configure additional storage VMs, it’s not supported.
Learn how to create additional storage VMs.
| License type | Storage VM limit |
|---|---|
Freemium | 24 storage VMs total 1,2 |
Capacity-based PAYGO or BYOL 3 | 24 storage VMs total 1,2 |
Node-based BYOL 4 | 24 storage VMs total 1,2 |
Node-based PAYGO |
|
These 24 storage VMs can serve data or be configured for disaster recovery (DR).
Each storage VM can have up to three LIFs where two are data LIFs and one is an SVM management LIF.
For capacity-based licensing, there are no extra licensing costs for additional storage VMs, but there is a 4 TiB minimum capacity charge per storage VM. For example, if you create two storage VMs and each has 2 TiB of provisioned capacity, you’ll be charged a total of 8 TiB.
For node-based BYOL, an add-on license is required for each additional data-serving storage VM beyond the first storage VM that comes with Cloud Volumes ONTAP by default. Contact your account team to obtain a storage VM add-on license.
Storage VMs that you configure for disaster recovery (DR) don’t require an add-on license (they are free of charge), but they do count against the storage VM limit. For example, if you have 12 data-serving storage VMs and 12 storage VMs configured for disaster recovery, then you’ve reached the limit and can’t create any additional storage VMs.
File and volume limits
| Logical storage | Parameter | Limit |
|---|---|---|
Files | Maximum size | 16 TiB |
Maximum per volume | Volume size dependent, up to 2 billion | |
FlexClone volumes | Hierarchical clone depth 1 | 499 |
FlexVol volumes | Maximum per node | 500 |
Minimum size | 20 MB | |
Maximum size | 100 TiB | |
Qtrees | Maximum per FlexVol volume | 4,995 |
Snapshot copies | Maximum per FlexVol volume | 1,023 |
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 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 |
FAQs
What is the maximum size of an Azure NetApp files volume? ›
Azure NetApp Files allows you to create volumes up to 500 TiB in size, exceeding the previous 100-TiB limit. Large volumes begin at a capacity of 102,401 GiB and scale up to 500 TiB. Regular Azure NetApp Files volumes are offered between 100 GiB and 102,400 GiB.
What is the minimum volume size for Azure NetApp files? ›If any volume is using Basic network features, the minimum size is 4 TiB.
What is the maximum capacity of NetApp? ›Maximum system capacity by license
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.
21 data disks is the limit for new deployments of Cloud Volumes ONTAP. If you upgrade a system that was created with version 9.7 or earlier, then the system continues to support 22 disks.
Is there a limit on Azure storage? ›...
Scale targets for standard storage accounts.
| Resource | Limit |
|---|---|
| Maximum number of storage accounts with standard endpoints per region per subscription, including standard and premium storage accounts. | 250 |
Each Azure subscription can have up to 200 storage accounts, each with up to 500 TiB (roughly 550 TB) of space. There are no limits to the number of blobs or files that you can put in a storage account.
How do I store large files in Azure? ›- Determine size of file chunk you want to process at a time.
- Read the number of bytes from your size into a buffer.
- Create a block ID to match your upload.
- Upload your buffer to Azure Blob Storage.
- Repeat until done.
Run the SQL query
Name your SQL query in the properties pane on the right. Publish your SQL query by pressing CTRL+S or selecting the Publish all button. Select the Run button to execute the SQL query. The blob count and total size per container are reported in the Results pane.
...
Azure increases the maximum size and performance of Azure Disks.
Storage capacity refers to how much disk space one or more storage devices provides. It measures how much data a computer system may contain. For an example, a computer with a 500GB hard drive has a storage capacity of 500 gigabytes. A network server with four 1TB drives, has a storage capacity of 4 terabytes.
What are the available storage capacity? ›
Available Storage Capacity means the capacity from the Storage Facility, expressed in whole MWs, that is available at a particular time to charge and discharge Energy. Available Storage Capacity has the meaning specified in Section 3.1(e).
Which of the following has maximum storage capacity? ›The correct answer is Terabyte.
How much capacity can a cloud storage hold? ›Google offers 15Gb of cloud storage per user. So, at minimum, each Google account, whether it is a consumer or Google Workspaces account, has access to a minimum of 15Gb of storage.
What is the maximum limit of free cloud storage? ›Google will automatically upgrade the storage cloud data limit on every Google Workspace account from 15GB to 1TB. You can continue using the current service and you will have access to 1TB of storage to store files, documents, and other stuff without any extra charges.
What is difference between LUN and volume in NetApp? ›LUN is a large file inside the volume. You can have multiple LUNs in the same volume. Total Volume size= data space + Snapshot reserve . Note that, if the snapshot copies grow to be bigger than the Snapshot reserve size, the volume data space will be used for extra snapshot space.
What are three types of storage available in Azure storage? ›Azure Queues: A messaging store for reliable messaging between application components. Azure Tables: A NoSQL store for schemaless storage of structured data. Azure Disks: Block-level storage volumes for Azure VMs.
What are the four types of storage that Azure storage can handle? ›- File.
- Blob.
- Queue.
- Table.
Go to your Azure Machine Learning workspace in the Azure portal. On the left pane, in the Support + troubleshooting section, select Usage + quotas to view your current quota limits and usage. Select a subscription to view the quota limits.
What is the difference between Azure file storage and blob? ›Azure File Storage and Blob Storage offer the same level of redundancy, but Azure Blob Storage is cheaper than File Storage. Azure File Storage provides the folder for the data storage, while Azure Blob Storage does not provide the folder. They give a flat structure for data storage.
What is the difference between Azure files and blob? ›What is the difference between blob and file storage? Azure Blob Storage is an object store used for storing vast amounts unstructured data, while Azure File Storage is a fully managed distributed file system based on the SMB protocol and looks like a typical hard drive once mounted.
What is standard storage in Azure? ›
Microsoft Azure offers two service tiers for its storage services: Standard Storage and Premium Storage. The Premium tier stores data on modern solid state drives (SSDs), while the Standard tier uses hard disk drives (HDDs).
How do you estimate the storage size? ›Multiply the length, width, and height of your belongings. If your larger items make a pile that measures 5 x 5 x 5 feet, you'd need a storage unit with at least 75 cubic feet.
How is maximum storage space calculated? ›- Usable Space = Total Sq. Ft. – Non-Storage Space Sq. Ft.
- 150,000 Sq. Ft. – 30,000 Sq. Ft. = 120,000 Sq. Ft.
- Storage Capacity = Usable Space in Sq. Ft. * Maximum Stack Height in Ft.
- 120,000 Sq. Ft. * 30 Ft. = 3,600,000 Cubic Feet.
- Ultra disks.
- Premium SSD v2.
- Premium SSDs (solid-state drives)
- Standard SSDs.
- Standard HDDs (hard disk drives)
Every device has an internal memory where it can store files and applications. The internal memory of devices can vary anywhere between 4 GB to 512GB.
What is the maximum volume size that Azure backup can protect? ›Individual disk size can be up to 32 TB and a maximum of 256 TB combined for all disks in a VM.
How do I increase NetApp volume size in Azure? ›Resize a volume using the Azure portal
From the NetApp Account view, go to Volumes, and select the volume that you want to resize. Right-click the volume name or select the "…" icon at the end of the volume's row to display the context menu. Select Resize.
Maximum Block Size is 100 MB by design, There are different ways you can upload large files to Blob.