Stabilizing destinations before a Snapshot copy

You might need to temporarily stop transfers to a destination. For example, if you want to create a Snapshot copy of a SnapMirror destination volume or qtree that contains a database, you need to ensure that its contents are stable during the Snapshot copy.

Considerations

Step

1. Enter the following command on the system on which you want to block transfers.snapmirror quiesce {dest_volume | /vol/volume_name/qtree_name}

   dest_volume is the name of the destination volume.

   qtree_name is the name of a qtree in volume_name.

   Example

   systemA> snapmirror quiesce vol1
   
   snapmirror quiesce: in progress.
   snapmirror quiesce: vol1: successfully quiesced

   SnapMirror stops any further data transfers to vol1.

   Example

   systemA> snapmirror quiesce vol2
   
   snapmirror quiesce: in progress.
   This can be a long-running operation. Use Control-C to interrupt.
   ......................................
   snapmirror quiesce: vol2: successfully quiesced

   SnapMirror waits for a transfer to finish and stops any further data transfers to vol2.

   Example

   systemA> snapmirror quiesce /vol/vol1/qtree1

   SnapMirror stops data transfers to qtree1 in vol1.

   If you use the snapmirror break command on a destination that is quiesced, the quiesce condition is automatically cleared when the destination becomes writable.

   Note: If you decide to abort a SnapMirror quiesce operation, press Ctrl-C or enter the snapmirror resume command at any time.

• What the quiesce command does
  The snapmirror quiesce command waits for all volume and qtree SnapMirror transfers to complete, and blocks any further updates. If a qtree is not in a stable state (is in transition), the snapmirror quiesce command forces it into a stable state.
• Resuming transfers after quiescing a destination
  You can use the snapmirror resume command to restore the capability for data transfer to a volume or qtree you have quiesced.