Ask the Community
Groups
Release Notes for Recovery Series and Unitrends Backup 10.4.6 - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="description"><strong>DESCRIPTION</strong></h2> <p>This document describes enhancements and fixes introduced in the 10.4.3 release. For upgrade instructions and considerations, reference the<a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013187317"> Upgrade Guide for Recovery Series and Unitrends Backup</a>.<br> </p> <h2 data-id="vsphere-7-0"> <br>vSphere 7.0</h2> <br>This release adds host-level support for vSphere 7.0 environments. You can now: <ul><li>Deploy the Unitrends Backup virtual appliance to your vSphere 7.0 environment. For details, see the Deployment Guide for Unitrends Backup on VMware.</li> <li>Protect vSphere 7.0 virtual machines by running host-level backups.</li> </ul> To run host-level backups for VMs hosted in vCenter 7.0 or ESXi 7.0, the following requirements and limitations apply: <ul><li>The Unitrends appliance must be running release 10.4.6.</li> <li>The vCenter must not be configured to use the Server High Availability feature. High Availability is not supported.</li> <li>Hosted VMs must not be configured to use VM encryption. The VM encryption feature and features that require VM encryption (such as virtual TPM) are not supported.</li> <li>Hosted VMs must not be configured to use NVDIMM. NVDIMM devices and controllers are not supported.</li> <li>Hosted VMs must not be configured to use Microsoft Virtualization Based Security (VBS). VBS is not supported.</li> <li>If a vCenter 7.0 VM migrates to a different vCenter, that VM is no longer protected on the original Unitrends schedule. You must manually add it to a new schedule to resume protection.</li> </ul><br>For additional VMware requirements, see VMware virtual machines in the Administrator Guide for Recovery Series,<br>Recovery MAX, and Unitrends Backup.<br><br> <h2 data-id="windows-agent">Windows agent</h2> This release includes updated Windows core and bare metal agents. The 10.4.6 core agent is recommended for all<br>Windows assets and is required for Windows fixes in this release.<br> <table border="1"><tbody><tr><td colspan="1" rowspan="1"><b>IMPORTANT!</b></td> <td colspan="1" rowspan="1">For Windows image-level backups of UEFI systems, backups may auto-promote to a new full after upgrading from a pre-10.4.4 agent if a Microsoft System Partition has the same disk/partition number as another volume.</td> </tr></tbody></table> <h2 data-id="fixes">Fixes</h2> <br>The table below lists fixes included in this release. Unless stated otherwise, you can apply each fix by simply upgrading your appliance. <table border="1"><tbody><tr><th colspan="1" rowspan="1"><b>Component </b></th> <th colspan="1" rowspan="1"><b>Fix</b></th> </tr><tr><td colspan="1" rowspan="1">Cold Backup Copy</td> <td colspan="1" rowspan="1"> <ul><li>Importing copies – Resolved an issue that could cause the import to fail due to insufficient space in the working directory. </li></ul></td> </tr><tr><td colspan="1" rowspan="1">SQL<br> backups</td> <td colspan="1" rowspan="1"> <ul><li>Auto-promotion after a failed differential backup – Resolved an issue where the next backup was not promoted to a full after a differential had failed with this error: SQL Server error 3035 - Cannot perform a differential backup for database <DBname>, because a current database backup does not exist. This fix requires the 10.4.6 Windows agent.</li></ul></td> </tr></tbody></table> </article> </main>