zrepl VS zfsbackup-go

Lastly there is zrepl. This is an automatic snapshot creation, pruning and replication daemon. It lets you automate the creation of ZFS snapshots at specific intervals, apply a retention policy to them, and replicate them out to a remote system with ZFS, like a NAS with TrueNAS on it.

I run it in a FreeBSD jail and take frequent ZFS snapshots using zrepl. I’ve had to restore after failed updates and it worked flawlessly.

As others have noted, I use syncoid but zrepl is an alternative that could be considered.

I’m going to throw out Zrepl again because it’s amazing: https://zrepl.github.io/

Current idea: We offer some form of container each other, where we have that zvol mounted somewhere for the replication use. This would mean that I could create an "inside zfs" where I create a filebased zpool. How is performance on a filebased zpool? (Although it is technically not so important that it performs critically, just trying to find the - or one of - "best" ways). Then we would offer each an ssh endpoint into that container (It doesn't have to be ssh, but it is so far convenient to setup and resilient to be open to the public). And my current plan is to use zrepl (https://zrepl.github.io/) to organise replication from my home server to this "inside" zpool.

Z3 doesn't seem to be maintained. This script seems to be a oneoff. ZFSBackup Go seems more full featured but also unmaintained and out of date as well.

6) build zfsbackup-go https://github.com/someone1/zfsbackup-go

I have a similar setup, but I use DoH-server to pass queries to pihole. Pihole is not accessible to the world on UDP 53. I guess this could be abused with a TCP reflection attack, but I don't think anymore so than just having an open web server, which I also have. That's sort of the whole point of a web server.

i’d also like to share: https://github.com/someone1/zfsbackup-go (can’t vet it fully, it seems promising and i started down the path but didn’t complete)