trying to use the seeding option for Replication to a Cloud Connect Replication Service Provider
both Tenant and SP have v9.5 ga installed
Case # 02008110
have a backup file with 2 servers located on an SP repository.
able to see the backup file on the Tenant Veeam server, can even do an FLR of a file from each of the backed up servers. Same thing on the SP Veeam server.
So i feel fairly confident that each server can properly see the backup
on the Tenant server setup the replication job with low bandwidth option and selected seed from backup file and provided the proper repository as the seed.
job starts and runs for a while and then each seed task for both VMs fails with
12/19/2016 9:47:56 AM :: Failed to create processing task for VM convert-ho Error: VM 'convert-ho' not found in backup for initial sync
checked the job logs and did not find any additional information, just an indication that it cannot find the backup file.
did a web session with 1st Level Support and was recommended to try restoring each VM at the SP and then use mapping. Don't want to use that method for our Customers but gave it a try.
Restored both VMs but in the mapping step no VMs are available to map to. Tried putting the restored VMs into the datastore as specified in the Hardware Plan, same result, nothing available to map.
found this Article https://helpcenter.veeam.com/backup/vsphere/replica_seeding_vm.html
which clearly details both backup and mapping seeding methods. Followed it all and no change, backup seeding fails, mapping seeding finds nothing to map.
the article mentions using the Detect button in the mapping but in my case it is ghosted whether an original vm is selected or not.
just hoping that someone has done the seeding step successfully in v9.5 and can provide some pointers as to what they may have done or where they may have placed the backups or restored VMs so that the seeding step works.