From: Jim C. Nasby <jnasby@pervasive.com>
To: Andy Shellam <andy.shellam@mailnetwork.co.uk>
Cc: 'Thomas F. O'Connell' <tfo@sitening.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PITR as Online Backup Solution
Date: Fri, 3 Mar 2006 21:16:44 -0600
Message-ID: <20060304031644.GM82012@pervasive.com> (raw)
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABOiYOz9rZ9SIlOq0NqO/h8AQAAAAA=@mailnetwork.co.uk>
References: <38B613F1-5A7E-469E-AC5D-B68D24C5A307@sitening.com>
<!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABOiYOz9rZ9SIlOq0NqO/h8AQAAAAA=@mailnetwork.co.uk>
On Fri, Mar 03, 2006 at 10:23:57AM -0000, Andy Shellam wrote:
> Hi Thomas,
>
> I've been trying to get a similar system up and running, and I have to say
> one point in the documentation isn't particularly clear.
>
> It says that you can string together an almost endless supply of WAL logs to
> replay against a database, however you must always start from a base backup
> - ie. You cannot do a recovery on your standby, add a log from your live,
> then re-do the recovery again. You would have to restore your base backup,
> then replay all the logs to include the new one.
>
> A guy called Simon Riggs came up with an idea of having a base backup, then
> creating a script to be called in your recovery_command that reads the WAL
> logs in, but if it cannot find one it needs, it sits and waits and retries
> every so often - every time it finds a new log, that is passed back to the
> PG recovery. Then you would have to find a method of telling the script
> that you wish to bring the database up and it will exit and allow PGSQL to
> come up at the current state with the latest data.
>
> This is a script I am looking to develop myself in the coming months, as I
> would also like a very similar situation to yourself.
Take a look at http://pgfoundry.org/projects/pgpitrha/. It's empty right
now because it was just approved, but Jeff Frost should be adding some
code he currently has sometime this weekend. I'll also be working on
this, hopefully improving on some stuff next week.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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: jnasby@pervasive.com, andy.shellam@mailnetwork.co.uk, tfo@sitening.com
Subject: Re: PITR as Online Backup Solution
In-Reply-To: <20060304031644.GM82012@pervasive.com>
References: <38B613F1-5A7E-469E-AC5D-B68D24C5A307@sitening.com> <!&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABOiYOz9rZ9SIlOq0NqO/h8AQAAAAA=@mailnetwork.co.uk> <20060304031644.GM82012@pervasive.com>
* 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