On Wed, 28 May 2003 18:35:04 -0400, George Sinclair
<George.Sinclair AT NOAA DOT GOV> wrote:

>I have some savesets that are from 10/??/02 but still show up as
>browsable on several older volumes. I can see this from the volumes
>listing under nwadmin. This seems odd given the fact that the browse
>policy for the affected clients was one month. One of the clients is no
>longer a member of any active group, but the index has not been removed.
>The other client is no longer listed in the client listing under
>nwadmin, and it's client index is gone. I guess I could understand this
>occurring for the one index that still exists because perhaps NetWorker
>still sees the last runs as browsable since the index is no longer
>getting updated, so:
>
>1. Am I wrong about that?
>
>2. Why would some of the savesets for the other index that no longer
>exists still be identified as browsable?

Basically, it's a bug. nsrim does not work on save sets that no longer have
a client resource associated with them. Legato know about this problem and
I expect the fix has gone into some reecent versions. I had a hot fix for
certain versions, but if there's only one or two clients giving you this
problem it's probably easier for you just to run nsrim for the problem
client, using: nsrim -c client. This should do the trick.

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