Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Recommended RAID for Postgres
Date: Mon, 30 Jun 2008 15:15:34 +0200
Message-ID: <46F5921DF52F6E40860287B30CADADC79463C4@EROS.nexus-ag.com>
In-Reply-To: <20080630125231.GB24497@easy2.in-chemnitz.de>
Thread-Topic: [ADMIN] Recommended RAID for Postgres
Thread-Index: AcjasFD0CzeIjyreRESGYTZSyjI/vwAApS9A
References: <46F5921DF52F6E40860287B30CADADC79463A3@EROS.nexus-ag.com>
	<20080630125231.GB24497@easy2.in-chemnitz.de>
From: =?iso-8859-1?Q?Thomas_Br=E4utigam?= <thomas.braeutigam@nexustelecom.com>
To: "Tino Schwarze" <postgresql@tisc.de>,
	<pgsql-admin@postgresql.org>

Hi Tino,

Why avoid RAID5? I though that would be good? Can you explain this?

Writing in the DB, I add about 5-10 GB of data a day. There is a lot of =
writing activity going on in the database every day.
What do you recommend how often I should backup the complete database?

Cheers Thomas


-----Original Message-----
From: pgsql-admin-owner@postgresql.org =
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tino Schwarze
Sent: Montag, 30. Juni 2008 14:53
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Recommended RAID for Postgres

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

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

Thats plenty of data.

> What do you guys recommend on RAID Levels for this Database. Which=20
> does Postgres recommend, and with which do Postgres run very good or=20
> 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=20
> 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=20
> maybe take a couple of days. So what would be a solution to bring up=20
> 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=E4hren erbl=FCht."

www.craniosacralzentrum.de
www.forteego.de

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make =
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin