Scheduling SnapVault snapshot updates

About SnapVault snapshot update schedules

After you have completed the initial baseline backup of qtrees on the filer primary storage systems to qtrees on the SnapVault secondary storage system (see Starting a SnapVault backup relationship), you must use the snapvault snap sched command to schedule

Regular SnapVault snapshot times of volumes on the primary storage system to capture new and changed data in the qtrees that have a SnapVault relationship configured through the snapvault start command
Regular transport of new or modified data in the primary qtrees to their associated secondary qtrees on the SnapVault secondary storage system
Regular Snapshots of the volume containing the updated secondary qtrees for SnapVault archival.
Note
The descriptions and procedures in this section pertain to SnapVault backup of NetApp filers only. For descriptions and procedures pertaining to SnapVault backup of Open Systems drives and directories, see Setting up SnapVault backup on Open Systems platforms and Managing SnapVault backup of Open Systems platforms.

Scheduling snapshots on the SnapVault filer primary storage system

To schedule a set of snapshots on the SnapVault primary storage system, you use the snapvault snap sched command to specify the volume to be snapshot, the snapshot basename, how many versions of the snapshots to be retained, and the days and hours to execute this set of snapshots.

To set a schedule for the primary storage system, complete the following step.

Step	Action
1	From the primary storage system, enter the following command: snapvault snap sched volume_name snap_name schedule_spec volume_name is the name of the volume on the primary storage system on which to create this set of snapshots. snap_name is the basename of a snapshot set, for example, sv_nightly. The name of this snapshot must be the same on the primary storage system and on the secondary storage system. The snap_name must not be "hourly," "nightly," or "weekly" to avoid conflict with `snap sched` snapshots. schedule_spec is made up of count[@day_list][@hour_list]. count is the number of snapshots to retain for this snapshot set. A zero (0) in this field means no new instance of this snapshot will be created. Caution The combined total of snapshots retained for this and other snapshot sets cannot exceed 251 snapshots per volume. If it does, SnapVault will not create new snapshots. @day_list is a comma-separated list that specifies the days on which a new snapshot for this set is created. 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-fri.` The dash (-) by itself means no snapshot will be created automatically. You can create the snapshot manually. The default value is `mon-sun`. @hour_list specifies the hours at which a new snapshot 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, `7, 8-17, 19, 21, 23`. The default is midnight (`0`).

Step

Action

From the primary storage system, enter the following command:

snapvault snap sched volume_name snap_name schedule_spec

volume_name is the name of the volume on the primary storage system on which to create this set of snapshots.

snap_name is the basename of a snapshot set, for example, sv_nightly. The name of this snapshot must be the same on the primary storage system and on the secondary storage system. The snap_name must not be "hourly," "nightly," or "weekly" to avoid conflict with snap sched snapshots.

schedule_spec is made up of count[@day_list][@hour_list].

count is the number of snapshots to retain for this snapshot set. A zero (0) in this field means no new instance of this snapshot will be created.

Caution
The combined total of snapshots retained for this and other snapshot sets cannot exceed 251 snapshots per volume. If it does, SnapVault will not create new snapshots.

@day_list is a comma-separated list that specifies the days on which a new snapshot for this set is created. 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-fri. The dash (-) by itself means no snapshot will be created automatically. You can create the snapshot manually. The default value is mon-sun.

@hour_list specifies the hours at which a new snapshot 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, 7, 8-17, 19, 21, 23. The default is midnight (0).

Example

The following three snapvault snap sched command lines schedule three sets of SnapVault snapshots on volume vol1 of the primary storage system.

filerB> snapvault snap sched vol1 sv_weekly 1@sat@19

filerB> snapvault snap sched vol1 sv_nightly 2@mon-fri@19

filerB> snapvault snap sched vol1 sv_hourly 11@mon-fri@7-18

Result

SnapVault primary storage system creates a snapshot on the specified volume, names it

sv_weekly.0 every Saturday at 7:00 p.m., and keeps one copy.
sv_nightly.0 every Monday through Friday at 7:00 p.m., and keeps two copies.
sv_hourly.0 every Monday through Friday, every hour from 7:00 a.m. to 6:00 p.m., and keeps eleven copies.

Scheduling snapshot backups to the SnapVault secondary storage system

To schedule the backup of SnapVault snapshots from the filer primary storage systems to the secondary storage system, use the snapvault snap sched -x command.

Complete the following step.

Step	Action
1	From the secondary storage system, enter the following command on a single line: snapvault snap sched -x sec_vol snap_name schedule_spec

In the command line just described:

The -x portion of the command is required on the secondary storage 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 of the specified volume is created.
sec_vol is the name of the volume on the secondary storage system for which this snapshot is scheduled.
snap_name is the basename of the set of snapshots to create, for example, sv_nightly. The basename of this snapshot set must match the basename of the corresponding snapshot set configured on the primary storage system volume. Each new snapshot created for this set is numbered 0, the number of each previous snapshot in this set is increased by 1, and the oldest snapshot in this set is deleted. The snap_name must not be "hourly," "nightly," or "weekly" to avoid conflict with regular Data ONTAP snap sched snapshots.
schedule_spec is made up of count[@day_list][@hour_list].
- count is the number of snapshots to retain for this set. A zero (0) in this field means no new secondary storage system snapshot will be created for this set, although the qtrees on the secondary storage system will be updated by the transfers from the primary storage systems.
  Caution
  The combined total of snapshots retained for this and other snapshot sets cannot exceed 251 snapshots per volume. If it does, SnapVault will not create new snapshots.
- @day_list is a comma-separated list that specifies the days on which a new snapshot 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 will be created automatically. You can create the snapshot manually.
- @hour_list specifies the hours at which a new snapshot 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
  You can stop and unschedule a set of snapshots on the primary storage system or the secondary storage system at any time with the snapvault snap unsched command. (See Unscheduling SnapVault snapshots.)

Example

The following three snapvault snap sched command lines schedule three sets of SnapVault transfer updates and snapshots on volume vol1 of the secondary storage system.

filerA> snapvault snap sched -x vol1 sv_weekly 5@sat@21

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

filerA> snapvault snap sched -x vol1 sv_hourly 4@mon-fri@8-19

Result:

SnapVault transfers qtree data from the primary storage system's snapshot as follows:

SnapVault transfers sv_weekly.0 to the secondary storage system every Saturday at 9:00 p.m., makes a new snapshot with the same name of all the transferred data, and keeps five copies.
SnapVault transfers sv_nightly.0 to the secondary storage system every Monday through Friday at 8:00 p.m., makes a new snapshot with the same name of 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 with the same name of all the transferred data, and keeps four copies.
Note
Snapshots scheduled on the secondary storage system with the snapvault snap sched -x command are created five minutes after the hour you specify to give SnapVault on the filer primary storage systems enough time to create the snapshots they need before the secondary storage system updates from them.

How to display the currently configured snapshot schedule

Enter the snapvault snap sched command without a schedule specification to show the current schedule values. If no snap_name is given, the command shows the basenames of all snapshot sets scheduled for the specified volume. If no volume_name is given, the command shows the basenames of all snapshots sets for all SnapVault volumes on the filer.

Example

filerA> snapvault snap sched

xfer   vol1 sv_weekly 5@sat@21

xfer   vol1 sv_nightly 5@mon-fri@20

xfer   vol1 sv_hourly 4@mon-fri@8-19

xfer   vol2 sv_nightly 5@mon-fri@20

xfer   vol2 sv_hourly 4@mon-fri@8-19