From: Claudio Duffini <blackhole@sacrocuore.it>
To: pgsql-admin@postgresql.org
Subject: Re: Online Backup and WAL archives
Date: Tue, 1 Feb 2005 16:30:47 +0100
Message-ID: <cto75p$10tk$1@news.hub.org> (raw)
References: <16895.32035.914311.612690@tanto-xipolis.de>
"Morus Walter" <morus.walter@tanto.de> 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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: blackhole@sacrocuore.it
Subject: Re: Online Backup and WAL archives
In-Reply-To: <cto75p$10tk$1@news.hub.org>
References: <16895.32035.914311.612690@tanto-xipolis.de> <cto75p$10tk$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox