Excluding network, name service, and other settings from SVM replication

You can use the -identity-preserve false option of the snapmirror create command to replicate only the volumes and security configurations of an SVM. Some protocol and name service settings are also preserved.

1. Create a destination SVM:vserver create -vserver SVM -subtype dp-destination

   The SVM name must be unique across the source and destination clusters.

   Example

   The following example creates a destination SVM named svm_backup :

   cluster_dst:> vserver create -vserver svm_backup -subtype dp-destination
   
2. Create a replication job schedule: job schedule cron create -name job_name -month month -dayofweek day_of_week -day day_of_month -hour hour -minute minute

   For -month, -dayofweek, and -hour, you can specify all to run the job every month, day of the week, and hour, respectively.

   Example

   The following example creates a job schedule named my_weekly that runs on Saturdays at 3:00 a.m.:

   cluster_dst::> job schedule cron create -name my_weekly -dayofweek "Saturday" -hour 3 -minute 0
   
3. Create a replication relationship that excludes network, name service, and other configuration settings:snapmirror create -source-path SVM: -destination-path SVM: -type DP|XDP -schedule schedule -policy policy -identity-preserve false
   Note

   You must enter a colon (:) after the SVM name in the -source-path and -destination-path options. See the examples below.

   You must run this command from the destination SVM or the destination cluster.

   Example

   The following example creates a SnapMirror DR relationship using the default MirrorAllSnapshots policy. The relationship excludes network, name service, and other configuration settings from SVM replication:

   cluster_dst::> snapmirror create -source-path svm1: -destination-path svm_backup: -type XDP -schedule my_daily -policy MirrorAllSnapshots -identity-preserve false
   

   Example

   The following example creates a unified replication relationship using the default MirrorAndVault policy. The relationship excludes network, name service, and other configuration settings:

   cluster_dst:> snapmirror create svm1: -destination-path svm_backup: -type XDP -schedule my_daily -policy MirrorAndVault -identity-preserve false
   

   Example

   Assuming you have created a custom policy with the policy type async-mirror , the following example creates a SnapMirror DR relationship. The relationship excludes network, name service, and other configuration settings from SVM replication:

   cluster_dst::> snapmirror create -source-path svm1: -destination-path svm_backup: -type XDP -schedule my_daily -policy my_mirrored -identity-preserve false
   

   Example

   Assuming you have created a custom policy with the policy type mirror-vault , the following example creates a unified replication relationship. The relationship excludes network, name service, and other configuration settings from SVM replication:

   cluster_dst::> snapmirror create -source-path svm1: -destination-path svm_backup: -type XDP -schedule my_daily -policy my_unified -identity-preserve false
   
4. Stop the destination SVM: vserver stopSVM name

   Example

   The following example stops a destination SVM named dvs1:

   destination_cluster::> vserver stop -vserver dvs1
   
5. If you are using SMB, you must also configure a CIFS server.

   See CIFS only: Creating a CIFS server.
6. From the destination SVM or the destination cluster, initialize the SVM replication relationship: snapmirror initialize -source-path SVM_name: -destination-path SVM_name: