Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 58D729FA200 for ; Wed, 30 May 2007 12:47:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 44060-03 for ; Wed, 30 May 2007 12:47:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id E52C09FA1B8 for ; Wed, 30 May 2007 12:47:38 -0300 (ADT) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=phlogiston.dydns.org) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1HtQOg-0003OL-5s for pgsql-admin@postgresql.org; Wed, 30 May 2007 11:47:38 -0400 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id B6FA5404E; Wed, 30 May 2007 11:47:32 -0400 (EDT) Date: Wed, 30 May 2007 11:47:32 -0400 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: Desaster Recovery from failover using SLONY-I Message-ID: <20070530154732.GG16260@phlogiston.dyndns.org> References: <465D58B3.6020408@dsa-ac.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <465D58B3.6020408@dsa-ac.de> User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/315 X-Sequence-Number: 25635 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