Backup Resposiory scan has errors, not sure what it means and what to do?

Question

hello, thanks, i ran a manual re-scan of the backup repositories.

why are some repositories have `skipped` ?
some of the .vbm files are damaged?
i know VBAR has this scary quirk where for agent backups, even if i have the .vbk, i cannot restore without the .vbm

please advise, thanks, david

Starting backup repositories synchronization
Enumerating repositories
Found 10 repositories
Processing backup repositories
br_theserver03_theen10_cdrive_old: Synchronizing
br_theserver03_theen10_ddata: skipped 1
br_theserver03_theen10_cdrive: skipped 1
br_hetz05: Synchronizing
br_theserver03_theen10_falconer_02: skipped 2
br_thevserver03_Virtual-Machine agent_vserver03_01: skipped 1
br_theserver03_theen10_cdata: No backups found
Default Backup Repository: skipped 1
br_theserver03_ts-ubuntu01: failed 1
br_theserver03_theen10_falconer: failed 1
Warning Failed to import backup path V:|br_thevbr01|br_theserver03_theen10_falconer|VeeamAgentUser3bef6c4c-360f-11b2-a85c-9070b4e81f40|abp_theen10_falconer_-_theen10|abp_theen1.vbm Details: '', hexadecimal value 0x02, is an invalid character. Line 759, position 16980.
Warning Failed to import backup path V:|br_thevbr01|br_theserver03_ts-ubuntu01|vbj_thevserver03_ts-ubuntu01|user01-Virtual-Machine agent_vserver03_9063E.vbm Details: '', hexadecimal value 0x02, is an invalid character. Line 1, position 1.
Warning br_theserver03_theen10_falconer: Failed to synchronize 1 backups
Warning br_theserver03_ts-ubuntu01: Failed to synchronize 1 backups

Best answer by Tommy O'Shea

@asdffdsa6132, you can still get support from Veeam, though it is just a “Best Effort” support, not subject to any SLA.

While the VBM file makes importing the backups easier, if it is corrupt you can rename the VBM file with a “.vbm_old” suffix, and manually import the VBK file.
As with any tweaking to metadata, you should do so at the direction of Veeam support. I’d wait to hear what support has to say.

Tommy O'Shea · Accepted Answer

​@asdffdsa6132, you can still get support from Veeam, though it is just a “Best Effort” support, not subject to any SLA.While the VBM file makes importing the backups easier, if it is corruptyou can rename theVBM file with a “.vbm_old” suffix,and manually import the VBK file.As with any tweaking to metadata, you should do so at the direction of Veeam support. I’d wait to hear what support has to say.

Chris.Childerhose · Answer

Based on this I would say the VBM is damaged as it is saying there is an invalid character. For this issue it probably best to contact Support as there could be a number of reasons there is skipped backups and they can help with the other issue and VBM error.

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded