Re: Corrupt Incrementally Updated Backup: missing pg_clog file

Jeff Janes wrote:
> On Wed, Oct 31, 2012 at 7:24 AM, Jürgen Fuchsberger <juergen.fuchsberger@uni-graz.at> wrote:
> > I have a problem with a corrupt backup, fortunately I was only testing so I
> > did not loose any data. Unfortunetely what I did is to follow the backup
> > guidelines in the documentation, which I thought should work reliably. Here
> > are the details:
> >
> > I am running a postgreSQL 8.4 database on a Debian Squeeze system. For
> > Backups I am using the warm standby and "Incrementally Updated Backup"
> > method as described in chapter 24.4 of the documentation. So my Setup is as
> > follows:
> >
> > Server 1 (Main): PostgreSQL 8.4 Database with archive_mode enabled shipping
> > WAL files to a NFS drive. Size of database is about 370 GB and growing.
> >
> > Server 2 (Replica): PostgreSQL 8.4 Database in recovery mode. Using
> > pg_standby in recovery.conf and getting WAL files from Server 1 NFS drive.
> >
> > All this works fine and runs without errors.
> >
> > The replica is backed up once a week using rsync,
>
> You can not safely backup a running server using rsync, except as
> described in the documentation.
>
> For this purpose, it does not matter that the running server is a warm standby.

I case that was ambiguous:
You cannot take a correct backup of a log shipping standby
server in 8.4.

Yours,
Laurenz Albe