If you have a file system like Zfs that gives you snapshots, you would not need a tool like oP’s to make multiple copies. You can periodically do rsync(think cron job), and literally include the —delete flag such that rsync tries to replicate source and destination. The trick is to keep making cheap snapshots on ZFS such that those deletions are captured in the snapshots. When you need a file that was deleted a year ago, or as of a year ago, simply browse to the snapshot of that time, and get your data back.
Zfs stores the delta only anyway, so they are quite cheap.
This is how I backup the primary storage of a huge HPC cluster - 2.5 Petabytes of research data.
Comments
If you have a file system like Zfs that gives you snapshots, you would not need a tool like oP’s to make multiple copies. You can periodically do rsync(think cron job), and literally include the —delete flag such that rsync tries to replicate source and destination. The trick is to keep making cheap snapshots on ZFS such that those deletions are captured in the snapshots. When you need a file that was deleted a year ago, or as of a year ago, simply browse to the snapshot of that time, and get your data back. Zfs stores the delta only anyway, so they are quite cheap.
This is how I backup the primary storage of a huge HPC cluster - 2.5 Petabytes of research data.
Even better, automate snapshot management (with optional off-node sync) with sanoid/syncoid [0] (Perl) or pyznap [1] (Python).
[0]: https://github.com/jimsalterjrs/sanoid
[1]: https://github.com/yboetz/pyznap