nostr:npub1fc3et0s4tpl7a90tu235rqmlnkrendezmf6n3jjx7u50stqzkldqfehhl3 Servers are a service. But why should it change anything? I take comfort in the fact my company is financially backing the server. We are a team of 11 people. They don't currently take part in any other way than to be there.
It's not the best practice, but it can work when you have a passionate and committed person as admin. I even know a single person hosting companies who have been fine for decades. In the overall picture it is not very wise, but it can work if the contingency plan is in place.
We have a two person system administration in our company and large corporates trust with us their servers. We do have a team working for us in the data center though, but only two people are the main responsible ones. It's been all fine for 10 years now.
nostr:npub1cmgqvz7xr07euwkum3mjghjqcu4d3k2fcyf6g4uwwe5ggnd6fetq0wrzd2 Two people are better than one, so that is good, of course.
Sysadmins know all about how well single points of failure work in the long run and it is no different with the human resource aspect too. I am not talking about finances, scale or passion here. I am talking about when life happens and there is no human backup that has SOP and is ingrained in the setup/support actively.
nostr:npub1fc3et0s4tpl7a90tu235rqmlnkrendezmf6n3jjx7u50stqzkldqfehhl3 There are always options. Most of the things can be automated. Servers are usually running without a human. I don't take that gloomy approach. If I was to die, there is not much I can do about it.
