barman + postgresql not start after barman retore
I use the barman for backup and restore
after some restore , we start the postgresql as the following
systemctl start postgresql.service
but postgresql not startup
from the log:
/var/lib/pgsql/backups/data/pg_log
we seen the following errors
LOG: database system was interrupted; last known up at 2017-08-06 07:30:49 UTC
LOG: restored log file "00000008.history" from archive
LOG: starting point-in-time recovery to 2017-08-06 07:30:49.813508+00
LOG: restored log file "0000000800000000000000C1" from archive
LOG: redo starts at 0/C1000080
LOG: recovery stopping before commit of transaction 96139, time 2017-08-06 07:30:49.855629+00
LOG: redo done at 0/C1001B90
FATAL: requested recovery stop point is before consistent recovery point
LOG: startup process (PID 55858) exited with exit code 1
LOG: terminating any other active server processes
please advice what is wrong configuration on BARMAN that cause this ?
postgresql restore linux barman
asked Aug 6 '17 at 8:20
yaelyael
1
bumped to the homepage by Community♦ 23 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I use the barman for backup and restore
after some restore , we start the postgresql as the following
systemctl start postgresql.service
but postgresql not startup
from the log:
/var/lib/pgsql/backups/data/pg_log
we seen the following errors
LOG: database system was interrupted; last known up at 2017-08-06 07:30:49 UTC
LOG: restored log file "00000008.history" from archive
LOG: starting point-in-time recovery to 2017-08-06 07:30:49.813508+00
LOG: restored log file "0000000800000000000000C1" from archive
LOG: redo starts at 0/C1000080
LOG: recovery stopping before commit of transaction 96139, time 2017-08-06 07:30:49.855629+00
LOG: redo done at 0/C1001B90
FATAL: requested recovery stop point is before consistent recovery point
LOG: startup process (PID 55858) exited with exit code 1
LOG: terminating any other active server processes
please advice what is wrong configuration on BARMAN that cause this ?
postgresql restore linux barman
asked Aug 6 '17 at 8:20
yaelyael
1
bumped to the homepage by Community♦ 23 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
It seems your missing some blocks in your WAL file 0000000800000000000000C1. Had you made a copy of your pg_xlog directory BEFORE restoring ?
– Arkhena
Aug 8 '17 at 17:51
add a comment |
I use the barman for backup and restore
after some restore , we start the postgresql as the following
systemctl start postgresql.service
but postgresql not startup
from the log:
/var/lib/pgsql/backups/data/pg_log
we seen the following errors
LOG: database system was interrupted; last known up at 2017-08-06 07:30:49 UTC
LOG: restored log file "00000008.history" from archive
LOG: starting point-in-time recovery to 2017-08-06 07:30:49.813508+00
LOG: restored log file "0000000800000000000000C1" from archive
LOG: redo starts at 0/C1000080
LOG: recovery stopping before commit of transaction 96139, time 2017-08-06 07:30:49.855629+00
LOG: redo done at 0/C1001B90
FATAL: requested recovery stop point is before consistent recovery point
LOG: startup process (PID 55858) exited with exit code 1
LOG: terminating any other active server processes
please advice what is wrong configuration on BARMAN that cause this ?
postgresql restore linux barman
asked Aug 6 '17 at 8:20
yaelyael
1
I use the barman for backup and restore
after some restore , we start the postgresql as the following
systemctl start postgresql.service
but postgresql not startup
from the log:
/var/lib/pgsql/backups/data/pg_log
we seen the following errors
LOG: database system was interrupted; last known up at 2017-08-06 07:30:49 UTC
LOG: restored log file "00000008.history" from archive
LOG: starting point-in-time recovery to 2017-08-06 07:30:49.813508+00
LOG: restored log file "0000000800000000000000C1" from archive
LOG: redo starts at 0/C1000080
LOG: recovery stopping before commit of transaction 96139, time 2017-08-06 07:30:49.855629+00
LOG: redo done at 0/C1001B90
FATAL: requested recovery stop point is before consistent recovery point
LOG: startup process (PID 55858) exited with exit code 1
LOG: terminating any other active server processes
please advice what is wrong configuration on BARMAN that cause this ?
postgresql restore linux barman
postgresql restore linux barman
asked Aug 6 '17 at 8:20
yaelyael
1
asked Aug 6 '17 at 8:20
yaelyael
1
asked Aug 6 '17 at 8:20
yaelyael
1
asked Aug 6 '17 at 8:20
yaelyael
1
asked Aug 6 '17 at 8:20
yaelyael
1
1
bumped to the homepage by Community♦ 23 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 23 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
It seems your missing some blocks in your WAL file 0000000800000000000000C1. Had you made a copy of your pg_xlog directory BEFORE restoring ?
– Arkhena
Aug 8 '17 at 17:51
add a comment |
It seems your missing some blocks in your WAL file 0000000800000000000000C1. Had you made a copy of your pg_xlog directory BEFORE restoring ?
– Arkhena
Aug 8 '17 at 17:51
It seems your missing some blocks in your WAL file 0000000800000000000000C1. Had you made a copy of your pg_xlog directory BEFORE restoring ?
– Arkhena
Aug 8 '17 at 17:51
It seems your missing some blocks in your WAL file 0000000800000000000000C1. Had you made a copy of your pg_xlog directory BEFORE restoring ?
– Arkhena
Aug 8 '17 at 17:51
add a comment |
1 Answer
1
active
oldest
votes
It looks to me like you are trying to restore to a point in time that is earlier than what is recorded in the backups.
Make sure you have not specified a recovery-time that is earlier than the backup you are trying to restore.
Check the files recovery.conf and backup.label in the postgres data directory.
If you want to restore to the latest possible, then you should make sure you don't have a property named recovery_target_time in the recovery.conf.
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f182795%2fbarman-postgresql-not-start-after-barman-retore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It looks to me like you are trying to restore to a point in time that is earlier than what is recorded in the backups.
Make sure you have not specified a recovery-time that is earlier than the backup you are trying to restore.
Check the files recovery.conf and backup.label in the postgres data directory.
If you want to restore to the latest possible, then you should make sure you don't have a property named recovery_target_time in the recovery.conf.
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
add a comment |
It looks to me like you are trying to restore to a point in time that is earlier than what is recorded in the backups.
Make sure you have not specified a recovery-time that is earlier than the backup you are trying to restore.
Check the files recovery.conf and backup.label in the postgres data directory.
If you want to restore to the latest possible, then you should make sure you don't have a property named recovery_target_time in the recovery.conf.
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
add a comment |
It looks to me like you are trying to restore to a point in time that is earlier than what is recorded in the backups.
Make sure you have not specified a recovery-time that is earlier than the backup you are trying to restore.
Check the files recovery.conf and backup.label in the postgres data directory.
If you want to restore to the latest possible, then you should make sure you don't have a property named recovery_target_time in the recovery.conf.
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
It looks to me like you are trying to restore to a point in time that is earlier than what is recorded in the backups.
Make sure you have not specified a recovery-time that is earlier than the backup you are trying to restore.
Check the files recovery.conf and backup.label in the postgres data directory.
If you want to restore to the latest possible, then you should make sure you don't have a property named recovery_target_time in the recovery.conf.
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
answered Aug 6 '17 at 10:24
Jimmy StenkeJimmy Stenke
61335
61335
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f182795%2fbarman-postgresql-not-start-after-barman-retore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It seems your missing some blocks in your WAL file 0000000800000000000000C1. Had you made a copy of your pg_xlog directory BEFORE restoring ?
– Arkhena
Aug 8 '17 at 17:51