365
Copyright © Acronis, Inc., 2000-2010
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. 38).
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.
Finally, we create retention rules for the archive: let us retain only backups that are no older than six
months, and let the cleanup be performed after each backup task and also on the last day of every
month.
Retention rules
: Delete backups older than
6 months
Apply the rules
:
After backing up
,
On schedule
Cleanup schedule
:
Monthly
, on the
Last day
of
All months
, at
10:00 PM
By default, a backup is not deleted as long as it has dependent backups that must be kept. For
example, if a full backup has become subject to deletion, but there are incremental or differential
backups that depend on it, the deletion is postponed until all the dependent backups can be deleted
as well.
For more information, see Retention rules (p. 38).
Resulting tasks
Any custom scheme always produces three backup tasks and—in case the retention rules are
specified—a cleanup task. Each task is listed in the list of tasks either as
Scheduled
(if the schedule
has been set up) or as
Manual
(if the schedule has not been set up).
You can manually run any backup task or cleanup task at any time, regardless of whether it has a
schedule.