Skip to main content
NetApp Knowledge Base

SM-S scheduled update failed due to destination lower version

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

Applies to

  • ONTAP 9.10
  • ONTAP 9.8
  • Synchronous SnapMirror (SM-S)

Issue

  • SnapMirror Synchronous relationships fail to update on schedule. EMS alerts indicate that the relatioship is going out-of-sync - 

[SOURCE_NODE_9.10: sm_logger_main: sms.status.out.of.sync:error]: Source volume "svm1:vol1" and destination volume "svm2:vol2" with relationship UUID "123" is in "out-of-sync" status due to the following reason: "Transfer failed.".
[SOURCE_NODE: sm_rpl_admin_main: sync.snapmirror.oos.frequent:error]: Source volume "svm1:vol1" and destination volume "svm2:vol2" with relationship UUID "123" is frequently undergoing change in status from "in-sync" to "out-of-sync".

[DEST_NODE_9.8: sm_logger_main: sms.status.out.of.sync:error]: Source volume "src_path" and destination volume "dest_path" with relationship UUID "123" is in "out-of-sync" status due to the following reason: "Transfer failed.(Error unmarshaling replication operation data on Cluster Id: <uuid>, Node Id: <uuid>(IDL generic failure(Refer to the corresponding sms.status.out.of.sync EMS generated on the SnapMirror destination cluster for more details on the OutOfSync reason. If the SnapMirror destination does not generate an OutOfSync EMS this could be a transient failure during a resync operation.)))".

  • Manual update works without issue.
  • Update failure messages include:
    • Failed to start replication on source.
    • Transfer failed.

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.