We use 4 x 100GB filesystems and when setting up a client we use the
index path field in the client record to point at whichever filesystem
is least full... To set this up I wrote some scripts to move all the
indexes using rsync and some nsradmin scripts to update the client
records... I maintain a 10GB /nsr/index filesystem also for people to
restore indexes of deleted clients and to catch anyone who doesn't
follow the procedures properly - and theres a script to monitor that and
tell me when things are getting out of balance...
The benefits are clear, although it's a bit of bother doing all this, we
have not run out of disk space on a weekend since we deployed the
scheme, and if we were to run out - only a quarter of the clients would
be impacted - and there is zero risk of causing a media db corruption
because it's on a separate filesystem to the indexes.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT listserv.temple DOT edu] On
Behalf Of Teresa Biehler
Sent: Thursday, 28 September 2006 10:58 PM
To: NETWORKER AT listserv.temple DOT edu
Subject: [Networker] large /nsr/index directories
As we've added more and more clients, our /nsr/index directory has
gotten large (200 GB). We need to create more space for the client
index directories and are weighing the pros and cons of expanding
/nsr/index vs creating a new file system and moving some of our clients
to that alternate location.
For those of you with large environments, how do you manage space for
/nsr/index? Do you use a single file system (i.e. all the client index
files into /nsr/index)? If so, have you had problems with reboots
causing long outages while that file system is checked (assuming you are
using ufs)? Do you move some client index directories to alternate
locations and use the "client index path" field in the client
definition? If so, do you find this difficult to manage? Have you
needed to create any special processes to handle this?
Thanks.
Teresa
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 wit 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
NOTICE
This e-mail and any attachments are confidential and may contain copyright
material of Macquarie Bank or third parties. If you are not the intended
recipient of this email you should not read, print, re-transmit, store or act
in reliance on this e-mail or any attachments, and should destroy all copies of
them. Macquarie Bank does not guarantee the integrity of any emails or any
attached files. The views or opinions expressed are the author's own and may
not reflect the views or opinions of Macquarie Bank.
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
wit 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
|
