"VM ‘<VM_ID>’ was recovered in optimized reprotect mode in another replication group"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• After performing a successful failover, you remove the recovered VM and then re-register it, when you attempt to configure a replication for this VM, the process fails with the following error:
  
  
• VM ‘<VM_ID>’ was recovered in optimized reprotect mode in another replication group. To configure new replication for the VM, you must first remove the existing recovered replication.
  
  
• You will see the same error on the recent tasks under Site recovery page.
  
  
• You will see the 'VM' you are trying to add will be showing as Recovered in the replication tab as shown below:

       

Environment

vSphere Replication 8.x

vSphere Replication 9.x

Cause

• The error occurred because the VM 'VM_ID' was previously recovered in optimized reprotect mode, which automatically placed it in another replication group. This is how the system is designed to work, ensuring that the recovered VM stays linked to its previous replication setup.

Resolution

You must first remove the recovered VM from replication before re-adding it to the replication process.

Refer article: Disabling VMware vSphere Replication on a virtual machine