>As a developer, I’ve modified quite a few system files I do as well. Given that such things tend to be more fragile between OS releases though and easy to for

>As a developer, I’ve modified quite a few system files I do as well. Given that such things tend to be more fragile between OS releases though and easy to forget I usually prefer to recreate them for upgrades or reinstalls anyway. Also provides an opportunity to reevaluate them. So these days I think the better way to go about it is with automation as much as possible rather than backups. That said: >It’s one reason I don’t use Backblaze – they refuse to backup system files. Well, you can use something like CCC to image your startup disk to a file somewhere else, and regular BB will cheerfully take care of that. Makes restores mildly more work but not much given that a failure which nukes the system files means having to do some level of reinstall/recover anyway. I use Backblaze B2 though, which has maintained decent pricing vs S3 and is much more natively flexible. Having local systems backup to TrueNAS (or have data folders that just live there) then that go to B2 is another way to handle things. With Apple making custom restores ever more difficult though all that might need some reevaluation too :(. I miss how powerful and pleasant their tools were at one point with no subscriptions or WAN required, and will always be a bit bummed things didn't go the way of adding your own signing to the system image utility, Net Boot/Net Install etc they already had going. Macs were really great to run heavily off a LAN back around 10.5.