Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It's very important to have decent and good documentation. The problem is that often we might have good documenting techniques, but we forget some crucial points. It can be extremely painful to find these crucial points during a disaster recovery.

Therefor I want to create this canonical question and answer on what we should be documenting and how we should be writing it down.

We already have these good questions and answers on what technologies we can use for documenting:

All answers will be merged into one big sectioned answer that administrators can use to checklist their own documentation.

share|improve this question

This answer provides a detailed overview on what to document. All other answers will be merged into this answer.

What do we document?

What to document

How to document it

References (if any)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.