Active Passive to Active Active
-
Is it possible to change the installation of a sql active passive cluster to an active active cluster. When I am tying to install the 2nd instance of sql server on the 2nd node I can not see the drive identified for the sql system. This drive had already been assigned to the 1st virtual server. Instructions were initially given to build an active passive cluster, but have now changed to re-configure the build to an active active cluster. I do not believe this is possible without a re-build because resource groups have already been assigned. I need confirmation of whether my theory is true or not??????
-
"This drive had already been assigned to the 1st virtual server"
I don't understand what you mean by the above.
For Active-Active installation, each instance should have one dedicated disk drive(volume) associated to it. The disk drive(resource) will be available to the servers on which the corresponding instance is running. If you use the same disk drive(i don't know even if that is supported or not and even if it is supported), both the instance will run on one node. You can't balance the resource.
Regarding re-configuring your exisiting Active-Passive installation, you can add a disk drive to your cluster and add that as a resource. You can then install SQL on the new instance. You will need an additional I.P. also and also assign a SQL Network name to it.
-
Also, it should be noted that Active/Active doesn't work if you're thinking of running the same application on each node. As noted above, each node should have it's own resources, which would mean that you'd have to merge the data at some point
Best situation for an Active/Active cluster is when you're running two distinct database applications. This allows each application two fail-over to the other node.
--------------------
Colt 45 - the original point and click interface
-
Active Active clustering is a good candidate for applications which can be broken into logical segments as well. An application which handles Provisioning on one database server, and Ordering on another. Perhaps one which handles Financial data on one and business function on another. Etc....
While this is still effectively the same thing as mentioned above (two seperate apps), some people might not realize that the logial seperation of different functions within a single application could be viewed or treated as two apps. This is a common scaling technique many larger companies use, with subsets of the common data either replicated between the servers, or linked server calls performing updates across the servers, etc...
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply