383 posts tagged with "voyager"

Changes compared to 26.8.0

New Features​

Added an allowlist of PKCS#11 driver module file paths permitted during Authenticode codesigning in the Comet Server admin settings (COMET-59771)​

When Comet Server Authenticode-codesigns the Backup Agent installers it generates for download, the signing key can be accessed through a PKCS#11 driver module. A top-level administrator can now maintain an allowlist of the driver module file paths permitted for this codesigning. Only modules whose file path appears on the allowlist may be used; a path outside the allowlist causes installer downloads to fail. When upgrading, any PKCS#11 module paths already in use are seeded into the allowlist automatically.

Added ConnectWise Manage PSA integration which raises job failure tickets (COMET-59932)​

ConnectWise Manage joins Comet's existing PSA integrations. Once configured, Comet Server automatically raises a ConnectWise Manage ticket when a backup job fails or a scheduled backup is missed, matched to the affected client, device, and Protected Item, with a severity mapped from the failure type. Repeated failures on the same device and Protected Item add a note to the existing ticket and escalate its severity instead of opening duplicates. The integration is configured under the PSA settings in the Comet Management Console, where you provide the Site URL, Company ID, public and private API keys, Client ID, and an optional Service Board and fallback ticket company.

Improved Microsoft 365 account selection with a new rule-based editor and exclude rules (COMET-59120)​

The account selection for Microsoft 365 Protected Items has been redesigned around an ordered list of include/exclude rules in both the Comet Management Console and the Comet Backup desktop app. You can now exclude specific users, groups, teams, or sites — for example, backing up an entire organization except a few accounts — with an "All accounts" rule automatically protecting users added to the organization later. Rules require Comet Backup 26.8.1 or later on the device.

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.

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.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.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.

Changes compared to 26.2.3

Notice​

Gradient PSA integration retired​

The Gradient PSA integration has been retired. Existing configurations are preserved and clearly marked as deprecated in the UI, with a startup warning to help administrators plan any necessary migration.

New Features​

Proxmox VM and LXC template backup and restore​

Proxmox customers can now protect their VM and LXC templates — with full backup and restore support. This closes a meaningful gap in Proxmox coverage, ensuring the building blocks of an environment can be recovered just as reliably as live workloads.

Zero-touch device registration for 2FA-enabled users​

Administrators can now register devices on behalf of users who have 2FA enabled, using either lobby mode or an install token, without requiring the user to be present or share their TOTP code. This removes a key friction point in enterprise and MSP deployments, enabling true zero-touch device provisioning.

Enhancements​

Disk image backup support for Ubuntu 25​

Customers running Ubuntu 25 can now take full disk image backups, keeping pace with the latest release cycle.

Auto-add Cluster Manager target when creating Storage Templates​

When setting up a Storage Template or replication target, administrators are now prompted to simultaneously register the destination as a Cluster Manager target — eliminating a common multi-step setup gap.

Streamlined licensing during Comet Core installation​

The Comet Core installer now presents a streamlined licensing experience showing only the serial license key option.

/run and /var/run excluded from Unix Files and Folders backups by default​

Files and Folders backups on Unix systems now automatically exclude /run and /var/run by default. Excluding these paths out-of-the-box improves efficiency and reduces unnecessary data capture without any user configuration.

Improved error messaging for Backblaze Storage Vault creation failures​

When a Backblaze-backed Storage Vault fails to be created, users now receive a clear, actionable error message instead of a generic server error — reducing troubleshooting time and support overhead.

Changes compared to 26.2.2

Enhancements​

• Update the Ukrainian language translation
• Perform automatic internet time sync in the Linux Recovery Media

Changes compared to 26.2.1

New Features​

• Added Storage Template replication as part of the Management Console replication

Enhancements​

• Allow easily selecting groups of snapshots to search for restore or to delete in the Comet Management Console web interface
• Added a lock/unlock button to password and bucket ID fields to prevent password manager autofill

Bug Fixes​

• Fixed an issue with the 'login as user' feature if Tenants are being used
• Fixed an issue with the Associated Devices table when viewing a Storage Vault in the Comet Management Console web interface
• Fixed an issue when proxmox restore fails if the backup is non-Proxmox VM and the target is RBD
• Fixed bug where a Proxmox tpmstate drive couldn't be read from rbd/ceph storage