This document describes enhancements and fixes introduced in the 10.4.2 release. For upgrade instructions and considerations, reference the Upgrade Guide for Recovery Series and Unitrends Backup.
- Intercom – This new feature provides enhanced real-time messaging around releases, security notices, upcoming events, and new features.
- Windows agent – This release includes updated Windows core and bare metal agents. The 10.4.2 core agent is recommended for all Windows assets and is required for Windows fixes in this release.
The table below lists fixes included in this release. Unless stated otherwise, you can apply each fix by simply upgrading your appliance.
|Cold Backup Copy||
- Import backup copies – Resolved an issue where the import failed with the error Failed to decompress archive data if the copy was created with the enableThreading=0 setting. If you are using the enableThreading=0 setting, run new full backup copies after upgrading to release 10.4.2.
- Fixed an issue where upgrading to release 10.4.2 prevented certain backup copies that were queued before the upgrade from being copied to the target (these copies remained stuck in the queue). With this fix, any copies that were in the queue before the upgrade are copied as expected after upgrading the appliance.
- Fixed a log rotation issue that caused a system partition to run out of space, which stopped various appliance services.
- Fixed an issue with editing the network adapter on CentOS 7 appliances running version 10.4.1. On the Edit Network Adapter page, the Choose Adapter Type drop-down contained no values and could not be modified. With this fix, the drop-down now contains these values and can be modified as needed: DHCP, Static, and Off.
- Windows replicas – Fixed an issue where the replica could enter the Halted state due to an out of space condition caused by applying new files to the replica before removing deleted files. With this fix, deleted files are removed before applying new files.
- Windows UEFI replicas – Fixed a boot order issue that could cause the replica VM to boot into live mode rather than entering restore mode.
- Hyper-V instant recovery (IR) – Fixed a protocol issue that caused instant recovery to fail with this error in the Windows event log: Remote share does not support resiliency.