So I've run a recovery plan (single VM for now) without error (planned migration). I have my original VM powered off in my production site and my recovered VM running in my DR site. I'm trying to run a reprotect (using the original VMDKs as seeds). When I run the reprotect action I get the following error:
"Unable to configure replication for virtual machine 'MyVM' because group 'MyVM' cannot be created. Another virtual machine 'MyVM' that has the same instance UUID '5001e2c6-d3e3-16c3-3da3-4e4fcc0e1c62' already exists on protection site 'DRSITE'"
I'm interpreting this as being because the reprotect is attempting to create a placeholder VM back in the production site using the same instance UUID of the VM that is now running in the DR site. However, I already have a (powered off) VM in my production site with this UUID - my original production VM. I'm assuming that if I unregister this VM from vcenter then the problem will be resolved so will confirm this imminently. However, I've not found any documentation of the "planned migration" process that confirms that this step is necessary and expected, so am concerned that my environment is behaving correctly. Can anyone confirm that this behaviour is expected?