Description

The snapmirror create command creates a SnapMirror relationship between a source and destination endpoint. 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 to create a volume SnapMirror relationship, 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 volume level SnapMirror relationships. Data ONTAP mirrors FlexVol volumes and Infinite 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 clustered Data ONTAP version 8.1, 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".

Load-sharing mirrors must be confined to a single Vserver; they are not allowed to span Vservers. Load-sharing relationships are created with the "Relationship Capability" field set to "Pre 8.2" even if both the source and destination volumes are on a storage system running Data ONTAP version 8.2 and later. There is no "8.2 and above" implementation for load-sharing relationships.

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.

The source or destination of a load-sharing relationship cannot be the source or destination of any other SnapMirror relationship.

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

|  [-source-cluster <Cluster name>] - Source Cluster

   -source-vserver <vserver name> - Source Vserver

   [-source-volume <volume name>]  } - Source Volume

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

|  [-destination-cluster <Cluster name>] - Destination Cluster

   -destination-vserver <vserver name> - Destination Vserver

   -destination-volume <volume name>  } - Destination Volume

[-type <snapmirrorType>] - Relationship Type

[-vserver <vserver name>] - Managing Vserver

[-schedule <text>] - SnapMirror Schedule

[-policy <sm_policy>] - SnapMirror Policy

[-tries <unsigned32_or_unlimited>] - Tries Limit

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

Examples

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

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

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

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

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

cluster1::> snapmirror create
       -destination-path cluster1://vs1.example.com/mkt1_ls1
       -source-path      cluster1://vs1.example.com/mkt1 -type LS -schedule 5min

See Also