1-800-691-1991 | 9am - 8pm ET
EN

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

KB ID: 2787
Product: Veeam Backup & Replication, Veeam Cloud Connect
Version: All
Published: 2018-10-23
Last Modified: 2020-08-13
Languages: FR

Challenge

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

Cause

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.

Solution

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.
KB ID: 2787
Product: Veeam Backup & Replication, Veeam Cloud Connect
Version: All
Published: 2018-10-23
Last Modified: 2020-08-13
Languages: FR

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.