zfs_autobackup VS zrepl

I recommend you to get familiar with https://github.com/psy0rz/zfs_autobackup/wiki first and then use the configuration you are happy with in my script.

I have a small home server running Ubuntu Server with a ZFS file system. To back up my files and use snapshots, I am currently using zfs-autobackup, which is easy to set up and works really well for ZFS. However, zfs-autobackup does not provide any information on files or folders that have been created, updated, or deleted from previous backups. While I am not too concerned about newly created or updated files, I would like to know which files have been deleted compared to the previous backup. Ideally, I would like to be able to see which files have been deleted before the backup takes place, so I can recover any unwanted deletions before it's too late.

as described here https://github.com/psy0rz/zfs_autobackup/issues/170

Use ZFS Autobackup https://github.com/psy0rz/zfs_autobackup or ZFS send and receive to create a clone of an existing pool on a new system https://www.thegeekdiary.com/zfs-tutorials-creating-zfs-snapshot-and-clones/

I just went back to sanoid. I have also looked at zfs-autobackup and might give that a try. I've been combining sanoid/syncoid with this script to clean up snapshots

If you want it to work really well in all circumstances, it WILL get complex. I tried to keep the code as readable as i could though. There where many refactors. Check it out: https://github.com/psy0rz/zfs_autobackup

Also have a look at https://github.com/psy0rz/zfs_autobackup .

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.