Skip to main content
NetApp Knowledge Base

Unable to delete a MetroCluster destination vserver "-mc"

  1. Last updated
  2. Save as PDF
Views:
486
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster
  • ONTAP 9.6P5
  • vserver

Issue

After deleting the source vserver the destination vserver -mc was not cleaned up and stuck in deleting state.
 
ClusterA::> vserver show -vserver vserver1-mc
                               Admin      Operational Root
Vserver     Type    Subtype    State      State       Volume     Aggregate
----------- ------- ---------- ---------- ----------- ---------- ----------
vserver1-mc data  sync-destination      stopped     -          -
                               deleting
MGWD logs shows the following error:
 
00000150.024aa2be 06d42aee Sat May 23 2020 02:55:14 +02:00 [kern_mgwd:info:2449] unconfigure_vserver_imp, src/tables/vserverdr/mcc/metrocluster_vserver.cc:4066 Failed to unconfigure vserver vserver1-mc Reason: MetroCluster Vserver unconfigure failed for Vserver 3a72c618-5a06-11ea-b8ed-00a098ef4776, Reason: Apply failed for object userprofile_all, Reason: MetroCluster Vserver unconfigure failed for Vserver 3a72c618-5a06-11ea-b8ed-00a098ef4776, Reason: Apply failed for object userprofile_all, Reason: entry doesn't exist.

 

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.