#SnapMirror update state stuck in Preparing...

1 messages · Page 1 of 1 (latest)

frank siren
#

I moved a source volume to another cluster, then removed the snapmirror relation on the destination, and created a new with "snapmirror create ..." then I ran a "snapmirror update" expecting it to figure out the snapshots etc.. but it's stuck in "Preparing" and transfers a bit of data... the destination node is working hard reading data, so I guess some kind of check is running? I think I should have done a "snapmirror resync" and maybe with the option "-quick-resync"... Any chance that I can stop the current update and try the resync? This is an XDP relationship so we have many more snapshots on the destination... "snapmirror show -fields percent-complete-cur-status" shows 42% done...

Screenshot_2026-05-20_at_14.12.24.jpg
toxic belfry
#

https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_relationships_report_a_Preparing_relationship_status
My guess is you're in the "Volumes involved in a cascade and/or fan-out scenario are resynced" scenario.

NetApp Knowledge Base
SnapMirror relationships report a Preparing relationship status

OnCommand System Manager reports a SnapMirror Relationship Status of “Preparing" for a significant amount of time in a Data Warehouse rebuild operation after snapmirror resync

frank siren
#

Yes I also found that... but would it be OK to stop the current update?

#

The screenshot shows the snapshots on the destination... it looks like the update process is working ist way through the old snapshots... and has been "stuck" here for 24 hours now...

#

It's not a fan-out or cacsade, just a standard SnapVault XDP... The backup relationship has been active for a long time where the destionsion is 9.16.1 and the source was 9.8 🙂 I know it's not supossed to work.. but there you go... we then "finally" moved the source from the 9.8 to another system running 9.15.1 (moved with snapmirror)... and now we just want to resync it again with the destination... but I'm a bit affraid to stop the current update... especially because the snapshots look like I have shown above.. 🙂

toxic belfry
#

The dw rebuild (Preparing) is more about total used data, rather than number of Snapshots. Though, more Snapshots could mean more used data.
You should be able to abort and resync with quick-resync.

frank siren
#

Hope you are right... just stopped it and started a resync with the quick-resync... but the snapshots on the destination still looks a bit strange with "0B" values as shows above... hopefully this is fixed once it is done...

#

....the destination controller is still "hammering" the disks with reads... my guess is that it's trying to finish what it started...

toxic belfry
#

The 0B is a just a reporting issue, it's waiting on a scanner.