Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

re: Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

bday — Sat, 13 Jun 2009 01:35:21 GMT

Is it safe to say you're upgrading the node without any active resources on it at that time?

re: Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

msclustm — Sat, 13 Jun 2009 01:38:34 GMT

Correct, you should move any active resources off the node before you upgrade so you can gracefully fail them over. However if you do an upgrade with resources still on the node, it should still work as the resources will failover during the upgrade, but it has not been tested, so we would recommend the safer experience with the planned failover.

Thanks!

Symon

Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering from RTM

Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering from RTM — Sat, 13 Jun 2009 14:15:27 GMT

PingBack from http://www.ditii.com/2009/06/13/rolling-upgrade-to-windows-server-2008-sp2-failover-clustering-from-rtm/

re: Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

sqldba — Sat, 13 Jun 2009 20:50:11 GMT

There is an issue when you install Windows 2008 SP2 remotely, if you have RDP to the server. your installation shows installing physicaly standing at the front of servers.After RDPing to server & once SP2 starts installing your connection is lost, Microst should maintain connection &Admin shouldn't use 3rd party software to connect Server using KVM over IP.

I think Microsoft should address this if you are installing remotely.

Thanks

Jay

Clustering and High Availability Rolling Upgrade to Windows Server | wheelbarrow

Clustering and High Availability Rolling Upgrade to Windows Server | wheelbarrow — Sun, 14 Jun 2009 07:19:02 GMT

PingBack from http://wheelbarrowstyle.info/story.php?id=1537

re: Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

msclustm — Mon, 15 Jun 2009 20:01:11 GMT

Losing your remote desktop connection is expected when the machine reboots during installation (or any time a machine reboots). This does not impair any functionality. Once the machine is upgraded you will be able to reconnect via remote desktop using the same credentials and machine information. The steps documented above were performed entirely using remote desktop.

Thanks,

Symon

Clustering and High Availability Rolling Upgrade to Windows Server | patio umbrella

Thu, 18 Jun 2009 07:00:12 GMT

PingBack from http://patioumbrellasource.info/story.php?id=2835

Clustering and High Availability : Rolling Upgrade to Windows … | Windows (7) Affinity

Tue, 23 Jun 2009 23:02:13 GMT

PingBack from http://www.windowsaffinity.com/?p=2441

re: Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

ronmac — Wed, 26 Aug 2009 20:45:06 GMT

You mention "A best practice is to also pause the node(s) you are about to upgrade by right-clicking the node name and selecting 'Pause'." Have you tried this? In fact you will see that you can't install the service pack onto a node that is paused. You will get the following error during the validation

checks:

"The machine is clustered, but the cluster is not online or cannot be

accessed from one of its nodes. To continue determine why the cluster is not

online and rerun setup instead of rerunning the rule since the rule can no

longer detect a cluster environment correctly."

So what is the best practice?

Thanks,

Ron

re: Rolling Upgrade to Windows Server 2008 SP2 Failover Clustering

msclustm — Wed, 26 Aug 2009 22:57:08 GMT

Hi Ron,

Great question. You will want to run Validation *after* you have updated all of your nodes. Ideally you want to get out of this 'mixed mode' cluster as quick as you can as the cluster may not be as stable during this time (and running Validation will mean you're in mixed mode for even longer).

Once you have upgraded all the nodes and they're online (not paused), Validation will complete successfully.

Thanks,

Symon Perriman

Program Manager

Clustering & HA