Query with the clretent field

I also tried this, again unsuccessful:


6095:mminfo: no matches found for the query

And what do you get when you do:
mminfo -avot -q ssid=2749776806 -r savetime,ssbrowse,ssretent,clretent,location

Unless you have under same ssid different cloneids I do not see much sense for clretent, but I guess you use cloning and assign different retention to one cloneid instance...

# mminfo -avot -q ssid=2749776806 -r savetime,ssbrowse,ssretent,clretent,location
date browse retent clretent location
04/15/09 05/13/09 05/21/09 05/07/09 VLIB2A
04/15/09 05/13/09 05/21/09 05/21/09 PLIB_SRV20

# mminfo -avot -q ssid=2749776806 -r clretent
undef

- the clone retention has already been changed by my script as it was not something that could wait which is why it is different. An explanation as to why I needed this info: there has been major backup data growth on this server over the last 3 weeks (about 50% from 50-60TB to 80-90TB) and a decision was made that as we had no VTL space for backups anymore we would reduce the retention on VTL backups to 3 weeks with the remaining time having just the physical tape copy existing. To add to the confusion there is a series of backups which have a 2 week browse/retention which are cloned to a pool with a 5 week retention so I was trying to build into my script some kind of allowance for these backups; but all backups share the same tape pool so most 2 week retentions will hang around until the 4 week retentions on the tape expire so I don't expect extending the retentions of these backups will affect us too much...

This is correct. In virtual library this ssid has clretent set to 05/07/09 so mminfo can't show it.




I never used this form of query so I can't say if it is meant to work that way or not. Usually when I use "X unit ago" only with -t option. It seems as with clretent this approach doesn't work.

While speaking about clretent, there is a known issue with clretent in 7.4.x and expiration of volumes which has been addressed by certain patches. No idea if those patches would address query part too.