The 3-2-1 backup rule gets repeated so often it’s turned into a slogan: three copies of your data, on two different media types, with one copy off-site. It’s good advice. It’s also advice that was mostly written with a few hundred gigabytes of irreplaceable photos in mind, not the 50, 100, or 200TB array a serious data hoarder ends up running. At that scale, “just keep an off-site copy” stops being a checkbox and starts being a real infrastructure and cost decision. Here’s what each part of 3-2-1 actually means once your data won’t fit on a shelf of external drives anymore. ...

There’s no single right NAS OS, there are three genuinely different philosophies, and the “which one is best” debate mostly happens because people are comparing them against different priorities without saying so. If you know what you’re actually optimizing for, capacity efficiency, mixed-drive flexibility, or full control, the choice mostly makes itself. Here’s what each one actually trades off. TrueNAS: ZFS-first, and it means it TrueNAS (SCALE, the Linux-based version, is the current default recommendation over the older FreeBSD-based CORE for most new builds) is built entirely around ZFS, and that shapes everything about how it works. You get real checksumming, snapshots, and the RAIDZ redundancy levels covered in the ZFS pool layout guide elsewhere on this site, all through a genuinely mature, well-tested web UI with a large ecosystem of documentation and community troubleshooting behind it. ...

Most homelabbers can tell you their NAS’s total raw capacity down to the terabyte and argue at length about CPU generations, but ask what the whole rack costs to run for a month and you’ll get a shrug. That’s understandable, electricity is a background cost that never shows up as a single line item the way a drive purchase does, but a lab that runs 24/7/365 adds up in ways a lot of people never actually check. Here’s how to measure it for real, where the draw actually comes from, and what’s worth changing. ...

The first time most people find out a self-hosted service is down is when someone tries to use it and it isn’t there. That’s the wrong order. If you’re running more than two or three services at home - Immich, a media server, a reverse proxy, whatever - you’ve already got enough surface area for something to quietly die on a Tuesday and stay dead until you notice by accident. ...

Most media library problems aren’t storage problems, they’re organization problems. Enough drive space and a working RAID array doesn’t help if your media server can’t identify half your files, or if a “quick reorganization” three years from now turns into a multi-day project because everything’s tangled together. Here’s a folder and naming structure that holds up regardless of which media server you’re running, and why the small decisions you make on day one matter more than they seem to. ...

Proxmox will let you install onto ZFS during setup with a few checkboxes and move on with your life, and that’s exactly how a lot of people end up with a storage layout they didn’t actually choose. ZFS is the best storage option built into Proxmox for most homelab setups, but it comes with tradeoffs that are easy to ignore during install and expensive to fix once you’ve got VMs and containers living on top of it. Here’s what the pool layout choices actually mean, what ZFS does to your RAM, and how to pick a shape you won’t be re-doing in six months. ...

10GbE gear has gotten cheap enough on the used market that it shows up in nearly every “should I upgrade my network” thread on r/homelab, usually with someone insisting it changed their life and someone else insisting it did nothing for them. Both are usually telling the truth - it depends entirely on what’s actually slow in your setup right now. Here’s how to figure out which camp you’re in before you buy anything. ...

Every self-hosted setup eventually hits the same wall: you’ve got four, six, ten services running on different ports, and typing http://10.0.0.50:8096 from memory has stopped being funny. A reverse proxy fixes that - one entry point, real hostnames, automatic TLS certificates, and a single place to manage access instead of juggling port numbers. The question isn’t whether you need one. It’s which one. There are more options than these three, but Nginx Proxy Manager, Traefik, and Caddy cover the vast majority of homelab setups for good reason - they’re mature, well documented, and each represents a genuinely different philosophy about how a reverse proxy should work. Picking the wrong one isn’t fatal, but re-migrating a dozen services to a different proxy after the fact is a weekend you don’t get back. ...

Somewhere in every data hoarder’s history there’s a drive that seemed like a great deal, went into an array without a second thought, and then turned a routine rebuild into a multi-day nightmare or a dropped drive. Almost every time, the actual cause is the same three letters: SMR. This isn’t an obscure edge case. It’s happened at scale, publicly, more than once - manufacturers quietly shipping SMR drives in product lines everyone assumed were CMR, and the data hoarding and NAS communities finding out the hard way when arrays started misbehaving. If you’re buying drives for a NAS, a ZFS pool, or any kind of RAID array, this is one of the few things worth actually understanding before you buy, not after. ...

Backups are the thing every homelab guide tells you to do and almost nobody actually verifies works until the day they need it. Proxmox makes this easier than most platforms because it ships a real backup product, Proxmox Backup Server (PBS), instead of leaving you to bolt one on yourself. Here’s how to actually set it up, what it buys you over the built-in vzdump backups, and the one step most people skip that makes the whole thing worthless if you never do it. ...