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
-
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
