Skip to main content
NetApp Knowledge Base

Is it required to quiesce a SM-BC relationship before physical relocation of clusters

Last Updated:

Applies to

  • ONTAP 9.8 and later
  • SnapMirror Business Continuity (SM-BC)


  • You cannot quiesce or abort the SnapMirror Business Continuity (SM-BC) / 'automatedfailover' relationship.
  • The only available options are update, failover or delete.
  • If the plan is to relocate the primary cluster then you must consider "planned failover". Otherwise, the mediator would negotiate a nondisruptive failover.
  • If the secondary cluster is taken offline, all paths through the secondary cluster would be unavailable to the host multipathing software and hence, the ability to failover would be compromised.
  • In case, both primary and secondary clusters have to be relocated then, shut down the secondary cluster followed by primary cluster. 
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.