This document describes new features and fixes introduced in the 10.5.1 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.|
Windows image-level replicas
Our replicas feature now includes the ability to create standby VM replicas of image-level backups in VMware or Hyper-V, further reducing RTO for those assets. For details, see Windows image-level replicas in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup.
On-box DCA for physical Recovery Series and Recovery Max appliances
You can now run copy data management VMs on your physical Unitrends appliance. On-box DCA jobs run in test mode utilizing the built-in hypervisor to provide scheduled screenshots of your recovered Windows image-level backups. For details, see Copy Data Management in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup.
On-box DCA provides no network capability. You can use the Run Test job mode only to stand up and power on VMs. No other job modes or custom tests are supported. Network capability and application-level testing will be added in an upcoming release.
Wasabi Standard and Wasabi S3
You can now copy backups to your Wasabi cloud environment. For details, see Adding a third-party cloud backup copy target in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup under the Backup copy targets topic.
This release includes updated Windows core and bare metal agents. The 10.5.1 core agent is recommended for all Windows assets and is required for the Window fix in this release.
|IMPORTANT!||Windows image-level backups – After upgrading from a pre-10.4.9 agent, the next backup is automatically promoted to a full.|
This release resolves an issue where certain failed Windows image-level backups could be marked as successful in the appliance UI. This fix requires the 10.5.1 Windows agent.