Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Thu, 20 Apr 2006 13:45:32 -0400
You could do it your way. I chose mine since I had two instances and needed
at least two nodes during production hours. Plus, I didn't need to take SQL
offline to reinstall it and the service packs and the hotfixes on the new
node. The SQL binaries and cluster configuration survived the upgrade.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Walter D''Souza" <WalterDSouza@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:892677BE-A164-4BC4-8C3C-26561BC12533@xxxxxxxxxxxxxxxx
Geoff,
As you have mentioned we have to do an inplace upgrade.
Is it possible to remove one existing node and add a new node with a clean
installation of 2003? Once we failed over resource to 2003 we will remove
the
other node from Cluster and do the same.
Thank you very much. ...Walter
"Geoff N. Hiten" wrote:
Been there, Done that.
Here is what I did:
First, I made absolutely sure I had all the drivers and software for
Windows
2003, especially HBA and any multi-pathing software.
I then upgraded one node in-place to Windows 2003. Once I was sure it
worked as a cluster host node, I upgraded its peer node, also in-place.
Next was adding two new nodes based on new hardware. Note, you cannot
add
x64 nodes to a 32-bit cluster. Once they worked fine, I removed the
original two host nodes and replaced them with two new ones that matched
the
other new nodes.
Finally, I wiped the old nodes and rebuilt them as a new cluster on
Windows
2003 for an entirely different purpose.
Started with 2 nodes and Windows 2000. Ended with 4 nodes and Windows
2003.
I also added a new SQL instance at the end.
Note that when you add or remove a node, you must re-run the SQL
installer.
You must re-run any service packs and hotfixes after the install when you
add nodes. Read up under "Maintaining a Failover Cluster" in BOL for
instructions on adding or removing nodes.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Walter D''Souza" <WalterDSouza@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D3F6CFCD-86F9-438C-99FC-DC3FF35B2E19@xxxxxxxxxxxxxxxx
I am planning to upgrade from Windows 2000 to a Windows 2003 Cluster. I
have
SQL server 2000 which we installed it as a virtual server.
We are doing a rolling upgrade and want to introduce new hardware at
the
same time. Is it possible/recommended?
On the Windows 2000 cluster take one of the current servers off the
cluster.
Bring in a new Windows 2003 Enterprise server with new hardware and
join
to
the Cluster. Do I need to install SQL server or when I move the
cluster
over will the SQL server software get installed.
I greatly appreicated being pointed in the right direction.
Thank you ...Walter
.
- Follow-Ups:
- Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- From: Walter D''Souza
- Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- References:
- Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- From: Geoff N. Hiten
- Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- Prev by Date: Re: SQL2005 Clustering Under Virtual Server Release 2
- Next by Date: Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- Previous by thread: Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- Next by thread: Re: Upgrading Windows 2000 cluster to Windows 2003 Cluster.
- Index(es):
Relevant Pages
|