add a no documentation recovery card #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The no documentation card indicates that the steps on how to recover are not (physically) available. Printed documentation is relevant in particular if your system that contains the documentation on how to recover from backup itself needs to be recovered.
Collaborator
|
Hi @cburger-scheidlin, What do you think about rephrasing the Recovery-Ace card? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The 'no documentation' card indicates that the steps on how to recover are not (physically) available. Recovery can be a stressful time, in particular if business data is involved or availability targets may be missed. An understandable and tested playbook for recovery is a great tool for injecting calm into this situation. For larger setups, it may even be vital in case the engineer on call - at 3am on a Sunday, naturally - needs to recover a system that they do not develop themselves. Printed documentation is relevant in particular if your system that contains the documentation on how to recover from backup itself needs to be recovered.