Hello,
I do not backup indexes via savegrp -O , i am still wondering what i lose 
in terms of recovery etc, indexes normally gets backed up after savegrp 
completes
(& index save is not disabled for the group), is this not enough ??
Thanks



"Landwehr, Jerome" <jlandweh AT HARRIS DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
02/08/2008 11:43 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
"Landwehr, Jerome" <jlandweh AT HARRIS DOT COM>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: [Networker] index cleanup






Not sure if there's a documented 'best practice' but this is what I do to 
cover all my bases

first I record the client ID in case I need to recreate the client 
resource to recover the index so I can make the client ID match what it 
used to be:

                 mminfo -q client=[name] -r client,clientid | sort -u >> 
deleted.index

then I remove the online index:

                 nsrck -Y -R [client]

and the (empty) directory:

                 rmdir /nsr/index/[client]

and finally, remove the client resources via the NW gui

it's very important to do a savegroup -O to back up the index regularly - 
it makes recovery _much_ easier!

HTH
Jerry



-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Christophe Dupre
Sent: Friday, February 08, 2008 11:03 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] index cleanup


Hello,
we are having free space issue in the NSR index directory. We'll be
increasing it shortly, but I need to do some clean up in the meantime.

I have noticed that we still have directories in /nsr/index for servers
that no longer exist and have been removed from the networker
configuration. I am pretty sure that we still have backups that have not
expired for those clients, but I am sure we no longer need to browse
them (and would not be able to as they have been removed from the
configuration).

Can I safely remove the /nsr/index/<oldclient> directory ?  I tried
    # nsrck -R -Y zeus
but it complains that:
nsrck: File index error: `zeus' is not a registered client

I'm guessing that before removing a client configuration, we should
force the removal of its indices. Which brings another question: is
there a Best Current Practice guide to removing Networker client
configuration ?

Any help or pointers greatly appreciated.

-- 
Christophe Dupré
Administrateur Unix et Réseau Sénior
(514) 931-4433 x3078
www.accovia.com 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type 
"signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type 
"signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER