Skip to main content
NetApp Knowledge Base

How FabricPool data tiering behaves after breaking a SnapMirror relationship

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

Applies to

  • ONTAP 9
  • FabricPool-enabled volumes
  • StorageGRID object tier
  • SnapMirror

Answer

In case where source and destination volumes both had tiering policy set to “Auto” with a 31-day cooling period.

  • When a SnapMirror relationship is broken:

    • Both volumes become read/write.
    • Each volume follows its own tiering policy and cooling period.

  • After the SnapMirror relationship is re-enabled:

    • Data on the destination volume becomes eligible for tiering to StorageGRID once it remains inactive (no reads or writes) for the configured cooling period (31 days in this case).
    • The cooling period includes the time when the SnapMirror relationship was broken.
  • If the destination volume’s tiering policy is set to “Auto” (or “Snapshot-only”), and no new data is written, blocks older than the cooling period 31 days will be marked cold and tiered to StorageGRID.

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.