From: Dawid Kuroczko <qnex42@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: WAL archiving
Date: Mon, 25 Feb 2008 02:02:17 +0100
Message-ID: <758d5e7f0802241702y48df55dejf0410e87d76fc598@mail.gmail.com> (raw)
In-Reply-To: <758d5e7f0802241701h221ddebbka852adc11f343ba6@mail.gmail.com>
References: <47BE07ED.1070802@internode.com.au>
<758d5e7f0802241701h221ddebbka852adc11f343ba6@mail.gmail.com>
On Fri, Feb 22, 2008 at 12:23 AM, Shilpa Sudhakar
<ssudhakar@internode.com.au> wrote:
> Since the wal logs keep increasing, do we take the base backup every now
> and then so that we can delete the old log files?
> How often do we take a base filesystem backup keeping in mind that our
> systems are 24 x 7.
Depends on your workload and needs.
Say, if you have a policy on having ability to "go back in time" for
at least 30 days, then
you must keep last base backup that was done before 30 days and all
the log files since
then.
But your primary concern should be probably recovery time after
failure (your whole machine
just fried ;)). What you need to do is restore last backup and reply
all archival WAL logs
since then. And assume worst possible situation (the machine fried
just before full backup),
for a weekly backups it means 7 days worth of WAL-log reply.
Now, if your database is DML-heavy recovery won't be very fast, so you
might want to take
base backups more frequently. Or better -- set up a standby server
which will constantly
reply the backups.
Regards,
Dawid Kuroczko
PS: And before setting a policy, do try test recovery and note down
how much time it took.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: qnex42@gmail.com
Subject: Re: WAL archiving
In-Reply-To: <758d5e7f0802241702y48df55dejf0410e87d76fc598@mail.gmail.com>
* 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