Creating backups from MS Exchange using the Acronis Exchange Agent causes log entries in PowerShell. This can be solved by deleting the PowerShell subkey under Event Log in Windows Registry.

Upgrade to Microsoft Exchange 2010 SP1 can corrupt Windows PowerShell. However, PowerShell is required for Acronis Backup to work with Microsoft Exchange 2010 correctly. Use the instructions from the external sources provided in this article to repair Windows PowerShell.

When creating an application-aware backup, you need to specify a guest OS user from Administrators group.

If the guest OS user that you specify is not built-in Administrator, then the following changes must be applied in the guest OS so that this user can be used for application protection in Acronis Backup.

Otherwise, you will see one of these errors:

The specified user does not have enough rights to create an application-aware backup. User Account Control is enabled in the guest system and this user is not a built-in administrator.


You are backing up an entire machine with the Application-aware backup option enabled. You have selected SQL, Exchange, or both.

After some time, you change the password for the user that has been specified during activation of the feature.

The backup starts failing with the following error message:

Logging on with the specified credentials is impossible, probably because the account does not exist or the password is invalid.

You have a backup plan of Microsoft SQL or Microsoft Exchange databases or mailboxes.

Later, you have revoked and reapplied application backup quota from this machine or have changed tenant licensing model.

Now these backup plans do not run on schedule, while other backup plans still run as scheduled.

If the database backup is stored in a managed vault, copy the necessary libraries from a machine with Microsoft Exchange Server to the storage node that manages this vault. If the database backup is stored in a centralized unmanaged vault, copy them to the management server. The version of Microsoft Exchange Server on the machine must be the same as the version of Microsoft Exchange Server, the data of which is backed up


The recovery of an Exchange database to original location fails with:

Error code: 254
Module: 91
LineInfo: 0x7A0C574AD2E3F5C3
Fields: {"$module":"arx_agent_fork_vsa64_12960"}
Message: It is not allowed to overwrite database <database> during recovery.


The This database can be overwritten by a restore option for this Exchange database is disabled. This is the embedded protection of Microsoft Exchange Server from accidental overwriting of its databases.

Table of trial limitations of Acronis products

By default, during an operation, Acronis Cyber Backup will save its temporary files to the \ProgramData\Acronis\Temp folder on the machine where Acronis Agent for Exchange is installed (during backup), or either on the Agent machine or Acronis Management Server machine (during browsing of backups and restore).

You may want to change this if the capacity of the disk with the ProgramData folder on the affected machine (Agent or AMS) is an issue.

How to troubleshoot issues with mailbox backup


A mailbox is a part of mailbox database that is a unit of granularity where mailboxes are created and stored. A mailbox database is stored as an Exchange database (.edb) file mostly on a separate mailbox server. A mailbox contains items like user's folders, calendar, meetings, attachments and etc.