 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / October 2005Cluster and Mirroring with 2005
I am looking for some advice on the following problem. I need a redundant SQL solution at our main location and a warm site in a different, off site location. The warm site would only become a hot site if we had a complete failure at the main location. What I was thinking was to create a failover cluster at our main location incase of simple hardware failure, the other server could take over. At the warm site I would have a witness server and have the database mirrored to a sql server there. I am going to be using sql server 2005. Is this a possible solution? If not, can you please point me in the right direction. $$$ is not really an issue. That is certainly a possible scenario. Remember that mirroring works at the database level, not at the server level. You will have to do some customization if you want to make it work for multiple databases. There are also performance, latency, and network bandwidth costs for mirroring. The lower your tolerance for data loss and outage time, the higher those costs. If money really isn't an issue, you may want to look at SAN-level data replication technologies. Since you will have a SAN for the cluster anyway, this may be a better option. Make sure the SAN vendor can keep multiple LUNS in synch or you may end up with mismatched data and log partitions, causing a corrupt and unusable database.  SignatureGeoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP >I am looking for some advice on the following problem. > [quoted text clipped - 10 lines] > Is this a possible solution? If not, can you please point me in the > right direction. $$$ is not really an issue. I noticed that you said 'warm site'. By 'warm', I assume you can afford losing some data during a site failover. If you can afford data loss of up to 15 minutes or so, the plain old log shipping may be the simplest and cheapest solution to consider. I'd keep it simple if a simple solution is enough. Linchi >I am looking for some advice on the following problem. > [quoted text clipped - 10 lines] > Is this a possible solution? If not, can you please point me in the > right direction. $$$ is not really an issue. Database mirroring is certainly an option, but so would be log shipping, remote mirroring, or stretch clustering. You might want to check out the following. Although for SS2K, most of the information still applies, with the exception of DB mirroring. Microsoft SQL Server 2000 High Availability Series http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlhalp.mspx SQL Server 2000 High Availability Series Implementing Remote Mirroring and Stretch Clustering http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/hasog05.mspx SQL Server 2005 Mission Critical High Availability http://www.microsoft.com/technet/prodtechnol/sql/themes/default.mspx Sincerely, Anthony Thomas > I am looking for some advice on the following problem. > [quoted text clipped - 10 lines] > Is this a possible solution? If not, can you please point me in the > right direction. $$$ is not really an issue. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.