> If your main concern is simply freeing space, an easier option might be 
> determine which clients have the largest indexes and then do multiple 
> "remove oldest cycle"s on the savesets consuming the most space.

I thought of that, but I need those oldest savesets, because those oldest 
savesets that are still browsable are old end-of-month backups, that I 
want to remain browsable. (at EOM, I run a script to change 
browse/retention times to +7 years in the future). The ones I want to get 
rid of are the daily (well, non-EOM) backups that are not EOM, that are 
still around, but are still older than our *usual* 2 month browse period.


> 
> Rick
> 
> On 5/13/2013 9:12 AM, Michael Leone wrote:
> > I have a question. Suppose I have a client that has a default browse/
> > retention policy of 6 months. Now I have decided I only need it to be 
a
> > browse time of 2 months. (the end goal: I need to free up some space 
on
> > the drive where the client indexes are stored)
> >
> > I will change the browse time in the client definition in NMC, and 
that is
> > only for *new* savesets for this client, created from now forward, For
> > existing savesets, I would need to change find all the savesets older 
than
> > 2 months, change the browse date to be a date that is now in the past, 
and
> > then ...  run "nsrim -X" to expire those 4 months of savesets?
> >