Networker

Re: [Networker] Can't connect to media database errors?

2002-10-03 13:33:16
Subject: Re: [Networker] Can't connect to media database errors?
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Thu, 3 Oct 2002 13:37:40 -0400
Thanks. I'll give that a try.

George

Bob Schuknecht wrote:
>
> Duncan,
>
> We've also encountered these errors and it had to do with Networker's
> once-a-day
> running of nsrck -MX. We are running version 6.0.2.
>
> We have about 180 clients defined on the backup server and when Networker
> starts
> this many concurrent nsrcks' our Compaq DL580 virtually does nothing else
> but run these
> checks. Any saves that are running typically display messages like you
> documented concerning
> the media database being unavailable.
>
> We found two files in /nsr/mm named cmprssd and nsrim.prv. Both of these are
> zero byte files
> but their creating time dictates when Networker will run these checks.
>
> To eliminate the contention problems between saves and the nsrcks we removed
> those two
> files and then re-created them at a time when the backup server is not doing
> anything.
>
> Bob Schuknecht
>
> >  -----Original Message-----
> > From:         "Duncan Boccio" <dboccio AT INCYTE DOT COM>@INTERNET@HHC
> > Sent: Wednesday, October 02, 2002 5:35 PM
> > To:   NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > Subject:      Re: [Networker] Can't connect to media database errors?
> >
> >
> > I've seen this when networker is trying to start a save and
> > a bootstrap is running. The bootstrap locks down the media
> > database and when a backup tries to start it can't connect to
> > the media database. Also, an nsrim process will sometimes
> > check the media database automatically after a  savegroup completion
> > if one hasn't run for a certain period of time (I'm not sure what the
> > criteria is for running the nsrim but the file /nsr/mm/nsrim.prv
> > has something to do with it). I think that if this nsrim proc is runninng
> > when a backup tries to start will cause the backup to fail with the
> > messages you see below.
> >
> > I'd check the daemon.log for anything like a bootstrap or the
> > media database compressing that might be locking down
> > the media database when the backup starts.
> >
> > Duncan
> >
> >
> > George Sinclair wrote:
> >
> > > Hello,
> > >
> > > We sporadically see failed saveset messages on random clients:
> > >
> > > --- Unsuccessful Save Sets ---
> > >
> > > * client:/tmp 1 retry attempted
> > > * client:/tmp save: error, can't connect to media database on server
> > > * client:/tmp
> > > * client:/tmp save: Cannot open save session with server
> > > * client:/vol03 1 retry attempted
> > > * client:/vol03 save: error, can't connect to media database on server
> > > * client:/vol03
> > > * client:/vol03 save: Cannot open save session with server
> > >
> > > I've substituted the word client and server in the sample. This does not
> > > always occur on the same clients and not always on the same file
> > > systems. This is just a sample.
> > >
> > > We're running NetWorker 6.1.1 on Solaris 2.8 with a Linux Storage node
> > > server running under RedHat 7.1. Does anyone know what causes these
> > > errors? Is there something we can do, or something we should NOT be
> > > doing that might be contributing to this problem? We are not running a
> > > SAN, and we try to stage our groups as appropriate.
> > >
> > > Thank you.
> > >
> > > George
> > >
> > > George.Sinclair AT noaa DOT gov
> > >
> > > --
> > > Note: To sign off this list, send a "signoff" 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" 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" 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" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=