X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 130A39FA2CB for ; Wed, 10 May 2006 14:00:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 30093-06 for ; Wed, 10 May 2006 14:00:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from morpheus.bostonstock.com (unknown [192.233.205.44]) by postgresql.org (Postfix) with ESMTP id 258CD9FA293 for ; Wed, 10 May 2006 14:00:14 -0300 (ADT) Received: by MORPHEUS with Internet Mail Service (5.5.2653.19) id <2R02CW82>; Wed, 10 May 2006 12:55:03 -0400 Message-ID: <0C4841B42F87D51195BD00B0D020F5CB044B2645@MORPHEUS> From: "mcelroy, tim" To: 'Scott Marlowe' Cc: "'pgsql-admin@postgresql.org'" Subject: Re: backups Date: Wed, 10 May 2006 12:54:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C67452.65F8F996" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/113 X-Sequence-Number: 21645 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C67452.65F8F996 Content-Type: text/plain; charset="iso-8859-1" Great, exactly the answer I was looking for. Thank you again Scott. Tim -----Original Message----- From: Scott Marlowe [mailto:smarlowe@g2switchworks.com] Sent: Wednesday, May 10, 2006 12:12 PM To: mcelroy, tim Cc: 'pgsql-admin@postgresql.org' Subject: RE: [ADMIN] backups 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. ------_=_NextPart_001_01C67452.65F8F996 Content-Type: text/html; charset="iso-8859-1" RE: [ADMIN] backups

Great, exactly the answer I was looking for.  Thank you again Scott.

Tim


 -----Original Message-----
From:   Scott Marlowe [mailto:smarlowe@g2switchworks.com]
Sent:   Wednesday, May 10, 2006 12:12 PM
To:     mcelroy, tim
Cc:     'pgsql-admin@postgresql.org'
Subject:        RE: [ADMIN] backups

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.

------_=_NextPart_001_01C67452.65F8F996--