Re: SQL 2008 clustering with Windows 2008

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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: SQL 2008 clustering with Windows 2008
    ... If you are just building a tw0-node cluster, the safest heartbeat network is a crossover cable. ... You can team the public NICs, but you need to put them on different switches to really make that highly redundant. ... So far the failover configuration is working correctly and now I am working ...
    (microsoft.public.sqlserver.clustering)
  • Re: Strange results from a tcpdump, can anyone help?
    ... traffic was going ballistic on most ports in the network. ... Note that all switches do what looks like unicast flooding, ... As soon as those ports were taken offline, ... IP under configuration? ...
    (comp.dcom.lans.ethernet)
  • Re: Remote Access and Outlook Web Access on SBS 2003
    ... that's how the *Wizard* configured your network. ... NETWORKING CONFIGURATION SUMMARY ... Restrict default Web site of IIS to only respond to ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Access and Outlook Web Access on SBS 2003
    ... SUMMARY OF SETTINGS FOR CONFIGURE E-MAIL AND INTERNET ... Internet Connection Wizard. ... network, firewall, secure Web site, and e-mail. ... NETWORKING CONFIGURATION SUMMARY ...
    (microsoft.public.windows.server.sbs)
  • Circa 1976, Long Distance Network Mapping Project [telecom]
    ... I had the opportunity to do some university level work in the 1970s related to the cost of operation and ROI feasibility for long-line costs over the old Bell Operated Public Switched Telephone Network. ... calls would default to a route based on what was termed a "homing" priority. ... There were five levels of ranked switches, or a hierarchy of switches based on where calls needed to go. ... For example, under the strict homing hierarchy-topology, a call from Walla Walla, Washington to Moscow, Idaho - a distance of less than 100 miles - would route from Walla Walla, to Yakima, to Seattle, to Sacramento, to Denver, to Salt Lake, to Boise, to Coeur d'Alene and finally to Moscow. ...
    (comp.dcom.telecom)