Re: Clustering Question

Edwin,

Thank you for your post. I would like to mention that I have been working as an IT administrator for the last 5 years and the last 10 in hardware component assembly, and like most I have developed websites in the past. I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. Just not sure which software would best suit my needs. Now about the internet connection. I was using DSL and Cable as a reference only. I am sure that it is going to take more like a T1 or T3 connection to support the traffic especially after the site gets rolling.

I am trying to get all of this in mind before I start the project. I thank you again for your help.


If there is anyone else who would like to chime in I would love to year your suggestions.

Bryan




"Edwin vMierlo [MVP]" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:O0ZBDLrIIHA.4592@xxxxxxxxxxxxxxxxxxxxxxx
wow, such a system would take a lot of postings to work out here in a
discussion group.

Surely you need an internet connection, but surely the SLA you get on "Cable
modem" and "DSL" connections is far from what you need for hosting a site.
But lets leave this asside for the moment.

Re-read the posts already in this thread, there is a lot of info already
given on clustering and SQL.

Re-read the post from Mathieu CHATEAU, which clearly lists all components
(times two) to do a very simple web hosting app in HA setup.
2 x server with Microsoft 2003 Web Edition (for NLB your website)
2 x server with Microsoft 2003 Entierprise Edition (for MSCS)
2 x SQL 2005 standard Edtion licenses
And your network gear : 2 routers, 2 switches, 2 Firewalls
and then 2 different ISP's for your connection
-> and this list is a very minimum list of equipment for hosting a website.

Lets start with Basic Inventory, for just one component of Mathieu's post,
the SQL cluster :

Do you want to cluster SQL ?
- then you need to get MS Windows 2003 Server Enterprise Edition, to start
with. 2 licenses one for each node in the cluster.
- NO small business editions

What version of SQL ? 2000/2005 ?
- If the answer 2005 and you are only a 2 node cluster, then you can use SQL
2005 standard edition.
- If the answer is 2000 then you need Enterprise Edition.
- If you will go to more than 2 nodes in your cluster then the answer is
Enterprise Edition for both 2000 and 2005.
- NO small business editions

Do you have Hardware which is on the Windows Catalog ?
You need a full cluster solution which is on the Windows catalog in order to
build a supported cluster, this means all hardware, servers, switches, HBA
and your shared storage is on the Catalog as one qualified solution. If it
is not, it might work, but don't call in for support when things go hairy. I
suggest to talk to your hardware vendor to get quotations.

So, now we have nothing done yet, just listed an inventory.
None of the above is really cheap, so you really need to ask yourself if you
are moving in the right path here.

Clustering is not as simple as "I have two boxes, lets slap them together"
And definitely not done (=impossible) with Small Business Edition.

It seems to me that you are quiet new to this, which is OK, I remember how I
struggled when trying to design the first web app I put on the wire.
I would advice you to hire a company with a proven track record in building
this type of setup, and get them to give you assistance.

Rgds,
Edwin.






"Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
news:B64780D6-6FFA-43D5-8A38-7799CFE37DCF@xxxxxxxxxxxxxxxx
What we are developing is an online auction site. (Hence high reliability)
Would we not need an internet connection?

Thanks,

Bryan

"Edwin vMierlo [MVP]" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:#6FuX0gIIHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
> Bryan,
>
> you cannot install Cluster (MSCS) on a Small Business Edition, you need
> Enterprise Edition or Datacenter.
>
> And what are you doing with Cable connections and DSL connections ?
> If you are clustering an SQL server (as per all posts in this thread)
> surely
> you want to do this behind a firewall, not connected to the internet.
>
> Rgds,
> Edwin.
>
> "Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
> news:%23Hx4KsgIIHA.6068@xxxxxxxxxxxxxxxxxxxxxxx
>> So let me see if I have this right. Here is what my situation is.
>>
>> I will have two computer (nodes)
>> One computer will have Window Server Small Business Edition with Cable
>> Internet
>> The Other computer will have Window Server Small Business Edition With
>> DSL
>> Internet And 1 Instance of SQL Server Edition deployed to both
machines.
>>
>> Is this correct?
>>
>> Thanks,
>>
>> Bryan
>>
>>
>> "Russ Kaufmann [MVP]" <russ@xxxxxxxxxxxxxxx> wrote in message
>> news:363DBB7D-2DF9-4485-831E-3E53DB004A32@xxxxxxxxxxxxxxxx
>> > "Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
>> > news:OSIqHu8FIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
>> >> Thanks for all the replies. But I am a little confused. If both
> machine
>> >> don't have Sql installed and running how would they be redundant?
> Would
>> >> you not need at least two machine running the same software?
>> >
>> > When you install an instance on a cluster, you install the instance
>> > (the
>> > install of SQL) to all nodes if you want to allow it to run on all
> nodes.
>> > When you install a second instance (another installation of SQL in a
>> > different location), then you install it to all nodes if you want it
to
> be
>> > able to run on all nodes.
>> >
>> > Then, to make it active/active, you run one instance on one node and
>> > run
>> > the other instance on the other node.
>> >
>> > Thus, instance1, if it fails on its active node, it will failover to
>> > the
>> > other node because all of the installation files are there for that
>> > instance. If instance2 fails on its active node, it will failover to
>> > the
>> > other node because all of the installation files are there for that
>> > instance, too.
>> >
>> > Refer to the books online for more information about instances and
how
> to
>> > install SQL on a cluster.
>> >
>> >
>> > -- >> > Russ Kaufmann
>> > MVP - Windows Server - Clustering
>> > ClusterHelp.com, a Microsoft Certified Gold Partner
>> > Web http://www.clusterhelp.com
>> > Blog http://msmvps.com/clusterhelp
>> >
>> > The next ClusterHelp classes are:
>> > Dec 10 - 13 in Denver
>> > Jan 21 - 24 in New York
>>
>
>


.

Relevant Pages

  • Re: Clustering Question
    ... You could make a test environnement through Virtual Machine to get a picture on Cluster. ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)
  • Re: Cant get SQL 2000 installed on new node in Cluster
    ... You can apply a service pack to a new node without taking the Virtual SQL ... server offline. ... When the install is asking for a virtual server name, ... one for the MSCS cluster or the one for the SQL cluster? ...
    (microsoft.public.sqlserver.clustering)
  • Re: Exchange 2007 CCR on Windows 2008 x64 RTM
    ... install guide, but I always did it too quickly after the failure. ... I'm an MCITP on Server 2008 & Exchange ... I'm told that this is caused by the way the cluster service creates the ... respond to the start or control request in a timely fashion occured ...
    (microsoft.public.exchange.setup)
  • Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... SQL Server 2000 EE ... I had a three-node A/A/P cluster. ... Install SQL 2000 binaries on newly added node for Instance 1 ... "All cluster disks available to this virtual server are owned by other nodes." ...
    (microsoft.public.sqlserver.clustering)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)