502 status code return from S3 storage

[killianG]

Hello,

Do you know if VEEAM Backup & replication of Object storage in S3, supports a 502 status code response from any S3 api call?
I haven't found any documentation about this anywhere..

Thanks a lot for your answers
Best regards,

[HannesK]

Hello,
and welcome to the forums.

Can you maybe explain a bit more what the background of the question is? Is it whether we can show a "bad gateway" error message in case status 502 is returned? Correct, we don't list all HTTP status codes in our documentation because it's HTTP and our HTTP client must be able to deal with HTTP status codes to work.

Best regards,
Hannes

[killianG]

Hello Hannes,

I want to know if Veeam supports 502 errors from s3 compatible storage. When putting an object to aws s3 for example, what happens if aws respond 502 ?

Thank you,
Best regards,

[HannesK]

Hello,
status 502 / bad gateway leads to failed upload if that answers the question?

Best regards,
Hannes

[killianG]

Hello again Hannes,

Thank you for your answer, does it retry after receiving a 502 ?

Thanks a lot,
Best regards

[HannesK]

with every kind of error (there are many more), we retry, yes.

[killianG]

Hannes,

Thanks a lot, is it raising a notification or something like that when receiving 502 ?

Thanks for your answers,
Best regards

[HannesK]

Hello,
yes, for errors (also warning and success), there are notifications. I'm still curious why this thread has focus on status 502 as it is just one of many things that can go wrong

Notifications are available the following ways
- daily email report summary
- history view -> storage management
- Last 24 Hours


Best regards,
Hannes

[killianG]

Hello Hannes,

Thanks for your answer.

To clarify, I'm talking about Veeam performing offload job periodically to copy or move data from the performance tier to the cloud tier.

To complete the offload, Veeam may create a substantial amount of simultaneous connections to the S3 connector.
Under load, nginx will send 502 Bad Gateway error codes. Veeam does not retry this error and the offload jobs fail.

I hope this is clearer now

Thanks a lot for your time and answers,
Best regards

[soncscy]

> Under load, nginx will send 502 Bad Gateway error codes. Veeam does not retry this error and the offload jobs fail.

Hrm, but isn't this wrong behavior? The S3 system should return 503 _well_ before it throws a 502.

https://aws.amazon.com/premiumsupport/k ... hrottling/

The S3 layer ought know about when it's reaching its limits well before it needs to issue a 502. I don't know how Veeam handles it, but if I was designing it, 502 should only be thrown once the system has absolutely hit capacity and cannot do more, and I even question if this is correct to do. (just 502 is misleading, I don't think it's the right message)

[HannesK]

Hello,

Veeam does not retry this error and the offload jobs fail.

what is the Veeam support case number for that issue?

Yes, I also remember 503 and exponential backoff question ("slow down please")

Just curious: you use nginx as load balancer for on-prem S3 storage? what is your overall setup?

Thanks,
Hannes

[Andreas Neufert]

Are you sure that the offload will not retry after 15-30min?