![]() 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. 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 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. Paul M.FreeFileSync 13 generalizes the way sync directions are set up: Don't hesitate to get Carbon Copy Cloner if you are in need of a backup solution for your Mac - you won't regret the decision. Ultimately, he was able to identify the problem as being due to runaway crash reports from a faulty piece of software, and walk me through the steps necessary to get rid of the issue and assure a clean backup, and to give me some advice on next steps to deal with the disc replacement process. Over the course of three days, I exchanged a number of emails with Mike Bombich, who got back to me with analysis of my CCC log files within a few hours each time. But the thing that really makes me sing Bombich's praises is the quality of its customer support. The documentation is a model of clarity, and serves as an educational repository and resource on the philosophy of backup strategies that greatly enhances one's understanding of the product and its use. It does the job of providing a robust backup solution for your Mac in a clean, elegant manner. I can't say enough good things about Bombich Software's Carbon Copy Cloner.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |