chore(backup): env-gated off-disk mirror + restore drill doc (#645)

The pg_dump sidecar wrote its dumps to the same disk it protects — one
disk failure lost both. Setting ROBOCO_BACKUP_MIRROR_DIR in .env to a
path on a different disk (external/remote mount) arms a mirror step after
every successful dump: tmp+rename copy, mirror pruned to the same
BACKUP_KEEP, unwritable mirror logs-and-skips without blocking the
primary. Unset, the script never attempts a copy — no fake off-disk
copies on the same disk. Docs gain the mirror setup and a quarterly
restore drill (throwaway pgvector container, pg_restore, row-count
sanity check).

Co-authored-by: Renn F <rennf93@users.noreply.github.com>
This commit is contained in:
Renzo F
2026-07-22 20:29:50 +02:00
committed by GitHub
co-authored by Renn F
parent 2e889c7009
commit 98a96bcd21
6 changed files with 101 additions and 2 deletions
+5
View File
@@ -59,6 +59,11 @@
# Path to data directory on the host (MUST be absolute for Docker-in-Docker)
# ROBOCO_DATA_DIR=/volume1/roboco/data
# Off-disk mirror for the daily pg_dump backups. Point at a path on a
# DIFFERENT disk (external USB, or a mounted remote/cloud share) — a
# same-disk mirror protects nothing. Unset = mirroring off.
# ROBOCO_BACKUP_MIRROR_DIR=/mnt/external/roboco-backups
# =============================================================================
# Application
# =============================================================================