Client ID Issue Backup HyperV Networker 19.3

Let me try to help you. I do not have HyperV experience but I think this is not necessary right now.

Unfortunately, the client id is not stored in the client's file index but in the media db. Consequently, deleting/renaming the file index files will show no effect.

 

The message already tells you what to do. You may either create a new client by re-applying or you can re-use the old client id. Unfortunately, the client configuration wizard is the wrong tool because it does not allow you to specify the client id. So please proceed as follows:

  -  Activate the 'Diagnostic View'

  -  Start the old configuration method by creating a 'New' client.

  -  In the tab 'General' add the 'Name' and specify the 'Save Set' and the 'Group'.

  -  In the tab 'Globals (1 of 2)' specify the 'Client id'.

  -  Click OK to confirm the creation of this client resource.

This should do the job. Do not forget that you still might need to adjust other configuration parameters.

 

Good luck.

Dear Bingo.1, thank you for your feedback. but that doesn't help us, sorry maybe we forgot something, what we want to add is a Windows Cluster client with 2 hosts/servers.

If you add the old configuration method by creating a 'New' client, we cannot change the backup type setting from the filesystem to HyperV Server. Or I don't know how to change it?

So far, if I add backups except for the filesystem type, I use the new client wizard.

Or is there a way how can I delete the client id that has been registered on the media db? maybe it can be very helpful if i remove it first before adding a new client.

 

thank you.

Let me guess - you have replaced your old Exchange servers by new models wit the same name. In this case they will of course get a new client id assigned. You most likely have deleted the old client resources as well. Now as you reconfigure those clients, they will get this new client id assigned. However, NW still remembers the old one and reports this potential misconfiguration. Am I missing something?

There is no way to delete the client id. However, you can either

  -  recreate the client with a filesystem backup configuration and re-apply the old client id.

     Remember that you do not have to use it later.

     Then use the configuration wizard to add the Exchange client instances.

  -  You can proceed and re-apply to assign a new client id.

  -  You can later repair the configuration with the utility nsrclientfix. Please see the appropriate manpage for details.

.

 

Dear bingo.1, okay I'll try to explain in more detail, so right now we're migrating all the servers backed up from the old networker version 9.2 to the current networker 19.3. but there is 1 server that appears an error like the one I attached above.

All servers can be moved one by one with these steps:
- uninstall client 9.2 then install client 19.3 on the server you want to backup to 19.3
- add new user with wizard client on networker 19.3,
- then try running a backup.

So far there have been no problems, but there is only 1 problem that at this time we don't know why the client id has been registered, and when we deleting the client on networker also delete the client id right?

at this time I returned the server back to the client version 9.2 and it was still successfully backed up on networker 9.2 (old version).

next weekend we try again install nw 19.3 and try your suggest for r epair the configuration with the utility nsrclientfix

thanks for your response, i appreciate it.

Sorry, but your statement is somehow incomplete.

AFAIK (and I usually do not monitor the client IDs permanently) a new client ID will only be assigned if the computer changed. So if you replace/change the physical/virtual server from let's say Windows 2016 to Windows 2019 then this will result in a new client ID. A 'simple' update of the NW software will not change it.

Also I do not understand what you want to tell me by the statement " - add new user with wizard client on networker 19.3". This of course does not make sense as this is a 'client', not a 'user' configuration wizard. This is an obvious typo or you want to tell us something and lost track during the statement.

 

What I wanted to tell you is that you should

  1. Create a 'normal' file system client instance and explicitly specify the old client ID.

         Remember that you must not assign it to a group if you do not want to use it.

  2. Next - as NW now recognizes the old client ID - you should use the wizard and specify the Exchange instance if the client.

I think this makes sense. Unfortunately, I can't verify that right now.

 

sorry, if you want to know "I replaced your old Exchange server with a new model with the same name" I said no, I just moved/migrated from networker 9.2 to networker 19.3.

Yes, I want to tell you that there are no problems with other servers moving/migrating from Networker 9.2 to Networker 19.3, and I did step by step according to the info above.

Basically, I just want to add a new client on Networker 19.3 with a HyperV backup type, whether it's with the old or new Client ID.

this week I tried again to re-add this server to Networker 19.3 by trying your suggestions, because on weekdays I can't try it. Thank you.