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 3EFDBD1DB51 for ; Sun, 7 Mar 2004 15:32:58 +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 63651-10 for ; Sun, 7 Mar 2004 11:33:00 -0400 (AST) Received: from fep04-mail.bloor.is.net.cable.rogers.com (fep04-mail.bloor.is.net.cable.rogers.com [66.185.86.74]) by svr1.postgresql.org (Postfix) with ESMTP id DC714D1DB0C for ; Sun, 7 Mar 2004 11:32:55 -0400 (AST) Received: from phlogiston.dydns.org ([65.49.121.67]) by fep04-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040307153232.ULRN3598.fep04-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org> for ; Sun, 7 Mar 2004 10:32:32 -0500 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 8F4B23F3A; Sun, 7 Mar 2004 10:32:58 -0500 (EST) Date: Sun, 7 Mar 2004 10:32:58 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: How to do fast, reliable backups? Message-ID: <20040307153258.GB23162@phlogiston.dyndns.org> Mail-Followup-To: pgsql-admin@postgresql.org References: <200403051637.42457.chris@ruprecht.org> <200403061329.17799.silvanadimartino@tin.it> <20040306163059.GC20089@phlogiston.dyndns.org> <200403070836.53742.silvanadimartino@tin.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403070836.53742.silvanadimartino@tin.it> User-Agent: Mutt/1.5.4i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep04-mail.bloor.is.net.cable.rogers.com from [65.49.121.67] using ID at Sun, 7 Mar 2004 10:32:32 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/105 X-Sequence-Number: 12674 On Sun, Mar 07, 2004 at 08:54:07AM +0000, Silvana Di Martino wrote: > > Of course, that's right. Nevertheless, it is hard to imagine anything better > than master-slave replication as a backup/recovery mechanism. For example, > how more data would you loose during a file system copy? This actually depends on how the PITR mechanism is implemented. A common approach is to do filesystem backup followed by log shipping to multiple, redundant destinations. In this scenario, you only lose what isn't in the logs, which in the case of Postgres means you only lose uncommitted transactions. A -- Andrew Sullivan | ajs@crankycanuck.ca This work was visionary and imaginative, and goes to show that visionary and imaginative work need not end up well. --Dennis Ritchie