-
-
Notifications
You must be signed in to change notification settings - Fork 902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s3cmd sync copies all files, even if they are unchanged #1372
Comments
I'm unable to diagnose this, but suspect that our S3 bucket configuration could be the cause. A single bucket is set up with a "folder" for each user to backup in to, using a similar method to this AWS blog. Will s3cmd sync work if it cannot write or delete pre-existing files in a bucket? |
I can confirm that the problem I see seems related to being unable to delete files. I set up a basic bucket with versioning enabled but otherwise defaults. With this test bucket "incremental" updates with I haven't yet put my finger on the exact cause. |
Sadly I'm going to have to give up on this and find an alternate utility. It's a pity as this is so very close to meeting all our needs! |
I'm attempting to create a backup solution. It needs to be capable of incremental copies using
s3cmd sync
and to preserve file permissions. (I can ignore the fact that directory permissions aren't preserved at the moment). I'm writing from Linux systems to an S3 bucket in to different "folders" in the one backup bucket.Unfortunately in all my testing the
s3cmd sync
command copies every single file every time, even if the file has not changed in any way. This is not what I had expected.The
--skip-existing
switch skips all existing files, even if they have changed. (Oddly the debug shows that s3cmd does all the slow md5sums checks first and then ignores them.)How can I use
s3cmd
to get an rsync-like sync from Linux to an s3 bucket please?EDIT: I'm currently using s3cmd version 2.2.0 from the Ubuntu repos, but will update if there are relevant bugfixes. Thanks!
The text was updated successfully, but these errors were encountered: