{"id":12536,"date":"2012-05-14T19:23:09","date_gmt":"2012-05-14T18:23:09","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=12536"},"modified":"2012-05-14T19:23:09","modified_gmt":"2012-05-14T18:23:09","slug":"choosing-a-windows-server-2012-hyper-v-dr-architecture","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=12536","title":{"rendered":"Choosing A Windows Server 2012 Hyper-V DR Architecture"},"content":{"rendered":"<p>I must be nuts; we\u2019re a nearly month from the release candidate and I\u2019m attempting to blog on this stuff <img decoding=\"async\" style=\"border-bottom-style: none; border-left-style: none; border-top-style: none; border-right-style: none\" class=\"wlEmoticon wlEmoticon-smile\" alt=\"Smile\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/wlEmoticon-smile3.png\" \/><\/p>\n<p>I\u2019ve been thinking a lot about DR and how to approach it with Windows Server 2012 Hyper-V.&#160; There is no one right solution.&#160; In fact, we have lots and lots of options thanks to VMs just being files.&#160; Yup, thanks to VHDX scaling out to 64 TB, the last reasonable reason to use passthrough disk (other than to get that last 2 or so percentage points of performance) are dead.&#160; That makes even the biggest of VMs \u201ceasy\u201d to replicate.<\/p>\n<p>Let\u2019s look at 2 approaches from a very high altitude level.&#160; An approach I\u2019m seeing quite a bit for cross-campus or short range DR plans is to build a stretch cluster.&#160; The usual approach is to use something like a HP P4000 SAN and stretch it between two sites.&#160; A single Hyper-V cluster is built, stretching across the WAN link.<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/image.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-bottom: 0px; border-left: 0px; padding-left: 0px; padding-right: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px; padding-top: 0px\" title=\"image\" border=\"0\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/image_thumb.png\" width=\"504\" height=\"166\" \/><\/a><\/p>\n<p align=\"center\"><em>SAN-SAN replication<\/em><\/p>\n<p>It\u2019s not a cheap solution and it comes with complexities \u2013 and that\u2019s true no matter what virtualisation you use:<\/p>\n<ul>\n<li>You have to choose a storage solution that stretches across sites and can do active\/active.&#160; You are locked into a single spec across both sites, making the hardware sales people very happy.<\/li>\n<li>You probably need a witness for the storage and the virtualisation cluster in a 3rd site, with site A and site B having independent network access to the witness site to avoid split brain when the link between A and B fails (and it will fail).<\/li>\n<li>Some high end storage solutions won\u2019t like CSV for this and you might need to so 1 VM per LUN<\/li>\n<li>The networking (IP redirect, stretched VLANs, routers, switches, and all that jazz) is messy.<\/li>\n<li>The WAN for this is mega pricey.<\/li>\n<li>Honestly, a stretch Hyper-V cluster doesn\u2019t play well with System Center Virtual Machine Manager \u2013 VMM just sees a single cluster and doesn\u2019t care about the WAN link or the impact on backup, client\/server app interaction, and so on.<\/li>\n<li>If you want to replicate to a hosting company then you need colo hosting and to place hardware in rented rackspace.<\/li>\n<li>Once a VM is created in a replicate LUN, it\u2019s replicated to site B.&#160; That\u2019s pretty nice in a cloud.<\/li>\n<li>When everything works it\u2019s a pretty fine solution, capable of having 0 data loss.&#160; But corruption in site A will replicate to site B because this SAN likely has synchronous replication.<\/li>\n<\/ul>\n<p>The above solution is something I see more and more, even in medium sized sites.&#160; It\u2019s complex, it\u2019s pricey, and very often they are struggling with getting it to work even in testing, let alone in the worst day of their professional careers.<\/p>\n<p>I recently listed to a RunAs Radio podcast where the guest spoke about his preference for VMware SRM for DR replication.&#160; I can understand why.&#160; Software replication can stretch much greater distances.&#160; You aren\u2019t as beholden to the storage vendor as before.&#160; <a href=\"https:\/\/aidanfinn.com\/?p=12147\" target=\"_blank\">Hyper-V Replica<\/a> is surely going to have the same impact \u2026 and more \u2026 without costing you hundreds of dollars\/euros\/pounds\/etc on a per VM basis like SRM does:<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/image1.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-bottom: 0px; border-left: 0px; padding-left: 0px; padding-right: 0px; display: block; float: none; margin-left: auto; border-top: 0px; margin-right: auto; border-right: 0px; padding-top: 0px\" title=\"image\" border=\"0\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/image_thumb1.png\" width=\"504\" height=\"229\" \/><\/a><\/p>\n<p align=\"center\"><em>Hyper-V Replica<\/em><\/p>\n<ul>\n<li>Hyper-V is hardware independent.&#160; You can replicate from a host to a host, from a cluster to a host, or from a host to a cluster.&#160; You can replicate from a HP cluster with a P4000 to a bunch of Dell hosts with a Compellent.<\/li>\n<li>Hyper-V Replica is built for unstable WAN connections.&#160; It cannot automatically failover \u2026 in fact, many of us prefer a manual decision on failover.&#160; We can reduce the RTO by automating VM start up using PowerShell and\/or Orchestrator in the DR site.&#160; The storage ni both sites is independent.&#160; No need for 3rd party witnesses and their networking.<\/li>\n<li>VMs are replicated instead of LUNs, therefore CSV is fully supported.&#160; You can replicate VMs from a CSV in site A to a CSV or a normal LUN in site B.<\/li>\n<li>Networking is easy!&#160; And you have options!&#160; The pipe for the replica probably either should be dedicated or have QoS to allow replication without impacting normal Internet connectivity.&#160; Because the replication is asynchronous, the WAN doesn\u2019t need massive bandwidth and low latency.&#160; You can choose to stretch VLANs, or you might not.&#160; You might use Network Virtualisation in site B or you might use IP address injection to change the VMs\u2019 IP addresses for the destination network.&#160; By the way, you can also dedicate a virtual switch(es) for firing up test copies of your VMs for DR testing.<\/li>\n<li>Hyper-V Replica is built for commercial broadband.&#160; Remember that your upload speed is the important factor.&#160; Sizing is tricky \u2026 I\u2019ve been saying that you could take your incremental backup and divide it by the number of 5 minute windows there are in your workday to figure out how much bandwidth Hyper-V Replica will require to replicate every 5 minutes \u2026 but that\u2019s worst case because there is pre-transmit compression going on.<\/li>\n<li>Hyper-V Replica is not a stretch cluster \u2026 therefore systems management solutions such as VMM will play nice by keeping it\u2019s placement of VMs local in site A.<\/li>\n<li>Your hardware options are very flexible.&#160; You could replicate to hardware you own in a branch\/head office or datacenter, you could rent rackspace and put hardware in colo hosting, or you could replicate to a hosting partner that hosts Hyper-V Replica.<\/li>\n<li>There just aren\u2019t as many delicate moving parts in this architecture.&#160; You pretty much have 2 simple independent infrastructures where 1 copies compressed differential data to another.<\/li>\n<li>Hyper-V Replica is configured on a per-VM basis.&#160; PowerShell can do this \u2013 I\u2019ve already seen examples posted online.&#160; You could probably make this a part of the Orchestrator runbook in a cloud implementation.&#160; So a little more work is requires but you can fire it and forget.<\/li>\n<li>Best of all, Hyper-V Replica is a tick box away in Hyper-V.&#160; Yup, zero dollars, nada, keine kosten, gratuito, free.&#160; Of course, you are free to continue wearing a tinfoil hat and paying vTax \u2026. <img decoding=\"async\" style=\"border-bottom-style: none; border-left-style: none; border-top-style: none; border-right-style: none\" class=\"wlEmoticon wlEmoticon-smilewithtongueout\" alt=\"Smile with tongue out\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/wlEmoticon-smilewithtongueout.png\" \/><\/li>\n<\/ul>\n<p><img decoding=\"async\" style=\"display: block; float: none; margin-left: auto; margin-right: auto\" src=\"http:\/\/scienceblogs.com\/startswithabang\/upload\/2009\/04\/weekend_diversion_do_tinfoil_h\/tinfoil-hat.jpg\" \/><\/p>\n<p align=\"center\"><em>Clinging to his overpriced DR with his cold dead hands because he thinks Stevie B. wants to steal his brainwaves<\/em><\/p>\n<p><div style=\"padding-bottom: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: none; padding-top: 0px\" id=\"scid:0767317B-992E-4b12-91E0-4F059A8CECA8:4c7bdd66-edd6-4bf2-ab0d-080f421ad3e7\" class=\"wlWriterEditableSmartContent\">Technorati Tags: <a href=\"http:\/\/technorati.com\/tags\/Windows+Server+2012\" rel=\"tag\">Windows Server 2012<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Hyper-V\" rel=\"tag\">Hyper-V<\/a>,<a href=\"http:\/\/technorati.com\/tags\/DR\" rel=\"tag\">DR<\/a><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I must be nuts; we\u2019re a nearly month from the release candidate and I\u2019m attempting to blog on this stuff I\u2019ve been thinking a lot about DR and how to approach it with Windows Server 2012 Hyper-V.&#160; There is no one right solution.&#160; In fact, we have lots and lots of options thanks to VMs &hellip; <a href=\"https:\/\/aidanfinn.com\/?p=12536\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Choosing A Windows Server 2012 Hyper-V DR Architecture&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[20],"tags":[61,181,118],"class_list":["post-12536","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-dr","tag-hyper-v","tag-windows-server-2012"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/12536","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=12536"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/12536\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12536"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12536"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12536"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}