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

Disaster recovery tests #489

Open
jchristgit opened this issue Aug 25, 2024 · 0 comments
Open

Disaster recovery tests #489

jchristgit opened this issue Aug 25, 2024 · 0 comments
Labels
component: services An issue relating to a Python Discord service (e.g. Bot, Site, Lancebot) group: docs Issues and pull requests related to our documentation

Comments

@jchristgit
Copy link
Member

jchristgit commented Aug 25, 2024

To ensure the DevOps team is prepared for the worst, we should carry out
(scheduled) disaster recovery tests.

We don't necessarily have to disable live services for this. The idea is more to
practice situations like the following and document what happens:

  • our LDAP server was nuked by accident, how do we restore it?
  • we lost the infractions table on the PostgreSQL database
  • netcup accidentally deleted lovelace
  • [please suggest more]

This issue just stands to plan this and discuss it.

Discussion so far

  • Joe mentioned that we have backups from Blackbox stored in Linode. The admins
    team has access to this.
@jchristgit jchristgit added component: services An issue relating to a Python Discord service (e.g. Bot, Site, Lancebot) group: docs Issues and pull requests related to our documentation labels Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: services An issue relating to a Python Discord service (e.g. Bot, Site, Lancebot) group: docs Issues and pull requests related to our documentation
Projects
Status: Up next
Development

No branches or pull requests

1 participant