…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.
No Backup, No mercy
When you’re performing a backup, a backup alarm (like on certain vehicles) should be sounding. That would remind you of what’s happening.
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.