Closed pterrien closed 1 year ago
yes thats the way to do it: the thinner will only remove snapshots that belong to that specific backup. So multiple jobs wont bother eachother.
the documenation indeed wasn't clear about this, so i added it:
https://github.com/psy0rz/zfs_autobackup/wiki#multiple-backups-of-the-same-data
Hi,
First, sorry if this question has been answered already, I searched the docs and issues but could not find the answer. And I haven't had the opportunity to test it myself yet, as I'm reorganizing my pools for the moment... but I will surely give
zfs-autobackup
a try, as I find it very well designed, the documentation is great and the code seems pretty clean!Let's say I have a dataset on my server, on which I would like to define 2 separate tasks, one being scheduled daily to backup to my workstation, the second being an on-demand backup to a removable drive (on the same server). From my understanding, I will define 2 user properties, eg
autobackup:scheduled
andautobackup:removable
, will schedule a backup task for the former, and a snapshot one for the latter. And when my removable drive is plugged in, I will then launch a backup forremovable
. Correct?My question is: how will
zfs-autobackup
manage the common snapshot for both the tasks, especially if I use the thinner? Will it be able to differentiate the snapshots for each backup task, setting the right holds so that myremovable
target never gets out-of-sync? What would be the proper way to do?Thanks.
Edit: changed the use case a bit, to have
scheduled
backup to my workstation instead of locally. Otherwise I believe I could cascade, and set theautobackup:removable
property on thescheduled
target, am I right?