Homelab Storage You Can Afford to Lose

Storage is where lab budgets go to die, because the advice is written for the restaurant, not the kitchen. A NAS, mirrored drives, and a backup server protect data — but part one established that a lab’s data is mostly supposed to be disposable. Buying protection for throwaway state is the single most common overspend after the rack.

The two piles

Pile one: rebuildable. VM disks, container images, model weights, media you can re-download, every experiment. If the SSD died tonight, you would lose an evening reinstalling — and part three made even that cheap, because the VMs are snapshots and templates now. This pile needs capacity, not protection. One SSD. Done.

Pile two: irreplaceable. Configs you hand-tuned, notes, anything you made rather than downloaded. On a lab this is usually gigabytes, not terabytes — small enough that protecting it properly costs almost nothing:

1. Get it off the machine. Proxmox’s built-in backup job to any second disk — a cheap USB drive is genuinely fine here — plus a copy somewhere that is not in your house. For gigabytes, free cloud tiers or a repo cover it.
2. Automate it. A backup that depends on remembering is a backup that stops the week you get busy.
3. Restore one thing, once. An untested backup is a hope, not a backup. Restoring a single VM from the backup file is a ten-minute drill that converts hope into knowledge.

• RAID as backup. Mirroring protects against one dead drive. It faithfully replicates deletions, ransomware, and your own mistakes — which are the actual threats to a lab. Redundancy is uptime insurance, and a kitchen does not need uptime.
• The premature NAS. A dedicated storage box is a fine part-eight project. Bought at part five it is an expensive external drive with a louder fan.
• Backing up the rebuildable pile. Nightly images of disposable VMs fill the backup disk in a month, and the job you then disable was the one protecting pile two.