xfs
[Top] [All Lists]

Re: [linux-lvm] PostgreSQL and file system level backup

To: linux-lvm@xxxxxxxxxxx
Subject: Re: [linux-lvm] PostgreSQL and file system level backup
From: Ragnar Kjørstad <lvm@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 16 Nov 2002 03:10:32 +0100
Cc: Postgres Admin List <pgsql-admin@xxxxxxxxxxxxxx>, "Linux-Xfs (E-mail)" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <2D92FEBFD3BE1346A6C397223A8DD3FC09208C@THOR.goeci.com>; from murthy.kambhampaty@goeci.com on Fri, Nov 15, 2002 at 04:25:49PM -0500
References: <2D92FEBFD3BE1346A6C397223A8DD3FC09208C@THOR.goeci.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Fri, Nov 15, 2002 at 04:25:49PM -0500, Murthy Kambhampaty wrote:
> "Unless the postmaster is shut down meanwhile, you'll probably end up with a
> corrupt database.  The problem is that xfsdump does not give you an
> instantaneous snapshot of the filesystem state, so you will probably collect
> inconsistent contents of the various files that make up the database."
> 
> Which gives rise to my present question: given that LVM DOES give an
> instantaneous snapshot of the filesystem, would an xfsdump of an LVM
> snapshot of an XFS filesystem give usable backups?

Yes, it should.

Allthough, some of the postgresql-developers use the term "corrupt
database" of a database where the table-files are inconsistant. That's
generally _always_ the case when the server is running, as the latest
updates are only available in the database-log. That's also the case for
the LVM-snapshot.

This "inconsistancy" will be fixed by log-replay when you start the server
(after restore).

If you want to avoid it, you can:
- shut down databasee
- take snapshot
- start database
- backup from snapshot



There was a long thread on this subject on the postgresql-list a month
or two ago.




-- 
Ragnar Kjørstad
Big Storage


<Prev in Thread] Current Thread [Next in Thread>