Re: [Networker] Why won't mminfo allow nsavetime on query?
2005-07-27 18:54:14
Thanks, Tim. Hmm ... maybe another bug in our release. I can work around
it using the client name. Maybe I'll give Legato a call to see if it's a
known issue. Looks like upgrading will fix a lot of things for us.
george
Tim Mooney wrote:
In regard to: Re: [Networker] Why won't mminfo allow nsavetime on
query?,...:
I guess I worded the question wrong. What I observe is that if I run
mminfo with -q savetime, and I use an nsavetime (numeric) value then
it says no matches found, but if I include the client name like:
nsrinfo -s server -q 'savetime=nsavetimevalue, client=clientname'
then it returns what I expect, but why does it say no matches found
when I say:
nsrinfo -s server -q 'savetime=nsavetimevalue'
I can't reproduce this on NetWorker 7.1.3. I'm able to get matches in
every single case when I query just on savetime=nsavetimevalue.
For example, doing
for c in client1 client2 client3 client4
do
mminfo -q client=$c -r nsavetime >> /tmp/nsavetimes
done
for s in `sort /tmp/nsavetimes`
do
mminfo -q savetime=$s -r 'client,name,level,nfiles,totalsize' 2>&1
done | tee grep -i 'matches'
returns no output, which means that there was always a match.
Tim
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
|
|