This document describes new features and fixes introduced in the 10.5.3 release. For upgrade instructions and considerations, reference the Upgrade Guide for Recovery Series and Unitrends Backup.
Windows image-level replicas
You can now opt to run Windows image-level replicas on your Recovery Series or Recovery MAX physical appliance. For details, see Windows image-level replicas in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup.
Red Hat 8.x
This release adds support for Red Hat 8.x. To protect Red Hat 8.x, the asset must be running the latest Linux agent.
This release includes updated Windows core and bare metal agents. The 10.5.3 core agent is recommended for all Windows assets.
||Windows image-level backups – After upgrading from a pre-10.4.9 agent, the next backup is automatically promoted to a full.
This release includes updated Linux agents. The latest agent is recommended for all Linux assets and is required to protect Red Hat 8.x assets.
The table below lists fixes included in this release. Unless stated otherwise, you can apply each fix by simply upgrading your appliance.
- Addressed a Linux vulnerability that could result in elevated command line access to the
- Third-party cloud targets (managed by Amazon, AWS, Google, or Rackspace) – Resolved an issue where incompatible storage threshold settings in the backup copy job could result in backups being copied even if the storage threshold had been reached. With this fix, the job fails with this message: Inconsistent 'overwrite' and 'purge' modes state. Please re-create job. If you receive this message:
- Delete the backup copy job.
- Create a new backup copy job.
When the new backup copy job runs, it deletes older copies as needed until the amount of stored
data is less than your storage threshold setting.
- NAS copied assets – Resolved an issue where the backup copy target appliance's LTR could not be applied to NAS copied assets. When attempting to apply LTR retention, the target's LTR policy was not listed in the Retention Policy field in the Edit NAS dialog. Instead, the Retention Policy field contained the LTR of the source backup appliance. With this fix, the LTR of the target appliance displays and can be applied to the NAS copied asset.