4 ms·
Sanoid seems like a great tool. It was at the top of my list when I was looking for this kind of solution. I ended up going with zfs_autobackup - https://githu
by mckmk 7y ago
Sanoid seems like a great tool. It was at the top of my list when I was looking for this kind of solution.
I ended up going with zfs_autobackup - https://github.com/psy0rz/zfs_autobackup https://github.com/psy0rz/zfs_autobackup because it doesn't need anything set up on the computer to backup. Just a script on the backup server that does pull backups.
I'm not trying to hijack the thread but I've often appreciated links to similar software in threads like this.
- waz0wski 7y agosanoid works great, used it for quite some time and the creator is actively involved in the zfs community in the spirit of link sharing for other tools, I've been moving many of my personal infrastructure & tools to golang-based apps, and I started using this for zfs replication https://github.com/zrepl/zrepl https://github.com/zrepl/zrepl No issues thus far in about 6mo of usage for local-and-remote snapshots
- Youden 7y agoThe issue I have with that is that if everything is done by the backup server, it has the ability to both create and destroy (prune) datasets (snapshots), which means it has the ability to erase all of the data and all of the backups. One thing I like about Sanoid/Syncoid is that if you set up Sanoid on both sides and use Syncoid to pull, the backup server only requires the ability to send snapshots (which you can configure with "zfs allow"). The backup server also doesn't require root in this case. This means neither server can delete the other's data. And you still get all the automatic snapshot creation (done on the primary server) and pruning (done on both servers).