zfs_autobackup VS zfs-replicate

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 .

Take a recursive snapshot. Use the right send/recv options to get everything to the new pool and maintain encryption. You might try https://github.com/rlaager/zfs-replicate but seriously, I have not tested exactly this scenario, it might break, and if it does, you get to keep the pieces (don't blame me). If you go this route, I'd love to hear if it worked.