Solved

msql cluster server replacement

Posted on 2011-03-10
15
340 Views
Last Modified: 2012-05-11
I want to upgrade my hardware in my sql cluster - is it possible to use imageing software and restore the image on the new server hardware - has anyone had any luck with this?
0
Comment
Question by:zingab
  • 6
  • 4
  • 2
  • +1
15 Comments
 
LVL 15

Expert Comment

by:Aaron Shilo
ID: 35097049
hi

i never had any luck with this since the hardware changes the image will never boot.

but i guess the querstion is how far are you goining with the upgrade.
0
 

Author Comment

by:zingab
ID: 35097880
what would be the best course of action?
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35120053
Move over all databases to one node. Evict the other, set up new hardware for the first new clusternode. Add clusternode, install sql cluster up to same SP on this new clusternode. Failover/move all databases to the new clusternode. Evict the second OLD cluster node. Repet the steps to install hw, add clusternode, SQL, SP etc.

DONE!

//Marten
0
Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

 
LVL 28

Expert Comment

by:Ryan McCauley
ID: 35128835
If your new cluster will have the exact same OS as well, you can do as marten suggests - essentially add your new hardware to your existing cluster, get SQL installed to exactly the same level, and then fail the databases onto the new hardware. Once that's done, evict your old nodes and you're done.

If you're upgrading the OS (we recently went from Windows 2003 R2 -> 2008 R2), there's no "upgrade path" per se - you have to actually move the databases. You can make this as smooth as possible, though, but moving all the logins (with SIDs intact) to your new database instance before you move your data over, using this script:

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

This copies your logins, with passwords intact, to the new SQL instance. Once that's done, restoring your databases on the new instance will result in properly mapped logins and everybody can resume using the application immediately.
0
 

Author Comment

by:zingab
ID: 35131462
is there anything that you guys are aware of documenting this process step by step...we are keeping the os the same version - sql 2005 standard
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35132215
Standard is what I presumed, thats why you need to evict one node before adding the first hw, and agin evict the other old node before adding the second new hw. Standard ed only supports two node cluster.

Prerequsite is of course windows server enterprise edition, it has the ms cluster service.

Quote my posting above: "SQL, SP etc". This means documenting SP and hotfix level. New nodes needs to be in the same SQL SP/Hotfix level.

//Marten
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35132252
The command:

select
serverproperty('Edition') as SQLEdition,
Serverproperty('ProductLevel') as ServicePack,
ServerProperty('ProductVersion')as Version,
ServerProperty('MachineName') as ServerName

Should give you the information you need. The column version can be compared to: http://www.sqlservercentral.com/articles/Administration/2960/
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35132877
Oh, and the windows enterprise edition should also be on the same OS SP level as existing nodes. Felt I wanted to point this out to!

//Marten
0
 

Author Comment

by:zingab
ID: 35138505
thanks -  last question is there a site that shows the process that you guys know of?
0
 
LVL 20

Accepted Solution

by:
Marten Rune earned 500 total points
ID: 35142156
0
 

Author Comment

by:zingab
ID: 35150226
Thanks everyone - now just getting back to my original though- would taking an image that is able to do a universal restore work?
0
 
LVL 20

Expert Comment

by:Marten Rune
ID: 35150720
No images is bound to hw, chipset on the motherboard, nic drivers etc etc.

Thats why normally you put some hypervisor between the hw and the os, THEN you can easily change the hw later on. But thats another story.

No you cant successfully change hw using a snapshot. It might work but you wont gain optimal performance from your hw.

Regards Marten
0
 
LVL 28

Expert Comment

by:Ryan McCauley
ID: 35151482
Though there's (in theory) no reason that wouldn't work, since there is software designed to do that kind of swapout, I'd be very skeptical about it since Cluster communication between nodes is so sensitive to any kind of disturbance and the cluster is so tightly bound to the hardware. There's no reason you couldn't give it a shot, just to test it, on an isolated network and see if you can clone the disks, but I wouldn't have high hopes.
0

Featured Post

Free Webinar: AWS Backup & DR

Join our upcoming webinar with experts from AWS, CloudBerry Lab, and the Town of Edgartown IT to discuss best practices for simplifying online backup management and cutting costs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question