Other 2 suggestions (logs + errors)

[murgurgula]

Hello,

It's me again with more suggestions :D I use s3s3mirror in prod and have to make sure all the data is copied.

Amazon trows errors sometimes and rejects the copy. I estimate that the s3bucket thinks u r DDoSing it and rejects the connection, which is normal, since the rate transfer is "too much".

However, this is prod, so I have to make sure no files are missing, so in my backup script, I run s3cmd after s3s3mirror is ran and I see lots of data missing.

It would be great, if the s3s3mirror output the failed files in a logfile somewhere (that we can define, as with .s3cfg suggestion), it would be easier to sync them later. It's cool to make the error log optional, since it can kill the disk (IO, eat all the space, etc) and kill the machine running the s3s3mirror.

Also (I'm not sure how easy/hard to do this one), when we use s3cmd and it fails, there's an error message like "permisison denied", "no such bucket", etc. It would be easier for people who use the tool to have the same kind of output to troubleshoot instead of the angry JABBA error. Most likely, amazon returns an error code and the tool catches it and trows JAVA error because it can not continue. Is there somehow a way to print the message amazon trows? It would be such a time saver...

Cheers!

Murg

[cobbzilla]

I love this idea. And yes, it is totally do-able. I'm marking this issue as "enhancement" and will get to it unless you'd like to beat me to it (you are more than welcome to!)

cheers.