Index  |  Top  -  Up Data ONTAP 8.3

snapmirror resync

Start a resynchronize operation

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

Description

The snapmirror resync command establishes or reestablishes a mirroring relationship between a source volume and a destination volume, typically in the following cases:

Attention:

The default behavior of the snapmirror resync command is defined as follows:

The snapmirror resync command supports an optional parameter "preserve". The parameter "preserve" is only supported for extended data protection (XDP) relationships. When used, the parameter "preserve" changes the behavior of snapmirror resync command. Changed behavior of the command can be described as follows:

If a SnapMirror relationship does not already exist, that is, the relationship was not created using the snapmirror create command, the snapmirror resync command will implicitly create the SnapMirror relationship, with the same behaviors as described for the snapmirror create command before resyncing it.

For Infinite Volumes, you must create Infinite Volume SnapMirror relationships using the snapmirror create command before you run the snapmirror resync command. The snapmirror resync command does not implicitly create the SnapMirror relationship.

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.

For relationships with "Relationship Capability" of "8.2 and above", you can track the progress of the operation using the snapmirror show command.

For relationships with "Relationship Capability" of "Pre 8.2", a job will be spawned to operate on the SnapMirror relationship, and the job id will be shown in the command output. The progress of the job can be tracked using the job show and job history show commands.

The snapmirror resync command fails if the destination volume does not have a Snapshot copy in common with the source volume.

The snapmirror resync command does not work on load-sharing mirrors.

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

Parameters

{  [-source-path | -S {<[vserver:]volume>|<[[cluster:]//vserver/]volume>}] - Source Path

Specifies the source endpoint of the SnapMirror relationship in one of two path formats. The normal format includes the names of the Vserver (vserver) and 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".

|  [-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. If this parameter is specified, parameters -source-volume and for relationships with "Relationship Capability" of "Pre 8.2", -source-cluster must also be specified.

   [-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.

{  -destination-path {<[vserver:]volume>|<[[cluster:]//vserver/]volume>} - Destination Path

Specifies the destination endpoint of the SnapMirror relationship in one of two path formats. The normal format includes the names of the Vserver (vserver) and 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".

|  [-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. If this parameter is specified, parameters -destination-volume and for relationships with "Relationship Capability" of "Pre 8.2", -destination-cluster must also be specified.

   -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.

[-source-snapshot | -s <text>] - Source Snapshot

This optional parameter specifies a Snapshot copy to transfer. The default behavior for a data protection relationship with a read-write source is that Data ONTAP creates a new Snapshot copy and uses it as the basis for determining what data are replicated; with this option, the specified Snapshot copy will be used instead. The default behavior for an extended data protection relationship depends on the relationship's policy type. For a data protection relationship, the specified Snapshot copy must be newer than the latest common Snapshot copy. For an extended data protection relationship, the specified Snapshot copy may be newer or older than the common Snapshot copy. This parameter is not supported for relationships with "Relationship Capability" of "Pre 8.2".

[-type <snapmirrorType>] - Snapmirror Relationship Type

Specifies the type of SnapMirror relationship if a relationship is implicitly created. The default is data protection (DP).

[-policy <sm_policy>] - SnapMirror Policy

This optional parameter designates the name of the SnapMirror policy which is associated with the SnapMirror relationship. If you do not designate a policy, the current policy will be retained. This parameter is not applicable to relationships with "Relationship Capability" of "Pre 8.2". This parameter is not supported by this operation for Infinite Volumes.
Note:

[-force | -f [true]] - Force

If this parameter is specified, the command proceeds without prompting for confirmation.

[-throttle | -k <throttleType>] - Throttle (KB/sec)

This optional parameter limits the network bandwidth used for the resync transfer. It sets the maximum rate (in Kbytes/sec) at which data can be transferred during the operation. If this parameter is not specified, the throttle value configured for the relationship with the snapmirror create or snapmirror modify commands will be used. To specify fully using the network bandwidth available, set the throttle value to unlimited or 0. The minimum throttle value is four Kbytes/sec, so if you specify a throttle value between 1 and 4, it will be treated as if you specified 4. The -throttle parameter does not affect load-sharing transfers and transfers for other relationships with "Relationship Capability" of "Pre 8.2" confined to a single cluster.

[-transfer-priority {low|normal}] - Transfer Priority

This optional parameter specifies the priority at which the transfer runs. The default value for this parameter is the value in the SnapMirror policy associated with this relationship. This parameter is not applicable to relationships with a "Relationship Capability" of "Pre 8.2".

[-preserve [true]] - Preserve

This parameter is only supported for extended data protection (XDP) relationships. It is not supported for data protection and load-sharing relationships. When specified, it changes the behavior of snapmirror resync to preserve Snapshot copies on the destination volume that are newer than the latest common Snapshot copy. This parameter is not supported for relationships with "Relationship Capability" of "Pre 8.2". This option is not supported for Infinite Volume SnapMirror relationships.

[-quick-resync [true]] - Quick Resync

This parameter is only supported for extended data protection (XDP) relationships. Specifying this optional parameter reduces the resync time because the resync does not incur storage efficiency overhead before the transfer of new data. Specifying this parameter is recommended if the source of the resync does not have volume efficiency enabled or if reducing resync time is more important than preserving all possible storage efficiency. When this parameter is specified, resync does not preserve the storage efficiency of the new data with existing data over the wire and on the destination.

[-foreground | -w [true]] - Foreground Process

This specifies whether the operation runs as a foreground process. If this parameter is specified, the default setting is true (the operation runs in the foreground). When set to true, the command will not return until the process completes. This parameter is only applicable to relationships with "Relationship Capability" of "Pre 8.2".

Examples

To reestablish mirroring for the destination endpoint vs2.example.com:dept_mkt_mirror that has been previously broken off with the snapmirror break command, type the following command:

vs2.example.com::> snapmirror resync -destination-path
       vs2.example.com:dept_mkt_dp_mirror

For relationships with "Relationship Capability" of "Pre 8.2", to reestablish mirroring for the destination endpoint cluster2://vs2.example.com/dept_mkt_mirror that has been previously broken off with the snapmirror break command, type the following command:

cluster2::> snapmirror resync -destination-path
         cluster2//vs2.example.com/dept_mkt_dp_mirror

To create a SnapMirror relationship and reestablish mirroring between the destination endpoint named vs2.example.com:dept_eng_dp_mirror2 and the source endpoint named vs1.example.com:dept_eng, type the following command:

vs2.example.com::> snapmirror resync -destination-path
         vs2.example.com:dept_eng_dp_mirror2
         -source-path vs1.example.com:dept_eng

To create a SnapMirror relationship and reestablish mirroring between the destination endpoint named cluster2://vs2.example.com/dept_eng_dp_mirror2 and the source endpoint named cluster1://vs1.example.com/dept_eng when the source cluster is running Data ONTAP 8.1 software, type the following command:

cluster2::> snapmirror resync -destination-path
         cluster2://vs2.example.com/dept_eng_dp_mirror2
         -source-path cluster1://vs1.example.com/dept_eng

See Also

snapmirror policy create   snapmirror create   snapmirror modify   snapmirror update   snapmirror policy   snapmirror show   job show   job history show   snapmirror break  
Index  |  Top  -  Up Data ONTAP 8.3

Copyright © 1994-2015 NetApp, Inc. Legal Information