Skip to main content
NetApp Knowledge Base

Can FabricPool tiering be stopped immediately by changing the policy to None?

Last Updated:


Applies to

  • ONTAP 9.2 and later
  • FabricPool


Yes, Volumes set to use None (default) as their tiering policy will stop tiering cold data to the cloud tier.

  • Setting the tiering policy to None prevents new tiering
  • Volume data that has previously been moved to the cloud tier remains in the cloud tier until it becomes hot
  • When cold blocks in a volume are read, they are made hot and are automatically moved back to the local tier
  • Data that was in the process of being tiered before changing policy to None, will continue to tier. This can be up to the TLOG size (60GB before 9.13.1, 240GB in 9.13.1)

Additional Information

  • Disabling the InterCluster LIF is highly discouraged.
    • If Connection is lost to the clousd tier,  the user or application receives an error message because cold blocks that exist exclusively on the cloud tier are unavailable until it comes back online
    • Additionally, cold local tier data fails to be written to the cloud tier if the cloud tier is offline
  • Technical Report - FabricPool Best Practices


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.