Networker

Re: [Networker] strange output from mminfo

2003-01-03 09:37:39
Subject: Re: [Networker] strange output from mminfo
From: Chris Madden <maddenca AT MYREALBOX DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Fri, 3 Jan 2003 15:39:45 +0100
I don't have a Networker environment handy (but do occasional consulting
work with it) but would imagine your difference is related to the level of
information being returned.  There are several levels of mminfo entry
detail.

>From Highest to Lowest detail:
Fragment Level - includes individual fragments of a save (relates a saveset
to the actual data files written to tape)
Section Level - includes individual chunks of save.  If a saveset spans from
one tape to another, or is larger than 2GB (on some platforms or before 6.?
version clients) you'll get multiple sections
Save Level - one entry for the overall saveset

My guess is the sorting algorithm mminfo uses invokes the "section level"
detail described above (even though the output level you're using is at the
"save level") and thus you get entries that appear to be duplicates.
Perhaps this is fixed in later versions of Networker as someone else
suggested you to try.  In my experience you're best off NOT using the sort
option (it also takes longer for the mminfo cmd to return) and do it in your
script that is interpreting the cmd output.  I'd also explicitly specify the
columns and column length of the data you're interested in.  Different
versions of Networker return different default column lengths and if you
have it fixed you can use unpack (or the like) to break on characters
instead of whitespace or some other logic making your script less likely to
break over time or upon the occasional funky saveset entry.

Just my 2 cents...hope it helps.

Cheers,
-Chris
----- Original Message -----
From: "Jim Lane" <JLane AT TORONTOHYDRO DOT COM>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Thursday, January 02, 2003 1:41 PM
Subject: Re: [Networker] strange output from mminfo


> after digging a bit more into this it seems that the difference is as
> follows. in the second, sorted by name within client, version a few
> savesets are listed twice. I discovered this by a manual match merge,
> crossing out entries until the orphans became obvious. I extended
> this listing format to include SSID and the duplicates on the longer
> listing were indeed non-unique. I'm not sure what to make of all this,
>
> other than to worry about how much faith I ought to be placing
> in any of the mminfo output I'm looking at. sigh.
>
> Jim Lane
> Sr. Technical Consultant
> Network Services
> Toronto Hydro
> office: (416)-542-2820
> cell: (416)-896-8576
>
> >>> kizzmit66 AT HOTMAIL DOT COM 26-Dec-02 12:38:48 PM >>>
> Hi Jim,
>    Can't really answer the question for you but may be able to give you
> a
> direction.  I ran your three commands here, using 6.1.2. The first two
> commands produced identical results for me, so I don't know why yours
> was
> different.  I believe the big difference for the third command is the
> inclusion of the fragsize as a report spec. My understanding is that
> you
> can have numerous frags per saveset. Removing fragsize made the third
> command produce the same as the previous two.
>
> Good luck
> pt
>
> On Tue, 24 Dec 2002 07:59:57 -0500, Jim Lane <JLane AT TORONTOHYDRO DOT COM>
> wrote:
>
> >Hi, All
> >
> >while i've just been starting to write a little script to check what
> >savesets have been created in the last day, i've started to notice
> >inconsistencies in the output from the mminfo command. i started
> with:
> >
> >  mminfo -a -t "last day"
> >
> >then to get it in a more manageable order i tried:
> >
> >  mminfo -a -t "last day" -ocn
> >
> >the problem is that these 2 forms of the command give different
> amounts
> >of output. the first one gives 372 lines and the second one gives
> 423.
> >i've repeated it a couple of times to be sure. there's no way to diff
> >this so i'm wondering what could account for the discrepancy? it gets
> >stranger still because with a custom report format such as
> >
> >  mminfo -a -t "last day" -ocn -r
> >"client,name,level,savetime,nfiles,fragsize"
> >
> >i get a whopping 5519 lines. is there any reasonable explanation for
> >something like this? or does the mminfo command do something
> drastically
> >different than i imagine?
> >for what it may be worth i'm running Networker 6.0 on AIX 4.3.3
> >TIA
> >
> >Jim Lane
> >Sr. Technical Consultant
> >Network Services
> >Toronto Hydro
> >office: (416)-542-2820
> >cell: (416)-896-8576
> >
> >--
> >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.
> >=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>