Skip to main content
NetApp Knowledge Base

Cross-vserver volume cloning causes DR CONFIG REPLICATION FAILED

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

Applies to

  • MetroCluster
  • ONTAP 9
  • Source Vservers containing volume clones cloned from a volume on another vserver

Issue

An AutoSupport is generated with the subject line of "System Notification (DR CONFIG REPLICATION FAILED) ERROR" and entries similar to the following appear in the Event Log:

Apply failed for Object: volume Method: baseline. Reason: Volume "vol01_clone" does not exist in Vserver "vserver01-mc".  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.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
    KCS Candidate/Contributor Workflow
    Published
    Confidence
    Validated
    Flag
    False
    Governance
    Experience
    KCS Enabled
    Yes
    Visibility
    Public
    Product Categories
    MetroCluster
    Specialty
    MetroCluster
  2. Tags
    This page has no tags.