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 5033E8B9B9A for ; Tue, 1 Feb 2005 17:11:54 +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 93888-08 for ; Tue, 1 Feb 2005 17:11:44 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 326168B9CE2 for ; Tue, 1 Feb 2005 17:11:45 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j11HBhgm055540 for ; Tue, 1 Feb 2005 17:11:43 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j11FRsST033722 for pgsql-admin@postgresql.org; Tue, 1 Feb 2005 15:27:54 GMT (envelope-from news) From: "Claudio Duffini" X-Newsgroups: pgsql.admin Subject: Re: Online Backup and WAL archives Date: Tue, 1 Feb 2005 16:30:47 +0100 Organization: Hub.Org Networking Services Lines: 54 Message-ID: References: <16895.32035.914311.612690@tanto-xipolis.de> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200502/8 X-Sequence-Number: 16176 "Morus Walter" ha scritto nel messaggio news:16895.32035.914311.612690@tanto-xipolis.de... > 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. It depends from the date of your "last" base backup. You must keep around all WAL segments since. The only way to keep WAL sets to a minimum is to base-backup frequently, but how much is the size of your DB ? How many transactions your users produce ? > > 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. The command to archive fully used segments is there just for this. We would use it to (keeping simple) rcp segments on another system. > 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? see answer #1 > > 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? Last base backup + WAL segments from that point on = Your Database > > 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. Replaying transactions is surely faster than a complete restore. Regards Claudio Duffini >