-
Notifications
You must be signed in to change notification settings - Fork 611
Manual database backup error and duplicated backup #3616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey @Eric-zch , sorry you're having trouble. Those backups do seem to be failing because pgBackRest is already in the middle of a backup. This makes sense as you're seeing two backups get created at the same time. So the ultimate question is why are two backups being attempted? When this occurs, do you see multiple backup jobs get created ( I see that you are using the PGO client. What version of the CLI are you using? What happens if you attempt to do a one-off backup as outlined in the following doc? https://access.crunchydata.com/documentation/postgres-operator/v5/tutorial/backup-management/ |
Hi @dsessler7 For our daily scheduled backup, there is no such issue. Yes, I used pgo client, I think it is user friendly compared with the old way of backup. pgo client version
Backup command:
There were 2 jobs (pnst-backup-2p8h,pnst-backup-vbrw) kicked off for the backup.
There were 5 pods started for this backup. 2 successful pods:
Backup Pod messages:
Backup history:
Messages got from Operator pod during the backup time:
|
Hi @dsessler7 Below is my testing for one-off backup based on https://access.crunchydata.com/documentation/postgres-operator/v5/tutorial/backup-management/
There were 2 jobs (pnst-backup-r694,pnst-backup-sgjr) started for the backup.
There were 5 pods started for the backup.
Pod messages
Opereator Pod messages during the backup.
|
Would you please send me the results of the following commands:
and
|
Hi @dsessler7
|
So, you are getting duplicate backups because you have two operators running:
Having multiple operators running can definitely cause weird behavior, so pick one and stick with it. The other thing I asked for was actually the wrong endpoint, but regardless, you're getting errors from the Kubernetes API saying that the annotations field on a couple endpoints are too large:
Could you send the |
Hi @dsessler7
I tested one-off backup.
There is no such problems now. Thanks a lot for your help! |
endpoint_output.txt |
@Eric-zch, glad you got the duplicate backup issue resolved. As far as the large endpoint annotations go, the massive |
@dsessler7
|
Noted. I've created a story in our backlog. |
Overview
I am testing Crunchy Postgres database backup on Openshift, and I found there are 2 results I do not understand.
(1) Multiple backup Pods were started and some Pods failed quickly.
(2) The backup command was executed twice after I issued one backup command.
Environment
Steps to Reproduce
Issue a manual database backup command:
There were 3 backup Pods (pnst-backup-pvl5-dc8gr,pnst-backup-pvl5-gcg9f,pnst-backup-pvl5-z78f8) with error.
The strange thing is: the full backup was excuted twice with 2 Pods (pnst-backup-tmjl-4f4jr, pnst-backup-pvl5-bdxkx)
The same thing happens from incremental backup too.
I did not have such a duplicated database backup problem when I was on pgo 5.2.0
The text was updated successfully, but these errors were encountered: