Re: SQL 2008 clustering with Windows 2008

If you are just building a tw0-node cluster, the safest heartbeat network is a crossover cable.

Never team the crossover network.

You can team the public NICs, but you need to put them on different switches to really make that highly redundant.

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


"OceanDeep via SQLMonster.com" <u46587@uwe> wrote in message news:8bb8dc51b2e6a@xxxxxx
Geoff,

So far the failover configuration is working correctly and now I am working
on the network configuration for clustering. I come across a knowledge base
article from SQL 2008 BOL, 258750, which is about heartbeat configuration on
a cluster server for windows 2000 and windows 2003. I assume it is still
appliable to Windows 2008. Let me know if this is not true.

It seems like that we need at least two or more network switches to make this
redundency work in case of network outrage. Based on the article, one network
adapter in a node will be dedicated just between the two nodes and the other
network adapter from each node will be connected to a network switch. I am
not sure if that the other adapter from each node should be connect to a
different switch. Is there a diagram out there that I can see what the best
connection/switch configuration are? If there is no such diagram, can you
explain how many switches and the connection scheme between the two nodes and
switches?

OceanDeep

Edwin vMierlo [MVP] wrote:
Geoff,

[quoted text clipped - 4 lines]
same disk? If so, if I need to assign a disk for MSDTC, I should also set up
another disk for it just like I did for quorum.

Yes, or as Geoff mentioned put it in the SQL Application and use a Disk
already configured

In other words, instead of
four disks from the Raid disks I have, I should set up five disks (with five
[quoted text clipped - 10 lines]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ocean

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-clustering/200810/1


.

Relevant Pages

  • Re: Windows 2008 bizarre cluster issue
    ... Then we went through all the network ... having run out of troubleshooting items for the server configuration ... First I would try to break any and all teaming, ... Cluster servers are IBM blades ...
    (microsoft.public.windows.server.clustering)
  • Re: 3 and 4 node heartbeat network
    ... I suspect your team leads were using hubs or low end switches ... isolated vlan for just the nodes used in that cluster. ... and rely on the public network for redundancy. ... The vlans ensure ...
    (microsoft.public.windows.server.clustering)
  • Re: Clustering across teamed / trunked adapters
    ... Windows Server 2003 ... Network adapter teaming and server clustering ... Recommended private "Heartbeat" configuration on a cluster server ...
    (microsoft.public.windows.server.clustering)
  • Re: Question for the Group
    ... If the whole VMS cluster was affected, ... Such incidents were one of the reasons to leave VMS for greener Unix ... the technical staff who designed the configuration, be they local, HP/ ... VAXStations clustered over the network died, ...
    (comp.os.vms)
  • Re: Cluster in IBM Bladecenter HS20
    ... > fails the whole cluster becomes unavailable. ... >> then you public network). ... >>> configuration is certified by the Windows Server Catalog. ...
    (microsoft.public.windows.server.clustering)
Quantcast