X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E894E3B5446 for ; Wed, 15 Dec 2004 23:56:25 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83750-07 for ; Wed, 15 Dec 2004 23:56:21 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id DB8F43B5466 for ; Wed, 15 Dec 2004 23:56:23 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id iBFNuKNP085420 for ; Wed, 15 Dec 2004 23:56:20 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id iBFNVN6K077784 for pgsql-admin@postgresql.org; Wed, 15 Dec 2004 23:31:23 GMT (envelope-from news) From: William Yu X-Newsgroups: pgsql.admin Subject: Re: Tyan Thunder MB for postgres server Date: Wed, 15 Dec 2004 15:29:58 -0800 Organization: Hub.Org Networking Services Lines: 23 Message-ID: References: <021a01c4e0dc$774d0620$7201a8c0@mst1x5r347kymb> <41BDB10A.6000200@did-it.com> <00bf01c4e17c$db69e100$7201a8c0@mst1x5r347kymb> <1103038201.22049.14.camel@state.g2switchworks.com> <000b01c4e24a$43deaae0$7201a8c0@mst1x5r347kymb> <41BFB085.6010102@talisys.com> <004501c4e268$acbadca0$7201a8c0@mst1x5r347kymb> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en In-Reply-To: <004501c4e268$acbadca0$7201a8c0@mst1x5r347kymb> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200412/148 X-Sequence-Number: 15734 Iain wrote: > Upon further investigation, I think this the way to go, specificaly > I'llbe recommending the 320-2 as I plan to put the WAL and DB on > seperate channels and partitions (as opposed to to putting them on the > same logical partition split over the two channels). SOmething to think about. Let's suppose a channel/cable completely dies. How would you protect against it? Split a logical mirror device over 2 channels. Another trick I've started doing with my MegaRAID setups is mirroring in hardware but striping in software. To do 100% hardware RAID-10 MegaRAID cards, all drives must have the same geometry. Not a big deal when you're first configuring a server but a few years down the line when a drive dies and you need a replacement, it can drive you up the wall. I had a set of IBM 36GBs that needed a replacement -- couldn't find any old stock so I decided to get the newest IBM (Hitachi) 36GBs -- NOT THE SAME GEOMETRY!@!@!#!$## After learning that lesson, I did some testing with mirroring. LSI is much less stringent for mirroring. I was able to pair a Seagate + IBM and still get a valid mirror drive. I then use Linux software RAID to stripe 2 mirror volumes together.