Solved

How to Perform Maintenace on Microsfot Cluster Nodes

Posted on 2013-01-21
1
245 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
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

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

707 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now