"Last Modified" property of file changes after Upload

Is this resolved. I am looking for a cloud storage for backup

This problem has been going on for years now. I have tried both goodsync and syncback and the net results is to jump thru hoops to make backups. if I simply automate the process, it will effectively do a complete back up daily, which means i NEVER stop doing full backups. couldn't figure out why i was always copying 32000 files every day, some are big files, and it runs 28 hours, EVERY DAY.

Goodsync has a work around, but it's a pain in the butt. Since this has been going on for years with promises to 'look into this' and it's still not fixed, i'm moving to a different backup solution as i can't have my system spending all it's resources all the time doing backups.

A normal back up should take 30 min. I talked to both tech supports from GS and SB.. And they need the time stamp to match files across drives and they both agree they can't simply add an option to 'ignore timestamp' as it will cause many more problems than the one it fixes.

Amazon screwed us already by doing unlimited, then took it away, and add in the timestamp problem, Amazon isn't the great deal it was before. Ample other solutions including MyCloud from WD, I put in a 3TB drive in the basement, it's readable from anywhere and you control your own files. I make the redundant backup there every day and it's usually 15 min. For my offsite, i'll find a different option that appreciates the importance of timestamps and doesn't screw with them.

Mostly love everything Amazon, but this one fails.

Hi, I have the same problem ! Looks like Amzon don't care about the situation as the previous message are really old.

Tested on google drive, I don't have the issue using my Sync software.

Any update on this? I'm currently uploading TB of data over and over continuously for the past few monthsas the "last modified" timestamp of many of my uploaded files are being changed after being uploaded. As other users have explained, back up applications rely on the timestamp difference to trigger files backup. Will most likely have to pass and stay with LiveDrive.

+100 on this. This is crazy that the file date changes. None of my syncs work. Just causes me to upload more data to Amazon...I am sure that isn't what you want.

Guys, any answer on this? I bet it´s a "must be fixed issue", since most 3rd part apps are not working accordingly.

+100 on that. This makes AMZN Cloud Drive virtually useless for all non-media storage. Many apps - esp. backup or sync apps - depend on modification times to determine coherency - at least as a first indicator. If you cannot depend on the mod time being reliable, then the only way you can ensure a file is not changed is by running some sort of checksum on the file (e.g. MD5). This is a) very slow and b) uses a lot of filesystem and network bandwidth. In the case of b) this is a detriment to AMZN as well as the user.

+1 on the request of having a coherent "modifiedDate".

I second this question. Our application depends on modifiedDate and spontaneous changes of modifiedDate (not related to user activity) make it hard to do any sync.