Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Configuration not supported?

  Asked By: Katie    Date: Aug 16    Category: Sharepoint    Views: 1074

I've got two nodes serving as a SQL cluster. I've got one machine acting as a search/index box and another functioning as an index/job server. Finally, I've got two machines running as WFE's. Any idea why it's saying it's not a supported configuration? Originally, I had intended for two of the servers to be search/index with one of them also support the job function but evidently it won't allow me to do this. What did I miss?



4 Answers Found

Answer #1    Answered By: Kalyan Pujari     Answered On: Aug 16

Your configuration  seems fairly close to a medium server  farm - you'd have to
make a couple changes to make it comply though.. you can have the same 2 WFE's,
but the search component needs to be enabled on those servers, with the
index/job components running  on the other machine. That would actually free up
1 server..

If you want to move to a large farm you would need at least 1 more server, and
change the search/Index server to a search only server, which would be the same
as your new server.

Here are the supported  topologies:

Small Server Farm.

* One server running sql  Server 2000 and one server running SharePoint Portal
Server 2003 assigned the Web, Search, Job, and Index services.

Medium Server Farm.

* One or two servers  running SharePoint Portal Server 2003 assigned the Web
service (more commonly known as front-end Web servers) and running SharePoint
Portal Server 2003 assigned the Search, Job, and Index services; and one server
running SQL Server 2000.

Large Server Farm.

* Two to eight servers running SharePoint Portal Server 2003 assigned the Web
service (more commonly known as front-end Web servers), two to four servers
running SharePoint Portal Server 2003 assigned the Search service, one to four
servers running SharePoint Portal Server 2003 assigned the Index service (one of
which must be assigned the job  Server role), and any number of servers running
SQL Server 2000.

Answer #2    Answered By: Jagdish Joshi     Answered On: Aug 16

One point I would like to add here...

Highly consider breaking the indexing/job function  off onto a
dedicated server  apart from your FEs/SQL. Not only will this bring
you into "supported" compliance, but with the indexing/job function on
a dedicated server, you can go to TOWN indexing massive amounts of
data very frequently without much impact to your farm performance
(User requests, browsing, SQL stuff).

It will allow you do have very powerful search and many content
sources with bigger indexes without impact to performance. The
indexing/job server is highly CPU intensive, and with this on a
separate box  you are not affecting CPU of your SQL server.

just a recommendation..

Answer #3    Answered By: Shara Johnson     Answered On: Aug 16

I'm going to modify my configuration  to do exactly this. I actually anticipated the need to off-shore the indexing function; my mistake was that I thought I could off-shore the search function  as well. At any rate, I've now got two wfe/search boxes, one index/job server, and two sql  nodes. I'll hold onto that extra box  for now and see if I can do something with it later.

Answer #4    Answered By: Christop Mcfadden     Answered On: Aug 16

Diversification of services is always a good idea, if the budget for hardware is available. Good suggestion.

Didn't find what you were looking for? Find more on Configuration not supported? Or get search suggestion and latest updates.