Hello again,

In my last message I said that I will try to label a tape for the 'Default'
pool ...  but I've discovered that there is a tape in this pool AND this
tape IS in the changer.

So now I'm more confused than before. If Legato claimed for a tape in the
pool 'Default' why it didn't use the tape we had in this pool and was in the
changer?

I'm dissapointed. At least today the backups went correctly so this kind of
problems are a little tricky to resolve. I've opened a case with my support
at Universtiy -> HP/Compaq -> Legato contract.

If some of you have any more ideas in the meantime they will be very
appreciated ;-)

See you.

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Darren Dunham
> Sent: Wednesday, October 27, 2004 5:14 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] More 'Default' pool problems with 
> Legato 7.1.2
> 
> 
> > My question was related to: why this is happenning now? 
> We've used Legato
> > for more than 4 years without having this problem. Backups 
> go to the "LCFIB
> > Normal" pool always.
> >
> > But now, AFTER UPGRADING TO 7.1.2, when there is a problem 
> with some client,
> > Legato tries to use tapes in the pool 'Default'. Has the 
> selection criteria
> > changed in version 7.1.2? Our group is defined in the same 
> manner for many
> > years and it has always worked (in version 5.5 and 6.x).
> 
> My response was general, and not specific to 7.1.2.  I'm not running
> that version at the moment, so if there's a new bug 
> introduced with it,
> I'm not aware of it directly.
> 
> You're probably familiar with 'savegrp -p' for probing clients.  It
> returns the pool that would be used.  You might try running 
> that during
> a maintenance period.  I'd certainly see if I could try it in a
> situation where either the master or client was disconnected 
> from DNS to
> simulate your earlier DNS failure.
> 
> > Our pool definition is:
> >
> > nsradmin> print type:NSR pool;name:LCFIB Normal
> 
> >                       groups: LCFIB-Normal;
> >                      clients: ;
> >                    save sets: ;
> >                       levels: ;
> >                      devices: ;
> 
> Given that, I see nothing that a DNS failure should affect.  I could
> have seen a client entry get confused in that case, but the group
> shouldn't.
> 
> > In the meantime, I'll try to label a tape in the pool 
> 'Default' to see
> > what's is saved into it when this problem appears. (Today 
> the backup has
> > finished ok :-)
> >
> > Any more idea?
> 
> Nope.  You can turn on all the daemons to a high debugging level, but
> that's just annoying to run with all the time.  I certainly don't know
> any tool that describes *why* networker has chosen a particular pool.
> 
> --
> Darren Dunham                                           
> ddunham AT taos DOT com
> Senior Technical Consultant         TAOS            
> http://www.taos.com/
> Got some Dr Pepper?                           San Francisco, 
> CA bay area
>          < This line left intentionally blank to confuse you. >
> 
> --
> 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. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> 

--
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. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=