Or you could delete the existing clients and re-add them with the old client 
IDs.  This should rename the client and indexes and when you scan the older 
media it should merge the old and new client indexes.


-----Original Message-----
From: EMC NetWorker discussion on behalf of Tim Mooney
Sent: Fri 8/8/2008 16:07
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Problems renaming NW 7.4.2 server in Windows
 
In regard to: Re: [Networker] Problems renaming NW 7.4.2 server in Windows,...:

> EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
> 08/08/2008 04:22:17 PM:
>
>>> Right now, it's not - it says it is creating "~client1", but I don't
> see
>>> that client as a restore source at all.
>>
>> I had that happen once several years ago when I recreated a client
> without
>> giving it the same client id as before.  It took quite a while, but
>> support was able to help me get to the point where I could recover.
>>
>> If you run an mminfo report after you've done the scanner, like this:
>>
>>     mminfo -av -r 'client,clientid' | sort -u
>>
>> (or whatever you would use to sort and remove duplicates on Windows),
>> are there any clients OR clientids that show up in the list that would
>> give you a clue what the old client ID was?
>
> It (sorta) does, yes!
>
> ~admndev007-1 7d246f01-00000004-45ba556e-45be1728-001d0000-0a4007c8
> ~admndev008-1 8df3178d-00000004-46028bdc-4603ec9b-02140000-0a4007c8
> ~admnlts003-1 2f1573b4-00000004-45ba5566-45be0fb3-00150000-0a4007c8
> ~pssql1-1  db0b337e-00000004-45ba5572-45be20d4-00210000-0a4007c8

I figured it might.

> After doing the "scanner -i", that's what the mminfo reports, altho I
> can't see those clients in the client list.

I seem to recall having the same issue when I ran into the problem years
ago.  This was like 9 or 10 years ago though and back in the NetWorker
5.x series though, so I'm sure I've forgotten most of the details.

> Should I presume that those are my old client IDs?

Yup.

> If so, do I need to
> delete "admnlts003", and remake it, using that client ID?

Yup.  Or, create it with a different name.  If NetWorker can resolve
the name, it should be fine creating the client as something like

        admnlts003-old

That way, you can have both the old data and the data you've backed
up since converting to the new server.

> *OR* can I just
> enter that client ID, directly into the existing "admnlts003" client,
> overwriting it's current client ID?

I don't think that's going to do what you want.  I would be very hesitant
to do that.

Tim
-- 
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER