Binary-comparison also processes all files in parallel.īefore version 10, FreeFileSync had shown a single advertisement during installation to help fund the project. Folder comparison will issue multiple requests at a time even when traversing only a single folder, by dynamically managing the workload while recursively reading the folder tree. The new parallel file operations architecture is not limited to the synchronization step, but used throughout the application.
#COPY NEW FILES ONLY FULL#
The idle time after issuing each file I/O request while waiting for the network response is not the limiting factor anymore: The number of parallel operations can be set as high as needed until the bandwidth is saturated and the network card is operating at full speed. This new design offers huge performance improvements for all scenarios that are dominated by latency, like synchronization against network shares or cloud devices including SFTP and FTP(S). During synchronization FreeFileSync will then spawn several tasks accordingly instead of processing only one file after another. It is now possible to specify the number of parallel file operations for each device inside the settings. The result is a straight-forward and intuitive way to handle multi-file renames:įreeFileSync with support for multi file renaming and the enhanced sync conceptĬan be obtained via the official website: įreeFileSync version 10 has added support for copying That can be copied or moved, while the commonalities are shown as editable text. The file name differences are represented as blocks Most file renaming tools are complex beasts, overflowing with options.įreeFileSync's renaming tool strips the complexity down to its core:Īll file names can be changed via a simple text input field.
#COPY NEW FILES ONLY MANUAL#
That's not quite the "conflict" that some users would like to see, but better than nothing).įreeFileSync 13 supports manual file renaming for multiple files at once! a "changes"-based "mirror" that "does nothing" if the changes are occurring on the target side? This opens up for new possibilities (like a proper "Update"),Īnd hopefully other kinds of sync scenarios, that are not immediately obvious The "changes"-based settings have always been hidden inside "Two way" but are now exposed. Therefore FreeFileSync now supports two fundamentally different ways to set up sync directions. "Mirror without database" is a frequent requirement and kept as the default. "Mirror" can be expressed both via "differences" and via "changes",īut doesn't need a database file in the first case. If it wasn't for the requirement of sync.ffs_db files: One might be tempted to go further and assume "changes" is the moreįundamental concept, and get rid of the old "differences" categories altogether. ( create, update, delete) similarly to how it is possible with the "differences" categories.Īll three, "Two way", "Mirror", and "Update" can be expressed in these new terms. Specific decisions can be made for each individual change
The last sync, in the exact same way that "Two way" operates: by using a database file.īut FreeFileSync doesn't stop there. The solution: The new "Update" variant will determine sync directions based on "changes" compared to This change couldn't be detected without a database, andĪ duplicate file was copied to the backup location instead of renaming the existing one. Unfortunately this is exactly what the old differences-based "Update" did.Īdditionally, when a file on the source side was renamed, Them copied over again during the next sync: The user is cleaning up unwanted photos. On the other hand, deleting photos from the backup, should not get
#COPY NEW FILES ONLY FREE#
The user is making free space for new photos. When photos on the smartphoneĪre deleted, they should not also be deleted on the backup drive:
These two cases, however, should get different treatment!Ĭopying photos from a smartphone to some backup location. The "Update" synchronization variant wasn't as fundamental and useful as the other two, "Two way", and "Mirror".īased on "differences", it was unable to distinguish whetherĪ new file was created on the source, or if an old file was deleted on the target. In addition to "differences" it is now possible to set sync directions based on "changes": Previously they were based on the "differences" found after comparison: left only, right only, left newer, right newer. FreeFileSync 13 generalizes the way sync directions are set up:
0 kommentar(er)
