Hier pflege ich wenn es wichtige Änderungen gab, die jeweils aktuelle Build Version von Altaro VM Backup ein.
Version 8.29 Build 8.29.4
Changes
Includes a user-friendly message when backup or restore operations fail due to the hypervisor not being supported by the VM Backup version being used.
Fixes an issue with Exchange Item Level Restore where some folders would not be listed correctly.
Other minor fixes and improvements
Version 8.27 Build 8.27.7.0
Note: Release 8.27.3 was recalled due to an issue when backing up VMware hosts, where VM snapshots
created during backup were not being removed, which could lead to more storage being used
up on the datastore than usual.
This build was recalled, fixed and replaced with build 8.27.7
All customers running 8.27.3 should upgrade immediately to avoid any issues with
snapshots being left on the VMware datastore.
Please download and upgrade to version 8.27.7 or later.
New
- Adds support for new Amazon S3 and Wasabi object storage regions
- Adds exchange granular restore support for Exchange 2019 CU9, CU10 and CU11
- Adds exchange granular restore support for Exchange 2016 CU21 and CU22
- Adds support for VMware ESXi hosts, and vCenter version 7.0 Update 3c
New
- Adds support for new Amazon S3 and Wasabi object storage regions
- Adds exchange granular restore support for Exchange 2019 CU9, CU10 and CU11
- Adds exchange granular restore support for Exchange 2016 CU21 and CU22
- Adds support for VMware ESXi hosts, and vCenter version 7.0 Update 3c
Fixes
- Fixes an issue that would fail restore operations for VMs that are configured to use an NVME controller on VMware hosts
- Note: Restoring VMs with an NVME controller is only possible if the backup of the VM is performed with Altaro VM Backup version 8.27 onwards
- Note: Restoring VMs with an NVME controller is only possible if the backup of the VM is performed with Altaro VM Backup version 8.27 onwards
- Fixes an issue that would prevent items from being listed within the granular exchange restore browser.
- Fixes an issue that would not list VMs for restore when adding the Azure offsite copy location manually as a restore source
- Fixes an error message when for restore operations for a VM from a 2012R2 host to a Windows Server 2022 host