Skip to main content

snapmirror resume

Enable future transfers

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

Description​

The snapmirror resume command enables future transfers for a SnapMirror relationship that has been quiesced.

If there is a scheduled transfer for the relationship, it will be triggered on the next schedule. If there is a restart checkpoint, it will be re-used if possible.

If applied on a load-sharing (LS) SnapMirror relationship, it enables future transfers for all the relationships in the load-sharing set.

If applied on a relationship with a policy of type strict-sync-mirror or sync-mirror, it enables future resync operations and initiates an Auto Resync.

When a quiesced SnapMirror relationship is resumed, future transfers remain enabled across reboots and fail-overs.

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

The relationship must exist on the destination Vserver or cluster. When issuing snapmirror resume, 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>}] - 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-cluster <Cluster name>] - Source Cluster
This parameter is not supported in ONTAP 9.4 and above.
[-source-vserver <vserver name>] - Source Vserver
This parameter is not supported in ONTAP 9.4 and above.
[-source-volume <volume name>]} - Source Volume
This parameter is not supported in ONTAP 9.4 and above.
{ -destination-path {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>} - 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-cluster <Cluster name>] - Destination Cluster
This parameter is not supported in ONTAP 9.4 and above.
-destination-vserver <vserver name> - Destination Vserver
This parameter is not supported in ONTAP 9.4 and above.
-destination-volume <volume name>} - Destination Volume
This parameter is not supported in ONTAP 9.4 and above.

Examples​

To re-enable future transfers for the SnapMirror relationship with the destination endpoint vs2.example.com:dept_eng_dp_mirror2 that has been previously quiesced, type the following command:

vs2.example.com::> snapmirror resume -destination-path
       vs2.example.com:dept_eng_dp_mirror2

To re-enable future transfers for the SnapMirror relationship with the destination endpoint cluster2://vs2.example.com/dept_eng_dp_mirror2 that has been previously quiesced, type the following command:

cluster2::> snapmirror resume -destination-path
         cluster2://vs2.example.com/dept_eng_dp_mirror2

To re-enable future transfers for the Vserver SnapMirror relationship with the destination endpoint dvs1.example.com: that has been previously quiesced, type the following command:

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

Under PVR control to re-enable future transfers and initiate an Auto Resync of 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 resume -destination-path
            vs2.example.com:/cg/cg_dst

Related reference