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. “
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.
If the backup appears under Backups>Disk or if the repository field is blank, you should right-click>Remove from Backups
Next, switch to the Backup Infrastructure view and rescan the repository:
The statistics should show that the backup was added:
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:
Note: Imported is hidden if it is empty.
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.