Release Notes for Recovery Series and Unitrends Backup 10.3.6


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

New appliances now run under CentOS 7

Beginning in Release 10.3.6, newly imaged Recovery Series appliances and newly deployed Unitrends Backup appliances run the CentOS 7 operating system. (See the CentOS 7 Release Notes for enhancements and fixes introduced in CentOS 7.)

These new features are included on our CentOS 7 appliances:
  • DHCP support – If you have connected the appliance to your network and DHCP is available, an IP address is automatically assigned to the appliance when you power it on for the first time. (You can opt to manually assign an IP if you prefer or if DHCP is not available on your network). 
    Note: Appliance backup copy target – To use the appliance as a hot backup copy target, you must assign a static IP address. Using a DHCP addressed appliance is not supported.
  • Windows replicas – Windows replicas of UEFI-based assets can reside on the appliance itself.  
Note: Disaster recovery to a CentOS 7 appliance – There is a known issue where performing disaster recovery (DR) of a CentOS 6 appliance to a CentOS 7 appliance target may not recover all job schedules correctly. After performing DR, check your schedules and modify as needed. This issue does not impact Recovery MAX appliances and will be resolved in an upcoming release for all other appliances.

Windows Server 2019

Release 10.3.6 extends Windows support to include file-level and image-level protection of Windows 2019. To protect your Windows 2019 environment:
  • The Unitrends appliance must be running Release 10.3.6 or higher.
  • The Windows asset must be running agent release Release 10.3.6 or higher.
The following Windows Server 2019 features are not yet supported:
  • Nano Servers (this deployment option does not install VSS components, which are required for agent backups)
  • Windows Containers, such as Kubernetes clusters
  • Shielded VMs
  • Storage Spaces Direct
  • Hyper-Converged Infrastructure (HCI) deployments
Note: Hyper-V Server 2019 will be supported in an upcoming release.


Cold backup copy (Recovery MAX Appliances only)

Release 10.3.6 adds cold backup copy support to Recovery MAX appliances. Backups can now be copied from the appliance to cold targets (such as NAS, eSATA, and USB devices) for long term storage. To use the cold backup copy feature, the Recovery MAX appliance must be running Release 10.3.6 or higher. For details, see Backup copy targets in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup.


The table below lists bugs that were resolved in the 10.3.6 releases. Unless stated otherwise, you can resolve each bug by simply upgrading your appliance.
Release 10.3.6-3
Component Bug
Instant Recovery
  • Windows image-level backups – Resolved an issue with instant recovery (IR) to a Recovery Series physical appliance that prevented the IR VM from entering instant recovery mode.
Release 10.3.6-2
Component   Bug
  • Hyper-V backups – Resolved an issue with VM recovery where the VM did not start due to an '.avhdx' does not exist for the VM error. This fix requires an agent upgrade.
  • Hyper-V backups – Resolved a display issue with file level recovery via iSCSI. In the iSCSI Initiator Properties dialog, the Hyper-V VM was present in the list of discovered targets but the VM name was not included in the iqn... string.
Windows Replicas
  • Live and audit modes – Resolved an issue where dynamic disks could be inaccessible upon booting into live or audit mode.
  • SQL database on dynamic disk - Resolved an issue that caused SQL restores to dynamic disk to fail. The SQL failure created an invalid checkpoint that caused subsequent restores of file-level incrementals to also fail.
  • Resolved an issue that caused DR of a CentOS 6 appliance to a CentOS 7 appliance target to fail. (Recovery MAX appliances only)

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