Documenting Disaster Recover Procedures
-
I have some examples from SW and the web, but I was wondering if anyone here had some documented procedures they do not mind sharing. Or just some nuetral advice. My goal for the weekend is to complete the initial draft of the DR process for one of my clients.
-
I've done a lot of DR testing over the years but have not written the documents.
-
I write DR documents for companies, but it's quite specific based on the company's needs, compliance requirements, and size/complexity of the systems. From start to finish, it's about a 3-week project in most cases, but could easily go longer depending on the detail required in the document. The last one I did was for a 90-person company that was SOX compliant due to their parent company being a larger public firm. It was a week of discovery, a week of writing it, and a week of editing, presenting, and revising. It came out to about 27 pages before appendices/diagrams.
-
As our company is the IT department for this company there is no discovery because we already know everything related to the IT infrastructure. I hate writing documentation. I know it is important. I still do not like writing it.
-
@JaredBusch said:
I hate writing documentation. I know it is important. I still do not like writing it.
This is why I get paid for documentation and technical writing engagements.
-
Well, I will be getting paid for it. I still do not like it!
-
@JaredBusch said:
Well, I will be getting paid for it. I still do not like it!
I actually enjoy writing documentation for the most part, but I can't seem to find the time to do it well enough to meet my own expectations.
-
If given time (and money) to make documentation, I tend to like it.
