Skip to main content
NetApp Knowledge Base

Unable to quiesce or break SnapMirror sync relationship after losing connection to primary cluster

  1. Last updated
  2. Save as PDF
Views:
199
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
DP
Last Updated:

Applies to

  • ONTAP 9
  • Snapmirror-Synchronous (SM-S)

Issue

  • The SnapMirror Synchronous (SM-S) primary cluster goes down, or is otherwise unreachable from the secondary cluster
  • The SM-S secondary cluster goes Out-of-Sync (OOS) 
  • While in this state, with the SM-S primary unreachable, attempts to quiesce or break the SM-S mirror fail.  This message is logged to snapmirror_audit:

Modification of relationship with destination "[SVM name]:/cg/[CG name]" is in progress. Wait a few minutes and try the command again.

  • The inability to quiesce or break the snapmirror relationship keeps the destination in a read-only state, preventing failover to the secondary cluster.

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.