NVp-Vproxy: FLR failing with:Unable to assign vProxy for FL Recovery: NSR VMware proxy is not available for datastores () using transport mode 'Hotadd' in vCenter

Summary: FLR fails saying that it is not available for datastores () using transport mode 'Hotadd'

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



File Level Recovery (either from NMC or from FLR web page on client) fails with the following error message:
Unable to assign vProxy for FL Recovery: NSR VMware proxy is not available for datastores () using transport mode 'Hotadd' in vCenter

Cause

vProxy has a list of ESX Datastores which it can access on the 'Datastore' settings.

Due to the FLR process, which is:
  1. NetWorker ask Data Domain to mount a backed up VM.
  2. Data Domain mounts a NFS datastore of the backup
  3. ESX mounts the DD NFS as an internal Datastore
  4. vProxy connects to the recently created ESX Datastore to perform the FLR to the target VM.
step 4 is failing because vProxy does not have on its settings the recently created ESX datastore name.

Resolution

Since we don't know the name that this FLR datastore will be given, we should have at least 1 vProxy with no restriction on which datastores the vproxy can access.

If you can't add any vProxy, or need to do the restore inmediately, simply cut to a notepad the list of Datastores from he vProxy settings, to leave it empty; and paste back once restore has finished.

Affected Products

Data Backup & Protection Storage, NetWorker
Article Properties
Article Number: 000050107
Article Type: Solution
Last Modified: 16 Jun 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.