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:
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.
Tenants who are unable to map replicas should ask their service provider whether this workaround is available.
Note: The console used for these steps may still display the replica after the service provider is removed in step 5; the replica should not appear the next time the console is opened.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case