| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Nagalingam, Karthikeyan" <KARTHIKEYAN(dot)Nagalingam(at)netapp(dot)com> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: deployment query |
| Date: | 2009-03-17 05:26:23 |
| Message-ID: | dcc563d10903162226h1b301dd7gacada7c7c1eea4d4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-performance |
On Mon, Mar 16, 2009 at 11:15 PM, Nagalingam, Karthikeyan
<KARTHIKEYAN(dot)Nagalingam(at)netapp(dot)com> wrote:
> Thanks Stefan for all your answers. My last question is "What is the
> Mostly used Disaster Recovery Solution for Postgresql in storage
> environment."
We use two methods of backup to keep the database afloat amid things
going horribly wrong. We have 1 or more slony backup dbs that allow
for failover and load balancing. We have offsite pg_dump backups
which are transferred via ssh to an offsite server in case of
catastrophic failure in the data center (like a huge power surge) that
kills both servers.
We routinely restore backup sets or parts of them for various testing scenarios.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-03-17 05:45:41 | Re: deployment query |
| Previous Message | Nagalingam, Karthikeyan | 2009-03-17 05:15:55 | Re: deployment query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-03-17 05:45:41 | Re: deployment query |
| Previous Message | Nagalingam, Karthikeyan | 2009-03-17 05:15:55 | Re: deployment query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-03-17 05:33:12 | Re: Postgres benchmarking with pgbench |
| Previous Message | Nagalingam, Karthikeyan | 2009-03-17 05:15:55 | Re: deployment query |