Quick links to help you solve clustering problems

Have you ever wondered what the ideal number of virtual clusters is for your environment? Find out the magic number and more with these links.

Hypervisor vendors always provide a maximum number of virtual clusters, but what is the ideal amount? Knowing how to find that magic number is just one of many important tidbits that users should know about clustering. It's also vital to know how to fix Hyper-V -- as well as VMware and XenServer -- clustering problems.

Cluster Shared Volumes considerations and virtual storage decisions
Setting up a Hyper-V cluster to use Cluster Shared Volumes properly might be simple, but there are a handful of precautions to take and details to consider to avoid storage bottlenecks. Without the right storage plan, virtual machine (VM) performance can suffer. Choosing the right number of Cluster Shared Volumes and avoiding disk contention are just two ways to keep your VM running at a high level. What other decisions can you make to prevent your VM from lagging?

How to fix Microsoft Hyper-V clustering problems
There are a lot of reasons that you might experience Hyper-V clustering problems, including hardware, drivers, patches and configuration issues. They can cause lagging and instability issues for your clusters, but there are ways to fix that. Disabling automatic server recovery and managing firmware, patches and drive updates are just some ways to fix your Microsoft Hyper-V VM clustering problems.

The magic number of virtual server clusters
The maximum number of hosts running on a Microsoft Hyper-V Server is 16 while the maximum number in a VMware server cluster that's running vSphere 4.1 is 32. It's not a good idea to max out the size of your virtual server cluster, but a cluster with a small number of hosts can waste resources. So what is the magic number for virtual server clusters? Find out where the middle ground is and if that number is a good fit for you.

Do you have the right disaster recovery option picked out for you company?

And how do you know it's the right one for you? Disaster recovery plans are key to shortening downtime and getting everything back to normal. Learn about the pros and cons of Hyper-V Recovery Manager and find the right disaster recovery option for your company with these links. 

Make the right disaster recovery option to fit your needs
irtual infrastructures continue to grow and become more complex and more companies are turning to multiple hypervisors. It can be difficult to stay on top of all of the changes and plan for what you need to do to protect your data center. But, luckily, as the environment grows, so do the choices. Businesses should start weighing disaster recovery options and choosing an approach that fits their needs.

The advantages and limitations of Hyper-V Recovery Manager
Microsoft's Hyper-V Recovery Manager coordinates the protection of Hyper-V VMs located inside your private cloud for disaster recovery purposes. It's able to back up VMs from a primary data center to a secondary one and automates the failover process to bring workloads back up on the secondary site. But, it also has drawbacks that may not make the automation worth the added cost.

This was first published in May 2014
This Content Component encountered an error

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchVMware

SearchWindowsServer

SearchCloudComputing

SearchVirtualDesktop

SearchDataCenter

Close