Skip site navigation (1) Skip section navigation (2)

Warm-Backup configuration question

From: Kenji Morishige <kenjim(at)juniper(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Cc: kenjim(at)juniper(dot)net
Subject: Warm-Backup configuration question
Date: 2007-08-23 23:54:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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:

if [ -e /export/raid/pgsql/recovery.stop ]; then
  exit 1
if [ -e $1 ]; then
  `/bin/cp $1 $2`
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



pgsql-admin by date

Next:From: Yingqi TangDate: 2007-08-24 00:34:56
Subject: run postgres.exe as a Windows Administrative account
Previous:From: Chander GanesanDate: 2007-08-23 21:59:44
Subject: Re: Logging the starting and stopping of PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group