KB ID: 105023
Cause 1:
If a full Replication job gets interrupted during its progress, and at the same time, an incremental job is scheduled for the same replication task, an error message may appear: "Target VM Name already exists."
Solution 1:
To resolve this issue, follow these steps:
1. Open the target ESXi server host.
2. Locate the particular replicated VM and delete it.
3. Run the Incremental job for the specific replication task.
Cause 2:
The target host may already have a virtual machine with the same name as the replicated VM.
Solution 2:
If there is already a virtual machine with the same name, rename the existing virtual machine and run the Incremental job for the specific replication task.
Cause 3:
During the restoration process to ESXi or vCenter, if the restore fails with an error message "VM Name already exists," it indicates that a virtual machine with the same name already exists in the target host.
Solution 3:
To address this situation:
1. If any virtual machine already exists with the restored VM name, try restoring again to ESXi or vCenter with a different name.
2. Alternatively, rename the existing VM with a different name in the target host and proceed with the restore to ESXi host or vCenter using the original name.