pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kenji Morishige <kenjim@juniper.net>
To: Mikko Partio <mpartio@gmail.com>
Cc: pgsql-admin@postgresql.org
Cc: kenjim@juniper.net
Subject: Re: Warm-Backup configuration question
Date: Fri, 24 Aug 2007 18:05:22 -0400
Message-ID: <20070824220522.GA9696@juniper.net> (raw)
In-Reply-To: <2ca799770708232118u52498eefv702f950b217c14a5@mail.gmail.com>
References: <20070823235452.GE20953@juniper.net>
	<2ca799770708232118u52498eefv702f950b217c14a5@mail.gmail.com>

Hmm. I recently installed 8.2.4 out of ports (FreeBSD) and didn't see that file
in contrib.  I'd like to take a look at it.
Kenji

On Fri, Aug 24, 2007 at 07:18:12AM +0300, Mikko Partio wrote:
> 
> 
> On 8/24/07, Kenji Morishige <kenjim@juniper.net> wrote:
> 
>     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.
> 
> 
> 
> 
> Why don't you just use pg_standby from contrib.
> 
> Regards
> 
> MP



view thread (4+ messages)

Message-ID: <20070824220522.GA9696@juniper.net>
Permalink:  ../20070824220522.GA9696@juniper.net/
Also on:    postgresql.org/message-id/20070824220522.GA9696@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, mpartio@gmail.com
  Subject: Re: Warm-Backup configuration question
  In-Reply-To: <20070824220522.GA9696@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