The sync function help for Toucan states that:
"Mirror Update is slightly different to Mirror Copy starts off using the copy routine and then removes unnecessary files and folders. Usually this is quicker than a Mirror Copy as it doesn't copy all of the files, however it may not create an exact copy."
Could you explain in what circumstance / why it might "...not create an exact copy."
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
only case that it might not create an exact copy is if there was a newer file in the destination directory as it won't get replaced by the one in the source directory.
Hi Steve,
I'm not sure if this has been updated/addressed later on as this is quite an old post, but I would prefer it to delete/overwrite the newer file regardless. The idea of a mirror is to have an exact duplicate of your source. the logic then is subtly different to performing a backup where newer files are considered the latest version.
I've had many occasions where the date written to the destination folder is in fact newer than the source date and could never get to the bottom of this, i.e. use App A to copy file B to location C and then file B on location C seems like the newer file which then completely screws up the subsequent sync.
Using my suggested logic for the mirror would overcome issues like this. B.t.w. I used FreeCommander Portable sync up to now.
Regards
Paul
of course, thinking about it this doesn't make any sense, and indeed I have a feeling it might be related to the bug in your other post, I shall get it changed (if it doesnt already do this) for the next pre-release.
Thanks Steve, I appreciate all your effort.