Skip to main content
NetApp Knowledge Base

FabricPool volume tiering does not start after changing tiering policy to All

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

Applies to

  • ONTAP 9
  • FabricPool aggregates

Issue

  • After changing the tiering policy of a volume  to “all” on a FabricPool-enabled aggregate, tiering does not start as expected.
  • The volume remains in the ready state, and no data is tiered to the object store.

Example:

Cluster1::> vol object-store tiering show -volume vol1 -instance

Vserver: demo_cluster
Volume: vol1
AggregateName: n1_aggr1
State: ready
TieringPolicy: all
TimeScanStarted: -
Footprint in ONTAPS3store: 0B 0%
...


cluster1::> vol show-footprint vol1

Vserver: demo_cluster
Volume: vol1


Feature                        Used      Used%
-----------------------------------------------
Volume Data Footprint           3.61TB     1%
Footprint in Performance Tier   3.66TB   100%
Footprint in ONTAPS3store         0B      0%
...

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.