TW
Not seen means it was not present in the source files of a backup run, e.g.: - the file was deleted or moved elsewhere - the backup run intentionally did...
@e-ferrari could you solve your issue?
Well, there was a read error on that file, so yes the backup of that file will be incomplete (or even skipped). Retries were implemented a while ago in master...
borg2 is still beta and not suitable for production. also, if the storage system is really down, retries might not help.
Some commands also have json output capability, so maybe you can use that.
Yes, guess we rather provide generic exporting (like json) than supporting misc. more specialised formats (? no idea about what prometheus need) directly.
IIRC, if you use `--log-json`, you'll get all log output as json. Some commands have a `--json` (or `--json-lines`) option, so their (non-logging) output is made in json format.
1.2.0 is rather old meanwhile, maybe you should run a more recent version (it is important to read the change log): https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup When creating inclusion/exclusion patterns, you can use `borg...
patternfile2 looks almost ok, but guess you need to get rid of the leading slash in the patterns. patternfile can't work as there is no relationship between the recursion roots...
For `create`, borg behaves like this: Pressing Ctrl-C once should make a checkpoint / commit the repo (that can take a while) and then abort. Pressing Ctrl-C twice aborts immediately.