X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D8AC711F60AE for ; Thu, 27 Apr 2006 11:04:37 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 28476-07 for ; Thu, 27 Apr 2006 11:04:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by postgresql.org (Postfix) with ESMTP id A233E11F60A2 for ; Thu, 27 Apr 2006 11:04:25 -0300 (ADT) Received: from osgiliath.mathom.us ([70.108.132.172]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IYD008GGWFBV2K0@vms042.mailsrvcs.net> for pgsql-performance@postgresql.org; Thu, 27 Apr 2006 09:04:24 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by osgiliath.mathom.us (Postfix) with ESMTP id 1170F6E6A8; Thu, 27 Apr 2006 10:04:21 -0400 (EDT) Received: from osgiliath.mathom.us ([127.0.0.1]) by localhost (osgiliath.home.mathom.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16908-03; Thu, 27 Apr 2006 10:04:20 -0400 (EDT) Received: by osgiliath.mathom.us (Postfix, from userid 1000) id CCBE56E945; Thu, 27 Apr 2006 10:04:19 -0400 (EDT) Date: Thu, 27 Apr 2006 10:04:19 -0400 From: Michael Stone Subject: Re: Running on an NFS Mounted Directory In-reply-to: To: Ketema Harris Cc: pgsql-performance@postgresql.org Mail-followup-to: Ketema Harris , pgsql-performance@postgresql.org Message-id: <20060427140417.GH31328@mathom.us> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-disposition: inline X-Pgp-Fingerprint: 53 FF 38 00 E7 DD 0A 9C 84 52 84 C5 EE DF 7C 88 X-Virus-Scanned: Debian amavisd-new at mathom.us References: <20060427132452.GG31328@mathom.us> User-Agent: Mutt/1.5.11+cvs20060403 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/643 X-Sequence-Number: 18727 On Thu, Apr 27, 2006 at 09:41:21AM -0400, Ketema Harris wrote: >>No, backups are completely unrelated to your storage type; you need them >> either way. >Please another post. I meant the storage would do the back ups. Which isn't a backup. Even expensive storage arrays can break or burn down. >>redundancy, expandability >What I mean by these stupid flavor words is: >Redundancy : raid 5. You can get that without external storage. >Expandability : the ability to stick another drive in my array and get more >storage and not have to turn of the db. You can also get that without external storage assuming you choose a platform with a volume manager. >>Do you >> need the ability to do snapshots? >Yes. If that's a hard requirement you'll have to eat the cost & performance problems of an external solution or choose a platform that will let you do that with direct-attach storage. (Something with a volume manager.) >>Do you want to share one big, expensive, reliable unit between >> multiple systems? Will you be doing failover? >Yes, and Yes. Really on one other system, a phone system, but it is the >crux of my business and will be writing a lot of recorded phone calls. I am >working with a storage company now to set up the failover, I want the db and >phone systems to never no if the storage switched over. If you actually have a couple of systems you're trying to fail over, a FC SAN may be a reasonable solution. Depending on your reliability requirement you can have multiple interfaces & FC switches to get redundant paths and a much higher level of storage reliability than you could get with direct attach storage. OTOH, if the DB server itself breaks you're still out of luck. :) You might compare that sort of solution with a solution that has redundant servers and implements the failover in software instead of hardware. Mike Stone