/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Unitrends General

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

This document describes new features and fixes introduced in the 10.7.4 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.

Nutanix AHV 6.5 – This release adds support for Nutanix AHV hypervisor version 6.5. You can now:

Deploy a Unitrends Backup virtual appliance to AHV 6.5.
Protect virtual machines that reside on an AHV 6.5 hypervisor by running host-level backups.

Windows agent

This release includes updated Windows core and bare metal agents. The 10.7.4 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:

NOTE:

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 updates	Fixed an issue that could cause upgrades via FTP to fail. Fixed an issue where upgrading or rebooting the appliance could reset the maximum number of database connections to the default value.
On-appliance recovery networking	Fixed an issue with Windows instant recovery and replica VMs that reside on physical Unitrends appliances. The VM could have no network connectivity upon entering live mode.
Recovery assurance	Fixed an issue that could cause on-box DCA jobs to fail on Gen 9 MAXS appliances.
Windows agent	For agent updates, streamlined the install process by excluding a component that has already been installed.
Windows and VM replicas	For replicas residing on ESXi hosts, operations will now be retried if Unitrends cannot contact the host, rather than failing on the first try.
Windows secure agent pairing	Fixed an issue that created many log files on the Windows asset. This fix requires the 10.7.4 Windows agent.