pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Thomas F. O'Connell <tfo@sitening.com>
Cc: PGSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: PITR as Online Backup Solution
Date: Sat, 04 Mar 2006 09:56:37 +0000
Message-ID: <1141466197.27729.561.camel@localhost.localdomain> (raw)
In-Reply-To: <94A88F1D-9A65-45D4-B410-21EB2D8B9872@sitening.com>
References: <38B613F1-5A7E-469E-AC5D-B68D24C5A307@sitening.com>
	<1141408492.27729.505.camel@localhost.localdomain>
	<94A88F1D-9A65-45D4-B410-21EB2D8B9872@sitening.com>

On Fri, 2006-03-03 at 12:03 -0600, Thomas F. O'Connell wrote:
> On Mar 3, 2006, at 11:54 AM, Simon Riggs wrote:
> 
> > On Thu, 2006-03-02 at 16:38 -0600, Thomas F. O'Connell wrote:
> >> Ideally, I'd be able to take a base backup of a production system,
> >> copy it to a remote system, which is also the repository for segment
> >> files generated by archive_command, and complete the recovery process
> >> outlined in the docs. From that point, it would make sense to me that
> >> I should be able to continuously replay WAL files against the new
> >> database (possibly as soon as archive_command generates a new one)
> >> without having to purge my data directory. Is that a reasonable
> >> assumption?
> >
> > Yes, it was designed to be able to do this.
> 
>  From the docs, I'm having a hard time determining which steps to  
> edit or omit in order to execute this scenario. Is it possible for  
> you (or anyone else on the list) to present an extension of section  
> 23.3.3 <http://www.postgresql.org/docs/8.1/static/backup- 
> online.html#BACKUP-PITR-RECOVERY> that covered the continuous replay  
> scenario? I'd be happy to help contribute a patch to the docs once I  
> understand the procedure a bit better.

The place the primary backs up to is the place where the secondary
restores from, otherwise all procedures are as documented. Neither
system knows about the other, so its simpler than maybe you think.

The only thing you need is the wait-for-next-file script.

Best Regards, Simon Riggs




view thread (11+ messages)  latest in thread

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

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com, tfo@sitening.com
  Subject: Re: PITR as Online Backup Solution
  In-Reply-To: <1141466197.27729.561.camel@localhost.localdomain>
  References: <38B613F1-5A7E-469E-AC5D-B68D24C5A307@sitening.com> <1141408492.27729.505.camel@localhost.localdomain> <94A88F1D-9A65-45D4-B410-21EB2D8B9872@sitening.com> <1141466197.27729.561.camel@localhost.localdomain>

* 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