Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.

NetApp KCS Award

NetApp Knowledge Base

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

Views:
501
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

 

Applies to

  • ONTAP 9.2 and later
  • FabricPool

Answer

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 60GB.

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

 

Scan to view the article on your device