From: Bruno Wolff III <bruno@wolff.to>
To: mcelroy, tim <tim.mcelroy@bostonstock.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Re: backups
Date: Wed, 10 May 2006 14:11:38 -0500
Message-ID: <20060510191138.GA4099@wolff.to> (raw)
In-Reply-To: <0C4841B42F87D51195BD00B0D020F5CB044B2643@MORPHEUS>
References: <0C4841B42F87D51195BD00B0D020F5CB044B2643@MORPHEUS>
On Wed, May 10, 2006 at 11:56:20 -0400,
"mcelroy, tim" <tim.mcelroy@bostonstock.com> 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.
You might want to make sure you have the configuration files backed up as well.
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: bruno@wolff.to, tim.mcelroy@bostonstock.com, smarlowe@g2switchworks.com
Subject: Re: backups
In-Reply-To: <20060510191138.GA4099@wolff.to>
* 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