I have seen this too, somehow the clientid and identity of clientY is cached in a non-visible way. I got around it by creating a new client, say clientZ using the clientid for clientY, which effectively (re)creates and renames clientY as clientZ. You can then properly remove clientZ and/or keep it around for reference. You are then free to rename your original client.
Steps that you should follow are: - write down client-id of old_name - delete all client resources for old_name - stop NW - move index from old_name to new_name - start NW - create client resource for new_name using new_name as name and old_client_id as new_client_id
In your steps as it seems stop/start step is missing.
I think you should first delete all resoruces for ClientY, restart services and then when you create new clientY - paste the client ID of CLientX there.
When I look a the client-list, I don't see a clientY. Someone has created the clientY and removed this client in the past. But for some reason networker is still aware of its client id.
I followed the steps but I have still the problem. But there was something strange. There was already a very old index-directory for the new_client. So I removed this dir old_name to new_name.
It is possible that new_client was once used and does have entries in media database. You can verify that with mminfo command. In such case, if such data is not required, you can remove it from media database using nsrmm command.
Client-id should exist to be removed. In your case you don't wish to remove it, but rather move so that is associated with new client name.
If we go back to your first message, what is that you get when you execute: mminfo -q clientid=y-y-y-y-y-y -r name,client,volume,ssid,savetime,ssretent,group,pool
mminfo -q clientid=y-y-y-y-y ? It appears that networker has indeed once known clientY as client-id y-y-y-y-y, but since all those resources were deleted you don't see it anymore.
If the above mminfo command gives results, try deleting all those savesets using: nsrmm -ydS
Jason20
19 Posts
0
February 20th, 2007 07:00
I got around it by creating a new client, say clientZ using the clientid for clientY, which effectively (re)creates and renames clientY as clientZ. You can then properly remove clientZ and/or keep it around for reference.
You are then free to rename your original client.
ble1
4 Operator
•
14.4K Posts
0
January 9th, 2007 08:00
- write down client-id of old_name
- delete all client resources for old_name
- stop NW
- move index from old_name to new_name
- start NW
- create client resource for new_name using new_name as name and old_client_id as new_client_id
In your steps as it seems stop/start step is missing.
amediratta
2 Intern
•
2K Posts
0
January 9th, 2007 08:00
nsrhti
46 Posts
0
January 9th, 2007 08:00
Someone has created the clientY and removed this client in the past. But for some reason networker is still aware of its client id.
nsrhti
46 Posts
0
January 12th, 2007 02:00
I followed the steps but I have still the problem.
But there was something strange. There was already a very old index-directory for the new_client. So I removed this dir old_name to new_name.
Is it possible te remove manually client-id 's .
Message was edited by:
carlo Maesen
ble1
4 Operator
•
14.4K Posts
0
January 12th, 2007 03:00
ble1
4 Operator
•
14.4K Posts
0
January 12th, 2007 04:00
nsrhti
46 Posts
0
January 12th, 2007 04:00
mminfo: no matches found for the query
Is it possible someone has used this once but never started a backup ?
nsrhti
46 Posts
0
January 12th, 2007 05:00
nsrhti
46 Posts
0
January 12th, 2007 06:00
mminfo: no matches found for the query
ble1
4 Operator
•
14.4K Posts
0
January 12th, 2007 06:00
If we go back to your first message, what is that you get when you execute:
mminfo -q clientid=y-y-y-y-y-y -r name,client,volume,ssid,savetime,ssretent,group,pool
nsrhti
46 Posts
0
January 12th, 2007 07:00
ble1
4 Operator
•
14.4K Posts
0
January 12th, 2007 07:00
xvan_egmond
74 Posts
0
January 16th, 2007 12:00
have you tried running:
mminfo -q clientid=y-y-y-y-y ?
It appears that networker has indeed once known clientY as client-id y-y-y-y-y, but since all those resources were deleted you don't see it anymore.
If the above mminfo command gives results, try deleting all those savesets using:
nsrmm -ydS
then try copying clientX to clientY
goodluck,
Xander
nsrhti
46 Posts
0
January 17th, 2007 00:00
I already did:
mminfo -q clientid=y-y-y-y-y-y -r name,client,volume,ssid,savetime,ssretent,group,pool
without any results.
I think some-one has created the client, but never started a backup.