Questions about creating active active clustering server 2012 R2

Question

Aloha All,
Been a long time since I've posted in a forum, forgive my lack of etiquette if any.

Here's my scenario:

I have a 2012 R2 domain with two servers who's primary functions are, web-app<-(DC) and SQL database<-(member server). We are bringing them in-house from external hosting. They are VM just an FYI, and so I have as many copies of them as I may need in case I break it.... not that that would ever happen ;).

My end goal is to set up active/active clustering, with quorum disk (SQL database will reside here ) so the web app/SQL is high availability.

For my theory, I have two nodes: node 1 and node 2. Each node is identical and consists of the two servers Web-app and SQL.

My theory: (I will get any licenses needed for legitimacy, I just want to see if my theory works first)

I bring up Node 1 leaving it in its' original configuration, then bring up node 2 making sure Node 1 and 2 don't communicate. Set the services for the web-app/SQL in Node 2 to "disabled" prior to demoting the DC in Node 2. This effectively removes AD from Node 2, leaving two stand alone servers. Rename both Node 2 machines, then join them into Node 1's AD, promote Node 2's web-app server to a DC thus creating a single domain with the four machines and 2 DC's. Allow for replication, and presuming it doesn't blow up, I can then proceed to re-enable previously mentioned services, resolve any web-app/SQL errors, configure the cluster, move SQL to the quorum disk, reconfigure DNS, etc.

My question(s)(for the moment):

-Is this possible, and what issues will potentially crop up with the web app/SQL?
-Any other issues I may not be aware of?
-Both the web app and SQL rely on AD service accounts to operate, so I understand they will not work once AD is removed. However--- if I set the web app and SQL services to "disabled" prior to removing AD, then turn them back on when joined to the new(original) AD, will that help prevent issue with the web app and SQL since it will see the original service accounts again?

Sorry for the confusion if any, I tried my best to be concise and provide as much detail as possible without making it sound like gibberish.

Any input and guidance is greatly appreciated.
Mahalo! (thanks)

RS

Answer 1

Hi,

Based on my understanding, currently, you have two Domains, each domain has two machines, one DC running web app, one member server running SQL service. You would like to merge the two domains, four machines together into one domain, and do clustering for web app and SQL service. If I misunderstand it, please feel free to let me know.

According to your description, I think you may have some misunderstandings about Cluster theory, and your theory may not work:

1. Firstly, when we talking about "cluster Node", it should be one machine and running the same services. Cluster node should not be two machines.
2. DC can't be a cluster node, DC should be set up standalone out of cluster. As far as I'm concerned, to achieve your goals, we should do the following steps:

a. Create a new VM in each domain, join the domain, then migrate the web-app service to the new VM. Let DC only running AD services and DNS services.

b. In domain 2, migrate SQL service from domain 2 to domain 1.

c. In domain 2, migrate web-app service from domain 2 to domain 1.

d. After all services in domain 2 to domain 1, demote DC in domain 2. Then repromote the DC and join domain 1.

c. Then install failover cluster feature in SQL server 1 and SQL server 2, webapp server 1 and webapp server 2.

d. Form Cluster 1 with SQL server 1 and SQL server 2, form Cluster 2 with webapp server 1 and webapp server 2.

Please note, cluster nodes should run the same services, so I suggest to create two clusters, one SQL cluster and one webapp cluster. If we want to use the four servers to create one cluster, we need to install SQL services in webapp too, and install webservice in SQL server.

Besides, cluster quorum is storage, can use file share or quorum disk, cluster quorum can't store SQL services.

And actually, I think each step above is complex, such as migrating SQL service from one domain to another, and create an SQL cluster, If you are not experienced, I would suggest you learn more about the theory before practice.

And if it is a production environment, I would highly recommend opening an advisory case with MS to design the plan for you.

Below is the link to open an advisory case with MS:

https://support.microsoft.com/en-us/gp/advopsmgr
Thanks for your time!
Best Regards,
Anne

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi Anne,

Thanks for your guidance, this is the first time I've done any type of clustering and clearly have a lot to understand yet... 

My end goal is to create redundancy for the web-app and SQL production servers. I have two physical servers that are identical, to which I installed the two vm clients: 1 sql server and 1 web app server. So I have two physical machines that contain the exact same vm clients; one set up is an exact copy of the other. I also have a 3rd physical machine I set up with FreeNAZ vm, was going to use that for Quorum disk and locate the SQL database as well. Should these two be on separate vm's?

What is the best way to reach my goal of redundancy?

Answer 3

Hi,

To be honest, it's not a few words can say. To much need to explain and don't know where to start.

Actually, you have two standalone hosts, the two are in totally different environments, different domains, different storage. While cluster should in same domain and use shared storage.

Best Regards,
Anne

Answer 4

Hey,

I assume that your goal is to create a Failover Cluster, where your VMs will be highly available and will start on the second host in case first one fails. Couple recommendations, spin up 2 VMs which will reside on local storage with DC roles inside, with replication configured between them. As for other VMs, you should put them on the shared storage and add them to the cluster. There are multiple shared storage options - separate SAN, Storage Spaces Direct or StarWind VSAN. S2D is available in Windows Server 2016 and higher, so you would need to upgrade your hosts. With 2 nodes and Windows Server 2012R2 (and higher) you can use StarWind VSAN. The following guide should help:
https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.