Define a schedule for creating a local copy on the destination with ONTAP
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-

Collection of separate PDF docs
Creating your file...
For SnapVault and unified replication relationships, you can protect against the possibility that an updated snapshot is corrupted by creating a copy of the last transferred snapshot on the destination. This “local copy” is retained regardless of the retention rules on the source, so that even if the snapshot originally transferred by SnapMirror is no longer available on the source, a copy of it will be available on the destination.
You specify the schedule for creating a local copy in the -schedule
option of the snapmirror policy add-rule
command. Learn more about snapmirror policy add-rule
in the ONTAP command reference.
-
Define a schedule for creating a local copy on the destination:
snapmirror policy add-rule -vserver SVM -policy policy_for_rule -snapmirror-label snapmirror-label -schedule schedule
For an example of how to create a job schedule, see Creating a replication job schedule.
The following example adds a schedule for creating a local copy to the default
MirrorAndVault
policy:cluster_dst::> snapmirror policy add-rule -vserver svm1 -policy MirrorAndVault -snapmirror-label my_monthly -schedule my_monthly
The following example adds a schedule for creating a local copy to the custom
my_unified
policy:cluster_dst::> snapmirror policy add-rule -vserver svm1 -policy my_unified -snapmirror-label my_monthly -schedule my_monthly