Creating And Implementing A Data Disaster Recovery Plan


Published on

Published in: Technology
  • Be the first to comment

Creating And Implementing A Data Disaster Recovery Plan

  1. 1. Creating and Implementing Data Disaster Recovery Plan
  2. 2. Introduction
  3. 3. Basic Backup Types <ul><li>Full. </li></ul><ul><li>Incremental. </li></ul><ul><li>Differential. </li></ul><ul><li>Copy. </li></ul><ul><li>Continuous. </li></ul>
  4. 4. Backup Considerations <ul><li>How much time do you have to perform the backup? </li></ul><ul><li>How much time do you have to restore data? </li></ul>
  5. 5. Recovery Time Objective (RTO) <ul><li>The RTO (Recovery Time Objective) will be contingent on several factors, including: - </li></ul><ul><ul><li>The amount of data to be restored : Do you have to restore a single file or an entire data store? </li></ul></ul><ul><ul><li>The number of restores to be performed : Do you have to store one full backup plus three incremental, or just one differential? </li></ul></ul><ul><ul><li>The type of backup media in use : Are you restoring from physical media or over the network? Newer tape media such as LTO-4 work with high-speed drives that greatly reduce the amount of time required to restore data. </li></ul></ul><ul><ul><li>The location of the backup files : Is the data on media physically located in an offsite storage location? </li></ul></ul>
  6. 6. Recovery Point Objective (RPO) <ul><li>RPO is a measure of the acceptable amount of data you can lose, in hours. </li></ul><ul><li>Example : Organization might define its RPO as 2 hours, which means you must restore data to within 2 hours of any disaster striking. </li></ul><ul><li>Data created or modified within that 2-hour range is considered an &quot;acceptable loss.&quot; </li></ul><ul><li>The RPO helps you determine how often you need to perform backups. </li></ul>
  7. 7. Types of Backup Media <ul><li>Disk-to-Disk backup. </li></ul><ul><li>Disk-to-Tape backup. </li></ul>
  8. 8. Backup Schedules <ul><li>Two basic schedule types: - </li></ul><ul><ul><li>Five-tape system. </li></ul></ul><ul><ul><li>Grandfather-father-son. </li></ul></ul>
  9. 9. Laying the foundation for backups <ul><li>It begins with centralized storage on a server rather than on local PC hard drives. </li></ul><ul><li>Preserving network availability during backup </li></ul><ul><li>Backups require a significant amount of bandwidth. </li></ul><ul><li>That’s why backups are scheduled during off hours when few or no users are accessing the network. </li></ul>
  10. 10. Optimizing Backup Performance <ul><li>Leveraging current infrastructure. </li></ul><ul><ul><li>Databases have a habit of growing with amazing speed. </li></ul></ul><ul><ul><li>They consume storage capacity at an alarming rate. </li></ul></ul><ul><ul><li>It's prudent to monitor end users' data storage allotment. </li></ul></ul><ul><ul><li>Need to limit storage to necessary business-related data only. </li></ul></ul>
  11. 11. Meeting Future Challenges <ul><li>No matter how well you optimize your system, your needs eventually grows. </li></ul><ul><li>When increasing your storage capacity, your network infrastructure must also be able to manage the load. </li></ul><ul><li>Even when backing up in off-peak hours, you still have only so many hours to conduct the backup. </li></ul>
  12. 12. Meeting Future Challenges <ul><li>Because of other maintenance tasks, you can't depend on 100-percent processing power and network availability, dedicated to backups. </li></ul><ul><li>Upgrade your hardware and network infrastructure, as needed, to provide sufficient ability to back up the growing amount business data. </li></ul>
  13. 13. Securing Data Backup & Storage <ul><li>It's possible for your data to be at risk of interception and theft, both during the backup process and while in storage . </li></ul><ul><li>To protect data in transit , the best method is using I nternet P rotocol Sec urity (IPSec) over a V irtual P rivate N etwork (VPN) tunnel to ensure security. </li></ul>
  14. 14. Securing Data Backup & Storage <ul><li>To maintain the security of backup media, keep your portable storage in a tape vault or some other secure location. </li></ul><ul><li>Smaller businesses with limited budgets, can use a safety deposit box or offsite safe. </li></ul><ul><li>The location must be readily accessible to authorized staff should the media be needed for a recovery procedure. </li></ul>
  15. 15. Storage Media Management <ul><li>Managing backup tapes is more than just switching them out and making sure they're properly stored. </li></ul><ul><li>There are a number of issues that come with using storage media repeatedly over long periods of time. </li></ul>
  16. 16. Storage Media Management <ul><li>Dirty or damaged tapes and tape drive heads. </li></ul><ul><li>Tape wear. </li></ul><ul><li>Long-term storage. </li></ul>
  17. 17. Testing Data Restoration <ul><li>Set a regular schedule to test your recovery system. </li></ul><ul><li>Remember that you're not just testing whether the system works but also how quickly it works. </li></ul><ul><li>How long can your business afford to remain offline without access to critical data? </li></ul><ul><li>The pre-determined values of RTO and RPO will come into play. ` </li></ul>
  18. 18. Putting the Plan in Writing <ul><li>The first part of testing data restoration is developing and documenting a plan. </li></ul><ul><li>In a disaster, multiple parts of your network infrastructure can fail or at least be impaired. </li></ul><ul><li>Your recovery plan, should take into account all of the different aspects, of the overall system and how to respond when faults occur. </li></ul>
  19. 19. Putting the Plan in Writing <ul><li>One method is to create an overall disaster management plan that addresses aspects of recovery after a disaster, with the following individual sub-plans: - </li></ul><ul><ul><li>Systems : Covers handling of server faults and general restoration of data, applications and services </li></ul></ul><ul><ul><li>Network : Focuses on bringing up internetworking devices, such as routers and switches </li></ul></ul><ul><ul><li>Communications : Coordinates how different organizations are contacted, such as law enforcement, company management, hazardous materials personnel and Federal Emergency Management Agency (FEMA), if necessary. </li></ul></ul><ul><ul><li>These different parts of the plan can easily map to different teams in a larger organization. </li></ul></ul>
  20. 20. Testing the Team <ul><li>When delegating responsibilities, don't forget to assign the task of performing a recovery in the event of a disaster. </li></ul><ul><li>When you test the team, test the recovery plan and how the members of the team mesh in their tasks. </li></ul><ul><li>If a team member has successfully corrected the hardware fault, do they have to wait for the tapes to be made available to initiate the recovery? </li></ul><ul><li>If the tapes and the servers are ready, is there a delay in restoring the correct configuration files to the local switch? </li></ul><ul><li>Testing the team is like running a fire drill. </li></ul><ul><li>You not only find out how well they work together, but also where the faults and gaps are in performance and, to some degree, the plan itself. </li></ul>
  21. 21. Running Test Levels <ul><li>Because you can face different types of disasters, you should run different types of tests. </li></ul><ul><li>One of the most common tests is restoring data from tape in the event of a data loss. </li></ul><ul><li>Any test you run must be conducted in off-peak hours when few or no end users are on the system. </li></ul><ul><li>Planning for the occasional weekend testing &quot;party&quot; is a small price to pay for the relative security of knowing your recovery plan works. </li></ul>
  22. 22. Running Test Levels <ul><li>Beyond restoring data to a server. </li></ul><ul><li>You can also introduce issues to different parts of your system and see how quickly those issues are addressed. </li></ul><ul><li>Depending on how extensive you want to be, you can announce where the problem lies or allow your staff to attempt a diagnosis based on certain symptoms you announce. </li></ul>
  23. 23. <ul><li>Ensure everyone knows their role ahead of time so they can participate efficiently in testing the recovery plan. </li></ul><ul><li>Although backups are conducted regularly. </li></ul><ul><li>Recovery operations are rarely performed. </li></ul><ul><li>So make sure your staff is familiar with how to perform a server recovery and deal with all equipment and network connectivity. </li></ul>Running Test Levels
  24. 24. Summing Up <ul><li>In this presentation, you were explained, how to create and test a data backup plan. </li></ul><ul><li>Tips for restoring data, systems and your network after a disaster. </li></ul><ul><li>In addition, you were explained, best practices and many advanced systems and network administration techniques. </li></ul>
  25. 25. ?