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

No strict backup rules #113

Open
agoncharov-reef opened this issue Jun 8, 2023 · 0 comments
Open

No strict backup rules #113

agoncharov-reef opened this issue Jun 8, 2023 · 0 comments
Assignees

Comments

@agoncharov-reef
Copy link
Contributor

The situation with backups is not good. Nobody checks whether they actually work (i.e. whether they are created, and whether whatever is created is good for restoring after failure), and we have only small section in README about backups

Proposal:

  1. Add strict policy for backing up each new project (script backup, cloud service snapshots, backup images rotation policy, b2-or-not-b2 etc)
  2. Add backups creation stats to grafana, set up alerts if backups are missing
  3. Add periodic checks that backups are usable
  4. Check all existing projects for all clients and ensure all is fine
@mjurbanski-reef mjurbanski-reef self-assigned this Jul 1, 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