Skip to main content
NetApp Knowledge Base

Why can the cloud tiered data copy from the local tier after the Cloud IC LIFs down?

Last Updated:

Applies to

  • ONTAP 9
  • FabricPool
  • Cloud Intercluster (IC) LIFs down
  • The imparied volume tiering policy is all


  • The data can still be read even though the Cloud Intercluster (IC) LIFs are down because the SSD blocks have not been reused yet.
  • When ONTAP tier data, ONTAP tier from the volume’s container file. Files inside the volume still have the old SSD blocks address in their indirect blocks.
  • When a read OPs comes in, WAFL first tries to use that SSD address. If SSD still has the block, all the context checks succeed and ONTAP uses that data to serve the read request. If the block has been reused, context checks fail and ONTAP redirects the read to the new cloud address ONTAP stored in the container file.
  • So it's expected behavior that the data can copy from the local tier when the IC LIFs are down as the volume still has the old SSD blocks address in their indirect blocks.

Additional Information

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.
Scan to view the article on your device