> encrypted Time Machine to a network location
this has a bonus feature where it will slowly corrupt itself over time and offer to start a completely new backup instead.
this has a bonus feature where it will slowly corrupt itself over time and offer to start a completely new backup instead.
It seemed to stop killing itself when I moved to a ZFS backed samba share.
Funnily enough I also kept snapshots enabled because I was expecting TM to bork itself eventually, so I could always rollback to a working state but I don’t remember needing to use that.
The only thing that definitely made it worse was smb over openvpn. It'd corrupt itself every couple months instead of once or twice a year.
Before MacOS 27, I was always able to remove the Time Machine destination, replace the corrupted sparse bundle with a fresh empty one, and reconfigure that as the new TM destination. I even made a script for this, so I didn’t have to figure out the terminal commands every time.
Unfortunately the script doesn’t work anymore; it throws ‘error 25’ on my MacOS 27.
What’s weirdest is that, before the corruption, TM backup and restore used to work fine on my MacOS 27. Seemingly the backup functionality works as normal, but setting the TM destination was broken.
And personally I've never had networked backups get corrupted, dunno why.
I suppose HFS+ backups were more finicky over the network as well.