Discussion Locked

Disaster Recovery Plan

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I need to know how should I go about developing a DRP in a situation whereby one is responsible for software applications and the hardware is the responsibility of somebody else.

7 replies

by mars9

First of all you need to define what comprises your area of responsibility:
- software program
-database applications, etc

This also extends to the data that is collected and used by both your business and customers.

What procedures must be incorporated into the daily activities and operations to ensure that the data is protected on an ongoing basis. What investments must be made to ensure that the software is available and can be used in another location?

If your office melted tomorrow (nothing left)what do you need to provide so that in entering a new physical location the business areas could pick up the moment they walked in a start business as usual.

In crafting a solution you need to take into account the most likelyscenarios (earthquakes? tornados? floods? war?). You also have to work with the business areas to identify what software and database applications support the key/critical areas and what needs to be made available first.

More to the point of your question - software needs hardware in order to function so you will need to work closly with the person doing the hardware piece. You need to do your research (focusing on what must be provided to enable the business to function and to not lose important records and data and continue to provide services to clients).

Develop high level requirements. Work with the hardware person to ensure that the hardware you need to support the software needs is in place.

by tphurley

A couple of additional questions need to be asked. Who is responsible for the both hardware and software? (This is important, because the responsiblity for a fully integrated DRP is their responsibility.) I will assume that you are putting your piece of the plan together. You will need to know where your backup software is going to reside and on what hardware it will be run on in the disaster. Remember that in a disaster other's are likely to be needing the same resources to run as you are. A full up test program to test the ability of your backed up software to run your application in the new environment should be included. A plan for annual testing is probably also a good idea as changes to the software as time goes by may affect the ability of your application to run. You also need a plan to assure that version control is carried out on your software so that the back up software reflects the "current" configuration and can be verified. TPH :-)

by manager

You may be in an unfortunate situation where (because of organizational structure or ill divided responsibilities) you are expected to devise a DRP for software alone. In an ideal world (and you may want to argue for this with your manager) you would define the companies main product offerings and then necessary back office/support functions (of course you need to consider the effect of office dispersion or multiple locations). A business leader from each necessary back office function and product offering would tell you what they need to run shop and minimally what would be most necessary to run shop. (if it is still the case that you only document software, then do just that, but make sure when assessing the software's requirements, you make sure to document any hardware dependencies you encounter). Your plan will more resemble a list of software, thier dependencies, and suggestions as to how to move these logical systems. (However you need to make sure you define beforehand that is what you will deliver since you will not be able to deliver a complete DRP if you do not have input on the physical implementation)

To make sure you properly CYA (cover your ---):

1) You want to make sure the lines of responsibility are clearly defined. Who is responsible for creating a plan for Databases/Data Access (does your organization define a database server by the admin that watches the box or the DBA that configures the databases)? Who is responsible for redirecting 3rd party feeds the software may use (what about if they are provided through leased lines? (hardware))? etc...

2) Collaborate as much as possible with whoever is responsible for ceating the hardware DRP. If this is easy work together and build one document. If this is difficult, make sure your boss knows what he will be recieving as a deliverable.

This discussion is closed to new replies.