ab87c0fada
Adds a server-wide backup capability beyond the existing ops_dashboard pg_dump flow: - Daily systemd timer (03:30) runs pg_dumpall + Forgejo dump, then restic to a local NAS repo and an offsite Backblaze B2 repo with Object Lock. Phase-based script with single-instance flock, structured statusfile, systemd hardening, and live-datadir excludes (Postgres / Forgejo) so the dumps stay authoritative. - Ops-agent gets nine new read-only/trigger commands (snapshots, stats, status, logs, plus two triggers) backed by sudoers-whitelisted wrapper scripts that source /etc/restic-backup.env so the agent never sees the restic password or B2 keys. - Two new flows (server_backup_full, server_backup_restore_test) drive the dashboard's "Backup now" and "Restore test" buttons. - /settings/backups gains a Server backup section with overall + per-phase status, NAS / B2 snapshot tables, restore-size / raw-data / dedup-ratio stats, and the last restore-test result. The existing pg_dump section is preserved unchanged. - Runbook docs/runbooks/server-backup.md follows the tailscale-setup pattern (plan + addendum) and covers B2 Object Lock + scoped keys, Forgejo subplan with isolated restore-test stack, the off-server maintenance flow for B2 prune, and the integrity-check schedule. Code-only change — installation on scrum4me-srv follows the runbook. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
18 lines
650 B
Bash
18 lines
650 B
Bash
#!/usr/bin/env bash
|
|
# Trigger server-backup.service ad-hoc. Refuses if a run is already active
|
|
# (the script itself also flock's, but checking here gives a friendlier error).
|
|
|
|
set -uo pipefail
|
|
|
|
UNIT=server-backup.service
|
|
|
|
active=$(systemctl is-active "$UNIT" 2>/dev/null || true)
|
|
if [ "$active" = "active" ] || [ "$active" = "activating" ]; then
|
|
echo "ERROR: $UNIT is already $active — refusing to trigger." >&2
|
|
exit 75
|
|
fi
|
|
|
|
# Use --no-block so we return immediately; the dashboard will poll via
|
|
# read-status.sh and tail the log to follow progress.
|
|
systemctl start --no-block "$UNIT"
|
|
echo "Triggered $UNIT. Follow with: journalctl -u $UNIT -f"
|