Skip to main content
NetApp Knowledge Base

Sync-destination SVM fails to initialize after DR test event

  1. Last updated
  2. Save as PDF
Views:
94
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

Issue

  • A MetroCluster sync-destination SVM or an SVM-DR initialization fails with an error

Example:

"Config replication service error on cluster "source". Reason: Configuration replication service is not active."  
  • SnapMirror config-replication service (CRS) shows an error

cluster::> snapmirror config-replication status show

                Enabled: true
                Running: false
         Storage Status: warning
         Storage In Use: Unavailable
        Storage Remarks: Unable to free resources due to error confirmation needed
        Vserver Streams: ok

OR

  • MetroCluster CRS shows an error

::> metrocluster check config-replication show
                Enabled: true
                Running: false
       Remote Heartbeat: ok
    Last Heartbeat Sent: 8/21/2023 11:24:52
Last Heartbeat Received: 8/21/2023 11:24:32
         Storage Status: warning
         Storage In Use: Unavailable
        Storage Remarks: Unable to free resources due to error confirmation needed
        Vserver Streams: ok
        Cluster Streams: ok

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.