Обсуждение: PGSQL Database Recovery in Portland Oregon Area needed ASAP
I have a client that is running an older version of Lyris List Manager against PostGres 7.1.2, that has crashed their database beyond my ability to recover it. The error that I am getting when we try and restart the database is:
/etc/init.d/postgresql start
Starting postgresql service: postmaster successfully started
DEBUG: database system was interrupted being in recovery at 2006-05-15 14:01:54 PDT
This propably means that some data blocks are corrupted
and you will have to use last backup for recovery.
DEBUG: CheckPoint record at (230, 4199276628)
DEBUG: Redo record at (230, 4199276628); Undo record at (0, 0); Shutdown TRUE
DEBUG: NextTransactionId: 159854941; NextOid: 34688714
DEBUG: database system was not properly shut down; automatic recovery in progress...
DEBUG: redo starts at (230, 4199276692)
[ OK ]
FATAL 2: btree_split_redo: uninitialized next right page
/usr/bin/postmaster: Startup proc 30311 exited with status 512 - abort
I have gone through the stuff on-line concerning this error and attempted to reinitialize the database and restore the night before's backup, but apparently the backups were not quite setup correctly as I cannot get a valid restore either. I am out of my depth on this one and am willing to contract somebody to help get this database back on-line again ASAP, as the client is getting frantic. If you have proven experience doing this sort of recovery, please contact me at the number or email address below. I am not a member of the lists, so please contact me directly. Rates are negotiable, but I will have to clear them with client before we proceed.
markh
====================================================
Mark A. Holm President
InfoArch, Inc. Cell: (503) 750-9741
7456 SW Baseline, PMB#123. Office: (503) 943-3202
Hillsboro, OR 97123 Fax: (503) 591-8584
http://www.infoarch.com <mailto:markh@infoarch.com>
On Tue, May 16, 2006 at 09:53:54AM -0700, Mark Holm wrote: > I have a client that is running an older version of Lyris List > Manager against PostGres 7.1.2, that has crashed their database > beyond my ability to recover it. The error that I am getting when we > try and restart the database is: Very old database, consider upgrading. > I have gone through the stuff on-line concerning this error and > attempted to reinitialize the database and restore the night before's > backup, but apparently the backups were not quite setup correctly as > I cannot get a valid restore either. I am out of my depth on this one > and am willing to contract somebody to help get this database back > on-line again ASAP, as the client is getting frantic. If you have > proven experience doing this sort of recovery, please contact me at > the number or email address below. I am not a member of the lists, so > please contact me directly. Rates are negotiable, but I will have to > clear them with client before we proceed. Make sure you have a physical backup. pg_resetxlog may get you far enough to start the server. Them immediatly dump, destroy the cluster and restore. pg_resetxlog solves some problems, but you can't guarentee your integrity anymore... Have a ncie day, -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.