vProxy - FLR error when mounting

Hi Chris,

The file level recovery workflow creates an NFS export on the Data Domain, which is then added as an VMware Datastore on the target ESXi hosts.  This error can come up if there is a firewall is preventing one of the ESXi hosts, in the VMware Cluster, from connecting to the NFS server (Data Domain) to mount the NFS Data Store.

Please ensure TCP and UDP access is available over ports 111 and 2049 (defaults) to the Data Domain from all of the ESXi hosts in the Cluster.

Hello Chris, From the configuration requirement side: From the VMware administration guide, could you please confirm the below settings are applied before attempting a FLR: Entering management credentials for the Data Domain resource (instant recovery and User mode file-level restore only) When performing an instant recovery of a virtual machine or file-level restore in User mode, ensure that you provide the management credentials for the Data Domain resource prior to initiating the recovery. Procedure 1. In the NMC Administration window, click Devices. The Devices window displays. 2. In the expanded left navigation pane, select Data Domain Systems. 3. In the right details pane, right click the Data Domain system and select Properties. In the Access pane, enter the management credentials. Management host, Management user, and Management password. The Management user should have Data Domain administrator privileges. a. In the Management host field, specify the host name of the Data Domain system used for management commands. b. In the Management user field, specify the username for a Data Domain user that has admin access. For example, sysadmin. c. In the Management password field, specify the password of the management user. d. In the Management port field, specify the management port. By default, the port is 3009. If required, in the Configuration pane, update the export path. EMC recommends leaving this field blank. When left blank, the default path is used, which is the short name of the NetWorker server. If you do enter a path in this field, ensure that the path has NFS permissions. When you log in to the Data Domain resource, navigate to the NFS section and add the Mtree device path (the path to the NetWorker backup device) as a valid NFS path. 6. Click OK to save the changes

Hi Blog,

We finally found the issue, port 2049 was not open in UDP mode.  Once open, it start working perfectly.

Thank you,

Chris

Hello,

I also have a problem during the datastore mount.

The message appears as follows:

....

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 TRACE:  [156] Unlocking VM ...

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 TRACE:  [156] Attemp #1 to clear virtual machine's custom field lock "EMC vProxy FLR Session" ...

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 TRACE:  [156] Setting custom attribute 'EMC vProxy FLR Session' value for object vm-12793 to '' ...

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 INFO:   [156] Set custom attribute 'EMC vProxy FLR Session' value for object vm-12793 to ''.

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 INFO:   [156] Unlocked virtual machine.

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 TRACE:  [156] Unmount complete

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 INFO:   [156] Disconnected from session on vCenter 'sbopvc06'.

159373:nsrvproxy_flr: vProxy Log: 2017/09/28 14:48:00 ERROR:  [156] Unable to create datastore 'EMC-FLR-sbopbckp11-1500552574' using 'DataDomain1.bop.win:/data/col1/sbopbckp10/FLR-sbopbckp11-6ae8a1e3-f88a-4d17-9c07-58730d90a21b': ServerFaultCode: An error occurred during host configuration.

152793:nsrvproxy_flr: vProxy Log Ends =================================================

150017:nsrvproxy_flr: Saveset Mount was terminated...

164881:nsrvproxy_flr: Operation completed with errors.

In my opinion, there is no talk about blocked communication, because everything works on the same network without blocking ports.

Can someone tell me what to check?

Regards