New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snapshot-policy USN plus attribute exclude may exclude all selected files #5175
Comments
This issue has been mentioned on Duplicati. There might be relevant details there: https://forum.duplicati.com/t/using-usn-policy-can-cause-loss-of-files/17878/23 |
I can't reproduce this. In the forum post you had this sequence
I only get a single line with
When I add the drive root as the source (with a filter to exclude subdirectories), I get the warning
The resulting backup is empty, so that might be the same reason. |
@Jojo-1000 Not directly related to the OP question, but would it make sense to automatically exclude The data there is unlikely to be restorable, even if there is permissions to read it. |
I don't think that is necessary. I doubt the normal user will ever enter such a path, so the only time it comes up is with snapshots where it is needed. |
Environment info
Description
Using Usn policy can cause loss of files discovered a bad interaction between these settings that seemingly decides there are no files.
Testing with buttons on GUI Source Exclude, it looks like
System files
andHidden files
can do it, butTemporary files
is safe.Steps to reproduce
No files. Home screen
Source size
is 0 bytes, Restore tree area empty.File backed up.
If I select the containing folder, e.g. C:\tmp\usntest here, the file gets backup.
Screenshots
Debug log
Forum has a few. The most worrisome part of a verbose log is when you see:
The text was updated successfully, but these errors were encountered: