From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Cc: Postgres Admin List <pgsql-admin@postgresql.org>,
"Linux-Xfs (E-mail)" <linux-xfs@oss.sgi.com>
Subject: Re: [linux-lvm] PostgreSQL and file system level backup
Date: Fri Nov 15 20:11:02 2002 [thread overview]
Message-ID: <20021116031032.V17827@vestdata.no> (raw)
In-Reply-To: <2D92FEBFD3BE1346A6C397223A8DD3FC09208C@THOR.goeci.com>; from murthy.kambhampaty@goeci.com on Fri, Nov 15, 2002 at 04:25:49PM -0500
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 parent reply other threads:[~2002-11-15 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 15:26 [linux-lvm] PostgreSQL and file system level backup Murthy Kambhampaty
2002-11-15 18:18 ` Steven Lembark
2002-11-15 20:11 ` Ragnar Kjørstad [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021116031032.V17827@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--cc=linux-lvm@sistina.com \
--cc=linux-xfs@oss.sgi.com \
--cc=pgsql-admin@postgresql.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox