Issue with SOBR and other issues.

[d42d01]

I've been having an issue with Veeam failing to synchronize with object storage (Backblaze). After rescanning the SOBR successfully I get two different errors when the backups run. The first is "cannot initialize new storage with unsupported format version". That error should age out once it reaches the retention policy. The second error is "local index is not synchronized with object storage" again. That job, which I call APP1 is the biggest issue. The job is offloading the data to the capacity tier but the data in the performance tier does not get dehydrated. So the backup data fills the performance tier and then all the jobs fail. I have multiple SOBRs and they each have there own capacity tiers and performance tiers. None of the other SOBRs are having this issue.

I don't have any more storage available locally so starting over isn't really an option. For now all the backup jobs that are using the SOBR with the sync errors have been disabled.

I have a support ticket open (05221757) since this issue started back in 1/9/2022. I've uploaded logs and spoken to support and they have grabbed screenshots and I've explained to them in greater detail what the issue is. I've escalated the ticket and called repeatedly to get an update. And I still have not received any updates with regards to the specific issue for APP1. I'm not sure if the first error has any affect on the offload process and if that would that cause the second issue. The other backup jobs that are using the same SOBR do not have any errors and they are working correctly (offloading, dehydrating etc).

We've been using Veeam for over 5+ years now and I've never had any issues with tickets or support responding in a timely fashion until now. So has anyone else had issues with jobs not dehydrating after an offload is completed that would explain the local index not synchronized error?

Thanks,
D

[wishr]

Hello D,

Welcome to Veeam R&D Forums and thanks for posting!

As far as I see your case has been escalated and our engineers are looking into it. Let's wait for their response and see what they will be able to find out.

Upd: I've pinged our support management, just in case.

Thanks

[d42d01]

It turns out there are duplicate folders in the object storage bucket. The strange thing is we deleted the duplicates using S3 browser but now it looks like the root folder is gone. But if I use Cyberduck to browse the bucket the root folder is there along with the duplicate folders.

[wishr]

Hello,

Have you had a chance to discuss it with the object storage vendor?

Thanks