Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 52F9D9FA2DE for ; Thu, 23 Aug 2007 23:15:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 02325-05 for ; Thu, 23 Aug 2007 23:15:38 -0300 (ADT) X-Greylist: delayed 00:21:09.928412 by SQLgrey-1.7.5 Received: from mail.jobflash.com (mail.jobflash.com [67.108.12.41]) by postgresql.org (Postfix) with ESMTP id 737BB9FA471 for ; Thu, 23 Aug 2007 23:15:44 -0300 (ADT) Received: from [192.168.1.76] (adsl-76-202-57-66.dsl.pltn13.sbcglobal.net [76.202.57.66]) by mail.jobflash.com (Postfix) with ESMTP id 294DF42103; Thu, 23 Aug 2007 18:54:33 -0700 (PDT) Message-ID: <46CE3A58.3050407@jobflash.com> Date: Thu, 23 Aug 2007 18:54:32 -0700 From: Tom Arthurs User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Kenji Morishige Cc: pgsql-admin@postgresql.org Subject: Re: Warm-Backup configuration question References: <20070823235452.GE20953@juniper.net> In-Reply-To: <20070823235452.GE20953@juniper.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200708/309 X-Sequence-Number: 26640 You need to make the script wait forever for the next archive file, or return 1 only if you want to complete the recovery. Here's a stub of what we do: #!/usr/bin/ksh set -e # Where copy.sh fetches WALs from ARCHDIR=/data3/archive_log # Name of log file that copy.sh writes to copy_log=copy.log # Name of stop file that copy looks for to signal "go live" copy_stop=copy.stop # How many seconds sleep between copy iterations seconds=15 # Expected size of WAL file size=16777216 src=$1 dest=$2 base=$(basename $src) exec >>$copy_log exec 2>&1 echo $base case $base in *.history) echo "\tignored" exit 1 ;; *.backup) size=+0 ;; esac while :; do if [ -f $copy_stop ]; then echo "\tstop file" rm $copy_stop exit 1 fi if [ -f "$src" ]; then if [ "$(find $src -size ${size}c)" ]; then echo "\tfound" cp $src $dest exit 0 else echo "\ttoo small" fi fi echo "\tsleeping $seconds" sleep $seconds done Kenji Morishige 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. > > Sincerely, > Kenji > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > >