Skip to main content
NetApp Knowledge Base

How to change the number of ONTAP SnapMirror relationship update retries

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

Applies to

  • ONTAP 9
  • ONTAP Select

Description

  • SnapMirror updates, both manual and scheduled, will retry when encountering an abort condition
  • The default number of tries is EIGHT based on the initial update attempt in addition to 7 retries (default)
  • When troubleshooting the number of retries, and the resulting messages, can increase the amount of time required to reproduce an error, or locate a root cause
  • The number of SnapMirror retries is configurable, and lowering the number of retries will reduce the time required to troubleshoot SnapMirror issues
    • Lowering the number of retries can be particularly helpful in scenarios where we need to quickly reach an error when packet traces are being collected
  • SnapMirror relationships are managed by their respective SnapMirror policies
    • Retries are controlled by these same policies

In the example below, SnapMirror is failing with network errors, so we are performing packet traces. As packet traces can grow very quickly, we ideally want to start the traces, reproduce the error, and stop traces to keep their size manageable. This is an ideal situation to reduce retries.

  • SnapMirror Failures: 
    • network error(CSM: Request was canceled because of a connection failure.)
    • network error(CSM: An operation did not complete within the specified timeout window.))
  • CSM Failures: 
    • CSM: Connection aborted.
    • CSM_CANNABORTED

 

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.