Backup Central

Hi,

Haven't done this in a long time so just wanted to corroborate.

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?

Oh, one more thing. The client is still listed under Local Hosts (nmc).
When I click on it, it tries to connect and then comes back with "Unable
to connect to server: Failed to contact using UDP ping". Certainly no
surprise, I'm sure. Most of the client entries under Local Hosts have
just the primary backup server and snode listed, and obviously the NW
instance ID is the same for all the references to the server and snode
respectively. I guess there's a certificate stored on the server that
has to match an entry on the client:/nsr/res/nsrladb entry.

Will it be necessary to delete this Local Hosts entry? How will I be
able to do it? Maybe it will get updated automatically once the new
client is started?

Thanks.

George


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

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?

Tim
--
Tim Mooney Tim.Mooney < at > ndsu.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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

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

Exactly. As long as you use the same DNS name and IP address on the
client, NW won't care that the actual physical client has been replaced
with all new hardware. I've done this a few times.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

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!

George

Tim


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

In regard to: Re: [Networker] New client with old name?, George Sinclair...:

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?

It does.

Maybe that will all get refreshed or regenerated when the first backup starts
or maybe when I start up the client?

If you thought to copy the /nsr/res from the old client to the new one,
things should just work.

If you didn't, you'll probably need to delete the peer information for
that particular client on your NetWorker server, and let it pick up the
new one that will automatically be generated when you start up the client
software on the new client system.

Tim
--
Tim Mooney Tim.Mooney < at > ndsu.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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER