[DRaaS] Contents for VM (vm name) already exist in the workload Datastore. Recovery will not be attempted from VCDR

Products

• VMware
• VMware Live Recovery

Issue/Introduction

To explain why VCDR protections may fail on VM's previously protected by Site Recovery Manager (SRM) and vSphere Replication (VR).

Symptoms:
While attempting to protect a VM with VCDR the following error message maybe seen: "Contents for VM (vm name) already exist in the workload Datastore. Recovery will not be attempted."

The VM was previously Protected by Site Recovery Manager/vSphere Replication.

 

Cause

Workload datastore files need to be cleaned up after removing Site Recovery Manager and vSphere Replication protections have been removed from the VM(s). VCDR will not protect the machines until the leftover vSAN datastore files for the VM(s) are removed.

Resolution

• Verify the name of the VM(s) that have been removed from Site Recovery Manager and vSphere Replication protections.
• Verfify if vSAN workload datastore has a placeholder for those VM(s). Even though the VM has had protections removed, the place holder in the workload datastore still needs to be cleaned up.

The screenshot below shows what a placeholder workload datastore file would look like, there are no .vmdk files in the folder.

• Clean up and remove any workload datastore placeholders for the VM(s) and try re-protecting from VCDR

Additional Information

Impact/Risks:
Do not remove vSAN datastore files without confirming that the appropriate files are being removed to avoid data loss. If there are .vmdk files and other files are tied to the VM(s) listed in the datastore removing those files because removing incorrect files will cause data loss and impact the SDDC.