pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Restoring DB From A Log?
2+ messages / 2 participants
[nested] [flat]

* Restoring DB From A Log?
@ 2004-03-20 13:12 Al Cohen <amc79@no.junk.please.cornell.edu>
  2004-03-22 16:34 ` Re: Restoring DB From A Log? Andrew Sullivan <ajs@crankycanuck.ca>
  0 siblings, 1 reply; 2+ messages in thread

From: Al Cohen @ 2004-03-20 13:12 UTC (permalink / raw)
  To: pgsql-admin

We've been using PostgreSQL for some time, and it's been very, very 
reliable.  However, we're starting to think about preparing for 
something bad happening - dead drives, fires, locusts, and whatnot.

In our particular situation, being down for two hours or so is OK. 
What's really bad is losing data.

The PostgreSQL replication solutions that we're seeing are very clever, 
but seem to require significant effort to set up and keep going.  Since 
we don't care if a slave DB is ready to kick over at a moment's notice, 
I'm wondering if there is some way to generate data, in real time, that 
would allow an offline rebuild in the event of catastrophe.  We could 
copy this data across the 'net as it's available, so we could be OK even 
if the place burned down.

Is there a log file that does or could do this?  Or some internal system 
table that we could use to generate something?

Thanks!

Al Cohen



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Restoring DB From A Log?
  2004-03-20 13:12 Restoring DB From A Log? Al Cohen <amc79@no.junk.please.cornell.edu>
@ 2004-03-22 16:34 ` Andrew Sullivan <ajs@crankycanuck.ca>
  0 siblings, 0 replies; 2+ messages in thread

From: Andrew Sullivan @ 2004-03-22 16:34 UTC (permalink / raw)
  To: pgsql-admin

On Sat, Mar 20, 2004 at 08:12:02AM -0500, Al Cohen wrote:
> In our particular situation, being down for two hours or so is OK. 
> What's really bad is losing data.
> 
> The PostgreSQL replication solutions that we're seeing are very clever, 
> but seem to require significant effort to set up and keep going.  Since 
> we don't care if a slave DB is ready to kick over at a moment's notice, 
> I'm wondering if there is some way to generate data, in real time, that 
> would allow an offline rebuild in the event of catastrophe.  We could 
> copy this data across the 'net as it's available, so we could be OK even 
> if the place burned down.
> 

Your closest current bet is one of the (admittedly possibly painful
to use) async replication systems available.  Note that _no_ async
system, log shipping, whatever can guarantee zero data loss: if you
lose the active master in a catastrophic explosion which consumes all
your disk, there is the possibility that there will be records which
were committed on that master but which were not committed anywhere
else.  This is even true of PITR approaches which stream the WAL to
some system in another city: you're only as up to date as the last
packet sent, and if a bomb goes off in your cage in your data centre,
you're going to lose something no matter what.

You might like to follow the Slony project, which has as one of its
design goals much easier administration than erserver.  You may also
want to watch the PITR project, which appears to be aiming to get
into 7.5.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2004-03-22 16:34 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-03-20 13:12 Restoring DB From A Log? Al Cohen <amc79@no.junk.please.cornell.edu>
2004-03-22 16:34 ` Andrew Sullivan <ajs@crankycanuck.ca>

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