Repository navigation
v0.2.0
Highlights
- External backup storage (S3-compatible). Upload backups to AWS S3, Backblaze B2, Hetzner, Wasabi, Cloudflare R2, MinIO or any other S3-compatible service.
- Configure one bucket under Settings, with a connection test. Turn the upload on per server in the Backups tab.
- Every backup is uploaded after it is created. Large archives are streamed in parts, so Cubeherd's memory use stays low.
- The retention rule applies to the bucket too: automatic archives beyond the limit are deleted there, manual ones never.
- The Backups tab lists local and external archives together. Archives that only exist externally can be downloaded, restored (fetched first) and deleted.
- An upload failure keeps the local archive and is reported as a failed operation.
- README header and screenshots.
Fixes
- Scheduled backups now actually run. In v0.1.0 an overdue or due schedule was pushed back every time the scheduler looked at it, so scheduled backups never started. Manual backups, backups before updates and restores were not affected. Runs missed while Cubeherd was down are caught up two minutes after the start.
- Corrected the English label of the CurseForge key check button.
Upgrade
docker pull ghcr.io/matserix/cubeherd:0.2.0Existing data and settings are kept. Your backup schedules start working without any change. Credentials for the external storage are stored in cubeherd.json (readable by its owner only), so ideally use a key that may only write to that bucket.
Full Changelog: v0.1.0...v0.2.0