Skip to main content

Learn how ONTAP reports used storage

Contributors netapp-aherbin netapp-aoife netapp-andreajost netapp-lenida

The amount of used storage is reported in ONTAP System Manager as either logical used or used space and in the ONTAP command line interface (CLI) as either physical used space or effective-total-footprint. Whether these values include space used by snapshots depends on your ONTAP version and, if you are using the CLI, the ONTAP command you choose. Understanding how used capacity is reported helps you monitor storage usage accurately.

Capacity reporting in System Manager

Depending on your ONTAP version, System Manager uses the term logical used or used to report capacity.

Note In System Manager, capacity representations do not account for root storage tier (aggregate) capacities.

ONTAP Version

Term used to report capacity

Includes space used for snapshots?

Definition

9.13.1 and later

logical used

No.
Space used for snapshots is reported separately.

The usable space (the logical blocks) in a volume or local tier (aggregate) derived from the amount of used physical space plus the space savings realized from the application of storage efficiency features.

9.12.1-9.9.1

Logical used

Yes

Same as above

9.8-9.7

Used

Yes

Same as above

9.6-9.5

Used

No

The physical blocks of storage used in the volume or local tier (aggregate).

Capacity reporting in the CLI

The ONTAP CLI uses the physical used and effective-total-footprint parameters to report capacity.

Beginning with ONTAP 9.14.1, the physical used parameter does not include aggregate-level storage efficiency savings such as temperature-sensitive storage efficiency (TSSE), inline compression, compaction, and cross-volume deduplication. As a result, it does not fully reflect the volume's physical used space. In ONTAP 9.14.1 and later, use the vol show-footprint command with the effective_total_footprint parameter for a complete view of physical used space of a volume.

ONTAP Version Command Parameter Description

9.14.1 and later

volume show-footprint

effective_total_footprint

Reflects the actual disk space used, including savings from the aggregate.

volume show-space

physical used

Reflects volume-level storage efficiency savings, including savings from the aggregate.

volume show

physical used

Does not include aggregate-level storage efficiency savings, so does not accurately reflect the volume's physical used space for TSSE enabled platforms.

9.13.1 and earlier

volume show-footprint

effective_total_footprint

Reflects the actual disk space used, including savings from the aggregate.

volume show-space

physical used

Reflects only volume-level storage efficiency savings.

volume show

total physical used

Reflects only volume-level storage efficiency savings.

Data reduction rate

The data reduction rate indicates how much the amount of storage consumed by your data is reduced after storage efficiency features, such as compression, compaction, and deduplication, have been applied.

  • Beginning with ONTAP 9.20.1, the data reduction rate (DRR)is reported with and without reducible data. Reducible data is data on which space savings are realized after storage efficiency features are applied. In ONTAP 9.19.1 and earlier, the DRR includes both reducible and non-reducible data. Non-reducible data is data for which space savings are not realized after storage efficiency features are applied, or data to which storage efficiency features cannot be applied. The DRR without reducible data provides a more accurate reflection of space saved from ONTAP storage efficiency. Learn how to view the DRR.

  • Beginning with ONTAP 9.13.1, data reduction considers the results of most storage efficiency features, such as deduplication and compression; however, snapshots and thin provisioning are not counted as part of the data reduction ratio.

    • In ONTAP 9.12.1 and earlier, data reduction ratios are displayed as follows:

      • The data reduction value displayed on the Capacity panel is the overall ratio of all logical used space compared to physical used space, and it includes the benefits derived from using snapshots and other storage efficiency features.

      • When you display the details panel, you see both the Overall ratio that was displayed on the overview panel and ratio of logical used space used only by client data compared to physical used space used only by client data, referred to as Without snapshots and clones.

Capacity measurement terms

The following terms are used when describing capacity in System Manager:

  • Allocated capacity: The amount of space that has been allocated for volumes in a storage VM.

  • Available: The amount of physical space available to store data or to provision volumes in a storage VM or on a local tier.

  • Capacity across volumes: The sum of the used storage and available storage of all the volumes on a storage VM.

  • Client data: The amount of space used by client data (either physical or logical).

  • Committed: The amount of committed capacity for a local tier.

  • Logical used %: The percentage of the current logical used capacity compared to the provisioned size, excluding snapshot reserves. This value can be greater than 100%, because it includes efficiency savings in the volume.

  • Maximum capacity: The maximum amount of space allocated for volumes on a storage VM.

  • Physical used: The amount of capacity used in the physical blocks of a volume or local tier.

  • Physical used %: The percentage of capacity used in the physical blocks of a volume compared to the provisioned size.

  • Provisioned capacity: A file system (volume) that has been allocated from a Cloud Volumes ONTAP system and is ready to store user or application data.

  • Reserved: The amount of space reserved for already provisioned volumes in a local tier.

  • Used: The amount of space that contains data.

  • Used and reserved: The sum of physical used and reserved space.

Capacity of a storage VM

The maximum capacity of a storage VM is determined by the total allocated space for volumes plus the remaining unallocated space.

  • The allocated space for volumes is the sum of the used capacity and the sum of available capacity of FlexVol volumes, FlexGroup volumes, and FlexCache volumes.

  • The capacity of volumes is included in the sums, even when they are restricted, offline, or in the recovery queue after deletion.

  • If volumes are configured with auto-grow, the maximum autosize value of the volume is used in the sums. Without auto-grow, the actual capacity of the volume is used in the sums.

The following chart explains how the measurement of the capacity across volumes relates to the maximum capacity limit.

Maximum capacity limit comprises allocated space and available space and the capacity across volumes occupies only the allocated space.

Beginning with ONTAP 9.13.1, cluster administrators can enable a maximum capacity limit for a storage VM. For information on supported and unsupported configurations, see Manage ONTAP SVM capacity limits.

After the maximum capacity limit is set, it cannot be changed to a size that is less than the currently allocated capacity.

When a storage VM reaches its maximum capacity limit, certain operations cannot be performed. System Manager provides suggestions for next steps in Insights .

Capacity measurement units in System Manager

System Manager calculates storage capacity based on binary units of 1024 (210) bytes.

  • Beginning with ONTAP 9.10.1, storage capacity units are displayed in System Manager as KiB, MiB, GiB, TiB, and PiB.

  • In ONTAP 9.10.0 and earlier, these units are displayed in System Manager as KB, MB, GB, TB, and PB.

Note The units used in System Manager for throughput continue to be KB/s, MB/s, GB/s, TB/s, and PB/s for all releases of ONTAP.

Capacity unit displayed in System Manager for ONTAP 9.10.0 and earlier

Capacity unit displayed in System Manager for ONTAP 9.10.1 and later

Calculation

Value in bytes

KB

KiB

1024

1024 bytes

MB

MiB

1024 * 1024

1,048,576 bytes

GB

GiB

1024 * 1024 * 1024

1,073,741,824 bytes

TB

TiB

1024 * 1024 * 1024 * 1024

1,099,511,627,776 bytes

PB

PiB

1024 * 1024 * 1024 * 1024 * 1024

1,125,899,906,842,624 bytes