Changes compared to 24.3.7

Enhancements​

• Added configuration to the Comet Server to set the maximum number of CPU cores that are allowed to be used when generating new builds of the Comet Backup client software
• Added a new environment variable (COMETD_TMPDIR) to allow configuration of the temp directory used by the Comet Server when running in Linux

Bug Fixes​

• Fixed an issue which caused the SEVT_TENANT_UPDATED event to emit the tenant name instead of the tenant ID
• Fixed an issue where the “Open Folder” button was not visible in the Comet Backup desktop app after a restore job had completed
• Fixed an issue where the “Open Folder” button in the Comet Backup desktop app failed to open a file browser at the location of the restored files for UNC paths
• Fixed an issue where S3 backups showed a Object Lock error about enabling Versioning on the S3 bucket instead of the real failure
• Fixed an issue where audit logs would not be pruned if Authentication Role was set to keep logs indefinitely
• Fixed an issue where setting “If the last job was Missed” on a schedule triggered extra backup jobs if the device’s live connection dropped while the scheduled job was still running

Changes compared to 24.3.6

New Features​

• Added support for selecting Windows drives by drive letter when configuring a Disk Image Protected Item

Enhancements​

• Added a label in the Comet Server web interface and the Comet Backup desktop app to distinguish if Protected Items are enforced via the policy
• Added the ability to convert Windows System Backup Protected Items to Disk Image Protected Items via the Users tab and Bulk Actions dropdown in the Comet Server web interface
• Improved Microsoft 365 Drive downloads by adding configurable account concurrency and adding concurrency to single file downloads

Bug Fixes​

• Fixed an issue with default Protected Items, allowing edit and delete options when the configured policy doesn’t strictly enforce it
• Fixed an issue with the Comet Backup desktop app deleting DeviceIdentificationEntropy and DeviceIdentificationHardwareIDOverride registry keys when uninstalled
• Fixed an issue causing a deadlock when too many requests to a Storage Vault fail during decompression in a single job
• Fixed an issue causing restores to panic when Comet fails to load a directory included in the files being restored
• Fixed an issue with some search results not appearing when multiple partial matches exist in the Comet Server web interface
• Fixed an issue with search results not appearing for results with non-ASCII characters in the Comet Server web interface
• Fixed an issue allowing search invocation underneath an active dialog in the Comet Server web interface
• Fixed an issue causing Comet Server to segfault when starting on Linux
• Fixed an issue causing clients running on Windows Server 2008R2 and Windows 7 to lose their live connection and become unable to be remotely upgraded after a Comet Server upgrade

Written by Callum Sinclair – Product Engineering Manager

What’s New? is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet over April 2024. 

There were three Comet releases during April – two in the Voyager release series, plus one update for our Mimas release series.

We’ve landed a few large and exciting features this April:

Hyper-V CBT (Changed Block Tracking)​

Hyper-V CBT is now available in our Voyager series. Hyper-V CBT performs efficient backups of Hyper-V Virtual Machines by only reading blocks of a virtual disk that have changed since the last backup job. This means Comet only needs to upload the data that has changed inside the VM without having to read and upload every byte.

You will find two new Hyper-V Backup Mode types when setting up a Hyper-V Protected Item. These are Latest VM State (Changed Block Tracking) and Latest VM State (Standard). You can read more about what these new modes do in our documentation here

Under the hood our two new Hyper-V Backup Mode types use WMI (Windows Management Instrumentation) and RCT (Windows Resilient Change Tracking) to perform the backup. This is a completely new way for Comet to backup Hyper-V VMs as our old implementation used Windows VSS (Windows Volume Shadow Copy Service).

New Hyper-V Backup Option One: Changed Block Tracking using WMI and RCT​

New Hyper-V Backup Option One: Hyper-V Backup using WMI​

Hyper-V Changed Block Tracking Using​

This enhancement improves our Hyper-V backup offering, ensuring faster backups of your Virtual Machines while also needing to upload less data.

Impossible Cloud Storage Templates​

We’re pleased to announce that Impossible Cloud is now available as a built-in Storage Template in our Voyager series. If you enter top-level credentials into the Storage Template, Comet can use them to provision private buckets with separate credentials for each user, allowing seamless direct-to-cloud backup.

Impossible Cloud IAM Storage Template​

Impossible Cloud IAM Storage Template with Object Lock​

Impossible Cloud Partner API Storage Template​

As a quick reminder – when using the Storage Templates, it’s likely you’ll want to configure cleanup for cloud buckets that are no longer being used by any user account. Comet’s solution for this problem is called Constellation Role, and it’s available from the settings page of your Comet Server. In Constellation, you can enter the same credentials for it to search through. When a Constellation report runs, it finds all your buckets; checks all the user accounts; cross-references the users’ Storage Vaults with the available buckets; and deletes any discovered buckets that are not in use by any user account.

Constellation Role is designed to scale up to clusters of multiple Comet Servers, with any mix of server replication, Storage Role, or direct-to-cloud buckets created by the Storage Template feature. You should have exactly one Constellation Role server amongst your entire cluster of Comet Servers.

Comet-Hosted Single Sign On​

Users can now sign into Comet-Hosted servers using their account.cometbackup.com accounts. This feature simplifies access to Comet-Hosted servers, allowing users to utilize their existing Comet Backup account credentials for authentication. To enhance security, users are encouraged to set up two-factor authentication (2FA) on account.cometbackup.com.

This feature has already been enabled, and will be used the next time you click the login button from the My Services page on account.cometbackup.com.

In addition, once you have clicked the login button on the My Services page you will notice the new “Login with Comet Account Portal” button appear on the login screen of your Comet-Hosted server. This button will only appear on browsers where you have clicked the My Services login button before. We have done this to ensure we don’t break any rebranding you have configured by showing a big “Login with Comet Account Portal” button.

Comet-Hosted London Region Now Available​

We are pleased to announce that Comet-Hosted is now available to be hosted in the London region. Comet users now have the choice of four geographically diverse locations to choose from when selecting where their Comet-Hosted server should be located.

Continued Comet Improvements​

Throughout April, we rolled out over twenty fixes and enhancements aimed at improving the overall quality and performance of Comet. These updates underline our commitment to providing a reliable and efficient backup solution for our users.

Changes compared to 24.3.5

Enhancements​

• Added the ability to configure SQL timeouts for MSSQL restores
• Improved error message output for when a Hyper-V backup fails due to Hyper-V not being installed on the endpoint
• Added additional threading to single file downloads from Microsoft 365, and added retry logic for when the download URL has expired. Expired URLs can cause 401 errors.

Bug Fixes​

• Fixed an issue causing a crash when data from multiple disks is selected for restore during granular restore workflows
• Fixed an issue causing logins requiring 2FA to fail on the Comet Server web interface
• Fixed an issue with the Comet Server web interface settings page to crash when a tenant has been deleted