{"id":14154,"date":"2013-02-01T12:59:53","date_gmt":"2013-02-01T12:59:53","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=14154"},"modified":"2013-02-01T12:59:53","modified_gmt":"2013-02-01T12:59:53","slug":"an-interesting-use-for-hyper-v-replica","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=14154","title":{"rendered":"An Interesting Use For Hyper-V Replica"},"content":{"rendered":"

I just saw a tweet that talked about using Hyper-V Replica for verification.  Huh?<\/p>\n

Consider this: you have a production VM running.  You have a change control process that demands that you test upgrades and rollback plans to systems before you implement those changes.  Building new VMs can be time consuming \u2013 forget the template copy process \u2013 consider the time it takes to copy databases, install updates, and so on.<\/p>\n

You could shut down the VM and copy it.  There\u2019s some downtime there.  You could backup and restore the VM \u2026 just make sure it\u2019s on an isolated network.<\/p>\n

You could use Hyper-V Replica.  No downtime is required to get the copy running.  You can do the initial copy via removable (optionally encrypted) media if you need to do the test offsite, and use SSL authentication if the test environment is in a different AD forest\/company.  Maybe you already have Hyper-V Replica in place and a cold offline replica of the desired VM exists on a host in the DR site.<\/p>\n

Test Failovers will:<\/p>\n