Skip to main content
NetApp Knowledge Base

SnapMirrors go into a queued state after upgrade to ONTAP 9.2

Views:
627
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

ONTAP 9.2 and later

Issue

  • On SnapMirror destination cluster nodes with multiple source cluster nodes, some SnapMirrors go into a queued state after the update schedule is triggered, after a manual update, or during initialization.
  • SnapMirror transfers are typically always queued initially, but relationships impacted by this issue will report they are queued and will stay in the queued state for some time before starting the transfer as seen in the /etc/log/snapmirror_audit logs.
  • Below, the relationship starts replicating one hour after waiting in a queued state.
EXAMPLE:
Wed Sep 13 13:10:01 2017 CreateSnapshotDest[Sep 13 13:10:00]:7caa055a-e032-11e5-95d8-00a0985dae38 Operation-Uuid=bcf90269-2d39-4d80-90f7-1852860e3da4 Group=none Operation-Cookie=0 action=End source=srcSVM:srcVol destination=dstSVM:dstVol status=SuccessNote=Scheduled update operation is queued.Wed Sep 13 13:10:01 2017 CreateSnapshotDest[Sep 13 13:10:00]:7caa055a-e032-11e5-95d8-00a0985dae38 Operation-Uuid=bcf90269-2d39-4d80-90f7-1852860e3da4 Group=none Operation-Cookie=0 action=End source=srcSVM:srcVol destination=dstSVM:dstVol status=SuccessNote=Scheduled update operation is queued.Wed Sep 13 14:09:27 2017 ScheduledUpdate[Sep 13 13:10:00]:7caa055a-e032-11e5-95d8-00a0985dae38 Operation-Uuid=bcf90269-2d39-4d80-90f7-1852860e3da4 Group=none Operation-Cookie=0 action=Start source=srcSVM:srcVol destination=dstSVM:dstVol
 
  • In these cases, some SnapMirrors continue to work and run immediately.
  • In addition,it may not be the same relationships which are queued each time the issue is noticed.Once the transferring relationships complete, the queued relationships begin their transfer.

 

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.