Acronis Backup for Linux Server - User Guide - Manual (Page 202)

202 Copyright © Acronis International GmbH, 2002-2014
Centralized vault
A networked location allotted by the management server (p. 207) administrator to serve as storage
for the backup archives (p. 199). A centralized vault can be managed by a storage node (p. 209) or be
unmanaged. The total number and size of archives stored in a centralized vault are limited by the
storage size only.
As soon as the management server administrator creates a centralized vault, the vault name and
path to the vault are distributed to all machines registered (p. 208) on the server. The shortcut to the
vault appears on the machines in the Vaults list. Any backup plan (p. 199) existing on the machines,
including local plans, can use the centralized vault.
On a machine that is not registered on the management server, a user having the privilege to back up
to the centralized vault can do so by specifying the full path to the vault. If the vault is managed, the
user's archives will be managed by the storage node as well as other archives stored in the vault.
Cleanup
Deleting backups (p. 199) from a backup archive (p. 199) or moving them to a different location in
order to get rid of outdated backups or prevent the archive from exceeding the desired size.
Cleanup consists of applying retention rules (p. 209) to an archive. The retention rules are set by the
backup plan (p. 199) that produces the archive. Cleanup may or may not result in deleting or moving
backups depending on whether the retention rules are violated or not.
Console (Acronis Backup Management Console)
A tool for remote or local access to Acronis agents (p. 199) and Acronis Backup Management Server
(p. 207).
Having connected the console to the management server, the administrator sets up centralized
backup plans (p. 201) and accesses other management server functionality, that is, performs
centralized management (p. 201). Using the direct console-agent connection, the administrator
performs direct management (p. 203).
Consolidation
Combining two or more subsequent backups (p. 199) belonging to the same archive (p. 199) into a
single backup.
Consolidation might be needed when deleting backups, either manually or during cleanup (p. 202).
For example, the retention rules require to delete a full backup (p. 206) that has expired but retain
the next incremental (p. 206) one. The backups will be combined into a single full backup which will
be dated with the incremental backup's date. Since consolidation may take a lot of time and system
resources, retention rules provide an option to not delete backups with dependencies. In our
example, the full backup will be retained until the incremental one also becomes obsolete. Then both
backups will be deleted.
D
Data catalog
Allows a user to easily find the required version of data and select it for recovery. On a managed
machine (p. 207), users can view and search data in any vault (p. 210) accessible from this machine.