Skip to main content
NetApp Stage KB

FabricPool Auto tiering policy is not tiering data as expected

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

 

 

Applies to

  • ONTAP 9
  • FlexGroup Volume
  • FabricPool
  • Tiering policy

Issue

  • Data tiering was not working as expected when configuring the Auto tiering policy in this way:
  1. FlexGroup Volume tiering-minimum-cooling-days 2
  2. object-store-name -tiering-fullness-threshold 0
  • Data tiering was not working as expected also after modifying the Auto tiering policy in this way:
  1. Flexgroup volume tiering-minimum-cooling-days 3
  2. object-store-name -tiering-fullness-threshold 30

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.