In regard to: Re: [Networker] Client id versus resource identifier?, George...:

Okay, so everyone agrees that in this case you wanna change the new
client id to match the old one ... well, we all know the original client
id could be determined easily enough by running mminfo, assuming the old
savesets were still in the media datatabase, and as Darren commented,
nsradmin could be used to change the id of the new client back its
original value -- all well and fine -- but how would having the wrong
value prevent you from recovering older savesets via saveset recover?
Clearly, you can't use saveset recover unless the client exists, so I
guess if you create it, and the id doesn't match the one that's
associated with the saveset(s) you're trying to recover then all bets
are off and NetWorker will simply hose you?

I'm not sure how NetWorker will treat a purely 6.x client, but I can tell
you that we had a number of clients that we deleted back when we were
running mainly 4.x and 5.1 clients with a 5.2 server.  Last year, we had
a restore request for data from one of those clients.  Our server was
(at the time) running 6.1.1.

I spent a month working with Legato, and we never were able to get the
data recovered from the clone tapes, using our 6.1.1 server.  In the end, I
gave up and installed 5.2 on some old hardware I luckily had available,
and recovered the data that way.

My understanding of the problem I ran into was basically

- 5.x used a very short client id.
- When you upgrade your server from 5.x to 6.x, the upgrade process
  converts all *existing* clients to a much longer client id.  Any
  savesets that are associated with a client that has been deleted
  will not get the client id upgraded to the long form.
- When creating a client, the 6.x tools will not let you create a
  client with the 5.x-style clientids.
- You can create a client with the same name as the 5.x client had, but
  because of the last issue, there's no way to match the new client's
  id with the 5.x client id associated with the old savesets.

But let's say that the original index is still on disk, and you don't
change the client id back to the correct (original) value but you never
ever recover anything from before and only recover stuff from that point
forward. Will NetWorker care that there are savesets for two different
client ids, both having the same client name? I'm thinking no, and you
could continue using the index and recovering newer stuff but just
couldn't recover older stuff.

It's hard to say, but you could be correct.

I just wanna be clear about this and confirm that it's not the index
where the id is stored, nor the res file but rather the database itself
since you can query for the id with mminfo, correct?

The clientid is associated with every saveset (hence it's almost certainly
part of the media db).  It also happens to reside in the res file.

In this case, since
the resource id is irrelevant, then there would be no need to recover an
older version of the nsr.res file?

I believe that's correct.

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