Skip to main content
NetApp Knowledge Base

FG Snapmirror scheduled update fails with error Transfer did not start because the relationship is quiesced

Last Updated:

Applies to

  • ONTAP 9.12.1
  • FlexGroup


  • SnapMirror scheduled update fails after volume move.

MonApr 03 16:05:00  [node01:]: Snapmirror update from source volume 'svm1:vol1' to destination volume 'dr_svm1:dr_vol1' failed with error 'Transfer did not start because the relationship is quiesced.'. Relationship UUID'b12fb5b6-5bd8-11ed-98fd-d039ea983852'

  • snapmirror show output

cluster::> snapmirror show
                Source Path: svm1:voll
           Destination Path: dr_svm1:dr_vol1
          Relationship Type: XDP
        SnapMirror Schedule: hourly
     SnapMirror Policy Type: mirror-vault
          SnapMirror Policy: XDPDefault
                Tries Limit: -
          Throttle (KB/sec): unlimited
               Mirror State: Snapmirrored
        Relationship Status: Idle
          Transfer Snapshot: -
          Snapshot Progress: -
             Total Progress: -
   etwork Compression Ratio: -
        Snapshot Checkpoint: -
                    Healthy: false
           Unhealthy Reason: Scheduled update failed to start. (Transfer did not start because the relationship is quiesced.)

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.