How often do you actually check/audit your backup or storage configs?
Posted by Ok-Tomorrow-7591@reddit | sysadmin | View on Reddit | 11 comments
I ran into this the other day and it got me thinking a bit.
we had everything set up properly at the start, permissions looked fine, configs were clean. but over time a few small changes happened here and there and no one was really keeping track of it anymore.
nothing broke, but when we tried to review things it was already a bit messy trying to figure out what changed and why.
made me wonder how others deal with this.
do you guys actually go back and review configs regularly, or is it more like you only look at it when something goes wrong?
and if you do check things, is it mostly manual or do you have something in place for it?
QuirkyEscalator@reddit
We have a morning check ticket with a checklist of stuff to check. Backups, monitoring alerts, emails, check if logs work, check if automation tasks work etc
gonyoda@reddit
Some jobs by law I had to do it yearly. Others, when it broke.
ellaesheahan@reddit
Honestly most teams say they’ll review regularly, but it often ends up being reactive. The better setup is doing light, scheduled audits (monthly/quarterly) plus automation where possible, things like version control, alerts, or policy checks so config drift doesn’t go unnoticed. Manual reviews still help, but relying only on them usually means you catch issues too late.
hb_2410@reddit
Not yet .....
Vektor0@reddit
AI SaaS sales slop.
tensorfish@reddit
Only checking when something breaks is how backup drift turns into archaeology. Put a boring monthly review on jobs, retention, creds, exclusions and target capacity, then do quarterly restore tests for the systems that actually matter.
rose_gold_glitter@reddit
Once a month and we have to provide evidence to the auditors that we really did it, too.
Mr_Dobalina71@reddit
It’s my full time job, so everyday.
Ok-Tomorrow-7591@reddit (OP)
haha fair, sounds like you're deep in it then, is that mostly manual checking or do you have something in place to keep track of changes?
GigaMonkeh@reddit
After every event where we need to restore and realise something is borked
Ok-Tomorrow-7591@reddit (OP)
yes thats honestly the worst timing for it. everything seems fine until you actually need to restore and then things start showing up.
do you usually change anything after that or does it kind of go back to normal till the next time?