1. Top 5 Tips in 2012 for Failsafe Virtual Machine Protection Greg Shields Senior Partner and Principal Technologist, Concentrated Technology, LLC http://ConcentratedTech.com

2. Administrative points on this webinar  Questions ●Can use the virtual Q&A panel. ●This webinar is recorded and available for replay after a few days. ●At the end of the webinar, we can raise virtual hand for dialog questions. ●Stick around until the end of the webinar! −Winners will receive a choice of books!  Overview of Veeam

3. Protecting VMs is so much More than Just HA

4. HA is important, but it ain’t everything.

5. Protecting VMs is so much More than Just HA HA is important, but it ain’t everything. Protects against host failure. Protects against application failure.

6. Protecting VMs is so much More than Just HA HA is important, but it ain’t everything. Protects against host failure. Protects against application failure. Does nothing for data loss. Does nothing for corruption. Does nothing for DR.

7. …and yet HA Seems to Get all the Attention.

8. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways…

9. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data.

10. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects.

11. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS.

12. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS. An accidentally-obliterated VM object.

13. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS. An accidentally-obliterated VM object. Corruption as a result of miscommunication between layers.

14. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS. An accidentally-obliterated VM object. Corruption as a result of miscommunication between layers. Stupid users.

15. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS. An accidentally-obliterated VM object. Corruption as a result of miscommunication between layers. Stupid users. Stupid admins.

16. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS. An accidentally-obliterated VM object. Corruption as a result of miscommunication between layers. Stupid users. Stupid admins. Water-based datacenter fire containment systems (Hint: These are bad.)

17. How Can your VMs Fail? (Kinda’ like Faces of Death, but for VMs) Plenty of ways… Lost or deleted data. Lost or deleted application objects. A lost, deleted, or corrupted OS. An accidentally-obliterated VM object. Corruption as a result of miscommunication between layers. Stupid users. Stupid admins. Water-based datacenter fire containment systems (Hint: These are bad.) The-tsunama-that-causes-a-tornado-which-brings-out-locusts- that-cause-a-nuclear-detonation-which-starts-an-earthquake- that…

18. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night.

19. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake…

20. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways…

21. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die…

22. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill…

23. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill… Let’s count the ways…

24. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill… Let’s count the ways… Failure in quiescence or VSS.

25. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill… Let’s count the ways… Failure in quiescence or VSS. Failure in capturing data across datacenter layers.

26. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill… Let’s count the ways… Failure in quiescence or VSS. Failure in capturing data across datacenter layers. Failure in verifying backup integrity.

27. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill… Let’s count the ways… Failure in quiescence or VSS. Failure in capturing data across datacenter layers. Failure in verifying backup integrity. Failure in notifying you when something happens.

28. Desperately Seeking Failsafe. (Dead VMs are only the Start) All these ways to kill a VM can keep you up at night. …but that insomnia’s a piece of cake… …when you start thinking about all the ways… …your backup solution can also die… …or kill… Let’s count the ways… Failure in quiescence or VSS. Failure in capturing data across datacenter layers. Failure in verifying backup integrity. Failure in notifying you when something happens. Failure in accounting for organic VM growth.

29. Five Failsafe VM Protection Tips (Ignore at your Peril)

30. Tip #1: Mind your Layers.

31. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #1: Mind your Layers. Your datacenter layers, that is.

32. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #1: Mind your Layers. Your datacenter layers, that is. Virtualization adds many layers of separation between VM and backup storage target. VM > Hypervisor > Host Server > Network > Storage

33. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #1: Mind your Layers. Your datacenter layers, that is. Virtualization adds many layers of separation between VM and backup storage target. VM > Hypervisor > Host Server > Network > Storage Disk-based backups have the potential to aggregate “the backups” with “the data”.

34. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #1: Mind your Layers. Your datacenter layers, that is. Virtualization adds many layers of separation between VM and backup storage target. VM > Hypervisor > Host Server > Network > Storage Disk-based backups have the potential to aggregate “the backups” with “the data”. This is bad.

35. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #1: Mind your Layers. Your datacenter layers, that is. Virtualization adds many layers of separation between VM and backup storage target. VM > Hypervisor > Host Server > Network > Storage Disk-based backups have the potential to aggregate “the backups” with “the data”. This is bad. Particularly when “the VMware admin” isn’t “the storage admin”.

36. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #1: Mind your Layers. Your datacenter layers, that is. Virtualization adds many layers of separation between VM and backup storage target. VM > Hypervisor > Host Server > Network > Storage Disk-based backups have the potential to aggregate “the backups” with “the data”. This is bad. Particularly when “the VMware admin” isn’t “the storage admin”. FAILSAFE: Ensure backups and data stay separate.

37. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #2: Don’t Test your Backups.

38. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #2: Don’t Test your Backups. Hire someone to test them for you.

39. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #2: Don’t Test your Backups. Hire someone to test them for you. Better idea: Hire an automation to do it (cheaper, more reliable).

40. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #2: Don’t Test your Backups. Hire someone to test them for you. Better idea: Hire an automation to do it (cheaper, more reliable). Be exceedingly careful about how that automation defines “a successful backup”. Disk file data integrity <> A recoverable backup.

41. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #2: Don’t Test your Backups. Hire someone to test them for you. Better idea: Hire an automation to do it (cheaper, more reliable). Be exceedingly careful about how that automation defines “a successful backup”. Disk file data integrity <> A recoverable backup. FAILSAFE: Ensure backups include data and application integrity verifications that automatically occur with each backup.

42. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #3: Proactively Monitor Quiescence.

43. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #3: Proactively Monitor Quiescence. (Honestly, a great name for a band.)

44. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #3: Proactively Monitor Quiescence. (Honestly, a great name for a band.) VSS is ridiculously complicated. VSS can easily break. VSS breaking might not be VSS’ fault.

45. Five Failsafe VM Protection Tips (Ignore at your Peril)

48. Tip #3: Proactively Monitor Quiescence. (Honestly, a great name for a band.) VSS is ridiculously complicated. VSS can easily break. VSS breaking might not be VSS’ fault. FAILSAFE: Take the Ronald Reagan approach with VSS: Trust but verify.

49. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success.

50. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success. Demand more visibility for failure. Especially personal failures.

51. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success. Demand more visibility for failure. Especially personal failures. Ensure alerting is configured to notify for job failures.

52. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success. Demand more visibility for failure. Especially personal failures. Ensure alerting is configured to notify for job failures. (You laugh, but this gets missed all the freaking time.)

53. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success. Demand more visibility for failure. Especially personal failures. Ensure alerting is configured to notify for job failures. (You laugh, but this gets missed all the freaking time.) (Go check yours. Right now.)

54. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success. Demand more visibility for failure. Especially personal failures. Ensure alerting is configured to notify for job failures. (You laugh, but this gets missed all the freaking time.) (Go check yours. Right now.) (No, really.)

55. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #4: Demand Visibility for Success. Demand more visibility for failure. Especially personal failures. Ensure alerting is configured to notify for job failures. (You laugh, but this gets missed all the freaking time.) (Go check yours. Right now.) (No, really.) FAILSAFE: Monitors are better monitors than you are. Use them.

56. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #5: Don’t add new Backup Jobs for New VMs.

57. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #5: Don’t add new Backup Jobs for New VMs. (If you don’t get the joke, see Tip #2.) Use a backup solution that’s designed to handle organic growth.

58. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #5: Don’t add new Backup Jobs for New VMs. (If you don’t get the joke, see Tip #2.) Use a backup solution that’s designed to handle organic growth. This is particularly important in Private Cloud environments. You might not be creating VMs. How will you know that you need to back them up?

59. Five Failsafe VM Protection Tips (Ignore at your Peril) Tip #5: Don’t add new Backup Jobs for New VMs. (If you don’t get the joke, see Tip #2.) Use a backup solution that’s designed to handle organic growth. This is particularly important in Private Cloud environments. You might not be creating VMs. How will you know that you need to back them up? FAILSAFE: Ensure your backup solution backs up and monitors your virtual platform constructs, and not just a list of VMs. Datastores, folders, clusters, other objects

60. Five Tips, Safe Failing. Tip #1: Layers! Tip #2: Testing! Tip #3: Monitoring! Tip #4: Alerting! Tip #5: Automation!

61. Questions and Answers  Winners receive a choice of the following books  Thank you for attending!  Resources: ●Twitter @Veeam Blog: http://www.veeam.com/blog Eval: Veeam.comhttp://www.veeam.com/blog