8 Copyright © Acronis, Inc., 2000-2011
3.2.2 Single file backup scheme (Always Incremental mode)
Usually, backups are kept only for a certain time period (retention time) or there is a policy to keep
only the last X backups in the backup chain. Backup archives are managed on a daily, weekly, etc.
basis. The main limitation of the Legacy mode backup archive is that you cannot delete a random
backup from the backup chain since it may have dependencies on it from subsequent backups. This is
where Always Incremental backup archive can help .
Always Incremental mode uses a new generation archive format which may contain several backups
from a number of virtual machines. After the first full backup, all other backups are saved to this
archive in incremental mode. Physically all data is located inside one file as opposed to the Legacy
archive format where each backup is stored in a separate .tib file. Therefore, unlike the Legacy mode
archive, it is possible to delete a random backup from Always Incremental archive even if it has
dependencies.
When a certain backup expires due to the pre-
The blocks of expired backups with dependencies (which are needed to restore the newer backups)
data that is not older than two days in order to restore the backup (retention time). This is the
basic rule of the Always Incremental archive. All excessive data in the archive is marked for deletion,
however all newer backups will
are filled, the total size of the archive will be increased.
This approach allows keeping the archive size as small as possible and prevents it from excessive
growing. Also, the implementation of this backup scheme significantly saves time and resources for
operation. Thus, the limitations of the Legacy archive mode are no longer true for Always
Incremental archive.
stays within the total size of the backups you want to keep.
