This article is not intended for use with:
The following are error messages that may prompt the use of this KB article:
Unable to repair replica VM.
File or folder already exists.This occurs most often when a loose file is named like a snapshot but is not associated with the replica (e.g., DC01-0000001.VMDK), is in the folder with the replica files. When VMware creates the first snapshot on the replica it can’t because the file it was going to create has the same name as the aforementioned loose file.
Invalid Snapshot ConfigurationVerify that the error is coming from the replica by checking the replica's Tasks & Events.
CID mismatch error: The parent virtual disk has been modified since the child was createdVerify that the error is coming from the replica by checking the replica's Tasks & Events.
Please be aware that as an alternative to performing the steps below, you may first attempt to clone the faulty replica within VMware; if it succeeds, map the Replication job to the clone of the replica.
Note: Before beginning:
Within the Veeam console under Replicas, find the replica that will be repaired and right-click it; from the context menu, choose “Remove from replicas…” ("Remove from configuration")
After you use the “Remove from replicas…” ("Remove from configuration") function, it will remove the VM from the Replication job. You will have to add the VM back to the replication job manually.
Using the datastore browser, go to the folder of the replica.
Most likely, there will be many files; keep in mind that the only files that are required are:
So, for example, here is a folder pre-cleanup post repair.
We can remove the following files:
Leaving the VMX, VMXF, NVRAM, and the VMDK for each disk. Removing the associated snapshot files that are no longer needed.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case