Re: Backup Strategy Second Opinion - Mailing list pgsql-general

From Tim Uckun
Subject Re: Backup Strategy Second Opinion
Date
Msg-id 855e4dcf0902231321h639fe398y29499883f2f65939@mail.gmail.com
Whole thread Raw
In response to Re: Backup Strategy Second Opinion  (Bryan Murphy <bmurphy1976@gmail.com>)
List pgsql-general
If you could publish a brief howto on this I would be most grateful. I bet many others would too.


On Mon, Feb 23, 2009 at 2:56 PM, Bryan Murphy <bmurphy1976@gmail.com> wrote:
On Sun, Feb 22, 2009 at 7:30 PM, Tim Uckun <timuckun@gmail.com> wrote:
>> 1. It's OK if we lose a few seconds (or even minutes) of transactions
>> should one of our primary databases crash.
>> 2. It's unlikely we'll need to load a backup that's more than a few days
>> old.
>
> How do you handle failover and falling back to the primary once it's up?

We don't plan to fail back to the primary.  Amazon is a very different
beast, once a server is dead, we just toss it away.  The secondary
permanently becomes the primary and we create a new tertiary from
scratch which then becomes a log shipped copy of the secondary.

Bryan

pgsql-general by date:

Previous
From: Markus Wanner
Date:
Subject: Re: High cpu usage after many inserts
Next
From: Marek Lewczuk
Date:
Subject: Re: overlaps behaviour - ('2006-03-01'::TimeStamp, '2007-12-01'::TimeStamp) overlaps ('2007-12-01'::TimeStamp, 'Infinity'::TimeStamp)