I have a backup schedule that run a full backup each Sunday and an incremental bacup Monday->Saturday and uploading it to my Amazon S3 account.
This has been running fine for quite a while, but last weekend the full backup log ended with this:
Uploading archive to Amazon's S3 server .. .. upload failed! HTTP/1.1 400 Bad Request
I took a manual rerun of the full backup and thought it might just be a server problem @ Amazon.
But then again today after the next full backup:
Uploading archive to Amazon's S3 server .. .. upload failed! HTTP/1.1 400 Bad Request
Is there anywhere I can find a more detailed log? From what I can see in Amazons documents this error appears when there is something wrong with metadata or POST-data?
My schedule is configured for all virtual servers, file under bucket, one file per server, continue on error and level = full. My incremental backups seems to run just fine still.
Any ideas what this might be?
I haven't seen a 400 error from Amazon before, but it would be interesting to know what conditions are triggering this.. for example, does it happen only when backing up certain domains, or to a particular bucket?
Also, does it happen all the time, or only occasionally?
--
Check out the forum guidelines!
check the time server.
Some times a worng server time give this error.
roberto
So, just to give you guys an update on this:
I did absolutely nothing. The next weekend the full backup ran just fine and no error message from Amazon. The same this weekend, full backup went just fine with no errors.
Not sure what my conclusion should be for this matter. It seems odd that two weekends in a row would stumble upon the same non consistent server-error at Amazon, and then run just fine the following two weekends, but I haven't got a better explanation for it.
I'm just happy it is up and running as before and not giving me any more of those slightly scary e-mails on a sunday morning. :)
I am getting same error as above Please any can help me
please mail me your suggestion
advance thanks