"Also guessing that running any index maintenance commands have any side 
effects or overheads that could affect future incrementals and restores?"
Just make sure your index backups are working properly.. :)


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Stanley R. Horwitz
Sent: Wednesday, September 05, 2012 8:20 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Managing indexes & disk space?

Paul,

Without knowing how many clients are being backed up in your data zone and what 
your browse period is for those clients, it is impossible to say if 300GB is a 
reasonable size for your server's index directory. The biggest influence on the 
client file index's size is the number of clients being backed up and your 
browse period(s) for them. More clients means a larger client file index. 
Longer browse  period means larger client file index. More individual files on 
a client also speaks to the size of the client file index.

You more than likely need to reduce the browse period for your clients and also 
delete the oldest index entries, at least for your largest clients (by number 
of files, not necessarily the amount of data being backed up), but this reduces 
the number of days you can browse those clients' backups. You can use the 
Console Manager GUI to delete old backup cycles, then let NetWorker invoke 
nsrim to clean up its databases. Be sure that when you do this, you are not 
violating any policies your management has or any legal requirements your 
employer needs to observe with regard to the management of your backups.

This topic is covered in the NetWorker Administration Guide. I suggest you take 
a look at it. 

On 09 5, 2012, at 6:20 AM, Paul Key wrote:

> Hi
> 
> Solaris 10
> NetWorker Management Console version 3.4.Build.187 based on NetWorker 
> version 7.4.Build.187
> 
> I am running short of available disk space on the file system that NSR 
> resides and am looking to manage the index data  - currently at around 
> 300GB (is this a reasonable size for the index directory?) i.e. get 
> back disk space
> 
> I was wondering what index management procedures are used by you good people?
> 
> I have looked at nsrim but was wondering if there is a recommended order of 
> applying index house-keeping commands on a regular basis? And what the best 
> commands to run against the indexes are to reclaim disk space?
> 
> Also guessing that running any index maintenance commands have any side 
> effects or overheads that could affect future incrementals and restores?
> 
> Thanks
> 
> Paul