Kroll Ontrack Recovering Your Virtual Data

1,245 views
1,170 views

Published on

Discussion of Data Recovery for VMware systems and other virtual environments

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

  • Be the first to like this

No Downloads
Views
Total views
1,245
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kroll Ontrack Recovering Your Virtual Data

  1. 1. Recovering Your Virtual Data<br />April 29, 2009<br />David LogueSr. Data Recovery Engineer<br />
  2. 2. Learning Objectives<br />Identify common data loss scenarios in virtual environments <br />Challenges with recovering virtual data<br />Recommendations when virtual data loss occurs <br />Design recommendations for a virtual environment with data loss prevention in mind <br />
  3. 3. BSOD or PSODDo They Give You Chills? <br />
  4. 4. Common Data Loss Scenarios<br /><ul><li>Hardware failures
  5. 5. RAID
  6. 6. Disk
  7. 7. Software failures
  8. 8. File System
  9. 9. Data Corruption
  10. 10. Database Corruption
  11. 11. VMware Metadata Corruption
  12. 12. Human error
  13. 13. Deleted
  14. 14. Overwritten
  15. 15. Formatted (Guest and Host level)</li></li></ul><li>Common Data Loss ScenariosFailure Types<br />
  16. 16. Common Data Loss ScenariosFailure Types<br />Source: Over 100 Kroll Ontrack Virtual Data Recovery Jobs Over the Past 12 Months <br />
  17. 17. Learning Objectives<br />Common data loss scenarios in virtual environments <br />Challenges with recovering virtual data<br />Recommendations when virtual data loss occurs <br />Design recommendations for a virtualenvironment with data lossprevention in mind<br />
  18. 18. Challenges with Recovering Virtual Data<br /><ul><li>Recovery of multiple guests on a single volume
  19. 19. Snapshots, logs and swap files add complexity
  20. 20. Virtual file system fragmentation
  21. 21. Size of the recovery
  22. 22. Lack of a good backup that has been tested
  23. 23. Using traditional methods of recovery, such as restore, may make the problem worse</li></li></ul><li>Case Study – Hospital in CrisisInitial Facts<br /><ul><li>Hospital had a 5 drive RAID 5 array attached to their VMware ESX server (1.2TB volume)
  24. 24. The array hosted 4 MS Windows 2003 Server virtual machines running MS SQL 2005 which contained their patient medical records
  25. 25. The RAID controller failed
  26. 26. Hospital replaced the RAID controller and rebooted
  27. 27. All of the drives stayed offline after the reboot</li></li></ul><li>Case Study – Hospital in CrisisCustomer Plan<br /><ul><li>Force the drives online and rebuild
  28. 28. If that failed, restore from backup
  29. 29. If that failed, recreate the missing patient data from other sources</li></li></ul><li>Case Study – Hospital in CrisisAdditional Options<br /><ul><li>Customer contacted Kroll Ontrack for a free Data Recovery consultation.
  30. 30. Kroll Ontrack’s recommendations:
  31. 31. Image the drives before starting the restore/rebuild process
  32. 32. If the restore or rebuild fails:
  33. 33. Start a Remote Data Recovery or
  34. 34. Ship drives to Kroll Ontrack for recovery</li></li></ul><li>Case Study – Hospital in CrisisAdditionalCustomerChallenges<br /><ul><li>The customer imaged the drives
  35. 35. The customer forced the drives online and determined:
  36. 36. The RAID configuration was damaged and
  37. 37. One of the drives was out of date (degraded)
  38. 38. Forcing a rebuild with a degraded would cause additional damage
  39. 39. Backups did not include the SQL data
  40. 40. Time to recreate data – 3 months to 2 years</li></li></ul><li>Case Study – Hospital in CrisisKroll Ontrack to the Rescue<br /><ul><li>The customer contacted Kroll Ontrack
  41. 41. Kroll Ontrack connected the customer remotely and started the evaluation and recovery</li></li></ul><li>Case Study – Hospital in Crisis VMware ® recovery overview<br />
  42. 42. Case Study – Hospital in Crisis VMware ® recovery overview <br /><ul><li>Locally attached drives, SANs, iSCSI, NFS Storage.</li></li></ul><li>Case Study – Hospital in Crisis VMware ® recovery overview <br /><ul><li>Software RAID manager used to replace RAID controllers that are no longer presenting the LUNs correctly. Supports all the types of RAID configurations.
  43. 43. Locally attached drives, SANs, iSCSI, NFS Storage.</li></li></ul><li>Case Study – Hospital in Crisis VMware ® recovery overview <br /><ul><li>Virtual device presented by the RAID manager. It is seen by the tools as if it was the original device.
  44. 44. Software RAID manager used to replace RAID controllers that are no longer presenting the LUNs correctly. Supports all the types of RAID configurations.
  45. 45. Locally attached drives, SANs, iSCSI, NFS Storage.</li></li></ul><li>Case Study – Hospital in Crisis VMware ® recovery overview <br /><ul><li>Specialized recovery tools are used to recover from corruption inside most any file system.
  46. 46. Virtual device presented by the RAID manager. It is seen by the tools as if it was the original device.
  47. 47. Software RAID manager used to replace RAID controllers that are no longer presenting the LUNs correctly. Supports all the types of RAID configurations.
  48. 48. Locally attached drives, SANs, iSCSI, NFS Storage.</li></li></ul><li>Case Study – Hospital in CrisisInside the RAID<br /><ul><li>The RAID failure was causing VMware data to be inaccessible, Ontrackreplaced the RAID controller with software to get to the data.</li></li></ul><li>Case Study – Hospital in CrisisInside the RAID<br /><ul><li>This virtual Raid is then accessed like the original array for the rest of the recovery process
  49. 49. Ontrackengineers mapped out the data to determine the original RAID configuration and present ed the array to our recovery tools.</li></li></ul><li>Case Study – Hospital in CrisisInside the RAID<br />Once the array was presented, individual virtual machines were recovered from the VMFS volume<br />
  50. 50. Case Study – Hospital in CrisisInside the RAID<br />Proprietary NTFS and SQL recovery tools were then used to recover critical databases<br />Once the array was presented, individual virtual machines were recovered from the VMFS volume<br />
  51. 51. Case Study – Hospital in CrisisConclusion<br />Ontrack used four levels of recovery to get to the customer data<br /><ul><li>Raid recovery tools to re-assemble the original Raid configuration
  52. 52. VMFS recovery tools to repair damage to the file system and copy out the VMDK files
  53. 53. NTFS recovery tools to repair the NT file system and copy out the SQL files
  54. 54. MS SQL recovery tools to extract the tables into a new database</li></ul>Kroll Ontrack was able to get a full recovery of the critical SQL data<br />
  55. 55. Learning Objectives<br />Common data loss scenarios in virtual environments <br />Challenges with recovering virtual data<br />Recommendations when virtual data loss occurs<br />Design recommendations for a virtualenvironment with data lossprevention in mind<br />
  56. 56. Recommendations When Data Loss Occurs<br />Don’t panic and don’t update your resume <br />When troubleshooting, do not write any data to the storage array or change storage configurations. <br />Don’t format the volume that has missing data<br />Use the support system offered by the software provider<br />Restore data to an alternate location and contact a data recovery company with extensive virtual data recovery experience including the ability to perform remote recoveries <br />
  57. 57. Recommendations When Data Loss Occurs<br />Definition of Data Recovery (DR)<br /><ul><li>DR gets back files from corrupted or inaccessible storage (directly from the failed system, not from a backup)
  58. 58. DR gets back most recent files vs most recent backup
  59. 59. In some cases, DR is faster than restoring from the last backup
  60. 60. DR fits well as part of an overall disaster recovery plan </li></li></ul><li>Learning Objectives<br />Common data loss scenarios in virtual environments <br />Challenges with recovering virtual data<br />Recommendations when virtual data loss occurs <br />Design recommendations for a virtual environment with data lossprevention in mind<br />
  61. 61. Design Recommendations<br />Implement naming conventions for hosts, guests, physical servers and virtual file system volume <br />Control who has access to the environment <br />Document the backup and recovery plan and include the contact information of your preferred data recovery vendor in the plan <br />Test your backups on a regular basis <br />Use the tools to manage your virtual environment; don’t take shortcuts<br />Be careful how you use snapshots and do your housekeeping<br />Monitor the data stores, logs and swaps<br />
  62. 62. Learning ObjectivesSummary<br />Common data loss scenarios in virtual environments <br />Challenges with recovering virtual data<br />Recommendations when virtual data loss occurs <br />Design recommendations for a virtualenvironment with data lossprevention in mind <br />
  63. 63. Conclusion<br />Thank you!<br />Dave Logue<br />Sr. Remote Data Recovery Engineer<br />Kroll Ontrack, a Marsh & McLennan Company<br />dlogue@krollontrack.com<br />
  64. 64. © 2008 Kroll Ontrack Inc.| www.krollontrack.com<br />

×