Changes compared to 22.6.0
- Update Dutch translation
- Add a random delay option for backup job schedules to spread out the CPU load for multiple jobs starting at the same time.
Changes compared to 22.6.0
Changes compared to 22.5.1
Comet Server supports using external authentication sources for admin accounts. If you have a highly-available LDAP server infrastructure using multiple servers, such as an Active Directory failover cluster with primary/fallback domain controllers, you are now able to configure multiple LDAP server addresses in Comet Server. When an admin user tries to authenticate at the Comet Server login screen, if a connection to the first entry on the list fails, Comet will try the remaining entries on the list before denying the authentication attempt.
Update Thai translation
Improve handling of temporary files on Synology devices using the SPK client installer
During backup jobs, Comet saves some temporary files in the system temporary directory. In the Synology DSM operating system, the default directory for temporary files (
/tmp) is a RAM disk. With this change, Comet switches to use a custom temporary directory. This reduces the RAM requirements for running Comet Backup on Synology devices, meaning that large backup jobs on RAM-constrained Synology devices will no longer cause slowdown or freezes due to running out of RAM.
Changes compared to 22.5.0
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
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
Changes compared to 22.3.5
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.
Changes compared to 22.3.4
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
Changes compared to 22.3.3
Changes compared to 22.3.2
This version contains an important security bugfix. Please upgrade as soon as possible.
Changes compared to 22.2.0