0

I was going to create a Windows Server Failover Cluster, in order to set up MS SQL Server AlwaysOn Availability Groups.

As a prerequisite of failover clustering, I've created and configured an Active Directory using two servers. One server is domain controller, another server is the member of the domain.

While following all the steps and suggestions of creating a failover clustering, I've found that all the nodes should be in the same Domain Role. As long as I understand, the domain must have at least one domain controller. And in order to create a meaningful Failover Cluster, there should be 2 or more nodes. This means that I need three server to setup a basic failover clustering with 2 nodes? One is domain controller, which is not going to participate in the clustering, and 2 others are domain members and are nodes of the failover cluster?

On other article, about Sql Server AlwaysOn availability group perquisites, the system/server/computer should not be a domain controller, but all the nodes should be domain members.

Ok, then I need three servers to setup two node (one primary, and one secondary replica) Sql Server AlwaysOn Availability Groups on top of a two node Failover Clusters (two domain members, and 1 domain controller)? How is that? Or I'm missing something, or it can be configured with only tow servers somehow?

Thanks.

2 Answers 2

2

There is some ambiguity in your question, but the following presumes you are talking about setting up a high-availability MS SQL environment on a Hyper-V failover cluster.

You are correct in so far as you will need a domain controller separate to the failover cluster nodes - for example, to reliably authenticate to the cluster nodes (some sysadmins set up a system in which the only domain controllers are VMs hosted on the failover cluster but this is inadvisable for fairly obvious reasons).

So your basic setup will be:


Domain controller on a separate server (can be run as a VM or on a physical server)

Failover cluster node 1

Failover cluster node 2


Now, your failover cluster nodes will share the role of hosting a bunch of VMs of your choosing, which you can set up after running through the failover clustering wizard in adding server roles to the physical servers. Two such VMs should be running MS SQL instances, which you can then configure for high availability as per the high availability guidelines you have. It is a good idea to distribute VMs which share roles between your cluster nodes, to minimise or completely mitigate any downtime if one of the nodes were to unexpectedly go offline at any point.

4
  • Sadly it is also wrong as the domain controllers can be virtual.
    – TomTom
    Dec 16, 2014 at 9:30
  • @TomTom I did quite clearly say can be run as a VM or on a physical server regarding the domain controller outside of the failover cluster - and there is nothing preventing the creation of further domain controllers as VMs on the failover cluster itself.
    – BE77Y
    Dec 16, 2014 at 9:37
  • and btw, do I also need a separate server and cluster node for iSCSI Storage?
    – Jack
    Dec 17, 2014 at 18:17
  • The physical servers will generally be running off internal storage, but the VMs they run/share on the failover cluster should be run off external storage accessible via redundant paths (for example via iSCSI, yes); see the MS documentation here
    – BE77Y
    Dec 18, 2014 at 8:56
1

You need at least three servers.

1x Domain Controller
2x SQL Servers

This, of course, assumes a lab or dev environment. In production, you will want at least one additional domain controller.

3
  • what do you mean? in production, 2 domain controllers and 2 sql servers? what is the role of another domain controller?
    – Jack
    Dec 16, 2014 at 8:58
  • 2
    Availability. Never run an Active Directory domain on a single domain comtroller in production, ever.
    – MDMarra
    Dec 16, 2014 at 9:10
  • 1
    That said it is totally valid to have 2 compuoters and run the 2 domain controllers virtual. FULLY supported since - hm - 2012 (or R2). Clusters do not need to find a domain to start and full virtual domain controller setups are supported.
    – TomTom
    Dec 16, 2014 at 9:30

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .