lost indexes

[stigger]

I have a client that has lost it's indexs, The story so far on Monday Morning I noticed the client wasn't backing up, I looked at the logs and client config and discovered that it had no Client id. I restarted the server and it then had a client id and would now back up, but it had no history. So I ran a nsrck -L5 clientname - no change, so i then ran nsrck -L7 clientname still no history... Now this server went west on the 16 but I cannot go back that far with the -t switch as we no long have the bootstraps.

Today I noticed this "9867 06/22/09 10:59:47 nsrmmdbd Creating new client id mapping for client:maitfs1" in the daemon.raw...

does this mean that the client id has changed and if so can I change it back and recover my indexes or am I in scanner land

 

[605]

If you know the old client id, i would suggest that you delete the instance and recreate it with the old id.

 

[stigger]

I thought of that any idea where to get it from though???

 

[hkuhlmann]

You get the client id with mminfo for example:
mminfo -av -q client=<clientname> -r clientid

If you have an old copy of you nsr\res dir, you will find the clientid in the resource files.

Regards
Heiko

 

[stigger]

Is that the res files on the client or the server??? I've been looking for the client id on the client and I cannot find it.

 

[denisfr]

Hello,

I have currently a case opened (since apr '08 ) for this behaviour, on a Linux client.

After some searches, we found that nsrim is the cause of the damage (and after the deletion of indexes, it prevents index from being updated).

Can you restore old index, and perform a nsrim -X in order to see if the problem is still present ?

What are your client/server NW versions ?

Denis