snapmirror resume
Enable future transfers
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.
This command is supported for SnapMirror relationships with the field "Relationship Capability" showing as either "8.2 and above" or "Pre 8.2" in the output of the snapmirror show command.
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). To support relationships with "Relationship Capability" of "Pre 8.2", a format which also includes the name of the cluster (cluster) is provided. The "Pre 8.2" format cannot be used when operating in a Vserver context on relationships with "Relationship Capability" of "8.2 and above". For SnapMirror relationships with an AltaVault source, the source endpoint is specified in the form hostip:/share/share-name. For SnapMirror relationships with a SolidFire source, the source endpoint is specified in the form hostip:/lun/name.
- | [-source-cluster <Cluster name>] - Source Cluster
- Specifies the source cluster of the SnapMirror relationship. If this parameter is specified, the -source-vserver and -source-volume parameters must also be specified. This parameter is only applicable for relationships with "Relationship Capability" of "Pre 8.2". This parameter cannot be specified when operating in a Vserver context on relationships with "Relationship Capability" of "8.2 and above".
- [-source-vserver <vserver name>] - Source Vserver
- Specifies the source Vserver of the SnapMirror relationship. For relationships with volumes as endpoints, if this parameter is specified, parameters -source-volume and for relationships with "Relationship Capability" of "Pre 8.2", -source-cluster must also be specified. 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. If this parameter is specified, parameters -source-vserver and for relationships with "Relationship Capability" of "Pre 8.2", -source-cluster must also be specified. 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>} - 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). To support relationships with "Relationship Capability" of "Pre 8.2", a format which also includes the name of the cluster (cluster) is provided. The "Pre 8.2" format cannot be used when operating in a Vserver context on relationships with "Relationship Capability" of "8.2 and above". For SnapMirror relationships with AltaVault destinations, the destination endpoint is specified in the form hostip:/share/share-name. For relationships with SolidFire destinations, the destination endpoint is specified in the form hostip:/lun/name.
- | [-destination-cluster <Cluster name>] - Destination Cluster
- Specifies the destination cluster of the SnapMirror relationship. If this parameter is specified, parameters -destination-vserver and -destination-volume must also be specified. This parameter is only applicable for relationships with "Relationship Capability" of "Pre 8.2". This parameter cannot be specified when operating in a Vserver context on relationships with "Relationship Capability" of "8.2 and above".
- -destination-vserver <vserver name> - Destination Vserver
- Specifies the destination Vserver of the SnapMirror relationship. For relationships with volumes as endpoints, if this parameter is specified, parameters -destination-volume and for relationships with "Relationship Capability" of "Pre 8.2", -destination-cluster must also be specified. 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. If this parameter is specified, parameters -destination-vserver and for relationships with "Relationship Capability" of "Pre 8.2", -destination-cluster must also be specified. This parameter is not supported for relationships with non-Data ONTAP destination endpoints.
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