Problem with client ID

[mlorencak]

Hi..

We have moved one of our hosts (Win2K) from one location to another. Everything is the same (hardware, software) even IP number is the same. The only thing it was changed is switch on witch the client is plugged in. And now the problem. From that time I can not execute backup or. Recover process any more. I can still browse with client using index on legato server, but that all. Because I couldn’t find the solution I have deleted client on server, I even un-install and the install the client software on host, but the problems stays. Finally I have deleted client indexes, but it didn’t help also.
Every time I try to create client on server I get the warning message:

Alias KrekSwift1 was one a client using client ID <client_id_number>. Recommend re-specify the client id to reclaim the KrekSwift1resources for krekswift1.r-kb.si.

From that message I assume that something is wrong from ID number. Or maybe I am wrong.

Thank you in advance

lp, mitja

 

[605]

In the client resource you can actually change the client id attribute.
So you only need to replace the new one with the old one. Probably,
editing the resource file directly is the easiest way to fix this problem
(handle with care!). Then restart the NetWorker daemons/services.

Although this never happened to me i have heard many times that this works.

Good luck.

 

[mlorencak]

Thanks for the answer. I would do this but have NW 7 and as
I know he hasn't got resorce file in /NSR/RES directory like
version before.
Is there any way to completely remove client resorces from
NW server configuration.

 

[605]

Yes, this is easy. However, in this case you also have to remove the client file index.

There is a way to recursively search through the NW resource database tree,
even on UNIX:

find /nsr/res/nsrdb -type f -exec grep -l &quot;string&quot; {} \;

this should point to the proper file which you then need to edit.

 

[mlorencak]

I found string &quot;krekswift&quot; in one file.
It looks like this:

---------------------------------------------
aliases: krekswift1, krekswift1.r-kb.si;
application information:;
archive services: Disabled;
archive users:;
backup command:;
browse policy: RKB - Dnevni;
client OS type:;
clone storage nodes:;
comment: dnevni;
CPUs:;
directive: NT standard directives;
enabler in use: No;
executable path:;
group:;
index path:;
licensed applications:;
name: krekswift1.r-kb.si;
ndmp: No;
NetWorker version:;
owner notification:;
parallelism: 4;
password:;
priority: 500;
remote access:;
remote user:;
retention policy: RKB - Dnevni;
save set: &quot;c:\\pw32&quot;;
schedule: Default;
server network interface:;
storage nodes: nsrserverhost;
type: NSR client;
resource identifier: 20.0.59.65.126.15.30.64.10.40.11.195(2)
---------------------------------------------------

can you tell me witch field must I change. I have even deleted this file. But when I try to re-create client I get
the same message again.

 

[wallace88]

In NetWorker 7, it checks the media database's client id table to determine if a new client was already defined. If so, it will give you the message you got, which essentially tells you what the client id was, just in case you want to reuse that id.

(I won't go into why the client id would have changed.)

Since this is still the same machine, just delete the client, then create it, and while creating it put in the client that is indicated.

The easiest way is to use the nwadmin gui, aka NetWorker Administrator. After starting this up, display hidden attributes by selecting: Options... Customize... then check off &quot;Display Hidden Attributes&quot;... and click OK.

Next, when you recreate the client, put in the name, then right under that should be the client id field. Put in the original client id. Then fill in the rest as necessary.




By the way, the reason why you don't see the client id field when you use nsradmin is because you first have to allow to display the hidden attributes: eg:

nsradmin
. type: NSR client; name: krekswift1.r-kb.si;
option hidden
print

 

[mlorencak]

I tried to enter &quot;old&quot; client ID when re-creating a client, but NW Admin said: this client was previously defined. Re-Apply to use new ID, otherwise client must be renamed first.

Is there a way to delete client from client id table in
media database. Maybe this should solve the problem.


lp, mitja

 

[wallace88]

The client id cannot be removed from the media database.

I just noticed that you are trying to rename the client as well, from krekswift1.r-kb.si to KrekSwift1. Try using the original name with the original client id.

And also populate the alias field with both names when you're recreating the client.

 

[DavinaTreiber]

605 - There is no way to edit the client ID by editing the res files directly, because the client ID is not stored in the res files, it is a key in the media database. You can only access the client ID from nwadmin or nsradmin.

 

[wallace88]

Actually, the client id is found in the res files. It just can't be easily changed once the client is creaed.

And there is no way to directly edit the client id tables in the media database. This is one of the reasons why client id problems develop.

 

[605]

O.K., let me suggest that you
- delete the client resource and
- delete/rename the /nsr/index/client directory before you recreate
the old one.

 

[wallace88]

605: tried that before... but unfortunately, deleting the client resource does not remove the client id from the media database. This is shown by running an mminfo query after deleting the client.

mminfo -avot -r client,clientid | sort | uniq | grep client_name

 

[DavinaTreiber]

wallace88 - the client id is NOT is the res files. If you really believe it is, then show me an example.

The usual reason for client ID problems developing is subtle changes in client names, such as the domain part changing. They can be notoriously difficult to remedy, as I have no doubt that you know, since NetWorker provides no tools to help. It is often necessary to create dummy clients (with real IP addresses) to attempt to divert a client ID when it is the wrong one. Even then it doesn't always work. And client indices are a total red herring, this is the media database we are looking at here, not the CFI. The index data can be sorted out after the client ID issues have been resolved.

I have every sympathy with people suffering from client ID problems, it is very obscure, and getting it wrong is a very easy trap to fall into. Believe me I have been there myself in a very big way.

 

[wallace88]

Yes, davina... you are correct... the client id is not found in the client resource file.

I was actually remembering seeing the client id value when I am looking at the client resource using nwadmin or nsradmin. Whan this happens, it gets the client id info from the media database, and displays it along with the rest of the client configuration.

 

[mlorencak]

It is nice you having discussion about my problem. But I still didn't find a solution for it.
I tried to create client and enter old client id. Didn't work. I have deleted indexes for that client. No go.

Can someone tell me why has client ID changed. We didn't change hostname, ip, hardware,.... Nothing.
Everything we did is move client to another location (different switch, bit same network).

lp, Mitja

 

[nwuser]

Hello,

I would like to know what kind of errors you got when you tried to perform backups after the client( system) relocation. Do you remember error message or something like that?

Also, could you write down about your name resolving - local hosts NIS DNS?

When creating client, try to do next:

1. Search for the original client id (using mminfo, like shown in previous posts)

2. (from gui or nsradmin) delete all possible client resources of krekswift1 client

3. shutdown networker and remove all index files related to the client krekswift1
!!!in nsr/index there should be no krekswift1 (or the alias names)

4. start networker

5. open admin gui and: create client, specify name and aliases, specify client id (check 1.)

6. shutdown networker

7. restart networker and check if client id is changed or if it is the one you entered