[ADMIN] error during PITR

is it possible that the timestamp that you put there ('2011-12-22
07:27:08') is before the time that you issued the command pg_stop_backup?
you can check that by looking at the backup.label file where is says when
the backup was finished.

you can only use point in time recovery after the point when you issued the
pg_stop_backup command and the backup was finished b/c up to that point you
need to recover all the relevant wal archives to bring your database into a
consistent mode. after that point you can stop at any time since the db is
already consistent.

On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL] <

Post by Karuna Karpe
Hello,
I doing PITR using following doc.
http://www.mkyong.com/database/postgresql-point-in-time-recovery-incremental-backup/
But when I am doing recovery till the specific time so I change parameter
in recover.conf file.
i.e. restore_command = 'cp /opt/PostgresPlus/archive/%f %p'
recovery_target_time = '2011-12-22 07:27:08'
when I restart ppas 9.0 server then I got following error: (this is in log
file)
LOG: database system was shut down at 2011-12-22 08:21:11 IST
LOG: starting point-in-time recovery to 2011-12-22 07:27:08+05:30
LOG: restored log file "000000010000000000000014" from archive
LOG: redo starts at 0/14000070
LOG: restored log file "000000010000000000000015" from archive
LOG: restored log file "000000010000000000000016" from archive
LOG: restored log file "000000010000000000000017" from archive
LOG: restored log file "000000010000000000000018" from archive
LOG: restored log file "000000010000000000000019" from archive
LOG: recovery stopping before commit of transaction 756, time 2011-12-22
07:29:08.152325+05:30
LOG: redo done at 0/2423F264
LOG: last completed transaction was at log time 2011-12-22
07:26:51.427245+05:30
FATAL: requested recovery stop point is before consistent recovery point
LOG: startup process (PID 5413) exited with exit code 1
Please let me know what is going wrong in that?
can any one please give me solution for this problem???
Regards,
Karuna Karpe.
------------------------------
If you reply to this email, your message will be added to the discussion
http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html
To start a new topic under PostgreSQL - admin, email
To unsubscribe from PostgreSQL - admin, click here<http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2076596&code=bWlycm9yeEBnbWFpbC5jb218MjA3NjU5NnwtMjExNTQzMjE0Mg==>
.
NAML<http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

--
View this message in context: http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094532.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

Jerry Sievers

2011-12-22 13:32:07 UTC

It is the *backup file that gets sent to the WAL repository where you
will find that information.

backup_label is written during pg_start_backup() and as such, doesn't
know where the ending spot is.

you can only use point in time recovery after the point when you issued the pg_stop_backup command and the backup was
finished b/c up to that point you need to recover all the relevant wal archives to bring your database into a
consistent mode. after that point you can stop at any time since the db is already consistent.
Hello,
?I doing PITR using following doc.
http://www.mkyong.com/database/postgresql-point-in-time-recovery-incremental-backup/
But when I am doing recovery till the specific time so I change parameter in recover.conf file.
i.e. restore_command = 'cp /opt/PostgresPlus/archive/%f %p'
????? recovery_target_time = '2011-12-22 07:27:08'
when I restart ppas 9.0 server then I got following error: (this is in log file)
LOG:? database system was shut down at 2011-12-22 08:21:11 IST
LOG:? starting point-in-time recovery to 2011-12-22 07:27:08+05:30
LOG:? restored log file "000000010000000000000014" from archive
LOG:? redo starts at 0/14000070
LOG:? restored log file "000000010000000000000015" from archive
LOG:? restored log file "000000010000000000000016" from archive
LOG:? restored log file "000000010000000000000017" from archive
LOG:? restored log file "000000010000000000000018" from archive
LOG:? restored log file "000000010000000000000019" from archive
LOG:? recovery stopping before commit of transaction 756, time 2011-12-22 07:29:08.152325+05:30
LOG:? redo done at 0/2423F264
LOG:? last completed transaction was at log time 2011-12-22 07:26:51.427245+05:30
FATAL:? requested recovery stop point is before consistent recovery point
LOG:? startup process (PID 5413) exited with exit code 1
Please let me know what is going wrong in that?
can any one please give me solution for this problem???
Regards,
Karuna Karpe.
------------------------------------------------------------------------------------------------------------------
http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html
To start a new topic under PostgreSQL - admin, email [hidden email]
To unsubscribe from PostgreSQL - admin, click here.
NAML
------------------------------------------
View this message in context: Re: error during PITR
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

--
Jerry Sievers
Postgres DBA/Development Consulting
e: ***@comcast.net
p: 305.321.1144

--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

mirrorx

2011-12-22 16:07:01 UTC

you are right. my bad :)

Post by MirrorX

Post by MirrorX
is it possible that the timestamp that you put there ('2011-12-22

07:27:08') is before the time that you issued the

Post by MirrorX
command pg_stop_backup? you can check that by looking at the

backup.label file where is says when the backup was

Post by MirrorX
finished.

It is the *backup file that gets sent to the WAL repository where you
will find that information.
backup_label is written during pg_start_backup() and as such, doesn't
know where the ending spot is.

Post by MirrorX
you can only use point in time recovery after the point when you issued

the pg_stop_backup command and the backup was

Post by MirrorX
finished b/c up to that point you need to recover all the relevant wal

archives to bring your database into a

Post by MirrorX
consistent mode. after that point you can stop at any time since the db

is already consistent.

Post by MirrorX
On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL] <[hidden
Hello,
?I doing PITR using following doc.

http://www.mkyong.com/database/postgresql-point-in-time-recovery-incremental-backup/

Post by MirrorX
But when I am doing recovery till the specific time so I change

parameter in recover.conf file.

Post by MirrorX
i.e. restore_command = 'cp /opt/PostgresPlus/archive/%f %p'
????? recovery_target_time = '2011-12-22 07:27:08'
when I restart ppas 9.0 server then I got following error: (this is

in log file)

Post by MirrorX
LOG:? database system was shut down at 2011-12-22 08:21:11 IST
LOG:? starting point-in-time recovery to 2011-12-22 07:27:08+05:30
LOG:? restored log file "000000010000000000000014" from archive
LOG:? redo starts at 0/14000070
LOG:? restored log file "000000010000000000000015" from archive
LOG:? restored log file "000000010000000000000016" from archive
LOG:? restored log file "000000010000000000000017" from archive
LOG:? restored log file "000000010000000000000018" from archive
LOG:? restored log file "000000010000000000000019" from archive
LOG:? recovery stopping before commit of transaction 756, time

2011-12-22 07:29:08.152325+05:30

Post by MirrorX
LOG:? redo done at 0/2423F264
LOG:? last completed transaction was at log time 2011-12-22

07:26:51.427245+05:30

Post by MirrorX
FATAL:? requested recovery stop point is before consistent recovery

point

Post by MirrorX
LOG:? startup process (PID 5413) exited with exit code 1
Please let me know what is going wrong in that?
can any one please give me solution for this problem???
Regards,
Karuna Karpe.

------------------------------------------------------------------------------------------------------------------

Post by MirrorX
If you reply to this email, your message will be added to the

http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html

Post by MirrorX
To start a new topic under PostgreSQL - admin, email [hidden email]
To unsubscribe from PostgreSQL - admin, click here.
NAML
------------------------------------------
View this message in context: Re: error during PITR
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

--
Jerry Sievers
Postgres DBA/Development Consulting
p: 305.321.1144

Karuna Karpe

2011-12-23 11:53:41 UTC

I have issue during PITR. this log as follow:

2011-12-23 11:44:18 ISTLOG: database system was shut down at 2011-12-23
11:41:37 IST
2011-12-23 11:44:18 ISTLOG: starting archive recovery
2011-12-23 11:44:18 ISTLOG: restored log file "00000001000000000000000F"
from archive
2011-12-23 11:44:18 ISTLOG: invalid xl_info in primary checkpoint record
2011-12-23 11:44:18 ISTLOG: restored log file "00000001000000000000000E"
from archive
2011-12-23 11:44:18 ISTLOG: using previous checkpoint record at 0/E000070
2011-12-23 11:44:18 ISTLOG: redo starts at 0/E0000C0
2011-12-23 11:44:18 ISTLOG: restored log file "00000001000000000000000F"
from archive
2011-12-23 11:44:18 ISTLOG: record with incorrect prev-link 0/E000094 at
0/F000020
2011-12-23 11:44:18 ISTLOG: redo done at 0/E0000C0
2011-12-23 11:44:18 ISTLOG: restored log file "00000001000000000000000E"
from archive
2011-12-23 11:44:18 ISTFATAL: WAL ends before consistent recovery point
2011-12-23 11:44:18 ISTLOG: startup process (PID 4435) exited with exit
code 1
2011-12-23 11:44:18 ISTLOG: terminating any other active server processes

Can please any one give me solution for that as soon as possible?

Regards,
Karuna Karpe.

Post by mirrorx
you are right. my bad :)

Post by MirrorX

Post by MirrorX
is it possible that the timestamp that you put there ('2011-12-22

07:27:08') is before the time that you issued the

Post by MirrorX
command pg_stop_backup? you can check that by looking at the

backup.label file where is says when the backup was

Post by MirrorX
finished.

It is the *backup file that gets sent to the WAL repository where you
will find that information.
backup_label is written during pg_start_backup() and as such, doesn't
know where the ending spot is.

Post by MirrorX
you can only use point in time recovery after the point when you issued

the pg_stop_backup command and the backup was

Post by MirrorX
finished b/c up to that point you need to recover all the relevant wal

archives to bring your database into a

Post by MirrorX
consistent mode. after that point you can stop at any time since the db

is already consistent.

Post by MirrorX
On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL]
Hello,
?I doing PITR using following doc.

http://www.mkyong.com/database/postgresql-point-in-time-recovery-incremental-backup/

Post by MirrorX
But when I am doing recovery till the specific time so I change

parameter in recover.conf file.

Post by MirrorX
i.e. restore_command = 'cp /opt/PostgresPlus/archive/%f %p'
????? recovery_target_time = '2011-12-22 07:27:08'
when I restart ppas 9.0 server then I got following error: (this is

in log file)

2011-12-22 07:29:08.152325+05:30

Post by MirrorX
LOG:? redo done at 0/2423F264
LOG:? last completed transaction was at log time 2011-12-22

07:26:51.427245+05:30

Post by MirrorX
FATAL:? requested recovery stop point is before consistent recovery

point

------------------------------------------------------------------------------------------------------------------

Post by MirrorX
If you reply to this email, your message will be added to the

http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html

--
Jerry Sievers
Postgres DBA/Development Consulting
p: 305.321.1144

Kevin Grittner

2011-12-23 14:58:55 UTC

Post by Karuna Karpe
2011-12-23 11:44:18 ISTLOG: restored log file
"00000001000000000000000F" from archive
2011-12-23 11:44:18 ISTLOG: record with incorrect prev-link
0/E000094 at 0/F000020
2011-12-23 11:44:18 ISTLOG: redo done at 0/E0000C0
2011-12-23 11:44:18 ISTLOG: restored log file
"00000001000000000000000E" from archive
2011-12-23 11:44:18 ISTFATAL: WAL ends before consistent recovery point
2011-12-23 11:44:18 ISTLOG: startup process (PID 4435) exited
with exit code 1
2011-12-23 11:44:18 ISTLOG: terminating any other active server processes
Can please any one give me solution for that as soon as possible?

It looks like you don't have a good copy of the
00000001000000000000000F WAL file. If you can retrieve a good copy
from somewhere, you should be able to proceed. If not, you should
go to an earlier base backup -- that will let you restore a
consistent version of the database for as far as you have good WAL
files.

You should also review your procedure for copying WAL files. We had
occasional problems like this when we were using samba shares; we've
had none since we copied the files to a directory on the database
server and used rsync to copy them off.

-Kevin

--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Continue reading on narkive:

Search results for '[ADMIN] error during PITR' (Questions and Answers)

Please point me to the right direction. Im lookin for a new faith, a new religion.?

started 2008-10-03 02:10:19 UTC

Hinduism - Will Pitrus accept srardha/Devasam/Padayal done by their sons in memory of them when the same sons?

started 2012-01-07 06:09:58 UTC

Hindu Celebrations - Udaga Santhi - What function or ceremony is this?

started 2012-05-30 03:09:14 UTC

Christians: how do you explain that nobody had a hell concept until Jesus came along?

started 2009-07-13 02:16:59 UTC