| From: | Grant <grant(at)conprojan(dot)com(dot)au> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Backup postgresql server. |
| Date: | 2001-04-03 23:38:25 |
| Message-ID: | Pine.LNX.4.21.0104040933570.27656-100000@webster.conprojan.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I did ask a similiar question previously.
There doesn't seem to be any widely used replication systems for
postgresql. As far as I can see.
Here's my plan.
1) Nightly, shutdown the postgresql service until a complete pg_dump is obtained.
2) Move and update a second machine with the data from pg_dump.
3) Restore and make READ ONLY.
4) In the php scripts to connect to the database, have a secondary IP of
the backup machine. If the primary READ/WRITE server is down, all
connections from php to the server will be read only until the main
server can be restored.
Does this sound ok? Or are there live replication services for
postgresql so I can have two servers that are READ/WRITE?
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Lizano | 2001-04-04 06:53:18 | Re: Recommended VACUM timing... |
| Previous Message | Tom Brown | 2001-04-03 21:16:04 | Postmaster hangs until Ctrl-C |