Reclaiming CFI disk space

We're running low on disk space for our CFI folder. Ordinarily, I run a
script that finds savesets with retention dates in the future, and I
expire them with

nsrm -y -e <yesterday> -o recycable -S <ssid>/<cloneid>

But the disk space isn't increasing, it's decreasing. Did I miss a step?
The SSIDs show as status ssflags vEF, although they do still show the
retention date to be in the future.

What did I forget to do here, to reclaim disk space on the CFI folder?



--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module

> We're running low on disk space for our CFI folder. Ordinarily, I
> run a script that finds savesets with retention dates in the future,
> and I expire them with
>
> nsrm -y -e <yesterday> -o recycable -S <ssid>/<cloneid>


DUH. I just realized I was running the wrong script. I don't want to
*expire* the savesets; I want to change the *browse* time to be yesterday,
so it removes all those browsable entries taking up the disk space, while
still retaining, so it could be rebuilt by recalling an earlier
CFI/bootstrap tape. Expiring the savesets saves on disk space where the
backup is stored; changing the browse time will remove the index entries,
freeing up space in the index (CFI) folder.

You know, I used to know that ...

I will rerun, doing

nsrm -y -w <yesterday> -o recyclable -S <ssid>

nsrim -X

Let's see if that will help ...


>
> But the disk space isn't increasing, it's decreasing. Did I miss a
> step? The SSIDs show as status ssflags vEF, although they do still
> show the retention date to be in the future.
>
> What did I forget to do here, to reclaim disk space on the CFI folder?

> -- This list is hosted as a public service at Temple University by
> Stan Horwitz If you wish to sign off this list or adjust your
> subscription settings, please do so via http://listserv.temple.edu/
> archives/emc-dataprotection-l.html If you have any questions
> regarding management of this list, please send email to owner-emc-
> dataprotection-l@listserv.temple.edu


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module

Sorry Michael,

but what are you doing after all these years with all your NW experience (and being on the forum)?

- The command "nsrm" does not even exist but you mentioned it twice - "nsrmm" is the obvious command.
- Setting a save set to 'recyclable' (nsrmm -o recyclable -S ssid[/cloneid] ...) is possible but this could lead to the
fact that it will be deleted if it is stored on disk.
- What you want to do is setting a save set to 'recoverable' ... but this is not a valid option for the command
"nsrmm -o <mode> -S <ssid> ..." .
What you can do instead is to purge the save set "nsrmm -d -P -S <ssid> ..." before your run "nsrim".

Try it ... and use "mminfo" to check the save set status before and after the process.
I am really surprised that you have never used this command so far.