FreeFileSync Forum

@haneek, thanks for the pointer, encouraging me to do a bit of experimentation.

Rather than recreating the job, what I did was to delete the sync.ffs_db file on both sides (on a single desktop, and on the NAS), and then run the job (with no changes) in order to recreate those two ffs files.

After ...

Does anyone else use two-way sync? Can anyone confirm this issue, or can anyone affirm that deletions do in fact get propagated?

Good question. I have two such Two-Way sync jobs. Yesterday, because of a bit of frustration with this problem, which was causing repeated issues, I changed one of those jobs on the main desktop to Mirror instead. However, on that location on the NAS, the sync.ff_db file does show a timestamp of ...

So anytime I delete a file or directory in this folder on any of the desktops or the NAS, that delete does not get propagated by FreeFileSync.

Its like the Two-Way sync just doesn't propagate deletes. It's like it doesn't update the database file or something. This is a major shortcoming. Has no ...

Hi. I have three desktops, and each has the same two-way sync job, to sync a same folder on each machine, to a same folder on a NAS, so all three desktop folders and the NAS folder should stay in sync when changes are made to that folder on any of the desktops. The FFS sync job is configured to ...

What you describe sounds like the behavior of old FreeFileSync versions. In newer ones it doesn't matter which file gets updated: The whole versioning folder is checked for outdated items after sync, which are then cleaned up accordingly.

In which version of FreeFileSync was this behavior ...

Well, this is very odd. Suddenly, the problem seems to have disappeared. I spent some time trying to reproduce it, but without any success. And, the ffs_tmp files that were formerly present have mysteriously disappeared as well. So, I re-enabled the job which had been producing these files, which ...

I don't think these new Samba issues are related to STATUS_EAS_NOT_SUPPORTED, so I'd appreciate if you'd open a new forum topic. If it included steps how to reproduce or a Process Monitor trace file , this would be even better.

Will do. My NAS is currently in the middle of a rebuild, but ...

Hmmm... 10.4 just released, but no mention of a fix for these problematic temp files. Zenju, is this something that is going to be addressed?

For me at least, the problematic temp files appear only for certain source files in certain batch jobs, although every file synchronized must create a temp file. Perhaps the Fail-Safe Copy option could be made a per job or per folder-pair option, so that it could be turned off for the problematic ...

… the only difference that I see is that all filenames would then contain a timestamp (which they don't when Replace is selected,) When using the Time-stamp [File] Naming Convention, the most recent previous version does not have/get a time-stamp. Only if a more recent previous version is added ...

Hi Plerry, I had exactly the same thought. This method should work well, and the only difference that I see is that all filenames would then contain a timestamp (which they don't when Replace is selected,) which could be good or bad, depending on the user's needs. I think I'll evaluate this method ...

While this feature is great, a small refinement would be excellent: Currently when Versioning Naming Convention is set to Replace, the Limit File Versions check boxes are all grayed out. Of course Minimum and Maximum do not make sense when only a single version is being retained, but Last X Days ...

Zenju, thanks so much for adding this feature--I have been waiting a looooong time for this! And thank you Plerry for explaining it.

A quick test of Maximum shows it to be working as expected. But a question regarding "Last x days:" does this refer to the number of days elapsed since the timestamp ...

Hi Zenju,

Resurrecting an old thread because this problem has just surfaced for me. On Windows 10, using FreeFileSync 8.3 donation edition, and suddenly getting hundreds of these temp files, named filename0.ffs_tmp through filename9.ffs_tmp, and then the same sequence for the next file, and so on ...

Zenju, thanks for the reply. So until then, the choice is either to RTS the entire drive (in this scenario), or else to use Task Manager to schedule regular backups. Anyone have any thoughts on advantages or disadvantages to either approach?

Zenju, many, many thanks for any excellent product. I've been using it for backup (mirror) via schedules, but am now attempting to use RealTimeSync, and a question has arisen.

As an example, let's say C_Drive.ffs_batch has the Mirror pair C:\ and \\NAS\share\C, and has Include Filter "*", and ...