Fantastic.  I'm having one small problem in creating the new client though.
I have deleted the old client and renamed the index folder to the new client
name.  When I go to create the new client I get the following message:

"SERVER lbksvbackup.pcca.com: lbksvtestcomm.pcca.com previously defined.
Re-Apply to use the original client id: XXX(which is not the one from the
old definition.  Otherwise the client must first be renamed."

I don't have a client listed with this name "lbksvtestcomm.pcca.com" but it
thinks that I do or did in the past.

I can't find any listing in nsradmin or mminfo that indicates that this
client is configured.

Do you know of a way to remove any and all references to a client name?

--Shawn

----- Original Message -----
From: "Philippe MICHEL" <philippe.michel AT THALES-IS DOT COM>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Wednesday, September 15, 2004 11:21 AM
Subject: Re: [Networker] Transferring indexes between client definitions

Shawn Cox wrote:

I'm in the process of renaming most of my servers due to a dns naming
convention change.

Say I have a client named xxx01.domain.com and have a years worth of
indexes
for it.  The box will be rebuilt on new hardware and in the process named
yyy01.domain.com.  In the past I have just added yyy01.domain.com to the
alias list of the original client definition and the backups go one
without
any trouble once the DNS is updated.  But this is a bit messy and causes
confusion when doing restores as the client names no longer match.

So, is there a way to create a new client definition with the new dns
name
and transfer the indexes from the old?  There is a client ID field in the
client definition, but it's read only and I can't seem to do much more
than
stare at it.

When creating a new client, you can reuse the id of an removed client and
the new client will
inherit the indexes of the old one. This is just what you need.
- take note of the client-id
- remove old-client
- rename /nsr/index/old-client to new-client
- create new-client with the same id as old-client (the id is not
read-only when creating a client)

If you have a lot of clients to rename, it can be largely automated.
Something like :

nsradmin -s server -i - <<EOF
option hidden
show name ; client id ; schedule ; browse policy ; retention policy ;
directive ; group ; save set ;
priority ; remote access ; remote user ; password ; backup command ;
aliases ; parallelism ; storage
nodes
print type: NSR client;
name: old-client;
EOF

will give most of what is needed to recreate the client. Change the name:
and aliases: fields in the
result, add
nsradmin -s server -i - <<EOF
create type: NSR client;
before each entry and EOF after them and you have a script to create the
new client.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=