Solved

How to Perform Maintenace on Microsfot Cluster Nodes

Posted on 2013-01-21
1
249 Views
Last Modified: 2013-03-31
Currently we have 3 nodes in our cluster and a group of virtual servers using Hyper-V.  We are using a shared store from a SAN and we have created 3 volumes (Cluster Disk 1, Cluster Disk 2, and Cluster Disk 3) At the beginning we migrated the VM’s to Cluster Disk 2   and setup VM's for high availability. However, after the migration we noticed that under Failover Cluster Manager only show the name of the first machine and the rest are nested or child object. Then we enabled Cluster Share Volumes and assigned Cluster Disk 3 to it and we created new VM's using the failover Cluster Manager and place them on node3.  Our challenge is how we can perform automatically maintenance on the nodes and when the servers reboot all VM’s dot not go to a single node (e.g. Node1), we need keep those VM’s on different nodes for to avoid overload on a single server.
Thanks you in advance for your help
0
Comment
Question by:Holguer
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 28

Accepted Solution

by:
Ryan McCauley earned 500 total points
ID: 38806435
I'm not sure I completely understand the issue, but from what I do, it sounds like you're looking to set a failover pattern on your VMs (so that they fail from A -> B -> C -> A), as well as setting a host preference (VMs 1 and 2 prefer node A, 3 and 4 prefer node B, and 5, 6, and 7 prefer C, for example). Though I've never set this up, it looks like it's pretty common - here are a few articles that talk about it:

Preferred owners on a cluster:
http://blogs.msdn.com/b/clustering/archive/2008/10/14/9000092.aspx

Hyper-V Clustering: Virtual Machine Failover Behavior:
http://blogs.technet.com/b/mattmcspirit/archive/2009/02/03/hyper-v-clustering-virtual-machine-failover-behaviour.aspx

You should be able to set up your VMs to prefer nodes so that they're evenly split across your cluster, as well as node failover patters so that they move to different nodes evenly in case there's a node failure.
0

Featured Post

The Ultimate Checklist to Optimize Your Website

Websites are getting bigger and complicated by the day. Video, images, custom fonts are all great for showcasing your product/service. But the price to pay in terms of reduced page load times and ultimately, decreased sales, can lead to some difficult decisions about what to cut.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question