In regard to: Re: [Networker] not found in media index, Davina Treiber said...:

>Tim Mooney wrote:
>
>> The obvious way to fix the problem is to do what Legato recommends -- move
>> the media database out of the way with NetWorker shut down, and then bring
>> it back online.  My recollection is that a blank media database will be
>> recreated.
>>
>> At that point, you have the tedious job of running `scanner -m' on all
>> your tapes, to repopulate your media database based on the available
>> tapes.
>
>It makes me laugh that they would even suggest this. I am working in an
>environment where the largest/oldest server has around 4000 volumes, and
>the thought of scanning even 2 or 3 tapes brings me out in a cold sweat.
>  Scanning in ALL the volumes is way beyond the realms of possibility.

I agree, but assuming you had subtle media database corruption that might
have started weeks or months ago, what other choice do you have?  The
check and repair capabilities in tools like `nsrim' are minimal at best.
Even if it couldn't repair problems, it would be nice if something like
`nsrim' had very thorough structure and consistency checks for the media
database, so you could at least tell when a problem started.  The way
things are now, NetWorker may not even detect media db consistency issues.

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