| From: | Jeni Fifrick <jfifrick(at)incomm(dot)com> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Suggestion on Backup |
| Date: | 2013-10-15 21:09:50 |
| Message-ID: | E59C57F2AE0F8641B5B428292D88479F26D1BB52@ATLPXCH01MB.uss.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
We're having Master & Slave Postgres 9.1.3 on CentOS - using Streaming Replication, which serve as a read-only database, and as 'backup' for the production database.
The current backup mechanism is using pg_dump.
We're in need to do maintenance process that required the server to be taken down.
So, during that time, we only have 1 Production server.
I'm trying to setup a process that can be used to have the continuous backup of the production, to make sure if some problems happen on the production server, we won't loss the data.
Could you experts give me suggestion on the best way to achieve this?
And detail on how to achieve it?
Thanks in advance,
Jen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jov | 2013-10-16 03:41:01 | Re: Suggestion on Backup |
| Previous Message | Christofer C. Bell | 2013-10-11 19:26:50 | Re: uuid extension not available |