Skip to main content
NetApp Knowledge Base

Cascading snapmirror fails to initialize

Views:
35
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • DP
  • Snapmirror

Issue

  • Deployed a new CVO system in Azure and trying to implement the following snapmirror cascade:
Site A ( production) to Site B ( Azure CVO1) to Site C ( new CVO in Azure).
 
  • The Site A to Site B replication of volumes is already in place and snapmirrored.
 
  • Created a new volumes on Site C, however when trying to create the cascade relationship from Site B to Site C in the cli,
the relationship gets created but mirror state shows as Broken-off instead of uninitialized in System Manager.
 
  • The only option available is to resync, which fails with the error:
 
"Transition to snapmirrored state failed. Reason: No common Snapshot copy found between
svm_b:vol_mir and svm_c:vol_mir".
 
  • The goal is to snapmirror the volume from SiteB to Site C, so end user can decomission site B and resume replication from Site A to Site C.

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.