March 19, 2014 at 2:28 pm
SPECS:
SQL: 2005 SP 4
Server: Windows Server 2003
Cluster: Two Nodes Active/Active each has its own instance
Project: Replace the two Windows Server 2003 Nodes with new Gen8 Windows Server 2008 R2 Enterprise.
I have been tasked to replace the current cluster nodes running on two very old G1 Servers with new Gen8 Servers. Each node has an instance running. SQL Cannot must stay at SQL 2005 SP4 and cannot be upgraded. The instance name needs to stay the name because we several application configured by the VirtualServer\instance name.
My questions are the following:
Can I install an SQL 2005 SP 4 on a Windows Server 2008 Cluster?
Is there a way to just move the instances over or backup and restore them?
This is my first shot in the dark on this project. At a high level what would be the best approach to do this. Do you have any links to websites that can help with this?
Your help is appreciated.
Jeff
March 19, 2014 at 3:27 pm
Can I install an SQL 2005 SP 4 on a Windows Server 2008 Cluster?
Min SP3 required on Windows Server 2008 R2.
http://support.microsoft.com/kb/955725
Is there a way to just move the instances over or backup and restore them?
You can't move the instances. You can move the DBs and server-level objects.
The instance name needs to stay the name because we several application configured by the VirtualServer\instance name.
For retaining the SQL Name, You can either use Client Alias at the client level or DNS alias at the network level.
--
SQLBuddy
March 19, 2014 at 6:19 pm
Thank you very much for the feedback.
Jeff
March 24, 2014 at 2:27 pm
I am working on migrating an SQL Cluster from Windows Server 2003 SQL 2005 to Windows Server 2008 SQL 2005 and I am considering doing the following:
Install Windows Server 2008 R2 on two new servers (DONE)
I would like to take these two servers off the network (disable the NIC)
Installing the Windows cluster and the two virtual instances on the new servers in Active/Active mode using the same names and IP addresses as the two old servers
Back up the system and production databases from the old servers onto external hard drive
Restoring all system and production database to the new servers
Take the old servers off line (disable the NIC or something)
Placing the two new servers on the network (enabling the NIC)
Testing
Rollback would be
Take the new servers off the network (disable NIC)
Putting the old servers back on the network (Enable the NIC)
The goal is not to have to change the application connections to the databases.
Please let me know what you think. Your help is appreciated.
Jeff
March 24, 2014 at 3:50 pm
jayoub (3/24/2014)
I am working on migrating an SQL Cluster from Windows Server 2003 SQL 2005 to Windows Server 2008 SQL 2005 and I am considering doing the following:Install Windows Server 2008 R2 on two new servers (DONE)
I would like to take these two servers off the network (disable the NIC)
Installing the Windows cluster and the two virtual instances on the new servers in Active/Active mode using the same names and IP addresses as the two old servers
Back up the system and production databases from the old servers onto external hard drive
Restoring all system and production database to the new servers
Take the old servers off line (disable the NIC or something)
Placing the two new servers on the network (enabling the NIC)
Testing
Rollback would be
Take the new servers off the network (disable NIC)
Putting the old servers back on the network (Enable the NIC)
The goal is not to have to change the application connections to the databases.
Please let me know what you think. Your help is appreciated.
If you disconnect the new servers from the network, they'll have no AD domain and DNS server. You wont be able to continue.
If you really want to use the same VNN and VIP you'll need a complete outage to perform this.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 24, 2014 at 6:29 pm
jayoub (3/24/2014)
I am working on migrating an SQL Cluster from Windows Server 2003 SQL 2005 to Windows Server 2008 SQL 2005 and I am considering doing the following:Install Windows Server 2008 R2 on two new servers (DONE)
I would like to take these two servers off the network (disable the NIC)
Installing the Windows cluster and the two virtual instances on the new servers in Active/Active mode using the same names and IP addresses as the two old servers
Back up the system and production databases from the old servers onto external hard drive
Restoring all system and production database to the new servers
Take the old servers off line (disable the NIC or something)
Placing the two new servers on the network (enabling the NIC)
Testing
Rollback would be
Take the new servers off the network (disable NIC)
Putting the old servers back on the network (Enable the NIC)
The goal is not to have to change the application connections to the databases.
Please let me know what you think. Your help is appreciated.
Build the new servers parallelly while attached to the network. And you can create a DNS alias name of the OLD Server pointing to new cluster to accomplish the client redirection.
Once you migrate all your databases to the new cluster, during the cutover take the old cluster down and create the DNS alias pointing to the new cluster.
Roll back is just bring the old servers up and change the DNS alias to point to the old servers.
Alternatively, you can create a client Alias on the user machines pointing to the new cluster. But this alternative approach is going to be tedious and cumbersome.
http://www.mssqltips.com/sqlservertip/1620/how-to-setup-and-use-a-sql-server-alias/
--
SQLBuddy
March 25, 2014 at 9:26 am
Again thank you very much for the help.
I printed the artical on setting up the Alias and will present the idea to the team and the developers.
Jeff
March 25, 2014 at 9:34 am
As i said previously, once you do this
jayoub (3/24/2014)
I would like to take these two servers off the network (disable the NIC)
You will not be able to do this
jayoub (3/24/2014)
Installing the Windows cluster and the two virtual instances on the new servers in Active/Active mode using the same names and IP addresses as the two old servers
A Windows Server Failover Cluster requires a DNS infrastructure and a Windows Server Active Directory domain. Once the servers are off the network they wont communicate with each other let alone a DNS primary zone or an AD catalog!!!!!
Also, i've installed SQL Server 2005 on a 2008 cluster previously and it's not pretty. There are a whole host of known issues with this, you'd be better off leaving it Windows 2003. Or move to Windows\SQL 2008.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 25, 2014 at 10:18 am
I dont understand how information like this is free because It is worth millions. Thank you very much.
You have given me lots to think about and I will redesign the plan to include the Alias redirect and keep the servers on line. I hate the old names anyway. I will also add to the plan the installation of SQL Server 2008 R2.
I do have a question. Will leaving the databases in SQL Server 2005 (90) compatibility level really keep these database at 2005. The Management hear freeks out everytime i mention upgrading to SQL 2008.
Please let me know
Your help is appreciated.
Jeff
March 25, 2014 at 10:26 am
jayoub (3/25/2014) Will leaving the databases in SQL Server 2005 (90) compatibility level really keep these database at 2005. The Management hear freeks out everytime i mention upgrading to SQL 2008.
Please let me know
Your help is appreciated.
Yeah, you can leave them at 90 compatibility level but you don't get the benefits of SQL Server 2008 upgrade.
--
SQLBuddy
March 25, 2014 at 10:34 am
[Url=http://technet.microsoft.com/en-us/library/bb510680.aspx] This[/url] details the compatibility levels.
There's no real need to panic. Why not set up a test system and verify the platform.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 25, 2014 at 11:37 am
Crazy, but we do not have a test system here and building it requires Developer support. When i mention it I get barked at.
I will plan to leave the compatibility level at 90 and use SQL 2008.
Thanks everyone for the help
Jeff
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply