Skip to main content
NetApp Knowledge Base

DR CONFIG REPLICATION FAILURE due to deleted snaplock volume

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

Applies to

  • MetroCluster
  • ONTAP 9.12.1P6 & earlier
  • ONTAP 9.13.1P1 & earlier

Issue

  • An autosupport is received titled DR CONFIG REPLICATION FAILED:

Message Name: callhome.dr.apply.failed
Event: callhome.dr.apply.failed: Call home for DR CONFIG REPLICATION FAILED

  • metrocluster vserver show  reports:

             Cluster  : cluster_name
             Vserver  : vserver_name
     Partner Vserver  : vserver_name-mc
 Configuration State  : syncing
       Stream Status  : processing-task
           Failed Row : Table Name: volume, Operation: get, Fields: vserver_name-mc vol1 aggr1 ... DEL ... enterprise ...
        Failed Reason : Apply failed for Object: volume Method: baseline. Reason: Internal Error. Reason entry doesn't exist
Last apply fail time  : 4/5/2022 10:34:52

 

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.