pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kenji Morishige <kenjim@juniper.net>
To: pgsql-admin@postgresql.org
Cc: kenjim@juniper.net
Subject: Warm-Backup configuration question
Date: Thu, 23 Aug 2007 19:54:52 -0400
Message-ID: <20070823235452.GE20953@juniper.net> (raw)

I've got 2 identical servers configured exactly the same way, except for some
minor differences for the WAL logging directories.  I have both machines set up
as a NFS server and client, so that the WAL archive gets written out to the
local filesystem of the backup machine depending on which role the machine is
currently configured for.  

I've been able to get the backup server syncronized by using the recover.conf
file as described in the documenation, but I can't seem to write a generic shell
script that will keep the warm-backup in a continously syncronizing mode.  It
always stops and renames the recover.conf to recover.done.

I've tried to write an alternate restore command as follows:

#!/usr/local/bin/bash
if [ -e /export/raid/pgsql/recovery.stop ]; then
  exit 1
fi 
if [ -e $1 ]; then
  `/bin/cp $1 $2`
fi
sleep 5
exit 0

The documenation says that it should return 0 only if it is successfull.  My
understanding is that the recovery script should continuously try to copy the
archived data to the WAL directory so that the WARM-BACKUP server can
syncronize.  I'd like to have the WARM-BACKUP always be only a few minutes
behind in syncronization from the PRIMARY without human intervention. I can
write a cronjob to clean out the WAL archive directory accordingly. 

I would be extremely gratefull for any assistance from anyone with a similar
configuration.  I must be confused by how the restore_command is supposed to
work.

Sincerely,
Kenji



view thread (4+ messages)  latest in thread

Message-ID: <20070823235452.GE20953@juniper.net>
Permalink:  ../20070823235452.GE20953@juniper.net/
Also on:    postgresql.org/message-id/20070823235452.GE20953@juniper.net

 · 

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-admin@postgresql.org
  Cc: kenjim@juniper.net
  Subject: Re: Warm-Backup configuration question
  In-Reply-To: <20070823235452.GE20953@juniper.net>

* 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