From: Matthew Schumacher <matt.s@aptalaska.net>
To: pgsql-performance@postgresql.org
Subject: Re: SAN vs Internal Disks
Date: Fri, 07 Sep 2007 09:21:10 -0800
Message-ID: <46E18886.7060502@aptalaska.net> (raw)
In-Reply-To: <20070907103341.GC20896@oppetid.no>
References: <a199704d0709060535q6fea139aq2e3863e685555b0d@mail.gmail.com>
<dcc563d10709060925o6f11f632sbfbc2b64530ae80d@mail.gmail.com>
<a199704d0709061003u71d536fbh9d71ed095dfe16b@mail.gmail.com>
<Pine.GSO.4.64.0709062354040.28915@westnet.com>
<20070907100446.GE1795@mathom.us>
<20070907103341.GC20896@oppetid.no>
I'm getting a san together to consolidate my disk space usage for my
servers. It's iscsi based and I'll be pxe booting my servers from it.
The idea is to keep spares on hand for one system (the san) and not have
to worry about spares for each specific storage system on each server.
This also makes growing filesystems and such pretty simple. Redundancy
is also good since I'll have two iscsi switches plugged into two cisco
ethernet switches and two different raid controllers on the jbod. I'll
start plugging my servers into each switch for further redundancy. In
the end I could loose disks, ethernet switches, cables, iscsi switches,
raid controller, whatever, and it keeps on moving.
That said, I'm not putting my postgres data on the san. The DB server
will boot from the san and use it for is OS, but there are 6 15k SAS
disks in it setup with raid-10 that will be used for the postgres data
mount. The machine is a dell 2950 and uses an LSI raid card.
The end result is a balance of cost, performance, and reliability. I'm
using iscsi for the cost, reliability, and ease of use, but where I need
performance I'm sticking to local disks.
schu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matt.s@aptalaska.net
Subject: Re: SAN vs Internal Disks
In-Reply-To: <46E18886.7060502@aptalaska.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox