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 71E8F8B9EEF for ; Thu, 3 Feb 2005 07:44:34 +0000 (GMT) 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 04589-05 for ; Thu, 3 Feb 2005 07:44:26 +0000 (GMT) Received: from mail.tanto.de (mail.tanto.de [213.61.178.43]) by svr1.postgresql.org (Postfix) with ESMTP id E29EE8B9F0A for ; Thu, 3 Feb 2005 07:44:26 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.tanto.de (Postfix) with ESMTP id 93DF023BF1 for ; Thu, 3 Feb 2005 08:44:26 +0100 (CET) Received: from mail.tanto.de ([127.0.0.1]) by localhost (mail.tanto.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26845-06 for ; Thu, 3 Feb 2005 08:44:26 +0100 (CET) Received: from tucholsky.office.tanto.de (tucholsky.office.tanto.de [10.0.0.35]) by mail.tanto.de (Postfix) with ESMTP id 76D2623BF0 for ; Thu, 3 Feb 2005 08:44:26 +0100 (CET) Received: from tucholsky.office.tanto.de (morus@localhost [127.0.0.1]) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id j137iZ72001223 for ; Thu, 3 Feb 2005 08:44:35 +0100 Received: (from morus@localhost) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-7.1) id j137iZUw001219; Thu, 3 Feb 2005 08:44:35 +0100 Resent-From: Morus Walter Resent-Message-ID: <16897.54883.765474.438904@tanto-xipolis.de> Resent-Date: Thu, 3 Feb 2005 08:44:35 +0100 Resent-To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16897.54334.12163.697101@tanto-xipolis.de> In-Reply-To: <42012233.40700@everytruckjob.com> References: <42012233.40700@everytruckjob.com> X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid From: Morus Walter To: Mark Reidenbach Subject: Re: PITR WAL backups Date: Thu, 3 Feb 2005 08:35:26 +0100 X-Virus-Scanned: by amavisd-new at mail.tanto.de Q&A postmaster@tanto.de X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/19 X-Sequence-Number: 16187 Mark Reidenbach writes: > The PITR documentation recommends that a user's archive command should > not overwrite an existing wal archive file, but it appears you need at > least the wal archive file that matches the .backup marker for the > recovery process to succeed. This makes sense because the recovery > process needs to replay what happened during the time it took to make > the backup. The problem I'm having is that you need to backup this wal > file before it's been archived to have a backup which is consistent, but > the documentation also states you need to make sure not to overwrite > existing files in your archive command. > ... > Is any of this correct or am I messing up the procedure entirely? > I'd like to know that as well, see the 'Online Backup and WAL archives' thread. I'm pretty sure that one thing you got wrong, is to say having the WAL named after the .backup is sufficient for restoring the backup. At least that's what I understood from your mail. Depending on the amount of database changes during the backup there may be a number of WALs created during the backup and I doubt that you can miss any of them. The question, how to make sure, to have enough WALs that the backup is usable, is still open to me. The general idea of WAL archiving is to keep all WALs so you can do PITR to any point up to the failure. But even then, it would be useful to know at which time sufficient WALs are saved to make the backup useful. Morus