Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 8323F9F96A8 for ; Wed, 10 Oct 2007 13:50:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 47564-07 for ; Wed, 10 Oct 2007 13:50:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id C72A09FB362 for ; Wed, 10 Oct 2007 13:50:03 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l9AGnxt07289; Wed, 10 Oct 2007 12:49:59 -0400 (EDT) From: Bruce Momjian Message-Id: <200710101649.l9AGnxt07289@momjian.us> Subject: Re: Using rsync for base backups for PITR In-Reply-To: <20071010164227.7D89F3F2710@mail.int.journyx.com> To: Scott Whitney Date: Wed, 10 Oct 2007 12:49:59 -0400 (EDT) CC: pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/80 X-Sequence-Number: 26994 Scott Whitney wrote: > In the same way that you don't have a valid archive while the tar is > running, no? In either case, I have to archive the WAL segments used during > the file system backup, right? Well, with the tar I assume you still have the old tar around. This is not true with the rsync update you suggested. > Is rsync a supported method for a warm standby server? Specifically, I'm > thinking about: > http://www.taygeta.com/ha-postgresql.html Well, the standby is fine while the rsync is not runing, but while syncing that backup has an inconsistent view of the database. PITR works only because the PITR logs fix up any consistencies. The rsync is not the same as a file system snapshot. -- Bruce Momjian http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +