HomelabBackupStrategies
title: Homelab Backup Strategies radar_quadrant: Techniques radar_ring: Assess radar_position: inner
Homelab backup strategies refers to the set of patterns for implementing multi-copy, multi-media, geographically distributed backup pipelines for self-hosted infrastructure. The 3-2-1 rule — three copies, two media types, one offsite — is the baseline. A June 2024 practitioner article at xtremeownage.com documents a concrete multi-layer implementation covering NAS, object storage, VMs, Kubernetes, and desktop devices.
The 3-2-1 rule requires at minimum: three copies of data, stored on two different media types, with one copy kept offsite. For irreplaceable data (photographs, personal records), the author treats 3-2-1 as a floor — maintaining seven or more physical copies is not unusual.
Immutable snapshots prevent administrative error or ransomware from destroying backups before the retention period expires. Applied at every tier: NAS shares (Synology Snapshot Manager), object storage (MinIO immutable buckets via sanoid on ZFS), and iSCSI LUNs backing Proxmox Backup Server. A snapshot that cannot be deleted until a timer expires breaks the ransomware destruction chain.
Peer-to-peer encrypted offsite replaces or supplements cloud storage with cross-replication to a trusted friend's NAS over a VPN tunnel. Data is encrypted before leaving the network so neither party can read the other's backups. Geographic separation ensures a single physical event cannot destroy both copies. This satisfies the offsite requirement without cloud dependency.
Incremental deduplication (Proxmox Backup Server over iSCSI) converts VM backups from full snapshots to delta chains, reducing storage consumption and transfer volume significantly. Point-in-time and file-level restore remain available.
Tier-appropriate tooling:
| Layer | Tool | Key property |
|---|---|---|
| NAS | Synology Active Backup + Snapshot Manager | Immutable share snapshots |
| Object storage | MinIO + sanoid (ZFS) | Immutable buckets, point-in-time rewind |
| VMs | Proxmox Backup Server | Incremental dedup, file-level restore |
| Kubernetes | Kasten K10 / Veeam | Workload + etcd snapshots to MinIO |
| Desktops | Synology Active Backup for Business | Targeted share backup, not full disk |
Placed in Techniques / Assess / inner.
The three non-obvious patterns — immutable snapshots at every tier, peer VPN offsite, and incremental dedup for VMs — are the delta over a naive 3-2-1 implementation. Each addresses a real failure mode: ransomware destroying backups before detection, cloud provider outages removing the offsite copy, and storage cost making VM backups impractical.
Complements the Personal Data Backup Pipeline blip (rclone + cron for file-level offsite sync) with a fuller multi-tier strategy covering VMs and Kubernetes. Inner position reflects direct applicability to any homelab running Proxmox, a NAS, and self-hosted services — which is the target profile for several other blips on this radar.
Trial gate: a backup pipeline covering at least three tiers (files, VMs or containers, and a database) with immutable snapshots at one tier and a verified restore from each.
