Release Notes for Recovery Series, Recovery Max, and Unitrends Backup 10.4.11

This document describes new features and fixes introduced in the 10.4.11 release. For upgrade instructions and considerations, reference the Upgrade Guide for Recovery Series and Unitrends Backup.

NOTE: To upgrade the appliance from version 10.2 or earlier, additional steps are required. For details, see Upgrade fails when upgrading from version 10.2 or older.


Windows agent

This release includes updated Windows core and bare metal agents. The 10.4.11 core agent is recommended for all Windows assets and is required for Windows fixes in this release.


IMPORTANT! Windows image-level backups – After upgrading to the 10.4.9 agent, the next backup is automatically promoted to a full.



The table below lists fixes included in this release. Unless stated otherwise, you can apply each fix by simply upgrading your appliance.

Component   Fix
Add Asset 
  • Add Windows 2003 asset – Resolved an issue where the appliance could not connect to the asset's agent. (This issue was seen in agent versions 10.4.8 and later.) When attempting to add the asset, this error displayed: Failed to save client. Registration for client has failed. This fix requires the 10.4.11 Windows agent.
  • Backup of Windows 2003 assets – Resolved an issue where the appliance could not connect to the asset's agent, causing backups to fail. (This issue was seen in agent versions 10.4.8 and later.) This fix requires the 10.4.11 Windows agent. 
  • Incremental backups of NAS CIFS and NFS assets – Resolved an issue where incremental backups could include data that had not changed since the last backup. With this fix, only changed data is included in incrementals.
NOTE: This issue was seen in NAS incremental schedules that were created on 10.4.10 appliances only. To fix this issue in these jobs, you must upgrade the appliance to 10.4.11, then delete and recreate the NAS incremental schedule.
  • NAS backups – Resolved an issue where job log files were not being purged, decreasing the amount of space available for backup storage.
  • Recovering files directly from a hot backup copy – Resolved an issue where the IP of the target appliance was not being identified correctly in some cases, causing recovery to fail. Example failure messages: 
    – The files have been placed in the downloads location but the link is unavailable.
    – Download facility temporarily unavailable.
  • Importing a host-level hot backup copy of a virtual machine – Resolved an issue where the import could fail if the virtual machine's UUID/GUID did not match the UUID/GUID in the backup copy. 
  • Recovering an AHV virtual machine from a backup that was run with exclusions (disks were excluded from the backup) – Resolved a mapping issue that could prevent non-critical disks from being recovered. 

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section