From: paul rivers <rivers.paul@gmail.com>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: Steve Poe <steve.poe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Planning hot/live backups?
Date: Mon, 24 Mar 2008 14:22:49 -0700
Message-ID: <47E81BA9.303@gmail.com> (raw)
In-Reply-To: <47E8128E.1060600@zeut.net>
References: <721b21dc0803241323u73443060w3a1912d52714549b@mail.gmail.com>
<47E8128E.1060600@zeut.net>
Matthew T. O'Connor wrote:
> Steve Poe wrote:
>> The owners of the animal hospital where I work at want to consider
>> live/hot
>> backups through out the day so we're less likely to lose a whole
>> day of transaction. We use Postgresql 8.0.15. We do 3AM
>> backups, using pg_dumpall, to a file when there is very little activity.
>
>
>
> You probably want to look into PITR, you can have a constant ongoing
> backup of your data and never lose more than a few minutes of data.
> The overhead isn't all the big especially if you are shipping the log
> files to a separate server.
>
>
I'll second that. PITR is IMHO the way to go, and I believe you'll be
pleasantly surprised how easy it is to do. As always, test your backup
strategy by restoring. Even better, make a point of periodically
testing a restore of production backups to a non-production system.
Paul
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-performance@postgresql.org
Cc: rivers.paul@gmail.com, matthew@zeut.net, steve.poe@gmail.com
Subject: Re: Planning hot/live backups?
In-Reply-To: <47E81BA9.303@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