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

Agree a backup policy #2127

Closed
iaindillingham opened this issue Nov 13, 2024 · 1 comment
Closed

Agree a backup policy #2127

iaindillingham opened this issue Nov 13, 2024 · 1 comment

Comments

@iaindillingham
Copy link
Member

We should agree, and write, a backup policy. Currently, the nature and frequency of backups are implementation details (#2116). The policy should describe how much data we're prepared to lose, should restoring from a backup be necessary.

@lucyb
Copy link
Contributor

lucyb commented Nov 20, 2024

I think we've decided to split the policy into:

  1. the core application database
  2. the coding systems databases

We can document our approach to 1. as part of doing the work in #2151. I've suggested we keep it at the current 30 days of backup, but that we move the backups to a separate folder (we can build on this in future).

I think the coding systems databases are less urgent, because we have the droplet snapshots that we can fallback on, and any policy can be documented when we pick up #2153.

Does this seem reasonable?

@lucyb lucyb closed this as completed Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants