Skip to main content
NetApp Knowledge Base

What are the different ways to schedule SnapMirror updates using ONTAP features?

Views:
2,683
Visibility:
Public
Votes:
3
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.7+
  • SnapMirror
  • SnapVault

Answer

There are two possible ways to make a SnapMirror update by schedule since ONTAP 9.7:

  1. Put a schedule as a parameter of the SnapMirror relationship:
  • A cron schedule can be set as a SnapMirror variable during the creation of a relationship:

 cluster1::> snapmirror create -source-path test: ?
   { [-destination-path] {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>|<[vserver:]/cg/[cgname]>}  Destination Path
  | [ -destination-cluster <cluster_name> ]     Destination Cluster (default: cluster1)
     [-destination-vserver] <vserver name>      Destination Vserver
    [[-destination-volume] <volume name>] }     Destination Volume (default: "")
  [[-type] {DP|LS|XDP|RST|TDP}]                 Relationship Type
  [ -vserver <vserver name> ]                   Managing Vserver
  [ -schedule <text> ]                          SnapMirror Schedule
  [ -policy <snapmirror policy> ]               SnapMirror Policy
  [ -tries {<integer>|unlimited} ]              Tries Limit
  [ -throttle|-k {<integer>|unlimited} ]        Throttle (KB/sec) (default: unlimited)
  [ -cg-item-mappings {<source volume>:@<destination volume>|<source item path>:@<destination item path>}, ... ]                                                             Consistency Group Item Mappings
  [ -identity-preserve {true|false} ]           Identity Preserve Vserver DR (default: false)
  [ -is-auto-expand-enabled {true|false} ]      Is Auto Expand Enabled

  • A cron schedule can be set as a SnapMirror variable during modification of a relationship by CLI:

cluster1::> snapmirror modify -source-path test: ?
   { [-destination-path] {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>|<[vserver:]/cg/[cgname]>}  Destination Path
  | [ -destination-cluster <cluster_name> ]     Destination Cluster
     [-destination-vserver] <vserver name>      Destination Vserver
     [-destination-volume] <volume name> }      Destination Volume
  [[-vserver] <vserver name>]                   Managing Vserver
  [ -schedule <text> ]                          SnapMirror Schedule
  [ -policy <snapmirror policy> ]               SnapMirror Policy
  [ -tries {<integer>|unlimited} ]              Tries Limit
  [ -throttle|-k {<integer>|unlimited} ]        Throttle (KB/sec)
  [ -is-auto-expand-enabled {true|false} ]      Is Auto Expand Enabled
  [ -foreground|-w [true] ]                     Foreground Process

  1. Put a schedule over the SnapMirror Policy:
  • You can add a schedule for the SnapMirror policy in ONTAP System Manager:

clipboard_eb110d355812557aee3b60ae0c34db662.png

  • You can add the feature by CLI with a hidden command
  • SnapMirror policies with a schedule can be checked, added, or modified with a hidden field called transfer-schedule-name:

cluster::> snapmirror policy show -fields transfer-schedule-name

  • The field transfer-schedule-name is public in ONTAP 9.11.1. For more details, refer to BUG 1349723 - Considerations for SnapMirror policies with "transfer_schedule" and the "-schedule" parameters in a SnapMirror relationship
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.