Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
meskio
Wiki Replica
Commits
e9b59ad7
Unverified
Commit
e9b59ad7
authored
3 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
try to document disaster scenarios
parent
a85bd485
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
service/crm.md
+5
-3
5 additions, 3 deletions
service/crm.md
with
5 additions
and
3 deletions
service/crm.md
+
5
−
3
View file @
e9b59ad7
...
...
@@ -128,9 +128,11 @@ accessible only by TPA. To add a user, on the backend server
## Disaster recovery
<!-- what to do if all goes to hell. e.g. restore from backups? -->
<!-- rebuild from scratch? not necessarily those procedures (e.g. see -->
<!-- "Installation" below but some pointers. -->
If Redis dies, we might lose in-process donations. But otherwise, it
is disposable and data should be recreated as needed.
If the entire database gets destroyed, it needs to be restored from
backups, by TPA.
# Reference
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment