From: Scott Marlowe <scott.marlowe@gmail.com>
To: Nagalingam, Karthikeyan <KARTHIKEYAN.Nagalingam@netapp.com>
Cc: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: pgsql-general@postgresql.org
Subject: Re: deployment query
Date: Mon, 16 Mar 2009 23:26:23 -0600
Message-ID: <dcc563d10903162226h1b301dd7gacada7c7c1eea4d4@mail.gmail.com> (raw)
In-Reply-To: <5FFF8E9361C5D84EBBAF70C1931CDDE303FD90CA@BTCMVEXC1-PRD.hq.netapp.com>
References: <5FFF8E9361C5D84EBBAF70C1931CDDE303D6C954@BTCMVEXC1-PRD.hq.netapp.com>
<49BEB50C.60708@kaltenbrunner.cc>
<5FFF8E9361C5D84EBBAF70C1931CDDE303FD90CA@BTCMVEXC1-PRD.hq.netapp.com>
On Mon, Mar 16, 2009 at 11:15 PM, Nagalingam, Karthikeyan
<KARTHIKEYAN.Nagalingam@netapp.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, KARTHIKEYAN.Nagalingam@netapp.com, stefan@kaltenbrunner.cc, pgsql-general@postgresql.org
Subject: Re: deployment query
In-Reply-To: <dcc563d10903162226h1b301dd7gacada7c7c1eea4d4@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox