From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: Desaster Recovery from failover using SLONY-I
Date: Wed, 30 May 2007 11:47:32 -0400
Message-ID: <20070530154732.GG16260@phlogiston.dyndns.org> (raw)
In-Reply-To: <465D58B3.6020408@dsa-ac.de>
References: <465D58B3.6020408@dsa-ac.de>
On Wed, May 30, 2007 at 12:57:55PM +0200, Peter Hausmann wrote:
> Hi,
>
> After a node is dropped due to failover, it takes days to recover the
> database, because it is build up from scratch.
This is from Slony? You know that that's a built-in limitation, and
that the preferred method is switchover, right? Failover should be
the last result. (Also, you'll get better results if you discuss
this on the slony list.)
> We would prefer another approach:
> Make an Online Backup of the Provider database.
> The provider database continues writing new data and the Slony-Logs.
> The Backup is restored to the failed system.
> The slony cluster is dropped from the restored system
> and the system is defined as Slony-subscriber.
> How can we setup this system to recover from the status of the backup time?
Slony knows nothing about the WAL-archiving backup method. When you
subscribe a datbaase, it automatically drops and recreates the target
from scratch. There has been some discussion of how to improve that,
but AFAIK nobody has written the support for it yet.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
A certain description of men are for getting out of debt, yet are
against all taxes for raising money to pay it off.
--Alexander Hamilton
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-admin@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Desaster Recovery from failover using SLONY-I
In-Reply-To: <20070530154732.GG16260@phlogiston.dyndns.org>
* 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