vRanger replications fail when attempting Hot-Add and falls back to network-based replication
possible VMWare process locking the vmdk, preventing Hot-Add.
1. Record the ESX server and datastore location for the VM (either source or replica)
2. In the vSphere client, migrate the VM to a new host and datastore
3. In the vSphere client, migrate the VM to the original host and original datastore
4. In vRanger, edit the replication job and re-establish the pre-seed information
5. Run the replication job
