I'll take a stab at this one. At work our MySQL database contains product info and indexing data. The reasoning for designing and taking this outside of the business application is the business app. doesn't do web communication well (limited functionality and at times spotty app reliability). The business app doesn't matter (and I bet no one has heard of it anyway). Our design spec was hearty at a HP DL 385 with dual AMD CPUs (dual core I think) 5GB of RAM and around 7 internal 15k drives in RAID 5. Every bit of hardware is HP/Compaq. Without starting a distro thread we picked Red Hat AS V4. This combo has served us well and I am sure *many* other distros would do this at least as well. For us our biggest corporate reason for R.H. was most of our application vendors suported R.H in one way or another (a vote for getting good at only one skillset/distro). During application & DB development we considered uptime and ordered a second identical box mainly for a total server failure of any sort. They run very well as MySQL master and slave. In the year it has been up we are very happy with this combination. Feel free to forward any specific questions (direct or via the group). Hope this helps, Joel ============================= Date: Tue, 24 Apr 2007 14:59:55 -0400 From: "John Westcott, IV" <John.Westcott@tufts.edu> Subject: [Wlug] MySQL Server Hardware To: wlug@mail.wlug.org Message-ID: <20070424145955.3hftuclhdwg0ck4s@webmail.tufts.edu> Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Howdy All, I work in a place that has traditionally used Sun Sparc hardware running Solaris to host a production MySQL environment. We are going to be replacing our database servers this year and I am trying to determine if I want to maintain the norm or if I want to try to change. I am interested to see what other people use for hardware/OS for a production MySQL installation that requires a high amount of uptime. Thanks in advance for any replies. -John Westcott