Re: Incremental Backups in postgres - Mailing list pgsql-general

From akp geek
Subject Re: Incremental Backups in postgres
Date
Msg-id 2024a9fb0911110951v4398f82cq60602ef46ed04067@mail.gmail.com
Whole thread Raw
In response to Re: Incremental Backups in postgres  (Alan Hodgson <ahodgson@simkin.ca>)
Responses Re: Incremental Backups in postgres  (Scott Mead <scott.lists@enterprisedb.com>)
List pgsql-general
Hi All -
                  I have read the document got a reasonable
understanding of the WAL process. I have some confusion regarding the
process.

1. I have set up the archiving process. Now the archive file are going
to a different mount point.
2. I set up job to create a back up of the PGDATA directory

Are the 2 above steps enough for recovery. My confusion is why we need
to have  Making a Base Backup. When you have time can you please
clarify?


Regards

On Tue, Nov 10, 2009 at 4:56 PM, Alan Hodgson <ahodgson@simkin.ca> wrote:
>
> On Tuesday 10 November 2009, akp geek <akpgeek@gmail.com> wrote:
> > So Is it always good to have the backup using PG_dump instead of PITR or
> > a combination of both
> >
>
> I like to do both. Ongoing PITR, daily base backups (by updating an rsync
> copy), and weekly pg_dumps that in turn go to tape.
>
> PITR gives a very recent restore point in the event of server loss. As
> previously mentioned, the full (custom) backups let you restore individual
> tables. They're also a lot smaller than base backups + WAL logs.
>
> --
> "No animals were harmed in the recording of this episode. We tried but that
> damn monkey was just too fast."
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Postgres Clustering Options
Next
From: John R Pierce
Date:
Subject: Re: Postgres Clustering Options