Failback plan or Sync back with Folder mapping in VLCR includes VMs that are not part of the Protection Group mapped.

Products

• VMware Live Recovery

Issue/Introduction

• Failover was performed on multiple Recovery plan mapped to same folder in the Recovery SDDC 

For eg: Recovery Plan 1 mapped to Protection Group A and mapped to Folder Test in Recovery SDDC vCenter. Recovery Plan 2 mapped to Protection Group B and mapped to same Folder Test in Recovery SDDC vCenter. 

• When performing a failback/sync back after creating a Failback recovery plan from the failover action with folder mapping, it will include VMs which are not part of the failback plan but are part of the same folder in Recovery SDDC vCenter. 

Environment

VMware Live Cyber Recovery 7.27.x

Cause

If the same folder is mapped for recovery in multiple recovery plans, the failback of one recovery plan will include all the VMs in the folder in the rSDDC vCenter. This is applicable if the recovery plan is using folder based Protection group. Because during the failback, it will search membership based on folder and it will pick all VMs in the folder.

Resolution

This is an expected behaviour. To avoid this situation, ensure to have unique folder mappings on the recovery SDDC for the folder based PGs recovery plans.

To workaround if the failover was already performed to same folder in rSDDC vCenter 

1. Before initiating the sync/failback, Create a new Folder (DR-temp) move the VMs which are not part of the failback plan you are attempting.
2. Wait for 2 minutes.
3. Refresh the Compliance Checks of the Failback Plan, and verify that there are no errors.
3. Verify the Preview of the Failback plan that it contains the only VMs it should have.
4. Cancel the Preview
5. Now, initiate the sync back/failback of this Plan.
6. Make sure the sync back/failback is successful, and acknowledge it.
7. After this, move VMs which should be previewed per the next plan you want to attempt.