Skip to main content

· 2 min read

Changes compared to 23.6.11

Enhancements

  • Improved performance of cleaning up Object Lock delete markers during retention passes for S3-compatible Storage Vaults
  • Improve initial startup performance of browsing files to restore from a disk image

· 2 min read

Changes compared to 23.6.7

Breaking changes

  • New, simpler configuration may be required for PKCS11 Authenticode codesigning with a hardware dongle

New Features

  • Added support for using OpenID Connect 1.0 for Single Sign-On for Comet Server admin users. This allows admin users to authenticate themselves to Comet Server using their existing credentials at an external Identity Provider, such as Microsoft Entra ID (formerly Azure AD), Google, or other OIDC providers

· One min read

Changes compared to 23.5.2

Bug Fixes

  • Fixed an issue where Wasabi error logs caused by System Clocks being too far behind or too far ahead not outputting as expected.
  • Fixed an issue with macOS notarization timing out when Apple takes longer than 10 minutes to process the request.
  • Fixed an issue with Office 365 clients where rate-limiting may cause list requests to restart unnecessarily
  • Fixed an issue with the Comet Backup desktop app crashing when loading if a recent backup job was extremely large.
  • Fixed an issue with Office 365 backups where workers can hang while querying the Vault
  • Fixed an issue with bucket name validation where Wasabi bucket names ending with a period were reported as invalid
  • Fixed an issue with error handling during a retention pass of a vault that has object lock enabled.
  • Fixed an issue with the Comet Server Docker container failing to start during a recreate event.
  • Fixed an issue with Office 365 clients hanging in some situations.

· One min read

Changes compared to 23.6.6

Enhancements

  • Changed incremental backups for local file paths to estimate backup size instead of scanning

Bug Fixes

  • Fixed and reinstated the disk image BIOS mode reporting feature that was removed due to a compatibility issue with Windows 7 and Windows Server 2008 devices

· 2 min read

Changes compared to 23.6.4

Enhancements

  • Comet Server quick search can now search user email addresses, device / Protected Item / Storage Vault / job IDs

Bug Fixes

  • Fix an issue with editing storage vault names when the 'prevent users viewing storage type' permission was set
  • Fix a cosmetic issue with the loading spinner not disappearing when no snapshots are found during the Disk Image restore process in the Comet web UI

  • Fix an issue with the disk image BIOS mode reporter stopping a backup job on a permissions error
  • Fix an issue with detecting timezones on Windows if multiple countries share the same effective timezone
  • Fix an issue with streaming restores of Microsoft SQL Server databases if the database name contains an invalid character
  • Fix an issue with "exit code 4" error messages missing further detail when failing to perform a T-SQL BACKUP / RESTORE command against Microsoft SQL Server
  • Fix an issue where Wasabi error logs caused by System Clocks being too far behind or too far ahead not outputting as expected
  • Fix a cosmetic issue with missing results in the Comet Server web interface quick search if the same device hardware is registered across multiple user accounts
  • Fix a cosmetic issue with the homepage Self-Backup widget if a Server Self-Backup is currently running
  • Fix a cosmetic issue with deleting single snapshots from the Comet Server web interface if no snapshots are selected
  • Fix a cosmetic issue with not highlighting the previous search content when using the Alt+Q keyboard shortcut in the Comet Server web interface
  • Fix a cosmetic issue with incorrect help text on the Policies page in the Comet Serverweb interface

· One min read

Changes compared to 23.6.3

New Features

  • Added an option to use temporary files instead of RAM during a restore
  • Added a partial data recovery option to zero over unreadable data chunks during a restore (Comet will not abandon the job when it finds an unreadable chunk)