Cross-vserver volume cloning causes DR CONFIG REPLICATION FAILED
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.