Brendan,

>>> {1}:/exp/legatodisk3/onsite>mminfo -q'ssid=3962789633'
>>> mminfo: no matches found for the query
>>
>> What does "mminfo -q ssid=3962789633 -r ssid" give you?
>
> Not really sure, but it will either give you and error (not sure whether
> the syntax is right), or it will return 3962789633
>
> What you are asking it to do is produce a report of the save set id for
> that save set it

True.  It will either return "no matches found" or "3962789633".

There was, however, a little bit of method in the madness.

NetWorker has had a bug in it for as long as I have known it (4+ years
now) where it does not correctly remove records from the mm database.
The test I gave is a quick way to determine whether this save set is a
victim of this bug or not.  If it is then Robert's problem might be
another symptom of the same bug.

Naturally I've attempted to report this bug to the Legato support
people but they were unable to think of a work around so they just
closed the call.  I've since discovered that if you persist with them
(repeatedly insist that it *is* a bug in their flagship product, that
your network passes the "ping" test, and that your DNS is correctly
configured, and refuse to let them close the call) for about 3 months
they start to believe you and will actually log it as a problem.  Maybe
I should have another go.  OTOH, I've got bigger fish to fry...

George.
--
George Scott           George.Scott AT its.monash DOT edu
Systems Programmer, IT Services, Monash University

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