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: Wed, 15 Mar 2006 10:41:23 +0000
Message-ID: <1142419283.3495.12.camel@localhost.localdomain> (raw)
In-Reply-To: <7D2D1D2C-B4C8-4317-A9F9-F1B138E627F1@sitening.com>
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>
<7D2D1D2C-B4C8-4317-A9F9-F1B138E627F1@sitening.com>
On Tue, 2006-03-14 at 16:41 -0600, Thomas F. O'Connell wrote:
> On Mar 4, 2006, at 3:56 AM, Simon Riggs wrote:
>
> > 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.
>
> A few more questions in this thread:
>
> 1. With the wait-for-next-file script scenario, what happens with
> recovery.conf? Does it ever become recovery.done? What happens in the
> event of needing to recover? Does the script need a trigger to say,
> "Okay, stop waiting. We need to use what we have right now."?
Yes.
Everything you need is discussed in the admin archives.
> 2. Are there any salient details when performing an online backup
> from one machine to another? I'm assuming filesystem is an important
> consideration since the recovery process is not like the pg_dump
> recovery process. Any other gotchas?
No
Best Regards, Simon Riggs
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: <1142419283.3495.12.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> <7D2D1D2C-B4C8-4317-A9F9-F1B138E627F1@sitening.com> <1142419283.3495.12.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