I inherited a website project using Postgres on linux and am now
working on a backup plan for the site.
I figure I can write a cron script to do a pg_dump every so often
(hourly? daily?). The site gets backed up to tape every day. Pretty
scrawny plan, eh?
Then, let's say the site gets hacked or the database crashes and it
needs to be restored. I know I can reverse the dump to get back where
it was when pg_dump was run, but what about the transactions after the
pg_dump? Do people have any strategies for backup that won't cause
those to be lost? It's a membership database with credit card
transactions, if that makes a difference.
The PostgreSQL User's Guide says, "This section needs to be written.
Volunteers?" for Chapter 13, "Database Recovery". Has anybody taken a
cut at it yet?
Thanks,
Rich Ackerman
richmond@shadow.net
