Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id E56FA650044
	for <pgsql-admin-postgresql.org@postgresql.org>;
	Mon,  7 Jul 2008 05:28: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 97400-02 for <pgsql-admin-postgresql.org@postgresql.org>;
	Mon,  7 Jul 2008 05:28:28 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from wa-out-1112.google.com (wa-out-1112.google.com
 [209.85.146.181])
	by postgresql.org (Postfix) with ESMTP id AC67C64FFE4
	for <pgsql-admin@postgresql.org>; Mon,  7 Jul 2008 05:28:30 -0300 (ADT)
Received: by wa-out-1112.google.com with SMTP id n4so1322586wag.5
	for <pgsql-admin@postgresql.org>; Mon, 07 Jul 2008 01:28:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=HLKOWfwOdn10bPoyhPxYOrkQU9NqCOao2iPD0wWCt9k=;
	b=IX1f2WG2ndcnq3w8K+85nseb1IM3g/wIvrLHvPMZ8aDecPHcpNLFECHlijS1gVSKmJ
	A18xgGACFB9HIi4tAOt0VVZj3oKPvQCOyyIrplJrm13o6LBvz5uq69EsFNTuRRcrpWZD
	tztiGWrRBPlPHtWHsU/2IzjQUehAyOlUvCMaA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:references;
	b=JvUuJc28RLaRBmiwxdzHyci+2YNR1Uc82hRdKvUf3+L/Y5BqyrHyHp1+7JnGnNHmFw
	uj1+2pXHguupDlQW52T8NuprxRoQL0JoZuIPmwAg1u59o3S6iASG31orRi1hHCTWh5BM
	SwFKtVy2XdHWlUQG1uprPVr7e/n9G0Doql/Zg=
Received: by 10.114.194.1 with SMTP id r1mr5911049waf.205.1215419309291;
	Mon, 07 Jul 2008 01:28:29 -0700 (PDT)
Received: by 10.114.102.2 with HTTP; Mon, 7 Jul 2008 01:28:28 -0700 (PDT)
Message-ID: <2ca799770807070128l2498e9c3pe5d9e469d0dc8269@mail.gmail.com>
Date: Mon, 7 Jul 2008 11:28:28 +0300
From: "Mikko Partio" <mpartio@gmail.com>
To: "=?ISO-8859-1?Q?Thomas_Br=E4utigam?=" <thomas.braeutigam@nexustelecom.com>
Subject: Re: Recommended RAID for Postgres
Cc: pgsql-admin@postgresql.org
In-Reply-To: <46F5921DF52F6E40860287B30CADADC79463A3@EROS.nexus-ag.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_16931_15265229.1215419308694"
References: <46F5921DF52F6E40860287B30CADADC79463A3@EROS.nexus-ag.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200807/75
X-Sequence-Number: 29685

------=_Part_16931_15265229.1215419308694
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Mon, Jun 30, 2008 at 3:30 PM, Thomas Br=E4utigam <
thomas.braeutigam@nexustelecom.com> wrote:

>  Hello all,
>
> I have a pretty huge Postgres DB, about 1,3 to 1,5 Terra. What do you guy=
s
> recommend on RAID Levels for this Database. Which does Postgres recommend=
,
> and with which do Postgres run very good or in the best way?
>

We are running one ~2 TB database, mainly read-only stuff except for at
batch import process every night. We are using RAID5 (RAID10 would require
too many hard disk drives).


> 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 t=
he
> 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 ab=
out
> one day after a crash. This would be the target.
>

I'd say that backup (using filesystem tools) the database once a week or
fortnight and archive wals everyday. That's what we are doing and it's been
working just fine.

Regards

Mikko

------=_Part_16931_15265229.1215419308694
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><br><div class=3D"gmail_quote">On Mon, Jun 30, 2008 at 3:30 PM, Thomas =
Br=E4utigam &lt;<a href=3D"mailto:thomas.braeutigam@nexustelecom.com">thoma=
s.braeutigam@nexustelecom.com</a>&gt; wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt =
0pt 0.8ex; padding-left: 1ex;">




<div>
<div><font size=3D"2" face=3D"Arial"><span>Hello=20
all,</span></font></div>
<div><font size=3D"2" face=3D"Arial"><span></span></font>&nbsp;</div>

<div><font size=3D"2" face=3D"Arial"><span>I have a pretty huge=20
Postgres DB, about 1,3 to 1,5 Terra. What do you guys recommend on RAID Lev=
els=20
for this Database. Which does Postgres recommend, and with which do Postgre=
s run=20
very good or in the best way?</span></font></div></div></blockquote><div><b=
r></div><div>We are running one ~2 TB database, mainly
read-only stuff except for at batch import process every night. We are
using RAID5 (RAID10 would require too many hard disk drives).<br>&nbsp;
<br></div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
 rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><d=
iv></div>
<div><font size=3D"2" face=3D"Arial"><span>What Backup Strategy=20
do you think would be the best. Dump the DB once a week or work with the WA=
L`s?=20
For your info, the data which is feeded to the database is available and co=
uld=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 size=3D"2" face=3D"Arial"><span></span></font></div></div></bloc=
kquote><div><br>I&#39;d say that backup (using filesystem tools) the databa=
se once a week or fortnight and archive wals everyday. That&#39;s what we a=
re doing and it&#39;s been working just fine. <br>
<br>Regards<br><br>Mikko<br></div></div><br>

------=_Part_16931_15265229.1215419308694--