From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Spiegelberg, Greg <gspiegelberg@cranel.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: andy.shellam@mailnetwork.co.uk, Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: FW: Setting up of PITR system.
Date: Tue, 11 Apr 2006 08:14:39 -0400 (EDT)
Message-ID: <200604111214.k3BCEdu06824@candle.pha.pa.us> (raw)
In-Reply-To: <82E74D266CB9B44390D3CCE44A781ED90B6375@POSTOFFICE.cranel.local>
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 <pgman@candle.pha.pa.us> 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. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pgman@candle.pha.pa.us, gspiegelberg@cranel.com, tgl@sss.pgh.pa.us, mallah.rajesh@gmail.com
Subject: Re: FW: Setting up of PITR system.
In-Reply-To: <200604111214.k3BCEdu06824@candle.pha.pa.us>
References: <82E74D266CB9B44390D3CCE44A781ED90B6375@POSTOFFICE.cranel.local> <200604111214.k3BCEdu06824@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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