Skip to main content
NetApp Knowledge Base

SnapMirror Source SVM does not start after rebooting the cluster

  1. Last updated
  2. Save as PDF
Views:
1,415
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirrorDisaster Recovery(DR)

Issue

  • SnapMirror source vserver (SVM) does not start after rebooting the cluster for maintenance outage etc.
  • The following message appears when "vserver start" command is performed.

Example:

Failed to start Vserver "svm1" because the management configuration for this Vserver is locked. Starting a locked Vserver can cause data access issues.To start the Vserver specify "-force".

 

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.