• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 454
  • Last Modified:

URGENT - Setting Up Hyper-V cluster

We will have 2 Dell PE R610 with Dell SAN MD3000i, both VM hosts running W2k8 R2 with Hyper-V role

What are the most critical areas of the setup I need to be concerned about?

I think the Cluster Manager which would be one of the Hyper-V host must be joined to the domin?

Do I need a third W2k8 R2 server Ent or St to manage the two Hyper-V hosts?
0
piotrmikula108
Asked:
piotrmikula108
  • 5
  • 3
3 Solutions
 
v-2vishpCommented:
Once you have joined the both the servers to the domain and added the role of Hyper V on it. Now proceed with introducing the SAN to window. Are you planning to setup CSV for live migration ? Once the disks show up in the disk management now start with the cluster validation ( i am assuming that you have setup at least two VMs with the network also configured), if the current configuration clears the validation that will be great else proceed with troubleshooting the errors and warning until we have least permissible warnings. Yes you will need a third server if you want to manage the cluster as the Failover Cluster Administrator is not available on a client level os not even as a add on. else you can RDP in any of the two servers and manage the cluster. Hope this helps.
0
 
piotrmikula108Author Commented:
thx, so I don't need a third server to only simply manage the two nodes, I'm ok with managing the cluster from one of the nodes. So that means if one of the servers goes down the other one will take over the roles of running the VMs (as well as the clustering) from the other host? Does it matter which node is the cluster manager?
0
 
piotrmikula108Author Commented:
can one of the existing physical boxes be the cluster manager if it runs only Windows Server 2008 Standard (not R2 even)
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
kevinhsiehCommented:
To do administration of hosts running Windows 2008 R2, you should administer from Windows 2008 R2 or Windows 7. The actual monitoring of the cluster and failover operations is done by the cluster itself, not a designated node. There is no "cluster manager" node.
0
 
piotrmikula108Author Commented:
kevinhsieh, thx for the calrification
0
 
piotrmikula108Author Commented:
can the cluster manager be installed on Windows 2008 Standard and how?
0
 
piotrmikula108Author Commented:
also my existing Dell R610 has dual E5620, the new server will have X5660. Will that introduce problems?

I looked up the differences between E5620 and X5660, they are slightly different as far as:
-      # cores
-      #of treads
-      Clock speed of course
-      Max turbo frequency
-      Bus/core ratio
-      Intel QPI Speed (not so important?)
-      Max TPD  (not so important?)
-      Memory types (not so important?)
-      Max Memory bandwidth (not so important?)
-      Tcase (probably irrelevant)

However they are at the same Instruction Set Extensions SSE4.2 is that the most important factor maybe?
0
 
kevinhsiehCommented:
A windows 2008 or Vista machine can not properly manage a Windows 2008 R2 cluster because it doesn't understand the R2 capabilities. My experience is that the Cluster management tool won't even connect. The Hyper-V Manager will, but it can't manage the R2 features. You need to use Windows 7 or Windows 2008 R2. To install the management tools, add it under Windows Features. On Windows 7, download and install RSAT.
0
 
kevinhsiehCommented:
I have 1950, 2950, R610 and R710 machines in my cluster running a variety of Intel processors. I enable processor compatability and don't worry about it.

http://www.microsoft.com/hyper-v-server/en/us/faq.aspx

Q.  Assuming host nodes have a virtualization capable processor from the same manufacturer, can I migrate a VM from a host using an older processor to a host with a newer processor?

A.  
It is highly recommended to use identical processors on all nodes of a cluster using Quick or Live Migration.

Live Migration or Quick Migration will work moving VMs from and older processor to a newer processor. However, to migrate a VM from a newer processor to an older processor, the VM must be turned off and restarted after moving the VM.

A new functionality is the “Processor Compatibility” option. This functionality can be enabled for VMs to allow both Live Migration and Quick Migration from newer to older processors from the same manufacturer.

The setting is under VM settings > Processor > “Migrate to a physical computer with a different processor version”.

You can live migrate or quick migrate a running VM from an older processor to new processor and back without the “Processor Compatibility” option as long as the VM is running all the time.


0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now