Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 28F98650F08
	for <pgsql-admin-postgresql.org@postgresql.org>;
	Mon, 30 Jun 2008 09:43:34 -0300 (ADT)
Received: from postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 05099-06-5 for
	<pgsql-admin-postgresql.org@postgresql.org>;
	Mon, 30 Jun 2008 09:43:22 -0300 (ADT)
X-Greylist: delayed 00:10:38.621614 by SQLgrey-1.7.6
Received: from typhon.nexustelecom.com (typhon.nexustelecom.com
	[212.203.104.229])
	by postgresql.org (Postfix) with ESMTP id 27B49650EB8
	for <pgsql-admin@postgresql.org>; Mon, 30 Jun 2008 09:41:12 -0300 (ADT)
X-IronPort-AV: E=Sophos;i="4.27,727,1204498800"; d="scan'208,217";a="214598"
Received: from unknown (HELO hermes.nexustelecom.com) ([172.29.1.4])
	by typhon.nexustelecom.com with ESMTP; 30 Jun 2008 14:30:31 +0200
Received: from hermes.nexustelecom.com (localhost [127.0.0.1])
	by hermes.nexustelecom.com (Postfix) with ESMTP id 4155D159F64
	for <pgsql-admin@postgresql.org>; Mon, 30 Jun 2008 14:30:31 +0200 (CEST)
Received: from EROS.nexus-ag.com (eros.nexus-ag.com [172.29.2.99])
	by hermes.nexustelecom.com (Postfix) with ESMTP id 1B5F8159F63
	for <pgsql-admin@postgresql.org>; Mon, 30 Jun 2008 14:30:24 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8DAAD.11A4731E"
Subject: Recommended RAID for Postgres
Date: Mon, 30 Jun 2008 14:30:23 +0200
Message-ID: <46F5921DF52F6E40860287B30CADADC79463A3@EROS.nexus-ag.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Recommended RAID for Postgres
Thread-Index: AcjarRFSiJvcBgVCSFu64Pbziy9G9g==
From: =?iso-8859-1?Q?Thomas_Br=E4utigam?= <thomas.braeutigam@nexustelecom.com>
To: <pgsql-admin@postgresql.org>
X-TBoneOriginalFrom: =?iso-8859-1?Q?Thomas_Br=E4utigam?=
	<thomas.braeutigam@nexustelecom.com>
X-TBoneOriginalTo: <pgsql-admin@postgresql.org>
X-TBoneDomainSigned: false
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.182 tagged_above=0 required=5 tests=AWL=0.181,
	HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200806/242
X-Sequence-Number: 29580

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8DAAD.11A4731E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello all,
=20
I have a pretty huge Postgres DB, about 1,3 to 1,5 Terra. 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?
=20
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.
=20
Thanks for a feedback and Cheers Thomas

------_=_NextPart_001_01C8DAAD.11A4731E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D524382612-30062008>Hello=20
all,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D524382612-30062008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D524382612-30062008>I have =
a pretty huge=20
Postgres DB, about 1,3 to 1,5 Terra. What do you guys recommend on RAID =
Levels=20
for this Database. Which does Postgres recommend, and with which do =
Postgres run=20
very good or in the best way?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D524382612-30062008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D524382612-30062008>What =
Backup Strategy=20
do you think would be the best. Dump the DB once a week or work with the =
WAL`s?=20
For your info, the data which is feeded to the database is available and =
could=20
be feeded again but it would maybe take a couple of days. So what would =
be a=20
solution to bring up the huge DB in about one day after a crash. This =
would be=20
the target.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D524382612-30062008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D524382612-30062008>Thanks =
for a=20
feedback and Cheers Thomas</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C8DAAD.11A4731E--