This KB article documents the procedure for mapping a replication job to a replica that was not created by a tenant's replication job.
Use case examples:
- The tenant has sent backup files to the Service Provider, and the Service Provider restores the VMs from the backup files to create replication mapping targets.
- The Service Providers environment has been impacted in such a way that the hypervisor reference IDs have changed and the tenant's job can no longer find the previously existing replicas.
When creating a replication job, seeding or mapping can be used to minimize the amount of traffic sent to a Cloud Service Provider. In most cases, seeding is the preferred method because it is not possible to map a Cloud Connect replication job to a replica that was not created with Cloud Connect. However, it is possible for a Cloud Service Provider to work around this limitation by replicating the existing replica.
Note: It is not possible to use a backup of a replica as a seed, because Veeam searches the backup file for the ID of the source VM, which is different from the ID of the replica.