Networker

Re: [Networker] mminfo 't' option -- STRANGE behavior!!!!

2004-10-20 11:54:23
Subject: Re: [Networker] mminfo 't' option -- STRANGE behavior!!!!
From: "Krishnan, Ramamurthy" <Ramamurthy.Krishnan AT KPMG.CO DOT UK>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 20 Oct 2004 16:52:40 +0100
Try using a more generic option of 

mminfo ... -t "12 hours ago"

You can co-relate your current time to 4PM yesterday and fill up the
number.  To me it works perfect..

- Ram. 

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Robert Maiello
Sent: 20 October 2004 16:45
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] mminfo 't' option -- STRANGE behavior!!!!

The mminfo manpage is ambiguous as to what "savetime" the -t refers to.
Is it the same as the savetime attribute (which is the time on the
client) or is it the sscreate attribute (which is the time it was
created on the server) ??

If one of your clients has a clock a bit out sync it may go missing from
reports?

Robert Maiello
Pioneer Data Systems

On Wed, 20 Oct 2004 11:32:34 -0400, George Sinclair
<George.Sinclair AT NOAA DOT GOV> wrote:

>Well, what I've discovered is that even with the '-a' option, using
'-t'
>does NOT list index entries, bootstrap or any savesets wherein the pool

>has indexing turned off. However, indexes, bootstrap and savesets from 
>pools with indexing turned off *DO* show up when using the 'saveset'
>attribute. I then tried using '-v' option with the '-a' and '-t' as:
>
>mminfo -s server -av -t 'yesterday 4 pm' or 'yesterday 16:00'
>
>and then I see the index, bootstrap and other entries that were missing

>when run without the 'v'. Of course, to get the output to match the 
>output from the mminfo command that uses the saveset attribute, I 
>likewise have to include '-v' option on that. What the heck is going on

>here?!!!! This seems ridiculous.
>
>Another thing I notice is that if I run the command with the saveset 
>attribute, but I grep out the index, bootstrap and the one saveset name
>(special) whose pool has indexing turned off as:
>
>mminfo -s server -q 'savetime>=yesterday 4pm' | grep -v "index:" | grep

>-v bootstrap | grep -v
>
>and then I compare with:
>
>mminfo -s server -t 'yesterday 4pm'
>
>then it matches, but if I go back a couple of days, I find a few 
>savesets that still show up in the first command and not the second, 
>but only a couple, and the pools that these write to do not have 
>indexing turned off. Based on what I've found, I just don't trust the 
>'-t' option to really give you everything. I have a sneaking suspicion 
>that it will leave something out that you were expecting.
>
>George
>
>
>Darren Dunham wrote:
>>
>> >
>> > Hi,
>> >
>> > I notice I receive identical output for all of the following 
>> > commands wherein I list savesets since 4 PM (EDT) yesterday:
>> >
>> > mminfo -s server -q 'savetime>=10/18/04 4 pm'
>> > mminfo -s server -q 'savetime>=10/18/04 16:00'
>> > mminfo -s server -q 'savetime>=1098129600'
>>
>> This uses -q, which implies -a.
>>
>> > HOWEVER, if I instead run:
>> >
>> > mminfo -s server -t 'yesterday 4 pm' or 'yesterday 16:00'
>>
>> This doesn't use q, c, m, N, or o and you haven't explicitly used -a.
>>
>> My assumption is that this is the difference.  Because I've been 
>> bitten by similar issues so many times, I just always use -a.
>>
>> See if that makes everything work the same.
>>
>> --
>> 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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=




                Email Disclaimer

This email has been sent from KPMG LLP, a UK limited
liability partnership, or from one of the companies within
its control (which include KPMG Audit Plc , KPMG United
Kingdom Plc and KPMG UK Limited). The information in
this email is confidential and may be legally privileged.
It is intended solely for the addressee.  Access to this
email by anyone else is unauthorised. If you are not the
intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it,
 is prohibited and may be unlawful.  When addressed to
our clients any opinions or advice contained in this email
are subject to the terms and conditions expressed in the
governing KPMG client engagement letter.

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