S3 error: The specified key does not exist.

[EWMarco]

Hi

I have just created a new job with corresponding copy job. The copy goes to a SOBR with S3 buckets only. Dozens of VMs are being copied successfully, however there's a handful that give the error mentioned.

Further in the error line it says "Storage chain is corrupted. Some objects are missing. Failed to load object."

I find this puzzling as this is the copy of an initial full backup. Obviously there should not yet be a chain that could be corrupt.

Can anyone shed light on this?

I have a case open on the matter, 06117857.

[veremin]

Let's wait until the support engineers process the provided debug logs and come to the conclusion. Thanks!

[ANT1H3R0]

I'm having this same issue. Have you gotten any resolution from Veeam on a fix?

[PetrM]

Hi Jason and Welcome to Veeam R&D Forums!

The error is quite generic and can may persist due to various reasons. Please contact our support team and provide a support case ID as requested when you make a post about a technical issue. We cannot troubleshoot technical issues effectively over the forum posts. All posts about technical issues without case ID will be eventually deleted by the forum moderator. You can also upload debug logs for our support as per the instructions of this KB.

Thanks!

[ANT1H3R0]

I have a case open, its 02955958. This is actually the second time I've opened a case for this issue. First time this happened I had to pretty much recreate all of my backup jobs to fix the issue.

[Gostev]

Perhaps your object storage is misbehaving then?