Index  |  Top  -  Up Data ONTAP 8.2

snapmirror create

Create a new SnapMirror relationship

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

Description

The snapmirror create command creates a SnapMirror relationship between a source and destination volume. You can use this command to create a data protection relationship, a vault relationship, or a load-sharing relationship between FlexVol volumes. You can also use it to create a data protection relationship between Infinite Volumes. Infinite Volumes support only data protection relationships.

Before using this command you typically create a source and destination volume using the volume create command. The source volume should be in the online state and a read-write (RW) type. The destination volume should be in the online state and a data protection (DP) type.

You must also take the volume style into consideration when creating SnapMirror relationships. Data ONTAP mirrors FlexVol volumes and Infinite Volumes. It does not mirror FlexCache volumes.

For an Infinite Volume SnapMirror relationship, the destination Infinite Volume size must be greater than or equal to the source Infinite Volume size in bytes. You can verify the size in bytes by running set -units KB followed by volume show.

If all systems involved are running Data ONTAP version 8.2 and later, a Vserver peering relationship must be set up using the vserver peer create command between the source and the destination Vservers in order to create a relationship between the source and destination volumes. To enable interoperability with Data ONTAP version 8.1, if the source volume is on a storage system running Data ONTAP version 8.1 operating in Cluster-Mode, the cluster administrator can create a data protection relationship between the source and destination volumes without a Vserver peering relationship between the source and destination Vservers. These relationships are managed the same way as on Data ONTAP 8.1 and the "Relationship Capability" field, as shown in the output of the snapmirror show command, is set to "Pre 8.2".

Note:

Load-sharing mirrors must be confined to a single Vserver; they are not allowed to span Vservers. Only the cluster administrator can create a load-sharing relationship. Load-sharing relationships are created with the "Relationship Capability" field set to "Pre 8.2".

A set of load-sharing mirrors can have one or more destination volumes. You create separate SnapMirror relationships between the common source volume and each destination volume to create the set of load-sharing mirrors.

After creating the relationship, the destination volume can be initialized using the snapmirror initialize command. The destination volumes in a set of load-sharing mirrors are initialized using the snapmirror initialize-ls-set command. Load sharing mirrors are not supported for Infinite Volumes.

The snapmirror create 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.

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

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

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

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

[-type <snapmirrorType>] - Relationship Type

Specifies the type of SnapMirror relationship that will be created. You can create a data protection relationship (DP), a vault relationship (XDP), or a load-sharing relationship (LS). The default is DP. Infnite Volumes support only data protection relationships (DP).

[-vserver <vserver name>] - Managing Vserver

If this optional parameter is specified, designates the managing Vserver. The managing Vserver is authorized to use snapmirror commands to manage the SnapMirror relationship. The -vserver parameter is currently a reserved parameter.

[-schedule <text>] - SnapMirror Schedule

This optional parameter designates the name of the schedule which is used to update the SnapMirror relationship. If you do not designate a schedule, updates are not scheduled, so you must update the SnapMirror relationship manually using the snapmirror update command or, in the case of a set of load-sharing mirrors, using the snapmirror update-ls-set command.
Note:

[-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 DPDefault policy is applied to data protection relationships and the XDPDefault policy is applied to vault relationships. This parameter is not applicable to relationships with "Relationship Capability" of "Pre 8.2".
Note:

[-tries <unsigned32_or_unlimited>] - Tries Limit

This optional parameter determines the maximum number of times to attempt each manual or scheduled transfer for a SnapMirror relationship. The default is eight times. This parameter is only applicable to relationships with "Relationship Capability" of "Pre 8.2". For relationships with "8.2 and above" capability, the tries limit is controlled by the value of tries in the SnapMirror policy which is associated with the relationship.
Note:

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

This optional parameter limits the network bandwidth used for transfers when the source and destination endpoints belong to different clusters. It configures for the relationship the maximum rate (in Kbytes/sec) at which data can be transferred between the clusters. If no throttle is configured, by default the SnapMirror relationship fully utilizes the network bandwidth available between the clusters. You can also configure the relationship to fully use the network bandwidth available by explicitly setting the throttle to unlimited or 0. The minimum effective throttle value is four Kbytes/sec, so if you specify a throttle value between 1 and 4, it will be treated as 4. The -throttle parameter does not affect load-sharing mirrors and other SnapMirror relationships confined to a single cluster.

Examples

To create a data protection mirror between the source endpoint vs1:dept_eng, and the destination endpoint vs2:dept_eng_dp_mirror2, type the following command:

vs2::> snapmirror create -destination-path
       vs2:dept_eng_dp_mirror2 -source-path vs1:dept_eng
       -type DP

To create a data protection mirror between the source endpoint clus1://vs1/dept_eng, and the destination endpoint clus2://vs2/dept_eng_dp_mirror2 when the source cluster is running Data ONTAP 8.1 software, type the following command:

clus2::> snapmirror create -destination-path
         clus2://vs2/dept_eng_dp_mirror2 -source-path clus1://vs1/dept_eng
         -type DP

To create a load-sharing mirror between the source endpoint clus1://vs1/mkt1, and the destination endpoint clus1://vs1/mkt1_ls1 with the schedule named 5min used to update the relationship, type the following command:

clus1::> snapmirror create -destination-path clus1://vs1/mkt1_ls1
         -source-path clus1://vs1/mkt1 -type LS -schedule 5min

See Also

snapmirror update   snapmirror update-ls-set   job schedule cron create   snapmirror policy create   volume create   vserver peer create   snapmirror show   snapmirror initialize   snapmirror initialize-ls-set  
Index  |  Top  -  Up Data ONTAP 8.2

Copyright © 1994-2013 NetApp, Inc. Legal Information