Table of ContentsView in Frames

Aborting an update to a load-sharing mirror

You can end an update to a set of load-sharing mirrors if the update started, but did not finish.

About this task

Load-sharing mirrors are either up to date and serving data to clients, or they are lagging and not serving data to clients.
  • If you are aborting an update to an up-to-date load-sharing mirror, transfers to associated up-to-date load-sharing mirrors in the set of load-sharing mirrors are also aborted.
  • If you are aborting an update to a lagging load-sharing mirror, then only the SnapMirror transfer associated with the lagging load-sharing mirror is aborted.

Step

  1. Use the snapmirror abort command to end an update to a particular load-sharing mirror.
    Note: You can use the snapmirror abort command on other load-sharing mirrors in the set if those load-sharing mirrors also prevent updates to other load-sharing mirrors in the set.
    Example
    The following example ends the update to the load-sharing mirror named dept_eng_ls_mirror2 on a Storage Virtual Machine (SVM) named vs0.
    cluster1::> snapmirror abort -source-path //vs0/dept_eng
    -destination-path //vs0/dept_eng_ls_mirror2
    [Job 184] Job is queued: snapmirror abort for the relationship with destination
    [Job 184] Job succeeded: SnapMirror: done