You can create a custom replication policy if the default policy for a relationship is not suitable. You might want to compress data in a network transfer, for example, or modify the number of attempts SnapMirror makes to transfer Snapshot copies.
The policy type of the replication policy determines the type of relationship it supports. The table below shows the available policy types.
Policy type |
Relationship type |
---|---|
async-mirror | SnapMirror DR |
vault | SnapVault |
mirror-vault | Unified replication |
strict-sync-mirror | SnapMirror Synchronous in the StrictSync mode (supported starting with ONTAP 9.5) |
sync-mirror | SnapMirror Synchronous in the Sync mode (supported starting with ONTAP 9.5) |
For complete command syntax, see the man page.
Starting with ONTAP 9.5, you can specify the schedule for creating a common Snapshot copy schedule for SnapMirror Synchronous relationships by using the -common-snapshot-schedule parameter. By default, the common Snapshot copy schedule for SnapMirror Synchronous relationships is one hour. You can specify a value from 30 minutes to two hours for the Snapshot copy schedule for SnapMirror Synchronous relationships.
cluster_dst::> snapmirror policy create -vserver svm1 -policy DR_compressed -type async-mirror -commentDR with network compression enabled-is-network-compression-enabled true
cluster_dst::> snapmirror policy create -vserver svm1 -policy my_snapvault -type vault
cluster_dst::> snapmirror policy create -vserver svm1 -policy my_unified -type mirror-vault
cluster_dst::> snapmirror policy create -vserver svm1 -policy my_strictsync -type strict-sync-mirror -common-snapshot-schedule my_sync_schedule
For vault
and mirror-vault
policy types, you must define rules that determine which Snapshot copies are transferred during initialization and update.
Use the snapmirror policy show command to verify that the SnapMirror policy was created. For complete command syntax, see the man page.