2.3.8 Linux packages ............................................................................................................................................... 20
2.3.9 Compatibility with encryption software ...................................................................................................... 22
2.4 System requirements ...............................................................................................................23
2.5 Supported file systems ............................................................................................................24
2.6.1 Installing the management server ............................................................................................................... 26
2.6.2 Adding machines via the web interface ...................................................................................................... 29
5.2.2 Selecting system state .................................................................................................................................. 57
5.3 Selecting a destination .............................................................................................................60
5.3.1 About Secure Zone ........................................................................................................................................ 62
5.11.3 Backup file name ........................................................................................................................................... 79
5.11.4 Backup format ............................................................................................................................................... 82
5.11.18 Mount points ................................................................................................................................................. 90
6.4.1 Recovering files by using the web interface .............................................................................................. 110
6.4.2 Downloading files from the cloud storage ................................................................................................ 111
6.4.3 Verifying file authenticity with Notary Service.......................................................................................... 112
6.4.4 Signing a file with ASign .............................................................................................................................. 113
6.4.5 Recovering files by using bootable media ................................................................................................. 114
6.4.6 Extracting files from local backups ............................................................................................................. 114
6.5 Recovering system state ........................................................................................................115
6.7.2 Date and time for files ................................................................................................................................ 117
6.7.7 Full path recovery ........................................................................................................................................ 118
6.7.8 Mount points ............................................................................................................................................... 119
6.7.12 VM power management ............................................................................................................................ 121
6.7.13 Windows event log ..................................................................................................................................... 121
7 Operations with backups ............................................................................................. 121
7.1 The Backups tab .....................................................................................................................121
7.2 Mounting volumes from a backup .........................................................................................122
9.1.4 Conversion to a virtual machine ................................................................................................................ 129
10 Bootable media ........................................................................................................... 130
10.1 Bootable Media Builder .........................................................................................................130
10.1.1 Linux-based bootable media ...................................................................................................................... 130
10.1.2 WinPE-based bootable media .................................................................................................................... 141
10.2 Connecting to a machine booted from media .......................................................................144
10.3 Registering media on the management server .....................................................................145
10.4 Configuring iSCSI and NDAS devices ......................................................................................146
10.6.1 Installing Acronis PXE Server ...................................................................................................................... 148
10.6.2 Setting up a machine to boot from PXE .................................................................................................... 149
10.6.3 Work across subnets ................................................................................................................................... 149
11 Protecting mobile devices ............................................................................................ 150
12 Protecting Microsoft applications ................................................................................. 154
12.2.2 Selecting Exchange Server data ................................................................................................................. 157
12.2.3 Protecting Always On Availability Groups (AAG) ...................................................................................... 158
12.2.4 Protecting Database Availability Groups (DAG) ........................................................................................ 159
12.3.1 Required user rights .................................................................................................................................... 161
16.2.3 Using SAN hardware snapshots ................................................................................................................. 187
16.2.4 Using a locally attached storage................................................................................................................. 191
19.1.1 What is a tape device? ................................................................................................................................ 207
19.1.2 Overview of tape support ........................................................................................................................... 208
19.1.3 Getting started with a tape device ............................................................................................................. 212
19.2.4 Deduplication best practices ...................................................................................................................... 227
19.2.5 Data catalog ................................................................................................................................................. 229
19.2.6 Cataloging best practices ............................................................................................................................ 230
20 System settings ............................................................................................................ 230
20.1 Email server ...........................................................................................................................230
21.1.1 Administrators and units ............................................................................................................................ 233
21.1.3 Creating units ............................................................................................................................................... 235
Support for Citrix XenServer 7.0, 7.1, 7.2, and Red Hat Virtualization 4.1 (p. 18)
Support for Debian 8.6, 8.7, 8.8, 9, and Ubuntu 17.04
Support for Windows Storage Server 2016
The capability to use a PostgreSQL database with the management server under Linux (p. 29)
A utility for agent mass deployment and upgrade.
For information about how to use this utility, refer to http://kb.acronis.com/content/60137
1.2 What's new in Acronis Backup 12.5
Important These new features are available in on-premise deployments only. They will be propagated to
cloud deployments in future releases.
New features available in all on-premise deployments
Backup
A new backup format (p. 82) that increases the backup speed and reduces the size of backups
Up to five locations for replication in a backup plan (p. 75)
Conversion to a virtual machine in a backup plan (p. 73)
Schedule by events (p. 66)
Setting conditions for backup plan execution (p. 67)
Predefined Grandfather-Father-Son (GFS) backup scheme (p. 64)
SFTP as a backup location (p. 60)
Default backup options stored on the management server (p. 232)
Selection of the backup method (full or incremental) when starting a backup manually (p. 76)
Backup options:
Email notifications (p. 86):
Specify the email notifications subject
Notifications are now based on alerts instead of backup activity results. You can
customize the list of alerts that trigger a notification.
The capability to assign a virtual machine to a specific agent (p. 192) (VM binding)
Operations with backups
Mounting volumes in the read/write mode (p. 122)
ASign allows a backed-up file to be signed by several people (p. 113)
Notifications and alerts
The capability to configure the severity of an alert (via the configuration file) (p. 201)
Device status is now derived from alerts instead of backup activity results. This covers a wider
range of events, for example, missed backups or ransomware activities.
Acronis Active Protection
Proactive protection from ransomware by detecting suspicious processes (p. 175)
Usability improvements
Dashboard - a customizable set of more than 20 widgets that are updated in real time (p. 198)
A new section in the UI shows all backup plans and other plans (p. 124)
The capability to set an encryption password in Backup Monitor (p. 71)
New features available with the Advanced licenses only
Administering
Customizable reports that can be sent or saved on a schedule (p. 199)
Roles on the management server: create units and assign administrators to them (p. 233)
Group management: built-in and custom groups of devices (p. 202)
Acronis Notary: prove that a file is authentic and unchanged since it was backed up (p. 72)
New backup locations
Acronis Storage Node with deduplication (p. 224)
Support for tape devices (p. 207)
Bootable media
Working with bootable media via the backup console (p. 145)
Automated backup and recovery by execution of a predefined or custom script (p. 133)
PXE Server for network boot (p. 148)
Applications
Support for Database Availability Groups (DAG) in Microsoft Exchange Server (p. 159)
Support for AlwaysOn Availability Group (AAG) in Microsoft SQL Server (p. 158)
Protecting Oracle Database (p. 175)
Virtualization
Backing up ESXi virtual machines from NetApp hardware snapshots (p. 187)
Backing up Citrix XenServer, Red Hat Virtualization (RHV/RHEV), Kernel-based Virtual Machines
(KVM), and Oracle virtual machines (by installing an agent into the guest system) (p. 11)
Operations with backups
Conversion to a virtual machine, validation, replication, and retention of backups can be
performed on a schedule by a dedicated agent (p. 125)
Cataloging - a separate catalog service enables search throughout all backups in managed
locations (p. 229)
2 Installation
2.1 Installation overview
Acronis Backup supports two methods of deployment: on-premise and cloud. The main difference
between them is the location of Acronis Backup Management Server.
Acronis Backup Management Server is the central point for managing all of your backups. With the
on-premise deployment, it is installed in your local network; with the cloud deployment, it is located
in one of the Acronis data centers. The web interface to this server is named a backup console.
Both types of deployment require that a backup agent is installed on each machine that you want to
back up. The supported types of storage are also the same. The cloud storage space is sold separately
from the Acronis Backup licenses.
On-premise deployment
On-premise deployment means that all of the product components are installed in your local
network. This is the only deployment method available with a perpetual license. Also, you have to
use this method if your machines are not connected to the Internet.
Management server location
You can install the management server on a machine running either Windows or Linux.
Installation in Windows is recommended because you will be able to deploy agents to other
machines from the management server. With the Advanced license, it is possible to create
organizational units and add administrators to them. This way, you can delegate backup
management to other people whose access permissions will be strictly limited to the corresponding
units.
Installation in Linux is recommended in a Linux-only environment. You will need to install an agent
locally on the machines that you want to back up.
Cloud deployment
Cloud deployment means that the management server is located in one of the Acronis data centers.
The benefit of this approach is that you do not need to maintain the management server in your local
network. You can think of Acronis Backup as of a backup service provided to you by Acronis.
Access to the account server enables you to create user accounts, set service usage quotas for them,
and create groups of users (units) to reflect the structure of your organization. Every user can access
the backup console, download the required agent, and install it on their machines in minutes.
Administrator accounts can be created at the unit or organization level. Each account has a view
scoped to their area of control. Users have access only to their own backups.
The following table summarizes differences between the on-premise and cloud deployments.
On-premise management server
Unit and account management with the Advanced
license only
Both subscription and perpetual licenses can be used
Agent for VMware (Virtual Appliance) and Agent for
VMware (Windows)
WAN optimization for replication of virtual machines
(replica seeding)
Bootable Media Builder
Backup and disk management in bootable media
Upgrade from previous versions of Acronis Backup,
including Acronis Backup for VMware
Participation in the Acronis Customer Experience
Program
Features introduced in version 12.5, which affects only
on-premise deployments. See "What's new in Acronis
Backup 12.5" (p. 7).
Unit and account management
A subscription license is required
No Agent for VMware (Virtual Appliance)
Mobile backup to cloud
What are you going to
back up?
Which agent to install?
Where to install it?
Agent availability
On-prem
Cloud
Physical machines
Disks, volumes, and files
on physical machines
running Windows
Agent for Windows
On the machine that will be backed up.
+
+
Disks, volumes, and files
on physical machines
running Linux
Agent for Linux
+
+
Disks, volumes, and files
on physical machines
running macOS
Agent for Mac
+
+
Applications
2.2 Components
Agents
Agents are applications that perform data backup, recovery, and other operations on the machines
managed by Acronis Backup.
Choose an agent, depending on what you are going to back up. The following table summarizes the
information, to help you decide.
Note that Agent for Windows is installed along with Agent for Exchange, Agent for SQL, Agent for
Active Directory, and Agent for Oracle. If you install, for example, Agent for SQL, you also will be able
to back up the entire machine where the agent is installed.
On the machine running the Mailbox role
of Microsoft Exchange Server.
If only mailbox backup is required, the
agent can be installed on any Windows
machine that has network access to the
machine running the Client Access role of
Microsoft Exchange Server.
+
+
No
mailbox
backup
Microsoft Office 365
mailboxes
Agent for Office 365
On a Windows machine that is connected
to the Internet.
+
+
Machines running Active
Directory Domain
Services
Agent for Active Directory
On the domain controller.
+
+
Machines running Oracle
Database
Agent for Oracle
On the machine running Oracle Database
+
–
Virtual machines
VMware ESXi virtual
machines
Agent for VMware
(Windows)
On a Windows machine that has network
access to vCenter Server and to the
virtual machine storage.*
+
+
Agent for VMware
(Virtual Appliance)
On the ESXi host.
+
–
Hyper-V virtual
machines
Agent for Hyper-V
On the Hyper-V host.
+
+
Virtual machines hosted
on Windows Azure
The same as for physical
machines**
On the machine that will be backed up.
+
+
Virtual machines hosted
on Amazon EC2
+
+
Citrix XenServer virtual
machines
+***
+
Red Hat Virtualization
(RHV/RHEV) virtual
machines
*If your ESXi uses a SAN attached storage, install the agent on a machine connected to the same SAN. The
Component
Function
Where to install it?
Availability
On-prem
Cloud
Management Server
Manages the agents.
Provides the web
interface to users.
On a machine running Windows or Linux.
+
–
Monitoring Service
Provides the dashboard
and reporting
functionality.
On the machine running the
management server.
+
–
Bootable Media Builder
Creates bootable media.
On a machine running Windows or Linux.
+
–
Backup Monitor
Enables users to monitor
backups outside the web
interface.
On a machine running Windows or
macOS.
+
+
Command-Line Tool
Provides the
command-line interface.
On a machine running Windows or Linux.
+
+
Storage Node
Stores backups. Is
required for cataloging
and deduplication.
On a machine running Windows.
+
–
Catalog Service
Performs cataloging of
backups on storage
nodes.
On a machine running Windows.
+
–
PXE Server
Enables booting machines
into bootable media
through the network.
On a machine running Windows.
+
–
agent will back up the virtual machines directly from the storage rather than via the ESXi host and LAN. For
detailed instructions, refer to "LAN-free backup" (p. 184).
**A virtual machine is considered virtual if it is backed up by an external agent. If an agent is installed in the
guest system, the backup and recovery operations are the same as with a physical machine. Nevertheless, the
machine is counted as virtual when you set quotas for the number of machines in a cloud deployment.
***With an Acronis Backup Advanced Virtual Host license, these virtual machines are considered as virtual (per
host licensing is used). With an Acronis Backup Virtual Host license, these machines are considered as physical
(per machine licensing is used).
Other components
2.3 Software requirements
2.3.1 Supported web browsers
The web interface supports the following web browsers:
Google Chrome 29 or later
Mozilla Firefox 23 or later
Opera 16 or later
Windows Internet Explorer 10 or later
Microsoft Edge 25 or later
Safari 8 or later running in the OS X and iOS operating systems
In other web browsers (including Safari browsers running in other operating systems), the user
interface might be displayed incorrectly or some functions may be unavailable.
2.3.2 Supported operating systems and environments
2.3.2.1 Agents
Agent for Windows
Windows XP Professional SP3 (x86, x64)
Windows Server 2003 SP1/2003 R2 and later – Standard and Enterprise editions (x86, x64)
Windows Small Business Server 2003/2003 R2
Windows Vista – all editions
Windows Server 2008 – Standard, Enterprise, Datacenter, and Web editions (x86, x64)
Windows Small Business Server 2008
Windows 7 – all editions
Windows Server 2008 R2 – Standard, Enterprise, Datacenter, Foundation, and Web editions
Windows MultiPoint Server 2010/2011/2012
Windows Small Business Server 2011 – all editions
Windows 8/8.1 – all editions (x86, x64), except for the Windows RT editions
Windows Server 2012/2012 R2 – all editions
Windows Storage Server 2003/2008/2008 R2/2012/2012 R2/2016
Windows 10 – Home, Pro, Education, Enterprise, and IoT Enterprise editions
Windows Server 2016 – all installation options, except for Nano Server
Agent for SQL, Agent for Exchange (for database backup and application-aware
backup), Agent for Active Directory
Each of these agents can be installed on a machine running any operating system listed
above and a supported version of the respective application.
Agent for Exchange (for mailbox backup)
This agent can be installed on a machine with or without Microsoft Exchange Server.
Windows Server 2008 – Standard, Enterprise, Datacenter, and Web editions (x86, x64)
Windows Small Business Server 2008
Windows 7 – all editions
Windows Server 2008 R2 – Standard, Enterprise, Datacenter, Foundation, and Web editions
Windows MultiPoint Server 2010/2011/2012
Windows Small Business Server 2011 – all editions
Windows 8/8.1 – all editions (x86, x64), except for the Windows RT editions
Windows Server 2012/2012 R2 – all editions
Windows Storage Server 2008/2008 R2/2012/2012 R2
Windows 10 – Home, Pro, Education, and Enterprise editions
Windows Server 2016 – all installation options, except for Nano Server
Agent for Office 365
Windows Server 2008 – Standard, Enterprise, Datacenter, and Web editions (x64 only)
Oracle Linux 5.x, 6.x, 7.0, 7.1, 7.2, 7.3 – both Unbreakable Enterprise Kernel and Red Hat
Compatible Kernel
CloudLinux 5.x, 6.x, 7, 7.1
ClearOS 5.x, 6.x, 7, 7.1
Before installing the product on a system that does not use RPM Package Manager, such as
an Ubuntu system, you need to install this manager manually; for example, by running the
following command (as the root user): apt-get install rpm
Agent for Mac
OS X Mavericks 10.9
OS X Yosemite 10.10
OS X El Capitan 10.11
macOS Sierra 10.12 – Apple File System (APFS) is not supported
Agent for VMware (Virtual Appliance)
This agent is delivered as a virtual appliance for running on an ESXi host.
VMware ESXi 4.1, 5.0, 5.1, 5.5, 6.0, 6.5
Agent for VMware (Windows)
This agent is delivered as a Windows application for running in any operating system listed
above for Agent for Windows with the following exceptions:
Windows Server 2008 R2 – Standard, Enterprise, Datacenter, and Foundation editions
Windows MultiPoint Server 2010/2011/2012
Windows Small Business Server 2011 – all editions
Windows 8/8.1 – all editions (x64 only), except for the Windows RT editions
Windows Server 2012/2012 R2 – all editions
Windows Storage Server 2008/2008 R2/2012/2012 R2/2016
Windows 10 – Home, Pro, Education, and Enterprise editions
Windows Server 2016 – all installation options, except for Nano Server
2.3.3 Supported Microsoft SQL Server versions
Microsoft SQL Server 2016
Microsoft SQL Server 2014
Microsoft SQL Server 2012
Microsoft SQL Server 2008 R2
Microsoft SQL Server 2008
Microsoft SQL Server 2005
2.3.4 Supported Microsoft Exchange Server versions
Microsoft Exchange Server 2016 – all editions.
Microsoft Exchange Server 2013 – all editions, Cumulative Update 1 (CU1) and later.
Microsoft Exchange Server 2010 – all editions, all service packs. Mailbox backup and granular
recovery from database backups are supported starting with Service Pack 1 (SP1).
Microsoft Exchange Server 2007 – all editions, all service packs. Mailbox backup and granular
recovery from database backups are not supported.
2.3.5 Supported Microsoft SharePoint versions
Acronis Backup 12.5 supports the following Microsoft SharePoint versions:
Microsoft SharePoint 2013
Microsoft SharePoint Server 2010 SP1
Microsoft SharePoint Foundation 2010 SP1
Microsoft Office SharePoint Server 2007 SP2*
Microsoft Windows SharePoint Services 3.0 SP2*
*In order to use SharePoint Explorer with these versions, you need a SharePoint recovery farm to attach the
databases to.
The backups or databases from which you extract data must originate from the same SharePoint
version as the one where SharePoint Explorer is installed.
2.3.6 Supported Oracle Database versions
Oracle Database version 11g, all editions
Oracle Database version 12c, all editions.
* In these editions, the HotAdd transport for virtual disks is supported on vSphere 5.0 and later. On version 4.1,
backups may run slower.
** Backup at a hypervisor level is not supported for vSphere Hypervisor because this product restricts access to
Remote Command Line Interface (RCLI) to read-only mode. The agent works during the vSphere Hypervisor
evaluation period while no serial key is entered. Once you enter a serial key, the agent stops functioning.
Limitations
Fault tolerant machines
Agent for VMware backs up a fault tolerant machine only if fault tolerance was enabled in
VMware vSphere 6.0 and later. If you upgraded from an earlier vSphere version, it is enough to
disable and enable fault tolerance for each machine. If you are using an earlier vSphere version,
install an agent in the guest operating system.
Independent disks and RDM
Agent for VMware does not back up Raw Device Mapping (RDM) disks in physical compatibility
mode or independent disks. The agent skips these disks and adds warnings to the log. You can
avoid the warnings by excluding independent disks and RDMs in physical compatibility mode
from the backup plan. If you want to back up these disks or data on these disks, install an agent
in the guest operating system.
Pass-through disks
Agent for Hyper-V does not back up pass-through disks. During backup, the agent skips these
disks and adds warnings to the log. You can avoid the warnings by excluding pass-through disks
from the backup plan. If you want to back up these disks or data on these disks, install an agent
in the guest operating system.
Encrypted virtual machines (introduced in VMware vSphere 6.5)
Encrypted virtual machines are backed up in an unencrypted state. If encryption is critical to
you, enable encryption of backups when creating a backup plan (p. 71).
Recovered virtual machines are always unencrypted. You can manually enable encryption
after the recovery is complete.
If you back up encrypted virtual machines, we recommend that you also encrypt the virtual
machine where Agent for VMware is running. Otherwise, operations with encrypted
machines may be slower than expected. Apply the VM Encryption Policy to the agent's
machine by using vSphere Web Client.
Encrypted virtual machines will be backed up via LAN, even if you configure the SAN
transport mode for the agent. The agent will fall back on the NBD transport because VMware
does not support SAN transport for backing up encrypted virtual disks.
Secure Boot (introduced in VMware vSphere 6.5)
Secure Boot is disabled after a virtual machine is recovered as a new virtual machine. You can
manually enable this option after the recovery is complete.
2.3.8 Linux packages
To add the necessary modules to the Linux kernel, the setup program needs the following Linux
packages:
The package with kernel headers or sources. The package version must match the kernel version.
The GNU Compiler Collection (GCC) compiler system. The GCC version must be the one with
which the kernel was compiled.
The Make tool.
The Perl interpreter.
The names of these packages vary depending on your Linux distribution.
In Red Hat Enterprise Linux, CentOS, and Fedora, the packages normally will be installed by the setup
program. In other distributions, you need to install the packages if they are not installed or do not
have the required versions.
Are the required packages already installed?
To check whether the packages are already installed, perform these steps:
1. Run the following command to find out the kernel version and the required GCC version:
cat /proc/version
This command returns lines similar to the following: Linux version 2.6.35.6 and gcc
version 4.5.1
2. Run the following command to check whether the Make tool and the GCC compiler are installed:
make -v
gcc -v
For gcc, ensure that the version returned by the command is the same as in the gcc version in
step 1. For make, just ensure that the command runs.
3. Check whether the appropriate version of the packages for building kernel modules is installed:
In Red Hat Enterprise Linux, CentOS, and Fedora, run the following command:
In either case, ensure that the package versions are the same as in Linux version in step 1.
4. Run the following command to check whether the Perl interpreter is installed:
perl --version
If you see the information about the Perl version, the interpreter is installed.
Installing the packages from the repository
The following table lists how to install the required packages in various Linux distributions.
The packages will be downloaded from the distribution's repository and installed.
For other Linux distributions, please refer to the distribution's documentation regarding the exact
names of the required packages and the ways to install them.
Installing the packages manually
You may need to install the packages manually if:
The machine does not have an active Red Hat subscription or Internet connection.
The setup program cannot find the kernel-devel or gcc version corresponding to the kernel
version. If the available kernel-devel is more recent than your kernel, you need to either update
the kernel or install the matching kernel-devel version manually.
You have the required packages on the local network and do not want to spend time for
automatic search and downloading.
Obtain the packages from your local network or a trusted third-party website, and install them as
follows:
In Red Hat Enterprise Linux, CentOS, or Fedora, run the following command as the root user:
You can specify all these packages in a single rpm command. Installing any of these packages may
require installing additional packages to resolve dependencies.
2.3.9 Compatibility with encryption software
There are no limitations on backing up and recovering data that is encrypted by file-level encryption
software.
Disk-level encryption software encrypts data on the fly. This is why data contained in the backup is
not encrypted. Disk-level encryption software often modifies system areas: boot records, or partition
tables, or file system tables. These factors affect disk-level backup and recovery, the ability of the
recovered system to boot and access to Secure Zone.
You can back up the data encrypted by the following disk-level encryption software:
Microsoft BitLocker Drive Encryption
McAfee Endpoint Encryption
PGP Whole Disk Encryption.
To ensure reliable disk-level recovery, follow the common rules and software-specific
recommendations.
Common installation rule
The strong recommendation is to install the encryption software before installing the backup agents.
The way of using Secure Zone
Secure Zone must not be encrypted with disk-level encryption. This is the only way to use Secure
Zone:
1. Install the encryption software; then, install the agent.
3. Exclude Secure Zone when encrypting the disk or its volumes.
Components to be installed
Occupied disk space
Minimum memory
consumption
Agent for Windows
850 MB
150 MB
Agent for Windows and one of the following agents:
Agent for SQL
Agent for Exchange
950 MB
170 MB
Agent for Windows and one of the following agents:
Agent for VMware (Windows)
Agent for Hyper-V
1170 MB
180 MB
Agent for Office 365
500 MB
170 MB
Agent for Linux
720 MB
130 MB
Agent for Mac
500 MB
150 MB
For on-premise deployments only
Management Server in Windows
1.7 GB
200 MB
Management Server in Linux
0.6 GB
200 MB
Management Server and Agent for Windows
2.4 GB
360 MB
Common backup rule
You can do a disk-level backup in the operating system. Do not try to back up using bootable media.
Software-specific recovery procedures
Microsoft BitLocker Drive Encryption
To recover a system that was encrypted by BitLocker:
1. Boot from the bootable media.
2. Recover the system. The recovered data will be unencrypted.
3. Reboot the recovered system.
4. Turn on BitLocker.
If you only need to recover one partition of a multi-partitioned disk, do so under the operating
system. Recovery under bootable media may make the recovered partition undetectable for
Windows.
McAfee Endpoint Encryption and PGP Whole Disk Encryption
You can recover an encrypted system partition by using bootable media only.
If the recovered system fails to boot, rebuild Master Boot Record as described in the following
Microsoft knowledge base article: https://support.microsoft.com/kb/2622803
2.4 System requirements
The following table summarizes disk space and memory requirements for typical installation cases.
The installation is performed with the default settings.
Management Server and agents on a machine running
Windows, Microsoft SQL Server, Microsoft Exchange Server, and
Active Directory Domain Services
3.35 GB
400 MB
Management Server and Agent for Linux
1.2 GB
340 MB
Storage Node and Agent for Windows
64-bit platform only
To use deduplication, minimum 8 GB of RAM are required.
For more information, see "Deduplication best practices" (p.
227).
1.1 GB
330 MB
While backing up, an agent typically consumes about 350 MB of memory (measured during a 500-GB
File system
Supported by
Limitations
Agents
Win-PE
bootable
media
Linux-based
bootable media
Mac bootable
media
FAT16/32
All agents
+ + +
No limitations
NTFS+ +
+
ext2/ext3/ext4
+ + -
HFS+
Agent for Mac
- - +
JFS
Agent for Linux
- + -
Files cannot be excluded
from a disk backup
volume backup). The peak consumption may reach 2 GB, depending on the amount and type of data
being processed.
Bootable media or a disk recovery with a reboot requires at least 1 GB of memory.
A management server with one registered machine consumes 200 MB of memory. Each of the newly
registered machines adds about 4 MB. Thus, a server with 100 registered machines consumes
approximately 600 MB above the operating system and running applications. The maximum number
of registered machines is 900-1000. This limitation originates from the management server's
embedded SQLite.
You can overcome this limitation by specifying an external Microsoft SQL Server instance during the
management server installation. With an external SQL database, up to 2000 machines can be
registered without significant performance degradation.
2.5 Supported file systems
A backup agent can back up any file system that is accessible from the operating system where the
agent is installed. For example, Agent for Windows can back up and recover an ext4 file system if the
corresponding driver is installed in Windows.
The following table summarizes the file systems that can be backed up and recovered. The
limitations apply to both the agents and bootable media.
The software automatically switches to the sector-by-sector mode when backing up drives with
unrecognized or unsupported file systems. A sector-by-sector backup is possible for any file system
that:
is block-based
spans a single disk
has a standard MBR/GPT partitioning scheme
If the file system does not meet these requirements, the backup fails.
An on-premise deployment includes a number of software components that are described in the
"Components" (p. 11) section. The diagram below illustrates the component interaction and the
ports required for this interaction. The arrow direction shows which component initiates a
connection.
2.6.1 Installing the management server
2.6.1.1 Installation in Windows
To install the management server
1. Log on as an administrator and start the Acronis Backup setup program.
2. [Optional] To change the language the setup program is displayed in, click Setup language.
3. Accept the terms of the license agreement and select whether the machine will participate in the
4. Leave the default setting Install a backup agent and Acronis Backup Management Server.
5. Do any of the following:
Click Install Acronis Backup.
This is the easiest way to install the product. Most of the installation parameters will be set
to their default values.
The following components will be installed:
Management Server
Monitoring Service
Agent for Windows
Other agents (Agent for Hyper-V, Agent for Exchange, Agent for SQL, and Agent for
Active Directory), if the respective hypervisor or application is detected on the machine
Bootable Media Builder
Command-Line Tool
Backup Monitor
Click Customize installation settings to configure the setup.
You will be able to select the components to be installed and to specify additional
parameters. For details, refer to "Customizing installation settings" (p. 27).
Click Create .mst and .msi files for unattended installation to extract the installation
packages. Review or modify the installation settings that will be added to the .mst file, and
then click Generate. Further steps of this procedure are not required.
If you want to deploy agents through Group Policy, refer to "Deploying agents through Group
Policy" (p. 42).
6. Proceed with the installation.
7. After the installation completes, click Close.
Customizing installation settings
This section describes settings that can be changed during installation.
The components to be installed.
The folder where the product will be installed.
The accounts under which the services will run.
You can choose one of the following:
Use Service User Accounts (default for the agent service)
Service User Accounts are Windows system accounts that are used to run services. The
advantage of this setting is that the domain security policies do not affect these accounts'
user rights. By default, the agent runs under the Local System account.
Create a new account (default for the management server service and the storage node
service)
The account names will be Acronis Agent User, AMS User, and ASN User for the agent,
management server, and the storage node services, respectively.
Use the following account
If you install the product on a domain controller, the setup program prompts you to specify
existing accounts (or the same account) for each service. For security reasons, the setup
program does not automatically create new accounts on a domain controller.
Also, choose this setting if you want the management server to use an existing Microsoft SQL
server installed on a different machine and use Windows Authentication for the SQL Server.
If you chose the Create a new account or Use the following account option, ensure that the
domain security policies do not affect the related accounts' rights. If an account is deprived of
the user rights assigned during the installation, the component may work incorrectly or not work.
Management server installation
The database to be used by the management server.
By default, the built-in SQLite database is used. You can select any edition of Microsoft SQL
Server 2012, Microsoft SQL Server 2014, or Microsoft SQL Server 2016. The instance you choose
can also be used by other programs.
Before selecting an instance installed on another machine, ensure that SQL Server Browser
Service and the TCP/IP protocol are enabled on that machine. For instructions on how to start
SQL Server Browser Service, refer to: http://msdn.microsoft.com/en-us/library/ms189093.aspx.
You can enable the TCP/IP protocol by using a similar procedure.
The port that will be used by a web browser to access the management server (by default, 9877)
and the port that will be used for communication between the product components (by default,
7780). Changing the latter port after the installation will require re-registering of all of the
components.
Windows Firewall is configured automatically during the installation. If you use a different
firewall, ensure that the ports are open for both incoming and outgoing requests through that
firewall.
Whether the agents and other components will access the management server by using its host
name or the IP address.
By default, the host name is specified. You may need to change this setting if DNS is unable to
resolve the host name to the IP address, which results in a component registration failure.
Agent installation
Whether the agent will connect to the Internet through an HTTP proxy server, when backing up
If a proxy server is required, specify its host name or IP address and the port number.
2.6.1.2 Installation in Linux
Preparation
1. Before installing the product on a system that does not use RPM Package Manager, such as an
Ubuntu system, you need to install this manager manually; for example, by running the following
command (as the root user): apt-get install rpm.
2. If you want to install Agent for Linux along with the management server, ensure that the
necessary Linux packages (p. 20) are installed on the machine.
3. Choose the database to be used by the management server.
By default, the built-in SQLite database is used. As an alternative, you can use PostgreSQL. For
information about how to configure the management server for using PostgreSQL, refer to
http://kb.acronis.com/content/60395.
Note If you switch to PostgreSQL after the management server has been working for some time, you will
have to add devices, configure backup plans and other settings from scratch.
Installation
To install the management server
1. As the root user, run the installation file.
2. Accept the terms of the license agreement.
3. [Optional] Select the components that you want to install.
By default, the following components will be installed:
Management Server
Agent for Linux
Bootable Media Builder
4. Specify the port that will be used by a web browser to access the management server. The
default value is 9877.
5. Specify the port that will be used for communication between the product components. The
default value is 7780.
6. Click Next to proceed with the installation.
7. After the installation completes, select Open web console, and then click Exit. The backup
console will open in your default web browser.
2.6.2 Adding machines via the web interface
To start adding a machine to the management server, click All devices > Add.
If the management server is installed in Linux, you will be asked to select the setup program based
on the type of the machine that you want to add. Once the setup program is downloaded, run it
locally on that machine.
The operations described later in this section are possible if the management server is installed in
Windows. In most cases, the agent will be silently deployed to the selected machine.
1.For successful installation on a remote machine running Windows XP, the option Control panel >
Folder options > View > Use simple file sharing must be disabled on that machine.
For successful installation on a remote machine running Windows Vista or later, the option
Control panel>Folder options>View>Use Sharing Wizard must be disabled on that machine.
2. For successful installation on a remote machine that is not a member of an Active Directory
domain, User Account Control (UAC) must be disabled (p. 31).
3. File and Printer Sharing must be enabled on the remote machine. To access this option:
On a machine running Windows XP with Service Pack 2 or Windows 2003 Server: go to
Control panel > Windows Firewall > Exceptions > File and Printer Sharing.
On a machine running Windows Vista, Windows Server 2008, Windows 7, or later: go to
Control panel > Windows Firewall > Network and Sharing Center > Change advanced
sharing settings.
4. Acronis Backup uses TCP ports 445 and 25001 for remote installation. Also, it uses TCP port 9876
for remote installation and for communication between the components.
Port 445 is automatically opened when you enable File and Printer Sharing. Ports 9876 and
25001 are automatically opened through Windows Firewall. If you use a different firewall, make
sure that these three ports are open (added to exceptions) for both incoming and outgoing
requests.
After the remote installation is complete, you can remove ports 445 and 25001 from exceptions.
Port 25001 is automatically closed through Windows Firewall. Port 9876 needs to remain open.
Adding the machine
1. Click All devices > Add.
2. Click Windows or the button that corresponds to the application that you want to protect.
Depending on the button you click, one of the following options is selected:
Agent for Windows
Agent for Hyper-V
Agent for SQL + Agent for Windows
Agent for Exchange + Agent for Windows
If you clicked Microsoft Exchange Server > Exchange mailboxes, and at least one Agent for
Exchange is already registered, you are taken directly to step 5.
Agent for Active Directory + Agent for Windows
Agent for Office 365
3. Specify the host name or IP address of the machine, and the credentials of an account with
administrative privileges on that machine.
4. Click Add.
5. If you clicked Microsoft Exchange Server > Exchange mailboxes in step 2, specify the machine
where the Client Access server role (CAS) of Microsoft Exchange Server is enabled. For more
information, refer to "Mailbox backup" (p. 162).