Replication job fails with error:

Can't delete replica when it is being processed.

 

If a replication job failed before the replica VM is fully created, the job may fail attempting to delete the VM as part of an undo operation on the failed run.

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.

1. Navigate to the replica in the “Ready” section under “Replicas”
2. 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.

https://helpcenter.veeam.com/docs/backup/vsphere/remove_replica_from_configuration.html?ver=95
 

Part 2: Map the replication job to use the existing replica.

1. Navigate to the replication job. Right click the job and click “Edit…”
2. In the “Name” section, check the "Low connection bandwidth" option
3. Click next to the “Virtual Machines” section, and add the source VM back into the replication job
4. Navigate to the “Seeding” section, and check the “Map replicas to existing VMs” check box
5. Select the original VM, and click “Edit…”, then select the existing replica
6. Click “Finish”

After doing this the job will need to calculate the digest, which can take an extended amount of time.