Cannot find VM in the backup file specified for seeding

KB ID:
1866
Product:
Veeam Backup & Replication
Version:
6.x, 7.x
Published:
Last Modified:
2014-05-20

Challenge

A replication job fails with the error “Cannot find VM in the backup file specified for seeding.” You may also see the error “VM ‘<vm name>’ not found in backup for initial sync. “

Cause

The configuration database has not been updated to link the backup files to the repository. This may be due to a missing or corrupt .vbm metadata file, or user error. 

Solution

If the backup appears under Backups>Disk or if the repository field is blank, you should right-click>Remove from Backups

User-added image



Next, switch to the Backup Infrastructure view and rescan the repository:

User-added image

The statistics should show that the backup was added:

User-added image

If no backups were added, verify that the .vbm (metadata) file and .vbk (full backup) file are present in the folder specified in the repository settings, or one of its subfolders. If you suspect the .vbm file is corrupt, try copying it again from the original location.
 
For seeding to work, the backup containing the VM to be replicated must appear under Backups>Imported with the repository specified for seeding:

User-added image

Note: Imported is hidden if it is empty.

More Information

A known issue resolved in 6.5.0.144 could also produce this error. See Patch #3 for Veeam Backup & Replication 6.5
 
If you are unable to resolve the seeding issue, try to restore from the backup and then map the job to the restored VM: How to Manually Seed a Replica


Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
3.8 out of 5 based on 11 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit