Обсуждение: error during PITR
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.
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.
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.
View this message in context: Re: error during PITR
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
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] <[hidden email]> wrote:
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 below:http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.htmlTo 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.
MirrorX <mirrorx@gmail.com> writes:
> 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.
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.
>
> On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL] <[hidden email]> wrote:
>
> 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 below:
> 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: postgres.consulting@comcast.net
p: 305.321.1144
you are right. my bad :)
On Thu, Dec 22, 2011 at 3:32 PM, Jerry Sievers <gsievers19@comcast.net> wrote:
MirrorX <mirrorx@gmail.com> writes:It is the *backup file that gets sent to the WAL repository where you
> 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.
will find that information.
backup_label is written during pg_start_backup() and as such, doesn't
know where the ending spot is.> On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL] <[hidden email]> wrote:
> 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/> ????? recovery_target_time = '2011-12-22 07:27:08'
>
> 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'>> LOG:? database system was shut down at 2011-12-22 08:21:11 IST
> when I restart ppas 9.0 server then I got following error: (this is in log file)
>
> 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 below:> To start a new topic under PostgreSQL - admin, email [hidden email]
> http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html> 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: postgres.consulting@comcast.net
p: 305.321.1144
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.
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.
On Thu, Dec 22, 2011 at 9:37 PM, mirrorx <mirrorx@gmail.com> wrote:
you are right. my bad :)On Thu, Dec 22, 2011 at 3:32 PM, Jerry Sievers <gsievers19@comcast.net> wrote:MirrorX <mirrorx@gmail.com> writes:It is the *backup file that gets sent to the WAL repository where you
> 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.
will find that information.
backup_label is written during pg_start_backup() and as such, doesn't
know where the ending spot is.> On Thu, Dec 22, 2011 at 12:11 PM, Karuna Karpe [via PostgreSQL] <[hidden email]> wrote:
> 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/> ????? recovery_target_time = '2011-12-22 07:27:08'
>
> 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'>> LOG:? database system was shut down at 2011-12-22 08:21:11 IST
> when I restart ppas 9.0 server then I got following error: (this is in log file)
>
> 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 below:> To start a new topic under PostgreSQL - admin, email [hidden email]
> http://postgresql.1045698.n5.nabble.com/error-during-PITR-tp5094221p5094221.html> 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: postgres.consulting@comcast.net
p: 305.321.1144
Karuna Karpe <karuna.karpe@os3infotech.com> wrote: > 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