X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 15E8FD1B967 for ; Sat, 6 Mar 2004 16:31:12 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 79275-06 for ; Sat, 6 Mar 2004 12:31:06 -0400 (AST) Received: from fep02-mail.bloor.is.net.cable.rogers.com (fep02-mail.bloor.is.net.cable.rogers.com [66.185.86.72]) by svr1.postgresql.org (Postfix) with ESMTP id 8EBEED1D44F for ; Sat, 6 Mar 2004 12:31:03 -0400 (AST) Received: from phlogiston.dydns.org ([65.49.121.67]) by fep02-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040306163023.NLFX434741.fep02-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org> for ; Sat, 6 Mar 2004 11:30:23 -0500 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id B7D2B3F40; Sat, 6 Mar 2004 11:30:59 -0500 (EST) Date: Sat, 6 Mar 2004 11:30:59 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: How to do fast, reliable backups? Message-ID: <20040306163059.GC20089@phlogiston.dyndns.org> Mail-Followup-To: pgsql-admin@postgresql.org References: <200403051637.42457.chris@ruprecht.org> <200403061329.17799.silvanadimartino@tin.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403061329.17799.silvanadimartino@tin.it> User-Agent: Mutt/1.5.4i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep02-mail.bloor.is.net.cable.rogers.com from [65.49.121.67] using ID at Sat, 6 Mar 2004 11:30:21 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/95 X-Sequence-Number: 12664 On Sat, Mar 06, 2004 at 01:39:28PM +0000, Silvana Di Martino wrote: > a slave replica of your main database server. Should you have any problem > with the main server, just switch the IP addresses of the master and slave > servers and you are up and running again. The switching takes a few > milliseconds and can even be performed automatically by a few specific > programs (look for "fault-tolerant linux systems" with google). While your And what do you do about the records which made it to the master database but which haven't been applied on the slave yet? Asynchronous replication with automatic failover is _dangerous_, because you can strand records. Many commercial systems do this with what they describe as conflict-management; in truth, this usually amounts to marking _both_ records as suspect and letting the DBA decide what to do. I'm not saying that master-slave systems are a bad idea, but you'd better be aware of what you're exposing yourself to before considering such hot-failover cases. A -- Andrew Sullivan | ajs@crankycanuck.ca