Axel Burri

If changing to `/usr/bin/env perl`, we would require to have a valid PATH environment, pointing to wherever `perl` is located. This is not always the case, e.g. quite common within...

I'm not aware of pacman hooks, I suspect it should be as easy as running something like: ``` btrbk -c /usr/share/btrbk/contrib/pacman.conf ``` Events can be modeled using groups, e.g. specify...

> not sure how unkosher that would be.. I will interrupt cron one for now. From a btrfs point of view, this should be kosher ;-)

I think this is all well described in [btrbk(1), Action "run"](/digint/btrbk/blob/master/doc/btrbk.1.asciidoc#actions): > Step 2: Create Backups > [...] After comparing the backups to the source snapshots, btrbk transfers all missing...

> Did you check if btrfs send correctly handles unreliable connections? I did some tests, but not that thorough as btrbk uses ssh which I fully trust: ssh either provides...

Same behavior, ssh connections do indeed survive closing / reopening of interfaces (just checked on both ssh client as well as server). However, if I remember correctly, systemd (which I...

Yes, the upload process will be resumed on next run. In order to make sure that btrbk does not abort on "garbled" subvolumes, some people always do a `btrbk clean`...

You are right, the term "resume" is a bit misleading here: - In the btrbk docs, resume refers to `btrbk resume` action, meaning "resume missing backups, i.e. re-sending of snapshots...

> WARNING: ... sh: ssh -i /root/.ssh/id_rsa [email protected] 'readlink -v -e /backups/thinkpad' > WARNING: ... [ERROR] Unrecognized command, bailing out! looks like your system at 192.168.1.10 does not have the...

I think having separate lockfiles would be more confusing than useful. There might be some use cases where the behavior you mention is not desired. What you describe can be...