Mark Steben
Senior Database Administrator
@utoRevenueT
A Dominion Enterprises Company
480 Pleasant Street
Suite B200
Lee, MA 01238
413-243-4800 Home Office
413-243-4809 Corporate Fax
msteben@autorevenue.com
Visit our new website at
www.autorevenue.com
IMPORTANT: The information contained in this e-mail message is confidential
and is intended only for the named addressee(s). If the reader of this
e-mail message is not the intended recipient (or the individual responsible
for the delivery of this e-mail message to the intended recipient), please
be advised that any re-use, dissemination, distribution or copying of this
e-mail message is prohibited. If you have received this e-mail message in
error, please reply to the sender that you have received this e-mail message
in error and then delete it. Thank you.
-----Original Message-----
From: Simon Riggs [mailto:simon@2ndquadrant.com]
Sent: Friday, May 16, 2008 12:30 PM
To: Mark Steben
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] error message in PITR restore:
On Fri, 2008-05-16 at 11:35 -0400, Mark Steben wrote:
> I'm in the process of implementing PITR backups and restores and
> learning as I practice. I restored
>
> Using tar -xzf (backup-name) followed by restarting postgres and
> having the server replay the logs.
>
> I used a recovery_target_time of 1 day prior to current_date
> Postgres seems to come up OK but
>
Did you use pg_start_backup()?
That sequence of events can occur if the backup_label file is missing,
since that won't constrain the stop point from being earlier than it
should be. Is there a backup_label file as part of the tar?
[Mark Steben]
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
[Mark Steben]
You may have hit on the issue. I started a tar, then realized that I did
not do a 'start backup' so I cancelled the tar then issued the
'start_backup' and 'restarted' the tar.
Now when I issue another start-backup I get the 'checkpoint request failed'
error.
There is a 'backup_label_old' file as part of the data cluster but not
A backup_label.
Simon, I think you uncovered the problem but I don't see anyway around it
Short of reloading the db from a pg_dump backup. Any suggestions would
Be appreciated. Thanks,
Mark
