26.8.7 ‘Voyager’ released

Changes compared to 26.8.6

New Features

• Added support for creating the Linux ISO recovery media on Windows using WSL2 in the Create Recovery Media wizard of the Comet Backup desktop app, so Docker or Podman is no longer required (COMET-60638)
• Added NFSv4 as a supported option for Storage Vaults and Storage Gateway (COMET-2248)
• Added a Linux (RPM) tab to the Codesigning settings dialog for uploading a GPG signing key to sign the Linux RPM backup-tool installer (COMET-59136)

Enhancements

• Duplicating a Protected Item in the Comet Backup desktop app now selects the new copy (COMET-60631)
• Improved the clarity of administrator account permissions in the Comet Management Console (COMET-59380)
• Unlocking a Storage Vault now also removes damaged lock files, and reports an error instead of success if some locks could not be read (COMET-60518)

Bug Fixes

• Fixed an issue with generating a Windows client installer if invalid codesigning credentials were supplied (COMET-60715)
• Fixed an issue with the integrated MCP server refusing every tool call for an admin account that has an IP whitelist
• Fixed an issue where policy backup rules targeting SMB, WebDAV or Storj Storage Vault types did not create a schedule for matching Storage Vaults. Existing policies with such rules will now create them (COMET-2248)
• Fixed the guest quota warning not appearing when first opening a VMware or Hyper-V Protected Item configured to back up all VMs in the Comet Backup desktop app (COMET-60510)
• Fixed the connection test for VMware, Proxmox and MongoDB Protected Items reporting success in some cases where the server could not actually be reached, in the Comet Backup desktop app (COMET-60510)
• Fixed an issue where two Protected Items with the same name could swap positions in the sidebar of the Comet Backup desktop app whenever the list refreshed (COMET-60631)
• Fixed IDrive e2 Storage Vaults looking up their regional endpoint on every connection, including when the endpoint was already known. Backup, restore and retention jobs on these Storage Vaults no longer depend on the IDrive e2 endpoint discovery API being reachable, and a job that does still need the lookup now fails in seconds rather than hanging for up to 20 minutes when that API is slow (COMET-60617)
• Fixed an issue where restoring a Hyper-V virtual machine could crash or silently restore incorrect data when the virtual machine's disks used differencing VHDX (.avhdx) chains. The issue was more likely on larger virtual disks and longer snapshot chains (COMET-60605)
• Fixed an issue where registering a device from the command line with backup-tool login prompt against an account with two-factor authentication enabled failed with ERR_TOTP_REQUIRED even when the correct six-digit code was entered at the prompt. This also affected first-time setup of the Linux client over SSH on headless servers (COMET-60407) (COMET-60300)
• Fixed an issue with installing Comet Backup on 32-bit ARM Synology devices (COMET-60447)
• Fixed Proxmox VM backups failing on Proxmox VE 9 with "Cannot find device" or "start node not found" errors (COMET-60573)
• Fixed a failed Proxmox VM disk backup leaving an uncommitted snapshot overlay attached to the running VM (COMET-60573)
• Fixed an issue with extra "Failed to check for running jobs locally" error messages in cases where a Storage Vault is being used concurrently (COMET-60518)
• Fixed an issue where a lock file that could not be read was ignored when checking whether a Storage Vault was in use (COMET-60518)
• Fixed an issue where a backup job with "Skip if already running" enabled could start a duplicate job if the running job refreshed its lock at the same time (COMET-60518)
• Fixed a cosmetic issue with timezone handling when browsing snapshot dates in the Comet Backup desktop app (COMET-60510)
• Fixed an issue with "CreateFile failed: 231" error messages in the Comet Backup desktop app (COMET-60510)