kamal-backup currently supports one Restic repository. Supporting optional secondary repositories would allow one
database export to be backed up once and then replicated using restic copy
(https://restic.readthedocs.io/en/stable/045_working_with_repos.html#copying-snapshots-between-repositories).
This would avoid running multiple backup accessories, schedules, and database exports just to store backups with
different providers.
Example:
restic:
repository: s3:https://primary.example.com/bucket
mirrors:
- repository: s3:https://secondary.example.com/bucket
Requirements:
- Existing YAML configuration must remain fully compatible and unchanged.
- mirrors must be optional, so current users receive identical behaviour after upgrading.
- Export the database once, back up to the primary repository, then copy the snapshot to mirrors.
- Support separate credentials for repositories using different S3-compatible providers.
- Report failures and freshness per repository.
This could provide simpler multi-provider redundancy without changing the current single-repository workflow.
kamal-backup currently supports one Restic repository. Supporting optional secondary repositories would allow one
database export to be backed up once and then replicated using restic copy
(https://restic.readthedocs.io/en/stable/045_working_with_repos.html#copying-snapshots-between-repositories).
This would avoid running multiple backup accessories, schedules, and database exports just to store backups with
different providers.
Example:
Requirements:
This could provide simpler multi-provider redundancy without changing the current single-repository workflow.