Table of ContentsView in Frames

Scheduling Snapshot copy backups to the SnapVault secondary system

You can schedule the backup of SnapVault Snapshot copies from the primary systems to the secondary system, by using the snapvault snap sched -x command.

Step

  1. From the secondary system, enter the following command on a single line:snapvault snap sched -x sec_vol snap_name schedule_spec
    The -x portion of the command is required on the secondary system. This parameter specifies that the SnapVault secondary qtrees on the specified volume are updated from their associated primary system qtrees just before the new Snapshot copy of the specified volume is created.

    sec_vol is the name of the volume on the secondary system for which this Snapshot copy is scheduled.

    snap_name is the basename of the set of Snapshot copies to create, for example, sv_nightly. The basename of this Snapshot set must match the basename of the corresponding Snapshot copy set configured on the primary system volume. Each new Snapshot copy created for this set is numbered 0, the number of each previous Snapshot copy in this set is increased by 1, and the oldest Snapshot copy in this set is deleted. The snap_name must not be hourly, nightly, or weekly to avoid conflict with regular Data ONTAP snap sched Snapshot copies.

    schedule_spec is made up of count[@day_list][@hour_list].
    • count is the number of Snapshot copies to retain for this set. A zero (0) in this field means no new secondary system Snapshot copy will be created for this set, although the qtrees on the secondary system will be updated by the transfers from the primary systems.
      Attention: The combined total of Snapshot copies retained for this and other Snapshot sets cannot exceed 251 Snapshot copies per volume. If it does, SnapVault will not create new Snapshot copies.
    • @day_list is a comma-separated list that specifies the days on which a new Snapshot copy is created for this set. Valid entries are mon, tue, wed, thu, fri, sat, sun. They are not case-sensitive. You can specify a range using a dash (-), for example, mon-sun. The dash (-) by itself means no Snapshot copy will be created automatically. You can create the Snapshot copy manually.
    • @hour_list specifies the hours at which a new Snapshot copy is created for this set. Valid entries are whole numbers from 0 to 23. You can specify a range using a dash (-), or use a comma-separated list, for example, 6, 8-17, 19, 21, 23. The default is midnight (0).
      Note: SnapVault transfers scheduled on the secondary system with the snapvault snap sched -x command are started five minutes after the hour you specify, to give SnapVault on the primary systems enough time to create Snapshot copies before the secondary system starts the update.
    Note: You can turn off the SnapVault Snapshot copy schedule on the primary or secondary system at any time with the snapvault snap unsched command. You can also use the options snapvault.enable off to stop all SnapVault transfers.

Scheduling Snapshot copy backups to the SnapVault secondary system

The following three snapvault snap sched command lines schedule three sets of SnapVault updates and Snapshot copies on volume vol1 of the secondary systems.
systemA> snapvault snap sched -x vol1 sv_weekly 5@sat@21

systemA> snapvault snap sched -x vol1 sv_nightly 5@mon-fri@20

systemA> snapvault snap sched -x vol1 sv_hourly 4@mon-fri@8-19
Result: SnapVault transfers qtree data from the primary systems Snapshot copy as follows:
  • SnapVault transfers sv_weekly.0 to the secondary storage system every Saturday at 9:00 p.m., makes a new Snapshot copy with the same name containing all the transferred data, and keeps five copies.
  • SnapVault transfers sv_nightly.0 to the secondary system every Monday through Friday at 8:00 p.m., makes a new Snapshot copy with the same name containing all the transferred data, and keeps five copies.
  • SnapVault transfers sv_hourly.0 to the secondary storage system every hour from 8:00 a.m. to 7:00 p.m., Monday through Friday, makes a new Snapshot copy with the same name containing all the transferred data, and keeps four copies.