Windows Server 2012 and the FREE Hyper-V Server 2012 include Hyper-V Replica as a new disaster recovery feature for site-level outages. Hyper-V Replica provides asynchronous host-to-host replication between sites for Virtual Machines.
For more details on implementing and automating disaster recovery with Hyper-V Replica, please see my prior post on this topic HERE.
Planning Network Bandwidth for Hyper-V Replica
By using asynchronous replication across a standard IP network connection between sites, Hyper-V Replica can provide a very quick (within seconds or minutes) Recovery Time Objective ( RTO ). However, when discussing disaster recovery with IT Pros, often times the conversation turns to planning for network bandwidth between sites to meet Recovery Point Objectives ( RPO ). My friend and colleague, Tommy Patterson, has authored a great step-by-step article and a planning tool on his "virtuallycloud9" blog as guidance for determining network bandwidth requirements when using Hyper-V Replica.
Tommy's article covers:
Be sure to check out this great article on Tommy's blog!
CLICK HERE TO READ THIS ARTICLE!
In this article, we walked through examples of the PowerShell 3.0 Cmdlets that you can leverage to easily implement an enterprise disaster recovery solution using Windows Server 2012 and Hyper-V Replica. To continue your learning, check out these resources next ...
How Are You Using Hyper-V Replica?
Have you found a unique and interesting use case for Hyper-V Replica and/or PowerShell 3.0? Be sure to share your story in the comments below!
Like this article? Subscribe to "IT Pros ROCK!" and stay up-to-date!