Balkrishna Sharma wrote:
>> average about two drive failures a month
> You must be having a real huge postgres setup with several hundreds
> of drives to have such high frequency of failure.
About 100 database servers with over 1000 drives spinning 24/7. Also
probably significant, managemen
.@wicourts.gov
> To: b...@hotmail.com; pgsql-admin@postgresql.org; q...@vp.pl
> Subject: Re: [ADMIN] db recovery after raid5 failure
>
> Balkrishna Sharma wrote:
>
> > If the database is not extremely huge, makes you wonder what does
> > a RAID actually give us.
>
Balkrishna Sharma wrote:
> If the database is not extremely huge, makes you wonder what does
> a RAID actually give us.
Well, RAID5 gives you a situations where you must have a second
drive fail before recovery for the first failure is complete, versus
being instantly dead on a single-drive fa
can't do
anything about.
> Date: Mon, 21 Jun 2010 15:30:45 -0500
> From: kevin.gritt...@wicourts.gov
> To: pgsql-admin@postgresql.org; q...@vp.pl
> Subject: Re: [ADMIN] db recovery after raid5 failure
>
> wrote:
>
> > I have serious problems recovering our db
wrote:
> I have serious problems recovering our db after recent raid5
> failure. Long story short - no recent dumps, some missing files
> (like pg_control).
Been there -- at least on the end of helping with recovery for
people in that position with a different database product. It can
be ver
Hello
I have serious problems recovering our db after recent raid5 failure.
Long story short - no recent dumps, some missing files (like pg_control).
long version of the story:
our raid failed.. badly. I was able to recover most of the files but some
(like pg_control) are missing (possibly more,
