NVP vProxy: NetWorker VIB to Open NFS Ports For vProxy FLR

• NetWorker VMware Protection (NVP) vProxy File Level Restore (FLR) or Instant Access restore fails with an NFS-related error in the recover session log.

159373:nsrvproxy_flr: vProxy Log: YYYY/MM/DDTHH:MM:SSZ INFO: [@(#) Build number: 123] Unmounting after mount failure: Unable to create datastore 'EMC-FLR-vproxy_name-026473-1645810870' using 'DD_NAME:/data/col1/networker/FLR-vproxy_name-4bd57875-57f8-4dbf-a98a-b949ea2d5d30': ServerFaultCode: An error occurred during host configuration. Operation failed, diagnostics report: Mount failed: Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Unable to connect to NFS server.

159373:nsrvproxy_flr: vProxy Log: YYYY/MM/DD HH:MM:SS INFO:   [@(#) Build number: 66] Unmounting after mount failure: Unable to create datastore '[VPROXY_NAME]-1487848168' using '[DATA_DOMAIN]:/data/col1/coral/[VPROXY_NAME]-519f0a6a-348f-4950-bba7-5af3b1e4fca8': ServerFaultCode: An error occurred during host configuration.

• NFSv3 is enabled on the Data Domain and is the default Network File System (NFS) protocol.

• The ESXi host the vProxy resides on is unable to reach NFS ports 2049, 2052 on the Data Domain host.

nc -zv DATA_DOMAIN_ADDRESS PORT

Workaround:

To recover files, you must perform a VMDK (disk restore) and copy the files from the recovered disk to the system the disk was restored to. A VMDK restore reboots the target VM during the restore. You can recover the disk to an alternate VM if it is the same OS type (that is: Linux or Windows).