Here is a sample plan provided only as a guide which can be used as a guide or an example of a disaster recovery plan. (This means it is not the only way to create a project plan.) Do research on the subject (Disaster Recovery Plan) thoroughly before embarking on a disaster recovery project to get better results. It is recommended you ask for a consultant to help you out in your disaster recovery planning attempt. It is NOT a simple project that you can accomplish easily by yourself (even with the best research facilities.)
There are six parts of Disaster Recovery Planning. You have the first part called Program Description with its phases which are: pre-planning of activities or Project Initiation, vulnerability assessment and general definition, requirements, business impact analysis, detailed definition of requirements, plan development, testing program, maintenance program, initial plan testing and plan implementation.
The other 5 parts of Disaster Recovery Planning are: Planning Scope and Plan Objectives, Project Organization and Staffing; Project Control; Schedule of Deliverables; and Resource Requirements.
You can get an idea of the complexity of the process through the program description. Its complexity requires adequate information processing resources and numbers of technical staff, and of course an appropriate budget (or sufficient funds.)
The Planning Scope and Plan Objectives of the Disaster Recovery Planning can be used to enable the organization to prepare to survive an alarming disaster and to continue with regular operations after a tragedy strikes.
The Project Organization and Staffing parts can be utilized for full implementation of any plans in their most effective and efficient methods as possible.
Project Control, on the other hand, acts as the support system of the management software itself.
Schedule of Deliverables creates the necessary schedules and so that the project can be maintained by phases.
And lastly, the Resource Requirements phase that is divided into three categories which are personnel, capital costs and on-going costs. This sums up the disaster recovery plan.
The server is a part of a whole network of computers communicating together to do specific tasks. It manages the traffic of data transmission as it directs commands and requests to its desired destination within the network. When things go wrong with the server, every unit that is connected to the network is affected. For this reason alone, big companies such as Microsoft have developed ways on how to handle server disaster recovery issues. Described below are some of the items that Microsoft Windows Engineers and Administrators must need to consider when it comes to dealing with disaster recovery and business continuity planning.
First is to plan for high availability. As a Server Administrator, it is not part of your job description to guess possible scenarios or outcomes. You must be precise on everything you do, or else, everything that you have worked for will be put into waste. Take a lot of your time to design a plan, carefully set your objectives and study hard to meet certain business expectations.
Anticipating and planning server down times is your second priority. Yes, it is a fact that the company expects a 100% uptime, but this only happens in the perfect world. Server breakdowns are most likely to occur due to power or UPS failure, hardware and software system malfunctions, and disk errors. To deal with such issue, assign a specific time for server maintenance to ensure that everything is in order. Keeping the balance between server uptime and downtime is a must to ensure business continuity when presented with such server issues.