Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 89A639F9BCF for ; Fri, 24 Aug 2007 19:05:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 00655-09 for ; Fri, 24 Aug 2007 19:05:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from smtpb.juniper.net (smtpb.juniper.net [207.17.137.119]) by postgresql.org (Postfix) with ESMTP id 998C79F9B48 for ; Fri, 24 Aug 2007 19:05:24 -0300 (ADT) Received: from unknown (HELO magenta.juniper.net) ([172.17.27.123]) by smtpb.juniper.net with ESMTP/TLS/DES-CBC3-SHA; 24 Aug 2007 15:05:23 -0700 Received: from kenjim-lnx.juniper.net (kenjim-lnx.juniper.net [172.17.58.60]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id l7OM5MS98399; Fri, 24 Aug 2007 15:05:22 -0700 (PDT) (envelope-from kenjim@juniper.net) Received: from kenjim-lnx.juniper.net (kenjim-lnx.juniper.net [127.0.0.1]) by kenjim-lnx.juniper.net (8.13.7/8.13.7) with ESMTP id l7OM5M7e010229; Fri, 24 Aug 2007 18:05:22 -0400 Received: (from kenjim@localhost) by kenjim-lnx.juniper.net (8.13.7/8.13.7/Submit) id l7OM5MJK010228; Fri, 24 Aug 2007 18:05:22 -0400 Date: Fri, 24 Aug 2007 18:05:22 -0400 From: Kenji Morishige To: Mikko Partio Cc: pgsql-admin@postgresql.org, kenjim@juniper.net Subject: Re: Warm-Backup configuration question Message-ID: <20070824220522.GA9696@juniper.net> References: <20070823235452.GE20953@juniper.net> <2ca799770708232118u52498eefv702f950b217c14a5@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2ca799770708232118u52498eefv702f950b217c14a5@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/320 X-Sequence-Number: 26651 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 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