zalando / zalando/postgres-operator

Backing up namespaces, resources and PVC's

Open
#2,181 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? K8
  • Are you running Postgres Operator in production? [yes | no] No
  • Type of issue? Question

So, I use Kasten K10's backup solution to backup all resources in a namespace, it includes all resources.
I was confused when I needed to restore my namespace that has PostgreSQL Operator, as patronictl -c postgres.yml history showed events that weren't in the backup...

To be clear, my PostgreSQL Operator, UI and PostgreSQL cluster itself are in the same space.

Naturally, I don't want to backup via the operator, as Kasten K10 will handle the entire process, usually well. However, I was concerned when I found that my restore of PostgreSQL was giving me "WAL value too different from lag" (along those lines), and when I looked at the members they were 100-200MB in lag - Kasten freezes all PVC's when it backups, crash consistent and haven't had trouble with restoring databases with it....

My using Kasten I guarantee all my assets (because PostgreSQL is a dependency on many other applications in the namespace), it all needs to be "snapped" at the same time.

Any ideas how I can get an easier time on turning on the cluster after restoring via Kasten? Why would I see any lag at all? There was no way to start automatically because of this. The only thing I did this time when restoring is listing members, and failingover the node with the lowest lag.......

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is named. Start by reproducing the Kasten K10 restore scenario described here, including the restored PVCs and the patronictl history in postgres.yml, then trace how the operator handles restored PostgreSQL members and WAL lag. Done means the restore behavior and the reason for the reported lag are documented or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.