Axel Burri

> Is there a specific reason for keeping them open? No. Point is that people very rarely close the tickets themselves, and it's already a lot of work for me...

btrbk needs a timestamp, which is set on the subvolumes created. Supporting configurable naming schemes would be pretty hard to implement, and would probably need a major redisign. > For...

I have implemented "timeshift-aware parents" in the [action-cp branch](https://github.com/digint/btrbk/commits/action-cp). Like action "archive", `btrbk cp` does not need any configuration (but takes some global config into account, like ssh_user etc.). Try...

I think the "--recursive" option needs some more testing, not sure what happens here in your case. Try passing all snapshot sources, e.g. ``` btrbk cp timeshift-btrfs/snapshots/* ssh://dest ``` Thanks...

I kind of agree with what you say. For the examples in the documentation I would say it's ok, at least I would not know what other directory I should...

I will need to refactor `btrbk archive` for this. I started working on this a while ago, but it's not finished yet... Sorry for the late reply, was very busy...

Design goals for refactored `btrbk archive` are: 1. Use same code base as `btrbk resume`: currently `archive` follows its own code path, even if 90% is more or less identical...

> But from what I learned, cannot be something that is not configured, it cannot be some foreign target not mentioned in btrbk.conf. This is not true. The target directory...

I regard it pretty dangerous to automatically restore from backups: e.g. many people backup their root file system, and this is not trivial to restore. Also there are many scenarios...

See this comment: https://github.com/digint/btrbk/issues/161#issuecomment-317712919 You are right, it would make sense to add this to a FAQ entry. I'm not really happy with my `rsync` approach to check all files...