There is a patch (LGTpa68362) for this or a similar problem in 7.1.2.
If the savefs fails, it automatically requests a tape for Default. I
might be late in the game to help, but I thought I would throw in my
$0.02 anyway.
Cheers,
Jim
------
Jim Neild
Enterprise Storage
Smart Systems for Health Agency (SSHA)
Phone: 905-944-5388
Blackberry: 416-648-4528
Fax: 905-944-5357
E-mail: jim.neild AT ssha.on DOT ca
"Not only is the universe stranger than we imagine, it is stranger than
we can imagine. "
"Something unknown is doing we don't know what."
Sir Arthur Eddington (1882 - 1944)
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Faidherbe, Thierry
Sent: Thursday, October 28, 2004 2:26 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] More 'Default' pool problems with Legato 7.1.2
Hi,
You can met backups to go to default pool in some cases.
I have fixed one occurring in some rare cases. The problem was related
to storage node affinity of the client and authorized tape devices in
pool settings.
Due to an hardware event, the drive of the client (acting as SAN SN) has
been disabled. NetWorker then relied on the next entry in the client
storage node affinity (because no local device to mount the required
volume) but pool could not be mounted on the second storage node's tape
devices.
So, pool criterium being too restrictive, it resulted in a tape from
Default pool to be mounted on the second SN.
The tape in your lib is maybe read-only that could prevent the volume to
be mounted for write operation. Mount it manually (too see if Networker
mount it in a write protected mode) or label a new one and let the
backup to be written on the default volume.
Once backup is completed, look sessions written on that volume to
determine clients causing problems.
This may be caused by time-outs setting for networker to elect a new
storage node if volume request failed to be served in the defined time
interval (per device save mount and save lockout timeouts).
HTH,
Th
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD
******* h ******* 1 Rue de l'aeronef/Luchtschipstraat
****** h ****** 1140 Bruxelles/Brussel/Brussels
***** hhhh pppp *****
***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
***** h h pppp ***** 1200 Bruxelles/Brussel/Brussels
****** p ****** BELGIUM
******* p *******
********* ********* Phone : +32 (0)2 / 729.85.42
Mobile : +32 (0)498/ 94.60.85
Fax : +32 (0)2 / 729.88.30
I N V E N T Email/MSN : thierry.faidherbe AT hp DOT com
Internet : http://www.hp.com/
________________________________________________________________________
MOBISTAR SA/NV
CSO/CTO/CEO/SSD/SBI
SYSTEM Team Charleroi, Mermoz 2 Phone : +32 (0)2 / 745.75.81
Avenue Jean Mermoz, 32 Fax : +32 (0)2 / 745.89.56
6041 GOSSELIES Email : tfhaidhe AT mail.mobistar DOT be
BELGIUM Web : http://www.mobistar.be/
________________________________________________________________________
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Manel Rodero
Sent: Thursday, October 28, 2004 12:27 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] More 'Default' pool problems with Legato 7.1.2
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
