File copied correctly, but with incorrect time stamp.

[stc]

I've seen this problem with different versions of BC, and under both Windows and Linux:

When syncing folders, files are copied correctly, but some of the destination files are Time-stamped with the current system date rather than the date of the original file. So after the file copy, some of the files in the dest folders are shown as being newer.

This occurs with a relatively small percentage of all files copied, and seems to be random. Most files' time stamps are set correctly.

Most recent occurrence was noticed when syncing folders from a Linux system to Windows, but again, I've seen it in the past when syncing local folders.

Any idea what could cause this? It would also be nice to be able to 'touch' entire folder trees in order to fix this. While BC does highlight the folders to denote the difference in time-stamps, selecting and 'touching' those folders apparently does not touch the files within.

[Aaron]

Hello,

The main issue is if the destination device does not support setting the timestamp during a copy, the file will get the timestamp of the time of the transfer. Folder timestamps are always updated (as soon as a file is copied into it), so visually they will have a newer timestamp, but the comparison color is controlled by the files inside, not the folder timestamp.

When you are performing a copy, is the small percentage all files of a few specific jobs? Or specific files within a larger copy where the other files did update correctly? The later scenario would be weird, suggesting at temporary hiccup of the destination; what protocol are you using to connect to it?

BC4 does have a right-click Touch command to manually set a timestamp of a selected file(s). You can select a file and edit it to a manual timestamp, or copy from the other side to the selected file. Does this command work for the problem files (post-transfer)?

[stc]

Hello,
When you are performing a copy, is the small percentage all files of a few specific jobs? Or specific files within a larger copy where the other files did update correctly? The later scenario would be weird, suggesting at temporary hiccup of the destination; what protocol are you using to connect to it?

BC4 does have a right-click Touch command to manually set a timestamp of a selected file(s). You can select a file and edit it to a manual timestamp, or copy from the other side to the selected file. Does this command work for the problem files (post-transfer)?

It is the latter case, Aaron, so yes it is weird. A single mass copy of a large folder tree to another drive will set the time stamps of most files correctly, but a few end up tagged with current system time.

Recopying those particular files usually corrects the problem, but sometimes random files with the group still get the wrong timestamp.

There's no particular pattern to the files that are mis-stamped. Doing the copy again will result in a different set of mis-stamped files.

Touch does work also. But it would be nice if there was a command to touch all the files in a selected group of folders. Otherwise it is necessary to open all the folders and select the files.

[Aaron]

Hello,

The Touch dialog has an option to "include folder contents", which should work for touching the files within.

Also, to troubleshoot: if you double check with a Full Refresh or external to BC4 (Windows Explorer -> Right click -> Properties), the files actually have the incorrect timestamp, correct? It's not a BC4 issue displaying an incorrect timestamp in view, but the file has the correct if refreshed to Properties?