Skip to main content
NetApp Knowledge Base

SnapMirror resync during SVM re-activation fails with "Reason: File operation failed, Reason: File exists"

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

Applies to

  • ONTAP 9
  • SVM Disaster Recovery (SVM DR)

Issue

  • The SnapMirror resync operations fail with error:

Failed to apply the source Vserver configuration. Reason: Apply failed for Object: root_direct_mounts Method: baseline. Reason: File operation failed, Reason: File exists. Execute "snapmirror show -destination-vserver  <destination-path> -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors. 

  • SnapMirror destination CRS-MLOG shows:

Apply failed for Object: root_direct_mounts Method: baseline Row: Table Name: root_direct_mounts, Operation: get, Fields: <destination-vserver> <volume-name>  <junction-path>- false Table Name: path_attrs_for_repl, Operation: get, Fields:<source-vserver> <junction-path> directory Reason: File operation failed, Reason: File exists.

 

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.