I am implementing a backup solution for a small webserver. So far, the tools I plan to use:
- zfSnap
- rclone
I want to zfs send an archive of the latest webserver snapshots to another HDD, then sync to cloud (rclone). I am missing a replication tool that does:
and manages the zipped archives on the backup drive, ie. sends the latest snapshot, deletes the old ones.
Before writing a script for this task, I was wondering if there was any tool fit for the job, that I may have missed? I came accross sanoid, zxfer, znapzend and others, but they don't seem to handle the making of single file backups. I don't see the appeal in replicating the filesystem as is (with incremental snapshots, etc.) on the backup drive for this particular application. Although, even if I eventually choose to replicate the filesystem (as opposed to a compressed snapshot stream), I still need to archive the latest snapshots to another directory before syncing it to the cloud.
I have seen the requests for a "zfSnap send" feature, but I am not sure if it was ever added / still needed.
- zfSnap
- rclone
I want to zfs send an archive of the latest webserver snapshots to another HDD, then sync to cloud (rclone). I am missing a replication tool that does:
zfs send zroot/webserver@snapshot | gzip > /backup/archive.gz
and manages the zipped archives on the backup drive, ie. sends the latest snapshot, deletes the old ones.
Before writing a script for this task, I was wondering if there was any tool fit for the job, that I may have missed? I came accross sanoid, zxfer, znapzend and others, but they don't seem to handle the making of single file backups. I don't see the appeal in replicating the filesystem as is (with incremental snapshots, etc.) on the backup drive for this particular application. Although, even if I eventually choose to replicate the filesystem (as opposed to a compressed snapshot stream), I still need to archive the latest snapshots to another directory before syncing it to the cloud.
I have seen the requests for a "zfSnap send" feature, but I am not sure if it was ever added / still needed.