Axel Burri

This should work, did you try it by now? (sorry for the late reply) You can use `btrbk run` (and have it complain about missing target disk if not connected,...

> When target disk is not connected, btrbk.service will logged as failed in journal but local snaps are indeed created. Ah, right. btrbk exits with a different code (10 =...

See discussion: #230 *Subvolume wildcards are not recursive*

I suspect you are using btrbk < 0.28.0 on your server. On earlier versions, the `target` option requires a target-type, which defaults to `send-receive` as of btrbk-0.28.0. Try: ``` target...

Sorry for the late reply, I kind of missed that one. The difference is that one defines a duration in which to keep all backups (e.g. if you run btrbk...

btrfs had some issues in the past with send/receive on files with linux capabilities, I remember a couple of posts on the btrfs mailing list regarding this, and having trouble...

Had that in mind for a long time, not implemented yet as it's not _that_ simple (I think). As a workaround, what you can do is to snapshot (or move)...

I'm currently working on some refactoring/consolidation of code in the [archive-refactoring](https://github.com/digint/btrbk/tree/archive-refactoring) branch. Most things work already as expected, e.g. you get a `--exclude` cmdline argument which excludes a filter argument...

Thanks for the insight! It might be worth mentioning in the FAQ, but if I understand it correctly what you are describing here is: "if you follow the grub docs,...

you can specify `group` for this in btrbk.conf, see: https://github.com/digint/btrbk/blob/master/doc/btrbk.conf.5.asciidoc#grouping-options also look at the `noauto` option, this way you can trigger section on-demand (e.g. `btrbk run mygroup`)