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

This document describes new features and fixes introduced in the 10.4.10 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.


Ubuntu 18 and 20 LTS

This release adds support for Ubuntu 18 and Ubuntu 20 LTS. To protect these environments, the Unitrends  appliance must be running release 10.4.10 and the asset must be running the latest Linux agent.


Linux agent

This release includes updated Linux agents. The latest agent is recommended for all Linux assets and is required to protect Ubuntu 18 and 20 LTS.

Windows agent

This release includes updated Windows core and bare metal agents. The 10.4.10 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
  • Windows image-level backups of UEFI assets – Resolved a mapping issue that could cause partitions to be excluded from the backup. This fix requires the 10.4.10 Windows agent.
  • Linux backups with exclusions – Resolved an issue where extensive output from exclusions could cause the backup to fail. This fix requires the latest Linux agent.
  • The Feedback feature has been fixed. You can now select ? > Feedback to submit comments to Unitrends.



Hot backup
  • Resolved an issue where hot backup copy jobs could fail if the target appliance had been configured originally as a source backup appliance. With this fix, backup copies run successfully in cases where the appliance role has been changed from source to target.
  • Import an Exchange hot backup copy – Resolved an issue where the import could fail if another backup in the group had already been imported.

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