Windows Server

Rob Carey · Guest

Good Day folks,

Here is what I am looking at accomplishing.

2 front end SharePoint Server 2003 web servers, load
balanced doing all work for internal sites except SQL.
1 SQL 2000 server for above mentioned web servers.

1 Front end SharePoint Server 2003 web server doing all
work for external sites connected to same SQL server as
above.

All front end servers will be connected to an Alteon
switch for load balancing.
Is that a viable solution for a small farm?
We expect alot more traffic on the internal sites then
the external so are only worried about that.
How would one accomplish this? Is there some
documentation somewhere, I have looked but dont see it.
Will the alteon switch work for load balancing or is
there another reccomendation?

Any information is greatly appreciated.

Thank You!!

Mike Walsh · Guest

Can we assume that both your Front-End Servers are going to be Windows
SharePoint Services servers rather than SharePoint Portal Server 2003
servers.

Your "SharePoint Server" web server is unfortunately a name that is
somewhere between the two.

Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please reply to the newsgroup

"Rob Carey" <anonymous@discussions.microsoft.com> wrote in message
news:127601c4f736$3848db50$a501280a@phx.gbl...

Guest

Hey Mike,

Thanks for the quick reply.

The plan is ts use the full version, the one you need
licensing for as we are to believe that is is more
scaleable for future growth. The two for the internal
sites would be identical boxes, hosting identical sites
for load balancing.

Mike Walsh · Guest

SharePoint Portal Server 2003 (the full version) has its own newsgroup at

microsoft.public.sharepoint.portalserver

so if that's really what you intend to use, you should ask there.

They will have people who have set up large and medium-scale farms.

Warning if that's what you mean you'll need servers for Indexing and Search
too !

Mike Walsh, Helsinki, Finland

<anonymous@discussions.microsoft.com> wrote in message
news:187601c4f73a$40dcc2f0$a301280a@phx.gbl...

Daniel Larson (www.portal · Guest

Rob,

As Mike pointed out-- there are HUGE differences in configuration between
SPS 2003 and WSS. Unless you know your need for SPS 2003 (SharePoint Portal
Server), you may only need WSS (Windows SharePoint Services).

SPS 2003 has very specific configurations that are supported-- and you're
proposed setup isn't supported. I believe you need a few boxes plus the
database box to cluster up SPS. (You need 1+ front end box with web and
search, 1 index and job box, plus the db) I could be mistaken-- read the docs
on MS.com.

On the other hand-- with Windows SharePoint Services only you can cluster 1
to n front end boxes without having to worry about configurations. The
supported configurations for WSS are much more flexible.

Do you have any notes you can share as to your intended use of the portal--
have you planned this out? This may determine whether ytou need or want SPS
or just WSS. (Note that SPS is an application built on top of WSS... so there
is a lot of crossover but there are a few specific issues for SPS).

Daniel Larson
http://www.portalbuilder.org

"Rob Carey" wrote:

Rob Carey · Guest

Daniel and Mike,

Thanks for the information. After some talk with the crew
here it looks like we have decided on just Windows
SharePoint Services 2.0 instead of the Portal version.
We are still looking at doing some type of farm
configuration for both redundancy and availability.
We have a seperate SQL server that the databases will be
hosted on.
What I was thinking would be to have 2 frount end web
servers for the intranet and one for the extranet and
have these connect to the same sql 2000 server.
These are on HP BL20P blade servers and have 3
10/100/1000 NIC's in them.
I have looked at what documentation I found and have a
general idea but could alway's use a fresh mind!
I am assuming that we have to set up some load balancing
withthe 2 frount end intranet web servers or can I use
out Alteon switch for that?
What would you reccomend for a solution?
Any pointers that you can offer?

Thanks Again!

Daniel Larson (www.portal · Guest

Rob,

That sounds good. You can use Windows Load Balancing/clustering services
(part of Windows 2003 Enterprise... not sure about Standard) to do the
clustering or any other clustering strategy-- it doesn't matter too much. You
can add just about as many WSS servers to the cluster as you want to scale
that sucker out.

It sounds like that's a good strategy. Remember that you can always add a
Portal Server instance on your intranet side and tie in content from the WSS
servers. The search capabilities of SPS (Portal Server) are pretty nice.

As far as pointers-- I recommend getting a good strategy for WHAT you want
or HOW you want to use the sites. If there is a specific need I recommend
thinking about building out site templates for specific solutions, although
the built in Team Site template is pretty flexible for general purpose use.

For the extranet, are you using Windows accounts or anonymous access? Let me
know if you need any help.

Daniel Larson
http://www.portalbuilder.org

"Rob Carey" wrote:

	Windows Server Forum Index -> Windows Services	All times are GMT
Page 1 of 1