Ressourcen für IT-Professionals >
Forenhomepage
>
Clustering
>
Clustering with Windows 2008 server and SQL redundancy
Clustering with Windows 2008 server and SQL redundancy
- I have 2 DELL PowerEdge 2950s and I am trying to decide the best scenario to create a redundant HA clustered SQL environment. The final outcome I would like to obtain is 2 redundant Windows 2008 server with SQL DBs that are constantly in synch with each other and if one fails the other assumes the role.
I am currently stuck on the initial configuration of the Windows Server 2008 HA. It's as each step leads me to another can of worms. I am able to fully install Windows 2008 on both servers, but when it comes to the Failover wizard its just error after error. From validation errors with the hard drives to the being able to add nodes.
This seems like it should be a simple setup and I have scoured the web high a low for decent walkthroughs , but I keep running into brickwalls. Any guidance would be much appreciated.
Thanks.
JohnnyDo
Antworten
- Hi!
You have two solutions without using third party tools:
1) Failover clustering: two nodes use a shared storage on which the data resides. Only one node is active. No replication takes place because there is only one set of data. Easy to set up via the failover clustering wizard as soon as you have set up the shared storage.
2) DB mirroring: two nodes have their own hdds for their data. There are different ways to replicate the data between the two nodes. See the following sites:
http://technet.microsoft.com/en-us/library/cc917680.aspx
http://technet.microsoft.com/en-us/library/cc917681.aspx
If you search for DB mirroring you will find tons of material. BUT: Mirroring is not easily set up. There are many things to consider and also the failover strategy has to be well planned.
hope that helps,
Andreas- Als Antwort markiertEdwin vMierloMVP, ModeratorDonnerstag, 2. Juli 2009 10:01
Alle Antworten
Are you using shared storage or did you plan to use some type of replication to keep the servers "in sync" with each other as you mentioned? This virtual lab is a great way to get some hands on experience so you can see the way things are suppose to work.
http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032345932
If you have no shared storage configured, the hard drive errors are to be expected. You can ignore most storage related errors if you plan on using 3rd party replication such as SteelEye DataKeeper, as shown in this video.
http://www.steeleye.com/downloads/resource/videos/datakeeper-for-sql/index.html
Can you post the exact errors you are receiving in your validation report?
David A. Bermingham Director of Product Management http://www.steeleye.com- David,
I just have 2 DELL 2950s with 3 73GB SCSI SAS drives builtin. All 3 drives are running in RAID5 and have been partitioned with 30GB for Windows System and the 105GB remaining for the DATA. Is it possible to complete the redundant solution with 2 server alone or do I need a 3rd component an external shared storage drive MD3000i for example?
Thanks.
JohnnyDo - Yes, you will need either shared storage or host based replication that is compatible with Windows Server Failover Clustering.
David A. Bermingham Director of Product Management http://www.steeleye.com- Als Antwort vorgeschlagenDavid Bermingham Mittwoch, 1. Juli 2009 08:03
- Hi!
You have two solutions without using third party tools:
1) Failover clustering: two nodes use a shared storage on which the data resides. Only one node is active. No replication takes place because there is only one set of data. Easy to set up via the failover clustering wizard as soon as you have set up the shared storage.
2) DB mirroring: two nodes have their own hdds for their data. There are different ways to replicate the data between the two nodes. See the following sites:
http://technet.microsoft.com/en-us/library/cc917680.aspx
http://technet.microsoft.com/en-us/library/cc917681.aspx
If you search for DB mirroring you will find tons of material. BUT: Mirroring is not easily set up. There are many things to consider and also the failover strategy has to be well planned.
hope that helps,
Andreas- Als Antwort markiertEdwin vMierloMVP, ModeratorDonnerstag, 2. Juli 2009 10:01
