FFS 9.0 (Windows) - Exclusions not working

[GJSchaller]

I'd set up a sync for a file server using the 8.x versions of FreeFileSync for Windows, and it worked well.

I upgraded to 9.0, and now I am finding that when I list a path as an exclusion for comparison, FFS does not exclude the path during the comparison.

I've tried multiple paths to compare, including:

D:\Foldername\

and

\\servername\foldername\

but in both cases, the path is still included in the comparison. Is this a bug introduced into 9.0?

[Plerry]

It is no bug.
Include- and Exclude-filter definitions are always relative to the root of the left and right sync location.
So, the absolute definitions you mention above do not work (and never have in earlier FFS versions).
As per your example, if your left location would be "D:\" and your right location "\\servername", your exclude-filter entry should read "\foldername\".
See here.

[GJSchaller]

Ah, OK - I think I got confused with the syntax for RoboCopy. I'll give this a shot - thank you for the feedback!

[dariusii]

Doesn't work. Attach with screen was added.


All life work with rsync (example)
(/usr/bin/rsync -vrht --modify-window=100 --delete-before --exclude-from '/home/iron/1/share/zones/zalman/exclude.txt' --delete-excluded --progress --stats /home/iron/1/share/zones/zalman/ /media/iron/zalman/

exclude.txt as
/movies/001/*
/movies/Docs/*
/Music/iTunes/iTunes\ Media/Podcasts/*
/Music/iTunes/iTunes\ Media/Mobile\ Applications/*
/Music/iTunes/iTunes\ Media/Home\ Videos/*
/Music/iTunes/Album\ Artwork/*
/Music/Other/*)
and didn't have problems.
With "windows" analogs was "began" :)

Excuse me but I don't understand, why that filters doesn't work.
FFS 9.0

555.jpg (270.56 KiB) Viewed 700 times

[Plerry]

If the rep.sparseimage.bz2-file was already in your right location before you added the exclude rule \backup\Apple\*.bz2 to your exclude filter, this makes sense.
Because you now excluded the/those *.bz2-files form the sync, they will not be touched in or deleted from your right location (nor in the left location).
The rep.sparseimage.bz2-file might e.g. pre-exist in the right location as a result of running an earlier sync without said exclude rule.

Remove G:\backup\Apple\rep.sparseimage.bz2 and then run just a FFS compare (no need to run a sync ...) and look at the compare results and planned actions. The relevant *.bz2-file should now not be mentioned as to be created on the right-side.
If it is (still) mentioned as to be created on the right-side, something strange is going on.