Skip to main content
NetApp Knowledge Base

SnapMirror replications are in the state "queued" and can't be updated manually

Views:
1,060
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
DP
Last Updated:

Applies to

  • Cloud Volumes ONTAP
  • ONTAP 9
  • SnapMirror
  • SnapVault

Issue

  • SnapMirror replication is not updating and with Queued status:
                                Source Path: SVM1:volume1
                              Source Cluster: -
                              Source Vserver: SVM1
                               Source Volume: volume1
                            Destination Path: netappbackup87667:/objstore/SVM1_volume1_dst
                         Destination Cluster: -
                         Destination Vserver: SVM1
                          Destination Volume: none
                           Relationship Type: XDP
                     Relationship Group Type: none
                            Managing Vserver: SVM1
                         SnapMirror Schedule: hourly
                      SnapMirror Policy Type: vault
                           SnapMirror Policy: CloudBackupService
                                 Tries Limit: -
                           Throttle (KB/sec): unlimited
             Consistency Group Item Mappings: -
          Current Transfer Throttle (KB/sec): unlimited
                                Mirror State: Snapmirrored
                         Relationship Status: Queued
                     File Restore File Count: -
                      File Restore File List: -
                           Transfer Snapshot: -
                           Snapshot Progress: -
                              Total Progress: -
                   Network Compression Ratio: -
                         Snapshot Checkpoint: 0B
                             Newest Snapshot: snap-daily_20220209204044
                   Newest Snapshot Timestamp: 02/07 20:40:44
                           Exported Snapshot: snap-daily_20220209204044
                 Exported Snapshot Timestamp: 02/07 20:40:44
                                     Healthy: false
                             Relationship ID: d65cba97-83c2-11ec-4b46-00a045b3e32d
                         Source Vserver UUID: 6781231f-c4f4-11e5-b363-33a34661f12c
                    Destination Vserver UUID: -
                        Current Operation ID: -
                               Transfer Type: update
                              Transfer Error: -
                          Last Transfer Type: update
                         Last Transfer Error: Transfer aborted.
                   Last Transfer Error Codes: 6620145
                          Last Transfer Size: -
     Last Transfer Network Compression Ratio: -
                      Last Transfer Duration: -
                          Last Transfer From: SVM1:volume1
                 Last Transfer End Timestamp: 02/11 08:49:20
                            Unhealthy Reason: Scheduled update failed to start. (Scheduled update was delayed because another SnapMirror operation for the relationship is queued.)
                       Progress Last Updated: -
                     Relationship Capability: 8.2 and above
                                    Lag Time: 87:54:52
                   Current Transfer Priority: normal

 

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.