On Error hook not triggered by warnings about backrest HOT 5 CLOSED

Hey, you're right that there was a behavior change here -- which isn't great. I did some work prior to the last release to downgrade warnings to not trigger error hooks but you're right in noticing that there currently isn't a good way to get notified of IO errors.

This will be fixed in the v1.0.0 release by adding the warning condition hook (I do want users to have the option to ignore warnings if they see them commonly -- e.g. backing up big directories of constantly changing sqlite databases (if a user isn't inclined to setup hooks to properly stop the applications doing writes).

Specifically addressed in f0ee20f

from backrest.

Hey, forgot to leave a comment on this thread. tl;dr is that warnings don't trigger error hooks at the moment. I plan to add a CONDITION_SNAPSHOT_WARNING to capture these cases.

from backrest.

These warnings already triggered the Discord hook with the error conditions. This example was from April 4th:

Maybe something changed in these latest versions. The last trigger for me was on April 10th, so if there was any change in Backrest it was after this date. I don't have these warnings all the time, they are sporadic.

For me it's ok to capture these errors with the existing error conditions, but having a new warning condition will be fine as well. This latest may be useful for other people.

from backrest.

Thanks for sharing your point of view.
I can wait for the next release to have the warning condition.
Is there a way we can stop a docker container from within Backrest running on another docker container?

from backrest.

Added the new backup warning hook type in 1.0.0 which should address this

from backrest.