Skip to main content
NetApp Knowledge Base

Why Primary Cluster In Snapmirror Active Sync Suspend I/O upon OOS Event

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

Applies to

  • ONTAP 9
  • SnapMirror active sync (SMas) formerly SnapMirror Business Continuity (SMBC)

Answer

  • Upon an Out of Sync event due to Intercluster or node failures, the Primary cluster will suspend I/O and seek consensus from the Ontap Mediator to designate a cluster serving data.
  • The I/O suspension can varies between 20 to 50 Sec before consensus is completed and I/O are resumed.
  • Client host must ensure that the timeout values are appropriate for the expected operation duration.

Additional Information

additionalInformation_text

 

 

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.