pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Balkrishna Sharma <b_ki@hotmail.com>
To: kevin.grittner@wicourts.gov
To: pgsql-admin@postgresql.org
To: qcor@vp.pl
Subject: Re: db recovery after raid5 failure
Date: Mon, 21 Jun 2010 18:27:54 -0400
Message-ID: <BAY149-w42459AB6E88C4807C2C8D7F0C30@phx.gbl> (raw)


If the database is not extremely huge, makes you wonder what does a RAID actually give us. A robust near-realtime replication setup (say PITR + cloud) may be good enough against once in a few years of disk failure.atleast you don't add another point of failure that you (your database/OS) can't do anything about.

> Date: Mon, 21 Jun 2010 15:30:45 -0500
> From: Kevin.Grittner@wicourts.gov
> To: pgsql-admin@postgresql.org; qcor@vp.pl
> Subject: Re: [ADMIN] db recovery after raid5 failure
> 
> <qcor@vp.pl> 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 very painful.  :-(  (I'm assuming from your post that a second
> drive failed before recovery from failure of the first was
> complete.)
>  
> First a word of advice -- don't discard anything.  Keep any backups,
> keep the bad drives, keep any logs, exports, reports, or anything
> else which might contain fragments of the data.  Make a backup of
> what you have now, if you haven't already.  Keep these things for a
> long time.
>  
> Second, a word of encouragement -- given all these scattered
> fragments and enough time and money, you'd might be surprised at how
> much data can be recovered.  But time and money is required --
> someone has to make the hard call of how much money it is worth to
> recover how much of the data.
>  
> Based on your description, it sounds like you will probably need the
> assistance of an outside company to recover very much.  Possibly one
> company specializing in recovery of data off of damaged disks, and
> another for PostgreSQL internals expertise.
>  
> I don't suppose there's another source for the data to avoid
> attempting this recovery?
>  
> -Kevin
> 
> -- 
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin

 		 	   		  
_________________________________________________________________
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1=

view thread (6+ messages)  latest in thread

Message-ID: <BAY149-w42459AB6E88C4807C2C8D7F0C30@phx.gbl>
Permalink:  ../BAY149-w42459AB6E88C4807C2C8D7F0C30@phx.gbl/
Also on:    postgresql.org/message-id/BAY149-w42459AB6E88C4807C2C8D7F0C30@phx.gbl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: b_ki@hotmail.com, kevin.grittner@wicourts.gov, qcor@vp.pl
  Subject: Re: db recovery after raid5 failure
  In-Reply-To: <BAY149-w42459AB6E88C4807C2C8D7F0C30@phx.gbl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox