Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
recovery ended before configured recovery target was reached
General
Escalation
General
Escalation
Description
I'm trying to restore the database from S3:
Restore fails without significant hint why:
The next boostrap process shows infinite loop:
The error is actually hidden on postgresql pvc: cluster1_2022-07-13-21-35-51/pg_log/postgresql-Wed.log contains:
Suggested fix: a) Show full postgresql log boostrap fails b) Describe this situation in documentation and mention recovery steps: kubectl -n pgo delete pgtasks.pg.percona.com cluster1-backrest-restore kubectl -n pgo delete job cluster1-bootstrap kubectl -n pgo delete pvc cluster1
At this step the cluster is ready to apply restore with proper coordinates, because we have specified target restore time after latest restore time in backup repository, we can safely use restore without --type=time or --type=lsn and --target.
I'm trying to restore the database from S3:
Restore fails without significant hint why:
The next boostrap process shows infinite loop:
The error is actually hidden on postgresql pvc:
cluster1_2022-07-13-21-35-51/pg_log/postgresql-Wed.log contains:
Suggested fix:
a) Show full postgresql log boostrap fails
b) Describe this situation in documentation and mention recovery steps:
kubectl -n pgo delete pgtasks.pg.percona.com cluster1-backrest-restore
kubectl -n pgo delete job cluster1-bootstrap
kubectl -n pgo delete pvc cluster1
At this step the cluster is ready to apply restore with proper coordinates, because we have specified target restore time after latest restore time in backup repository, we can safely use restore without --type=time or --type=lsn and --target.