Skip to main content
Question

after veeam migration, repo not syncronised backup errors now occur

  • July 28, 2025
  • 4 comments
  • 189 views

MavMikeVBR
Forum|alt.badge.img+1

After move to a new veeam server and restore of database, jobs failing with the error below. I’ve done a rescan as well

Task failed. Error: Cannot proceed with the job: existing backup meta file ‘FILE.vbm' on repository 'repo_XFS' is not synchronized with the DB. To resolve this, run repository rescan

4 comments

Mohamed Ali
Forum|alt.badge.img+2
  • VUG Leader
  • July 28, 2025

@MavMikeVBR  Disable the jobs and then go to the backup repository and rename the existing .vbm metadata file to “FILE.vbm.bak”. After that rescan the repository from the Veeam console.

This will force Veeam to re-detect the backup files and generate fresh metadata. Once the scan completes, edit the job, map it to the detected backup chain if needed, re-enable the job, and run it again. 


MavMikeVBR
Forum|alt.badge.img+1
  • Author
  • Influencer
  • July 28, 2025

@MavMikeVBR  Disable the jobs and then go to the backup repository and rename the existing .vbm metadata file to “FILE.vbm.bak”. After that rescan the repository from the Veeam console.

This will force Veeam to re-detect the backup files and generate fresh metadata. Once the scan completes, edit the job, map it to the detected backup chain if needed, re-enable the job, and run it again. 

problem is, the backups are immutable on this repo


Mohamed Ali
Forum|alt.badge.img+2
  • VUG Leader
  • July 28, 2025

In that case do not try to rename the vbm file. Instead, remove the backup from the configuration (Backups → Disk → Right-click the affected backup → Remove from configuration). Then rescan the repository and re-map the job and try to trigger the backup again.

If it fails again, I recommend opening a support case with Veeam technical support.


Marcel.K
Forum|alt.badge.img+11
  • Veeam Legend
  • July 29, 2025

Did you try to reinstall transport service on repository?