Re: [Networker] New client with old name?

2012-01-06 14:53:50
Subject: Re: [Networker] New client with old name?
From: George Sinclair <george.sinclair AT NOAA DOT GOV>
Date: Fri, 6 Jan 2012 14:53:23 -0500
On 2012-01-06 14:04, Tim Mooney wrote:
In regard to: [Networker] New client with old name?, George Sinclair said...:

An old RH Linux client was decommissioned. A new RH Linux client now exists with the same host name and IP address. The same disks have been moved to it, so it has the same file systems as before. The client software has been installed but not yet started. We would like to continue using the same
CFI as before. Is it a simple matter of removing the old NSR client
resource(s), starting the client software on the new box and then
re-creating the NSR client resource with the same clientid (before
applying changes) as before? Is that all?

If you want to use the same client indexes, why do any of that?  Why not
just schedule an out-of-band full backup?  You could limit the full to
just the filesystems that would have changed (the OS volumes, I'm
guessing), or you could back up everything.

Either way, you already have the client resource, why remove it just to
recreate it?

Ok, I see what you guys are saying. Yes, that makes sense. I guess I'm confusing this with another scenario wherein the IP and/or host name was changed.

With the exception of one file system, all the others are rather small, and fulls could certainly be re-run from scratch without serious impact. I believe all the system file systems (e.g. /, /usr, /var) are new so a full would be recommended on those. Kind of silly to run incrementals there. There are three other non-system file systems that were on the old box, but the disks were transferred. Two of these file systems had not changed on the old box in quite some time so the only activity we saw on the old box was if we ran a full. The other one (this is the big one) had regular activity, but most of it is static, and it was broken down into multiple save sets for static and non-static data segregation. Even if I have to re-run a full on the non-static save set, it's not that large. Just for laughs, I'll probably run an incremental backup estimate just to see what NW reports on the three amigos. I'm sure it will report large incrementals on the new system file systems, however.

What about the entry for this host under 'Local Hosts' ??? Doesn't the NW client create some kind of certificate on its side to agree with the server? Maybe that will all get refreshed or regenerated when the first backup starts or maybe when I start up the client?

Thanks again!



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 or
via RSS at

<Prev in Thread] Current Thread [Next in Thread>