Q

Hyper-V Replica improves fault tolerance without a failover cluster

Are you looking for a cheaper alternative to a failover cluster? Windows Server 2012 includes a new feature, Hyper-V Replica, that can be an effective substitute.

I can't afford to build a failover cluster. Are there any other options for providing fault tolerance?

Historically, the only way to make Microsoft Hyper-V virtual machines fault tolerant was to build a host server cluster. The problem with using failover clustering was that it required the use of a Cluster Shared Volume (CSV), which is expensive, to say the least. This requirement put Hyper-V clustering beyond the financial reach of many small and medium-sized businesses.

Windows Server 2012 offers some lower cost alternatives to traditional Hyper-V clustering. One of the biggest changes that Microsoft has made in the new version is to remove the requirement for clusters to depend on a CSV. It is now possible to build a failover Hyper-V cluster without using shared storage. All you need is enough local storage in each cluster node to accommodate the VMs.

Another option is something called Microsoft Hyper-V Replica. Replication is similar to clustering, but it isn't a true clustering solution. When Hyper-V Replica is enabled, VMs (or rather the virtual hard drives that make up the VMs) are replicated from one Hyper-V host to another. The replica doesn't provide the same level of failover protection that a true cluster does, but you can manually perform both planned and unplanned failovers.

Another nice thing about the Hyper-V Replica feature is that you can create replicas using a minimum of two servers (a source server and a target server). Failover clusters require a minimum of three servers (either three cluster nodes or two cluster nodes and a file share witness). Being able to create a replica based on only two servers helps to reduce costs compared to failover clustering.

Next Steps

New VM replication tool for IT shops

Disaster recovery options for SMBs

Hyper-V Replica takes center stage at WPC 2011

This was last published in December 2012

Dig Deeper on Disaster recovery, failover and high availability for virtual servers

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

A Hyper-V replica is for disaster recovery.

You are pretty much guaranteed to lose data when you rely on Hyper-V replicas. Hyper-V makes a sort of snapshot of the data every 5 minutes and copies the differences asynchronously to the other machine/location. If it can't copy the data, it will try again later. So if you copy offsite and you don't have enough bandwidth you'll lose more than 5 minutes of changes.
Cancel

-ADS BY GOOGLE

SearchVMware

SearchWindowsServer

SearchCloudComputing

SearchVirtualDesktop

SearchDataCenter

Close