Good DevOps practice is to build your systems with failure in mind.

What you build *will* break. That's inevitable. So what you build should be built to be quickly recoverable.

You should have good disaster recovery plans.

You should have backups.

Your deployment should be automated, and use infrastructure-as-code extensively.

#DevOps #MastoAdmin

If you do not schedule maintenance, your systems will schedule it for you.
@aurynn And sometimes thatโ€™s the easiest way to get it done, speaking as someone whoโ€™s worked with a lot of decision-averse managers
@ghost_bird oof, I'm sorry to hear you've had that struggle
@aurynn guaranteed, the untested DR plans always fail.
@rich Untested plans are just hopes and dreams
@aurynn ominous
@lawlznet It comes from an older idea of factory machines that do not have scheduled maintenance will schedule it for you
@aurynn lol no worries, i got the joke. xP

@aurynn I have reckons about automation...

okay it might almost be a thesis...

@aurynn and for your truly ancient legacy systems where spiders dwell, have some sort of break glass documentation for what to do when it does that thing it does once every 7 years because Terry (who knew how to soothe it) has left.
@annamal tested DR documentation is important
@aurynn especially in a disaster prone country :)
@aurynn indeed. The same for our personnal computers and smartphones
@aurynn Considering making this post my team's mission statement.