With Update 5, the Acronis flagship backup product offers enhancements and addresses issues found in the previous releases.
What's new in Acronis Backup
The cataloging performance is improved.
Acronis Active Restore now works faster, by using a Read-Only Memory cache, and supports Windows 8/8.1 and Windows Server 2012/2012R2.
Fixed issues
This section describes issues that have been fixed in Acronis Backup.
Installation
[ABR-59278] Agent for Hyper-V is not installed during remote installation of Acronis Backup components.
Local management
[OBC-73] Backup of a network share in the silent mode, to the cloud storage, fails if a file or a directory is deleted from the share during the process.
[ABR-40471] When exporting a backup, the progress in the Details window of the activity works incorrectly.
[ABR-58717] The backup export command does not support the --silent_mode parameter.
Centralized management
[ABR-58959] Deletion of an incremental single-pass backup from a managed centralized tape-based vault fails. The following error appears: "Internal error: Failed to open the service directory of the location."
[ABR-57658] Centralized unmanaged vaults on a DFS share become inaccessible after updating Acronis Backup components.
[ABR-57789] A managed centralized vault becomes inaccessible if a file is manually placed in the .meta folder of the vault.
Applications
[APPS-1729] Single-pass backup of a Microsoft SQL Server database fails if the database files were removed from a user-defined filegroup.
[ABR-57926] Validation of a Microsoft Exchange database backup on a deduplicating vault may fail. The following error appears: "Failed to find the requested checksums in the deduplication database."
Known issues
This section describes issues that are currently known and provides solutions to avoid the issues where possible.
Installation
[ABR-25735] When installing Acronis Backup, license keys are requested one-by-one from the license server. This may cause a significant delay if the server is connected remotely.
[ABR-33952] Cannot remotely upgrade Acronis Backup & Recovery 11 Agent for Linux if the upgrade license is added to the license server but the full Acronis Backup & Recovery 11 license is not.
[ABR-40749] In some cases, Acronis Backup installation freezes on Windows Server 2012 R2.
Local management
There is no agentless single-pass disk and application backup of virtual machines (the Microsoft SQL metadata is not cataloged).
Solution: Such VMs should be backed up as physical ones. To do so, the required agents need to be installed into the guest OS.
[ABR-20686] Backup finishes with the "Succeeded with warnings" result if it is manually stopped or canceled. The result should be "Stopped".
[ABR-32785] Acronis Backup Management Console displays a disk number instead of a storage space name in the Archive view tab, the Backup Content window, and the Disk management view.
[ABR-31544] No warnings in the log after recovery of files to a ReFS volume if the files have a compressed attribute. Such files are not supported.
[ABR-31547] Recovery of files to a ReFS volume fails if the files have an encrypted attribute.
[ABR-32851] It is impossible to browse and back up volumes on dynamic disks that have a sector size of 4 KB (known as dynamic Advanced Format disks).
[ABR-31348] In Windows 8/Windows Server 2012: Disks that are made members of a storage pool disappear from Acronis Backup Management Console only after restarting Agent for Windows to which Acronis Backup Management Console is connected.
[ABR-32573] The "E00060106: Failed to save data of backup being edited" error appears when mounting a ReFS volume from a disk backup in the Read only access mode.
Solution: Click Ignore.
[ABR-31884] The Backup and Recover items are not disabled in the Windows context menu if only Acronis Backup Agent for Exchange is installed on the machine. The Recover item is also not disabled in the Windows context menu if an Exchange backup is selected in the system.
[ABR-30600] The Wake-on-LAN functionality does not work in Windows 8/Windows Server 2012.
[ABR-35418] A backup of a large amount of data under Linux-based bootable media with the Linux-style volume representation fails if the destination folder name contains a space character.
[ABR-34769] If Acronis Backup is installed in a folder whose name contains non-Latin characters (for example, Cyrillic), backups fail.
[ABR-34665] If Acronis Backup is installed in a folder whose name contains non-Latin characters (for example, Kanji), generating a disaster recovery plan fails.
[ABR-34269] Under bootable media based on WinPE 4.0, the Disk Management view must be absent.
[ABR-32792] Under bootable media, an unclear error message "The file is read-only" is shown while trying to create a folder on a ReFS volume during the recovery task setup.
[ABR-32106] When backing up a volume that contains an SQL database in the single-user mode and in use, the backup fails. The error is "Failed to start creating the volume snapshot."
[ABR-28582] During a recovery from a backup stored on FTP, a Linux-based bootable media reboots if the machine has less than 724 MB of RAM.
Centralized management
[ABR-27698] The When there is insufficient space while backing up setting for the Clean up archive parameter within the Custom backup scheme does not work if an archive is stored in a managed vault.
[ABR-29591] Storage node settings changed in the Windows registry are not applied until the storage node service restart.
Virtualization
[ABR-32176] Recovery of a virtual machine that has 4096-byte sector VHDX disks successfully completes with warnings and the log contains multiple "Failed to detect GRUB activator. An invalid sector size" errors.
[ABRXII-3548] Acronis Backup Command-Line Tool fails to back up individual disks or volumes of a virtual machine by using Acronis Management Server Service (--service=ams).
Solution: Back up the entire virtual machine instead (do not specify the --disk or --volume parameters).
[ABR-38392] Letters of dynamic volumes of virtual machines are shown incorrectly in the Data to Back Up window.
[ABR-38395] Letters of volumes A and B of virtual machines are shown incorrectly in the Data to Back Up window.