Rolling Upgrade Walkthrough
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
This walkthrough covers the rolling upgrade of a Windows 2000 Advanced Server based cluster to Windows Server 2003 Enterprise Edition. For the latest information about rolling upgrades, please refer to the on-line help and the release notes on the Windows Server 2003 Enterprise Edition CD.
Prepare a list of all resources.
Identify resources that do not support rolling upgrades.
If you have a resource that does not support rolling upgrades, you have three choices:
Take the resource offline and continue with the rolling upgrade. The resource will be unavailable during the entire rolling upgrade process. You will have to bring this resource online once all nodes have been upgraded.
Remove the resource. The resource will be unavailable during the entire rolling upgrade process. You will have to reinstall this resource once all nodes have been upgraded.
If the majority of the resources do not support rolling upgrades, you may consider upgrading all nodes at once, or performing a clean install. In both cases, all resources will be unavailable during the upgrade/install process.
To start Cluster Administrator (see Figure 7 below), click Start, point to Programs, point to Administrative Tools, and click Cluster Administrator.
Figure 7: Cluster Administrator
All nodes and resource groups are up and online.
Click the first node (in our example, I4DELL1N1).
Click the File menu and click Pause Node. The status of I4DELL1N1 changes to Paused. (See Figure 8 below.)
Figure 8: I4DELL1N1 is paused.
In the left pane, click the + next to I4DELL1N1 to expand it. Double-click Active Groups. All groups currently hosted on I4DELL1N1 are displayed in the right pane (Figure 9 below).
Figure 9: I4DELL1N1 Active groups.
Click Disk Group 1 in the right pane. Click the File menu and click Move Group. Repeat this step for each group listed.
The services will be interrupted during the time that the services in each group are being moved to the other node and restarted. After all groups are moved, I4DELL1N2 hosts all groups and handles all client requests. I4DELL1N1 is idle (Figure 10 below).
Figure 10: I4DELL1N2 has all groups.
You will now need to review all resource types installed on your cluster.
Click Resource Types in the left pane (Figure 11 below).
Figure 11: Resource types
Determine which resource types do not support rolling upgrades and take offline all resources that are not supported. (Refer to Table 1 above.)
After ensuring that the latest released Service Pack has been applied, use Windows Server 2003 Enterprise Edition Setup to upgrade I4DELL1N1.
To make sure that Windows Server 2003 Setup does not place temporary files on one of the clustered disks, use the installation option /tempdrive:X. (For more information, refer to the Known Issues section of this paper.)
Setup detects Cluster Server on I4DELL1N1 and automatically installs Cluster service for Windows Server 2003 Enterprise Edition. I4DELL1N1 automatically rejoins the cluster at the end of the upgrade process, but is still paused and does not handle any cluster-related work.
You will now need to perform validation tests on I4DELL1N1 to confirm functionality.
Start Cluster Administrator on I4DELL1N1. You should see both nodes: I4DELL1N1 in Paused state, and I4DELL1N1 in Up state.
Click I4DELL1N1 and then click Resume Node.
Repeat steps 4, 5, 6, 7, 8, 10, 11, and 12 on the second node (I4DELL1N2).
If necessary, upgrade any applications that do not support rolling upgrades.
Test the cluster by moving groups between nodes. All resources should come online on any node.