Changes compared to 25.3.5
It is now possible to cancel running jobs in bulk from the Job Logs page on a Comet Management Console. This is an effective way to stop all currently running backup jobs with one click.
Changes compared to 25.2.2
Changes compared to 25.3.4
Changes compared to 25.3.3
In previous versions of Comet, the "Select all except..." option for Microsoft 365 Protected Items was provided as an alternative way to select accounts, allowing for the automatic inclusion of new accounts and potential exclusion of others. User feedback was that the behaviour of this option was unintuitive, and so we have elected to remove this option in favour of a more intuitive alternative.
In Comet 25.3.4, we are introducing the new "Back up everything" option for Microsoft 365 backups. This option provides a simple way to back up everything within a domain, including any accounts that are added later.
To back up everything with exceptions, users should instead create a group in Microsoft 365 and have the group auto-assign to new accounts. Users to be excluded can be removed from the group, and this group can then be selected in Comet.
Changes compared to 25.2.1
VMware Protected Items that have been configured to use the Latest VM state (Changed Block Tracking) mode will now fallback to performing a full VM backup when Comet detects that more than 50% of the disk has changed. This speeds up the backup peformance when large parts of the VM has been modified.
Changes compared to 25.3.2
Comet uses a custom Linux kernel driver backupsnap61 to snapshot a block device during a Linux Disk Image Protected Item backup.
In previous releases, backupsnap61 had to be installed manually using the backupsnap61-install.sh script found in the Comet Backup install directory.
Without backupsnap61 installed, Comet can't guarantee it can get exclusive read access to a block device. This will appear as a warning in a Linux Disk Image backup job log.
Now, backupsnap61 is installed automatically by Comet to ensure a snapshot driver is always available before starting a Linux Disk Image backup.
Changes compared to 25.3.1
Creating the Linux recovery environment ISO using Comet Backup on a Linux endpoint can now be done without requiring Docker to be installed. This simplifies the install requirements to build the Linux recovery environment and also reduces how long it takes to build the recovery environment.
VMware Protected Items that have been configured to use the Latest VM state (Changed Block Tracking) mode will now fallback to performing a full VM backup when Comet detects that more than 50% of the disk has changed. This speeds up the backup peformance when large parts of the VM has been modified.
Changes compared to 25.3.0
Changes compared to 25.2.0
As part of our efforts to improve the experience of using Comet, in Comet 25.3.0 we have added functionality to automatically change Storage Vault access keys for some of our supported storage providers, allowing admins to manually unlock compatible Storage Vaults without the risk of data loss.
Vaults can also be automatically unlocked when specified criteria, configured in user policy settings, have been met.
The following Storage Vault types are currently supported:
Comet 25.3.0 adds support for setting yearly schedules and retention rules - great for long term storage, archival, and compliance requirements.
Changes compared to 25.2.0
To make it easier to find vaults that are shared with other devices, the "Show Storage Vaults in use by other devices" option has been moved directly under the Storage Vault selector.
This makes it significantly easier to backup to or restore from a Storage Vault that is owned by other devices in the same user account.