Yannick Boetzel

Development on pyznap is pretty much on hold atm, I don't think I will have time to work on this in the near future. But I can keep it open...

I agree with xylle, I'd rather keep it simple than have too many options that complicate the code. Also, following the reddit thread I think the reasoning mercenary_sysadmin gave to...

Sorry, I totally missed this question. I never used encrypted datasets, so I'm actually not too familiar with how they work with zfs send/recv. Would it also work if you...

Hm no idea what exactly is causing this. I never worked with encrypted datasets, so no experience there on how exactly they behave with zfs send/recv.

You should create a second policy for your backup server, something like: ``` [default/data] frequent = 4 hourly = 24 daily = 7 snap = no clean = yes ```...

There is no easy way, no. You could have two different config files, one for frequent+hourly snaps and one for the daily snaps. Then you run the daily one only...

In that case it's best to have two different policies. Since the settings in the config are recursive, you could do something like this: ``` [ssh:22:[email protected]:default] frequent = 4 hourly...

Hi Thanks for the PR. It will take me a bit of time to go through this, as there are quite a lot of changes.

There is currently no way to avoid this. `pyznap send` will send all snapshots, you cannot exclude hourly/frequent ones. So send will always send those and snap will immediately delete...

pyznap unmounts the destination datasets before sending, see #44. You can easily remount them with `zfs mount path/to/dataset`. I haven't had time to look into the issue more. It shouldn't...