I noticed this today with the Opus Sync command but subsequent testing demonstrates the same thing happening with Opus Copy (or indeed Copy/Paste). When Source is local and Target is a mapped disk on a PC on the local LAN, files are copied and almost immediately the modified date on the target is changed to the current time. This does not happen when the target is a local folder. I tested with Explorer Copy/Paste and the target date is correctly preserved. Screenshots show the problem E:\ is local, X:\ is mapped to another PC. I'm on 10.0.5.0.
10.0.5.0 changed the order that the metadata and timestamp were written, so the timestamp is written after the metadata. That should mean the timestamp is preserved (obviously, as it's set last), but it seems something weird is happening with some (but not all) network drives.
It may be related to bugs in the way Windows Server 2008 caches timestamps, but we aren't sure yet (and only had one other report so far):
We've reproduced this and should have a work-around in the next update. Looks like a bug in Windows with how network shares handle file dates being set, as per the articles I linked earlier, and we've found a way to avoid it.
What's the exact issue you're seeing? What are the steps to reproduce it?
Have you checked if the same thing happens in File Explorer, in case it's something the server or RaiDrive is doing? (Assuming the actions that lead to the issue are things you can do in Explorer as well, of course.)
Thanks for the quick reply. I did some tests and at this time I can't reproduce it. I noticed this happening when copying wildcam video from an SD card to the networkdrive. I don't have the SD card here at this time, I'll pick it up tomorrow and test again. I don't know how it is formatted. It may have something to do with that, no idea.
I tried with another SD card, and it does copy the date correctly.
More news tomorrow.