pgBackRest as backup option for Postgres
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
It allows PITR for Postgres which is crucial for time-sensitive data.
Describe the solution you'd like
Under backups, the option to choose pgBackRest which handles backups and restores automatically.
Also restores should gracefully stop the postgres container, mount a temporary container to the volume, restore the backup and start the postgres container again. (Postgres does need to be stopped for the restore).
Also delta restores are a great option instead of wiping the complete directory and replacing it with the one from the backup.
Describe alternatives you've considered
Running it myself. But would make a lot of sense in Dokploy.
Running minute backups, but does add lots of storage to S3.
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or existing entry points. Start by tracing the current backup and Postgres restore flows, then define how a pgBackRest option would provide PITR, stop and restart the Postgres container, use a temporary container, and support delta restores; done means these restore behaviors work safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100