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.

Sign up for GitHub

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

Jump to bottom

Spike: Make a plan for database backups, DR plan #1225

Open
exalate-issue-sync bot opened this issue Nov 27, 2024 · 0 comments
Open

Spike: Make a plan for database backups, DR plan #1225

exalate-issue-sync bot opened this issue Nov 27, 2024 · 0 comments
Assignees
@lbeaufort @toddlees

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Nov 27, 2024 •
edited
Loading

  • How should we make ad-hoc backups? IE before a big migration
  • Where should we store ad-hoc database backups? s3?
  • How long should we keep ad-hoc database backups? cloud.gov saves them for 35 days.
  • How often does cloud.gov take a snapshot?
  • How will we restore backups if we turn off SSH access to prod?
  • Turn off ssh in prod, have a break glass option
  • Have a maintenance mode for the site when we need to take it down

Task:

Please create a follow-up to be refined on January 23, 2025

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1859
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lbeaufort lbeaufort

@toddlees toddlees

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lbeaufort @toddlees