Changes compared to 26.8.8

New Features​

• Added support for Windows Authenticode codesigning of client software using a key stored in AWS Key Management Service (KMS) or in Google Cloud Key Management Service (Cloud KMS), configurable in the Codesigning dialog of the Comet Management Console (COMET-60714)
• Added support for Windows Authenticode codesigning of client software using Azure Artifact Signing (formerly Azure Trusted Signing), configurable in the Codesigning dialog of the Comet Management Console (COMET-5374)
• Added the ability to mount a File and Folder snapshot as a read-only folder from the Restore dialog of the Comet Backup desktop app on Linux, including when running inside WSL2. Files are downloaded from the Storage Vault only when they are opened, and active mounts can be opened or unmounted from the new Mounted snapshots dialog (COMET-60718)
• Added an option to skip Office 365 mail messages and OneDrive and SharePoint files that are already present at the destination when restoring to the Office 365 cloud, enabled by default in the restore dialog (COMET-60209)
• Added support for automatically rotating Storage Vault access keys and clearing Storage Vault locks for Storage Vaults provisioned from a Backblaze B2 Storage Template (COMET-60613)
• Added support for automatically rotating Storage Vault access keys and clearing Storage Vault locks for Storage Vaults provisioned from a Comet Storage Gateway Template (COMET-60612)
• Added an option to issue a new key for an existing bucket, from the Storage Buckets page of the Comet Management Console (COMET-3289)

Changes compared to 26.8.7

Enhancements​

• Improved the speed and reduced the memory usage of loading Storage Vault indexes in Comet Backup jobs and restores, especially for large Storage Vaults (COMET-60533)
• Improved index lookup performance for Storage Vaults with a large number of index files, and reduced the number of open file handles when using on-disk indexes (COMET-60749)
• Linux Disk Image backups now keep their snapshot difference storage on disk instead of in RAM where possible, and the storage can grow during the backup, so large or busy devices are less likely to run out of snapshot space (COMET-59641)
• Updated the OpenSSL library bundled with the VMware (VDDK) support on Windows to a newer 3.0.x release (COMET-5831)
• The Comet Backup desktop app now runs Storage Vault search, email preview, retention passes, index rebuilds, and snapshot and file deletion through the background service, instead of starting them as the logged-in user (COMET-60727)

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)

Changes compared to 26.7.2

Changes compared to 26.8.5

Changes compared to 26.8.4

New Features​

Added a custom partition tool in the WinPE Recovery Environment (COMET-2138)​

The WinPE Recovery Environment now has its own Disk Management dialog, so disks can be prepared for a Disk Image restore without calling out to Windows' diskmgmt.msc. It can list disks and their partitions, initialize a raw disk as GPT or MBR, clean a disk, create a new simple volume through a wizard, format a partition, assign or change a drive letter, extend a volume into adjacent unallocated space, shrink an NTFS volume, and delete a partition.

Added the ability to set the backup job speed limit to specific times and days (COMET-3574)​

A backup job's speed limit can now follow a schedule, so a job can be held to a lower speed during business hours and run at full speed overnight. This is a long-standing feature request from customers whose devices share a slow internet connection, where a large first backup can run for days. When a scheduled window starts or ends, the new limit applies immediately, including to transfers already in progress.

engine1/mysql Protected Items support a METADATA_FILE EngineProps key: an optional client-local file stored in each snapshot as .metadata, skipped by database replay restores and retrievable with a file restore (COMET-60200)​

This lets an integration attach its own recovery metadata to every MySQL snapshot, so each snapshot is self-contained for disaster recovery. Comet only carries the file: it is read at backup time, only the path appears in the Protected Item settings, and if the file is missing the job logs a warning while the database streams still back up.

engine1/mysql Protected Items support an INCLUDE_USERS_GRANTS EngineProps key: when set to "1", the server's user accounts and privilege grants are captured as a SQL script stored in each snapshot as .users-grants.sql, skipped by database replay restores and retrievable with a file restore. Verified against MySQL 8.0.43 and MariaDB 11.4 and 10.6, including MariaDB roles; servers without SHOW CREATE USER fall back to SHOW GRANTS alone (COMET-60200)​

The generated script replays in dependency order and creates each account with IF NOT EXISTS, so an account that already exists on the target, such as root, is left alone while its grants still apply. A restore never runs the script automatically, because doing so could rewrite the target server's accounts; it is retrieved with a file restore and applied by hand.

Changes compared to 26.8.3

New Features​

Added an Extra Fields section to the user profile page in the Comet Management Console for free-form content (COMET-60171)​

User profiles have supported free-form metadata since Comet 26.2.1, but it could only be edited through the API. The user profile page in the Comet Management Console now has an Extra Fields section for editing it directly, useful for notes, contact details, or IDs linking the user to an external system. Each entry can be marked as admin-only or visible to the end user, and the same key name may be stored at both visibility levels independently.

Added a Test Connection button to the Proxmox destination page of the Restore dialog in the Comet Management Console, testing SSH connectivity via the connected device (COMET-5839)​

Previously, a wrong server address or credentials for a Proxmox restore started from the Comet Management Console only surfaced after the job had been submitted. The Proxmox destination page of the Restore dialog now has a Test Connection button, matching the Comet Backup desktop app. The test is relayed through the connected device, so it checks the same SSH connection the restore job itself will use. A successful test with no destination node or storage target selected prompts you to pick them, and a failed test against the Proxmox web interface port (8006) suggests using the SSH port instead.

Changes compared to 26.8.2

New Features​

• Added support for restoring directly to remote and cloud locations (COMET-2051)
• Added the ability to create Admin API tokens for programmatic API access without sharing their password or 2FA (COMET-59379)

Changes compared to 26.7.1

Enhancements​

• Improved the layout of field rows on narrow screens throughout the Comet Management Console, giving input boxes and drop-downs around 80px more width in dialogs such as Remote Server, Restore, Code-signing and Storage Vault location

Changes compared to 26.8.1

New Features​

Added a Custom code section to the Branding page of the Comet Management Console (COMET-1637)​

A top-level administrator can now inject custom JavaScript and CSS into the web interface. Code can be supplied inline or loaded from an external URL, placed in the document head or at the end of the document body, and is applied to the login page and to the web interface of all tenants. The page Content-Security-Policy is extended automatically to permit only the specific code that was configured.