Call Tree

---

Infrastructure Inventory

Hardware and software inventories are very important to any DR plan. Without this information, you expose yourself and your company to potential failure during the execution of the plan. While this may seem like a great deal of work, the outcome far outweighs the grief you are putting yourself through today. The success of the plan will be measured by the thoroughness of your work during the development of your plan.

Hardware Inventory

Include as much detail as possible about the hardware that will be protected by this DR plan. The more detail the better. Also include as much information about the maintenance contract as possible for the hardware as well. Here's a brief sample list of what you may want to include in your hardware inventory:

• Server name

• Make/model

• Serial number

• OS

  • Patch level

• Memory

  • Amount

  • Type

• Disk controllers

• Disk drives

• Partitions

• Network interface card

• IP address

For your UNIX servers, try to script as much of this as possible; if you are using VERITAS NetBackup, use the NetBackup Configuration Verification Utility (NCVU) found on VERITAS' support Web site. It will make running this inventory much easier. For Windows NT and 2000 servers, formal software packages are available that will help you create this type of information. How it is gathered is not the issue; the fact that you gather it for all machines deemed critical is what is important.

Architecture Inventory

The reason we included this heading under Hardware Inventory is that we feel the two go hand in hand. We want to stress the importance of diagrams that illustrate your network configuration, server configuration, drive partitioning, and so on. Include any and all diagrams necessary for this DR plan here. We're sure many of you have spent hours creating your Visio diagrams; now is the time to display them. Any paper or electronic diagrams should be recorded in your DR plan. If your company has an information librarian, then have him or her mark and track these documents; if not, include a table similar to the one in Table D.8.

Software Inventory

Equally as important as the hardware inventory, the software inventory will play a critical role in a successful recovery. Following is another sample list of the information you may want to include in your software inventory list:

• Application name

• Functional name (Finance, for example)

• Default installation path

  • Installation path different from default? (Y/N)

  • If yes, explain

• Software version

• Maintenance contract information

• Software license

• Hosting server

Table D.8: Example of an Architecture Inventory

PURPOSE	DOCUMENT NAME (P)APER/ (E)LECTRONIC	LOCATION(S)	LAST UPDATED	OWNER
Network for building 500	P-Network Map 500 E-NetMap_500.doc	P-Off-site Vendor E-Server/Path/ Document	04-30-02	O. L. Mysu
Finance application server	P-Finance Server E-FINSERV.doc	P-Corporate Library E-Server/Path/ Document	01-08-02	C. S. Psyrvivour

---