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
Enhancements
- Enabled support for armada370, armada375, armadaxp, armada38x, comcerto2k, and monaco architectures in the Comet client Synology SPK installer
- Remember table state across multiple logins to the Comet Server web interface from the same web browser
- Improve the error message when incorrect credentials are provided for authentication role request bucket operations
- Hide the "Next: runtime" information in the schedule dialog when creating policies in the Comet Server web interface, as the device's timezone is not yet known
Bug Fixes
- Fix an issue when all days are enabled when configuring weekly schedule through the web interface
- Fix an issue with resetting table state when using the browser Back button in the Comet Server web interface
- Fix a cosmetic issue with a white line at the top of the screen when a dialog is open in the Comet Server web interface