Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 22E2D9FC016 for ; Thu, 15 Feb 2007 23:10:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 07942-02-9 for ; Thu, 15 Feb 2007 23:10:36 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 3BCAF9FC005 for ; Thu, 15 Feb 2007 23:10:26 -0400 (AST) Received: from perhan.alvh.no-ip.org (216-155-79-222.bk1-dsl.surnet.cl [216.155.79.222]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l1G3AR21012837; Thu, 15 Feb 2007 19:10:28 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id AFA9532A18; Fri, 16 Feb 2007 00:10:21 -0300 (CLST) Date: Fri, 16 Feb 2007 00:10:21 -0300 From: Alvaro Herrera To: pedro noticioso Cc: pgsql-admin@postgresql.org Subject: Re: WAL files backup Message-ID: <20070216031021.GF4682@alvh.no-ip.org> Mail-Followup-To: pedro noticioso , pgsql-admin@postgresql.org References: <20070215190304.40190.qmail@web55411.mail.re4.yahoo.com> <945295.11491.qm@web55414.mail.re4.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <945295.11491.qm@web55414.mail.re4.yahoo.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Thu, 15 Feb 2007 19:10:29 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.222 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200702/229 X-Sequence-Number: 24694 pedro noticioso wrote: > regresamos wal files a pg_xlog - COPY BACKED UP WAL > FILES BACK TO pg_xlog DIRECTORY This step is wrong. You don't have to manually put the pg_xlog files in the pg_xlog directory -- you have to let the recovery_command copy them back from the archive area. Note that recovery.conf does not go into the share/ directory, but in data/. And it must be present _only_ when you want the system to attempt the recovery, not before. Also I didn't see any pg_start_backup() nor pg_stop_backup() calls in your procedure. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.