Skip to content

Replace unsafe hot-copy advice with sqlite3 online backup #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Yanujz merged 1 commit into from
Sep 20, 2026
Merged

Replace unsafe hot-copy advice with sqlite3 online backup #70

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,8 +193,11 @@ service at one probe/minute over 90 days.
- **Health & metrics:** point probes at `/healthz` (`HEALTHCHECK` is baked
into the image); scrape `/metrics` and alert on
`epmon_service_up == 0`.
- **Data:** back up the SQLite file — hot copies while running are safe —
or mount the volume into your backup job.
- **Data:** back up the SQLite file with the online backup — never a
plain `cp` of the live file, which can capture a torn write:
`sqlite3 /data/epmon.db ".backup '/backup/epmon-$(date -u +%FT%TZ).db'"`
(then `PRAGMA integrity_check` on restores), or mount the volume into
your backup job and back up from there.

## Metrics (`/metrics`, Prometheus text format)

Expand Down
Loading