From: Scott Marlowe <scott.marlowe@gmail.com>
To: Arnold, Sandra <ArnoldS@osti.gov>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: The OS Command for pg_hotbackup -- Use lvmsnapshot instead of tar cvzf
Date: Tue, 2 Mar 2010 12:54:29 -0700
Message-ID: <dcc563d11003021154h7da61c9dg2aee52cf08da8f3@mail.gmail.com> (raw)
In-Reply-To: <dcc563d11003021120u2cc0ec95ud8802126521e442c@mail.gmail.com>
References: <54E5385D47A89542BC678F5426799F3904961EF60F@OSTIEX01.osti.gov>
<dcc563d11003021120u2cc0ec95ud8802126521e442c@mail.gmail.com>
On Tue, Mar 2, 2010 at 12:20 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> On Tue, Mar 2, 2010 at 8:43 AM, Arnold, Sandra <ArnoldS@osti.gov> wrote:
>> I am currently using the pg_hotbackup Perl script to backup my production
>> PostgreSQL database. However, the next production database is going to be
>> close to a terrabyte in size. We feel that a tar cvzf command is not the
>> correct OS backup solution to use. Instead we would like to use
>> lvmsnapshot. Is anyone using the pg_hotbackup script but instead of the tar
>> cvzf OS command are they using lvmsnapshot?
>>
>> Or, is anyone using lvmsnapshot and doing point-in-time recoveries?
>
> I do not run my databases on LVM because, at least in the past, LVM
> did not properly honor fsync / write barrier commands. I don't know
> if this has since been fixed. If your transaction rate on LVM is
> unnaturally higher than it should / could be, then suspect it is not
> fsyncing, and putting your data on it is putting it at risk.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, ArnoldS@osti.gov, pgsql-general@postgresql.org
Subject: Re: The OS Command for pg_hotbackup -- Use lvmsnapshot instead of tar cvzf
In-Reply-To: <dcc563d11003021154h7da61c9dg2aee52cf08da8f3@mail.gmail.com>
* 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