Release Notes for Recovery Series, Recovery Max, ION/ION+, and Unitrends Backup 10.6.8

This document describes new features and fixes introduced in the 10.6.8 release. For upgrade instructions and considerations, reference the Upgrade Guide for Recovery Series, Recovery MAX, ION/ION+, and Unitrends Backup.



Windows agents

This release includes updated Windows core and bare metal agents. The 10.6.8 core agent is recommended for most Windows assets and is required for Windows fixes in this release.

Consider the following before upgrading the Windows agent:

  • Secure agent pairing – Beginning in Windows agent release 10.6.6, a secure pairing is automatically established between the appliance and the Windows agent on each of its protected assets. This pairing enables Transport Layer Security (TLS) to encrypt data and authenticate connections between appliances and agents. Communication between appliances and agents is only allowed if there is a matching (paired) certificate.
    • If upgrading from a pre-10.6.6 agent release, backups may fail until the pairing completes successfully (this can take up to two hours).
    • The secure agent pairing feature is not used to protect these clustered configurations: Hyper-V clusters, SQL clusters, and file server clusters. To protect these clusters, install agent version 10.6.7. The 10.6.7+ agent detects the cluster and disables secure agent pairing.
    • For additional requirements, see Installing or upgrading the Windows agent in the Upgrade Guide for Recovery Series, Recovery MAX, ION/ION+, and Unitrends Backup.
  • Image-level backups – If upgrading from a pre-10.6.3 agent release, the asset's next Windows image-level backup is promoted to a full.
  • The Windows agent does not require rebooting after updating as of version 10.6.1. A reboot is required if you upgrade from an agent before 10.6.1.



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

Component   Fix
Adding a third-party cloud target for cold backup copy
  • Fixed an issue found in some environments that prevented users from adding a third-party cloud backup copy target. This error would display upon clicking Save in the Add Cloud Backup Copy Target dialog: cloud configuration error: Error response from daemon: no such id: cldadm
Appliance database
  • Fixed a database maintenance issue found in some environments that could cause the database to run low on available space, impacting appliance performance.
  • Nutanix AHV host-level backups – Fixed an issue where AHV backups failed if the AHV host cluster was configured with a fully qualified domain name (FQDN).
  • VMware host-level backups – Fixed an issue that could cause VMware backups to hang, which consumed additional CPU and memory resources on the VMware virtual host.
Windows secure agent pairing
  • Fixed an issue where secure agent pairing failed with the error SSL_accept failed in some



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