From: Andrew Sullivan <ajs@commandprompt.com>
To: pgsql-admin@postgresql.org
Subject: Re: Backup and failover process
Date: Wed, 16 Jul 2008 10:15:29 -0400
Message-ID: <20080716141529.GI5261@commandprompt.com> (raw)
In-Reply-To: <B10E6810AC2A2F4EA7550D072CDE87601970FD@SAB-FENWICK.sab.uiuc.edu>
References: <B10E6810AC2A2F4EA7550D072CDE87601970FD@SAB-FENWICK.sab.uiuc.edu>
On Tue, Jul 15, 2008 at 11:08:27AM -0500, Campbell, Lance wrote:
> 1) On the primary server, all WAL files will be written to a backup directory. Once a night I will delete all of the WAL files on the primary server from the backup directory. I will create a full file SQL dump of the database and put it into the same backup folder that the WAL files are put in. The backup directory will be rsynced to the failover server. This will cause the failover server to delete all of the WAL files it has copies of each night.
> 2) On the primary server, I will then check periodically with cron during the day to see if there is a new WAL file. If there is a new WAL file I will then copy it to the fail over server.
> 3) At the end of the day I will repeat step #1.
I think your outline sounds rather fragile. Moreover, I don't
understand why you're planning to delete WAL files from the target
server. It seems to me you'd be better off using pg_standby along
with some helper applications. (Command Prompt has a tool we use for
this, and I believe it's been released, but I'll have to check.)
A
--
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
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-admin@postgresql.org
Cc: ajs@commandprompt.com
Subject: Re: Backup and failover process
In-Reply-To: <20080716141529.GI5261@commandprompt.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