9 docs tagged with "backup"

Reusable Kustomize component that wires a per-app k8up `Schedule` into the app's namespace — pointed at the cluster's Restic repository on Hetzner S3, with the standard hourly / daily / weekly / monthly retention.

Two encrypted, offline WD Elements drives that form the cold tier of the 3-2-1 backup strategy.

Backup and restore recipes for in-cluster PostgreSQL using kubectl, pg_dump, and psql.

Step-by-step guide to restoring a PostgreSQL database dump into a CloudNativePG cluster using k8up, Restic snapshots, and pv for streamed progress.

From "production is gone" to "Talos reinstalled, Flux reconciled, persistent data restored" — the documented end-to-end recovery path for the homelab.

Off-site Synology DS723+ NAS with RAID 1 and BTRFS snapshots, replicated continuously via Syncthing as the hot backup tier.

Self-hosted photo and video timeline with automatic mobile backup, on-device face / object detection, and shared albums — the homelab's Google Photos replacement.

Continuous, peer-to-peer file synchronisation — the engine that keeps the off-site hot-storage tier (Maresa Synology) in step with the primary datasets.

How a byte written to a Longhorn PVC ends up in three places — warm (Restic to Hetzner S3), hot (Syncthing to the off-site Synology), cold (encrypted WD Elements drives) — and what it takes to restore from each.