This issue can generally be resolved by removing the reference to the replica out of Veeam and then mapping the replication job to use the existing replica.Important: If you do not see a replica VM either in Veeam or in VMware, please create a new job.
The steps for doing this are below.
Part 1: Remove the Replica from configuration.
- Navigate to the replica in the “Ready” section under “Replicas”
- Right click the replica and click “Remove from configuration”
Note: Removing the replica from configuration will remove the source VM from the job as well. You will add this back to the job in the next step.
Part 2: Map the replication job to use the existing replica.
- Navigate to the replication job. Right click the job and click “Edit…”
- In the “Name” section, check the "Low connection bandwidth" option
- Click next to the “Virtual Machines” section, and add the source VM back into the replication job
- Navigate to the “Seeding” section, and check the “Map replicas to existing VMs” check box
- Select the original VM, and click “Edit…”, then select the existing replica
- Click “Finish”
After doing this the job will need to calculate the digest, which can take an extended amount of time.