v2.1.1, under the Sync tab, does not update my files. However, v2.0.7 updates just fine, under Mirror(Update).
As a side-note. If 'Copy' copies from source to destination, and 'Mirror' makes an exact copy, what is the difference?
Also, is it possible to combine multiple functions, per job, in whatever order you want? ...I don't want to create one job to Update from source to destination and then another to Clean files in destination that are not in the source, which I did before with 'Mirror(Update)' in v2.0.7. Could you also allow an option (which the user can toggle) that asks you to confirm deletion of all or individual files?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
difference is that Mirror will remove any files in the destination that are not in the source, I shall update the helpfile to make it clearer.
The easiest way to chain things together like this is to create a job for each step and then chain them together on the script tab.
As for them files not being updated, this may seem like a really silly question, but are they actually different, in 2.1.0 and later if two files are the same, even if one is newer then it won't be copied, as there is no need! I have just done a bit of testing with Update and it seems to work fine for me
...Doesn't Update --update-- files? ...Even if both files are 'the same,' my understanding is 'Update' copies the --newer-- version of the file from source to destination. Am I misunderstanding? ...The pre-release seems to have fixed most of this.
Now another update problem that I've had in every Toucan is updating a file that only changes the 'Accessed' Timestamp (the program that handles this file keeps the 'Accessed' and 'Created' timestamps constant). Will toucan compare the creation, modified, and accessed timestamps in the update process?
they are exactly the same, then what is the point it copying it? I think I am not quite understanding what you are saying here!
If you check the Retain Timestamps option then they should all be updated, is this not the case? In the update process the modified time is currently used.
These files are encrypted files and the program I use, TrueCrypt, does not modify the 'Created' or 'Modified' Timestamps, only the 'Accessed' Timestamp. So, when I'm backing up my files, the only change in the file is the Accessed timestamp. So far, Toucan does not seem to recognize the difference and has not updated that file. That's why, up until v2.1.2, I have simply created a job that copies them from source to destination. As mentioned in a different place, now I can't even copy from source to destination:
https://portableapps.com/node/19928
try following the instructions in the help tab in the sync section for disabling the streams? That way the actual copying should be done exactly the same as it was before 2.1.0, and we can see if it it isn't being copied because that part of Toucan thinks the files are the same, or if the update routine has a flaw in it. Thanks in advance.
Disabling the stream seems to solve my copy problem. I also noticed that, from the 'Accessed' timestamp, only the day gets recorded on my flash drive, not the specific time. This may be the reason I could not update.
this helps to narrow it down, thanks
Toucan wouldn't sync several files (mirror mode) until I disabled the stream option, in which case it would copy everything regardless of it being newer or not.
This bug happened in all kinds of operations: network share to network share, network share to local HD, network share to usb drive, and usb drive to local HD.
So last accessed time does not seem to matter much (incidentally, not storing the last access time on a usb drive is by design, to avoid wearing it out).
I don't know if this is related or not, but sometimes Toucan leaves a Toucan.tmp file behind, which gets erased the next time I execute the sync job.
for the confirmation
Sorry for the long delay in replying, I have been away.
I will do some more testing to see if I can get this reproduced, what operating systems are you using? And you last bit of information is very intriguing, that might well mean that Toucan tries to copy the file but it cannot rename it, there should be an error in that case, but I will check.
We use Windows XP Pro SP3 for the workstations, and the network shares reside on Novell Netware servers.