NVP vProxy: Unable to install FLR agent on Linux Virtual Machine.

Summary: During a File Level Recover (FLR) of a Linux Virtual Machine (VM) protected with the NetWorker VMware Protection (NVP) vProxy appliance. The FLR mount fails, stating that the FLR agent is not installed, and the virtual machine does not allow installation. ...

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

Briefly describe the symptoms of the issue.
  • During the FLR, a nonroot account was specified.
  • The FLR was initiated from the NetWorker Management Console (NMC) or the Dell EMC Data Protection Restore Client.
  • The following errors are observed in the mount output from the recover wizard.
159373:nsrvproxy_flr: vProxy Log: 2022-02-08T11:49:06Z ERROR: [@(#) Build number: 153] Cannot connect to vProxy Agent: Unable to connect to ':9613': dial tcp :9613: connect: connection refused
159373:nsrvproxy_flr: vProxy Log: 2022-02-08T11:49:06Z INFO: [@(#) Build number: 153] FLR Agent is not installed on VM
159373:nsrvproxy_flr: vProxy Log: 2022-02-08T11:49:06Z INFO: [@(#) Build number: 153] Set custom attribute 'Dell EMC vProxy FLR Session' value for object vm-XX to ''.
159373:nsrvproxy_flr: vProxy Log: 2022-02-08T11:49:06Z INFO: [@(#) Build number: 153] Unlocked virtual machine.
159373:nsrvproxy_flr: vProxy Log: 2022-02-08T11:49:06Z INFO: [@(#) Build number: 153] Disconnected from session on vCenter 'XXXXX'.
159373:nsrvproxy_flr: vProxy Log: 2022-02-08T11:49:06Z ERROR: [@(#) Build number: 153] FLR Agent is not installed on the virtual machine and the request does not allow installation.
152793:nsrvproxy_flr: vProxy Log Ends 
Mount log locations for vProxy:
  • /opt/emc/vproxy/runtime/logs/vflrd/
  • /opt/emc/vproxy/runtime/logs/recycle/vflrd/
Mount log locations for NetWorker server:
  • /nsr/logs/adhoc/nsrvproxy_flr
  • /nsr/logs/recover/recover_name (If performed from NMC and recover session was saved).
The FLR agent location on the target VM is: 
  • /opt/emc/vproxyra/

Cause

There are several possibilities causing the issue some of which are listed below:
  1. The FLR agent was not installed. This can occur if the user does not have the required permissions (or heightened security environment) to install the FLR agent.
  2. The agent may have been installed, but the FLR mount user may not be able to run the automated script that is used to verify FLR agent installation. 
  3. There is antivirus software that is installed on the target VM blocking the FLR agent install.

Resolution

Verify that the FLR agent is installed. Ensure that the user for the FLR mount process can run the script confirming the agent’s installation.
 
1. Log in to the Linux VM using the credentials used during the FLR mount and open a shell console.
2. Run the command below to verify if the agent is installed and the user has permissions to use the agent: /opt/emc/vproxyra/bin/vflragentc

vflragetc
[admin@rhel-client01 ~]$ /opt/emc/vproxyra/bin/vflragentc
vflragentc program started
AgentResponse:{"Protocol":1,"AgentVersion":{"Release":"4.4.0-14_1","BuildNumber":"1","BuildStamp":"2025-08-22T06:06:47Z"},"Mountpoint":"","OutputFile":"","IncomingDir":"","UpgradeFile":"","Filename":"","ErrorMessage":"An agent command must be specified.","ActivityLog":"","AppAgentData":{"Protocol":0,"Agent":"","Version":{"Complete":"","Numbers":null,"Build":"","Comment":""},"MetadataValues":null,"MetadataFiles":null,"DownloadFiles":null,"FilesList":null,"WorkDir":"","Operation":0,"MonitorData":null,"AppData":"","BrowseResults":null,"Utilization":null}}
NOTE: If this command returns an error, confirm that nonroot user accounts have the required OS permissions listed in the NetWorker VMware Integration Guide.

3. If the agent is installed verify if it is started: /opt/emc/vproxyra/bin/vflragent status
4. If the agent is not running, attempt to start it: /opt/emc/vproxyra/bin/vflragent start
 
If the agent has not been installed on this VM previously. The root account can be used to install the FLR agent during the FLR recovery process. Subsequent FLR can be performed using a nonroot account once the agent is installed. The nonroot users must have appropriate operating system permissions documented in the NetWorker VMware Integration Guide, available through: Support for NetWorker | Manuals & Documents

NetWorker Web User Interface (NWUI) Method

If NWUI server has been installed in the NetWorker environment, you can specify Run with elevated privileges during the FLR. This option is not available in the NMC or Data Protection Restore Client. https://NetWorker_Server:9090/nwui
Run with elevated privileges

Verify if NWUI is installed on the NetWorker server (Included by default on NetWorker Virtual Edition):
Linux:  
rpm -qa | grep lgtonwui
Windows:  
wmic product get name, version, vendor | find "Web UI Server"

 

Manual Installation Method

If the FLR process cannot install the agent, copy it from the vProxy appliance to the target VM and install locally using OS commands. 

1. Open an SSH session to the VM you would like to install the FLR agent on.
2. Use the Secure Copy Protocol (scp) command to copy the FLR agent from the vProxy to the VM:
scp admin@vPROXY_ADDRESS:/opt/emc/sw-repo/vflragent/linux/emc*.rpm TARGET-DOWNLOAD-DIRECTORY
Example: 
[admin@rhel-client01 ~]$ scp admin@nsr-vproxy01:/opt/emc/sw-repo/vflragent/linux/emc*.rpm .
The authenticity of host 'nsr-vproxy01 (192.168.9.151)' can't be established.
ED25519 key fingerprint is SHA256:ZsV1JnrdzQ2DdcY1gH9bOrCFnEgBsABruninvAGaPEg.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'nsr-vproxy01' (ED25519) to the list of known hosts.
admin@nsr-vproxy01's password:
emc-vProxy-FLRAgent-4.4.0-14_1.x86_64.rpm                                                                                    100%   19MB 153.7MB/s   00:00
[admin@rhel-client01 ~]$
NOTE: This command copied the FLR agent to the FLR user's home directory on the target Linux VM. Alternatively, you can open an SSH session to the vProxy appliance and scp the FLR agent to the Linux VM. Example command: scp /opt/emc/sw-repo/vflragent/linux/emc*.rpm VM_USERNAME@VM_ADDRESS:~

3. Log in to the Linux virtual machine the agent was copied to, using the FLR user's credentials.
4. Run the following command to install the FLR agent: sudo rpm -ivh emc*.rpm 
[admin@rhel-client01 ~]$ sudo rpm -ivh emc*.rpm
[sudo] password for admin:
warning: emc-vProxy-FLRAgent-4.4.0-14_1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID ff48d101: NOKEY
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:emc-vProxy-FLRAgent-4.4.0-14_1   ################################# [100%]
5. Verify that the agent is installed: rpm -qa | grep -i flragent
6. Run the post install script: sudo /opt/emc/vproxyra/bin/postinstall.sh
7. Verify that the FLR user can run the agent validation command: /opt/emc/vproxyra/bin/vflragentc 
[admin@rhel-client01 ~]$ /opt/emc/vproxyra/bin/vflragentc
vflragentc program started
AgentResponse:{"Protocol":1,"AgentVersion":{"Release":"4.4.0-14_1","BuildNumber":"1","BuildStamp":"2025-08-22T06:06:47Z"},"Mountpoint":"","OutputFile":"","IncomingDir":"","UpgradeFile":"","Filename":"","ErrorMessage":"An agent command must be specified.","ActivityLog":"","AppAgentData":{"Protocol":0,"Agent":"","Version":{"Complete":"","Numbers":null,"Build":"","Comment":""},"MetadataValues":null,"MetadataFiles":null,"DownloadFiles":null,"FilesList":null,"WorkDir":"","Operation":0,"MonitorData":null,"AppData":"","BrowseResults":null,"Utilization":null}}

Additional Information

Affected Products

NetWorker
Article Properties
Article Number: 000198224
Article Type: Solution
Last Modified: 17 Nov 2025
Version:  8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.