- Newest
- Most votes
- Most comments
The command you want to do is aws s3 sync s3://bucketname1 s3://bucketname2 --force-glacier-transfer --storage-class STANDARD
There is a known issues here - https://github.com/aws/aws-cli/issues/1699
Basically, when you do a restore, the CLI still thinks it's an archived object. The above command will force it to do the sync anyway, and wont initiate a new restore.
Try to check this page(https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html) and play with different params.
Maybe you should provide --storage-class GLACIER
or pass --force-glacier-transfer
.
In general, I do not think moving 30 Tb using s3 sync
is the best option. If your buckets are in the same region, I would suggest to try Amazon S3 Batch Operations
. You create a job, specify source, destination, maybe smth. else and AWS will run this job for you. I did it couple of times and it worked just fine.
Hey MaxBorysov
Thanks for the message. I used --force-glacier-transfer and it worked
Hi There
Can you try adding the --force-glacier-transfer
option to the CLI command?
--force-glacier-transfer
Forces a transfer request on all Glacier objects in a sync or recursive copy. [1]
[1] https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html
Hey Matt-B
Thanks for the message. I add the --force-glacier-transfer and it did the trick.
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Hey micah
Thanks for the message. The article you mentioned helped me with other minor issues related to this transfer. And I used --force-glacier-transfer as you also mentioned.