Throughout our Disaster Recovery Planning Series for IT Pros this month, we’ve been discussing the steps involved in planning an effective Disaster Recovery strategy … And planning for the additional capacity needed to implement a successful DR plan is certainly an important part of that process. Replicating application workloads and data between sites can incur additional CPU, Memory, Storage and Network overhead that we’ll need to account for as part of our datacenter and wide area network load. If you’re using our native Hyper-V Replica engine as part of your DR strategy, the good news is that our Solution Accelerators team has built a tool to help us predict the capacity needed for these DR scenarios: the Hyper-V Replica Capacity Planner tool.
The Hyper-V Replica Capacity Planner tool was updated this past month with a new version that adds several new features, including support for Windows Server 2012 R2, Hyper-V Replica Extended Replication and new storage support for virtual hard disks located on CSVFS volumes and SMB shares.
The Hyper-V Replica Capacity Planner tool was updated with a new version that adds several new features, including support for Windows Server 2012 R2, Hyper-V Replica Extended Replication and new storage support for virtual hard disks located on CSVFS volumes and Scale-out File Server (SoFS) SMB shares.
Hyper-V Replica is our included asynchronous site-to-site VM replication engine for our bare-metal Hyper-V hypervisor in Windows Server 2012 and 2012 R2. Using Hyper-V Replica, you can quickly implement a cost-effective disaster recovery plan for your business critical VMs without the high costs involved in traditional DR solutions – you just need a Hyper-V host and/or cluster at each site and an IP WAN or Internet connection between them. No expensive shared storage or extra licenses are required!
Get familiar with Hyper-V Replica:
For a quick primer on implementing and using Hyper-V Replica, check out these articles:
- What’s New in Hyper-V in Windows Server 2012 R2
- Hyper-V Replica Overview from TechNet Library
- Step-by-Step: Configuring & Using Hyper-V Replica by Kevin Remde
- Step-by-Step: Automated Disaster Recovery with Hyper-V Replica and PowerShell 3.0 by Keith Mayer
- Step-by-Step: Planning RPO and WAN Bandwidth for Hyper-V Replica by Tommy Patterson
- Guided Hands-on Lab: Deliver Disaster Recovery as a Service (DRaaS) with Windows Azure HRM
How much Host and Network Capacity Do I Need?
When evaluating Hyper-V Replica, we need to plan for additional host and network capacity to ensure that ongoing replication is able to successfully communicate changes to our replicated VMs at our DR sites. Recently, we released an updated version of our free Capacity Planner for Hyper-V Replica to assist in planning for the capacity needed in VM replication scenarios, with added support for new Hyper-V Replica features in Windows Server 2012 R2. After downloading and running this tool, a comprehensive report is prepared that shows CPU, RAM, Disk and Network capacity needed to successfully support your specific configuration and environment.
Get started with Hyper-V Replica:
To get started with building your Hyper-V Replica lab, you’ll need to install and configure a minimum of two hosts or host clusters running either our Hyper-V bare-metal hypervisor in Windows Server 2012 or 2012 R2. Below, I’ve included a list of resources to help you get started:
- DOWNLOAD: Microsoft Private Cloud Evaluation Kit with Windows Server 2012 R2
- DOWNLOAD: FREE Hyper-V Server 2012 R2
- BUILD: Windows Server 2012 Hyper-V Hosts with the “Early Experts” Virtualizer Quest
- BUILD: Hyper-V Server 2012 R2 Host
- CONFIGURE: Hyper-V Replica using Windows Server 2012 R2 Hyper-V Manager by Kevin Remde
- CLUSTER: Build a FREE Hyper-V Server 2012 R2 Host Cluster
- CLUSTER: Configure Hyper-V Replica Broker in a Cluster by Yung Chou