We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
I think you might have answered your own question... but in case it isn't clear:
To make you Active/Passive cluster into an Active/Active cluster, you add a second SQL Instance to the cluster, and when everything is working 'normally', keep the instances on different nodes.
Ted Bouskill
An Active/Active cluster is actually two Active/Passive clusters. Let's say you have
SQLServerA
SQLServerB
First you setup an ActivePassive SQL cluster like this:
SQLServerA\SqlCluster1 - Active
SQLServerB\SqlCluster1 - Passive
Then you do this
SQLServerA\SqlCluster2 - Passive
SQLServerB\SqlCluster2 - Active
The benefit is you can run services on both servers concurrently, however if there is a failover condition that the load of both instances will be placed on one server. Considering that it should be a rare occurrence that is a good trade off.
A worse case scenario would be if both instances were running at 100% capacity then one instanced failed over so both instances were running on one server which would then cause both instances to degrade severely as one server tries to handle the full load. However, I would never allow two servers to run consistently at a high load because you have no buffer for spikes.
If both servers are running at 60% or less then a failover occurs there will be some degradation but it would be tolerable. I have used an Active/Active cluster successfully for a SharePoint 2010 farm where one instance hosted search databases and the other hosted the content databases.
There is another option. Use two Active/Passive clusters in a 3 node cluster.
SqlServerA\SqlInstance1 - Active
SqlServerB\SqlInstance2 - Active
SqlServerC\SqlInstance1 - Passive
SqlServerC\SqlInstance2 - Passive
That way you have two fully function SQL servers with one server standing by for two clusters.
Mark Wills
Hmmm... I have normally stayed away from active / active relying on active / passive for failover clustering. Though... that is not to say it doesnt have a place...
Why are you wanting to replace active/passive with active/active ? What do you think you will be gaining ?
Some people think it is both high availability and load balancing, but it isnt...
To make you Active/Passive cluster into an Active/Active cluster, you add a second SQL Instance to the cluster, and when everything is working 'normally', keep the instances on different nodes.