This is against s3cmd 1.5.0-beta1
For backing up our data, I first do an s3cmd sync, then do a complete local and remote listing with md5 sums, then diff it. Last night's backup did a LOT of remote copies, and for some reason, about 10% of them ended up in wrong files (~79 out of 769). What's more interesting is that when I re-ran the same sync, it correctly identified the wrong files and replaced them.
I have not gone in and investigated the logic used for remote copies. I'm doing a sync of an Artifactory backup, but I suspect there are local files that are getting renamed or copied over in the local backup; e.g. (from the sync logged output):
remote copy: artifactory.config.xml -> etc/artifactory.config.latest.1398439773000.xml
remote copy: artifactory.config.xml -> etc/artifactory.config.latest.xml
The first file copied had the wrong md5 sum, but the second one was correct.
I did some searching for this issue, and did a git clone and 'git log --grep="remote copy"', and don't see any changes that might affect this issue, so haven't tried the latest bleeding edge. Let me know if there's any other data I can gather, thanks!
Log in to post a comment.