FreeFileSync Forum

I'm afraid the method you suggested won't work:
The nightly batch file already opens "C:\LogFolder\BatchName-%Date%.log" and directs all output, including the STDOUT output of the called FFS batches, to that file. The re-direction you suggested (2> C:\LogFolder\BatchName-%Date%.log > nul) then tries ...

Task Scheduler, in PROPERTIES/ACTIONS/ADD ARGUMENTS specifies "> C:\LogFolder\BatchName-%Date%.log 2>&1" (See attached screen print).
I did run a test where I routed the output of the call to > nul and this did, in fact suppress the new diagnostic message. The only thing I'm afraid of at this point ...

You are correct:
Task Scheduler starts a "nightly batch" file. This batch file then calls FFS as described in my original post. (Call "C:\Program Files\FreeFileSync\FreeFileSync.exe" "Z:\09 System\015 Directory Tools\$$ Synchronization\FreeFileSync\Config Files\$MACHINE\GlobalSettings-MACHINE ...

Is there any easy way to turn it off? (I am getting about 20 versions of this chunk of data in my nightly batch output)
Having extra info WHEN NEEDED is great but when it is NOT needed, it's just clutter.

For your information:
I believe when you published version 14.6 you left a diagnostic message active:

In my nightly sync jobs, FFS is called from a batch file. After upgrading to 14.6, after each and every call,
[E.G.: Call "C:\Program Files\FreeFileSync\FreeFileSync.exe" "Z:\09 System\015 ...

Excellent! I just excluded the "Some files will be synchronized as part of multiple folder pairs...." error message and I should be back in business.
Excellent customer support! I wish other companies where this prompt!
Thanks Xenon!

You are correct: I had "Ignore Errors" checked as quite often I get errors regarding syncing from multiple folders. That brings me to another question: Is there a way to let it display one type of error but suppress another type of error? (yeah, I know: that's asking a lot)

I have two external USB sticks that I use for backups on alternating months. I.e. data get backed up on stick 1 in Jan and then on stick 2 in Feb then on stick 1 in Mar etc. I have 2 ffs_batch jobs: one for each of those USB sticks. The only difference between those batch jobs is the volume name of ...

@Zenju:
I ran my original version of the ffs_batch file (the one that originally prompted me to post here) and, using FreeFileSync 11.29, I no longer get an error message when trying to synchronize from one source folder to multiple target folders.
(I have not checked if the proper error messages ...

I ended up splitting the ffs_batch file into TWO jobs:
Job 1 mirrors Folders “Y” and “Z” to their counterparts on the target drive (“I”)
Job 2 uses the appropriate files within drive “Z” to update the files in the root folder of “I”.

I still believe the error messages could be a lot clearer by ...

Maybe I just don't understand what a "base folder" is:
I am under the impression that a "base" folder is the same as a "source" folder.
I am synchronizing (mirroring) the entire base folder ("Z") to its counterpart on the target drive "I".
I am also synchronizing (updating) a file within the that ...

The GUI warning message / log only lists files in the target folder. It does not list ANY files in the base folders. Here is the relevant part of the message:
4:53:54 Info: Synchronizing folder pair: Mirror ->
Z:\
I:\Source
14:53:54 Info: Updating file "I:\Source\09 System\015 Directory Tools ...

In my post time-stamped 09:29 I pointed out:
There are 4 files on the "Z" drive that get updated on the ROOT of the "I" drive.
The ENTIRE "Y" and "Z" drives are then mirrored to their respective sub-folders on the "I" drive.
In other words, some files are mirrored or updated from one single ...

I am not certain what you mean by the "FreeFileSync file": The folder pairs from the ffs_batch file are listed in my last post.
I did an Explorer search for that file on the source drive ("Z") and there is one and only one version of it.
I did an Explorer search on the second source drive in that ...

The only SOURCE location (base folders) are on "Y" and on "Z".
The "I" drive is only a TARGET. Here are the Folder Pairs used (from the ffs_batch file):
<Left Threads="10">Z:\09 System\003 Setup\Setup T5.2</Left>
<Right Threads="10">[T5Backup2]\</Right>

<Left Threads="10">Z:\08 OEM\Samsung ...

I am aware of what it is supposed to mean but this is not what is happening here:
The exact same path and file name appears in the sunglasses (read) line as in the Floppy (write) line.
The error message never mentions the source or base folder(s). (The source for this file is, in fact, on the "Z ...

I received the following warning message and I need a bit of an explanation:

Warning Some files will be synchronized as part of multiple base folders.
To avoid conflicts, set up exclude filters so that each updated file is included by only one base folder.
I:\ 👓 DIR\<PATH>\GlobalSettings ...

Yup - that was the problem. It's funny how you can keep staring at something and you just never see it. All it takes is a fresh pair of eyes and the problem and its solution become obvious.

I am trying to keep 2 folders in sync. Folder1 is on Server1. Whenever something gets changed here, Folder2 on Server2 should also be changed such that both folders are identical.
To accomplish this, I tried to use RealtimeSync. I specified the SOURCE folder in the first line of RealtimeSync and ...

I have a similar problem: I own 3 devices on which the Donation Edition is installed. I am told, however, that it is installed on FOUR devices.
Two of the three devices have multiple boot drives (One is a 'current' install with all updates and one is an 'older' install - a snapshot of what the ...