VMware vSphere • SOBR Offload and Direct to Object Rescan Issues

I'm creating this post to get some insight into what could be causing SOBR object repository offloads and direct to object repositories to continually need rescans. As a Service Provider, we've had numerous cases into Veeam Support over the last few years due to SOBR offload issues and direct to object storage backups needing rescans. Sometimes rescans will fix the issue but there are also times where we have to reseed the jobs or totally replace the capacity tier extent. This is no small task especially when these tiers sometimes hold upwards of 250TB. I don't know if this is just expected with the amount of SOBRs and direct to object repositories we support, but it's a continuing issue. The issue affects numerous different Veeam servers even some in tenant sites so it's not environment specific. However, the object storage is mainly Wasabi us-east-1.

Below are some of our case numbers that I found over the past few years with a quick search through existing and closed tickets related to the object storage. All of them are slightly different but all related to the SOBR or direct to object backup functionality in Veeam.

Case #06032122
Case #07047854
Case #07383849
Case #07528925
Case #07828798
Case #07828667

These are not the only times we have the issues as we will put a ticket in usually if the simple rescan doesn't resolve the issue. We see the rescan issues with SOBR offloads and direct to object backups on almost a daily case to which we have to continually rescan these repositories. I'd appreciate any input as to what could resolve this permanently.

Eric

Statistics: Posted by EricinIT — Sep 24, 2025 11:58 pm

---