A Proxmox Backup Server job backs up entire VMs and containers, which covers you if a whole box dies. It does not, by itself, give you a clean, restorable copy of the actual data living inside your self-hosted apps, the Vaultwarden vault, the Paperless-ngx document store, the dozen docker-compose.yaml files and their bind-mounted config directories that took real time to get right. If your backup strategy stops at the hypervisor layer, you’re covered against hardware death but not against the more common failure: a bad update, a fat-fingered docker compose down -v, or a config file you meant to edit and instead overwrote. This is where an app-level backup tool earns its place alongside whatever you’re already doing at the VM/container level. ...

Proxmox hands you two completely different ways to run a workload, LXC containers and full VMs, and the “New CT” and “Create VM” buttons sit right next to each other in the UI like the choice barely matters. It matters. Pick the wrong one for a given workload and you’ll either waste resources you didn’t need to waste, or hit a wall six months in when something a container fundamentally can’t do turns out to be exactly what you needed. Here’s how to actually decide, workload by workload, instead of defaulting to whichever one you set up first. ...

Ask “what should I run Proxmox on” in any homelab community and you’ll get two camps talking past each other, one pushing a mini PC (an Intel NUC-style box, a Beelink, a Minisforum), the other pushing a custom build in a real case with expansion slots. Both are right, for different homelabs. The question isn’t which is objectively better, it’s which set of tradeoffs actually matches what you’re going to do with the box. ...

Run five self-hosted apps and you’ve got five separate logins, five separate password resets, and five separate places an old account can quietly stay active after you meant to lock someone out. Once you cross that threshold, a single sign-on layer stops being a nice-to-have and starts being the thing that keeps your homelab’s security model from turning into a pile of unrelated logins nobody’s actually tracking. Here’s what an SSO layer buys you, and how the two most common self-hosted options actually differ. ...

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. ...