I have recently encountered a very strange problem involving the resulting target time stamp on a very specific type of file using file sync. The files are several to many years old, and are part of a Quicken archive set accumulated over many years. The files involved are _ALL_ .eml files (text email threads from CheckFree) of 18K to 21K bytes (typically 18,526 or 20,072). They represent about 20% of the files copied, and many but not of all of these files seem to be affected -- typically 144 or 145 files but some times as many as 244 files.
The files affected are all copied correctly but the target time stamp is set to the (current) copy time rather than the original time stamp. Solution procedure is: (a) do a folder compare, (b) display only mis-compares ignoring folder structure, (c) select all and do a binary compare showing that all files are identical, (d) repeat steps (a) and (b) and use touch to correct the time stamps of the target files.
Failure is VERY repeatable. System is Win7 Ultimate x64 with BC 3.1.11. Drives involved (3) are all 2TB SATA, one attached to MOBO and two attached to an add-in card.
I have been a user of BC for backup/archive purposes for many years and this really shakes my confidence. I hope someone can explain the problem and/or fix it.
The files affected are all copied correctly but the target time stamp is set to the (current) copy time rather than the original time stamp. Solution procedure is: (a) do a folder compare, (b) display only mis-compares ignoring folder structure, (c) select all and do a binary compare showing that all files are identical, (d) repeat steps (a) and (b) and use touch to correct the time stamps of the target files.
Failure is VERY repeatable. System is Win7 Ultimate x64 with BC 3.1.11. Drives involved (3) are all 2TB SATA, one attached to MOBO and two attached to an add-in card.
I have been a user of BC for backup/archive purposes for many years and this really shakes my confidence. I hope someone can explain the problem and/or fix it.
Comment