Skip to main content
NetApp Knowledge Base

Sync snapmirror destination is reporting sms.fanout.comm.snap.deleted message

  1. Last updated
  2. Save as PDF
Views:
295
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror Synchronous (SM-S) and SnapMirror asynchronous fan-out configuration

Issue

  • SnapMirror asynchronous and SnapMirror Synchronous (SM-S) fan-out configuration:
Async-SRC                              Async-DST
Cluster1:node1/src1        Cluster1:node2/dst1
Cluster1:node2/src2        Cluster1:node1/dst2
 
Sync-SRC                                 Sync-DST
Cluster1:node1/src1        Cluster2:node1/dst1
Cluster1:node2/src2        Cluster2:node2/dst2
  • The destination side of the Sync snapmirror relationships(Sync-DST) are reporting sms.fanout.comm.snap.deleted message.
Example:
11/6/2024 19:23:45 node1 ALERT sms.fanout.comm.snap.deleted: SnapMirror Synchronous operation 'Update' for relationship 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' has cleaned up some of the old base Snapshot copies between the synchronous source and synchronous destination, which could result in no common Snapshot copy existing between the synchronous and asynchronous destinations.
 
  • In comparing the number of snapmirror common snapshots between Async-DST and Sync-DST, some snapmirror common snapshots exist only on Sync-DST.
  • According to the ASUP, the status of Async snapmirror relationship is shown as broken-off

Note:
There are times when there is no fan-out relationship, but there are stale Snapshot Snapshots on the source volume, either from a reverse relationship or  a  deleted fan-out relationship

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.