Skip to main content
NetApp Knowledge Base

Cold data not tiered to cloud after SnapMirror

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

Applies to

  • ONTAP 9
  • FabricPool
  • SnapMirror

Issue

  • When SnapMirroring data from one FabricPool to another, data tiered to the Cloud / Capacity tier at the source may not be tiered on the destination
  • The discrepancy in tiering can be observed by running this command on the source and destination volume show-footprint -fields volume-blocks-footprint-bin0,volume-blocks-footprint-bin1 -volume-blocks-footprint-bin1
  • Note: These commands should only be expected to yield the same results when the SnapMirror relationship is in sync

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.