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 0EC148B9E5F for ; Tue, 1 Feb 2005 12:59:16 +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 70527-05 for ; Tue, 1 Feb 2005 12:59:09 +0000 (GMT) Received: from mail.tanto.de (mail.tanto.de [213.61.178.43]) by svr1.postgresql.org (Postfix) with ESMTP id 543288B9E22 for ; Tue, 1 Feb 2005 12:59:11 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.tanto.de (Postfix) with ESMTP id 4D17623BC6 for ; Tue, 1 Feb 2005 13:59:38 +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 16985-01 for ; Tue, 1 Feb 2005 13:59:38 +0100 (CET) Received: from tucholsky.office.tanto.de (tucholsky.office.tanto.de [10.0.0.35]) by mail.tanto.de (Postfix) with ESMTP id 2A3F423B8E for ; Tue, 1 Feb 2005 13:59:38 +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 j11CxG72027759 for ; Tue, 1 Feb 2005 13:59:16 +0100 Received: (from morus@localhost) by tucholsky.office.tanto.de (8.12.3/8.12.3/Debian-7.1) id j11CxF2c027755; Tue, 1 Feb 2005 13:59:15 +0100 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16895.32035.914311.612690@tanto-xipolis.de> Date: Tue, 1 Feb 2005 13:59:15 +0100 To: pgsql-admin@postgresql.org Subject: Online Backup and WAL archives X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid 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/5 X-Sequence-Number: 16173 Hi, I'm currently considering to use postgresql 8.0 online backups. The documentation says ' To make use of this backup, you will need to keep around all the WAL segment files generated at or after the starting time of the backup. ' Now I'm wondering how much of these WAL segment files do I really need in order to recover the databases to a consistent state. Let's say I cannot write the WAL segments to tape dynamically when they are archived. Then a complete disk failure would mean, that I loose WAL segments also. Therefore I would like to save a minimum number of WAL segments at or after the online backup that allows recovery. Is that possible? How would I decide how much of the WAL I need? Of course I could recover to the state of database at about the time of the backup only, but it would be a consistent state at least. Or should I use the previous online backup plus all WAL segements up to the current backup? I expect the online backup to faster on recovery than an SQL dump, since the latter would imply recreation of indexes during recovery. Therefore I would prefer to use online backups. Morus