Acronis Backup Recovery 10 Server for Windows Manuale Utente
Copyright © Acronis, Inc., 2000-2009
173
A management server has two built-in groups that contain all machines of each type: All physical
machines (p. 179), All virtual machines (p. 182).
machines (p. 179), All virtual machines (p. 182).
Built-in groups cannot be deleted, moved to other groups or manually modified. Custom groups
cannot be created within built-in groups. There is no way to remove a physical machine from the
built-in group except for deleting the machine from the management server. Virtual machines are
deleted as a result of their host server deletion.
cannot be created within built-in groups. There is no way to remove a physical machine from the
built-in group except for deleting the machine from the management server. Virtual machines are
deleted as a result of their host server deletion.
A backup policy (p. 171) can be applied to a built-in group.
C
Centralized backup plan
A backup plan (p. 171) that appears on the managed machine (p. 178) as a result of deploying a
backup policy (p. 171) from the management server (p. 179). Such plan can be modified only by
editing the backup policy.
backup policy (p. 171) from the management server (p. 179). Such plan can be modified only by
editing the backup policy.
Centralized management
Management of the Acronis Backup & Recovery 10 infrastructure through a central management unit
known as Acronis Backup & Recovery 10 Management Server (p. 179). The centralized management
operations include:
known as Acronis Backup & Recovery 10 Management Server (p. 179). The centralized management
operations include:
•
creating, applying and managing backup policies (p. 171)
•
•
managing the tasks (p. 181) existing on the machines
•
creating and managing centralized vaults (p. 173) for storing archives
•
managing storage nodes (p. 180)
•
monitoring activities of the Acronis Backup & Recovery 10 components, viewing the centralized
log and more.
log and more.
Centralized task
A task (p. 181) belonging to a centralized backup plan (p. 173). Such task appears on the managed
machine (p. 178) as a result of deploying a backup policy (p. 171) from the management server (p.
179) and can be modified only by editing the backup policy.
machine (p. 178) as a result of deploying a backup policy (p. 171) from the management server (p.
179) and can be modified only by editing the backup policy.
Centralized vault
A networked location allotted by the management server (p. 179) administrator to serve as storage
for the backup archives (p. 170). A centralized vault can be managed by a storage node (p. 180) 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. 170). A centralized vault can be managed by a storage node (p. 180) 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. 180) on the server. The shortcut to the vault
appears on the machines in the Centralized vaults list. Any backup plan (p. 171) existing on the
machines, including local plans, can use the centralized vault.
to the vault are distributed to all machines registered (p. 180) on the server. The shortcut to the vault
appears on the machines in the Centralized vaults list. Any backup plan (p. 171) existing on the
machines, including local plans, can use the centralized vault.