all groups > sql server clustering > january 2005 >
You're in the

sql server clustering

group:

Failover with Replication


Failover with Replication bk29
1/27/2005 4:19:02 PM
sql server clustering:
Hello,

I am not sure how to approach this problem. What I need to do is setup
failover as well as data copying. I need to setup clustering on two nodes.
If one node goes down then the other node should pick up the load. But the
problem is that you need to have a shared SAN. Is there anyway to get away
from a shared SAN (disk array) and still setup clustering.

Can you have two servers with their own seperate storage. Node A
(Primary) also replicates the data to Node B (Seconday). But if node A goes
done, node B picks up the load but it already has all the data from Node A.

Basically what I am trying to do is setup failover as well have data
replication so that if the data gets corrupt on Node A for any reason, Node B
would be a Hot stand by and would switch over automatically.

Please let me know how this could be possible or if you need any
further explanation.

Thanks,
--
RE: Failover with Replication bk29
1/28/2005 9:59:03 AM
Thank You for the response. It was very helpful. I have found some third
party software like incepto and geoclusters that seem to accomplish what we
are trying to do. But they are not supported by microsoft.

I guess our main concern with Clustering was the Shared disk being the
single point of failure due to user interaction, corruption, etc. If we
implement the log shipping we will not have a hot standby. If for some
reason the shared disk does fail, we can bring up the log shipped server, but
this will have to be a manual process and for some applications it may be too
time consuming.

I will resarch further with the third party software. Any further advice
would be appreciated. Thank you again for your help.


[quoted text, click to view]
RE: Failover with Replication uttamkp NO[at]SPAM online.microsoft.com
1/28/2005 2:19:52 PM
For SQL Server 2000 Failover Clustering you need shared storage. With Win2K3 MSCS, there is a new feature -- Majority Node Set Quorum and you do not need shared storage for the quorum. But for SQL Server
virtual instance, you need a shared storage for your databases. I do believe that there are third party solutions that have SQL Server solutions with MNS Quorum. They use their high-end SAN's for the database
storage replicating the IO on a controller level.

If you do not have shared storage and based on your explanation, you may benefit from SQL Server Log Shipping.

Best Regards,

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

AddThis Social Bookmark Button