I'm confused. I have a tape with an expired saveset. I need to extend the 
saveset expiration date, so I can then go and do a "nsrck -L7" on the 
index that applies to that saveset, so I can recover it.

>mminfo -avot -q 
"volume=006510,client=admndbs007,savetime>05/25/2011,savetime<05/27/2011" 
-r volume,name,level,s
etime(22),ssbrowse(22),ssretent(22),ssid,cloneid,ssflags
006510         MSSQL:   full  5/25/2011 8:35:05 PM 7/25/2011 11:59:59 PM 
7/25/2011 11:59:59 PM 1407033572 1306370106 vrEF

So there's the ssid, and the cloneid, and it expired back on July 25.

>nsrmm -S  1407033572/1306370106 -e 12/31/2018
If this saveset has dependents with longer retention periods, the 
dependent savesets will not be browsable after the retention policy 
expiration dat
`Mon Dec 31 00:00:00 2018'.
Are you sure you want to change the retention policy expiration of this 
saveset to `Mon Dec 31 00:00:00 2018'? (yes/no)  [no] yes

And yet, the expiration doesn't change ...

006510         MSSQL:   full  5/25/2011 8:35:05 PM 7/25/2011 11:59:59 PM 
7/25/2011 11:59:59 PM 1407033572 1306370106 vrEF

So what am I doing wrong, in this case? This is the same procedure I 
usually use, to recover expired savesets ....

-- 
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER