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

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

NOTES:

Rebooting the Unitrends appliance is recommended upon upgrading to this release.


VMware 8.0

You can now use host-level backups to protect virtual machines hosted in vCenter 8.0 or ESXi 8.0.

For host-level protection of VMware 8.0 environments, the Unitrends appliance must be running release 10.7.5 or higher. For additional requirements, see VMware virtual machines in the Administrator Guide for Recovery Series, Recovery MAX, ION/ION+, and Unitrends Backup.


Linux agent and support for new Linux versions

This release includes an updated Linux agent. The 10.7.5 agent is required for protection of these newly supported 64-bit Linux versions: Alma Linux 9, Debian 10, CentOS 9, Fedora 35, OpenSUSE 42, RHEL 9, Rocky Linux 9, and Ubuntu 22.04.

 

Automated secure pairing of Unitrends Linux agents

Beginning in Linux agent release 10.7.5, a secure pairing is automatically established between the appliance and the Linux 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.

This feature blocks any communication with Unitrends agent software that doesn't originate from a paired appliance (think of a Bluetooth headset, if it's not paired or in pairing mode, no one else can communicate with it). This eliminates the threat of a rogue appliance running backups or code against an agent.

To use the secure pairing feature, these requirements must be met:

  • The Unitrends appliance must be running release 10.7.5 or higher.
  • The Linux asset must be running agent release 10.7.5 or higher.
  • The Unitrends appliance version must be equal to or higher than the Linux agent version.
IMPORTANT!

Be sure to upgrade your Unitrends appliance before upgrading your Linux agents.

  • Jobs will fail if you attempt to protect a 10.7.5 or higher agent with an appliance that is running an
    older release.
  • You cannot add an asset that is running a 10.7.5 or higher agent to an appliance that is running an
    older release. If you attempt this, you receive an error similar to: Failed to save client: Registration
    for client assetName failed. The Unitrends System could not connect to the Unitrends Agent on
    assetName. Please ensure that the Agent software is installed on assetName, the Agent service is
    running (if applicable), and no firewall settings are preventing access.
IMPORTANT! Do NOT install the 10.7.5 agent on other Linux versions that are not listed below. Instead, locate
your Linux version on the Unitrends Downloads page and install the latest supported agent.

– Alma Linux 9, 64-bit
– CentOS 7, 64-bit
– CentOS 9, 64-bit
– Debian 10, 64-bit
– Fedora 35, 64-bit
– OpenSUSE 42, 64-bit
– Oracle Linux 8.1, 64-bit
– RHEL 7, 64-bit
– RHEL 8.4, 64-bit
– RHEL 9, 64-bit
– Rocky Linux 9
– SLES 11 SP3, 64-bit
– SUSE 15, 64-bit
– Ubuntu 22.04, 64-bit

 

Windows agent

This release includes updated Windows core and bare metal agents. The 10.7.5 core agent is recommended for most 64-bit Windows assets is required for Windows fixes in this release.
Consider the following before upgrading the Windows agent:

NOTES:

For additional agent requirements, see Installing or upgrading the Windows agent in the Upgrade Guide for
Recovery Series, Recovery MAX, ION/ION+, and Unitrends Backup.

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.9 agent release, backups may fail until the pairing completes successfully (this can take up to two hours).
    • To protect Hyper-V clusters, SQL clusters, or file server clusters with the secure agent pairing feature:
      - The cluster must be running agent version 10.6.9 or higher.
      - The Unitrends appliance and cluster must be running in the same time zone.

 

Fixes

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

Component   Fix
Appliance performance
  • Fixed an issue that could result in excessive resource utilization.
Appliance security
  • Disabled an unneeded process that could raise firewall security flags.
Backups
  • Fixed an issue handling Windows mountpoints that could cause synthetic backups to fail.
  • Fixed an issue that caused Windows image-level backups to fail with this error: The backup
    cannot proceed due to an unsupported configuration found in one of the disks configured on
    the system. This fix requires the 10.7.5 Windows agent.
Backup
retention
  • Fixed an issue that could result in a backup being deleted even though it was in the process
    of being imported or migrated during instant recovery.
Windows
agent
  • Fixed an issue where the agent was not installed with all necessary configuration settings in cases where the C:\PCBP directory had been manually removed or renamed prior to installation. This fix requires the 10.7.5 Windows agent.
  • The agent is now called Unitrends Agent when viewing Windows processes and services. This fix requires the 10.7.5 Windows agent.
  • For readability, agent logs no longer include full pathnames. This fix requires the 10.7.5 Windows agent.
Windows
secure agent
pairing
  • Fixed an issue that resulted in excessive CPU utilization on the protected asset. This fix requires the 10.7.5 Windows agent.

 

 

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