[VLCR] DR Failback committed in VMware Live Cyber Recovery version 7.26.x may fail during failback post upgrade to 7.27.x
search cancel

[VLCR] DR Failback committed in VMware Live Cyber Recovery version 7.26.x may fail during failback post upgrade to 7.27.x

book

Article ID: 320390

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

  • The failback plan compliance check "Recovery site" section will show an error at "Folders in protection group queries are mapped" indicating a Folder on the recovery SDDC is not mapped for failover.

 

  • If the user nonetheless proceeds through the failback wizard, the Preview step will show an error "Could not retrieve failover preview".

  • If the user nonetheless proceeds though that and starts failback, failback will fail shortly after it is started.

  • The issue only impacts failovers of plans containing folder-filter based Protection groups that were failed over in version 7.26.x and hence had the Protection Groups modified during failover to point to the VMC on AWS rSDDC. The system was them upgraded to vresion 7.27.x, and then a failback of that plan was initiated in newer version.

Cause

A step in failover was removed in version 7.27.x, as was its corresponding step in failback.That step changed the filter attributes of a folder-based Protection Group to use the vCenter of the VMC on AWS rSDDC and the mapped folder on the SDDC during failover, and changed it back during failback. A failover run in version 7.27.x does not have this issue.  

Refer VMware Live Cyber Recovery release notes here

 

 

 

 

 

Resolution

Please gather below information and open a support request with VMware by Broadcom

1) The protected site vCenter IP address

Note: if you know the failback plan name, you can find that in the VLCR UI and see the mapping to the protected-side vCenter.

2) The Protection Groups involved in the DR failback plan.

3) Org ID of your deployment.