Changes compared to 26.7.0

Changes compared to 26.5.4

New Features​

Automatically start a Bulk Update Campaign when the Comet Management Console restarts​

Keeping every device on the latest Backup Agent usually means an administrator remembering to launch a Bulk Update Campaign by hand after each server upgrade. A new Automatic Upgrade Campaign option now does this for you: when enabled, Comet Server starts a fresh Bulk Update Campaign automatically each time the Comet Management Console restarts, rolling the update out across your device fleet with no manual step.

To avoid redundant campaigns caused by quick or repeated restarts, a new campaign is only started if it has been more than 24 hours since the last bulk upgrade campaign.

The option is configured by a top-level administrator under the Backup Agent Downloads settings. Turn on the Enabled toggle, then use Configure upgrade campaign to pre-set exactly how the automatic campaign should behave — whether to upgrade older versions and/or downgrade newer ones, whether to wait for running backup jobs to finish or interrupt them, and whether to target all devices or a filtered subset.

Added support for NinjaOne RMM integration​

NinjaOne is a unified IT management platform combining RMM, endpoint management, and ticketing. Comet's new NinjaOne integration surfaces backup status directly inside NinjaOne, so you can monitor your customers' backups alongside the rest of their endpoint data instead of switching between tools.

Once configured, Comet writes the outcome of each backup to custom fields on the matching NinjaOne device — Last Backup Status, Last Backup Time, Last Backup Destination, Last Backup Total Size, and the Comet Job ID — refreshed automatically after every job.

Optionally, you can also enable automatic ticketing. When a backup fails, Comet opens a NinjaOne ticket against the affected device, with a link back to the Comet job log and a summary of the run. Repeated failures on the same device and Protected Item add a comment to the existing ticket and escalate its severity rather than creating duplicates, and when the next backup succeeds Comet resolves the ticket automatically with a resolution comment.

The integration is configured under Settings → Integrations in the Comet Management Console and requires the NinjaOne Agent on each device. For full setup instructions, see the NinjaOne integration guide.

Janus 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 Janus. Fun fact: Janus takes its name from the Roman god of gates, doorways, beginnings, and endings — fitting for a moon caught in one of the Solar System's strangest orbital arrangements. This small, potato-shaped, heavily cratered moon shares its orbit with a sister moon, Epimetheus, and about every four years the two moons drift close enough that they swap orbits with each other — a co-orbital dance found nowhere else in the Solar System. Keep an eye out for Epimetheus; that name may sound familiar again later this year.

Comet 26.7.0 Janus focuses on smarter administration and faster performance across the platform. Highlights include Model Context Protocol (MCP) support for agent-based workflows, Comet Server webhook notifications that render natively as Slack messages, saved job searches in the Comet Management Console, and a new Storage Template option to prevent end-user edits of template-provisioned Storage Vaults. This release also delivers performance improvements across our Comet Management Console, the Comet Backup desktop app, and Office 365 Protected Items.

As always for a new quarterly release, there are two changelogs for 26.7.0 depending on whether you are coming from the previous quarterly release or the previous Voyager release:

Changes compared to 26.4.5 (Phoebe)

Notice​

Comet Backup on macOS now requires macOS 12 "Monterey" or later​

Any users of macOS 10.13 "High Sierra", 10.14 "Mojave", 10.15 "Catalina", and 11 "Big Sur" should remain on the Comet 26.4.x "Phoebe" quarterly series.

New Features​

Model Context Protocol (MCP) support​

Self-Hosted Management Console Only

Comet Server can now act as a Model Context Protocol (MCP) server, letting you connect AI assistants and agent tooling directly to your Comet Server. Over 100 tools are available covering users, jobs, storage, policies, devices, and server settings, so you can automate routine administration and reporting with the AI tooling of your choice. Tools are read-only by default, with write access available on an opt-in basis.

Comet Server webhook notifications as Slack messages​

Comet Server webhooks can now be formatted as Slack messages. Point a webhook at a Slack Incoming Webhook URL and job notifications render natively in your chosen Slack channel, with no middleware or custom integration needed. This can be configured when adding or editing a webhook in the Comet Management Console.

Enhancements​

2FA status visible in User list​

The Users list in the Comet Management Console now shows each user's two-factor authentication (2FA) status, so admins can audit 2FA coverage across all their accounts at a glance instead of opening each user's detail page.

Saved job searches in the Comet Management Console​

Job searches in the Comet Management Console can now be saved and recalled, so the filtered views you check regularly are one click away instead of being rebuilt each time.

Storage Template lock option for provisioned Storage Vaults​

A new "Prevent users from editing the Storage Vaults created from this template" option is available in Storage Template settings in the Comet Management Console. Storage Vaults provisioned from a template with this option enabled cannot be modified by the end user in either the Comet Management Console or the Comet Backup desktop app, even when the account policy would otherwise permit editing Storage Vaults — so centrally provisioned storage stays exactly as you configured it.

Policy default schedules applied to policy default Protected Items​

Policy default schedules are now automatically applied to policy default Protected Items that have no schedules of their own, ensuring devices covered by a Policy always end up with a backup schedule in place. For enforced Protected Items, schedules are always applied; for unenforced Protected Items, schedules are applied at Protected Item creation time. Default schedules are shown in a greyed-out, non-interactive state so they can be told apart from explicitly configured schedules.

Linux Sandboxing always enabled for home directory restores​

Linux Sandboxing is now permanently enabled for Files and Folders restores to home directories, improving security by keeping restore file writes isolated from the rest of the system.

Improved Missed Backup log details​

Missed Backup log entries now record whether the target device was online at the time the backup was expected to run, so you can quickly tell whether a backup was missed because the device was offline or for another reason.

Faster Files and Folders restores on Linux​

The Linux restore sandbox has received multiple performance optimisations, and is now bypassed entirely for restores outside home directories where it is not required — making Files and Folders restores on Linux faster.

Improved Office 365 backup memory efficiency​

Office 365 calendar and mail backups now stream events and messages as they are processed, rather than collecting them all in memory before starting. This reduces peak memory usage when backing up large mailboxes.

Faster Comet Server web interface load times (COMET-1680)​

The Comet Management Console now loads quicker on initial startup, reducing the time admins and users spend waiting to access the web interface.

Additional Impossible Cloud regions available as Storage Vaults (COMET-59652)​

Comet now supports the eu-west-3 and us-east-1 regions when configuring an Impossible Cloud Storage Vault, giving admins additional options for data residency and lower-latency backups in those geographies.

Other enhancements​

• Added support for ML-KEM post-quantum encryption in TLS, helping protect data in transit against future quantum computing threats (COMET-59543)
• Improved overall performance and reduced memory usage across Comet Server and the Comet Backup client applications (COMET-5034)
• The pre-built macOS Comet Backup Agent installer now comes with the server URL pre-filled, so end users only need to enter their credentials to log in
• Cross-device restores in the Comet Backup desktop client now show a temporary Protected Item entry for the restore, so you can see and monitor the restore's progress
• The Comet Backup desktop client's granular restore wizard now displays disk partition sizes, matching the Comet Management Console and making it easier to pick the right partition to restore
• Improved the speed of Office 365 backup jobs
• Improved the performance of Comet Server user APIs, particularly with larger user profiles, for a more responsive Comet Management Console on busy servers
• Improved performance of the Comet Backup desktop app when rendering main screen charts (COMET-59908)
• Added an in-process DNS cache, on by default for Linux and macOS which typically lack an OS-level DNS cache, cutting repeated DNS lookups during backup and storage operations
• The Comet Backup desktop app now communicates with its background service more directly, making the app more responsive (COMET-1951)
• Bulk Update Campaigns now skip devices whose operating system is not supported by the new software version, rather than upgrading them to a version they cannot run
• Bulk Update Campaigns now send the update to busy devices as soon as their running backup job finishes, so campaigns complete sooner without interrupting backups
• Improved performance when making settings changes in the Comet Backup desktop application (COMET-59860)
• The Storage Template Test Connection action now performs a full end-to-end test by provisioning a temporary Storage Vault and removing it again, so storage permission problems are caught when the template is configured rather than when a user first requests storage
• Improved high DPI display support for Comet Backup on legacy x86_64 macOS machines (COMET-59362)
• Email reports can now be given an optional Name, shown in the report list in both the Comet Management Console and the Comet Backup desktop app, making it easier to tell apart multiple reports of the same type
• Added a User / Account column to the Storage Buckets page of the Comet Management Console, showing which user accounts use each bucket according to the latest Constellation report with links to each user's detail page, making it easier to audit storage usage

Changes compared to 26.5.3

New Features​

Model Context Protocol (MCP) support​

Added Model Context Protocol (MCP) support to the Comet Management Console, facilitating agent-based workflows.

Comet Server webhook notifications as Slack messages​

Added an option to format Comet Server webhook notifications as Slack messages, allowing a webhook to target a Slack Incoming Webhook URL and render natively in a Slack channel. This is configurable when adding or editing a webhook in the Comet Management Console.

Changes compared to 26.4.4

New Features​

• Added deeplink support in the Comet Management Console for navigating directly to individual and all Protected Items, Storage Vaults, and devices via shareable URLs (COMET-59329)

Changes compared to 26.5.2

Enhancements​

• Added deeplink support for Storage Vaults
• Improved the performance of Comet Server user APIs, particularly with larger user profiles
• Improved performance of the Comet Backup desktop app when rendering main screen charts (COMET-59908)
• Added in-process DNS Cache for Comet server and client binaries - on by default for Linux and MacOS
• Improve performance of the Comet Backup desktop app (COMET-1951)

Changes compared to 26.5.1

NOTICE: Comet Backup on macOS now requires macOS 12 "Monterey" or later.

Any users of macOS 10.13 "High Sierra", 10.14 "Mojave", 10.15 "Catalina", and 11 "Big Sur" should remain on the Comet 26.4.x "Phoebe" quarterly series.

Enhancements​

• Added support for deeplinks to user devices, the device actions dialog, and backup dialog on Comet Management Console
• Added the default server URL to the pre-built macOS Comet Backup Agent installer
• Added a job filter and a button to show deleted Protected Items on the Recent Activity page of the Comet Management Console
• Added a temporary Protected Item entry when performing cross-device restores from the Comet Backup desktop client
• Improved performance and reduced memory usage (COMET-5034)
• Added support for ML-KEM post-quantum encryption in TLS (COMET-59543)
• Updated the Comet Backup desktop client's granular restore wizard to display disk partition sizes, bringing it in alignment with the Comet Management Console web experience
• Improved the speed of Office 365 backup jobs

Bug Fixes​

• Fixed an issue causing live connected devices to fail to reconnect after a password change in the Comet Management Console
• Fixed an issue with starting sessions
• Fixed an issue with obtaining TOTP codes
• Fixed an issue causing Comet Backup agent installation failures on Synology DSM7 devices during fresh installations
• Fixed an issue causing Office 365 backups to potentially skip "calendars" and "contacts" in some cases where duplicate items are found
• Fixed an issue causing the configure button to be shown while performing a cross-device restore on a Comet Backup desktop client with no Protected Item available to edit
• Fixed an issue in the Comet Backup desktop app where scheduled backup jobs could run immediately instead of at their scheduled time, which could cause scheduled backups to be missed

Changes compared to 26.4.3

Enhancements​

• Added a job filter and a button to show deleted Protected Items on the Recent Activity page of the Comet Management Console (COMET-59549)
• Added an item count display for running backup jobs in the Comet Management Console, giving users another way to monitor job progress (COMET-59546)
• Backup job warning and error log messages are now aggregated, removing the previous log message cap (COMET-59547)
• Added a log message indicating when Files and Folders backup diagnostic logging is active (COMET-59545)

Bug Fixes​

• Fixed an issue with invalid paths in Comet Server Storage Role (COMET-59556)
• Fixed an issue with "relative path config not allowed" errors when using FTP Storage Vaults with "Store in default home directory" enabled (COMET-59732)

Changes compared to 26.5.0

Enhancements​

Faster Comet Server web interface load times (COMET-1680)​

The Comet Management Console now loads quicker on initial startup, reducing the time admins and users spend waiting to access the web interface.

Additional Impossible Cloud regions available as Storage Vaults (COMET-59652)​

Comet now supports the eu-west-3 and us-east-1 regions when configuring an Impossible Cloud Storage Vault, giving admins additional options for data residency and lower-latency backups in those geographies.

Changes compared to 26.4.0

Enhancements​

Log message aggregation for backup jobs​

In Comet 26.5.0, the previous hard cap of 15,000 log messages per backup job has been replaced with an aggregation approach. Up to 1,000 instances of the same warning message are recorded verbatim; after that, a summary entry is appended for every further 1,000 occurrences of the same message. This ensures that new issues are always visible in the job log and makes it easier to confirm that a job is still actively running.

Diagnostic logging status indicator for Files and Folders backups​

When Files and Folders diagnostic logging is active, Comet now logs a message at the start of the job to indicate that diagnostic logging is enabled. This is useful when reviewing logs with support and serves as a reminder to disable diagnostic logging when it is no longer needed.

Live item count updates for running backups​

The Comet Management Console now shows a live updating item count while a backup job is running, matching the existing behaviour in the Comet Backup desktop app. This gives users an additional way to confirm that a job is making progress when it might otherwise appear to have stalled.

2FA status visible in User list​

Admins can now view each user's two-factor authentication (2FA) status directly from the Users list in the Comet Management Console, without needing to open each user's detail page.

Improved offline license quota visibility​

The Comet Management Console now displays a warning banner when the offline license quota is exceeded. The offline server license information widget has been moved to the home page, and the quota exceeded warning message has been improved for clarity.

Linux Sandboxing always enabled for home directory restores​

Linux Sandboxing is now permanently enabled for Files and Folders restores to home directories, improving security by isolating file write operations from the broader system.

Improved Missed Backup log details​

Missed Backup log entries now include additional context about whether the target device was online at the time the backup was expected to run, making it easier to diagnose why a scheduled backup was missed.

Linux Files and Folders restore sandbox performance improvements​

Multiple performance optimisations have been applied to the Linux Files and Folders restore sandbox: the sandbox is now bypassed for non-home paths, a Trie data structure is used for fast path matching, LChown and Chmod operations are combined to reduce worker channel round trips, and worker/UID affinity scheduling has been introduced.

Improved Office 365 backup memory efficiency​

Office 365 calendar and mail backups now stream events and messages as they are processed rather than collecting them all in memory before starting. This reduces peak memory usage during backups of large mailboxes.

Policy default schedules applied to policy default Protected Items​

Policy default schedules are now automatically applied to policy default Protected Items that have no schedules of their own configured. For enforced Protected Items, schedules are always applied; for unenforced Protected Items, schedules are applied at Protected Item creation time. Default schedules are shown in a greyed-out, non-interactive state to distinguish them from explicitly configured schedules.