X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6E61752960 for ; Fri, 1 Apr 2005 00:41:43 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12167-08 for ; Thu, 31 Mar 2005 23:41:34 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by svr1.postgresql.org (Postfix) with ESMTP id 42BCE533D0 for ; Fri, 1 Apr 2005 00:41:33 +0100 (BST) Received: by wproxy.gmail.com with SMTP id 68so801071wri for ; Thu, 31 Mar 2005 15:41:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=prCUEkSvbCSp1vV9twsJR67c5TGv6ubACMbAPFHcBr8lSpyHPzVcsw1EaH5lsQJ9KNT8ziaqbMvrV4+m2rbl0BW6HyQUzHvpzX04owflQdiSLWyTyTYWDN3ONtISLacNgCn5OrJqLtQQ40SMt2s9G62w0hYEezVpPhW6rwHv8Bg= Received: by 10.54.52.27 with SMTP id z27mr136323wrz; Thu, 31 Mar 2005 15:41:32 -0800 (PST) Received: by 10.54.18.43 with HTTP; Thu, 31 Mar 2005 15:41:31 -0800 (PST) Message-ID: <89bc2a0405033115412175ce96@mail.gmail.com> Date: Thu, 31 Mar 2005 18:41:31 -0500 From: Jason DiCioccio Reply-To: Jason DiCioccio To: pgsql-admin@postgresql.org Subject: Online Backups with 8.0 -- Confused Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.398 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/1 X-Sequence-Number: 17014 Greetings, I am having some trouble figuring out exactly what I'm supposed to be doing to successfully recover from an online backup. I am not in a critical situation or anything, simply doing some testing to make sure that my backup system would work. Here's the problem: I do a 'SELECT pg_start_backup('backup1');', it gives me the usual successful result. I then backup (via rsync) the data directory, in this case /usr/local/pgsql/data. This goes fine. I then do a pg_stop_backup(); and backup my archived WAL directory. Here's where the problem seems to occur. Should all of the WAL files necessary for restoration not be in the archive directory after a pg_stop_backup();? It does not appear that this is the case, because if I try to restore a database backed up via the method above, I receive the following errors: cp: /usr/local/pgsql/archive/00000001.history: No such file or directory cp: /usr/local/pgsql/archive/000000010000000000000022: No such file or directory PANIC: WAL ends before end time of backup dump Abort trap (core dumped) Now, realize that ..0022 was not in the archive directory, and actually is still not. However, it seems to be requiring it. Do I have to wait for this log to be archived? Is there a way that I can force the archival of this WAL log? Any help would be greatly appreciated. Thanks! -JD-