Release Notes for Recovery Series and Unitrends Backup 10.3.11


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

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

Component   Bug
  • Updated the version requirement message that displays when running /usr/bp/bin/disaster_recovery. The message now reads: If your new appliance is on a version prior to Release 9.1, the utility will not be available, so you will need to upgrade to at least Release 9.1 to restore appliance metadata.
  • Protected Assets > Remove – Fixed an issue where an asset could not be removed if a completed backup copy job containing the asset still displayed on the Active Jobs page. With this fix, the asset can be removed as long as there is no job actively running for the asset.
  • Windows image-level backups – Resolved an issue where backups could fail with the following error due to an offset mismatch: More blocks in the bitmap(nnnnn) than the backup(nnnnn). 
Cold backup
  • Import backup copies from tape – Resolved an issue where the import failed in some cases due to extra padding at the end of the backup copy.
  • Test option for checking available space on media – Resolved an issue where the Test option did not accurately report the amount of available space if the media was not mounted on the appliance.
  • Instant Recovery (IR) of UEFI-based Windows image-level backups to a Unitrends appliance target – Resolved an issue where IR could fail in cases where IR objects for multiple UEFI-based assets were running on the appliance.
  • Windows replica run on a Unitrends appliance – Resolved an issue where a UEFI-based replica could enter the halted state if multiple UEFI-based replicas were running on the appliance.

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