Network Admin D R P

695 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
695
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
36
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Network Admin D R P

  1. 1. Data Networking Year 2 Network Administration Planning a Disaster Recovery Plan Colm Bennett
  2. 2. What is a Disaster Recovery Plan? <ul><li>a set of policies and procedures for reacting to and recovering from an IT-disabling disaster </li></ul><ul><li>Usually part of a Business Continuity Plan </li></ul><ul><ul><li>A BCP will cover more than just the IT side </li></ul></ul><ul><li>Usually a script detailing how to get from certain disaster scenarios back to functioning IT system </li></ul>
  3. 3. Steps in creating a DRP <ul><li>Risk Analysis </li></ul><ul><li>Budget </li></ul><ul><li>Develop the Plan </li></ul><ul><li>Test </li></ul>
  4. 4. Risk Analysis <ul><li>Assess your key risks and probabilities of these risks </li></ul><ul><ul><li>Acts of God </li></ul></ul><ul><ul><ul><li>Flood, Wind etc </li></ul></ul></ul><ul><ul><li>Accident </li></ul></ul><ul><ul><ul><li>Overwrite key backup, pull wrong plug etc </li></ul></ul></ul><ul><ul><li>Malicious </li></ul></ul><ul><ul><ul><li>Virus, arson, theft etc </li></ul></ul></ul><ul><li>Establish Business implications of key risks </li></ul>
  5. 5. Budget <ul><li>Based on business implications, establish budget for both prevention and recovery </li></ul><ul><li>Ideally this budget is decided on by Business Unit after being presented with Risk Analysis by IT </li></ul><ul><li>IT shouldn't make budget decision in isolation because they are not close enough to gauge real business impact of risks </li></ul>
  6. 6. Do Plan <ul><li>Establish Recovery Time Objectives (RTO) for key systems </li></ul><ul><ul><li>How long before they must be back up </li></ul></ul><ul><li>Establish Recovery Point Objectives (RPO) for key systems </li></ul><ul><ul><li>How much data much be recovered </li></ul></ul><ul><ul><ul><li>e.g. Can we restore accounts to end of last week? </li></ul></ul></ul><ul><li>Based on these benchmarks, create a plan </li></ul>
  7. 7. Do Plan <ul><li>3 Key approaches </li></ul><ul><ul><li>Mix and Match depending on RTO and RTP </li></ul></ul><ul><li>Backup and Restore </li></ul><ul><ul><li>ID Key Data </li></ul></ul><ul><ul><li>Off Site storage </li></ul></ul><ul><li>Replication </li></ul><ul><ul><li>Backup Servers </li></ul></ul><ul><ul><li>Hot off site etc </li></ul></ul><ul><li>Failover </li></ul><ul><ul><li>Hotswap parts </li></ul></ul><ul><ul><li>Off site WAN cluster </li></ul></ul>
  8. 8. Test It! <ul><li>Absolutely Key </li></ul><ul><li>Backups should be restored periodically </li></ul><ul><li>Replication sites should be used for real business </li></ul><ul><li>Failover should switch from one to another regularly </li></ul><ul><li>Should be updated with feedback from testing </li></ul>

×