Problem:

svMotion is not supported with CDP replicas as it creates many extra files that are left behind thus breaking the replication.

Solution:

Currently the only workaround is:

1. Remove VM from job/policy
2. Remove replica vm from vsphere
3. Manually move the files from datastore to datastore
4. Re-add the vm in vsphere
5. Re-add the vm in the job/policy and use replica mapping to point to the just re-added vm