[VCDR] Recovery fails if External NFS Datastores are mounted in a VCDR recovery SDDC

Products

• VMware Live Recovery
• VMware Cloud on AWS
• VMware Cloud on Dell EMC

Issue/Introduction

To provide the known limitation when using both VCDR and Faction in the same Recovery SDDC.

Symptoms:
Issues are seen when attempting to failover using VCDR to a Recovery SDDC with external NFS storage mounted. 

The failover may fail with  error "VM vm_name failed recovery. Error: A specified parameter was not correct: path" .


 

Cause

This issue is introduced when a Faction NFS or External NFS datastore are mounted with the name ds01 or use the same nasConfig to mount NFS volumes, and then attaching the SDDC to VCDR after. When running a VCDR failover, we attempt to write to the VCDR ds01 datastore, but at deployment it will not be mounted to the Recovery SDDC vCenter, as the external NFS datastore may have same name or config. 
 
With respect to Faction Cloud control volumes, both VCDR and Faction will use the name "ds01" for the datastore.  As a result, VCDR attempts to write to the Faction/Other NFS datastore during the failover, which fails.

Resolution

Confirm if Faction NFS datastores or External NFS datastore like FSx, VMware Cloud Flex storage are/were mounted to the Recovery SDDC vCenter, before deploying VCDR.

This is a known product limitation. VCDR deployment does not support External NFS storage mounted in the recovery SDDC. 

Additional Information

Caveats and Limitations
Run a Failback Recovery Plan
Running a Recovery Plan for Failover

Impact/Risks:
Customer will not be able to run a successful failover when using both VCDR and Faction in the same Recovery SDDC.