Recovery fails if External NFS Datastores are mounted in a VLCR recovery SDDC

Products

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

Issue/Introduction

When attempting to failover using VLCR 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" .


 

Environment

VMware Live Cyber Recovery 7.26.x and older

Cause

The cause for failure occurs when a Faction NFS or External NFS datastore is mounted with the name ds01 or use the same nasConfig to mount NFS volumes in Recovery SDDC before attaching it to the VLCR as it will  attempt to mount the Cloud Filesystem as NFS mount in the Recovery SDDC with name 'ds01'. 
 
With respect to Faction Cloud control volumes, both VLCR and Faction will use the name "ds01" for the datastore.  As a result, VLCR attempts to write to the Faction/Other NFS datastore during the failover and fails.

Resolution

VLCR deployments prior to July 2024 does not support External NFS storage mounted in the recovery SDDC. Confirm, if Faction NFS datastores or External NFS datastore like Amazon FSx are/were mounted to the Recovery SDDC vCenter, before attaching it to VLCR as recovery SDDC. 


VLCR Deployments after July 2024, mounts the cloud filesystem with the same name as it was associated with during the Cloud Filesystem deployment phase. Please ensure you do not have any thirdparty datastores with the same name attached in the recovery SDDC. Refer documentation Recovery SDDC datastores