The manual states clearly that it will "apply the same move on the target side during synchronization instead of a slow copy and delete"FreeFileSync is able to detect moved files on one side and can quickly apply the same move on the target side during synchronization instead of a slow copy and delete. To make this work, FreeFileSync requires database files ("sync.ffs_db") to compare the current file system state against the time of the last synchronization.
As a test, Empty your recycle bin and test this on your system the way you say it is working, if it is indeed working and you are only re-organizing files on the source (left) to match your already synced (mirror) drive on the right, then when you run the sync, YOU SHOULD NOT get any files in your recycle bin (as long as you actually did not delete any files from the source) if this is working as intended. If you are getting files in your recycle bin, then it is only copying files then deleting the files that no longer exist instead of sending the gathered commands to just move the files at the target.
I have tried modifying permissions, the only thing I have yet to try is conflicting programs... I install a lot of programs by default, but these programs were already installed when I performed that first (and only) successful series of tests on April 26, 2020.
I have tried with and without "Fail-safe file copy", "Copy locked files", "Copy DACL, SACL, Owner, Group".
With and without Administrative permissions (for FFS)
My hair is not long enough to pull out or I would be.
I have even tried this on an older OS, Windows 2011 SBS Server (Went back to the last version of FFS that officially supported Windows 7.
I have tried on Windows 10 using compatibility modes (Win 8, Win 7, Win XP)
I am going to try an older Windows 10 build sometime this week. No, not virtualized, I will be installing it on bare metal on a computer.
I will again explain a purpose I am using this for:
Folder Structure:
Engineering Packs\0-999\
Engineering Packs\1000-1999\
Engineering Packs\2000-2999\
Engineering Packs\3000-3999\
Engineering Packs\Hold for revisions
Engineering Packs\New and revised
There could essentially be 1000 folders in each of the folders above and possibly more in "Hold for revisions" or "New and revised" while unlikely, but possible.
Released Engineering packed will be in the #ed directories, and a pack that needs changes to it will be put in "Hold for Revisions"
After the engineer gets done with the changes, it will be put in "New and revised" to be reviewed by another engineer before being re-released to the pack folders.
Since a lot of changes and moving can be done here, with not a lot of changes happening except for in the hold for revisions folder, the "Detect moved files" feature is really beneficial here so that move commands are sent to the target instead of file(s) and folder(s) being deleted and re-copied.
Local Share Master (Share on server)
External Drive Clone (Backup clone for external safekeeping NOT ONLINE, occasional sync with the possible rotation of drives)
I do hope this clarifies a situation that this can be used for, and how what it currently IS doing IS NOT what it is supposed to be doing.
I thank you for your time, and I believe it would do everyone a world of good if the developer could record a video of how the "detect moved files" is supposed to work, how to get it to work correctly, and so on.