Sync database is not updated when folders are the same

[DeirdreYoung]

It seems like a small dumb thing, but here it goes.

I use FreeFileSync to copy files from a NAS to an external hard drive for backup.

I will sometimes add files to the NAS and add those same files to the HD.

When I "sync", it says No files to synchronize. True enough - so it doesn't update the sync.ffs_db

But if I rename a file on the NAS and then sync, FFS doesn't recognize the existing files as being the same (and I do have "Detect moved files" checked, I love that feature!) so it deletes the file on the backup disk, and copies the file from the NAS instead of doing a move/rename.

My suggestion, then, is to update sync.ffs_db even when a sync reports nothing to synchronize - because the file list itself may have changed.

[Plerry]

> I will sometimes add files to the NAS and add those same files to the HD.
This is a bit unusual use-case when normally using FreeFileSync for your syncs ...
Nevertheless, your suggestion makes sense.

[Zenju]

My suggestion, then, is to update sync.ffs_db even when a sync reports nothing to synchronize - because the file list itself may have changed.

That's already the current behavior. Maybe you're running an old FFS version.
Or you're not really running a "sync" but doing a "compare" only.

Just tested, and renamed files are detected correctly when following the steps described in the first post.