Big Al on Mon, 11 Mar 2019 15:04:40 -0400 typed
in alt.windows7.general the following:
On 3/11/19 1:23 AM, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.



Try this, I have it in all of my batch files like:
robocopy D:\src G:\dest /MIR /NJH /NJS /NDL
/DST

/dst Compensates for one-hour DST time differences.

https://docs.microsoft.com/en-us/win...mands/robocopy

Which goes back to my question: apparently there is a difference
in how the times are computer, because I can't see what is the
difference between the source drive file dated "Jan 2 2019 10:20 AM"
and the target drive file dated "Jan 2 2019 10:20 AM".

I can see some confusion if I save a file at 01:20 AM Standard
time, run the backup before 01:58, amend the file at 01:10 Daylight
time, and then run backups again.

But backing up as "newer" files which haven't been touched since
1996 (45 time changes ago) - that is the confusing part.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?