2.2.2Local approach: Importing old tasks into new agents .................................................................................. 4
2.2.3Centralized approach: Converting group tasks into backup policies .......................................................... 6
2.2.4Combination of both approaches .................................................................................................................. 7
2.3 Using backup archives created with Acronis True Image Echo ................................................. 8
2.3.1Access to archives stored in a local or network folder ................................................................................. 8
2.3.2Access to archives stored on Acronis Backup Server.................................................................................... 8
2.3.3Coexistence of the backup server and the storage node ............................................................................. 9
3.6.2Importing all tasks at once ............................................................................................................................ 14
3.6.4Importing old settings ................................................................................................................................... 15
5What else you may want to know ........................................................................................ 19
1 Introduction
Acronis® Backup & Recovery™ 10 succeeds Acronis True Image Echo as the next generation disaster
recovery solution. To make customers comfortable about migration to the new product, Acronis
gives them the flexibility of performing a gradual upgrade; enables the customers to import backup
strategies they used with Acronis True Image Echo into Acronis Backup & Recovery 10; and provides
documentation that covers all aspects of the upgrade process.
2 Choosing the way to upgrade
This chapter provides an overview about the possible ways of upgrading from Acronis True Image
Echo and describes the options you can choose during the upgrade.
You will also get some general information on how to:
Perform gradual upgrade in case you want to keep part of your infrastructure protected by
Acronis True Image Echo
Migrate old tasks from Acronis True Image Echo
Use the backup archives created with the previous version of Acronis True Image.
Thus, after reading this chapter you should be able to make a decision on which method of upgrading
is most convenient for your infrastructure.
2.1 Gradual upgrade
Components of Acronis Backup & Recovery 10 do not interact with Acronis True Image Echo
components. The old console cannot be connected to a new agent; new agents do not back up to
Acronis Backup Server; old agents cannot be registered on Acronis Backup & Recovery 10
Management Server.
The new and the old agent cannot run on the same machine, so the old agent is removed when you
install the new one. Apart from this, the products do not interact with each other—they can operate
independently in the same network, each protecting only those machines where the respective agent
resides. This makes possible gradual or partial migration to the new product or deployment of the
new product only on the machines that are not protected with Echo. A sample scenario of gradual
upgrade and the steps to perform are described later in this document.
In fact, the upgrade granularity is a single machine, which implies upgrade on an as-needed basis
with very minimal notice. Also, you can test a new backup strategy on a single machine or on few
machines, while the remaining machines are protected by Echo. Then upgrade the majority of the
Acronis True Image Echo components and apply the proven strategy to them. The minimal steps
required to start using Acronis Backup & Recovery 10 on a single machine are described later in this
document.
2.2 Importing backup strategies from Acronis True Image
Echo
In Acronis True Image Echo, a backup strategy consists of backup tasks—local tasks (tasks residing on
the agents) and group tasks (tasks residing on Acronis Group Server).
When upgrading to Acronis Backup & Recovery 10, you have the option to import these tasks by
using any of the following approaches:
Local approach: Import the local tasks without importing the group tasks. The local tasks become
local backup plans.
Centralized approach: Import the group tasks without importing the local tasks. The group tasks
become backup policies, which you can then apply to the machines to which the corresponding
group tasks originally applied—as well as to any other machine.
Combination of both: Import the group tasks and the local tasks. The resulting backup policies
apply to the corresponding machines automatically. The backup plans originating from group
tasks become centralized backup plans. The rest of the backup plans remain local.
This section describes each of these approaches.
2.2.1 Acronis Backup & Recovery 10 Upgrade Tool
Acronis Backup & Recovery 10 includes a script called Acronis Backup & Recovery 10 Upgrade Tool.
When run after upgrading the agents, this tool provides the ability to import Acronis True Image Echo
tasks into Acronis Backup & Recovery 10 and to make archives stored on Acronis Backup Server
accessible from Acronis Backup & Recovery 10. If you do not need these options, you do not need to
use the upgrade tool.
2.2.2 Local approach: Importing old tasks into new agents
Acronis Backup & Recovery 10 has the ability to import Acronis True Image Echo backup or validation
tasks into Acronis Backup & Recovery 10 agents. The backup tasks are converted into local backup
plans. You can modify them to use, if necessary, new backup schemes and scheduling options offered
by Acronis Backup & Recovery 10.
You can import all tasks at once, or import only the tasks you need. Until imported, the old tasks will
not run.
The tasks that back up data to Acronis Backup Server or validate the archives stored on it will not be
imported. This is because Acronis Backup & Recovery 10 agents are not supposed to interact with
Acronis Backup Server, as well as with other Acronis True Image Echo components. The backup
strategy that uses such tasks may be re-created with a storage node or other location as a backup
destination.
After upgrading Acronis True Image Echo (ATIE) Agent to Acronis Backup & Recovery 10 (ABR10) Agent, the
old tasks remain on the machine in the form of scripts. Then they are imported to ABR10 agent.
In case of local installation in Windows
When installing the agent locally on a machine running Windows, old backup tasks and validation
tasks are imported automatically, unless you disable the import in the installation wizard. This way,
the new agent starts protecting the machine immediately after the installation, and the gap during
which the machine is not protected is negligible.
In case of remote installation of the agents or installation using Group Policy
New agents can be installed remotely on machines running Windows, by using Acronis Backup &
Recovery 10 Management Console; or, in an Active Directory domain, the agents can be deployed
using Group Policy (or a similar software deployment tool). To import tasks in these cases, follow
these steps:
1. Deploy the agent and the upgrade tool using Group Policy
2. Create your own script that will execute the upgrade tool on each of the machines, and run this
script after the agent and the upgrade tool are deployed on all machines. An example of such
script is the following .bat file:
@echo off
%SystemDrive%
cd %ProgramFiles%\Acronis\UpgradeTool
cscript UpgradeTool.vbs Agent
To import the old tasks centrally, you may want to run this script as a logon or startup script in a
Group Policy object.
When installing the agent on a machine running Linux, you have to run the upgrade tool manually
with the Agent parameter after the installation.
Summary
The tasks existing on a machine, including those originated from Acronis Group Server, continue
functioning as local backup plans. Centralized backup policies can be created and deployed anew.
If all the tasks you need to import originate from Acronis Group Server, you can opt for the
centralized approach instead of the local approach: convert the source group task into a backup
policy and apply the policy to the machines that were included in the group task. Organizing such
machines into groups will make sense.
2.2.3 Centralized approach: Converting group tasks into backup
policies
Acronis Backup & Recovery 10 has the ability to import Acronis True Image Echo group tasks into
Acronis Backup & Recovery 10 Management Server.
The group tasks that back up data to Acronis Backup Server or validate the archives stored on it will
not be imported. In that case, create and apply a backup policy with a backup destination other than
the backup server.
The import is performed by running the same upgrade tool with the GS parameter after installing the
management server. Each group task will be converted into a backup policy.
To deploy all centralized backup strategies, you need to apply the policy to the upgraded machines
that were originally included in the group task. Instead of applying the policy to each machine
individually, you may want to organize the machines into a group on the management server and
then apply the policy to that group.
Again, you can modify the resulting polices to use new options offered by Acronis Backup & Recovery
10, or apply the policies as is.
Summary
Each group task is converted into a backup policy, which preserves and expands the ability of
centralized management. Centralized backup plans replace the tasks that originated from Acronis
Group Server. The tasks that originated locally, if any, are lost.
The benefits of this approach:
This is the only approach that enables the resulting policy to apply to a group rather than to each
individual machine.
You do not have to run the upgrade tool on each machine. This comes in handy when the agents
are installed through Group Policy.
This totally centralized approach is not an option in the following two cases:
When there are locally originated tasks on the machines and you want to keep these tasks.
When you do not wish or are not able to determine which machines were included in the group
task (normally, you see the machines when editing a group task, but there may be a vast number
of them or the group server may have already been removed).
In either of these cases, combine the centralized approach with the local approach as described
below.
2.2.4 Combination of both approaches
To continue using both local and centralized backup strategies, import both tasks into the agents and
group tasks into the management server. As soon as the machines with the agents are registered on
the management server, the server establishes a correspondence between the imported backup
tasks (converted to local backup plans) and the imported group task (converted to a backup policy).
Local backup plans sourced from the former group tasks become centralized backup plans and can be
managed from the management server. The rest of the local backup plans remain local and can be
managed both from the management server and by direct console-agent connection.
After the group task-sourced backup plans (such as Backup plan 2 in the picture) are "picked up" by
the policy, they become linked to the policy so that any change you make to the policy will be
propagated to the corresponding backup plans.
In this scenario, you should not modify the policy until all the necessary tasks are picked up by the
policy. This is especially important to remember if you opt for a gradual upgrade.
What if you need to import both tasks into the agents and group tasks into the management server,
but do not want to link backup plans to policies? To achieve this: when importing the group tasks,
run the upgrade tool with the additional –r parameter. The group task-sourced backup plans will
remain local even after the machines are registered on the management server.
Summary
You continue using the local backup strategies as local and the centralized ones as centralized. You
do not need to specify the machines to apply the resulting policy to—the correspondence between
the policy and the imported tasks establishes automatically.
The policy applies to each individual machine though. There is no way to make the policy apply to the
group.
2.3 Using backup archives created with Acronis True
Image Echo
Acronis Backup & Recovery 10 has the ability to recover data from backup archives created with
Acronis True Image Echo. If you are going to make use of this ability, consider the following.
2.3.1 Access to archives stored in a local or network folder
To facilitate access to such archives, you may want to perform any of the following optional steps:
Connect the console to a machine with the agent, and then create a personal vault where the
machine’s backups are located
Connect the console to the management server and create a centralized unmanaged vault where
backups from multiple machines are located
The vault you create can store both Acronis True Image Echo archives and Acronis Backup &
Recovery 10 archives. You can specify this vault as a destination for new backup plans and policies.
2.3.2 Access to archives stored on Acronis Backup Server
Archives stored on an Acronis Backup Server can be accessed only if you import the backup server’s
locations into Acronis Backup & Recovery 10 Storage Node.
This can be done by running the above mentioned upgrade tool with the BS parameter. The storage
node must be installed on the same machine as the backup server and the storage node service must
be granted permissions for the necessary folders.
As a result, the backup server’s locations will be accessible to the storage node in the read-only
mode. Having connected the console to the management server or to a registered machine, you will
find these locations among the centralized vaults. When operating under bootable media or on a
non-registered machine, specify the vault by path:
2.3.3 Coexistence of the backup server and the storage node
A gradual upgrade scenario might require that both the backup server and the storage node work in
parallel for a period of time. Let’s see what happens when they do so.
Assume that both the backup server and the storage node are installed and operational on the same
machine, and that you imported the backup server's locations as the storage node's centralized
vaults. In this case:
The backup server continues working as before: Acronis True Image Echo components can back
up data to and recover data from the locations; the backup server cleans up the location
according to quotas and time limits.
The storage node accesses the corresponding centralized vaults in the read-only mode: you can
view the vaults' contents and recover data from their archives, but no archives can be deleted
from the vaults or written to the vaults.
When restarting the machine or manually restarting services, make sure that the backup server
service starts before the storage node service. Otherwise, the backup server may not work.
To ensure the correct order of starting the services, you can make the storage node service
dependent on the backup server service, as described in the corresponding Microsoft Help and
Support article: http://support.microsoft.com/kb/193888.
3 The upgrade procedure
3.1 Before the upgrade
3.1.1 Preparation
Before proceeding with the upgrade on one or more machines, make sure that you have the
appropriate number of license keys for Acronis Backup & Recovery 10 and for the corresponding
Acronis True Image Echo editions.
3. Install Acronis Backup & Recovery 10 Management Server and (optionally) convert the Acronis
Group Server's group tasks to the management server's backup policies. See "Upgrading Acronis
Group Server to Acronis Backup & Recovery 10 Management Server (p. 11)".
4. Install Acronis Backup & Recovery 10 Storage Node and (optionally) convert the Acronis Backup
Server's backup locations to the storage node's centralized vaults. See "Upgrading Acronis
Backup Server to Acronis Backup & Recovery 10 Storage Node (p. 12)".
5. Upgrade Acronis True Image Echo agents and local versions, and (optionally) import the local
tasks and backup locations. See "Upgrading Acronis True Image Echo agents and local versions (p.
13)".
6. Add the machines with upgraded agents to the management server. At this point, the policy,
resulting from the group task conversion (if performed), will become applied to these machines.
3.2 Installing or upgrading the Acronis License Server
If an earlier version of the license server is already installed, upgrade it by installing the new license
server on the same machine. In this case, the old license keys will be present on the upgraded license
server. If you have not used a license server before, import both old license keys and upgrade license
keys to the newly installed license server.
To install or upgrade the license server
1. Run the Acronis Backup & Recovery 10 setup file.
2. Click Install Acronis License Server and follow the on-screen instructions.
3. Import the upgrade license keys for Acronis Backup & Recovery 10.
4. If you have not used a license server before, import the old license keys.
Result:
The license server contains the old license keys and the newly imported upgrade license keys.
You can install Acronis Backup & Recovery 10 Management Console on the same machine as Acronis
True Image Echo Management Console, or on a different machine. In either case, you can continue
using Acronis True Image Echo Management Console with Acronis True Image Echo components if
these still exist in your infrastructure.
To install Acronis Backup & Recovery 10 Management Console
1. Run the Acronis Backup & Recovery 10 setup file.
2. In the list of components, select the Management Console check box.
Acronis Backup & Recovery 10 Management Console is installed.
You can continue using Acronis True Image Echo Management Console with Acronis True Image
Echo components.
3.4 Upgrading Acronis Group Server to Acronis Backup &
Recovery 10 Management Server
You can install Acronis Backup & Recovery 10 Management Server on the same machine as the
Acronis Group Server, or on a different machine.
The management server and the group server are independent of each other: if you are not planning
to use the group server, you can uninstall it at any time, including before the management server's
installation. Otherwise, you can continue using the group server with Acronis True Image Echo
components if these still exist in your infrastructure.
It is recommended that you install Acronis Backup & Recovery 10 Agent for Windows along with the
management server – to be able to back up the server itself.
You can convert the group server's group tasks to the management server's backup policies during
installation, or after the management server is installed. You will still be able to convert group tasks
even after you uninstall the group server.
The tasks that back up data to Acronis Backup Server or validate archives stored on it cannot be converted.
To install the management server
1. Run the Acronis Backup & Recovery 10 setup file.
2. In the list of components to install, select the Management Server check box. Select to install
Agent for Windows; if conversion of group tasks is required, select to install Upgrade Tool.
3. Select where to install the components.
4. Select the Convert group tasks to backup policies check box if you want to convert group tasks
during installation. Otherwise, you can convert the tasks later at any time. For details, see
"Converting group tasks with the upgrade tool" later in this section.
5. Follow the on-screen instructions. For details, see the "Local installation (Windows)" section of
the Installation Guide.
Converting group tasks with the upgrade tool
To convert the group server's group tasks
1. On the machine where the management server is installed, log on as a member of the
Administrators group.
2. Change the current folder to the folder where the upgrade tool is installed—by default:
C:\Program Files\Acronis\UpgradeTool. If Acronis Backup & Recovery 10 is installed in a folder
other than the default folder, change the path accordingly.
3. If the management server and the group server (or more precisely, the group server’s database)
are installed on the same machine, run the following command (note capitalization):
cscript UpgradeTool.vbs GS [-r]
(the optional parameter -r is described below). Otherwise, run the following command:
Specifies the name or IP address of the machine where the group server, or more precisely,
the group server’s database (GroupServerEcho.fdb), resides.
-uUserName
Specifies the user name of a member of the Administrators group on the MachineName
machine.
-pPassword
Specifies the password for the UserName user. If you skip this parameter, the upgrade tool
will prompt you for a password.
-r
Effective only if you are planning to upgrade the machines' tasks—see "Upgrading Acronis
True Image Echo agents and local versions (p. 13)".
This parameter prohibits the conversion of local backup plans, resulting from the upgrade of
group tasks on a machine, to centralized backup plans. When this parameter is specified,
local backup plans resulting from upgrade of group tasks on a machine, will remain local after
the machine is registered on the management server. Otherwise, the management server
will convert them to centralized backup plans and establish correspondence between these
centralized plans and the policy resulting from the group task upgrade.
Result:
The imported group tasks become the management server's backup policies and appear in the
Backup policies view.
(After you upgraded tasks on a machine and if you did not specify the -r parameter.) When a
machine to which a group task was originally applied registers on the management server, the
corresponding backup policy will become applied to that machine.
3.5 Upgrading Acronis Backup Server to Acronis Backup
& Recovery 10 Storage Node
You can install Acronis Backup & Recovery 10 Storage Node on the same machine as the Acronis
Backup Server, or on a different machine.
If you want to import the backup server's locations as the storage node's centralized vaults, install
the storage node on the same machine.
To install Acronis Backup & Recovery 10 Storage Node
1. Run the Acronis Backup & Recovery 10 setup file.
2. In the list of components to install, select the Storage Node check box. To be able to import the
backup server's locations, select the Upgrade Tool check box.
3. To be able to import the backup server's locations, select to run the storage node service under
the existing account with the administrative privileges. You will have to reinstall the storage node
to change the account after installation.
4. Follow the on-screen instructions. For details, see the "Local installation (Windows)" section in
the Installation Guide.
To import the backup server's locations
1. On the machine where the storage node is installed, log on as a member of the Administrators
2. Change the current folder to the folder where the upgrade tool is installed—by default:
C:\Program Files\Acronis\UpgradeTool
3. If Acronis Backup & Recovery 10 is installed in a folder other than the default folder, change the
path accordingly.
4. Run the following command:
cscript UpgradeTool.vbs BS
Result:
The backup server's backup locations are the storage node's centralized vaults.
If the storage node is registered on the management server, these centralized vaults will appear
on the management server in the Vaults view.
Each centralized vault is named according to the backup location's folder.
Each centralized vault displays all archives currently present in the corresponding backup
location.
3.6 Upgrading Acronis True Image Echo agents and local
versions
3.6.1 Installing agents
To upgrade Acronis True Image Echo agents and local versions, install Acronis Backup & Recovery 10
agents on the machines where the old agents and local versions are installed.
In Windows:
1. Run the Acronis Backup & Recovery 10 setup file.
2. Specify the name or IP address of the Acronis License Server.
3. In the list of components, select the components that you want to install. Select to install Acronis
Backup & Recovery 10 Management Console, along with the agent, if local administration is
required on the machine. To be able to import the old tasks, select the Upgrade Tool check box.
4. Select the Proceed with installation (the previous version of the product will be removed)
check box. Optionally, during installation, you can:
import the old backup and validation tasks of Acronis True Image Echo by selecting the
and event tracing options of Acronis True Image Echo by selecting the Import user settings
to Acronis Backup & Recovery 10 check box.
Otherwise, you can import the tasks and settings later at any time. For details, see "Importing all
tasks at once", "Importing individual tasks" and "Importing old settings" later in this document.
5. Follow the on-screen instructions. For details, see the "Local installation (Windows)" section in
the Installation Guide.
Instead of local installation, you can install Acronis Backup & Recovery 10 agents remotely or by
using Group Policy. For details, see the "Remote installation (Windows)" and "Installing components
using Group Policy" sections in the Installation Guide.
Note: To upgrade an Acronis True Image Echo agent using the console’s remote installation functionality, you
need either Acronis True Image Echo or Acronis Backup & Recovery 10 agent on the machine you operate from.
Otherwise, at least one full or upgrade license must be available (i.e. free) on the license server. This may be a
license for any edition of Acronis True Image Echo or Acronis Backup & Recovery 10. The license will remain
available after the upgrade.
In Linux:
1. Install Acronis Backup & Recovery 10 Agent for Linux and the Upgrade Tool as described in
"Installation procedure" of the Installation Guide.
2. Install Acronis Backup & Recovery 10 Management Console, if local administration is required on
the machine.
Result:
The Acronis True Image Echo agents and local versions are replaced with Acronis Backup &
Recovery 10 components.
3.6.2 Importing all tasks at once
You might want to import the old backup tasks and validation tasks to Acronis Backup & Recovery 10.
If you do not import them, these tasks will no longer run.
Note: The tasks that back up data to Acronis Backup Server or validate archives stored on it will not be imported
to Acronis Backup & Recovery 10.
You can import the old tasks at the time of agent installation (see the installation instructions earlier
in this section), or later by using Acronis Backup & Recovery 10 Upgrade Tool. This command-line
utility is located in the Acronis Backup & Recovery 10 installation directory, in the UpgradeTool
subdirectory.
In Windows:
1. Change the current folder to the folder where the upgrade tool is installed—by default:
C:\Program Files\Acronis\UpgradeTool
2. If Acronis Backup & Recovery 10 is installed in a folder other than the default folder, change the
path accordingly.
3. Run the following command (note capitalization):
cscript UpgradeTool.vbs Agent
In Linux:
1. Change the current directory to: /usr/lib/Acronis/UpgradeTool
2. Run the following command:
UpgradeTool.sh Agent
Result:
Tasks that were present in Acronis True Image Echo are converted to Acronis Backup & Recovery
10 tasks and appear in the Backup plans and tasks view.
Each backup task's schedule, items to back up, and backup destination are the same as before,
but the task will create a new archive to perform further backups.
Each backup task is part of a backup plan. You can edit the backup plan to change the task's
Instead of importing all tasks from Acronis True Image Echo at once, you can use the upgrade tool to
import an individual backup or validation task.
Note: The tasks that back up data to Acronis Backup Server or validate archives stored on it cannot be
imported.
Acronis True Image Echo stores each task as a .tis file. By default, these files are located in the folder
C:\Documents and Settings\All Users\Application Data\Acronis\TrueImage\Scripts.
The names of the .tis files are Universally Unique Identifiers (UUIDs), such as 6AED5F49-7EED-4E3E939E-19360A44137F.tib.tis. Each file has the XML format. The <display> tag in the file specifies the
task name as it appears in the list of tasks.
To import a task
1. Determine the file name of the task that you want to import—for example, by examining the
content of the <display> tag.
2. Change the current folder to the one where the upgrade tool is installed.
3. Run the following command, specifying the task's file name:
cscript UpgradeTool.vbs Script -f "C:\Documents and Settings\All
Users\Application Data\Acronis\TrueImage\Scripts\6AED5F49-7EED-4E3E-939E19360A44137F.tib.tis"
As a result, the task is imported as an Acronis Backup & Recovery 10 task and becomes part of a
backup plan.
3.6.4 Importing old settings
The upgrade tool enables you to import settings of the default backup options, default restoration
options, notification options, and event tracing options of Acronis True Image Echo Agents to the
default backup and recovery options of Acronis Backup & Recovery 10 Agent.
To import the old options (both in Windows and Linux):
1. Change the current folder (directory) to the one where the upgrade tool is installed.
2. In Windows, run the following command:
cscript UpgradeTool.vbs Options
In Linux, run the following command:
./UpgradeTool.sh Options
The old options are imported as follows:
Notifications is imported as Notifications in both Default backup options and Default recovery
options.
Event tracing is imported as Event tracing in both Default backup options and Default recovery
options.
Archive splitting is imported as Backup splitting.
In Media components, if Place Acronis One-Click Restore on media is the only check box
selected, it is imported as Acronis Bootable Agent and One-Click Restore.
Validate backup archive upon its creation completion is not imported from Additional settings
in Default backup options or Default recovery options.
In Default recovery options, Files to exclude from restoration, Files overwriting mode, and
Restore files and folders without restoring full path (in Additional settings) are not imported.
Other options are imported as the corresponding options in Default backup options and Default
recovery options.
4 Sample scenarios
4.1 Scenario 1 - The minimal steps required to start using
the new software
1. Install Acronis License Server.
2. Import the upgrade license key and the license key for Acronis True Image Echo.
3. On a machine with the Acronis True Image Echo agent, install the components called "the
managed machine components" in the installation wizard (actually, the agent and the bootable
components) and the management console.
4. Start the console. You can:
Create bootable media
Back up data to local folders, removable media or a network share
Recover data from the backup archives you create or from archives created with Acronis
True Image Echo, except for the archives located on Acronis Backup Server
Perform disk management operations.
4.2 Scenario 2 - Centralized upgrade
Suppose that your existing backup environment is as follows:
You have Acronis Group Server.
You have machines with Acronis True Image Echo agents.
All the machines back up data according to a group task applied to them by the group server.
The backup destination is different from Acronis Backup Server—for example, a network share.
When upgrading, suppose that you want to:
Preserve the way the upgraded machines back up data—including parameters such as backup
schedule and destination
Retain the ability to modify the backup parameters centrally so that the changes automatically
4. Register the upgraded machines on the management server.
If you imported the old tasks, the backup policy will apply to the registered machines at this point.
5. Apply the backup policy to the machines, by connecting to the management server.
As a result:
The backup policy applies to the machines to which the group task originally applied.
The policy's backup parameters are the same as those of the group task.
If you need to change backup parameters—such as to change the backup destination—edit the
backup policy, and the changes will affect all the machines to which the policy applies.
4.3 Scenario 3 - Gradual upgrade
Assume that 200 Acronis True Image Echo agents, an Acronis Group Server (AGS) and an Acronis
Backup Server (ABS) are installed, all on different machines.
Group tasks are deployed to all the machines. One hundred of them back up data to the backup
server, the remaining 100 back up to a network share.
Existing infrastructure
You decide on upgrading 50 of the agents backing up to the backup server (and change their backup
destination to Acronis Backup & Recovery 10 Storage Node) and 50 of the agents backing up to the
network share.
You will retain archives stored on the backup server and need the ability to recover data from them
with Acronis Backup & Recovery 10.
All the upgraded agents should be managed by Acronis Backup & Recovery 10 Management Server.
Group tasks are to be converted to backup policies, and the local tasks, once generated by the group
tasks, are to be converted to centralized backup plans corresponding to the policies. Locally
originated backup tasks should be converted to local backup plans.
The non-upgraded agents should continue functioning within the Acronis True Image Echo
infrastructure and interact with the group server and the backup server.
Note that this scenario is quite complex. If for example you do not need access to the old archives,
simply skip the corresponding steps in the procedure described below.
Required infrastructure
Steps to perform
1. Upgrade or install Acronis License Server and import upgrade license keys. Echo license keys
need to be present on the license server, otherwise upgrade keys will not be useable.
3. Install Acronis Backup & Recovery 10 Management Server, along with the agent and the upgrade
tool. In our example, the management server is installed separately from the group server.
4. Run the upgrade tool specifying the name and credentials for the machine where the group
server's database (GroupServerEcho.fdb) is located. As a result, group tasks are converted to
backup policies and imported into the management server's database.
5. Install Acronis Backup & Recovery 10 Storage Node, along with the upgrade tool, on the machine
where the backup server resides. When asked by the wizard, choose to run the storage node
under an existing account with administrative privileges. Register the storage node on the
management server, either during installation, or after the installation, on the management
server side.
6. Run the upgrade tool on the machine with the backup server and the storage node. As a result,
the backup server's locations are imported into the storage node as read-only centralized vaults.
7. Install Acronis Backup & Recovery 10 agent, along with the upgrade tool, on the 100 machines
where upgrade is required. As a result, the old agents are replaced with the new agents.
8. Import the tasks that use the network share as a backup destination, into the new agents. This
can be done either during installation by selecting the Import existing tasks check box, or after
the installation, by running the upgrade tool on each of the 50 machines that back up to the
network share.
9. Register all the upgraded machines on the management server. At this point, the policy, resulting
from the group task upgrade in step 4, becomes applied to these machines.
10. Create a vault on the storage node for those 50 machines that were previously backed up to the
backup server.
11. Create a new backup policy, specifying this vault as the backup destination, and apply the policy
to those 50 machines that were previously backed up to the backup server.
Acronis True Image for Microsoft Windows Small
Business Server
Acronis Backup & Recovery 10 Advanced Server SBS
Edition
Upgrading from other Acronis True Image Echo editions, for example, from Acronis True Image Echo
Server for Windows to Acronis Backup & Recovery 10 Advanced Server, is possible with full license
keys.
Is it possible to upgrade from Acronis True Image 9.1?
Yes, but you will have to remove Acronis True Image 9.1 agents before installing Acronis Backup &
Recovery 10 agents. Also, you cannot import tasks and backup server locations from Acronis True
Image 9.1 straight into Acronis Backup & Recovery 10. To be able do this, first upgrade Acronis True
Image 9.1 to Acronis True Image Echo.
Is it possible to upgrade to a different language version of the product?
If the language version of Acronis True Image Echo does not match the language version of Acronis
Backup & Recovery 10, you will have to remove Acronis True Image Echo agents and then install
Acronis Backup & Recovery 10 agents anew using the upgrade license keys.
Is installation of Acronis License Server mandatory?
Yes. The advanced editions of Acronis Backup & Recovery 10 include Acronis License Server that has
to be installed prior to the Echo agents and local versions upgrade.
How to upgrade a local version of Acronis True Image Echo?
Acronis True Image Echo includes components for local management of servers and workstations.
These components are referred to as "local versions" as opposed to agents that enable both local
and remote management. The advanced editions of Acronis Backup & Recovery 10 do not have local
versions. Local versions of Acronis True Image Echo are upgraded to Acronis Backup & Recovery 10
agents. Then you can install Acronis Backup & Recovery 10 Management Console on the machines,
where local administration is required.
What happens when I install Acronis Backup & Recovery 10 components over Acronis True Image
Echo components?
When installed, Acronis Backup & Recovery 10 agent replaces the Acronis True Image Echo agent
residing on the same machine. Acronis License Server updates the previous version of Acronis
License Server. Acronis Backup & Recovery 10 Management Console, Management Server and
Storage Node are installed side by side with the corresponding Echo components. During the
upgrade installation, Acronis services will be restarted and all Acronis tasks related to these services
will be stopped.
Can Acronis Backup Server and Acronis Backup & Recovery 10 Storage Node run on the same
machine?
Yes, these components can work side by side on the same machine. Moreover, only in this case can
you make Acronis Backup Server locations visible in Acronis Backup & Recovery 10 Storage Node.
Can Acronis Group Server and Acronis Backup & Recovery 10 Management Server run on the same
machine?