FreeFileSync Forum

I've used several sync apps over recent years and they all work this way.
If something is excluded then any matching files are ignored on both sides of the sync.

Right or wrong, developers have decided not to second guess and delete "extra" files on either side.

Actually you can but I'm not sure about a RealTimeSync for three locations. Try it.

On the main screen, click on the green plus sign to add another folder pair.

I think two sync jobs would do it.

First sync any two locations, then use a second job to sync the third location with one of the first two.

If you use a RealTimeSync then you may have to increase the "minimum idle time" to insure the first sync is completed before starting the second sync.

This is similar to issues I've had with a new sync job and an empty target. The sync does nothing.
Something to try that's worked for me is to manually copy one file to the target then redo the compare and sync.

You're welcome.

What you are doing is similar to my backup procedure. I also have a backup drive that does not have a drive letter assigned. I use a batch file to run my backup and use the mountvol command to mount the backup drive to a folder prior to running my backup task then dismount after.

I ...

Yes you can. See the help file section about "Variable Drive Letters".
https://freefilesync.org/manual.php?topic=variable-drive-letters

Here's something that may help.

In VeraCrypt, open settings, preferences and look about halfway down for the option "Preserve modification timestamp of file containers".

If unchecked, then any change to a file or folder in the container will update the container's timestamp.
If checked, then ...

I had the same problem that I originally attributed to syncing to a Cryptomator vault on a NAS. This beta version fixes it.

You might need to switch to comparing by file content or file size. Either the use of Google Drive or Cryptomator is likely the cause of the timestamps being lost


Same thing happened to me and I was able to isolate the cause to a recent Cryptomator release. If my vault was stored on a local ...

I have experienced the same and believe I have an answer. In my case, I specify max of 7 days but deleted files actually stay much longer. They stay until something new is added to the versioning folder.

It seems that old versions are deleted only after something is added to the versioning folder ...