August 7, 2010 at 1:31 pm
Hi,
We have 2 node active/passive cluster set up for SQL Server 2005 x64 with SP3 on Windows 2003 x64 with SP2.
Now we want to first perform in-place upgrade for OS from Windows 2003 x64 with SP2 to Windows 2008 with SP2 and then perform in-place upgrade of SQL Server 2005 to SQL Server 2008
Questions:
1. Is that possible to perform in-place upgrade for Clustered Windows 2003 x64 to Windows 2008 x64?
2. If yes, please direct me to that link.
3. Once we upgrade OS to Windows 2008, then can we directly perform in-place upgrade of SQL Server 2005 to 2008? or do we need to do the cluster setup again for Windows 2008?
Thanks
August 8, 2010 at 2:37 am
Hi Mamata,
We are also looking for this option of upgrading 2 node clustered Windows 2003 x64 to Windows 2008 x64 and then upgrade SQL Server 2005 to SQL Server 2008.
But our according to our Windows admin, in Windows 2008, the cluster installation is completely changed and so it's NOT possible to perform upgrade of a 2 node clustered Windows 2003 x64 to Windows 2008 x64
But, I'm NOT sure whether any body did this kind of upgrade and what Microsoft suggests and our Windows admin still looking for the options to achieve this upgrade
If you find any information, please share in this thread.
Thanks
August 8, 2010 at 9:44 am
It wouldn't be possible to maintain your passive node as a passive node during the upgrade, I agree.
However, one idea might be to drop the passive node out of the 2003 cluster, upgrade to Windows Server 2008, set up the 2008 Cluster with a different cluster name than your production 2003 cluster, install SQL 2008, move your databases over, and then cut over your services to the new Win 2008/SQL 2008 system. At that point it would be a one node cluster. Then you would blow away your remaining Win 2003/SQL 2005 node and build it up as the passive node to your new cluster.
We made this same transition a few months back but we elected to use new hardware and then just re-purpose the old hardware for something else which makes the process easier and less risky.
We also found the differences to Windows Server 2008 clustering to be substantial. One of the things we didn't like is that you have to make computer objects in the domain for SQL Server 2008 which meant it could not be the same as the Windows Server 2008 Cluster as we previously had it with Win 2003/SQL 2005. It's not a big deal but it's strange that with default single server instances you can use the host computer name but with clusters you cannot.
August 8, 2010 at 11:58 am
tnk (8/8/2010)
However, one idea might be to drop the passive node out of the 2003 cluster, upgrade to Windows Server 2008, set up the 2008 Cluster with a different cluster name than your production 2003 cluster, install SQL 2008, move your databases over, and then cut over your services to the new Win 2008/SQL 2008 system. At that point it would be a one node cluster. Then you would blow away your remaining Win 2003/SQL 2005 node and build it up as the passive node to your new cluster.
This (a side by side migration) would be my preferred route too
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 9, 2010 at 4:36 pm
It wouldn't be possible to maintain your passive node as a passive node during the upgrade, I agree.
However, one idea might be to drop the passive node out of the 2003 cluster, upgrade to Windows Server 2008, set up the 2008 Cluster with a different cluster name than your production 2003 cluster, install SQL 2008, move your databases over, and then cut over your services to the new Win 2008/SQL 2008 system. At that point it would be a one node cluster. Then you would blow away your remaining Win 2003/SQL 2005 node and build it up as the passive node to your new cluster.
Hi Tnk,
We have also have log shipping configured for the databases on SQL Server failover cluster instance.
Then after drop out the passive node out of windows 2003 cluster and install fresh Windows cluster 2008 and install SQL Server 2008 and then restore the databases
If we want to do this, we need to disable the log shipping right? because we are installing the New SQL Server 2008 instance, we cannot have the old log shipping configuration right?
Can we have same Virtual server name with different IP? because we do not want to make the instance name change as lot of work need be done to make the application change to point to new instance name.
Please advice
August 9, 2010 at 4:53 pm
gmamata7 (8/9/2010)
Can we have same Virtual server name with different IP?
no you cannot, like a computername the virtual network name must be unique in the Windows domain
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 9, 2010 at 5:03 pm
gmamata7 (8/7/2010)
Hi,We have 2 node active/passive cluster set up for SQL Server 2005 x64 with SP3 on Windows 2003 x64 with SP2.
Now we want to first perform in-place upgrade for OS from Windows 2003 x64 with SP2 to Windows 2008 with SP2 and then perform in-place upgrade of SQL Server 2005 to SQL Server 2008
Questions:
1. Is that possible to perform in-place upgrade for Clustered Windows 2003 x64 to Windows 2008 x64?
2. If yes, please direct me to that link.
3. Once we upgrade OS to Windows 2008, then can we directly perform in-place upgrade of SQL Server 2005 to 2008? or do we need to do the cluster setup again for Windows 2008?
Thanks
Link: SQL 2008 Upgrade Technical Reference Guide See section 4.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 9, 2010 at 5:30 pm
Thank you Perry & Waynes,
I glance through the document, SQL Server 2008 Upgrade Technical Reference Guide, to see whether we can keep the same Virtual server name and SQL Server instance while installing the SQL Server 2008 on Windows 2008 after erasing Windows 2003 cluster node.
Could you please suggest any other documents or links that outlines the steps for upgrading Windows Server 2003 2 node cluster with SQL Server 2005 to Windows 2008 cluster with SQL Server 2008?
I did find the below but NOT the complete documentation
If you want to upgrade the operating system on the cluster nodes to Windows Server 2008, you will face some challenges. The biggest challenge is that a rolling upgrade (that is, an upgrade performed one cluster node at a time) is not supported as it was with Windows Server 2003. With Windows Server 2008, the operating system-level clustering feature that SQL Server is built on was completely recoded, so a direct upgrade is not possible.
To reuse existing cluster nodes, you must install a fresh copy of Windows Server 2008, meaning that the existing configuration will be erased. You can then reinstall SQL Server after the installation of Windows Server 2008 is complete. This means that before tearing down the old configuration, performing backups of all databases and scripting all objects is essential. Although these tasks are part of a normal upgrade process, there is additional pressure to do them because the old configuration will no longer exist. If you are going to deploy Windows Server 2008, consider purchasing new hardware and implementing an upgrade strategy that would allow the configuration of the existing cluster to remain.
I know it's very challenging task but we have NO other options left. I appreciate your inputs.
I found a link which describes database upgrade from SQL Server 2000 Active/Active cluster running on Window 2000 Server to a Windows Server 2003/SQL Server 2005 Active/Active cluster
Similarly, I'm looking for upgrade a SQL Server 2005 Active/Passive cluster running on Window 2003 Server to a Windows Server 2008/SQL Server 2008 Active/Passive cluster on same nodes
Thanks
Please advice
August 9, 2010 at 7:50 pm
I believe that the document is pretty clear... an in place update of a Windows Server 2003 cluster / sql 2005 cluster to Windows Server 2008 cluster / SQL 2008 cluster isn't supported.
This leaves you two choices:
1. Backup existing system. Slick the drives, build new Windows Server 2008 cluster. Add SQL 2008 cluster. Restore databases.
2. Build your Windows Server 2008 / SQL Server 2008 cluster on new hardware. Copy/log ship/etc. your databases over to new cluster.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 10, 2010 at 1:11 am
gmamata7 (8/9/2010)
to see whether we can keep the same Virtual server name and SQL Server instance
As I said the virtual network name, like a computername must be unique in the domain. This is basic Windows infrastructure, do you understand how a cluster works. If not I would leave well alone!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 10, 2010 at 12:39 pm
gmamata7 (8/7/2010)
Hi,We have 2 node active/passive cluster set up for SQL Server 2005 x64 with SP3 on Windows 2003 x64 with SP2.
Now we want to first perform in-place upgrade for OS from Windows 2003 x64 with SP2 to Windows 2008 with SP2 and then perform in-place upgrade of SQL Server 2005 to SQL Server 2008
Questions:
1. Is that possible to perform in-place upgrade for Clustered Windows 2003 x64 to Windows 2008 x64?
2. If yes, please direct me to that link.
3. Once we upgrade OS to Windows 2008, then can we directly perform in-place upgrade of SQL Server 2005 to 2008? or do we need to do the cluster setup again for Windows 2008?
Thanks
They are all correct, MS doesnt support an in place upgrade cause the changes within the windows OS - clustering has changed big time.
Here is a good souce for step by step instructions on practicing setting up the cluster on win 08 and sql 08.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply