Thanks,
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?
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.
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? 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?
George
Davina Treiber wrote:
>
> George Sinclair wrote:
> > Hi,
> >
> > After reading several posts and followups, I'm still confused about this
> > business of the client ID versus the resource identifier and what, if
> > anything, I should do with these values if re-creating or renaming a
> > client:
>
> I don't know why the resource identifier has come into this discussion,
> it is totally irrelevant. Forget it even exists. There is nothing at all
> in NetWorker that requires you to know the resource ID or to do anything
> with it.
>
> The client ID is hugely important. Having been bitten by it myself I
> would always be careful to specify it when re-creating a client that has
> previously been deleted. I'm not sure whether it is a problem when
> re-creating the client with the same name, but I wouldn't take any
> chances, because the consequences of getting it wrong are serious. You
> can find backups been written into the media DB under a different client
> ID, making it extremely difficult to recover from. It is very difficult
> to fix.
>
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
