Fixed an issue with 'Invalid Authentication' errors when a user profile has many thousands of Protected Items and/or Storage Vaults
Fixed an issue with unresponsive cancellation when accessing a remote Proxmox VE server
Fixed an issue with missing warning messages when manually starting cometd.exe on Windows outside of a service context
Fixed an issue with not respecting the choice of target backup method for Proxmox LXC containers
Fixed an issue where the Polish (pl_PL) language was not considered when parsing the Accept-Language HTTP header to translate error messages in the Comet API
Improved handling of password resets from the management console
Comet 25.9.1 brings improved functionality for performing user password resets. Previously, a password reset would cause logged-in clients to eventually close after user or background activity triggered an authentication failure. Now, management console users can choose whether to distribute updated passwords or disconnect devices, with well-established outcomes.
Admins and backup users can now choose to either update passwords on all connected devices or log out on all connected devices and return them to the login dialog, while admins also have the option of logging out all connected devices and terminating the backup agent.
Improved handling of non-default Microsoft 365 document libraries
Handling of non-default document libraries has been improved to allow for greater backup speed and correct OneDrive attribution.
Fixed an issue causing an invalid address to be applied when automatically provisioning a Comet Storage Gateway Storage Vault during device registration
Fixed an issue causing repeated content to appear during a granular restore for some Hyper-V Protected Items
Fixed an issue causing incorrect 'Size' and 'Received Time' values to be displayed for Microsoft 365 mail in the management console restore dialog
Fixed an issue with determining the Linux kernel version after recent software updates on Debian 13
Fixed an issue with Proxmox-to-Proxmox virtual machine restores failing due to a mounted ISO
Fixed an issue causing an authentication error when restoring data from a Microsoft 365 Protected Item
Fixed a cosmetic issue with field alignment when restoring to a Proxmox VE server in the Comet Backup agent
Titan is the latest entry in our quarterly rollup series. It branches off from our main rolling Voyager development into a fixed target for our partners to qualify and build upon.
This Quarterly release is named after Saturn's moon Titan. Fun fact: Titan, Saturn's largest moon, is the only moon with a substantial atmosphere and the only place besides Earth known to have liquids on its surface, including clouds, rain, rivers, lakes and seas of liquid hydrocarbons like methane and ethane.
As for the software, Comet 25.8.0 Titan, brings 4 new features and 7 enhancements, including a General Access Beta for Proxmox VE Protected Item backup, an MSI Installer for Comet Backup desktop app on Windows, an RPM Installer for Comet Backup desktop app on Linux, and much more.
As always for a new quarterly release, there are two changelogs for 25.8.0 depending on whether you are coming from the previous quarterly release or the previous Voyager release:
To provide more flexibility for installing the Comet Backup desktop application on Windows, Comet 25.6.3 offers a new .msi installer option.
Using a .msi installer is great option for mass deployments and supports all the install features and flags that Comet's .exe installer offers.
Automatically Create New Storage Vaults Using Policies Protected Items
Since Comet 24.12.0, a new user setting has been available to choose if devices that share the same user account login should back up Protected Items to a shared Storage Vault or isolated Storage Vaults.
This has been extended to interact with Comet's Policy system to set Default Protected Items. A Default Protected Item is a great way to ensure Protected Items are automatically created when a new device is registered to a user.
Now, when the Policy setting under the Storage Vaults tab Automatically create Storage Vault for new devices is configured, new devices registered to a user will have a Default Protected Item created and will have a Storage Vault automatically provisioned and ready to back up.
To make the most out of the Default Protected Item feature you will need to set a Schedule when configuring the Default Protected Item.
When the Storage Vault for the Schedule is set to The Latest Storage Vault any new device registered to the user with this policy set will automatically have a Protected Item and new Storage Vault created and will back up data to this new Storage Vault based on the Schedule.