FreeFileSync Forum

1) I don't know about the icon, but when using the Task Scheduler, when you define a Basic Task, you define the next and then click next, which brings you to the Trigger tab. There you can select when the task is to be run, e.g. "When I log on", instead of "When the computer starts&qu...

You can either select not to use the the recycle bin for (previous versions of) files that get modified or deleted: https://freefilesync.org/forum/viewtopic.php?t=9195&p=33227 Or use Versioning , which uses a self selected location to store (previous versions of) files that get modified or delet...

If the default filter entries do not already exclude your recycle bin, then run a Compare in FFS, right-click on the RecycleBin, and select to exclude.

FreeFileSync does not (or at least: is not supposed to) change/modify file content when copying.
So it seems there must have been a corruption during copying.
You can try to do a verification after copying, by setting the VerifyCopiedFiles flag to true.

If your message is intended as criticism, you should not criticize FreeFileSync (FFS) and/or RealTimeSync (RTS), but rather Google Drive. If you read the RTS manual page , you can read what RTS does (get notified by the OS if changes in the monitored directories occur) and why ( only run FFS when ch...

This warning occurs if there is an (at least partial) overlap between one or more of your base folders or any of their contents (including in subfolders). You write your target base folder is on your I:\ drive, but it seems that either the source base folder is also on the I:\ drive (and has an over...

If your Microsoft account is an Admin account on your machine, you should have full control (Controllo completo). However, if your Microsoft account is not an Admin account on your machine, you are a plain User, that only has read and execution rights, no write access (Lettura ed esecuzione).

Simply make sure the user under which credentials you run FFS has write access to the mentioned folder.

If it is always the same file causing issues, and (as you write) you don't care about this one file, you can use the FFS Exclude Filter to exclude said file from your sync.

When saving your *.ffs_batch job, did you follow the instructions as per here, item 2) and 3) (checkmark Run minimized, AutoClose and IgnoreErrors)?

For FFS exit codes see https://freefilesync.org/manual.php?topic=command-line.
So, it seems your sync runs, but results in warning.
Check the FFS log-files to see the which warnings.

One option is to set up (at least) two accounts on your Fedora machine; one limited account for your sun (possibly even without login credentials), and (at least one) separate account for you, with login credentials. For the latter account you could then use an auto-mount for your NAS share. Or even...

In line with the FFS Manual section on Filtering, you could add
*- Copy*
to your Exclude Filter.
This will exclude all files and folders (and their content!) that have "- Copy" in their name.

@pnachtwey
Instead of using two different sync variants sequentially,
try out creating your own Custom sync variant,

a) The *.ffs_df files are binary files created by, and understood (only) by FFS. The file-structure is not officially documented or supported for use by anything other than FFS. However, the FFS code is open source, so if you (really) want to, you could extract the file structure from there, and use...

If that does not do the job, try creating a trace.
https://freefilesync.org/faq.php#trace

If it is that critical to you, you can define a command to be executed on (FFS) completion, invoking a custom script that sends an E-mail via your self-selected server.

Like therube mentioned, the list he(?) shares is with the default setting (Error | Warning | Success), but he also mentions that you can change the setting to only show Errors and Warnings or just Errors. FFS_Email.png Then, only file-names for which Errors respectively Errors and Warnings occurred ...

If the username and password for 192.168.20.100 are identical to your Windows username and password, you don't need to do anything special. If they are different: In the Windows Credentials Manager you can create a user/password combination to be used when identifying towards the network resource 19...

As instructed per the FFS manual page on scheduling batch jobs, you should not just checkmark Ignore Errors, but also Auto-close, when saving your *.ffs_batch job.

Assuming Windows: use the Task Scheduler to schedule your FFS sync task to run every day at 14:00. See here . > backup folder is local same as original folder Having your backup in exactly the same folder is not possible (in FFS). In a subfolder of your original folder is possible, but then you need...

Save each of your sync configurations from the FFS GUI as a *.ffs_gui-file (or *.ffs_batch-file) under a self-selected, preferably descriptive name via the File menu, or via one of the icons in the Configuration box (top left) in the FFS GUI. Those will then show up as recent sync configurations, an...

> Why do you discard the FTP possibility in favour of the "SMB with another user" possibility? I don't mention FTP or SMB. Either one should work, assuming your NAS supports the protocol. It should also not make any difference for the Credential Manager, as those credentials are used per t...

Simply checkmark "Don't show THIS warning again".
Other warnings should still be shown.

The best thing to do, is to create your FFS Scheduled Task to be run under dedicated user credentials. See here . And only that dedicated user (or the credentials stored for that user in the Credential manager for your NAS LAN location) should have access to the NAS share. Obviously, you need to tru...

When you get the referred to warning in the FreeFileSync (FFS) GUI, you have the option to checkmark not to get that warning any more in the future. That should resolve your issue.

Read here (2nd paragraph).
The RTS Idle time has nothing to do with AFK, but just with files being created or modified within the RTS monitored folders.