this post was submitted on 27 Nov 2023
2 points (100.0% liked)
Data Hoarder
24 readers
1 users here now
We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time (tm) ). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
founded 10 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ehh better to nag when something goes wrong rather than expecting me to notice something suddenly isn't there.
...and on top of this, also something that repeatedly warns when a successful backup wasn't performed within the last X days.
As sometimes the issue is that the backup just never triggered to start in the first place.
Also saves time looking into old warnings that have since come good.
Sucks that so many systems don't do this. I ended up writing my own thing that wraps all my cronjobs etc, and sends the exitcode + output to one of my web servers. Every type of "checkin" has an expiry period so that it's marked as an "expired" form of failure if it just hasn't been heard from within X hours/days.
Currently got 870 things doing regular checkins. Really sucked handling that in the past just using emails, which didn't even get sent if the thing didn't run in the first place, and didn't tell me not to bother looking into it if it was already working again since the email sent.