[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:	NetWorker
Notice:	kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:	DECWET::RANDALL.com::lenox

Created:	Thu Oct 10 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	750
Total number of notes:	3361

700.0. "mminfo -r -q with no level" by SANITY::LEMONS (And we thank you for your support.) Wed May 21 1997 12:49

    NetWorker Server for Digital UNIX V4.3 SSB
    
    # mminfo -r 'client,name,volume,level,savetime' -q 'client=boron,
    level=full'
     client    name                           volume           lvl  date
    boron.gppc.dec.com /u04                   O10062          full  5/05/97
    boron.gppc.dec.com /usr/sap               O10062          full  5/05/97
    boron.gppc.dec.com /                      O10063          full  5/05/97
    boron.gppc.dec.com /usr                   O10063          full  5/05/97
    # mminfo -r 'client,name,volume,level,savetime' -q 'client=boron'
    mminfo: no matches found for the query
    #
    
    I expected the second command, which does not include level in the
    query, to show me savesets of ALL levels for the client.  Instead, it
    shows me none.
    
    What's happening?
    
    Thanks
    tl

T.R	Title	User	Personal Name	Date	Lines
700.1	normal stuff... yesterday is default	DECWET::EVANS	NSR Engineering	`Wed May 21 1997 13:26`	6
	mminfo reports by default only entries that fall within last 24 hours unless you say "-a" or "-t <date>" I noticed that all those fulls were prior to yesterday, so I'm betting you had no entries in last 24 hours for boron. Also wathc out for long vs short names!! I got caught by that.
700.2		SANITY::LEMONS	And we thank you for your support.	`Wed May 21 1997 14:01`	29
	.1> Also wathc out for long vs short names!! I got caught by that. That, it turns out, was my problem: # mminfo -r 'client,name,volume,level,savetime' -q 'client=boron' mminfo: no matches found for the query # mminfo -r 'client,name,volume,level,savetime' -q 'client=boron.gppc.dec.com' client name volume lvl date boron.gppc.dec.com /u04 O10062 full 5/05/97 boron.gppc.dec.com /usr/sap O10062 full 5/05/97 And yet, this works: # mminfo -r 'client,name,volume,level,savetime' -q 'client=boron, level=full' client name volume lvl date boron.gppc.dec.com /u04 O10062 full 5/05/97 boron.gppc.dec.com /usr/sap O10062 full 5/05/97 boron.gppc.dec.com / O10063 full 5/05/97 boron.gppc.dec.com /usr O10063 full 5/05/97 # Wierd. It seems that, depending on which switches are used, a long name is/isn't required. That doesn't feel real good to me. Thanks, though, for the workaround. Using the real, long name is something I should be doing anyway. tl
700.3	yeah, I see that too	DECWET::EVANS	NSR Engineering	`Fri May 23 1997 09:57`	4
	when I do mminfo ... -c <client.dec.com> I get different lists of savesets from when I type mminfo.. -q client=<client.dec.com> FWIW
700.4		SANITY::LEMONS	And we thank you for your support.	`Fri May 23 1997 11:29`	3
	uh oh. Which one gives the correct list? tl
700.5	mminfo ... -c <client>	DECWET::EVANS	NSR Engineering	`Tue May 27 1997 08:47`	0
700.6		SANITY::LEMONS	And we thank you for your support.	`Tue May 27 1997 09:00`	8
	Hi Bruce Thanks for researching this; I'll use -c 'clientname' in my scripts. Do you view this as a bug that needs to be fixed, at some point? Thanks tl
700.7	unsure... I think it was my crufty test indexes	DECWET::EVANS	NSR Engineering	`Tue May 27 1997 09:17`	0