May 26, 2006 at 8:28 am
We want to upgrade our 2-node (active-passive) Windows 2000 Advanced Server SP4 cluster to Windows 2003 Enterprise Server SP1. We want to follow the instructions in the following link
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/rllupnet.mspx
but are there any issues with the SQL resource types (SQL Server, SQL Server Agent, Microsoft Search Service Instance) and Analysis Services (generic service). We clustered AS by following the instructions in KB308023. All other active resource types that we use are supported for a rolling upgrade (file share, IP Address, Network Name, Physical Disk & DTC) and all are in one cluster group. We are running SQL 2000 SP3a w/AWE enabled (w/ 3gb /PAE switches - servers have 6gb RAM). Has anyone upgraded with success, if so, did any special steps need to be taken w/SQL & AS? Any tips or links pointing to this would be appreciated.
May 29, 2006 at 8:00 am
This was removed by the editor as SPAM
June 5, 2006 at 3:12 pm
Well, we bit the bullet and just did it. I did contact M/S and they indicated rolling upgrades on a cluster were supported with AS.
After network drivers were updated and an unexpected failover when Windows Updates were applied, the rolling upgrade to W2K3 w/SP1 on the passive node worked. However, when we attempted the failover to the newly upgraded node, MSDTC failed and when Analysis Services attempted to come online EVERYTHING failed back over to the other node running W2K. I contacted M/S and they had me uninstall and install MSDTC (something the rolling upgrade documentation indicated you shouldn't do in a mixed mode). They also told me to apply a post SP1 fix for comclust and they supplied the fix. Once this was done, I forced a failover and everything came online on the upgraded node.
We are now operating in mixed mode. You may now ask, why? Well, since W2K Adv. Server only supports 2 nodes, we want to migrate the cluster to new hardware seamlessly. Next, we want to evict node A, which is running W2K. Then we want to add the 2 new nodes (w/new hardware and clean installs of W2K3 s/SP1). Once these are added, we should be able to evict node B and the cluster will be running on the new hardware. If anyone has any helpful tips, suggestions or experience with this process, please advise.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply