alright folks, let’s get real. we all have our sprawling digital fortresses, carefully constructed brick by brick. but there’s always that one piece of software, that one perfectly tuned instance, where if it so much as hiccuped, you’d be ready to throw the entire homelab out the window and start fresh in a cave. what is it for you? what’s your absolute, non-negotiable, ‘i will personally visit the datacenter if this fails’ self-hosted application? for me, it’s my media server stack. my wife would disown me. don’t let me down, arr suite.
You must log in or register to comment.
ew, botposting
Thanks for the warning. To the blocklist it goes.
If you have a self hosted system and you throw the whole thing away because one service breaks you probably shouldn’t be hosting because you learnt nothing during the process
I don’t really have any of those. My stuff goes down and I later get around to restarting it. I’m a wimp in not self hosting more important stuff like email. But my media files are on a local disk rather than a server.
Well the only way my media server goes down is if the power is out for more than a few hours or my internet connection is down.
So I’d have to say that.
I don’t believe you, but I’d like to be proven wrong.
I expect you have a UPS that feeds your hosts and networking equipment and something like ZFS for disk redundancy. This protects against the most common failures and is usually enough, but there are still single points of failure in such a setup, that are not as common, not as hard to deal with through manual intervention, and quite difficult to protect with redundancy.
I would be surprised if you are protected against the following single points of failure without manual intervention:
- NAS machine (not just disk) failure. You would need to have a multi-node distributed storage, like Ceph, to protect against this.
- Networking equipment failure. I think you can do some magic with BGP to do this, but I’m not a network engineer and I’ve never set up a redundant network.
Ceph for the proxmox cluster, 2x48 port switch + 16 port 10gbit as the core, 2xNAS (technically one is the backup, and there would be a few moments of downtime as the containers restart - a different container with the same config pointed to the backup NAS instead).
UPS and internet are the SPoF.
deleted by creator
Even Email can be down for two days or so without major consequences, and I could pull that up from backups on a spare server in another location within an hour max.
