Rolling upgrade on 2000 cluster
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Rolling upgrade on 2000 cluster

 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering
Author Message
Peter Lykkegaard
Guest





Posted: Fri Oct 14, 2005 8:51 am    Post subject: Rolling upgrade on 2000 cluster Reply with quote

Hi All

We are going to upgrade a windows 2000/MSSQL 2000 cluster
At the same time we'd like to upgrade some middleware on the same cluster

Installation folder and configuration will change
The new middleware version is partly backwards compatible but not fully

We need to check a few things before setting it to production

My idea was to move ressources to one node and remove the passive node from
the cluster
Upgrade to win2003 creating a new cluster (new name/ip) etc and check that
everything is working
Set it to production and upgrade the last node and add this to the new
cluster

Crazy?

Any ideas/comments?

NB! I have read the rolling upgrade thing and it sounds tempting :)
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/2e0186ba-1a09-42b5-81c8-3ecca4ddde5e.mspx


Thanks/Peter
Back to top
Ryan Sokolowski [MVP]
Guest





Posted: Fri Oct 14, 2005 8:50 pm    Post subject: Re: Rolling upgrade on 2000 cluster Reply with quote

Yes, I'm concerned as to why you're choosing to combine these tasks. Just
upgrade the existing cluster in-place first. Do a rolling upgrade (without
removing any nodes from the cluster) and get the whole thing to W2K3 first.
Then address any application configuration changes or modifications
afterwards...

Make sense?

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

This posting is provided "AS IS" with no warranties, and confers no rights.

"Peter Lykkegaard" <peter.aghl@gmail.com> wrote in message
news:utVtQnJ0FHA.2960@tk2msftngp13.phx.gbl...
Quote:
Hi All

We are going to upgrade a windows 2000/MSSQL 2000 cluster
At the same time we'd like to upgrade some middleware on the same cluster

Installation folder and configuration will change
The new middleware version is partly backwards compatible but not fully

We need to check a few things before setting it to production

My idea was to move ressources to one node and remove the passive node
from the cluster
Upgrade to win2003 creating a new cluster (new name/ip) etc and check that
everything is working
Set it to production and upgrade the last node and add this to the new
cluster

Crazy?

Any ideas/comments?

NB! I have read the rolling upgrade thing and it sounds tempting :)
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/2e0186ba-1a09-42b5-81c8-3ecca4ddde5e.mspx


Thanks/Peter
Back to top
Peter Lykkegaard
Guest





Posted: Fri Oct 14, 2005 8:50 pm    Post subject: Re: Rolling upgrade on 2000 cluster Reply with quote

"Ryan Sokolowski [MVP]" wrote

Quote:
Yes, I'm concerned as to why you're choosing to combine these tasks. Just
upgrade the existing cluster in-place first. Do a rolling upgrade
(without removing any nodes from the cluster) and get the whole thing to
W2K3 first. Then address any application configuration changes or
modifications afterwards...

Make sense?

Yep no problems


The intial plan was to upgrade the middleware and leave the 2000 cluster as
is
The 2000 to 2003 upgrade was an addon project

After I have read the docs on rolling upgrade your suggestion was my own
conclusion as well :-)

Thanks/Peter
Back to top
Peter Lykkegaard
Guest





Posted: Mon Oct 17, 2005 12:50 pm    Post subject: Re: Rolling upgrade on 2000 cluster Reply with quote

"Ryan Sokolowski [MVP]" wrote

Quote:
Yes, I'm concerned as to why you're choosing to combine these tasks. Just
upgrade the existing cluster in-place first. Do a rolling upgrade
(without removing any nodes from the cluster) and get the whole thing to
W2K3 first. Then address any application configuration changes or
modifications afterwards...

Hmm, change of plans


The customer would like to do a clean install of the 2003 ent server on one
node and run tests on this new setup for a period
This will be a bit messy hardwarewise

I think I need new disks for quorum and mssql?

Comments?

Thanks/Peter
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Clustering All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB