Re: 2 Default instances on Active/Active
- From: "Anthony Thomas" <ALThomas@xxxxxxxxx>
- Date: Sat, 10 Mar 2007 12:49:26 -0600
You must also keep in mind that at any time, all instances may be running on
a single node (i.e., you take one node down for maintenance), and as such,
you need to be able to separate out the binaries for each instance, both
physically and logically.
Although it may appear to be transparent to you, each instance MUST listen
on a different TCP port and/or pipe name. If you are running each instance
on a separate node, and each is listening on TCP 1433, whenever a failover
occurs, the second (or subsequent) instance will fail to bind to TCP because
another instance already has TCP 1433 locked.
Although you can configure the installation to use Dynamic Ports, we prefer
to use static port assignments, for stability, and because many of our
systems must be accessible through the inner firewall.
The listener (SS2K UDP 1434) or Browser Service (SS2K5) provides instance
name to port/pipe translation, for both cluster and stand-alone systems with
multiple instances. The only difference in a clustered configuration is
that each instance must also have a dedicated virtual server name. However,
although abstracted, multiple instances must be configured as if they all
could run on a single physical node simultaneously. The only way to
distinguish this is by instance name and TCP Port or Named Pipes pipe name.
Because it can be confusing for many of our end users, we reserve default
instance configurations for stand-alone instances only. All our clustered
configurations, even if they host only a single instance, use named
instances. We also use non-standard TCP port assignments in order to
logically determine the port, without lookup reference: Instance 1 uses TCP
11291, Instance 2 uses TCP 11292, etc. For SS2K5, we disable Named Pipes;
so, TCP is the only protocol (other than the local shared memory one) we
configure.
Sincerely,
Anthony Thomas
--
"Himanshu" <Himanshu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F9FD0F38-8DA8-4A00-8B73-A49B72477EE8@xxxxxxxxxxxxxxxx
I just setup my first 2 node Active/Active SQL Cluster and from what I cancluster.
tell you can have only one (1) default instance in an Active/Active
The other instance has to be a named instance. Is this correct, or am Icrazy?
appreciated :)
If so, I don't undertand why this limitation. Since the 2 SQL Servers will
always listen on 2 different IP addresses, and both are listening on port
1433, why can't I have 2 Default Instances? Is there a work around where I
can fool the cluster into having two Default Instances?
Thank you for reading this post - and all replies are very much
.
- Follow-Ups:
- Re: 2 Default instances on Active/Active
- From: pscvln
- Re: 2 Default instances on Active/Active
- Prev by Date: Re: "Setup failed to perform required operations on the clustered nodes" - SP4 install on failover node
- Next by Date: Re: "Setup failed to perform required operations on the clustered nodes" - SP4 install on failover node
- Previous by thread: Re: 2 Default instances on Active/Active
- Next by thread: Re: 2 Default instances on Active/Active
- Index(es):
Relevant Pages
|
