BackupWhen

Backup When Page Overview

This page allows Users to control when backup runs should be performed. It allows Users to specify the maximum interval between two Full backups.

All parameters in this page must be specified for a backup set before activating (scheduling) backup runs.

Backup When Page Options

The Backup When page lets you control how backups will be scheduled. You can specify the overall backup cycle time, as well as the days, dates, and times within the backup cycle when backups will execute.

• The Backup When page is divided into two panels shown below.

Backup Cycle Panel

A Full Backup Cycle is the maximum time within which at least one full backup of each DLE in the backup set must happen. Amanda tries to perform full backups of the DLE as many times as possible within the backup cycle to reduce the backup recovery time. You can specify Full Backup Cycle in either days or in months.

Time Range

Select Days or Months from the dropdown for specifying the Full Backup Cycle. The GUI initially displays the default Time Range value as Days. After the Month option is selected, the ZMC right panel changes to reflect that choice.

Backup Cycle

The number of days or months within which at least one full backup for all DLEs must be performed.

Backup Time

Specifies the time of day when the backup run starts, in 24-hour format (1:00 pm is specified as 1300). This time is the same for all days and for all the DLEs in the set.

Media in rotation

Specifies the number of backup media (i.e. tapes, virtual tapes, etc.). Backup media may be overwritten after the value specified is used. For example: If the number of media in rotation is 7, and each backup run consumes a medium, daily backups would go through the rotation in 7 days, and go back to overwriting the first volume on the 8th day. This results in a backup retention policy of 7 days.

Backup Week/Month Panel

The panel on the right (titled Backup Week or Backup Month depending on context) lets you set which days of the week or days of the month to run backups.

• When choosing a calender month, and a date such as the 31st does not exist, no back up will run on that day. It will, however, run in those months that the date is valid.

Example 1 Week(Days):+
Suppose Mondays and Fridays are heavy work schedule days on which days the user does not want any Backup to run.
Then tick Tuesday, Wednesday, Thursday, Saturday and Sunday.
If the user has specified a 10 day Backup cycle, and the user is starting the process on a Monday, no backup will happen that day. 
Full/ incremental backups will happen on Tuesdays, Wednesdays, Thursdays, Saturdays and Sundays. 
This will repeat for the entire cycle.
Example 2(Dates of)Month:
For another backup set, where User has selected slowly changing data, User has specified a 3 month Backup Cycle.   
The User wants the backups to run on the 1st, 10th and 20th of each month irrespective of what day of the week they fall on.
Just tick the dates 1st, 10th and 20th in the Month panel.

Note: On Solaris 10 servers, choosing all days of the week does not work from the Zmanda Management Console. The crontab entry on the Solaris 10 server must be changed manually. Change the crontab entry for amdump from 1-7 to 0-6 on the Amanda server on Solaris

Save

Click the Save button to save all changes before moving to the next page. If all the parameters have been entered correctly, following message is displayed:

Scheduling parameters have been saved for this backup set.