Multi Site Clustering for Hyper-V disaster recovery - Greg Shields

667 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Multi Site Clustering for Hyper-V disaster recovery - Greg Shields

  1. 1. Multi-Site Clusteringfor Hyper-VDisaster Recovery<br />Greg Shields, MVP, vExpertSenior PartnerConcentrated Technology<br />www.ConcentratedTech.com<br />@ConcentratdGreg<br />
  2. 2. About the speaker<br />Over 15 years of Windows experience<br /><ul><li>Administrator– Managed environments ranging from a few dozen to many thousands of users…
  3. 3. Consultant – Hands-on and Strategic…
  4. 4. Speaker – TechMentor, Tech Ed, Windows Connections, MMS, VMworld, ISACA, others…
  5. 5. Analyst/Author – Fourteen books and counting…
  6. 6. Columnist – TechNet Magazine, Redmond Magazine,Windows IT Pro Magazine, TechTarget Online, others…
  7. 7. All-around good guy…</li></li></ul><li>What Makes a Disaster?<br />Which of the following would you consider a disaster?<br />Impacts your datacenter and causes damage. That damage causes the entire processing of that datacenter to cease<br />Interrupts the functionality of your datacenter for an extended period of time<br />It’s immediately ceasing all processing on that server<br />It causes problems with a service, shutting down that service and preventing some action from occurring on the server<br />It causes a server or an entire rack of servers to inadvertently and rapidly power down<br />
  8. 8. What Makes a Disaster?<br />Which of the following would you consider a disaster?<br />It’s immediately ceasing all processing on that server<br />Just a bad day…<br />It causes problems with a service, shutting down that service and preventing some action from occurring on the server<br />It causes a server or an entire rack of servers to inadvertently and rapidly power down<br />
  9. 9. What Makes a Disaster?<br />Your decision to “declare a disaster” and move to “disaster ops” is a major one<br />The technologies used for disaster protection are different than those used for high-availability<br /><ul><li>More complex
  10. 10. More expensive</li></ul>Failover and failback processes involve more thought<br /><ul><li>You might not be able to just “fail back” with a click of a button</li></li></ul><li>Multi-Site Hyper-V == Single-Site Hyper-V<br />Multi-site Hyper-V looks very much the same as single-site Hyper-V<br /><ul><li>Microsoft has not done a good job of explaining this fact!
  11. 11. Some Hyper-V hosts
  12. 12. Some networking and storage
  13. 13. Virtual machines that Live Migrate around</li></ul>But there are some major differences too…<br /><ul><li>VMs can Live Migrate across sites
  14. 14. Sites typically have different subnet arrangements
  15. 15. Data in the primary site must be replaced with the DR site
  16. 16. Clients need to know where your servers go!</li></li></ul><li>Constructing Site-Proof Hyper-V: Three Things<br />At a very high level, Hyper-V disaster recovery is three things<br />Once you have these three things, layering Hyper-V atop is easy.<br />Target <br />Servers & <br />Cluster<br />Storage <br />mechanism<br />Replication<br />mechanism<br />
  17. 17. Constructing Site-Proof Hyper-V: Three Things<br />Replication Mechanism<br />Storage Device(s)<br />Target Servers<br />
  18. 18. Thing 1: A Storage Mechanism<br />Typically, two SANs in two different locations<br />Backup SAN doesn’t necessarily need to be of the same size or speed as the primary SAN<br />FibreChannel,<br />iSCSI,<br />FCoE, <br />heck JBOD<br />Replicated <br />≠<br />Full data<br />(not always)<br />Similar model<br />or<br />manufacturer<br />DR <br />– not for <br />everything!<br />Similarity <br />proper<br />replication<br />DR Environments: <br />Where Old SANs <br />Go To Die!<br />
  19. 19. Want more?<br />See the rest and watch more training videos at www.backupacademy.com<br />

×