Skip to main content
NetApp Knowledge Base

How does OnCommand Unified Manager (DFM) aggregate overcommitted Calculation work?

  1. Last updated
  2. Save as PDF
Views:
363
Visibility:
Public
Votes:
4
Category:
oncommand-unified-manager-core-package
Specialty:
legacy
Last Updated:

Applies to

OnCommand Unified Manager Core Package (DFM)

 

Answer

During overcommittment calculations, 'autogrow' is taken into account. OnCommand Unified Manager/ DFM treats autogrow as a method of thin provisioning. Therefore, it is included in the aggregate overcommitted calculations.

For example: If a volume size is 100GB, autogrow is enabled, and the 'maximum-size' is set to 200GB, the 'maximum-size' value (that is, 200GB in this case) is taken into account when calculating aggregate overcommitted.

 

Additional Information

additionalInformation_text

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.