Basic system documentation rules
1. Do not put doc on network.. so don't use wiki or all kind of CSM tools for that. network down = no doc.
2. Try to use scripts as much as possible to document your system and use CVS to keep track of change.. (automated, cron, report diff, etc)
3. Password and those stuff should be in a encrypted file (ok I know this is obvious)...
4. Keep track of past incident, problem, (internal and with vendors) (problem are recuring... so)
5. Avoid doing diagram. This is a real waste of time and they are only good for manager that want to show to other people how nice is the network in my cie.
6. Again... everything should be on your USB key (with a copy on the network).
Slashdot Mirror
Simple.. use CVS. Documentation is centralized and de-centralized. You have versioning, log, comment, and overall this... it's free
Basic system documentation rules 1. Do not put doc on network.. so don't use wiki or all kind of CSM tools for that. network down = no doc. 2. Try to use scripts as much as possible to document your system and use CVS to keep track of change.. (automated, cron, report diff, etc) 3. Password and those stuff should be in a encrypted file (ok I know this is obvious)... 4. Keep track of past incident, problem, (internal and with vendors) (problem are recuring... so) 5. Avoid doing diagram. This is a real waste of time and they are only good for manager that want to show to other people how nice is the network in my cie. 6. Again... everything should be on your USB key (with a copy on the network).