Problem Description
While attempting to submit a VMware File Level Restore (FLR) to an alternate location, the restore job fails during submission and displays the following error message:
Plaintext
Failed to schedule restore. Error : customerid=xxxxx, siteid=xxxxx, layer=Job, method=FLRRestore, msg=Failed to connect to client cause=Failed to connect to client: Failed to connect to client.
Cause
This issue typically occurs when the Backup Proxy Pool selected during the VMware FLR restore configuration does not contain the specific backup proxy associated with the target ESXi/vCenter environment.
By default, the restore wizard auto-selects the Default Proxy Pool.
If the required target backup proxy is not a member of this default pool, the restore submission fails because Druva Cloud cannot establish a valid communication path to the destination client environment.
Resolution
Follow the steps below to manually map the correct proxy pool during the VMware File Level Restore configuration:
Log in to the Druva Management Console and navigate to Restore → VMware → File Level Restore.
Select the required VM backup snapshot and choose Restore to Alternate Location.
Locate the Backup Proxy Pool dropdown setting within the restore configuration wizard.
Manually select the correct Backup Proxy Pool that contains the specific backup proxy registered to your destination ESXi/vCenter.
Proceed with submitting the restore job.
⚠️ Important: Do not leave the selection set to Default Proxy Pool unless you have explicitly verified that the required target backup proxy is an active member of that pool.