You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then both Windows, Program Files and Program Files (x86) will be included in the backup.
0.16.0 and earlier versions work fine.
Note that using ? instead of the character range still works correctly.
Case sensitivity or insensitivity doesn't seem to matter either (--iexclude and --exclude produce same results in the above example).
Expected behavior
Allow to use character ranges to limit drives as in 0.16.0 and earlier versions
Do you have any idea what may have caused this?
No changes, besides upgrading from 0.15.2 and making fresh snapshots of my data.
Did restic help you today? Did it make you happy in any way?
Small bug aside, restic rocks.
The text was updated successfully, but these errors were encountered:
Output of
restic version
restic 0.16.4 compiled with go1.21.6 on windows/amd64
Note: all versions tested below are from the github's release page.
What backend/service did you use to store the repository?
Tested against local storage and backblaze (b2)
Problem description / Steps to reproduce
Exclusion patterns using character range to limit disk drives no longer work starting with version 16.1, for example:
[cCrR]:/Program File*
[cCrR]:/Windows
If such exclude patterns - stored in file test.txt - are used in the following invocation:
restic_0.16.4_windows_amd64.exe -r s:\windrivebackup --iexclude-file=./test.txt --use-fs-snapshot c:/
Then both
Windows
,Program Files
andProgram Files (x86)
will be included in the backup.0.16.0 and earlier versions work fine.
Note that using
?
instead of the character range still works correctly.Case sensitivity or insensitivity doesn't seem to matter either (--iexclude and --exclude produce same results in the above example).
Expected behavior
Allow to use character ranges to limit drives as in 0.16.0 and earlier versions
Do you have any idea what may have caused this?
No changes, besides upgrading from 0.15.2 and making fresh snapshots of my data.
Did restic help you today? Did it make you happy in any way?
Small bug aside, restic rocks.
The text was updated successfully, but these errors were encountered: