Disaster Recovery & Data Backup Strategies


Published on

Published in: Technology
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Myriad Pro Regular 48pt Presented By:  Myriad Pro Semibold 30pt (all caps) Presenter: Myriad Pro Semibold 48pt Company: Myriad Pro Regular 48pt Date: Myriad Pro Regular 24pt
  • Disaster Recovery & Data Backup Strategies

    1. 1. Break Out Session 3 Disaster Recovery and Data Backup PRESENTED BY: Kris Bushover, Spiceworks Inc Eric Osterholm, OuterNet
    2. 2. Session Overview <ul><li>Data Backup – Why and How </li></ul><ul><li>Identifying Critical Data Systems </li></ul><ul><li>Planning for backup </li></ul><ul><li>Implementing, Monitoring, and Testing </li></ul>
    3. 3. Backup – Why do it? <ul><li>Increasingly, even the smallest businesses have become reliant upon the data they generate </li></ul><ul><ul><li>Critical data drives sales, tracks students, monitors inventories, and assists in the delivery of healthcare </li></ul></ul>
    4. 4. Backup – Why do it? <ul><li>Bottom line, in business today, you are your data </li></ul><ul><li>Lose data, lose business </li></ul><ul><li>Lost productivity, customer relationships, etc </li></ul>
    5. 5. Backup – Planning <ul><li>I already have RAID protection, why should I back the data up? </li></ul><ul><li>I already copy the data I need to disks/other systems/a CD in my desk drawer..... </li></ul>
    6. 6. Backup – Planning Can you recover it when you need it?
    7. 7. Backup – Planning Solutions fall into 3 tiers: User Snapshots, folder redirection Server Tape, Disk to disk, HSM, Virtualization Site Replication, Synthetic fulls
    8. 8. Backup – Planning <ul><li>Start backup planning by identifying the critical data systems </li></ul><ul><li>What relies on that data? </li></ul><ul><li>Get together with the business process owners and identify the data that they need to drive their business functions </li></ul>
    9. 9. Backup – Planning <ul><li>Determine “criticality” of data </li></ul><ul><ul><li>Work with process owners </li></ul></ul><ul><ul><li>Begin determining RTO/RPO </li></ul></ul><ul><ul><ul><li>RTO – recovery time objective: the amount of time that can pass between data system failure and restoration of functionality </li></ul></ul></ul><ul><ul><ul><li>RPO – recovery point objective: the reflected point in time of recovered data or the most recent version of the data that will be restored </li></ul></ul></ul>
    10. 10. Backup – Planning <ul><li>Based on this information, determine capacity requirements </li></ul><ul><ul><li>How much data needs to be backed up? </li></ul></ul><ul><ul><li>How much will the data set grow? </li></ul></ul><ul><ul><li>What is the acceptable backup window? </li></ul></ul><ul><ul><ul><li>System utilization </li></ul></ul></ul><ul><ul><ul><li>Peak and ebb periods </li></ul></ul></ul>
    11. 11. Backup – Planning <ul><li>Individual high-capacity systems may require dedicated backup resources; determine this now </li></ul><ul><li>Based on RTO/RPO, determine where offsite backup storage fits </li></ul>
    12. 12. Developing the Backup Plan <ul><li>Determine the repository type </li></ul><ul><ul><li>Full </li></ul></ul><ul><ul><li>Full+Incremental </li></ul></ul><ul><ul><li>Full+Differential </li></ul></ul><ul><ul><li>Continous Data Protection (CDP)‏ </li></ul></ul><ul><ul><li>Virtualization </li></ul></ul><ul><ul><li>Snapshots </li></ul></ul><ul><ul><li>Replication </li></ul></ul>
    13. 13. Developing the Backup Plan <ul><li>Full Backup </li></ul><ul><ul><li>Complete backup of the entire targeted data set </li></ul></ul><ul><ul><li>Restores are simple: restore using the single backup </li></ul></ul><ul><ul><li>Takes up the most space (of traditional backups)‏ </li></ul></ul>
    14. 14. Developing the Backup Plan <ul><li>Full+Incremental Backup </li></ul><ul><ul><li>Full backup made, followed by backups of only the data that has changed since the last full or incremental backup </li></ul></ul><ul><ul><li>Restores are more complicated: requires all backups and all incrementals </li></ul></ul><ul><ul><li>Complex storage requirements </li></ul></ul>
    15. 15. Developing the Backup Plan <ul><li>Full+Differential Backup </li></ul><ul><ul><li>Make a full backup, followed by a backup that captures all changes made since the last full backup </li></ul></ul><ul><ul><li>Data may be (probably will be) duplicated throughout the backup sets </li></ul></ul><ul><ul><li>Recovery requires last full backup and last differential </li></ul></ul>
    16. 16. Developing the Backup Plan <ul><li>Continuous Data Protection (CDP)‏ </li></ul><ul><ul><li>Backup system logs all changes to the system </li></ul></ul><ul><ul><li>Most often a block-level function </li></ul></ul><ul><ul><li>Dedicated hardware appliances and storage systems </li></ul></ul><ul><ul><li>Normally yields highest confidence in recovery, lowest RTO </li></ul></ul>
    17. 17. Developing the Backup Plan <ul><li>Virtualization </li></ul><ul><ul><li>Not directly a backup solution </li></ul></ul><ul><ul><li>Used in conjunction with snapshots or replication </li></ul></ul><ul><ul><li>Can provide fastest and most flexible recovery options </li></ul></ul>
    18. 18. Developing the Backup Plan <ul><li>Snapshots </li></ul><ul><ul><li>Keeps ‘point in time’ images of live system </li></ul></ul><ul><ul><li>Enables user accessible restore options </li></ul></ul><ul><ul><li>Based on base image + ‘differences’ = susceptible to corruption of all images </li></ul></ul><ul><ul><li>NetApp ‘.snapshot’ and Microsoft VSS </li></ul></ul>
    19. 19. Developing the Backup Plan <ul><li>Replication </li></ul><ul><ul><li>Copies file system changes as they are made </li></ul></ul><ul><ul><li>Bandwidth requirements play a big part: </li></ul></ul><ul><ul><ul><li>Synchronous = delayed commit </li></ul></ul></ul><ul><ul><ul><li>Asynchronous = image latency </li></ul></ul></ul><ul><ul><li>Used extensively for hosted offsite DR scenarios </li></ul></ul>
    20. 20. Developing the Backup Plan <ul><li>Determine Media Type(s)‏ </li></ul><ul><ul><li>Tape </li></ul></ul><ul><ul><li>Disk-based backup </li></ul></ul><ul><ul><ul><li>More on this in a moment </li></ul></ul></ul><ul><ul><li>Optical </li></ul></ul><ul><ul><li>Offsite/Internet-based systems </li></ul></ul><ul><ul><li>Hybrids </li></ul></ul>
    21. 21. Developing the Backup Plan <ul><li>Tape </li></ul><ul><ul><li>Magnetic tape is the classic backup medium </li></ul></ul><ul><ul><li>Sequential access: very fast writing of new data, really slow access for reading data </li></ul></ul><ul><ul><li>Numerous formats </li></ul></ul><ul><ul><ul><li>LTO, DLT, AIT, DAT, etc </li></ul></ul></ul>
    22. 22. Developing the Backup Plan <ul><li>Tape </li></ul><ul><ul><li>Tape drives/robotic libraries can be extremely expensive, but also very high capacity </li></ul></ul><ul><ul><ul><li>Provide a good cost/capacity ratio </li></ul></ul></ul><ul><ul><li>Tape is portable </li></ul></ul><ul><ul><ul><li>Can be stored offsite for DR purposes </li></ul></ul></ul>
    23. 23. Developing the Backup Plan <ul><li>Disk </li></ul><ul><ul><li>Faster backups </li></ul></ul><ul><ul><ul><li>Can eliminate streaming issues often seen when using tape to back up many small files </li></ul></ul></ul><ul><ul><li>Shorter restore times </li></ul></ul><ul><ul><ul><li>Seeking on disk is much faster than seeking on linear tape </li></ul></ul></ul>
    24. 24. Developing the Backup Plan <ul><li>Disk </li></ul><ul><ul><li>Physically managing disks can be less complex than managing multiple tapes </li></ul></ul><ul><ul><li>Disk reliability can be higher </li></ul></ul><ul><ul><ul><li>Mainly because it is not handled as much </li></ul></ul></ul><ul><ul><li>However..... </li></ul></ul>
    25. 25. Developing the Backup Plan <ul><li>Disk </li></ul><ul><ul><li>Since tapes normally contain a single backup, it is often just a matter of locating the tape that contains the needed data </li></ul></ul><ul><ul><li>Disk,on the other hand, will contain many sets of backup data, so coherent catalogs are of utmost importance </li></ul></ul>
    26. 26. Developing the Backup Plan <ul><li>Disk </li></ul><ul><ul><li>Other strategies exist for disk </li></ul></ul><ul><ul><ul><li>Virtual Tape Libraries </li></ul></ul></ul><ul><ul><ul><ul><li>Emulate tape to eliminate some of the previously mentioned complexity </li></ul></ul></ul></ul><ul><ul><li>Snapshot storage </li></ul></ul>
    27. 27. Developing the Backup Plan <ul><li>Optical </li></ul><ul><ul><li>Good for archiving (WORM)‏ </li></ul></ul><ul><ul><li>Not much else </li></ul></ul><ul><li>Offsite/Internet-based </li></ul><ul><ul><li>Data is shipped offsite over the internet to a hosting/storage provider </li></ul></ul><ul><ul><li>Replication </li></ul></ul>
    28. 28. Developing the Backup Plan <ul><li>Determine Backup Windows </li></ul><ul><ul><li>Normally, when systems are at lowest utilization (ie, middle of the night)‏ </li></ul></ul><ul><ul><li>Backup windows must be monitored </li></ul></ul><ul><ul><ul><li>More on this in a minute </li></ul></ul></ul>
    29. 29. Developing the Backup Plan <ul><li>RTO/RPO can affect the above decisions </li></ul><ul><ul><li>Aggressive RTO may call for high-capacity, fast tape or disk systems </li></ul></ul><ul><ul><li>Less aggressive RTOs may call for single tape systems with simple media rotation schemes </li></ul></ul><ul><ul><li>RTOs approaching 0 may require complex CDP/backup/replication systems </li></ul></ul>
    30. 30. Implement the Backup Plan <ul><li>Implement the plan </li></ul><ul><ul><li>As soon as the backup plan is in place and implemented, begin monitoring </li></ul></ul><ul><ul><li>Monitor conditions such as: </li></ul></ul><ul><ul><ul><li>Backup window violations (excessive run times)‏ </li></ul></ul></ul><ul><ul><ul><li>Errors/missed files </li></ul></ul></ul><ul><ul><ul><li>Unplanned media consumption rates </li></ul></ul></ul><ul><ul><ul><li>Bandwidth consumption </li></ul></ul></ul><ul><ul><ul><li>Affect on system performance </li></ul></ul></ul>
    31. 31. Implement the Backup Plan <ul><li>Backup Window Violations </li></ul><ul><ul><li>If backup windows are missed, decide whether to abort the backup or increase the window </li></ul></ul><ul><ul><li>Could be a capacity issue </li></ul></ul><ul><ul><ul><li>Increase capacity of backup system </li></ul></ul></ul><ul><ul><ul><li>Change media type (tape to disk)‏ </li></ul></ul></ul><ul><ul><ul><li>Change strategy (differential to incremental or CDP)‏ </li></ul></ul></ul>
    32. 32. Implement the Backup Plan <ul><li>Backup Window Violations </li></ul><ul><ul><li>Change to a Disk-to-Disk-to-Tape scheme </li></ul></ul><ul><ul><ul><li>Data is backed up to disk (staged), and then from there backed up to tape </li></ul></ul></ul><ul><ul><ul><li>Can have benefits in network systems where latency is affecting backup run times </li></ul></ul></ul><ul><ul><ul><li>Other benefits include being able to compress the data on the disk prior to backing up to tape and possibly encrypting </li></ul></ul></ul>
    33. 33. Implement the Backup Plan <ul><li>Test Your Backups </li></ul><ul><ul><li>Once again.... test your backups </li></ul></ul><ul><ul><li>Test for errors and completeness </li></ul></ul><ul><ul><li>If available, periodically restore to secondary/test systems </li></ul></ul><ul><ul><li>Address any and all errors thrown by backup systems immediately </li></ul></ul><ul><ul><li>Discard media that shows excessive errors </li></ul></ul>
    34. 34. Implement the Backup Plan <ul><li>Maintain Contacts </li></ul><ul><ul><li>Check in with business process owners to ensure that objectives have not changed </li></ul></ul><ul><ul><li>Brief stake-holders on quality control methods in place to ensure their data is safe and secure </li></ul></ul>
    35. 35. Implement the Backup Plan <ul><li>Document </li></ul><ul><ul><li>Document how all of the backup systems work </li></ul></ul><ul><ul><ul><li>Backup strategies for various systems </li></ul></ul></ul><ul><ul><ul><li>Restore procedures </li></ul></ul></ul><ul><ul><ul><li>Where media is stored and how it is rotated </li></ul></ul></ul><ul><ul><ul><li>What to do in case of a missed backup window </li></ul></ul></ul><ul><ul><ul><li>Emergency contacts </li></ul></ul></ul><ul><ul><ul><ul><li>Vendors, OEMs, backup specialists, etc </li></ul></ul></ul></ul>
    36. 36. Questions?