Skip to main content
NetApp Knowledge Base

What is the recommended procedure when SnapMirror scheduled update is taking too long and aborting the transfer during ONTAP cluster migration?

  1. Last updated
  2. Save as PDF
Views:
30
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

ONTAP 9

Answer

  • SnapMirror update operations can be aborted using the snapmirror abort command.
  • Abort is effective only when the SnapMirror relationship is in a “Transferring” state.
  • These internal stages are not specifically shown in SnapMirror status output; only broader states like “Transferring” or “Finalizing” are visible in snapmirror show.
  • If abort is successful, the relationship returns to “Idle” state and manual update or schedule can be restarted.
  • If abort is not possible and update continues beyond the migration window, consider deleting the SnapMirror relationship after abort attempt.
  • After abort and delete, the new SnapMirror relationship between the new source and DR must be initialized (snapmirror initialize).
  • Resync (snapmirror resync) is only possible if a common snapshot exists at both source and destination. Forceful deletion of the previous relationship usually removes the common snapshot, requiring initialize.
  • Initialize will perform a full data transfer. Plan for sufficient bandwidth and time, especially for large volumes.
  • Scheduled SnapMirror updates can be controlled by removing the schedule with snapmirror modify -schedule "" and performing manual updates.
  • Quiesce (snapmirror quiesce) prevents both scheduled and manual updates. Use modify to remove schedule if manual control is needed.
  • Modifying the schedule during an active update does not interrupt the running update. The change only affects future scheduled updates.
  • Example procedure for migration when update takes too long:
  1. Attempt to abort the running SnapMirror update with:snapmirror abort -destination-path <SVM:volume>
  2. If abort is successful, delete the SnapMirror relationship:snapmirror delete -destination-path <SVM:volume>
  3. Create new SnapMirror relationship from new source to DR.
  4. Initialize the new relationship:snapmirror initialize -destination-path <SVM:volume>
  5. Monitor the transfer and ensure DR capacity and bandwidth are sufficient.

Additional Information

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.