PITR pod error - context deadline exceded

Percona Everest
1

Hello,
we have recently migrated a critical workload to the Everest solution. We also implemented backup using MinIO S3 storage and enabled the Point-In-Time Recovery (PITR) feature.

For the first two days everything worked perfectly. However, the pod is now failing repeatedly with the following error:

2025/06/24 07:05:52 ERROR: collect binlog files: manage binlog: put binlog.000807 object: put object *****: context deadline exceeded

I have verified the MinIO connectivity and there are no apparent reachability issues. Moreover, there are no further logs regarding this error, neither in PITR nor in MinIO.

Have you ever encountered this issue before? Is there a timeout setting that could be tuned to mitigate this?

Many thanks,
Davide

2

Could you provide the details on your setup of Minio with Everest for Backups?
I have been running a test from last couple of days but it didnt face any error like this.

What happens if you disable PITR and enable it back again?
Could you also try using mc client then put the object (Binary log that is failing) to upload?
Let us know how it goes.