Halfwalker

Bingo ! That was it - replicating the **halflapp** dataset now. I'll post here if the **ryzen2** one fails ``` Replication: Attempt #1 Status: fan-out-filesystems Started: 2023-10-14 16:08:12 -0400 EDT...

OK, the **ryzen2** one seemed to backup fine, so that's good. I set up a timer to trigger backups, came back after a while to see zrepl was stuck in...

Point of interest - it's definitely the replication from **ryzen2** to **bondi** that kicks that spl `panic` - soon as it tried to replication it kill zfs on **bondi**. I...

Doh - just remembered, I had NOT replaced the `zrepl` binary on **ryzen2** ... Did that, but it still causes the panic when replication starts. **bondi** is ubuntu 18.04, using...

That seems to have done the trick ... Changed the **bondi** config to point to a new dataset. Replication from both **ryzen2** and **halflapp** to **bondi** worked fine with the...

Sort of answering my own question above ... From the docs https://zrepl.github.io/quickstart/fan_out_replication.html it appears that each pull client wants its own source job on the server. But the config seems...

Yup - could do that. I tend to like the explicitness of `type: disable`, but omitting it works fine (for me) :stuck_out_tongue_winking_eye:

I use a threshold hook script to decide whether or not to snapshot. It looks at a configurable property to determine if at least that many bytes have been written...

Yup, I currently use `err_is_fatal=true` in the zrepl job config for the hook. I do like the idea of formalizing things in the yaml, but also with the capability to...

Definitely better with those two `SystemCallFilter` lines commented out. It keeps thinking that the target backup pool has been modified though ``` ╔══════════════════════╗┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ ║jobs ║│Job: home_to_backup │ ║├──backuppool_sink ║│Type: push...