> dmitri 
> 
> As per EMC:
> "...the NetWorker media database reporting via mminfo command can
> only report the record as a ssid/clone-id pair, not just for the ssid.
> This is why your volretent value is specified on the source volume still
> as the longest date."
> 
> That is volretent can only report the longest of SSID/CLONEID combo, 
> and cloneid happens to be the longest.  However NW expires tapes based
> on SSID provided retention period.  It looks like rather bug or broken
> logic for "mminfo" reporting, because in the case when clone retention
> is longer then source volume, "volretent" value becomes incorrect and 
> in fact does not report VOLume RETENTion of this queried volume.


Yep, it's a bug. Even with browse/retention policies equal, I've seen, 
eg.:

* It's currently April 12

* Most 'distant' saveset expiration (on the volume) into the future is May 
24

* mminfo reports a volretent of May 5th for the volume...

...go figure. :-)  I reported this long ago to Sun, since we're using 
their OEM'ed version of Networker, but who knows if it got passed along to 
EMC/Legato.

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