Cannot find VM in the backup file specified for seeding
| KB ID: | 1866 |
| Product: | Veeam Backup & Replication | 10 | 11 |
| Published: | 2014-04-14 |
| Last Modified: | 2022-09-10 |
Challenge
A replication job with seeding enabled fails with any of the following errors:
Failed to create processing task for VM <VM> Error: VM [VM] not found in backup for initial sync
![Screenshot of Failed to create processing task for VM VM Error: VM [VM] not found in backup for initial sync](http://cdn.veeam.com/content/veeam/en/knowledge-base/kb1866/jcr:content/content-parsys/section-main/section-with-background-content/section-sections/section-with-background-content/section_with_backgro_challenge/section-with-background-content/image/file.web.ntfile.png/VMwareReplicaSeedError.png)
Cannot find VM in the backup file specified for seeding
Error: Specified seed repository does not contain backup of the required VM.
Cause
These errros occur when the Replication job's seeding task cannot identify a replica seed in the reposistory for the VM that needed to be seeded.
The seeding operation of a replication job Replica seeding is done using restore points (replica seeds) that exist in the replication target site to reduce the amount of replication traffic, as opposed to sending all the replication data across a slow bandwidth connection.
Solution
- Review the "Creating Replica Seeds" procedure to ensure all the initial seed creation and placement steps have been followed correctly.
- Rescan the Repository where the replica seeds are stored.
The only way restore points can be added to the database and associated with a repository is for them to be detected during a repository rescan. - Edit the Replication Job and make sure the Repository where the replica seeds are stored is selected for seeding.
- Review the list of restore points under Backups > Disk (Imported) to determine if a replica seed (restore point) for the VM failing to seed is listed with the repository name listed in the repository column.
Next steps based on what you observe:
- If no replica seed is available for that VM associated with Repository being used for seeding, review the underlying storage and ensure that the replica seeds are present on disk.
- If you observe that a replica seed for the VM is present under Backups > Disk (Imported), but the repository column is empty, this indicates that the replica seeds were incorrectly imported using the Import Backup function. To rectify this, use the Remove from configuration function to remove those backups from the database and rescan the repository where the replica seeds are located.
- If a replica seed (restore point) for the VM is present and the correct repository is listed in the Repository column, ensure that the VM is added to the replication job via the same vCenter/Cluster/Host as it was added to the seed-generating backup job.
If the seeding operation continues to fail, perform manual replica seed as is documented in KB1760.
More information
When the seeding function is enabled in the Replication job, a seeding operation is initiated when there is no Replica associated with the VM being replicated. A seeding operation will occur under the following circumstances:
- A VM is added to the replication job, and no existing replica is mapped to that VM.
- The Replica, for a previously successfully replicated VM, has been deleted from disk.
- The underlying Reference ID used by the virtual environment to track the VM has changed.
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
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.