Replace cluster servers 1

[pagy]

3 node sql cluster - windows 2003 sp1 and sql 2000 sp4, data and log files stored on a SAN.
We want to replace the 3 nodes with some better specced machines so I was thinking,

build new nodes
configure clustering
install sql and patch to sp4
plug new servers into the san
detach or backup databases from old nodes
power down old nodes
attach or restore to new nodes

The actual location of the data files won't change obviously as they are on the san
Does this plan hold up???? Any suggestions gratefully received

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[mrdenny]

That will work fine if you are ok with the outage while you move everything over, and if you are ok with changing the the name and IP address of the virtual world.

I would recommend doing an inplace swap out of the hardware.

Evict one node from the cluster.
Build a new machine.
Add it to the cluster.
Push the SQL binaries to it, and service pack it.
Fail to it for testing.

Repeat for each node until all three nodes are complete.

It will take a couple of days for the whole cluster to be done in this method, but it will make it so that you don't have to change any connection strings, firewall settings, etc.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[pagy]

Thanks mrdenny. We've actually scheduled a weekend worths of downtime for this and some other bits we are doing so the outage isn't really a problem.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[pagy]

Ah, what about if the new cluster nodes had to be in a different domain in a different forest?? It has just be thrown into the mix that this may have to happen.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[mrdenny]

Here is the MSKB on moving a cluster to a new domain.

http://support.microsoft.com/kb/269196

I would do the new servers first, make sure everything is working fine for a day or two, then change to it a new domain via KB 269196.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[pagy]

Nice one, thanks. Have you ever moved an SQL cluster to a different domain before Denny??

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[mrdenny]

I've never had to move a SQL Cluster from one domain to another.

Sorry.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[mrdenny]

However the MSKB does appear fairly straight forward.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[pagy]

Yep, it doesn't look too complicated.

Thanks Denny


Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[pagy]

Just to update;

Have moved the SQL cluster to another domain following the below KB entries;

http://support.microsoft.com/default.aspx?scid=kb;EN-US;269196

http://support.microsoft.com/kb/319016/

It has worked and all databases are online and accessible.

The only issue we have had is the following;
After we reboot a server hosting one particular sql virtual server it puts the old IP address for that virtual server back in the registry which stops the SQL Server resource from coming online. It's not a big issue to work around as I just change the reg entry again. When I've found out why this is happening I will post the solution.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[mrdenny]

Glad it all worked out.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[ejanakieff]

I need to do the same.

I have two nodes cluster and I have to move SQL Server 2000 SP4 and all the databases to a new two servers.

My question is:

How is better: detach the databases from old nodes, and after attach them in the new nodes or do an backup and restore?

When I have installed the SQL server 2005 SP4, I have to restore system databases (master, msdn and model), and after the user database?