Hi,

Be sure that your name resolution is working correctly - that the NetWorker server can resolve correctly the Virtual Centre server and vice-versa.  The vCenter needs to have the NetWorker client software installed on it also for this to work.  If there's a firewall between these two, that could also be the issue here.

-Bobby

The name resolution is good.

We have no firewall on the backup network.

The networker client software is installed and work fine, the vCenter is backuped very well.

Have an idea ?

have you added the VADP user role in vcenter?

Try clearing Java cache.

It might be java cache files issue as well.

Regards,

Prajith

Tried, no change.

Hi Thierry,

The backup of VM work fine.

And i do backup via VADP.

Hi,

In order to troubleshoot autodiscovery problems, you can run the autodiscovery manually using the nsrvim command.  This should give you extra information around what's happening:

nsrvim -s [networker server name] -D5 -v -d --names [Virtual Center Server name] > nsrvim_out 2>&1

I don't have any system right now to test this, but from what I can see, it should work.

-Bobby

If the user mentioned in the Username and Password Fields has non-administrative privileges on the vCenter server, follow the following steps to create a VADP User role in vCenter :

1. Log in to the vCenter Server with Administrator privileges using vSphere Client.

2. From the vCenter Server, select  View > Administration > Roles.

3. Click Add Role.

4. Name the role VADP User.

5. Assign the required permissions to the VADP User role and click OK.

And assign the VADP User role to the user specified in the NetWorker Hypervisor resource:

1. Log in to the vCenter Server with Administrator privileges using vSphere Client.

2. Select the vCenter server in the left pane.

3. Click the  Permissions tab in the right pane.

4. Right-click inside the right pane and select  Add Permission.

5. Add the NetWorker Hypervisor user and assign the VADP User role.

6. Ensure Propagate to Child Objects is enabled and click OK.

When you click on the Enable Auto-Discovery. Configure in the Auto-Discovery dialog box:

a. In the Hostname field, enter the fully qualified domain name (FQDN) or IP address of the vCenter server. ( Make sure name resolutions and network connectivity is perfect )

b. In the Username and Password fields, enter the credentials required to log onto the server. The username and  password must belong to an account that has permission to perform VADP backups, snapshots and registering/creating a new VM. The user specified in the Hypervisor resource must also have administrative privileges on vCenter.

c. When the vCenter server configuration is complete, right-click Virtualization and select  Run Autodiscovery  to generate the topology map.

Thank to take a time for my problem.

I say again.

My autodiscovery seems to be good.

The result is successful.

The 250 VM on this 2 vCenter are backed up fine.

All is green in networker.

But i have no topology map...

The setup of autodiscovery is good.

The role "VADP User" is created since many month.

And the Networker Hypervisor user have been added to this role since many month too..

All seems to be correct.

But i have no display in topology map.

And i repeat, all backup of VM are good.

I think without a correct configuration of "autodiscovery" and permission for VADP user, my backup should be failed...

Hi, we have the same problem on a Networker 7.6.3, Is your vCenter server is x86 or x64 base ?  I think there could be  an issue here. 

Ben

Hi Vidda911,

Did you try to re-install the NetWorker client on the vCenter again ? , As the NetWorker client on vCenter is only

required if using the auto-discovery feature or the virtualization map feature.

Also make sure that you use the auto-discovery of VMware environments with VMware vCenter only as NetWorker supports that. It does not support auto-discovery with an ESX server.

If re-installing the NetWorker client did not fix the issue , try to re-create the NSR Hypervisor resource again.

Waiting your updates.

Thanks,

Ahmed Bahaa

Hi Vidda911,

Did you try to re-install the client , and re-create the NSR hypervisor resource again ? Is the problem solved or not ?

Waiting your updates.

Thanks,

Ahmed Bahaa

Hi Vidda911,

The error messages you provided are mainly for connectivity issues between backup server and vCenter server, Make sure that the NetWorker server can resolve the IP/FQDN of the Virtual Centre server, and that the Virtual Centre server can resolve the NetWorker server. Check the DNS records and hosts file and how is the naming resolutions with NetBIOS and FQDN names , beside the IP addresses as well. You can check the following powerlink article as well:

https://solutions.emc.com/emcsolutionview.asp?id=esg110876

Thanks,

Ahmed Bahaa

Hi Ahmed,

ok i have do that today.

Uninstallation of Networker client on each 4 vCenter.

New Installation of Networker client on each 4 vCenter.

re create the NSR hypervisor..

And now i have random error.

Sometime "NSR hypervisor resource 'FQDN of one of four vCenter' not found"

Sometime "Falling back to rsh, but RUSER not provided"

Sometime it's works but no display in virtualization menu.

I no longer understand anything

My NWS resolve the 4 IP<->FQDN of  4 vCenter...