Files
esh-pfi-infrastructure/configs/restic/vm-esh-nas/profiles.yaml
T
vh 6e203dcb99 fix(restic): stop publishing rest-server passwords in systemd units
resticprofile schedule copies env-file values into the generated units, which
are 0644, so RESTIC_REPOSITORY (the rest-server basic-auth password included)
was readable by every local user on every restic host.

New playbooks/restic-repository-file.yaml:
- derives /etc/restic/repository (root 0400) from restic.env;
- uploads the profile switched to repository-file, but only when the live
  profile's sha matches the repo copy it was edited from (drift guard);
- checks the repository is reachable through the new profile (cat config);
- regenerates the units and verifies they exist and contain no rest:http.

Applied to ana-docker, fv-ml1 (configs/restic/ana-ml2), esh-docker-vm,
esh-vm-db, irv-ml1, nh3-dev and nh3-docker. An independent check across all
eight restic hosts (these seven plus esh-ml1) found 0 leaking units. nh3-docker's
scheduled unit ran a real backup afterwards (snapshot a29b889d). Each host's
URL and passphrase are vaulted as <host>/etc/restic/{repository,password}.

restic.env is kept (root 0600) because the per-host READMEs and the freshness
probe source it. A rotation must update the vault, restic.env and repository.

vm-esh-nas has no infra-ops account. Its in-place migration script is staged
for Prime to run with sudo, and its repo profile is pre-edited to match.

Also mirrors augaman-dev's 401df2d (compose header only). The config hash on
esh-ml1 is unchanged.
2026-09-27 01:51:05 -07:00

94 lines
3.0 KiB
YAML

# resticprofile config for vm-esh-nas.
#
# Second ESH Docker host (filezilla, dockge, agents). VM on esh-pve-nas.
# Covered by vzdump at the hypervisor level; this restic adds per-file
# restore + cross-site redundancy.
#
# Writes cross-site to the Anaheim rest-server (10.250.50.70:8000/vm-esh-nas/)
# because the ESH site has no local rest-server. Credentials live in
# /etc/restic/restic.env; passphrase in /etc/restic/password.
#
# Explicit NFS exclusions below are **critical** — this host mounts
# /mnt/{share,music,books,media} from 10.0.50.50 (hundreds of TB of
# media). They're not in the source list, but the exclude-patterns
# provide a second line of defense if the source list is ever edited
# carelessly.
#
# No DB hook needed: no relational databases on this host. Dockge /
# beszel-agent / dozzle-agent store trivial SQLite state captured raw.
version: "1"
global:
priority: low
ionice: true
ionice-class: 2
ionice-level: 7
min-memory: 100
default:
repository-file: /etc/restic/repository # not env-file: schedule copies env-file values into world-readable units
env:
RESTIC_PASSWORD_FILE: /etc/restic/password
initialize: false
lock: /var/lock/restic-vm-esh-nas.lock
backup:
verbose: 1
run-after:
- date +%s > /var/lib/restic/last-success
source:
- /opt/docker # compose files (~56 KB)
- /etc # host config
- /root # root's scripts, ssh keys, shell history
- /home # user home dirs (lkraven, nas, user)
- /var/lib/docker/volumes # beszel-agent, dozzle-agent, dockge state
exclude:
# CRITICAL: NFS mounts from 10.0.50.50 — never follow.
# These are in /mnt/, not in the source list, but pattern exclude
# protects against careless source edits.
- /mnt/share
- /mnt/music
- /mnt/books
- /mnt/media
# Docker internals
- /var/lib/docker/volumes/backingFsBlockDev
- /var/lib/docker/volumes/metadata.db
# Ephemeral / regenerable
- /opt/docker/compose/*/logs
- "**/*.log"
- "**/*.log.*"
- "**/*.pid"
# Per-user shell / app noise
- /root/.cache
- /root/.local/share/Trash
- /root/.python_history
- /home/*/.cache
- /home/*/.local/share/Trash
- /home/*/.npm
- /home/*/.mozilla/firefox/*/Cache
tag:
- host:vm-esh-nas
- site:esh
- fleet:home-lab
schedule: "*-*-* 01:00:00"
schedule-permission: system
schedule-log: /var/log/restic-backup.log
forget:
keep-daily: 7
keep-weekly: 4
keep-monthly: 12
keep-yearly: 3
tag:
- host:vm-esh-nas
# Schedule removed 2026-04-21: forget against --append-only rest-server
# always fails (delete ops blocked). Run manually during the prune
# ceremony when --append-only is temporarily off.
check:
read-data-subset: 10%
schedule: "Sun *-*-* 05:00:00"
schedule-permission: system
schedule-log: /var/log/restic-check.log