tag:blogger.com,1999:blog-2157078164517103759.post2873538757369380178..comments2023-07-31T03:31:57.774-07:00Comments on A Static State: Part 3 - FAST for SharePoint 2010 Physical ArchitectureJason Apergishttp://www.blogger.com/profile/01817509015412502702noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2157078164517103759.post-38906095411499185612011-02-18T08:14:11.818-08:002011-02-18T08:14:11.818-08:00A four farm configuration is a very common place t...A four farm configuration is a very common place to start. I am going to have to give a generic response - sorry about that. I say right up SLA around what you can support, test and have a plan on how you plan to add in more boxes or reconfigure services when you need to.Jason Apergishttps://www.blogger.com/profile/01817509015412502702noreply@blogger.comtag:blogger.com,1999:blog-2157078164517103759.post-63453614694720816312011-02-17T15:26:56.123-08:002011-02-17T15:26:56.123-08:00Hi Jason,
Here is a question on a medium size co...Hi Jason,<br /> Here is a question on a medium size configuration. I would have:<br />1. Admin with query, web analyzer, and 12 docprocs<br />2. Non-Admin with Content Dist. searchengine, and doc procs<br />3. QR server with content dist. column 0 and doc procs<br />4. QR index-dispatcher, column 1<br /><br />About 40 million docs, different indexing (some once a month others once every couple of hours. Low QPS is expected maybe at most 5 to 10. <br /><br />Do we need another row which is a substantial cost. Don't we still have Fault Tolerance if one of the QR servers go down?<br /><br />Thanks.<br /><br />Mark<br /><br />MarkSmith0306@att.netUnknownhttps://www.blogger.com/profile/16198096503534722466noreply@blogger.com