IT Employment
I have the mundane task of developing a comprehensive disaster recovery plan. It's a dirty job - but somebody's got to do it.
The problem is, where do you start? Could someone who has developed such a plan shed some light on this fo me. Thanx
by tmcclure
Start small. Look at the services at the LAN level. IE what would you do if:
A server goes down. A switch or router went. Are there any critical users who need a spare PC? How about printing?
How about backup procedures. Do you have an off site backup? If your server goes down can you shift the laod to another server temporarily
Look at your enviornment and create different situations and how you would solve them at the user level, LAN level and WAN level.
by warthog
I would agree to start small. Create the same basic questions that would be applied to:
Users, desktops, servers, server room etc. What would a user need if? Their system crashed or the building caught fire? A user needs certain software, a phone, a place to work etc. If the building ended up in a rubble, what steps do you think you would need to take to get people working again? Lay out some basic questions then start interviewing various dept managers for their input. Then search the Internet to see if someone else published their dist.recovery guidelines or check out the library. Each site will have different requirements - if your company is large, you may need a hot site etc. Good Luck.
by jmessina83
Hi, i just wanted to ask a question......i'm doing a UNI assignment which is to CREATE A DISASTER RECOVERY PLAN.....i was wondering if you knew any sites thats give you the steps to do this?
John
by ayoshi
I would start by doing a business criticality analysis. I would first determine a matrix of general business areas with specific IT processes attached.
Consult with the business owners, and find out a "preferred" no outage greater than "x" hoursor days, and an "under no circumstances can be out more than 'x' hours or days" for each process.
Then take the most critical processes, and define what would be required to support those processes if anything failed. Start small by thinking about individual components (servers, routers, etc...), then expand the scope to cover LAN, WAN, buildings, sites, etc....
For each "backup", you must then define the most cost-efficient way to meet the recovery requirements as defined in the first step.
The most critical individual task I can recommend is to make sure that you have an off-site backup of ALL data.
This discussion is closed to new replies.
Sort by Trending