| ▲ | tristor 5 hours ago | |||||||||||||
I use the 3-2-1 strategy for backups. I keep one copy off-site by using cloud backups, currently I primarily use Backblaze for that purpose but am considering alternatives for several reasons. I keep a second copy on an external SSD via Time Machine, and I keep one copy on-device. I'd like to use network Time Machine to get rid of the inconvenience of having a bunch of USB external SSDs floating around, especially since none of them are large enough to backup my entire drive if I get close to filling it. I appreciate the perspective, I definitely take backups seriously for my photography. | ||||||||||||||
| ▲ | oarsinsync 4 hours ago | parent | next [-] | |||||||||||||
I think a combination of: 1/ ZFS datasets with hourly (or daily) snapshots 2/ Samba with vfs_fruit Gives the peace of mind that even when the sparsebundle shits the bed, you can rollback to a suitable snapshot and only lose a small period of backups, rather than having to lose the entire history and start again from scratch. (I say when, not if, through considerable experience over the last 15 years that it will always, inevitably, shit the bed.) | ||||||||||||||
| ▲ | tedd4u 3 hours ago | parent | prev [-] | |||||||||||||
A 2-drive Synology (e.g. DS225+) in RAID 0 or RAID 1 works fine for this, for 90% less than this beast. Synology documented their optimal settings for Time Machine a couple years ago, too. Hope this is helpful. [1] [1] https://kb.synology.com/en-us/DSM/tutorial/How_to_back_up_fi... | ||||||||||||||
| ||||||||||||||