11.1.1-2 – July 30, 2026

NOTE  This release contains a kernel update that requires a reboot of your Unitrends appliance.
Wait for the reboot notice, then follow these steps to reboot.

New features

VMware vSphere 9 support

Unitrends now supports backup and recovery of virtual machines running on VMware vSphere 9 (vCenter 9 / ESXi 9).
You can protect vSphere 9 environments using the same workflows and functionality available for earlier VMware versions.
For requirements and limitations, see Additional VMware requirements.
To deploy a Unitrends Backup appliance to ESXi 9.0, see the Deployment Guide for Unitrends Backup on VMware.

Enhancements

Gen 8 appliance migration now available for all devices

All remaining Generation 8 appliances with software RAID can now migrate to Alma 9.
The migration option is available for these devices in the appliance management interface.
For the migration procedure, see CentOS 7 Upgrade to AlmaLinux 9.

Cold copy: retention settings behavior clarified

When configuring cold copy schedules, the UI now prevents retention period settings from being applied unless the overwrite or delete older backups option is also selected.
Helper text explains why this requirement exists.
If you have existing cold copy schedules, review your retention settings when next editing those schedules.
For descriptions of these settings, see Backup copy job settings.
To review an existing schedule, see To view or edit a backup copy job.

Corrupted incremental VMware backups are now flagged with a warning

Previously completed VMware incremental backups that may contain corrupted data are now marked with a warning status rather than shown as successful.
This gives you earlier visibility into potential data integrity issues before they affect recovery.
To review a backup's status, see To view details of a recent job.

Upgrade of base OS packages to AlmaLinux 9.8

These updates improve the security posture of Unitrends.
The appliance picks up the upstream kernel and system library fixes with no separate migration step.
Because the kernel is updated, a one-time reboot is required to complete the update.

Fixes

• Hyper-V backups no longer cause an OS fault and host reboot due to a null pointer dereference in the Changed Block Tracking (CBT) driver.
  The driver has been updated to handle high-concurrency backup loads without triggering a crash.
  For details, see Hyper-V virtual machines.
• File-level restore (FLR) now works correctly for VMware backups.
  The CIFS path now appears in the FLR details view, and Browse and Download actions complete successfully.
  For details, see Windows file-level recovery.
• FLR downloads no longer fail when a file or folder name contains an apostrophe (']).
  Files and folders with special characters in their names can now be downloaded without error.
• Restoring a file that resides in a folder whose name contains a backquote (`]) no longer returns an invalid filename error.
  Image-level index and VMware VM backups are both affected by this fix.
• SQL Server backups no longer fail for databases whose names contain a single quote (']).
  Inventory sync also now correctly lists these databases after the fix. For details, see SQL backup requirements and considerations.
• Backups of virtual machines hosted on ESXi 9.0 no longer fail with a "server refused connection" error.
  VMware 9 environments now connect and complete backups as expected.
• DCA jobs configured with Re-IP no longer fail with a "network adapter not found" error.
  The fix correctly handles IR VMs in audit mode that do not have a connected network adapter at the time the Re-IP operation runs.
  For details, see Recovery assurance procedures.
• After a successful VMware replica restore, the Go Live and Audit buttons are now enabled as expected, so you no longer need to manually power on restored VMs directly on the ESXi host to proceed.
  For details, see Bringing the VM replica live in production.
• Image-level backups replicated to a long-term retention (LTR) target now correctly apply the Grandfather-Father-Son (GFS) retention policy to both the image-level and file-level instances.
  Previously, the file-level instance was silently skipped, causing that instance's retention to go unenforced.
• Instance-level encryption can now be enabled after appliance-level encryption has already been configured.
  Previously, enabling appliance-level encryption first prevented users from subsequently enabling instance-level encryption through the UI.
  For details, see Encryption.
• Changing an appliance's hostname now correctly updates the Fully Qualified Domain Name (FQDN) field.
  Previously the FQDN was not refreshed after a hostname change, which also caused subsequent backups to fail.
  For details, see To view or edit network settings.
• Appliances running CentOS 7 can now update to version 11.1.1-1 from earlier releases such as 10.9.1.
  The upgrade path was previously blocked for these appliances.
  For details, see CentOS 7 Upgrade to AlmaLinux 9.
• NAS (NFS) backups now generate client-side log files.
  Previously, only server-side logs were created, making it difficult to diagnose NAS backup failures.
  For details, see NAS Backups Overview.