pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Desaster Recovery from failover using SLONY-I 2+ messages / 2 participants [nested] [flat]
* Desaster Recovery from failover using SLONY-I @ 2007-05-30 10:57 Peter Hausmann <peter.hausmann@dsa-ac.de> 0 siblings, 1 reply; 2+ messages in thread From: Peter Hausmann @ 2007-05-30 10:57 UTC (permalink / raw) To: pgsql-admin Hi, After a node is dropped due to failover, it takes days to recover the database, because it is build up from scratch. 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? Thank you for any hint. -- Mit freundlichen Gruessen / With best regards Dipl.-Inform. Peter Hausmann DSA Daten- und Systemtechnik GmbH Pascalstrasse 28 D-52076 Aachen Germany Phone: +49 (0) 2408 / 9492- 779 Fax: +49 (0) 2408 / 9492- 92 ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Desaster Recovery from failover using SLONY-I @ 2007-05-30 15:47 Andrew Sullivan <ajs@crankycanuck.ca> parent: Peter Hausmann <peter.hausmann@dsa-ac.de> 0 siblings, 0 replies; 2+ messages in thread From: Andrew Sullivan @ 2007-05-30 15:47 UTC (permalink / raw) To: pgsql-admin 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2007-05-30 15:47 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2007-05-30 10:57 Desaster Recovery from failover using SLONY-I Peter Hausmann <peter.hausmann@dsa-ac.de> 2007-05-30 15:47 ` Andrew Sullivan <ajs@crankycanuck.ca>
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