NVP-vProxy: Backup fail "Client 'vCenter' is not properly configured on the NetWorker Server"

Summary: Unable to backup Virtual Machines (VM) using the NetWorker VMware Protection (NVP) vProxy solution. The backup fails, reporting that the vCenter is not properly configured on the NetWorker server. ...

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

All vCenter client resources were deleted.

All vProxy backup failed with error: 
MM/DD/YYYY HH:mm:SS Backup failed.
MM/DD/YYYY HH:mm:SS Unable to process VM 'vmname': Client 'vcenter' is not properly configured on the NetWorker Server or 'vcenter'(if not a virtual host) is not in the aliases list for client 'networker server'
MM/DD/YYYY HH:mm:SS vmname: Backup failed.
MM/DD/YYYY HH:mm:SS Final Summary of VMs: 
MM/DD/YYYY HH:mm:SS 0 canceled backups
MM/DD/YYYY HH:mm:SS X failed backups
MM/DD/YYYY HH:mm:SS 0 successful backups
MM/DD/YYYY HH:mm:SS 0 waiting backups
MM/DD/YYYY HH:mm:SS 0 running backups
MM/DD/YYYY HH:mm:SS 0 savesets output to next action
MM/DD/YYYY HH:mm:SS Action has finished with failures.
MM/DD/YYYY HH:mm:SS Action backup vmware-vproxy 'Backup' with job id jobid is exiting with status 'failed', exit code 1

Cause

vCenter client resource does not exist in NetWorker. All the vCenter client resource was removed from NMC thinking the vCenter is not needed for backup.

Resolution

NetWorker VMware Protection (NVP) uses a singular client resource for each VMware vCenter configured in NetWorker. VM backups appear as save sets within the vCenter client resource. Here is an example of how a VM backup appears in the NetWorker media database. 
vm:vmware-vm-uuid:vcentername

Example:

[root@nsr ~]# mminfo -kvot
 volume        type   client           date     time         size ssid      fl   lvl name
ddve01VMbackup.001 Data Domain vcsa.amer.lan 03/19/2025 06:00:18 PM 94 GB 4191895152 cr full vm:503e178f-6982-0b07-36b2-c46c6d3ec4c9:vcsa.amer.lan
ddve01VMbackup.001 Data Domain vcsa.amer.lan 03/20/2025 12:57:25 PM 41 GB 4259072246 cr full vm:503edaab-e481-b0e7-1433-835e23dd2a5d:vcsa.amer.lan
ddve01VMbackup.001 Data Domain vcsa.amer.lan 03/20/2025 12:57:26 PM 94 GB 4242295030 cr full vm:503e178f-6982-0b07-36b2-c46c6d3ec4c9:vcsa.amer.lan
ddve01VMbackup.001 Data Domain vcsa.amer.lan 03/20/2025 12:57:27 PM 188 GB 4225517814 cr full vm:503e7439-7053-9fc0-6c26-02f5f021b289:vcsa.amer.lan

The vCenter client resource should not be deleted from NetWorker. Re-create all the vCenter client resource and resume backup.

Create a new client in NMC for the vCenter using the fully qualified name of the vCenter.

  1. Open an Administrator command-prompt or root SSH session on the NetWorker server.
  2. Enter the nsradmin prompt:
nsradmin
  1. From the nsradmin prompt, use the create type command to create a new client resource for the vCenter server using its Fully Qualified Domain Name (FQDN):
create type: nsr client; name: <VCENTER_FQDN>; backup type: vProxy
Example: 
nsradmin> create type: nsr client; name: vcsa.amer.lan; backup type: vProxy
                        type: NSR client;
                        name: vcsa.amer.lan;
                 backup type: vProxy;
Create? y
created resource id 52.0.169.11.0.0.0.0.218.150.219.103.192.168.9.150(1)
nsradmin>
  1. Try the backups again.

If the issue persists, you must remove the Hypervisor (vCenter) resource from NetWorker and add it back. NetWorker: Removing vCenter entry from NMC VMware View/Removing NSR Hypervisor

Affected Products

NetWorker

Products

NetWorker
Article Properties
Article Number: 000034174
Article Type: Solution
Last Modified: 20 Mar 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.