X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 1EB3611F6292 for ; Tue, 11 Apr 2006 09:14:56 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.112 X-Spam-Level: X-Spam-Status: No, score=0.112 required=5 tests=[AWL=0.112] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id IM0Irw1qmEOD for ; Tue, 11 Apr 2006 09:14:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from candle.pha.pa.us (candle.pha.pa.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id B5DA511F626D for ; Tue, 11 Apr 2006 09:14:48 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id k3BCEdu06824; Tue, 11 Apr 2006 08:14:39 -0400 (EDT) From: Bruce Momjian Message-Id: <200604111214.k3BCEdu06824@candle.pha.pa.us> Subject: Re: FW: Setting up of PITR system. In-Reply-To: <82E74D266CB9B44390D3CCE44A781ED90B6375@POSTOFFICE.cranel.local> To: "Spiegelberg, Greg" Date: Tue, 11 Apr 2006 08:14:39 -0400 (EDT) CC: Tom Lane , andy.shellam@mailnetwork.co.uk, Rajesh Kumar Mallah , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200604/98 X-Sequence-Number: 21267 We already recommend file system snapshots as a backup method in our documentation. --------------------------------------------------------------------------- Spiegelberg, Greg wrote: > You should implement filesystem or volume level snapshots. LVM, Veritas and the like all have the functionality and it gets the database out of "backup" mode quickly. > > http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html > > Before the lvcreate -s command issue the pg_start_backup() and after pg_stop_backup(). Then do what you will with the snapshot volume. Just in case a fsck may be necessary I'd recommend mounting read-only. > > Caveat emptor, I believe certain filesystems take issue with this, like xfs, however we have not seen anything unusual with ext3. Also note that you must have some space unallocated in the proper LVM disk group for the snapshot volume. > > Greg > > ________________________________ > > From: pgsql-admin-owner@postgresql.org on behalf of Tom Lane > Sent: Mon 4/10/2006 7:19 PM > To: Bruce Momjian > Cc: andy.shellam@mailnetwork.co.uk; 'Rajesh Kumar Mallah'; pgsql-admin@postgresql.org > Subject: Re: FW: [ADMIN] Setting up of PITR system. > > > > Bruce Momjian writes: > > Tom Lane wrote: > >> It definitely is a pain in the neck that GNU tar complains about files > >> changing underneath it --- I've looked for a way to disable that, or at > >> least reduce it to a warning instead of an error condition, but gtar > >> doesn't seem to have such a switch. You should try alternative backup > >> tools such as cpio or rsync. > > > You mean the tar exits or that it just returns an error code on > > completion? > > I don't recall whether it finishes making the tarball, but it definitely > returns nonzero exit status, which makes it effectively unusable in any > automated script (you certainly don't want to ignore exit status in a > backup script ...) > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +