| From: | paul rivers <rivers(dot)paul(at)gmail(dot)com> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | Steve Poe <steve(dot)poe(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Planning hot/live backups? |
| Date: | 2008-03-24 21:22:49 |
| Message-ID: | 47E81BA9.303@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-24 22:23:48 | Re: Planning hot/live backups? |
| Previous Message | Matthew T. O'Connor | 2008-03-24 20:43:58 | Re: Planning hot/live backups? |