Acronis K/Backup & Recovery 10 Srv+5 Workst/DE KIT33100124739 Manuale Utente
Codici prodotto
KIT33100124739
Copyright © Acronis, Inc., 2000-2009
205
Centralized vault
A networked location allotted by the management server (p. 210) administrator to serve as storage
for the backup archives (p. 201). A centralized vault can be managed by a storage node (p. 212) or be
unmanaged. The total number and size of archives stored in a centralized vault are limited by the
storage size only.
for the backup archives (p. 201). A centralized vault can be managed by a storage node (p. 212) 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. 211) on the server. The shortcut to the vault
appears on the machines in the Centralized vaults list. Any backup plan (p. 202) existing on the
machines, including local plans, can use the centralized vault.
to the vault are distributed to all machines registered (p. 211) on the server. The shortcut to the vault
appears on the machines in the Centralized vaults list. Any backup plan (p. 202) 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.
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. 201) from a backup archive (p. 201) in order to get rid of outdated backups or
prevent the archive from exceeding the desired size.
prevent the archive from exceeding the desired size.
Cleanup consists in applying to an archive the retention rules set by the backup plan (p. 202) that
produces the archive. This operation checks if the archive has exceeded its maximum size and/or for
expired backups. This may or may not result in deleting backups depending on whether the retention
rules are violated or not.
produces the archive. This operation checks if the archive has exceeded its maximum size and/or for
expired backups. This may or may not result in deleting backups depending on whether the retention
rules are violated or not.
For more information please refer to Retention rules (p. 33).
Console (Acronis Backup & Recovery 10 Management Console)
A tool for remote or local access to Acronis agents (p. 201) and Acronis Backup & Recovery 10
Management Server (p. 210).
Management Server (p. 210).
Having connected the console to the management server, the administrator sets up and manages
backup policies (p. 202) and accesses other management server functionality, that is, performs
centralized management (p. 204). Using the direct console-agent connection, the administrator
performs direct management (p. 206).
backup policies (p. 202) and accesses other management server functionality, that is, performs
centralized management (p. 204). Using the direct console-agent connection, the administrator
performs direct management (p. 206).
Consolidation
Combining two or more subsequent backups (p. 201) belonging to the same archive (p. 201) into a
single backup.
single backup.
Consolidation might be needed when deleting backups, either manually or during cleanup (p. 205).
For example, the retention rules require to delete a full backup (p. 209) that has expired but retain
the next incremental (p. 210) 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.
For example, the retention rules require to delete a full backup (p. 209) that has expired but retain
the next incremental (p. 210) 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.