In regard to: [Networker] Client id -- final question and 2 observations,...:

Question 1: Should you change the id back to match the original as soon
as son of fred is first created?

I wouldn't.  You're not talking about a replacement host, you're talking
about a new host, that might have a completely different purpose and
completely different filesystems, that just happens to have the same name
as the prior client.

I think it makes sense to just leave it as the new id because if you
ever wanted to recover savesets based on the old id, you could just
change it back, recover what you wanted, and then change the id back to
the new one once you're done as long as you did so before the next
backups run for fred. The only danger I can see with this is that you
might forget to change it back in which case the next backups would use
the old client id and then you'd have a little bit of an aberration.

Observation 1: Regardless of whether you should or shouldn't reuse the
same id, it seems logical that as long as the current client id matches
the one for the saveset(s) that you specifically want to recover, then
you should be fine to recover them whereupon the id SHOULD then be
changed back, if necessary, to match the client id for the most recent
savesets.

Observation 2: If you're adding the new fred relatively soon after the
old one goes away then seems reasonable that you would just keep the
original index so if you did need to recover anything recent that was
backed up on the old fred, you could use nwrecover. For example, maybe
you move all the data from the old fred to the new fred, and everything
on the new host is set up the same way with same OS, etc. BUT, if you're
adding the new client long after, or if there really is no association
between the new fred and the old one whatsoever, except for the fact
that they just happen to have the same host names, then seems reasonable
to just create a whole new index and not use the old one at all.

I actually wouldn't do any of that.  Before creating fred #2, I would
either delete or rename the index for the deleted client fred #1.  I
would let fred #2 start completely fresh.

If I needed to get data back from the old client, I would set up my
networker server to query /etc/hosts before DNS, insert a fake name
(like old-fred.your.fqdn), create a client that exactly matches the fake
DNS name I added *and* that has the same clientid as the old fred.

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=