Release Notes for Recovery Series and Unitrends Backup 10.3.7


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

The table below lists bugs that were resolved in this release. Unless stated otherwise, you can resolve each bug by simply upgrading your appliance.


Component   Bug
  • eSATA backup copy target (single disk and multi-drive Recovery Archive) – Resolved an issue where preparing drives failed with an unknown device type error.
  • Import from tape backup copy target – Resolved an issue where the import failed with this error: Failed to read from backup file.
Hot Backup
  • Import NDMP backup – Resolved an issue where hot copies of NDMP backups were imported with warnings and could not be recovered.
  • Windows image-level backups – Resolved an issue with instant recovery to a Recovery Series or Recovery MAX appliance where recovery would fail if any disk in the backup was larger than 2 TB.
  • Windows image-level backups – For instant recovery (IR) to a Recovery Series or Recovery MAX appliance, a more robust available memory check has been implemented to ensure adequate memory is available for the recovery. If not, the following message now displays in the UI when attempting the IR: Image Instant recovery failed: Insufficient resources to start the VM recovery instance.
  • Hyper-V backups – Improved error handling in file level recovery and instant recovery operations for cases where corrupted data is encountered.
  • Resolved an issue where the appliance could no longer detect clustered instances that had moved to another cluster node.
  • Audit mode and dynamic disks– Resolved an issue where a replica's dynamic disks could become unmounted upon exiting audit mode and returning to restore mode. Subsequent restores would appear to run successfully, but data that would have been restored to a dynamic disk was either skipped or restored to another non-dynamic disk. This could lead to a range of undesireable results (e.g., the replica could contain inaccurate data or enter the halted state).

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