Hello dear Proxmox-Community,
We are using a Proxmox Backup Server to back up data to S3. However, we are encountering errors during various operations. In the logs, we found these multiple errors:
2026-02-08T22:42:27+01:00: <Error><Code>SlowDown</Code><Message>Please reduce your request rate.</Message><RequestId>s3-bridge/H7Qk8EVpeL-41753582</RequestId></Error>
2026-02-08T22:42:27+01:00: failed to remove dir "ns/server1/ct/908/2025-11-29T09:42:35Z": unexpected status code 503 Service Unavailable
We would like to know whether there are any settings on the Impossible Cloud side or on the Proxmox side that we can adjust to prevent these issues from occurring.
When deleting larger datasets or performing other operations, the error causes the process to abort and results in a significant amount of manual rework.
Additionally, in the S3 endpoint configuration there are settings such as Rate In/Out and Burst In/Out. We are wondering what values should be configured there in our case?
The Impossible Cloud Support recommended us, that we contact Proxmox and should ask them to implement an appopriate exponential backoff/retry mechanism, as recommended by AWS: https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/retry-backoff.html
Thank you very much for your assistance.
Kind regards,
ceneos
We are using a Proxmox Backup Server to back up data to S3. However, we are encountering errors during various operations. In the logs, we found these multiple errors:
2026-02-08T22:42:27+01:00: <Error><Code>SlowDown</Code><Message>Please reduce your request rate.</Message><RequestId>s3-bridge/H7Qk8EVpeL-41753582</RequestId></Error>
2026-02-08T22:42:27+01:00: failed to remove dir "ns/server1/ct/908/2025-11-29T09:42:35Z": unexpected status code 503 Service Unavailable
We would like to know whether there are any settings on the Impossible Cloud side or on the Proxmox side that we can adjust to prevent these issues from occurring.
When deleting larger datasets or performing other operations, the error causes the process to abort and results in a significant amount of manual rework.
Additionally, in the S3 endpoint configuration there are settings such as Rate In/Out and Burst In/Out. We are wondering what values should be configured there in our case?
The Impossible Cloud Support recommended us, that we contact Proxmox and should ask them to implement an appopriate exponential backoff/retry mechanism, as recommended by AWS: https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/retry-backoff.html
Thank you very much for your assistance.
Kind regards,
ceneos
