Re: nodes will not shut down

From: John Toner [MVP] (jtoner_at_DIE.SPAM.DIE.mvps.org)
Date: 01/18/05


Date: Tue, 18 Jan 2005 09:54:59 -0500

Jog,

NT was a different animal...and if you had no downtime in an 8 year period,
I believe that this had more to do with luck and the size of your business
than your cluster configuration.

In an ealier post, you said it would be possible to make another node a DC
and move DNS to this node. This would be highly recommended, and also move
all operational master roles to this non-clustered DC. If this were my
environment, I would set it up with this external DC/DNS, and then perhaps
use one of the cluster nodes (the passive or least taxed node) as a
secondary DC. This way, your environment will still continue to function if
you lose one server.

You also mention that the private NIC didn't have a DNS record, and uses
itself for DNS. You might want to read through the following KB for the
recommended settings for the heartbeat NIC:
http://support.microsoft.com/kb/258750

Regards,
John

"Jog Dial" <JogDial@discussions.microsoft.com> wrote in message
news:68308A72-59D1-47BD-AA17-93C5B3EFB48E@microsoft.com...
> Ok, two severs, that's £1000 each, two more copies of windows 2003 server
> £500 each, that's another £3000 pounds. UPS to keep them up, another
£600.
> That aint exactly peanuts - when I'm fairly sure there is a way to make
what
> I have work... just because nobody else has figured it out... like I say,
I
> had an NT cluster as PDC and BDC (which everyone fretted about) work
> perfectly for over 8 years and the cluster never failed during that time
and
> that was before a lot of people even knew what clusters were. I guess I
just
> don't give up that easily and buy my way out of problems. I didn't have
DNS
> thrown into the equation I'll admit, but as I can see everyone here seems
to
> be loaded with more money than brains or will to figure things out, I'll
> leave it at that and work it out myself. Don't get me wrong, I do
appreciate
> the advice, but if I can make it work as well as my last cluster, then my
> company will be very happy and 0% downtime for a cluster over 8 years is
> pretty track record in my view anyway.
>
> Thanks
>
>
> "Russ Kaufmann" wrote:
>
> > "Jog Dial" <JogDial@discussions.microsoft.com> wrote in message
> > news:F5E1C205-FA25-4112-AEB3-0FD6C6F14EC1@microsoft.com...
> > > Hi,
> > >
> > > Thanks for the pointers, I can see a number of things to look for,
however
> > > I
> > > can't agree with dumping the cluster nodes as DCs.s I only have one
other
> > > DC, If that goes down, I have no DCs. I've been running an NT cluster
for
> > > the last 6 years, one PDC, the other BDC and I never had a single
problem
> > > with it and I had no other DCs. So far, I've been very happy with
2003
> > > e2k3
> > > as cluster as well, but this problem has cropped up, recently as well,
it
> > > wasn't doing this to begin with... There is some form of DNS
funkyness
> > > going
> > > on as it is registering the private addresses in DNS - the links you
gave
> > > speak of this and hopefully I can get that fixed as I think that the
> > > private
> > > network is the root cause of the problem.
> > >
> > > We run a pretty small shop here, currently only three servers on this
> > > network, but I use a cluster as I need it to be up all the time, we
only
> > > have
> > > about 50 users on it and the machines are way over spec in every way,
and
> > > I
> > > just don't agree with not running DCs on them. That may be what's
causing
> > > my
> > > problem in a roundabout way, hopefully geting the DNS straightened
out
> > > will
> > > solve the problem - at least I've got quite a few things to try now.
> >
> > OK, I am confused. Uptime is extremely important to your company. Yet,
you
> > are running a configuration that is likely causing your problems. So, is
> > uptime important or not? If so, buy two low-end servers for your DCs and
get
> > the DC functions off of your cluster. The low-end servers are not going
to
> > cost much at all. Small drive, single CPU, 512 MB of RAM, and you are
ready
> > to go.
> >
> >
> >



Relevant Pages

  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... Second, in your hosts file, you put a hostname and IP address. ... Private Cluster Network: 192.168.x.x ... No DNS required. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... I was explicitly stating that the cluster comm was NOT used just for the hearbeat. ... MVP - Windows Server - Clustering ... The routing stack in the host uses it in the following order: lmhosts, hosts, dns and wins. ... is it finds the host IP in the hosts file and no network requests are required. ...
    (microsoft.public.windows.server.clustering)
  • Re: DNS is picking up the heart beat address of the 2nd cluster node
    ... DNS is picking up the heart beat address of the 2nd cluster ... The problem I am having is that DNS is picking up the 2nd nodes ... > heart beat address of 10.0.0.2. ...
    (microsoft.public.windows.server.dns)
  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... As for the hosts file. ... hence you only add the cluster Nodes in the file. ... does nothing with a properly configured systems and DNS. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... I am not about to argue that DNS can be an issue. ... you mentioned a hosts file for the private only? ... MVP - Windows Server - Clustering ... http://www.clusterhelp.com - Cluster Training ...
    (microsoft.public.windows.server.clustering)