Release notes for Acronis Backup & Recovery 11 build 17438 Release date: 5-June-2012 Build: 17438 Overview Acronis continues the trend of expanding the backup and recovery capabilities covering physical, virtual, and cloud environments. Acronis Backup & Recovery 11 build 17438 addresses issues found in Update 0.5. Fixed issues This section describes known issues that have been fixed in Acronis Backup & Recovery 11 build 17438. Installation Acronis Management Server fails to start after installation on Windows Server 2003. The error in the Windows Event Logs: "Failure Audit: Login failed for user 'AMS User'. [CLIENT: ]". Installation of Acronis Management Server fails with the "Windows NT user or group 'localhost\AMS User' not found. Check the name again." error if the existing local SQL server and Acronis Management Server Service account are specified for the operational and/or reporting server during installation. Acronis Storage Node Service hangs in the "Stopping" state after updating Acronis Backup & Recovery 11 Update 0 to Update 0.5 in Windows 2008. Cannot connect to a management server or a managed machine if Acronis Backup & Recovery 11 RTM was updated to Update 0 and then to Update 0.5 and the PXE server was installed. Acronis Management Machine Service and Acronis Managed Machine Service crash and are automatically restarted when the product is updating. This leads to an incorrect behavior of the installer. Acronis Managed Machine Service does not start after updating Acronis Backup & Recovery 11 to Update 0.5 because some logs have become corrupted. The '.Meta' folder is removed during Acronis Storage Node uninstallation. After reinstalling Acronis Storage Node, all of its vaults become unavailable to Acronis Management Server. License binding does not work when installing Agent for Linux on an ESX virtual machine and specifying the license server during the installation. Local Management File-level backup does not include NFS mount points. Backup to a folder which has a name that contains reserved symbols fails. For example, backup to folder 'name#3' goes as follows: The TIB file is placed in a new folder named 'name' and the XML file is placed in folder 'name#3' and the task fails. Backup to a centralized managed vault finishes with the "Failed to find the URI of the last backup." error if the Disaster recovery plan (DRP) option is enabled. The archive is created and the log contains no errors. Incremental backup to an Initial Seeding backup which is split into three or more parts fails with the "The base full backup cannot be found." error. Archive comments are not shown in the Archive view if the archive was created using the Back up now feature. The operating system does not boot after recovery if it was upgraded from Windows XP to Vista/7 in the backup archive. Cannot remove backup data from catalog databases created with Acronis Backup & Recovery 11 RTM/Update 0. Re-attempts are needed when a Network Attached Storage (NAS) returns the "Resource temporarily unavailable" error during backup. Recovery of an incremental backup of an archive on an RDX storage (in the Removable media mode) fails if the full backup of this archive is located on another RDX storage. Recovery of an incremental file backup on an RDX storage to the original location fails with the "Process 'service_process.exe' has failed." error. Connection to a SilverSHielD SFTP server hangs. Comments for a backup are absent in the Archive view if the archive was created in a bootable media. A bootable media fails to boot from a flash drive on DELL machines. Centralized Management Recovery, compacting and backup operations block each other if they are performed simultaneously. An agent does not notify Acronis Management Server that the IP address of the agent has been changed until Acronis Managed Machine Service is restarted. When an agent is deleted from Acronis Management Server, the agent's centralized recovery tasks are not deleted from Acronis Management Server. Acronis Storage Node Service endlessly writes the same error to the log if the service cannot preallocate enough free space for the indexing activity. The log size increases rapidly. Cannot export the Acronis Management Server log to an XML file correctly. Acronis Management Server starts for a long time (>5 mins) after a month of work. After updating Acronis Backup & Recovery 11 to Update 0.5, Acronis Management Server crashes sporadically because of a stack overflow error. Acronis Storage Node Service does not progressively pre-allocate free space for data store and temporary files on NTFS vaults. Cannot explore a centralized unmanaged vault on a NAS storage or re-enter credentials to access the vault. Slow indexing of a deduplicating vault with encryption. Tapes A tape is not moved from the Free pool to the Acronis pool after backing up to this tape. Old media becomes offline and new media appears after every inventorying of a stand-alone tape drive even if a new media has not been inserted. When browsing the contents of a tape-based vault, some of the data is read directly from the tape if all of the required catalog files are not available. Replication to a tape-based vault hangs if no tape is available and the silent mode is enabled in the backup plan. A backup plan works with tapes from the Acronis pool only even if a tape is located in another pool. Deleting a backup using retention rules leads to inconsistency of the tape management database and the storage node's database. Not all cache files are available for reading if their total count exceeds 2000. The HP LTO Ultrium-3 tape drive is not detected after updating Acronis Backup & Recovery 11 to Update 0.5. Linux Disk recovery fails with the "TOL: Process 'service_process.exe' has failed." error. Mounting of a disk backup does not work in OpenSUSE. Recovering a machine that uses GRUB 1.5 to a virtual machine on an ESXi 4.1 by using bootable media makes the virtual machine unbootable (reproduces on CentOS). Some Debian machines become unbootable after recovery. Virtualization ESXi 4.1 becomes unbootable after recovering the SSD disk where it is located via Linux-based bootable media. The "Boot Error" appears on ESXi boot. Deletion of virtual appliances from Acronis Management Server hangs on 33%. The New virtual machine option is not available as a recovery target on the Recover data sheet in the standalone version of Acronis Backup & Recovery 11 Update 0.5. Known issues This section describes issues that are currently known and provides solutions to avoid the issues. Installation 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. Local management 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. Centralized management 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 17437 makes all the previously created vaults inaccessible to Acronis Management Console build 17318. Solution: Update Acronis Management Console to build 17437. Linux 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. Virtualization 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.