Skip to content

Homelab backup stack — official captures (restic, Longhorn, farmOS Docker)

Evidence summary

Field Content
Abstract Official captures for restic 0.18.1 semantics, Longhorn backup/restore/system docs, and a farmOS.org Docker/hosting page—parallel homelab track to Backup / DR — official documentation cluster.
Authority mix Upstream project docs (restic, Longhorn) + farmOS web capture (version must be confirmed against current hosting docs).
Decision relevance Parallel paths: app/DB backups vs Longhorn volume backup vs etcd—see Kubernetes platform backup / DR — Pi, k3s, Longhorn. farmOS Docker capture reflects historical v1.x compose patterns—not sole authority for farmOS 2.x / PostgreSQL backup design.
Canonical wiki links Backup and disaster recovery package — smart farm stack · Backup strategy comparison — farmOS, homelab, PostgreSQL, containers · Restore and recovery tiers — homelab farm systems

Key claims (public-safe):

  • restic docs emphasize correct stdin/command failure semantics—relevant when scripting app-aware dumps into restic.
  • Longhorn docs distinguish system backup bundles vs volume backup targets—do not conflate with etcd snapshots alone.

Open questions / follow-ups

  • Confirm farmOS major version and Postgres backup path against live deployment before treating Docker capture as restore-order truth.

Ingest wave: moved from raw/inbox/ to stable raw/processed/2026/*-inbox-2026-04-17.md (2026-04-18).

What each file is

Raw path Authority Notes
restic-backing-up... restic user manual (0.18.1) Backup semantics, --stdin-from-command, warning on naive \| restic --stdin masking command failures
restic-removing... restic Snapshot removal / forget policies
longhorn-backup-system... Longhorn docs (1.11.1 path in page) System backup bundle, volume policies, backup target
longhorn-restore-system... Longhorn docs System restore flow
longhorn-documentation-hub... Longhorn Short hub / index capture
farmos-docker-developing... farmOS.org (capture) Historical v1.x pattern: docker-compose + MariaDB sidecar—use for compose/volume thinking only; confirm current farmOS hosting for farmOS 2.x (PostgreSQL) before production backup design

Synthesis