Networker

Re: [Networker] Why is an old saveset still browsable?

2003-06-02 07:46:45
Subject: Re: [Networker] Why is an old saveset still browsable?
From: Davina Treiber <treiber AT HOTPOP DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Mon, 2 Jun 2003 07:46:47 -0400
On Fri, 30 May 2003 17:31:11 -0400, George Sinclair
<George.Sinclair AT NOAA DOT GOV> wrote:

>Yes, this appears to be exactly what's happening. It looks as if the
>problem occurs in the following two scenarios:
>
>1. The client is no longer being backed up, never mind the fact that its
>index may or may not still exist on disk.
>2. The affected saveset is no longer being backed up -- either it
>doesn't exist anymore or it's just being skipped -- but the client is
>still being backed up.
>
>I ran an mminfo command to track these rascals down. Excluding cases
>where the saveset is still within the browse policy, I still found a ton
>of them. It looks like most of the "recoverable" ones show up with "vrF"
>or sometimes "vrEiF" for the ssflags whereas these ones that are still
>listed as "browsable" seem to show up with "vF". So I greped out the
>ones with "vrF" and "vrEiF" and the majority of the output fit into one
>of the above two scenarios. The rest were divided between those that
>were still legitimately within the browse policy and those that were
>actually "recoverable" but showed up with "vF". In most cases, however,
>this was due to the fact that they were written to a pool that had
>indexing turned off so the client's index did not get updated. Not sure
>about the others.

So, have you run an nsrim for the affected clients? Did it help?

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

<Prev in Thread] Current Thread [Next in Thread>