3 ms·
> with one sys-admin dealing with it, And if that one sys-admin wants to go on vacation? Or travel away from a computer? Or takes another job? You can never h
by PragmaticPulp 5y ago
> with one sys-admin dealing with it,
And if that one sys-admin wants to go on vacation? Or travel away from a computer? Or takes another job?
You can never have “just one” admin handling a server and being on-call 24/7.
Would you really want a job where you could never, ever be away from a computer because you’re the only on-call person? This doesn’t work.
- new_guy 5y ago> Would you really want a job where you could never, ever be away from a computer because you’re the only on-call person? This doesn’t work. Works fine for me. $20K a month for two people doing f*k all is insane.
- Melkman 5y agoWhy would it be necessary to have an engineer on call 24/7 ? If you do your risk calculations and an outage of 12 hours is acceptable in the expected frequency you just let the engineer have a nice evening and night an deal with the outage in the morning. If outages are only to be expected once a year an you can tolerate 48 hours of outage you don't need any on call engineer. Most outages are cause by changes. You can test those and plan putting these in production and have elevated monitoring after this to catch problems early. Only problem remaining is hardware outages. And those are very rare as long as you do decent lifecycle maintenance. As others said before. Not everyone is Google or Amazon and needs 99,999% uptime.