Apologies, the bug was in 6.1.1.
Kit
>
> From: Kit Cunningham <kit AT 4F.CO DOT NZ>
> Date: 2004/12/07 Tue AM 08:08:15 GMT+13:00
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: status last backup completion using nsradmin
>
> There is a bug in 7.1.1 where the no_supress file is ignored.
>
> Kit
> >
> > From: Teresa Biehler <tpbsys AT RIT DOT EDU>
> > Date: 2004/12/07 Tue AM 05:02:25 GMT+13:00
> > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > Subject: Re: status last backup completion using nsradmin
> >
> > This file already exists and I'm still getting lines that are
> > suppressed. We're running v7.1.1.
> >
> > -Teresa
> >
> > -----Original Message-----
> > From: Itzik Meirson [mailto:imeirson AT mbi.co DOT il]=20
> > Sent: Monday, December 06, 2004 10:57 AM
> > To: Legato NetWorker discussion; Teresa Biehler
> > Subject: RE: [Networker] status last backup completion using nsradmin
> >
> > Sometime in the past, probably around 6.1.3, Legato started suppressing
> > lines to avoid overloading the "NSR group" resource with text.
> > If you are aware of the consequences and want to avoid this suppression
> > you can create an empty file "NO_SUPPRESS" in the /nsr/debug directory.
> > Itzik
> >
> > > -----Original Message-----
> > > From: Legato NetWorker discussion=20
> > > [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Teresa Biehler
> > > Sent: Monday, December 06, 2004 17:46
> > > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > > Subject: Re: [Networker] status last backup completion using nsradmin
> > >=20
> > > I get "X lines of suppressed output" when I do this. Is=20
> > > there a way to force all the output to be written?
> > >=20
> > > Thanks.
> > > Teresa
> > >=20
> > > -----Original Message-----
> > > From: Legato NetWorker discussion=20
> > > [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
> > > On Behalf Of Darren Dunham
> > > Sent: Friday, December 03, 2004 12:20 PM
> > > To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> > > Subject: Re: [Networker] status last backup completion using nsradmin
> > >=20
> > > >
> > > > I have a script using nsradmin to status the backup.
> > > > When the status=3Didle, I want to find out if the savegroup's last=20
> > > > backup completed successful or failed.
> > >=20
> > > The group as a whole, or just individual save sessions?
> > >=20
> > > And what's a failure to you? Is one file saying "size=20
> > > changed" a failure, or does an entire host have to be down?
> > >=20
> > > If you're just waiting for the group to finish *and* you have=20
> > > no access to the savegroup report, you can get the=20
> > > information out of the 'completion' attribute.
> > >=20
> > > nsradmin> show completion
> > > nsradmin> print type:nsr group; name: mygroup
> > >=20
> > > It should be about the same information, but you'll have to=20
> > > parse it to some extent.
> > >=20
> > > --
> > > Darren Dunham =20
> > > ddunham AT taos DOT com
> > > Senior Technical Consultant TAOS =20
> > > http://www.taos.com/
> > > Got some Dr Pepper? San Francisco,=20
> > > CA bay area
> > > < This line left intentionally blank to confuse you. >
> > >=20
> > > --
> > > Note: To sign off this list, send a "signoff networker"=20
> > > command via email to listserv AT listmail.temple DOT edu or visit=20
> > > the list's Web site at=20
> > > http://listmail.temple.edu/archives/networker.html where you=20
> > > can also view and post messages to the list. Questions=20
> > > regarding this list should be sent to stan AT temple DOT edu=20
> > > =
> > =3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
> > *=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
> > >=20
> > > --
> > > Note: To sign off this list, send a "signoff networker"=20
> > > command via email to listserv AT listmail.temple DOT edu or visit=20
> > > the list's Web site at=20
> > > http://listmail.temple.edu/archives/networker.html where you=20
> > > can also view and post messages to the list. Questions=20
> > > regarding this list should be sent to stan AT temple DOT edu=20
> > > =
> > =3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
> > *=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
> > >=20
> > >=20
> >
> > ************************************************************************
> > **************************
> > The contents of this email and any attachments are confidential.
> > It is intended for the named recipient(s) only.
> > If you have received this email in error please notify the system
> > manager or the=20
> > sender immediately and do not disclose the contents to any one or make
> > copies.
> >
> > MBI - System Team
> > ************************************************************************
> > **************************
> >
> > --
> > 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
> > =3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
> >
>
> --
> 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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
