> > Something like this should work.
> >
> > /usr/sbin/nsr/mminfo -q "volretent>='today',volretent<='1 week'" -r 
> > "volume,volretent" 
> >  
> 
> I doubt very much that this will work. It depends on the save set expiry 
> not the volume.

But the 'volretent' is simply the largest value for 'ssretent' on the
volume (in normal cases), right?

> There is probably no way to accomplish exactly what David has asked 
> without writinng some pretty complex scripts to determine save set 
> dependencies, and even then the result will be affected by potential 
> failures of backups that have not yet run.

Depends on the scale of retention and cycles.  If someone is doing (say)
monthly retention and weekly cycles, then unless they've missed several
fulls, near future backups should have no effect on the retent time
because newer cycles would already exist.

If someone is trying to do 6 week retention with a monthly cycle, then
even one failure is going to throw them off.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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
wit 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