Re: Cluster without a domain controller

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



So what is the real risk with having each cluster node also acting as a DC?

Normally, your DC has much more traffic and processing to do than your clusters, but in this case, his DC is only handling the requests from the two cluster nodes and that's it. There is no other authentications going on, since he doesn't have a domain.

If each of the Nodes is also a DC and Node-1 is Active and Node-2 is standby DC (clearly the DC's are not actually clustered), then what is the actual risk?

What I mean by "what is the risk" is, technically, what issues will arise from this config? (aside from marketecture and documentation)

"Russ Kaufmann [MVP]" <russ@xxxxxxxxxxxxxxx> wrote in message news:%23Oo4%23$LrHHA.4300@xxxxxxxxxxxxxxxxxxxxxxx
"Kenny Speer" <kenny.speer@xxxxxxxxx> wrote in message news:5122C787-2483-42A9-855C-0862424B2A52@xxxxxxxxxxxxxxxx
I'm sure I'll get flamed for it, but just run "dcpromo" on your cluster nodes. Have one of them be the active DC and the other one be a backup DC. You can then also run a DNS on each node and forward your requests to your real DNS servers. This will work, albeit may not be supported by MS, or at least it's not recommended.

Let's go back to step one when dealing with High Availability, Kenny.

First, you do a risk analysis. As part of the risk analysis, you will work with management to decide what risks to mitigate and which ones you will just need to accept.

Something you should NEVER do, is add more risk with your design.


--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp

The next ClusterHelp classes are:
July 10-13 in Denver
July 16-19 in New York

.



Relevant Pages

  • Re: Metabolic syndrome doesnt exist, diabetes groups claim
    ... >> believing in something greater than the sum of these risk factors. ... Absence of underlying mechanism. ... Put simply a cluster of risk factors exist ... >> multiple symptoms or are they multiple diseases that just happen to ...
    (alt.support.diabetes)
  • Re: Cluster without a domain controller
    ... MVP - Windows Server - Clustering ... justified is if the cluster is being deployed to a DMZ and there is no ... Windows Server 2008 Readiness Team ... What I mean by "what is the risk" is, technically, what issues will arise ...
    (microsoft.public.windows.server.clustering)
  • Re: Metabolic syndrome doesnt exist, diabetes groups claim
    ... > there is no need to believe in something greater than the simple sum. ... But even if the risk factors are merely additive, ... Put simply a cluster of risk factors exist ... > multiple symptoms or are they multiple diseases that just happen to ...
    (alt.support.diabetes)
  • Re: private network setup on 4-node cluster
    ... I have identified mis-management of the switch as a risk to my ... cluster. ... To mitigate the risk, I would replace it with a dumb hub or a smart ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster without a domain controller
    ... You also have to ask why even cluster it, because AD makes itself available when you have more than one DC. ... MVP - Windows Server - Clustering ... If each of the Nodes is also a DC and Node-1 is Active and Node-2 is standby DC, then what is the actual risk? ... As part of the risk analysis, you will work with management to decide what risks to mitigate and which ones you will just need to accept. ...
    (microsoft.public.windows.server.clustering)