Powered by System Center
// Main banner ad on homepage
Preparation for upgrading your Hyper-V R2 cluster to SP1
Here are a few good links documenting the upgrade of Hyper-V R2 clusters to SP1 including a list of updates and hotfixes related to this combination. Please also read the warning at the end!
- Upgrading a Hyper-V R2 Cluster to Windows Server 2008 R2 SP1: http://workinghardinit.wordpress.com/2011/02/17/upgrading-a-hyper-v-r2-cluster-to-windows-2008-r2-sp1/
- Hyper-V Failover Cluster Step-by-Step Guide Rolling Upgrade SP1:
http://ramazancan.wordpress.com/2011/03/07/hyper-v-failover-clusterstep-by-step-guide-rolling-upgrade-sp1/ - Hyper-V Dynamic Memory Configuration Guide:
http://technet.microsoft.com/en-us/library/ff817651(WS.10).aspx - Make sure you run Cluster Validation after the upgrade of all cluster nodes has finished: http://technet.microsoft.com/en-us/library/cc726064.aspx
- FAQ Dynamic Memory and RemoteFX (Windows Server 2008 R2 SP1): http://kristiannese.blogspot.com/2011/02/faq-dynamic-memory-and-remotefx-windows.html
- Windows 2008 R2 SP1 general availability and what it means for Exchange: http://blogs.technet.com/b/exchange/archive/2011/02/11/3411983.aspx
- Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment:
http://support.microsoft.com/kb/956893 - Here is the link to SP1 itself:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda
The following spreadsheet filters updates and hotfixes for Hyper-V and Cluster:
WARNING AND DISCLAIMER:
I would like to stress that upgrading to SP1 is not something that should be taken lightly. Make sure your backups are secure and you know you can restore those backups.
So far our test upgrades have been fairly easy and without any problems. Cluster Validation completed 100% successfully. We are using HP Blade Servers and HP EVA 4400 storage in our testing environment.
I also advise you to make an upgrade plan before performing the actual upgrade. Read all the stuff you can get and document current configuration and check which guests must be upgraded depending on their workloads.
Several reports have reached me with cluster validation errors after the upgrade. If you get these, leave a comment under this blog (with a short description of your server/storage config).
See also this thread on the Windows Server – High Availability (Clustering) Forum about the Cluster Validation errors with SP1:
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/e67026af-7f9b-4698-9ca7-11853431ed86/
Update 3/29/2011: Problem has been acknowledged by Microsoft. They are working hard to create a fix as soon as possible
| Print article | This entry was posted by Hans Vredevoort on March 18, 2011 at 17:25, and is filed under Hans Vredevoort, Hyper-v. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
Twitter
RSS
about 2 years ago
Cluster validation fails after installing WIN2008R2 SP1 on first node
Hi Hans,
After installing Windows Server 2008 R2 SP1 on the first of 5 nodes in our Hyper-V cluster I ran the cluster validation on this node. Before I upgraded this node to SP1 the cluster validation passed all test but after installing SP1 I get several failures under Storage.
List Potential Cluster Disks
Disk with identifier 346c3449 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Disk with identifier 346c3446 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Disk with identifier 346c3447 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Disk with identifier 346c3444 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Disk with identifier e3d87bb6 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Disk with identifier b5ebe3a5 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Disk with identifier ca638220 has a Persistent Reservation on it. The disk might be part of some other cluster. Removing the disk from validation set
Validate Microsoft MPIO-based disks
Versions of DSM named Microsoft DSM, installed on nodes hprv-01 and hprv-02. do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-01 and hprv-03 do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-01 and hprv-04 do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-01 and hprv-05 do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-02 and hprv-01 do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-03 and hprv-01 do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-04 and hprv-01 do not match
Versions of DSM named Microsoft DSM, installed on nodes hprv-05 and hprv-01 do not match
Indicates two revision levels are incompatible
Validate SCSI device Vital Product Data (VPD)
An error occurred while executing the test.
Specified argument was out of the range of valid values.
Parameter name: percentage
Have you seen this before and can you give me an advise about what to do
about 2 years ago
Jeroen,
This is exactly what I was looking for. We are monitoring this and will update as soon as possible. If you get the validation errors these will be in clusters with 3 or more nodes.
Hans