Date: Mon, 30 Jun 2008 14:52:31 +0200
From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Recommended RAID for Postgres
Message-ID: <20080630125231.GB24497@easy2.in-chemnitz.de>
References: <46F5921DF52F6E40860287B30CADADC79463A3@EROS.nexus-ag.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <46F5921DF52F6E40860287B30CADADC79463A3@EROS.nexus-ag.com>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Mon, Jun 30, 2008 at 02:30:23PM +0200, Thomas Bräutigam wrote:

> I have a pretty huge Postgres DB, about 1,3 to 1,5 Terra. 

Thats plenty of data.

> What do you guys recommend on RAID Levels for this Database. Which
> does Postgres recommend, and with which do Postgres run very good or
> in the best way?  

Avoid RAID5. Go for RAID10.

BTW: I wonder how much the used filesystem affects Postgres' performance...

> What Backup Strategy do you think would be the best. Dump the DB once
> a week or work with the WAL`s? For your info, the data which is feeded
> to the database is available and could be feeded again but it would
> maybe take a couple of days. So what would be a solution to bring up
> the huge DB in about one day after a crash. This would be the target.

How much writing activity is on the DB? WALs are probably the way to go.
How often you backup the whole DB space (as a starting point for
replaying WALs) depends on how much changes the DB gets. And how long it
will take to restore the DB space and the WALs afterwards.

HTH,

Tino.

-- 
"What we nourish flourishes." - "Was wir nähren erblüht."

www.craniosacralzentrum.de
www.forteego.de