Networker

Re: [Networker] More 'Default' pool problems with Legato 7.1.2

2004-10-27 03:17:00
Subject: Re: [Networker] More 'Default' pool problems with Legato 7.1.2
From: Manel Rodero <manel AT FIB.UPC DOT ES>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 27 Oct 2004 09:08:20 +0200
Hi Darren,

Yes, I know that the pool "Default" is used when a job doesn't match the
selection criteria for another pool.

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).

Our pool definition is:

nsradmin> print type:NSR pool;name:LCFIB Normal
                        type: NSR pool;
                        name: LCFIB Normal;
                     comment: ;
                     enabled: Yes;
                   pool type: Backup;
              label template: LCFIB Normal;
                      groups: LCFIB-Normal;
                     clients: ;
                   save sets: ;
                      levels: ;
                     devices: ;
         store index entries: Yes;
           auto media verify: No;
      Recycle to other pools: No;
    Recycle from other pools: No;
      volume type preference: ;
                 mount class: default;

And the group definition is:

nsradmin> print type:NSR group;name:LCFIB-Normal
                        type: NSR group;
                        name: LCFIB-Normal;
                     comment: ;
                    snapshot: False;
                   autostart: Enabled;
                  start time: "0:30";
                    interval: "24:00";
              client retries: 3;
                      clones: No;
                  clone pool: Default Clone;
                     printer: ;
             Snapshot Policy: Daily;
               Snapshot Pool: Default;

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?

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Darren Dunham
> Sent: Tuesday, October 26, 2004 5:11 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] More 'Default' pool problems with 
> Legato 7.1.2
> 
> 
> > Today, only 1 machine in the group hasn't finished the 
> backup. I've stopped
> > the group. I've used 'nsradmin -s machine -v1 -p390113' to 
> see if we have
> > connectivity with the daemon running in the client. I've found this
> > connection a lot more slow than other clients. I've login 
> into this machine
> > and restarted NetWorker (/etc/init.d/networker stop + 
> start). Then, nsradmin
> > was connecting faster than before. I've restarted the 
> backup and it finished
> > properly, without asking for tapes in the 'Default' pool.
> >
> > I would like to know why Legato asks for tapes in the 
> 'Default' pool:
> 
> It asks for 'default' pool tapes when no other pool matches 
> the job it's
> trying to do.
> 
>      There are four pools  shipped  pre-enabled  with  NetWorker.
>      The  Default  pool  is  meant to collect any backup data not
>      directed to a pool a user creates with  selection  criteria.
> 
> > a) if it has 4 tapes that can be used (the 2 into drives, 
> one at 94% at the
> > other at 70%; and 2 that can be recicled)?
> 
> No.  If any other pool matches (whether it has tapes or not), it would
> request from that pool.
> 
> > b) only when it has problems when some machine (we detected 
> the problem
> > asking for 'Default' tapes some days before when we had DNS 
> problems and
> > Legato can't contact, resolve a lot of name machines)?
> 
> Name resolution problems usually cause the backup to be aborted (can't
> verify the name), not for the backup to change class.  I 
> suppose if your
> pool names clients by name, it's possible, but I've never seen it.
> 
> How is the pool (that you think should be used, but isn't) defined?
> 
> Sometimes the easiest thing to do is create a 'default' volume real
> quick (even a disk volume).  Examine the job that is being sent to it,
> and determine why it's not matching your existing pools (group, level,
> client, save set).
> 
> --
> 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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=