On 06/09/2008, at 5:11 PM, Daniel Pittman wrote:
"Tony Sceats" <[EMAIL PROTECTED]> writes:
On Sat, Sep 6, 2008 at 12:22 PM, Daniel Pittman
<[EMAIL PROTECTED]> wrote:
Kyle <[EMAIL PROTECTED]> writes:
The software I can tune myself. I was more looking for Linux
specific tuning.
* Yes, I was/am concerned about I/O.
* But also ensuring the OS itself (system processes) is not
hindering anything
otherwise.
For a backup system I would also suggest tuning the networking in
addition to what people have added here. I would also suggest only
changing one thing at a time, assessing the impact, and moving on.
There are a lot of guides around on getting the best out of the
network so a google search should yield results.
As a guide:
* If possible, use Gigabit or better for the backup server.
* There may be some benefits in using multiple NIC's (bonded).
* Tune the TCP buffers (wmem and rmem).
* Split NICS across CPU's (processor affinity).
* Don't spend too much time with interrupt coalation unless you have a
lot of time and need *every* bit of network IO.
* If your networking infrastucture can support it use large tcp frames
(>1500 mtu).
* for local backups avoid transiting large backups over firewalls and
routers. 802.1q tagging is really useful here (vlan trunking). Not
always avoidable but can make a considerable difference.
Cheers
Jason.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
