Hello,
In a lab, I've been trying to setup an A/A cluster that will sit behind
BizTalk. This should hopefully, closely mirror our Prod environment. It is a
learning exercise for new team members. I am really struggling and kinda
want to start over with my plan. Our formal installation documentation is
being re-written as I work because the existing docs are worthless garbage.
Also, the lab has VM's.

From Prod environment, I know this:
1. Each physical server has a hostname which is in DNS.
2. Each server has a virtual name, also in DNS.
3. There is a cluster name. Maybe a clustername on each node, but not sure
on this.
4.

Based on my past trials and failures, I want to start by knowing the
following.

1. What DNS records/aliases do I need. I'm thinking the following for each
node in the cluster:
A. Normal hostname record for the server.
B. The clustername (maybe more than one for each type of instance (SQL,
SSAS, MSDTC))
C. Each virtual hostname. I may be confused on the wording her, but I think
each server has a virtual name which may be first part of the instance name.
D. How many IP addresses do I need. I think 3 per node (hostname, virtual,
and clustername, 1 clustername for each service (SQL, SSAS, SSIS))

The other part of my problem is setting everything up in Cluster Admin
console. In lab, it is already included in the VM image that is handed to
me. It has the following groups: I don't know about or understand why any
exist or their purpose.
1. Cluster Group: IP Addr, Name, MSDTC, Quorum
2. Group 0: Its empty. Purpose unknown.
3. MSDTC Group: IP Addr, Network Name, Physical Disk.

I did not note the resources defined under the Cluster Config tree.
Under Networks, I have the LAN, and the private heartbeat.

During SQL Setup, I struggled greatly with the virtual name. It seems I did
not have the virtual names in DNS and they were needed. Named Instances
should always be INST1 and INST2. In Prod, our servernames and vitrual names
are like this:
For first node:
Phys. Hostname: Server123A - Will be node A
Virtual name: ServerPRDSQL123A
Instance name: ServerPRDSQL123A\INST1

For 2nd node:
Phys. Hostname: Server123B - Will be node B
Virtual name: ServerPRDSQL123B
Instance name: Server01PRDSQLB\INST2

I know this is a lot to digest but I wanted to be complete as possible.

So, questions in summary:
1. What needs to be in Cluster Admin. What are each of these and what's
the purpose.
2. What DNS entries are needed?
3. How many IP addresses are needed?
4. During the SQL install, how do I match up all this, stuff?

I'd love a nice KB or other document which answered these questions, or
provide a nice novice-level description of the config and install process.

Thanks in advance,
Rich

See if this helps.

http://searchsqlserver.techtarget.co..._needs_URL.pdf


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"DetRich" <DetRich (AT) discussions (DOT) microsoft.com> wrote

Thanks for the reply Geoff.

I already have this document. It's intro level and does not provide the
details that I'm looking for.

Thanks,
Rich

"Geoff N. Hiten" wrote:

Some of the questions you are asking show that you don't have all of the
concepts of clustering correct, hence the recommendation of an introductory
document.

Typically, as you create the cluster and the virtual instances, DNS entries
get registered automatically. That is if your network settings are correct.

The virtual resources (cluster, Virtual server name, etc) are independent of
each host node, so you only need a single IP for each resource group, not
for each group per each node.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"rich" <rich (AT) discussions (DOT) microsoft.com> wrote