Client: "NIG-PC" -- Windows 10 VM, Retrospect 15.6.0, with C drive and external E drive. Both drives had "Test_Data" and "Test_Data2" directories, each with a couple of text files inside.
Server: Windows Server 2016, Retrospect Multi Server Premium v220.127.116.11
Client was added by Direct IP with "Volumes" tab "Client Sources" set to "Client Desktop" -- both C and E drives were visible
A new disk-based Backup Set called "Filter_Test" was created
A new filter called "Filter_Test" was created, initially blank and then edited as per the following screenshots
After the filter was edited, an Immediate Backup was created: Source -- "NIG-PC"; Destination -- "Filter_Test"; Selecting -- "Filter_Test". The Preview button was clicked and, once the results generated, the screenshot taken. The Immediate Backup was then cancelled to clear any cached Preview and to force a re-scan for the next test
"Windows folder path exactly matches \Test_Data\" -- no drive letter, so nothing is matched:
"Windows folder path exactly matches E:\Test_Data" -- no trailing backslash, so nothing is matched:
"Windows folder path exactly matches E:\Test_Data\" -- drive letter and trailing slash included, matches only with "Test_Data" on E and not E:\Test_Data2 or C:\Test_Data:
So, what about "matches pattern"? We know from the filter dialog tip that "* matches any or no characters and ? matches any single character", but x509 had no special characters in his filter yet still got matches. Let's see what we can find out, starting with a filter similar to x509's...
"Windows folder path matches pattern \Test_Data" -- matches Test_Data and Test_Data2 on both drives:
"Windows folder path matches pattern \Test_Data\" -- matches Test_Data only on both drives:
"Windows folder path matches pattern E:\Test" -- matches Test_Data and Test_Data2 only on the E drive:
"Windows folder path matches pattern st_Data" -- matches Test_Data and Test_Data2 on both drives:
Exact folder matching requires a full path, including the drive letter, and a terminating backslash, i.e. "E:\Test_Data\".
The "matches pattern" condition includes invisible "*"s, both prefix and postfix, i.e. if you enter "st_Data" it is actually "*st_Data*". That may be what you want, e.g. the same folder name at different levels of the directory structure across multiple drives on a client, but could also greatly widen the matches beyond what was expected.
As always, the more explicit you are the closer the filter results will match your wishes. Vagueness on "includes" can massively increase backup resource requirements, vagueness on "excludes" can result in important data being missed. So test, test, test -- and be careful out there!
Yes this was all done with "includes" whilst x509 was having trouble with "excludes" -- that's simply because I think it is much easier to see none, one or two ticked boxes amongst a column of unticked in a fuzzy screenshot than to spot the gaps in a line of selected items. But the conclusions above also apply to "excludes", and it's simple enough to verify for yourself if you doubt it.
Hope that helps someone!