This is still an on-going problem (even in v9) when you rotate USB disks and choose NOT to use a repository with the Rotated Hard Disk option. The
problem seems to occur when the incorrect .vbm file is present on the plugged in USB disk, probably because the disks haven't be changed at the
correct time (e.g daily on specific days). What is a pity is Veeam doesn't have the option to auto-rescan the DB, because this would then allow the job
to run successfully. We have many clients running Veeam and the only option is to initiate a manual rescan after the failed Backup job. The reason
we prefer not to use the Rotated Hard Disk option is this creates a fresh VBK if the wrong disk is plugged and we loose the roll-back history.
I believe an auto-rescan DB or rescan DB via a PowerShell command would be a useful addition.