It's not perfect, but this isn't a replacement to the tried and tested, fail-safe method of backing things up. Any decent safety solution needs to be multi-tie

It's not perfect, but this isn't a replacement to the tried and tested, fail-safe method of backing things up. Any decent safety solution needs to be multi-tiered; I backup my configs to Git, make a backup of the now read-only filesystem after you've set this up and put it somewhere safe, and when the worst happens, restore to a new card, or build from the backup configs. I don't keep anything critical on Pi SD cards, that's why losing so many cards has been little more than an inconvenience. For read-only filesystems, a simple copy of the card in multiple locations, on and off-site is good, for read-write, backups configs to Git, RAID arrays and off-site. If the system is time-critical, first, I would suggest not running it on a Pi, use something more reliable (I moved my home automation to a NUC because it's more reliable than the Pis were), or, use multiple Pi's in redundancy, even half a dozen Pis is cheaper than a NUC if your use-case supports distributing the load.