Re: Newb Active-Passive / Active-Active Single Instance Question

Tech-Archive recommends: Speed Up your PC by fixing your registry

Glen

Different terminology all meaning the same thing (more or less)

GROUP = INSTANCE = VIRTUAL SERVER

Example, an SQL Virtual Server is a SQL Instance installed in a Group

NODE = Physical machine which can "run" one or more Cluster Groups
(Instances/virtual servers)

16 Instance Cluster, on 4 nodes
First of all each cluster will have a cluster group, containing the Cluster
Name, Cluster IP addres and a Disk (for Quorum)

then 16 groups, each of them containing
- IP address
- Network Name
- Minimum of 1 disk, more if the application requires, more than likely you
will have more disks.
- the Application (e.g. SQL)

Then, depending on the usage of MSDTC, this could be either in the cluster
group if MSDTC only have light usage OR you could have a seperate group for
heavy MSDTC usage, this group would contain
- IP address
- Network Name
- 1 Disk
- MSDTC

there you have it, this would be a configuration of a 16 instance cluster

Now, each of the nodes could run between ZERO and ALL groups. Obviously, for
performance reasons you will spread the groups equally (based on use) over
the 4 nodes.

Does this explains it ?



"Glen" <Glen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:18FF19FE-B8F6-45C1-B5E4-C93542770828@xxxxxxxxxxxxxxxx
The confusion is still there where do you make the differentiation of
INSTANCE and Cluster GROUP? - Is it your reference to GROUP is a physical
cluster node?

The intention is to expand this cluster for more application in about 6-8
months hence the use of mulitple instance on a node is to allow some level
os
expansion with the existing hardware

The 16instance on 4nodes, if someone lay out how Microsoft did this in the
test bed for their benchmarking whitepaper in terms of examples of:
- Disk
- Servername/Instance (I get this a bit but to my understanding this can
be done is different ways?)
- Memory
- IP addresses (real and virtual, con only have 4 real)
- Virtual server

This should aliviate all confusion.


--Glen



"Edwin vMierlo" wrote:

response in line


"Glen" <Glen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:67F4289D-38A3-4BE3-8640-D4730987C0AE@xxxxxxxxxxxxxxxx
Hi I still want to be clear on this singe and multiple instance.

There is a Design for 3 applications (EPO, LCS, Helpdesk) on a 4 node
SQL
2005 Cluster. The intension for the redundancy is 2 Active 2 Passive
nodes
so
there is a 50% fault-tolerance. The Disk space is SAN storage.

The intention is the Helpdesk is intensive and will be an instance on
one
node and one virtual server. The EPO and LCS however are less
intensive
and
were designed to be on another node. So the question is:
- Will this now be 2 instances (EPO, LCS) on a single node and is this
now
one or two virtual servers. I thinking it will be 2 VS.

If EPO and LCS applications can run in 2 Groups, I would recommend this,
as
they can independantly fail over from eachother. If however one of the
applications cannot run without the other, and therefore there is a
dependancy, then you must put them in 1 cluster Group.



- Now how does it configure multiple IP addresses for each instance on
a
cluster node as it is no longer like Windows Clustering is it that SQL
2005
have a different cluster admin console?

Each cluster group will have to contain an "IP resource" and "Network
Name
resource" and therefore each group can be used with a seperate IP/Name
from
the network.



- Now on the failover is it that a single instance can failover if it
fails
or only all the instances on the node must failover.

A single group can move independantly from Node to Node.




I am still confused as to how the 16instance 4nodes work with:
- Disk
- Servername/Instance (I get this a bit but to my understanding this
can
be
done is different ways?)
- Memory
- IP addresses
- Virtual server

Thanks a mil.

Sorry Glen, I do not understand your question ? Above you talk about 3
instances, now you are talking about 16... please specify your question
more
clearly

HTH,
_Edwin.





.

Relevant Pages

  • Re: New to clustering and need some clarification on disk resource
    ... "Geoff N. Hiten" wrote: ... second node, only the primary, during a cluster install. ... Senior SQL Infrastructure Consultant ... enough disk space for all your data. ...
    (microsoft.public.sqlserver.clustering)
  • Re: New to clustering and need some clarification on disk resource
    ... The clustered disk should have MDF and LDF files. ... Did you look at the SQL setup logs to see what went wrong? ... Microsoft SQL Server MVP ... running, quorum is clustered and running, cluster is healthy and i got 29 out ...
    (microsoft.public.sqlserver.clustering)
  • Re: Default or named instances??
    ... this with SRV records, i didnt see a _sql records, lots of other types.. ... I've setup the cluster and tried to install the second instance as ... For each instance I need a virtual server name and an instance name ... The second named instance is accessible by the new virtal servers' name ...
    (microsoft.public.sqlserver.clustering)
  • Re: Default or named instances??
    ... The SQL alias name becomes the service name. ... It has to be a named instance. ... I will have to disagree with the analogy you gave though about treating the cluster as a single system and that's exactly what I'm trying to resolve here. ... According to your explanation about the relationship between SQL instance and virtual server I would change the analogy to say I could treat the VIRTUAL SERVER as I would a single system. ...
    (microsoft.public.sqlserver.clustering)
  • Re: about another instance of virtual server on sql2000 cluster
    ... Multiple instances on a cluster look and act just like multiple ... Microsoft SQL Server MVP ... > the new instance of sql virtual server is myclustersql02\myclustersql02 ... You can specify the same path, and the install will create a ...
    (microsoft.public.sqlserver.clustering)