Skip to main content
NetApp Knowledge Base

DR CONFIG REPLICATION FAILED: Schedule not found

Views:
221
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster

Issue

  • An autosupport titled DR CONFIG REPLICATION FAILED is triggered from one or more nodes
  • metrocluster vserver show displays an error for one or more vservers

Example:

                              Cluster  : ClusterA
                              Vserver  : SVM1
                      Partner Vserver  : SVM1-mc
                  Configuration State  : syncing
                        Stream Status  : processing-task
                            Failed Row : Table Name: snapshot_policy_byuuid, Operation: get, Fields: SVM1-mc                                          XDS true - 1 daily2205 5 daily2205 hourly vserver-admin false
                         Failed Reason : Apply failed for Object: snapshot_policy_byuuid Method: baseline. Reason:                                          Cannot enable policy. Reason: Schedule daily2205 not found.
                 Last apply fail time  : 3/29/2020 12:25:41

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.