I’m not 100% sure about it, but you could replace -.DS_Store with -*.DS_Store or -*\.DS_Store.
According to the documentation about filters, it’s best practice to supply folder exclusions first. Maybe it helps changing the order of the filter list.
Neither of those alternatives seem to work. Strangely though, when I moved -*/iPod Photo Cache/ to the top of the list, even that rule stopped working. I moved it to the bottom again and the rule started working again.
mohak, did you use the browse tool to browse to the “/iPod Photo Cache” and check it (giving it a red X) or did you manually type that in?
Also, if you browse through the Source Data folder tree (usually shown above the Filters list you provided) do you see the “offending” iPod Photo Cache file listed with a red X next to it such as seen here next to Downloads?
mohak, OK - then I think the issue is that your formatting of the Exclude XXXX value is incorrect.
May I suggest using the folder tree to browse down to and “red x” the folder or file you don’t want backed up and then go down to the Filters section and see what filter was added? That should give you an idea of what formatting the “Exclude folder” or “Exclude file” fields are expecting.
I used that method for some of my initial exclusions as well as the “Edit as text” option (the 3 vertical dots) to manually put Exclude Expressions in and then use the tree view above to verify what I my rule was supposed to exclude was really excluded.
O.K., this is quite strange. First, I removed all existing filters. Then manually excluded a file and a folder from the source tree. This added a “red X” next to them in the source tree and added the following rules in the filters section.
mohak, yes - the test-filters command including items that the GUI says should be excluded is similar to what I commented on in another topic
However in reviewing my actual backups I’m not finding any of the items that I excluded - so it looks like the filters during backups are working as expected and that it’s likely just a bug with the test-filters command that we’re seeing. Note, however, that this has not yet been confirmed.
If you have the time / ability I’d suggest doing a backup then browse through the files available to be restored specifically looking for items you know you excluded. I found the “Search” button very handy for that purpose.
I think I found the reason for the strange behaviour in the previous post and I think it’s because of the %HOME% variable in the source data selection. When I created the backup job, I selected the source directories from User Data->Home->....
Apparently, the filters did not work when I did that. So I removed those directories and instead selected the same folders from Computer->Users->mohak->....
Now when I use either of the following filters individually, the I see the appropriate files being exclude.
-*/iPod Photo Cache/
Unfortunately, when I use both together, I still get the original behaviour, i.e., whichever one I put at the bottom, is the only one that seems to work. I am now thinking this could be a fault in the way the Web-UI is calling the command line. I shall look into it further.
I get the impression that excluding files which have ONLY an extension is a bit wonky. For example, I couldn’t get “.plexignore” to be filtered out whether I tried filtering the extension “plexignore” or the whole filename “.plexignore” - perhaps a bug in the parser?