.vbm is not synchronized with the DB. To resolve this, run repository rescan

[mlumsden76]

Case # 07201508

We have a several veeam agents backing up to object storage repository that have recently come up with the error ".vbm is not synchronized with the DB. To resolve this, run repository rescan". I've been working with veeam support for over a week, sending logs and information. Today we had a remote support session to review the issue and the only resolution we could reach was to start a new backup job. There is no way to remove the .vbm file and rescan with object storage. Can someone take a look at my case and comment on that?

These agents pivot through cloud connect configured storage an get their backup policy from service provider console.

[Mildur]

Hello Michael

I'm not aware of any workaround besides creating a new backup job. Let me check with the team.
How often do your agent fail? Does it happen often or is it a one time issue?

Best,
Fabian

[mlumsden76]

The job was running OK daily for months, and then it just started failing, and fails every time now. We several agents failing in this way, I'm unhappy with the solution that I just start a new backup job. The solution to fix this issue on a standard storage repository was to just delete the .vbm. That would always work. I guess you can't delete this file when the backup data is object storage though.

[Dima P.]

Hello Michael,

We've asked support team to collect all the needed information for troubleshooting and share it with our QA team for the investigation. Stay tuned for updates via support channel. Thank you!

[Ivan239]

I guess you can't delete this file when the backup data is object storage though.

Support can upload an empty VBM into the object repository backup checkpoint from the cloud connect side using a hidden cmdlet.
This is equivalent to deleting it from the block repository, but I’m not 100% sure that it will solve the issue in the case of an object repository.

[mlumsden76]

Thank you Ivan. That's interesting. I'll see what the support engineer comes back with, and mention this if they don't offer it as a solution.

[admd]

Hello !

I have the same error, we can't delete the .VBM on the S3 Storage.
What solution was given to you from the support team ?

Thanks for your help.

[MaartenA]

Support has a workaround for it with a couple of steps. One of the steps is to attach the tenant to a temporary VBR server and then choose to remove it from configuration / rescan cloud repository / remap backup on agent side. Ask support for the complete steps.

[murphyranch]

Did anyone get the steps to do the work around on this? I too am seeing issue. It is sporadic and a rescan of the repository fixes it for a while.

Thanks in Advance.

[Dima P.]

Hello Bruce,

Please raise a support case and share the case ID with us. Thank you!