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

Comet Lysithea takes its name from another moon of Jupiter — it was discovered by Seth Barnes Nicholson in 1938, and is named after Lysithea, one of Zeus’ lovers.

Lysithea brings 10 features and 15 enhancements, including a new Getting Started guide for first-time Comet Server admins; the ability to codesign macOS client software installers without requiring SSH access to a macOS system; the addition of Amazon AWS and custom IAM-Compatible storage providers as Requestable storage targets; improvements to bulk upgrade campaigns and the Bulk Replace Addresses page in the Comet Server web interface; Synology improvements (including support for Synology devices with Armada CPUs); and more. All users of the previous quarterly series 22.2.x ‘Elara’ and earlier are encouraged to upgrade. We strongly recommend that users of versions older than 22.2.1 ‘Elara’ upgrade, as 22.2.1 contains an important security bugfix.

As always for a new quarterly release, there are two changelogs for 22.5.0 ‘Lysithea’ depending on whether you are coming from the previous quarterly or the previous Voyager.

Changes compared to 22.2.1

New Features​

• Option to codesign macOS client software installer directly. When this option is enabled, Comet Server will perform macOS codesigning locally, without requiring SSH access to a macOS system.

• Added a new Getting Started guide which walks new Comet Server admins through the first steps of running a Comet Server, from adding their first user to downloading and installing the Comet Backup desktop client to running a backup job. This guide appears the first time an admin logs into a new server and can be dismissed at any time.

Thank you to our partners for getting the Chinese (Traditional) localization started! The best-quality translations come from our customers, who better understand the software and the backup industry. We appreciate any translation assistance that is offered.

If you want to correct a translation in Comet, or if you want to translate Comet into a new language, further information is available via CometBackup/translations at GitHub.

This release comes with two key improvements to server self backup. Using the new slider component you can select 'faster' or 'smaller' to optimize the compression levels for the backup. A new option has been added to exclude the job database from the Comet Server self backup. It is best practice to keep regular backups of your comet server. Some very large databases can cause this to be a high cpu operation. In this case, we recommend having two backup schedules, one very regular backup that excludes the job database and another less regular backup that includes all databases.

We have also improved the onboarding experience for DSM-7. There is added guidance on how to configure permissions in the DSM 7 Synology SPK for the Comet client

New Features​

• Feature: Add Chinese (Traditional) language translation for client-facing text

Changes compared to 22.3.5

New Features​

Comet Backup supports many different cloud storage providers (e.g. SFTP or S3-compatible) if you bring your own storage credentials. If you have configured Comet Backup to back up directly to a cloud storage provider, you should avoid reusing storage credentials across customers. For each customer, you should either create new cloud storage credentials manually; or proxy the data through Comet Server Storage Role; or ideally, have Comet Server allocate new cloud storage credentials automatically. Previous versions of Comet Server supported this "Requestable" provisioning for Backblaze B2, Wasabi Cloud Storage, and custom HTTP integrations. The latest version of Comet Server extends this support to Amazon AWS and to custom IAM-compatible cloud services.

• Feature: Allow selecting Amazon AWS as a Requestable storage target

• Feature: Allow selecting "Custom IAM-Compatible" as a Requestable storage target

Changes compared to 22.3.4

Enhancements​

• Hourly schedule configuration could be run on specific days and within a specified time

• Individual paths for Files and Folders Protected Items can now be edited in the Comet Backup desktop app

Bug Fixes​

• Fix an issue with the time zone of Synology devices being detected by Comet as UTC even when the device is set to another time zone

• Fix an issue with email reporting table allowing duplicate email entries

• Fix an issue with Office 365 where Comet could crash due to incorrect parsing of error response
• Fix an issue with Office 365 when OneDrive files or folders are restored to filesystem
• Fix an issue with 'Once Only' schedule type which displays 'Invalid Date' when default values are kept

• Fix an issue with tab order of the Schedule editor dialog in the Desktop client which now runs from top to bottom, left to right

Changes compared to 22.3.3

Bug Fixes​

• Fix an issue with the new macOS codesigning toolchain on Comet Server for Linux if the cometd user account has no writeable home directory
• Fix an issue with panics occurring if there is a network error during the initial login process when installing the Comet Backup desktop application
• Fix an issue causing the Comet Server web interface to crash when clicking "Restore" on the final page of the Restore wizard
• Fix an issue with inaccurate subprocess exit codes returned from the backup.elevator service
• Fix an issue with Utimesnano warnings when restoring the timestamp of the /Users directory on macOS

Changes compared to 22.3.2

New Features​

• Option to codesign macOS client software installer directly. When this option is enabled, Comet Server will perform macOS codesigning locally, without requiring SSH access to a macOS system.

• Added a new Getting Started guide which walks new Comet Server admins through the first steps of running a Comet Server, from adding their first user to downloading and installing the Comet Backup desktop client to running a backup job. This guide appears the first time an admin logs into a new server and can be dismissed at any time.

Bug Fixes​

• Fix an issue with generating an uncompressed package when signing the macOS client installer by SSH
• Fix an issue with malformed folder entries inside *.xar archives when creating an unsigned macOS client installer
• Fix an cosmetic issue with logo positioning on the Comet Server web interface navigation bar
• Fix an issue with the cancel button on macOS not working due to a missing tmp file
• Fix a crash that can occur if Comet encounters an error while performing an Office 365 backup

This version contains an important security bugfix. Please upgrade as soon as possible.

Changes compared to 22.2.0

Bug Fixes​

• Fix a security issue with cross-Tenant information disclosure
• Fix an issue with excessive logging of "Excluding system path '.../@eaDir' when running backup jobs on Synology NAS clients
• Fix an issue where enabling and disabling SSH access on a DSM 6 Synology NAS is necessary to allow the Synology SPK to install correctly

This version contains an important security bugfix. Please upgrade as soon as possible.

Changes compared to 22.3.1

Bug Fixes​

• Fix a security issue with cross-Tenant information disclosure
• Fix an issue where enabling and disabling SSH access on a DSM 6 Synology NAS is necessary to allow the Synology SPK to install correctly

Changes compared to 22.3.0

We have improved Wasabi storage location detection. Try it out with the new Wasabi region "ca-central-1" based in Toronto, Canada.

Enhancements​

• Enhancement: Update bucket region autodetection for latest Wasabi region

Changes compared to 22.2.0

New Features​

• Support sending a bulk upgrade to a custom query of users
• Option to choose whether a bulk upgrade campaign overrides/interrupts any running backup jobs or not
• Support separate 'Find' and 'Find and Replace' modes on the advanced 'Bulk Replace Addresses' page in the Comet Server web interface
• Some job and device metadata is now available as environment variables in Before/After commands
• New backup-tool command to output the unique device ID