pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Robert Treat <xzilla@users.sourceforge.net>
To: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: Hot Backup
Date: 24 Oct 2002 10:42:00 -0400
Message-ID: <1035470520.12582.7.camel@camel> (raw)
In-Reply-To: <20021022103442.C4016@mail.libertyrms.com>
References: <3DA323B1.3732.155CAB4F@localhost>
	<1034084444.6801.12.camel@camel>
	<20021022103442.C4016@mail.libertyrms.com>

I think you missed the part of the thread where the nuclear bomb hit the
data center.  hmm... maybe it wasn't a nuclear bomb, but it was getting
there. :-)

BTW - I believe we'll have real PITR in 7.4, about 6 months away. 

Robert Treat

On Tue, 2002-10-22 at 10:34, Andrew Sullivan wrote:
> On Tue, Oct 08, 2002 at 09:40:44AM -0400, Robert Treat wrote:
> 
> > Is it me or do doomsdays scenarios sometimes seem a little silly? I'd
> 
> Not if your contract requires five-nines reliablility and no more
> than 180 minutes of downtime _ever_.  Is five-nines realistic?  For
> most purposes, probably not, according to recent pronouncements (see,
> e.g. <http://www.bcr.com/bcrmag/2002/05/p22.asp;).  But it's in
> lots of contracts anyway.
> 
> > like to ask just where are you storing your "incremental backups" with
> > Oracle/m$ sql ?? If it's on the same drive, then when you drive craps
> 
> The more or less standard way of doing this is to stream the
> PITR-required stuff to another device on another controller -- lots
> of people stream to tape.  People have been doing this for ages,
> partly because disks used to be (a) expensive and (b) unreliable. 
> 






view thread (18+ messages)  latest in thread

Message-ID: <1035470520.12582.7.camel@camel>
Permalink:  ../1035470520.12582.7.camel@camel/
Also on:    postgresql.org/message-id/1035470520.12582.7.camel@camel

 · 

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-hackers@postgresql.org
  Cc: xzilla@users.sourceforge.net, andrew@libertyrms.info, pgsql-general@postgresql.org
  Subject: Re: Hot Backup
  In-Reply-To: <1035470520.12582.7.camel@camel>

* 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