From: Scott Marlowe <smarlowe@g2switchworks.com>
To: mcelroy, tim <tim.mcelroy@bostonstock.com>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Re: backups
Date: Wed, 10 May 2006 11:11:53 -0500
Message-ID: <1147277513.9755.35.camel@state.g2switchworks.com> (raw)
In-Reply-To: <0C4841B42F87D51195BD00B0D020F5CB044B2643@MORPHEUS>
References: <0C4841B42F87D51195BD00B0D020F5CB044B2643@MORPHEUS>
On Wed, 2006-05-10 at 10:56, mcelroy, tim wrote:
> Thanks for the quick answer Scott. I thought so but wanted to
> double-check. I was asked by the person who performs our system
> backups if just backing up the directory where I put the nightly
> backups (created with pg_dump) was enough. I also have them backing
> up /var/lib/pgsql and everything under that and they're complaining
> that it's taking too long. I would think we would also want to back
> up the pg_xlog directory though. Or is that overkill? Is there a
> standard in the PG community I should follow? Is just performing the
> pg_dump and saving that to tape enough? I just don't want to get bit
> in the butt if I tell him to not back something up that should be
> backed up.
Generally speaking, backing up with pg_dump is plenty.
The /var/lib/pgsql directory backups aren't necessarily useful since the
files may not be backed up in the same "state" i.e. some transaction
might be in two places at once, partially written, etc... pg_dump
doesn't not have this problem.
If you want something more up to the second, look for point in time
replication in the postgresql docs.
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: smarlowe@g2switchworks.com, tim.mcelroy@bostonstock.com
Subject: Re: backups
In-Reply-To: <1147277513.9755.35.camel@state.g2switchworks.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