vserver create -vserver SVM -subtype dp-destination

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

The following example creates a destination SVM named svm_backup:

For more information, see Create an SVM intercluster peer relationship.

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.

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

snapmirror create -source-path SVM: -destination-path SVM: -type DP|XDP -schedule schedule -policy policy -identity-preserve false

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:

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

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:

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:

vserver stop

SVM name

The following example stops a destination SVM named dvs1:

See SMB only: Creating an SMB server.

snapmirror initialize -source-path SVM_name: -destination-path SVM_name: