Skip to content

Backup and disaster recovery — doctrine hub

Purpose: Router for backup / restore / DR across farm records (farmOS / PostgreSQL), Kubernetes (k3s, etcd), cluster storage (Longhorn), Rancher, secrets, and edge scope—so readers land on the canonical spine first instead of skimming dozens of analyses.

What this hub owns: Navigation (labels, read order, “which page is authoritative for X?”). It does not duplicate the DR package prose or invent RPO/RTO numbers.

What it does not own: Per-site cron schedules, bucket names, or restore drill dates—those stay in operator runbooks and evidence.

Integration: New backup/DR PDFs or doc captures should activate into this hub + Backup and disaster recovery package — smart farm stack and the Backup / DR — official documentation cluster Evidence summary—not source-note-only when they change restore order or tier labels.

Start here

Reader goal Open
Full doctrine (backup vs sync, tiers, parallel tracks, read order) Backup and disaster recovery package — smart farm stack — canonical spine (page_subtype: operational_guide)
Incident: what to restore first Disaster recovery decision rules — farm edge stack
Prove backups work Runbook — backup validation and recovery drill
Official doc pointers + vault captures Backup / DR — official documentation cluster

Canonical (durable scope)

Page Role
Backup and disaster recovery package — smart farm stack Navigation spine, package map, non-negotiable distinctions, read order
Restore and recovery tiers — homelab farm systems Tier 0–3 labels; RPO/RTO worksheet
Backup strategy comparison — farmOS, homelab, PostgreSQL, containers Logical vs volume vs container patterns
Kubernetes platform backup / DR — Pi fleet, k3s, Longhorn Integration: parallel tracks (app / Longhorn / etcd / Rancher / secrets)
Disaster recovery decision rules — farm edge stack Failure classes, restore order, execution alignment

Entities (vocabulary): Backup and restore tier labels — farm stack, Edge cluster storage roles — homelab / farm stack.

Supporting analyses and sequences

Page Role
Central vs local backup scope — farm edge stack What must be central vs queued at edge
Raspberry Pi k3s fleet — backup and restore sequence Ordered steps with platform guide
Off-grid implications — backup and networking choices Power/WAN vs backup windows
How to provision k3s, Longhorn, and Rancher on a Raspberry Pi fleet Provisioning context (backup chapter inline)