Skip to content
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

Consider adding a nightly database dump #165

Open
nonprofittechy opened this issue Sep 29, 2023 · 1 comment
Open

Consider adding a nightly database dump #165

nonprofittechy opened this issue Sep 29, 2023 · 1 comment
Labels

Comments

@nonprofittechy
Copy link
Member

Although Postgres is transaction safe, this would still improve recoverability. We may want to keep at least a few days of dumps as well.

@BryceStevenWilley
Copy link
Collaborator

Some additional thoughts:

  • This could be as simple as a cron job running on the AWS server or in the postgres container that runs pg_dump 1, and sends the gzipped dump to S3.
  • Alternatively, we might be able to run pg_dump as a scheduled job from the java size? idk.
  • One more alternative is to try to directly backup the docker volume where the postgres data is stored. This might not be optimal, as it wouldn't work across postgres versions I think. https://www.howtogeek.com/devops/how-to-back-up-your-docker-volumes/

Footnotes

  1. Of the options mentioned in the postgres docs, the Write ahead log (WAL) is mostly for crash protection, and taking a file level archive says it should only be done when postgres is not running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants