How can you recover from an i/o error reading a .VBM file?

[jimerb]

One of my backups has a corrupt.vbm file.

Looks like a simple I/O error on the backup disk. I cannot even open it in notepad (It's only 59K),

Is there I can rebuild this file? If I delete it will VEEAM try to recreate it?

[Gostev]

The good news is VBM file is not essential. You will be able to import backups even without it, it will just take a little longer. So yes, you can delete it.

I believe there in fact a way to re-create it too from the data in actual backup files, but for this it is better to contact support.
Re-creating VBM file will allow your existing jobs to continue the chain normally.

[jimerb]

The problem is that the next backup job is failing because it can't read the file. What if I rename it and run the backup again?

[chris.childerhose]

You can try renaming or deleting then run a Full Backup again as I am sure that recreates the file. It will not continue the current chain but only way to fix it.

[jimerb]

That worked! I have this setup for scaleout to Azure. Is Veeam smart enough to clean up what's in the cloud?

[chris.childerhose]

I believe there would be some manual cleanup now that a new chain has started. You could wait for your retention period to pass to see if Veeam does it automatically but now that the backup is associated to a new VBM and chain I am pretty sure it will not.

[Gostev]

Also, following such a storage error you will definitely want to replace your backup target, because your actual backups may either be already corrupted or will experience similar corruption soon.