Days sheltering in place: 124
Keyboarding: a new bar of the west world theme
I finally watched The Lion King, meh, it was OK. Bambi all over again with Disney killing off animals' parents before their time. Really don't see what all the fuss was about, still, at least I know I wasn't really missing anything all these years.
Scribblings rule on backups: You always need N+1 systems, where N is the number of backup systems you currently have.
Tonight, one of my backup systems failed. Which is OK. It's why you have planned redundancy to avoid a single point of failure. Also, this is probably my least useful backup - I would use it if I absolutely needed - and finally, this happens about once per year.
This is my TimeMachine backup to a network drive. With it I can perform a full restore of my system and it is never more than a few hours old. The problem is TimeMachine has an architectural problem. If it finds a problem with your backup archive, it doesn't try and fix it, it throws it all away and starts again. I'm happy that it is looking for coruption, but sad that it can't at least attempt to fix it.
I also have a TimeMachine backup on a local drive, plus an ARQ backup on a local drive, well two local drives, plus a cloud drive (wasabi), plus I have an ARQ Cloud Backup, and finally I always have a reasonably recent SuperDuper clone of my main drive. Single point of failure, no not me.
In the scheme of things if I need to recover anything the TimeMachine Network Backup would be the last port of call, but one-day I'll need it, and I'll be happy it's there - well, actually, a lot of shit has got to have hit a lot of fans before I use that backup, but still, it'll be there if I need it - unless it corrupts itself again of course.
Redundancy is important for backups. Have a local backup, have an offsite backup. Ideally have two of each. Then see the rule above.