Skip to main content
NetApp Knowledge Base

Why did FabricPool take two extra days to tier data?

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

Applies to

  • ONTAP 9
  • FabricPool

Answer

Data was added after the cooling scanner ran for the day

 
Example:
 
  • Minimum cooling days is set to 2
  • Policy set to Auto
  • Fullness threshold has been reached
 
1st day: Data moved after scanner ran for that day.
2nd day: Scanner runs and discovers data.
3rd day: Scanner sees data again, but it is only 1 day cooled.
4th day: Scanner sees the data as cooled for 2 days and moves it.
 
 
Note: The data cooling scanner only runs once a day
 

Additional Information

To check your tiering policy and cooling days:
 
cluster1::> volume show -volume <vol-name> -fields tiering-policy, tiering-minimum-cooling-days
 
To check your fullness threshold:
 
cluster1::> aggr object-store show -fields tiering-fullness-threshold
 

Also see:

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.