Skip to main content
NetApp Knowledge Base

How to configure event notification whenever SnapMirror fails regardless of the cause

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

Applies to

  • ONTAP 9
  • SnapMirror

Description

  • The related EMS events generated by ONTAP vary depending on the cause.

Example 1: The following errors are detected when SnapMirror is paused or broken from the System Manager on the SnapMirror destination side.

  • When paused:

cluster2::> event log show -message-name *snap*
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
11/8/2024 13:40:03  cluster2-01      ERROR         smc.snapmir.update.fail: Snapmirror update from source volume 'cluster1_svm1:cluster1_svm1_inventory' to destination volume 'cluster2_svm1:cluster1_svm1_inventory_dest' failed with error 'Transfer did not start. The relationship is quiesced, or Vserver peering between source and destination Vservers has been suspended or removed.'. Relationship UUID 'c579a9d2-9d9e-11ef-a659-0050569cb19e'.

  • When broken:

cluster2::> event log show -message-name *snapmi*
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
11/8/2024 13:50:03  cluster2-01      ERROR         smc.snapmir.update.fail: Snapmirror update from source volume 'cluster1_svm1:cluster1_svm1_inventory' to destination volume 'cluster2_svm1:cluster1_svm1_inventory_dest' failed with error 'Destination cluster2_svm1:cluster1_svm1_inventory_dest must be a data-protection volume.'. Relationship UUID 'c579a9d2-9d9e-11ef-a659-0050569cb19e'.


Example 2: When the Interconnect LIF on the SnapMirror source side is manually brought down, the following error is detected after some time:
cluster1::> network interface modify -vserver cluster1 -lif lif_Default_18 -status-admin down

Warning: Disabling LIF "lif_Default_18" on system Vserver "cluster1" could interrupt services required for proper cluster operation. Are you sure you want to continue? {y|n}: y

cluster2::> event log show -message-name *snapmi*
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
11/8/2024 14:25:02  cluster2-01      ERROR         smc.snapmir.schd.trans.overrun: Scheduled transfer from source volume 'cluster1_svm1:cluster1_svm1_inventory' to destination volume 'cluster2_svm1:cluster1_svm1_inventory_dest' is taking longer than the schedule window. Relationship UUID 'c579a9d2-9d9e-11ef-a659-0050569cb19e'.

  • This article explains how to configure event notifications for SnapMirror failures, regardless of the cause.

 

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.