Skip to main content
NetApp Knowledge Base

Rebooting an SVMDR destination node with an orphaned destination SVM can cause an outage in ONTAP

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

Applies to

  • ONTAP 9.x
  • SVM-DR

Issue

  • An SVM which was once the destination of an SVM-DR relationship can be in a state where a reboot of any node in the cluster will result in the SVM being put into a running / started state
  • This issue can also be seen after a restart of the MGWD subsystem
  • If the SVM was the destination for an identity-preserve SVMDR this can cause duplicate IPs, outages for clients, or other "split-brain" behavior

 

 

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.