No Documentation for DR

By Baadil ·

I am about to inherit a network which has absolutely no documentation or documentation that is so old that it is completely useless. My first goal is to document every single aspect of this network for config management purposes as well as for disaster recovery.

I will be doing the following:

- Create visual map of the network, servers, routers, WAN, Workstations.

- Create detailed config docs for each server for DR including installed software and its config, RAID information as well as hardware information.

- Create config docs for each router/switch.

- Create DR plan.

To accomplish this, I am in need of a lot of help. I am looking for tools, utilities, templates, sample documents and plans.

I know its a big task but I have to do it so any and all help you can provide is very much appreciated.

Thank you

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Start here

by Tig2 In reply to No Documentation for DR

Then try here:

There is a lot of good information out there. Start with the TR article for a broad view and then begin your narrowing out process.

Good luck!

Collapse -

re: Start here

by Baadil In reply to Start here

Thank you for the links. Yes, looking around I see a lot of info. Are there any toold that you prefer to use over others? Just looking for recommendations.


Collapse -

From a DR perspective

by Tig2 In reply to re: Start here

I am pretty wary of tools. I would rather take the time to look at the machine, screenshot what is REALLY there, and use Visio or similar to create the maps.

I also find that interviewing both the system architect and the end users that use/maintain the system is VERY valuable.

There is really no one best answer. What I can tell you is that I base my foundations on the ITIL Best Practises for Service Delivery. From there, I determine what apps/services are critical in the event of disaster. Those are the things that I take first look at.

I keep the tools I use restricted to the most common for a reason- I may need to get to the source doco during an emergency. If I keep my tools restricted to common apps, I am most likely to do that successfully.

I guess, in short, I prefer to take a look at all of the physical network personally. I want to see what every device is doing. That gives me my physical map. From there, i can develop the logical map. Through end user discussion, I can prioritise at a high level. Through discussion with business, I can refine my prioritisation.

Let me know how you progress with this effort. You are doing the right things.

If I can be of further assistance, post back or peer mail.

Collapse -


by TheVirtualOne In reply to No Documentation for DR

I'd suggest loading "The Dude" to get a quick visual... then looking into something like Spiceworks. I use both of these tools continuously as I enter into a new contract.

Related Discussions

Related Forums