I guess you mean retention time. The index savesets are not browsable.

The data saveset and the corresponding index saveset should be recoverable in 
order to run nsrck -L7.

If they have expired, then you can use nsrmm to set the retention to some date 
in the future (e.g. using  -e "tomorrow"),  and then, change the mode to 
"notrecyclable", again with nsrmm ( using both ssid & cloneid of the saveset 
to be reset).

I suggest using the numeric nsavetime instead of the date-formatted savetime 
with nsrinfo.

It is easy to have problems because nsrinfo has the mm/dd/yyyy format 
hardcoded whereas mminfo can change depending on the locale.  This is an 
annoying  design (bug?) in networker.


Suggestion: 
if you run 
   mminfo ...  -r"...,savetime,...,nsavetime,client" 
then  the last two fields (savetime & client) can be appended to the nsrinfo 
command
   nsrinfo -L7 -t   <APPEND HERE> 
this can also be scripted easily.

 

jee



On Friday 28 Sep 2012 12:13:57 you wrote:
> In regard to: [Networker] nsrck -L7 error, Werth, Dave said (at 11:40pm 
on...:
> > I'm trying to restore an index from back in May using the command:
> > 
> > nsrck -L7 -t "05/27/12" Athena
> > 
> > When I run it I get the following message shortly after starting the
> > command with no indication that the tape loaded in the drive was
> > accessed:
> > 
> > 39078:nsrck: SYSTEM error: The operation completed successfully.
> > 
> > I've used mminfo to confirm that the index information is still in the
> > media database.
> 
> Check your logs on your backup server.  Do they contain something like
> 
>    nsrck: SYSTEM error: 'nsrindexasm' exited with status 76
> 
> ?
> 
> > Does anyone have any helpful advice for me.  I'd prefer to avoid using
> > scanner because it will take the better part of a day to run.
> 
> You say that the index info is still in the media database, but has it
> passed its browse period?  If so, have you read this
> 
>       https://solutions.emc.com/emcsolutionview.asp?id=esg98649
> 
> Tim