I have created a script to run the pg_basebackup utility. The options it uses are:
pg_basebackup -D $BACKUP_DIR/$TIMEINFO -F t -z -Z 9 –x
where $BACKUP_DIR is set to our backup directory and $TIMEINFO is set to TIMEINFO=`date +%Y%m%d_%H%M%S`.
The backup looks ok when I unzip it and untar it. As it is being created, it switches to the next WAL file and the first one is way small.
From: Denish Patel [mailto:denish@xxxxxxxxxx]
Sent: Wednesday, October 23, 2013 3:07 PM
To: Ginepro, Raymond C
Cc: pgsql-admin@xxxxxxxxxxxxxx
Subject: Re: wrong size archive file
Before going into recovery discussion, I would like to learn about how did you take a backup ? Have you followed "Making A Base Backup" procedure documented in http://www.postgresql.org/docs/9.2/static/continuous-archiving.html ?
On Wed, Oct 23, 2013 at 2:56 PM, Ginepro, Raymond C <GineproR@xxxxxxxxx> wrote:
Good afternoon,
I am testing out recovery on 9.2 postgres and I am getting the following message when I try to start up the cluster:
FATAL: archive file "00000001000000000000004C" has wrong size: 305 instead of 16777216
This archive log was active at the start of the backup and is not 16M in size in the original pg_xlog. How do I get around this? Is there a fix for this?
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Denish Patel,
OmniTi Computer Consulting Inc.
Database Architect,
Phone: 240.646.0770 x 232
OmniTi Computer Consulting Inc.
Database Architect,
http://omniti.com/does/data-management
