NVP vProxy: How To Unregister/Re-Register a vProxy Appliance

Summary: This KB explains how to manually unregister and register a NetWorker VMware Protection (NVP) vProxy appliance using the NetWorker server’s nsradmin command-line options.

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

Instructions

The NetWorker VMware Protection integration is configured with the vProxy Appliance. The vProxy must be unregistered and re-registered against the NetWorker Server.

Method 1:

  1. From the NetWorker Management Console (NMC) or NetWorker Web User Interface (NWUI), delete the vProxy resource. Deleting the vProxy from NetWorker should unregister it from the NetWorker server resource database (nsrdb). Deleting the vProxy from NetWorker does not delete the vProxy Virtual Machine (VM) from VMware.

NMC: Devices->VMware Proxies
NWUI: Protection->VMware Proxies

  1. Using the NMC or NWUI add the vProxy back. Readding the vProxy issues a new registration for the vProxy. 

Method 2:

If the above method fails, manually unregister and reregister the vProxy using the NetWorker server’s nsradmin command-line utility.

  1. On the NetWorker server, open a Administrator/root command prompt
  2. Enter: nsradmin
  3. Enter: option hidden
  4. Enter: visual
  5. This opens a CLI utility that can be used to change the NetWorker Server Resource Database (nsrdb). You can use ESC, arrow keys, and ENTER to navigate and make changes.
Use the keyboards arrow-keys and move to Select then press Enter. Highlight NSR VMware Proxy then press Enter.
nsradmin utility, enabling hidden options and using visual mode to access NSR VMware Proxy
  1. Use the Next/Prev options to select the vProxy host you must unregister.
  2. Use the arrow keys to select Edit and hit Enter.
  3. Use the arrow keys to select Unregister and press Enter, press ESC and save changes.
unregistering a vProxy appliance from nsradmin visual mode
  1. Wait 30-60 seconds.
  2. Use the arrow keys to select Register and press Enter, press ESC and save changes.

Logging:

The NMC should report that the vProxy has been unregistered/registered:
 NMC Log window showing unregister and register status 
 
The NetWorker server daemon.raw also includes messaging about the unregistration and registration operations:
Linux: /nsr/logs/daemon.raw
Windows: <INSTALL_DRIVE>:\Program Files\EMC NetWorker\nsr\logs\daemon.raw

Additional Information

In some instances the vProxy will not register, this can occur for several causes. A common solution is to perform the following.

  1. Delete the vProxy from the NetWorker Management Console (NMC) or NetWorker Web User Interface (NWUI)
  2. Open an SSH session to the vProxy appliance and log in as admin.
  3. Once logged in as admin, switch to root:
sudo su -
  1. Rename the vProxyRegistry.dat:
mv /opt/emc/vproxy/runtime/state/vProxyRegistry.dat /opt/emc/vproxy/runtime/state/vProxyRegistry.dat_`date -I`
  1. Confirm that the vProxy can reach port 9090 on the NetWorker server:
curl -v NETWORKER_SERVER_FQDN:9090
  1. Reboot the vProxy VM:
reboot
  1. Once the vProxy VM has come back online, confirm that you can connect to port 9090 on the vProxy from the NetWorker server:
nsrports -t VPROXY_FQDN -p 9090
NOTE: If connection issues occur (name resolution or port 9090), verify DNS settings and consult your network or firewall team about port communication. It is possible that it is being blocked by a network or firewall device. If no connection issues are observed, the vProxy can be added in the NetWorker Management Console (NMC) or NetWorker Web User Interface (NWUI).

In some instances, debug messaging may be required. The following KB provides information about enabling vrapid debugging on the vProxy appliance: NetWorker VMware Protection-vProxy: How to Enable Debug Logging
The vProxy's /opt/emc/vproxy/runtime/logs/vrapid/vrapid-engine.log contains information regarding vProxy registration operations.

vProxy admin user account is locked:

NOTE: If both the admin or root passwords are unknown, the vProxy appliance must be redeployed. From vSphere, select the vProxy VM and open the VM's Summary tab. Make note of the information in the Virtual Machine Details and Related Objects windows. Shut down, and delete the vProxy VM. Redeploy the vProxy VM. vProxy OVA packages are available on the Dell NetWorker Products page. Consult with your VMware administrator for assistance deploying and reconfiguring the VM.

If vProxy will not register, and root credentials are known, check to see if the admin user account is locked on the vProxy.

  1. From vSphere, open a VMware Console session to the vProxy VM:

Accessing vProxy VM console from VMware vSphere

  1. Log in as root.
  2. Use pam_tally2 to reset the admin account:
pam_tally2 --user=admin --reset
  1. If the current admin password is not known, you can change it using the Linux passwd command:
passwd admin
  1. Use Method 1 from the Resolution field to remove the vProxy and add it back using the new password.

If the admin account continues to lock when no known SSH connections are being performed, check to see where the SSH session is coming from:

journalctl -u sshd | grep -w 'admin'

This command shows what systems are attempting (and failing) to login using the admin account:

Dec 06 09:23:36 nsr-vproxy02.amer.lan sshd[9407]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.9.100  user=admin
Dec 06 09:23:38 nsr-vproxy02.amer.lan sshd[9407]: Failed password for admin from 192.168.9.100 port 54788 ssh2

Affected Products

NetWorker

Products

NetWorker Family
Article Properties
Article Number: 000156072
Article Type: How To
Last Modified: 06 Nov 2025
Version:  10
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.