Skip to main content
NetApp Knowledge Base

SVMDR Initialization failing with "duplicate entry" error

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

Applies to

  • ONTAP 9
  • SnapMirror 
  • SVMDR

Issue

Creation of new SVMDR setup while older SVM still present, results in failure of initialization.

mgwd.logs show duplicate entry conflict with application component.
Fri Aug 13 2021 19:23:29 +10:00 [kern_mgwd:info] ERR: appdm::Api: src/tables/appdmAppSGUI.cc:apply_imp:677 returning: 1005/69 - Application component "application" already exists in application "application" in Vserver "vserver_name".
Fri Aug 13 2021 19:23:32 +10:00 [kern_mgwd:info] ERR: appdm::db: src/tables/appdmDb.cc:makeVolumeInAppError:3410 Failed finding application volume - Vserver: vserver, volume: msid: 1234567891, entry doesn't exist
Fri Aug 13 2021 19:23:32 +10:00 [kern_mgwd:info] ERR: appdm::db: src/tables/appdmDb.cc:makeVolumeInAppError:3415 returning: 1005/5 - Volume "msid: 1234567891" in Vserver "vserver" is part of application "lookup failed". A volume can be part of at most one application at a time.

 

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.