Release notes for Acronis Backup & Recovery 11 build 17440
Release date: 25-July-2012 Build: 17440
Acronis continues the trend of expanding the backup and recovery capabilities covering physical, virtual, and cloud environments. Acronis Backup & Recovery 11 build 17440 addresses issues found in the previous builds.
This section describes known issues that have been fixed in Acronis Backup & Recovery 11 build 17440.
After updating Acronis Backup & Recovery 11, the library for an Acronis Storage Node catalog (catalog_item_provider.dll) is not updated because it has no version. This leads to Acronis Storage Node crashes.
Disk-level backup using the Initial Seeding scheme fails with the following errors: "ProtectCommand: Failed to execute the command" and "URI is empty".
Acronis Storage Node crashes during parallel backups of multiple agents (over 20).
When creating a centralized vault, cannot find in the Vault Users window users and groups which use special symbols in their name.
Recovery from a managed vault fails if the vault is being compacted.
After updating Acronis Backup & Recovery 11, backup of some of the virtual machines in a backup plan does not start if the plan is executed by VA.
The contents of the cache folder for catalog files on a virtual appliance (/var/lib/Acronis/BackupAndRecovery/MMS/Catalog/) are not removed after cataloging data backed up to an FTP or SMB network share via this virtual appliance or after browsing this data through the Data view of Acronis Management Console connected to the appliance.
Service_process.exe may hang with high CPU usage on backup tasks' activation when backing up virtual machines' data via Agent for ESX(i) (Windows) during several days of scheduled activity.
A virtual appliance crashes when the log files occupy all the disk space.
The log files are not removed from the /var/lib/Acronis/ServiceProcess/ folder on a virtual appliance according to the Log cleanup rules option. However, the log entries are removed from Acronis Management Console.
This section describes issues that are currently known and provides solutions to avoid the issues.
Installation of Acronis Management Server hangs during SQL Express installation if McAfee SaaS Total Protection is installed and running on the system. Solution: Disable McAfee software during installation.
Remote installation of the Acronis components does not proceed if the Windows installer version on the target systems is lower than 3.1, but the installation wizard reports the installation as successful. Solution: Before starting remote installation, make sure that the target machines have Windows installer version 3.1 or higher.
No error message is shown if adding a license to the license server failed because of insufficient permission.
When upgrading from Acronis Backup & Recovery 10 or Acronis True Image Echo/9.1, you need to specify a full license key for this product along with the upgrade key for Acronis Backup & Recovery 11. With a stand-alone edition, you can specify an upgrade key for the old product instead of the full key.
The "Operation failed: synchronizing with Agent" alert appears on the management server after a machine is successfully registered. Solution: The reason for this is that Acronis Managed Machine Service had not yet started when Acronis Management Server was trying to synchronize with it. The alert can be safely ignored.
A backup finishes with the Warning status instead of Failed if the system does not have enough disk space for creating snapshot. Solution: Pay attention to this warning and make sure there is enough disk space for a snapshot.
A backup plan with the Run now scheme does not start automatically after editing. Solution: It is still possible to start the backup plan manually like a backup plan with any other backup scheme.
Excluding the root of a volume does not work. Solution: Exclude the volume using the Items to back up control.
A postponed backup replication prevents the scheduled start of the next backup. Solution: Make sure that the replication finishes before the next backup is scheduled to start.
Replication/cleanup task fails with the "Cannot find the specified archive" error if the archive is located on an Iomega REV drive. Solution: Do not create backup plans with replication/cleanup options on Iomega REV drives.
Activation of Acronis Startup Recovery Manager fails if the operating system resides on a Dynamic GPT partition.
Acronis Startup Recovery Manager does not load if the system volume is on a dynamic GPT disk. Solution: Boot the machine using Linux-based bootable media.
A system volume recovered to a not original dynamic GPT disk is unbootable. Solution: Convert the destination volume to basic before recovery.
Recovery of the system volume does not start from a running operating system, if the system is located on a dynamic GPT volume.
Acronis WinPE Bootable Media cannot boot on UEFI systems. Solution: Use the default (Linux-based) Acronis Bootable Media on machines with UEFI boot type.
Unable to recover a system volume under WinPE-based bootable media using Acronis Active Restore from a backup located in Acronis Secure Zone. Solution: Perform the recovery using Linux-based bootable media.
Unable to recover a dynamic volume with MBR to the original location under WinPE-based bootable media. Solution: Perform the recovery under Linux-based bootable media.
Recovery of a network folder to the original location fails because of a logon failure. Solution: Specify access credentials for the network folder when creating a recovery task.
The Backups column of the Archive view shows Not available for vaults organized on Acronis Online Backup Storage. Solution: In Acronis Online Backup Storage, the first backup of an archive is always full, the later backups are incremental.
Unable to configure the list of columns in the Log table of activity details (Backup plans and tasks > any backup plan > Details > History > any activity > Details > Log).
If opened files are directly selected for backup and their attributes have not changed since the time of the previous backup, the changes to these files will not be placed in an incremental or differential backup. Solution: When creating or editing the backup plan, select the folder with these files rather than selecting the files directly.
Multiple "Failed to establish connection" error messages in the Acronis Management Server log after performing remote installation. Solution: The reason for this is that Acronis Managed Machine Service had not yet started when Acronis Management Server was trying to synchronize with it. The error messages can be safely ignored.
USB hard drives are added to the source list of a centralized backup plan when the [Fixed volumes] template is used.
You cannot delete a centralized recovery task after the target machine is deleted from the management server.
The cataloging activity is not shown in the backup plan progress and backup plan history if the backup is performed to a managed vault. Solution: Cataloging of a managed vault is performed by Acronis Storage Node. You can monitor the progress of the cataloging in the Current activities view on Acronis Management Server and see its result in the management server log.
Replication to a managed vault on Acronis Backup & Recovery 11 Storage Node Update 0 fails with the "Cannot create archive '' in vault 'arl:/...'." error. Solution: Update the storage node to Acronis Backup & Recovery 11 Storage Node Update 0.5.
Updating Acronis Management Server from build 17318 to 17440 makes all the previously created vaults inaccessible to Acronis Management Console build 17318. Solution: Update Acronis Management Console to build 17440.
Agent for Linux fails to mount backups located in Acronis Secure Zone. Solution: Export backups from Acronis Secure Zone to another local volume and mount the backups.
The Next start time column value does not change for a backup plan with several tasks.
When backing up virtual machines with a Linux operating system and LVM volumes using Agent for ESX(i), those volumes are backed up in the sector-by-sector mode.
Solution: The backed up volumes can be recovered back to the original place without any problem. If you need to migrate the machine to hardware or to a different hypervisor, install Agent for Linux in the guest system and back up the machine as if it were a physical one.
Dynamic disks are recovered as offline by Agent for ESX(i) (Windows) and Agent for ESX(i) (Virtual Appliance). Solution: Turn the disk into the online state using Windows Disk Management.
ESXi5 is unbootable after recovering its volumes by using Linux-based bootable media . Error "Boot Error" appears when booting up. Solution: Recover disks instead of volumes.
When removing Virtual Appliance from an ESX host, virtual disks that were manually attached to it will be deleted along with their content without any warning. Solution: Before removing a Virtual Appliance detach all manually attached disks from it.
The mouse does not work when you access a Hyper-V virtual machine booted into bootable media via Remote Desktop Connection. Solution: Connect Acronis Management Console to the bootable media.
When backing up to an unmanaged vault (except for a locally-attached storage), Agent for ESX(i) (Virtual Appliance) does not perform full cataloging. Solution: If you need a full catalog in an unmanaged vault, back up virtual machines with Agent for ESX(i) (Windows).
If the console is directly connected to an Agent for ESX(i) (Virtual Appliance), the Data view tab is available only for managed vaults and locally attached storages. Solution: Connect the console to the management server and the data view for centralized unmanaged vaults will become available.