I can't see why the replication process can't see the existing seed source. I included in attachment to this ticket screenshots of settings and cloud inventory information that I expect should satisfy the job requirements.
Userlevel 7
+4
Did you check the pre-reqs for replica seeding?
https://helpcenter.veeam.com/docs/backup/vsphere/replica_seeding.html?ver=120
Userlevel 7
+20
Also, this is not a Support forum. If you need to get technical support, then open a support ticket and post on the Forums for further assistance - https://forums.veeam.com
Userlevel 7
+17
A couple requirements
If it’s still not working, the only other option would be to open a support case as Chris suggests. Mapping has a higher priority than Seeding, but I see you don’t have Mapping enabled, so the job using Mapping over Seeding isn’t the issue.
Userlevel 7
+17
Here’s the info from the Guide on how to create the Seed:
https://helpcenter.veeam.com/docs/backup/vsphere/replica_create_seed.html?ver=120
Userlevel 7
+6
I’ve only seen this when I setup backups and replica’s at the same time, but the backup hasn’t yet run to place data into the repository to use as seed data. In that case, I wait until the initial backup has run, or I start the replication without using seed data from the back repo. If these scenarios don’t fit your use case, I’d proceed with support to determine the source of the issue as I’m not sure what would caused seed data to not be seen in the repo if it is there.
Comment
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.