Page 1 of 1
Ignore timestamp Altogether
Posted: Thu Dec 18, 2025 12:18 am
by fletch
Scenario: Copying files by mask from A: to B:.
If I chose Ignore Timestamp Altogether, shouldn't it ALWAYS copy files matching the mask from A: to B:?
I have a file on B: whose date is NEWER because the app that uses it "touched" it when the app starts. But the data in the file is months old.
FWIW, the file sizes are different.
The When Size Is Different setting is set to Copy.
Re: Ignore timestamp Altogether
Posted: Thu Dec 18, 2025 12:55 am
by tobias
Hello,
the option Ignore Timestamp Altogether is used to copy fewer files, not more files.
To overwrite newer files with older ones, you need the Exact Mirror copying mode.
Click the Configure button to specify if files should also be deleted.
It could be argued that the setting you mentioned should also cause Standard Copying to copy the file, but the base fact is that Standard Copying never replaced newer file with older ones.
Re: Ignore timestamp Altogether
Posted: Thu Dec 18, 2025 1:59 am
by fletch
Hmmm, I'm trying to grasp the scenario where that would copy FEWER files. Is it equivalent to copy files that only differ by size? Just curious.
However, Exact Mirror is THE clue/tip I needed. Just didn't occur to use that even though I use it on other jobs. That works as desired so thanks for that !!!
Not sure I'd suggest to alter Standard Copying's current behavior. Unless others find value in that. I was just thinking to myself, if the size is different then that would flag the file for copying and if Ignore Timestamp Altogether were active, it should work. But I'm OK with using Exact Mirror.
Re: Ignore timestamp Altogether
Posted: Thu Dec 18, 2025 11:43 am
by tobias
The ignore option can cause Syncovery to copy fewer files, because it would not copy a file even if it has a newer timestamp on the source side.
This should really never be used.