Hi,
I have 1 file in folder: P:\_something_folder\System_Assemblies.rar
And second file: P:\_something_file.rar
And I have rule in excluded filter: _something*.rar
The good news is that file P:\_something_file.rar is excluded correctly.
Bad news is that file P:\_something_folder\System_Assemblies.rar is also excluded but should be not.
The problem is obviously that filtering is not separating folder names from file names but it should be applied separately.
This is what filter is doing: P:\_something_folder\System_Assemblies.rar - it is bug.
Filters like this _*something_*e.rar or P:\_something_*e.rar or \_something*.rar also not working correctly.
It means that if these filters are not implemented correctly it can lead to unpredictable number of missing files in backup folders.
Bug - incorrect filtering with wildcard *, mixed folder with file
- Posts: 3
- Joined: 1 Nov 2020
-
- Posts: 2451
- Joined: 22 Aug 2012
What you describe may not be the behavior you expected, but is by design, not a bug and described in the Manual.
The "*" wildcard is simply eager in the full (relative) path name, inclusive one or more "\"s.
If it is not possible to more specifically define just your base location root-level .rar file(s) that you want to exclude, e.g. by using one or more literals, e.g. \_something_file.rar, or by using one or more "?" wildcards instead of the eager "*" wildcard, you may need to revert to using two left-right pairs, as e.g. described in the Manual (Example: Exclude a sub folder except for certain files)
As per your posting:
_*something_*e.rar should work OK, as that should not exclude your System_Assemblies.rar file, because that filename does not end on e.rar.
P:\_something_*e.rar does not work as, per the Manual, filter definitions are relative to the left- and right-base-location and thus can never include a drive-letter.
\_something*.rar obviously does also exclude *.rar files in any \_something* (sub)folders because of the eager "*"
The "*" wildcard is simply eager in the full (relative) path name, inclusive one or more "\"s.
If it is not possible to more specifically define just your base location root-level .rar file(s) that you want to exclude, e.g. by using one or more literals, e.g. \_something_file.rar, or by using one or more "?" wildcards instead of the eager "*" wildcard, you may need to revert to using two left-right pairs, as e.g. described in the Manual (Example: Exclude a sub folder except for certain files)
As per your posting:
_*something_*e.rar should work OK, as that should not exclude your System_Assemblies.rar file, because that filename does not end on e.rar.
P:\_something_*e.rar does not work as, per the Manual, filter definitions are relative to the left- and right-base-location and thus can never include a drive-letter.
\_something*.rar obviously does also exclude *.rar files in any \_something* (sub)folders because of the eager "*"
-
- Posts: 4055
- Joined: 11 Jun 2019
It is working exactly as it should, as Plerry said, just not how you want. You can define folders in the filters by ending with a slash though.
- Posts: 3
- Joined: 1 Nov 2020
Thanks for the answers.
I would not say that "just not how you want" (but you are right) because I was describing the common or usual behavior implemented in DOS/Windows command line, Rar, Java, C#, Total Commander or other common tools so I had some usual expectations but sure, this is not a standard and every tool has some differences. Sorry, my fault.
Can I ask?
Would it be possible to provide a list (or log) of ignored files to be able to check what is ignored during the process? With current implementation I am not sure which files could be forgotten and I have a multiple complicated structures in folders and many files.
I would not say that "just not how you want" (but you are right) because I was describing the common or usual behavior implemented in DOS/Windows command line, Rar, Java, C#, Total Commander or other common tools so I had some usual expectations but sure, this is not a standard and every tool has some differences. Sorry, my fault.
Can I ask?
Would it be possible to provide a list (or log) of ignored files to be able to check what is ignored during the process? With current implementation I am not sure which files could be forgotten and I have a multiple complicated structures in folders and many files.
-
- Posts: 2451
- Joined: 22 Aug 2012
> Can I ask? ...
I am not aware of any such direct ability in the program.
You can however run a Compare in the FFS GUI and then export the file list as a *.csv file via Tools > Export file list.
If you do so before and after making a change to the Include and/or Exclude Filter, you can then compare the two file lists.
Assuming no changes were made in the files/folders being compared between running said two Compares, the difference between the two file list should be the result of (changes in) your Filter settings.
Note, that you can change what files are visible (and get exported to the *.csv-file) via the icons mid below the Compare result window.
I am not aware of any such direct ability in the program.
You can however run a Compare in the FFS GUI and then export the file list as a *.csv file via Tools > Export file list.
If you do so before and after making a change to the Include and/or Exclude Filter, you can then compare the two file lists.
Assuming no changes were made in the files/folders being compared between running said two Compares, the difference between the two file list should be the result of (changes in) your Filter settings.
Note, that you can change what files are visible (and get exported to the *.csv-file) via the icons mid below the Compare result window.
-
- Posts: 4055
- Joined: 11 Jun 2019
An easier way would be to run a sync, remove the filter, then run a compare. Then everything that shows up is what has been ignored previously
- Posts: 3
- Joined: 1 Nov 2020
Ok, thanks guys, but doing all this when something changes on lot of files takes a lot of time.
I will find some way. Thank you very much for answers and ideas.
I will find some way. Thank you very much for answers and ideas.
-
- Posts: 2451
- Joined: 22 Aug 2012
Perhaps a more direct way to assess the impact of your Exclude Filter entries is to turn things around.
If you put (only) your proposed Exclude Filter entries in your Include Filter and use an empty Exclude Filter, and then run a Compare (and make all files visible, also the equal ones), all files (and only those files) listed in the Compare result window would be excluded if you would put those Filter entries in your Exclude Filter.
If you put (only) your proposed Exclude Filter entries in your Include Filter and use an empty Exclude Filter, and then run a Compare (and make all files visible, also the equal ones), all files (and only those files) listed in the Compare result window would be excluded if you would put those Filter entries in your Exclude Filter.
