First, I am in doubt whether the deletion of your obviously unimportant backups 
will really free as much index space as you need. But only you can check and 
verify this.

In general I think there are better alternatives to manage index space. 
 - One of course is to extend the disk space.
 - One is to move the index to another location.
 - Another one is to purge the index for certain save sets (nsrmm -dP -S 
<ssid>). The will have the same result as your idea (changing the 
browse/retention dates and run nsrim) but this method is obviously 
easier/faster to use.
 - The forth idea is to review the browse policy in general. 
   I understand that you need to keep the backup for 7 years (retention) but do 
you really need to select a single entity (a file) via the CFI for an instant 
recovery when it is more than 1year old? - Could your customers not accept a 
reasonable longer recovery period for such backups where you rebuild the CFI 
for that save set or where you recover the whole save set to a temp location 
and get the file(s) from here?

Your idea is disturbing the whole principle of NetWorker policies (although it 
is possible). However what you really established so far is more related to 
archiving than to backups.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------