Skip to content

Backups & Disaster Recovery

Current state: degraded

Both pieces of backup-relevant hardware are currently down:

  • Cubi N (Proxmox Backup Server) — degraded
  • Beelink (mini NAS) — degraded, repair pending

Until both are repaired, treat this as no working backup path. Restore these first before anything else on the roadmap — everything downstream depends on them.

What needs backing up

General

  • VS Code config
  • SSH config
  • Tailnet ACLs (with change history/reasoning tracked, not just the file)
  • All Docker Compose directories
  • All app data
  • Various other config files

Sensitive (handle with more care — encryption, tighter retention/access)

  • Bitwarden/Vaultwarden vaults
  • Email client settings
  • Secrets: SSH keys, Cloudflare tokens, other API tokens, *arr-stack API keys
  • Email
  • Immich photo library
  • Notes

Open questions

  • No backup destination, schedule, or retention policy is documented yet — once Cubi N is back up, this needs to be defined (local PBS retention + an offsite copy, at minimum for the "sensitive" tier)
  • No restore has ever been tested/rehearsed
  • Where the "sensitive" tier gets encrypted at rest, and with what, isn't decided yet