Friday 26 March 2010

Updating Procedure for Hyper-V Cluster Nodes

To update the nodes running the Hyper-V Server 2008 R2 OS underneath it all, there are a couple of steps that need to happen before any updates can be applied.

  1. Live Migrate any VMs running on the node to be updated to another node.
  2. Migrate any cluster storage controlled by the node to be updated to another node.

To date, we have been using the native Hyper-V Management console along with the Failover Clustering Management (FCM) console to manage our Hyper-V based clusters.

We have not jumped into Virtual Machine Manager yet.

Once the node is cleared of any resources, run the needed updates on the node proper via direct KVM session.

In the case of the Intel Modular Server (IMS)*, the IMS’s Web management has a KVM facility built into it that is Java driven.

Once the node has completed its reboot cycle and shows as Online in the FCM, test Live Migrate a non-critical VM back onto the node to make sure everything is running as expected.

With that test complete, Live Migrate VMs and storage back onto the node.

Repeat for each node.

Philip Elder
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*The Intel Modular Server we are currently using has been graciously provided to us by Intel for demo and learning purposes.

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

No comments: