Acronis Backup & Recovery 10 Advanced Server SBS Edition Manuale Utente
252
Copyright © Acronis, Inc., 2000-2010
The resulting archive's options
The exported archive inherits the options of the original archive, including encryption and the
password. When exporting a password-protected archive, you are prompted for the password. If the
original archive is encrypted, the password is used to encrypt the resulting archive.
password. When exporting a password-protected archive, you are prompted for the password. If the
original archive is encrypted, the password is used to encrypt the resulting archive.
Source and destination locations
When the console is connected to a managed machine, you can export an archive or part of an
archive to and from any location accessible to the agent residing on the machine. These include
personal vaults, locally attached tape devices, removable media and, in the advanced product
versions, managed and unmanaged centralized vaults.
archive to and from any location accessible to the agent residing on the machine. These include
personal vaults, locally attached tape devices, removable media and, in the advanced product
versions, managed and unmanaged centralized vaults.
When the console is connected to a management server, two export methods are available:
export from a managed vault. The export is performed by the storage node that manages the
vault. The destination can be a network share or a local folder of the storage node.
vault. The destination can be a network share or a local folder of the storage node.
export from an unmanaged centralized vault. The export is performed by the agent installed on
the managed machine you specify. The destination can be any location accessible to the agent,
including a managed vault.
the managed machine you specify. The destination can be any location accessible to the agent,
including a managed vault.
Tip. When configuring export to a deduplicating managed vault, choose a machine where the deduplication
add-on to the agent is installed. Otherwise the export task will fail.
add-on to the agent is installed. Otherwise the export task will fail.
Operations with an export task
An export task starts immediately after you complete its configuration. An export task can be
stopped or deleted in the same way as any other task.
stopped or deleted in the same way as any other task.
Once the export task is completed, you can run it again at any time. Before doing so, delete the
archive that resulted from the previous task run if the archive still exists in the destination vault.
Otherwise the task will fail. You cannot edit an export task to specify another name for the
destination archive (this is a limitation).
archive that resulted from the previous task run if the archive still exists in the destination vault.
Otherwise the task will fail. You cannot edit an export task to specify another name for the
destination archive (this is a limitation).
Tip. You can implement the staging scenario manually, by regularly running the archive deletion task followed
by the export task.
by the export task.
Different ways to create an export task
Using the Export page is the most general way to create an export task. Here, you can export any
backup, or archive you have permission to access.
backup, or archive you have permission to access.
You can access the Export page from the Vaults view. Right-click the object to export (archive or
backup) and select Export from the context menu. The Export page will be opened with the pre-
selected object as a source. All you need to do is to select a destination and (optionally) provide a
name for the task.
backup) and select Export from the context menu. The Export page will be opened with the pre-
selected object as a source. All you need to do is to select a destination and (optionally) provide a
name for the task.
To export an archive or a backup perform the following steps.
General
Task name
[Optional] Enter a unique name for the task. A conscious name lets you quickly identify the
task among the others.
task among the others.
Task credentials (p. 253)