"I don't know if you're just using rsync, but automatically syncing modifications, corruptions and deletions without any kind of retention system isn't a good i

"I don't know if you're just using rsync, but automatically syncing modifications, corruptions and deletions without any kind of retention system isn't a good idea ..." This is, broadly, correct. However, we have been encouraging our customers to configure "dumb" 1:1 mirror rsync jobs to us and then allow the platform to handle all of the retention with the ZFS snapshots. An rsync.net customer configures any arbitrary schedule of days/weeks/months/quarters/years and then we (rsync.net) handle the rotation, retention and maintenance of these snapshots. The benefits of this, beyond the fire and forget aspect, are twofold: First, they are more efficient than typical retention schemes like 'rsnapshot' or "rsync snapshots" since ZFS diffs on a bit basis and not a full file basis - so if you change a file, but only by a little bit, you don't pay the entire size of the files as a penalty in your snapshot size. Second, the ZFS snapshots are immutable. Even if someone steals your rsync.net credentials and wipes out your entire account, the snapshots cannot be changed.[1] Of course you may do whatever you'd like - you can even configure snapshots on an account you use 'borg' with and get very inefficient "snapshots of snapshots". Whatever makes you happy - we just give you an empty UNIX filesystem to do whatever you like with. [1] https://twitter.com/rsyncnet/status/1453044746213990405 https://twitter.com/rsyncnet/status/1453044746213990405