User`s guide

Examples

Weekly full backup

The following scheme yields a full backup performed every Friday night.

Full backup: Schedule: Weekly, every Friday, at 10:00 PM

Here, all parameters except Schedule in Full backup are left empty. All backups in the archive are

kept indefinitely (no archive cleanup is performed).

Full and incremental backup plus cleanup

With the following scheme, the archive will consist of weekly full backups and daily incremental

backups. We further require that a full backup begin only after all users have logged off.

Full backup: Schedule: Weekly, every Friday, at 10:00 PM

Full backup: Conditions: User is logged off

Incremental: Schedule: Weekly, every workday, at 9:00 PM

Also, let all backups older than one year be deleted from the archive, and let the cleanup be

performed upon creating a new backup.

Retention rules: Delete backups older than 12 months

Apply the rules: After backing up

By default, a one-year-old full backup will not be deleted until all incremental backups that depend

on it become subject to deletion too. For more information, see Retention rules (p. 31).

Monthly full, weekly differential, and daily incremental backups plus cleanup

This example demonstrates the use of all options available in the Custom scheme.

Suppose that we need a scheme that will produce monthly full backups, weekly differential backups,

and daily incremental backups. Then the backup schedule can look as follows.

Full backup: Schedule: Monthly, every Last Sunday of the month, at 9:00 PM

Incremental: Schedule: Weekly, every workday, at 7:00 PM

Differential: Schedule: Weekly, every Saturday, at 8:00 PM

Further, we want to add conditions that have to be satisfied for a backup task to start. This is set up

in the Conditions fields for each backup type.

Full backup: Conditions: Location available

Incremental: Conditions: User is logged off

Differential: Conditions: User is idle

As a result, a full backup—originally scheduled at 9:00 PM—may actually start later: as soon as the

backup location becomes available. Likewise, backup tasks for incremental and differential backups

will wait until all users are logged off and users are idle, respectively.