Off-site / object-storage backup target for the SQLite DB #18

Open
opened 2026-07-07 16:52:40 +00:00 by claude-bot · 0 comments
Contributor

Goal

Optionally ship the existing timestamped SQLite backups to an off-box target (S3-compatible object storage, or a mounted remote path) so a host failure doesn't lose approved schemes and history.

Why it's valuable

v1 already creates timestamped backups before bulk operations and prunes by BACKUP_RETAIN_COUNT, but they live on the same volume as the DB. Off-site copies make the data actually durable — important because approved schemes represent real curation effort.

Sketch

  • Env-gated backup target (e.g. BACKUP_S3_ENDPOINT/bucket/creds, or BACKUP_REMOTE_PATH).
  • After each local backup, upload the artifact; apply the same retention remotely.
  • Restore path documented in docs/troubleshooting.md.

Acceptance criteria

  • Backups optionally uploaded to an S3-compatible or remote-path target
  • Remote retention honored
  • Feature env-gated, off by default; restore documented

Proposed enhancement (not in the original spec).

## Goal Optionally ship the existing timestamped SQLite backups to an off-box target (S3-compatible object storage, or a mounted remote path) so a host failure doesn't lose approved schemes and history. ## Why it's valuable v1 already creates timestamped backups before bulk operations and prunes by `BACKUP_RETAIN_COUNT`, but they live on the same volume as the DB. Off-site copies make the data actually durable — important because approved schemes represent real curation effort. ## Sketch - Env-gated backup target (e.g. `BACKUP_S3_ENDPOINT`/bucket/creds, or `BACKUP_REMOTE_PATH`). - After each local backup, upload the artifact; apply the same retention remotely. - Restore path documented in `docs/troubleshooting.md`. ## Acceptance criteria - [ ] Backups optionally uploaded to an S3-compatible or remote-path target - [ ] Remote retention honored - [ ] Feature env-gated, off by default; restore documented Proposed enhancement (not in the original spec).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rbrooks/Iris-WLED#18
No description provided.