Skip to main content

Manage SVM capacity limits

Contributors netapp-ahibbard netapp-dbagwell netapp-lenida
PDFs

Beginning with ONTAP 9.13.1, you can set a maximum capacity for a storage VM (SVM). You can also configure alerts when the SVM approaches a threshold capacity level.

About this task

Capacity on an SVM is calculated as the sum of FlexVols, FlexGroup volumes, FlexClones, FlexCache volumes. Volumes impact capacity calculation even if they are restricted, offline, or in the recovery queue after deletion. If you have volumes configured with auto-grow, the maximum autosize value of the volume will be calculated toward the SVM size; without auto-grow, the actual size of the volume will be calculated.

The following table captures how autosize-mode parameters impact the capacity calculation.

autosize-mode off

Size parameter will be used for computation

autosize-mode grow

The max-autosize parameter will be used for computation

autosize-mode grow-shrink

The max-autosize parameter will be used for computation
Before you begin

  • You must be a cluster administrator to set an SVM limit.

  • Beginning with ONTAP 9.16.1, storage limits can be configured for SVMs that contain data protection volumes, including the following data protection types:

    • FlexVol volumes in asynchronous DR without cascade

    • FlexVol volumes in synchronous DR (both sync and strict-sync policies)

    • Restore

  • Storage limits for SVMs is not supported for the following configurations:

    • SnapMirror vault relationships

    • SnapMirror active sync

    • FlexGroup volumes

    • Consistency groups

    • SVM DR

    • Cascades

    • MetroCluster

  • When you migrate an SVM, the source SVM cannot have a storage limit enabled. To complete the migrate operation, disable the storage limit on the source then complete the migration.

  • SVM capacity is distinct from quotas. Quotas cannot exceed the max size.

  • You cannot set a storage limit when other operations are in progress on the SVM. Use the job show vserver <svm_name> command to see existing jobs. Try running the command again when any jobs have been completed.

Capacity impact

When you reach the capacity limit, the following operations will fail:

  • Creating a LUN, namespace, or volume

  • Cloning a LUN, namespace, or volume

  • Modifying a LUN, namespace, or volume

  • Increasing the size of a LUN, namespace, or volume

  • Expanding a LUN, namespace, or volume

  • Rehosting a LUN, namespace, or volume

Set a capacity limit on a new SVM

System Manager
Steps

  1. Select Storage > Storage VMs.

  2. Select Add icon to create the SVM.

  3. Name the SVM and select an Access protocol.

  4. Under Storage VM settings, select Enable maximum capacity limit.

    Provide a maximum capacity size for the SVM.

  5. Select Save.

Set or modify a capacity limit on an existing SVM

You can set a capacity limit and threshold alert on an existing SVM or disable a capacity limit.

Once you set the capacity limit, you cannot modify the limit to a value less than the currently allocated capacity.

System Manager
Steps

  1. Select Storage > Storage VMs.

  2. Select the SVM you want to modify. Next to the name of the SVM, select Menu options icon then Edit.

  3. To enable a capacity limit, select the box next to Enable capacity limit. Enter a value for the Maximum capacity and a percentage value for Alert threshold.

    If you wish to disable the capacity limit, uncheck the box next Enable capacity limit.

  4. Select Save.

Reaching capacity limits

When you reach the maximum capacity or the alert threshold, you can consult the vserver.storage.threshold EMS messages or use the Insights page in System Manager to learn about possible actions. Possible resolutions include:

  • Editing the SVM maximum capacity limits

  • Purging the volumes recovery queue to free up space

  • Delete snapshot to provide space for the volume

Related information