Skip to main content
NetApp Knowledge Base

CONTAP-801732: Sync relationship status differs between source and destination after destination reboot

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

Issue

After a disruptive reboot of the destination cluster, a Sync or StrictSync FlexVol consistency group relationship may show InSync on the destination while the source reports {}OutOfSync{}. The destination may remain incorrectly marked InSync if Fast Resync does not start after baseline gather, a volume move, or consistency group setup.
This status mismatch can make the relationship’s recovery point objective appear current when it is not. Performing a reverse resync while the relationship is in this state may result in data loss.
 

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.