Re: Small to medium web farm configuration question

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



The reasons are straightforward. My client wants the availability of the
two-server web farm. We've used that configuration for their external
website and they like the ability to do system/site maintenance without loss
of service. But they don't necessarily want to purchase an additional server
and licenses (Windows and SPS) for the index/job server. Since they're going
to the two-server web farm for availability more than for capacity, the
two-server configuration will give them more than enough capacity for one of
the two servers to handle the load of the indexing and job services.

Bottom line, they want the high availability of two web servers, but don't
see any benefit to separating the index and job services onto a separate and
third server.

Zoe
"Engelbert" <Engelbert@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23wcotijDGHA.740@xxxxxxxxxxxxxxxxxxxxxxx
> You probably can. I think we're all saying the same thing namely that's
> it's more efficient to split your servers in the way Bill lists.
>
> No doubt you can have two front-ends and pile all the rest into one server
> but why do it when all the expertise available to you here advises against
> it (or at least proposes something else as better) ?
>
> Engelbert
>
> "Zoe Hart" <zoehart@xxxxxxxxxxxxxxxxx> wrote in message
> news:ekrMJThDGHA.3528@xxxxxxxxxxxxxxxxxxxxxxx
>> So if I want to limit myself to three servers, then I have to give up the
>> availability of the load-balanced configuration? Bummer. I don't
>> understand why, if I can run all the services on a single front end, why
>> I can't run them all on one of two load-balanced servers. Will it not
>> work or is it just not supported?
>>
>> Zoe
>>
>> "Bill English [MVP]" <bill@xxxxxxxxxxxxx> wrote in message
>> news:uFd3RuzCGHA.4068@xxxxxxxxxxxxxxxxxxxxxxx
>>> Probably SQL, WFE/Search and Index/Job.
>>>
>>> --
>>> Bill English, MVP
>>> www.mindsharp.com
>>>
>>> "Engelbert" <Engelbert@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:ePUgisxCGHA.3980@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Which three ?
>>>>
>>>> Engelbert
>>>>
>>>> (Thinking that two front-ends is excessive and prefering an Index
>>>> Server instead of one of them)
>>>>
>>>> "Shane Young [SPS MVP]" <Shane @ SharePoint911 dot com> wrote in
>>>> message news:eWVE7twCGHA.1028@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Read this.
>>>>> http://groups.google.com/group/microsoft.public.sharepoint.portalserver/browse_thread/thread/d3983f16d6f9229d/f0ecd2870f5e2a85?lnk=st&q=KB+888037&rnum=1&hl=en#f0ecd2870f5e2a85
>>>>>
>>>>> From what I have read of
>>>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;888037 you
>>>>> should be able to do it with 3 servers.
>>>>>
>>>>> --
>>>>> Shane Young - SPS MVP
>>>>> SharePoint911 - http://www.SharePoint911.com
>>>>> Blog - http://msmvps.com/shane/
>>>>>
>>>>>
>>>>>
>>>>> "Zoe Hart [MVP]" <zoehart@xxxxxxxxxxxxxxxx> wrote in message
>>>>> news:%23CVmWl$BGHA.1032@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> I've been reading a white paper "Capacity Planning for Microsoft
>>>>>> Office SharePoint Portal Server 2003" and its "Medium Farm" high
>>>>>> availability configuration includes 2 web servers, 1 database server,
>>>>>> and 1 index server. We are considering a 3-server configuration with
>>>>>> 2 web servers and 1 database server and I was wondering possible and
>>>>>> supported to put the index server on either the database server
>>>>>> (assuming both SQL and SPS installed) or one of the two web servers.
>>>>>> Or does going to multiple web servers require a separate, additional
>>>>>> index/job server? I understand that putting the service on one of the
>>>>>> two web servers will have a load/performance impact, but we're going
>>>>>> to the 2 web server configuration for availability and its likely to
>>>>>> result in excess capacity so that the index load/performance impact
>>>>>> should not be an issue. Are there other factors we should be
>>>>>> considering? Also, if I did run the service on Web1 and Web1 went
>>>>>> down, would it be a relatively simple/small configuration change to
>>>>>> turn on the indexing service on Web2 - a sort of manual failover in
>>>>>> the event that we aren't able to restore Web1 to working order in a
>>>>>> short time period?
>>>>>>
>>>>>> Thanks,
>>>>>> Zoe
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.



Relevant Pages

  • new backup server
    ... I've had the configuration and pricing set ... comments on my choice of tape changer, or comments on issues related to ... I have a number of hand-me-down Sun Enterprise 250 servers. ... Amanda seems to be flexible enough that I can just ...
    (SunManagers)
  • Re: Exchange 2000 - Domain Controller Failover - could not send or
    ... > ESM DSAccess tab as Global Catalog Servers. ... clients could not send or receive email. ... >>> Enterprise Configuration to the second DC and still no luck. ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Prblm: GAL and child domain, basically two different GALs. Wants shared GAL.
    ... I have just configured two Exchange servers in a customer's network. ... have two separate GALs, one for each domain, which is not very global. ... configuration looks the same in the Exchange System Manager on both ...
    (microsoft.public.exchange.admin)
  • VIPA Issue Routing Configuration
    ... servers, we have each with a 10/100 NIC on the general network. ... The issue we're encountering is that with a virtual interface configured, ... route be added to the server's routing table that directs traffic through ... The configuration of our servers was done as per the VIPA document on IBM's ...
    (comp.unix.aix)
  • Re: all the workstation and servers lost internet connection sudde
    ... > both servers have two NICs in the same subnet, ... > configuration and is the root cause of your problem. ... >> Ethernet adapter Local Area Connection: ...
    (microsoft.public.backoffice.smallbiz2000)