Replication Error: The name '{vmname}' already exists.

Veeam Backup & Replication;Veeam Backup & Replication Cloud Edition
Last Modified:
KB Languages:


Veeam Backup & Replication replication job fails with the following error message:

Processing <vmname> Error: The name '<vmname>_replica' already exists.

User-added image

When the error above occurs within Veeam Backup & Replication the following correlating event can be found within the vSphere Events.

VMware Error


This error occurs when a Replication job sends the "Register virtual machine" task to the vSphere environment, and a VM already exists that matches what the replica would be named.

Note: The default suffix for replicas in Veeam Backup & Replication is '_replica'. If the suffix has been changed in the job settings the failure error will reflect this different suffix.


Important: If the replication job has been configured so that no replica suffix is specified, and the job is configured to target the same vCenter as the VM being replicated, this error is occuring because you cannot create a replica that would have the same exact name as the production VM. If the replication destination shares a vCenter with the VMs being replicated, a replica suffix must be configured within the replication job.

To resolve this issue, do either of the following:
  • Configuring Replica Mapping for the existing replica named in the error message. This will allow the Replication job to reuse the existing replica.
  • Delete the existing replica VM named in the error. This will allow the Replication job to create a new replica VM.

More Information

Under no circumstances should two different Replication jobs ever be mapped to the same replica.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
2.5 out of 5 based on 8 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: