Skip to main content

Recent releases

View All
Quarterly
Voyager

26.8.5 ‘Voyager’ released

· 5 min read

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.

Enhancements​

  • Improved the reliability of Disk Image backups of LVM volumes on Linux. Fixed-size LVM snapshots are now monitored during the backup and automatically extended before their copy-on-write space fills up, which previously caused backups of busy volumes to fail with I/O errors (COMET-59640)
  • Added a clear warning to the job report when an LVM snapshot became invalid during a Disk Image backup on Linux, instead of only surfacing unexplained I/O errors (COMET-59640)
  • Table view settings in the Comet Management Console (visible columns, sorting, page size, and the group-view toggle) are now kept when upgrading Comet Server, instead of being reset on every upgrade. If a table's columns changed in the new version, only the settings for the changed columns are reset, and existing saved settings are carried over on upgrade (COMET-60015)
  • The engine1/mysql EngineProps keys are now documented in the SDK docs (COMET-60200)

Bug Fixes​

  • Fixed the forced admin password reset dialog in the Comet Management Console showing device password-update/logout options that do not apply to admin accounts (COMET-60442)
  • Fixed a security issue with connecting to malicious MySQL and MongoDB database servers (COMET-60426)
  • Fixed the Comet Backup desktop app closing completely when saving settings fails because the account password was changed elsewhere; it now returns to the login screen (COMET-60455)
  • Fixed the Proxmox "Test Connection" action in the Comet Management Console rejecting every current Comet Backup agent with "Incompatible agent version"; the compatibility check referenced a version newer than the release the feature shipped in (COMET-60536)
  • Corrected the documented availability of the CustomBranding server setting from 26.9.0 to 26.8.2 in the generated API documentation and SDKs (COMET-60536)
  • Fixed an issue where backing up a Proxmox VM with a PCI or GPU passthrough device failed during disk discovery (COMET-60270)
  • Fixed an issue where restoring a Proxmox VM configured with a hook script failed (COMET-60270)
  • Fixed an issue with detecting write failures to a Storage Vault (COMET-60511)