Many of us have delayed installing Windows Server 2008 R2 SP1 on HP ProLiant Servers until guidance from HP became available. While writing my blogpost Preparing for upgrading your Hyper-V R2 cluster to SP1 about two months ago I was unable to find any details. Searching for an updated BladeSystem Matrix Compatibility guide, I stumbled upon the long expected HP Integration Note: Implementing Microsoft Server 2008 R2 Service Pack 1 on HP ProLiant and Integrity servers.
Posts tagged upgrade
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:
- Hyper-V Dynamic Memory Configuration Guide:
- 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:
- Here is the link to SP1 itself:
More often than not Service Pack upgrades go without any problems but if you are unlucky things can get really bad.
My fellow Cluster MVP, Robert Smit (also from the Netherlands) came across a failed SP1 upgrade ending with 0x800705b4 and 0x80070643. The end of the game is that your server is lost and you have to forcibly test your recovery plan.
If your server is part of a cluster and you have not used up too many resources and fully consumed your cluster reserve you may be able to remove the troublesome node from the cluster.
The primary lesson is: “don’t upgrade all your servers simultaneously”
Just upgrade one and see how that one goes. If the SP1 upgrade was successful, upgrade the next.
For the full story read Roberts blog at:
Back in August I wrote a blog on upgrading a Hyper-V cluster to Hyper-V R2. Microsoft has now officially published documentation on upgrading Hyper-V clusters to Hyper-V R2:
Other documentation available on the following migration to R2 topics:
Migration from R2 RC to R2 RTM:
DHCP Migration from 2003 or 2008 to R2: