Skip to main content

snapmirror quiesce

Disable future transfers

Availability: This command is available to cluster and Vserver administrators at the admin privilege level.

Description

The snapmirror quiesce command disables future transfers for a SnapMirror relationship. If there is no transfer in progress, the relationship becomes "Quiesced".

If there is a transfer in progress, it is not affected, and the relationship becomes "Quiescing" until the transfer completes. If the current transfer aborts, it will be treated like a future transfer and will not restart.

If applied to a load-sharing (LS) SnapMirror relationship, all the relationships in the load-sharing set will be quiesced.

If applied to a relationship with a policy of type strict-sync-mirror or sync-mirror, any ongoing operation is aborted, and if the relationship is InSync, synchronous replication is stopped. If the replication policy type is "strict-sync-mirror", then the primary client I/O disruption is not enforced. A new common Snapshot copy is created if the relationship is InSync, unless a recent one exists. The relationship becomes "Quiescing" until these operations complete.

When a SnapMirror relationship is quiesced, it remains quiesced across reboots and fail-overs.

The snapmirror quiesce command must be used from the destination Vserver or cluster.

The relationship must exist on the destination Vserver or cluster. When issuing snapmirror quiesce, you must specify the destination endpoint. The specification of the source endpoint of the relationship is optional.

Parameters

{ [-source-path | -S {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>|<[vserver:]/cg/[cgname]>}] - Source Path
This parameter specifies the source endpoint of the SnapMirror relationship in one of four path formats. The normal format includes the names of the Vserver (vserver) and/or the volume (volume).
[-source-vserver <vserver name>] - Source Vserver
Specifies the source Vserver of the SnapMirror relationship. This parameter is not supported for relationships with non-Data ONTAP source endpoints.
[-source-volume <volume name>]} - Source Volume
Specifies the source volume of the SnapMirror relationship. This parameter is not supported for relationships with non-Data ONTAP source endpoints.
{ -destination-path {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>|<[vserver:]/cg/[cgname]>} - Destination Path
This parameter specifies the destination endpoint of the SnapMirror relationship in one of four path formats. The normal format includes the names of the Vserver (vserver) and/or volume (volume).
-destination-vserver <vserver name> - Destination Vserver
Specifies the destination Vserver of the SnapMirror relationship. This parameter is not supported for relationships with non-Data ONTAP destination endpoints.
-destination-volume <volume name>} - Destination Volume
Specifies the destination volume of the SnapMirror relationship. This parameter is not supported for relationships with non-Data ONTAP destination endpoints.

Examples

To quiesce the SnapMirror relationship with the destination endpoint vs2.example.com:dept_eng_mirror2, type the following command:

vs2.example.com::> snapmirror quiesce -destination-path
vs2.example.com:dept_eng_mirror2

To quiesce the Vserver SnapMirror relationship with the destination endpoint dvs1.example.com:, type the following command:

cluster2::> snapmirror quiesce -destination-path
dvs1.example.com:

Under PVR control to quiesce the synchronous SnapMirror Consistency Group relationship with the destination Consistency Group cg_dst in Vserver vs2.example.com, type the following command:

vs2.example.com::> snapmirror quiesce -destination-path
vs2.example.com:/cg/cg_dst