Improve USN and Snapshot error handling #4085
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has been mentioned on Duplicati. There might be relevant details there: https://forum.duplicati.com/t/how-can-i-check-if-usn-and-vss-are-working/9061/4 |
warwickmm
reviewed
Feb 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If snapshot fails and policy is set to Required, show "Failed to create a snapshot" message instead of cryptic exception message like "access denied."
If snapshot policy set to Auto, record the failure in the Information log.
If USN policy set to On, write to Warning log instead of Error log. (This is more consistent with how snapshot policy is handled.)